yashsingh1/xdaforums huggingface dataset:
[Magisk] swour:
This thread indeed is a mess. Without applying any of the mentioned workaround solutions I have been able to pay via NFC yesterday.

Another device with same hardware, software and configuration has been failing to make any payments for the last week. The only "clue" being that it had 'Find My Device' toggled on, which I have since disabled and re-added the card successfully again to Google Pay.

Stock ROM with Android 8.0 on Samsung A520F.

Magisk 18.1 without any apps added to the hide list or any other measures taken

Google Play services 15.0.90

Google Pay 2.83
[Magisk] beatschubser:
13.7.30-all

not certified
[Magisk] Droiderat:
From the developer's readme for Magisk Manager 7.0.0:

## Magisk (e8f35b02) (18112)

- Application component granularity MagiskHide:

Starting from this release, you can target specific components

of an app as a target. If you want to completely hide from an

app, you should select all of its components as targets.

- Improvements to MagiskHide to hijack target processes sooner

​
[Magisk] JarlPenguin:
Oops, my bad. They are hidden by default. If you have 13.x in pretty sure GPay will definitely work.

---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------

The fact that you have the stock ROM makes it easier to be compliant to SafetyNet.

---------- Post added at 04:15 PM ---------- Previous post was at 04:14 PM ----------

I advise you to hide every. I'm on Canary too, but I don't have 10 Google Play Services. Hmm
[Magisk] tlf55:
Look at the screenshot
[Magisk] joeyddr:
have you tried a terminal with all that blocked?
[Magisk] jacek607:
I just fixed issues with GPay by turning "Core only" -> restart -> turn off "Core only" - > restart

GPay is now working well and I am able to install modules in Magisk. Wierd, but happy it solved the problem:)
[Magisk] joeyddr:
what phone os/magisk version?
[Magisk] jacek607:
Droid Turbo

RR v. 7.0 (Android Pie)

Magisk 18.1
[Magisk] djide:
In a couple of hours can you check if it sticks. Mine reverts back to stop working.
[Magisk] kleest:
Uhm.. I meant the Google Play services version, not the Play store version. :cyclops:
[Magisk] cawpin:
Click Disable. That will uninstall all updates. It worked for me.
[Magisk] Kashmir33:
When I got to the step of hiding "NFC" related things via Magisk my phone rebooted when I hit the checkmark for com.oem.nfc

Any idea why that was?
[Magisk] caluz78:
Mine still working after more than a month now..

Never deleted anything.. the only thing that makes me working is not updating GPS (still on 14.7.99).

I blocked the update disabling the service.
[Magisk] rajone9:
what service did you disable?
[Magisk] caluz78:
UpdateSchedulerService
[Magisk] rajone9:
I can't find it among the services
[Magisk] caluz78:
It's a GPS service.. I use an app called Service Disabler to find it.
[Magisk] highdiver_2000:
delete
[Magisk] caluz78:
we are talking about google PLAY services, not google PAY.
[Magisk] rajone9:
I'm using service disabler too, but no sign of it
[Magisk] caluz78:
Do not use search bar..
[Magisk] rajone9:
cheers
[Magisk] ben63vw:
I was wondering why Gpay all of a sudden detected root on my Mate 20 X EVR-AL00C00. Followed these steps and except for the install in step 4 (the install failed cause after I uninstalled previous updates in step 3 for Google Play services it was the same version that was downloaded in step 4) and I'm using Magisk Hide with Gpay and all of Google Play services just to be sure.

Works with latest versions of Magisk and Gpay:

Magisk v19.0 (19000) beta

Magisk Manager v7.1.1 (203)

Goggle Pay v2.86.243324902

Google Play Services v14.7.99 (100400-223214910)
[Magisk] raphytaffy:
SafetyNet passes, but I'm unable to use Google Pay at the moment. Just came across this thread and read through various fixes.

