yashsingh1/xdaforums huggingface dataset:
[Android Software Development] gj4560:
I'm on a Pixel 7 Pro with February patch, USNF 2.4.0, Enforce DenyList on for Google Play store, Google wallet, Google services framework. For some reason CTS profile randomly fails and passes for no obvious reason, sometimes when I check with YASNAC it passes, but other times it fails. So far this hasn't seemed to have affected Google wallet, it still says my phone meets security requirements and I can use tap to pay fine, also the Play store still says my device is certified. Very weird issue, I don't know why it's happening and I've only noticed it start happening with the February patch (I think, I only rooted my phone a few days ago before updating to Feb). It is using BASIC evaluation type although I haven't checked the Google Play integrity checker. Wonder what's going on?
[Android Software Development] JakeDHS07:
They did a background update to GPS which is why people are suddenly failing I'm convinced of it. Couple posts ago someone who was ignoring updates said that it's failing for them even so this is my conclusion. This happens every now and then and I'm sure we'll have a working fix before long as there are many talented and hard working devs in this community. Then a year or so later they will change something again and the cycle repeats. This has always been the case and probably always will be. Why they don't just let people use their devices how they choose to while warning them of the risks I will never understand. It would be very simple to have a disclaimer that people can then dismiss which absolves them of any liability or risk and let's the user assume it themselves. If that were the case none of this hard work would even be necessary. But I digress.
[Android Software Development] pndwal:
I put info here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88114877

But just for fun, would someone with this issue install old USNF 2.3.1 and confirm for me that S/N ctsProfileMatch then passes again (although I'm sure it won't fix PI deviceIntegrity for most)? Ta... 👍 PW
[Android Software Development] JakeDHS07:
I'll give it a shot. Stand by
[Android Software Development] JakeDHS07:
Fail remains the same upon downgrade and reboot. No change.
[Android Software Development] Bad Bimr:
I tried 2.3.1, 2.3.1 Mod 1, 2.3.1 Mod 2 and 2.4 and all fail with a Pixel 6A and a Pixel 7.

It seems Google wins today.

BB
[Android Software Development] joeyhuab:
For fellow custom ROM developers, I can confirm that safetynet/Play Integrity passes again after importing and modifying this commit from hentaiOS and StatiXOS while staying rooted and using kdrag0n's v2.4.0 fix. This is on my latest build for the Xiaomi K20 Pro/Mi 9T Pro, but it's confirmed to pass on my co-founder's OnePlus 8 Pro. We're working on Evolution X updates for the Pixel 6 and 7 series as well and maybe that will give the Pixel users here some hope.
[Android Software Development] JakeDHS07:
That's great to hear! Perhaps @pndwal @Displax @kdrag0n should take a look at this. I'm not sure how to merge a commit like this and publish a build but at least it would be a temp working fix.
[Android Software Development] Displax:
"Ah... Here We Go Again"

Okkkkkk - here you are MOD 3.0 😄

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-87198517
[Android Software Development] Displax:
I'm going to sleep now) 👀
[Android Software Development] JakeDHS07:
Still failing with mod 3? 🤷
[Android Software Development] mingaldrichgan:
Same. 😓
[Android Software Development] JakeDHS07:
I got really excited for a hot second there like damn that was a quick turnaround. Lmfao 😅
[Android Software Development] Displax:
Firstly, test this on Pixel's
[Android Software Development] JakeDHS07:
I'm running a Pixel 7 Pro. Still got fail device integrity here. All current build.
[Android Software Development] mingaldrichgan:
I'm on a Pixel 7 Pro (Feb patch). Should I also have MHPC enabled or not? (I don't currently.)
[Android Software Development] gj4560:
Test what? I don't see the file to download

😅 Maybe I'm not looking in the right spot
[Android Software Development] JakeDHS07:
MHPC is deprecated. And the fingerprints for our device aren't even available through it so might as well not have it at all.
[Android Software Development] Lughnasadh:
Release v2.3.1-MOD_3.0 · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Release v2.3.1-MOD_3.0 · Displax/safetynet-fix

github.com
[Android Software Development] gj4560:
Ah great thanks, I was expecting it to be uploaded here instead of GitHub so I was looking in the wrong place.
[Android Software Development] Displax:
Try this

Original post updated, thanks.
[Android Software Development] toffee^god:
Thank you Displax

