yashsingh1/xdaforums huggingface dataset:
[Magisk] Nothing4You:
pixel 3 xl, stock rom, february security patch level, using latest magisk canary.

play store services 15.0.90 installed, uninstalling updates won't lower the version, downgrade doesn't seem to be possible.
[Magisk] Eric214:
I didn't have to do anything but the steps to downgrade play services. I just went back into the Google play app and trapped in my credit cards and added the security code and it added them just fine. No need to remove existing cards or the pay app and start from scratch.
[Magisk] jcmm11:
Interesting. I can confirm that it won't allow you to uninstall updates. The following should work (I have NOT tested this).

MAKE SURE YOU HAVE A BACKUP OF THE DATA PARTITION BEFORE STARTING!

Download the app from apk mirror. Turn on airplane mode.

In a terminal emulator, as root, run the following.

rm -rf /data/app/com.google.android.gms* /data/data/com.google.android.gms /data/user_de/0/com.google.android.gms

Reboot the phone

Install the downloaded apk

Turn off background data etc

Turn off airplane mode

Profit!
[Magisk] littleantony:
Same issue, UK and rooted in aex
[Magisk] stefr07:
I have those dots but when i try to remove upgrade it say 'no' ?.. well i still have m'y crédit card and will wait for a magisk upgrade. Thks
[Magisk] Paxi648:
I used Titanium Backup to freeze the Play Services on my Pixel 3 Xl. While they were deactivated, I was able to uninstall updates and downgrade to the working version.
[Magisk] Nothing4You:
this worked for me aswell, after that i was able to add cards/paypal again.
[Magisk] bot_rosco:
Does anyone know how to get around the issue where you get spammed with play services needs to be updated to use play services after the downgrade.
[Magisk] evolucja:
For me it was enough to wipe Google Play Services data.
[Magisk] jasonbiggs:
So, I reset using factory image and didn't root. Pay will not add cards still. I thought it only checked for root? Does it check to see if bootloader is unlocked also?
[Magisk] sash11:
Should not matter. How did you reset? Did you wipe all user data and apps or just flashed stock images?
[Magisk] jasonbiggs:
Complete wipe with "-w"
[Magisk] jsaxon2:
Yes, it also checks for unlocked bootloader. You can maybe find a custom kernel for your device that masks the bootloader unlocked flag.
[Magisk] sash11:
Try clearing cache and storage for Google Services framework and Google Pay.
[Magisk] backslide:
Device: Unlocked Samsung Galaxy S7 (exynos)

OS: 7 (stock ROM with root)

Magisk version: 18.1

Magisk Manager: v7.0.0 (185)

Play Services: 15.0.90

Google Pay 2.83.235070858

After doing the steps in post #5, I've had no problem for a week now. Added a card fine last Saturday, didn't have a need to pay until Wednesday but paid just fine, twice on Friday and once just now.
[Magisk] penciluser:
Pixel 3 XL here stock ROM with custom kernel and this solution worked. Magisk 18.1
[Magisk] Nekromantik:
Post 5 works for me in adding card.

But do you need to leave play services and pay without background data access?
[Magisk] Windroid-user:
After finishing the tutorial mine are still without background data access. I'm pretty sure you need to keep them like that so that it doesn't automatically update in the background.

You mean play not pay right? Because google pay has got nothing to do with checking for Magisk from what I've gathered.

Are there are downsides you've noticed to keeping them restricted?
[Magisk] gregwee:
The most painless way I've gotten it to work is to update Google Play Services to 15.1.78 Beta.. I installed this about 4 days ago, and GPay has worked flawlessly so far. The version also doesn't update itself like the non-beta 14.7.99, which automatically updates itself after I've downgraded it twice.

You can download Google Play Services 15.1.78 beta at: https://www.apkmirror.com/apk/googl...5-1-78-020400-235076232-android-apk-download/

Phone Specs as follows:

OnePlus 6T, OOS9.0.7 rooted

