yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Changelog

v6.1.2

Release notes

Added rudimentary tampering check.

Added fingerprints for OnePlus 9RT, Samsung Galaxy A52 4G and Xiaomi Mi 6X and Redmi K30 Pro. Updated fingerprints for OnePlus 6 to Nord CE, many variants. List updated to v137.

Spoiler content hidden.
[Magisk] Didgeridoohan:
Current fingerprints list version

The fingerprints list will update without the need to update the entire module. Keep an eye on this thread for info about updates.

When you run the props command it'll be updated automatically, or run the props command with the -f option if you've disabled automatic updates of the fingerprints list (can be done in the script settings). The list can also be updated from the "Edit device fingerprint" menu.

Current fingerprints list - List v137

Spoiler content hidden.
[Magisk] Didgeridoohan:
Nice and shiny new support thread. And while moving everything over I also found what the issue was with the old one and why I couldn't update the OP of that one... :laugh:

Oh well... It's done now.

Will be back shortly with some new fingerprints added to the list (well, they've already been posted in the old support thread, but I'll add them to the module). :good:
[Magisk] skullkid383:
I was worried when I seen last thread close lol
[Magisk] Didgeridoohan:
Update to v2.1.6-v15

Tiny update, mainly some fingerprints.

v2.1.6

Added some new fingerprints (Sony Xperia Z, Sony Xperia Z1, Xiaomi Redmi 4 Prime, Xiaomi Redmi Note 5/5 Plus), list v15. Thank you [MENTION=9129635]0LDST4R[/MENTION].

Very minor improvements that doesn't even deserve their own release, or changelog.
[Magisk] hari_hazz:
Please add support for Mi3/Mi4(cancro)
[Magisk] Didgeridoohan:
Untested, but collected from the official Xiaomi firmware downloads:

Xiaomi/cancro/cancro:6.0.1/MMB29M/V9.5.2.0.MXDMIFA:user/release-keys

I won't be updating the fingerprints list for a single print though, so meanwhile you can enter it manually (if it works, like I said: untested).

Note to self: make sure to update the fingerprint collecting instructions.
[Magisk] belphegore:
I have a Galaxy S6 with 8.1, is it possible to choose the fingerprint provided with 5.0.2? What could happen if I choose the Google Pixel 8.1 fingerprint or something else?
[Magisk] Didgeridoohan:
You can use whatever fingerprint that's certified with any device. Using a different device's fingerprint will make your device seem like that device though.

If you can provide an updated fingerprint for the S6 (I believe the official release is currently on Nougat), that would be great. There are way too many devices out there, and even though I sometimes search for fingerprints myself, I very much rely on users providing certified fingerprints and updates for them...

Edit:

I had a few minutes free and tracked down this one:

samsung/zerofltexx/zeroflte:7.0/NRD90M/G920FXXS5EQL1:user/release-keys

Haven't tested it yet, but if it works I'll update the list later.

Also found the S6 Edge while I was at it... Same thing there, untested:

samsung/zeroltexx/zerolte:7.0/NRD90M/G925FXXS5EQL1:user/release-keys
[Magisk] belphegore:
I tried the Pixel with 8.1 on the S6 and it works. If I have to install 7.1.2 stock I will post the fingerprint for you.
[Magisk] Didgeridoohan:
Fingerprints list updated to v16

Added fingerprints for the Samsung Galaxy S9 and S9 Plus. Thank you [MENTION=7166349]turbolukex5[/MENTION].

Also added a fingerprints for the Samsung Galaxy S6 Edge and Xiaomi Mi 3/4.

Updated the fingerprint for the Samsung Galaxy S6.

The list will automatically update when you run the props command, or you can do it manually from the "Edit device fingerprint" menu if you've disabled automatic updates.

I also finally updated the tips on how to find a certified fingerprint for your device. You'll find them in the documentation on GitHub. I also updated the documentation index in the OP to reflect the documentation update.
[Magisk] hari_hazz:
Thank you so much..