3.0 worked for me after clearing play store, services, wallet, play protect and a reboot on Pixel 6
[Android Software Development] mingaldrichgan:
That's what I thought but others have brought it up in recent pages of this thread so I wasn't sure if I was missing something.
[Android Software Development] gj4560:
This version seems to be working great for me on my Pixel 7 Pro with Feb patch! CTS profile passes consistently now and I am meeting both basic and device integrity. I didn't clear data for anything, just installed this test version over the previous 3.0 mod and all seems good. Thanks a lot for your hard work!
[Android Software Development] 5riram:
This seems to work on Pixel 7.
[Android Software Development] zetsumeikuro:
You sir are a Chad. 7pro CTS passing again as well as MEETS_DEVICE_INTEGRITY.
[Android Software Development] mingaldrichgan:
It works!!
[Android Software Development] iwearthebelt:
Excellent news, it's working for me on Pixel 6 Pro, February release. Great job!! Just disabled the other module I had and flashed this one.
[Android Software Development] JakeDHS07:
Success. You're a master 🤘
[Android Software Development] TKruzze:
Can confirm it's working on Pixel 7. This is only module installed.
[Android Software Development] iwearthebelt:
Just want to add that the first time I opened Google wallet I got the message that tap and pay wouldn't work, but after clearing the message I went to my bank and sure enough tap and pay is absolutely working! Thank you Dev!!!
[Android Software Development] vurtomatic:
Works! 🙏🏼
[Android Software Development] bigknowz:
Bear with me, can add cards, haven't tried to GPay yet.

Updated to Mod_3.0, cleared cache Wallet and GPS

reboot and failed Meets_device_integrity, Wallet sees root

In DenyList, unchecked Google Play Protect and for Wallet unchecked lifeboat

cleared cache wallet and GPS

Added cards

still failing Meets_device_integrity, Wallet not warning about root

will update post tomorrow morning after I try to get on the subway
[Android Software Development] Pietplezier:
Updated to to "safetynet-fix-v2.3.1-MOD_3.0.zip" on my pixel 6a with stock rom with magisk on it. 2 green checkmarks again! Adding a card to Google wallet works, haven't tested to actually pay with my phone.

View attachment 5831505
[Android Software Development] xdrc45:
@Displax Thank you for all your hard work. Working fine on P7P
[Android Software Development] gj4560:
Just an update on this, I've noticed that Google wallet occasionally says my device may be jailbroken or running uncertified software and tap to pay won't be available, however it still works and SafetyNet still passes (the pay contactless setup in wallet also says my phone meets security requirements). It didn't happen before on kdrag0n's USNF 2.4.0 (before the background GPS update too presumably) so I'm not sure why this is occurring. Always scares me to see that pop up haha but I suppose as long as tap to pay is still working and SafetyNet is still passing then it's fine.
[Android Software Development] juliovedovatto:
No luck for me, it still fails using the modded version provided by @Displax 🥲

Related info:

Poco F1 (Beryllium) - PixelOS (A13)

Magisk Delta (Zgisk enabled, also HideList)

Cleared both Google Play and Play Services data, restarted device couple times
[Android Software Development] WhoIsJohnGalt1979:
@Displax Pixel 7 Pro with Feb stable and 3.0 and Shamiko works perfectly, normalcy is restored. I don't add play store in deny list when using your mods in deny list to circumvent my phone showing up as a Nexus 6p in the devices list in my Google account under security tab. Thank you once again.
[Android Software Development] nicolas666:
Doesn't work on my Oneplus 7. I am running on PixelExperience.
[Android Software Development] ddrum2000:
I'm passing the cts check as well as device integrity with the new 3.0 mod but I can't seem to add cards. Any thoughts?

Ignore me. I was able to add cards. We'll see about spending money tomorrow :)
[Android Software Development] Bad Bimr:
Had to reboot twice but it seems to work. Keeping my fingers crossed, Tested on Pixel 7. Will attempt on Pixel 6A tomorrow. Keeping my fingers crossed.

BB
[Android Software Development] stubbs95:
OnePlus 7T pro with derpfest 13 custom ROM and magisk delta, even with the 3.0 mod, cts fails.

Here my modules and settings:
[Android Software Development] ProudlyTM:
Mod 3.0 is not working for me either unfortunately.. LineageOS 20 on Redmi Note 10 Pro
[Android Software Development] AndDiSa:
Thank you, @Displax