Magisk v18.1, Magisk Manager v7.0.0(185)

Magisk hide: Google Seach, Google Pay, Google Play Store, Pokemon Go

Magisk Manager package hidden/repackaged
[Magisk] HamsterHam:
What play services did you install? 14.7.99?

Right finally got my card added using 14.7.99. I'll test at a terminal later.

Pixel 3 XL running DU and latest Canary Magisk.

Edit: 14.7.99 works perfectly. Just paid for something and it worked.
[Magisk] vergilbt:
Same question for me: all services are working fine without background access?
[Magisk] pOOBAH1973:
On my Axon 7 (A2017G), I've tested with Magisk 16.7 on 8.0.0. Oreo (A2017GV1.30B02) - According to Root Checker Safety net is OK, and root not detected.

Google Play Services are 15.0.90 (040400-231259764)

Google Pay app is 2.83.235079858

Googe Pay setup with Paypal fails. Do I need an older Googe Pay app maybe?
[Magisk] cosmos321:
No you need an older version of the google play services. Just download the device right version from this thread, (point 4), uninstall your version, install the v14.7.99 and everything is fine.
[Magisk] t0m2k:
guys, im going crazy 4 real. Ive flashed complete stock CSB9 on my s9+ Exy via Odin. Im not even able to setup GPAY because its telling me, im rooted. what the hell?
[Magisk] pOOBAH1973:
Unfortunately it fails at point 4 here. Error message is simply "App not installed". I can sideload other apps, so it's enabled in System settings.
[Magisk] cosmos321:
Have you done the instructions step-by-step? It worked perfectly in my case.

Maybe you have selected a wrong version?
[Magisk] pOOBAH1973:
Step 4 worked now. The device admins weren't properly removed so I couldn't downgrade Google Play Services.

I downgraded Google Play Services now and I'm on the correct version. Next step: Verification of Google Pay Mastercard via Phone [MENTION=3583752]paypal[/MENTION].:) Oh joy.
[Magisk] warrencoakley:
Remove the safety patch Module and install the Magisk Config Props and configure the fingerprint. This method works.
[Magisk] vickystarboy:
I have disabled saftey patcher and installed proos config.Can you guide me how to configure it i know little about all these.though i am still passing safteynet and play Store certification after flashing props config.do i need to configure or leave it as it is..
[Magisk] 73sydney:
Try watching this....from a few pages ago (pays to read the last 5 pages or so of a thread if youre having an issue...top tip)

https://www.youtube.com/watch?v=wKYC0r-m0Mo

Also Magisk Config Props has its own thread where you can ask any follow up questions:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] vickystarboy:
Sadly my model isn't listed.i am using a realme x.thank you for replying.
[Magisk] Droidge:
Can’t use GPay here even with the fix installed alongside the MagiskHide props module. Failing both SafetyNet checks, too. Got no other modules installed that tamper with anything SafetyNet related. I guess this is goodbye to apps that use SafetyNet for a long, long time, and that’s being optimistic. Got a Galaxy Note8 running custom OneUI firmware.
[Magisk] Didgeridoohan:
The module/modification doesn't have to be tampering with anything directly SafetyNet related to trigger both SN checks. Try disabling one module after another and see if you can get things working again (or just enable Core Only Mode and see if at least basic integrity starts passing).
[Magisk] Droidge:
Thank you so much for the prompt response! I uninstalled a bunch of modules I wasn’t using anymore, et voila, I started passing SafetyNet again. Cheers!
[Magisk] Didgeridoohan:
Just out of curiosity, do you happen to know which one it was?
[Magisk] 73sydney:
Just fyi, looks like the recent google hammer is making a comeback...

