yashsingh1/xdaforums huggingface dataset:
[Magisk] blu.italia:
You have to use SQLite3 Universal Binaries and GPay SQLite Fix:

https://xdaforums.com/showpost.php?p=79643248&postcount=176
[Magisk] glennza:
Thanks, that might have fixed it. I am seeing Device Certified in Play Store now; wasn't getting it before. Won't know for sure until I go to buy something but it looks promising!
[Magisk] pndwal:
Playstore is certified if ctsProfile passes and you clear G Play Services cache. I think SQLite Fix module clears cache on installation, which likely accounts for fixed certification.

Still, this fix may well get it going for you. Please let us know... PW
[Magisk] SeverusSnape:
GPay here also is not working.

I´m on MIUI 12.3 Xiaomi.eu 20.11.18 on my MI 9Tpro.

Tried Magisk v21.1 & 20.4

SQLiteFix 2.2 is also installed.

SafetyNet is pass.

I get the attached Message in GPay

How can i get GPay back to work ?

Regards
[Magisk] 73sydney:
Cant see the pics/message this end
[Magisk] warrencoakley:
Did you get it working in the end? And if so what did you do?
[Magisk] RealCaracas:
Yes I did delete the data of Google Play Services and Google Pay apps...
[Magisk] warrencoakley:
What magisk modules do you have installed?
[Magisk] OGIGA:
Earlier in the month, Google Pay quit working and Safetynet started failing. Then, Safetynet was passing sometimes, but not consistently. Now, it passes pretty consistently, but sometimes failing if I have VPN (AdGuard) running.

Now, Google throws up another wrench: a whole new GPay app. Yes, my app drawer has Google Pay (the one that has been around) and GPay (new one). I tried adding GPay to Magisk Hide and EdXposed blacklist like the Google Pay method, but GPay won't pass Safetynet while Google Pay still passes. Still doesn't pass if I turn off EdXposed from Magisk. Guess I'll just be patient until someone shows the way. Using OnePlus 7T btw.
[Magisk] loadie:
Downloaded, signed in and added cards on the NEW gpay app.also used it for contactless pay, and it worked. Not hidden in magisk hide, I use and did not change the db.dg 0 all attest that I had been using for google pay .

Anyone else tried this app yet?

Didn't see any threads for the new one so posted here.
[Magisk] Masonjar13:
Wanted to throw my experience in here, since I came looking, but stumbled upon my own solution.

I've never used Google Pay before, and I just today installed the new GPay app. I've been running Magisk for a while, on OP7P, 20.4 currently. It was throwing me a device not allowed error, assumed it was Magisk of course. But I had an OTA (10.3.7) and decided to install that finally. After installing, no error. My assumption is that it was either the GSM package update (2020.08) or security patch (2020.11) that GPay required. Or it just noticed I had an OTA and wanted me to install it. Also, not hiding Magisk in any way, with stock OOS.

Paraphrase: if you can't get the new GPay working, try updating your ROM.
[Magisk] nunytes:
It seems to be finally working with latest riru and EdXposed with latest GSM and apps!
[Magisk] rahmanjunior:
I also have edxposed

How did you fix it? Mine doesn't work
[Magisk] nunytes:
You need latest beta (currently v0.5.0.6_4586) and latest Riru core (currently v23.0) and a certified device at PlayStore.

Install those files, clear GServices and PlayStore data and flash SQL fix in Magisk manager (better the canary version). That should be enough.

Currently I'm with Magisk stable 20.4 and the latest GPay app is working fine. I can even update the app in store.

I hope I've helped 😃

Edit: I've added some screenshots of my setup to help you. I'm on latest MIUI global stable with October security patch. Don't forget to first flash Riru core, reboot, and then flash the EdXposed!
[Magisk] cmstlist:
Edit: accidentally posted twice
[Magisk] cmstlist:
I just lost SafetyNet for a little while because of the new ctsProfile changes. I got it back but Google Pay is still upset.

