yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] jpschewe:
I've recently noticed that Google Wallet isn't working for me again. I had it working for the past 6 months under Lineage OS with Magisk installed and the deny list active. However now wallet is complaining that the device doesn't meet security requirements. I'm passing YASNAC. I've recently found play integrity checker and that fails on MEETS_STRONG_INTEGRITY.

I tried hiding Magisk and that didn't help. I tried the universal safetynet module and that didn't help either.

Other ideas?

Device: OnePlus 6T

OS: LineageOS 20-20230706-NIGHTLY-fajita

Magisk: 26.1 (26100)
[General Questions and Answers] simplepinoi177:
First, most rooted devices will fail MEETS_STRONG_INTEGRITY, but can still successfully use Google Wallet -- as I understand it, there are very few apps and protocols that rely on meeting strong integrity as a security function to restrict/deny access or allow continuing using the app/service.

Second, just some ideas & thoughts;

you don't identify which USNF module you utilize, so in case you are using the original, you may want to consider using Displax's MOD as there has been further successes in many cases using his than the original

You may want to consider using the beta version of Magisk to get the bleeding edge of rooting with it and install/flash Magisk Canary -- especially considering you are using a custom ROM. If anything, you probably want to post in the LineageOS threads as it might be an issue between the ROM, Magisk, and Google Wallet more than anything; especially considering you said it was working fine for 6 months

there are multiple other root hiding methods that have varying successes -- one that comes to mind for you is the use of Shamiko if the regular ol' denylist is no longer working.

Also it wouldn't hurt if you reconfigured the denylist, and then did the obligatory clear cache & data of Google Play Protect, Google Framework, Google Play Services, Wallet, Gpay -- be aware this will remove cards if you have them entered in Wallet and you will merely have to re-add them -- and be sure to restart (personal experience; I did all that and couldn't add card, but after restart I could).

Hope this helps and good luck!
[General Questions and Answers] b_fizzle:
Exactly my issue too.
[General Questions and Answers] Johnjohnvg:
Universal SafetyNet Fix [MOD] worked for my Xiaomi Redmi Note 11 NFC with custom ROM​

Used version v2.4.0-MOD_2.0 and despite that the device fails "MEETS STRONG INTEGRITY, wallet is fully functional.

Found it here, https://xdaforums.com/t/cts-profile-match-failed.4414843/#post-88135049, thank you Oshvitzon
[General Questions and Answers] andriy_:
The same issue here. I even reissued the card (but number left the same) - still can't add it to the Wallet. Other cards work, the problematic card works on other phones... I sent the logs to google few months ago, waiting.
[General Questions and Answers] simplepinoi177:
Sounds like an issue I had with one of my cards -- it wasn't rooting or even the device (not directly). I had to call the bank, and something on the bank's end had to "authorize" it to work on my specific device & my device's Wallet. That's why it'll work on other phones but not on mine -- I was able to add on my wife's but not on mine. Supposedly there was something of a signal being sent from my device's Wallet that was flagged or had to be cleared/authorized on their end to get it to work on my phone/device.

This might explain it -- and even absolve magisk/rooting in terms of affecting it...
[General Questions and Answers] andriy_:
The bank told me that they don't receive any calls from the phone / Google during the procedure. They cleared the tokens etc. - it didn't help also....
[General Questions and Answers] simplepinoi177:
yes....that "tokens".....it was just a thought....sorry that didn't work..

Have you cleared data for Google Play Store, Google Play Services, Google Framework, and Play Protect, and of course Wallet & GPay? (This will remove all cards)
[General Questions and Answers] andriy_:
Sure, I did these things multiple time (except Google Framework - I don't have it). At some point Google told me that my account triggered some security alerts, and I need to slow down. Also I deleted the card from pay.google.com etc.
[General Questions and Answers] simplepinoi177:
K...just confirming....

sorry it all hasn't helped working it out...
[General Questions and Answers] nik3r:
Leaving this here for people with similar issue.

If you install a SafetyNet Fix of your choice that works and YASNAC passes BASIC test but Wallet still will not work.

The Wallet checks some kind of tripwire in Google Play Services so you need to refresh that while you're passing.

1) Make sure YASNAC passes.

