yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Thanks for detailing how you achieved successful setup, especially MagiskHideProps alternative to SafetyPatch module. Its interesting that 9/P 'fingerprint' works with 10/Q ROM.

I hadn't tried MagiskHideProps module as simply flashing SafetyPatch mod did the trick in my 'test run' without the configuration MagiskHideProps requires. Does MagiskHideProps have advantages you know of?

Like you, I'm still waiting to test NFC payment for real.

I got past the 'may be rooted / altered' warning, and GPay checked and validated account details with my bank, etc on a test device, but I can't actually pay with it as it lacks NFC. (I'm awaiting a new Redmi Note 8T, but Toll Global freight have gone and lost it for the last 10 days!...) Test run done on Mi Pad 4 running LOS 17 beta (Android 10/Q). PW
[Magisk] rishipkothari:
[MENTION=7550078]pndwal[/MENTION] my pleasure!

- I edited my post, installed Google pay from the play store, not a modified or old version of any kind.

- MagiskHide props just edits the build.prop in a scripted way, it seems. I'm not familiar with the safetynet module, so I can't comment on it

- I actually even tried to use an sqlite editor to edit the dg.db manually, but that didn't seem to work. Not sure what the difference was between manual editing and the Magisk module, but it was successful this way for me

Will post back when I test it out in a store!
[Magisk] pndwal:
Yes, thanks, edited mine also - just realised I misunderstood (- you meant GPay SQLite Fix module of course, not a systemless GPay app module as I had assumed.)

Interesting that you seem to have Android 10/Q with 9/P fingerprint applied to MagiskHideProps working.

Using either SafetyPatch or MagiskHideProps module resolves the following issue for many devices from Chinese OEMs like Xiaomi: Playstore, Settings, about, Play Protect certification says 'Device is NOT certified'. (These OEMs have neglected to have devices certified by Google to save a little money and time, and strangely this applies to devices sold with Global ROMs, not just their China ROM counterparts) After flashing SafetyPatch module, Play Protect certification says 'Device IS certified'.

I'm still waiting to see if my Redmi Note 8T with NFC comes certified, as I am incredulous that Xiaomi would market a Global version with NFC not supporting GPay, but it won't surprise me considering their policy to date. Either way we can fix this with root and SafetyPatch module or MagiskHideProps. (I know this won't matter much with likes of Pixel 3). Regards, PW
[Magisk] rishipkothari:
Cannot comment on this, have only tried this on my current pixel 3. Maybe someone else can chime in?
[Magisk] jcmm11:
As long as you're passing Safety Net you can get "Play Store certified". If it's showing as uncertified simply go to Settings/Apps & Notifications/Google Play Store, stop the app, delete storage

When you restart the app it probably won't show any certification status for a little while and will then show as certified. If it still shows as uncertified then instead of just restarting the app (after again clearing storage) reboot the phone.
[Magisk] pndwal:
Yes, on revisiting this I understand that safetynetcheck is passing as magisk hide, systemless root etc are hiding CTS incompatibility, while modules like SafetyPatch further hide unlocked b/l, feign play protect certification etc. Also, once it fails, play store needs refreshing manually to reflect this changed reported status as you point out. Thanks.

Further reading on a complex subject:

https://customroms.net/faq/safetynet-android/

https://koz.io/inside-safetynet/
[Magisk] Walhalla:
you guys are able to setup your cards for contactless payment in google pay after setting the file permissions to 440? I can not add any of my Master or Visacards. I get an error message everytime. Only PayPal works.
[Magisk] Dunge2:
Thank you for the solution to delete to db.

On another note, the software 'SQLite Editor' used 3gb of wireless data in less than a day? I wonder what it is, isn't this supposed to be a local editor only?
[Magisk] PataniPatano:
Worked like a charm on my Xiaomi Mi Mix 2S, thank you very much for making this method accessible to everyone! :good:
[Magisk] CSX321:
Mine was the opposite. I was able to set up a card for contactless payment that I already had in Pay, but I can't get the PayPal process to complete. After it prompts for me to log in to PP, it just goes back to the "let's get started" screen or whatever.

I'm a bit curious about it myself. I just uninstalled it, because my battery ran down overnight, even though it was on the wireless charger.
[Magisk] sliding_billy:
To be sure, are you talking about SQLite Database Editor (the free app linked in the OP) or SQLite Editor (the $2.49 app from Speed Software)? I used the free one and it is showing 0 B of data used (in settings>apps>SQLite Editor>App data usage) since I installed it on the 13th.
[Magisk] mufftimuff:
Work great on MI9 with all Updates. Btw normal pay Apps are okay now, too. Thanks.
[Magisk] zencooler:
Be carefull as it can change the state that fails the payment even after few days. It's better to edit databese values according to this thread advise.
[Magisk] Walhalla:
[MENTION=1975647]CSX321[/MENTION]

try to start the linking process in the PayPal app. Perhaps that helps.
[Magisk] Bidalos:
You don't need other solution with this solution.

Uninstall Google Pay and install again, unblock Google Play Services, install updates !

Don't forget to Magisk Hide, Google Pay and Google Play services after.

Now apply this solution, only this solution, nothing more!
[Magisk] HamsterHam:
With this method nothing extra needs hiding in Magisk. Literally just the default com.google.android.gms.unstable. I haven't hidden gpay or any extra Google Play Service.

Just do as OP said, nothing more nothing less.
[Magisk] CSX321:
Thanks, good idea! That worked.
[Magisk] Karpfenhai:
Hey guys, nice approach :)

