yashsingh1/xdaforums huggingface dataset:
[Magisk] dyingearth:
I was able to add one card, but the second one I tried to add failed. This is after upgrade to Magisk 19, removing /data/data/com.google.gms using the app storage management and then hide just google pay, all gms apps. Payment at a vending machine works.

This is Pixel 2 XL running March 2019 patch build.
[Magisk] ThatFluxNerd:
Update! Tried paying, but tapping the phone on the terminal doesn't work, and the terminal throws a "Card unsupported" error (I know this terminal works).

I'm running LineageOS 16 (build from 28.03.19) on Xiaomi Mi Mix 2S with Magisk v19.0-3eae9494(19001). Google Pay version: 2.85.239456103. Google Play Services version: 16.0.89 (100400-239467275).
[Magisk] upperbladez:
How do you clear GMS?
[Magisk] joeyddr:
i i deleted the folder in twrp... or you can try any of the other ways in this thread.
[Magisk] wabmorgan:
You can also rename the file data/data/com.google.android.gms by changing the end to .bak
[Magisk] MRL3GS:
Updated to v19

Deleted the data/data/com.google.android.gms folder

Then hid Google Pay and Google Play Services

Tested and working!
[Magisk] 73sydney:
And despite everything tried here, and most recently re-activating card via renaming gms folder, just now (with nothing changed on my end except the update to magisk 19 yesterday), my bank just sent me the notification that the card linked to my virtual wallet (google pay) has been de-activated....

The nonsense continues folks.....

Google, just leave me the fudge alone....
[Magisk] Michalec:
Yesterday I've updated Magisk to v19. GMS and Gpay in magiskhide, then reboot. After reboot tried adding my cards and success. Will see today if I can pay.

Didn't wiped anything.

Wysłane z mojego ONEPLUS A6013 przy użyciu Tapatalka
[Magisk] johnlgalt:
Confirmed still working here after using the hide method, with GPay now upgraded to 2.85.
[Magisk] ammmze:
Am I correct in assuming that "Goat" in magiskhide is a mis-typed "Gpay"?
[Magisk] Michalec:
Yes, fixed typo, thanks :)

Wysłane z mojego ONEPLUS A6013 przy użyciu Tapatalka
[Magisk] sathya86online:
So this works with the latest Play Services or the old one?
[Magisk] highdiver_2000:
Didn't work for me
[Magisk] martyfender:
This works for me on the latest Play Services beta 16.0.89, yesterdays update to Google Pay 2.85, hidden and Magisk 19001 latest with the default com.google.gms.unstable only hidden.