Also as [MENTION=4667597]Didgeridoohan[/MENTION] posted in his MagiskHide Props Config thread, [MENTION=7550078]pwndal[/MENTION] is keeping a list of modules that may fail or cause issues with SafetyNet here: https://xdaforums.com/showpost.php?p=82166469&postcount=39193
[Magisk] Droidge:
Pretty sure it was FDE.AI.
[Magisk] 73sydney:
Makes sense, its snakeoil for one thing
[Magisk] DiRKiNg:
Uninstalled FDE.AI help me to pass SafetyNet and CTSProfile again! :highfive:
[Magisk] wabmorgan:
This worked. Thanks.
[Magisk] brainwash123:
This might help someone:

I had edXposed with RiRu modules installed, on Pixel 3, Android 10. The safety checks were failing, so I installed "props" and followed the steps . The check was still failing, so I disabled the edXposed module (but not Riru core or anything else) and rebooted, re-ran the check within Magisk, then re-ran the check inside GPay, it passed successfully.

Afterwards I re-enabled the xposed module and rebooted the phone, GPay continued to work. I did not make any payments with it (actually, I never did) but went through all the menus and options..

Magisk Hide was enabled for everything Google.

I hope I will remember to edit my reply if it stops working.
[Magisk] X46X:
Hi, SafetyNet pass for me but gPay not. Software standard issue.. Anyone know some fix for that?
[Magisk] buffal0b1ll:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/post82119353
[Magisk] nespresso33:
Hello guys.

S9 with custom rom and rooted. Google Pay is working good without any tweaks.

Samsung Pay by the way, is not working. "device modified".

I dont know why my google pay is working, but I know a few months ago, it was not working.
[Magisk] chrisrevoltes:
Custom Rom based on vanilla, or on aosp?
[Magisk] tiga05:
Because you hided google pay first with magisk and then tried to do something with it. That's why you don't need any SQL fix.

Only an idea, but maybe you can not use Samsung pay because Knox is triggered now and Samsung pay is checking if Knox was triggered.
[Magisk] Sk1t:
I can pass safety net but on the Payment Methods Screen when I press add it just dims the display with a small grey bottom. Anyone else getting this?

https://imgur.com/a/scArTCH
[Magisk] RedWave31:
For those having problems with Paylib sans contact and Google Pay and the dreaded Error_security_trc, that might be because of Safetynet not being OK and bad modules.

- You have to fo FIRST TRULY PASS SAFETYNET. Remove modules, disable EdXposed... It's mandatory. I will not cover Safetynet fail with 0 magisk modules installed itself in this post.

- There are Magisk or EdXposed modules that "Fake pass" Safetynet in Magisk, but don't trully do.

- Even with a failed Widevine L1 degraded to L3, Root Explorer and so on, hundred of rom flashes and bad decisions, I still pass Safetynet without "hiding helper modules" like MagiskHide Props. You SHOULD NOT NEED those kind of modules (YMMV)

NEEDED:

- Gpay Fix Module v2.2+ (faster than SQLITE manual digging!)

- Of course, you have to hide from Google Play Store, Google Pay, Paylib, Google Play Services, potentially also Google Service Framework, Paypal, SecureElementApplication, and so on.

- If using EdXposed, enable APP MODE, Blacklist mode, and blacklist Google Service Framework, Google Play Services. I didn't need to blacklist Google Pay and Paylib sans contact in EdXposed, the hooks seem to matter less than Magisk & Safetynet.

- REMEMBER : the more you hide/blacklist apps, the slower your phone will be !! Selecting carefully is better.

- To FIRST PASS SAFETYNET. Remove modules, disable EdXposed... It's mandatory. I will not cover Safetynet in this post.

- Clear app data from Google Pay, Google Play Services, Google Framework (optional), Paylib sans contact

- A reboot just to be sure

- TWRP Cache & Dalvik wipe optional

Here is a quick list of Google Pay and Paylib sans contact compatible Magisk modules and EdXposed Modules (only mine, not a complete list)

Gpay Compatible MAGISK Modules :

- App Systemizer 17.3.1

- Disable screenshot & Camera sounds 1.4

- Global Optimized GPS File Replacer 6.0

- GPAY SQLITE FIX 2.2 >> Important to have