For those who struggle to get sqlite3 running but have Titanium installed, just copy the binary over to /system/xbin, set 755 and you're good to go, no reboot needed, source /data/data/com.keramidas.titaniumbackup/files

Regards.
[Magisk] matssa:
Will the binary change or get removed when updating with the next June patch? Gonna try this and use a Tasker command :)

---------- Post added at 09:20 PM ---------- Previous post was at 09:09 PM ----------

Thanks works like a charm with the sqlite3 of titanium backup. Managed to add 2 cards but didn't test the paiement though.
[Magisk] switchy85:
Can you share your Tasker profile for that? I have Tasker but I suck at it.
[Magisk] martyfender:
On my device under dg.db there is a key called

devicekey

/16.0.81 (040700-{{cl}})/

NextBook

/NX16A8116K:6.0.1/MMB29M/

V4.0.3

:user/

release-keys

It has a value of 10 in the c column. Should this remain the same? I have changed every attest value to 0 and changed the file permissions in the root terminal.

I am on the latest play services beta 17.1.91. Attest values in the database go all the way back for every older version of gms that I had installed in the past.

Thanks
[Magisk] Tr4sHCr4fT:
so that's why my battery wasn't full even after 2h

---------- Post added at 01:05 AM ---------- Previous post was at 12:42 AM ----------

next level: SQL Trigger :D
[Magisk] lssong99:
Here is the description and XML for import to Tasker:

(I use the TitaniumBackup's sqlite3 binary as suggested by @ Karpfenhai, you could edit it if you use other sqlite3)

GPay (326)

A1: Run Shell [ Command:chmod 777 /data/data/com.google.android.gms/databases/dg.db

/data/data/com.keramidas.TitaniumBackup/files/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';"

chmod 444 /data/data/com.google.android.gms/databases/dg.db Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In:%DebugMsg Store Result In: ]
[Magisk] Bidalos:
No, do not change.

Only the lines with "attest"
[Magisk] hammondegs:
Works in Macrodroid as well.

Thanks :good:
[Magisk] Walhalla:
I already suggested this on the last page. You don't need to copy the binary. Just execute it. It's there as long as Titanium Backup is installed.
[Magisk] lucidity1:
I can confirm these steps work on my Pixel 3 running the December 2019 security patch. Thanks!
[Magisk] rishipkothari:
[MENTION=3996588]lucidity1[/MENTION] my pleasure!

[MENTION=7550078]pndwal[/MENTION] my setup works great! Had a chance to use it for payment and no hiccups!
[Magisk] jerem62k:
For my case i needed also to wipe data for google pay app

Paiement is successfuly done after
[Magisk] Didgeridoohan:
For those that are wondering, the only real difference between Safetypatch and MagiskHide Props Config is that with MHPC you'll have to pick what device fingerprint to use for the CTS certification. Safetypatch does it automatically by using a Huawei print. Flash and forget, or pick the print you want... It's of course possible to change the Safetypatch print to one you want by editing the module script files, but if you're going to do that you don't really need the module anyway and can just use a simple boot script instead.

And about Play store certification:

As long as you pass the CTS part of SafetyNet all you need to do to change an "uncertified" status to "certified", is to clear data for the Play store (and possibly reboot).

https://didgeridoohan.com/magisk/Ma...and_other_apps_wont_install_or_doesnt_show_up
[Magisk] ivivaitylin:
Sorry for the slow reply, but I can confirm that SafetyPatch did the job, thanks to you and the two other replies with helpful suggestions.
[Magisk] pndwal:
Thanks for heads-up!

Do you think there is any advantage in using a more closely matched print than Huawei one (on Xiaomi device)? PW

---------- Post added at 09:19 PM ---------- Previous post was at 09:03 PM ----------

Glad you found SafetyPatch.

Please try clicking Thanks button (?) in posts for those who help. (You will be elevating their profile, your handle will appear with thanks, and others can see / find thanked posts.) :) PW
[Magisk] ivivaitylin:
Done! And as a bonus, since applying the SafetyPatch, google Opinion Rewards has started sending me surveys again, so it's a double bonus :D
[Magisk] Ch3vr0n:
Wait, now being rooted with magisk is the reason why I haven't received surveys anymore? I was wondering why I haven't gotten any in months. I'm not very used to modules and I'd rather not use a Huawei fingerprint ok my pixel 3 xl. Would that other module fix the survey's for me? I pass cts and I'm certified for play store according to magisk itself.

