yashsingh1/xdaforums huggingface dataset:
[Magisk] joeyddr:
It was working on the latest play services for me... if i clear the app data on play services and reboot it works for a few days.
[Magisk] D-m-x:
To be fair, there is some maintenance going on on Googles end. In Germany at least paying with PayPal through Google pay suddenly was hit and miss about 2 weeks ago. For some it worked for some it didn't. Or even just worked only sometimes. They confirmed they were doing something behind the scenes and it would take some time (at least PayPal did). Google just did Google things and didn't care like usual. Maybe there is something going on.

Gesendet von meinem Nexus 5 mit Tapatalk
[Magisk] Phoenix Wright:
I've been looking into this, here's what I did and found out:

A few days after updating to 18.2 canary I tried enabling in-store payments and Google Pay said the phone was rooted or altered. I then wiped /data/data/com.google.android.gms in recovery, and it worked again for approximately 12 hours (with default MagiskHide settings, only "unstable" enabled in the list). I then wiped data again and enabled MagiskHide on all the play services + Google Pay, and it worked for several days, so I considered it to be a pass. I then disabled MagiskHide on Google Pay and it still worked for several days. Thus:

- the result of the google pay root check is stored in the /data/data/com.google.android.gms folder (Google Play Services data folder), for all other apps Android just wipes the /data/data folder but that's not the case for Play Services as there's a custom UI for deleting data which doesn't seem to remove everything, and obviously this data isn't removed. You can wipe /data/data/com.google.android.gms in recovery to remove the result of the check.

- the check is done apparently randomly in the span of a day or two. That's probably to achieve what happened in this thread, conflicting reports and people having no idea what triggers the check and how to deal with it

- the check is done by Google Play Services, but by something other than the "unstable" (safetynet) process.

- not sure about this one, but given that Magisk 18.1 and older have imperfect MagiskHide functionality (the hiding can be "raced" and thus defeated with some tricks, according to John himself), it's possible Google is also doing that. Using 18.2 is your best bet as it enables hiding on a process as soon as possible.

