Database Info

Android Pay and Custom ROM

Anyone get Android Pay and Custom ROM working on their rooted and customized Nexus 5 ?
Here are the steps I took in order to add cards and get Android Pay functioning on my phone:
- Get the Google Pay APK from here: http://www.apkmirror.com/apk/google-inc/android-pay/android-pay-1-0-102576552-android-apk-download/
- You'll also need an upgrade for Google Play Services, I was not able to get it through Apple Pay, I had to get it from here:
http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-8-1-14-2244331-238-android-apk-download/
NOTE: have to install Google Play Services that ends in 238 for the N5
Then do the following steps:
- Install Android Pay
- Install Google Play Services
- Clear Data for Android Pay
- Go into SuperSU and unroot
- setup Android Pay
- re-root using SuperSU
So this allowed me to add/manage cards in Android Pay - but some users are getting an error such as:
"MASTERCARD-XXXX can't be used with Android Pay right now " when trying to pay with their phone.
The other item I noted is that after verifying my credit card with the issuing bank - it took several hours (>8) before I received official confirmation that the card was made available for mobile payment.
I'm guessing that it may take a while before the cards are 'activated for mobile payment?
Anyone able to use Android Pay to make a payment on their N5 (rooted, Custom ROM) ?
Note: I'm running on Cataclysm and HellsCore Kernel.

I just received email confirmation from my bank that my card had been added. I did receive verbal confirmation the day I added it, but maybe it takes a few days. The problem now is that I had removed my card and re-added it this morning, before that initial email confirmation came through. Now I don't know if I need to wait for another email confirmation before trying again.

The process worked for me, but I haven't yet tried to make a payment. One note on the steps (although this is probably understood by most who would be going through the process): For re-rooting SuperSU, you may want to clarify this is done by re-installing SuperSU in recovery.

Empty Hand said:
The process worked for me, but I haven't yet tried to make a payment. One note on the steps (although this is probably understood by most who would be going through the process): For re-rooting SuperSU, you may want to clarify this is done by re-installing SuperSU in recovery.
Click to expand...
Click to collapse
All I did was turn back on "Enable Superuser" in SuperSU Free - I did not re-install SuperSu in recovery...

luigidk said:
Anyone get Android Pay and Custom ROM working on their rooted and customized Nexus 5 ?
Here are the steps I took in order to add cards and get Android Pay functioning on my phone:
- Get the Google Pay APK from here: http://www.apkmirror.com/apk/google-...-apk-download/
- You'll also need an upgrade for Google Play Services, I was not able to get it through Apple Pay, I had to get it from here:
http://www.apkmirror.com/apk/google-...-apk-download/
NOTE: have to install Google Play Services that ends in 238 for the N5
Then do the following steps:
- Install Android Pay
- Install Google Play Services
- Clear Data for Android Pay
- Go into SuperSU and unroot
- setup Android Pay
- re-root using SuperSU
So this allowed me to add/manage cards in Android Pay - but some users are getting an error such as:
"MASTERCARD-XXXX can't be used with Android Pay right now " when trying to pay with their phone.
The other item I noted is that after verifying my credit card with the issuing bank - it took several hours (>8) before I received official confirmation that the card was made available for mobile payment.
I'm guessing that it may take a while before the cards are 'activated for mobile payment?
Anyone able to use Android Pay to make a payment on their N5 (rooted, Custom ROM) ?
Note: I'm running on Cataclysm and HellsCore Kernel.
Click to expand...
Click to collapse
I'm getting that those links are broken/don't work.......
EDIT: I've had the 'Unfortunately, Google Play services has stopped' constantly with any iteration of the Google Play Services update I've downloaded. I just dl'd the 'universal' version 240 from the XDA Developers posting , everything else has worked fine but I'm still getting the service stop error. Anyone have any suggestions on how to get this message to stop? When I go to Manage Apps, there's no option to clear data/uninstall updates, only clear cache and disable (and I don't want to disable it, for sure.)

Joshmccullough said:
I'm getting that those links are broken/don't work.......
EDIT: I've had the 'Unfortunately, Google Play services has stopped' constantly with any iteration of the Google Play Services update I've downloaded. I just dl'd the 'universal' version 240 from the XDA Developers posting , everything else has worked fine but I'm still getting the service stop error. Anyone have any suggestions on how to get this message to stop? When I go to Manage Apps, there's no option to clear data/uninstall updates, only clear cache and disable (and I don't want to disable it, for sure.)
Click to expand...
Click to collapse
What device?
Nexus 5 requires either Play services -230 or -238, not -240
Sent from my Nexus 5 using Tapatalk

I fixed the links - but if they fail again - just goto http://www.apkmirror.com/ and find the latest android pay and latest google play services (ending in 238) apks - and use those.

