yashsingh1/xdaforums huggingface dataset:
[Magisk] tom510:
It started working for me despite not changing anything. Integrity device test started passing and after clearing cache+data from google play,play services and wallet its working again.
[Magisk] sanguinesaintly:
Same here. I'd cleared cache and data many times before with no result, but this time I cleared them , rebooted, and it added the card back it. Haven't tried it yet but looks promising. Maybe someone at Google had second thoughts !
[Magisk] Lughnasadh:
For what it's worth, even some non-rooted/bootloader locked users have been having some problems as of late. Maybe some growing pains on Google's part...

Some people aren't able to tap and pay with Google Wallet right now

Google Wallet is blocking some users from tap-to-pay and it's a mystery as to why

www.androidpolice.com
[Magisk] pndwal:
Yup... Thanks...

I suspected Google had been playing with PI deviceIntegrity at the server end... Seems they've also reverted something now also... I expect more fiddling / issues will arrise too...

Nb. The AP article, while no doubt an accurate reflection of user experiences, esp. issues had with un-modded devices, may be a little misleading...

Google has already deprecated S/N which is why they're migrating to PI already and are urging banks etc to do the same...

The article says "Google, however, has made plans to deprecate the SafetyNet Attestation API by 2024"...

Actually, Devs need to move to PI before a June 2023 'Migration deadline'...

The June 2024 date is simply the 'Full turndown' date when S/N API will fail for older app versions. These older apps will actually fail in June 2023 if Devs have failed to issue PI compliant versions (in addition) by this time...

https://developer.android.com/training/safetynet/deprecation-timeline

👀 PW
[Magisk] Lughnasadh:
Yeah, AP doesn't always get into the nitty gritty 🙃
[Magisk] wondakson:
Fixed now after clearing data and rebooting. Thanks Google, I guess
[Magisk] 73sydney:
Google Play Service data wipe:

Just a gentle reminder to any Watch 4/5 owners out there that a Google Play Services clearing will sever the Watch connection, requiring a Watch reset...so factor that into your equation folks

As always, for most things deficient on Watch, blame Samsung
[Magisk] batboy00:
Indeed, after doing absolutely nothing on my phone, the MEETS_DEVICE_INTEGRITY became green (since last Friday it was red) and now the Wallet does not complain any more. No data wipe, nothing. Google must have messed up with something.
[Magisk] jhavron:
Right! I hate when I'm the tool for the tool 👎
[Magisk] zagreous:
So similarly to others, last week integrity checker suddenly reported my phone no longer MEETS_DEVICE_INTEGRITY. As others have reported it went back to normal after a few days and I get two green checkmarks in PI checker. Since then I can't add my card to gpay. The setup goes well until the part where it normally prompts me to put in the code sent via SMS. The app tells me it can't add the card right now and to contact my bank. Customer support told me to wait and try again in 24 hrs, which didn't help. Has anyone else experienced this? And is it related to PI and/or magisk?
[Magisk] pndwal:
https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87400949

See this also; scroll down to Related Issues:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637

👍 PW
[Magisk] batboy00:
I have the same problem. Apparently, if the bank customer service informed me well, Google sends a sort of "recommendation" back to the bank when trying to add a card. Some banks take it into consideration, some don't. So maybe on devices that don't have a strong identity or something similar, Google can inform the bank about this detail. After that, it's the bank decision to allow the card to be added or not. From this point of view I don't think you can do anything. Or try to change your bank :)
[Magisk] pndwal:
Guess that's possible... Anyone blocked from their bank but still able to add cards for another w/ Contactless setup displaying 'Device meets security requirements'?

My experience (more than once) and that of several others has been that Contactless setup displayed 'Device does not mean security requirements' message even when deviceIntegrity verdict passed, and solution was simply to wipe Play Services data and either wipe G Pay/Wallet data and reboot or uninstall it, reboot and reinstall... PW
[Magisk] zagreous:
Gpay displays that I pass security and I've wiped data/uninstalled many times. It's probably as @batboy00 says and my bank just had enough of my messing around.
[Magisk] pndwal:
Mmm...

