yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
So I tested your print, and it did not pass... As I suspected actually, after this post of yours. What did pass was the ro.build.fingerprint. And judging by the device name, "river_retru_n", it makes me think that this is the XT1962-5 global device (maybe the Russian version, because of the ret

ru

). Not sure which device the other prints are for (device name being just "river"), but if I had to take a guess it would be XT1962-1, the US/Canada devices.
[Magisk] klausxda:
Fingerprint for Xiaomi Redmi Note 9 Pro (joyeuse)

untested, but found in the official ROM for Xiaomi Redmi Note 9 Pro (joyeuse) taken from here: https://c.mi.com//miuidownload/detail?device=1900378, file updater.script:

ui_print("Target: Redmi/joyeuse_global/joyeuse:10/QKQ1.191215.002/V11.0.5.0.QJZMIXM:user/release-keys");
[Magisk] Didgeridoohan:
Thank you. Considering that the current print I have, V11.0.4.0, has a security patch date of 2020-06-01, I'm guessing that this print would be 2020-08-01 (or maybe July). But, do you happen to know for sure?

Edit: turned out to be July.
[Magisk] LaCruz:
In my g973f I have to use default Fingerprint (A310). Any ideas to use both g973f?
[Magisk] Didgeridoohan:
I'm sorry, I don't understand. What are you talking about?
[Magisk] Kraznov:
Hey OP,

Would you mind checking if the Samsung Galaxy tab A 10.1 (2019) works (SM-T510)?

Security patch: 2020-07-01

ro.build.product: gta3xlwifi

fingerprint: samsung/gta3xlwifieea/gta3xlwifi:10/QP1A.190711.020/T510XXU3BTFN:user/release-keys
[Magisk] Didgeridoohan:
Fingerprints list updated to v100

Another momentous occasion! The fingerprints list has now reached the 100th release. 345 devices on the list, 494 prints in total. As long as Google isn't shutting us down for good (and yes, I know [MENTION=4470081]topjohnwu[/MENTION] has been speculating on Twitter, but that's just speculation and likely quite some time away if it is possible), keep 'em coming!

Today's update is sponsored by [MENTION=7786725]zgfg[/MENTION], [MENTION=7887589]SyberHexen[/MENTION], [MENTION=9506129]JarlPenguin[/MENTION], [MENTION=358748]smohanv[/MENTION], [MENTION=6897543]klausxda[/MENTION] and [MENTION=11072209]Kraznov[/MENTION]. Thanks for the prints!

New

Huawei P9 Plus VIE-AL10

Motorola Moto G7 XT1962-5

Samsung Galaxy tab A 10.1 WiFi 2019 SM-T510

Updated

Motorola Moto G7 XT1962-1

Motorola Moto G7 Power

Motorola Moto G7 Play

Redmi Note 9 Pro

