[Discussion] Google Pay Magisk Discussion Thread

Search This thread

73sydney

Senior Member
  • Like
Reactions: sdkyron

Zilla0617

Senior Member
I having problems activating google pay on rooted Pixel 6 pro. Tried clearing storage of cache of play services, play store, gpay. Adding Gpay sqlite fix, still encountering issues. On magisk canary 23014. Please help

EDIT: I figured it out.
 
Last edited:

jcmm11

Recognized Contributor
Feb 10, 2012
3,587
3,603
Google Pixel 4a 5G
I having problems activating google pay on rooted Pixel 6 pro. Tried clearing storage of cache of play services, play store, gpay. Adding Gpay sqlite fix, still encountering issues. On magisk canary 23014. Please help

EDIT: I figured it out.
A quick summary of what you figured out could be helpful to the next person to come along
 
  • Like
Reactions: Fry-kun and ZzEzZ

Eznaa

Member
Jun 7, 2021
16
5
Fairphone
ASUS ZenFone 8
Hi there, has situation changed recently ?
Can't get device to meet security requirement in google Pay app on my rooted Fairphone4. Although I have:

- Magisk hide: google play store, google pay, google services
- Hidden Magisk app
- Riru Module
- Universal SafetyNet Fix 2.1.2 for Riru
- GPay SQLLite Fix 2.4

I can pass SafetyNet test but that's about it.

Edit: it is now fixed, I must have messed up in the steps provided in the guide. Probably did not wipe all Google Play Service data after toggling plane mode or something? Anyway did it all over again and it ended up working.
 
Last edited:

Zebov

Senior Member
Feb 7, 2011
64
11
Google Pixel 6
Rooted Pixel 6 - I can't get anything but passing with basic attestation. Google play services is unchecked in the denylist after every reboot. I have GPay SQLite fix (and binaries) and the universal safetynet fix installed. Can't pass anything or add any card.
 
Rooted Pixel 6 - I can't get anything but passing with basic attestation. Google play services is unchecked in the denylist after every reboot. I have GPay SQLite fix (and binaries) and the universal safetynet fix installed. Can't pass anything or add any card.
Started happening to me last night and that's when I noticed that Google Play Services is unchecked at reboot on the DenyList.
 
You don't need any of this. If your device isnt certified in playstore use dragons safety net patcher.
To make gpay work. Hide magisk app in magisk settings hide magisk app rename it. Then enable magisk hide or denylist(if on zygisk) select all Google app and gms in hide or denylist. Reboot phone. Clear cache and data on playstore and all Google apps that may affect it if playstore alone doesn't work. Profit
 

raphytaffy

Senior Member
Apr 10, 2010
398
46
San Jose, CA
Pixel 4XL
Android 10
QQ3A.200805.001

Magisk 8b29267a (20426)
Manager d6dbab53 (301)

Everything was working fine ever since the last time I posted here (May 20, 2019). Not sure what has changed, but GPay is no longer working for me.

Attached screenshots show:
  • Google Play services and GPay hidden in Magisk Hide
  • MagiskHide Props Config installed
  • SafetyNey API Error failing both basicIntegrity and ctsProfile
  • Card showing Not Setup in GPay
I have
  • Confirmed that MagiskHide is working with Root Checker
  • Confirmed MagiskHide is still working after a reboot
  • Cleared Google Play Services cache
Can anyone help with any other tips that might get this working again?

Edit: it looks like it is working again. Not sure which step did the trick. I'm assuming something in the cache was stuck, but eventually cleared.
 

Attachments

  • Screenshot_20220117-213817.png
    Screenshot_20220117-213817.png
    247 KB · Views: 58
  • Screenshot_20220117-213846.png
    Screenshot_20220117-213846.png
    222.6 KB · Views: 61
  • Screenshot_20220117-213859.png
    Screenshot_20220117-213859.png
    85.6 KB · Views: 51
  • Screenshot_20220117-214754.png
    Screenshot_20220117-214754.png
    703.2 KB · Views: 64
Last edited:

Zotyoo

Member
Jul 11, 2015
24
5
Have you done/tried the following:

1) toggle magiskhide on

2) added com.google.android.gms.unstable to MagiskHide list (or Deny List in latest Magisk versions)

3) hide (rename) magisk app (from Settings menu)

4) Clear data of affected apps:
  • Toggle Airplane Mode on
  • Clear data and cache of:
    • Google Play
    • Google Play Services
    • Google Pay (Warning: this will remove any card and loyalty cards present - you can try without, but is recommended)
  • Usually this will be achieved by (exact steps and terminology may change per device or ROM):
    • Opening Settings
    • Going to Apps, choosing Show All Apps
    • Enabling Show System Apps via a menu option
    • Locating the app, tapping it and then finding Storage/Cache
    • Tapping Clear Data
  • Reboot and then Toggle Airplane Mode off
  • Open Google Play Store, wait 5 minutes, go to Settings and check Certification at bottom
5) Test Google Pay
I did everything based on the description. The unstable version was not found, but all google apps are turned on in the magisk hide menu. From November 2021, Google pay went smoothly. This year, my phone was discharged last week, after turning it on, everything seemed to be fine, but Google Pay listed a rooted phone. That allowed him to pay. Then I looked again at what the problem might be, and all the modules in Magisk were inactive, so Universal Safetynet fix, riru, and so on. I turned it on, rebooted it, and haven't used it since, but Pay was seemingly good, it didn't write a bug. I paid again but refused. The device does not go through the security system. Whatever Safetynet check gives the green light, play protect will not find a security issue. The card is visible in Google Pay, you can also import it to your smart phone, but the payment will not match when you check Google Pay. Samsung S10, Android 10, stock rom, Magisk. It was written that it would work after a hard reset, but I don't want to do that yet. Do you have any ideas what else can be done? Otherwise, there are two other banking applications above, both of which write the operating system as secure. It still worked for about 3 months. Airplane mode is there, I don't know what I forgot to delete. But he didn’t fail on a single check, now only Google Pay has a problem, which hasn’t been a problem so far. Thanks for the help!
 

73sydney

Senior Member
You don't need any of this. If your device isnt certified in playstore use dragons safety net patcher.
To make gpay work. Hide magisk app in magisk settings hide magisk app rename it. Then enable magisk hide or denylist(if on zygisk) select all Google app and gms in hide or denylist. Reboot phone. Clear cache and data on playstore and all Google apps that may affect it if playstore alone doesn't work. Profit

Absolutely DO NOT hide ALL Google apps...thats complete overkill, making magisk work harder than it needs to for NO benefit

Do NOT do that....
 
Absolutely DO NOT hide ALL Google apps...thats complete overkill, making magisk work harder than it needs to for NO benefit

Do NOT do that....
What is the point of a hide feature if it is so limited that you can't use it. Does not hurt anything and works fine.
Currently with new safety net patch from kdragon you don't need to mess with props and only need to hide play services playstore and gpay. I posted all bc before this other Google app would stop it from working and this was so it worked regardless for the people who don't know how to test for 3 hrs.
 

73sydney

Senior Member
What is the point of a hide feature if it is so limited that you can't use it. Does not hurt anything and works fine.
Currently with new safety net patch from kdragon you don't need to mess with props and only need to hide play services playstore and gpay. I posted all bc before this other Google app would stop it from working and this was so it worked regardless for the people who don't know how to test for 3 hrs.


It IS supposed to be a limited use function...youre completely misreading its purpose.
 

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.