yashsingh1/xdaforums huggingface dataset:
[Magisk] zencooler:
>> firstly clear GMS cache and data

how do I do this? GMS appears in Magisk, but not in the Settings -> Apps area of the phone where one can clear cache and data. Or do I manually do this somewhere via the file system?

--> If your phone doesn't support of clearing cache and data in the Settings-Applications then simply use Titanum Backup: find GMS on the application list and use options "Special Features" for clearing cache and "Backup properties" for deleting data. (of course do the backup of GMS before you clear its data - you can do this via Titanum Backup [apk+data])

>> remove full GMS data folder

I presume this is the /data/data/com.google.android.gms folder?

--> Exactely. Remove this folder (of course please do the backup of this folder for any future inconveniences if you want to go back to previuos settings - you can e.g. simply move whole folder to SD card)

>> reinstall of GPay

There doesn't seem to be an uninstall option for GPay, just the ability to "Uninstall Updates" .. ?

--> Hmmmm... It looks you have GPay installed as a system application. If so, please first Uninstall updates and then use Titanum Backup to Unistall base Google Pay app. Obviously do the restart of the phone after it's done (and once again: do the backup of GPay before you uninstall updates and base app - you can do this via Titanum Backup [apk+data])

Many Thanks..!

--> No prob :) Remember to zero attestation values in the dg.db and to change permission of this file to read only (following guides in this thread) before you add your cards to Gpay
[Magisk] nevoz:
hi zencoooler,

Thanks again for your great help, unfortunately it is still detecting root. This is what I did:

- used Titanium backup to clear GMS cache and data

- deleted /data/data/com.google.android.gms

- used Titanium backup to clear cache and data for Gpay, and to Uninstall it

- rebooted phone

- installed Google Pay (from Play Store)

- followed the steps in the original post from BostonDan (attestation was already zero for the one line in the database. No editing needed.)

- used root explorer to check dg.db permissions (was still on 440, I presume since no editing of the file was needed)

- ensured that GMS and GPay were hidden in Magisk Hide (GMS was already enabled for hiding. Enabled GPay for hiding)

- ran Gpay ... still no good.

Cheers.
[Magisk] alphahere:
https://www.xda-developers.com/google-pay-safetynet-checker-pixel-4-face-authentication/

The game continues.
[Magisk] sliding_billy:
If only Google didn't throw hidden checks in both before launching an updated version and after when they realize that Safetynet doesn't mean crap. If they have hidden mechanisms in place to keep an app (that is is supposed to use Safetynet as its security determinant) like Netflix from showing in the store or getting updated, imagine what will happen with a financial system that is too easy to "hide" modifications. Seriously, is anyone ever going to feel safe enough again to walk into a store with nothing but a rooted (or BL unlocked) phone and GPay and not carry a card in your pocket? Once we get to a point where you can check attestation before purchase and the purchase fails (it will happen) despite attestation passing, we are back to carrying a card just in case defeating the whole purpose of GPay.
[Magisk] marvi0:
Thanks op this worked for me!
[Magisk] zencooler:
Oopppsss. Bad luck.

It's quite obvious but have you checked if SafetyNet is passed in your Magisk Manager?

Second (and maybe the last) try: hide also Google Services Framework if the SafetyNet is passed successfully.

By the way: do you have stock kernel or some custom one? It's known issue on some configurstions/smartphones that unlocked bootloader is not hidden by stock kernel but some custom kernels hide it successfully. Maybe that's the issue you faced in your case.
[Magisk] crisco654:
Happy to report this worked! I have a Pixel 2, and I'm on Android Pie with July security update . Magisk 19.3, using Magisk Manager 7.3.2. Haven't tested it in an actual store yet.
[Magisk] pokeseeker:
Is it safe to update to Google Pay 2.94?
[Magisk] sadiku:
I did update today and payment still work fine.

我從使用 Tapatalk 的 Pixel 2 XL 發送
[Magisk] badaas:
Use Canary magisk + props editor magisk module.

Use props to change fingerprint fw to latest.
[Magisk] Player04:
I can confirm update still works on my s10+
[Magisk] biikman:
Worked fine on S9 + SM-G9650
[Magisk] nevoz:
hi Zencooler,

I owe you many thanks. It should have been obvious to me, but I didn't realise the importance of SafetyNet passing. After seeing your post, I ran the SafetyNet check, and found that it failing due to "ctsProfile: false". I did some Googling and attempted the MagiskHide Props Config, but the osm0sis busybox just wouldn't install. I then looked around for other methods to get ctsProfile: false to change to true, without luck. I then decided to wipe then phone. Props and busybox then worked fine, ctsProfile passed, and GPay then accepted the cards (without even needing to even do any of the BostonDan stuff .. ! (except for hiding the required apps in Magisk) ). I tried it in shops and it did work - except in one shop I was getting a "card declined - do not honor" but I don't think that has anything to do with root detection.