Now here's the wrench. Last time this happened I fixed it by resetting Google Services among other things. Little did I know, that also deleted the tracing data used by my local COVID-19 exposure notification app. Any idea how to get Pay working again without a full Google reset that would delete the COVID data?
[Magisk] fastracer:
yeah having the same issue, don't want to delete GP services...have to reinstall my Wear OS etc...any way around this as my card is added but it says contactless payments are not working
[Magisk] a_khusairi:
anyone who has a problem with the safetynet in January, can try this https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Magisk] Shished:
This only works for android 11 ROMs, will cause bootloop when installed on android 10 ROM.
[Magisk] a_khusairi:
use the latest, work on android 10 https://github.com/kdrag0n/safetynet-fix/releases
[Magisk] Namelesswonder:
Install the new fix from kdrag0n and it should begin working fine.

If you can remove and add your card just fine then it's working. For whatever reason the Google Pay app won't stop showing the "not setup" warning but tap to pay works just fine for me. If you're still getting the pop-up or "device is modified" then try deleting /data/data/com.google.android.gms/databases/dg.db, then clearing the data and cache for Google Pay, and rebooting. If Google Pay blocks you from adding your card then you aren't passing SafetyNet for another reason.
[Magisk] cmstlist:
Huh, funny thing happened. Pay has now flipped back to "You're all set to pay with your phone" all on its own. I have not done anything to try and fix it since the last time I was playing with it yesterday.