Ugh even with mhpc running, banking app still detects root (even with manager renamed). App works, just can't use fingerprint to login
[Magisk] pndwal:
I believe either module will fix it for you (SafetyPatch being simpler to set up).

Please check my steps - post #764 here.

Check in Playstore if certified, this way: go to Playstore, Settings, about, Play Protect certification.

If it says 'Device is NOT certified', this is likely the problem with banking app. So long as you have full Safetynetcheck pass, go to Settings/Apps & Notifications/Google Play Store, stop the app, then delete it's storage and restart. Check certification again.

Also, ensure you set up SQLite binaries and module as described.

Not sure if there are any problems using SafetyPatch w/ Huawei print for Play Protect certification, but you will get closer match with [MENTION=4667597]Didgeridoohan[/MENTION]'s MagiskHide Props Config.

Great resources:

https://didgeridoohan.com/magisk/Ma...and_other_apps_wont_install_or_doesnt_show_up

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

Hope it helps. PW
[Magisk] DevanteWeary:
No. I've been rooted for years and get them fairly often up until they introduced the Google Points program.

Since then many people are not only complaining that they stopped getting surveys, but also that they actually are enforcing the yearly credit expiration.

Some people report losing much money, over $100 in some cases. When I found out about it, I had close to $100 that I was going to lose the very next day. So now we are forced to spend it and not getting any new reward surveys.
[Magisk] Ch3vr0n:
Guess I can get rid of that props and BusyBox module then. No matter what I do, banking app won't let me use fingerprint for login or signing. Works perfectly fine otherwise (with being rooted, through password).
[Magisk] Didgeridoohan:
If you're on stock Pixel you don't need it... The device fingerprint function of that module (and other similar modules) is really only for custom ROMs that don't pass CTS.