So, thanks very much for persisting with my issue Zencooler, I would have given up otherwise!
[Magisk] zencooler:
Thanks for the info. Glad to hear you found the solution! [emoji106]

Remember to secure dg.db by setting read only permissions as GMS is working continuesly on checking attestation. Even if this works now it can stop one day if this database is not in read only state.

Regards!
[Magisk] nevoz:
Thanks again Zencooler,

I notice that the attestation values in dg.db are set to 10, instead of zero, but GPay still seems to be working. Should I change this to 0 before changing the file to read-only, or is that unnecessary?
[Magisk] adrisanfe:
I am on a Redmi K20 Pro with xiaomi.eu, if i flash this "GPay SQLite Fix (Full Edition)" on magisk, should google pay work? Sorry, but im new in this thing of GPay and i am a bit confused
[Magisk] zencooler:
Yes, change values to zero before you change permission to dg.db file. Many users reported that GPay was working fine with attestation values different than zero but later on it failed. So it will be better to zero it and then set 440 mod to the file according to this thread explanation.
[Magisk] nevoz:
Thanks again Zencooler, have set attestation to 0, and dg.db perm to octal 440 :)
[Magisk] potato salad:
Thanks for this! Really straight forward. Worked for me on a pixel 3a XL and confirmed at a walgreens.
[Magisk] xunholyx:
After I read that article a few days ago, I stopped updating G Pay. It's sitting there waiting for an update just like YouTube (I have Vanced)
[Magisk] zencooler:
I have upgraded GPay to latest ver. 2.94.259479103 and GMS to latest ver. 18.4.53 on last Friday (2019-08-02) and everything works with no problem at all.

Of course I have dg.db secured with 440 permission and attestation values set to zero. I use custom ROM and Magisk 19.4 + Magisk Hide.

I paid contactlessly many times after this upgrade, so seems to be still the working solution for Note 9 with my set up as above.
[Magisk] HyunJoon:
Same here! Update to 2.94. And it stil working.
[Magisk] Player04:
I updated to latest version and used gpay checkout yesterday, at costco. STILL WORKS
[Magisk] ciltocruz:
This works perfectly for me in the 3XL pixel.

I installed it last Monday 29 and today it is still working properly. For now there are 5 correct payments.

Thanks!! =)
[Magisk] smokeythebear3:
Anybody else on the Android q beta 6 having any problems? I have magisk hide enabled for both GMS and Android pay, plus I modified the dg.db file and I still can't add my credit cards.
[Magisk] Shylockus:
Samsunf s9+ ...succesfuly rooted then edited and dg.db set to read only..gopay worked but no samsungpass.... then unrooted succesfuly..but not worling properly... so tried to root again AND it was not possible... db.bd was not erased during rooting procedure was not able to rewrite it (it is not in whiped content!) roor stuck in bootloop... so i was able to load to stock rom again but dg.bp is read only and i ca´nt find a way to set it r/w again... root is impossible...funny...factory set phone is not possible connect to samsungpass and gogle pay..... so if you unroot dont forget to set dg.bp to r/w state... it will NOT be rootable again... OR does know a way to set it R/W without rooted system???
[Magisk] jonners59:
Superman rom on samsung s7

Did not work... any ideas, please
[Magisk] lapapunk:
Same here.

Guys, help please.

Fix doesn't work on pixel 2xl / Android Q beta 6.

Any chance to fix it?
[Magisk] xunholyx:
Are you using the MagiskHide Props Config module to change you device fingerprint to Pie? G Pay doesn't work on Q yet, so you have to make it think you are on Pie.

You can find it in the Magisk module repo. The thread for it is here

This is what I'm using for Pixel 2XL on beta Q
[Magisk] lapapunk:
Ok. I've installed props config, and now I should add path for pie fingerprint in build prop? But where I can get this path? Can u share yours?
[Magisk] elreydenj:
After install open terminal emulator of your choice and type su then hit enter. Then type props and press enter. Follow the steps that appear after.
[Magisk] lapapunk:
Yeah. Thx u guys so much. Now it's working.

Love u xD
[Magisk] Larzzzz82:
[MENTION=2449699]BostonDan[/MENTION] thank you for this. It worked perfectly.

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

