yashsingh1/xdaforums huggingface dataset:
[Magisk] Valiante:
I ended up getting it to work by clearing the data from the Google app. Very strange but who cares, simple fix.

Honestly thought that as well, but it's most definitely working only with this module
[Magisk] zgfg:
One more fingerprint submission:

Huawei P9 EVA-AL10 (8.0.0)

ro.product.manufacturer = HUAWEI

ro.product.model = EVA-AL10

ro.build.fingerprint = HUAWEI/EVA-AL10/HWEVA:8.0.0/HUAWEIEVA-AL10/550(C00):user/release-keys

ro.build.version.security_patch = 2020-07-01
[Magisk] pndwal:
Just interested in this.

-Did you get ctsProfile pass after installing MagiskHide Props Config without selecting anything in terminal?

-And did 'ok Google' w/ screen off start working just by clearing data?

-Have you checked to see what happens if you disable MagiskHide Props Config module now and reboot?

-I'm also interested to know model & ROM. :good: PW

---------- Post added at 04:12 AM ---------- Previous post was at 04:01 AM ----------

Hey [MENTION=4667597]Didgeridoohan[/MENTION].

You may want to reword this:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#whats-this

to point to this:

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation :good: PW
[Magisk] Didgeridoohan:
Oops... Forgot about that. :good:
[Magisk] mandhir.s.bajwa:
I went through multiple posts and the guides available here. I see tons of helpful tips on what to do if ctsProfile is false and some apps are not working.

In my case ctsProfile and basicintegrity, both are true, I've used the magist hide and yet few apps are finding the root and won't work.

Any solution for this?
[Magisk] Didgeridoohan:
That's because this thread mainly deals with passing CTS...

There are several ways of detecting Magisk that MagiskHide currently can't deal with. Apart from that:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] ipdev:
Hi all. :)

When I have some time, I try to find fingerprints for the list.

Normally missing devices or devices that are mentioned in this thread.

MHPC list is 336 devices, Google's list is 29,253 devices.

Close race but, we could try and close the gap a little bit. :p

[MENTION=7450174]bouyhy01[/MENTION]

Found the current print for 9S.

[MENTION=11047653]Doligem[/MENTION]

I'm not a sammy guy but, I found an older (9) print for SM-A750GN.

[MENTION=6935079]Betrox[/MENTION]

No luck on a newer version.

The last stable release is already in the list.

I even double checked the last China Beta. (Failed SafetyNet)

ro.build.fingerprint=xiaomi/whyred/whyred:9/PKQ1.180904.001/20.6.18:user/release-keys

ro.build.version.security_patch=2020-07-05

I do not remember if Google Beta 2 was certified but, Beta 3 is.

Since Android 11 is soon approaching, Pixel (Beta 3) is also included in the list.

I know beta(s) are normally ignored but, maybe think of them as a placeholder for the next release.

Fingerprints..

Pixel 2 -> 4. (11 Beta)

POCO F2 Pro (10)

Redmi Note 9S (10)

Samsung Galaxy A7 (2018) [SM-A750GN] (9)

Cheers all. :cowboy:
[Magisk] Doligem:
[MENTION=11047653]Doligem[/MENTION]

I'm not a sammy guy but, I found an older (9) print for SM-A750GN.

Sorry for late, I found a current verision for my device A7 2018 (SM-A750GN) - Android 10

Here, please add as fast as you can. Thankssss :

Samsung SM-A750GN [Build Date - May 22 2020]

# Samsung Galaxy A7 (2018) a7y18lte SM-A750GN

# ro.bootimage.build.fingerprint=samsung/a7y18ltedx/a7y18lte:10/QP1A.190711.020/A750GNDXS6CTE1:user/release-keys

# ro.build.version.security_patch=2020-06-01

# ro.build.version.release=10

# ro.build.version.sdk=29

# ro.product.device=a7y18lte

# ro.product.brand=samsung

# ro.product.manufacturer=samsung

# ro.product.model=SM-A750GN

# ro.product.name=a7y18ltedx

# ro.build.product=a7y18lte