Bank should be able to tell you if something looks wrong at their end however...

In my case (first one) I persisted since I had also called my bank and was told everything was fine for contactless payments at their end... Had Contactless setup 'Your phone does not meet the security requirements' message that time, and uninstall, wipes and reboot was the cure...

With my latest episode, Wallet Contactless setup still said 'Your phone meets security requirements', but on trying to re-add cards I got 'You cannot use contactless on this device as it does NOT meet security requirements' as mentioned... However after simply clearing Wallet data and rebooting Wallet updated and cards re-appeared again...

I'm still skeptical your bank will have blacklisted your device; I suspect possible a bank glitch or a possible wait/delay after such a failure as your bank indicated... I'd be trying again...

However if you have deviceIntegrity passing and have fully uninstalled G Pay/Wallet, cleared Play Services, rebooted and set up Wallet again, I guess after giving it a bit more time you can only try setting up a different card/bank... 🙃 PW
[Magisk] 73sydney:
not saying its this, but just for sharing...

but back in my pixel days, about 3 years ago, when i was routinely testing (flashing) 2-4 ROM's a week, i did have a GPay failure that rendered contactless broken. Contacted bank...nope no issue there. Contacted Google via web...yup my account had gotten garbled by too many GPay setup requests from my bank :) Took them 24 hours to turn around on that one

aka when (too much) ROM flashing goes wrong

only time it wasnt something i could fix with a wipe
[Magisk] zagreous:
Well I went and made a new bank account added the new card to gpay and it works fine. Still can't set up the old card... seems like my device is on some sort of blacklist with the old bank.

P.S.: No idea if this is caused by magisk, root, Xposed or whatever so apologies if my original question doesn't belong in this forum.
[Magisk] 73sydney:
GPay Magisk Module Update:

As people seem to still be installing it, without reading the warning in my sig, in the thread, or in the README on my github repo, ive made the decision to remove the repo. As most long term people know ive been trying to wean people off it (including begging the world to "please let it die") for some time now, i myself havent used it in nearly 2 years.

I've explained (at length) previously why it has stopped being suitable here:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87231671

I had up till today kept it available for those rare few edge cases where against all odds it has seemed to be the only "fix" for a handful of people a year. I fear its now at a point where its truly a distraction and sending people off on a tangent that they neednt be on. This was prompted by an issue created on my github just now, and i decided it was high time it went...

So it is going bye byes....after somewhere north of 38,000 downloads (not counting forks and Androidacy stealing it and trying to monetize it)...

As always, thanks go to @BostonDan for his original method that led to my repurposing his hard work almost like it was my own, and to all the contributors over the years (@braveheartleo @Didgeridoohan (aka The Man) @Zackptg5 @Skittles9823 @jcmm11 @osm0sis), and for @pndwal who largely offered support for it almost singlehandedly for most of the time it was up....
[Magisk] okij:
Lol, when I read this in red letters, I initially thought that you pushed an update of your module which simply removes its functionality and leaves it as a placebo for those people who still think that they need it. 😂

But it's fine that you let it die and I really like the tombstone. 😇
[Magisk] 73sydney:
Considering people had been ignoring everything else i wrote about it for over a year now, including "you prolly dont need it" (and mods say i cant be subtle) which when that didnt stop them moved to "you shouldnt use it", i was half tempted to remove any functional code and leave it in place much as you thought, but then i thought of the sheer amount of work that would leave @pndwal when he'd inevitably have to respond (before i did, because he always beat me to it) to posts about "why isnt it working?". Despite him being a world class pedant and residing up a clock tower, i do have some sympathy towards him....hence i felt that no one could ignore the tombstone....
[Magisk] 73sydney:
Got a PM this morning:

Could You send me link to this fix? There is no file on GitHub anymore.

linked to above headstone post

And then this, which is where currently people should be looking for the correct method:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637

Update: i set the repo back to public, stripped of anything pretty much just the info in the announcement post above. Changed all remaining text to past tense to hopefully hammer it home.

Im most happy about the changelog :)
[Magisk] pndwal:
Murderer! PW

