yashsingh1/xdaforums huggingface dataset:
[Magisk] beren:
i can confirm that these steps are working (actually i did not update Pay and GPS), for adding cards to Gpay app....couldn't check if payments are working yet...

at the end of steps asked me to turn on wifi scanning (i choose NO), is this needed to perform payment?

I am on pixel 2 xl stock rom + magisk 19.
[Magisk] Kirahvi:
Google pay working with latest OOS beta (27) and magisk 19.0 no other tricks performed.

Didn't work with the same build and magisk 18.1

Big thanks to everyone involved with magisk, until the next **** up by google...
[Magisk] queerquirks:
My magisk got upgraded to v19 last Friday and it worked for 2 days. Failed again today for Gpay
[Magisk] 73sydney:
Why arent people getting that none of the posted fixes last....

Can we stop posting misinformation, i.ee that just because you got your card working doesnt mean a thing, and its a bonus it worked for a couple of days, this is not a fix....

All this is doing is sending people around in a circle of half-assedness

Its been said plenty of times but people are choosing to ignore it, the real damage is done not on your device ,its done on googles end....

This is my last attempt to inject some sanity here...i fully expect that this will just keep going in a "heres how i got my card accepted on my device" posts vein....that is not a win, anyone can do that.....youre not wining over google folks, its a temporary reprieve...
[Magisk] rodrigofd:
Working solution - Possible theory

My solution: (S10+, with Magisk 19.1, Magisk Manager 7.1.2)

* Ensure you have latest Google Play Services, Google Pay

* Wipe data from both . Turn off all connections, reboot

* Find some different internet connection... it could be a far away cell antenna, with different public ip, or a public wifi, etc. and connect to it

* Try adding the cards again

I suspect Google or the processors might be running some kind of IP or gateway blacklisting.

Please share your results!

Cheers!
[Magisk] jsylvia007:
I concur with this 100%. I originally came here to track solutions that might last, and what it seems more of is "works for me, but I had to sacrifice an old ball mouse, and add my cards via 8-track".
[Magisk] Freshek:
I think Google has to finally notice that we, the advanced users, should be able to use Google Pay. It's not really a security risk to us as we are aware of what applications we install on our phones. I think a *real* solution for this issue will be found later or sooner, but it's an endless circle - we find a workaround, Google patches it. This breaks the whole concept of mobile payments.

Maybe we should start a petition on change.org? :D
[Magisk] dvhttn:
Still going after updating to the latest 19x release but other details as above .... No old versions of GPS just the latest ones. So that's from about mid-March now ....
[Magisk] D-m-x:
While I do like to say that you are right, at least I have the same opinion, I will also tell you that this is a waste of time. They won't care. If not for some smart Dev GPay on altered Phones is done for.
[Magisk] zencooler:
It doesn't make sense as you are always on different IP each time your are traveling, reconnecting, restarting etc.

I am pretty sure Google is doing nothing with network identification.

You just need to remove all GPay and GMS data from your phone after failed identification to get rid your trace and set up all your cards again of course after the SafetyNet passed and GPay, GMS and Google Play Framework are hidden in Magisk Hide.
[Magisk] warrencoakley:
Has anyone update to the April security patch yet and still has it working?
[Magisk] frozst:
Same problem here, mine stopped working on the 1st march (UK). I wonder if unistalling magisk completely will make it work again? I am not that bothered about root to be honest. Thanks!
[Magisk] vettean:
Well the one fix that seems to work flawlessly all the time is actually the simplest: Just enable Magisk Core Mode. Google Pay has worked for me everytime for the past couple of weeks. No deleting, renaming, reinstalling, etc. necessary.

Now this may not be ideal for those who really want their modules, but no biggie for me. The only module I would miss was Dolby Atmos. So I just installed it as a separate app via TWRP.
[Magisk] ctzw:
Any conclusions now to make things work? I have a S9+ G965F, booted to TWRP, and flashed the magisk 19 zip mentioned in this thread, and caused my phone to boot loop..... Had to wipe system and reinstall everything.....
[Magisk] dbareis:
Clearing GSM data is worse than the original problem, I needed to factory reset my watch for starters, many other things lost including Google fit data. Didn't fix it either.

All I had to do was install the latest beta magisk to solve my gpay issue
[Magisk] vMAC:
Let me know if that works for you.
[Magisk] Dunge2:
Which subprocess of Google Play Services do we need to hide? All of them or only com.google.android.gms and .unstable?

