yashsingh1/xdaforums huggingface dataset:
[Magisk] tom1807:
No idea what I did wrong, but using a OnePlus3T installed Magisk v19.0 (19000) and Magisk Manager v7.1.1.

GooglePlayServices is on 16.0.91 and GPay (v2.86.243324902) works. I didn't find Google Pay initially in the Magisk Hide after Setup, so I selected "Show System apps" selected Google Pay and in Google Play Services the "com.google.android.gms.unstable" and since April 25 Google Pay works.

Cheers

Tom
[Magisk] zencooler:
Mine was also working with no problem (more than a month) up to the version 16.0.91 but when GMS has been updated to 17.1.1 (with no changes of GPay version) the attestation state failed after one day of using GPay. I checked this two times. The second time after clearing GMS and GPay and setting up cards the same result was the same: one day using and then failed again.

So I think the new version of GMS (17.x) is much more smart in root recognizing.

I do not know how to successfully keep GMS in the previous version (if I downgrade it). All settings of GMS in Service Disabler app done for GMS (UpdateSchedulerService and SystemUpdateService are off) and also "Allow for Background Data" is off in the application settings.

Any other suggestion how to keep GMS version and disallow for auto update?
[Magisk] ssceddie:
I would to try another app like service disabler, maybe this app works not correctly. At my SM-G960F it works with this app: Disable Service 1.6.5
[Magisk] Adramel:
And how does it work? Is this an old version of Magisk?

It does not install with me
[Magisk] zencooler:
It's not for disabling services. It is simple, very good tool for checking attestation tests trigger (you can check it instead of being surprised in the shop when you trying to pay using GPay).
[Magisk] Adramel:
But how to install it? For me it is reported as an upgrade MagiskMenager. Should I delete the current version?
[Magisk] pr0adam:
And how long has it been since you've done that?
[Magisk] highdiver_2000:
Google Play Services 16.0.89 ran for like 3 weeks. All I did in late March was hide Play services and rename the GMS folder. I did not restrict it in any way.

Pay app, I stopped updates. This appears to have a minimal role to play in the new Magisk-hide busting action. I have manually updated with no ill effects.

When Google Play Services updated to 16.0.91, everything broke again. Cleared the data and Hide Google Services Framework to no success. I renamed the GMS folder, it still did not work.

Removed updates to Play Services and installed 16.0.89. Disabled the updates for it. The rest is in my previous post.

Now both app and service updates are disabled.
[Magisk] warrencoakley:
How do you disable updates for GMS. I have tried everything and it seems it automatically updates itself afterwards "support libraries" thing. I do think the GMS updates us what is breaking it so if I can stay on a previous one and it doesn't update all should be good.
[Magisk] MRL3GS:
Just updated to Magisk 19.1 and deleted the GMS folder and I can now add my card again

---------- Post added at 10:34 PM ---------- Previous post was at 10:34 PM ----------