Device : Mi3/Mi4 (cancro)View attachment 4503408
[Magisk] Semela:
Hey guys could someone, please, help me?

I successfully installed TWRP+magisk but I can't pass ctsProfile on my mi max 2. (miui 9 global beta 8.4.19)

I downloaded this module and since there is no fingerprint for my phone I decided to find one in the official rom. I unpacked it, and found updater-script. However, I got lost here.

What exactly am I supposed to look here for?

This is what I see there

https://pastebin.com/xj8h3mL4

What should I use as a fingerprint after "Xiaomi Mi Max 2=" ? SHould it be like this:

Xiaomi Mi Max 2=Xiaomi/oxygen/oxygen:7.1.1/NMF26F/8.4.19 ?

This is my current fingerprint: Xiaomi/oxygen/oxygen:7.1.1/NMF26F/8.4.19:user/release-keys

Thank you.
[Magisk] Didgeridoohan:
You need what's printed after "Target:". But as you see that's the same as your current fingerprint...

ui_print("Target: Xiaomi/oxygen/oxygen:7.1.1/NMF26F/8.4.19:user/release-keys");

I tested your fingerprint, and it passes the CTS profile check just fine. You have something else going on...
[Magisk] Semela:
Damn.. Is there any way I could troubleshoot it?
[Magisk] CGA_d3:
Device: Pixel 2 XL

ROM: 8.1.0 (May 5, 2018) (OPM4.171019.016.B1, May 2018, Fi Carriers) (f28b4a9b2c25ae32c6d0506e41f89473ef43662d197c97c49b38966abdbfdb7f)

ctsProfile: true

basicIntegrity: true

Fingerprint:

google/taimen/taimen:8.1.0/OPM4.171019.016.B1/4720843:user/release-keys

Note: enabling Xposed Framework (SDK 27) v90.2-beta3 gets you basicIntegrity: false
[Magisk] Didgeridoohan:
That will always happen, and the ctsProfile: true result is because of the No Device Check Xposed module rather than this module.
[Magisk] CGA_d3:
I know this module won't hide Xposed, I just wanted to warn users like me who have to enable it for work purposes. Until last week I was getting ctsProfile: false, but basicIntegrity: true; and suddenly this week all the Google apps stopped working, so I have to disable Xposed when I'm finished using it.

Cheers!
[Magisk] kaisar11:
anyway to pass safetynet with xposed installed
[Magisk] Didgeridoohan:
Wrong thread. Answer is: nope.

(Take a look at the large friendly red letters in the OP.)
[Magisk] navalynt:
Huawai P20 Pro (CLT-L29) working fingerprint for devices that are region C432 (or that have been converted to C432)

HUAWEI/CLT-L29/HWCLT:8.1.0/HUAWEICLT-L29/128(C432):user/release-keys
[Magisk] thugzie:
Anyone can help with fingerprint for Mi8?
[Magisk] slimdick:
Xiaomi MI4C working fingerprint from last MIUI Stable 9.5.2

Xiaomi Mi 4C (7.0)=Xiaomi/libra/libra:7.0/NRD90M/V9.5.2.0.NXKCNFA:user/release-keys
[Magisk] tomaasz:
Hi

Are you able to successfully hide root for nc+ GO app ? MagiskHide can not
[Magisk] Didgeridoohan:
Doesn't look like there's much available for the Mi 8 yet. I'd ask around in the Xiaomi forums.

You're in the wrong thread really... And it doesn't help to post the same query in several different threads.

If the tips found here can't help you, there's nothing this module can do. If you need further help, the general support thread is more suited for your query. Make sure to accompany your post with plenty of details and preferably logs.
[Magisk] rajivshahi:
Will it still work after removing magisk or it needs magisk to be present to work..
[Magisk] Didgeridoohan:
Magisk is required. If you don't want to use Magisk, you can quite easily make the modifications the module does systemlessly, to the actual build.prop file. You just need root and a file explorer...
[Magisk] rajivshahi:
Thanks for your quick reply...
[Magisk] Didgeridoohan:
Update to v2.3.0-v19