I'm now trying to pinpoint which component of play services is doing the check, so the default magiskhide list can be updated (I'll report on github once I'm sure).
[Magisk] chris2ferz:
can you mention here too? (don't know your github link)

seems after i cleared data for google play services - some of my notifications aren't working (hate side effects)
[Magisk] andrewwdai:
folks, please disable this service in Play Store apk. GMS stays on 14.7 version for 2 days and counting.
[Magisk] Ramone360:
How do I get to those settings?
[Magisk] sam0056:
Does anyone have Google pay goes to black screen issue while trying to setup just after entering the last 3 digits of card when it says contacting your bank.
[Magisk] andrewwdai:
There are several apps, including Android Tools, Service Disabler, etc. All of them need root.

I will report tomorrow if it holds. So far, it allows me to add cards and do transactions. At least I know what caused GPay not working!
[Magisk] tom1807:
Something doesn't add up, I used GPS v15.0.90 since end of January and used GP last time on March 6, 2019. Using Magisk 17.3 and MM 6.1.

MY GPS version is not updated to any newer version yet, however today was the first time I couldn't use. GP.

So from end of January until March 6, I was able to use GP with v15.0.90, the only new I did was enabling GP on my watch last Friday, but still then I had no problems to add the card again.

Cheers

Tom
[Magisk] swour:
My experience as well. I'm guessing it took until now for the server side changes to roll out to my device. I won't be bothering with Google Pay anymore, nothing fixes this for longer than a few days at most anyway.
[Magisk] marklar666:
I got tired of fighting with this **** every week or two so I uninstalled Magisk (unroot), Magisk Manager, flashed stock firmware but this f..ng Android Pay still says my phone is rooted! Arrgghhh!!!

Any advice how to make it working again?
[Magisk] bmcgarry84:
I just wiped my phone, installed stock image and updated all apps. Without root, Magisk, or even TWRP I cannot add a card to GPay. Only modification would be an unlocked bootloader.
[Magisk] rafikowy:
Same here.

Looks like unlocked bootloader is enough to be blocked in GPay.
[Magisk] jcmm11:
[MENTION=4819188]marklar666[/MENTION] [MENTION=4378107]bmcgarry84[/MENTION] [MENTION=5750370]rafikowy[/MENTION]

If the system determines you have an unlocked bootloader it will flag you. One thing you can try is to install a custom kernel - they (all as far as I know, it's been available for ages) have a patch that will prevent the system from seeing the unlocked bootloader. A custom kernel in and of itself will not cause the system to flag you.
[Magisk] Phoenix Wright:
If you don't wipe GMS data, even if you unroot and everything it'll still have the cached result from when you were rooted (as I said, the check is done randomly). I'm not even sure they redo the check after it fails once.
[Magisk] infatality:
I doubt so.. I'm using a custom kernels which hide the bootloader.. Still unable to add any cards.. Even without magisk..
[Magisk] Senliast:
For those, who cannot remove updates - try to disable device admin for G Pay and Device lost, then delete data of Play Services, then uninstall updates. Please note, that you will lose all your cards in G Pay.
[Magisk] bobbillbell:
Followed all instructions and worked well, thanks!! However...

Google Pay : 2.83.235070858, Play Services : 14.7.99 (no problems), Magisk 18.1

Tried updating Play Services to version 16.0.86 with Magisk 18.1. This worked for a few days (4) but has stopped again, and adding a card is denied.

I've now reverted back to Pay 2.83 and Play Services 14.7.99 with Magisk 18.1, and was able to add a card again, which usually means it will work when trying to pay in store/s. Will check in again in a couple of days if it stays stable.

In the meantime, the workaround guide makes the statement "Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet". I'm happy to follow that rule but can anyone tell me if there's a way to check what play services versions are bypassed by which Magisk versions, so we know when it's safe to update each?
[Magisk] BillGoss:
I tend to switch ROMs on my phone. I run stock OxygenOS 5.0.8 and LineageOS 16.0.

On both ROMs I use Magisk 18.1 and I have not hidden Google Pay nor hidden Magisk Manager.

Google Pay has worked perfectly on both ROMs, then suddenly it stopped working on OOS with "You can no longer pay in shops with Google Pay", yet the virtual card details are unchanged. However, it still works just fine on Los.

I checked the versions of the Google apps I was running and, surprisingly, both ROMs are at the same version of Pay, Play Store, and Play Services. I've attached copies of the list of Google apps installed on each ROM.

Wouldn't this indicate that the problem isn't [necessarily] caused by updated versions of Google apps?
[Magisk] Adreaver:
Reporting that renaming com.google.android.gms to com.google.android.gms.bak worked for me. Able to successfully add a card where before it was detecting root.

Magisk Canary 18.2.945f8810

Magisk Manager 7.0.0

Magisk Hide on GPay and GPS

GPay 2.84.237487748

GPS 15.0.90

Pixel 2XL

March Security Update

Stock Rooted
[Magisk] HamsterHam:
Yup! I agree with this. Given up trying all the workarounds. Pointless.
[Magisk] Itachisasuke:
I assume booting into TWRP and using adb shell to rename the folder?

Does this blow away all the current cards that are stored or does it just remove the root detection flag?

This issue is definitely temporal in nature.
[Magisk] joeyddr:
yes it does, also blows away your backup account and fit data.
[Magisk] Itachisasuke:
Bleh, back to accepting I'm not gonna have GPay until we have a real fix if any...
[Magisk] yung40oz84:
The Google pay stuff is hit or miss right now, but just for reference.

I installed the latest canary magisk, latest beta play services, and latest Google pay app, wiped all play services data, added a card 3 days ago. Since then I let it sit and haven't tested a payment, I've updated to latest magisk canary from yesterday, and update play services yesterday. This morning I walked into DD and made a successful payment.
[Magisk] joeyddr:
Mine lasted over a week before it happened again.
[Magisk] warrencoakley:
Yep tried all these work arounds and no dice. Just got to wait for a solid fix. Still getting this trying to get a soda from a vending machine today. Grrrr!
[Magisk] warrencoakley:
Here's the result from the card
[Magisk] chris2ferz:
magisk hide google play services

i can only seem to hide google play services for instant apps and not the main one.

not sure why it's not listed - have checked system apps - not there where i can see it

even if i'm able to do that i'm not sure it would help much anyway from what is being talked about here.

it worked best for me when magisk was 17.x - updating to 18.x seemed to be where i started having trouble
[Magisk] Chamelleon:
Seems to be fine now. Few hours without update. We'll see if it stays like this.
[Magisk] warrencoakley:
There is a vast amount of GPS 14.7.99 Which one did you use? I'm on Google Pixel 2 XL.
[Magisk] yung40oz84:
It not magisk, it's something Google did. It started with March security update. I used it on magisk 18 forever
[Magisk] DaveW1972:
I followed the instructions in this thread but didn't bother downloading the APK as Google Play svcs dropped down to under 14.5.74 when I removed updates.

Google Pay works properly and, as a bonus, my Santander banking app (which has never worked with root on my XZ1) is also working - for now!

I have started the clock...
[Magisk] chris2ferz:
maybe we can hope for a module that hooks in and can fool those sys calls or sandbox somehow - think it's unbelievable that it thinks root for an unloked bootloader - not a good assumption - could be awhile to fix - Samsung pay is a no-go but since it hasn't probably been a target much there might be an easier way there.

---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------

if that does work (and hopefully it does) then for how long? could it be a matter of time before GP enforces a certain version of GPS? Hoping for a more global fix but that is interesting - so did you have to delete gps data too or just downgrade?
[Magisk] DaveW1972:
I just downgraded. When I charge it overnight it will probably go wrong again and update...I'll update here when it does!
[Magisk] chris2ferz:
are you clearing any data (cache or otherwise) when you downgrade?

I had problems when i cleared app data for GPS and some notifications stopped working - not all but some and i had to fix that which was a pain
[Magisk] andrewwdai:
Ok. I have two phones which I downgraded GPS of both. One self-updated to 15.09 and the other did not. The only difference was that the self-updating one was re-started once. The one with downgraded GPS has been working for 3 days now.
[Magisk] dipstik:
maybe a module that stops Google PS from updating and spoofing the version to pay requests...
[Magisk] prot-:
Holy sh** that worked!
[Magisk] Itachisasuke:
It will likely only work a few days before it's detected again and the folder will need cleared again.
[Magisk] Chamelleon:
I use 14.7.99 from APKMirror. Still working.
[Magisk] warrencoakley:
Yeah but which one?
[Magisk] Chamelleon:
Arm64 nodpi android 8.0+
[Magisk] neekless:
I was on 16.0.86. Uninstalled GPS updates (went back to what my rom came with, version 12.8.72).

Updated to 16.0.86 again and tried to add a card. Root detected.

Uninstalled GPS updates and updated to 15.0.9. Tried to add a card, successfully added.

Edit: Nvm, tried removing and readding my card, doesn't work now.
[Magisk] smartt699:
I still can't pay

Just thank you.!!! Step by step pretty easy and it's working I'm so happy!

I can add cards no problem now but I still can't pay. Error message you cannot pay with Google pay....
[Magisk] Slats2:
Update on the Google Pay Issue

https://xdaforums.com/showpost.php?p=79146123&postcount=323 & https://xdaforums.com/showpost.php?p=79152118&postcount=340
[Magisk] irony_delerium:
I'm not sure if this will help or not, but:

I'm reasonably certain it's not detecting root. I have a P10 and a Mate 9, running OmniROM 9 (March sec patch) on an EMUI 9 vendor. The ROM itself is passing SafetyNet on a clean install (no Magisk), no root, no obvious signs of tampering that should be obvious to Play Services. (Yes, I patched the build, init forces verifiedbootstate=green, build type is marked "user", etc; also have a certified fingerprint. It technically has root, but it's not installed as "su", and is generally invisible to everything unless I access it over adb.)

Until about a week ago, everything worked reliably - GPay worked without issue, etc. Over the past week, pretty consistently, within about 24 hours of adding cards, GPay will stop working with an error saying "You can no longer pay in stores"; trying to add a new card at this point gets me a message indicating system modification or root.

The only way out is to clear GMS data and start over, re-adding all of my cards. Eventually my bank is going to go "wtf?"

I've tried various versions of Play Services - at this point, they all seem to fail, though. Currently 16.0.87, which worked for about 16 hours before taking a dump all over my cards.
[Magisk] Kaverin:
I can confirm this process has worked for me so far on my old Nexus 5 running a rooted LineageOS 14.1 with an unlocked bootloader, though I had a little snag uninstalling the previous updates for Google Play services. It wouldn't actually come out, so I had to just use ADB and install/replace it with the version mentioned in the workaround. I'm also using Magisk 18.1 with v7.0.0 of the manager, running in core only mode and repackaged, and hiding ALL Google apps (and Paypal) from root. I've only tested Google Pay in one place since the fix, but it did work, so hopefully it will continue to work. It's a huge pain when NFC payments stop working since I use them so often now. :(

I'm just glad someone knows what the specific problem is and how to get around it, so thanks.
[Magisk] MC_Ohr:
Hello,

Do you know which subfolder or file it is in the data folder? When I delete or clear data I have to reset up my wearOS watch again, so I would like to delete just the specific folder/file

Gesendet von meinem HTC U11 life mit Tapatalk
[Magisk] warrencoakley:
What work around did you use?
[Magisk] Slats2:
All you have to do is boot into twrp and use the file manager to rename the /data/data/com.google.android.gms to /data/data/com.google.android.gms.bak

Then reboot!

I don't have a wearOS device so I'm only referring to Android 9.

Hope that helps.
[Magisk] Kaverin:
I used the method that JarlPenguin gave in post #5 of this thread, but also some other things I believe I read in later posts of this thread (or maybe another similar thread), mainly the running of Magisk in core only mode and so on.

I tried including a direct link but the forum isn't letting me for some reason.
[Magisk] MC_Ohr:
Hello, the point is that there are many subfolders in com.google.android.gms one of them is responsible for wearOS, so when I delete/rename the whole folder, I have to reinitialize my Watch to get connected again. Some settings like SmartLock are also gone, but thats no big deal. BTW I have no TWRP because for HTC U11 life Android one it's not availlable. So I use ES File Explorer to delete/rename.
[Magisk] Slats2:
The whole folder needs to be renamed in TWRP. The Watch needs to be paired again as Google Play has been reset.
[Magisk] prot-:
It's not necessary to do twrp. Just do it in something like root browser then reboot . Works a charm
[Magisk] Dreamer(3MF):
You Can Also Download

ClearPlayStoreWithServicesData4Magisk

From This Thread https://xdaforums.com/apps/magisk/module-google-playstore-services-data-t3789498 & Flash It And Then Reboot.
[Magisk] warrencoakley:
Is this Module going to help with passing GPay?
[Magisk] chwiejak:
Any news with permanent solutuon for gpay problem?

Br
[Magisk] Itachisasuke:
Nadda yet homie.
[Magisk] c3k:
try renaming

com.google.android.gms/databases/android_pay

and

com.google.android.gms/databases/android_pay-journal

and let us know

you'll probably have to add the card again

here I found:

PaymentCards.token_state = 3

Wallets.fails_attestation = 1

both could be what we're looking for and if confirmed I can made a reset utility while waiting for a permanent fix...

as soon I can reach a store I'll test too

EDIT: don't work
[Magisk] david19au:
Does John know about this issue? He usually acknowledges new problems when they arise like this on his Twitter. It doesn't seem he knows about anything.
[Magisk] royhanks3:
Is there anyway to permanently stop Google play services from updating? I've disabled background usage of Google play services as well as the Google play store, but every hour or so, play services updates itself again.
[Magisk] Eric214:
DO STEP ONE... TURN OF DEVICE ADMIN FOR PLAY SERVICES AND GOOGLE PAY. That will allow you to uninstall updates

---------- Post added at 09:51 PM ---------- Previous post was at 09:49 PM ----------

When you get the alert, in the notification shade, swipe slowly to the right to get the cog and turn off the notification
[Magisk] JarlPenguin:
You have to disable Google Pay and Find My Device as device administrators.

---------- Post added at 05:58 AM ---------- Previous post was at 05:53 AM ----------

I'm afraid not. Try detaching it from the Play Store, but other than that I can't think of anything.

---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------

Replace the system version with the 14.7.99 apk. Here's what I mean (have a backup before continuing)

1. Navigate to /system/priv-app/PrebuiltGmsCorePi

2. Replace the existing file there with your downgraded apk.

3. Reboot.

4. Profit!
[Magisk] sturmeh:
After following steps correctly, it works and I am able to use Google Pay again.

Hopefully Magisk is updated soon! :)
[Magisk] Matrixie:
Now a new issue has popped up - how do I stop Play Services from updating automatically? I've turned off background data for Services and Play Store, and set it to not update apps automatically, but I had to do the fix again this morning as Play Services had updated overnight.
[Magisk] sisqoboy:
Titanium backup will be sufficient as a backup for play services right?
[Magisk] InsaneNutter:
Strangely enough I did start having this issue on Saturday with LineageOS 15.1 on my OnePlus 5T.

I was planning to upgrade to LineageOS 16 on Sunday anyway, so I did and can currently use Google Pay with the Play Services 15.1.78 beta installed.

Rom: lineage-16.0-20190303-nightly-dumpling-signed

Gapps: Open Gapps - ARM64, 9.0, Nano (3rd March 2019)

Magisk version: Magisk 18.1 (18100)

Magisk Hide: Enabled for Google Pay and Pokemon Go only

I have also used the Magisk Hide Props Config module to change my devices fingerprint.
[Magisk] sisqoboy:
Anyone any clue which apk for xiaomi mi 8 pie?

Edit: Turns out it is the arm64-v8a with nodpi
[Magisk] sisqoboy:
LOVE YOU MATE!

can confirm it works on xiaomi mi 8 pie
[Magisk] PhotoPaul:
Don't know what to make of this, but I'll share it in case it helps someone debug this issue.

I followed the workaround instructions (graciously posted by JarlPenguin) downgrading google play services etc.

When I was done I restarted my OnePlus 5T and it got into a soft boot loop (timed-out while it was showing the booting animation, and automatically rebooting into recovery).

I tried and failed to fix the soft boot loop by clearing caches, and by dirty flashing the stock ROM, but nothing worked, so I ended up factory resetting from within recovery (TWRP).

As soon as the phone was setup, apps re-installed and system apps updated to their most recent versions, somehow Google Pay is now working again without the need of any workaround (I have unlocked bootloader and Magisk installed and rooted).

Google Pay is v. 2.82.231680166

Google Play Services is v. 15.1.78
[Magisk] beatschubser:
Still not sure if these workarounds actually work or if it's a coincidence. I haven't changed anything over the last couple of days, and sometimes GPay is working, sometimes I get the error message. For me it looks like Google is messing around on their end.
[Magisk] memone75:
Same here, haven't touched anything and now it's correctly registering my cards for contactless payments

Play services 15.0.90

Pay 2.82.231680166
[Magisk] tlf55:
Have you tried the contactless payment ? Because I always could add card and go to Google pay without the "workaround" it's just the payment in stores with NFC that didn't worked anymore (it was saying that "Google pay isn't authorized to pay in this store anymore")
[Magisk] david19au:
Try paying in stores with it. The registering process can be successful but when paying, it might deny it. (You'll get the "You are not able to pay in stores with this card anymore")
[Magisk] sam00561:
Thats what was happening to me one oneplus 5T i can add card successfully but when paying in store get error you are not authorised to pay in stores something along those lines. This has become a big headache it was quite embarrasing as there was a que behind me and my card was not with me.
[Magisk] memone75:
Did it right now and it worked!
[Magisk] ego42:
Brilliant! I can confirm this extremely simple workaround worked for me. Thanks!
[Magisk] kradcliffe:
Not working for me (Note 8). When I downgrade Play Services I get constant error messages and notifications to update it.
[Magisk] PhotoPaul:
I added two cards after the factory reset, and both of them worked again on the same POS.
[Magisk] Superschmiddi:
JarlPenguin's workaround in post #5 worked for me. Thanks!

Do we get here information if Magsik is updated and working again so we can update the Google Play Services?
[Magisk] MC_Ohr:
Thank you for searching for it. Unfortunately I renamed the whole folder and was able to add my card again.

Gesendet von meinem HTC U11 life mit Tapatalk
[Magisk] chris2ferz:
VERY NICE! what i've been looking for - g**gle will probably get around this but it will hopefully work for awhile (while we wait for a perm fix)

can you elaborate where those two strings were found? one in each file you mentioned?

*UPDATE*

those are databases (mine were located at /data/data/com.google.android.gms/databases)

i opened android_pay and found the fails_attestation set to 1 - i changed to 0 and it stuck until i opened gpay and it changed it to 1 again (i'm assuming 0 is good)

the other database android_pay-journal was empty for me.

???? hmmm

close but still seems like another trigger somewhere
[Magisk] warrencoakley:
I've flashed this but felt it didn't do anything and removed it. Now all my Magisk Modules are only displaying the Android logo on my home screen.

Any ideas what this has done to them?

I've tried rebooting and reinstalling the Modules and it's the same thing. Grrrr!
[Magisk] warrencoakley:
Here is what I mean
[Magisk] joeyddr:
i renamed them and pay fails to launch when i did.
[Magisk] chris2ferz:
mine says "There was a problem setting the active account.

same for you?
[Magisk] joeyddr:
yep.
[Magisk] jhedfors:
Same for me until I rebooted. I was then able to add the cards like a new setup.
[Magisk] joeyddr:
I rebooted and it was normal again but went to add paypal to it and it still said i was rooted.
[Magisk] chris2ferz:
wow it gave me hell even after a reboot but finally opened after trying a few times.

but says i'm rooted - so i think there are other triggers or files involved with this (at least for some of us)
[Magisk] joeyddr:
yeah it sure did, hung the whole phone up I couldn't even force stop it... another reboot resolved it though.