[Discussion] Google Pay Magisk Discussion Thread

Search This thread

73sydney

Senior Member
Use zygisk it's no so limited in the way it works, and you really didn't read why I told them to. xxxxxxx
Mod Edit: Post edited.
im merely clearing up some disinformation, which youre spreading...its also misinformation others have tried to stop being spread many times in the past, whenever they see it

ive mentioned twice now that the magisk dev will tell you exactly the same thing, only enable hiding on a very granular level.

and theres this:

Make sure that the app in question is selected in the Hide list (Under MagiskHide in the Magisk app). But, don't go crazy... Only add those apps that actually detect root. If you add too many unnecessary apps and processes you will very likely experience system instabilities (also see "System instabilities")

from: https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

for instance, have a look at my Google Pay Magisk Module, the script only hides whats absolutely necessary. Its been downloaded 35,000 times...which should tell you that the very limited hiding it does, works...

com.google.android.gsf_com.google.process.gapps
com.google.android.gsf_com.google.process.gservices
com.google.android.gms
com.google.android.apps.walletnfcrel'

thats 4 packages

and for newer zygisk denylist...3

com.google.android.gsf_com.google.process.gapps
com.google.android.gsf_com.google.process.gservices
com.google.android.apps.walletnfcrel

As said many times almost every issue with Google Pay not working has been resolved by making sure SafetyNet passes, and clearing the data of Google Play Store, Google Play Services and Google Pay....not by adding every Google app to MagiskHide/Deny List

xxxxxxxxxx
Mod Edit: Post edited.
 
Last edited by a moderator:

ahb83

Senior Member
Nov 21, 2010
148
9
When I try to configure the deny list and check Google Play Services, it doesn't stay checked after a reboot. I cannot pass sn because of this. Anyone know why it won't stay checked after a reboot?
 

pndwal

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.
Well it can... 😬

Its use should definitely be limited in traditional Magisk as hiding more than a few apps / processes makes the system unstable due to restrictions on the hide daemon's passive reaction speed (to app processes). Also Webview and more are broken by indiscriminate hiding of Chrome and other Google apps / processes... Nb
- www.twitter.com/topjohnwu/status/1039528958289760256

