[Magisk] Google wallet (pay) with magisk

Search This thread

Danishblunt

Senior Member
Jul 2, 2015
66
27
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:

step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.

- Reboot

NOTE: Remeber to clear google wallet just in case.

ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh

then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:

Enjoy.
 
Last edited:

deechte

Senior Member
Feb 1, 2007
916
215
Soest
OnePlus 7T Pro
I'm very grateful for this guide, thank you so much! I'm not an ace at this, rooted my device long ago and simply kept updating.

The recent developments at Magisk got me so confused. I follow the Magisk - The Age of Zygisk thread, but there are so many things I don't understand and problems people have, that I was going to give up. I was still on Magisk v23 because of all of this. And then Google Wallet recently started complaining about root on my device.

So happy I found this thread with a simple step by step approach. After clearing data of the Wallet app, Play Store and Play Services I obviously had to re-add my banking card to it, and I was able to successfully do it. No warnings so far in the app, but I still have to make my first payment.
Update: by now I've been able to pay multiple times without trouble.

Edit: bootloader is unlocked.
 
Last edited:

LoredoJC

New member
Jul 30, 2022
1
0
On my ZE620KL nothing worked, many tries, I waited a few days and it didn't work. Even changing the rom for an official Asus rom (without root) the app kept saying that the device is not safe. It only started to allow contactless payment after relocking the bootloader. I believe that in my case, gpay did not work by detecting the unlocked bootloader.

Edit
The device passed all tests, safenet, Google protect, basic, CTS (with root).

but it still only worked after relocking the bootloader
 
Last edited:

Clasimodo

Senior Member
Dec 22, 2006
183
36
On Samsung I didn't even have to hide Magisk. Magiskhide Props Config did the job. I had Universal SafetyNet Fix already installed, but don't know if that is necessary for wallet to work. I paid in different places without a problem.
 

oksagi

Senior Member
Oct 30, 2008
389
77
Pixel 6 with latest Magisk 25.2.
MagiskHide Props module.
Changed the fingerprint, cleared cache for Playstore, Play services and walled app.
I was able with these steps to pay via wallet yesterday.

Thanks for the workaround!
 
  • Like
Reactions: Rpgilligan85

Rayfen Windspear

Senior Member
Dec 17, 2015
134
118
Utah
Update on my Pixel 2. I changed the fingerprint to Pixel 6 and it let me add my card. Netflix updated as well. Looks like they are starting to deprecate some of the *really* older fingerprints.
 

mj084

Senior Member
Sep 26, 2008
1,070
362
Berlin
On Samsung I didn't even have to hide Magisk. Magiskhide Props Config did the job. I had Universal SafetyNet Fix already installed, but don't know if that is necessary for wallet to work. I paid in different places without a problem.
Here too on OnePlus 7T - worked some days before using MagiskHide Props Config - now I installed the module and setted a certified Fingerprint and I was able to add my credit card to Google Wallet :)
 

Rayfen Windspear

Senior Member
Dec 17, 2015
134
118
Utah
Another update from me on Pixel 2. Changing the fingerprint from an Android 11 print to 12 caused my Camera app to update, totally breaking it on launch. Had to reverse my fingerprint back to Pixel 2 @ 11 to get my camera back up. I AM running LineageOS on 12 (12.1), but it looks like the Camera app is fingerprint dependent. Appears everything still works on the Pay side. Note that I haven't gotten around to making a payment yet, but the app no longer simply rejects me. I've yet to have it fail without it telling me to get lost from the app beforehand.

Looks like the GPay/Wallet/Play Store only check periodically and cache the results. Seems strange for something they would want to lock down pretty tight like Card payments... but whatever. Works for me at the moment.

I suspect I'll possibly have to mess with my fingerprint eventually again. If/when I do, I'll be sure to report back if it's the device they may have blacklisted, or if it was the Android 11 fingerprint. I'd suspect it's the device, not the OS though. It's certainly getting on the old side :cry:
 

Rayfen Windspear

Senior Member
Dec 17, 2015
134
118
Utah
Fingerprint back to Pixel 2 at android 11 restored my camera, but after a day or so, killed gpay again 😒. Any other fingerprint makes my camera want to update and break. Going to try several to see what correlation there is between OS and device that causes success. Trying Pixel 3 @ 11 right now. Have to wait for caches to settle before gpay decides I'm kosher again though.
 

Rayfen Windspear

Senior Member
Dec 17, 2015
134
118
Utah
Well, now I'm stuck with a choice between a working camera app, and having Pay work 😒. Updating my fingerprint to anything causes the camera app to update and throw an unsupported device error. Manually extracting and installing the camera app causes it to crash unable to load some shared library file.

Leaving the fingerprint on Pixel 2 @android 11 brings back the camera, but breaks Pay for the whole Wallet... Although it has let me add cards/methods without issue, and doesn't whine that I'm rooted when tapping on "not set up" like it does when you are rooted and have zero Pay mitigations.