PS. Only in the past tense...
[Magisk] m0han:
Did he serve time (in the past ;))?
[Magisk] m0han:
There once was a module, a strange kind of module.....
[Magisk] shisaya24:
Hello, I tried the modded safetynetfix module by Displax (also one by HuskyDG) but Google Wallet doesnt let me add cards. Has anything changed? I would be really thankful if you could help me. I dont pass device integrity even after installing the modded module by Displax...
[Magisk] pndwal:
You'll definitely need to pass deviceIntegrity...

Without any information on your setup proffered I can't give you much more except to suggest disabling

all

modules apart from the @Displax modded USNF, reboot and test the PI verdict again... PW
[Magisk] shisaya24:
Which information on my setup do you need? :)

Android 13, LineageOS Unofficial port.

Redmi Note 11.

Magisk 25.2, denylist enabled and enforced only on wallet app as stated by you. Modded Safetynet Fix is installed...

Removing all modules except the modded safetynetcheck by Displax doesnt help, unfortunately. Device-Integrity isnt passed.
[Magisk] pndwal:
So deviceIntegrity is your issue... Could be ROM problem... Does SafetyNet pass?... Zygisk = Yes in Maagisk App home screen? PW
[Magisk] bigknowz:
Failing on strong integrity. Pixel 6 pro stock magisk 25.2 with displax mod. Contactless has been spotty last few weeks, Google must be playing with the server again.
[Magisk] zgfg:
Of course. Do you think you could cheat on Trusted Execution Environment?

Strong fails for all of us since Play Integrity API was introduced. And nobody makes a drama about👍
[Magisk] bigknowz:
So I should be able to make contactless payments? Thoughts appreciated.
[Magisk] zgfg:
Frankly, I don't know and don't care - I don't use it.

And there are always people who report problems while for others it works - hence the answer is never black or white, but the the shades of grey

Have you read anything of the discussion in this thread and some others?

For months it is discussed here how Play Integrity works, what is Trusted Execution Environment and why Strong Integrity cannot be fooled - and you will see many posts how people still happily use Wallet, etc
[Magisk] bigknowz:
Worked fine this morning

It worked fine this morning, not sure what changed.
[Magisk] pndwal:
Likely nothing changed... For now only deviceIntegrity is required...