Is there an easy way to tell if Google Pay works after any of these fixes other than trying at a terminal?
[Magisk] dbareis:
I think if you can add a new card then it's working
[Magisk] erbarad:
I can add cards, activate contactless payments so in theory i'm good. But whean near a terminal - nothing happens. NFC is on, and the terminal itself detects the phone as there are some error tones coming from it, the phone itself however remains inactive, no overlay shows up. What gives?
[Magisk] sam0056:
Are you on a custom rom or stock I had this problem once on a custom rom where card was added but machine couldn't detect it.
[Magisk] Nhyphk:
So still no way to use Google Pay with root without having to downgrade Google play services? Hahaha I rooted so I wouldn't have to do that anymore to play some games. ?
[Magisk] dbareis:
I haven't downgraded anything.
[Magisk] zencooler:
Seems that you have not NFC set up to use Google Pay. Go to NFC settings of your smartphone and here you have to switch on the option "touch and pay" (or something similar). Then in this option you have additional settings related to apps supporting contactless payment. Check if Google Pay is choosen here. Hope this helps.
[Magisk] Nosferatu.:
Last time I comment since people like to "selectively read" if at all. This method flat out works...no downgrading or trickery....

https://xdaforums.com/showpost.php?p=79342303&postcount=967
[Magisk] highdiver_2000:
Mine:

Magisk v19.0 (19000) beta

Magisk Manager v7.1.1 (203)

Google Pay v2.85.239456103 <<this is behind as updates are disabled.

Google Play Services v16.0.89 (100400-239467275)

---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------