So now I'm just waiting again to see if it will spring alive again after a bit, and then I'll tackle trying to get the right camera version installed without letting the stupid play store update it.
 

deechte

Senior Member
Feb 1, 2007
916
215
Soest
OnePlus 7T Pro
Well, now I'm stuck with a choice between a working camera app, and having Pay work 😒. Updating my fingerprint to anything causes the camera app to update and throw an unsupported device error. Manually extracting and installing the camera app causes it to crash unable to load some shared library file.

Leaving the fingerprint on Pixel 2 @android 11 brings back the camera, but breaks Pay for the whole Wallet... Although it has let me add cards/methods without issue, and doesn't whine that I'm rooted when tapping on "not set up" like it does when you are rooted and have zero Pay mitigations.

So now I'm just waiting again to see if it will spring alive again after a bit, and then I'll tackle trying to get the right camera version installed without letting the stupid play store update it.
If your camera app updates through play store, you could disable automatic updates. If it updates without play store, maybe installing AFWall+ and blocking internet access for it might work?
 

Rayfen Windspear

Senior Member
Dec 17, 2015
134
118
Utah
If your camera app updates through play store, you could disable automatic updates. If it updates without play store, maybe installing AFWall+ and blocking internet access for it might work?
I disabled auto update, then I walk away from it and and come back to find it had updated.

As to Pay update. I was changing my fingerprint all day yesterday playing with the camera, but I did a system update overnight, and Pay activated. It's been a while since I've opened recovery and wiped dalvik/cache. LineaogeOS recovery doesn't have that option. I wonder if changing fingerprint then clearing it would avoid having to wait.
 

Rayfen Windspear

Senior Member
Dec 17, 2015
134
118
Utah
Now this o_O

Screenshot_20220809-111959_Google Play Store.png


Here we go again...
 

Danishblunt

Senior Member
Jul 2, 2015
66
27
Well, now I'm stuck with a choice between a working camera app, and having Pay work 😒. Updating my fingerprint to anything causes the camera app to update and throw an unsupported device error. Manually extracting and installing the camera app causes it to crash unable to load some shared library file.

Leaving the fingerprint on Pixel 2 @android 11 brings back the camera, but breaks Pay for the whole Wallet... Although it has let me add cards/methods without issue, and doesn't whine that I'm rooted when tapping on "not set up" like it does when you are rooted and have zero Pay mitigations.

So now I'm just waiting again to see if it will spring alive again after a bit, and then I'll tackle trying to get the right camera version installed without letting the stupid play store update it.
Well if thats the only issue, why not download a gcam mod for your pixel 2 instead?
 
  • Love
Reactions: Rayfen Windspear

V0latyle

Forum Moderator
Staff member
My phone passed all the tests but would not work with Wallet. Tried fingerprint in props but my phone or variants of not listed. Followed Reddit suggestion of disabling/removing Props and flashing modded safetynet fix 2.32 modded by Displax over normal one. That solved my problem with my Oukitel F150 R2022
The reason for this is that Google has deprecated the SafetyNet certifications in favor of the new Play Integrity API, which uses 3 fields:

MEETS_DEVICE_INTEGRITY
  • The app is running on an Android device powered by Google Play services. The device passes system integrity checks and meets Android compatibility requirements. This is replacing SafetyNet's ctsProfile. This is what USNF fixes.
MEETS_BASIC_INTEGRITY
  • The app is running on a device that passes basic system integrity checks. The device may not meet Android compatibility requirements and may not be approved to run Google Play services. For example, the device may be running an unrecognized version of Android, may have an unlocked bootloader, or may not have been certified by the manufacturer. This is replacing SafetyNet's basicIntegrity, and means that Play Services has not detected root.
MEETS_STRONG_INTEGRITY
  • The app is running on an Android device powered by Google Play services and has a strong guarantee of system integrity such as a hardware-backed proof of boot integrity. The device passes system integrity checks and meets Android compatibility requirements.
    This is replacing SafetyNet's Hardware Attestation, and uses the Android system's Trusted Execution Environment to guarantee process security. This will not pass with an unlocked bootloader, and cannot be spoofed as it specifically relies on hardware security; unlocking the bootloader "breaks" TEE.

The workaround for this is the modded USNF module by @Displax which spoofs an older fingerprint causing apps to fall back to the "old way" of using only the DEVICE and BASIC fields. I imagine at some point in the future, app developers (especially large ones like Google) will eventually remove this fallback in their apps, which will mean that anyone whose device does not pass Play Integrity will not be able to use the app. This will include everyone running versions of Android older than 8.0, when TEE was implemented.
 
Last edited:

pndwal

Senior Member
Would you consider possibly boiling this down to a fairly simpler explanation that we can sticky? It's likely this will be the topic of quite repetitive questions going forward.

I tried to explain it somewhat simply here, please let me know how far I missed the mark
Wow.. another thread 😬... Perhaps we could condense this in @Didgeridoohan's GPay thread?

Anyway, since you asked me to critique, it's there:
https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-87274413

🤠 👍 PW
 
  • Like