Any plans to update this app to add the gms feature?
[Magisk] tiga05:
Updated to magisk 19.1 some minutes ago(official update, No beta!). Tried to add a new card. It works( at 18.x it didn't!). I will try to pay something with my credit card tomorrow.

Edit: I did nothing nothing special like deleting anything. But my magisk is running in "hide mode" and I am hiding google, google play services and google pay

Edit2: I was looking for a donate button. Am I blind? Is there no possibility to keep this great work up with some money?
[Magisk] Windroid-user:
Wow I feel bad for you guys... up until March Gpay was working fine for me, I had to fix it twice, first fix made me switch from magisk 18 to magisk 18.2 with all the wiping gms and folder things, second fix simply required me to upgrade to magisk 19.

Gpay has now been working for three weeks (since 12 April)

Both Google Play Services and Google Pay are up to date.

GMS = 16.0.91

Gpay = 2.86.243324902

It's a galaxy note 4 so it is definitely not up to date in terms of security, also it works great, sometimes too great... it can buzz like crazy until you move it away, this rarely happens though. I think because NFC is too sensitive, may be due to the 10000 mah battery with a more sensitive NFC chip than in standard battery.

Basically NFC is built into the battery for those that do not know, but it's in different places for different phones.

There is a step by step guide I posted somewhere of how I did it, if you want I can locate it but I doubt it will work any different given the amount of tutorials/guides posted on here (pretty much) daily.
[Magisk] highdiver_2000:
I use this https://xdaforums.com/showpost.php?p=79417757&postcount=1100
[Magisk] altwu:
i have a verizon google pixel xl and when i was running the march and april updates, i couldn't pay with google pay. my credit card was already added, so i didn't try adding card. i couldn't use google pay to pay. i would get the message "You can no longer pay in stores with google pay." i updated to magisk 19.1, hid google pay and google play services, and i can use google pay again! thanks [MENTION=4470081]topjohnwu[/MENTION]!

verizon google pixel xl

android build PQ2A.190405.003

google pay version 2.86.243324902

google play services version 16.0.91 (100400-244116403)
[Magisk] LLStarks:
Apparently changing your fingerprint with the MagiskHide Props Config is enough to at least add a card before failing again soon after.

https://www.reddit.com/r/Android/comments/bjl5ld/magisk_v191_stable_release_now_out/emad40n/

Credit to trunks.
[Magisk] jcmm11:
Look at the bottom of the Magisk Manager app. There's both a PayPal and Patreon button.
[Magisk] warrencoakley:
Yes i have these installed in Google Pixel 2 XL but it still updates the support libraries automatically even with these unchecked.
[Magisk] D-m-x:
So, as I'm goind to need GPay to work in a few weeks: I'm assuming GPay works when running the phone unlocked hiding the unlocked Bootloader with a Custom Kernel but without Magisk (rooting)? Or does everything need to be a 100% Stock for it to work without hiccups?
[Magisk] zencooler:
None of these methods are preventing of GMS update. Even if you switch off all update, scheduled updates, system update etc. services inside GMS.

The only way to stop update is remove permissions of downloads cache folder. But aware it will stop also updates you can do manually via Google Play Store as this folder is a common place to cache downloads.

I use this trick by simple script removing folder /data/data/com.android.providers.download/cache then creating empty file with the same name (/data/data/com.android.providers.download/cache). This is because removing is not preventing Play Services to create cache folders again automatically. But if there is such file they cannot do this and it finally stops updates :)

I created also simple script to remove this cache file if I want to update something manually. Then immediately use script again to create cache file to prevent GMS to be updated. Works like a charm.
[Magisk] warrencoakley:
Can you share on how I can do this please in a detailed post possibly?
[Magisk] zencooler:
You don't need to write scripts as you can do the same trick manually via any file explorer with granted root permission (e. g. ES File Explorer or FX Explorer etc.).

If you are not familiar with scripts you can write a task in any tool that is able to run she'll commands (e. g. Tasker).

My scripts are very simple.

1. To prevent of updating:

rm -r /data/data/com.android.providers.downloads/cache

touch /data/data/com.android.providers.downloads/cache

2. To allow updates again:

rm -r /data/data/com.android.providers.downloads/cache

Regards.
[Magisk] gregwee:
I just updated Magisk from 18.1 to 19.1, hide GPay and Google Play Services in Magisk, and now, I can activate my credit card in GPay again... Previously, it refused to activate, always giving the error that the phone was altered..
[Magisk] Superschmiddi:
"DisableService" prevents GMS from updating on my Google Pixel 2 XL.

Also there is Magisk Manager 7.1.2 (209) and Magisk v19.2 (19101) out now. Maybe it fixes the root detection too.

Nevertheless I let the update services stay disabled, works so far for me.
[Magisk] Itachisasuke:
I was hoping I'd be in the same boat but just updated to 19.1 and rehid GPay and Services but still can't add cards.

I didn't blow away the Google Play Services data folder just a straight upgrade to 19.1 with MagiskHide enabled.
[Magisk] gregwee:
I was just re-activating a card that I previously added before GPay started giving me issues when I tried paying... I didn't try to add a new card. In any case, I don't expect this solution to last very long as Google seems to be ever updating/changing to detect root... I'm hoping to buy a watch soon that allows GPay to be used, so I can just use the watch instead of the phone...

I didn't blow away the Google Play folder or clear any data/cache either.. It just started working for me after the update and reboot..
[Magisk] Itachisasuke:
Yeah my original cards are still activated but I just tried hitting the vending machine at work and no dice still. Not a huge deal as I always have my card.

I'm actually more interested from a technical perspective how the root detection is working. I know both topjohnwu and Chainfire said its fairly easy to detect regardless of how we try to hide it.
[Magisk] warrencoakley:
How do you do that?
[Magisk] Superschmiddi:
Download Disable Service APK here and uncheck like on the attatched screenshots.

Also I hid the common things in Magisk.
[Magisk] Tr4sHCr4fT:
I think some banks are doing perma-ban of GPay when it once failed attestation. I can't add a Revolut card to my phone, but could add it to my WearOS watch. Also i can't add my comdirect card at all. All other cards and PayPal work fine...
[Magisk] warrencoakley:
So what version of GMS are you on?

