yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
And because its a day ending in Y, it must mean an update....

Magisk Method Gpay SQLite Fix.....

Changelog:

SQLite binary for arm-v7:

16/11/2019

Due to me finally hitting an occasion where my hastily rejigged (from an earlier module) sqlite3 binary for arm-v7 didnt install the binary properly,

i pinched the install logic from the guys who make the aarch64 version as it was way more sound than my cobbled together module. Ultimately mine failed when the ROM didnt already have an xbin directoy...bit of an oops that one...only ran afoul of this for the first time about an hour ago flashing a new ROM to test....i blame me, ive been suckling at the teat of Microsoft for so long now bash has long since been my native tongue....

Not wanting to reinvent the wheel, and it being 4am here and me needing some zzz's soon, i took inspiration (stole the code) from the aarch64 sqlite3 module and have edited the install.sh on my github, and uploaded a new zip. I have not bumped the version code , just replaced the file, So anyone with an arm-v7 device, who may have had the provided SQLite3 v4.1 static binary for arm-v7 fail to be detected by the GPay SQLite Fix module, please download the new SQLite3 v4.1 static binary for arm-v7 only from the releases page linked at the end of this post., and sorry for the oversight on my part folks

Also tidied up the OP a little, better formatting, leading to better readability (i hope), hid some more of the older changelogs under the hide tag to shorten the post (again)...
[Magisk] ButtonBoy:
What about Android 10?

What can I do to help you debug this on Android 10? It does not seem to work, as the Safety Net still triggers on my OOS-10 device.
[Magisk] jcmm11:
This won't help with Safety Net. For tips on passing Safety Net see https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
[Magisk] jallenhayslett:
Can confirm, [MENTION=9317193]73sydney[/MENTION]'s module does the job on a fresh system. I've done it a few times, even accidentally swapping the last two steps (reboot, then add card), and it still managed to work. Obviously you'll want to follow their instructions by the letter to avoid issues, but it does seem as though if it's a fresh system there is some wiggle room.

Can also confirm that it will be a mixed bag of hassles if you try to do it on an already set up system. Almost more trouble than it's worth.

Simple steps:

Wipe

Flash ROM

Flash Magisk (kernel, recovery, etc. optional)

Boot system

Setup Google Account

Install Google Pay (Don't open the app, just install)

Flash SQL module

Reboot

Flash GPay module

Add card(s)

Reboot

From that point just continue setting up the phone, updates, modules like normal.

I usually stop the auto updates after adding my Google account and re-enable them after I flash the GPay module. With Android 10 I ran the Google Play Services update check before flashing the module but, depending on what they do to block it in the future, it may be advisable to skip that update until after you've flashed the module.

Caveat Emptor:

I run a Pixel 2 with Google's stock factory image so I probably have fewer hoops to jump through than most but, for reasons I could never quite pinpoint, my GPay started flaking on me last year and eventually I just gave up on it. A few months ago when this module came along I decided to give it another shot and it cleared up whatever issues I was having and I haven't run into any problems since.
[Magisk] aagha:
I think you're right.

I waited about 48 hours and was able to add the card.
[Magisk] kevin.chiha:
Does anyone know if google pay would work on a smartwatch linked to my rooted phone? i.e. google pay doesn't work on my phone because it's rooted/custom rom. Would google pay work if I got a smartwatch and linked it to my rooted phone?
[Magisk] kevin.chiha:
Before trying this fix, google pay wouldn't let me add any cards. I tried this fix with the same steps and I could successfully add cards to Google pay. However, when paying at a shop, the terminal would give an error and payment doesn't go through. Tried it many times. Anyone know why?
[Magisk] 73sydney:
Meh, another issue.....my fault

Magisk Method Gpay SQLite Fix.....

Changelog:

SQLite binary for arm-v7:

18/11/2019

install.sh:

Changed:

set_perm_recursive $MODPATH 0 0 0755 0755

Oversight meant permissions for the sqlite3 binary were not being set properly after i changed the module install logic over, my bad

So, those who have bothered to have had GPay issues (or have bothered to open the /cache/payfixfirstrun.log and find SQLite3 command FAILED) and use the SQLite3 arm-v7 binary from me, please use the new zip next time.

Its always easiest to get this fix working on a fresh flash, but if you want to try fixing the issue without a new flash, you can try this:

1) Uninstall the SQLite3 binary & Gpay SQLite Fix

2) Clear the cache and storage on Google Pay

3) Reboot

4) Install the new SQLite3 binary

