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!
Related
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
Please help Magisk Safetynet is failed
Google seems having updated SafetyNet today...
What an annoying thing...
Same thing here. Was all good until about an hour ago. Highly irritating...
Try this, worked for me:
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
@Displax provided the perfect fix. It worked for many ppl. Check it out. I just flashed the USFN v1.2.0-MOD and it worked.
bzkrtSLAYER said:
Please help Magisk Safetynet is failed
Click to expand...
Click to collapse
THE SAFETYNET ATTESTION API NOW NO LONGER QUERIES CTS PROFILE ON ANDROID DEVICE BUT SUCH ONE STORED ON GOOGLE SERVERS BY OEM/CARRIER.
I followed the embedded video and it works perfectly! Beware, though, that when you clear Play Store data, auto-updating of apps will get enabled, so if you don't want your apps being updated, go to airplane mode and change that setting in the play store before re-connecting.
I also had the issue that at first the play store wouldn't recognize the installed apps and wouldn't offer manual updates for those that are available. Killing and re-starting play store did the trick.
tOz666 said:
Try this, worked for me:
Click to expand...
Click to collapse
This worked for me, albeit it has slowed my phone down quite a bit (at least, for the first 15 minutes or so after booting. It settles down after a while). I'll take it, though.
ttar ttar said:
@Displax provided the perfect fix. It worked for many ppl. Check it out. I just flashed the USFN v1.2.0-MOD and it worked.
Click to expand...
Click to collapse
I suppose that you mean this https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85573473
Didnt work for me
Pixel 5a
Also didn't work for me...
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.
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.
So I just bought my google pixel 7 pro and promptly rooted it, I set Magisk up and even got the safety net fix mod version. I also passed YASNAC so im trying to figure out why I can see certain apps from the google playstore like for instance KWGT. I live in the states so it makes no sense to me as to why i wouldnt be able to see apps.
I am also getting an error when trying to sign in to apps like youtube and youtube music
Idk at this time exactly what all I cant find, but i can tell something is amok, can someone help me out here?
Kai2150 said:
So I just bought my google pixel 7 pro and promptly rooted it, I set Magisk up and even got the safety net fix mod version. I also passed YASNAC so im trying to figure out why I can see certain apps from the google playstore like for instance KWGT. I live in the states so it makes no sense to me as to why i wouldnt be able to see apps.
I am also getting an error when trying to sign in to apps like youtube and youtube music
Idk at this time exactly what all I cant find, but i can tell something is amok, can someone help me out here?
Click to expand...
Click to collapse
Usually not seeing apps in Play Store is because of Play Protect certification not being "Device is certified". This is caused by rooting. Usually USNF MOD (2.4.0-MOD_1.2 as of this writing) is enough to take care of this type of issue.
So first things first, check on the status of your device; check your Play Protect certification (in Play Store settings, About if you aren't aware), what you pass in apps YASNAC and Play Integrity API Checker. I'm guessing you're not gonna pass everything you need to (everything but STRONG_INTEGRITY), and if you don't, you most likely need to reset a bunch of Google services to get it reset and re-established to see everything...
I can walk you through that if it ends up being that way...
simplepinoi177 said:
Usually not seeing apps in Play Store is because of Play Protect certification not being "Device is certified". This is caused by rooting. Usually USNF MOD (2.4.0-MOD_1.2 as of this writing) is enough to take care of this type of issue.
So first things first, check on the status of your device; check your Play Protect certification (in Play Store settings, About if you aren't aware), what you pass in apps YASNAC and Play Integrity API Checker. I'm guessing you're not gonna pass everything you need to (everything but STRONG_INTEGRITY), and if you don't, you most likely need to reset a bunch of Google services to get it reset and re-established to see everything...
I can walk you through that if it ends up being that way...
Click to expand...
Click to collapse
Yeah it says I'm not certified, tho Yasnac says I pass the basic check. I'll try using the Play Integrity API checker and get back to you and yeah if you could walk me through that would be a big help
simplepinoi177 said:
Usually not seeing apps in Play Store is because of Play Protect certification not being "Device is certified". This is caused by rooting. Usually USNF MOD (2.4.0-MOD_1.2 as of this writing) is enough to take care of this type of issue.
So first things first, check on the status of your device; check your Play Protect certification (in Play Store settings, About if you aren't aware), what you pass in apps YASNAC and Play Integrity API Checker. I'm guessing you're not gonna pass everything you need to (everything but STRONG_INTEGRITY), and if you don't, you most likely need to reset a bunch of Google services to get it reset and re-established to see everything...
I can walk you through that if it ends up being that way...
Click to expand...
Click to collapse
I also checked with Play Integrity API checker and it passed everything but strong integrity.
simplepinoi177 said:
Usually not seeing apps in Play Store is because of Play Protect certification not being "Device is certified". This is caused by rooting. Usually USNF MOD (2.4.0-MOD_1.2 as of this writing) is enough to take care of this type of issue.
So first things first, check on the status of your device; check your Play Protect certification (in Play Store settings, About if you aren't aware), what you pass in apps YASNAC and Play Integrity API Checker. I'm guessing you're not gonna pass everything you need to (everything but STRONG_INTEGRITY), and if you don't, you most likely need to reset a bunch of Google services to get it reset and re-established to see everything...
I can walk you through that if it ends up being that way...
Click to expand...
Click to collapse
Something else I just figured out is Google Play Services keeps unchecking itself in the DenyList, from what I can tell it's after each restart.
I went ahead and cleared Google Play store, Google Play services, and Google wallet l, idk what else to clear but I did it in airplane mode restarted then turned off airplane mode
Kai2150 said:
Something else I just figured out is Google Play Services keeps unchecking itself in the DenyList, from what I can tell it's after each restart.
I went ahead and cleared Google Play store, Google Play services, and Google wallet l, idk what else to clear but I did it in airplane mode restarted then turned off airplane mode
Click to expand...
Click to collapse
After clearing it doesn't show if the device is certified or not so... Idk what to do here
Kai2150 said:
Something else I just figured out is Google Play Services keeps unchecking itself in the DenyList, from what I can tell it's after each restart.
Click to expand...
Click to collapse
If you are using an USNF mod, then that is normal. The mod won't work properly if Google Play Services is checked so it unchecks it and "denies" it in the background.
Lughnasadh said:
If you are using an USNF mod, then that is normal. The mod won't work properly if Google Play Services is checked so it unchecks it and "denies" it in the background.
Click to expand...
Click to collapse
I figured it out, I cleared everything and got it certified so we are straight now ty
Kai2150 said:
I figured it out, I cleared everything and got it certified so we are straight now ty
Click to expand...
Click to collapse
I'm glad it got figured out...
Sorry I only now had time to come in and help...
basically, it went as I was going to say & predict; with you passing everything, it gets tricky -- after you clear data and cache on multiple google services, you'll find that Play Store won't state anything about it being certified, and usually it randomly comes back as certified after some time. This is the experience I've read of other members here.
But alls well that ends well...hopefully everything now will be problem free...