yashsingh1/xdaforums huggingface dataset:
[Magisk] andrewwdai:
folks, I noticed that GPS updated from 17.1.22 to 17.4.55. I thought in order for GPay to work I need to leave dg.db RW so that an entry of "attest" would be created and i then can change it to "0". It turns out it is not necessary. I have dg.db locked RR, and despite the update of GPS I can still use GPay with no problem at all. So at least at this point we don't need to run the script as long as dg.db is locked.

a side note: now banks are rolling out "contactless" ATM, i just need to wave my phone to do a balance inquiry. If GPay allows you to withdraw money, it surely should allow you to use credit card. no embarassment at point of sales no more!!!
[Magisk] exovision:
Got you wrong. :D

No idea what "Bash Savvy" is but I'm more than capable technically. Probably more so than most here I'm sure...

I'm just not a PC guy that's all.

Got Termux.

Can you give me detailed instructions from the beginning.

1. Save the script. HOW? With Termux?

2. ~/ (Enter)

3. Open Script HOW? And why can't you just run the command.

Make Script from this full command? No changes?

am force-stop /data/data/com.google.android.apps.walletnfcrel
chmod 777 /data/data/com.google.android.gms/databases/dg.db
/sbin/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"
chmod 440 /data/data/com.google.android.gms/databases/dg.db

Many thanks. :o
[Magisk] GryphonBR:
That is not at all my experience. Have you checked whether SafetyNet passes from Magisk?

Bash is one of the most popular Linux terminal applications. In terms of how to save it, there are a number of different ways; being a Linux guy myself, I went with 'vi script.sh' and then simply pasted the script, saved it and, to run, command was './script.sh' after making it executable with 'chmod +x script.sh'

And don't get me wrong, I'm not trying to sound harsh or snob, but saying you're technically capable when you need detailed instructions on running a relatively simple script seems a little overreaching.
[Magisk] exovision:
Before I get started, I would like to thank you for your help. :good: I appreciate your help.

I have you taken you in a certain way, and you do sound like a snob as you say. But I wouldn't use that word..

Think about it. I have a rooted Pixel 2 XL. SO I have managed some 'bashing'...

I have 3 mac's and have updated 2 of them with new CPU's (Which requires extensive building), custom software, custom PCI's, USB 3 Mods, installed Windows on a mac to flash a couple of GPU's. And done countless other custom configurations....

I build and customize Analog Synthesizers & Drum machines. I also program complex Calrec, Lawo & Studer Consoles and their routers at work.

I've done a couple of Python coding courses.

I also dabbler with Crypto Currency and the other day I built a carport in my backyard.

So I would say I am more than capable to run 5 lines of code on a phone.

So if you don't wanna sound like a jerk on a forum where everyone tries to help and share knowledge then I would suggest keeping the personal comments to yourself and just dish out the help when someone asks if you have the knowledge. Unless the question start's with "Does the phone need to be rooted to do this".

Oh and I got it working before your last comment just by fiddling around with the script on a .txt file...

Peace.
[Magisk] GryphonBR:
I've been helping a bunch of people for the last couple of days in varying degrees, and I'm glad you seem to have gotten the script running. Or so I presume.

At any rate, I'm not a jerk; it's just that if someone tells me they don't understand Linux scripting I can simplify the explanation. You chose to go the "I'm more than capable" route and now call me a jerk only because I pointed out that you were asking for somewhat basic guidance, which once again is fine but letting people know what your actual knowledge of something is might turn out to be more effective overall. Just my two cents, but since you already consider me a jerk, you might just as well disregard all I've said.
[Magisk] exovision:
I'm just stating I don't need your personal comments and maintaining I have what it takes to run 5 lines of code on a phone.

Thanks again
[Magisk] GryphonBR:
Dude, what personal comments? I said you didn't look very bash savvy, sorry if that offended you. You went with name calling here, not me.
[Magisk] exovision:
You presumed to know things about me personally.

Just leave it. I'm not about to get into a debate on here.

Thanks
[Magisk] Superschmiddi:
Same here :good:
[Magisk] Hubird:
Thanks for the detailed answer. It seems like it's a bit of a cat and mouse game at the moment.
[Magisk] GryphonBR:
Well, actually this has been a cat and mouse for a long time, according to topjohnwu himself. In fact, rooting itself is a major part of the game.
[Magisk] swour:
Did you not make any modifications to the database at all? I'm still on GPS 16.x as everything works fine with this setup. If simply locking dg.db would suffice for updating to 17.x it would make it easier. That in turn would mean changing the attest values are a placebo.