Is clearing Pay cache and reinstalling it enough or do you really need to delete that gms folder? More importantly, what does it impact? Lost of purchase card and history, but does it clear other Google Play elements like game saves and stuff?
[Magisk] ls117:
Got mines working, I didn't see anyone mention using the magisk hide module. I had to change my device fingerprint(axon7), and the ctsprofile failure finally stopped. I've never actually been able to add a card to wallet that worked, so I'm not even sure what I can do with it besides the obvious. My question is does this allow you to spend your wallet balance without having to transfer it? Eager to try this as I've never used NFC before.
[Magisk] warrencoakley:
Can confirm it is still holding after flashing April security update. Magisk Canary, stock, Pixel 2 XL
[Magisk] Dazzel:
Still working over a few weeks on my Oneplus 5T with latest LOS. Using the Magisk Beta Channel right now and no changes to the device fingerprint.
[Magisk] pgriffith:
Like everyone else here, my GPay stopped working a couple of weeks ago. So I switched to my Banks app for touch & pay, same functionality, but GPay scans WAY quicker for whatever reason.

Since then I've updated to Magisk 19 and have hidden the usual Google services. For ****s and giggles I thought I'd try it at my local restaurant tonight as I know them well, and they wouldn't mind me having to take the time to switch my phone over to my banks app for tap & pay. Lo & behold it worked just fine, went to the supermarket afterwards and used it twice more, no issues. So no deleting/renaming files or anything, not using core and not hiding Magisk itself, just worked for me ... for how long who knows? Nexus 6P, latest Google image (Dec I think).
[Magisk] Nekromantik:
On a clean ROM install I installed Pay and added it to Magisk 19 hide along with play services. Then tried to add card but nope.

This is on Pixel 2 XL.
[Magisk] zencooler:
You have to clear Google Play Service cache and data and then reinstall GPay and hide Google apps and add your cards again. Detail manual you can find in previous posts by many users. It will work for you.
[Magisk] Nekromantik:
Yup did that.

No go.
[Magisk] zencooler:
What exactely you have an issue? What is a problem with adding cards to GPay? Are you getting any error messages? Send some screens or write detail info.
[Magisk] wabmorgan:
Anyone ?
[Magisk] warrencoakley:
Yes I have and it's working fine on Canary build
[Magisk] Nekromantik:
Just the normal this card cannot be added as phone is rooted or modified.
[Magisk] sheik124:
Well, that was anti-climactic...

I came here looking for something crazy, but fixing this on my V20 (stock AT&T rooted Oreo, latest Magisk Manager and Magisk) was this easy:

Force stop Google Pay

Open Magisk Hide, enable literally everything with "Google" in the name

Clear cache for Google Pay

I added two cards and just bought a pack of cigarettes. No more error message...

Didn't touch the cache or data for Play Services.
[Magisk] jasonbiggs:
I kept getting that message when trying to add my cards but as of today Google Pay just sent to me an email as attached. I clicked on the link to open Google pay and my cards added! Go figure. Next test will be to see if they actually work to make purchases.
[Magisk] sensen_21:
hi, can anyone help me? Im using magisk 18.1, having trouble running my mobile banking app since they're updated, they refuse to work in root phone

previous version mobile banking apps work perfectly, i already activate magisk hide & put my mobile banking there

any solution pls?
[Magisk] klaberte:
Same for me. Perhaps I need to downgrade Google Pay?
[Magisk] nomesrjp:
Don't bother, it doesn't change the outcome (went to v2.81.x). I think it's a recent backend change that's caused it.
[Magisk] karnasw:
That works. Thank you :)

Edit: I said that too early. Standard error few seconds later. :/

I tried every solution in this thread. None of them works. I have Magisk 19.
[Magisk] wieman01:
Reading this thread and the solutions provided would be a good start.
[Magisk] Pierreken:
Tried this today, enabled them all, deleted cache of google pay app (not data) and tried to add a card but still gave the message about rooted or altered phone.

CORRECTION: I was still on Magisk v18.x. After updating to Magisk v19 (beta) I could add my card and I just bought something from the vending machine with my phone. Thank you!
[Magisk] absinth4:
Nice! thats a saver! With the method in the 1st page posts u need to do the trick every day from what i've experienced. I tried it yesterday and worked fine for acouple of purchases but this morning i couldnt pay again (along with the same message). Tried the solution above and it works perfectly, but only with the magisgk v.19. Thanks heroes!
[Magisk] EthanITA:
Actually for who has issues about Google Pay detecting root, can try to hide root from Google Play Services. After that it's worth trying to clear data/cache of Google Pay or reboot. I'm with Magisk 18.1, once I've hidden root from Google Services, Google Pay doesn't show the warning message anymore.
[Magisk] CSX321:
I expect you'll probably have the same issue with v19. I've got v19, done all the things to make it work, had it working fine Mon-Wed, didn't use it yesterday, then today just now: fail. I guess I'll just use my watch to pay from now on, unless and until this gets figured out.
[Magisk] wabmorgan:
Updated to April security update for Pixel 2 XL. Magisk v19. Was able to use Gpay to make a purchase.
[Magisk] dbareis:
I'm on v19, 2 days in a row I've used Google pay successfully, I did decide to hide all Android/Google user and system apps I could see... I didn't clear data or cache to get it to work.