Spasmodic loss of root or deviceIntegrity may trigger detection which is cached and can take days to clear unless apps data is cleared for instant fix... PW
[Magisk] shisaya24:
Yes sn passes and zygisk displays yes in home screen but no device integrity..
[Magisk] northsail:
You need to change the finger print
[Magisk] shisaya24:
Thanks for your advice but I already did that (despite the fact that most people say it's not necessary anymore with the modded safetynet fix). I tried like 7 different fingerprints from Google or Xiaomi with different Android versions.

... Do you know which fingerprint?
[Magisk] northsail:
I use normal safetynet with finger print (using a model that support android 12), i passed the device integrity without any problem. The only problem is google play updates, SIM and camera (using pixel phones), for example i installed pixel 6 pro fingerprint, google play try to update my camera app and sim app, i disabled automatic updates.
[Magisk] shisaya24:
Thing is, I tried normal safetynet + Pixel 6 Pro fingerprint and Google pay/wallet didn't let me add cards.
[Magisk] northsail:
is Integrity checker showed the two first fields in green?
[Magisk] shisaya24:
No, that's exactly my problem - the first check isn't green. Only the second.
[Magisk] pndwal:
You could try with official USNF and fingerprints in MHPC... Many find one Android version earlier works, or even just one or two ROM version print earlier...

Don't expect G Pay/Wallet to pass as soon as deviceIntegrity does... Deal with that after fixing deviceIntegrity...

I suspect however that your ROM may be spoofing a print to pass Safety net as well as integrating SafetyNet Fix to pass S/N w/o Magisk... Do you know if ROM can do this?

Nb. Official LOS will never integrate such spoofing / bypasses...

This may be interfering with Magisk USNF module and/or MHPC depending on dev implementation... In view of this you could check if ROM updates are available to address this or try official LOS if available w/ @Displax USNF modded module only...

🤠 PW
[Magisk] shisaya24:
Thanks - I will talk to the maintainer of the LOS version and see what we can figure out. I did however already try choosing a fingerprint of android 12, 11, 10 & 9 (I think I didn't go lower) with different devices tried for each version. None had an effect...
[Magisk] 73sydney:
the worst ive ever had to do was one version lower, in safetynet only days, so the generation of print isnt your issue
[Magisk] shisaya24:
Sorry but what is "generation of print"? And why is it not an issue? I can't follow 🙈
[Magisk] pndwal:
mmm... But that's for passing CTS Profile match...

In the case of deviceIntegrity we need to do both that and also have a somewhat elusive print mismatch to trigger bypassing of hardware attestation enforcement for PI (even though fallback to Basic evaluation type has already been achieved)

@Displax said we need different SDK level for some (especially custom) ROMs, but very recent, although mismatched, prints have worked for a number of devices... PW
[Magisk] northsail:
In my case;

Zygisk

Hide Magisk

Safety Net

and the first field is green.

For the second one, just change print.
[Magisk] shisaya24:
Which fingerprint is recommended for LineageOS 20 based on Android 13? Do you have any recommendations I could try...? Device integrity still not passing for me...
[Magisk] pndwal:
Really I've told you all I know... We need mismatched print where CTS Profile match passes but deviceIntegrity doesn't and some custom ROMs require different SDK (Android) level while others can work with a slightly older print...

Anyway, if you've had no success after many print changes I wouldn't mind betting it's a ROM issue as I indicated... Also, I've seen very few cases where @ Displax mod, which uses a very old Android 6 print targeting gms, fails...

Does dev have a discussion forum?... Is this build device specific or a GSI?... PW
[Magisk] shisaya24:
The dev has a Telegram group - it's a device specific build. Dev is very motivated and responsive and seemingly fixed the issue rom sided by integrating the play integrity fix into the ROM. Waiting for the link so I can try myself. Maybe it was really a conflict between the rom sided fixes and the modules
[Magisk] aNGERY:
I'm having an issue with my contactless payment not working. Vibrates like it wants to work, then doesn't.

I'm on a Oneplus 10 pro on A13. Any tips?
[Magisk] pndwal:
What passes?... PW
[Magisk] aNGERY:
I attached a few pics. The Google Pay icon says Google Pay, it shows wallet in info.
[Magisk] cescman:
I had the same problem before. You may try clearing data and cache of the app. If it still doesn't work, try installing an older version of Google pay and add some cards. If it works, you can update the app afterwards in the play store. I previously tried the January version of Google wallet when I got the error few months ago
[Magisk] aNGERY:
I rolled play services back and it started working. Hmmm
[Magisk] pndwal:
Doubt you needed to roll back, but should have cleared Google Play Services data as well as G Pay/Wallet... See this:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637

🙂 PW
[Magisk] aNGERY:
I appreciate it.

So I switched to displax's usnf mod, cleared the cache and data, uninstalled updates and it started working.

I'm still failing, and will probably continue to fail secure device.

If it happens again, I just need to clear the data then?
[Magisk] pndwal:
Do you mean strongIntegrity verdict here?

For now my guide is working... No guarantees for future use in this game! 😜 PW
[Magisk] Annil:
Google Wallet stopped working now and detects root, too.

A13 with P6P and used the guide from @pndwal using also mod 2.0 patch from displax.

Not sure what else I could do now or what's wrong. It just started with that free week ago after some Google apps for updated...
[Magisk] pndwal:
Mod 2.0 should be fixed again per

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87579273

(Bad DOS endings)

Nb. Latest includes new prop mismatch needed for A13 launch version devices... Older mod version should be fine for P6 etc.

Also, see this:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87481637

- Scroll to 'Related Issues'... PW
[Magisk] borisSweden:
OK I have an idea, lets say you have one unmodded stock phone with Google approved status and a rooted phone. Why cant I just ping the home phone when I tap the card terminal NFC tag with my rooted phone?

For some Gpay and Samsung Pay isn't a option because "reason" and you dont want to fork out for a Fitbit, Garmin or a S-Gear until GNU Taler is ready. Because this constant struggle with Gapps, Integrity, Safety Net, Hide, DenyList can't go on forever.
[Magisk] zgfg:
I don't understand how would you 'ping' the other phone

Wallet (or any other 'banking' app) calls SafetyNet, now PlayIntegrity API from the Google Play Services running on that SAME phone. And that PI API inspects again the SAME (own) phone

Only if you would spoof the complete Google Play Services (GMS) to make it to 'ping' the other phone, to execute there the Hardware type CTS Profile attestation, to returm the result, that your spoofed GMS would send then to Google server (as its own CTS Profile Attestation), for the final verdict

Not sure if that would be possible without the modifications on that other phone (sitting 'at your home'.

But in that case, those modifications on that other phone would also require the unlocked Bootloader (to flash the modifications), hence that phone would no more run its stock firmware with the locked Bootloader, meaning that it would also not be able to pass the Strong Integrity (Hardware type CTS Profile attestation, ie, on the Trusted Execution Environment=TEE). Hence you're back on the square one
[Magisk] borisSweden:
The unmodded phone will be on Android Pie which has the lax Android Pay requirements. Android enthusiast have several phones laying around and can find a use for them.
[Magisk] zgfg:
Fine. I have described the technical issues. Please be free to comment how would you solve/implement the details in question

Btw, that were only my comments (from the perspective how Google Play Services uses Play Integraty API for the attestation - in various threads here there were links to the official Google specification and comments from the users/'enthusiasts' from XDA)

Actually, I'm not interested specifically into the Wallet, and definitely, I can not participate in possible development, hence probably I will also not comment further here about.

There was another thread here on XDA about the game of mice and cat, with the similar ideas, wishes, and so
[Magisk] Zilla0617:
So going through the thread I'm having an issue with Google Wallet that i haven't seen discussed. For some odd reason, Google Wallet is disabled but GPay (old version) works fine. When i go to open Wallet from the playstore it looks like its going to open but then quickly opens GPay instead. On my app homescreen its list GPay, Wallet is not listed, but when go to settings to see all my apps it lists Google Wallet not GPay. The quick setting for Wallet is disabled as well as the options to show wallet on my lockscreen. My device is rooted Pixel 6 Pro on stock October rom on stable Magisk 25.2 and Im located in the US. Magisk 25.2 is hidden and I named it settings.

Prior to this occurring about a week ago or so, Wallet worked in fine. In fact I had no apps hidden just the Universal safetynet 2.3.2 module installed. Cards are stored and I can add more if I wanted. Now with the same setup. Wallet is disabled, but GPay works fine. No other apps complains that of my device is rooted. Integrity check passes for the 1st 2 options

Steps I tried to alleviate the issue:

Deleted and reinstalled Wallet only for it revert to GPay when opened

Wiped data and cache for Wallet

Wiped data and cache for Google plays services, framework, and Google play store

Hid Wallet

Hid Google playstore

Installed Safetynet fix-MOD 2.3.1

Rebooted numerous times

Google store shows my device is certified. Something is preventing my device from using Wallet and is downgrading me to GPay. I rather not factory reset my phone. Something else I noticed when wiping data and cache for play services and framework the new app icon design for messages appeared, totaling 2 (contacts and messages) with the new app icon design. My phone app icon still shows the old icon

Thanks in advance.
[Magisk] pp085ster:
Having a similar issue. Are you able to go into your Google settings page (Settings -> Google)? For me this does nothing. If I try to update the OS (Settings -> System -> System update), it also does nothing when I click on it. Basically a bunch of Google apps/services stop working for me. Can you confirm the same?

I reported my issue here too
[Magisk] Zilla0617:
No I do not have that issue. Updating to the November patched fixed my issue with wallet not being present. The quick setting feature is still disabled as well as the option to have wallet on the lock screen. Specifically, with your issue, do you happen to have any modules that changes system's font?