5) Reboot

6) Install the Gpay SQLite Fix

7) Add card to Google Pay

8) Reboot
[Magisk] wrapcaesar:
Hello, in the github the most recent version is 9 days ago and you said that you changed 2 days ago. And where is the sqlite3 updated?

Thanks. I can't make it to work... If it works one android 10 nfc payments, I'll give you some money ☺
[Magisk] vonDubenshire:
Ok I really think people are not taking their time to read the instructions

I am still using the original mod packaged together in Magisk with no issues

Been working for me all beta & today
[Magisk] 73sydney:
I changed GPay SQLite Fix v1.9 9 days ago - the release date states this because i created a new release

I changed SQLite3 v4.1 2 days ago - the release date says June because i only updated the file attachment to that release, and didnt create a new release becuase it was hardly worth doing so, there enough numbers in SQLite3 v4.1 adding a v1.x to the end didnt seem helpful (the existing v4.1 is the version number of the included SQLite binary). sure i coudl rename it SQLite3 4.1 v1.x but i really hate verson creep for the sake of one file :)

I cant really make it any clearer than the info inthe original post here: https://xdaforums.com/showpost.php?p=79643248&postcount=176

I recently (maybe 4 days ago) edited that to make it very much clearert than it used to be....

It was tested and developed on Pie, on my Note 4 using LOS 16. I dont have an Android 10 device, or a device that runs Android 10 to test on, some people have no issues when using it on Android 10, others do ...so you may find help from other using Android 10 in the last 5-10 pages of this thread, some of those tips seem to be variable, when one becomes an accepted method ill add it to my ogirinal post. I do expect an Android 10 build for my Note 4 in the coming months, but till then, theres no point asking me for help with Android 10, i simply dont have a device that runs it...
[Magisk] wrapcaesar:
It's very clear and I did all of that, but it's not working on my oneplus 7 (android q) with android certified and netsafety passing. I don't know what to do anymore ;(
[Magisk] 73sydney:
As i said, read the last 5-10 pages of this thread for tips from others using Android 10....

I know some people had issue because they were also running EdXposed on Android 10...which i never have.

Again, no point asking me, i cant give you answers based on an OS ive never used (Android 10) or other frameworks i never have (EdXposed)

Always read the last few pages of a thread for recent tips or search it, theres this thread youre on, or this one (thread where the module is actually hosted): https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/page73
[Magisk] wrapcaesar:
Hello 73sydney, thank you for responding so quickly and being so attentive. I have android 10, everything seems correct and no edxposed but I still get an error and cannot make payments with nfc doing your method very carefully.... What can I do? :(
[Magisk] kevin.chiha:
Which device and ROM are you using? It seems that tap to pay is not working on android 10 AOSP roms. Something about an HCE bug for NFC. Nothing to do with 73sydney's fix. This fix only lets you add cards to google pay. If you're able to do that then this fix is already working for you.
[Magisk] vonDubenshire:
Remove find my phone from device admin

Uninstall Google pay

Clear storage from Google Play services

Hide the important services.

Reboot.

Let GPS update

Reboot

Toggle Magisk Hide on, then off, about 45 seconds after each reboot

Make sure GPS is done updating

Install Google pay, hide it in Magisk

Reboot again, do the toggle

Install at least these: busy box, curl (not necessary?) , SQL module fix, propsconfig? Maybe not needed

Do them one at a time and reboot after each

Do SQL patch last

Hide any more suspicious apps that night talk to GPS and tell it you're rooted

Hide Google Pay

Reboot again, do the hide toggle, wait a bit

Now try to add a card from scratch.

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

Oh that's out of my league

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

Oh that's out of my league
[Magisk] wrapcaesar:
I'm using Oneplus 7 and its official rom (OOS 10.0.1). I've been always able to add cards to google pay but not pay with nfc (only on android pie)... I thought this fixed it!
[Magisk] wrapcaesar:
Can someone tell me or show me how the dg.db is set up, please? I think I screwed up there trying to fix it so many times andd changing it... Or at least, how can i reset everything on that database?
[Magisk] zencooler:
Try to remove dg.db file and reinstall Google Pay with clearing data. It should generate the new dg.db.
[Magisk] wrapcaesar:
I did remove the database and it's still not working after completing all the steps...

My new database shows 3 rows and one at "0" ad_attest, devicekey at "10" and checkin at 14400
[Magisk] linuxdep:
Hi, for two days i have fixed the safetyNet Status to green, but twoday it is red...

last fix ha had used EdExposed Manager to blacklist google services and google play? twoday i have test with all google apps/services, but always red???

Can someone help me?

---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------

Hi, for two days i have fixed the safetyNet Status to green, but twoday it is red...

last fix ha had used EdExposed Manager to blacklist google services and google play? twoday i have test with all google apps/services, but always red???

Can someone help me?
[Magisk] -sandro-:
I tried to read the thread but I couldn't find any definite instruction and there's nothing in the first post like always.

I'm running Android 10 on the OP6 with stock rom + root. In stores I can't make payments via GPay NFC. It worked with Android 9 and magisk hide.

1) is there a fix that works?