Time for another update.

This time I have (apart from a bunch of optimisations and new fingerprints) added two new features.

You can now delete prop values from your system ([MENTION=5129165]esgie[/MENTION], this one is for you) with the "Delete props" option. See the documentation for more details.

There's also now a feature in the module to save all the relevant logs and files when troubleshooting. Use the "Collect logs" option in the script (or the -l option) and then attach the resulting packaged file to your post. As alwasy, more details are found in the documentation...

And lastly, here's the changelog.

Changelog

v2.3.0

Added a function for removing props. See the documentation for details.

Added a function to collect and package the logs and relevant troubleshooting files for easy uploading.

Updated and clarified the documentation on how to use the configuration file.

A bunch of improvements and tweaks. Several of which may go horribly wrong.

Updated and added bunch of new fingerprints (Asus ZenPad S 8.0, Huawei P20 Pro, Samsung Galaxy S8, Sony Xperia XZ1 Dual and XZ1 Compact, Xiaomi Mi 4C and Redmi Note 3 Pro SE), list v19. Thank you to [MENTION=4688377]russel5[/MENTION], [MENTION=7166349]turbolukex5[/MENTION], [MENTION=3885843]allrockedout[/MENTION], [MENTION=1765068]navalynt[/MENTION] and [MENTION=2567034]slimdick[/MENTION].

Don’t turn your back, don’t look away, and don’t blink! Good luck.
[Magisk] Didgeridoohan:
No... What I meant was "I would ask around there, if I where you". As in: you should ask around in the Xiaomi forums. :good:
[Magisk] kullurumanoj:
Hi [MENTION=4667597]Didgeridoohan[/MENTION],

I'm using this module from months... when I was on miui global rom beta this module helped in fixing safety net and CTS profile mismatch and later I moved to miui china beta rom and CTS profile is not matching from long time ,I have taken logs from the latest beta release...

Thanks in advance
[Magisk] Didgeridoohan:
Everything looks alright there, but you could try changing the boot script to post-fs-data (under script settings) and reboot.

If it still doesn't work, run the "Collect logs" option again and post the propslogs.tar.gz file that'll be saved to your internal storage.
[Magisk] thugzie:
oooh! ok i get it now ;)

thanks anyway :)
[Magisk] cFendez:
Please add support for Mi MIX 2 (chiron)

Thanks!
[Magisk] Didgeridoohan:
Since I don't have time to get one myself, here you go:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] kullurumanoj:
Heyy man , it's still same ,still CTS is failing... I have followed the steps as you said and attached the file.

Thanks in advance
[Magisk] Griasahi:
[MENTION=4667597]Didgeridoohan[/MENTION]

Samsung Galaxy J5 2015 (6.0.1)

samsung/j5lteub/j5lte:6.0.1/MMB29M/J500MUBU1BQE1:user/release-keys
[Magisk] Didgeridoohan:
I don't know what solution you're looking for... And from your description it doesn't sound like you need the feature anyway. If you just need to pass SafetyNet there's no need to enable device simulation.

If you really want to have the feature enabled you can always try to find which prop is causing your issue (disable them all and then enable one by one until you find which one is causing your problem) and just disable that one.
[Magisk] dra 99:
Hello, can you help me?

So, here it is

I am on ROM xiaomi (stockrom) safety net fix there are no obstacles

then I moved to the custom cm12 rom, then it was constrained in cts Profile: false then how to overcome it?

I want to use this module and I still don't understand what else to do next when it's in the menu props

My device is Xiaomi Note 3 for CM12 base,
[Magisk] garylawwd:
Change device fingerprint to whatever you want. It doesn't have to be your specific model but to be safe pick something close to your models specs or pick your model if its there. Reboot and done.