Working on Pixel 3a with stock ROM ( Android 12 ).
[Android Software Development] jknaggs:
Ok, just installed this morning in UK and after trying many different variations Pixel 7 pro now passes. Shamiko enabled, no enforce denylist and only cache wiped in play services & wallet. Will try payment today and report back. View attachment 5831613
[Android Software Development] Bxperiaz3:
Same for me with the same setup. Displax ftw 🙏🏼
[Android Software Development] seanho12345:
Did you publish the source code for the MOD3.0. I'm curious on what have you changed to make it work.
[Android Software Development] Bxperiaz3:
Actually I'm still getting play store not certified and wallet gives the security standards blurb when I open. Passes playstore integrity and safety net though? I'll try a contactless payment shortly
[Android Software Development] Displax:
Expected that it not work on ROM that manipulate system.prop himself, need to wait wix in this ROMs

Not now. Need some tests and improvements and than will be published.
[Android Software Development] crypticc:
What device? I'm pxl6pro and no dice.
[Android Software Development] crypticc:
How are you able to get both Gpay and wallet. I only see wallet in play store.

Which region are you? I recently came back from holiday in India and they were still using Gpay which was deprecated years ago I thought.
[Android Software Development] crypticc:
I'm still on Google TQ1A.221205.011 which I understand is January and yet over the weekend sporadic issues fixed by wiping the usual app data and reboot, but as of yesterday even that wouldn't work.

I'm thinking they did something on the quiet in FW before xmas, but unused, and just released the app capability recently.
[Android Software Development] crypticc:
Some further information... I've cleared and then uninstalled wallet, rebooted. But wallet is still in toolbar and launches when clicked. It's not in the app list, even as a system app so I can't clear data. Wondering if there's another apk labelled differently and maybe it's that which is being validated. Any next steps/logs needed?
[Android Software Development] Nekromantik:
Pixel 7 Pro
[Android Software Development] inzaghi89:
You need to install universal safetynet modified by @Displax . Afair it's on page 91 this thread. For me it works.
[Android Software Development] shoey63:
Well yes. Had to change it from original stock 12 to stock 10 to get the PI hardware-based verdict enforcement. Now that doesn't work, even Yasnac hardware backed attestation fails unless I use the original 12 stock fingerprint.

Tried the lot. Even HuskyDG's prop reset module. No change.

ROG Phone 3 (ZS661KS)

WW-31.0210.0210.258 (Stock android 12)View attachment 5831683View attachment 5831685
[Android Software Development] digger16309:
I'm on the December update and failing CTS. Maybe it's the Play Services January update (which I have).
[Android Software Development] jknaggs:
OK, have carried out a couple of transactions on Gipsy all went without a hitch. However on initial opening of Gpay I had device unsafe warning. Exited, ran YASNAC and passed. Reopened Gpay , no warning and payment successful.
[Android Software Development] straumli:
Wrt Magisk Modules view: I am able to select and install the old and known v2.4.0.zip but I cannot select this mod. It is greyed out somehow? Could somebody advise what I am doing wrong?

View attachment 5831721
[Android Software Development] inzaghi89:
The file size is different than mine. I'm not sure but I think that it might be downloaded wrong. Please try with my mirror

https://dl.keepmind.eu/safetynet-fix-v2.3.1-MOD_3.0.zip
[Android Software Development] AnyNameYouWish:
So I don't pass device integrity , but I do pass basic integrity.

View attachment 5831719

I disabled all Magisk modules, and deleted XPL folder as mentionned in previous post.

Cleared cache and data from GPS / GMS / Wallet, and installed safety net-fix 2.3.1-MOD latest version.

Tried again with safetynet-fix 2.4.0.

Both fail to pass device integrity.

In Magisk's deny list I have GPS, Wallet and bank apps checked. I also check GMS after reboot to try and see.

Tried with both deny list enforced and shamiko without enforcement.

If that matters, I'm on Pixel 5 A13 january update.

What more could I try to pass both device and basic integrity?
[Android Software Development] straumli:
Your file does the trick, thank you!
[Android Software Development] AnyNameYouWish:
Oh nevermind, mod v3.0 do the trick.

Sorry and thanks!
[Android Software Development] crypticc:
I have that but only see wallet.

When I was in India I momentarily saw gPay as an app but not here in UK.

