yashsingh1/xdaforums huggingface dataset:
[Magisk] chris2ferz:
when core mode is enabled in 18.1, GPS is still not visible but it's the best you can do since it has better compatibility hiding root traces from GPS - so it works for some - unsure for how long just yet. Either way you need Canary to fully hide GPS from the GUI otherwise it's CLI (either term or adb) as others have mentioned - good luck
[Magisk] Flounderist:
I want to report this scenario:

Yesterday I clean flashed (ROM+pico gapps) my backup device, who doesn't even had GPay installed previously.

On the initial setup the device asked me to register a credit/debit card so I gave a try. Even without any root or magisk installed, the card setup failed with the rooting/tampering message.

It is clear it isn't a magisk issue, I assume that Play Services is looking at the bootloader status, regardless of any root.

Probably we should focus more on how GPS get the device bootloader status information.
[Magisk] Didgeridoohan:
Clarification: MagiskHide is no different if Core Only Mode activated or not. The only difference is that MagiskHide doesn't have to unmount any modules in Core Only Mode.
[Magisk] joeyddr:
i'm on the latest canary and did what you posted here and i was able to add card and paypal.... also on the latest services beta
[Magisk] fw85:
Just the main folder com.google.android.gms I believe. Make backups.

Type that command in a terminal. (using your preferred terminal emulator app)
[Magisk] pokko:
Just

su magiskhide --add com.google.android.gms

??
[Magisk] Itachisasuke:
This makes me wonder if the new Google Play Services is using the mount table, fstab (not sure if this exists in Android), or comparing prop files to flag the device as unsecure.

If just enabling Magisk Core works without wiping the data repository for Google Play Services then there must be a solution set that allows us to hide the Service from querying the mount or prop locations.

Obviously this is purely speculation and would need to be examined for technical accuracy and feasibility.
[Magisk] ChronoReverse:
Yeah. The old method GPS used to detect unlocked bootloader was already loaded on my non-rooted Pixel 2's kernel but the new GPS seems to be able to detect unlocked bootloader anyway.
[Magisk] Flounderist:
It could be possible to create a flashable zip to prevent it?
[Magisk] Phoenix Wright:
It does all of that, and magisk hide already deals with all that. The only issue is that magisk hide is only active on the "unstable" process within play services (which handles safetynet checks), google pay used to only rely on safetynet before but now it (also) relies on checks made by the main play services process, that magisk hide is not enabled on by default.
[Magisk] sb1893:
Update: 3/22 - The above process is still working for me. I am still able to add cards to Google Pay and AM able to make in-store payments as well. I am still on Google Play Services 15.0.90 and Magisk 18.1 (stable)....I know others have reported different/varied results....but wanted to post my experience over the past 10 days as well. Thanks!
[Magisk] SimplyCity:
Hi there. Small info from my side.

Phone: LG V30

Rom: stock, V21w-EUR-XX

Latest TWRP, stock kernel

Magisk: latest 18.2 (18121)

Just an hour ago I tried to add my card to gpay while on 18.1 stable, but unsuccessful. Flashed magisk uninstaller, cleared cashes, flashed 18.2. Booted without issues. Added to magisk hide list: android service library, Google services framework, Google pay, play store and com.google.andoid.gms from Google play services (com.google.andoid.gms.unstable was already checked from the start). Rebooted to recovery and renamed com.google.andoid.gms folder. Rebooted to system without wipeing caches. And successfully added my card to gpay, confirmed by my bank.

It seems everything is working. Appreciate for the guide.

:)