When I try to revert back to 14.7.99 after a few minutes it automatically updates back to 16.

"Updating support libraries" comes up and starts downloading.

I have that app installed and unticked.
[Magisk] Superschmiddi:
16.0.91
[Magisk] warrencoakley:
Yes I'd like to go back to 14.7.99 but your method even though I'm on 16 will not stop it updating back to 16 in a matter of seconds.
[Magisk] zencooler:
True. That's why I wrote you cannot stop GMS autoupdate using this kind of methods. Even if you stop part of GMS services the other Google apps will update libraries and finally this updates GMS.

The only way is to stop any updates on lower level. I am using my idea of download cache blocking and it is successfull story ;) I explained details few posts before on this thread.
[Magisk] Superschmiddi:
But mine isnt updating anymore. I read some pages back, that GMS is on v 17.x.x. ?
[Magisk] zencooler:
GMS version is platform dependent. Means that on some phones the newest version is 16.0.91, on some 17.1.22 and on some 16.0.89 etc. It's possible that on your phone 16.0.91 is the latest one yet...
[Magisk] warrencoakley:
So how do I action these then please do I can try it out and see if I will remain on 14.7.99

Do I run these in terminal?

How do I do it via a file explorer?

Thanks for your help.
[Magisk] Dark_Eyes_:
YMMV, but I tried using GPay after a complete factory reset, no Magisk whatsoever, stock recovery but a custom kernel to hide the bootloader unlock. Though the hack to hide the unlocked bootloader appeared to work, I still wasn't able to use GPay. If you really need GPay to work reliably, I advice you to lock the bootloader (and go back to pure stock beforehand)...
[Magisk] TraderJack:
I am trying to follow mmf01's post here to get Gpay to work on my Pixel 3 XL running stock April update.

I *did* install TWRP to the bootloader and if GPay can't work with that configuration I will go ahead and remove that.

I currently also have Magisk 19.1 installed, and understand that I will probably need to install Canary.

HOWEVER, I see no mention of "Google Services Framework" ("com.google.android.gsf") anywhere on my phone.

It isn't listed in my installed apps nor is it shows in Magisk's hide function.

Is this something that I will magically see when I install Canary?

UPDATE: Never mine, ID10T error. I needed to show system apps in Magisk.

I got this working WITH TWRP INSTALLED TO MY BOOT PARTITION following mmf01's post.

Thanks
[Magisk] beatschubser:
Oh, sorry - Play service version is 15.0.90
[Magisk] nahsha:
I'm on v. 15.0.90 of play services using magisk 18.1, safety net passes, google pay (hidden in magisk) detects phone as rooted. I'm unable to disable/uninstall updates in play services (greyed out). I'm using a oneplus 5, (stable 9.0.3 pie ROM)
[Magisk] xocomaox:
Working for me. Play Services 15.0.90. Magisk v18

Here's what I did:

Originally I had a newer version of Play Services and couldn't register my card. I followed the downgrade instructions here to get 14.7.99.

This allowed me to register my card successfully. However, I didn't have a terminal on hand to test.

Today I had a terminal available, but noticed Play Services automatically updated. I guess you cannot stop this from happening?

I tested it and it was fine!
[Magisk] tlf55:
Yes with all blocked I was able to pay with NFC in store
[Magisk] joeyddr:
what phone OS?
[Magisk] JarlPenguin:
Detach it from Google Play
[Magisk] kradcliffe:
OK, I had this bug yesterday, but deleting the cache and data on Google Pay then setting my card up again seems to have worked. (Note 8, Magisk 17.1)

I couldn't downgrade Play Services as it gave constant errors. Currently 15.0.90 and Pay 2.82

Worked fine when paying for three separate purchases earlier today.
[Magisk] inigoml:
Thank you, mate. You saved my day! :good:

I don't use any other module but MagiskHide. So, this workaround has enabled again my Google Pay without loosing anything.
[Magisk] habylab:
Is safety net working for those that are having issues?

I haven't had these issues aside from the last day or so, so I'm not sure why downgrading to a November update of Google Play Services fixes this? I've had many updates since November. Surely something else must be at play here.
[Magisk] joeyddr:
safety net passes fine.
[Magisk] Bradco:
Hello, I think I'm in the right place :)

google pay does not work he tells me my phone is rooter or has a modified rom. it's a U pro roote with a modified stock rom. I have magisk manager 7 magisk 18.1 the phone is certified on google play and I pass the safetynet and I check with magisk hide google pay / mixplorer and another app that needs the root. I do not know where the problem may come from.