Banking apps usually look for other stuff (but now we're getting OT);

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Ch3vr0n:
I tried just about everything I could from that website. Would you mind if I send a dm?
[Magisk] pndwal:
A dm? To whom?
[Magisk] Jakob1379:
Wait what? It finally works for me as well!! I finally figured that xposed was the missing link. It has to be deactivated for gpay to work.. Installed via gpay sqlite fix zip.
[Magisk] db452:
Thanks to [MENTION=9350973]All[/MENTION] of you to make Google Pay working with bootloader unlocked

:svetius:

One question please to step #4: I was able to add my PayPal account to Google Pay, but I was not able to set it for contactless payments. It tells me that it's not possible because my device is modified or rooted.

But after reboot and letting gpay.sh do its thing I'm able to finish the process of contactless payments ability (I get conformation of PayPal that it was added successfully.

Did I Everything right? Should it be that way?

Greetings from Germany,

DB452
[Magisk] pndwal:
Actually need reboot to activate each / any Magisk module. Reboot is specified after SQLite binary purely because this must be activated prior - not on same reboot as GPay SQLite Fix.

Also, may need to wipe data / storage in GPay app before setting up, to reset any device information it has retained. Simply doing this now should ensure all is as it should be even though it appears your final reboot achieved a reset of GPay data.

See my successful steps at post #764 (4th post page 77). PW
[Magisk] beejkitsune:
Can confirm that OP works for me on Pixel 3 XL, Android 10 December 2019 security patch, Magisk 20.3 Canary.
[Magisk] MrPierc:
Hello, i use this tutorial from BostonDan (many thanks) from Septemeber 2019 until yesterday and all worked like a charm!

I use Latest weekly Rom + Magisk 19.4 (working always) + SQLite + Terminal like in #1 post. Everything works fine. I can add my Mastercard Bank card to Google Pay and i can pay in market. But i CANT add meal card (Edenred, mastercard).

I try Factory reset, i try Magisk 20.02 = but Magisk stop working and i must "Format data" in TWRP. Now Magisk 19.4 or 20.2 still no accept add meal card!

Thanks for advices!

– MI9SE, MIUI Rom Based on China Stable / Weekly builds (MIUI 11.2 by Xiaomi.eu 20.1.2 weekly).

– Android 10 QK1. 190828.002

– Security patch 2019-11-01
[Magisk] marvi0:
Hello which gpay version app are we supposed to use?i have seen a post on here which mentions there is a gpay download but can't find it?
[Magisk] billyx1:
That was not what I said. I have studied computer science so believe me I know the facts.

---------- Post added at 08:58 AM ---------- Previous post was at 08:51 AM ----------

I didn't see in the document that an ONLINE verification is done during the payment process by the terminal. So please proove.
[Magisk] pndwal:
We'll, you did originally say:

[MENTION=4385440]theCroh[/MENTION] quoted Googles official explaination of the workings of GPay verbatim, to show that, in fact, Google Pay IS MAKING AN ONLINE CHECK THAT THE ACCOUNT EXISTS each time a transaction is processed, and, contrary to your understanding, IN NO WAY does a terminal 'just rely on the data sent by the mobile'. Moreover, the document CLEARLY SHOWS that an online verification IS done during the payment process by the terminal, doing so by activating a 'one-time-use password' to process transaction ONLY if the card network validates the sent cryptogram and is able to confirm a match between the token and the customer’s actual card number.

Obviously this verification is conducted ONLINE, so I don't understand why you didn't see, in a document dedicated to explaining how the verification process works, that such a verification IS IN FACT HAPPENING if you actually read it, much less what further proof you want.

I understood next to nothing about GPay process before checking the link sent by [MENTION=4385440]theCroh[/MENTION]. Personally, I thank him for the clear reference and edification. PW.
[Magisk] pndwal:
Official GPay app will appear in Playstore when everything is set up right on your phone, and work too!

Some have loosely referred to 'GPay SQLite Fix' as 'GPay module' in this thread, and this confused me too (until I reexamined the context).

I don't think anyone here has suggested any sort of GPay App, or App module, for sideload. PW

PS:

See steps that were successful for me at post #764 (4th post page 77)
[Magisk] pndwal:
A GitHub reference:

https://github.com/davidramiro/gpay-gms-patch/blob/master/README.md PW
[Magisk] 73sydney:
Magisk Method Gpay SQLite Fix.....

Changelog:

SQLite Universal Binaries

11/1/2020

Probably should have been done sooner, but i was hell busy end of last year...had some time finally tonight/this morning, so here it is, an *almost* universal SQLite binaries package

Universal (well almost, support from arm-v7+ ) SQLite3 binaries for Android.

This module will first check to see if an SQLite3 binary already exists in the common paths (as per my GPay SQLite Fix module), so it doesnt try and install another or overwrite an existing one.

Again, only armeabi-v7a architecture and above is provided by this module

Specifically supported:

armeabi-v7a

arm64-v8a

x86

x86_64

This module will put an sqlite3 binary into /system/bin if /system/xbin is not present

Any scripts relying on this sqlite3 binary need to check both paths for sqlite....

The previous SQLite binary for arm-v7 only module remains linked below for now, but please try the new one first

Downloads in download section of my Gpay SQlite Fix post via this link or Google Pay SQLite Fix link in my sig
[Magisk] joluke:
your signature doesn't appear..
[Magisk] jcmm11:
You're probably using XDA Labs app. Either view in browser or click on his image (or where his image would be).
[Magisk] joluke:
Thanks for your help [emoji6]
[Magisk] 73sydney:
I did include a "this link" in the post as well :)

I generally post a link as well as refer to my sig, as i am aware sometimes people cant see the sig depending on how they view the forum :)
[Magisk] FluffyDiscord:
Hello, the magisk module doesn't work for me. What can I do to help you debug/workaround it, pretty please
[Magisk] joluke:
Thanks a lot [emoji4]
[Magisk] pndwal:
Please describe phone model / ROM type, what didn't work - loading Magisk mod (which version did you try), loading sqlite binaries, passing safetynetcheck fully, etc... pretty please :) PW
[Magisk] MrPierc:
Hello, when i add card, Google pay error = OR-TAPSH-08.