Everything you need to know is in the documentation you just need to read.
[Magisk] dra 99:
thank you for the information, now safetynet on my custom ROM has become a fix ??
[Magisk] dafaher:
Thank you very much ipdev but Didgeridoohan told me that I didn't need this module because my device already passed both the ctsProfile and basicintegrity checks, so I uninstalled it. Thanks for your support!
[Magisk] Didgeridoohan:
Well, if you could possibly post your working device fingerprint here it could possibly help others with the same device. You can simply use the getprop command to get ro.build.fingerprint, and possibly ro.build.version.security_patch if your device is new enough.
[Magisk] dafaher:
I'm not sure if this is what you asked, I hope I have done well:

ui_print("Target: samsung/espresso10wifixx/espresso10wifi:4.2.2/JDQ39/P5110XXDML1:user/release-keys");

My device is a Samsung Galaxy Tab 2 7.0 (GT-P3110), and I'm running this rom:

https://xdaforums.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798

It's an old tablet, but it has been so faithful to me that I'm not ready to let it go. When I installed Magisk, it recommended me to update to the latest version of Magisk Manager and that's what I did. Then, I ran a check and immediately passed the ctsProfile and basicintegrity checks, I didn't have to do anything else (except the settings that everyone recommended me to block Pokemon Go, although it didn't work and keep saying that my device isn't compatible). That's when I installed MagiskHide Props Config but you told me that if I passed both checks this module couldn't help me, and I uninstalled it.

Hopefully someone finds this information useful, at least to know that this tablet can run Magisk without problems. And while I still couldn't solve the PoGo issue, Magisk rooted my tablet instantly, I double checked it with Root Checker :)

Thanks for all your support, Didgeridoohan!
[Magisk] michaelmaverick:
Newest Xiaomi Mix 2S fingerprint: Xiaomi/polaris/polaris:9/PKQ1.180729.001/V10.3.3.0.PDGMIXM:user/release-keys__2019-05-01
[Magisk] Akhil3472:
Hi ..

Magisk hide doesn't work for yono sbi app - app not working force exiting

Can anyone have solution for this ...plz reply
[Magisk] Didgeridoohan:
Not the correct place... This is for discussing the MagiskHide Props Config module. You want to go to the general support thread or find any other thread that deals with hiding root from banking apps.

Before you go though, I tested it and can hide root from the app perfectly fine. You're at a disadvantage though if you're using Android 6... More details here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Didgeridoohan:
I just noticed that there's no security patch date accompanying this fingerprint. I'll need that as well...
[Magisk] iPusak Gaoq™:
Here is the new fingerprint...

Xiaomi/laurel_sprout_eea/laurel_sprout:9/PKQ1.190416.001/V10.3.5.0.PFQEUXM:user/release-keys

Security Patch Date : 2019-07-05
[Magisk] Bob1313:
I just installed MagiskHide props config and I changed my build.prop with a terminal (edit device fingerprint), now I can see a green (enabled) next to it, but when I go to the google play store it still sees it as my samsung galaxy s3 (I edited it to an s6). I clear cache and data on both google play and services app, but it still shows my old phone. Anyone has any idea? Thanks in advance.
[Magisk] ipdev:
After setting the new fingerprint, you could try:

1. Logging out of your Google account(s), then clear PlayStore cache and storage. Reboot and log back in.

2. Disable PlayStore, clear the app cache and storage. Reboot, enable PlayStore app and reboot again.

Note:

- 1 is annoying if you have multiple accounts logged in.

- 2 may cause errors while PlayStore updates are uninstalled and the app is disabled.

Reason for the extra reboot. You will also fall back to the system installed PlayStore version until it updates.

I haven't had to do it lately but, the second option is the one I use.

Might be a big hammer approach but, always worked for me. :silly:

Cheers.

Edit:

Quick test on my Poco and neither 1 or 2 worked for me.

Google did not alert me or email about logging in a new device.
[MENTION=10064832]Bob1313[/MENTION] Device simulation may help but, I'm not sure.
[Magisk] Didgeridoohan:
Is there any reason you need the Play store to see your device as a S6 rather than S3? I've personally only seen the device change like that in the Play store when changing my fingerprint to a Google Nexus device, and I change my fingerprint back and forth all the time when testing... I might not keep it with the new print long enough for it to register though.

