yashsingh1/xdaforums huggingface dataset:
[Magisk] Prof. Yaffle:
My 6T went through a little phase of not working several months ago but something updated and it's worked ever since. I'm not sure if it was a Magisk update that fixed it or something else but all I have hidden are Google Pay, PayPal and the default part of Google Play Services (com.google.android.gms.unstable). I don't think PayPal has anything to do with it but it was suggested at the time as a potential issue so I've left it hidden.
[Magisk] Optiongeek:
Thank you kind stranger. I have followed these helpful instructions successfully.

However, GPay still seems to be complaining about "root" when I try to add a new card. I've enabled both Google Play & Google Pay in Magisk Hide. Any other tasks I'm missing?
[Magisk] jcmm11:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Brava27:
Whoever fixed this and made it work again, you guys are absolutely Legends. Thanks so much

Sent from my Blackberry Bold
[Magisk] zencooler:
Here is the working solution: https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

Please read last few pages. There is a modified solution for OP post.
[Magisk] Brava27:
I meant to say it works! I'm very excited about this lol

Sent from my Blackberry Bold
[Magisk] Windroid-user:
Did you use he magisk module?

I want that blackberry bold... good times
[Magisk] vonDubenshire:
I am successfully using this every time. It works great. If you aren't having it work on anything that's remotely standard then just accept it's probably a little step missed somewhere.

No harm in going over the basics.

It also works fine on Q, but you have to change fingerprint to Pie.
[Magisk] AndroidPr0:
I'm on a custom rom on the pixel 3 xl. I have magisk, magisk hide and repackage on, magisk hide enabled for play services and Google pay, and magisk hide props config module installed.

Is there any easy way to get gpay to work without modifying SQL files and such?

Thanks.

---------- Post added at 01:08 AM ---------- Previous post was at 01:08 AM ----------

I'm on a custom rom on the pixel 3 xl. I have magisk, magisk hide and repackage on, magisk hide enabled for play services and Google pay, and magisk hide props config module installed.

Is there any easy way to get gpay to work without modifying SQL files and such?

Thanks.
[Magisk] vonDubenshire:
No. But if you read this, there is a module that will do it all FOR you so you don't have to.

Is that acceptable? Easiest way.
[Magisk] srqrob:
Sorry, but did you intend to include a link or is this a reference back to previous posts?
[Magisk] peet47:
this one ?

https://github.com/stylemessiah/GPay-SQLite-Fix
[Magisk] srqrob:
All of my phones have been rooted for years. Present P2XL latest August, 2019 security update, stock rom and kernel. Thinking about going without root on latest Android. If I unroot and uninstall Magisk 19.3 and Magisk Manager and delete installers but leave bootloader unlocked, reinstall the latest factory image without the -w, will Google Pay likely function OK? I've heard horror stories about relocking bootloader on P2XL.
[Magisk] jcmm11:
No, the unlocked bootloader will keep it from running. A custom kernel may solve that issue though.

As far as relocking goes, as long as you're COMPLETELY stock you should be able to relock with no problem. I think (would have to check) that, same as unlocking, it'll wipe /data - but I may be wrong about that part.

The horror stories arise if you try to lock a non-stock phone.
[Magisk] zencooler:
I don't know Pixel phones but from my point of view if you leave bootloader unlocked it will not solve the GPay issue as it checks all security levels and will still recognize security issue.
[Magisk] Windroid-user:
If your bootloader is unlocked just flash a kernel which hides your bootloader status like Sultan Kernel and hide magisk manager first if it's a fresh magisk install, then use magisk hide to hide gms and Google pay + any other apps that try to detect root e.g banking apps.

After that flash the module shown in the screenshot plus any other modules you want.

Reboot your phone and flash this module: https://github.com/stylemessiah/GPay-SQLite-Fix