All my attest values are "10" as well. The fails attest value in the android_pay database is negative.
[Magisk] MC_Ohr:
I have manually updated and after that I set the dg.db to read only permission. Everything is working fine here. Just in case it stops working I copied the android_pay and the dg.db to sdcard to overwrite if it doesn't work at all.

Gesendet von meinem HTC U11 life mit Tapatalk
[Magisk] CSX321:
FWIW, after installing the June update, Pay is working again on my phone. :confused: :cool: I'll take it.
[Magisk] Superschmiddi:
I changed the attest values to "0". Nothing else.
[Magisk] Adramel:
What does it look like to add a GPay card like at the moment? I have GMS 17.4.55 .

The "old" way with deleting /date/date/*gms doesn't work anymore.

Can I currently add a card without installing an older version of GMS? Is there any kind of user-friendly way?
[Magisk] zencooler:
There is a whole thread about the solution here: https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

In the short words: the solution is to set the attestation values to zero in the sql database and lock database by settings permissions to read only.

Regards.
[Magisk] Adramel:
Interesting, it's working.

Will GPay still work after the next update or will it have to be done from the beginning?
[Magisk] zencooler:
It will work until Google doesn't change the idea of attestation settings in the future releases.
[Magisk] Vendru:
Pay+ magisk 19.3

Hello,

My magisk safety checks passed although I cannot use google pay as it said my device has been modified. Netflix e.g. works perfectly. What can be the solution?

P.s I downloaded gpay apk as it is not available in my country and I could add successfully credit cards just the contactless payment is not working
[Magisk] xdaillum:
Just wanted to add a data point for this. This solution worked for me (as I shared here) up until today.

Interesting thing is, I attempted 2x transactions today. One at about 2pm GMT+8. That went through fine (as it has for the past month). The second attempted transaction was at 10pm GMT+8. I got the dreaded "You can no longer use Google Pay on this phone" message for the first time since this fix worked for me.

Time to hunt for a new solution.
[Magisk] Fry-kun:
So some time ago I've added the SQLite triggers to reset attestation and set DB to read-only to add cards. Then I set DB back to read-write and was able to pay once. The next time I tried to pay (same day?), it didn't work.

Do I need to keep the DB read-only from now on? Seems like it shouldn't be necessary with triggers...
[Magisk] dardack:
In my experience yes must be kept read only to regularly and reliably work.

---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------

Since I'm bootloader unlocked I update manually with fastboot. Do I have to rerun the SQL and read only after install?
[Magisk] heynando:
Holy bananas. I had no idea the game with Google pay was so rough this days. This is some nasty configuring to get it working temporarily. Up until last week I was using it daily but the cards were already added. Last week bought a new phone and I thought my Magisk was the problem but it's actually Google Pay that's the real villain. I can't add any cards to my new phone, nevermind paying with them.

It's always a bummer when we see Big Corp win over people. They always get to win.
[Magisk] sliding_billy:
I upgraded a PIxel 3 and Pixel 3 XL on Monday. I checked the attestation values to ensure they were all still set to 0 and the reran the chmod 440 dg.db command in terminal to be safe. I paid this morning with the P3 (and will do the same with the 3 XL tomorrow probably) and it worked fine.
[Magisk] CSX321:
My experience was the same as [MENTION=4609886]sliding_billy[/MENTION]. I didn't need to do anything after flashing the update. The db was unchanged and still read-only.
[Magisk] dardack:
Thanks guys. Appreciate the info.
[Magisk] atmfrank:
(semi)Newb here. I have a massive headache from searching the answer to the $M question. Is there a possibility to have G pay work on a rooted phone, with Magisk whatever version installed?

You see, I am trying to decide if I should put my life on hold and go through with converting (frankensteining) an AT&T locked LG V30 to US998 while retaining most of the cool advanced Android features I have come to enjoy over the years. G Pay is one of them. I have done a fair of amount of rooting and customer rom installations on the old HTC platform in the past. So I am ready to go...but I need to know if should throw my H931 out or jump back into the fray again. Thx,

Can some kind soul here provide a quick summary where things stand?
[Magisk] edgeglider:
Were you able to fix your problem? Currently facing it right now and I'm stumped
[Magisk] andrewwdai:
Is the problem with Chase credit card? Yes, I have the same problem, but I dont care coz I use other cards.
[Magisk] BostonDan:
I found a solution for everybody, currently outlined on p132 or 133.

I also posted the fix to it's own thread.

See

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

If this doesn't work, I ultimately had to reset my phone to factory (prior to my fix for Google pay), and reload everything. This cleared this particular error for me. I did not look for other attestation values that may need to be reset in the databases.

Good luck.

Cheers,

B.D.
[Magisk] andreacos92:
Same here. OnePlus 5 running latest OOS beta, with latest bluspark kernel and Magisk 19.3.

Since a couple of days Google Pay doesn't work at all. I can remove and re-add cards etc, but when I put the phone on the POS nothing happens, no errors or other things.

Google Pay is the latest v 2.90, updated yesterday but I have this problem since before.

Google Play Services is v 17.4.55 and it was updated some days ago, so it could be the issue.

Does anyone have any ideas? I already tried the SQL/ReadOnly method.
[Magisk] andreacos92:
I downgraded Google Play Services to version 17.1.22 and temporarily disabled Play Store app (otherwise it was keeping to autoupdate to 17.4.22 immediately), cleared data and cache of Play Services and Google Pay, reactivated my cards for contactless payments and now it works.

So, the problem is the new version of Google Play Services :confused: Can it be related to root/Magisk/ etc?

Is there any other way to disable Play Services autoupdate, a part form disable Play Store?
[Magisk] warrencoakley:
I've done the same but went back to 16.9 I disable Google Play and enable it time to time to.update apps then disable it again. Still on 16.9 now over 5 weeks and GPay still working with this method.
[Magisk] andreacos92:
I tried, but as soon as I enabled Play Store, it updates Play Services to 17.4.22 automatically :(
[Magisk] warrencoakley:
Strange. I also use the disable service app too. But it's working flawlessly for me.
[Magisk] andreacos92:
Which service did you disable?
[Magisk] Hastaloego:
yeah it does, but from the latest posts im not the only one with that problem
[Magisk] andreacos92:
I've tried different workarounds, but nothing worked. The only way to make it works again is to downgrade GSM to 17.1.22.

It's like 17.4.55 doesn't use NFC.
[Magisk] Senliast:
Guys, if someone of you still cannot use G Pay, you can try my Automate flows. I wrote them and using for already a month and have no problems with payments.

https://llamalab.com/automate/community/flows/29931

https://llamalab.com/automate/community/flows/29930
[Magisk] FruitSidewalk59:
half working

Just tried this method and it works!

But still cannot complete a transaction with Google Pay
[Magisk] andreacos92:
What was you problem with payments before using this method?
[Magisk] FruitSidewalk59:
Since I use a custom rom on Pixel 2 Xl, I could not add card for in-store payment with NFC as it gave me error saying " Google Pay can’t be used on this device....This device seems to be rooted or has unlocked bootloader."

Hiding Magisk did not help as confirmed by many on this thread.

The Automate flow fixed it for me and I was able to add the card back into Google Pay without any issues popping up.
[Magisk] andreacos92:
Ok, so maybe you would have fixed it also with the method here https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950 , that it's the same of Automate Flow.

I and a few other guys here have the problem that we can add cards without problems, but nothing happens when we try to pay, and these methods didn't work for us. :(
[Magisk] FruitSidewalk59:
You are correct. I just came back from Walmart and I could not get Google Pay to work correctly and it kept vibrating the phone and cancelling the transaction. :(
[Magisk] upperbladez:
I can't believe this still isn't working. It's a real shame.
[Magisk] AndersonLikau:
I just confirmed my Google pay and it worked at seven eleven. I'm using pixel 2 xl with latest updates for all apps. I didn't have to disable any apps, although every single oogle related apps/system is hidden in magisk(not sure if that would make it different from others). Also running havoc os and sultan kernel, everything newest updates.

I used sqlite by super and terminal by jack. Then I manually changed the value of all attest related things and typed commands manually on the terminal. I have to call my bank to verify my card but I was able to connect my PayPal which had my card linked to it and walah!
[Magisk] andreacos92:
Well, at least your phone keep vibrating so you know it tries to pay but there is an error, probably related to root/magisk.

I, [MENTION=6031703]Hastaloego[/MENTION] , [MENTION=6283797]FloFloFlow[/MENTION] can add cards but nothing happens when we put the phone on the POS, no errors, no vibration, nothing. Really frustrating.
[Magisk] Tr4sHCr4fT:
Magisk 19.0 is now detected, 19.3 still working.
[Magisk] CSX321:
Walmart or Walgreens? I didn't think Walmart supported anything but Walmart Pay?
[Magisk] joeyddr:
yeah, where I live walmart disables it and only allows walmart pay.
[Magisk] LLStarks:
You guys can do more reliable testing at your bank if they have NFC-enabled doors or ATMs. Debit card must be stored as the primary. Not sure who aside from Chase is doing this in a widespread manner.
[Magisk] upperbladez:
It's working for you? It's not working for me.
[Magisk] FruitSidewalk59:
One of the two walmarts near me allows to use NFC. I also tried at Price Chopper where I used NFC 4 months ago on the same rom, and it did not work this time.
[Magisk] CSX321:
Interesting. I hope Walmart starts accepting it everywhere eventually. I was reading up on contactless payment stuff this morning, and I found a story that said some places which technically accept it have also made agreements to only accept it if it's tied to a VISA. Mine currently isn't, which explains why I've sometimes gotten an error, "You can't use this card for payments here" or something like that.
[Magisk] GryphonBR:
Well, just for a slightly merrier update: using the fix I posted a while ago just the one time, currently on GPS 17.4.55 and GPay 2.90.250604638 and still able to pay with my cards. Haven't tried adding any cards lately, but I'd guess paying trumps adding cards, eh? BTW my GPS was auto updated in the background (I was originally on 17.4.22 I think, but definitely not on 17.4.55) without any conflicts or issues either.
[Magisk] Fry-kun:
I kept getting errors with Chase card, but tried Discover the other day and it went through just fine.

Not sure what that's about
[Magisk] moebius83:
jumping in just to add: this specific issue has nothing to do with root/magisk, my OnePlus 5 is not and has never been rooted, but since google play services were updated to 17.4.55 (automatically) I cannot use Google Pay anymore, nothing happens when I put my phone close to the contactless receiver. Downgrading to 17.1.94 fixes the issue for me, however Google Play Services update automatically after a while. I guess it's a GPS bug introduced in the latest version, I wonder if it's just OnePlus affected by it.
[Magisk] andreacos92:
This is really an useful information.

That means Google messed up something in latest Google Play Services with our device. There are other two users with the same problem with a Xiaomi Mi Mix 2, so it seems there are a few devices affected.

Maybe we can report that to Google, it's not accettable, and maybe they will fix it in the next release.

I can confirm that there isn't an accettable way to block GSM from updating automatically after a while, I tried almost anything but nothing worked.
[Magisk] zencooler:
Yes, it seems latest GMS has some bug on some devices.

In terms of stopping GMS to be auto updated there are two 100% working solutions (I wrote about this few times):

1. Freeze Google Play Store (e. g. via Titanum Backup option)

2. Change the permissions to read only for folder /data/data/com.android.providers.downloads/cache (or just remove it and create empty file with the same name "cache" to block system of recreating a folder). Aware this will stop any others updates you could do via Play Store.
[Magisk] moebius83:
I'm glad this helps, I spent 3 days trying to understand why suddenly I couldn't pay with my phone, performing a factory reset fixed the issue, but then after an apparent "random" reason, it just stopped working again.

The one thing I found very hard was debugging the issue, it just wasn't viable for me to go somewhere and try to pay every time I wanted to test if it was working, so I found a way to test Google Pay from home, I'm reporting it here as it could be useful:

grab another phone with NFC

install on that phone a Credit Card NFC Reader (I used https://play.google.com/store/apps/details?id=com.github.devnied.emvnfccard)

open the Credit Card NFC Reader app and tap your Google Pay phone on the back of the second phone, this should trigger the Google Pay on your phone as the app tries to read the "google pay" credit card

of course you won't be able to see if the payment goes through, but you should be able to see at least if google pay starts correctly on your phone, in my case, it wasn't until I downgraded GPS.
[Magisk] andreacos92:
I tried both solutions:

1. It seems to work (despite once GMS updated anyway with Play Store freezed), but it's not the most convenient for me. I want apps update, or I want to see what apps have an available update at least...

2. .... so this second solution is acceptable at the moment for me. I sent a PM to you a few days ago about this. Anyway, even with a cache empty file replacing the folder, GMS updated. The file was still there, Play Store couldn't updtate other apps, but GMS updated.

Google Power.

I ended up keeping latest version of GMS and hoping in a fix.

---------- Post added at 09:42 AM ---------- Previous post was at 09:24 AM ----------

Interesting, I will try method this with my old Samsung s4.

Until now, because I'm studying in library/study room, I've tried at the POS of automatic vending machines (for coffee/snack/ etc), only if there are not many people around, because it failed every time with latest GSM/GPS.

Does anyone know the correct section to report a bug to Google?
[Magisk] andreacos92:
[MENTION=3346258]moebius83[/MENTION] [MENTION=1072347]zencooler[/MENTION] [MENTION=1269285]ssceddie[/MENTION] [MENTION=6283797]FloFloFlow[/MENTION] [MENTION=6031703]Hastaloego[/MENTION] [MENTION=3091959]tjengo[/MENTION]

I submitted an issue at Google Issue Tracker, here

https://issuetracker.google.com/issues/135132389

It would be nice if you can click on the Star next to the title, according to Google it can be an important signal for prioritization.

:)
[Magisk] zencooler:
Done. It's starred by me. Good luck!
[Magisk] moebius83:
thanks for doing that! I starred it and added a comment!
[Magisk] alessandro_xda:
starred
[Magisk] R-iel:
This still works for me on S9+ on SoLdieR9312 19.0 ROM :) After a couple on minutes Google Play Services gets updated, but even after that I can pay with phone.
[Magisk] Hastaloego:
done
[Magisk] moebius83:
we probably hijacked this thread enough, since this specific issue has nothing to do with Magisk or root, let's move the discussion to this other thread I opened: https://xdaforums.com/oneplus-5/help/google-pay-stops-oneplus-5-rooted-device-t3938976

thanks and sorry for the hijacking :)
[Magisk] warrencoakley:
Currently the only way I found to block it from updating is by disabling Google Play
[Magisk] nebula9:
On CrDroid on an LG V30, Google Pay just works. I checked the attest state and it'd actually 10 (!), Yet I have had no issues whatsoever without setting anything up. How might this have happened? Play services is current ...
[Magisk] mmidders:
Downgrading Google Play services (henceforth GPS)

Hi there

I've been trying to downgrade my GPS version to one where google pay was working (Xiaomi Mix 3, running LOS), but without much success; any ideas?

My method:

1. download legacy GPS from apkmirror etc.

2. airplane mode on

3. backup GPS with Titanium backup

4. uninstall GPS with Ti backup

5. install legacy apk

So far it always fails at step 5; apk not installed. Is there some dependency on other apps/version number etc.?

Alternatively, I was wondering if there is any way to hack opengapps with a legacy version of GPS...

Slàinte

midders
[Magisk] zencooler:
If you have previous backup of GMS done via Titanum Backup is the easiest way to restore it from backup. If not then try to uninstall updates via normal Android apps settings. It should restore the original version of GMS delivered with ROM. Then you can update to any version downloaded from e. g. APK Mirror.
[Magisk] mmidders:
LOS doesn't include GPS, it came from opengapps so the current version is the lowest possible. Am looking into legacy versions of opengapps...

Also, trying to restore GPS from Ti backup didn't seem to work, had to reinstall opengapps from TWRP.
[Magisk] andreacos92:
You have to uninstall the GPS updates, restoring the default version (if there is any).

You have to go in Device Administrators, and disable Google Pay and Find My Device, then you should be able to uninstall Play Services and reinstall from the apk. Clear data and cache and reboot.

Anyway, what's your issue with the latest GPS version/GPay? Is it something like this https://issuetracker.google.com/issues/135132389 ?
[Magisk] McNamara_br:
i did that and works perfectly! thank u so much :)

Xiaomi Mi8 - rom xiaomi.eu 9.3.21

Magisk 19.3
[Magisk] blisside:
I got GPay working on magisk on a pixel 2 XL by simply installating the SafetyPatch module from the Magisk store
[Magisk] Frosthaxx:
Google pay is only usually affected if safetynet doesn't pass. Safety patch usually works well in conquering this dilemma
[Magisk] BostonDan:
This is not true. That use to be the case,

The reason I first looked into finding a solution was because my safetynet would pass, but Google pay would still not permit adding cards or paying.

Cheers,

B.D.
[Magisk] Frosthaxx:
Hmm odd. Still the case for me. Then again I guess it affects devices different