Pure Nexus Project, tried the steps in OP as well as trying exposed modules to hide root. I also tried using bootunlocker to lock the BL and change the tamper flag to stock. Still no luck.

RoyJ said:
Pure Nexus Project, tried the steps in OP as well as trying exposed modules to hide root. I also tried using bootunlocker to lock the BL and change the tamper flag to stock. Still no luck.
Click to expand...
Click to collapse
Supposedly this Xposed module goes the extra mile, and addresses the real obstacle to Android Pay activation: the new SafetyNet API
http://repo.xposed.info/module/com.pyler.nodevicecheck
Sent from my Nexus 5 using Tapatalk

silvertrain78 said:
What device?
Nexus 5 requires either Play services -230 or -238, not -240
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, Nexus 5. I'll have to try 230, nothing else has worked so far. 240 was supposed to be a 'universal' GPServices.....I see a commenter above posted something about a new Xposed module, maybe have to give that a shot, too.
EDIT: Looks like v.238 was the trick, no Google Play Services errors so far. Now I just have to test out Android Pay somewhere.
Does anyone know if you have to somehow choose between Android Pay and Google Wallet when using NFC payment at a terminal?

Joshmccullough said:
Yeah, Nexus 5. I'll have to try 230, nothing else has worked so far. 240 was supposed to be a 'universal' GPServices.....I see a commenter above posted something about a new Xposed module, maybe have to give that a shot, too.
EDIT: Looks like v.238 was the trick, no Google Play Services errors so far. Now I just have to test out Android Pay somewhere.
Does anyone know if you have to somehow choose between Android Pay and Google Wallet when using NFC payment at a terminal?
Click to expand...
Click to collapse
Glad you got it set. FYI, for Nexus 5 the -230 Play services is universal DPI.
I'm pretty sure at the pos terminal you'll only be able to use Android Pay. It has completely assumed all duties of the old Wallet. If you have a Google Wallet physical card you can add it as an option for Pay, but otherwise Wallet is now just for p2p transactions (like PayPal).
Sent from my Nexus 5 using Tapatalk

silvertrain78 said:
Glad you got it set. FYI, for Nexus 5 the -230 Play services is universal DPI.
I'm pretty sure at the pos terminal you'll only be able to use Android Pay. It has completely assumed all duties of the old Wallet. If you have a Google Wallet physical card you can add it as an option for Pay, but otherwise Wallet is now just for p2p transactions (like PayPal).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Has any one been able to get Android pay to work at a pos?
Sent from my LG-V510 using Tapatalk

silvertrain78 said:
Supposedly this Xposed module goes the extra mile, and addresses the real obstacle to Android Pay activation: the new SafetyNet API
http://repo.xposed.info/module/com.pyler.nodevicecheck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Sadly, this still doesn't work.

silvertrain78 said:
What device?
Nexus 5 requires either Play services -230 or -238, not -240
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, Nexus 5. Got it fixed and working as noted above, just needed the right Google Play Services update and then the instructions in the OP worked like a charm.
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
silvertrain78 said:
Glad you got it set. FYI, for Nexus 5 the -230 Play services is universal DPI.
I'm pretty sure at the pos terminal you'll only be able to use Android Pay. It has completely assumed all duties of the old Wallet. If you have a Google Wallet physical card you can add it as an option for Pay, but otherwise Wallet is now just for p2p transactions (like PayPal).
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I just noticed that the old Google Wallet app was auto-removed at some point from my phone (I had both for a while), now I've just got Android Pay and Google Wallet, so that makes complete sense.
FWIW, when I tried adding my Google Wallet card to Android Pay, I initially got the 'you can't use this on your phone'/root error; just unrooted through SU, added the card, re-rooted, no message. I just have to test it out on a POS terminal somewhere and see how it flies.

Joshmccullough said:
Yeah, Nexus 5. Got it fixed and working as noted above, just needed the right Google Play Services update and then the instructions in the OP worked like a charm.
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
I just noticed that the old Google Wallet app was auto-removed at some point from my phone (I had both for a while), now I've just got Android Pay and Google Wallet, so that makes complete sense.
FWIW, when I tried adding my Google Wallet card to Android Pay, I initially got the 'you can't use this on your phone'/root error; just unrooted through SU, added the card, re-rooted, no message. I just have to test it out on a POS terminal somewhere and see how it flies.
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Nexus 5 using Tapatalk

Not working at POS
Finally had an opportunity to use Android Pay at a Whole Foods POS.
Touched my phone to the card reader - and Android Pay popped up - with my default credit card.
Then - I got the dreaded: "Visa-xxxx can't work with Android Pay right now" message.
Seems this is a common issue - so it looks like we'll have to wait a bit for this to work.
I'll continue to try it at places that accept Android Pay - and will update accordingly.
NOTE: one thing was apparent... for me the experience of using my phone to pay - is no better an experience (probably more clunky) - than merely swiping my credit card - which I can probably get out of my pocket and swipe, faster than getting out my phone, unlocking it and positioning it on the reader.
Perhaps the security promises with Android Pay will trump a mag stripe card... but from a user experience standpoint... not that great.