Echoe[emoji769] team member / N8 Oreo
[Magisk] DanRyb:
Consider yourself lucky, I just performed the same exact steps and still get the root message in Google Pay when trying to add a card.
[Magisk] dumdidum123:
I followed all the steps, no problem when adding my paypal account to Google Pay. Even when I try to pay in a store it seems to work, since I get no error on my device, but the store cashing systems say "No Authorization" and the payment process is aborted. I tried it in different stores where I was able to pay in the last weeks.
[Magisk] DanRyb:
The same thing happened to me. Is there a fix for this? Small issue but a bit annoying.
[Magisk] warrencoakley:
Could find a work around. My phone started to become unresponsive and then bootlooped. Had to reinstall and flash everything. Nightmare.
[Magisk] zoman7663:
Just wanted to say thank you to all that have looked at, worked on and solved this problem. I'm on a OnePlus 6T stock 9.0.12 with XXX NoLimits and Renovate Ice installed. Simply dirty upgrade to Magisk Canary 18.2 and hiding the additional Google Play Services did the trick for me. No data wiping or anything just installed 18.2 right over 18.1 and back in business.... Thank you!
[Magisk] glenb77:
just checked in store and got some wierd error, but it said please use card. i've had the 'cannot be used in store' error in the past, never saw this error. i also did have the issuer verifying with me after i added because there were so many attempts. i am still able to add card normally in gpay. i'll try once more in store and check. personally i am going to wait until there is more clarity on this and can be assured it will work or not, one way or the other.
[Magisk] jrbmed08:
I tried to do this but I get an "unrecognized option" error for --add.
[Magisk] glenb77:
to clarify, i tried one more time and error in store is: 'card not accepted please use chip reader' no issue with card and works with chip reader. but this is discover who does crazy security stuff and i had a lot attempts when gpay was failing so maybe that is issue. i'll try with my alternate card tomorrow and see. i also contacted issuer to ask.
[Magisk] jcmm11:
What, exactly, did you enter? It should look like this

enter su, hit return. Now in root mode.

magiskhide --add com.google.android.gms
[Magisk] smartt699:
For me uninstalling 18.1 via recovery

Installing 18.2 via recovery

Boot hide all Google pay, services,play

Rename com.google.android.gms adding .Bak

Reboot

Voilà buying things with gpay all week
[Magisk] NeuesS5:
Please write a bad review in the Playstore.

Only when paying to show that it does not work is very bad.
[Magisk] c3k:
I was in core mode (18.1), now I launch this command and disabled the core mode, will it work?
[Magisk] caluz78:
8 days here with 14.7.99 (with update services disabled) and everything is working.. (last payment 1 hour ago)
[Magisk] Itachisasuke:
Bleh I was hoping that just by adding com.google.android.gms and the Google Services Framework to MagiskHide using adb shell and rebooting would work but it looks like the data folder still needs to be addressed which is what has been documented but I wanted to see if it was completely necessary based on the fact that just by enabling Magisk Core it functions without changing any data folders.

I'm wondering if we can pinpoint more specifically where the check is being kept so we don't need to nuke the folder in it's entirety or why just clicking Magisk Core works without any data edits.
[Magisk] yung40oz84:
This has been known forever. There's many articles on the change and pay not working with unlocked bootloader. This was bypassed in magisk, also kernel patch, but it's not working anymore apparently, so a new method is needed as Google is using a new method.
[Magisk] badflife:
Thanks.

I followed every step and i could successfully add my credit card.

And could also do a payment.
[Magisk] IM0001:
Well on a Pixel 2XL, latest Canary build and going through all the steps above. (Both Clearing Play Services Data, or renaming the gms folder in data.) work for a bit to add a card, then it breaks after a short bit later. Something is still flagging it after a period of time as I can add one of my cards, then when I go to add a 2nd it says "Something Went Wrong" endlessly.
[Magisk] Flounderist:
I know. I was pointing out the fact that I wasn't able to add any card even without any root or magisk installed.

Hiding and downgrading stuff is not an acceptable, on the long term, workaround.

GPS is overlooking on all the google related apps, I would never block it.
[Magisk] =dgim=:
I had error on installation in my OnePlus 3T and Magisk 18.2 (build from 17 or 18.03) via latest TWRP. I had to recover a lot, rom/boot partition etc.

