[Discussion] Google Pay Magisk Discussion Thread

Search This thread

TraderJack

Senior Member
Oct 5, 2008
383
143
Google Pixel 3 XL
Yes, you're right.
Lygisk is a fork of Magisk (just rebuilds with some patches) which can survive after OTA updates.

Interesting. According to why I see on the Telegram Channel, it is built using the latest Magisk so it is 25.1/2 and uses the Zygisk deny and not the old Magisk hide mechanism.

I can only surmise that the particular fingerprint for your device is still in the databases as only being valid for basic attestation despite it being a 12 OS. Again, I would expect that sooner or later (most likely sooner) you will being to see an issue. Once that happens though I'm not sure how safe any of us will be using different fingerprints. I see no reason for instance that the Pixel 3 XL 9 fingerprint works when the 12 doesn't, as that device should support HA even on 9.
 
  • Like
Reactions: helgi1507

Lada333

Senior Member
Feb 7, 2016
1,252
400
22
Budapest
OnePlus 3T
Google Pixel 4a
I format all device in recovery before installing, so, yes.
Fwiw, I just dirty flashed v8.7 and it looks like contactless still works for me. I have yet to actually try it out though, I'm going off by Wallet telling me that my device is set up for contactless payments.

EDIT: Yup, still working as expected.
 
Last edited:
  • Like
Reactions: helgi1507

zgfg

Senior Member
Oct 10, 2016
7,813
5,226
Please be aware that this app is not 100% accurate. The api has 2 more readings you can get (which are pretty important) but Google gives them to you only if you upload the app on Play Store. So I made a better app and uploaded it to Play Store. Now I'm just waiting for Google to verify my identity and it will be up. (Oh and by the way the app is 100% open source, I'll link everything once it's up)
Do you have an info about the availability of your app on Google Play - so far I could not find yet

Could you provide more details, something like in YASNAC, to see the relevant data when eg failing