2) Clear data for apps Google Play Services, Google Play Store and Wallet.

3) Clearing Google Play Services will break your google accounts login, so remove all google accounts from the phone.

4) Reboot and add your primary google account from play store.

5) Wait for Play Store to certify your device (in options last entry), this seems to be rate limited to several times a day so have patience if you did it recently and the line doesn't show up at all.

6) Wallet contacless payments should now work fine.
[General Questions and Answers] DineshValor:
Did you able to pay via NFC?

Tried myself to add card and pay via NFC and it's fail to via Gpay Tap to Pay at Petrol Pump.
[General Questions and Answers] adamater2:
Magisk delta + hidelist + all google things onto hidelist worked for me (pixel 6 android 13 custom kernel), and deleting all magisk apks in download folder

Also have installed diplax safety net fix and shamiko but it was toggling the hidelist that fixed it.
[General Questions and Answers] hssxda:
You are GENIUS!!! I deleted all magisk files from my downloads folder and without doing anything else Wallet no longer warns me that I can't use tap to pay!!
[General Questions and Answers] MightySashiman:
hi there, strangely wallet worked this morning for contactless payments, and now it's giving me an error (the usual device is not secured enough, might be rooted...)

Can someone relate to my issue?
[General Questions and Answers] gorkmc:
The same issue here on my Oneplus 6. OxygenOS 10.3.12. Android 10.
[General Questions and Answers] deechte:
Same here since 2 days on Oneplus 11.
[General Questions and Answers] stalker780:
Today Wallet was blocked both on my and my wife's phones.

Magisk 26.3/26.4 + safetynet-fix does not work any more.

Looks like a new wave of updates from Google.
[General Questions and Answers] Lughnasadh:
Try using this.
[General Questions and Answers] 4Ny:
Same here. Magisk Canary aa6c6c15.

POCO F2 Pro. Android 12. MIUI 14 Stable.

Diplax safety net
[General Questions and Answers] deechte:
Instead of the Safetynet Fix module or alongside it?
[General Questions and Answers] Lughnasadh:
Instead of. If your using Displax's mod it will replace that so you don't have to uninstall it first.
[General Questions and Answers] deechte:
Thanks I'll try. I've never heard of any displax mod.
[General Questions and Answers] stalker780:
Thanks. This fix worked 👌
[General Questions and Answers] deechte:
Terrific, this module instead of Safetynet Fix is the solution. Thanks so much for dropping this here.

Could you explain what the difference between the modules is, besides the fact that one works and one doesn't work anymore?
[General Questions and Answers] Lughnasadh:
USNF spoofs fingerprint in general while PIF only spoofs Google Play Services to pass Play Integrity/SafetyNet checks.
[General Questions and Answers] 4Ny:
It's not working for me

EDIT : Probably because of MIUI
[General Questions and Answers] gorkmc:
It doesn't work for me either. Have you done anything other than install PlayIntegrityFix ?
[General Questions and Answers] Clasimodo:
I cleared data of Wallet, Google Play and Google Play Services. After this a reboot. It seems that clearing data of the Services can lead to problems in Samsung wearables (watch). The earbuds don't give problems here.
[General Questions and Answers] Clasimodo:
Sry
[General Questions and Answers] deechte:
I did clear data of Wallet, Google Play Store, Google Play Services and Services Framework before installing PIF, because I was trying to get it to work with SNF. And of course had a bunch of Google apps in the Zygisk Denylist etc as per the other instructions in this thread.
[General Questions and Answers] gorkmc:
It still doesn't work. I cleared the cache of Wallet, Google Play Store, Google Play Services and Services Framework.

Added the above apps to the Zygisk Denylist. Safetynet check passed. However, Wallet check says my phone is not secure.

