yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
No worries... :o

Your research is kind of correct. If basic integrity is failing as well, you've got bigger issues than what this module can help you with. You need to figure out why basic integrity fails. If you can do that, and fix it, this module might help you pass the CTS profile check.

It is possible to fake the CTS profile though, but it means installing Xposed and using the No Device Check Xposed module, but that might bring another host of problems...

Attach them to a post right here...
[Magisk] allrockedout:
Here you go. Basically I sideloaded these gapps because the ROM hasn't been released with gapps yet. Not sure if that matters.
[Magisk] Didgeridoohan:
Everything looks fine in the logs... And you say you pass basic integrity, but not the CTS profile? Did it work on the same ROM with USNF?
[Magisk] allrockedout:
Yeah basic integrity is fine. I tried installing UNSF on magisk 16.4 but get error in twrp. So I went back to magisk 14.6 and it installed in twrp but cts profile still fails. Tried installing it multiple times still won't pass.
[Magisk] Didgeridoohan:
Ok... It's hard to say what it could be. I'm not sure if I can fix it, but could you post your build.prop and the output file of this command:

su -c getprop > /sdcard/props.txt
[Magisk] allrockedout:
Hope this helps. My phone has NFC so I would like to use Google pay. ?
[Magisk] allrockedout:
Sorry build prop didn't upload here are both files
[Magisk] Didgeridoohan:
Did your run the getprop command with the module active and a different fingerprint selected, or just the stock fingerprint?

I tested the fingerprint your device comes with, and it's certified and passes the CTS check just fine. I'm currently at a loss as to what could be causing your problem.

Of course, I didn't sleep much, have just woken up, and haven't started my caffeine intake yet today, so my brain could work gooder...
[Magisk] d3ssorion:
The same with my mix 2 on miui 10. Fingerprint from global firmware does not help. I ask your help
[Magisk] Didgeridoohan:
So we have a trend. Two reports of the Xiaomi Mi Mix 2 not being able to pass the CTS profile check, even with this module.

Have you tried another device's fingerprint from the module?

Could you make sure that the fingerprint from the module sets properly? Run this command in a terminal emulator:

getprop ro.build.fingerprint

Let's start with that...
[Magisk] d3ssorion:
The problem is that Miui 10 china developer. Verification does not work even on a clean system without magical. Any ideas?
[Magisk] Didgeridoohan:
Likely causes:

Bootloader unlocked.

Hasn't been Google certified.

Both of those will give a false result for the CTS profile check.