silvertrain78 said:
What ROM are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Cataclysm ROM, most recent version.
---------- Post added at 04:40 PM ---------- Previous post was at 04:37 PM ----------
luigidk said:
Finally had an opportunity to use Android Pay at a Whole Foods POS.
Touched my phone to the card reader - and Android Pay popped up - with my default credit card.
Then - I got the dreaded: "Visa-xxxx can't work with Android Pay right now" message.
Seems this is a common issue - so it looks like we'll have to wait a bit for this to work.
I'll continue to try it at places that accept Android Pay - and will update accordingly.
NOTE: one thing was apparent... for me the experience of using my phone to pay - is no better an experience (probably more clunky) - than merely swiping my credit card - which I can probably get out of my pocket and swipe, faster than getting out my phone, unlocking it and positioning it on the reader.
Perhaps the security promises with Android Pay will trump a mag stripe card... but from a user experience standpoint... not that great.
Click to expand...
Click to collapse
Are you rooted, hence the 'didn't work' problem, or it's just plain not working right now?
Yeah, I've putzed around with the original Google Wallet/NFC payment a few times and I found the same thing was true: it's about as much hassle, maybe even more, as using a regular credit or debit card. At least with the cards you know they're going to work, barring some major snafu; with Google Wallet/Android Pay, maybe the place you're at doesn't accept it as payment, maybe the card vendor isn't on-board with Android Pay yet, maybe your phone's rooted and it doesn't work to begin with, etc. I like the idea of having multiple cards available to use with Google Pay, so I can choose which one I want to use at any given time, but I think there's also a lot of barriers to making phone-based payment the default method of payment for people.
EDIT: Well, initial swing and a miss; I had my Google Wallet card set as the default card to use with Android Pay, and got a message saying that the Google Wallet card wasn't able to be used with Android Pay at this time. I was at McDonald's for lunch and if there wasn't a big line behind me I'd have taken time to switch cards and try again, but as it was I froze up and just went with a physical card. I didn't get a 'you're using a rooted phone, you hAxx0rZ!!!! Stop trying to overthrow capitalism and steal Bitcoins, anarchist!!!' error message, at least, so that's a good thing.

Doing more research on this - there seems to be strong evidence that Android Pay won't work on a rooted/custom rom phone.
Lots of speculation as to whether it is related to an unlocked bootloader, root, custom rom, or some combination...
Has anyone tried this on vanilla N5 ?

I'm using stock and I have play services 238 the latest one and Android pay still says "Google play services have stopped" what do I do?

Here's a thought: maybe it's a server-side activation, and that's why it doesn't work for rooted users who temporarily disable superuser when attempting to add a card?
That's the only thing I can think to explain why some users are able to unroot and flip the switch, while others can't
Sent from my Nexus 5 using Tapatalk

INFO: SafetyNet check in magisk stopped working.

https://twitter.com/topjohnwu/status/1029239685338419200?s=19
https://stackoverflow.com/questions...et-attestation-stop-working/50960333#50960333

hmmm, wonder how long it will take for them to fix this

RiTCHiE007 said:
hmmm, wonder how long it will take for them to fix this
Click to expand...
Click to collapse
I'm more concerned with whether they can fix it. This appears to be an effort to tighten security by Google.

iElvis said:
I'm more concerned with whether they can fix it. This appears to be an effort to tighten security by Google.
Click to expand...
Click to collapse
yea, this whole new key system take a while before they can find a cure

Don't think this will be sorted for a while. A whole new level of security.

I've been getting this too. Play Store still shows "certified" though.

Just used my phone and my gear s3 frontier watch for Google Pay and Samsung pay earlier this afternoon. Rooted with Magisk 16.7 and no issues. Is it happening to some and not others for the failed SafetyNet checks?

Looks like it's an issue with API calls failing :
https://stackoverflow.com/questions/50960332/why-did-safetynet-attestation-stop-working/50960333

You can test it with this app...
The beta version is optimized for the new Api...?
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
Sent from my ONEPLUS A6003 using XDA Labs

Or can use the new release of "SafetyNet Helper Sample" app, it has just been updated with latest API and my O+6 now passes the test.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

zyvex_14 said:
Or can use the new release of "SafetyNet Helper Sample" app, it has just been updated with latest API and my O+6 now passes the test.
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Click to expand...
Click to collapse
So how is this app working but magisk is failig?

Static-xy said:
So how is this app working but magisk is failig?
Click to expand...
Click to collapse
Because of the API version.
Magisk used an old one which Google doesn't validate anymore. Developper is working on an update of Magisk, he succeed to pass now Safetynet but not released yet due to a question of key validation (more details of his Twitter account)