- Magisk Manager for Recovery 2019.4.4

- Riru Core 21.2

- Riru Edxposed 0.5.0.0 Sandhook/Yahfa

- Riru Enhanced mode for Storage Isolation 22.5

- Universal GMS Doze 1.7.6-Q

- Viper4Android FX 2.7.1.6

Compatible EDXPOSED Modules

- Adblocker Reborn 1.8.2

- CustoMIUIzer 2.2.1

- Instagram Adkiller 1.2

- XprivacyLua 1.27

>> Needs more investigating after this line >>

POSSIBLE BAD MODULES for Magisk:

- Advanced Charging Controller 2020.3.1-r3-dev

- HiddenSettings 0.0.4

- NFC Screen Off 0.2.1

- ZipSigner 3.0

As you can see, I have a lot of modules on my MI9 (MIUI 12 on Xiaomi.eu 20.5.14 ROM)

POSSIBLE BAD MODULES for EdXposed:

- EdXposed Manager 4.5.7

- HiddenCore Module 1.7 (this one will show Safetynet passed in Magisk, but it doesn't in reality)

Google Pay is working on compatible banks, Paylib sans contact as well.
[Magisk] jhedfors:
[MENTION=4667597]Didgeridoohan[/MENTION], et al... :)

Not sure if anything can be done. This is not so much a problem with Google Pay and Magisk, as they are working great for me....

My issue is whenever I decide to reset my device, Google Pay makes me re-authorize all my cards in my wallet. This is not such a big deal with my Visa cards, but my main card is a MasterCard debit, which forces me to call my bank. My other cards are Visa's and they allow you to simply to use a 2-factor authentication, but MasterCard does not allow this.

Are there are specific files that I can backup and restore, or any way to prevent Google Pay from requiring reauthorization of my cards?