2) can you link the instructions?
[Magisk] wrapcaesar:
Sandro, it's quite ridiculous but I found out its a oneplus problem and not root as its working for some people. I went as far to re lock the bootloader and lose root jus tbwcause of Google pay. It still doesn't work. I have oneplus 7... We will have to wait for a new security patch update...
[Magisk] jhpdroid:
Install the MagiskHide Props Config module and use it to set the device fingerprint to OP6 A10.
[Magisk] -sandro-:
What's that for? the fingerprint part I mean
[Magisk] jhpdroid:
The OOS A10 fingerprint (at least for the Tmo phones) causes the SafetyNet ctsProfile check to fail, replacing it with the module fixes it.
[Magisk] YoshiFan501:
So i have a weird glitch with my google pay. I cannot add cards because they say double check your card details, no matter what i type into them. i scan my card and type it in multiple times, no dice. adding paypal works, though.
[Magisk] Hyflex:
Hi,

I'm running into an issue with the LG ThinQ app detecting root yet somehow I managed to add a contactless payment with Google Pay.

It's a Pixel 2 XL with Stock ROM, Magisk Beta, MagiskHide Enabled, MagiskHide Props, Systemless Hosts.

I pass the SafetyNet tests on the Magisk app

Anyone able to look into the ThinQ app and provide me with some advice?

Thanks
[Magisk] milesian:
ThinQ looks for the Magisk package/name which you can change in options. Do that then reinstall ThinQ and you're good.
[Magisk] Hyflex:
Genius, thanks buddy!
[Magisk] umijani010:
Hi

Since note 10+ Android 10 update I am unable to use GPay. It always detects root before I can add card. SafetyNet is all green? Any help? Thanks
[Magisk] zencooler:
Just follow the manual on special dedicated thread here: https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

It works fine on Samsung phones with Android 10.
[Magisk] umijani010:
It worked :) Thanks alot mate
[Magisk] Gruber008:
Today, for the first time I've got an issue which states that my phone is rooted and that I can't use Google Pay (even though I pass SafetyNet).