I did at some point try all of what you suggested. So all I can conclude is, there is some sort of regular re-check that happens. Therefore if you are passing SafetyNet and have done all the above steps but Pay still won't work, sleep on it and check again.
[Magisk] angiotell:
Hi. I'm on Ambasadii ROM 3.0 Android 11. All is perfect but Google Pay doesn't work. What can I do? Please
[Magisk] angiotell:
Could you send me new file from kdrag0n please?
[Magisk] Namelesswonder:
It was linked 4 posts ago in the thread...
[Magisk] angiotell:
Installed but GPay doesn'w work... Any solution please?
[Magisk] pndwal:
Think you may not have cleared Google Play Services cache initially. This generally will reset Play Protect (In Playstore Settings) to 'Device is certified' immediately, after which G Pay normally works fine from the get-go (at least if it's added to Magisk Manager Hide list and then its data is cleared).

If you forgot to clear Play Services cache, here is what occurs:

G Pay is tripped again, and you have to wait till Play Services refreshes SafetyNet attestation (including ctsProfile) and Play Protect certification before any call from G Pay to the SafetyNet attestation API In Play Services can succeed. Next, when the SafetyNet attestation API receives a call from G Pay, this service will evaluate the runtime environment and request a signed attestation of the assessment results from Google's servers. Google's servers then send the signed attestation to the SafetyNet Attestation service on the device which then returns this signed attestation to your G Pay App. G Pay then forwards the signed attestation to its own dedicated 'client' server which validates the response and communicates its findings to your G Pay App.

https://developer.android.com/training/safetynet/attestation

Clearly, all this can take some time.

The reverse is also true; G Pay can work for some days with failed ctsProfile attestation.

This does have some benefits however. For example, SafetyNet failures that are brief (eg caused by instability in EdXposed mod(s), experiments with SafetyNet and various mod configurations, toggling MagiskHide on and off, etc etc) will seldom cause G Pay or other Apps that use SafetyNet API to fail or require resetting.

Anyhow, it is useful to know that your G Pay reverted spontaneously, and that you didn't have to wait to long. PW
[Magisk] cmstlist:
After applying the Magisk fix, I did clear Play Services cache, but not Play Services data, because doing so would have deleted COVID-19 exposure notification tracing data. I tried a few things including several wipes of Pay, wiping specific files from the Play Services folder, no help. I left it that way, not working yet, because I didn't know what to try next. The next day it spontaneously resolved.
[Magisk] pndwal:
Ah good... It wasn't clear that you tried clearing GPS cache, only that you wanted to avoid 'resetting' Play Services (which, incidentally, is not normally needed). 🙁

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-84281361

I did say clearing cache 'generally resets Play Protect immediately', but in some cases no Play Protect certification state shows at all for a period despite having ctsProfile pass, before 'device is certified' shows up again. This may be due to internet issues and other factors.

A key to getting immediate G Pay success is therefore to check in Playstore that device certification is restored BEFORE initialising G Pay, and limited network access / speed can prolong this process.

Another factor is that G Pay may detect root even after this in the interim between installing and selecting G Pay in Magisk Manager Hide list, so if it is ever reinstalled it's data should also be cleared after activating it in Hide list (as I indicated), especially if it has been run before toggling this setting. This applies to other apps using SafetyNet API also of course.

Also, clearing App's data may be required after any event where MagiskHide fails or is disabled and is restored. Eg. if it is ever toggled off, root is lost, an update deactivates it requiring manual reset, or SafetyNet has failed for some reason.

Hope this helps some in future. PW
[Magisk] Chucknorris1975:
I've tried this and gpay still fails with "this device is rooted" etc etc. Running LOS 17.1 and Magisk 21.4. Also, I pass safteynet.
[Magisk] JkdJedi:
This was a huge help and so sick I can still use G Pay with a rooted phone.. After clearing Cache and Data of Google Services I was seamlessly able to use G Pay without any hiccups.... AWESOME!
[Magisk] marcash:
due to the problem with magisk22 and oneplus8 pro's new OTA update 11044. -> root not working.

now i have also that GPay detect rooted phone even when magisk is not installed.

how to get rid off this rest of root things. all uninstall methods are if magisk is installed
[Magisk] tiga05:
@marcash

If Google pay detected root at your at your smartphone you have two possibilities in my opinion:

- reinstall your smartphone (and setup Google pay in magisk hide at first before you start it for the very first time)

- search in this forum for the sql fix or use this link:

Working: Magisk with Google Pay as of gms 17.1.22 on Pie

Ok. I tried this and it worked on gms 17.1.22, allowing one to add cards and pay in store. Warning YMMV, but this is the process I did to get this working. One caveat is that I suspect users will have to reverse some step if gms is updated and...

xdaforums.com

Someone from this thread also created a magisk module for this.

GitHub - stylemessiah/GPay-SQLite-Fix: A magisk module that ONCE allowed Google Pay to work on rooted phones

A magisk module that ONCE allowed Google Pay to work on rooted phones - GitHub - stylemessiah/GPay-SQLite-Fix: A magisk module that ONCE allowed Google Pay to work on rooted phones

github.com

The thing is: Once, Google pay detected your rooted smartphone, it will set some note about this in some sqlite file which is not deleted if you uninstall Google pay. Therefore you have to edit it by yourself and reset this again or use this module.

Resetting this values not always work under all circumstances. But the first thing will work if magisk is working correctly and Google did not activate the hardware key attestation at your smartphone, yet ( https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/amp/ )

Edit:

Maybe I did misunderstand your intention:

If your smartphone does not have root anymore and your Google pay says its rooted, then this is maybe because you still have a unlocked bootloader. You have to relock the bootloader (which deletes all your data, so Google for that and prepare everything before you do this!!) for that.
[Magisk] zelitrex36:
As said on the Magisk thread, I still a problem on Gpay after the magisk Setup.

In fact it's exactly that :

https://xdaforums.com/t/discussion-...cussion-thread.3906703/page-108#post-83776951

Only difference is that's in french "non configuré" lol

But unlike RealCaracas... wiping datas didn't solve my problem.

My setups in Magisk are :

I already wipe :

google play service AR (can't find the non AR one on the applications tab), Gpay, Playstore.

I'll gladly try any idea you could have. It's so frustrating to pass all the safety checks and still can use Gpay lol

Regards.
[Magisk] wrymer:
Hi!

I'm new here. I'm just updated my Xperia XA2 Ultra with some problems to Lineage 17.1, but as usual GPay don't work.

I have Magisk installed (and working with dedicated modules).

What i have done:

installed TWRP edited database and set chmod 440

Specs as follows:

XPERIA XA2 Ultra

Magisk v22.0 with Magiskmanager

Magisk hide: Google Pay, Google Play Store

Magisk Manager package hidden/repackaged

Busybox for Android NDK

GPaySQLIte Fix

SQLite for ARM

If i run GPay i got messages to configure sms permission to GPay.

Anyone can Help?
[Magisk] pndwal:
Problem is 'cards not configured'?

Please confirm you still have FULL SafetyNet pass and playprotect certification, AND that you DID actually clear Google Pay DATA

AFTER

, toggling on Google Pay in MagiskHide list and rebooting.

Google Play Services will be visible if you select 'Show all Apps' (shows system services) in top right menu. There will probably be two (dual) due to USNF Magisk module, but you shouldn't need to clear cache(s) unless having issues with SafetyNet / certification. PW
[Magisk] 73sydney:
In other news ill be soon back to a bank that uses Google Pay (& Samsung Pay - i have had an Active 2 watch a little while now - fun getting that to work on a rooted phone)
[Magisk] zelitrex36:
Yeah I can confirm that I did everything you said and yes I could pass SafetyNet Pass and playprotect certification. Yes I wiped data AFTER toggling all required apps in MagiskHide (I mean my Teams problem you've seen on the other post too, not all my apps^^).

And yes that didn't work.

BUT

thanks to you I finally found that Google Play Service (not the purple AR one) and wiped it with all the others (playstore, Gpay, Teams, In-Tune all that for the 15th time) and after rebooting, IT WOOOOOOOOOOOOOOORKS !!!!!!!!

2 things from that experience :

1) Even if Magisk was ok with safetynet check, playstore got certified and Gpay let me setup a credit card, I still needed to wipe GPS data

2) You're a Hero !! (At least a very kind person to answer everyone's questions). Thank you so much.