Also, John did much debugging w/ early MagiakHide just to make it useable (see 'More on timing issues here also' link and John's general rule from here:
- https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84868359

Nb. The hiding elements retained by denyist may well have changed, ie hijacking app_process (Zygote) rather than simply monitoring these passively may now be used / possible with Zygisk and be faster / not face this restriction any longer. However I haven't checked code for this nor am I aware of comments by John about changes to the mechanism used here. Someone may know more...
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.
Just to qualify this, those using stock or custom ROMs that spoof certified (use a certified fingerprint matched to security patch date) won't need MHPC, but many custom ROM users, eg all official LineageOS (except where fingerprint / patch dates match before any update that bumps up security level) users, as well as those with uncertified stock ROMs (China region etc) will need to spoof certified by using a working fingerprint. 👀 PW
 
Last edited:
  • Like
Reactions: Lord Sithek

pndwal

Senior Member
When I try to configure the deny list and check Google Play Services, it doesn't stay checked after a reboot. I cannot pass sn because of this. Anyone know why it won't stay checked after a reboot?
Yup, @kdrag0n's Zygisk solutions remove these from denylist as USNF hides these itself so as to better target Play Services only... explanation in USNF GitHub...

Your failing S/N has a different explanation...

Nb. to pass with MagiskHide we need SafetyNet process, com.google.android.gms.unstable in hidelist where Magisk is in /sbin. For Android 11+ etc (assuming Magisk is not in /sbin), main process, com.google.android.gms needs adding also. However, MagiskHide adds these automatically when toggling ON...

Nb. 2 Only these processes need to be / should be hidden to pass Safety net... 🙃 PW
 
Last edited:
  • Like
Reactions: Graddy01
Has anyone lost the Google Pay cards from the power menu? I updated Magisk when prompted (I don't know why, everything worked fine) and then of course my cards were all not able to be used for contactless payment.
I've enabled zygote, hidden gms and banking etc, added safetynet and props hide, cleared cache and data from play, pay, services, ran the latest gpay and added my cards successfully.
Everything appears good, Play Store says certified etc but for the life of me the option to enable cards on the power menu is gone and i'm not sure if i've done something whacky. Any ideas or suggestions greatly welcome!
Pixel 2 XL on last build/security patch running Magisk version whatever came out yesterday.
Thanks!
 
Has anyone lost the Google Pay cards from the power menu? I updated Magisk when prompted (I don't know why, everything worked fine) and then of course my cards were all not able to be used for contactless payment.
I've enabled zygote, hidden gms and banking etc, added safetynet and props hide, cleared cache and data from play, pay, services, ran the latest gpay and added my cards successfully.
Everything appears good, Play Store says certified etc but for the life of me the option to enable cards on the power menu is gone and i'm not sure if i've done something whacky. Any ideas or suggestions greatly welcome!
Pixel 2 XL on last build/security patch running Magisk version whatever came out yesterday.
Thanks!
I could delete the post but in case someone else finds it useful... My cards are back on the power menu after leaving it for a few hours.
Clearing the Pay data didn't do anything at the time but now it looks like all my cards have gone bar the primary one I actually removed and added during the gpay sqlite module installation. I've added the second card and afterpay with no issues.

Not sure what the winning combo is, after spending about 2 hours removing and rebooting things multiple times. Thanks @73sydney for the module maintenance!
 

DocMAX

Senior Member
Nov 22, 2006
684
29
While we need to delete Google Services Data sometimes, to make Pay work, is there a way to backup all credit cards and restore them? (titanium backup?)
 

nightmare1942

Member
Nov 29, 2009
29
7
Hi guys and gals,

after reading many infos here I got everything to work for me.
I needed these settings for the following apps:

  • Google Pay (GPay)
  • Pokemon Go
  • comdirect photoTAN app

What I did was the following:

  1. Updated to magisk 24.1
    • Needed a deinstall and reinstall
    • modules already installed were Busybox, MagiskHide Props Config, Smali Patcher
  2. Installed Universal SafetyNet Fix for Zygisk by kdrag0n
  3. Enabled Zygisk
  4. Rebooted
  5. Enforced DenyList
  6. Added the three apps above to the DenyList (just left everything checked by default, didn't enable anything else)
  7. Deleted all data (not only cache) from the apps above, Google Play Services and Google Play Store
  8. Reconfigured all three apps and it seems to work fine (haven't yet testet GPay in RL, but looks good)

I hope this will help to understand what needs to be done at least.

I have a Galaxy S9+ with CustomROM on Android 12.
 
  • Like
Reactions: J.PG

renanrdrigues

Member
Jan 1, 2022
11
0
Hi guys and gals,

after reading many infos here I got everything to work for me.
I needed these settings for the following apps:

  • Google Pay (GPay)
  • Pokemon Go
  • comdirect photoTAN app

What I did was the following:

  1. Updated to magisk 24.1
    • Needed a deinstall and reinstall
    • modules already installed were Busybox, MagiskHide Props Config, Smali Patcher
  2. Installed Universal SafetyNet Fix for Zygisk by kdrag0n
  3. Enabled Zygisk
  4. Rebooted
  5. Enforced DenyList
  6. Added the three apps above to the DenyList (just left everything checked by default, didn't enable anything else)
  7. Deleted all data (not only cache) from the apps above, Google Play Services and Google Play Store
  8. Reconfigured all three apps and it seems to work fine (haven't yet testet GPay in RL, but looks good)

I hope this will help to understand what needs to be done at least.

I have a Galaxy S9+ with CustomROM on Android 12.

Nice !!! worked for me on lineage 18.1 - S7 Edge
 
Last edited:

Gogikz

New member
Dec 8, 2021
3
1
Hi boys and girls,
I can't set Up a google pay.Safety chek pass as well but stil can't set up my card.Magisk v.24.3 on redmi note 9 pro.The problem came after software update
Screenshot_2022-03-10-12-01-02-686_org.freeandroidtools.safetynettest.jpg
 

Attachments

  • Screenshot_2022-03-10-11-02-17-255_ltxtteme.ryjl.bqra.jpg
    Screenshot_2022-03-10-11-02-17-255_ltxtteme.ryjl.bqra.jpg
    315.2 KB · Views: 80
Last edited:

73sydney

Senior Member
Hi boys and girls,
I can't set Up a google pay.Safety chek pass as well but stil can't set up my card.Magisk v.24.3 on redmi note 9 pro.The problem came after software updateView attachment 5557267

Can somebody help to solv this problem


1) Theres a section of my modules post here: https://forum.xda-developers.com/t/...s-of-gms-17-1-22-on-pie.3929950/post-79643248

titled "Clear Play Store & Play Store Services Data & Check Play Store Certification"

which suggests:

Clear Play Store & Play Store Services Data & Check Play Store Certification
  • Toggle Airplane Mode on
  • Clear data and cache of:
    • Google Play
    • Google Play Services
    • Google Pay (note: may/will remove any cards previously entered)
  • 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
  • Toggle Airplane Mode off
  • Open Google Play Store, wait 5 minutes, go to Settings and check Certification at bottom, it may take some time for "Certified" to appear, but as long as its not "Not Certified", and just showing version info, you are good to go

an awful lot, in fact most, GPay issues are resolved merely by doing what this section says...

2) Disable DNSCrypt-Proxy temporarily (and reboot) - i dunno what if any blocklist youre using, but theres a chance that a blocklist entry may be interfering.

Beyond this, i have no idea, you mention a software update...so you may wish to check with other sin your devices threads to see if anyone else is having issues
 
  • Like
Reactions: rodken

Gogikz

New member
Dec 8, 2021
3
1
Thanks I had try this but I miss one step.After I read your post and did everyting step by stem my problem is solved.Thanks a lot
 
  • Like
Reactions: 73sydney

varunpilankar

Senior Member
Jul 8, 2012
200
51
Sony Xperia SP
Moto X
I'm using rooted android 10 with Safetynet Pass & Play Store -Certified, but I'm still not able to activate tap to pay on Paytm app.


It's gives me a error - "This functionality is not available due to security concerns with your device."

How can I fix it?
 

73sydney

Senior Member
I'm using rooted android 10 with Safetynet Pass & Play Store -Certified, but I'm still not able to activate tap to pay on Paytm app.


It's gives me a error - "This functionality is not available due to security concerns with your device."

How can I fix it?

Things to try?

1) Make sure you do not have a visible TWRP folder on internal memory - if you do and have a backup in there, rename the folder until you need it, or alternately move it off device

2) Make sure you are using the most up to date Magisk your device supports, and set MagiskHide or Zygisk (dependent on Magisk version) and relevant apps set to hide (do not hide all apps like an insane person). Consider installing Shamiko if using current Magisk 24.x with Zygisk

All details here: https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/

3) Make sure you do not have any of the known apps/modules that are known to cause issues, this include "tweak" apps/scripts like FDE.AI or (badly configured) EdXposed (on older Magisk) - which are noted here: https://forum.xda-developers.com/t/...s-of-gms-17-1-22-on-pie.3929950/post-79643248

4) If you have any magisk modules installed, try toggling them off and retrying (you;d be surprised what will give up root, something as benign as a font module will betray you)

5) And despite having a SafetyNet pass and certification in Google Play, and perhaps after 4) above, i would still give the standard troubleshooting steps of clearing data as in the three posts above this one ↑ a go....