Xiaomi Mi 10 Pro
[Magisk] smohanv:
Good work. Well done. Gone for a century. wow....
[Magisk] BlackVoltage:
Thanks a lot you two Didgeridoohan. I really did not see that even after you pointed it out to me :(

Works like a charm - with the right spelling

(Nevertheless the apps from "Deutsche kreditbank" still do not work (for some days the separation via "island" worked for that)
[Magisk] Didgeridoohan:
Do you mean DKB-TAN2go? That's a special little app, isn't it? Every time someone says they have issues with it detecting root I test and have zero issues opening it (I can not test further than opening the app, since I'm not a customer). But, that at least tells us that Magisk can hide from it just fine and that if you are having issues it is likely detecting something about your device that Magisk cannot hide. If Island worked that suggests that it is detecting something on your internal storage or one of your apps.

I'm always using the current Canary release on my devices. At the moment that is Magisk build 20420 and Manager 297 (hidden, with stub version 10).

This isn't the thread for further troubleshooting on specific apps detecting root, but you can always find help in the General support thread, there are lots of tips and tricks in my troubleshooting guide, and there are usually some discussions on this in Magisk's Github issues.
[Magisk] vhatp:
Hello,

I am having the issue with ctsProfile, while basicintegrity is ok.

With Your utility, the props menu claims a conflict:

1 - Edit device fingerprint (disabled)
2 - Improved hiding
3 - Edit MagiskHide props
4 - Add/edit custom props
5 - Script settings
r - Reset all options/settings
b - Reboot device

See the module readme or the
support thread @ XDA for details.

Enter 'e' to exit: 1
1

MagiskHide Props Config v2.1.6
by Didgeridoohan @ XDA Developers

=====================================
ro.build.fingerprint (disabled)
=====================================

Fingerprint modification currently disabled
because of a conflicting module.

I have created a printslist file (without extension) in the internal root, with the fingerprint of Sony Xperia XZ1 Compact.

The only other module installed is universal-safetynet-fix-v2-beta-5.

Is this a problem? Or what else could it be?

Thanks a lot in advance!
[Magisk] abacate123:
Yes, it's. Uninstall the Universal Fix module, then try this one again.
[Magisk] Didgeridoohan:
You already have your answer that it's the USNF module that's causing a conflict. It partly does the same thing, it replaces the device fingerprint with a certified one, so that's why I disable that part of the module if USNF is detected.

And since it's doing the same thing, I'm curious to know if you'll have any luck with this module.

There's already a fingerprint for that device in the module, so there's no need to create a custom list... Unless you have a different one you want to use, of course.
[Magisk] abacate123:
Don't underestimate your own module haha. I mean, I've tried many times with USNF and it simply didn't work at all, sometimes it even didn't install, and when it installed, it broke my Magisk, and I had to reinstall it through TWRP. Also that module is outdated.

With your module, it works like a charm.

:)
[Magisk] russel5:
[MENTION=4667597]Didgeridoohan[/MENTION] thanks for this awesome tool. Find strange bug, when trying reset custom props (number 4) see this

sed: unmatched '|'

And props not reset only deactivated.
[Magisk] Didgeridoohan:
Thanks. Sounds like there's a typo in there somewhere... I'll take a look in a few hours.
[Magisk] russel5:
reinstall your module, bug is gone...:silly:
[Magisk] russel5:
[MENTION=4667597]Didgeridoohan[/MENTION] one more question

Why when added this lines

persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1

ctsProfiles makes false again?
[Magisk] Didgeridoohan:
Interesting...

Could you post the propsconf.log and propsconf_last.log please (they're in /cache)?
[Magisk] russel5:
Sorry but no, i delete this lines and do not want to write it again. If i have a time in a future to test this settings again, i post this logs.
[Magisk] Didgeridoohan:
Ok. Too bad... I could not reproduce the issue on my side though.
[Magisk] oslo83:
Thanks for this module.

Here is a new approved one for Honor 9 as the following update's B365 give cts error:

Honor 9=HONOR/STF-L09/HWSTF:8.0.0/HUAWEISTF-L09/364(C432):user/release-keys
[Magisk] Past2Present:
Samsung J5 2016 (SM J510FN) Android 7.1.1

samsung/j5xnltexx/j5xnlte:7.1.1/NMF26X/J510FNXXS2BRA2:user/release-keys

Verstuurd vanaf mijn SM-J510FN met Tapatalk
[Magisk] iBART:
Just a question; with LOS 15.1 I don't pass the test because there is no oreo fingerprint avaible, right?
[Magisk] Didgeridoohan:
You can use a Nougat, Lollipop, Kitkat, etc fingerprint on Oreo. All that matters is that the fingerprint is certified by Google.
[Magisk] abacate123:
As said above. I'd also recommend you to use your own device's stock build fingerprint, just in case. You can try others from the list if you wish too. It has nothing to do with Android version. Example, I'm using the fingerprint from my 5.0.2 stock rom, but I'm actually running AEX 7.1.2 here.
[Magisk] AserLaser:
When I write props Into terminal it says: SH: props: not found
[Magisk] Didgeridoohan:
That means somethings wrong... Please provide the logs mentioned under "Issues" in the OP.
[Magisk] AserLaser:
Here the logs

Havent all files mentioned tho
[Magisk] Didgeridoohan:
I think you forgot something... :p
[Magisk] Athing13:
Im not make xposed im make smali patcher,im sory im newbie
[Magisk] Didgeridoohan:
No worries. Everyone's a newbie at some point.

Good luck.
[Magisk] jenslody:
Newest rootbeer detects MagiskManager if it is not repackaged.

Everything else can be hidden as before.
[Magisk] yassouna51:
Here i found those in /cache
[Magisk] Didgeridoohan:
What Magisk version are you on? Could you post the Magisk log as well?
[Magisk] Didgeridoohan:
Update to v2.3.4

Just another small bug-fix release. And updated the module for [MENTION=4544860]osm0sis[/MENTION]' new Busybox release. If you haven't already, make sure you give that guy some appreciation (as in: donations, people! He works damned hard for free)!

Changelog

v2.3.4

Updated for Busybox v1.29.1. Thank you [MENTION=4544860]osm0sis[/MENTION].

Bugfixes. Because I'm blind.
[Magisk] coolhandz:
Alright, so my goal here is to get SamsungPay working on latest version. If i rollback to the previous version, it works fine when everything is hidden, but after the update it is obviously detecting root or Magisk itself in some way. I downloaded this module and enabled Improved Hiding without success. I've also enabled Hide Magisk in the Magisk app and have all Samsung related apps hidden.

My set-up: Pixel XL running ResurrectionRemix Build # rr_marlin-userdebug 8.1.0 OPM2.171019.029.B1 5c25905556 test-keys

I also have ElementalX-3.09 and am using Magisk 16.6

Would I be able to use the fingerprint for Pixel XL 8.1.0. that is listed in this module or will it cause it issues?

I have attached a log, but can't see what triggers SamsungPay to see root although I can see the line where it says root is detected.
[Magisk] Didgeridoohan:
This module can't do anything that would help with Samsung Pay. I've answered you in the Samsung Pay thread about that, to keep things on topic.

About device fingerprints:

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint
[Magisk] hari_hazz:
Could you please help me too pass Safetynet as before

Device : Mi 3W(Cancro)

Rom : MIUI 10 8.7.19(alpha build)

Device Fingerprint Selected from your lists (Still Error)
[Magisk] Didgeridoohan:
Everything looks like it should in your logs.

I still haven't had much of an opportunity to figure out why MIUI has issues passing the ctsProfile check. It's on the to-do list though and will be looked into in time (hopefully before Christmas). Some users have had more success on the Global builds (I see you're using the China build), so that might be worth a try.
[Magisk] MajinkenSword:
Hi, seems this module stopped working after the latest update and keeps on asking me to reboot my phone. Using a Huawei P20 Pro using RomAur v1.3.

Also, can you teach me on how to manually get logs?

Here's a screenshot for your reference.
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] jenslody:
I'm not sure if I read the logs correctly, but it looks like you run the scripts in the default boot-stage.

I currently had to change the boot-stage from "late-start service" (service.d) to "post-fs-data" (post-fs-data.d) to work.

Cts suddenly failed, probably after a change on googles site, or a new helper apk (downloaded by droidguard-app).
[Magisk] MajinkenSword:
Thank you. Here you go ?

Edit: Grr, weird, it doesn't want to attach the logs. I'll try again later
[Magisk] MajinkenSword:
Sorry, had to do this since 'edit' wasn't allowing me to attach these...
[Magisk] martyfender:
Unless something else is going on, when I hit the edit button, I then have to hit the advanced button every time I want to attach to an edited post. Yes, it is very annoying. It is the same with most of the option buttons above such as hide, etc..
[Magisk] Didgeridoohan:
Well... Those logs are for v2.3.1 of the module, so something is wrong (obviously)...

There wasn't a propsconf_install.log available? If there is, i would very much like to see that too. And, like it says in the docs, the Magisk log would also be useful.

If nothing else, an unusual - reinstall of the module might work, but I would very much like to see those logs first.
[Magisk] MajinkenSword:
Sorry, got confused and attached the logs inside the cache folder. Here are the ones from /data/cache.
[Magisk] hari_hazz:
could you please elaborate the procedure to do?
[Magisk] Didgeridoohan:
I've made sure to make the documentation for this module as extensive as possible, and it's found linked in the OP...

You want this part:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#boot-stage

I didn't suggest it to you, since it's previously been shown to not have any effect on MIUI, but it's worth a try.
[Magisk] jenslody:
If it's tan2go:

I use it myself without issues.

I use microG, hence no safetynet.

Tan2go has to be in the hidelist and the manager has to be hidden and all is fine, even tans get pushed via gcm or it's successor.

Latest canary by the way, of course.
[Magisk] LaCruz:
Using option 1) and option 2) with props.
[Magisk] Didgeridoohan:
I still don't quite follow what you mean, but I'll give it a shot.

If you're talking about the device model not matching the set fingerprint or your device when you use the "Force BASIC attestation" option, that is normal. A device that uses hardware backed key attestation can be fooled into using basic attestation by changing the model. That's how Google identifies which devices to use hardware attestation on...

More:

https://github.com/Magisk-Modules-R...master/README.md#my-devices-model-has-changed

If this isn't what you're talking about I'm going to need more details to understand.
[Magisk] nvrpunk:
I cannot pass cts, even on canary on my pixel 4, regardless of method. Anyone have any ideas outside the props module?

**adding to this, that i have the canary of magisk, and the eval type is Hardware**. seems like im ****ed.
[Magisk] Didgeridoohan:
Have you tried option #2 in the main menu of the props script, "Force BASIC attestation"? It's designed for your situation...
[Magisk] meric57:
Hello, after reinstating official firmware TH7 of my S10 and root TRWP + magisks.

All is ok except galaxy store I have a message see screenshot, is there a workaround against this problem, something must be changed build.prop.

Will there be an update of hardwareoff 1.1 or not

Thank you
[Magisk] Didgeridoohan:
First of all I have a couple of issues with that screenshot. It's huge! Better to attach it rather than embedding it in the post. And I don't speak french so it's kind of useless...

I'm guessing it's complaining that you don't have a compatible device or something along those lines.

I've got nothing to do with the Hardwareoff module, but I do have a feature in this module that works on the same principal and should be able to help with getting into the Galaxy store. Just activate "Force BASIC attestation". If the default setting doesn't help, try picking the S4 or S9 from the list instead (I've had reports those work fine).
[Magisk] meric57:
Hello Didgeridoohan, if I understand correctly to deactivate the magiskhide prop module and I just use warehardoff and with terminal I change to S4 or S9.

There is not for android 10 just android 8.
[Magisk] Didgeridoohan:
If you want to deactivate MagiskHide Props Config and only use the Hardwareoff module, but still have the Galaxy store working you'll have to manually edit the files in the Hardwareoff module and change the model props to match a device that doesn't use hardware attestation (like an S4 or an S9).

To me it sounds like you would find it easier to just remove Hardwareoff and activate "Force BASIC attestation" in MagiskHide Props Config. But instead of using the default setting use the "Pick from fingerprints list" option and pick the device you want to use (I'll likely change that menu option in the next update to "Pick from device list", to avoid confusion).
[Magisk] meric57:
Hello, I tried with S4 and S9 it doesn't work.

How to modify directly in Props, there is no explanation to modify the value of my SM-G973F galaxy s 10 thank you

When I look with explorer root in build.prop I still have G973F
[Magisk] Didgeridoohan:
When you say "it doesn't work", what exactly do you mean? The CTS profile check? Does your device still use hardware attestation? The Galaxy store? You need to be more detailed...

You need to understand that Magisk does not change the build.prop file.

Take a look in the module docs for a quick explanation:

https://github.com/Magisk-Modules-R...uildprop-doesnt-change-after-using-the-module
[Magisk] meric57:
Hello, here is the play store certify no worry magisk all is green in safety.

Just concern with galaxy store and my samsung account asks for password once I type I "processing failure" if I deactivate magisk its working, I saw on the forum a post which had to change the model of the telephone I find more .

I did with terminal: su / props / 1 / f / 26 / S9 and S4 tries 2 / Y / Y nothing to change after starting
[Magisk] Didgeridoohan:
That's why I mentioned changing the name of the "Pick from fingerprint list" option in the "Force BASIC attestation" menu...

I'm not saying that you should use the S4 or S9 fingerprint, but that you should use them for the "Force BASIC attestation" feature. So: props - 2 - f, and then pick the device you want to use for the model value.
[Magisk] meric57:
Thank you for your answer, I am testing certain model samsung S4 not s9 no, complicate you do not know a member who has successfully unlocked galaxy store and his samsung account.

On the net no problem the impossible to connect I will find the right choice in the list to suggest I keep you informed if I find thank you
[Magisk] Didgeridoohan:
I think I've already said this, but I've had reports of using both the S4 and the S9 will change evaluation type from hardware to basic and keep Galaxy store working.

Which is why I suggested those...
[Magisk] OhioYJ:
[MENTION=4667597]Didgeridoohan[/MENTION] here is the new Android 10 build prop for the Tab S5e:

---------------

Samsung Tab S5e

---------------

getprop ro.build.fingerprint:

samsung/gts4lvwifixx/gts4lvwifi:10/QP1A.190711.020/T720XXU1BTG3:user/release-keys

getprop ro.build.version.security_patch:

2020-06-01

getprop ro.product.manufacturer:

samsung

getprop ro.product.model:

SM-T720

*Edit, so I got my tablet back up and running (LOS) after going back to stock to get this key. Looks like this is another Samsung device that requires "Force BASIC key attestation" to pass ctsProfile now (using that fingerprint). Just as an FYI.
[Magisk] Some_Random_Username:
Hello, here are latest fingerprints for OnePlus Nord and EU variants of 8-series (latter is most likely a late respin of previous update 200808)

OnePlus Nord AC2001 (10): OnePlus/Nord_IND/Nord:10/QKQ1.200412.002/2009010217:user/release-keys__2020-07-01

OnePlus Nord European AC2003 (10): OnePlus/Nord_EEA/Nord:10/QKQ1.200412.002/2009010216:user/release-keys__2020-07-01

OnePlus Nord Global AC2003 (10): OnePlus/Nord/Nord:10/QKQ1.200412.002/2009010217:user/release-keys__2020-07-01

OnePlus 8 IN2013 (10): OnePlus/OnePlus8_EEA/OnePlus8:10/QKQ1.191222.002/2008150504:user/release-keys__2020-08-01

OnePlus 8 Pro IN2023 (10): OnePlus/OnePlus8Pro_EEA/OnePlus8Pro:10/QKQ1.191222.002/2008150503:user/release-keys__2020-08-01

Additionally, I've just noticed a small typo you made that got introduced two months ago along with fingerprint: HD1910 is 7T Pro, not 7 Pro :D
[Magisk] Didgeridoohan:
Module updated to v5.3.3, fingerprints list updated to v101

A few minor ui tweaks, but mainly a release for the fingerprints submitted over the past few days.

Thank you to [MENTION=7558004]lawrencee[/MENTION], [MENTION=3720814]OhioYJ[/MENTION] and [MENTION=8234677]Some_Random_Username[/MENTION] for the prints.

Changelog

v5.3.3

More (very) minor ui tweaks.

Added fingerprint for Samsung Galaxy J7 Neo SM-J701M. Updated fingerprints for OnePlus 8 IN2013, 8 Pro IN2023, Nord AC2001, Nord European AC2003 and Nord Global AC2003 and Samsung Galaxy Tab S5e SM-T720. List updated to v5.

There are 10 types of people in the world. Those who understand binary numbers and those who don't.
[Magisk] crok.bic:
Oh, that pun.. old but gold :D
[Magisk] ipdev:
That compleatly cought me offguard and made me laugh harder than I have in a few weeks. :D

Miss the science jokes though.. :p

Cheers. :cowboy:
[Magisk] lawrencee:
Thank you so much for this... really needed this update
[Magisk] pndwal:
Correct, 10 types; 11 types don't appreciate Gray Code... :laugh: PW
[Magisk] dr4go:
rofl, really nice one. [emoji1303]

Back to topic: [MENTION=4667597]Didgeridoohan[/MENTION] I may have a question / bug report, but it also may just be normal Magisk behavior... First of all I'm using my Galaxy S10 without twrp, but rooted with Magisk (therefore the phone is obviously still encrypted). In the beginning I struggled a lot with that, but that's irrelevant and offtopic. Whenever I flash a new build, I do it via Odin, followed by a reboot to recovery (sar without initramfs).

Already the last month I realized that when I spoof the device's fingerprint the phone doesn't rebuild the dalvik/art cache, which caused some force closes until I realized that. This month therefore I did the following: reset settings via props, power off, flashed via Odin. All went fine on my device, but I struggled a lot with my girlfriend's phone (S10e).

Reason (at least I believe to be the reason): the Magisk module got an update, but I didn't reboot after updating the module (Magisk was saying... "will be updated on next reboot"), reset settings via props, power off, flashing vis Odin...

Force closes all over the place, I couldn't even unlock the phone because it bootlooped that quick... After that I thought: ****, again the cache problem (this time it was worse though, because One UI got updated to 2.5). Thank god I managed to drop a reboot command in the end, which boots unrooted (to system, not recovery) and realized the device was updated, which updated the cache ("Optimizing apps...").

If you have twrp and / or an unencrypted phone, it's easy to fix that, but that is no fun on an encrypted sar device without initramfs.

Additional notes: Magisk's safe mode didn't help, which I found very strange, but it was my first time I wanted to use it and need to investigate further (previously I have always created core-only Magisk builds for such situations).

Additional bug (I realized that only yesterday, because I always use Magisk to reboot the device): when changing an option in your module and pressing 'r' it reboots to system on those devices and you'll end up being unrooted.

Thanks for everything! [emoji256][emoji482][emoji256]
[Magisk] Didgeridoohan:
Hm... Changing prop values can cause issues on a device. I don't think I've heard of this one in particular before, and I haven't experienced it myself. Unfortunately I haven't really got anything in a way of explanation/solution for you.

Yes, updating the module will create a folder in /data/adb named modules_update. That's where Magisk places the updated files, since it can be bad for the system if Magisk tries to update already magic mounted files (that are found in /data/adb/modules). During the next reboot the files in modules_update will be merged with into the modules directory.

During the module update the module files in /data/adb/modules_update will be edited to reflect the current settings. But, when you do a reset of the module the /data/adb/modules_update directory is not taken into account, causing the system.prop file to be merged back from modules_update at the next reboot and the fingerprint and whatever other props you've set will still be active. But not reflected in the module when running the props script. Easily fixed by setting a new fingerprint or prop since this will reload and create a new system.prop file.

It's a bit of an edge case, but I'll get this sorted in the next update.

This I would love some details on. What do you mean with "didn't help"? Where modules still active?

Yeah, that's a thing with the recovery patched devices. Regular reboots will simply boot straight into an unrooted system. That's how Magisk is designed... I'll think about if there's an easy way for me to work around that.