Reactions: V0latyle

arwindr79

New member
Sep 25, 2014
4
2
Thanks for the instructions, finally managed to make a payment today. Sprint LG G8 crossflashed to A11, Magisk 25.2, google pay worked fine but broke after the update to wallet. Even though my exact model number wasn't on the fingerprint list, the G8 fingerprint which is listed seems to be working fine.
 

jono0080

New member
Jan 9, 2017
1
0
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
- Update Magisk to 25.2, Update magisk app to 25.2 as well
- Rename Magisk app if you havent already
- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
- then:

step 1.) Download any terminal (I use termux)
step 2.) type SU
step 3.) type props
step 4.) edit device fingerprint
step 5.) follow the onscreen promt
step 6.) once successfully changed, reboot device
optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
step 7.) enjoy working google wallet.

- Reboot

NOTE: Remeber to clear google wallet just in case.

ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh

then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:

Enjoy.
Worked a treat on s21 ultra followed step by step now have it working again
 

Top Liked Posts

  • 1
    I have my doubts that v2.3.1-MOD did anything to fix my issue. On my previous attempts, I only cleared the cache of Google Play Service and Google Wallet. When I switched to 2.3.1-MOD, I pressed "Clear all data" instead.

    I'm not sure how Wallet detected the root in the first place, but maybe it cached the detection somewhere that wouldn't be purged by clearing the cache?
    I experimented a little. If I go back to the OP method I cannot add a payment card (rooted warning). I cleared data of Google Play. If I then remove the props module and then install the mod instead of the original safety fix I can add a payment card.
  • 2
    I have my doubts that v2.3.1-MOD did anything to fix my issue. On my previous attempts, I only cleared the cache of Google Play Service and Google Wallet. When I switched to 2.3.1-MOD, I pressed "Clear all data" instead.
    You'll find out, I think, when whatever it is that triggered it in the first place (some kind of Google Play Service action, perhaps) recurs, which it surely will at least try to do.

    There's a fork of the fork, incidentally, here, and that one looks more maintained and even documented. Not sure of its efficacy yet.
    1
    Installed pixel 4 android 12 fingerptint on pixel 4 android 13.
    Had to clear all data in google play services then contactless returned
    1
    I have my doubts that v2.3.1-MOD did anything to fix my issue. On my previous attempts, I only cleared the cache of Google Play Service and Google Wallet. When I switched to 2.3.1-MOD, I pressed "Clear all data" instead.

    I'm not sure how Wallet detected the root in the first place, but maybe it cached the detection somewhere that wouldn't be purged by clearing the cache?
    I experimented a little. If I go back to the OP method I cannot add a payment card (rooted warning). I cleared data of Google Play. If I then remove the props module and then install the mod instead of the original safety fix I can add a payment card.
  • 22
    Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:
    - Update Magisk to 25.2, Update magisk app to 25.2 as well
    - Rename Magisk app if you havent already
    - [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)
    - install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix
    - then:

    step 1.) Download any terminal (I use termux)
    step 2.) type SU
    step 3.) type props
    step 4.) edit device fingerprint
    step 5.) follow the onscreen promt
    step 6.) once successfully changed, reboot device
    optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.
    step 7.) enjoy working google wallet.

    - Reboot

    NOTE: Remeber to clear google wallet just in case.

    ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh

    then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:

    Enjoy.
    3
    Oneplus 8t fingerprint unlock stopped working, anyone has a fix?
    Uninstall prop module and install only this safetynet-fix

    3
    I think some steps are not necessary. Like hiding all Google apps and SQ Lite

    Also, momo-hider is depreciated. Use shamiko.

    Lastly, I just installed magisk hide props (and configured it) and now it works.
    3
    hi may I ask what does step 5 mean? Thanks!

    Sorry, I don't get it. I should change the FP from my Google PIxel 6 to any other, like 6Pro or Pixel 5?

    Cheers
    Tom

    I figured out you need to subsequently choose:
    A) edit device fingerprint
    B) pick a certified fingerprint
    C) choose your specific brand, device and Android version
    D) confirm with Yes

    This does not really change anything to your actual fingerprint you use to unlock your device, but apparently it changes something needed to make it all work.
    2
    I figured out you need to subsequently choose:
    A) edit device fingerprint
    B) pick a certified fingerprint
    C) choose your specific brand, device and Android version
    D) confirm with Yes

    This does not really change anything to your actual fingerprint you use to unlock your device, but apparently it changes something needed to make it all work.
    Thanks, so basically I did it right, didn't work me, still showed "doesn't meet requirements. But today, without further doing. It was fine.
    ... then I just let it settle for a few days and it finally started working.

    So I guess that's what I'm trying now. The waiting game. The same thing happened when setting up a Pixel 4a 5G for my wife. Did all the steps, didn't work immediately, but checked a few days later and it had picked it up... super annoying.
    Thanks to your post, I thought check again after it didn't worked yesterday. And yes, it shows today, "You are ready to pay..."

    Cheers
    Tom