# ro.vendor.build.fingerprint=samsung/a7y18ltedx/a7y18lte:10/QP1A.190711.020/A750GNDXS6CTE1:user/release-keys

# ro.product.vendor.manufacturer=samsung

# ro.product.vendor.model=SM-A750GN

# ro.product.vendor.brand=samsung

# ro.product.vendor.name=a7y18ltedx

# ro.product.vendor.device=a7y18lte

THANKSS !!
[Magisk] zgfg:
One more fingerprint:

Huawei P9 Plus VIE-AL10 (8.0.0)

ro.product.manufacturer = Huawei

ro.product.model = VIE-AL10

ro.build.fingerprint = HUAWEI/VIE-AL10/HWVIE:8.0.0/HUAWEIVIE-AL10/550(C00):user/release-keys

ro.build.version.security_patch = 2020-07-01
[Magisk] Doligem:
Edit: Ok I just try again and my device change to other fingerprint. But in netflix app it shows this error, please help !

[IMG="error"]https://www.linkpicture.com/q/InShot_20200824_165818859.jpg[/IMG]
[Magisk] Didgeridoohan:
You pass SafetyNet, both checks, and your Play Store is certified? If so you've likely got issues that are unrelated to SafetyNet. No idea what...
[Magisk] Doligem:
Have u added my device yet ?
[Magisk] Didgeridoohan:
When I add new/updated devices there's always a post announcing this.

If you're in such a rush to use the print, there are several ways to enter a print without using the included list (check the docs, linked in the OP).
[Magisk] Doligem:
What things I should enable in device simulation ? Because my device change fingerprint after I enable some features in device simulation .. so what should I do ?
[Magisk] Displax:
Xiaomi Mi A1

xiaomi/tissot/tissot_sprout:9/PKQ1.180917.001/V10.0.24.0.PDHMIXM:user/release-keys__2020-08-01
[Magisk] jenslody:
Netflix works without passing safetynet.

It looks more like a network issue, e.g. a firewall or a dns-blocker, blocking Netflix.
[Magisk] Didgeridoohan:
Yeah. The only SafetyNet related thing I'm aware of that affects Netflix is Play Store certification (and that'll be uncertified if you don't pass CTS).
[Magisk] Displax:
Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.13.0.QDIMIXM:user/release-keys__2020-08-05
[Magisk] Some_Random_Username:
Hi all, here are latest fingerprints for OnePlus devices.

Note that OnePlus/Nord_EEA/Nord:10/QKQ1.200412.002/2008180157:user/release-keys__2020-07-01 is an update over OnePlus/Nord_EEA/Nord:10/QKQ1.200412.002/2007162338:user/release-keys__2020-07-01 while OnePlus/Nord/Nord:10/QKQ1.200412.002/2008180159:user/release-keys__2020-07-01 is a new fingerprint, but still for AC2003 that time sold in Hong-Kong, see https://xdaforums.com/showpost.php?p=83241319&postcount=11
[Magisk] Displax:
There is EURO variant for Xiaomi Mi A3, you can add it too. So need rename to: "Xiaomi Mi A3 Global" and "Xiaomi Mi A3 European"

Props for it:

Xiaomi Mi A3 European (9 & 10):Xiaomi:Mi A3=Xiaomi/laurel_sprout_eea/laurel_sprout:9/PKQ1.190416.001/V10.3.17.0.PFQEUXM:user/release-keys__2020-03-05;Xiaomi/laurel_sprout_eea/laurel_sprout:10/QKQ1.190910.002/V11.0.6.0.QFQEUXM:user/release-keys__2020-08-05
[Magisk] jenslody:
But if it is installed (like in this case), it should not matter, drm and at least widevine l3 is a must, but leads to another error.