iElvis said:
I'm more concerned with whether they can fix it. This appears to be an effort to tighten security by Google.
Click to expand...
Click to collapse
This is not a Magisk Issue. MagiskHide works with the latest API (check Safetynet Sample tester from the play store) and Play Store itself also works with the new API. The problem is that ALL the applications on the play store have to upgrade to the new API themselves, and then, they will work! because MagiskHide works with the new API. So nothing to fix by Magisk side here, all the devs must update their apps on the play store to validate their apps, or the Google Server side returns KO due to old API usage, not due to Magisk.
The devs just have to recompile their apps on the play store to use the new API and re-publish, nothing else. Of course the problem here is that everyone have to wait for them to update.. this seems a derp by Google.. I wonder if they really wanted to kill Magisk with this move and they risk big time, and Magisk just patched it on speedlight time and now someone at Google is having a bad time.

safety.net check works with this unofficial magisk:
https://forum.xda-developers.com/app...built-t3521901

Toni Moon said:
safety.net check works with this unofficial magisk:
https://forum.xda-developers.com/app...built-t3521901
Click to expand...
Click to collapse
fault signal
404 Page Not Found

https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
https://www.htcmania.com/showthread.php?t=1435264

Google Pay not working with Magisk, despite trying everything

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

Question Google wallet quick setting tile says" wallet unavailable." [SOLVED]

I have a pixel 7 pro. Yesterday I had to clear the cache and data on Google Play services. After that the Google wallet, quick setting tile as well as the shortcut on my lock screen are gone. The quick setting tile is great out and says" wallet unavailable." I have tried clearing data and cache on the wallet and GPay. Nothing will work. What do I do?
I can add cards and ready it for NFC payments. To use it though. I would have to open my phone and open the app every time. The quick setting tile and lock screen route are much better.

Is your device rooted?

