[Discussion] Google Pay Magisk Discussion Thread

Search This thread

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,996
4,364
Please note, Wallet started complaining (as is the case with others) when on 2.4.0 (kdrag0n). Rolled back to 2.3.1_mod_2.1 (Displax), cleared cache for Wallet (for precaution) and then updated Google Play system. After ~+24 hours, it has dropped off and no more apparent error messages (as of yet).
Wallet is def. spamming with it, but tap to pay setup shows good (unlike previous where tap to pay setup showed issue). tap to pay seems to work.
 

bigknowz

Senior Member
Jan 9, 2012
955
503
NYC
Google Pixel 7 Pro
Please note, Wallet started complaining (as is the case with others) when on 2.4.0 (kdrag0n). Rolled back to 2.3.1_mod_2.1 (Displax), cleared cache for Wallet (for precaution) and then updated Google Play system. After ~+24 hours, it has dropped off and no more apparent error messages (as of yet).
Thanks for the info, Tap to Pay stopped working this morning, root detection. Went back to mod_2.1 and Tap to Pay working again.
 

simplydat

Senior Member
Oct 13, 2009
137
23
Please note, Wallet started complaining (as is the case with others) when on 2.4.0 (kdrag0n). Rolled back to 2.3.1_mod_2.1 (Displax), cleared cache for Wallet (for precaution) and then updated Google Play system. After ~+24 hours, it has dropped off and no more apparent error messages (as of yet).
Thanks for this. Rolled back to 2.3.1 by Displax.
 

bigknowz

Senior Member
Jan 9, 2012
955
503
NYC
Google Pixel 7 Pro
Have just paid through Google Wallet, with USNF-MOD-2.31-v2.1. No changes for me on this subject.. Sony Xperia XZ2 running LineageOS 20.0. Latest Magisk Delta Canary. Zygisk and MagiskHide are enabled. SuList is not enforced.
 

Attachments

  • Screenshot_20230207-141214.png
    Screenshot_20230207-141214.png
    228.5 KB · Views: 68
My Play Store app was updated today. These are its 'About' info, along with gms'. Are these the latest, which have been giving people headaches today? I ask it because I keep passing the device integrity test, and my Google Wallet is still good to go. Might it be that Sony is extremely dev friendly?
 

Attachments

  • Screenshot_20230208-150240_Play Integrity API Checker.png
    Screenshot_20230208-150240_Play Integrity API Checker.png
    72.6 KB · Views: 61
  • Screenshot_20230208-150158_Settings.png
    Screenshot_20230208-150158_Settings.png
    139.3 KB · Views: 60
  • Screenshot_20230208-150221_Google Play Store.png
    Screenshot_20230208-150221_Google Play Store.png
    144.1 KB · Views: 56
  • Screenshot_20230208-150918_System UI.png
    Screenshot_20230208-150918_System UI.png
    75 KB · Views: 66

m0han

Senior Member
Apr 30, 2012
5,448
2,558
My Play Store app was updated today..... Are these the latest, which have been giving people headaches today? I ask it because I keep passing the device integrity test, and my Google Wallet is still good to go....
Not just Sony, I guess. GPay works, as of now.
 

Attachments

  • SS_20230209_121442.jpg
    SS_20230209_121442.jpg
    173.3 KB · Views: 61
  • SS_20230209_121555.jpg
    SS_20230209_121555.jpg
    134.4 KB · Views: 58

pershoot

Inactive Recognized Developer
Dec 1, 2008
7,996
4,364
tap to pay setup flipped back to security requirements error (on displax 2.3.1-mod_2.1).

have not tested at terminal.
 

pndwal

Senior Member
I didn't before, but did just now as you mentioned it. passed.
Should come right without intervention as long as you have PI deviceIntegrity... Can take a week... Clearing data definitely clears detection flags but can be arduous establishing setup / Wallet updates again... Clearing cache only is safe but may not reset detection flags... PW
 

BesoC

Senior Member
Dec 29, 2007
183
32
Tbilisi
Magisk hidden, Zygisk enabled, safetynet-fix 2.3.1-MOD_3.0 installed
Force stop, clear cache and storage for Google Play Services, Play Store and Wallet, reboot.
Repeat 4 times
Still Play Integrity API Checker shows red cross for MEETS_DEVICE_INTEGRITY