The first one can be hidden by MagiskHide and the second (usually) by changing to a different, certified, device fingerprint.
[Magisk] allrockedout:
I probably ran the getprop on stock fingerprint I forget now. I'll try again later today.
[Magisk] skullkid383:
Forgot to mention xposed makes it fail as well
[Magisk] jcmm11:
Zarchiver has the ability to open .img files and extract files from them (you'd want to extract build.prop)
[Magisk] Didgeridoohan:
Fingerprints list updated to v43

Got a bunch of new fingerprints submitted, so here's an update. List is pushed up to v43.

Huge thank you to [MENTION=5248028]devloz[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=7530018]oslo83[/MENTION], [MENTION=6948826]Nebrassy[/MENTION], [MENTION=6043888]DN38416[/MENTION], [MENTION=5819220]astrit1[/MENTION], [MENTION=9637474]michaelmaverick[/MENTION], [MENTION=4544860]osm0sis[/MENTION] and possibly some more that I'm forgetting about right now. Wouldn't be the same without your contributions.

New fingerprints

Huawei Mate 20 Pro

Huawei P20

LG G6 H870

Samsung Galaxy A5 2015

Updated fingerprints

Essential PH-1

Google Pixel

Google Pixel XL

Google Pixel 2

Google Pixel 2 XL

Google Pixel 3

Google Pixel 3 XL

Google Pixel C

OnePlus 5T

Xiaomi Mi A1

Xiaomi Mi A2

Xiaomi Mi Mix 2S

Xiaomi Pocophone F1
[Magisk] xTanker:
I followed that guide and that's what it gave me.
[Magisk] Didgeridoohan:
Well, it's not quite complete... I could theoretically create the fingerprint from that info and the one I have on the list already, but I would still need the security patch date as well. And even then it would just be an educted guess on my part. Much better to get the whole thing straight off.

I updated the docs a bit for you and added an example of what a fingerprint looks like.
[Magisk] Bradco:
Hello

I find the fingerprint coming from a ROM where I know that the safetynet is ok (my phone's ROM stock but improved). I add it does not work, I tried to change the security patch version corresponding to the fingerprint does not work either (I'm not sure I did it correctly).

go back with a fingerprint in the list.
[Magisk] Didgeridoohan:
If you post the fingerprint and security patch date here I can take a look at them and add to the list if it passes CTS.
[Magisk] Bradco:
Yes but I think I make a mistake, I look in system/build.prop and I think the good fingerprint is in /default.prop

I need to test if it workq I give you a feedback
[Magisk] oslo83:
[MENTION=4728656]ej8989[/MENTION] is also confirming what i reported,

that hw_show_lte_tile 'prop'

was effectively switched from false to true using custom prop option with at least Magisk Hide Props 2.7.2 .

So I should resolve to do and send a 3.x log when i'm adding it this custom 'prop' ....

It's a setting used on Huawei/Honor on emui9.
[Magisk] arpio:
Working fingerprint for Asus Zenfone Max M1(zb555kl/X00PD)

Thanks to raza231198 for providing the fingerprint from stock rom.

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

Security patch level: 2018-11-05

I didn't use the module, updated manually.

Cleared cache and data Google Play Store and Goggle Play Services
[Magisk] Bradco:
small question if i change the values of the fingerprint and security patch directly in the build.prop file the satety net will passed ?
[Magisk] arpio:
It worked for me. But I'm not an expert.
[Magisk] Bradco:
it's good to know thanks :good:
[Magisk] ipdev:
It seems U Pro isn't available on Elephone's download list yet. Link

I found one here on xda Link.

I pulled the fingerprint from boot_a.img and it failed cts.

I noticed something late, and I was too tired to check so I postponed this post.

Got sidetracked when I got home tonight.

I noticed the vendor_b.img had a different fingerprint than boot_a.img ?

So I took a look at a few files, and well.

Attached zip is U_Pro build and default props.

This is the one that worked for me.

Elephone U Pro (8.0.0)=Elephone/U_Pro/U_Pro:8.0.0/Elephone_U_Pro_20180917/09172123:user/release-keys__2018-09-05

Cheers. :)
[Magisk] Bradco:
Great news :good: for the fingerprint I looked in the system_a.img the good is in the file vendor_b.img?

you have to go through all the files to find it

Have you change the date of security patch ?

EDIT 1 : I just tried I can not pass the safetynet I have to do something wrong if someone can help me info I have a resurection res remix trebble GSI

Edit 2 : I tried with this method Custom fingerprints list I do not find in the Custom category

EDIT 3 : i finaly did it with custom method, I'm not too bad :D

how does it work with the method: Use a vendor fingerprint (for Treble GSI ROMs)

how to add the fingerprint directly to the phone files without having to change it with the module?

Use vendor fingerprint (for Treble GSI ROMs)
[Magisk] zippy01:
Is this to work alongside magisk hide? I don't have any issue with playstore or safety net just 1 banking app that I use since recently.

Thank you
[Magisk] Didgeridoohan:
If you have a Treble GSI ROM, like you do, the vendor partition will be stock, meaning that the vendor fingerprint can be used to pass the CTS profile check. More here:

https://github.com/Magisk-Modules-R...md#use-vendor-fingerprint-for-treble-gsi-roms

It's unlikely that this module can do anything for you. Take a look here for things to try:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] zippy01:
Thank you, I actually found an oldish backup of the app so might just use that for the time being ? your link is very helpful though thank you
[Magisk] brennancb:
Installation fails every time

I receive only this information after it tries to install from magisk manager.