I can install and run Netflix on my J5 with microG (therefore no safetynet at the moment) and aurorastore.
[Magisk] Doligem:
Firstly I want to explain why I want to change the fingerprint .. Netflix only plays HD with Widevine L1 devices (and only in this list https://help.netflix.com/en/node/23939#). I have downloaded DRM info and checked that my device is also Widevine L1, but inside the Netflix app it defaults to Widevine L3 just because my device is not on their support list. So I search google to find out how to play netflix HD and I find this article "https://xdaforums.com/showpost.php?p=82173651&postcount=55" they said that edit buildprops to another device so netflix imagine that my device is on their support list, but when I changed (choose 1 fingerprint and reboot), it pass SafetyNet, but in netflix app it has not changed, then I enabled device simulation (include already enabled item and add Brand, Model and Manufacturer) and in netflix app it has changed but not pass SafetyNet. So can all of you guys tell me what should I do ? And really change buildprops, the netflix app will change too? Thanks...
[Magisk] Displax:
Google Pixel 4a

Google Pixel 4a (10):Google:Pixel 4a=google/sunfish/sunfish:10/QD4A.200805.003/6598198:user/release-keys__2020-08-05
[Magisk] CoryCoolguy:
Pixel 4a fingerprint

You beat me to adding the Pixel 4a and now I look a fool
[Magisk] ReservedName:
maybe this fingerprint submission will finally go through (stupid xda not posting my reply no matter how many times i log in)

Google Pixel 4a Android 10 (QD4A.200805.003)

ro.product.manufacturer = Google

ro.build.product=sunfish

ro.system.build.fingerprint=google/sunfish/sunfish:10/QD4A.200805.003/6598198:user/release-keys

ro.build.version.security_patch=2020-08-05
[Magisk] swour:
Samsung Galaxy A5(2017) fingerprint update:

Security patch date: 2020-08-01
[Magisk] monicaONxda:
Device not in list? Can I use a similar device? Galaxy Note 10+ 5G

I have a "Samsung Galaxy Galaxy Note 10+ 5G SM-976B" with Exynos Soc which is not in the device list!

Can I use a similar device such as the "Samsung Galaxy Note 10 Plus SM-N975F" which has also a Exynos Soc?

Does it depend on the Soc, actually?

Thanks!
[Magisk] Didgeridoohan:
[MENTION=11035411]monicaONxda[/MENTION]

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint
[Magisk] LDL707:
I have a ZTE Axon 7 running crDroid. It's rooted with Magisk, and I have the pix3lify and PIXELARITY modules installed. When I look at the device information in Android Settings, the device says it's a Pixel 2 XL.

Which fingerprint should I use? Should I base it on my hardware (Axon 7) or the device that the device thinks it is (Pixel)?
[Magisk] Didgeridoohan:
That would be the PIXELARITY module that changes a whole bunch of props. It already uses a Pixel 2 XL fingerprint so there's no need to change to another. But, I don't think it updates the security patch date. You can use the custom props feature of MagiskHide Props Config to set that to the matching date though. For the Android 9 version of the PIXELARITY module I believe that is 2019-08-05 and for the Android 10 it would be 2019-09-05. The prop to set is ro.build.version.security_patch.

And, of course, nowadays you might also have to change the type of key attestation that your device uses. I have no idea if Pixel 2 XL is already ok, but if CTS doesn't pass after updating the security patch date you can try to enable "Force BASIC attestation".
[Magisk] 73sydney:
On stock August ROM, my Pixel 2 XL passes CTS and has basic (non hardware backed) attestation....fwiw
[Magisk] unknown40404:
Xiaomi MI 10

[ro.build.version.security_patch]: [2020-07-01]

[ro.product.manufacturer]: [Xiaomi]

[ro.product.model]: [Mi 10]

[ro.build.fingerprint]: [Xiaomi/umi_eea/umi:10/QKQ1.191117.002/V11.0.10.0.QJBEUVF:user/release-keys]

Following fingerprint already exists:

Xiaomi Mi 10 (10):Xiaomi:Mi 10=Xiaomi/umi/umi:10/QKQ1.191117.002/V11.0.15.0.QJBCNXM:user/release-keys__2020-02-01

It looks like that it's newer because of version 11.0.15.0 but the date is 2020-02-01, so does it even matter to post another one? Or is mine going to be also accepted and there will be two fingerprints available?

Thanks. Really appreciate this module, been using it on my OnePlus 3 without an issue until I got my Mi 10. :)
[Magisk] LDL707:
I'm not entirely sure what this means for me. I'm new to the Props Config process. My phone originally passed the SafetyNet check and worked with Google Pay, etc. Then, out of the blue, I got a notification from Google Pay saying my device no longer met the requirements, and when I ran the SafetyNet check, the ctsProfile failed. The attestation check still shows as "Basic".