I'm running OOS 9.0.8 on my OnePlus 5 with edXposed.
[Magisk] Cedoresti:
hi, maybe i have wrong question, (i don't reading about permissive and enforcing) the gpay possible work on permissive ? i use custom kernel.
[Magisk] Bernard9:
Same here sadly. Oneplus 5t, edexposed and suddenly Google pay stopped working. Safety net was failing, but after installing hidden core module via edexposed safetynet is passing again. However that did not fix the google pay. I tried installing props config via magisk and resetting the fingerprint via terminal as suggested earlier in the thread and that didn't help as well. Anyone has any idea how to fix? Latest magisk, latest edexposed running.
[Magisk] dustintinsley:
Same for me. Just happened today. OnePlus 7 Pro.

---------- Post added at 09:29 PM ---------- Previous post was at 09:12 PM ----------

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950 fixes the issue for me.
[Magisk] Atharkhan101:
Worked

Flashing Magisk 19.4 zip worked. I think the culprit is the magisk zip update. It never worked on Magisk 20.0 zip so I tried flashing old versions and it worked. Magisk manager apk can have any update it doesn't matter. My other banking apps are working however HDFC banking app is not working. Can anyone please help me how to make HDFC banking app work. I tried RootCloak, magisk hide still not working.
[Magisk] derFan11:
With Magisk 20.3 I experienced an interesseting issue. GPay (and some Google Services) takes forever to load. And when presenting the card for payment nothing happens, as if NFC is disabled (it's still working though). I've the SQLite Fix installed, everything is hidden and GPay dosen't complain about root.

So I'm little bit lost here. Any suggestions?
[Magisk] patrickdrd:
hello,

what can I use to bypass icard root detection?

I tried with rootcloak xposed module,

it works on one mobile device, but not on the other
[Magisk] HaselnuesseTo:
I'm facing exactly the same issue. Do you found a fix for it?

Magisk Manager 7.5.1 and Magisk 20.3, Android 9 (lineage_polaris 190405.003885f5c804a)

EDIT: I read older pages of this thread and it seems that this issue exists since June 2019. Search for "nothing happens" in this thread. There's also an opened cases at googles issue tracker.
[Magisk] derFan11:
Good to know, that I'm not the only one.

I didn't found a fix. I had my suspicions about Magisk, but didn't tried to find out how to downgrade to 19.x (which seems to be a possible solution).

I'm on Android 10 with Xiaomi.eu 11.0.5 (MIUI11).
[Magisk] ykjae:
I've been tryna get the Hub workstation app to work obviously for work reasons.. Now that I've gotten Google pay to work following this guide I'm wondering if there's something simply changeable to hide the custom os./root detection.
[Magisk] bbender716:
FYI, updated to Feb security update for Pixel 4 and pay fix no longer works. Neither the gpay module nor manually setting dg.db 'attest' entries to 0 and chmod 440 work. Instead you get a new error that says "invalid entry' I'm the app when enabling the card and then the dreaded "card could not be activated" message.
[Magisk] warrencoakley:
Yes I got this too. Any one know a fix?
[Magisk] 73sydney:
That doesnt sound good, but perhaps one shouldnt be surprised if they have, at last, put in some new gubbins to try and stop the circumvention

Sorry i cant do anything practically as im still stuck on my trusty Note 4 with patches to December :(
[Magisk] Bluffer94:
I just updated my Pixel 4 to february patch as well through factory image without wipe.

Google pay works just fine, I added a new Visa card without a problem.

I'm using latest magisk canary.

Gesendet von meinem Pixel 4 mit Tapatalk
[Magisk] warrencoakley:
I stand corrected, just cleared GMS, reinstalled GPay Fix and Patch and its back working
[Magisk] RootedLee:
PayBack Pay app

Same here. Does anybody have any luck getting the PayBack Pay app to work despite of Magisk and root?
[Magisk] drup88:
Has anyone had all their loyalty cards (passes) dissapear suddenly?
[Magisk] sliding_billy:
I only have one, but it is still there (I am using manual SQL edit not the module).
[Magisk] zencooler:
I have many loyality cards (more than ten) and use GPay fix (sql patch) since last year and they never dissapeared.
[Magisk] lordxenu:
are you guys hiding the magisk manager too? Santander banking app was detecting root on my phone until I hid Magisk manager too.
[Magisk] RootedLee:
[MENTION=7547650]lordxenu[/MENTION] : interesting. Wouldn't one take for granted that MM is hidden by default/ to begin with....

Anyway, with the PayBack app it's different - it does not require MM to be hidden, too, but launches normally after disabling Xposed in MM then restart. Because I'm stuck with Android 7.1.1 on my aging Samsung I can't install Android 8 + EdXposed, which supposedly allows to be either visible to only certain apps via whitelist, or invisible to selected via blacklist. Not a biggie, so I'll just go with that until my next phone with EdXposed.
[Magisk] lordxenu:
it's not hidden by default no, you have to go into the settings menu and give the app a different name, as I mentioned my banking app was detecting root and exiting before I hid manager. Worth a try ?
[Magisk] ct_tec313:
How do you clear GMS?
[Magisk] drup88:
Today I lost all ability to use any of my credit cards and public transport cards in gpay.

Tried removing and adding and now I cannot even add. Has anyone had any issues?

--------- beginning of head
EdXposed Log
Powered by Log Catcher
QQ support group: 855219808
Telegram support group: @Code_Of_MeowCat
Telegram channel: @EdXposed
--------- beginning of information
Manufacturer: Google
Brand: google
Device: coral
Product: coral
Model: Pixel 4 XL
Fingerprint: google/coral/coral:10/QQ1B.200205.002/6084387:user/release-keys
ROM description: coral-user 10 QQ1B.200205.002 6084387 release-keys
Architecture: arm64-v8a
Android build: QQ1B.200205.002
Android version: 10
Android sdk: 29
EdXposed version: v0.4.6.1 (4510) (SandHook)
EdXposed api: 90.0
Riru version: v19.7 (29)
Riru api: 4
Magisk: 20.3:MAGISKSU (20300)

Images of magisk version, modules and safety net passing. https://photos.app.goo.gl/PRaVDJ5a15tJpSro8
[Magisk] zencooler:
But what the GPay message you have got?

First of all check if the /data/data/com.google.android.gms/databases/dg.db file has permissions set to 440

If not it means something wrong with script to secure this file of the Google check mechanism.

Then clear GPay cache and data and set this permissions to 440 and install GPay SQL fix again to prevent it from any atestate status changing. And on the end add your cards again then.

WARNING: clearing data of GPay will loose your list of transactions and (if you had any) loyality cards.
[Magisk] 73sydney:
1) Be aware EdXposed adds complexity and needs extra steps, ive never used it, dont use it. never plan to use it, but info was posted by a member who did, and its available in the original post for my module: https://xdaforums.com/showpost.php?p=79643248&postcount=176

2) If youre using my module, theres also a /cache/payfixfirstrun.log showing what happens on first run, and whether the steps have been completed properly

3) Also, because you reported the previous module version was possibly wiping passes and loyalty cards, i added the ability to NOT clear Google Pay data on install, it has a warning that if you skip this step the Google Pay fix may not work. So if you skipped this step, theres pretty much no way at this point to troubleshoot any further, without wiping the chance and storage of Google Pay.