Like [MENTION=7280276]ipdev[/MENTION] says, the device simulation feature might work for you, but keep in mind it's a feature that sometimes causes issues when activated.
[Magisk] ipdev:
Speaking of fingerprints. Got a little sidetracked.

Nothing new, just some updated fingerprints.

Pixel(s), Essential PH-1, OnePlus 5T and 7Pro, Poco F1.

Cheers all.

Edit:

So OnePlus gave us another update for 5T.

9.0.8 with August security date.
[Magisk] elreydenj:
Has the newest android 9 fingerprint for the Pixel 3 XL been added to the list [MENTION=4667597]Didgeridoohan[/MENTION]? The one for august security patch? It does not show in the list when you go to props in terminal and it chooses a verified fingerprint. I believe someone listed it a few pages back.

---------- Post added at 01:29 PM ---------- Previous post was at 01:29 PM ----------

Has the newest android 9 fingerprint for the Pixel 3 XL been added to the list [MENTION=10040679]digd[/MENTION]eridoohan? The one for august security patch? It does not show in the list when you go to props in terminal and it chooses a verified fingerprint. I believe someone listed it a few pages back.
[Magisk] Didgeridoohan:
It has not.

It will be.

No ETAs...

(Probably this weekend.)
[Magisk] elreydenj:
Thank you. I was trying to add it manually and I must have made a mistake. What exactly would I need to enter to do it myself. Thank you for your time.
[Magisk] Didgeridoohan:
Just copy paste it in terminal (after entering the "Edit device fingerprint" menu). Don't forget the security patch date...

You can also use the configuration file.

Edit: or the custom list.
[Magisk] elreydenj:
Got it. Security patch date is determined by the kernel correct?
[Magisk] jcmm11:
getprop ro.build.version.security_patch

And no, it's not determined by the kernel. You could have a kernel with a different patch set running. e. g. - a custom kernel that hasn't been updated yet.
[Magisk] arpio:
Updated fingerprint for Asus Zenfone Max M1 (ZB555KL):

asus/WW_X00PD/ASUS_X00P_4:8.0.0/OPR1.170623.032/15.00.1907.103:user/release-keys

Security Patch: July 5, 2019
[Magisk] ipdev:
Awhile back, (if I remember correctly) someone was looking for a OnePlus 7Pro 5G print.

OnePlus released a 5G update today. Had a little time to kill so. ;)

One more fingerprint for the next update.
[Magisk] Didgeridoohan:
Fingerprints list updated to v62

I was really hoping to have some time for a proper update to the module this weekend. I did not... Too much work. Anyway, I have a whole bunch of new fingerprints that a lot of nice people have submitted over the past month so I figured I could at least push those. Here they are. A small note: there was one print submitted that I haven't added to the list yet, the Xiaomi Mi A3. Turns out that this particular print might have exposed a small bug in resetprop that needs to be taken care of first.

Thank you to [MENTION=9506129]JarlPenguin[/MENTION], [MENTION=7530018]oslo83[/MENTION], [MENTION=6965378]dafaher[/MENTION], [MENTION=6043888]DN38416[/MENTION], [MENTION=9637474]michaelmaverick[/MENTION], [MENTION=7280276]ipdev[/MENTION] and [MENTION=9665703]arpio[/MENTION] for providing those prints. You guys are awesome!