Add your cards and reboot (if you don't know how to navigate to the download in github follow the screenshots)

I can only confirm that this works on a Pixel 2 XL running Pie August security patch

I really recommend a custom kernel like Sultan instead of a stock kernel which is stock but only hides the bootloader status because this has greatly improved my Pixel 2 XL in terms of performance, can't comment on battery life because it is not my phone but I'm sure that it's the same if not better.

Make sure you follow the instructions when flashing kernel because if you want to keep twrp you have to flash it again however this may vary from kernel to kernel. Also twrp does not trip safetynet and Gpay plus banking apps work fine with this setup.

Any questions just quote/mention/PM me.
[Magisk] Windroid-user:
Here are the screenshots in order of guide
[Magisk] Pekempy:
What kernel would you suggest for Q beta?
[Magisk] Windroid-user:
Sorry man I'm only a student this is my father's phone which I definitely cannot experiment with. I unlocked the bootloader purely to flash that kernel due to ram management issues it was having. It seemed to be the most stable, simple flash and forget kernel to use with noticeable improvements.

Before even unlocking the bootloader I had to upgrade to Pie because it was still on Oreo (not that you have to update/upgrade first).

If you really want to upgrade to Q I recommend waiting for the stable release or asking other users if you really really want to.
[Magisk] LiiQuoR:
Thx man ;) worked ! I don't understand why this module is not on the first page of the thread... help a lot when the database doesn't want to be changed !
[Magisk] Windroid-user:
Okay so basically it took me like 5 mins to figure out but on the first post it directs you to what I assume is the user who originally created this fix. However, it requires you to manually edit the database rather than having the modules do the work for you.
[Magisk] LLStarks:
Nothing works on Q anymore with Play Services 19.0.56. Not even the device fingerprint swap.
[Magisk] elreydenj:
Just used pay with play services 19.0.56 10 minutes ago. Rooted and fingerprint module active as they always have been.
[Magisk] ansh1996:
myki not working in google pay

I am using Google pixel 2 XL (taimen) with BlissROM official. I used the GPay SQLite fix and thankfully all the cards are working in my device now.

However, if i try to set up a myki ticket (NFC ticket used for public transport in Melbourne, Australia), i cannot load money onto the ticket as the app cant verify my card's CVV. I think the problem is related to the problem that we have with the card set up but maybe just situated in a different place in the code. If someone more experienced with this can look into it I'll be happy to co-ordinate. If there's already a solution available I'd really appreciate if someone can point me to it. Thank You. :)
[Magisk] JaylanPHNX:
Using the SQL module worked for me (Pixel 2xl). Thank you very much to its maker.
[Magisk] Windroid-user:
Device fingerprint swap? Sounds cool gonna find out what it is now oh no wait I remember now isn't it when another finger unlocks the phone it will show a different setup and everything like a different phone? What phone were you using that on?

Also another feature I think google or someone should implement is how much access a user (or fingerprint) has, for example you don't mind another user unlocking your phone and using it but you don't want them to be accessing your banking apps or something else like gallery or whatever. Kinda like device fingerprint swap now that I think about it but if it was implemented it would be much faster, as it doesn't have to change your screen which takes a few seconds at least on a phone I saw on not sure which.

Like permissions basically. Imagine google sees this and implements it in android 10 O_o I'm gonna be rich (not).
[Magisk] Audioboxer:
Thanks mate that module worked for me.

Any idea if it's systemless though? Hope it hasn't broke my OTAs lol.
[Magisk] LLStarks:
Device fingerprint has nothing to do with fingerprint unlock. Device fingerprint is the build string. Prior versions of Play Services were happy to accept a Pie fingerprint on a Q phone. You needed a Pie fingerprint to use Pay.
[Magisk] Windroid-user:
TWRP doesn't break OTA's right? I believe OTA will work but you have to reflash magisk and possibly the modules which may mean going the whole guide... Maybe.
[Magisk] jcmm11:
TWRP installed on phone does break OTA. You need stock recovery (among other things).
[Magisk] Audioboxer:
I'm not using TWRP :) Recovery is standard.

Some root apps or in the case of magisk, root modules, mount the system folder as RW (read/write). This breaks OTA capabilities as an OTA will error out as the system parition has been tampered with.

Either way I'll find out when the next security patch drops lol.
[Magisk] habylab:
I've had that for ages, all fine here.
[Magisk] Brava27:
Oreo or pie? Works fine for me on pie but I prefer oreo for now. Note 9 here.

Sent from my Blackberry Bold
[Magisk] sisqoboy:
Jumping between this two. Now it is working again with the rool back.

Also blocked data access. Will see…
[Magisk] Commando_Dhruva:
Those still facing issue. Disable phone and sms permission for Play services.
[Magisk] Artnig:
Unlocked and Rooted 6T, stock 9.11 OOS

Stock recovery, no TWRP.

Magisk 18.0

Google Play services 15.0.90

GPay 2.80