-Found /data/adb/magisk_merge.img

! /data/adb/magisk_merge.img mount failed...

! Installation failed

I'm on a Moto G5S Plus running Magisk v18.1 and Magisk Manager v7.0.0. I'm running stock 7.1.1 Nougat with TWRP.

I'm pretty tech savvy but I'm new to the phone modification scene. I understand how a lot of this stuff works on a pretty basic level unfortunately I do t know how to read code to troubleshoot any of this stuff myself. Pretty much just following the steps and learning as I go. Any help would be greatly appreciated.

Also, I saved the log from the failed installation, but I can't find the button for attachments. I typed what it said but not sure if it contains additional information in it.
[Magisk] jcmm11:
Do me a favor. Reboot the phone and try installing it again immediately after you reboot.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_modules
[Magisk] jcmm11:
It's interesting. I have at least one module that gives me a mount error on the magisk_merge image, but if I reboot the phone and try again it works just fine. (For the record I usually install via TWRP, and that doesn't cause any issues)
[Magisk] Didgeridoohan:
Hm, that might mean that the merge image is busy somehow and rebooting fixes it. Motorola devices are well known to have a broken f2fs, so in this case I'm pretty sure that my link applies...
[Magisk] Didgeridoohan:
Update to v3.0.3-v44

I was just gonna push an update to the fingerprints list, but while testing I got so annoyed with how I had made the query to activate device simulation when picking a fingerprint that I just had to update the module at the same time. So here it is...

Thank you to [MENTION=4544860]osm0sis[/MENTION], [MENTION=9665703]arpio[/MENTION] and [MENTION=7280276]ipdev[/MENTION] for the fingerprints.

Changelog

v3.0.3

Small update to the query for activating device simulation or not when picking a new fingerprint.

Updated the fingerprints list and added Asus Zenfone Max M1 and the Elephone U Pro to the list, and updated the OnePlus 5. List updated to v44.
[Magisk] rooban90:
I usually change in both build.prop and default.prop
[Magisk] wilsonhlacerda:
Hi [MENTION=4667597]Didgeridoohan[/MENTION]

thanks for the module, tutorials and all support you give to whole Magisk users!

A new tested and working fingerprint to you (old device, but running fine with LOS):

Samsung S4 Active I9295

samsung/jactiveltexx/jactivelte:5.0.1/LRX22C/I9295XXSDQD6:user/release-keys

security patch: 2016-06-01

More details and props here: https://desktop.firmware.mobi/device:50/firmware:5728

With unofficial LOS 14.1, your module and above fingerprint I can successfully pass SafetyNet tests and get certified device on Play Store.

Bonus info: with Xposed (systemless on Magisk) as expected I can't pass SafetyNet, BUT adding the Xposed module No Device Check I can have ctsProfile TRUE and certified device on Play Store (but basicIntegrity FALSE as expected).
[Magisk] szunyi77:
Hello. Can somebody help me? I have come up with the latest firmware redmi note 4 mido and are currently using the CrDroid pie. PayPal does not accept fingerprints. Recognizes, but does not move, but does not work. I've tried everything with the Magisk module but it doesn't work. What do I do wrong? I attached pictures. Thanks

[IMG="http://p.coldline.hu/2019/02/10/3063748-20190210-dt4BWe.png"]http://p.coldline.hu/2019/02/10/3063748-20190210-dt4BWe.png[/IMG]

[IMG="http://p.coldline.hu/2019/02/10/3063754-20190210-obDcbG.png"]http://p.coldline.hu/2019/02/10/3063754-20190210-obDcbG.png[/IMG]
[Magisk] spida_singh:
As advised earlier

Skype for Business and Face Unlock in settings force close when the device fingerprint change have been made (fails with or without device emulations)

