[Discussion] Google Pay Magisk Discussion Thread

Search This thread

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,303
1
14,761
Gothenburg
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/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
And a Magisk Module for it here:
https://forum.xda-developers.com/ap...7-1-22-pie-t3929950/post79643248#post79643248

For general tips on first getting SafetyNet to pass fully, check here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
 
Last edited:

sisqoboy

Senior Member
Apr 28, 2012
332
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,156
  • Like
Reactions: xdasp1986

gregwee

Senior Member
Jun 13, 2009
157
22
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
1
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:
  • Like
Reactions: bigmikey307

JarlPenguin

Recognized Developer
Oct 16, 2018
1,019
933
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:

Semtronix

Senior Member
Jul 10, 2013
182
130
Torrington, CT
Confirming that as a working solution. Thanks for that. Will disabling background data prevent Play Services from updating itself?
 

PuffDaddy_d

Senior Member
Aug 29, 2010
1,699
371
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.
 
  • Like
Reactions: Elia231100

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,019
933
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
272
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:

Nothing4You

Member
Dec 18, 2013
23
3
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:

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,587
3,603
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.
  • 3
    FYI, I had a problem - all of a sudden yesterday - with Google Pay on my OnePlus 9 Pro. Tried everything I could, even installing older versions of the apk, no luck for 3 hours. Google Pay kept showing something like "Checking for updates, this may take a few minutes".

    Finally, turns out it's the latest version of Google Play Services (I was naive enough to opt in the beta testing program).

    If you come across something like that, what worked for me was uninstalling Google Play Services updates, opting out of beta program, then re-applying the usual Google Pay process, and I was good to go.
    I too, was naive enough to opt in the beta testing program - and have since dropped it like it was hot.
    2
    Wish I was still there, we would've met for coffee and figured this out. I've learned that when it comes to stuff like this, 2 minds are always better than one.

    Maybe @pndwal can do that coffee thing if both of you are up for it 😄

    Its not pebkac......

    I catlogged it just now

    and theres several weird errors....

    my personal favourite is the line where it says zygote is sending signal 9 (which is SIGKILL = vewwy bad) to the process whenever the top up activity fires...

    theres no obvious "root detected" status in the entire log.

    and im not sure @pndwal wants to chance being seen with me...he knows why :)
    2
    FYI, I had a problem - all of a sudden yesterday - with Google Pay on my OnePlus 9 Pro. Tried everything I could, even installing older versions of the apk, no luck for 3 hours. Google Pay kept showing something like "Checking for updates, this may take a few minutes".

    Finally, turns out it's the latest version of Google Play Services (I was naive enough to opt in the beta testing program).

    If you come across something like that, what worked for me was uninstalling Google Play Services updates, opting out of beta program, then re-applying the usual Google Pay process, and I was good to go.
    2
    FYI, I had a problem - all of a sudden yesterday - with Google Pay on my OnePlus 9 Pro. Tried everything I could, even installing older versions of the apk, no luck for 3 hours. Google Pay kept showing something like "Checking for updates, this may take a few minutes".

    Finally, turns out it's the latest version of Google Play Services (I was naive enough to opt in the beta testing program).

    If you come across something like that, what worked for me was uninstalling Google Play Services updates, opting out of beta program, then re-applying the usual Google Pay process, and I was good to go.

    didnt even know there WAS a beta program for core google services...i wouldnt have been signing up for that :)

    thanks for the heads up and sharing the info for the benefit of others!

    fwiw its been a long while since a specific version of Google Pay itself caused any dramas...
    2
    Just tapped on Opal terminal w/ GPay this morning! - don't need to (probably can't as you say) add Opal to GPay but.

    I do have the card I associated with GPay added in Opal Travel app, so see trips both in 'Opal activity' and 'Contactless payment activity'... PW
    Yes, that's exactly what I used to do in Sydney. Having Myki on Google Pay is probably the alternative for not being able to tap-and-pay in Melbourne (or I could be wrong).

    Glad we have an electronic option regardless.
  • 61
    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
    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.
    27
    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/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
    And a Magisk Module for it here:
    https://forum.xda-developers.com/ap...7-1-22-pie-t3929950/post79643248#post79643248

    For general tips on first getting SafetyNet to pass fully, check here:
    https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
    18
    So here's the app to check fails_attestation value. The source code is available here. I may also implement a quick way to delete the gms data folder if you want.
    18
    All you really need to do to fix this is:
    1. Add Google Services to Magisk Hide (if you're on Magisk 18.1 use "su magiskhide --add com.google.android.gms" in terminal)
    2. Add Google Pay and Google Services Framework to Magisk Hide
    3. Go to data/data and rename com.google.android.gms to com.google.android.gms.bak for example (or delete it altogether, but backing up seems safer)

    Reboot and do whatever you like in GPay, it should work now. That's all I've done. I don't think you need to reinstall Magisk.