What is PIF and SNF?
[General Questions and Answers] simplepinoi177:
You should clear data on all of those after installing PIF. For the most part, Displax MOD (and PIF I believe, but I'm not sure) doesn't require those to be in Denylist, but it never hurts -- supposedly it/they do it automatically under the hood.

PIF is Play Integrity Fix and SNF is probably short for USNF which means Universal SafetyNet Fix which what's posted in the OP...

The original and main branch of USNF is unfortunately rather a bit out of date (I don't know if development on it is completely dropped or not), so Displax's MOD for it is the more updated one, and then PIF compounded on what he was doing so it applied to more devices on other OEMs (I believe, I've never needed to use PIF so I don't know too much about it)....

In either case, the reason why it's starting to be out of date and/or might not be actively developed is because SafetyNet has depreciated as the commonly established method of checking security/integrity. Google and most other apps/services now use Play Integrity API (hence the "Play Integrity" in the PIFixer) -- so to check your device, it's best to use Play Integrity API Checker or the more comprehensive TB Checker apps to check your device.

In terms of Play Integrity API Checker, it's acceptable to only pass 2 of the 3 as the 3rd "MEETS_STRONG_INTEGRITY" hardly any apps employ that requirement to be checked to run.
[General Questions and Answers] MightySashiman:
After installing the v12 module, I'm having an issue trying to readd my payment card to Wallet. It's telling me I'm going to receive a code by SMS but nothing ever happens. Wallet app briefly shows a loading icon, but I don't receive an SMS with a code, and Wallet doesn't display a screen where any code should be input by the user. Can somebody relate?

Edit: fixed. I had previously cleared data+cache of both Wallet and PlayStore. It wasn't enough. Had to also clear Play Services (and reboot of course). After that, the registering process of my card did work correctly.
[General Questions and Answers] Pietplezier:
Google wallet was working great for monts and monts, and since today it was broken "seems to be rooted bla bla" PlayIntegrityFix did the magic!!!! :-)
[General Questions and Answers] atay_:
I could confirm as well. Yesterday Google Wallet stopped working, saying "Phone doesn't meet security requiements", but after installing this one and clearning data of Wallet and Google Services, everything works again. BeyondRom 6.4, S20.

Thanks!
[General Questions and Answers] gorkmc:
It's work for me, too. I just cleared the cache data for the above Google apps. And now there is au update, v12.1
[General Questions and Answers] △ TRY △:
I managed to make it work .

I'm on Redmi Note 10 Pro , Magisk 26.4 , SafetyNetFix v2.3.1-MOD_3.0 & I'm on Stock MIUI.

Magisk working, YAASNAC Safetynet passing , but couldn't use Google Wallet .

Here's what I did :

1. Installed Magisk , installed safetynet and hide props module

2. Enforced Deny List + Configure Deny list to Google Apps ... Wllet , Google , Play Services all that

3.Used Termux to edit devices fingerprint - changed with Redmi Note 10 Pro Global

4. Cleared all data from Google ---> Apps , Google Play Services - Manage data - Clear all data

5. Cleared Wallet storage

6. Rebooted

7.Happy cuz all is working fine now . SafetyNet Passing and Waller Security Requirements
[General Questions and Answers] Fooking Rekt:
You are not supposed to add Google services to Denylist
[General Questions and Answers] simplepinoi177:
At least for Displax MOD, it kinda doesn't matter -- Displax does stuff under the hood on the Google Services stuff. To the point that you'll find that at least one doesn't even stay checked in DenyList and would still pass (at least before Google's last update)....
[General Questions and Answers] simplepinoi177:
Still...??? That's confusing....I mean, Wallet is still supposed to work on an unlocked bootloader; it really is just root detecting....

I imagine clearing the cache and data (while still unrooted) of Play Protect Services, Framework, Play Services, Play Store, Wallet, GPay should work it all out....

If not, I've bookmarked this
[General Questions and Answers] ZitroneEmu139:
SafetynetFix is available in a new version 2.4 and has also worked for me with the Redmi Note 10 Pro. I just did not hear the data and am also heard, Let's at least now see if there is still an error in the own hours when paying

------------- German ----------------

SafetynetFix ist in einer neuen Version 2.4 erhältlich und hat auch für mich mit dem Redmi Note 10 Pro gearbeitet. Ich habe die Daten einfach nicht gehört und bin auch gehört, Lassen Sie uns zumindest jetzt sehen, ob in den eigenen Stunden noch ein Fehler beim Bezahlen vorliegt
[General Questions and Answers] Fooking Rekt:
Adding certain Google apps to Denylist makes them not run properly and then things such as Wallet will stop working. Only the specific app, in this case Wallet, should be added to Deylist.
[General Questions and Answers] simplepinoi177:
I have a different experience (it works whether on or off Denylist) and I remember it being discussed about Displax's Mod not caring if it's on there as it invalidates it anyways, but I could easily be wrong (or my circumstance is different) and I'll take your word for it....
[General Questions and Answers] bl3d2death:
Suddenly my wallet app won't work. I did not changed anything. Must be an update or something like that.