This is with the modified USNF mod 2.1 installed
[Android Software Development] crypticc:
Which region are you please? Trying to understand how you have Gpay. Even I look in apps there's only wallet and only see that if I manually install wallet from Play Store. (Though the shortcut for wallet in drop down menu even before then)

Correction.... Several reboot and clearing and freezing and rebooting I now have Gpay, but can't find to block in Magisk.

This is actually how it was when I was in India and was able to add my card. Now here cannot so will try adding via Gpay again. (Last time I did the it worked for a day or two)
[Android Software Development] zackielrian:
Rog
[Android Software Development] Marcyvee:
It there a way to pass safetynet with LSPosed zygisk 1.8.6?

Edit: sorry, I passed it.
[Android Software Development] jknaggs:
Apologies, it's Google wallet. All still working OK.
[Android Software Development] pndwal:
So is it something like this?:

gmscompat: Make CTS/Play Integrity pass again …

👍 PW
[Android Software Development] apong1984:
Can someone help me make a mod like as

[safetynet-fix v2.3.1-MOD_3.0]

for riru user

THX :)
[Android Software Development] bigknowz:
View attachment 5831827
[Android Software Development] SchmilK:
Attempted to get things working yesterday with google wallet tap to pay with no success. Saw this this morning from the Pixel 7 Pro thread, installed it over my existing version, rebooted, went to the Cafe at work and taped my way into an egg sandwich and a coffee!

THANK YOU!!!
[Android Software Development] V0latyle:
Use Zygisk. You need to be using an updated version of Magisk anyway, previous versions have security vulnerabilities.
[Android Software Development] _Raziel666:
So is there a way for non-Pixel phones (rooted or unrooted) for this to work or not?

I've tried following this thread the last couple of days but not sure where we are at the moment.
[Android Software Development] apong1984:
I'm use magisk lite channel

It doesn't has zygisk 😅
[Android Software Development] V0latyle:
For what to work, exactly?

You cannot use Magisk modules if unrooted.

You should update to the latest official release.
[Android Software Development] cognitivedissonance:
This morning I just got a pop-up from Google Wallet warning me that my Tap To Pay would no longer be available due to not meeting security requirements. Sure enough when I checked in the Google Wallet app (Profile letter in the upper right > Tap To Pay setup) the first thing listed is the message "Phone doesn't meet security requirements."

I checked to see if safety net was still passing, and the CTS profile match failed. I'm on Magisk 25.2 stable, USNF 2.4.0, Shamiko 0.6 (Denylist not enforcing of course,) Systemless Hosts 1.0, and BusyBox 1.34.1. I've been running this for quite a while without issue.

I found this thread, and installed Displax's USNF 2.3.1 (MOD 3) overtop of USNF 2.4.0 and then rebooted. SafetyNet check now fully passes again including CTS profile match. The issue with Wallet remains though -- it still is showing "Phone doesn't meet security requirements." Is that expected, or are there further steps I can take?
[Android Software Development] _Raziel666:
For payments with Google Wallet!
[Android Software Development] V0latyle:
Clear data for Wallet and GPay, make sure both are in DenyList (include all subprocesses).

Stop checking for SafetyNet pass. You need to be checking Play Integrity.

All you have to do is read this thread. Others have asked your question, and it has been answered many times.
[Android Software Development] osm0sis:
Must be an A/B test, since my device is still doing fine with MOD 2.1.
[Android Software Development] crypticc:
Heads up I've noticed a flurry of updates for banking apps today

Citi

Chase etc

They currently work. Not sure if they will if updated.
[Android Software Development] TotallyAnxious:
Pixel 7 Pro working fine with 3.0 mod.
[Android Software Development] cognitivedissonance:
Well crap, this is the first I'd seen of Play Integrity, and I fail all 3 of those checks. I guess I need to start digging into what's happening there. Very strange that this just randomly popped up. Anyway thanks for the help.
[Android Software Development] V0latyle:
I've written a pretty comprehensive article here that should help clarify things.
[Android Software Development] cognitivedissonance:
Just read through and then skipped to the end. Seems like something may have changed over the course of the past couple days given that people are seeing it break randomly. Hopefully a better understanding of how to pass the checks more reliably is gained in the near future, because it sounds like right now there's no definite way to fix it in the same way we worked around safetynet.
[Android Software Development] cbomb1337:
All these USF mods drain my battery badly. They create a wakelock. Noticed it before in pixel 6 and tab s7.
[Android Software Development] jknaggs:
Just updated Chase UK and working fine.
[Android Software Development] iwearthebelt:
I had the same issue, it will disappear after the first time you opened the wallet. It shouldn't show that message again.
[Android Software Development] ddrum2000:
I'm not sure how i got both because this was not previously the case. I'm in the USA.
[Android Software Development] cognitivedissonance:
You're correct - Wallet only gives the one pop-up, but it still seems to be detecting an issue with Play Integrity, which is unsurprising because I currently am failing all 3 of the Play Integrity checks.