Both catlog and module logs attached
[Magisk] Didgeridoohan:
Yes, this is one way to fool the Google servers into thinking your device is certified (but you can't fool the on-device check, basic integrity). If you use that Xposed module you have no need for this module though...

This module can help you pass the CTS profile part of the SafetyNet check. If you have general issues with apps detecting root there's something else going on... Take a look here for tips on what to try:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Reading logs take time and that is a commodity I do not have a lot of at the moment. I will see if I can get an opportunity to sift through them sometime this week, but no promises...
[Magisk] szunyi77:
Thanks. I have tried almost everything, but PayPal and banking applications are pushing fingerprints. Another idea for someone? thanks

Tapatalkkal küldve az én Redmi Note 4 eszközömről
[Magisk] bitye:
Can anyone assist with MIUI 9.2.11 on POCO?

It's fine in PM too but I maybe fail on some point as any version instant bootloop after I use what I read here. Same with last 4 betas
[Magisk] Didgeridoohan:
In that case you're in the wrong thread... You'd be better of taking this to the general support thread, see if there's already a thread about this issue (I believe there might be, search), or if there isn't already one start a thread of your own.

Do you mean that using this module causes your device to bootloop? What options are you using and please try to provide logs (see the module documentation). Without more info there is no way to help...
[Magisk] skullkid383:
[MENTION=4667597]Didgeridoohan[/MENTION] odd ? When did u add build version and y I ask cause it confused me for a min there but then I was like I been using this module since u made it and figured u changed something's and looking around I seen that just disabled that part and all is well
[Magisk] Didgeridoohan:
I'm currently too thick to follow what you're saying... :laugh: What do you mean?
[Magisk] skullkid383:
My bad I was wondering what was the point of adding build.version.release prop in ur module if it doesn't mess with safety net
[Magisk] Didgeridoohan:
That is part of the new device simulation feature. It's a requested feature added in v3.0.0. It has nothing to do with SafetyNet. Don't enable it if you don't need it...
[Magisk] brennancb:
Rebooting didn't help. Seems to be this f2fs issue mentioned. I guess I could try from TWRP instead of Magisk Manager.
[Magisk] Didgeridoohan:
Wouldn't help... But all is not lost. There are interesting things happening with Magisk at the moment:

https://github.com/topjohnwu/Magisk/commit/1321f097b823729ba0b2dd99e611098538cb8a73
[Magisk] martyfender:
Yes, it is an evolutionary change, indeed. I just updated 2 of my Nextbook Ares 8A, x86, Android 6.0.1 tablets to the latest Canary build and so far everything is working great.

I tested the fingerprint change, with the other one that works with my device and all is working as expected, in the hour or two that I have had it on my devices.
[Magisk] szunyi77:
Hello. I tried sh-hide command works on the menu appears. For example, if I type - - enable, write sh not found. Redmi note 4 mido CrDroid rom pie

Tapatalkkal küldve az én Redmi Note 4 eszközömről
[Magisk] Didgeridoohan:
You've ended up in the wrong thread...

Edit: I'm going to assume you wanted to post that here:

https://xdaforums.com/apps/magisk/magisk-shellhide-t3855616
[Magisk] Notonlyeyes:
Hi [MENTION=4667597]Didgeridoohan[/MENTION] ,thanks for all your work.

Updating list Fingerprint for Huawei P8 Lite 2017:

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/401(C432):user/release-keys

Security Patch Date: 2019-01-01

I tried the test it's working

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/401(C432):user/release-keys__2019-01-01
[Magisk] Pipsname:
Ran into a happy little accident.
[Magisk] oslo83:
Huawei P20

HUAWEI/EML-L29/HWEML:9/HUAWEIEML-L29/197C432R1:user/release-keys
[Magisk] AJsama:
cannot run .sh during boot (itried reboot several times)

op5t on oos ob19 (magisk 18.2-18102)
[Magisk] Didgeridoohan:
According to the logs you are 100% correct... :D

I have two initial guesses:

Either the module installation is broken somehow and a reinstallation should fix it.

Or, whatever the service.sh script in the xXx module (no idea which one that is, but that's it's id) is doing, is something that breaks all other module service.sh scripts. In which case disabling/uninstalling that module should fix it. If it is the xXx module causing issues you should report it to the module creator.
[Magisk] AJsama:
got it, reinstalling it didn't fix

i will report it to another module creator
[Magisk] Didgeridoohan:
Did you first make sure that it actually was the xXx module that caused it?

Edit: And which module is that?
[Magisk] AJsama:
i am sure...

that module is called magisk rom
[Magisk] Didgeridoohan:
Thank you. I'm curious as to what that script is doing. Would you mind uploading it (it'll be in the xXx module folder in /sbin/.magisk/img)?
[Magisk] AJsama:
this?(i renamed it into .txt so that i can upload it)