Edit: It turns out that I was misinformed by my bank regarding MasterCard debit , as I was able to add a different MasterCard debit, and got 2 factor authentication just fine... So it DOES look like my banks issue...:(
[Magisk] Michael1200:
Same issue since today. Very weird. Anyone know a fix?
[Magisk] Michael1200:
Update: Fixed it by reverting Google Play Services to 20.18.16
[Magisk] BostonDan:
I don't believe so. When you reset your device, I believe the seed for the encryption changes forcing renewal of cards based on your new security key. I may be wrong but this is my understanding.

Cheers,

B.D.
[Magisk] Sk1t:
Glad it's fixed for you :)

I ended up just doing a fresh install.
[Magisk] jhedfors:
Thanks. Are you referring to encryption specific to the app? My device is currently not encrypted.

I decided to make TWRP backup with all apps removed except Google Pay, so I can use that as a base when I "reset" my device next time.
[Magisk] sisqoboy:
Hi guys,

Few weeks ago I have an issue.

Once I make a payment next time it says the cardvis not registered for the gpay. I reregister it and works for one transaction and starts the whole story again.

SafetyNe check is fine.

Anyone any idea why I need to register the card again and again ?
[Magisk] lucfig:
Hi guys.

Do you had battery drain after cleaning Google play services data?

---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------

Hi guys.

Do you had battery drain after cleaning Google play services data?
[Magisk] Hyflex:
Hi Guys,

I have a Pixel 2 XL and I am trying to get Magisk hidden so I can use the likes of Google Pay.

Before I install "Magisk Hide Props Config" if I open Magisk Manager and check SafetyNet both of them ctsProfile and basicIntegrity are true, yet after installing MagiskHide Props Config the ctsProfile turns false...

I tried:

- Enabled a 2 XL fingerprint by swapping my original QQ3A.200605.001/6392402:user/release-keys to QP1A.191105.004/5908170:user/release-keys

- Enabled Vendor Fingerprint (Treble GSI ROM)

I never tried any of the advanced props changes because I don't know what's what...
[Magisk] Didgeridoohan:
That is very curious and would need some further digging to figure out. If you could post the module logs in the module thread I would be very grateful.

But, if you're passing SafetyNet already you have no use for MagiskHide Props Config (unless you want to use it for editing other prop values)... The "Edit device fingerprint" feature is for passing CTS on devices that aren't certified, nothing more.
[Magisk] Hyflex:
[MENTION=4667597]Didgeridoohan[/MENTION] The reason I installed this module was because Google pay was saying that I was rooted and wasn't letting me use it...

For reference I'm on:

Latest Android 10 Stock ROM with TWRP, Magisk and Sultans Kernel.

As for the logs, how exactly do you want them? Reset this module to defaults and then gather logs?
[Magisk] lucfig:
In my experience, from the moment safety net fails, the only way to pass again is by cleaning Google play services data.

Here are the steps I keep using for using Google pay (have to do every time I flash a kernel):

-Magisk installed

-Google Pay fix module (no other modules, such as magisk hide props)

-Hide Google play services, Google pay, bank app and google structure framework, not sure if this is the correct name. I've seen people pass just by hiding GPS, but I could not.

-Clean Google play services data

-Set up my card in Google pay

That's it.

Enviado de meu HD1903 usando o Tapatalk
[Magisk] Hyflex:
Where did you get the google pay fix module from? I've found a few but I am not sure what's the correct one:

https://xdaforums.com/apps/magisk/module-tez-hider-t3796567

https://github.com/stylemessiah/GPay-SQLite-Fix

Also, I'm not sure what you mean by "Google Structure Framework"
[Magisk] pndwal:
Use the latter, by [MENTION=9317193]73sydney[/MENTION], as cited in OP. (GitHub link doesn't specify the post, only thread).

It's a long post. Please read it carefully. :) PW
[Magisk] Hyflex:
Thanks guys! It appeared to work... I just need to test gpay in a shop!
[Magisk] pndwal:
Working?
[Magisk] Hyflex:
I've not been to the shops yet unfortunately, I would guess it would work because it's fixed my issues with a few other apps including my banking app where I don't get a warning anymore and I can use fingerprint login for the app.
[Magisk] davwheat:
I'm having a very odd issue.

With the GPay Fix installed and PropsHide disabled, GPay refuses to enable.

I'm getting a message saying "Please contact your card issuer for more info". I know it's not them as I've contacted them and they've told me nothing is stopping it being enabled.

I read some other posts about this issue but they were from last year, and their suggested fixes don't work.

ctsProfile and basicIntegrity both pass. Any ideas?
[Magisk] lucfig:
I got it working without any additional Magisk module. So I suggest you to remove both GPay fix and Props Hide. Clean Google play services data. Hide both Google play services and your bank app and try again.

Enviado de meu HD1903 usando o Tapatalk
[Magisk] davwheat:
Well removing both of those resulted in the "this device has been rooted or altered" message (which I've never seen before, even before I installed those modules).

I already had GPS, GPay, and GSF hidden. Why do I need my bank app hidden? It only checks for MM and repackaging MM under a random name fixes any issues with it.

Clearing data of GPS, GPay and GSF and rebooting solved that, but left me exactly where I was, saying "Your card couldn't be added. Contact your card issuer".

This only surfaced when I installed LineageOS for my phone, not on my previous ROM (AOSiP). Noone else has any issues with it, though...
[Magisk] lucfig:
Yeah, I believe in custom ROMs you need the hide props module.

I could only register my card by hiding the bank app. I don't even have gpay hidden and only the unstable service is hidden in GPS.

Enviado de meu HD1903 usando o Tapatalk
[Magisk] warrencoakley:
I had to do an update to Vance which involved downloading Xposed , Riru etc. It seems by doing this Safety Net is failing. I uninstall everything I installed but it still fails.

Are you stating from your post to have Safety Net working again I have to clear Google Play Services data?
[Magisk] lucfig:
Exactly. Once it is detected, I'm not aware of any other way.

Enviado de meu HD1903 usando o Tapatalk
[Magisk] warrencoakley:
Yeo tried it and we are all good in the hood again.
[Magisk] reversegear:
clear data of google play services. it will work again
[Magisk] lucfig:
That's exactly what we were doing. Lol

Enviado de meu HD1903 usando o Tapatalk
[Magisk] boricua65:
I just purchased the LG V35 ThinQ LG-V350AWM and cross flashed with the NAO version (V350ULM) to get rid of the AT&T bloat. I, too, am getting the message "This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way", when I try to register my credit/debit cards. Will steps outlined in the first post work for my phone? I did not root.

TIA
[Magisk] veitograf:
I got gpay working on my pixel 4 with an older version of the gpay fix until I installed edxposed. now gpay tells me I am rooted and is not working anymore. Installing the latest gpay fix and clearing Google service data did not help.

Anyone else facing the problem with exposed?
[Magisk] perkoxcar:
I am on Mi Note 10 Lite, Magisk 20.4, xiaomi.eu rom.

Sqlite fix is installed.Magisk hide enabled.

I cannot pass cts profile but all other things pass.

When I enter Gpay no warning is shown and I can add cards with no problem.

What does this mean ? Can I use gpay in stores or not ?

Might to try it out today.
[Magisk] HSgod:
I think gpay need only basicIntegrity, tried one time and works without cts
[Magisk] kirk100:
This has happened to me too. Any ideas for a fix before I wipe my phone and start again?
[Magisk] lilbrat:
Try the lastest canary version for exposed...
[Magisk] porotikos:
Hi guys. Thank god i found this amazing thread. I hope you can help me.

i have a xiami mi note 10 pro. Global rom. Running magisk 20.4. Phone is rooted.

Magiskhide is enabled. I pass basic integrity, but fail cts.

card in google pay is added. But it states that it cant be used in stores because i have administrative rights. (guess gpay detects my root.)

is this some new problem? Anything i could donoe not? Thank you
[Magisk] pndwal:
Likely can fix by fixing CTS and "Device is Certified" status in playstore settings. (Likely need MagiskHide Props module, configured, also new workaround if hardware backed attestation is now tripping CTS on you device:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83028387 [check this thread for related safetynet developments and Magisk related solutions] - check attestation type using Canary Magisk manager if unsure), then load SQLite binaries Magisk module and G pay fix module by [MENTION=9317193]73sydney[/MENTION], as mentioned in OP here:

It's a long post. Please read it carefully. :)

Also, don't forget to clear playstore / Google Services / G Pay data or caches. PW
[Magisk] Fusseldieb:
I was reading through hundreds of posts on reddit, xda and other forums that people were having troubles with root + gpay.

My question now is: Is it really worth? Like... I want to root my S10e to use more advance stuff, but I also use G Pay and considering the huge amount of effort and it seemingly breaking all the time I really don't see why I should.

Can someone please prove me otherwise?

---------- Post added at 10:05 AM ---------- Previous post was at 10:04 AM ----------

I was reading through hundreds of posts on reddit, xda and other forums that people were having troubles with root + gpay.

My question now is: Is it really worth? Like... I want to root my S10e to use more advance stuff, but I also use G Pay and considering the huge amount of effort and it seemingly breaking all the time I really don't see why I should.

Can someone please prove me otherwise?
[Magisk] lilbrat:
With all do respect can't really prove it as far other devices go .. I have a OP 6T stock room and kernel but rooted lastest magisk and also have exposed installed running various mods and without any scripts from this thread or anywhere else and my g pay works just fine without any issues..
[Magisk] crisco654:
Hi, so, I have a Pixel 4XL, and I'm currently on Android 10 with the July security update. Using Magisk 20.4 with Magisk Manager 7.5.1. Before I go through the 100 of pages looking for a fix, I wanted to ask first whether there is even a fix for google pay, for what I'm currently running. Thanks!
[Magisk] pndwal:
Yes - relevant info above:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/post83072657 PW