Not a single problem here, confirmed as I just paid for something moments ago. Wasn't even aware of this issue until seeing people saying GPay stopped working on my device in the subforum, so maybe it only happens to those with custom recoveries? Just my thoughts on this.
[Magisk] sash11:
Custom recovery has nothing to do with it. My PH-1 has stock recovery on it. I started to have issues non the less. Fixed with hiding two apps in Magisk.
[Magisk] jasonbiggs:
Just did that and..."updating play services libraries"... Back to 15.0.9... plus Google pay will not work unless those permissions are turned on [emoji19]
[Magisk] HamsterHam:
I can't get my card to add at all running play services 15.0.90. I'm using latest canary build as well.

Think anyone that is struggling will have to wait for magisk to be updated to solve it.
[Magisk] swour:
The mystery continues. From two devices identical in all parts from software versions to configuration except for a few non relevant apps, one is able to use Google Pay - the other isn't.

I'm not convinced that out of all the workarounds mentioned there actually has been one that didn't cause it to start working again out of luck.

On the device where I was previously able to re-add a card, the setup process now fails every time. The previous method to make it through the process doesn't work anymore: Delete data and cache for the Store and Pay app, cache of the Play services app.

Another odd thing I have noticed, once I add either the Store or Google services to the hide list, Safetynet checks will fail consistently until removed again from Magisk hide and another round of deleting cache and data has been performed.

Aside from the troubles with the Google Pay app, the device(s) pass Safetynet and show certified.

Can anyone with certainty confirm that the latest 18.2 builds of Magisk fix this?
[Magisk] Commando_Dhruva:
Just give the permission once and it will work
[Magisk] HamsterHam:
[MENTION=4453960]swour[/MENTION] that's what I think as well.
[Magisk] Nekromantik:
nothing works for me either

not tried to downgrade play services though.

Magisk canary reports CTS check as passed and play store shows verified but cant add my card
[Magisk] swour:
If that's the case, 18.2 not fixing this, and all reports from users regarding this are ignored, what are the chances of finding a solution?
[Magisk] HamsterHam:
Let's see what [MENTION=4470081]topjohnwu[/MENTION] comes up with. He'll hopefully be able to get it to work again.
[Magisk] cbarai:
I don't have any issues adding a card, it is only when I try to make a payment that it says not allowed.

I'm on play services 16.0.81 updated 25 the Feb but the issue only occurred this afternoon. I made one payment via g pay then half an hour later next payment showed the error message and has done so since then.
[Magisk] yung40oz84:
So I just wanted to let the thread now that I used the method from post 5 using the canary build, latest play services, and g pay. Added card successfully. I then had system reboots from quickswitch and canary build not playing nice together so I then went back into recovery, ran magisk uninstaller, installed stable magisk 18.1. I am now on 18.1, play services 15.0.90 and latest Google pay and I can successfully add more cards which I verified, and I have made several payments since with 2 different cards.

---------- Post added at 12:58 AM ---------- Previous post was at 12:56 AM ----------

Your in beta play services, maybe go to stable. Try to follow post 5, it worked for me. But I would go to 15.0.90 stable play services for starters. I am on that, latest g pay, and magisk 18.1 and made successful payments today.
[Magisk] sisqoboy:
Every day my play services go back to v 15.0.90

I need to block the network for it.

So so so so annoying!
[Magisk] Sojourner353:
Mines updated to v15.0.90 and everything still works
[Magisk] Windroid-user:
I think if you guys have the canary build (not sure what that means) or magisk 18.1 and you followed [MENTION=9506129]JarlPenguin[/MENTION] 's tutorial and it still doesn't work then I think you should downgrade to magisk 18 since google pay has been working fine for me after following his awesome tutorial.

Also yes I'm running google play services V15.0.90 and my last payment was on Friday 8th of march which is 2 days ago. Running latest Google Pay version 2.83.235070858
[Magisk] sisqoboy:
I can live with play services v 14.xx if it hadn't updated itself again and again.

Mine definitely blocked when got play services updated to v.15
[Magisk] Windroid-user:
Oh yeah, I was thinking of Cyanogenmod OTA's where it replaces twrp after every single update maybe even reboot lol... so annoying and pointless, I feel old now haha
[Magisk] ultimatepichu:
I've read through quite a lot of posts here. So let me confirm this real quick: Google Pay is broken on Q beta 6, correct?