[/COLOR [MENTION=2449699]BostonDan[/MENTION] thank you for this. It worked perfectly.
[Magisk] finesse:
Any one installed the new version of gpay, 2.95.262992467? Regards
[Magisk] CSX321:
I have, and I just now paid successfully. No problem.
[Magisk] xunholyx:
Yes. I did. It still works.
[Magisk] finesse:
Thanks, as ever. Best regards.
[Magisk] FruitSidewalk59:
works!

Thank you so much. I was finally able to use gpay yesterday (at Trader Joe's)
[Magisk] jaggillararla:
Love u too man (no homo)
[Magisk] Jexx11:
Working for me on August update Pixel 2 XL, thanks for this!
[Magisk] Terrigible:
Maybe don't quote the whole post and just @ them on your next post?
[Magisk] vonDubenshire:
I have reset my phone several times and used this script flawlessly each time. It also works with Android Q, but I have to change the device fingerprint back to Android Pie.

I am on Pie now. No issues.
[Magisk] in_dependence:
unfortunately, didn't work for me. Services and GPay are hidden in magisk. SQlite installed, GPAY sqlite fix runed, device rebooted.

Nexus 5x, LineageOS 15.1.

GMS version - 18.3.85(090400-2677519)

Google pay version - 2.95.262992467

Also, i didn't lock my bootloader. Is it safe to do this on custom rom?

best regards
[Magisk] Rohan3910:
If you lock your bootloader on a custom rom, it will no longer boot.
[Magisk] in_dependence:
Thanks for advice. So, is there something i can do to make gpay work, or there is nothing for now and i should wait for thread updates?
[Magisk] jaggillararla:
Did you get magiskhide props config ? And change your devices fingerprint there. Since you're using a custom rom you need to get that module from magisk

Edit you also need busybox from magisk
[Magisk] in_dependence:
Didn't know about this.

Fingerprint change helped. Thanks a lot!
[Magisk] scarlaty:
Hi,

Didn't work here, I've tested without and with the magisk Gpay script but same problem.

When I try to set the NFC for my CB (Boursorama and Revolut), Gpay says I need to contact my banq :

[IMG="Capture of error"]https://i.imgur.com/eVyJILL.jpg[/IMG]

My Xiaomi MI 9 run with last global xiaomi.eu rom.

Sql lite installed

Magisk modules :

- Busybox for android NDK

- GPay SQLite Fix (1,7)

- MagiskHide Props Config

Any idea of what I'm doing wrong ?

Edit : After delete /data/data/com.google.android.gms/ and reboot, it's working ! Thanks ;)
[Magisk] JanyV50:
Works! After so long time, this simple trick worked! Mi MIX 3 on MIUI 10.3.2 EU, Magisk 19.3, hidden google play services and google pay.
[Magisk] Foba:
Thank you sooo freaking much. I haven't been able to use Google pay for almost a year now. LIFE Sava

Just for reference:

Device: Google Pixel 3XL (crosshatch)

Android Version: 9

Magisk Version: 19.3

Magisk Manager Version: 7.3.2

Google Pay Version: 2.95

Google Play Services Version: 18.3.85
[Magisk] Nextasy:
Ok,l tried and its not working.

The OP says "change any value that lists "attest" in the name ". Does that also include the ones that say "ad_attest"?

Can somebody tell me which trick or process actually works?

Thanks
[Magisk] ssceddie:
No, or try it if not works^^
[Magisk] loadie:
This is what I have. Followed [MENTION=2449699]BostonDan[/MENTION] to a tee.

Been working since may though gpay and security updates to current August.
[Magisk] Nextasy:
Did you also.run the terminal command as instructed in the OP?

oh, l 4got to say l have a Samsung galaxy s10+..So the db strings are quite different. Dont know if this makes any difference..
[Magisk] loadie:
not sure about samsung, i have a pixel 2xl but yes, i ran open the terminal emulator.

1. su

2. cd /data/date/com.google.android.gms/databases

(note, i believe there is a space between cd and / )

3. chmod 440 dg.db

this makes the dg.db permission 440 ( read only)
[Magisk] Nextasy:
l ran the command just now and l got a "not found" error. maybe die to the missing space.

l ll try again.

tried again and this time no error. how do l know if it's working?
[Magisk] loadie:
It took me a couple of times to get it right.

Does that path manually take you to the dg.db file?
[Magisk] Nextasy:
I think l got it right this time, at least no error. But how do know it works?
[Magisk] loadie:
I would reboot and then go check permissions on dg.db file and it should be 440. Is so, it stuck.
[Magisk] Nextasy:
yeah, attribute is 440 and l was able to add my cards details

cheers
[Magisk] evilryry:
Looking for an opinion on my pay issues. I have a 3 XL rooted on Q/10 Beta 6, which is now supported for Pay. Pay was working great for a few days after being on Q, and within the last few days it's stopped working. I have the fix applied and have tried to reapply it a few times and have also used the magisk module to automate it. Everything looks in order with the db file. Phone passes safety net as it should, magisk hide is checked for everything necessary, and everything else I can think to check looks absolutely fine. But the pay doesn't work, because it says something about the software and being rooted and all that jazz. Getting confused with it. Any opinions/suggestions? Pay has been working fine still on my girlfriend's Pixel 2 on Q as well, so I dont think Q is the problem. Thanks!
[Magisk] onimaca:
Since i installed the SQL-fix i no longer receive notifications for most of the apps like bank, emails, whatsapp business... that were shown before instantly

It seems the fix interferes with push notifications

Is there anyone experiencing same problem. Any idea about how can i solve the issue?
[Magisk] jaggillararla:
Read through the topic
[Magisk] evilryry:
I have, and nothing has worked so that's why I explained my situation and asked if there was any other options, lol. Thanks for your help though.
[Magisk] jaggillararla:
Did u read about other pixel users who Changed their fingerprint?
[Magisk] evilryry:
Yep. Though that shouldn't matter, since Q passes safety net. Fingerprint change is mainly for those who can't pass it due to a CTS mismatch afaik.
[Magisk] buffal0b1ll:
You would think.

But you gotta spoof a pie fingerprint on Q for Pay to work.
[Magisk] evilryry:
It worked for a little bit. GF is on Q (B6) on her pixel 2 and uses pay daily. Confusing.
[Magisk] buffal0b1ll:
GF has locked bootloader, right? If you have unlocked bootloader and you're on Q with a Q fingerprint, Google can detect it (even tho you pass safety net) and fails to add cards to Pay/make transactions. If you want to stay rooted on Q and use Pay just try changing the fingerprint with the mod already. How many testimonies in this thread do you have to read before you believe it?

I've been passing safety net on Q since DP1, but didn't finally get Pay to work until I combined: sqlite edit 440 dg.db AND MagiskHideProps pie fingerprint.
[Magisk] simplepinoi177:
So happy for this...!!!

I just wanted to come back here and give my thanks to this thread!

I was able to finally try and pay for something at a store front and was so happy (and shocked tbh) when it worked flawlessly! As I've mentioned before, I've tried many other methods and "workarounds" ranging from simple to complicated, and I have been successful from searching, finding, installing the app up to running it successfully without errors or blocks and even successfully loading credit cards and verification for "in-store purchases"! But, in the end, I would be able to get that far, but still not be able to make a purchase as the app would come out with an error; which was weird because the NFC would still detect and vibrate so the signal and data would exchange, but would be stopped on the app end...I actually ended up giving up using the app/feature for the last couple of months with the compromise of keeping rooted.

Now I can breathe easy and relax with the knowledge that this is an open option available to me when I need/want it.

Now, the only thing I'm wondering/curious about is, as I update by using the Full Factory image and the flash-all way, that this usually formats and resets system files and permissions and if I'm going to have to re-do this workaround method every single time; although, if that's the way it has to be, I'll be glad and more than willing to if it saves me this...

but GOD! sifting through the SQL trying to find "attest" and changing things to "0" is sooooo damn tedious...!!!

Also, I've found a user (@alershka) who says he doesn't even do any SQL editing, and merely deletes the .db file, updates, redoes the "fingerprint" via the a magisk module, and then just has to add the cards back...so...I wonder...

Anyways....this is so great and after a considerable amount of time I'm super happy for this!
[Magisk] Software Guru:
I've followed the instructions but GPay says 'The card can't be used to pay in stores' for both my cards (they both have contactless icon on the card and I know they both work)

:(
[Magisk] Terrigible:
Check the Google pay website for your country to see if your card can be used to pay in stores.
[Magisk] Software Guru:
I live in the UK, it should work with no issues
[Magisk] Terrigible:
Where you live has nothing to do with whether your card can be added or not. Please check the website to be sure.

EDIT: Let me do you a favour. https://support.google.com/pay/answer/7351534
[Magisk] Software Guru:
Apologies I saw B Bank and assumed it was Barclays but looks like they are not supported which I find very strange

;)
[Magisk] highdiver_2000:
I used OP's steps. A bit brain numbing to change all the lines of attest.

Could have use the script but I was lazy to search and confirmed the right version of sqlite.

It works! Bought lunch and dessert in different transactions.

Now to figure how to do this on my main phone, mix 2s
[Magisk] simplepinoi177:
I know it's been referenced before in this thread, but since it was around 7 pages ago, I'd like to re-iterate it again here for future reference...

You can find 73sydney's SQL Magisk module and initial post

HERE

or on post #176 . Also, you can get the url for direct download in his signature (of course also found on said post).
[Magisk] finesse:
Anyone updated to the latest Google services?
[Magisk] ilarson007:
This worked for me on Android 10, Pixel 3XL, build QP1A.190711.020.

Thanks!
[Magisk] dardack:
Updated to 10, GPay still working, the dg.db still read only. So far so good until they break it again.
[Magisk] Shycat:
Make magisk work with Google pay

Hi, did exacly what you explained and it perfectly worked. Before finding your post, I've tried everything possible (Hide root with Magisk etc...) Thanks! :D
[Magisk] wabmorgan:
Updated to Android 10. Still working. ? Pixel 2 XL
[Magisk] jmaa_:
I originally tried this on my Pixel 3 XL running Pie and was unsuccessful, so I decided to try again after doing a fresh flash of Android 10. Did full wipe and flashed QP1A.190711.020, installed Magisk Canary 19.4 using the patched boot.img method mentioned here (https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117), and followed your instructions. So far I've been able to verify existing cards, add new ones, and pay for a purchase successfully. GMS version 19.0.56, stock build and haven't installed any modules yet. I'll post an update if I run into any issues.
[Magisk] speedtouchbr:
Everything working here! Thank you
[Magisk] dunderball:
Just wanna say the Magisk module worked great for me. I'm on a Pixel 3a using Magisk stable, on latest Android Pie release.
[Magisk] Fentadroid:
Sorry, stupid question:

1) GPay.SQLite.Fix.v1.7.zip is a magisk module right? So when you mean "Install" you mean through Magisk, correct?

2) How the module works? It runs every time we reboot the phone or do we need to install the module everytime we add a card o make changes to the system? Such as system upgrade, re-reoot etc etc?

