there is new info
the author made a module. but only works on a11
and caused boot loop on android 10 and below
I do hope you could include his fix on your module but supports a10 and below
In order to enforce SafetyNet security, Google Play Services is now using hardware attestation for ctsProfile validation in all cases, even when basic attestation is selected. The SafetyNet API res...github.com
Thanks, it works on Xiaomi.eu A11MM is in his telegram group. He has already updated it for more devices. Only works on A11 for now.
ProtonAOSP Android 11 ROM ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy. Usage with my Proton Kernel is recommended to get the most out of your phone. The ROM does not include Proton...forum.xda-developers.com
I notice this added value benefit of the @kdrag0n fix over current 'force Basic' MHPC solution for ctsProfile (apart from it no longer working for most ):
Hope you can implement this very much... Would love to see solution for Android 10 and earlier ROMs also! All best, PWIt defeats both hardware attestation and the new SafetyNet ctsProfile updates released today, without any changes to device or model names, as long as you can pass basic attestation (i.e. fingerprints and security patch levels). No device-specific features (such as the Pixel-exclusive Google Assistant design) will be lost.
Sorry I thought the info may be helpful or related. Please delete that post and this one if you think it isn't needed here.@elphamale That's great, but has nothing at all to do with this thread. Please post it in one is the GPay threads instead.
Edit: and when you do, maybe you can clarify how it's any different from this: https://forum.xda-developers.com/t/working-magisk-with-google-pay-as-of-gms-17-1-22-on-pie.3929950/
Worked on my Pix3. Play Store showing "Certified" and Gpay re-allowed contactless payments after I clicked "Check Software" in the warning dialog inside the app.
Looks to be an Android 10 build so you will need to add the matching security date to the end.I know I should've searched before posting but there are so many pages I couldn't do it. Sorry.
Just to make sure, to use a custom fingerprint I have to create a file named printslist (without extensions) on the root of internal storage. Then on that file I simply write the device name + fingerprint?
Would this be correct for example?
=is what is displayed on the screen when you run the props command and select custom prints list.
Google Nexus 6 (7.1.1):Motorola:Nexus 6=google/shamu/shamu:7.1.1/N8I11B/4171878:user/release-keys Google Nexus 6P (8.1.0):Huawei:Nexus 6P=google/angler/angler:8.1.0/OPM7.181205.001/5080180:user/release-keys__2018-12-05
Motorola one action (10):Motorola:motorola one action=motorola/troika_m1/troika:10/QSBS30.121-12-12-7/702ad:user/release-keys__YYYY-MM-DD
:is what is displayed on the screen when you run the props command and select custom prints list.
MotorolaOneAction Google Nexus 6 (7.1.1) Google Nexus 6P (8.1.0) Motorola one action (10)
=using the older (basic) printslist layout.
:using the current printslist layout.
|Retail Branding||Marketing Name||Device||Model|
|Motorola||motorola one action||troika||motorola one action|
|Motorola||motorola one action||troika_sprout||motorola one action|
NVIDIA/foster_e/foster:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05 NVIDIA/foster_e_hdd/foster:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05 NVIDIA/darcy/darcy:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05 NVIDIA/sif/sif:9/PPR1.180610.011/4079180_2740.7538:user/release-keys__2021-04-05 NVIDIA/mdarcy/mdarcy:9/PPR1.180610.011/4079208_2740.7538:user/release-keys__2021-04-05