Have you checked your Play Integrity? And have you checked in the Wallet menus to see if it still shows the message I mentioned?
[Android Software Development] V0latyle:
Well, as @pndwal pointed out, Google appears to still be tinkering with the inner workings of the Play Integrity API, as he described here. Up until this point, PI only seemed to evaluate the profile/fingerprint of the device, and accept basic vs hardware-backed attestation as is. Now, it seems that they're attempting to verify whether the fingerprint/profile of the device matches what's actually running - so for example, my Pixel 5 running Android 11, 12, or 13 is a valid CTS profile, but 10 or prior is not.

In other words, PI doesn't appear to simply accept whether basic vs hardware backed attestation is used, but rather is determining which should be used based on the environment - that is, any compatible platform running Android 8+ should be using hardware backed attestation.

@Displax would you mind explaining what all changed in Mod 3.0?
[Android Software Development] crypticc:
Sorry to bug you but this mention of both wallet and Gpay really confusing me.

When I look in apps Inc system I only see wallet (and only if I've actively installed from Google play). If I search Gpay it brings back the wallet (again only if actively installed)

The wallet shortcut still works in the menu but I presume it's using a hidden APK that I can't block it clear.

That's UK phone pxl6pro

Edit:. Actually then installing wallet again (I think Magisk still had the flag set from previous install) and I've now been able to add a card.

This is still with the mod 3 that I updated to earlier that was previously failing.

I still don't understand the references to Gpay on UK phones but for now at least I'm up and running again.

P.s. this is what I get in pi check

View attachment 5831971
[Android Software Development] chuppito:
hello, do you have a functional solution for wallet? so far I'm failing. I tried the 2 versions Universal safetynet fix
[Android Software Development] cognitivedissonance:
Some of this is definitely over my head, so just in case it helps give context to someone who knows a lot more than me, I guess I'll give a couple additional details about my setup. I'm on a Pixel 2 XL running the latest Android 10 factory image, taken directly from Google.

I also have a sneaking suspicion that I may have screwed something up with my attempts to install the root version of ReVanced Extended. Those attempts included uninstalling Vanced (which was installed overtop of the system YouTube app,) reattaching YouTube to the Play Store (had been disconnected using TeMeFi,) then updating YouTube with the target version from apk mirror, patching it, then installing the patched version over top, and finally detaching using TeMeFi again. TeMeFi seems sorta intrusive, so it could be that, or it could be screwing with a system app that's causing me to fail Play Integrity checking.

Gpay ---> https://play.google.com/store/apps/details?id=com.google.android.apps.nbu.paisa.user

Google Wallet ---> https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel
[Android Software Development] Jon8RFC:
Mod 2.1 failed to help as of yesterday (maybe before then, I hadn't checked in at least a week) on p7p with JANUARY 2023 update.

Installed mod 3.0 on JANUARY 2023 update and all is well.

Thanks!
[Android Software Development] V0latyle:
There actually seem to be 3 separate components.

Pixel firmware has some sort of built in GPay/Wallet functionality. There's also the standalone GPay app, as well as the standalone Wallet app. I have both on my Pixel 5, but if I uninstall both of them, I still have Wallet in my Quick Settings.

Try this:

Remove any previous versions of Universal SafetyNet Fix and MagiskHide Props Config from Magisk.

Reboot device.

Go into Magisk DenyList, and enable DenyList on all components of Play Store, Wallet, and GPay. Clear data for all 3 apps.

Download and install USNF 2.3.1 MOD 3.0

Reboot again

Check Play Integrity status, use Play Integrity API Checker
[Android Software Development] V0latyle:
Shouldn't be hard to pass BASIC and DEVICE integrity. See my previous post

I don't think this would actually cause it, but it's possible.