Is the security patch date the only thing that I need to change? Is it possible that there's something else going on that is causing me to fail the ctsProfile check?
[Magisk] Didgeridoohan:
First thing you should try is to make sure that MagiskHide is properly active (toggle it off and on again). Basic integrity can actually pass even with MagiskHide off.

If that doesn't help all you likely should have to do is to change the security patch date. But of course, there's always a possibility it could be something else as well. We'll pass that bridge when we get there...
[Magisk] LDL707:
Ok. To do this, I enter the terminal, enter "props" and then select "5" for "Add/edit custom props"? Is that right? When I do that, it says "Currently no custom props set."

I'm assuming I then select "n" for "New custom prop". After that, I'm not really sure where I go. In the documentation, the only thing that seems to mention the security patch date is the CONFPROPS and setting ro.build.version.security_patch to the desired date, which in this case I guess would be 2019-08-05. What do I type into the terminal to do that?

Sorry for the noob questions.
[Magisk] Didgeridoohan:
After you've pressed "n" for "New custom prop" you enter the prop you want to set, in this case ro.build.version.security_patch. Press enter and then add the value you want the prop to be set to.

You can also use the props command with run options to bypass the ui. It would look like this:

props ro.build.version.security_patch 2019-08-05
[Magisk] Didgeridoohan:
Well... The difference is that the fingerprint you have provided is the European version while the one already on the list is the global version. So yes, there will now be two entries for the Mi 10.
[Magisk] Didgeridoohan:
Module updated to v5.3.2, prints list updated to v99

Small update (mainly ui fixes) to the module, big update to the fingerprints list.

Thank you to [MENTION=7786725]zgfg[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=11047653]Doligem[/MENTION], [MENTION=6345368]Displax[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=9971068]CoryCoolguy[/MENTION], [MENTION=4453960]swour[/MENTION], [MENTION=6118332]ReservedName[/MENTION] and [MENTION=11058773]unknown40404[/MENTION] for providing all those prints.

Changelog

v5.3.2

Some minor fixes/clarifications in the ui.

Added PIXELARITY to the list of modules that also edit device fingerprint.

Added fingerprint for Google Pixel 4a, Huawei Mate 9 and P9 EVA-AL10, OnePlus Nord Global AC2003, Samsung Galaxy A7 2018 and Xiaomi Mi 10 European. Updated print for Google Pixel 2-4 (all variants), Oneplus 6, 6T, 7 (several variants), 7 Pro (several variants), 7T (several variants), 7T Pro (several variants), 8 (several variants), 8 Pro (several variants) and OnePlus Nord, POCO F2 Pro, Samsung Galaxy A5 2017 and Xiaomi Mi A1, Mi A2 and Mi 9T European. List updated to v99.
[Magisk] LDL707:
Ok, thanks.

The date was set for 2020-08-05. I changed it to 2019-08-05.

It's still failing the ctsProfile check though. Is there any log or anything that tells why it fails?
[Magisk] zgfg:
Please check the previous questions and answers about CTS - thrre are tons of them above. There is an option in MHPC to fix it (if due to Hardware based attestation) and it is also described in the MHPC guide
[Magisk] Didgeridoohan:
I'm assuming that you are running Android 9... Because in that case you might be out of luck.

I tested and for the Android 10 PIXELARITY print the 2019-09-05 security patch date matches and CTS passes. But, none of the usual dates worked with the Android 9 print. There's something funny about that print though, since that particular build isn't available on the Google factory image page for the Pixel 2 XL. :confused:
[Magisk] Displax:
You forgot this :)
[Magisk] zgfg:
[MENTION=4667597]Didgeridoohan[/MENTION],

and that
[Magisk] LDL707:
Would getting rid of the PIXELARITY module help?
[Magisk] Didgeridoohan:
Those two I had some interesting issues with... They broke the resetprop tool on my test device and the prints didn't get set at all. I got the Android 10 print to pass on a different device, but the 9 print didn't.