Looks like you went 3 days, oh well let's see how I go...
[Magisk] bigknowz:
Phoenix Wright solution

Flashed DU April update today, and the /data/data/com.google.android.gms.bak solution still working, deleted and then added a card to confirm. Original (unless someone else figured it out first) post is here.
[Magisk] highdiver_2000:
Mine was working for the past week. Today 6 Apr. I tried to pay at BK. It said I can't pay in store
[Magisk] TerrorApple:
Magisk 19?
[Magisk] ToRvaLDs:
Same here, Magisk 19.

Inviato dal mio MI 8 utilizzando Tapatalk
[Magisk] highdiver_2000:
Yeah Magisk 19 beta
[Magisk] Superschmiddi:
There is a Google Pay update out now, is it save to install? Im on Magisk v19 and Manager 7.1.1
[Magisk] finesse:
Good question, I came to ask too.... I'm using V19 & previously deleted the gms folder.
[Magisk] nomesrjp:
Latest Google Pay and Magisk, no issues whatsoever, providing you follow earlier advice.
[Magisk] davekaye:
OnePlus - Oxygen OS

I'm on a OnePlus 5T, rooted, using latest version of Oxygen OS. Google Pay didn't work. Upgraded Magisk to the Beta track and Google Pay started to work. I was able to add an Amex card, but had trouble with a Chase card which I seldom use, so not an issue. GPay now works at a local POS terminal. Thanks to all for the suggestion to upgrade Magisk. to the Beta track.
[Magisk] Pro4TLZZ:
ok just to be clear what do i have to do to use gpay on op5?
[Magisk] Adramel:
Magisk 19

Remove the card from GPay, uninstall GPay, delete/rename data/data/com.google.android.gms

Install GPay and add a card.

After each GPS upgrade, you must repeat this procedure.
[Magisk] Pro4TLZZ:
thanks bud, will do
[Magisk] xxxvego:
From Monday to yesterday GPay worked without a problem, yesterday I paid contactlessly in the store. Today I could not pay anymore, but I just managed to reconfigure contactless payments (I do not know for how long), the steps I've taken:

1. Remove card from GPay

2. Force stop GPay, clear cache and data GPay

3. Rename data/data/com.google.android.gms to data/data/com.google.android.gms.bak

4. Reboot and add card.

Magisk 19.1 beta, 7.1 Manager
[Magisk] seco2004:
I have an OnePlus 5 too, all I had to do was install Magisk Beta 19.0, no other workaround was necessary.
[Magisk] Tr4sHCr4fT:
So can GPay & v19 be now considered as "working for most" or "working for some"?
[Magisk] vettean:
I have Magisk v.19 installed and have tried all workarounds mentioned in this long thread, but no luck in getting my Chase Visa verified on my Galaxy S5 phone. However, no problem with getting PayPal activated. I don't get why one card and the not the other was able to be added.

Just for the heck of it, I installed Google Pay on the Galaxy Tab S3 to see if I could get my Chase Visa verified by the Chase Bank. No problem getting the card verified on the tablet although it still has Magisk v.18.1 installed.
[Magisk] D-m-x:
Same as before. Working for some but only for a limited time. Totally random, can work for hours, days, weeks. There is no definite fix for this since nobody does anything special, just the same steps that have been explained before.
[Magisk] c3k:
3 weeks in core mode, stable and updated versions, no problem
[Magisk] Goose1701:
On a OnePlus 5t, ran into the issue of not being able to use Pay in stores a couple of weeks ago on 18.1(have always had everything with google in the name hid). Switched to core mode and still didn't work. Decided yesterday to updated to 19.0 beta and had no issue adding a card. Went to the store today and was able to purchase some items. We'll see how long it lasts.
[Magisk] dbareis:
V19 had now worked for a week for me, I did also hide every googleish app I could identify
[Magisk] HorstigerHorst:
Quick question ...

If I'd buy a smartwatch with Gpay integrated, will it be corrupted by my rooted phone?