Unfortunately, no. That is why I go to McDonald's self-service terminals. They have 3 or 4 compared to BK (HJ) or KFC 2 or 3. :)
[Magisk] Truant_Luce:
So since I updated to magisk 19 and deleted the GMS folder, my NFC is very slow in activating. Also, if I have the device plugged in, and screen off, after a bit, it will not wake up and I must hard reset in order to get it to boot up again. Anyone else experience similar things?
[Magisk] erbarad:
It's set up and gpay is the default touch and pay method.
[Magisk] rajone9:
with service disabled, google play service has updated after few hours :(
[Magisk] warrencoakley:
3 time now in 8 days going down. Updated to new GPay update and it seems to have patched my method I just to use to get it working again.

Anyone updated to new GPay update and had it working that can share their method please?
[Magisk] zencooler:
I think you do not need to care about Google Play Services version. I updated it regularly (see attached screen and have no problem at all). The only thing you have to be worry about version is Google Pay (some users reported issue on the latest version 2.86.x). That's why I keep the version 2.85.x and everything works like a charm since few weeks. I pay everyday using Google Pay with no problem. Today I also made three contact less payments. View attachment 4744219
[Magisk] zencooler:
What the detail GPay version you have already installed? I keep the version 2.85.x...
[Magisk] warrencoakley:
Yeah im on 2.86 but only from this morning as i was on 2.85 and it failed. Are you staying roll back to GPay 2.85 and try again?

So I need to roll back on Google Play Services too?

I'm currently on 16.7.96? Are you on this one?
[Magisk] zencooler:
Look for my previous post where I explained Google Play Services versioning. It doesn't matter from my point of view on what version of Google Play Services you are. Go back to version 2.85.x with your Google Pay and clear cache and data of GMS (or better: remover GMS folder) then reinstall GPay to 2.85.x. Be sure you are on on the latest Magisk 19004 and of course check SafetyNet pass and hide GMS, GPay and Google Play Framework in Magisk Hide. The set up your cards again in GPay.
[Magisk] warrencoakley:
Yeah no joy. They have patched something. I've tried a few ways including your own and no joy. Damn it. Getting tired of it now.
[Magisk] yung40oz84:
Deleting GMS folder always works for me, and for awhile actually, but the problem is that it screws up my notifications. Specifically G photos notifications don't work correctly like downloads, and also play store installing notifications. I am tempted to wipe now but don't want bunk notifications and I haven't found a fix for that. I've already tried wiping those apps data.
[Magisk] dvhttn:
Since I posted the original note above I have had GP upgrade twice and I have upgraded Magisk from 19000 to 19004 and I still have GP working.

On an S7 Flat with the Galaxy Project Oreo (latest version) ROM installed - so based off of the stock Oreo. :D
[Magisk] warrencoakley:
Tried and disabled Ad away and still no joy. I've tried about 5 different methods including my own that worked everytime but it still States the cannot pay in shops.
[Magisk] dvhttn:
If it wasn't clear I only disabled Adaway to enable me to add the card. After this I enabled it again and I have only used it for payment with Adaway enabled. I suspect that Adaway does have some effect as the 'recent activity' in GP only goes up until the last time I enabled my card - nothing since even though it makes payments correctly.

I know that to get my banking app (LLoyds here in the UK) to work correctly I have to add some urls to Adaway myself (search for 'santander banking app hide' or similar you you should find out which ones) so I'm assuming that one or two that Adaway blocks by default are the culprits. Just a hunch though ....
[Magisk] zencooler:
And the other suggestion made by one of this thread users is that after clearing GMS and reinstall GPay you have to add your cards with WI-FI off (on mobile data transmission only).

Of course later on (after all cards are set up) you can use mobile data or wi-fi as the problem is triggered during the process of adding cards. There is a database attestation state changed after this failed check. That's why even if you have your cards successfully added you will get an error during the payment. You can check this attestation state using GMS Toolbox written by another user on this thread.

Check it. Hope this is the clue.
[Magisk] 73sydney:
As i and others have pointed out many times, its pot luck, and little to do with what you do on your device

Ive been taking part in this thread since early, done all the tricks, and at most Pay will work for maybe a week before it stops working, Pay says i cant use it to pay, and i get a txt and email from my bank saying my card has been detached from my virtual wallet....

Worth noting i have never had wifi turned on while adding my cards, like ever...so disavow yourself of that, like every other theory here, working, right now....
[Magisk] wieman01:
Correlation <> causation. Tough, but true.
[Magisk] Nhyphk:
I have moto G6 Plus with Pie. Should I hide everything from Google Play Services? I have only one setting hidden from it, because of pogo.
[Magisk] baddevil2:
Hey guys,

I have the same problem as the bulk of users here.

Device: Xiaomi Mi 8

ROM: Pixel Experience

GMS/GPS: Tried latest beta but it recognizes root anyway. Downgraded to 14.7.99 , now I can add my card again, but can't pay with it

GPay: Tried with latest and downgraded to 2.85.x but no success

I can add the PayPal credit card without problems but if I put my device on the payment terminal it only says "unknown card".

Some weeks ago I was able to fix it with deleting com.android.google.gms and clearing cache of play services and play framework + magisk hide
[Magisk] warrencoakley:
Yes the same but that doesn't work for me anymore. Something has changed and a new work around is needed if any. :(
[Magisk] baddevil2:
The curious is, even my default banking app (Volksbank in Germany) is not working. It's exactly the same error. So maybe it is ROM/AOSP related?
[Magisk] iankelly2001:
Where can I download "GMS Toolbox", referred to above? Searches have drawn a blank for me.
[Magisk] Nekromantik:
Deleting or renaming gms folder method no longer working for me on pixel 2 XL running magisk 19 stable.
[Magisk] wieman01:
This is worth looking into. Nice observation in my opinion.
[Magisk] jcmm11:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/post79209796
[Magisk] warrencoakley:
My banking app is fine. Just can't add the cards anymore

---------- Post added at 12:01 PM ---------- Previous post was at 12:01 PM ----------

Yes me neither. Hope someone finds an alternative
[Magisk] zencooler:
Seems that nobody knows how it works exactely and many users have own experience and recommendations for GPay root recognising issue.

In my case as I wrote before it was an observation that clearing GMS and clearing GPay and set up them all again on clean both apps is a key of success. Of course with support of Magisk 19.x (updated regularly till version 19004) and hiding GPay, GMS and Google Play Framework in Magisk Hide + change of Magisk Manager name into random one (using Magisk Manager option to do this itself). Adding cards into a clear GPay and clear GMS was successfull and I use GPay with six different cards for contactless payments everyday with no problem at all. The only thing is that I keep the 2.85.x version of GPay and I do not update it. GMS and the rest is continuesly updating and it is not interferring with my GPay issue.

I am on this set up one month now and it is still working on daily basis bank transactions.

But it's possible it can work in different way on other hardware and ROMs versions. Personally I am on Note 9 (SM-N960F) with Dr's Ketan ROM P09 (based on Android Pie stock CSC1 firmware version).
[Magisk] joeyddr:
been almost 3 weeks and still working, I am on the latet pay and play servers and latest canary of magisk... the only thin i did different this time is NOT add my bank card, just paypal and it has been solid. The last few times after i add my bank card it only lasted about a day or 2.
[Magisk] PhotoPaul:
In the past I was adding a Chase issued Visa card and a Charles Schwab Mastercard and after one or two days it was breaking. This time I haven't added the Mastercard and it's been working for a couple weeks now.
[Magisk] MartinRK:
Just followed the methods, turn off wifi, hide google play service, Gpay in MagiskHide and clear cache then clear data of the two apps, and reboot. Open Gpay and delete all card I've added before and re-add my cards, but I cannot use contactless payments, how can I solve this?

Device: Xiaomi 9

Rom: MIUI 10 Global 9.3.22 beta

Google play service: 16.0.89 (100400-239467275)

Google pay: 2.86.243324902
[Magisk] wabmorgan:
Renaming the folder worked fine for me. ?

Same phone. Same magisk.

I do have the magisk package hidden in settings.
[Magisk] backslashV:
Followed this to the t and it didn't work.
[Magisk] warrencoakley:
Can't get this to open and install
[Magisk] alex1301:
Hey there,

rooted my Mi 9 recently and tried to add a card to GPay. It detects root even after I have hidden root in Magisk Manager, repacked the app and even tried to change the footprint.

I tried the lates canary build, but nothing.

This should not be a post about blaming Magisk, this is mostly a post for general information!
[Magisk] MartinRK:
Hey buddy, same issue here. I installed magisk 19.0 and magisk manager 7.1.1 on my Mi 9, installed magiskHide and changed my device fingerprint in terminal and I passed the safetynet test. But still I cannot use contactless payment in google pay. I know the magiskHide works because after I hided the Pokemon Go, it didn't show that "my system is rooted", and I could play this game. I wonder how google pay detects root.
[Magisk] PuffDaddy_d:
We were all warned about this years ago when safety net was first created. Developers were concerned that devices would become increasingly harder to root, and even when rooting, it would break core functionality of the device. Magisk was created to get around this, but it too was operating on borrowed time before Google found a workaround to Magisk's workaround. We'll just have to be patient until another exploit can be found to enable GPay, and hope the developer doesn't give up before it's found.
[Magisk] jcmm11:
Quoting Chainfire in the suhide-lite thread:

Quoting myself from the OP of the old suhide thread:

I still stand behind this statement I made a year ago.

I will add to this another concern that I've posted before: on the A/B layout devices such as the Google Pixel (XL), it is possible to detect the device is rooted with a handful of lines of code, and I do not see any way to beat this detection aside from custom kernels. As soon as this detection is added to SafetyNet, it is pretty much game over. Frankly I'm surprised it hasn't been added yet.
[Magisk] tech_head:
I run with a custom kernel installed. t hides the BL status from everything.

I can pass SafetyNet with no additional work with the custom kernel.

WIth root, it just needs to hide the root stuff.

Will they eventually figure it out? Yep, but a custom kernel should be able to hide anything.

I guess the next step will be building root into the custom kernel?
[Magisk] Saison2018:
Just for sharing knowledge/Information/Experience

Device: Huawei P20 Pro (CLT-L09)

ROM: EMUI 9.0.0.241, fingerprint change to 9.0.0.203 with "MagiskHide Props Config" module

GMS/GPS: 16.0.89

GPay: 2.86.243324902

I tried many workarounds but the only solution was to add Google Framework, Google Play Service and Google Pay to Magisk hide

AND

deleting GMS folder.

After doing this, I was able to finish configuration and to set payment.

This week, I was able to pay successfully in 2 different places with my phone.

I agree, deleting GMS folder "destroy" google config (SmartLock, google drive backup, .....) but it was easy in my case to reconfigure.

I hope this configuration will work as long as possible.
[Magisk] Gaaat:
I'm currently running a custom kernel which also hides bootloader status, still, GPay is able to detect my device is rooted
[Magisk] tech_head:
For Magisk (root) I hide the following and Google Pay just works;

Google Pay

Phone Services

I also have Root Checker Pro installed on my device and I hide it using Magisk hide.

This gives me an indication if hiding root is successful. If it ever detects root, then something is dramatically wrong.
[Magisk] highdiver_2000:
I just upgraded by MIUI 10 Open Beta. The full version from Mi.

As expected, lost my recovery and root. Put back both and touch nothing else. (Google Play Services and other Magisk modules get auto recovered)

Walk up to McD , ordered and paid using G Pay.
[Magisk] cawpin:
I just had a weird experience. I tried to use Android Pay twice this morning, within an hour of each other. First time worked, second time I got the "can't pay in store" error. Magisk Canary 19.0-8d4c4072 (19004) and Manager 7.1.1-8d4c4072 (206). Pixel 3 XL, Android 9 March 5 security patch. Android Pay 2.86.243324902
[Magisk] dbareis:
It sounds to me that there are potentially 3 or more likely different issues in this thread. V19 magisk solved the can't pay in store issue for me
[Magisk] BostonDan:
I also use AA Mirror which requires the use of phenotype patcher, which has to be installed first before Google pay can be used. I have tried the method multiple times and cannot pair cards for in store payments. I've given up until a method can be found as I need AA Mirror for my car.

Guess I'll just continue to lurk until a solution is found.

Cheers,

B.D.
[Magisk] dablado:
I'm able to use Pay with Xiaomi Mi9. I use the Magisk Manager 7.7.1 and Magisk v19.0

The issue is the Google Play Services. The last version detects Magisk. It's necesary downgrade to v14.7.99.

Enviado desde mi MI 9 mediante Tapatalk
[Magisk] zencooler:
Why did you write AA Phenotype Patcher has to be installed before GPay usage? What is the source of this info??? I use them both and I have no issue at all. AA Mirror works fine (patched via AA Phenotype Patcher) and GPay also works like a charm. I use latest Google Play Services and GPay 2.85.x with Magisk 19004. All works every day with few cards defined in GPay with no problem at all.
[Magisk] mcflyrk01:
wow i have tried EVERYTHING else and this is the only thing that has finally worked!! Pixel 2 XL on Colt OS, Magisk Canary v19.0, GPay v2.86.243324902, GPlay services 16.0.89
[Magisk] BostonDan:
Maybe it was from before with AA Unlock, but I found that if I tried to set up my wearos watch before I did AA Unlock, the AA Unlock would not take. I have been doing it this way ever since. As most people write YMMV.

Cheers,

B.D.
[Magisk] ajm786:
Awesome! Ever since that post, GPay has been going strong for me. I've used it pretty much every single day, even this afternoon at my favorite bakery.
[Magisk] redmictian:
For Russian users or anyone who can use bank applications which can use GPay services without installing app itself.

There is one Russian bank - Sberbank which provides Gpay without installing the app.

1) Install the app