Also, I pass on Xiaomi Mi 9T although it runs MIUI 12.5/A11 (it's also in the fingerprint), hence I believe it doesn't use TEE but kind of Basic attestation and gets tricked by USNF functionality built into the Xiaomi.eu ROM - would like to see what's really going on there 😁
 

zgfg

Senior Member
Oct 10, 2016
7,813
5,226
I was waiting for Google to verify my identity now they just need to approve it (should take less than 24 hours). Keep in mind that I've never fully tested it. I can't test it until it's up on Play Store 🥲
"Is this the verdict for my Does not meet device integrity", or I should look for something else in logcat:

07-25 19:26:40.410 W/IntegrityServic(27680): type=1400 audit(0.0:208304): avc: denied { write } for name="tasks" dev="cgroup" ino=21 scontext=u:r:untrusted_app:s0:c232,c256,c512,c768 tcontext=u:eek:bject_r:cgroup:s0 tclass=file permissive=0 app=gr.nikolasspyr.integritytest
 

1nikolas

Senior Member
Jul 28, 2015
199
126
Heraklion, Greece
"Is this the verdict for my Does not meet device integrity", or I should look for something else in logcat:

07-25 19:26:40.410 W/IntegrityServic(27680): type=1400 audit(0.0:208304): avc: denied { write } for name="tasks" dev="cgroup" ino=21 scontext=u:r:untrusted_app:s0:c232,c256,c512,c768 tcontext=u:eek:bject_r:cgroup:s0 tclass=file permissive=0 app=gr.nikolasspyr.integritytest
The old app can't get you more info so looking at logcat won't help. Just wait till the new app is out
 
  • Like
Reactions: zgfg

Displax

Senior Member
Jan 19, 2015
289
1,008
26
Kyiv
Modification of Universal SafetyNet Fix with Play Integrity API bypass

 

zgfg

Senior Member
Oct 10, 2016
7,813
5,226
Modification of Universal SafetyNet Fix with Play Integrity API bypass

Thanks👍

Xiaomi 11 Lite 5G NE, MIUI 12.5/A11 (as released with - ie original A11 device)

Previously, with USNF V2.3.1 I was passing SafetyNet with Basic type attestation, now with your v2.3.2 mod I can also pass Play Integrity with MEETS_DEVICE_INTEGRITY
 

Attachments

  • Screenshot_2022-07-25-21-58-14-926_gr.nikolasspyr.integritytest.jpg
    Screenshot_2022-07-25-21-58-14-926_gr.nikolasspyr.integritytest.jpg
    89 KB · Views: 86
Last edited:

shadowstep

Senior Moderator
Staff member
Jun 6, 2014
6,260
14,754
31
Ambala Cantt
OnePlus 9R
Modification of Universal SafetyNet Fix with Play Integrity API bypass

Works for me as well, on OnePlus 9R running stock OOS 11. (y)
 

jons99

Senior Member
Nov 5, 2019
255
300
Modification of Universal SafetyNet Fix with Play Integrity API bypass

working well on pixel 5 latest google update thanks
 

Griffinx

Member
Dec 29, 2010
38
9
Modification of Universal SafetyNet Fix with Play Integrity API bypass

This is working fine for me in the shops on Pixel 6 even though the Wallet app is still saying that my phone doesn't meet the security requirements.
 

letm

Member
May 21, 2007
18
5
Redmi 9 Power
After 4 days to try, Ok for me. I tested it today 2 times with success.

My phone >> Redmi 9T-M2010J19SY-RKQ1.201004.002/V12.5.8.0.RJQEUXM under android 11

my modules run under magisk stable V 25.2 (25200)
busybox for android ndk 1.34.1
denylist Unmount V0.4
Gpay sqlite ver V2.8
Magiskhide propos config V6.12-V137
SQLite universal binaries V1.4
Universal Safetynet fic V2.3.1
Zygisk LSPosed V1.83

If you use lucky patcher, you need to hide it >> tools box >> xposed >> check all and apply
Hide Zygisk LSPosed V1.83 if you use it >> Parameters >> Create the shortcut

uninstall G(oogle) Pay, install wallet via google play.
In magisk 25 : Hide in exclusion list >> wallet, google play, play services.

Now go to "Magiskhide props config" in terminal to reset it to default >>type su >>type props >> option "r" to reset and reboot.

after restarted go to "Magiskhide props config" >>type su >>type props >> option 1 (fingerprint) >> option f >> option 7 google >> option 26 pixel 5 >> choose 11 or 12 (depend of your version) >> type yes >> after dont reboot type N (no) and no terminal exit.
//I you have a Redmi 9T under android 10 use pixel 4.. (not tested) Don't test redmi 9T fingerprints They don't work.//

Active airplaine mode and Clear cache and data for wallet, google play, play services. Reboot.
After reboot de-active airplaine mode, wait 5 minutes and launch wallet. Link a payment card to try it and it should be ok, like the attached screenshot.

Note : Before use wallet, you can test that wallet passed all security with the apk @1nikolas >> https://forum.xda-developers.com/t/...cussion-thread.3906703/page-130#post-87182459
 

Attachments

  • 1658941562871.jpg
    1658941562871.jpg
    96.5 KB · Views: 34
  • Love
Reactions: palopaxo

zgfg

Senior Member
Oct 10, 2016
7,813
5,226
After 4 days to try, Ok for me. I tested it today 2 times with success.

My phone >> Redmi 9T-M2010J19SY-RKQ1.201004.002/V12.5.8.0.RJQEUXM under android 11

my modules run under magisk stable V 25.2 (25200)
busybox for android ndk 1.34.1
denylist Unmount V0.4
Gpay sqlite ver V2.8
Magiskhide propos config V6.12-V137
SQLite universal binaries V1.4
Universal Safetynet fic V2.3.1
Zygisk LSPosed V1.83

If you use lucky patcher, you need to hide it >> tools box >> xposed >> check all and apply
Hide Zygisk LSPosed V1.83 if you use it >> Parameters >> Create the shortcut

uninstall G(oogle) Pay, install wallet via google play.
In magisk 25 : Hide in exclusion list >> wallet, google play, play services.

Now go to "Magiskhide props config" in terminal to reset it to default >>type su >>type props >> option "r" to reset and reboot.

after restarted go to "Magiskhide props config" >>type su >>type props >> option 1 (fingerprint) >> option f >> option 7 google >> option 26 pixel 5 >> choose 11 or 12 (depend of your version) >> type yes >> after dont reboot type N (no) and no terminal exit.
//I you have a Redmi 9T under android 10 use pixel 4.. (not tested) Don't test redmi 9T fingerprints They don't work.//

Active airplaine mode and Clear cache and data for wallet, google play, play services. Reboot.
After reboot de-active airplaine mode, wait 5 minutes and launch wallet. Link a payment card to try it and it should be ok, like the attached screenshot.

Note : Before use wallet, you can test that wallet passed all security with the apk @1nikolas >> https://forum.xda-developers.com/t/...cussion-thread.3906703/page-130#post-87182459
Just few comments:

With USNF v2.3.2 (posted here few days ago - specifically for Wallet and Play Integrity), you should be able to pass without MHPC (since you have the rooted but stock ROM)

Even if you put Google Play Services to DenyList, USNF will remove it (open the list again and check)

Also, Google Play app should be checking through Google Play Services hence Google Play app should not need to be added to DenyList
 
  • Like
Reactions: 73sydney

Top Liked Posts

  • 1
    So similarly to others, last week integrity checker suddenly reported my phone no longer MEETS_DEVICE_INTEGRITY. As others have reported it went back to normal after a few days and I get two green checkmarks in PI checker. Since then I can't add my card to gpay. The setup goes well until the part where it normally prompts me to put in the code sent via SMS. The app tells me it can't add the card right now and to contact my bank. Customer support told me to wait and try again in 24 hrs, which didn't help. Has anyone else experienced this? And is it related to PI and/or magisk?
    https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-87400949

    See this also; scroll down to Related Issues:

    https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-87481637

    👍 PW
    1
    Gpay displays that I pass security and I've wiped data/uninstalled many times. It's probably as @batboy00 says and my bank just had enough of my messing around.

    not saying its this, but just for sharing...

    but back in my pixel days, about 3 years ago, when i was routinely testing (flashing) 2-4 ROM's a week, i did have a GPay failure that rendered contactless broken. Contacted bank...nope no issue there. Contacted Google via web...yup my account had gotten garbled by too many GPay setup requests from my bank :) Took them 24 hours to turn around on that one

    aka when (too much) ROM flashing goes wrong

    only time it wasnt something i could fix with a wipe
  • 8
    @brambles1234, @Nekromantik, @cescman, others searching, here's a little Summary / Guide:

    Current fixes needed for Google Pay / Wallet


    These days we need passing deviceIntegrity in new Play Integrity API. (Don't worry about strong integrity; few if any apps will use this at present as that would exclude users/customers using any device launched with Android 7 or earlier even if on latest Android as well as a number of newer devices with broken keymaster implementations.) Nb. While Safety net API is already depreciated, it's attestation must all be passing and Evaluation type showing BASIC for PI deviceIntegrity to pass since the same signals (plus more) are used by PI...

    To check these, use YASNAC (S/N) and Play Integrity API Checker (PI) from Play Store...

    Many devices passing S/N CTS Profile match, especially those running Android 11+, won't pass PI deviceIntegrity verdict with current official Universal SafetyNet Fix alone. @Displax's safetynet-fix-xxxx-MOD is the current solution:
    https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
    - See my notes in post above for technical details, incl. why this solution also negates the need for setting a fingerprint in MagiskHide Props Config module for ROMs not passing CTS Profile match (China region, Beta, Developer, many custom ROMS)...
    - Also note Usage: Delete/disable/reset MHPC (if installed / spoofing fingerprint).
    - Note that Zygisk should be enabled and working, and only Google Pay/Wallet needs to be in denylist whether enforced or disabled with Shamiko etc active; no need for Play Store, Google Play Services processes etc when using any Zygisk-USNF builds...

    Once PI deviceIntegrity is restored / passing, Google Pay/Wallet security requirements may pass again after some days (could take a week!) if simply left... Clearing Google Play Services and Google Pay/Wallet data should fix this immediately but you will need to set up cards again... Nb. Be sure to reboot immediately after clearing Google Pay/Wallet data (before opening app) to avoid issues (eg. app works but Activity list fails to populate).

    Clearing Play Store data may be needed to restore Play Protect 'Device is certified' in Play Store Settings, About... This will affect whether Google Pay and other apps calling S/N or PI APIs appear in the Store...

    Related Issues:

    A number of users have experienced contactless payment failure with Google Pay / Wallet stating "Your phone does not meet the security requirements" irrespective of SafetyNet or Play Integrity status. (Several of us experienced this suddenly, and it predated both new Wallet upgrade an Play Integrity implementation.)...

    Further, in tackling this I experienced two issues restoring a working setup;
    - Issue where 'Google Pay/Wallet is currently updating' fails to complete, and
    - After restoring app, Activity list fails to populate.

    I put steps to fix these here:
    Initial fix:
    https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-86981221
    Resolved Activity list won't populate:
    https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-86991951
    Summary (scroll to 'In short...'):
    https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-86992241

    Hope this helps those concerned. 🤠 PW
    7
    Whenever I come to XDA and ask a question I'm normally receive a really unhelpful reply, along the lines of "if you search you will find your answer" This is can be very annoying, especially after I have spent an hour looking and I still can't find the answer? Hence the reason I ask a question.

    The reason I say this is because I have got Google wallet working and I will share what I did.

    1. Uninstalled Google wallet
    2. Deleted both cache and data from play store
    3. Updated Xprivacy Lua
    4. Reinstalled UNSF
    5. Changed fingerprint using su / props
    6. Restarted phone

    It is pertinent to say here that I fail all api integrity checks using the app on playstore. However Google wallet contactless payment works better than before.

    I will keep this updated if I have as any issues.

    Please understand that someone asking the same question over and over (and often expecting to be spoonfed) can be taxing.

    And yes the search system can sometimes take a bit of learning to fully utilize properly....but really, heres the key.....if its a recent issue, then the issue is very likely not just affecting you, and so the solution will often be found in the last 5-10 pages of a thread. People get really tired of people who rock up create a new post at the end of the thread, when the answer is maybe 3 pages back, and they seem to think thats too much effort. Standard Operating Procedure on any thread should be to read the last 5-10 pages before creating a new post. That would earn the average person who thinks theyre catching a tough break because theyve touched a nerve that been tugged at by 50 people before them a lot of respect....consider trying the last 5-10 pages of a thread method in future, it will often not only giver you the solution, but the context, which can be just as important, and often you may be able to provide some input or insight no one else has, which everyone can benefit from. Also if people just rock up and expect an answer in 5 minutes everytime (theres plenty do it, some people might have been registered for 3, sometimes many more, years and never post until they need something, happens all the time), then they dont learn anything, and they also dont contribute....

    As for your steps above:

    3. Updated Xprivacy Lua <-thats not required and is a personal choice, and has no real bearing ion the issue)

    Usually one would do:

    1. Install USNF Mod (the Mod is important as already stated)
    2. Integrity Test
    3. Test contactless menu in Wallet

    If contactless fails:
    4. Delete both cache and data from play store and reboot
    5. Test contactless menu in Wallet

    Note

    Step 4 has been known to take days to return a positive contactless setup, in some cases


    Note #2:

    5. Changed fingerprint using su / props <- this should be largely unnecessary except in the case of chinese ROM's or other edge cases as far as i remember
    5
    Play Integrity API Checker updated to v1.0:

    Thanks @1nikolas
    5
    ... Note #2:

    5. Changed fingerprint using su / props <- this should be largely unnecessary except in the case of chinese ROM's or other edge cases as far as i remember
    ... And with @Displax USNF_mod it is not needed even for ROMs not passing CTS Profile match (China region, Beta, Developer, many custom ROMS) in most cases. (There may rare be exceptions where this modded module doesn't work.)

    Technical:

    This mod actually adjusts the fingerprint prop to achieve the mismatch needed along with device prop mismatch to trigger bypassing of hardware based attestation enforcement in Play Integrity (different from the actual Evaluation type fallback triggered by the exception caused when trying to use key attestation with an injected 'fake' keystore provider registered)...

    All these mods, official and unofficial, target the gms attestation process (one process within Google Play Services) only. The prop changes are not globally applied, so issues with OEM specific functions (eg Galaxy Store, special camera functions etc) caused by model prop changes and issues with Play Store (eg. YouTube not updating as expected) etc caused by fingerprint prop changes are successfully avoided...

    Issues with unmatched security patch prop dates are also avoided with this solution...

    The @Displax mod also kills a second bird (or rabbit 😜 ), ie. allowing ROMs not passing CTS Profile match to pass as mentioned above, simply because the fingerprint prop used for HA bypass trigger must also be properly certified for CTS...

    --> This makes this USNF build a true 'Universal' fix, encompassing both old S/N API and new PI API, as well as the whole range of certified stock and uncertified China region, Beta, Developer and custom ROMS...

    👀 PW
    4
    This module helps pass Libc and Syscall File Detection (in Ruru app) with Riru on Magisk Delta. Other detections remain, though. https://github.com/stylemessiah/AppDataIsolation/releases

    Google Pay works.

    Thanks, now passing also Libc and Syscall (and everything else)

    im glad to know the module works for someone else...

    blame @Stillhard for PM'ing the method behind it to me, i just packaged it
  • 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
    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.
    26
    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.