You may be asking for other problem if you hide more of the Play Service entries and Google Play Services Framework, although some appear to do just that without any issues, so far.
[Magisk] marcocsh:
With the new magisk 19.0 and magisk manager 7.1, and clearing google pay data, google pay come back to life. Big thanks to the dev!
[Magisk] Aletheia:
Updated to 19 from canary (didn't get the chansen to try purchases with the canary build), hid GPS.gms and my card (that was previously declined) started to work. No wipe or re-adding of cards. ?
[Magisk] iosonofrancesco:
same for me!
[Magisk] joeyddr:
Broke again this morning.... worked yesterday afternoon after the gms delete and update to v19 magisk
[Magisk] pr0adam:
did you do anything else like hide google pay in magisk settings? I havent gotten a chance to pay at a terminal yet and its pretty discouraging to read that within 24 hours it stopped working for people
[Magisk] joeyddr:
Yes I hid pay and play services.
[Magisk] martyfender:
Try hiding the Magisk Manager in settings. You might also have to rename or delete the data/data/com.google.android.gms folder, and delete data of Google Pay, then reboot.
[Magisk] pr0adam:
ill hopefully try a payment today after work it is getting kinda embarassing failing the payment every time lately though lmao
[Magisk] joeyddr:
Magisk was already hidden and i did all that yesterday and it was working and it got flagged again in under 24hrs.
[Magisk] finesse:
Confirmed.

Update to V19 & latest manager.

Hide pay and play services in magisk hide.

Delete the above mentioned folder

Clear pay data, and reinstall

Reboot

Job done

Thanks all

---------- Post added at 02:06 PM ---------- Previous post was at 02:02 PM ----------

Question, do I disabled future Google play services uodates?
[Magisk] NFSP G35:
Another (mostly) confirmed...

Updated to Magisk 19 and latest manager,

Renamed /data/data/com.google.android.gms

Hide pay and play services

Clear data & cache for pay and services

Reboots throughout those steps (don't remember all of them)

Then I was able to get through the setup process. Haven't had a chance to test paying yet, hopefully later today.
[Magisk] abyssq:
Updated to Magisk 19 and latest manager

Renamed /data/data/com.google.android.gms

Hide pay and play services

Hide magisk

Clear data & cache for pay and services

And still doesn't work. :/
[Magisk] sam00561:
cant you even add the card
[Magisk] dimm0k:
when you clear/rename /data/data/com.google.android.gms, what data gets lost?
[Magisk] rfactor117:
2 things... Cache from Gpay (you have to reconfirm your cards) and confirm user location history.

Hope this helps ?
[Magisk] pr0adam:
also for me i had to pick my google account to backup to, but thats because i have multiple google accounts added to my phone for different gmails. nothing big.
[Magisk] swour:
Being able to add payment cards again does not equal success. I'd be interested if all those who cheerfully reported GPay as working again can actually pay contactless for longer than a week, at a minimum. Anything else is still pure luck because the background checks probably haven't triggered yet.
[Magisk] methuntt:
Pixel 2 pie working (gpay method)

1- Magisk 19

2- hide apps shown in below screenshot ( ignore phone pe)

3- try to use the app mentioned two pages before and if result ok then

4- open gpay and add card or

This worked for me ?( i didn't rename the magisk package or delete the gms folder).
[Magisk] methuntt:
Thanks for the app and it helped me lot.
[Magisk] joeyddr:
and fit data.
[Magisk] Superschmiddi:
Hm my GPay is failing again.

Tried to flash MAgisk v19 but it failes

"Updater process ended with ERROR: 1

Error installing zip file '/sdcard/MagiskManager/Magisk-v19.0.zip'"

Its really annoying right now :(

edit: Okay, now it worked, trying to pay with GPay again.
[Magisk] eelsid:
First try changing your active slot with fastboot. If it still throws that error flash stock boot.img to slots A and B, boot TWRP, and reflash TWRP, whatever kernel, and magisk.
[Magisk] Superschmiddi:
I edited my last post, I managed to boot again, just did a factory image flash.
[Magisk] Brakiss:
Pixel 3 xl, followed all steps, no joy. Says I am rooted when I try to update cards.
[Magisk] joeyddr:
I feel all these "confirmed" are gonna be temporary.
[Magisk] D-m-x:
Of course they are. If we have learned anything from the past weeks is, that this is unpredictable. Might work one day and the next not. As far as I'm concerned there is no real fix, only workarounds. Deleting Play Services Data might work but thats no guarantee.
[Magisk] joeyddr:
indeed, but we still don't know the real cause and i think hiding gms and pay is just a placebo. They are doing something else that gets around hide and its just a timed thing.
[Magisk] D-m-x:
Yes, I do have the same opinion. As I stated before, I think the easy times to get past these checks might be over, if not forever. But lets see about that, Devs here are smart. Maybe someone will eventually get around it, but I'm a pessimist, so I naturally fear for the worst :)
[Magisk] IM0001:
So I was having a hard time adding a 2nd card to Gpay even though I was able to add another card and pay pal just fine on the last 18.2 canary build. But I was also behind on a android update build on my 2XL.

Decided to do a full image update, booted and let everything settle, then reboot into twrp, installed the latest 18.2 canary, reboot, made sure pay was hidden as well as the 2 gms entries. My 2nd card was successfully verified on its own after (already called the bank, guess the token needed a android update or something?) and last night I paid with it at the movies twice successfully. I did update to the 19.0 canary build that manager was pinging me about beforehand as well.

I do notice today there is a pending Google Pay update waiting to install. $10 says that may be breaking things again so I am going to hold off installing it until we know more hopefully.
[Magisk] timo625:
When you have a Wear OS device you have to reset and pair it again. Could be annoying for some people... For me it was okay because I use the watch in nearly stock state.
[Magisk] D-m-x:
This is not the only thing, all settings in Settings/Google are reverted back to default. Additionally this also gave me problems accessing certain settings like the Location Settings and Play Protect. It can work, but I don't like to tamper with gms settings.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] rafitamolin:
This morning it broke again. Updated to Magisk 19 and hid Magisk Manager from the system on settings, rebooted and now it seems to be working again.
[Magisk] wabmorgan:
Updated to 19. Still works. ? I just bought lunch with Gpay. ?
[Magisk] dvhttn:
Updated to 18122 then today to 19001. GP still working. My transaction history shows that it's been working with no problem ssince at least the 15th March (now the 29th). Go figure ....
[Magisk] warrencoakley:
9 days in on Canary build with 23 GPay/contactless transactions and it is still holding. #winner
[Magisk] fw85:
Been 7 days now on 18.1 since fixing it, using GPay daily, including contactless payments. Works just fine.
[Magisk] c3k:
I've to report that the app say "Fails" but I can pay.

Magisk 18.1 core mode, never deleted entire gms folder, only the databases/android_pay one time.
[Magisk] cbarai:
Thanks for the app, mine says failed but I've got no issues with GPay now since I moved to the Canary build 2+ weeks ago.

Thinking about the upgrade to 19 now.
[Magisk] jcmm11:
If you're running the latest Canary you should already be on 19
[Magisk] cbarai:
I was on the last build before 19. Just updated to 19 between my last post and this post. Hopefully payments will remain unaffected when I check tomorrow.
[Magisk] ledhed:
I tried all the various methods. The furthest I've gotten is adding 1 card. By the second card, it detects root.
[Magisk] highdiver_2000:
Yes, the second card breaks things
[Magisk] krs360:
You don't need to reset it, just a couple of adb commands.

https://www.xda-developers.com/pair-android-wear-without-factory-reset/
[Magisk] Droiderat:
Per request:

On March 6 (after Google Pay died for me), I installed Magisk canary, and hid Google Pay and com.google.android.gms.unstable. I didn't clear any caches or rename any folders. Google Pay and Google Play Services are updating normally (and without restriction) via the Play Store.

I have been using Google Pay successfully every day since. Not a single rejection. And I have 5 cards installed, including PayPal. Galaxy S7, with the latest Oreo, including the March security patch.
[Magisk] Freshek:
How many rows do you have in the `Wallets` table inside the `android_pay` db?
[Magisk] c3k:
Only one
[Magisk] timo625:
Really? It's so simple? Man I've wasted so much time always resetting my watch after flashing new ROMs or wiping my phone... Thank you for this link! I just should've googled this...

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] Freshek:
And what's the `fails_attestation` value?
[Magisk] c3k:
Is 1
[Magisk] zencooler:
I fixed my GPay six days ago (by Magisk Canary, clearing GMS and hiding GPay) and set up my six cards with no problem at all. Yesterday I reinstalled Magisk into 19.01 (no changes in GPay 2.85.239456103 and no clearing GMS 16.0.89). Today I paid using NFC and everything works like a charm.

Regards!
[Magisk] cbarai:
How would I check?
[Magisk] Tr4sHCr4fT:
so, it's now limited to 1 card? well, better then unroot i guess.
[Magisk] skejpa:
Anyone tested Magisk 19 with Xiaomi Mi 8 ?

Odesláno z mého MI 8 pomocí Tapatalk
[Magisk] hawkinsst7:
Would it be dumb to hide root from every single thing by default, and unhide for specific apps that need root?
[Magisk] PuffDaddy_d:
If your solution works, please remember to state the device and OS version you are using.

So far, nothing has worked for me with my Pixel 3 on Pie
[Magisk] jsylvia007:
This was always a question I had.
[Magisk] NFSP G35:
I was able to successfully pay. It failed the first 2 tries with a red exclamation point, but succeeded on the third try. Guessing that was more of a hardware fluke than any software issue.

---edit---

Forgot to add... HTC 10 With unofficial LOS 16 (Pie)
[Magisk] Tr4sHCr4fT:
a 'whitelist' mode of operation would be actually nice

root disabled per default until you launch a root app...
[Magisk] jrbmed08:
Those are the steps I followed. I used the Terminal Emulator app. I guess it doesn't matter now that we have Magisk beta 19, which should enable that feature, right? But I updated Magisk, uninstalled/reinstalled Google Pay, hid it again, used random package name, and Google Pay still detects root.
[Magisk] Freshek:
Never mind.

Yes. Been working flawlessly for me for almost a week on latest stable xiaomi.eu.

Interesting. What's your Google Play Services version?
[Magisk] Haldy:
I confirm that after update of Magisk to v19 and hiding GPay its working again.

Odesláno z mého MI 5 pomocí Tapatalk
[Magisk] Tr4sHCr4fT:
I wonder what would happen if one somehow prevents changing the value, maybe by creating a dummy table with only one item with id=0 then defining it as a foreign key for fails_attestation, so setting it to 1 would violate the constraint...
[Magisk] rocfob:
Tried it just now, Google Pay is still broken with error message "Couldn't finish setup to pay in stores"

Pixel 2, stock ROM. Magisk v18.1 Magisk Manager v7.1.1 (203) Magisk Hide Google Pay.
[Magisk] Freshek:
You can try that yourself by preventing any process to write to that file. If you have busybox installed on your device, simply run

su -c chattr +i android_pay

in the folder which contains the android_pay file. Although I think it will simply make GMS crashing constantly.
[Magisk] JaylanPHNX:
I'm using Magisk 19 on Pixel 2xl and I've hidden Magisk manager, added Pay and Play Services to hide, cleared data for Pay and Play Services, rebooted. I still can't setup in-store payment for my card; it says device rooted or altered. Is it possible my substratum themes are interfering? Should I run in core-only mode for setup? I thought Magisk 19 was going up solve my problem, but sadly no.
[Magisk] wieman01:
Have been able to do payments for a few days now although Magisk occasionally shows the device is failing safety net. Strange, but it is what it is. I am using Magisk 18.1.

I am on Lineage 15.1, Samsung S5, KLTE.
[Magisk] cmstlist:
Can confirm indeed, on my Xperia X Compact, Magisk 19.0 beta did the trick. I was able to re-add contactless for my Tangerine card.

I will test it out later at a transit fare card top-up machine.
[Magisk] zencooler:
So. change the Magisk to 19.x,, clear Google Play Service folder and reinstall Google Pay. Then add your cards again. Detail info you can find in previous posts of this thread. This should work for You.
[Magisk] methuntt:
No substratum won't interfer.

Check safety net pass and open playstore and see Device is certified in playstore settings.

If everything ok then follow below steps

Hide play services, play store, phone, phone services, google service framework, Install gpay and hide gpay. As shown below (ignore other apps)

Now open gpay and add..

This method i did and it's working on magisk 19.

Another working method in all magisk v17+ but it has some more steps

1) hide play store,google services framework, gpay. If magisk shows play services, phone, phone service hide that too.

2) Uninstall play services update (if it tries to update - disable background data in settings) and

important ----remove phone permission from play services by going into app info.

3) Now download or if u already installed gpay just clear data. Now open give required permission and add card. It will surely work.