I have active card in bank account, i have Magisk, fixed dg.db with chmod 440 and cant add card. Google Pay somehow blocked my card in Google Pay?

Magisk 20.3, safetypatch v3, safety net Green (ok), Google Pay = Play protect certificated
[Magisk] FluffyDiscord:
LG G7 ThinQ EU, stock Pie

Magisk 20.3

Installed sql binaries from magisk repo v1.3

Gpay fix full edition v1.9

Can not pass safety net (not sure which module does this, maybe edxposed? List: https://imgur.com/a/11igUqg)

With that I guess, it won't work because of safety net?

Exit: U enabled black/white list in EdXposed, blacklisted Google play, play services and play framework and then checked Google play and play services in Compat List.

Now I fully pass safety net and your module works! If you wouldn't mind adding this bit to your post, for people using EdXposed?
[Magisk] pndwal:
Does basic integrity pass but CTS fail?

Applying SafetyPatch Magisk module should fix (from Magisk repo). This is most simple, but uses a Huawei fingerprint to pass. MagiskHideProps config will also work with fingerprint of your choice.

Also, hide in Magisk: Google Play Services, Google Play, Google Services Framework etc (com.google.android.ext.services com.google.android.apps.walletnfcrel com.google.android.gms com.google.android.gsf com.paypal.android.p2pmobile)

May also need BusyBox (module by osm0sis in Magisk repo), and to clear data / cache for Google Pay.

See steps that were successful for me at post #764 (4th post page 77) PW

Refs:

https://didgeridoohan.com/magisk/Ma...and_other_apps_wont_install_or_doesnt_show_up

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

https://github.com/davidramiro/gpay-gms-patch/blob/master/README.md

Further reading on a complex subject:

https://customroms.net/faq/safetynet-android/

https://koz.io/inside-safetynet/
[Magisk] 73sydney:
Its not easy for me to document things like edXposd or SafetyPatch Magisk module because i havent used them and have no plans to do so on my device

If someone wants to give clear step by step instructions on how it is done in either, than ill add them to my post.

Until then i will add a note for people to search the thread with keyswords edxposed and safetypatch.....
[Magisk] pndwal:
Looks like you succeed last few minutes. Well done!

Yes, read xposed installer (edexposed) must also be hidden in Magisk, or xposed uninstalled

Also, as it seems you discovered, [MENTION=5917892]kevinwu128[/MENTION] wrote:

Also, check the GitHub ref in the following post re EDXposed blacklist settings, etc:
[Magisk] pndwal:
- I've put the best notes & refs re. Xposed usage (from members here) in my post above (but I don't use Xposed either).

- Applying SafetyPatch Magisk module (from Magisk repo) fixes safetynetcheck CTS for many custom ROMs and Chinese stock uncertified ROMs (many Xiaomi MIUI users, etc) that fail this check.

Method:

Simply find in Magisk repo, apply and reboot, then Check safetynetcheck CTS is passing, and Playstore/ settings/ About: Play Protect certification says Device is certified.

SafetyPatch is most simple, but uses a Huawei fingerprint to pass. MagiskHideProps config (Magisk repo also) will also work with fingerprint of users choice.

Many thanks for your valuable module and efforts. PW
[Magisk] 73sydney:
Thanks for that i hadnt seen those, so ill update my post soon with those as the preferred tips
[Magisk] 73sydney:
Have updated my original post with the info for you, and others, thanks.

Check it out and let me know if you think its okay and i havent buthered it :)
[Magisk] tiga05:
Hello,

Just want to give some feedback:

I am using now the google pay app version 2.86.2433xxx since about one year + the newest magisk version and only hided google pay + google play services app in magisk.

And I never had a single problem.

I have a oneplus 3T. During the last year I changed from the custom ROM skydragon OS to the official ROM of oneplus and later the year back to skydragon OS. During this I only restored the app via titanium backup. Unfortunately I had to readd my credit cards multiply times. But also this worked without problems all the time.

... Maybe this helps someone.
[Magisk] pndwal:
Not buthered, or even butchered ?, but you mention "SafetyPatcher" several times. Module is simply "SafetyPatch" in Magisk repo.

Thanks for including these details for a more inclusive solution (incl. credit given :) ), as well as for recent SQLite Universal Binarys update.

Really, your module has made a technical and challenging process the dead-easy (and entirely systemless) solution it is now. PW
[Magisk] 73sydney:
Cheers, fixed the SafetyPatch(er) thing

Im often working on this stuff at 4am, long days, and nights :)
[Magisk] gabx:
Thank you. Simple, well documented and works like a charm