Since right now I can't get Gpay to work, even though I have 7.1.1 and 19.0 installed and pass the safetynet-tests.
[Magisk] Dunge2:
I'll ask again:

1. Which subprocess of Google Play Services do we need to hide? All of them or only com.google.android.gms and .unstable?

2. Is clearing Pay cache and reinstalling it enough or do you really need to delete that gms folder? More importantly, what does it impact? Lost of purchase card and history, but does it clear other Google Play elements like game saves and stuff?
[Magisk] highdiver_2000:
rename com.google.android.gms to com.google.android.gms.1

You can rename the gms folder only.

Purchase history is kept in the Pay app. If you reinstall the app, history is lost. You might be able to find it in Google web site. Maybe.

Your Google Backup settings will be cleared. You need to set this.

Location History is turned off. If this is important (it is for me), turn it back on.

Games stuff is handled by Google Games. Google Play Services is a transport for it.

Disable Googe Pay auto updates
[Magisk] Dunge2:
I'm talking about the list of checkmarks under Magisk Hide, not files.

Strangely, clearing Pay data and reinstalling it kept my cards and history. That's why I'm here, it didn't fix my pay and was wondering if I had to rename files.

Surely there's more in the whole Google Play folder than just the backup and cards?
[Magisk] backslashV:
Pixel 2 XL on April update with Magisk 19 beta and GPay is still not working.
[Magisk] ToRvaLDs:
Yes there's more, but not essential, it will recreate data at boot. I'm trying to find which is the folders/files that prevent gpay to work in order to delete only that.

Inviato dal mio MI 8 utilizzando Tapatalk
[Magisk] NeuesS5:
After the last post I was motivated to try it again:

Cell Phone: Samsung Galaxy S5 G900f

LineageOs 16 from 2019_03_27

Magisk 18.1 (core functions only)

Filtered in google for Magisk Hide

and everything on hide:

com.android.chrome

com.android.vending

com.google.android.apps.adm

com.google.android.apps.authenticator2

com.google.android.apps.docs

com.google.android.apps.docs.editors.docs

com.google.android.apps.docs.editors.sheets

com.google.android.apps.fitness

com.google.android.apps.forscience.whistlepunk

com.google.android.apps.googleassistant

com.google.android.apps.maps

com.google.android.apps.nbu.files

com.google.android.apps.paidtasks

com.google.android.apps.photos.scanner

com.google.android.apps.restore

com.google.android.apps.tachyon

com.google.android.apps.translate

com.google.android.apps.turbo

com.google.android.apps.walletnfcrel

com.google.android.apps.wellbeing

com.google.android.backuptransport

com.google.android.calendar

com.google.android.carriersetup

com.google.android.configupdater

com.google.android.ext.services

com.google.android.ext.shared

com.google.android.feedback

com.google.android.gm

com.google.android.gms

com.google.android.gms.setup

com.google.android.gms/.droidguard.DroidGuardService

com.google.android.GoogleCamera

com.google.android.googlequicksearchbox

com.google.android.gsf

com.google.android.markup

com.google.android.onetimeinitializer

com.google.android.packageinstaller

com.google.android.partnersetup

com.google.android.play.games

com.google.android.setupwizard

com.google.android.stardroid

com.google.android.syncadapters.calendar

com.google.android.syncadapters.contacts

com.google.android.tts

com.google.android.youtube

com.governikus.ausweisapp2

com.paypal.android.p2pmobile

de.aoksystems.ma.abp.app

de.hafas.android.db

de.payback.client.android

Set.

Then Google Pay memory deleted as a precaution also again memory with TitaniumBackup data deleted.

Booted into the TWRP

there under / data / data com.google.android.gms deleted

Restarted

Paypal with APP set up in Google Pay.

Works with me
[Magisk] ToRvaLDs:
Same here, but after some days it stop working again

Inviato dal mio MI 8 utilizzando Tapatalk
[Magisk] gooomis:
Hi,

I've tried possibly every fix from here, on Magisk 18.1, 19 and 19.1, and it still doesn't want to work.

My device is Mi 8 (dipper) and currently on Syberia 2.4.

I can add my card and unfortunately, I cannot pay with it, no error whatsoever.

Logcat is filled with "PaymentMethodAdapter: Action fix flow description is missing" and "PayMethodFilterEval: The payment method's token state is unknown".

Dunno what else to do.
[Magisk] highdiver_2000:
Hide Googe Pay and in settings check Magisk Hide

Interesting. Please note. There is Google Pay and Google Play Services (aka gms)

[/quote]