Fortunatelly after flashed latest build of Magisk 18.2 (today's build) and reinstalled and hiding GPay/com.android.google gms service which is from that build default hidden - finally GPay is working again on my OP3T.

Eh...
[Magisk] c3k:
First pay works, second blocked, so manual hiding com.google.android.gms on 18.1 is useless.

I'll go back to core mode, best and simplest solution for me at the moment.
[Magisk] Itachisasuke:
I am also thinking of the scenario when we install an OTA or Factory Image Update that if the flags get set before Magisk is loaded again we will forever be clearing that data folder every month for us Pixel users.
[Magisk] mmf01:
This worked perfectly. Pixel 3 XL. Thank you!
[Magisk] dvhttn:
Just to say that I've an S7 running the Galaxy Project ROM (Oreo) with the 121 canary build og Magisk installed. I hide GP and gms.unstable from GPS, I'm NOT in core only mode and I haven't hidden Magisk Manager. But ..... GP has been working for over a week now. Am I just lucky?
[Magisk] c3k:
Seems there are two way to (continually) use GP at the moment:

- use canary and hide the right packages

- use stable in core mode
[Magisk] Big_T71:
Hmmm, or a third for me

- use canary and hide nothing, with MagiskHide Props Config module (lineage 14.1)
[Magisk] shivaagarwal1:
Everytime I rename the com.google.android.gms to .bak, it resets to its original name. Any suggestions?
[Magisk] royhanks3:
I'm a bit lost in the process myself, are you naming the entire folder that or just one specific file? When I search "gms" in root explorer I get a decent amount of file names with that extension and an entire folder. Also, once changed, Google pay no longer opens for me on my Mate 10.
[Magisk] shivaagarwal1:
Just the com.google.android.gms file in root/data/data folder
[Magisk] royhanks3:
So, I'm not just seeing "com.google.android.gms" file. Hopefully my screenshot helps figure out which file name to change
[Magisk] shivaagarwal1:
First one
[Magisk] Oggy512:
Works here with OP6, stock OOS 9.0.4 and Magisk 18.1 (normal mode, no core). I could add a Mastercard (N26) which is working, but I can't add my Revolut MC... after typing the CVV nothing happens. But at least N26 is working...
[Magisk] pakatsui:
I add my Revolut Visa card after this, and after "Your bank is verifying your card..." I get an error saying "Double-check your card details. Something's not right. Please double-check the details and try again." All the data is correct.
[Magisk] Superschmiddi:
If I do this I cant add paypal anymore, only cards.

I think I gonna reflash actual factory image to my Pixel 2 XL without Magisk. Really annoying :(
[Magisk] reppi:
Same here, no PayPal.
[Magisk] Superschmiddi:
Even if I undo everything and reinstall GPay theres no more PayPal......
[Magisk] twotimer:
To be able to add PayPal again after deleting the com.google.android.gms folder - you have to do it via the PayPal app itself (there's "Google Pay" somewhere in the settings)
[Magisk] mc.cerny:
working on pixel 3. thx

but how long?

Odesláno z mého Pixel 3 pomocí Tapatalk
[Magisk] badflife:
I could add Revolut Card and PayPal using this method.
[Magisk] Superschmiddi:
Theres another problem, I renamed the folder to ... .bak but it automatically renamed it correctly..
[Magisk] geniusit:
I can't find Google Services Framework....how can I add it? I have a S9+
[Magisk] Superschmiddi:
I reflashed the actual factory image for my Pixel 2 XL without installing Magisk, still dont have the PayPal option within GPay.

If I try to connect PayPal through the PayPal app I still get the "device is rooted" message although I didnt root it now, what is going on :(
[Magisk] adamjmacdonald:
Top right 3 dots menu in magisk hide... Check show system apps
[Magisk] prgopala:
Same thing happened with me for a card that was already existing and i was trying to setup contact less. I figured out that after entering the cvv there is no button to continue, so i tried to click on the address which brought up the continue button. Try it and let me know.
[Magisk] zertyx:
Did you mount System as R/W?
[Magisk] m4rcs90:
Additionally, I hid the PayPal App in Magisk and was abled to add my PayPal to GPay, which I wasn't before. Couldn't check in store payment, yet.
[Magisk] Superschmiddi:
I rooted my Google Pixel 2 XL again, did the steps [MENTION=7186058]fw85[/MENTION] described again and now its working.

I use Magisk Hide for:

com.google.android.gms

Google Services Framework

Google Pay

My Banking App+Security App

Renaming the com.google.android.gms folder in root\data\data isnt needed for me because its automatically renamed to its original name with every reboot.

Also I ticked in Magisk the option to repack Magisk with random package name.

Core only isnt necessary for me.

Hiding PayPal isnt needed for me otherwise it is detecting root again while connecting PayPal to GPay.
[Magisk] pokko:
[MENTION=6889326]Superschmiddi[/MENTION] You have to install paypal app
[Magisk] Umbardacil:
Method from post #5 worked for me like a charm[emoji106]
[Magisk] MC_Ohr:
For me the .bak was deleted after reboot and a new folder was added.

Gesendet von meinem HTC U11 life mit Tapatalk
[Magisk] mmf01:
For anyone looking, this is where to find “GMS”/“Google Play Services” Data Folder (This is on Pixel 3 XL - YMMV)

—>Don’t search for this, Browse. Using Root Explorer, attached is where to find the gms folder to rename or delete. Second attachment is the full path.

Posted step by step process for Pixel 3 XL (may work with others too) here:

—>https://xdaforums.com/showpost.php?p=79184685&postcount=1185
[Magisk] Itachisasuke:
Anyone know if we can just get away with just uninstalling Google Pay and deleting the

/data/data/com.google.android.gms/databases/android_pay.db

which seems to be storing the attestation check if that would be sufficient instead of nuking the entire folder. Obviously this would be after adding gms and gsf to MagiskHide.

Basing this off of [MENTION=2177334]mmf01[/MENTION] 's post above.

I'm assuming whatever the steps are, we will likely be doing them after each OTA or Factory Image Flash if Pay discovers root before Magisk is reinstalled.
[Magisk] mmf01:
Click in the box with your name/address, then click continue. It proceed to terms and conditions and you should be good to go.

---------- Post added at 03:14 PM ---------- Previous post was at 02:43 PM ----------

When I previously attempted to change 'fails_attestation' to 0, each time it would flip back to 1, so I'm thinking something else was triggering it. In fact, a search across all file content within 'com.google.android.gms' for either 'snet' or 'attest' returns a boatload of files referencing stored checks related to SafetyNet.

Perhaps it's worth a try deleting just android_pay.db, but I somewhat recall trying that first and then GPay simply wouldn't open until I deleted the GMS folder entirely and went through all the steps listed in my post here https://xdaforums.com/showpost.php?p=79184685&postcount=1185

And....yeah, I suspect it will be more work each update cycle to combat this check, however, deleting the GMS folder wasn't a big deal for me at least. It didn't wipe my Google Account (as I was expecting), nor did it create 'ghost' devices in Google Play/Music, or cause other issues typically associated with approaches like this in the past....YYMV, but the only ill-effect (if you want to call it that...lol) for me was being prompted to turn on "Backup" again. So.... so far, so good....
[Magisk] Itachisasuke:
Appreciate the response.

Yeah I was hesitant to delete or rename the folder knowing the data partition is going to run a check and rebuild it.

I was expecting some data artifacting or strange behavior with other Google Applications but if it only unchecks the Backup option that isn't too bad as long as it doesn't remove the current backup that's stored in Google Drive and it can easily be renabled and the backup works properly.

I agree we should probably start thinking of a longer term solution if any or get used to blowing that folder away every time we update.
[Magisk] mmf01:
Glad to help. For backup, I can confirm backup shows current without other instances being left, so I assume it's working without issue.

For next factory update solution - I believe Magisk stores it's settings in 'data', so I'm thinking as long as the 'data' partition is backed up via fastboot twrp prior to the factory flash (update), and we re-install Magisk post-update, then restore the 'data' partition only, thinking we should be good to go as 'data' is where the magic happens and should mirror everything that WAS working just fine prior to the update. Outside this GPay debacle, I've used this approach many times to avoid having to mess with the hoops of having to remove root, update, reapply, etc.... Backup Partitions. Factory Flash Image/Update. Re-Install Magisk. Restore Data. Done. This approach usually works for me, except in rare cases, which is sometimes during major Android updates (8 to 9, etc.).
[Magisk] Kielbek:
I've got problem with Magisk and GPay too. What I could say. Neither Stable or Canary is working for me... Core and normal mode. Also Systemless hosts are not working properly. I installed PokemonGo (because it was using safetynet in the past) and even if I'm passing safetynet it says that my OS is incompatible after 2 minutes of "playing" or so. It thought that it may help you guys with testing what's going on.
[Magisk] adamjmacdonald:
There's a lot of speculation in this thread, meanwhile these instructions are working fine for magisk 18.1 stable release for days now with daily gpay NFC transactions. HTC 10 stock rom with custom kernel.
[Magisk] xiphosurus:
Just wanted to leave a note that doing just the following worked for me. Not sure if every step is needed, but it's what I did. I suspect step 3 is crucial. My phone is OP6T on OOS beta 6.

1. Still on

Magisk 18.1 with MM 7.0.0

2. Enable replace Magisk Manger with random package name.

3. Turn on Magisk Core Only Mode

4. Under Magisk Hide, search for google as keyword and enable pretty much anything google related.

5. Reboot.

With these steps, I was able to set-up existing credit cards for in-store payment, and actually use it in store. Also, all my banking apps works, including SingPass for those from Singapore. I did not have to rename com.google.android.gms folder or use the canary build like some of you. However, it still does stop working every now and then. Then I would turn off and on Magisk Hide to get it working again. Good luck.
[Magisk] yung40oz84:
These steps are good, minus services framework and Pay. The key is Google play services, specifically, .gms and .gms.unstable. And, possibly only 1 of them. That's the only 2 things I have hidden, I renamed the folder to .Bak, and it's been working for 2 days with successful payments. Just waiting for it to fail eventually [emoji23] Now, I am on canary currently, but that doesn't matter. It's what is hidden that matters and the .gms is doing the check, whether your on canary or stable. I succeeded with these steps on stable 18.1 prior to going to canary.

---------- Post added at 12:24 AM ---------- Previous post was at 12:16 AM ----------

I did exactly as posted here with only those 2 things hidden, latest canary, latest stable play services, and I added card and PayPal, paid with card today. We'll see if it lasts until a random check is done, but so far so good. And, like u said I have nothing else hidden. Not Google pay, services framework, nothing. Thanks bud! Did. You officially open a issue on GitHub? I can verify there.
[Magisk] krs360:
Latest Canary changlog says its fixed (attached).

Cleared data as suggested, still can't add a card.
[Magisk] Michalec:
How did you cleared data? Use Titanium Backup. GMS has own "clearing", that's why u need to use alternative method.
[Magisk] dfxxx:
Where can i download the latest Canary?
[Magisk] Eclipse1991:
Hey guys ive come across this thread but I got a xiaomi mi 8 and just installed the 9.3.21 xiaomi.eu rom. Does someone have like a small guide how to get magisk on it for the first time ? I appreciate every help.

Gesendet von meinem MI 8 mit Tapatalk
[Magisk] JustinTrouble:
Good spot! I'd already installed that version, but missed the changelog.

It worked for me. I've just managed to add a card that I couldn't before.

I was able to clear data in Settings > Apps & notifications > See all apps > Google Play services > Storage > Clear Storage > Clear All Data.

You're in the wrong thread. Have a look through the other threads under this forum.
[Magisk] Eclipse1991:
No i think im right here because i want to get gpay working aswell but in order to do that I need magisk aswell [emoji846]

Gesendet von meinem MI 8 mit Tapatalk
[Magisk] PuffDaddy_d:
No, he's saying there's already a "how to install magisk" thread. Go to your phone's sub forum for device specific instructions.
[Magisk] Eclipse1991:
Okay got it, thanks guys.

Gesendet von meinem MI 8 mit Tapatalk
[Magisk] sebastix1x:
Using masigk 18.2 from a custom Update Channel seems to Work aswell.

https://github.com/ianmacd/MagiskBuilds

Channel: https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json

Edit: i am using a oneplus 6t
[Magisk] martyfender:
I think it is a bad idea to hide Chrome/System Webview, as the system depends on webview for so many things. Chrome's webview is used on Android versions newer than 6, I believe.

This is from the Magisk and MagiskHide Installation and Troubleshooting guide, by [MENTION=4667597]Didgeridoohan[/MENTION]:

I'm not even sure if it is advisable to hide everything else, Google, except for play services and pay, for that matter.

I hope to see others input on if this should be done, also.
[Magisk] benlm72:
Many thanks, that works for me ! At last adding a card, no payment tested for now.

I just notice that the su cmd have to be cut in two parts for me, as stated in one older post : first su, then magiskhide --add... Otherwise I get un unknown command about --add

I was able to rename com.google.android.gms with ES explorer. A new one is created after reboot.
[Magisk] Freshek:
I took a look at the source code of latest Google Services and to me it looks like they're testing new SafetyNet API. I'm not sure though. It was just a quick look.

Also the attestation flag in the DB seems to be some kind of cache for the Attestation result.

Nevermind, looks like some other API.
[Magisk] royhanks3:
I did the same thing here, and the error I'm getting now is "double check the card details" and it's saying this with every card I try. I'm on the latest magisk Canary. I can't figure out what's tripping it for me.
[Magisk] Freshek:
What's your Google Services version?
[Magisk] royhanks3:
14.7.99
[Magisk] dumdidum123:
Payment was possible today for me!

What I have: Magisk v18.1

What I did:

-Magisk Hide for: Google Pay, Google Play Store, Google Play Services-Framework, Paypal

-Magisk Hide via Terminal for Google Play Service (magiskhide --add com.google.android.gms)

-Magisk in Core Mode

-Delete Data for Google Play Services

-Reboot

-Adding PayPal to Google Pay via Google Pay App

-Done

Worked, I tried to pay and it worked just like before.
[Magisk] wabmorgan:
I have to admit i have not tried to purchase anything yet but I turned on core mode in 18.1 on my Pixel 2 XL and it will pass safety net.