2) Install last Magisk (19) and hide Sberbank app and Google services

3) Open Sberbank app

4) Click on your card

5) Add to Gpay

6) Works for me
[Magisk] fightinfilipino:
for anyone on a Pixel 3XL (and presumably also the Pixel 3), i managed to get GPay working (cards added and pay-in-store working) after some frustrating trial and error. thanks to [MENTION=3106156]ajm786[/MENTION] and [MENTION=5571261]michaelbaxter[/MENTION] for their steps and feedback. this is what i ended up doing:

1. Make sure Google Account backup setting is turned OFF, and delete any Android backups on Google Drive (instructions should be here: https://support.google.com/drive/answer/6305834?co=GENIE.Platform=Android&hl=en)

2. Install the April update (non-wipe) (following instructions from this thread: https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195)

3. Boot TWRP (v3.2.3-5, newer version could not decrypt phone) (following instructions from same thread above) and installed TWRP (also v3.2.3-5).

4. Install Magisk Uninstaller zip to uninstall prior versions of Magisk. Booted into system and then rebooted back to TWRP recovery.

5. Installed Magisk Canary (following instructions from the Canary thread: https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337).

6. Booted back into system. Deleted /data/data/com.google.android.gms folder.

7. Hide all Google Play services, Google Play, and Google Pay using Magisk Hide. You'll need to check "Show system apps" in the Magisk Hide settings. I also hid Carrier Services and Phone Services. Am not sure if the latter are actually required.

8. Run the SafetyNet check in Magisk Manager. If 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.

9.*If you have WiFi turned on, TURN IT OFF.

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

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

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

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

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

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

16. Upon rebooting,*ensure WiFi is turned off, then immediately open GPay and start adding your cards.

following the above, i was able to successfully add three different cards and use GPay in three separate stores without error. i do have WiFi still turned off. am not sure if turning WiFi back on will cause problems. anyone have feedback on WiFi causing issues?

edit: interestingly enough, after i did this, i am unable to get Fate GO to run, getting the dreaded Error 61 there. everything else seems to be working fine including banking/card apps, Fire Emblem Heroes.

edit 4/23: just successfully used GPay again in store. this is after i turned WiFi and backups back on. knock on wood!
[Magisk] BostonDan:
Just a question, after doing this can you turn backup back on, or must it stay off?

Cheers,

B.D.