6) Consider running RootBeer to see what may be triggering root detection, if at all

As always, i prolly try these things in this order for a possible "quick fix":

1, 5 and 6 - 5 has solved an awful lot of issues by itself...

And sometimes it will just resolve itself after a few days...GPay is sometimes a weird beast....
 
Last edited:
  • Like
Reactions: Dante63

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Haven't had much time to dig further into issue... Suspect it's an issue with late Canary, but haven't tested... PW
    Still not sure what caused this glitch (likely SafetyNet failure during Magisk setup).

    Anyway, I found in Google Pay, Contactless setup
    IMG_20220604_135028.jpg


    the Last item said 'Your phone does not meet the security requirements'.

    Clearing Google Pay data wouldn't fix.

    I am scared to clear data for the several components that appear in applist w/ 'security' as keyword... So next I cleared Google Play Services and Google Play Store data, but now Google Play wouldn't even open, just this (unending):
    IMG_20220604_133229.jpg

    Strangely, clearing Google Pay data again had no effect either...

    Next, I simply uninstalled Google Pay completely, then reinstalled it from Play Store, and now get 'Your phone meets he security requirements' as shown above. Also:
    IMG_20220604_134358.jpg

    so seems I'm good to go again! 😛

    I don't know if version changed, but I assume I had latest version before as I auto-update... Some things are a mystery, but Uninstalling and reinstalling did the trick for me where clearing data wouldn't...

    For others facing this, clearly you'll need to fix any SafetyNet issues first...

    Hope this might alay some anguish. 😜 PW
    3
    Confuzzled, do you mean the usual

    * Airplane mode on
    * Wipe data of Play Services, Play Store and Google Pay
    * Reboot
    * Airplane mode off

    didnt work...you had to fully uninstall pay as well?
    Didn't do Aeroplane (are you American 😛) mode thing (seldom do), just the wipes and reboot suggested as stated...

    Did work!; by 'did this', I mean I did exactly what rodken prescribed (no need nor mention of full uninstalling G Pay again!) 'and it did the trick' for me. 👍

    By 'I think the reboot made the difference', I mean my original fix, while allowing Contactless payment to work, was flawed...

    If I had also rebooted after wiping G Pay app data, I believe I would have both fixed Contactless Payment setup (security requirement) issue, 'Google Pay is currently updating' would have completed and I should have avoided broken Activity list...

    In short, if you get
    IMG_20220604_110358.jpg

    and see 'Your phone does not meet the security requirements' in Contactless setup, clearing Google Pay app data won't fix it.

    Fix by
    1) Clearing Google Play Services and Google Play Store data.*
    (but now

    IMG_20220604_133229.jpg

    won't complete...)
    *Clearing Play Store data may (likely) not be required.
    2) Clear Google Pay app data and reboot. (I'm not 100% sure full uninstall / reinstall of G Pay app, which I did, is not necessary here, but I now suspect it isn't).

    Now 'Google Pay is currently updating' should complete and you should get
    IMG_20220604_134358.jpg

    and, after payments
    IMG_20220607_162612.jpg

    👍

    ...If you're still getting
    IMG_20220607_163018.jpg

    for Oreo Double Stuffed Cinnamon Bun bikkies in some vain attempt to scroll back to the 80's & 90's, you really need to re-evaluate your whole approach, get 'with it' (suggest biting ends off TimTams and sucking rum / brandy into them at least) and maybe chuck out that Royal Doulton tea set and the Queen Anne furniture... And why the hankering for American Kraft/Heinz Nabisco Coffee anyway? ... No wonder your spellings all up the shoot!
    😁 PW
    2
    (but now

    View attachment 5632207
    won't complete...)
    *Clearing Play Store data may (likely) not be required.
    2) Clear Google Pay app data and reboot. (I'm not 100% sure full uninstall / reinstall of G Pay app, which I did, is not necessary here, but I now suspect it isn't).

    Now 'Google Pay is currently updating' should complete and you should get
    View attachment 5632235
    I'm in the same predicament as you were - I cleared Google Pay data, rebooted, and when I started it again, it asked me for the Google account and then I'm back to the 'updating' screen. How long should it take to update?

    EDIT: Jumped the gun, tried again after 5 mins and we're good!
    2
    Bummer....Google Services are sometimes a mystery unto themselves
    Especially, with the beta version of Google Play Services.
    1
    Still not sure what caused this glitch (likely SafetyNet failure during Magisk setup).

    Anyway, I found in Google Pay, Contactless setup
    View attachment 5630005

    the Last item said 'Your phone does not meet the security requirements'.

    Clearing Google Pay data wouldn't fix.

    I am scared to clear data for the several components that appear in applist w/ 'security' as keyword... So next I cleared Google Play Services and Google Play Store data, but now Google Play wouldn't even open, just this (unending):
    View attachment 5630011
    Strangely, clearing Google Pay data again had no effect either...

    Next, I simply uninstalled Google Pay completely, then reinstalled it from Play Store, and now get 'Your phone meets he security requirements' as shown above. Also:
    View attachment 5630017
    so seems I'm good to go again! 😛

    I don't know if version changed, but I assume I had latest version before as I auto-update... Some things are a mystery, but Uninstalling and reinstalling did the trick for me where clearing data wouldn't...

    For others facing this, clearly you'll need to fix any SafetyNet issues first...

    Hope this might alay some anguish. 😜 PW

    Thats slightly bonkers, wouldnt think it would be a database issue as a data clear would handle that, maybe some backend Google Pay thingy? The only issue i ever had with Google Pay was one of those rare error codes where you have to contact Google Pay and they reset it from their end..24-48 hour turnaround. In my case it was an issue where the originating bank (my bank) spammed their backend with false data when i was adding my card after a ROM flash

    In any event, youve maintained your track record of solving issue sin this thread before i get to them. Your sacrifice is noted...

    Ponkles
  • 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.