I will look closer into what happened with resetprop before adding it to the list.

And that one didn't pass CTS when I tested it.
[Magisk] Didgeridoohan:
Depends on what you mean with "help"... It could help to pass CTS (if that's important to you), but you'd loose whatever you're using the module for, of course.
[Magisk] zgfg:
I've corrected ro.product.model in the post

But how do you really test it - by Device simulation or just by changing the Fingerprint and Security patch date

Because I wanted to test similarly but I have a phone with unlocked Bootloader (and different version of Android, etc) and I was wondering how to setup the test to make sure that CTS Hardware-backed attest would not interfere, but on the other side that I emulate the case as closely as possible

And if I go into Device simulation, there are options for a number of props (partition, etc) that was I was afraid to tackle (although, hopefully, it would not make a permanent harm and I can always disable the whole MHPC or edit its system.props in case of bootloop)
[Magisk] Didgeridoohan:
Just the print and patch date. My test device already uses basic attestation, but there should be no issues forcing basic attestation as well when testing a fingerprint.
[Magisk] zgfg:
Ok, sorry, it was small caps, now correct values (corrected also in my original post):

ro.build.fingerprint = HUAWEI/VIE-AL10/HWVIE:8.0.0/HUAWEIVIE-AL10/550(C00):user/release-keys

ro.build.version.security_patch = 2020-07-01

ro.product.manufacturer = Huawei

ro.product.model = VIE-AL10

It passes now with (and with the previous, wrong print didn't)
[Magisk] Didgeridoohan:
That would certainly do it. They're sticklers for details over at Google HQ... Confirmed working and I'll add it to the next update.
[Magisk] JarlPenguin:
Moto G7 August patch Q fingerprint:

ro.build.fingerprint=motorola/river_retail/river:10/QPUS30.52-16-2-5/58144:user/release-keys

ro.build.version.security_patch=2020-08-01

ro.build.product=river
[Magisk] Didgeridoohan:
Thank you. I happened to note that this print has the device name as "river_retail", while the one I already have (including an Android 10 print submitted yesterday) is just "river". Do you happen to know the difference?
[Magisk] JarlPenguin:
I believe there is no difference (stock sets the build fingerprint through init scripts), but on stock there are 2 different props with different fingerprints.

ro.build.fingerprint is actually motorola/river_retru_n/river_n:10/QPUS30.52-16-2-5/58144:user/release-keys

while ro.vendor.build.fingerprint and ro.system.build.fingerprint are the one listed in the previous post.
[Magisk] smohanv:
Hi OP

Here is the details I found from my build.prop.

Is this fingerprint included in your module?. So far I have been fixing db.dg file to fix my access to GPay. But I don't know this it is going to work anymore if I migrated to Android 11. So, I believe that only your module is the way forward to make CTS and SafetyNet to pass.

Am I correct in my assumptions.

See build.prop details relevant to fingerprint.

ro.system.build.date=Thu Aug 6 02:29:03 CST 2020

ro.system.build.date.utc=1596652143

ro.system.build.fingerprint=Xiaomi/cmi/cmi:10/QKQ1.191117.002/V12.0.4.0.QJACNXM:user/release-keys

ro.system.build.id=QKQ1.191117.002

ro.system.build.tags=release-keys

ro.system.build.type=user

ro.system.build.version.incremental=V12.0.4.0.QJACNXM

ro.system.build.version.release=10

ro.system.build.version.sdk=29

ro.product.system.brand=Xiaomi

ro.product.system.device=cmi

ro.product.system.manufacturer=Xiaomi

ro.product.system.model=Mi 10 Pro

ro.product.system.name=cmi

---------- Post added at 08:08 PM ---------- Previous post was at 08:08 PM ----------

Hi OP

Here is the details I found from my build.prop.

Is this fingerprint included in your module?. So far I have been fixing db.dg file to fix my access to GPay. But I don't know this it is going to work anymore if I migrated to Android 11. So, I believe that only your module is the way forward to make CTS and SafetyNet to pass.

Am I correct in my assumptions.

See build.prop details relevant to fingerprint.

ro.system.build.date=Thu Aug 6 02:29:03 CST 2020

ro.system.build.date.utc=1596652143

ro.system.build.fingerprint=Xiaomi/cmi/cmi:10/QKQ1.191117.002/V12.0.4.0.QJACNXM:user/release-keys

ro.system.build.id=QKQ1.191117.002

ro.system.build.tags=release-keys

ro.system.build.type=user

ro.system.build.version.incremental=V12.0.4.0.QJACNXM

ro.system.build.version.release=10

ro.system.build.version.sdk=29

ro.product.system.brand=Xiaomi

ro.product.system.device=cmi

ro.product.system.manufacturer=Xiaomi

ro.product.system.model=Mi 10 Pro

ro.product.system.name=cmi
[Magisk] Didgeridoohan:
I do have the Mi 10 Pro in the list, but it's an older print than what you have here (build version V11.0.13.0 vs V12.0.4.0). If you could also provide the security patch date I can update the print. Although, Google doesn't really care and you can use whatever fingerprint.

If you move to a custom ROM you'll need the fingerprint to pass CTS, and if the device uses hardware backed key attestation for the bootloader check you can use the "Force BASIC attestation" feature to fool that as well.

GPay isn't something I can help with, really, since I've never used it...
[Magisk] smohanv:
Here it is.

ro.system.build.date=Thu Aug 6 02:29:03 CST 2020

ro.system.build.date.utc=1596652143

ro.system.build.fingerprint=Xiaomi/cmi/cmi:10/QKQ1.191117.002/V12.0.4.0.QJACNXM:user/release-keys

ro.system.build.id=QKQ1.191117.002

ro.system.build.tags=release-keys

ro.system.build.type=user

ro.system.build.version.incremental=V12.0.4.0.QJACNXM

ro.system.build.version.release=10

ro.system.build.version.sdk=29

ro.product.system.brand=Xiaomi

ro.product.system.device=cmi

ro.product.system.manufacturer=Xiaomi

ro.product.system.model=Mi 10 Pro

ro.product.system.name=cmi

# end common build properties

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=QKQ1.191117.002

ro.build.keys=release-keys

ro.build.version.incremental=V12.0.4.0.QJACNXM

ro.build.version.sdk=29

ro.build.version.preview_sdk=0

ro.build.version.preview_sdk_fingerprint=REL

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=10

ro.build.version.security_patch=2020-07-01

---------- Post added at 09:38 PM ---------- Previous post was at 09:28 PM ----------

My question was not about GPay. If I roll my firmware to Android 11 Beta (MIUI 12 Beta), should you need fingerprint and security patch details to include in your module.

I believe that if the fingerprint is added for Android 11 in your module hope it will pass SafetyNet and CTS.

Thanks.
[Magisk] raptor22:
Would like to clarify the use of this module on Pixel 4 XL, running stock ROM but with Magisk and custom kernel. Hardware backed attestation was enabled

When I enable Force basic attestation using the default value (to Nexus 5), I am able to pass ctsProfile.

However when I enable force basic attestation using the Pixel 4XL fingerprint from the list in terminal, ctsProfile fails. No matter what I do, I fail ctsProfile but pass basic integrity, unless my phone model is changed to Nexus 5 then both passes.

I have also tried to change the security patch and fingerprint boot stage to post-fs-data as per GitHub, but to avail either. Is there any way to have my device model be shown as Pixel 4 XL rather than Nexus 5, and pass ctsProfile?
[Magisk] Didgeridoohan:
No. Google uses the device model to determine when to do a hardware based check. That's how we currently fool SafetyNet into using a basic check instead, by changing the model name to one that isn't on their list of devices that should use the hardware based key attestation.
[Magisk] Didgeridoohan:
Thanks for the print, it passes CTS just fine.

About passing CTS on MIUI 12 Beta: If Xiaomi bothers to get it Google certified you won't need to use a certified device fingerprint to pass CTS (but you might have to use "Force BASIC attestation" if the device uses hardware backed key attestation for the bootloader state check). If they don't get it certified you will have to use a different print, like the one you just posted.