Any idea how to fix properly?
[General Questions and Answers] deechte:
That's not my experience. I always add every app from Google and my bank to the deny list.

Read back.
[General Questions and Answers] Fooking Rekt:
In theory this should not only not work, it should actually break Google Wallet
[General Questions and Answers] deechte:
What can I say. It has worked flawlessly for me for years across different devices.
[General Questions and Answers] simplepinoi177:
I must say, I'm of the same experience as @deechte 🤷‍♂️

If it means anything, I'm on a Pixel 7 Pro....
[General Questions and Answers] Zoneee:
+1 after the latest Wallet update, I think. Magisk was updated before that to 26.4 as well. Im on a Realme GT 5G with Realme UI 4 (A13 5 October Security Update)

I was using the Displax mod successfully for a few months now without any breakage.

Tried the safetynetfix by Chiteroman, but I think its still broken according to the latest discussion in his thread:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

The game of cat and mouse still continues.
[General Questions and Answers] XdekHckr:
Guys this method is completely useless, just install safetynet fix and change magisk name and hide root from Google apps and services then clear their data and reboot and you are good to go.
[General Questions and Answers] soadzoor:
A few days (or 1-2 weeks) ago, my phone (poco f2 pro) started having problems with google wallet, it complained about being rooted. I have stock rom with unlocked bootloader and magisk with safetynet fix and the usual google apps in the denylist.

I tried a lot of things, but only one of them worked: uninstalled safetynet fix, and installed play integrity fix: https://github.com/chiteroman/PlayIntegrityFix

After reboot and clearing data for wallet, I was able to add my card again. Hopefully some folks find this helpful. Cheers
[General Questions and Answers] laolaxyz:
I failed with all solutions proposed with playfix v12.x. However with v13 is's working like a charm (Samsung S21ultra with Dr. Keatan ROM V11)
[General Questions and Answers] gschaden:
For me instructions at https://github.com/chiteroman/PlayIntegrityFix helped. I disable other magisk modules and only used this one.

On a redmi note 10 pro.
[General Questions and Answers] thefanum:
This is what I've done, successfully, for years. The entire time really.
[General Questions and Answers] marc_aurel:
New Wallet Version 23.44.582097972 from today

seems to break the combination Magisk + PlayIntegrityFix

again.
[General Questions and Answers] marc_aurel:
problem fixed with latest PlayIntegrityFix 13.9
[General Questions and Answers] ZitroneEmu139:
English:

Sorry for the question,

Did I understand that correctly? I should not add a google service to the denylist? wasn't that always mandatory before or have I misunderstood something?

------------------------------------------------------------------------------------------------------------------------

German:

Sorry Für die frage,

Hab ich das jetzt richtig verstanden? Ich sollte keine google service zur Denylist hinzufügen? war das nicht vorher immer pflicht oder hab ich da jetzt etwas falsch verstanden?
[General Questions and Answers] tfhavel:
I just got Gpay to work on a Magisk rooted Pixel4a by installing the Play Integrity Fix module v14.5 by citeroman which requires Zygisk (build sunfish-ota-tq3a.230805.001.s1).
[General Questions and Answers] △ TRY △:
Found a way to make it work .

1.Magisk Manager

2.Zygisk Enabled + Systemless Host

3.Play Integrity Fix (by chiteroman)

4. After installing the module/ modules I EnforcedDenyList on : PlayStore , GoogleWallet, GooglePlay

5.Every now and than I have to cehck for updates on the PlayIntegrity module for making sure banking apps and GWallet would work ...

6. After every update I clear the cache on GooglePlay Services and reboot ... or clear all data in the GooglePlay Services.