I bought this phone on december and read Magisk wasn't working anymore so I tried a lot of things until I found a module on xiaomi.eu forum that could work. And without you, I would have gave up. You were right about not giving up at the end.
[Magisk] wrymer:
Hi everyone!

So i'm tired trying GPay works, so i wish to back to stack ROM. Where i should search infos how i should back to stock ROM?

I used Google, but that what i found there is quite useless.

Greetings!
[Magisk] Lord Sithek:
You should find it on your device's respecive thread. Whatever your device is :sneaky: In your case Xperia XA2 Ultra as I just realized o_O:ROFLMAO:
[Magisk] pndwal:
Interesting you needed this despite SafetyNet passing and device being certified.

Just curious, did you try clearing Google Play Services cache only before clearing data? PW
[Magisk] HippoMan:
I decided to try Google Pay, which I hadn't used until now, and I am having an issue with Google Pay seemingly forgetting about payment methods.

I am successfully running Magisk 22.0 to root my OnePlus 7 Pro (GM-1917) with OOS 10.3.8 (an Android 10 release). Google Pay is marked as "hidden", and SafetyNet passes.

I can invoke Google Pay with no problems, and it is not telling me that there is anything about my device which would prevent Google Pay from functioning.

I can even register PayPal and a credit card as Google Pay payment methods, and they initially show up as being properly set up and ready to use. Both are valid accounts that I am continuing to be able to make payments with, outside of Google Pay. However, this is where the problem occurs. Within 10 or 15 minutes after successfully registering these payment methods in Google Pay (with bank verification, 2FA verification, etc.), those payment methods disappear from Google Pay with no notifications and no error messages. I then have to re-register these payment methods before they once again are available for a few minutes.

I have repeated this scenario several times, and it always results in the initially accepted payment methods disappearing after a little while from Google Pay.

I don't see anything related to this in the logs, and I am getting no alerts or messages from the bank nor from PayPal concerning these payment methods somehow being inappropriate.

Thank you for any insights.
[Magisk] pndwal:
Could try clearing DATA for Google Pay, Google PlayStore, AND Google Play Services and rebooting before trying again... Apparently this just now fixed similar problem ('Cards not configured') for this user:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-84621725 PW

PS. You made me a bit giddy moving this issue around like that!... Hippos aren't usually that quick.
[Magisk] HippoMan:
I can sometimes be a turbo-charged hippo.

I saw that discussion earlier and tried it, and it didn't solve my problem. But now that you mentioned it here, I decided to be a thorough turbo-charged hippo and try again ...

I cleared data for Google Pay, Google PlayStore, and Google Play Services.

I also made sure that everything even remotely related to Google is listed in Magisk Hide.

I then rebooted.

I then set up a payment method for PayPal.

That payment method remained for a few minutes of starting and stopping Google Pay (including stopping via "force kill").

But then, I rebooted, and when I went back to Google Pay, the payment method had disappeared.

Something still seems to be causing Google Pay to forget its payment methods.
[Magisk] 73sydney:
Okay, so the magisk module currently only clears data/cache for Google Pay (with a warning about loyalty cards).