I had been using this for long time from magisk v17+.

And I'm having Pixel 2 (pie).
[Magisk] tox10:
I installed Magisk 19.0 beta on my xiaomi Mi 6, put Play-Services + G-Pay in Magisk Hide and G-Pay works perfectly again...
[Magisk] haybill:
Sorry to go 'Off Topic', but just wondering if anyone knows of this will work to make the Santander UK Banking App usable, once more, because it was working fine until the Bank's App received its latest update-- until then, Magisk Hide for the Santander App, using Adaway with Magisk option 'Systemless Hosts, rename Magisk Manager made it possible to use Online Banking App from Santander-- however their latest update detects a Rooted Device.

I'm wondering if the steps in this thread, for Google Pay will work with the Santander Bank App-- anyone tried????
[Magisk] hawkinsst7:
Why would it be dumb? Seems like a default whitelist would mean nothing would be able to "leak" that you have root, except for apps you allow. It reduces the things Pay can use to detect rooting, right?. What's the down side that I'm missing?
[Magisk] Freshek:
That would drain the battery a lot I guess.
[Magisk] jcmm11:
Because of the way that Magisk works you'd be generating a lot of overhead and I can almost guarantee that unexpected results will occur.

Topjohnwu has said 'only hide things that have to be hidden or things will break' (paraphrasing)
[Magisk] martyfender:
You can find that in this guide and more, concerning the previous post.

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] Brava27:
Got rejected today at the shop with Google pay I hate this.

