[Discussion] Google Pay Magisk Discussion Thread

Search This thread

cridus

Senior Member
Apr 3, 2013
60
12
This sucks, tomorrow (in a few hours actually) I'll go on a trip and since two days ago google pay (or google wallet) started telling me that my phone doesn't meet security requirements... I'd really like being able to pay with the phone again...
google wallet, google play services, google play and (for what it's worth) google services framework are all in the denylist. my bank's app too.
I've updated magisk to the latest (stable) version, updated the universal safety-net fix to the latest ver and installed both shamiko and MagiskHide Props Config. I did disable "enforce denylist" after installing shamiko.
I've cleared all data from google play, google play services and google wallet and then rebooted.

nothing worked.

what else can I try?
 

zgfg

Senior Member
Oct 10, 2016
9,603
7,459
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11
This sucks, tomorrow (in a few hours actually) I'll go on a trip and since two days ago google pay (or google wallet) started telling me that my phone doesn't meet security requirements... I'd really like being able to pay with the phone again...
google wallet, google play services, google play and (for what it's worth) google services framework are all in the denylist. my bank's app too.
I've updated magisk to the latest (stable) version, updated the universal safety-net fix to the latest ver and installed both shamiko and MagiskHide Props Config. I did disable "enforce denylist" after installing shamiko.
I've cleared all data from google play, google play services and google wallet and then rebooted.

nothing worked.

what else can I try?
Have you updated USNF from this thread or the newer/better/modded version from another thread (please don't ask which thread - every second post is about, just scroll back, where, why, etc)
 
Last edited:
  • Like
Reactions: cridus

cridus

Senior Member
Apr 3, 2013
60
12
You have updated USNF from this thread or the newer/better/modded version from another thread (please don't ask which thread - every second post is about, just scroll back, where, why, etc)

I didn't know there were two different variants. I got it from kdrag0n's github. is there a new better one?
(I'll take a look in the meantime)

edit: it worked, omg thank you so much.

here's the thread with the other, working version of USNF, for convenience for anyone bumping into this post:

 
Last edited:
  • Like
Reactions: Alonzzo2 and zgfg

Sorensonn

Senior Member
Feb 22, 2009
92
7
My GooglePay stopped working today for no apparent reason. Bank app and other root-sensitive apps were working fine. I was using older Magisk version GPay SQLite Fix, MagiskHide Props Config and regular version of Universal Safety Net Fix.

Now I updated Magisk, turned off GPay SQLite Fix and MagiskHide Props Config, updated Universal SafetyNet Fix to version 2.4.0 mod 1.2, installed Shamiko 0.71 (blacklist enforcing turned off) and....

GPay still doesn't work (root or blahblah). SafetyNet check is OK, Google Play integrity is OK (device and basic integrity, strong integrity fails), I've purged google services cache - same. Bank app and other root sensitive apps work just fine. I removed and added again my debit card, but GPay still refuses to work.

Any ideas? Oneplus 7T Pro.
 

cridus

Senior Member
Apr 3, 2013
60
12
My GooglePay stopped working today for no apparent reason. Bank app and other root-sensitive apps were working fine. I was using older Magisk version GPay SQLite Fix, MagiskHide Props Config and regular version of Universal Safety Net Fix.

Now I updated Magisk, turned off GPay SQLite Fix and MagiskHide Props Config, updated Universal SafetyNet Fix to version 2.4.0 mod 1.2, installed Shamiko 0.71 (blacklist enforcing turned off) and....

GPay still doesn't work (root or blahblah). SafetyNet check is OK, Google Play integrity is OK (device and basic integrity, strong integrity fails), I've purged google services cache - same. Bank app and other root sensitive apps work just fine. I removed and added again my debit card, but GPay still refuses to work.

Any ideas? Oneplus 7T Pro.

my phone is a OnePlus 7 so if you do all that I did and it still doesn't work, it's pretty odd (I'd expect them to be pretty similar in that).
did you also add google play and google play services to the denylist? I'm not sure it's actually needed but I did that too.
 

wfred

Senior Member
Mar 15, 2014
167
48
Upstate, NY
My GooglePay stopped working today for no apparent reason. Bank app and other root-sensitive apps were working fine. I was using older Magisk version GPay SQLite Fix, MagiskHide Props Config and regular version of Universal Safety Net Fix.

Now I updated Magisk, turned off GPay SQLite Fix and MagiskHide Props Config, updated Universal SafetyNet Fix to version 2.4.0 mod 1.2, installed Shamiko 0.71 (blacklist enforcing turned off) and....

GPay still doesn't work (root or blahblah). SafetyNet check is OK, Google Play integrity is OK (device and basic integrity, strong integrity fails), I've purged google services cache - same. Bank app and other root sensitive apps work just fine. I removed and added again my debit card, but GPay still refuses to work.

Any ideas? Oneplus 7T Pro.
I also have a 7T. Try clearing the gpay and play cache & data. You have to reenter the cards, but it worked for me
 

malkovich78

New member
May 18, 2010
1
0
My GooglePay stopped working today for no apparent reason. Bank app and other root-sensitive apps were working fine. I was using older Magisk version GPay SQLite Fix, MagiskHide Props Config and regular version of Universal Safety Net Fix.

Now I updated Magisk, turned off GPay SQLite Fix and MagiskHide Props Config, updated Universal SafetyNet Fix to version 2.4.0 mod 1.2, installed Shamiko 0.71 (blacklist enforcing turned off) and....

GPay still doesn't work (root or blahblah). SafetyNet check is OK, Google Play integrity is OK (device and basic integrity, strong integrity fails), I've purged google services cache - same. Bank app and other root sensitive apps work just fine. I removed and added again my debit card, but GPay still refuses to work.

Any ideas? Oneplus 7T Pro.
The same happened to me on a Xiaomi device.
The solution which worked in my case was unistalling the official Magisk app and installing Magik Delta instead with SafetyNet Fix module version 2.4.0; no need to reinstall Wallet nor re-adding cards.

Regards.
 

Sorensonn

Senior Member
Feb 22, 2009
92
7
Thanks everybody, I will try that. Something must have happened to GPay (update or something?) because GPay stopped working on my wife's OnePlus 8 same day as mine.
 

TurboLed

Senior Member
Mar 2, 2012
158
70
Same for me, I was about to pay at a gas station on Friday and it failed when the day before everything was fine. When I clear the storage, Google Pay says the phone is compliant until I try to add a credit card. Will try updating to latest USNF. Pixel 3 XL with Shamiko...
 

Tester786

New member
Jun 4, 2023
1
0
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads.

Please use this to discuss issues with Google Pay and possible solutions.


There's a working solution here:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517


For general tips on first getting SafetyNet to pass fully, check here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
will google pay per hour or week?
 

kullurumanoj

Senior Member
Aug 10, 2014
59
22
Hyderabad
Hello All, Is anyone able to use nfc feature on cred or paytm? In paytm app it says the functionality isn't available due to security reasons. I'm using hml, I'm not a developer, lsposed and xprivacylua setup. Please help me in debugging the issue
 

tehdomic

Member
Oct 8, 2012
19
6
Is the failing MEETS_STRONG_INTEGRITY thing the reason why some Google Wallet payments don't work anymore?
Screenshot_2023-06-25-22-33-12-01_c164fb607f41c6d3a88bed2bf1a99c07.jpg
 

Zeti2000

Member
Aug 13, 2022
13
0
Screenshot_20230803-111358_Magisk Delta.png
When I installed Magisk (no matter wich version), the ”module” and ”superuser” are grayed out and I can click them. Also on settings I’m missing options (screenshot). Am I doing something wrong here? Or whats going on?
 

beeshyams

Senior Member
Dec 29, 2014
1,748
670
Bangalore
View attachment 5968861When I installed Magisk (no matter wich version), the ”module” and ”superuser” are grayed out and I can click them. Also on settings I’m missing options (screenshot). Am I doing something wrong here? Or whats going on?
Delete cache of Magisk module and reboot.. May need to repeat twice. For me, this happened with hide Magisk module, in which case also uninstall the hidden (Magisk with new name default being settings)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 63
    The new Google Play services update caused this.

    Temporary workaround:

    1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.

    2. Search "Google Play services" in the Settings search bar.

    3. Press the three dots and press "Uninstall previous updates".

    4. Download this update - https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-14-7-99-release/
    Pick your needed edition (arm or arm64, etc.), download it and install it.

    5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.

    6. Download Google Pay from the Play Store.

    7. Set up your cards. Enjoy!

    Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.

    Tested Google Pay versions:

    2.79.x-2.83.235070858 - working

    Tested Google Play services versions:

    14.7.99, 16.0.86 - working with Magisk 18.1

    14.8.49-16.x- working with Magisk 18.2 Canary
    33
    This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads.

    Please use this to discuss issues with Google Pay and possible solutions.


    There's a working solution here:
    https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517


    For general tips on first getting SafetyNet to pass fully, check here:
    https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
    29
    Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that Google pay does not register the "recent transactions" on the Google pay app. Another caveat is that I suspect users will have to reverse some step if gms is updated and then reapply, but this still needs to be confirmed

    Without further ado, here is my process:

    1) download a SQL database editor. I used

    https://play.google.com/store/apps/details?id=com.tomminosoftware.sqliteeditor&hl=en_US

    2) download a terminal emulator program. I used terminus but any terminal emulator should work.

    3) make sure Google pay is forced close, if it is open.

    4) open SQL editor. Navigate to /data/data/com.google.android.gms/databases

    5) open dg.db

    6) change any value that lists "attest" in the name (first column) to 0 in the third column. Mine was showing a value of 10 in the third column for each of these values. (Column c for sqlite databse editor I used)

    7) open the terminal emulator.

    8) get root access (su)

    9) cd /data/data/com.google.android.gms/databases

    10) type: chmod 440 dg.db
    This makes dg.db read only (for owner and group, and no access for world.)

    11) reboot

    I suspect when gms is updated, one will have to go back to steps 10 and 11 and chmod 660 dg.db to allow new keys to be written to the database, and then go back and redo all these steps to reset the attestation values back to 0.

    If there is still an error, verify in sqlite database editor that all attest release keys values in dg.db are 0 when dg.db is read only (owner and group).

    Again, YMMV but this worked for me, so I give it back to the community now.

    Edit: recent activities did show up soon afterwards for the payment method.

    Cheers,
    B.D.
    28
    The app is finally public! (thanks Google for taking a week to approve this 🤦)
    I made it beta testing since I haven't tested it on much devices. If you find any problem, please open an issue here and I'll take a look at them once I return from vacation.


    Source code:

    If you are curious, the possible outcomes I've seen are:
    • 3 ticks (unrooted samsung)
    • tick/tick/x (unrooted redmi note 4 with unlocked bootloader)
    • x/tick/x (my rooted a11 op7t)
    23
    UPDATE 1/8/2022
    This app is officially discontinued in favor of a new app I published on Play Store. Read more here:

    ====================
    ORIGINAL MESSAGE:

    I just made this simple app which tells you if your device passes the new Play Integrity API (which is presumably what Google Pay and Play Store use to detect root now). If you don't trust random apks from the internet feel free not to use this. I'll upload the source code at a later time since it's very junk now (probably on github).
    You can use it to play around and see if you manage to get it to pass without having to mess with Google Pay. There are screenshots of the 2 possible outputs (pass screenshot is from an online emulator).
    Also I didn't test it much since I don't have many devices that can pass. Hope it works fine 🤞

    Hope this helps someone find a solution :)

    EDIT:
    Here is a quote from Google of what exactly "Does not meet device integrity" mean:
    The app is running on a device that has signs of attack (such as API hooking) or system compromise (such as being rooted), or the app is not running on a physical device (such as an emulator that does not pass Google Play integrity checks).
    ...
    If you are having problems with your testing device meeting device integrity, make sure the factory ROM is installed (for example, by resetting the device) and that the bootloader is locked.