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.
Google is working on things on their end... Check the main Magisk thread and you'll see that it's been discussed a bit already. You can use XprivasyLua or spoof the model prop with MHPC. There's also a small tweak to the USNF module that @Displax posted in there that should do it for you.
Johns working like crazy for the next Magisk release, check the commits on GitHub. The only thing he won't be working on is MagiskHide.So far only 2.0.0 safetynet fix is available unless you are pateron of kdrag0n. I know the 2.0.0 build does not work on anything I have. I haven't checked on devices I haven't updated yet.
I was under the impression we weren't getting anymore releases anytime soon from topjohnwu now that he was working for Google. I thought most people had gone to vvb2060's builds of Magisk?
You went with the default it sounds like... A0001 is the model for the OnePlus One, that will be set if you pick the default value. The recommendation is to pick a device from the list, one that most closely matches your device (but not your actual device). It'll still show the wrong model, but you're less likely to experience weird issues...