I've done manual changing those values via SQL, I've tried the magisk modules, but it still says my phone is altered.
[Magisk] buffal0b1ll:
Use MagiskHideProps module to pick the pie system fingerprint and reboot. Sqlite edit + pie fingerprint gets Pay to work on Q.
[Magisk] ultimatepichu:
I installed the module, it's still getting the same error.
[Magisk] buffal0b1ll:
Did you clear Pay app data, or uninstall and reinstall it? Is your SQL lite editing attest values to 0 in dg.db and chmod 440 done correctly?
[Magisk] ultimatepichu:
yea. tried clearing the app data, and when it didn't work, I reinstalled. Reapplied those modules.

Then manually checked dg.db and chmod 440 it after.

I seldom use gPay so I guess it's fine until next week.
[Magisk] buffal0b1ll:
You did hide Pay and Play Services in MM too?
[Magisk] ultimatepichu:
Well yeah I did.
[Magisk] pekmez_:
Same here.... i even accepted bank terms, then there is loading wheel saying "contacting your bank", and than it fails for shoping saying "Cant pay in shops on this phone This may be because it is rooted or altered in some other way."

i have hidden magisk manager, hidden google pay, hidden google play services, modules installed on magisk are: "magiskhide props config" and "sqlite for arm aarch64 devices".
[Magisk] Windroid-user:
Unfortunately you missed one...

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

My guide is on page 177 in case you have to start fresh with the modules, also wipe Google Pay data just in case but not really necessary

So go to that link, flash the module, set up your cards and reboot.

Your unlocked bootloader is hidden and you are on Pie right?
[Magisk] pekmez_:
It works mate, thank you very much
[Magisk] PriMieon:
I've got a question:

I installed Android 10 on my pixel coming from a custom rom.

I installed magisk by batching my boot image, hid all Google apps, then downloaded automate and started the gpay fix thing, installed the sqlite fix module through magisk, deleted all play store and play service data, then tried adding a card on my gpay and everything works.

Magisk passes and the PlayStore says my device is certified.

But Netflix won't show up on the play store

So why is it that Google's saftynet, Google pay and the PlayStore can't detect my root but the the not even installed Netflix can?

Netflix can't run without being installed. So it must be the PlayStore seeing my root. But why does it then say I'm certified?

Why won't Google use this security measures to protect gpay?

Does anyone know how I get Netflix to show up again?

---------- Post added at 06:41 AM ---------- Previous post was at 06:41 AM ----------

I've got a question:

I installed Android 10 on my pixel coming from a custom rom.

I installed magisk by batching my boot image, hid all Google apps, then downloaded automate and started the gpay fix thing, installed the sqlite fix module through magisk, deleted all play store and play service data, then tried adding a card on my gpay and everything works.

Magisk passes and the PlayStore says my device is certified.

But Netflix won't show up on the play store

So why is it that Google's saftynet, Google pay and the PlayStore can't detect my root but the the not even installed Netflix can?

Netflix can't run without being installed. So it must be the PlayStore seeing my root. But why does it then say I'm certified?

Why won't Google use this security measures to protect gpay?

Does anyone know how I get Netflix to show up again?
[Magisk] sliding_billy:
Netflix hasn't shown up on a BL unlocked Pixel 3 in months. It doesn't matter if you are certified, unless you return to stock and relock your BL, it won't show or do updates if it is already on there. The latest version on APK Mirror is working fine before and after update to 10. https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
[Magisk] LLStarks:
Still no Pay solution for 10 plus the latest GPlay?
[Magisk] sliding_billy:
The same SQL attestation fix https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950 that was working in Pie continues to work in 10 from all accounts I have seen (including my Pixel 3 updated to 10 and continuing to function fine while having all Google software up to date including GPay).
[Magisk] uzzz2004:
I can't run the process from step 7 onwards (with terminal emulator, I can't use it) you can help me out, but thanks

7) open the terminal emulator.

8) get root access (su)

9) cd /data/data/com.google.android.gms/databases

10) type: chmod 440 dg.db

This makes dg.db read only (for owner and group, and no access for world.)
[Magisk] daviddgz:
Do you think that will work on a s9 with soldier rom on pie? It stopped working a few months ago and I'm looking at fixing it now.