Try using the safetynet-fix 2.0 mod and shamiko (doesn't require lsposed, just a module made by them).
To use shamiko you turn off "Enforce DenyList" before flashing as shamiko module does that using the "Configure DenyList" and hides more aspects of magisk/zygisk.
I have wallet working fine.
I have not added any Google apps to DenyList.

V0latyle said:
Is your device rooted?
Click to expand...
Click to collapse
Yes. But I'm able to add a card and even to turn on scanning to pay. I just need to open the app. I wasn't required to do this before.
TotallyAnxious said:
Try using the safetynet-fix 2.0 mod and shamiko (doesn't require lsposed, just a module made by them).
To use shamiko you turn off "Enforce DenyList" before flashing as shamiko module does that using the "Configure DenyList" and hides more aspects of magisk/zygisk.
I have wallet working fine.
I have not added any Google apps to DenyList.
Click to expand...
Click to collapse
I have the latest safety net fix. I am not using shamiko. I didn't need it before. Idk what would have changed to require it now.

Schroeder09 said:
I have the latest safety net fix. I am not using shamiko. I didn't need it before. Idk what would have changed to require it now.
Click to expand...
Click to collapse
You *checks notes* reported a problem and asked for helped and turned down the first suggestion given. Mkay.

TotallyAnxious said:
You *checks notes* reported a problem and asked for helped and turned down the first suggestion given. Mkay.
Click to expand...
Click to collapse
It's more of a question. You don't have to be defensive. Why all of a sudden is this required when it wasn't before? Is Google known to do things on the server side that randomly breaks the magisk hide functionality? I know people struggle with it a lot, but it's usually been pretty stable for me.

Schroeder09 said:
It's more of a question. You don't have to be defensive. Why all of a sudden is this required when it wasn't before? Is Google known to do things on the server side that randomly breaks the magisk hide functionality? I know people struggle with it a lot, but it's usually been pretty stable for me.
Click to expand...
Click to collapse
Google is known to do this. Server side updates.
You didn't ask a question. You said I'm not going to using shamiko. Which is a complete rebuff of my suggestion.
Edit: magisk hide? Are you using magisk delta and or other unofficial magisk build?

Shamiko generally isn't required unless you're trying to specifically hide root, which is not necessary for Google Wallet, which relies exclusively on Play Integrity to report device state. I try to ensure I fully understand what the problem is before I offer solutions.
@Schroeder09 have you tried clearing Wallet data? You may have to re-add cards but it sounds like a bug
Schroeder09 said:
I have the latest safety net fix. I am not using shamiko. I didn't need it before. Idk what would have changed to require it now.
Click to expand...
Click to collapse
Please note that SafetyNet has been discontinued and replaced by Play Integrity. More information here. Just for the sake of eliminating possibilities, can you download Play Integrity Checker and post your response? You should have BASIC and DEVICE green, STRONG red.

V0latyle said:
Well...to be fair, it seems like your response assumed he was having a certification/attestation failure, and threw a bunch of unnecessary stuff at him. Shamiko generally isn't required unless you're trying to specifically hide root, which is not necessary for Google Wallet, which relies exclusively on Play Integrity to report device state.
Let's not be disrespectful, folks.
@Schroeder09 have you tried clearing Wallet data? You may have to re-add cards but it sounds like a bug
Please note that SafetyNet has been discontinued and replaced by Play Integrity. More information here. Just for the sake of eliminating possibilities, can you download Play Integrity Checker and post your response? You should have BASIC and DEVICE green, STRONG red.
Click to expand...
Click to collapse
I made a suggestion and explained my suggestion. That's not throwing too much at someone.
If you read the original post you'd would see that they cleared data already.

Given that everything was working prior, it sounds like Shamiko won't help in this particular circumstance as this isn't a attestation/certification issue.
@Schroeder09 since this happened after clearing data for Google Play Services (which removes your Google account) you might have to basically start over with apps that require Google sign in. This will be a pain in the butt, but may be worth a try:
Manually remove your Google account
Force stop and clear data for Google Play Services, GPay, Play Store, and Wallet
Reboot
Add your Google account
Open GPay, Play Store, and Wallet, and set everything back up
Reboot again
Basically, clearing data for Play Services has ripple effects that can cause problem in dependent apps, since they use the GMS suite to access your Google account data

TotallyAnxious said:
Google is known to do this. Server side updates.
You didn't ask a question. You said I'm not going to using shamiko. Which is a complete rebuff of my suggestion.
Edit: magisk hide? Are you using magisk delta and or other unofficial magisk build?
Click to expand...
Click to collapse
What I meant was I currently do not have it. I already have safety net fix 2.3.1 and what's always been enough. Not that I will not use it. I didn't mean that.
I have YASNAC and integrity checker. Both pass. Google Play store says my device is certified. This happened after clearing the cache and data from Google Play services. That's all I did. Again, the apps themselves are functioning. The quick tile and the lock screen access for the wallet are what is no longer functioning.

V0latyle said:
Again, mind your tone, disrespect will not be tolerated here.
You offered a solution without understanding what the problem is, and from my own experience, it sounds like Shamiko won't help in this particular circumstance
@Schroeder09 since this happened after clearing data for Google Play Services (which removes your Google account) you might have to basically start over with apps that require Google sign in. This will be a pain in the butt, but may be worth a try:
Manually remove your Google account
Force stop and clear data for Google Play Services, GPay, Play Store, and Wallet
Reboot
Add your Google account
Open GPay, Play Store, and Wallet, and set everything back up
Reboot again
Basically, clearing data for Play Services has ripple effects that can cause problem in dependent apps, since they use the GMS suite to access your Google account data
Click to expand...
Click to collapse
Delete my posts if you want act this way.

V0latyle said:
Again, mind your tone, disrespect will not be tolerated here.
You offered a solution without understanding what the problem is, and from my own experience, it sounds like Shamiko won't help in this particular circumstance
@Schroeder09 since this happened after clearing data for Google Play Services (which removes your Google account) you might have to basically start over with apps that require Google sign in. This will be a pain in the butt, but may be worth a try:
Manually remove your Google account
Force stop and clear data for Google Play Services, GPay, Play Store, and Wallet
Reboot
Add your Google account
Open GPay, Play Store, and Wallet, and set everything back up
Reboot again
Basically, clearing data for Play Services has ripple effects that can cause problem in dependent apps, since they use the GMS suite to access your Google account data
Click to expand...
Click to collapse
I did clear cache and data from Google pay and g pay after this happen. Yes, I did have to re-add the cards and set everything back up. I did not remove my account from the Google app. I will do them all simultaneously and report back. Thanks.

TotallyAnxious said:
Delete my posts if you want act this way.
Click to expand...
Click to collapse
Folks, please try to stay on topic and refrain from personal quibbles. If you have a concern that is not related to the content of the thread or its posts, then this is not the place for it. If you have a specific comment about V0latyle's advice, you are more than welcome to raise it here, but I ask that you do so in a way that is civil and reasonable.
Thanks for helping to keep the board clean.

Schroeder09 said:
I did clear cache and data from Google pay and g pay after this happen. Yes, I did have to re-add the cards and set everything back up. I did not remove my account from the Google app. I will do them all simultaneously and report back. Thanks.
Click to expand...
Click to collapse
Right, I think you may need to set things back up in a specific order though. Try the steps I suggested.
I want to reiterate that while I don't have anything in particular against Shamiko, I don't think it will help in this circumstance because you're already passing Play Integrity. Shamiko is intended to help hide Magisk, Zygisk, and the su binary, all of which are not necessary for Google apps.

I just checked and Wallet is working fine for me without Shamiko. The only thing I have installed is Displax's SafetyNet fix mod and I've added all Google apps to DenyList (may not be necessary but it doesn't break anything either) including both Wallet and GPay since I have both apps on my phone.

I think we all might be getting tunnel vision into thinking this is a SafetyNet or Magisk issue -- when I think it could be Wallet and/or a bug connecting it to its Quick Tile...
I'm thinking you should try an older version of Wallet & GPay [Google Pay] (APKMirror would be a good resource to look at) and see if it still doesn't show up with those; maybe a recent update is causing some kind of bug/glitch/incompatibility...
Also, if not Wallet or Magisk, I'm thinking since this had all started with Google Play Services, it might still have to do with that more than anything else. I recall myself when I was attempting some other things, I cleared cache & data of Services, Services Framework, and Play Store and found that my Wallet had been reset as well (even though I did not clear its data); Also I think I do remember seeing the quick tile as unavailable. Maybe re-establishing Play Services & Framework need to be done before anything as well. I know Play Store didn't want to work right until I cleared data twice more on Play Services...
If it is root, I would suggest flashing the stock init_boot back and removing/uninstalling Magisk and seeing if it would still cause the issue -- although, now that I think of it, will Wallet put up a stink just for having the bootloader unlocked? because if it does, I wouldn't re-lock the bootloader just for this and would instead trying other hide-root methods instead...
Also, a thought -- You could try other Quick Tile apps/customizers to see if they can't get a proper Quick Tile for Wallet working. It might show whether any/all Quick Tiles towards it are having an issue or just the Wallet app...
I dunno if any of this will get anything working properly, but it's just some ideas to help troubleshoot and maybe identify/narrow-down where the issue might truly lie...good luck!

V0latyle said:
Given that everything was working prior, it sounds like Shamiko won't help in this particular circumstance as this isn't a attestation/certification issue.
@Schroeder09 since this happened after clearing data for Google Play Services (which removes your Google account) you might have to basically start over with apps that require Google sign in. This will be a pain in the butt, but may be worth a try:
Manually remove your Google account
Force stop and clear data for Google Play Services, GPay, Play Store, and Wallet
Reboot
Add your Google account
Open GPay, Play Store, and Wallet, and set everything back up
Reboot again
Basically, clearing data for Play Services has ripple effects that can cause problem in dependent apps, since they use the GMS suite to access your Google account data
Click to expand...
Click to collapse
Completed and still no dice. Guess I'll just do a fresh install at the next update and wipe everything.
EDIT: it did work! It's taken 2-5 minutes to load but the card is now in the QS tile and on the lock screen. Thank you.

Schroeder09 said:
Completed and still no dice. Guess I'll just do a fresh install at the next update and wipe everything.
EDIT: it did work! It's taken 2-5 minutes to load but the card is now in the QS tile and on the lock screen. Thank you.
Click to expand...
Click to collapse
Glad to help.

Question Wallet not working

I'm on a rooted phone and I have the safety net fix v2.3.1 mod v3.
It says your device doesn't support contactless payments. Sometimes says try again. I've tried clearing cache for the wallet app play services and play store, didn't work.
What to do ?

You've the answer in your hand
Wallet is being more strictly about rooted/modded device.
SafetyNet is deprecated and now Google use a new method to check it.

zSyntex said:
You've the answer in your hand
Wallet is being more strictly about rooted/modded device.
SafetyNet is deprecated and now Google use a new method to check it.
Click to expand...
Click to collapse
Is there a way to bypass or is it just not possible at this time(s, until someone finds a way)

TheShinyEnd said:
Is there a way to bypass or is it just not possible at this time(s, until someone finds a way)
Click to expand...
Click to collapse
Not for the moment. Every app that use the new method couldn't work with that bypass

zSyntex said:
Not for the moment. Every app that use the new method couldn't work with that bypass
Click to expand...
Click to collapse
Will downgrading the wallet app work?

TheShinyEnd said:
Will downgrading the wallet app work?
Click to expand...
Click to collapse
No, it's server side.

zSyntex said:
No, it's server side.
Click to expand...
Click to collapse
Okay, thanks for the information.

TheShinyEnd said:
I'm on a rooted phone and I have the safety net fix v2.3.1 mod v3.
It says your device doesn't support contactless payments. Sometimes says try again. I've tried clearing cache for the wallet app play services and play store, didn't work.
What to do ?
Click to expand...
Click to collapse
zSyntex might be incorrect.
USNF version you are using is outdated. Also, for the Pixel 6 & 7, using Displax's Mod is more successful (I've hyperlinked to the post where you can get information to it in the quote below;post 3223).
In any case, I suggest you do what I have quoted below... I am able to get contactless payments working with the latest Wallet version on the March firmware doing the method below...
simplepinoi177 said:
you might want to check out Post #3223, for Pixel 6 & Pixel 7 particularly, that mod works out real well...
And of course the obligatory clear cache & data of Google Play Protect, Google Framework, Google Play Services, Wallet, Gpay, all these apps' ticks in their respective sub-menu is ticked in Zygisk DenyList, and be sure to restart (personal experience; I did all that and couldn't add card, but after restart I could). Also, I passed safetynet and successfully added card, but had to call the banks on two cards to get it working without error at a store...
Click to expand...
Click to collapse

simplepinoi177 said:
zSyntex might be incorrect.
USNF version you are using is outdated. Also, for the Pixel 6 & 7, using Displax's Mod is more successful (I've hyperlinked to the post where you can get information to it in the quote below;post 3223).
In any case, I suggest you do what I have quoted below... I am able to get contactless payments working with the latest Wallet version on the March firmware doing the method below...
Click to expand...
Click to collapse
Okay.. I'll try this method, thanks for the update.