This is working just fine for me ... I used it on stock rom and custom roms too ... works the same . The only inconvenience is that you have to be up to date with the module updates for it to actually work ...
[General Questions and Answers] simplepinoi177:
One thing that should be made known is that Play Integrity Fix (by chiteroman) will no longer work "out of the box". There are some reports that the module is still working for some, but that is bound & inevitable to not be the case within weeks (if not days). The method he employed to get ALL devices using his module are continually blocked by Google and he had to update the module & version every 2-4 business days (they didn't seem to block on weekends 😆). So he's made the decision to stop and one must find their own aspects of his method and implement it in his module to get it working -- this doesn't mean he's stopped developing or updating the module though!

Now it is a mad dash to use the 3 or 4 other methods out there that somewhat automate the "method" he was using to a new "fingerprint" (unless you're very willing to look into it, just take the term in context), but they all require a number of further steps and considerations and none work "out of the box" (install, and simply leave and forget with no set up or modifying of the module) that the main branch of Play Integrity Fix (PIF) used to be able to achieve/do.

There is a lot more involved and time consuming method (which I can state and go further into in this thread, if prompted to), but once figured out, found, and set up, it seems to be more consistent and stable with no further steps to it working (most of us who have done it haven't had the need to change or update; unlike the 3 or 4 methods i talked about above) -- just checking every now and then that you can still use Wallet.

Apologies for this wall of text, but I just wanted to make it known at least in this thread this consideration & caveat in relation to the established and most acknowledged condition to getting Wallet to work (passing MEETS_DEVICE_INTEGRITY; merely passing SafetyNet attestation [depreciated; out of favor] and cts profile match is

no longer enough

).
[General Questions and Answers] airmark:
I hereby prompt you to go into further details :)
[General Questions and Answers] simplepinoi177:
So the more involved and time consuming method is to go through dumps of files in ROM firmware images (either in websites that publish such files individually or extracting such files yourself). You find a specific file called the build.prop file and you look into the fields & values in there and see if they meet a certain criteria (that, I can also go into further details if prompted). If not, you move on; if they do, then you download that and the other build.prop files in the firmware image (dump or extracted), and you have to get the fields & values of around 8-12 fields -- which are informally referred to as the "fingerprint" (of the device). You copy them into a blank file in a particular format as to create your own "custom fingerprint", which Play Integrity Fix(PIF) or Play Integrity Fork(PIFork) will then use & call upon to spoof your device to Play Integrity checks. There are scripts and tools that will do all of that last part automatedly for you; the scripts would output the blank file (pif.json) and you would just have to place it in the right root folder, but the tool would do all of it for you.

After, you just check with any of the 4 Play Integrity checkers to see if that custom fingerprint passes MEETS_DEVICE_INTEGRITY or not; if it doesn't, you move on, if it does, that fingerprint seemingly seems to hold for a long time -- longer than from repos & from pickaprint.sh, and definitely longer than Play Integrity Next(PINext)/xiaomi.eu fingerprints -- that those who have gone through this method have had theirs not banned for about a month now (mine I extracted Dec. 8).

So, that is the basics, and the above explanation is the most manual way to go about it; but there are 2 other methods where it isn't as manual -- Play Integrity Next (which essentially is PIF, but it downloads the fingerprint from the xiaomi.eu custom ROM internally & automatically without the need of updating the version of the module each and every time like PIF does) and TheFreeman193's Play Integrity Fix Script (PIFS)/pickaprint.sh which works in conjunction with a PIF/PIFork that will download and load a whole host of custom fingerprints to test.

So, if you're further interested in this, there's a comprehensive guide I wrote that completely goes into all the foundational info in a non-Android-technical fashion but that means it's rather an extensive writeup to put it in such a fashion. I can point you to it, if prompted here.

Hopefully that satisfies your prompt/inquiry and this helps.
[General Questions and Answers] airmark:
Thanks, I need to find some time to try these, ideally the not so manual method
[General Questions and Answers] simplepinoi177:
If you need a comprehensive (albeit non-concise) resource that goes through all the foundational info you would need to understand it all in the full basic sense (and even step by step instructions to getting you there, but manually), I could point you to one I had a hand in making....

just let me know...
[General Questions and Answers] OliverTwist559:
Hey, thank you for your explanations :)

I would be happy to read this comprehensive resource if it's possible :)

let me know how to do.

thanx, have a good day.

Olivier