Thanks
[Magisk] sliding_billy:
Not sure what you mean by "I can't use it." I use Terminal Emulator for Android - Jack Palevich with no issues on either 9 or 10. In a pinch though (and I often do it when the terminal entries are too long for the tiny keys on a phone), you can use an ADB root shell in commander (or PowerShell) on your PC. Root shell and terminal emulator are interchangeable and will work for steps 8-10.

---------- Post added at 03:03 AM ---------- Previous post was at 03:02 AM ----------

All you can do is try, but I honestly don't know.
[Magisk] buffal0b1ll:
No idea why TE won't work for you, but another way to change the dg.db to 440 is to use a root file manager like Solid Explorer or MiXplorer
[Magisk] Devo7v:
It definitely works. I was using that exact setup until he abandoned the ROM. I'm now on Ambasadii with the GPay fix and everything is working as expected. If you've got the time I would switch over to Ambasadii, it's very similar to Soldier and it's actively maintained.
[Magisk] uzzz2004:
ok thanks, done with this system it works, I use samsung note 9
[Magisk] Bardok84:
Hi,

I rooted my Xperia 10, Android 9.0 , the bootloader is unlocked and google pay first stopped working first because the root status. I hid Root with xposed and rootCloack... and then Google Pay stopped working but this time because the bootloader is unlocked....

What could I do??? if I go to the first page on this thread, there is two links to giving solutions but in my case, which one is the most recomended???? What am I wrong??

Thank you very very much
[Magisk] sash11:
Go with the first link. Second link only automates part of the solution from the first one.
[Magisk] frozst:
Thanks for the suggestion, is it stable? I saw the post was closed and a lot of people reported not being stable.
[Magisk] Bardok84:
Ok, I will try it.

I have been checking the link looking for a "turorial" about what should I do, and I found on the last pages on that thread this:

Take a look at "ilarson007 " user, he quoted some steps to follow..., are thouse steps the recommended for me????

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/page52

My Xperia 10 with ANDROID 9.0 is rooted through Magisk, and unlocked bootloader. But google pay does not work because ir detects the unlocked bootloader....,

I hid root with xposed + RootCloak, but happens the same.

This situation drove me crazy..., lets see is there is any solution.

Many thanks for your invaluable help and attention.
[Magisk] dadenet:
Hi guys ,

I have a pixel 3xl , with rooting by magic mask , , hide gpay , bootloader unlocked , Android 10 ,.factory ROM , somebody have a solution to register the credit card with gpay ?

Inviato dal mio Pixel 3 XL utilizzando Tapatalk
[Magisk] sliding_billy:
OP method is working, or you can read all the posts from the end until you find the last one about the Magisk module that automates the process from the OP. https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950 Manually making the changes is easy enough, and it survives a flash-all (minus -w) so to me it isn't worth doing it any other way.
[Magisk] Bardok84:
Hi

Please, would you know if the steps could work on my Xperia 10 with Android 9.0, Rooted by Magisk , unlocked bootloader???

Or the process it is only exclusively for pixel devices??

Thank you very very much

Regards
[Magisk] ssceddie:
Xposed is much stranger that normaly root/magisk. Xposed will never work with gpay or similar apps at the same time.
[Magisk] Bardok84:
I have read about this...maybe there, is my problem. So What should I try on my Xperia 10??

-Unistall Xposed and rootcloak

-Hide Root with Magisk Hide (I am not sure which version is the best)

- Then try to follow the stepa of here??

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

Would it work having a xperia and being android 9.0?

Any advice or suggeation is a really treasure for me. Thank a lot for your help.

Regards
[Magisk] sliding_billy:
I agree with the previous post. No Xposed if you want to use GPay. Current version of Magisk (19.3) for Android 9 with the Magisk hide that is built in along with the steps in the "working" thread you posted and the various processes that need hidden according to that thread. It should be device agnostic, but I know there are some banks' cards that never pass regardless of methods.
[Magisk] sash11:
Dude, instead of asking if the steps will work or not, just follow them) They worked on two of my phones: Pixel 3a XL and PH-1. Just hide GPay, Google Play Services and Google Services Framework in Magisk Hide. I used SQLite editor as described in the OP to edit the DB file and Root Explorer to set set permissions on DB file to read only. You do not need to use Xposed or rootcloak at all.
[Magisk] dunderball:
Hi there, I ran into a strange issue where my NFC option completely went away, and in Google Pay it prompts me to turn on NFC. It's just gone from the phone until I rebooted. Anyone else run into this before? I'm on a Pixel 3a.