Pixel 2 with Android 9 (PPR1.180610.009) and Magisk v18.1 and Magisk Manager v7.
I used Google Pay with my VISA card for over a year, last used it last Friday and it worked nicely. Today I tried in two different places and I get the "You can no longer use Google Pay in shops" error message.
As far as I know I did not do any update to anything major since months, maybe just the YouTube Advanced Magisk module.
SafetyNet check pass successfully (both ctsProfile and basicIntegrity).
Google Pay is checked under "Magisk Hide" (don't remember doing this, but maybe, anyway I didn't change it between when it was working or not).
My credit card works fine when not using the phone.
Anyone have suggestions on what else I should check? Others around me using the same bank works fine on their phones. (Canada)
Google somehow managed to block Magisk. Same happened to me this week. Keep an eye out on Magisk forum, there's a specific post for Google Pay issues.
EDIT: Instructions on link below
https://forum.xda-developers.com/showpost.php?p=79029481&postcount=9
Hi! I have a problem!!!
OPPO Find x2 Pro (China). After the last update ( PDEM30_11_C_08) , the ability to pay was lost GPay---
CTS profile Status -FAILED (bySafetyNet Test (APK))
/Can you Help me ?
Mod translated by Google:
Don't help others.
不帮助别人。
I can only chime in to say that about two months ago after i finally allowed the update it also broke my google pay. Previously it worked fine.
Used to be able to use google pay until the latest update.
Now i'm unable to use google pay even thorugh my phone is stock and passes the safetyNet checks.
Oppo hasn't gotten back with their replies not optimistic i must say.
I know this is not the only post in regards to the recent Google Pay and Wallet updates not working on rooted phones, and maybe I missed something, but I don't think I'm the only one who has seemingly tried everything, only for it to do the same thing. What I've tried:
Installing Displax's SafetyNet mod
Adding all Google Play components and Pay and Wallet to the Denylist
Editing the dg.db database, including manually and with the GPay-SQLite-Fix module
Changing the device's fingerprint to Android 10 (I have a Pixel 5, so I changed it to a 4 XL, which is the newest similar phone to mine to support Android 10) and Android 11.
Side note: This causes CTSProfileMatch to fail for me, so I see no point in changing it.
Installed DevOptsHide and Hide USB Debug Mode Xposed modules, as one suggested on the Github issue for kdrag0n's SafetyNet Fix.
That was all I could find regarding this issue. It's worth noting that once I edited the dg.db file, it would say that it meets the safety requirements until I try to add a card, at which point I can't, and the safety requirements are no longer met. If somebody can find or share something I don't know or haven't seen, I would greatly appreciate it. It really sucks how hard Google is clamping down rooted devices; it seems like they really don't like it. Anyway, have a good one, and stay safe!
Today all app developers as Google and/or OEMs without any difficulty are able to detect whether their device's OS got tampered or not: you can't prevent this.
xXx yYy said:
Today all app developers as Google and/or OEMs without any difficulty are able to detect whether their device's OS got tampered or not: you can't prevent this.
Click to expand...
Click to collapse
So are you saying that I'm SOL for now until the community comes up with a fix? It seems like what worked a month ago is already obsolete.
Bump
Device doesn't meet security requirements
Is your device rooted or do you have adb enabled? If the device is rooted you need to do some things to hide it. If your device is not rooted, maybe check to make sure adb is disabled.
Like the comment above says, if you're rooted with Magisk, install this and it should start working fine after wiping the app.
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Adding on to this just because it's about Google Wallet...
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Curiousn00b said:
Like the comment above says, if you're rooted with Magisk, install this and it should start working fine after wiping the app.
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Adding on to this just because it's about Google Wallet...
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Click to expand...
Click to collapse
Wallet is the successor to Pay. They just haven't removed the old app
synesthete said:
Is your device rooted or do you have adb enabled? If the device is rooted you need to do some things to hide it. If your device is not rooted, maybe check to make sure adb is disabled.
Click to expand...
Click to collapse
I am currently rooted I am able to pass safety net I also have hide google wallet in magisk
highgrade said:
Device doesn't meet security requirements
Click to expand...
Click to collapse
Is this when you're trying to pay with Wallet or just setting up the app?
If it's while trying to pay, it might be because you unlocked your phone via face unlock before paying. You might have to unlock with the fingerprint scanner to make sure it works.
Might not be your issue here and I hate to say it but man, the fact that this is an issue at all makes me mad, for any regular user such an error would make absolutely no sense, and you would never understand it unless someone tells you.
highgrade said:
I am currently rooted I am able to pass safety net I also have hide google wallet in magisk
Click to expand...
Click to collapse
I am rooted and wallet is working. Here is how I have set mine up:
Magisk installed:
Zygisk enabled
Enforce Denylist enabled
Denylist blocking: Wallet, Pay, Google Play Services, and some other banking apps.
Install the Safetynet Fix module from this post: https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
Then install the MagiskHidePropsConfig module. (No need to configure it).
Force quit Wallet and wipe its data.
For quite and wiped data for Google Play Services.
Reboot
Then added card.
Those were the only modules that I needed. Maybe disable anything else you don't need while doing this in case they conflict.
JakeDHS07 said:
Wallet is the successor to Pay. They just haven't removed the old app
Click to expand...
Click to collapse
I think Pay has transitioned to being an app to send money to friends/family/etc like Venmo. I haven't used it since its split with Wallet, though.
Curiousn00b said:
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Click to expand...
Click to collapse
JakeDHS07 said:
Wallet is the successor to Pay. They just haven't removed the old app
Click to expand...
Click to collapse
As I understand it, Wallet holds all your "cards" like loyalty cards, gift cards, and transportation passes (metro, train, bus) -- hence "wallet" -- while GPay handles the credit cards for transactions for in-store/shops.
I guess Wallet is the app while GPay might be classified as the process...
Also...
synesthete said:
I think Pay has transitioned to being an app to send money to friends/family/etc like Venmo. I haven't used it since its split with Wallet, though.
Click to expand...
Click to collapse
Yes I noticed that GPay is transitioning to be like Venmo. I haven't used GPay in a long time, but since setting it up on my P7P, it was pushing hard to set things up so I could "easily send/receive payments to my family & friends" (like Venmo, i imagine...)...
simplepinoi177 said:
As I understand it, Wallet holds all your "cards" like loyalty cards, gift cards, and transportation passes (metro, train, bus) -- hence "wallet" -- while GPay handles the credit cards for transactions for in-store/shops.
I guess Wallet is the app while GPay might be classified as the process...
Click to expand...
Click to collapse
Just an FYI, but Wallet is just a part of GPay. What @Curiousn00b had said earlier in this thread is correct. GPay can do everything that Google Wallet does - and more. So therefore, GPay can handle credit cards, debit cards, gift cards, loyalty cards, transit passes, tickets, etc.
The reason why Google has released the Google Wallet app - an app specifically for adding your payment cards, transit cards, loyalty cards, etc - is because a large swarm of people were complaining about GPay being too difficult to use (as the newer features were seemingly confusing to the less tech-knowledgeable folks - which is still around 75-80% of the global population). Google had announced this publicly on a blog post around 1-2 years ago.
highgrade said:
Device doesn't meet security requirements
Click to expand...
Click to collapse
Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
SafetyNet
Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!
efkosk said:
Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!
Click to expand...
Click to collapse
I have Play Store, GPay, and Google Wallet on the DenyList and don't have this error.
And yes, Google can easily decide one day to bypass the DenyList or force hardware attestation at which point you would have to choose between your apps and root. It's been a whack a mole game for awhile now and that's just expected to become worse.
EtherealRemnant said:
I have Play Store, GPay, and Google Wallet on the DenyList and don't have this error.
And yes, Google can easily decide one day to bypass the DenyList or force hardware attestation at which point you would have to choose between your apps and root. It's been a whack a mole game for awhile now and that's just expected to become worse.
Click to expand...
Click to collapse
Thanks!
In the meantime, I cleaned the google play cache storage, added the cards again. I haven't received a bad notification yet
Do I understand correctly that at any time without any action on my part (update app, updateOS) my bank apps, gpay can stop working due to root?
efkosk said:
Thanks!
In the meantime, I cleaned the google play cache storage, added the cards again. I haven't received a bad notification yet
Do I understand correctly that at any time without any action on my part (update app, updateOS) my bank apps, gpay can stop working due to root?
Click to expand...
Click to collapse
If you turn off updates, it's extremely unlikely that it would change, but you're also taking added risk when it comes to exploits and I wouldn't recommend this path.
are we talking about an application or OS update?
If it can stop working for me after the next OS update (via pixelflasher, for example), then that is acceptable for me.
But if it can happen to me after an automatic update of the application via Google Play, it's a problem.
Sorry for possibly stupid questions, I'm trying to understand how it works.
Thank you very much for your help and giving of your time.
efkosk said:
are we talking about an application or OS update?
If it can stop working for me after the next OS update (via pixelflasher, for example), then that is acceptable for me.
But if it can happen to me after an automatic update of the application via Google Play, it's a problem.
Sorry for possibly stupid questions, I'm trying to understand how it works.
Thank you very much for your help and giving of your time.
Click to expand...
Click to collapse
Either can happen. There are ways to detect root that get past our attempts to hide it as it is so an app update can add further detection easily. Just ask my Security Service Federal Credit Union app that won't even open on a rooted phone no matter what I do.
Can I "quickly unroot" it by uninstalling magisk? Does it wipe my data? I want rooted, but I need planB in a crisis situation.
Thx for your reply!
Users with root are not afraid of the situation that they ask for a bill in a restaurant and Gpay won't work for them?
efkosk said:
Can I "quickly unroot" it by uninstalling magisk? Does it wipe my data? I want rooted, but I need planB in a crisis situation.
Thx for your reply!
Users with root are not afraid of the situation that they ask for a bill in a restaurant and Gpay won't work for them?
Click to expand...
Click to collapse
Unfortunately removing root just exposes the unlocked bootloader and GPay won't work with that condition either. It's why I rooted in the first place so I could pass SafetyNet again as Discover is 5% with mobile wallet this quarter.
I carry credit cards with me everywhere I go. It's only recently I've started using tap to pay as it wasn't really available in the Denver area. Even now I can only thing of a couple places that take it - namely the liquor store I go to with my husband lol. Interestingly I went to Dollar Tree yesterday and they have added it.
So if I want to unroot, I will lose data, because after re-locking the bootloader, the data is wiped. I'm right?
efkosk said:
So if I want to unroot, I will lose data, because after re-locking the bootloader, the data is wiped. I'm right?
Click to expand...
Click to collapse
Correct. Honestly I wouldn't say you're at immediate risk of having an issue and that dumping root and all that just for a remote possibility isn't worth it.
You can also turn off automatic app updates for the individual apps in the Play Store. As long as you leave automatic updates on for the rest of your apps, the ones you disable individually will just be sitting there showing updates and you can choose to update them when you're ready.