[Discussion] Google Pay Magisk Discussion Thread

[Garbonzo17]

USNF has issues as you'll see here... So

... Don't put gms (Play Services) in denylist for ANY USNF builds. (Only needed for custom ROMs integrating @kdrag0n's SNF or their own solutions for S/N / PI)...

Please be specific what you mean by


... Are you getting the "Google Pay is Currently Updating..." Screen that never goes away? Other?... PW

No, but I got everything working again. And my fix isn't gonna jive with what I am seeing here (I don't believe).
I currently have also made the cardinal sin of changing MORE than one thing at the time... so I am NOT 100% why it works now...
1st (and probably NOT relevant) I have GPS (only com.google.android.gms nothing else) and Google Wallet on denylist. Set Enorce DenyList=off though, so I am even more confused that I was... (but this is how my OnePlus 6t is set, so I did same)
2nd I switched from Displax v2.1 mod back to 2.0 (I think I was originally using that from when I did the whole Tmo conversion of this phone back in December...
3rd I went through the process of uninstalling wallet (actually disabled again in addition to uninstalling updates), dumping updates for play store/services and storage/cache, rebooted, and cards added fine without the red circles telling me contactless no good cuz I suck!

So, it is probably #2 or #3 (I feel like probably the steps in #3), and I really have to (and hate) to move on with my day, this has eaten enough, but I feel like I understand marginally more than I did.. and it was your posts both in this thread and others that you linked to that got me to the goal (even if it may be temp, considering I don't know what blew it up a few days ago, but from what I am reading I am certainly not the only one having these issues... and guys like you doing the lords work in making stuff work for those of us that like to tinker...

THANKS (to everyone, really) for this community.
-G

 

[pndwal]

No, but I got everything working again...
I currently have also made the cardinal sin of changing MORE than one thing at the time... so I am NOT 100% why it works now...
1st (and probably NOT relevant) I have GPS (only com.google.android.gms nothing else)

Play Services is generally referred to as gms, not GPS...

But gms in denylist with USNF?... Why? ... USNF will hide that itself as denylist prevents zygisk modifications in gms... If denylist is not enforced and proper hiding modules source denylist for convenience there is usually no conflict, but both Shamiko (or other) and USNF will be competing to hide root from attestation/droidguard (com.google.android.gms.unstable) and/or main (com.google.android.gms) process...

and Google Wallet on denylist. Set Enorce DenyList=off though, so I am even more confused that I was...

Zy-USNF works w/o denylist enforced as it does its own process hiding (unlike Riru-USNF which used MagiskHide's hidelist) since denylist breaks modifications in 'denied' processes... It's denying Magisk modifications...

Long explanation: Denylist can hide root from gms, but then the primary fix, which uses Zygisk to inject code into gms to register the fake keystore that produces the exception which causes our fallback to basic attestation will be broken!!! (... because denylist prevents zygisk modifications in processes as mentioned above.)

... but from what I am reading I am certainly not the only one having these issues...

No... Stay on any of @Displax's modded builds for now... PW

 

[wfred]

Are you getting the "Google Pay is Currently Updating..." Screen that never goes away

Yeah, I am.
Cleared play & wallet cache & data, downgraded from 2.4 to 2.3.1 v2.1
Now it's stuck on Google Pay updating.
How long does it usually take for that to clear?

 

[pndwal]

... and now still having no luck with getting wallet/pay to work...

... Are you getting the "Google Pay is Currently Updating..." Screen that never goes away? Other?... PW

Yeah, I am.
Cleared play & wallet cache & data, downgraded from 2.4 to 2.3.1 v2.1
Now it's stuck on Google Pay updating.
How long does it usually take for that to clear?

Nice interception of that ball!

Answered here:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88092445

Hope it helps...

PW

 

[Fun_GKC]

Suddenly can't use Google Pay today. Anyone has the same issue?

 

[Fun_GKC]

Suddenly can't use Google Pay today. Anyone has the same issue
nvm. Just read the last page.

 

[Rokcy98]

Suddenly can't use Google Pay today. Anyone has the same issue?

I have your same problem, did you solve this?

 

[bombadier]

I have just had a strange experience, wallet was working fine on Thursday, went to pay for a takeaway tonight and wallet payment was rejected with the message your phone doesn't meet security requirements, checked play integrity API checker and my device was failing meets_device_integrity, my banking app is still working, read some of these comments and downgraded from USNF 2.4.0 official to USNF 2.3.1_2.1 MOD by Displax and rebooted my phone, after rebooting I passed meets_device_integrity, still had the error in wallet so wiped cache and reloaded the app, error message is gone, will see if wallet works tomorrow at the shops but not sure what the issue was other as 2.4.0 just randomly stopped working

Update not tried to use wallet yet but am still getting the error when opening the app, have deleted my bank card and added it again which was successful, just need to test making a payment

Update Google wallet seems to be working just made a payment

 

[Garbonzo17]

I have just had a strange experience, wallet was working fine on Thursday, went to pay for a takeaway tonight and wallet payment was rejected with the message your phone doesn't meet security requirements, checked play integrity API checker and my device was failing meets_device_integrity, my banking app is still working, read some of these comments and downgraded from USNF 2.4.0 official to USNF 2.3.1_2.1 MOD by Displax and rebooted my phone, after rebooting I passed meets_device_integrity, still had the error in wallet so wiped cache and reloaded the app, error message is gone, will see if wallet works tomorrow at the shops but not sure what the issue was other as 2.4.0 just randomly stopped working

Update not tried to use wallet yet but am still getting the error when opening the app, have deleted my bank card and added it again which was successfull, just need to test making a payment

If you re-added the cards and it seems normal when you attempt a (dry) purchase, you should be good to go. (I was in your situation earlier in the week, and have been using everything fine for the last 3 days or so)
I am still unclear as to what caused working installs (using USNF2.4.0 official) to just stop working...
But as long as people better with these things than are working on this situation (and USNF2.3x/displax holds) I feel pretty good about things!
Thanks again to @pndwal and others for taking the time to explain things slowly enough for non-coders to follow.

-g

 

[cmstlist]

Just wanted to report on Pixel 6a this seems to have worked?

I removed 2.4.0, added the above mod, then before any reboots I did a force-close + cache clear on Play Store, Wallet and Play Services. Did not wipe data of any. Then reboot. On first open of Wallet app it still complained. But then after quitting and reopening the app, no further complaints.

EDIT: Yes it worked. The error appeared when I tried to make a payment at a cafe this morning. After doing the above I went grocery shopping and was able to pay again.

Follow up: this weekend I've been often getting the message about my device not meeting security requirements, when opening Wallet app. It's especially prone to happen when I launch it from the Wallet quick settings tile. But after getting the message, the contactless symbol is not crossed out, and payments still work

Clearly there's something going on that could use another fix.

 

[pndwal]

Follow up: this weekend I've been often getting the message about my device not meeting security requirements, when opening Wallet app. It's especially prone to happen when I launch it from the Wallet quick settings tile. But after getting the message, the contactless symbol is not crossed out, and payments still work

Clearly there's something going on that could use another fix.

Are you using a custom ROM? If so, which? PW

 

[cmstlist]

Are you using a custom ROM? If so, which? PW

No, stock Pixel 6a on latest Android 13, latest Magisk. Universal SafetyNet Fix V2.3.1-MOD_2.1 by kdragon, modded by Displax

 

[pndwal]

No, stock Pixel 6a on latest Android 13, latest Magisk. Universal SafetyNet Fix V2.3.1-MOD_2.1 by kdragon, modded by Displax

mmm... Then it may have just been a glitch... I've seen this inexplicably before also...

You could try earlier @Displax mod builds that don't build Hide "Enable OEM Unlock" setting... @kdrag0n was concerned that this might cause per-device breakages and @Displax has agreed that it shouldn't be merged in official USNF, although it caused no problems for me (Xiaomi RN8T)...

Summary: You need neither:

Updated 2.1:
Hide "Enable OEM Unlock" setting

nor:

Updated 2.0:
Bypassing DEVICE_INTEGRITY for devices that shipped with Android 13+ (Pixel`s 7 )

but you do need:

Updated:
Drop fingerprint to lowest possible (6.0) to ensure that no one use same Android version

... PW

 

[cmstlist]

mmm... Then it may have just been a glitch... I've seen this inexplicably before also...

You could try earlier @Displax mod builds that don't build Hide "Enable OEM Unlock" setting... @kdrag0n was concerned that this might cause per-device breakages and @Displax has agreed that it shouldn't be merged in official USNF, although it caused no problems for me (Xiaomi RN8T)...

Summary: You need neither:

nor:

but you do need:

... PW

Sure I'll try the older mod. On first reboot no complaint from Wallet, Safetynet still passes. Will see if it stays consistent.

 

[cmstlist]

mmm... Then it may have just been a glitch... I've seen this inexplicably before also...

You could try earlier @Displax mod builds that don't build Hide "Enable OEM Unlock" setting... @kdrag0n was concerned that this might cause per-device breakages and @Displax has agreed that it shouldn't be merged in official USNF, although it caused no problems for me (Xiaomi RN8T)...

Summary: You need neither:

nor:

but you do need:

... PW

Update: No I'm having the same experience as before. Open Wallet and get the warning, but then it seems to work anyway.

 

[pndwal]

Update: No I'm having the same experience as before. Open Wallet and get the warning, but then it seems to work anyway.

mmm... Just checked mine and strangely enough I can now confirm you are not alone:

... I've just cleared Google Play services data and tried opening Wallet but it's icon was removed from app drawer in lauuncher... Opened Play Store and wallet is still there:

But after opening from here:

... This isn't completing... Again...

Will get back to this later... PW

 

[cmstlist]

mmm... Just checked mine and strangely enough I can now confirm you are not alone:
View attachment 5828739
... I've just cleared Google Play services data and tried opening Wallet but it's icon was removed from app drawer in lauuncher... Opened Play Store and wallet is still there:
View attachment 5828747
But after opening from here:
View attachment 5828749
... This isn't completing... Again...

Will get back to this later... PW

Interesting, that's MORE non functional than mine
For me it's just sporadic and no failed payments so far. Except for last weekend when I was still on USNF 2.4.0. It seems like there are different conflicting sources of checks going on and having some kind of race condition. Sometimes the successful check wins, sometimes the unsuccessful wins. On my device the unsuccessful check lives just long enough to give me an error, then the successful check appears to take over

 

[bombadier]

Interesting, that's MORE non functional than mine
For me it's just sporadic and no failed payments so far. Except for last weekend when I was still on USNF 2.4.0. It seems like there are different conflicting sources of checks going on and having some kind of race condition. Sometimes the successful check wins, sometimes the unsuccessful wins. On my device the unsuccessful check lives just long enough to give me an error, then the successful check appears to take over

After my spot of bother yesterday since going back to Displax's version of USNF (That fixed the failed meets_device_integrity), I was still getting the error message after wiping wallet's cache, since deleting payment method and adding my card I have had no further error messages in wallet and can make payments

 

[cmstlist]

After my spot of bother yesterday since going back to Displax's version of USNF (That fixed the failed meets_device_integrity), I was still getting the error message after wiping wallet's cache, since deleting payment method and adding my card I have had no further error messages in wallet and can make payments

Good to know, but it seems all the anecdotes here are along the lines of "Aha! I did X and that fixed it... [insert 1-7 days] nope that didn't fix it"
So I think there will have to be some new fix/patch developed to deal with a new behaviour.

I'm taking this phone on vacation in 2 weeks for a 5-week vacation to mostly Australia. If Pay fails, no sweat, I can still use the physical cards in my wallet. But two things I might hesitate with:
- Using Pay for contactless entry to the Sydney transit system. If it succeeds on the way in and fails on the way out, I'm stuck and might have to pay a fine. (It treats the phone as a different device than the physical card.) Plus if I use the same card regularly it applies fare-capping daily and weekly, and that won't work right if I start via Pay and have to switch midway to the physical card.
- Using the mobile Myki feature in Melbourne via Wallet instead of a physical card. If I load money onto mobile Myki and then Wallet fails on me, the money becomes inaccessible. Plus if I wipe GP Services it destroys the transit card and the money is not retrievable.

 

[pershoot]

Please note, Wallet started complaining (as is the case with others) when on 2.4.0 (kdrag0n). Rolled back to 2.3.1_mod_2.1 (Displax), cleared cache for Wallet (for precaution) and then updated Google Play system. After ~+24 hours, it has dropped off and no more apparent error messages (as of yet).