----

this one is wrong

i re-uploaded a correct one( maybe?)
[Magisk] jcmm11:
Upload /system/etc/xXx/xXx.sh

(You should be able to find that in the module directory as well)
[Magisk] AJsama:
this?
[Magisk] Didgeridoohan:
Thank you...

That script is a bit too big for me to feel like sifting through... But, there's a lot of sleep commands in there that might be blocking stuff. Should be fixed upstream already, since [MENTION=4470081]topjohnwu[/MENTION] made this commit just a few hours ago:

https://github.com/topjohnwu/Magisk/commit/8b84039f1fd10be5c2383048db5bfc422ca8a05a
[Magisk] AJsama:
well, thanks a lot
[Magisk] :
Xiaomi Mi A2 Lite android 9 Pie latest stable version

xiaomi/daisy/daisy_sprout:9/PKQ1.180917.001/V10.0.3.0.PDLMIFJ:user/release-keys
[Magisk] Didgeridoohan:
[MENTION=7530018]oslo83[/MENTION] and [MENTION=9204302]mihhut[/MENTION] Do you also happen to have a new security patch date that goes with those prints, or is it the same as the old ones I have in the prints list already (2018-11-01 and 2018-11-05, respectively)?
[Magisk] :
And when I want to get back the normal fingerprint, do I have to reset the phone?
[Magisk] oslo83:
Huawei P20

HUAWEI/EML-L29/HWEML:9/HUAWEIEML-L29/197C432R1:user/release-keys__2019-01-01

:)
[Magisk] Didgeridoohan:
If you're using the module, no. There'll be an option to reset the fingerprint in the fingerprint menu.
[Magisk] martyfender:
No, you have to open the terminal emulator again with root access and type props, enter key, then choose option one, and select reset and reboot.
[Magisk] Estebanium:
Hi guys, I am currently on stock rom to get my fingerprint. Am I right to just run getprop ro.build.fingerprint > {full path to file you want generated} to get my fingerprint? I am a bit confused, because I expected to also copy a file from somewhere that is needed for the fingerprint. Or is the path from getprop output the magic? Thank you in advanced.
[Magisk] Didgeridoohan:
Running the getprop command is all you need to grab the fingerprint, and piping it to a file with ">" will make it easier to save. No other files need, but depending on your ROM build date you'll also need the security patch date. Details:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf#matching-the-android-security-patch-date
[Magisk] ipdev:
To elaborate on Didgeridoohan's comment.

If you are running the rom you want to pull the fingerprint from, make sure to give your terminal app storage permissions.

getprop ro.build.fingerprint > /sdcard/printslist
getprop ro.build.version.security_patch >> /sdcard/printslist

Now both the fingerprint and security date will be in a file named printslist stored in your root storage. (/sdcard/)

Please share this with the rest of us. ;)

To use it as a custom option you will need to edit it a bit, the current format is.

What ever name you want=fingerprint__date

Cheers. :)

Example from my Nexus 5x

/sdcard/printslist

google/bullhead/bullhead:8.1.0/OPM7.181205.001/5080180:user/release-keys
2018-12-05

Edited /sdcard/printslist

Pick this Goofy device=google/bullhead/bullhead:8.1.0/OPM7.181205.001/5080180:user/release-keys__2018-12-05
[Magisk] Estebanium:
Thank you for your help. Here is the latest fingerprint for Samsung S7 Edge:

2019-01-01
samsung/hero2ltexx/hero2lte:8.0.0/R16NW/G935FXXU3ESA3:user/release-keys
[Magisk] bitye:
Thanks man, finally V3.0.3 with v44 working like a charm with my Pocophone with MIUI 9.2.18 closed beta. No issues, no boot loop, and I just dirty flashed the last 4 updates..
[Magisk] nguyenpa:
Please support

Xiaomi max 1

Xiaomi/helium/helium:6.0.1/MMB29M/V8.2.3.0.MBDMIDL:user/release-keys
[Magisk] Didgeridoohan:
Fingerprints list updated to v45

Had a few new and updated fingerprints that have been posted in the past couple of weeks. Tested and the list is now updated to v45. Thank you to [MENTION=4668495]wilsonhlacerda[/MENTION], [MENTION=4807746]nguyenpa[/MENTION], [MENTION=7530018]oslo83[/MENTION], [MENTION=4553005]Notonlyeyes[/MENTION] and [MENTION=6867525]Estebanium[/MENTION] for providing prints.

The list will automatically update when you run the props command, or (if you've disabled automatic updates) when using the -f runtime option, or by updating manually from the "Edit fingerprints" menu.

New fingerprints

Samsung Galaxy S4 Active

Xiaomi Mi Max

Updated fingerprints

Huawei P8 Lite

Huawei P20

Samsung Galaxy S7 Edge
[Magisk] xpdragon:
When I selected Xiaomi MI Pad 4 fingerprint, it said the selected fingerprint is for Samsung Galaxy J3. Does anyone have Xiaomi MI Pad 4 fingerprint? Thanks.
[Magisk] Didgeridoohan:
Ha! Thank you for finding and reporting on that. Pure and simple copy-pasta error from my side. Fixed...

The fingerprints list is now on v46. Nothing new, just fixed the Samsung Galaxy J3 and Xiaomi Mi Pad 4.
[Magisk] xpdragon:
Thanks a lot for the quick fix.
[Magisk] raystef66:
[MENTION=4667597]Didgeridoohan[/MENTION] HI man !

Seems the 3.0.3 still shows as version=v3.0.2-v43 - just thought to mention this.

Keep up the good work :good:
[Magisk] Didgeridoohan:
First I was a bit confused what you meant... Then I took a look at the zip in the OP. Seems like I accidentally put the v3.0.2 module up as the v3.0.3 zip. :silly: Oh well, the only difference between the two versions is the fingerprints list and a small tweak to the reboot menu when picking a new fingerprint.

Kind of funny that 1600+ people have downloaded it and you're the first one to react (does everyone just download without checking what it actually is). :laugh:

Removed the zip for now and I'll upload the real v3.0.3 later.
[Magisk] raystef66:
No problem at all - yeah I checked the version in modules to be at the latest release and I guess some have a sharp eye on that :cyclops:

No worries though as the differences would be small I guess - thnx again :highfive:
[Magisk] Didgeridoohan:
Updated the OP with the real v3.0.3 zip (not just v3.0.2 in disguise). Thank you [MENTION=5334294]raystef66[/MENTION] for the heads up.

Edit: just to clarify, it was only the provided zip in the OP of this thread and in the releases page of GitHub that had gotten messed up. Updating or downloading through the Magisk Manager Downloads section has been working properly all along...
[Magisk] Nebrassy:
Mi A2 February patch

xiaomi/jasmine/jasmine_sprout:9/PKQ1.180904.001/V10.0.4.0.PDIMIXM:user/release-keys

2019-02-05
[Magisk] dieterhaack:
OnePlus/OnePlus6T/OnePlus6T:9/PKQ1.180716.001/1901231231:user/release-keys

2019-01-01

OnePlus 6T device=OnePlus/OnePlus6T/OnePlus6T:9/PKQ1.180716.001/1901231231:user/release-keys__2019-01-01
[Magisk] Huexxx:
Xiaomi Mi Mix 2=Xiaomi/chiron/chiron:8.0.0/OPR1.170623.027/V10.2.2.0.ODEMIXM:user/release-keys__2018-12-01

ctsProfile: true