Google wallet occasionally fails security test

[knasiotis]

As reported by two people on XDA dev thread (check GT500x's posts as well), sometimes Google Wallet shows that the device is not secure. Zygisk enforce is enabled, google gms and google wallet are included in the exceptions list. I have also tried lsposed hidemyapplist and hid everything magisk related from google apps. The weird thing is that google wallet fails, then it works. If I leave my phone idle for 30 minutes for example (or after booting the phone) and reopen google wallet it will fail again, and soonly after, it will pass. So it's kinda working and at the same time it's not working. Integrity checker meets DEVICE_INTEGRITY and BASIC_INTEGRITY I even tried changing props. Didn't work. This started after installing the new Android 13 MIUI 14 EU rom so I am curious if google added a new test for integrity or something on android 13. It's not just wallet, integrity checker app fails and if I do one more test, DEVICE_INTEGRITY and BASIC_INTEGRITY will pass again. Device model: MI 11 Ultra (star) Android version: 13 ROM name/version: MIUI 14 EU rom (stable) USNF, magisk, LSposed and hidemyapplist versions obviously latest

[gilcu3]

Same here with Lineage OS 20 on a Oneplus 7T. Google Wallet started complaining just a couple of days ago, after being fine with the latest version of this module since it was published. EDIT: strangely enough, this doesn't happen with the @Displax's latest version

[pndwal]

I can confirm 2.4.0 is failing intermittently for many; I can get failed deviceIntegrity in Play Integrity API checker immediately after boot, and @osm0sis reports ctsProfileMatch failing in YASNAC also...

Google Pay/Wallet users particularly are getting failures w/ 'Device doesn't meet Security requirements' message as Google monitors device security even when Pay/Wallet is not invoked... Many users are reverting to @Displax's USNF modded fork ATM and variously clearing Play Services, Play Store and G Pay/Wallet data to restore working Pay/Wallet...

My device (Xiaomi RedMi Note 8T w/ stock MIUI A10) like many A8, 9 & 10 devices, actually needs none of the three prop based bypasses we now have to pass either S/N or PI deviceIntegrity; I do need the principal broken keystore based fallback to Basic attestation to pass these however... Because of this, I think the issue is something other than the new temporary fingerprint prop spoofing... Guessing that the fake keystore may simply be registered too late or that some other change is preventing USNF from working straight after bootup...

[rapperskull]

Yesterday Google Wallet gave me the Device doesn't meet Security requirements message, while Play Integrity API Checker says I'm good. My device is the Realme GT 2 Pro.

[hondacbr600]

Yesterday Google Wallet gave me the Device doesn't meet Security requirements message, while Play Integrity API Checker says I'm good. My device is the Realme GT 2 Pro.

I even had a notification from Google Wallet^^ I added every google process I found to the deny list, idk if this helped or not, but I was able to use wireless payment. Xiaomi 11T Pro

[knasiotis]

Same here with Lineage OS 20 on a Oneplus 7T. Google Wallet started complaining just a couple of days ago, after being fine with the latest version of this module since it was published. EDIT: strangely enough, this doesn't happen with the @Displax's latest version

After reboot Displax's version also fails

[gilcu3]

Same here with Lineage OS 20 on a Oneplus 7T. Google Wallet started complaining just a couple of days ago, after being fine with the latest version of this module since it was published. EDIT: strangely enough, this doesn't happen with the @Displax's latest version

After reboot Displax's version also fails

Mine doesn't. It has been working for several days with some reboots, and just tested now again, and still nothing detected by Wallet.

[fzechert]

I can confirm intermittent issues with Google Wallet / Pay with both the newest version 2.4.0, as well as with the special 2.3.1 version from this older bug #196 .

I started to observe these problems on Wednesday 2023-01-25.

Device Info Device model: OnePlus 7T H1903 Android version: 12, Security patch from August 5, 2022 ROM name/version: HD1903_11_F.17

Usually a reboot of the phone solves this problem for a couple of hours, until the problem reappears. I have installed Displax's version mentioned above and will report back as soon as possible whether this helps or not.

If I can do anything in the meantime to help with debugging this problem, feel free to let me know.

Edit: Displax's version has the same intermittent problem on my device.

[stanelie]

I've noticed that just switching ON the deny list in Magisk and switching it back off is enough to make the issue go away for a time.

Maybe it's unrelated...

[IMgoRt]

I get this most times now on my OnePlus 8 A13, running YASNAC clears it for a short while

[TheSingular]

For me, it fails on rebooting the device and also randomly after leaving it idle. Opening the Magisk app afterwards fixes it (no need to switch deny mode).

Samsung Galaxy A80 on Android 11. I also have shamiko module.

Edit: I have installed Displax's latest version(2.3.1-MOD_2.1), and have no more issues.

Edit Feb. 8th,2023: Suddenly play integrity and even safetynet's basic integrity fails. My phone passes no checks now.

Another edit: Uninstalled System UI Tuner app and reset all its changes, then rebooted. It's working again now.

Edit Feb 9th, 2023: I have installed the latest Displax version again since there was an update (2.3.1-MOD_3.0), once again no problems.

Edit Feb 13th, 2023: I have installed the latest Displax version again since there was an update (2.4.0-MOD_1.1), once again no problems so far.

Edit Feb 14th, 2023: 2.4.0-MOD_1.1 from Displax has the same problem as 2.4.0 of kdrag0n. Have to open the magisk app for it to work for some reason. Reverting to 2.3.1-MOD_3.0.

Edit Feb 18th, 2023: Installed 2.4.0-MOD_1.2 at February 16th, no problems.

[AByakugans]

Same here, after restart Google Wallet is saying my device is rooted or not certified. Tried it with original USNF and Displax version both the same. Device is Samsung Galaxy 20 Note Ultra 5G with Android 13. With or without Samiko the same. Anyone has working solution to this?

[kovaga]

Device Info Device model: OnePlus 7T H1903 Android version: 12, Security patch from August 5, 2022 ROM name/version: HD1903_11_F.17

i have the exact same version as yourself. And started getting the same messages around mid january as well. Tried with the 2.4.0 version just now, added 2 cards fine, then tried adding paypal account, but failed with the "rooted device" message.

[Conan179]

Hello@all My Fold4 has now "caught" it too. Sometimes I get the message that I don't pass the safety standards, sometimes not. The message has been coming to me for 2 days. Inntresandt is, I just tested the intrigritet twice. The first time, I failed devices, the second time I didn't, I didn't close the app, just briefly in the background. Device model: Samsung Fold 4 Android version: 13, Security patch from 1. Januar 2023 ROM name/version: stock one ui rom

[vonernue]

I'm currently on Pixel 7 and is also encountering issue with the USNF 2.4.0 or the modded 2.3.1. However, my issue seems to be a lot worse. My device simply won't pass CTS profile match or DEVICE_INTERGRITY. No matter how much time I clear the GAPPS. Can someone provide a list of what they are clearing or any steps that I probably done wrong in the process?

[rapperskull]

My device also started failing DEVICE_INTEGRITY intermittently.

[ahaverty]

FWIW: I'm not rooted, and I don't have this library installed, but I did start getting this same issue yesterday on gpay & play store after a month of pixel experience working flawlessly on my OnePlus7T Pro. Others on Reddit responding with the same: https://www.reddit.com/r/PixelExperience/comments/10wgvf1/your_device_doesnt_meet_security_requirements_on/

(2023/02/13 Edit: I've since caved and bought a new phone. Good luck all 💪)

[vonernue]

FWIW: I'm not rooted, and I don't have this library installed, but I did start getting this same issue yesterday on gpay & play store after a month of pixel experience working flawlessly on my OnePlus7T Pro. Others on Reddit responding with the same: https://www.reddit.com/r/PixelExperience/comments/10wgvf1/your_device_doesnt_meet_security_requirements_on/

I do have a OP7T that is running PE12 and have an ancient USNF v2.2.1 with MHPC installed. It's running perfectly fine with CTS profile and DEVICE_INTEGRITY passed.

[o0Mardev]

this type of error with Google wallet happened to me too now I have installed the safety net fix mod 2.3.1 by Displax. I will report if it works.

Edit: Everything seems to work I installed version 2.3.1 mod 3.0

[LuminarySage]

I'm currently on Pixel 7 and is also encountering issue with the USNF 2.4.0 or the modded 2.3.1. However, my issue seems to be a lot worse. My device simply won't pass CTS profile match or DEVICE_INTERGRITY. No matter how much time I clear the GAPPS. Can someone provide a list of what they are clearing or any steps that I probably done wrong in the process?

Same thing on my pixel 7 pro. Saw on xda forum someone said that devices that launched with android 13 got it worse from this whole snafu

[ElijahElliotP]

On a rooted Asus Zenfone 9 (USNF 2.4.0) - had been having this problem for a couple weeks, despite passing checks using the deny list, etc. Two days ago the wallet warning spontaneously went away and I have been able to tap to pay. I have made no changes to the phone in this time though.

[jcgoble3]

I also have the CTS profile match/device integrity failure. Pixel 7 (non-Pro here running stock Android, rooted with Magisk and USNF 2.4.0. Have not tried any solutions yet as GPay mobile payments are the only thing currently I have been blocked from, and that isn't a huge deal to me since I always carry my physical credit card (several places I go regularly don't accept tap-to-pay). As long as Pokemon GO and my banking and 401(k) apps are happy (and so far they are happy), it's not a big deal to me.

[vonernue]

Just tried the new MOD 3.0 from Displax. Everything is working flawlessly with CTS profile match and DEVICE_INTEGRITY passed. https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_3.0

[jcgoble3]

The MOD 3.0 seems to have done the trick for me as well. If GPay still complains about not meeting requirements after installing Displax's mod, even though YASNAC or Integrity Checker are happy, try force-stopping GPay and clearing its cache then re-opening it.

[ElijahElliotP]

On a rooted Asus Zenfone 9 (USNF 2.4.0) - had been having this problem for a couple weeks, despite passing checks using the deny list, etc. Two days ago the wallet warning spontaneously went away and I have been able to tap to pay. I have made no changes to the phone in this time though.

I used tap to pay only 6 hours ago. Opening the wallet app this evening and the notice is back - can no longer tap to pay. Again I have made no deny list modifications or changed anything else within magisk in the intervening time.

[jcgoble3]

Update: When I ran out at halftime of the Super Bowl to grab takeout for dinner, I tried to pay with my phone and got the same "Try again" message that I've been getting for a couple of weeks. No message pops up in the app and YASNAC and Integrity Checker are happy, but when I actually try to pay it doesn't work with the same message I've been getting since this started.

[Tragen]

I had the same problem. YASNAC was good and I couldn't pay. I switched to Displax for now. 4.0-MOD1.1 and everything is working fine now.

[kovaga]

https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_3.0

Works for me as well. Just made two payments.

[Tragen]

Google Pay works but the banking app bunq still says my phone might be rooted

[o0Mardev]

Update. I am currently using the latest wallet version: 2.177.509644858 and the latest Displax module 2.4.0 mod 1.1. Wallet is still showing this message Even though safety net and play integrity always pass (except the last play integrity flag STRONG_INTEGRITY) (Edit I also tried to use magisk denylist on wallet)

[Displax]

Update. I am currently using the latest wallet version: 2.177.509644858 and the latest Displax module 2.4.0 mod 1.1. Wallet is still showing this message Even though safety net and play integrity always pass (except the last play integrity flag STRONG_INTEGRITY) (Edit I also tried to use magisk denylist on wallet)

Use MOD 1.2 and clear GMS data, if needed.

[o0Mardev]

I updated to MOD 1.2 and cleared Google play services data, now I'm stuck on "Google Wallet is currently updating" message. Edit. now it works correctly.

[macerg]

I am getting the same issue on both of my OnePlus 6 Android 11, Magisk 26.1 plus USNF V 2.4.0 Intermittent security fail on Google wallet.

[pndwal]

... USNF V 2 4.0...

What build is that?

Official was known to be broken for some time now... Have you tried @Displax fork yet?

[macerg]

Yes, I installed it today. That is failing also but perhaps not so frequently. Hard to tell as early days.

[pndwal]

Yes, I installed it today. That is failing also but perhaps not so frequently. Hard to tell as early days.

In case of issues with latest @Displax build, some have found that his pre-part-time spoofing v2.3.1-MOD_3.0 build works better...

[macerg]

Yes, 2.3.1 seems to be better for me too.

[fengchupc]

Agree 2.3.1 I've downgraded from 2.4.0 and now looks all is working as expected. Will try it in a POS tomorrow.

Tried this morning, and even though it popup the root alert in Google Pay when I restart the mobile but it's working. The only thing is the payment card isn't the one that I set as default. That payment card I've removed from my Google account already and set another one as default, but it still using the old card.

[kazink]

Google Wallet started showing me the "This device doesn't meet the security standards" warning only a few days ago. I noticed that it shows the message only every few hours. If I restart the app, the phone, or even clear the cache and run the app again, it won't show the message again, but trying to pay will fail anyways. Maybe that causes confusion in some people, who think it sometimes works. For me at least it didn't work at all (despite YASNAC and Integrity Check consistently showing a pass in both app and basic integrity). I had some old kdrag0n version of the fix (a half year old, or more) and the google apps deny-listed in Magisk. Tried to update to the newest version 2.4.0 - it didn't help. Tried displax's 2.4.0-mod_1.2 - didn't help. The thing that fixed it for me, as for people above, was displax's 2.3.1-mod_3.0. I have a fairly old phone with Android 9. Perhaps that's related. Thank you.

[devauxbr]

Hi all,

FWIW I was in the exact same situation as @kazink with my OnePlus 6T running on up to date LineageOS 20 + Magisk with deny-list for Google packages + MagiskHide Props Config to get basic SafetyNet passing : Google Wallet was working fine... Then one day it was not, with this "This device doesn't meet the security standards". Opening the app randomly showed the message,sometimes not, but still on every payment attempt the message would show up and payment systematically failed (YASNAC and Integrity Check still passing without issue)

Tried to install latest kdrag0n safetynet-fix : no luck Tried latest displax's 2.4.0-mod_1.2 : no luck Tried older displax's 2.3.1-mod_3.0 : works like a charm 🎉 🙌

Thanks !

[linjan]

Reporting, that also installing 2.3.1-mod3 instead 2.4.0 helped. Thanks a lot🙏

[pndwal]

Reporting, that also installing 2.3.1-mod3 instead 2.4.0 helped. Thanks a lot🙏

Did you try most recent modded (2.4.0-mod_1.3) build?... It has now been fixed for most...