[Discussion] Google Pay Magisk Discussion Thread

Search This thread

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,299
1
14,823
Gone
Google Nexus 4
Nexus 6
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
 
Last edited by a moderator:

sisqoboy

Senior Member
Apr 28, 2012
333
25
Hoping solution is coming soon. :)
 

Attachments

  • Screenshot_2019-02-28-18-12-24-793_com.google.android.gms.jpg
    Screenshot_2019-02-28-18-12-24-793_com.google.android.gms.jpg
    72.5 KB · Views: 18,884
  • Like
Reactions: xdasp1986

gregwee

Senior Member
Jun 13, 2009
157
23
My GPay suddenly stopped working in the last few days. Didn't update/install anything, but possible GPay updated itself in the background.

Specs as follows:
OnePlus 6T, OOS9.0.7 rooted
Magisk v18.1, Magisk Manager v7.0.0(185)
Magisk hide: Google Seach, Google Pay, Google Play Store, Pokemon Go
Magisk Manager package hidden/repackaged

Any solution would be greatly appreciated..
 

alibob911

New member
Oct 16, 2016
3
2
Same on my OnePlus 6T.
Probably a coincidence, but the only thing I did between when it worked and when it stopped working was that I installed the Google Dialer Framework module, the Google Phone and Contacts app from apkmirror and then remove them.
 
Last edited:

JarlPenguin

Recognized Developer
Oct 16, 2018
1,021
946
Earth
github.com
Moto G5S
Moto G7
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
 
Last edited:

PuffDaddy_d

Senior Member
Aug 29, 2010
1,699
373
Houston, TX
Google Pixel 6 Pro
My GPay suddenly stopped working in the last few days. Didn't update/install anything, but possible GPay updated itself in the background.

Specs as follows:
OnePlus 6T, OOS9.0.7 rooted
Magisk v18.1, Magisk Manager v7.0.0(185)
Magisk hide: Google Seach, Google Pay, Google Play Store, Pokemon Go
Magisk Manager package hidden/repackaged

Any solution would be greatly appreciated..
Same here, pixel 3

---------- Post added at 05:45 PM ---------- Previous post was at 05:41 PM ----------

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 - working

14.8.49-15.0.10 - not working, downgrade to 14.7.99
Only downside to this is losing the cards and having to re-add them to Google Pay. It's not a big deal for credit cards, but I have a bunch of store loyalty cards that I added and threw away (or lost) the physical cards.
 

Matrixie

Senior Member
Jun 10, 2014
76
17
Thank you! This has been bugging me for ages now. Super frustrating to not have contactless working. And the fix was so simple! Cheers.
 

JarlPenguin

Recognized Developer
Oct 16, 2018
1,021
946
Earth
github.com
Moto G5S
Moto G7
Confirming that as a working solution. Thanks for that. Will disabling background data prevent Play Services from updating itself?
Yep, but check once in a while to see.

---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------

Same here, pixel 3

---------- Post added at 05:45 PM ---------- Previous post was at 05:41 PM ----------


Only downside to this is losing the cards and having to re-add them to Google Pay. It's not a big deal for credit cards, but I have a bunch of store loyalty cards that I added and threw away (or lost) the physical cards.
I haven't lost any of my loyalty cards. Did you reset your Google Play Services data by accident?
 

gozzaa

Senior Member
Nov 22, 2010
852
273
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 - working

14.8.49-15.0.10 - not working, downgrade to 14.7.99

I dont have an option to uninstall old updates from play services. Any idea?
there are no 3 dots on my screen :eek:
 
Last edited:
  • Like
Reactions: Tester786

Nothing4You

Member
Dec 18, 2013
23
5
Bonn
pixel 3 xl, stock rom, february security patch level, using latest magisk canary.
play store services 15.0.90 installed, uninstalling updates won't lower the version, downgrade doesn't seem to be possible.
 
Last edited:
  • Like
Reactions: Tester786

Eric214

Senior Member
Oct 24, 2012
1,651
549
Philly
Same here, pixel 3

---------- Post added at 05:45 PM ---------- Previous post was at 05:41 PM ----------


Only downside to this is losing the cards and having to re-add them to Google Pay. It's not a big deal for credit cards, but I have a bunch of store loyalty cards that I added and threw away (or lost) the physical cards.

I didn't have to do anything but the steps to downgrade play services. I just went back into the Google play app and trapped in my credit cards and added the security code and it added them just fine. No need to remove existing cards or the pay app and start from scratch.
 
  • Like
Reactions: PuffDaddy_d

jcmm11

Recognized Contributor
Feb 10, 2012
3,589
3,613
Google Pixel 4a 5G
pixel 3 xl, stock rom, february security patch level, using latest magisk canary.
play store services 15.0.90 installed, uninstalling updates won't lower the version, downgrade doesn't seem to be possible.
Interesting. I can confirm that it won't allow you to uninstall updates. The following should work (I have NOT tested this).

MAKE SURE YOU HAVE A BACKUP OF THE DATA PARTITION BEFORE STARTING!

Download the app from apk mirror. Turn on airplane mode.

In a terminal emulator, as root, run the following.

Code:
rm -rf /data/app/com.google.android.gms* /data/data/com.google.android.gms /data/user_de/0/com.google.android.gms

Reboot the phone
Install the downloaded apk
Turn off background data etc

Turn off airplane mode
Profit!
 
  • Like
Reactions: JarlPenguin

bot_rosco

Member
Jan 29, 2018
14
7
Does anyone know how to get around the issue where you get spammed with play services needs to be updated to use play services after the downgrade.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    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:

    1
    USNF v2.4.0

    I see a weird thing with GSF though, it keeps getting unticked . Any time I open the denylist, it's unticked, even though last time I definitely made sure both gapps and gservices sub-items were ticked
    Not weird. Mentioned here and elsewhere that USNF removes GFS from DenyList (it takes care by itself, and it has been that since the beginnings of USNF). You can find how it removes from the USNF scripts

    Btw, make sure to use the newer and modded safetynet-fix-v2.4.0-MOD_1.2.zip
    1
    Installing the modified USNF appears to have fixed it, Wallet is back in action, thanks!
    Not weird. Mentioned here and elsewhere that USNF removes GFS from DenyList (it takes care by itself, and it has been that since the beginnings of USNF). You can find how it removes from the USNF scripts

    Btw, make sure to use the newer and modded safetynet-fix-v2.4.0-MOD_1.2.zip
    1
    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)
    1
    Yep, the patched Universal SafetyNet fix solved the issue.
  • 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.