3) I suppose it works on Android 10 too

4) Why don't you add it to the magisk module repo so any upgrade will be easy? :)

Thanks!!
[Magisk] HerrT:
1) yes

2) it runs on reboot. no need to run after adding a card

3) yes (at least on my phone)

4) https://xdaforums.com/showpost.php?p=79755673&postcount=271 (paragraph "Edit/Update:")
[Magisk] pataposha:
What is meaning of that 10 value?

It seems that 10 = some google "failure" status code and 0 = "good" status code?

It seems that dg.db contains last protobuf-requests (including binary data, protobuf name, timestamps).

Strange thing is magisk successfully hides itself from SafetyNet specifically in "attest" protobuf, it would be logical to mark this response as "good" but still we have modify it in db.

Can somebody specify meaning of 0 and 10?
[Magisk] simplepinoi177:
Well...I can't speak towards the other things...but in HEX and basic coding, 1 (or derivations of 01 or 10) is a sort of "trigger" or an enabling of sorts; while 0 is the opposite. I'm thinking setting it to 0 removes all the to-do "checks" Google Pay or Google Play Services or something or other requests for before allowing the process to move forward or the processes after the checks; or, essentially, changing it to seem that it doesn't require those checks anymore -- because then it would/should be stopped by the "10" value or "trigger".