simplepinoi177 said:
zSyntex might be incorrect.
USNF version you are using is outdated. Also, for the Pixel 6 & 7, using Displax's Mod is more successful (I've hyperlinked to the post where you can get information to it in the quote below;post 3223).
In any case, I suggest you do what I have quoted below... I am able to get contactless payments working with the latest Wallet version on the March firmware doing the method below...
Click to expand...
Click to collapse
I'm not wrong. Google deprecated SafetyNet officially, check its Source Blog.
I don't know if dev updated the patcher
Some device need to patch the bootloader while others not

Yeah, I see.. they've made a post - they are going to switch to "Play Integrity API" from their "SafetyNet Attestation API" and will fully enforce it in June of 2024.
Discontinuing the SafetyNet Attestation API | Android Developers
developer.android.com

My wallet still works...

zSyntex said:
Not for the moment. Every app that use the new method couldn't work with that bypass
Click to expand...
Click to collapse
zSyntex said:
I'm not wrong. Google deprecated SafetyNet officially, check its Source Blog.
I don't know if dev updated the patcher
Some device need to patch the bootloader while others not
Click to expand...
Click to collapse
Yes, it's been a long time coming that Google has depreciated SafetyNet. Most apps don't even employ that protocol in "stability" checks. But the devs of UniversalSafetyNetFix had long anticipated that as well. I believe they only kept the name because that is what everyone knows it as; it's not to mean that it only applies to SafetyNet. This "bypass"(USNF) does still work.
TheShinyEnd said:
Yeah, I see.. they've made a post - they are going to switch to "Play Integrity API" from their "SafetyNet Attestation API" and will fully enforce it in June of 2024.
Discontinuing the SafetyNet Attestation API | Android Developers
developer.android.com
Click to expand...
Click to collapse
Yes, this is true, but as I've just stated, it has been a long time coming and has been anticipated by the devs for almost as long.
That is why, in THIS DEFACTO CENTRAL THREAD on everything outside of stock (by roirraW "edor" ehT) actually presents using the USNF Mod (that works particularly with our Pixel 6 & 7's in spoofing not just SafetyNet but Play Integrity API) but also strongly suggests using the "Play Integrity API Checker" app after implementing the mod/fix to make sure you pass enough of the checks (everything but STRONG_INTEGRITY; is explained in the thread why that isn't to be worried about)! I mean, doing what was directed in the thread and what I had quoted before, I'm like @gpvechhi and my contactless payments in Wallet work, even though i am rooted -- only using USNF Mod and Zygisk DenyList...