Edit: Oh yeah. Forgot... The list will be updated when you run the props command, or (if you've disabled automatic updates) by using the -f option or from the Edit device fingerprint menu.

New and updated prints:

New

OnePlus 7 Pro NR

Samsung Galaxy Tab 2 7.0

Updated

Asus Zenfone Max M1

Essential PH-1

Google Pixel

Google Pixel XL

Google Pixel 2

Google Pixel 2 XL

Google Pixel 3

Google Pixel 3 XL

Google Pixel 3a

Google Pixel 3a XL

Huawei Mate 20 Pro

Motorola Moto G5S

OnePlus 5T

OnePlus 7 Pro

Xiaomi Mi Mix 2S

Xiaomi Pocophone F1
[Magisk] xunholyx:
Just so you know, I used the old FP for Pixel 2XL from July on Qpp6 and it was working for G Pay. Updated to Aug version though now that you've updated
[Magisk] leipnacht:
Please add support for device ZTE Nubia Red Magic 3

nubia/NX629J/NX629J:9/PKQ1.190321.001/eng.nubia.20190715.220013:user/release-keys

Security Patch: 2019-03-05

Thank you
[Magisk] Makishima:
I used the module to change my device fingerprint which made ctsprofile go green immediately, so that worked great, but then I couldn't uninstall any apps, the phone soft rebooted immediately and I also couldn't log in on new apps, the app just crashed. My launcher, Hyperion, also crashed and the phone said it caused a problem and that I should delete it, but... Well, I couldn't. :P As soon as I reverted the fingerprint, everything worked fine.

Something I did wrong? I chose the fingerprint that matched my phone's model but I didn't see any choices to match the ro.build.version.security_patch date. And as I said, ctsprofile was enabled.

Hope the logs show something.
[Magisk] Didgeridoohan:
You've done nothing wrong, but you could test something:

Set the fingerprint up again, but before rebooting go to the module directory, /data/adb/modules/MagiskHidePropsConf, edit system.prop and remove the line that starts with ro.vendor.build.fingerprint. Then reboot and see if that works better.
[Magisk] Makishima:
It seems to work now! Thank you so much! Now to certify Play Store... or get rid of it. :victory:

EDIT: It worked just fine, then I thought I should clear my Play Store data and reboot to see if it gets certified... and now I have the same problem. Can't download apps, can't uninstall apps (forces soft reboot), can't log into apps. I could before the reboot! Why would that happen?...
[Magisk] Makishima:
[MENTION=4667597]Didgeridoohan[/MENTION] I have reverted the changes once again.... If you have any ideas why this might be happening, please tell me. Thank you.
[Magisk] Didgeridoohan:
Can you clear the Play store data without this happening if you don't have the fingerprint active (just to make sure)? Other than that I don't really know...
[Magisk] Makishima:
I did not clear the Play Store data the first time I enabled the fingerprint and had this problem. I'll try again, though.
[Magisk] KromerX:
Can you please add fingerprint for Asus ZenFone 5Z?
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] KromerX:
Fingerprint for Asus Zenfone 5Z

Sorry, will much appreciate your effort if you can add this device to the list of "white" fingerprints.

Stock Fingerprint of target version:

asus/WW_Z01RD/ASUS_Z01R_1:9/PPR1.180610.009/WW_90.11.162.72_20190531:user/release-keys
[Magisk] Didgeridoohan:
Thank you, I will test it and add to the list if it works (I only add prints that I have personally made sure works). But, I'll also need the security patch date.

https://github.com/Magisk-Modules-R...E.md#matching-the-android-security-patch-date
[Magisk] KromerX:
I just tried that as a custom fingerprint and it works like a charm.

Stock security patch for this rom is a 2019-05 . But it also works without any edits on recent security patch that I have on AOSIP custom rom which is 1st of August 2019.
[Magisk] Didgeridoohan:
Confirmed. Doesn't seem like the patch date matters for that print. I'm curious, what's the build date of that ROM (ro.build.date)?
[Magisk] Makishima:
I tried once again to set the fingerprint and delete the vendor line in the system.prop. Well, it broke my lockscreen PIN for starters; fortunately, another user had the same issue and he mentions deleting locksettings.db from TWRP, so that was fine. However, upon booting, even though ctsprofile passed and Play Store said it was certified, I still couldn't log into apps or delete them.

Another problem I have is I cannot install any apps from the Play Store. It downloads the app up to a certain point, even 100% sometimes or less most of the time and it stops, then I reboot and then it installs it and then the same for the second app. And so on. This happens both with an uncertified and a certified Play Store for me so not sure that is the problem. SuperSU did not cause me this problem. But this seems to be a side-effect of Magisk maybe, not this module in particular. Does anyone else have this problem?