But, disclaimer; I am no expert, and only have a rudimentary understanding of basic code; so I could just as easily be absolutely mistaken...
[Magisk] D3RP_:
Works on Android Q, latest as of September 5th, Pixel 2 Vzw.
[Magisk] 73sydney:
Thanks [MENTION=5406457]HerrT[/MENTION] for the linkage to the (longer/original) answer

But, yes, it would be ideal to have module added to the magisk repo, but basically it boils down to the fact that:

a) i encountered some really rude tools manning the approval process (not Didgeroodoohan its important to point out) and i couldnt be bothered dealing with egos

b) i was told by aforersaid egos it didnt do "enough" to warrant adding - meanwhile simpler modules exist like ones to replace gps.conf with custom settings, so you figure that out, and let me know :)

But i did everything i was asked and tried to jump through the hoops....but theres only some much assclownage i can tolerate :)

I take some comfort in knowing its useful to people and like to point out i didnt create the method, i just packaged it to make it easier for people to use the method
[Magisk] Zerogoki_00:
Android Pie OmniROM, Magisk 19.4 Canary, GMS 19.0.56, Google Pay 2.96, everything works! Thank you
[Magisk] fOmey:
a & b) Screw them.

c) [MENTION=4667597]Didgeridoohan[/MENTION], get this dam module on the repo already.. pull some strings.
[Magisk] 73sydney:
He came up with the trickiest solutions in it too :)