EDIT:
Uninstall USNF, reboot, check with Integrity API Checker - got 3 red crosses, predictable.
Reinstall USNF, reboot - MEETS_DEVICE_INTEGRITY is red :(
 

pndwal

Senior Member
Magisk hidden, Zygisk enabled, safetynet-fix 2.3.1-MOD_3.0 installed
Force stop, clear cache and storage for Google Play Services, Play Store and Wallet, reboot.
Repeat 4 times
Still Play Integrity API Checker shows red cross for MEETS_DEVICE_INTEGRITY

EDIT:
Uninstall USNF, reboot, check with Integrity API Checker - got 3 red crosses, predictable.
Reinstall USNF, reboot - MEETS_DEVICE_INTEGRITY is red :(
Don't bother fixing Pay/Wallet till you have deviceIntegrity...

It's pretty much useless posting issues like this w/o at least giving device details/ROM/mods... But I remembered you. 😉

OnePlus? RiceDroid?...

... I just posted re. this today:
PSA for custom ROM users:

If your ROM integrates it's own prop changes/spoofing you should not be surprised if @Displax's latest USNF fails to work for you... You'll likely need to wait for the ROMs maintaining Dev to incorporate the changes natively...

Many custom ROMs are built clean and are thus more suitable for USNF and other magisk solutions, but of course these won't pass Play Integrity deviceIntegrity w/o magisk and USNF etc, so it's a choice for users... For example, official LineageOS will never spoof props/other expected signals, although many unofficial builds do.

👀 PW
🙃 PW
 
  • Like
Reactions: ipdev and shoey63

Top Liked Posts

  • 1
    @DineshValor does Privacy Space support android 10 with Lsposed? Also can share the link to download the module? I'm finding a old one which mentioned support for Android 9
    It's supported upto android 13 and currently I'm using LSposed with android 12.
    Here is the link:
    Screenshot_2023-03-28-13-06-25-43_084ab3bc34f7aa7ccff83653f52abafc.jpg

    Screenshot_2023-03-28-13-11-37-30_084ab3bc34f7aa7ccff83653f52abafc.jpg
    1
    following this guide, landed me into bootloop. Is there a brief guide - blog or video?
    Sorry about that issue, but right now I'm busy in some other stuff, i will make sure to create a brief video as a demo, plz grant me some time.
  • 2
    This is so weird. I have Galaxy S22 and Galaxy S20+, both with latest stock firmware + Magisk 25.2, I have all google apps in DenyList. Also, the ROM is heavily modified: I disable almost all Samsung Apps (except for system-critical). SafetyNetFix of latest Git-downloaded version installed, TWRP also of latest available (corsicanu's build). Everything works, but Google Wallet sometimes throws a pop-up warning about root. I usually kill the app, wipe it's cache, start it again and I can again pay without problem. Also, no matter what, contact-less payment have all checks green, despite prior toast warning. Reboot also fixes the issue (making payments possible again, in cases where cache wipe or app-kill won't work).
    If you're using the original Universal SafetyNet Fix by kdrag0n, you might wanna switch to the Displax fork linked a couple of posts above and test.

    Hope this helps.
    2
    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?
    Requirements:-
    - Magisk v25.2
    - LSPosed v1.8.6
    - PrivacySpace v1.3.7 (LSPosed module app)
    - Enable Zygisk (Enforce DenyList - Disabled) under Magisk (+ download some Magisk module as shown in screenshot¹)
    Screenshot_2023-03-18-17-10-02-79_9d1fb82a3633e78ac9c37e5a64e38237.jpg

    Follow below steps to fix "This functionality is not available due to security concerns with your device" in Paytm (Tap to Tay):-
    1. Download frest original Paytm app or clear data & force stop.
    2. Open PrivacySpace app/module under LSPosed.
    3. Hidden Apps > select Paytm (+ all other modules such as Lucky Patcher, etc as show in screenshot²).
    Screenshot_2023-03-18-17-20-27-10_30686f06bc9783668a8afa418b45660d.jpg
    4. Blacklist > select Paytm.
    Note: If u want to recieve Paytm app update in Play Store then select Play Store in "Connected with Others" to unhide Paytm app for Play Store.
    Screenshot_2023-03-18-17-27-19-47_30686f06bc9783668a8afa418b45660d.jpg
    5. All Set, Try your Luck Now, and do not forget to let me know if it's work for you too.
    1
    If you're using the original Universal SafetyNet Fix by kdrag0n, you might wanna switch to the Displax fork linked a couple of posts above and test.

    Hope this helps.
    Yes, just did so. I'm using 2.4 MOD from this thread. Will see how it works
    1
    I don't prefer G Pay for anything.. Will like to stick with Paytm and try to work on fixing tap to pay
    I see you said you pass SafetyNet... But of course that's deprecated; most banks have migrated to new Play Integrity API now... Are you passing PI deviceIntegrity?...If not official Universal SafetyNet Fix will likely not help as it currently has issues... You'll need @Displax's up-to-date fork with fixes...

    Also, did you install Shamiko for proper root hiding as suggested more than once above?

    🤠 PW
    1
    Does anyone happen to know why GPay 'Check bank balance' is not working? When I tap on the account on the 'Select account' screen, a line flashes above and disappears. Nothing else happens. Hope this is not OT here.
    I'm using same version GPay and didn't face such issue, probably it's your device app bug or something in your device. There no traces related magisk. Kindly confirm your side.
  • 62
    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
    32
    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.
    27
    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.