Sent from my Blackberry Bold
[Magisk] c3k:
15.0.90
[Magisk] MRL3GS:
Latest one
[Magisk] rocfob:
Thank you so much! Here were my steps:

Update to v19 (Download .zip and install using TWRP)

Magisk hide Google Pay

Magisk hide com.google.anroid.gms.unstable

Rename data/data/com.google.android.gms folder

Uninstall Google Pay

Reboot

Install Google Pay and set up cards. All the cards that were previously in Google Pay retained, just needed to re-verify with CVV.
[Magisk] Freshek:
Weird. For me it still works flawlessly. For how long was it working correctly?
[Magisk] Antonio.90:
Update magisk to 19.0 on havoc 2.3 Device xiaomi mi mix 2

Google pay start works whit magisk Hide
[Magisk] escrifonife1:
I have a Mi 8 and It's working for me.
[Magisk] highdiver_2000:
Never mind
[Magisk] alibob911:
Magisk 19

Magisk Manager 7.1.1

OnePlus 6T stock 9.0.12 + rooted

Is anyone getting a SafetyNet API error when running the SafetyNet test?

Also, I can't get into Google Pay when I hide Magisk from it. However, when it's hidden, I can pay with it. Is that expected behaviour?
[Magisk] highdiver_2000:
Mi Mix2s with MIUI Global Beta, Majisk 19. I do 3 payment over 3 days. Only1 card configured.