I do not think the problem comes from the Rom but I'm not sure.

issue is it
[Magisk] bggold:
Thanks you Thank you Thank you. Did this and it worked.
[Magisk] Cowbell_Guy:
What exactly is core only mode?
[Magisk] xocomaox:
It is toggled in Magisk settings and when it's enabled you cannot load modules. Kind of sucks if you use modules, but the downgrade method here works so it should be a last resort.
[Magisk] Droiderat:
Galaxy S7 SM-G930F. Oreo ESAE (BTU) - Feb security patch

Google Pay 2.83

Google Play Services 15.0.90

Google Pay broke for me, as it did for others. Fixed by installing Magisk 18.2, Canary, along with Magisk Manager 7.0.0, Canary, and then hiding Google Pay and all of the Google Play Services components. I did not try to determine whether it would be successful if I hid less than all. I did not have to change any of my settings in Pay, or uninstall/reinstall it.
[Magisk] inigoml:
A limited magisk mode that disables all extensions but a pair of them. It keeps working MagiskHide and others, but most of them no. For me it's not a problem because I don't use other extensions and only need Google Pay (In fact I root my phone because I'm Xiaomi beta tester and by default SafetyNet does not work in beta versions, only in stable).
[Magisk] Nothing4You:
yesterday i was finally able to test in-store again and it worked fine. removing and adding cards works fine too.

google play services: 15.1.78

google pay: 2.83.235070858

magisk hidden:

google play services com.google.android.gms.unstable (com.google.android.gms)

google pay com.google.android.apps.walletnfcrel

there are no other gps items in magisk hide on my device.
[Magisk] gregwee:
Updating Google Play Services to 15.1.78 beta seems to solve the Gpay issue. I still need to actually try it at a shop later, but at least when I look at the Gpay app, it doesn't disable the card for contactless payment.

You can download the Google Play Services beta at: https://www.apkmirror.com/apk/googl...5-1-78-020400-235076232-android-apk-download/
[Magisk] habylab:
I'm on 16.0.81 beta and Google Pay works, but I'm having banking apps detect something and kicking me out. Safety net still passes.
[Magisk] jacek607:
Just checked: GPay is still working well
[Magisk] fronc:
Why does this app need root access?
[Magisk] jcmm11:
Because it's accessing restricted data on the /data/ partition. (All data on the /data/ partition is restricted)
[Magisk] lssong99:
Really strange... I had my Pixel 3XL factory resetted and update factory image (App patch) with wipe. However right after finishing the setup (no magisk or any other root solution installation, not restore from previous online backup, logged into my Google account.) I just tried the Google Pay to set up a new card... It failed with the same old "Your device is rooted..." Message...

The only thing my Pixel 3XL is not "stock" is the unlocked bootloader (I didn't lock it since plan to flash custom kernel later)...

This could be a big problem... This means even after wipe still being detected as root.... Anyone has similar experience!?
[Magisk] zencooler:
As I wrote you can just run the file explorer with root access and browse to the folder:

/data/data/com.android.providers.downloads and delete "cache" folder from this place.

Then create new file with name "cache".

That's all.

If you want to restore updates functionality you can just remove this "cache" file. System will recreate cache folder automatically during any update process.

Alternatively you can use commands in terminal window after su granted root permission.
[Magisk] jcmm11:
And if Pay sees an unlocked bootloader it assumes you have a rooted phone. So you have to hide the bootloader status, which means either a custom kernel or Magisk. A custom kernel may be enough to allow Google pay to run (delete it's cache and data).
[Magisk] andrewwdai:
why can't we just freeze the play store so gms won't update? mine is still 14.7.99 after i got rid of the play store.
[Magisk] zencooler:
It's ok unless you want to update regularly your other apps...
[Magisk] andrewwdai:
use apkpure or aptoid. getting rid of play store + downgrade gpay to 2.85 seem to get it working again. for how long, not sure.
[Magisk] Constrabus:
How did you disable updates?

Could we have a link to Play 10.0.89?

Thanks
[Magisk] xdaillum:
Firstly, thanks so much for posting this. I just wanted to share that this worked for me.

However, just wanted to point out that I only needed to follow the steps through to step #2. I did not update my Google Pay/Google Play Services or proceed beyond that point. It seems all I had to do was just update my Magisk. I'm not even sure if I needed to add all the Google Play Services to MagiskHide!

This also seems to have solved some other issues I've been having with other apps intermittently picking up that I have a rooted phone too.

Have been using this for about a week so far and used it about 5 times. Worked every single time :)
[Magisk] nnjimmy59:
I have a LG V30+. Rooted and unlocked running vs996 stock firmware . My GPay stopped working about a month ago. I updated to Magisk 19.1 stable and all is well. I've used GPay three times now with no problems. Just wanted to share.
[Magisk] Nekromantik:
anyone here on Dirty Unicorns have it working?

I was on Magisk 19.0 and not working but even after updating to 19.1 and adding Play Services and GPay to MagiskHide and deleting gsm folder I still cant add a card.
[Magisk] slinson:
19.1 stable working for me now
[Magisk] highdiver_2000:
On a real browser, Search for disable service.

Play Services 16.0.89 is available on apk mirror.
[Magisk] ChillerMarvin:
sadly not for me. just installed 19.1 magisk, deleted gpay and google play services cache and data and tried to add my paypal, but it throws the same error as everyone here gets
[Magisk] ssceddie:
Are you disabled the Wifi during you wanna add your pp Account
[Magisk] Pro4TLZZ:
Ok so I never did the folder thing, but moving to magisk canary 19 solved my Google pay thing
[Magisk] JarlPenguin:
When I added my device ID here: https://google.com/android/uncertified, it seems like GPay seems to work even with CTS returning false. Anyone experiencing the same thing?
[Magisk] borderite:
Magisk v19.1 has revived GPay on Nexus 6P

As many of you experienced, GPay stopped working on my Nexus 6P with Magisk a couple of months ago. I was lazy enough not to do anything special. I just waited for the updated version of Magisk. Now we have Magisk v19.1. I used GPay at a couple of stores successfully yesterday. Thank you!!

P.S. Interestingly, GMS Toolbox still says that the attestation state is "Fails".
[Magisk] mslezak:
My god, so simple. Root browser rename the folder and hide a few services and it works after a reboot. Wonderful! 19.1 working :) It actually worked even without hiding Google Pay

- Later note - I can add cards fine and they are ready for in store payment, but it just doesn't do anything when I use it at a terminal. No errors or anything. HCE Wallet. Just doesn't seem to do NFC at ALL!

Anyone have a fix?
[Magisk] Gaaat:
Updated to Magisk 19.1 stable, cleared GPay cache and data and Magisk Hide on all Google Play Services and GPay.

Successfully added card over mobile data (I don't think wifi would be different) and it is ready for in store payment.

I'm on Xz Premium with bootloader unlocked hiding kernel.
[Magisk] Paz9:
I haven't enrolled in the beta but today I found my gps updated to the latest beta version and pay stopped working

Tried deleting the gms folder and still didn't work

Manually downgraded to 16091 and deleted gms folder and began working again

Disabled Google Play store so my gps doesn't automatically update

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

What Google Play service version do you have?

After 16091 or new beta doesn't work, not even clearing the GMs folder, Google is getting smarter

Make sure your on 16.0.91, then try again it should work

But it may update automatically, you might need to disable play store or use a service modification and disable system update for gps

---------- Post added at 12:22 PM ---------- Previous post was at 12:07 PM ----------

Which service did you disable with disable service
[Magisk] Superschmiddi:
[MENTION=3433052]virtyx[/MENTION]

Look at the attached screenshots from my post a few later the one you quoted ?

https://xdaforums.com/showpost.php?p=79450963&postcount=1170
[Magisk] Paz9:
Whopp missed that

Thanks!
[Magisk] Flipz77:
Why fiddle with updates and packages when you can just use the PropsConfig module? It just works
[Magisk] ssceddie:
And how to use this modul for this gpay Problem
[Magisk] Tr4sHCr4fT:
To confirm on my theory of bank-side device bans: I've reverted to stock and still can't add a particular card, while the rest is working. Deleting gms and data won't help also. It does not throw the 'altered or rooted' error - Zenfone2 stock kernel is not leaking bootloader state - but 'can't setup for contactless ... please contact bank'.
[Magisk] xxxvego:
I have a Revolut card added to GPay. Currently there is a promotion, using my link, the person registering for the first time will receive a free physical card. Link for those interested:https://revolut.com/r/adam1pyi.

In the case of GPay updates, I only disable contactless payments, stop GPay, change the name of the /data/data(...).gms folder to (...). Gms.bak, restart the phone and after reboot configure contactless payments. For a month each time this way with this card works for me.
[Magisk] warrencoakley:
Can you explain how to do it please?