I know for a while now ive had notes in the steps in the OP to clear data for Play Store and Play Services if there was an issue, but given the amount of times we've seen it crop up, and youve specifically done my support for me :) and advised people to do it (putting completely aside the fact its written in the instructions in my OP), should i think about just adding the data clearing for those packages to the script - i think i toyed with putting the device into airplane mode then clearing those packages in the script, then at script end asking people to reboot (and manually toggle air plane off) but it seemed like a lot to do, for everyone. Is it worth reconsidering? Do the numbers of folks having to clear data warrant it? Thoughts?

Also, found in my travels a sweeeeeeet Windows .exe for doing payload.bin dumps (handy for folks who want boot.img files to use for magisk install) ...added to my sig :)
[Magisk] HippoMan:
As for me, I already followed that clearing-the-data procedure before I even reported this problem, and then I did it again today, just to make sure, when @pndwal mentioned it to me, above.

Unfortunately, this data clearing didn't solve my problem any of the times I did it. Something else is causing the Google Pay payment methods to be forgotten for me. It happens after a certain amount of time passes, or after a reboot.

Maybe this isn't related to Magisk. I really don't know.
[Magisk] 73sydney:
I take it youre using my module? if so, have a look for /cache/payfixfirstrun.log

You arent running any funky conflicting modules or edXposed/Riru as mentioned in the OP under Preinstallation checks?

Not using any automatic cache clearing/speedup/booster apps?
[Magisk] HippoMan:
I'm using the GPay.SQLite.Fix.v2.3.zip Magisk module. I have installed it and rebooted. However, the /cache directory is empty.

In addition, I manually performed the dg.db changes.

No conflicting modules. Also, the "tiny.cc/b2b1kz" link that you mention is currently a dead link:

Unable to determine IP address from host name "tiny.cc"

However, I believe that the following link gets me to the same post:

https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-79643248

Under Pre-Installation Checks on that page, EdXposed is specified. However, I'm using LSPosed, and this doesn't allow me to do the Xposed blacklisting/whitelisting.

However, SafetyNet has been consistently passing for me, even before I did anything involving GPay. My GPay problem is not related to SafetyNet.

I have always been able to run GPay, and I have always been able to add cards and payment methods such as PayPal. I have never had any problem with this. However, after a period of time, these cards and payment methods disappear.

I believe that this means that all of the Xposed stuff, Magisk stuff, sqlite DB stuff, and cache clearing are working properly ... but that something external to all of this is causing one or more of those changes to be altered or reversed over time.

I know that nothing is changing w/r/t any Xposed or Magisk modules. Therefore, I'm guessing that whatever is causing my problem is either messing with the DB or with the cache (or both).

Actually, this might be the culprit. I am running xXx_NoLimits, and I believe it might do things to the cache as part of its speedup/debloating functionality.

I will investigate further and report back ... probably tomorrow, because it's past my bedtime.

Thank you for all your help!
[Magisk] 73sydney:
the fact you have no log file from my module under /cache is a sign :) :)

also the tiny.cc link works fine for me, you must have truncated it somehow?

@pndwal might get a lil upset if i fixed this one, usually he does all the support for my module :) :)

p.s. sleep is for the weak :)
[Magisk] HippoMan:
PS: Column "c" of dg.db is not being changed. It still contains the zeros I put there in the rows where column "a" contains the string "attest". However, its permissions have been changed (not by me!) back to 660, even though I originally set them to 440.

But given that the column "c" values have not changed, it's clear nothing is altering the contents of dg.db. Therefore, it appears that I should be focusing solely on trying to determine which software could be altering the cache.

OK. It's bedtime now.
[Magisk] HippoMan:
In that case, I am proud to be weak! :)

As for /cache being empty: even though your module didn't create the log file there and therefore maybe didn't run properly on my device, I still made what I think are all the same changes manually.

In any case, I believe that I made sufficient changes, because as I mentioned, SafetyNet passes, GPay works fine for me, and I can add cards and add payment methods such as PayPal.

The only problem is that some of the changes seem to get undone as time goes on so that the cards and payment methods eventually disappear, and that is what I will be investigating ...

... after I get my sleep :)

PS: I simply clicked on that tiny.cc link in my standard linux Firefox browser.

PPS: The tiny.cc link works now. My problem must have been due to a temporary network error getting to the DNS servers that tiny.cc uses. I now notice that dig tiny.cc sometimes times out and sometimes runs properly.