I can open Google App to see my past transactions.
[Magisk] 73sydney:
Read my (and others) comments earlier in this thread, do what you want, eventually you will get declined

https://xdaforums.com/apps/magisk/d...discussion-t3906703/post79219245#post79219245

Most recently i had everything set up as you quote and then like 3 or 4 days later, i got the usual notice from my bank that the "card linked my virtual wallet had been deactivated"

Its google end causing the problems.....you can do whatever you like on your device, eventually they will just blacklist you
[Magisk] ajm786:
There's a lot of confusing information going on here. I'm sure it's not anyone's fault, but the fact that Google is randomizing things on their end.

Here are the things I noticed while trying to get my GPay working again. I'm using a rooted Samsung Galaxy Note 9 N960F-DS. Reverting to the older 14.x.x version of Play Services always fixes it, but only temporarily. It eventually automatically updates to 15.0.90 and breaks GPay in the process. Attempting to rename the com.google.android.gms folder is completely hit or miss, and in my case doesn't work at all.

Here's what I did to fix mine.

1. Update Magisk to the latest beta, v19, and the latest Magisk Manager, v17.1.

2. Hide all Google Play services and Google Pay using Magisk Hide.

2a. Run the SafetyNet check in Magisk Manager. If you get any failures, don't bother going forward with the other steps because you'll just be wasting your time. Address this until you get a full SafetyNet pass on this step.

3. If you have WiFi turned on, TURN IT OFF. I found this to be a critical step for me.

4. Update to the latest Google Pay, v2.85.239456103.

5. Update to Google Play Services to the latest, v16.0.89.

6. Clear Google Pay data. You MUST clear cache FIRST, then clear data. Do not open the app after doing this.

7. Clear Google Play Services data. You MUST clear cache FIRST, then go into Manage Storage, and then choose Clear All Data.

8. IMMEDIATELY REBOOT. If you don't, and you try adding cards again, everything will fail and you will have start all over again.

9. Upon rebooting, ensure WiFi is turned off, then immediately open GPay and start adding your cards. I added all 3 of my cards successfully: one Visa and 2 AMEX. Once finished, you should also be able to pay in stores.

I did this process 3 times so far. Each time I tried, as soon as I turned on WiFi on any of these steps, it would detect root and break GPay. Performing all the above steps solely on mobile data, I'm able to complete adding my cards successfully. So far, I've paid 3 times in stores with GPay, so I can vouch that it works, at least for me.
[Magisk] ang3l:
How can you perform updates (4 and 5) after turning off WiFi (3)??
[Magisk] ajm786:
Using your phone's mobile data, obviously.
[Magisk] JustinTrouble:
It was said a long time ago that this is not recommended because it would cause performance problems.
[Magisk] Cowbell_Guy:
I still can't get Google pay to work on 19.0. uninstalled the Google pay app after upgrading magic. Then redownloaded the Google pay app, tried to hide it in magisk. And I'm now getting this error when adding a card. Have tried removing/ re adding card numerous times

Pixel 2 xl. Anyone have any advice? Thanks
[Magisk] hawkinsst7:
Do we think that the new ptrace method would alleviate those performance issues, since it's happening with the zygote at the process level and not via logs?

Other than performance, might there be any other side effects? I'd be willing to try it out.
[Magisk] jcmm11:
How can I say this so you'll understand. DON'T DO IT OR YOU'LL REGRET IT!!! ?
[Magisk] zencooler:
That is not enough to avoid this root recognizing by GPay. You have to clear all cache and data of Google Play Services and GPay before you you reinstall GPay app. It is crucial to clear your current error. It will work for you.

You can find detail steps you have to do in previous posts of this thread.

Good luck.
[Magisk] JustinTrouble:
Clear all Google Play services data, then add your card.
[Magisk] Windroid-user:
I'm guessing restrict background data on the Google related services, because it says that this applies only for mobile data, not wifi.

Not that obvious... Unless it clearly states in the instructions or something, haven't actually read it since many posts come through this thread.

Okay I was lazy just checked it was the post before. Yeah didn't clearly state but I'm sure he meant mobile data. If you don't have mobile data then what you can do is download the apks beforehand using wifi and install them when you get to that step since installing does not require an Internet connection
[Magisk] jrbmed08:
Brilliant! This worked perfectly for me, at least in the sense that I could add a card. I'll try paying next time I have a chance.

Edit: Pixel 2 with ElementalX kernel and Magisk, otherwise stock Pie.
[Magisk] wbedard:
I have the same setup as you and the GPay app functions fine for me while hidden in Magisk. Feel free to followup via PM if you want to work together to get your GPay fixed up.

R/

wbedard