Google Play folder or Gms or Google Play services does a lot of other stuff (makes Maps work, location awareness etc) You can google it.
[Magisk] Dunge2:
Sorry to be pedentic about this, but I want to be sure there's a proper answer. Other posts mention hiding everything under Play Services too, and the list look like this:

[IMG="hide"]https://i.imgur.com/cqX5jqS_d.jpg?maxwidth=640[/IMG]

I've also read that the more things are hidden, the more performance it requires (hence why they aren't by default), so I would like to avoid unnecessary otems if possible. But maybe I'm just overthinking this.

Hence why I'm hesitant to delete it. Oh well, tons of other persons in this thread did it and nobody reported back with any important things missing, so I might just do it.
[Magisk] martyfender:
Don't hide this:

com.android.chrome

Many functions in Android depend on Android System Webview and versions of Android newer than 6 use Chrome's System Webview, instead of the standalone version. Also, it is very questionable that you need to hide many of the other ones on your list. It could potentially lead to unexpected results or system instability.

However, it may work for you and others. I am just sharing what I know about potential problems.
[Magisk] D-m-x:
It can break stuff. I deleted it to try some things and suddenly I couldn't access some settings (Google Play Protect for example). Deleting that folder also resets your Google Settings on this device.

Gesendet von meinem SHIELD Tablet K1 mit Tapatalk
[Magisk] highdiver_2000:
Magisk Hide means hiding root from the app. You are not denying it permissions to work.

Yes. I have hidden everything under com.google.android.gms with no side effects. So far.

You might want to re-read my previous post
[Magisk] Windroid-user:
Other people say they use their smartwatch fine even though their linked phone does not work with Gpay.

So the problem does not spread to other linked devices, and I guess it makes sense since the reason this is happening is because it is detecting root in our devices which is a security risk... Unfortunately.
[Magisk] HorstigerHorst:
Please don't get me wrong :o

So far I have not received the Smartwatch yet!

I was asking if there are known problems with that setup.

Funny thing though:

It seems like a custom ROM and Magisk don't "kill" the Google Pay app on a Huawei Watch 2 (Classic or LTE).
[Magisk] mkz14:
I have a Mi8 with Pixel Experience CAF and tried paying with this and LOS16 but never worked.

Tried magisk 18 and 19 hiding my bank app and It lets me install the credit card but when I'm about to pay It never pops...

Dunno how to fix it...
[Magisk] tkawa:
THX

Thank you for your guide. :svetius:

I followed it all and it works for me well. :):):)

Xiaomi Mi8EE with mi-globe ROM 9-3-28 + Magisk 19.0
[Magisk] Pro4TLZZ:
Got stuck in step 3. Wasn't able to contact server on opening gpay. Had to name folder back to .gms
[Magisk] highdiver_2000:
After rename gms, you need to restart the phone. Then install gpay
[Magisk] upperbladez:
Can you make a video of this?
[Magisk] martyfender:
Has anyone updated to the new gpay, released today? Is it working for you?
[Magisk] D-m-x:
Or a Broadway show lol

His steps are pretty forward. These are also the same steps that have been described countless times in here, just in other words.
[Magisk] upperbladez:
Are you his friend?
[Magisk] Bradster321:
Hi all sorry for interrupting but I've had magisk working fine (kind of) on v18.1 but when i update to v19 safetynet fails and I've tried all sorts like hiding magisk as well as google play store, services and etc the universal safetynet patch doesn't work and I've even tried it in core mode and done a fresh install, idk what else to try. i would use v18 however idk a permanent fix for google pay, i downgrade google play services and it works however it just ends up auto updating even when i disable background usage, permissions and admins. Help would be much appreciated, cheers

sorry if its a tedious question i've been searching everywhere but i cant seem to get a solution since magisk 19 is so new, plus i've only first heard of magisk last week so i'm not knowledgeable on the subject.

Samsung s9+

Magisk 19

ElementalX kernal
[Magisk] warrencoakley:
Yes working fine

---------- Post added 10th April 2019 at 12:02 AM ---------- Previous post was 9th April 2019 at 11:58 PM ----------

Go follow the steps that's been repeated many times on other pages. The key really is Magisk Canary build, clear cache of GPay, deleting GMS folder, uninstall GPay, reinstall and add cards. P.S make sure you hide all Google related apps,services and banking apps and then hide Magisk Canary too.
[Magisk] warrencoakley:
I stand corrected, it breaks GPay and you cannot pay. I will try the workaround again and see if it works.
[Magisk] ajm786:
Not for me. I upgraded to the latest GPay last night. Just bought a bottle of water at work with it this morning.

Using the steps I had posted a while back, I'm going strong at least a week and a half. :D