TheShinyEnd said:
I'm on a rooted phone and I have the safety net fix v2.3.1 mod v3.
It says your device doesn't support contactless payments. Sometimes says try again. I've tried clearing cache for the wallet app play services and play store, didn't work.
What to do ?
Click to expand...
Click to collapse
Try with USNF v2.4.0 mod v1.2 (Displax).

So I tried to use my credit card on my phone, says your device doesn't support contactless payments. the issue still persists, by any chance I need to re-add the wallet's information? - Already have it saved.
YASNAC - Passing
Play Integrity - Passing
I've resetted cache for all the play related apps and services, wallet as well, still nothing.
Sometimes, I do notice that the GMS(Google Play Services), com.google.android.gms, Is turned off in configure-deny list of magisk, I have it turned on, but probably after a phone restart or something related, it turns off for some reason.
Is GMS in the enforced deny list a necessity ?
And do I need to re-add my wallet information ?

TheShinyEnd said:
So I tried to use my credit card on my phone, says your device doesn't support contactless payments. the issue still persists, by any chance I need to re-add the wallet's information?
Click to expand...
Click to collapse
I think this might be another issue than root detection...
I spoke a little about it at the bottom of my quoted post:
simplepinoi177 said:
you might want to check out Post #3223, for Pixel 6 & Pixel 7 particularly, that mod works out real well...
And of course the obligatory clear cache & data of Google Play Protect, Google Framework, Google Play Services, Wallet, Gpay, all these apps' ticks in their respective sub-menu is ticked in Zygisk DenyList, and be sure to restart (personal experience; I did all that and couldn't add card, but after restart I could). Also, I passed safetynet and successfully added card, but had to call the banks on two cards to get it working without error at a store...
Click to expand...
Click to collapse
I recall running into that "doesn't support contactless payments" because it needed to be activated/enabled in the bank's system -- I had to call the bank to confirm things and get it working. This may be the case here.
TheShinyEnd said:
Sometimes, I do notice that the GMS(Google Play Services), com.google.android.gms, Is turned off in configure-deny list of magisk, I have it turned on, but probably after a phone restart or something related, it turns off for some reason.
Is GMS in the enforced deny list a necessity ?
And do I need to re-add my wallet information ?
Click to expand...
Click to collapse
So, if you are using USNF Displax Mod (which I linked to in the quote as Post #3223 and Fishawy suggested), the mod takes care of a lot of the GMS things under the hood to bypass the root checks that, as a result/side-effect, GMS and some other Google services ends up not staying "ticked" in the deny list after a reboot.
TheShinyEnd said:
...by any chance I need to re-add the wallet's information? - Already have it saved.
YASNAC - Passing
Play Integrity - Passing
I've resetted cache for all the play related apps and services, wallet as well, still nothing.
Click to expand...
Click to collapse
You should try again what I quoted; if all done correctly, you would need to re-add the cards and wallet's information again -- so it seems that you may have not since you mention needing to still "need to re-add". Also, you can't just reset the cache, but you must clear data as well (as directed in the quote I left).
Fishawy said:
Try with USNF v2.4.0 mod v1.2 (Displax).
Click to expand...
Click to collapse
It really is most important you try what I quoted and what Fishawy suggested -- it's most likely why things aren't working for you as they are working for most of us.
TheShinyEnd said:
Okay.. I'll try this method, thanks for the update.
Click to expand...
Click to collapse
You stated this, but have yet to indicate if you implemented the Displax Mod instead of the regular USNF.
At worst, if you are implementing Displax's mod and passing everything, and have done the steps I quoted before (particularly ticking sub-selections), you may need to completely re-initialize Google Services and Wallet, which I found the best directions on how to do quoted below...
V0latyle said:
Given that everything was working prior, it sounds like Shamiko won't help in this particular circumstance as this isn't a attestation/certification issue.
...since this happened after clearing data for Google Play Services (which removes your Google account) you might have to basically start over with apps that require Google sign in. This will be a pain in the butt, but may be worth a try:
Manually remove your Google account
Force stop and clear data for Google Play Services, [Google Frameworks, Google Play Protect,] GPay, Play Store, and Wallet
Reboot
Add your Google account
Open GPay, Play Store, and Wallet, and set everything back up
Reboot again
Basically, clearing data for Play Services has ripple effects that can cause problem in dependent apps, since they use the GMS suite to access your Google account data
Click to expand...
Click to collapse

simplepinoi177 said:
I think this might be another issue than root detection...
I spoke a little about it at the bottom of my quoted post:
I recall running into that "doesn't support contactless payments" because it needed to be activated/enabled in the bank's system -- I had to call the bank to confirm things and get it working. This may be the case here.
So, if you are using USNF Displax Mod (which I linked to in the quote as Post #3223 and Fishawy suggested), the mod takes care of a lot of the GMS things under the hood to bypass the root checks that, as a result/side-effect, GMS and some other Google services ends up not staying "ticked" in the deny list after a reboot.
You should try again what I quoted; if all done correctly, you would need to re-add the cards and wallet's information again -- so it seems that you may have not since you mention needing to still "need to re-add". Also, you can't just reset the cache, but you must clear data as well (as directed in the quote I left).
It really is most important you try what I quoted and what Fishawy suggested -- it's most likely why things aren't working for you as they are working for most of us.
You stated this, but have yet to indicate if you implemented the Displax Mod instead of the regular USNF.
At worst, if you are implementing Displax's mod and passing everything, and have done the steps I quoted before (particularly ticking sub-selections), you may need to completely re-initialize Google Services and Wallet, which I found the best directions on how to do quoted below...
Click to expand...
Click to collapse
I am indeed using "USNF v2.4.0 Mod v1.2 (Displax)", resetted data & cache.. I'll re-add the cards see how that goes.
Thank you very much for the help, much appreciated !

TheShinyEnd said:
I am indeed using "USNF v2.4.0 Mod v1.2 (Displax)", resetted data & cache.. I'll re-add the cards see how that goes.
Thank you very much for the help, much appreciated !
Click to expand...
Click to collapse
Resetting the data & cache for every single Google app in the quoted steps (there are 6) should remove all the cards in the Wallet app anyways...so that'd be the next step regardless...
Good luck!