Try #1 first, if that fails, look at #2

If all else fails, i would weigh up trying #3

If #3 isnt possible for you, then i have no further answers at thsi time. Google security, the module or even the manual steps are just a hack to bypass this, theres no garauntees it will work for everyone.

And as i always point out, the module works best on a fresh ROM flash
[Magisk] drup88:
I managed to get it to work but not long before I applied March update and lost it again. Have people been successful with gpay on March update of Android 10?
[Magisk] cubemario:
I guess google just updated cts checking methdos.

I got ctsProfile: false even after downgraded to January update on my Pixel 4 XL.
[Magisk] zencooler:
Guys, it's not because the security updates. It's because the Google Play Services and/or Google Playstore updates done by Google few days ago. The big number of devs here is trying to patch this CTS fail now... There is one method (quite complicated) in separate thread here:

https://xdaforums.com/apps/magisk/safetynet-fix-google-update-march-2020-t4063679
[Magisk] sliding_billy:
Paid with GPay at two vendors this morning with failed CTS and not certified Play Store (Pixel 3 XL). I have used the manual SQL fix since the day it was posted (on different ROMs and stock on Pixel 3 and P3XL) and just self-compiled and dirty flashed DU 14.1 yesterday. Play store stayed certified until a DU 14.0 dirty flash a few days ago and is still certified on 4 devices besides the 3XL. Adding a card might fail, but for now the app works at least.
[Magisk] zencooler:
+1

I have CTS failed and GPay is still working (I paid today in the shop). However I remember (last year before SQL patch method has been worked out) it was working fine few days (sometimes longer) before it said the devices is not secure. So it's probably question of not so long time and GPay will stop working...
[Magisk] sliding_billy:
Agreed, but just like Play Store staying certified until flash I have a feeling that GPay will work until a card is added. Looks like the detection is happening at a different point than use.
[Magisk] zencooler:
To be honest I don't think so. Last year it was recognizing the security issue during the card adding process but also stopped to work with no interference with the list of cards :(
[Magisk] sliding_billy:
Yeah, we shall see. Last time, we didn't understand the attestation. That just hasn't changed yet.
[Magisk] lilbrat:
Hmm, then I must have a really screwed up phone, I have a rooted OP 6T , latest Magisk version currently none of the mods need to get GPay to work, devices is certified by playstore and services are updated as of 4 March and I just reflashed and updated my phone on Friday, cards were picked with no issues and verified and used it just fine... so is it just effecting certain brands/models?
[Magisk] smohanv:
I use the method explained in this thread. I always get my GPay works in Android 10.

Thread link: https://xdaforums.com/Mi-9/how-to/g...xiaomi-mi9-t3972227/post80326837#post80326837
[Magisk] Ryoncz:
I have 1+6T also, even root and my GPAY is broken. I fixed that with two magisk modules (SQLite3 Universal Binaries and GPay SQLite Fix) and GPAY go again broke today morning.
[Magisk] dr4go:
Are you kidding me? You can't even use Chrome with that garbage. Completely useless... Fascinating what it actually does though: it supresses Google's answers of the SafetyNet requests... still useless...
[Magisk] zencooler:
Hah. You are right. It's not mine :)
[Magisk] drup88:
What magisk modules do you have enabled? What are you magisk hiding?
[Magisk] lilbrat:
This is all ....