yashsingh1/xdaforums huggingface dataset:
[Magisk] eckengucker:
I can't get NFC working. I pass play protect, safety net etc. but in G pay it shows my phone doesn't meet security requirements. I tried clearing cache and reinstall sql fix. After a reboot it is working on the first app start but after 2 seconds G pay reopens itself and NFC is gone. Any advise? I tried different fingerprints too.

Edit: I wiped all Google caches while in airplane mode and it is working now.
[Magisk] LaCruz:
Wipping all Google caches while in airplane mode is essential. Now gPay works fine!

Thanks!
[Magisk] 73sydney:
I'll add the airplane toggle as a specific step (for clarity) to the instructions for people who need to clear data/cache, thanks gents
[Magisk] dipstik:
any consensus if offical 11 breaks things?
[Magisk] evilryry:
It shouldn't, been using the zip method through the 11 beta and it's kept working :D I haven't updated to official yet though.

Update: I have Hardware based checking now upon flashing to official 11, boo.
[Magisk] xunholyx:
It still works.
[Magisk] djjohnnyblaze:
Still working here as well.
[Magisk] ryandanger:
Just as an (obvious) FYI to anyone who also updated their Pixel 4 XL to Android 11 and are using the Magisk Hide Props Config module, option #2 Force Basic key attestation; your device will be spoofed as a Nexus 5, and you lose access to the "new" transparent Google Assistant. Nothing else that I can see has been forced off.
[Magisk] Didgeridoohan:
You could try picking another device from the list when activating the option. Maybe that one of the Pixel devices still use basic attestation and that it'll keep the transparent function working.

Prior to A11 the Pixel 3a would use basic attestation. No idea if that's still the case though...
[Magisk] 73sydney:
Top tip: People should ideally be checking SafetyNet via (Canary) Magisk Manager to see if their device is still on basic or hardware attestation before using #2....you may be causing issues where you shouldnt have any

I'll be flashing Android 11 tomorrow to see if my Pixel 2XL is still doing basic...
[Magisk] pershoot:
This process is confirmed working on Android 11 (release; OTA), P2XL and Magisk Canary Beta; GPAY contactless is operational.
[Magisk] 73sydney:
Glad to hear, though my plans to test basic attestation is still working on Pixel 2 XL on Android has been hampered by the fact i cant get magisk to install by any method - bootloop city :)

From clean full wipe flash at least....

Having to go back to 10/BlissROM for now
[Magisk] djjohnnyblaze:
Working on Android 11 as well for me.

P3a

Magisk Canary latest

Safetynet passes without any workarounds.
[Magisk] 73sydney:
Im pleased to report tonight i am bathing in the glow of Android 11 with root

1) flash-all.bat (with wipe enabled - because clean install)

2) Immediately on reboot from 1) and before it gets anywhere near to beginning of setup: fastboot boot twrp-3.4.0-1-taimen.img

3) adb push Magisk-e66b0bf3(20425).zip /tmp

4) adb shell twrp install /tmp/Magisk-e66b0bf3(20425).zip

5) adb reboot

6) after reboot, install canary magisk manager (for whatever reason doesnt install from TWRP flash)

7) open canary magisk manager and enable magiskhide

Safetynet pass with Basic EvalType still...party time

So Pixel 2 XL/Pixel & 3/XL/A at least, no change in evalType
[Magisk] useformildaccess:
Clear Google Pay's Cache and Storage

I cant seem to clear Google Pay's cache and storage either manually or through the GPay SQLite fix Magisk module. My device passes basicIntegrity and ctsProfile with basic evalType but all of a sudden Google Pay says "phone doesn't meet security requirements." Cards I have added on my previous phone showed up on my new OnePlus 7T and I was able to set them up for in-store payments but never had a chance to test them until recently when Google Pay declined the transaction at a gas station. Then I noticed I could add new cards but cant set them up for in-store payments. That's when I noticed that Google pay is saying my "phone doesn't meet security requirements." At first I tried clearing the cache and storage but nothing happened. The cards are there still showing to be setup for use except Google Pay is still saying "phone doesn't meet security requirements." Then I followed your guide and installed GPay SQLite fix Magisk module. Yet still, the cards are there still showing to be setup for use except Google Pay is still saying "phone doesn't meet security requirements." My Google Pay version is 2.116.328438545. Am I missing something? Any suggestions?
[Magisk] pndwal:
Haha, I just replied to identical post here:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/post83525091

To reiterate:

Did you read through whole Magisk Module post?

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

Do you have the SQlite binaries loaded too (I prefer Magisk module for this)?

Is your G Pay downloaded from playstore (not sideloaded version)?

May need to clear data as well as cache as suggested.

Also, try this if still failing: Add G Pay, Playstore, and G Play Services to hide list in Magisk Manager, then toggle on airplane mode, reboot, clear caches, and possibly data for all of these, reboot, toggle off airplane mode. PW
[Magisk] LeMoise:
Tried this on Android 11 and just wanted to say it got it working for me. Appreciate it.
[Magisk] 73sydney:
Sorry folks, as theres effectively 2 threads on Google Pay issues, i updated the othe rthread where a LOT has been happening (resulting in changes) and now updating here

Magisk Method Gpay SQLite Fix.....

Changelog:

SQLite3 Universal Binaries

v1.1 - 1/10/2020

- Added

mkdir -p $MODPATH/system/xbin

In response to report from XDA user [MENTION=4950275]djjohnnyblaze[/MENTION] that the sqlite binary wasnt getting copied on his device under Android 11

Recommended especially for those folks who have recently tried installing the Gpay SQLite Fix and find it reports it doesnt find the sqlite binary, that you thought was just installed by the SQLite3 Universal Binaries module!

Current users can also check if theyre unaffected by checking the contents of the /cache/payfixfirstrun.log file, if the sqlite binary hasnt been found by the module, it will show up here as:

In addtition, my OP has been updated quite a bit lately, theres now a Pre Installation Checks (to better target where the issue is (CTS fail for example) before installing my module, hopefully leading to less posts wiht the same core issue(s) over and over) and to which ive just added the following (due to newer devices and issues which have presented for the first time in more recent patch updates)

Links updated in main post here, or in my signature
[Magisk] pndwal:
'Tiny cc' link above not working! ;) PW
[Magisk] 73sydney:
Fixing now, thanks

Youre always cleaning up my messes :)
[Magisk] Izy:
was working then stopped so started from fresh now getting failure of eval hardware

reinstalling props etc and the config from guide it still fails eval

changing props in termal still gives failure hardware eval

trying edexposed hide make it show as passed on hardware but pay still fails

edit i have it passing now with basic but still no gpay passing detects modified device
[Magisk] pndwal:
Do you at least have basicIntegrity pass in Magisk and EdXposed fully removed? Even Canary EdXposed is tripping basicIntegrity now. PW
[Magisk] FenderKetchup:
Wipe your Google Play Services data
[Magisk] Izy:
Nope was failing even after a complete reconfig from scratch.

Could only get hw to work with Ed. Then I got basic to activate after

And yeah I wiped gplay

I literally was using this since months ago then it just stopped
[Magisk] pndwal:
We are talking about basicIntegrity pass failing in SafetyNet right?

Basic / Hardware Attestation type will be irrelevant if this is failing. You need to fix this first. It will necessarily trip ctsProfile, and should pass regardless of ctsProfile status, or evalType.

After you have basicIntegrity, configure MagiskHide Props Config for fingerprint (if needed) and 'Force Basic'.

Nb. SafetyNet basicIntegrity and Basic Attestation are two different things, and shouldn't be confused. PW
[Magisk] Izy:
yeah its all working again. didnt it from scratch a 5th time

last time the problem was after retrying it it was failing both now its working again
[Magisk] inningsdefeat500:
Which exact steps did you follow please
[Magisk] c3k:
I was using Gpay on my rooted S10 (and before with my S8) with this method, until my card expire and now I can't add a new card.

I try the entiry process from zero (cleared Google Pay, Google Play Services, Google Service Framework and Google Play data).

I'm passing safetynet with basic attestion.

Google Pay don't let me add a card with error "contact your bank" (but the same card works with other device / account).

Suggestions?
[Magisk] Player04:
i had that problem. it;s the banks bank.
[Magisk] c3k:
Yes and no.

Same card works on other (stock) device.

Other card from different bank works on my device.

The bank that didn't accept the card say that Google report a "low risk". I think they want a zero risk. My guess is that Google give a classification to the device and the bank decide which level require.

Could be?

My setup: Samsung S10, Magisk 21, MagiskHide Props Config, passing SafetyNet with evalType basic simulating a SM-A300FU (Samsung A3 2015).
[Magisk] inningsdefeat500:
Anyone had this work with N9860 Note 20 Ultra

With so many steps, I am hoping if someone can guide me the right n exact steps

I had it working a while ago by hiding google apps in magisk but then stopped suddenly
[Magisk] inningsdefeat500:
This by far was the most important part

Toggle Airplane Mode on

Clear

data

and cache of:

Google Play

Google Play Services

Usually this will be achieved by (exact steps and terminology may change per device or ROM):

Opening Settings

Going to Apps, choosing Show All Apps

Enabling Show System Apps via a menu option

Locating the app, tapping it and then finding Storage/Cache

Tapping Clear Data

Toggle Airplane Mode off

Open Google Play Store, go to Settings and check Certification at bottom
[Magisk] Jonny:
Thanks, this worked for me with an Umidigi S5 Pro. The only downside is I had to reset my TicWatch E2 and reconnect it as it apparently clears connected smart devices as well.
[Magisk] dandu3:
you just need to adb in your watch and reset it's play services, and then make the bluetooth discoverable. a couple quick commands and you're good to go. YMMV tho, I've had weird issues sometimes on my watch and ended up resetting it anyways, but I liked the idea of saving a few writes cycles on the flash memory to help keep it as fast as possible because it's already meh
[Magisk] Userbck:
I have the ultra no magisk eu stabl /device is certified with unlocked bootloader. Installed with twrp no problem
[Magisk] inningsdefeat500:
Anyone have the latest Gplay and have it working? I am not taking update Nov 3 yet
[Magisk] badaas:
Everything passes but card says not setup even though it is, settings say security issue.

Basic with safety net all green.

Seems the end...
[Magisk] ryandanger:
Getting the same on my Pixel 4 XL. Interestingly enough, I'm passing SafetyNet with Basic without the fingerprint changes.

edit: Downgrade your Google Pay to 2.117.332286456. Passes again for me now even without the fingerprint changes!
[Magisk] badaas:
Downgrade same problem for me..
[Magisk] inningsdefeat500:
So I was right? dont upgrade?
[Magisk] mr nick:
I'm on 2.118.332329909 and Gpay is still working despite the fact that I now have a safetynet fail (ctsprofile) since getting an OS update a week or so ago.
[Magisk] zencooler:
I am on the newest GPay 2.119.340301324 and my SafetyNet still passed and GPay works with no problem at all.

I have forced basic attestation in props config and GPay SQL Fix.
[Magisk] GarryG:
Followed the instructions in the thread with the SQL, but can't use Gpay anymore ... SafetyNet completely green with Basic.

OxygenOS 10.0.14, Gpay 2.119.340301324

For the attest-entries - I changed all entries that have that string, so too stuff like ad_attest or pay_attestation ... was that wrong?
[Magisk] zencooler:
Clear all cache and data of GMS and GPay and then check if GPay Fix is a working as a module in Magisk + check if the dg.db file is set with 440 permissions. If you have SafetyNet passed with this points checked and confirmed it should be able to set up cards in GPay and use it with no problem.
[Magisk] GarryG:
Confirmed, I had a snafu in the Gpay fix in Magisk ... re-did the whole thing, re-added the card, now at least it's not complaining about not being set up anymore ... I reckon it will work again ... Thanks a lot!!
[Magisk] dixet:
Lifesaver! This works on MIUI 12.1.3, Android 11, GMS20.39.15!
[Magisk] mhrussell1:
I just got prompted to switch to the new version of GPay which I denied. I am on 2.119 on Pixel 3 and latest A11 with canary Magisk. Anyone know if this breaks the db exploit? 2.119 is not called "Google Pay (old app)" in the app store. I suspect it won't be long before we are forced to the "new" app.

TIA,

Mark
[Magisk] CSX321:
I've been holding off on the A11 update with my Pixel 3, waiting for confirmation that the reported freezing problems with canary have been solved. I guess yes they have?
[Magisk] mhrussell1:
I have had zero problems with canary Magisk and A11 (and GPay) on my Pixel 3.

Mark
[Magisk] BostonDan:
Unfortunately, the new GPay (actually called GPay, not Google Pay) does not work on a rooted phone. Advanced detection now. Not sure if it's sensing the unlocked bootloader or what, but still...

Edit: nevermind. It was a magisk module that broke safety net (both cts and Basi integrity). When removed and gpay cache and data cleared, all worked fine.

Cheers,

B.D.
[Magisk] nunytes:
Hello!

My play store is showing certified device and the safety net is ok with basic evalType.

My GPay is currently working only few hours until it says my device is modified and insecure. I've downgraded to 2.117 version but the problem persists until I wipe all the Google services data and add the card again.

Is this a common problem or I missed something?

My phone is Xiaomi Redmi Note 8 Pro with stable Magisk 20.4 (with latest canary manager) and EdXposed installed (hidded from safety net).

I appreciate some help if there's something I can do ?

Thanks!
[Magisk] balkerman:
The freezing is related to the systemless hosts option. Just remove or don't enable and no more freezing.
[Magisk] Lord Sithek:
I have similar experiences, and I've tried many different things. I tried Magisk Canary (currently using beta), latest Riru Core, latest EdXposed Canary, SudoHide Xposed module and SQLite fix. Of course Magisk Hide always enabled. However, GPay always detects root after some short time. If you'll find solution, let me know ?

Xiaomi Mi Note 10, A10, xiaomi.eu
[Magisk] blu.italia:
Same here!

When i read the Google help Page for this, i think they also now check the build Text. And in the build text for me is the following

QQ3A.200805.001

PixelExperience_polaris-10.0-20201122-0400-OFFICIAL

And this is the sign for Google that i dont use official Software. But it is only a thought.

I cant understand, Why it is a problem for google when we have a rooted Phone.
[Magisk] zgfg:
That build text is called device fingerprint, e.g. you get it from Terminal app by

getprop ro.build.fingerprint

You can also read them (there are more similar props), by use of e.g. SesEdit app from Playstore

In order to get GPay working, your Device must show as certified in Playstore, and in order for that device must pass SafetyNet test

Mathematically speaking, these are NECESSARY condintions, but maybe NOT SUFFICIENT

That is, if you don't pass A then 100% B will also fail. But if you do pass A, there is still a (small) chance to fail B, but bcs of other reasons

You can use Magisk Hide Props Config to fake the device fingerprint and/or device product model to trick the Google to pass the SafetyNet

Edxposed etc, might be just one of those other reasons to fail the Basic Integrity (part of the SafetyNet test)

Those tests and restrictions are not only Google's wish. E.g., banks don't want their users to use the rooted phones (discuss with them how and why) and they require some mechanism to attest if the phones are running the original software that was certified by the phone vendors or if somebody tweaked the phone by potentially security risky changes

They don't have mechanism and it would be too complicated, practically impossible to prove that your changes did not introduce security risks - the other way would be for you to go alone to Google and pay for the time and material to let them attest and certify your root changes against all standards, security, etc - then you would show to your bank your attest certificate and your bank would say ok

Think similarly about passing the technical exam for your car if you replaced the original and certified engine, suspension, etc
[Magisk] blu.italia:
My device is certified in play store and pass safetynet test. I dont use edxposed. Perhaps it is useful to hide magisk Manager! I think this is a important point.
[Magisk] Lord Sithek:
Possibly repacking Magisk Manager would help. But EdXposed is the main challenge - that's what it's all about ? I don't really want to sacrifice this since I use several modules important to me
[Magisk] zgfg:
Hiding Magisk Manager has nothing about SafetyNet and Device is (not) certified.

But you must make sure that Magisk Hide is enabled in Magisk Manager settings

(Magisk and Magisk hide is not the same as Magisk Manager and Hide Magisk Manager)

But yes, there are some banking apps etc that also look for Magisk Manager and if find the apo, they conclude that phone is rooted (similarly they may look for Titanium app or TWRP folder)

Anyway, theory behind the SafetyNet (with the table what and how causes Basic Integraty and CTS Prifile failing - you will see that huding Magisk Manager app has nothing with them) is here, official from Google:

https://developer.android.com/training/safetynet/attestation
[Magisk] Mew789:
Is it working with latest gpay version ? I have uses magiskhide propos config module and can pass safetynet but still cannot use gpay. They Say m'y sévices doesn't respect security...
[Magisk] blu.italia:
The Google Pay Version isnt important. The Google Pay App also isnt important. You can use Google Pay without the App. Google Pay is firmly integrated in Android. With the App, perhaps you have more Features.

Have you hide the magisk Manager? After that clear App data for Google play store and Services, restart and try it again. Do you use SQL and gpay fix module in magisk?

---------- Post added at 10:01 PM ---------- Previous post was at 09:55 PM ----------

@Lord Sithek and zgfg

I think you miss understand me. Google pay work for a few days, but then there come the safety failure in the Google Pay App. I havent changed anything. And now i only hide magisk Manager and Google pay work again.

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

@Lord Sithek and zgfg

I think you miss understand me. Google pay work for a few days, but then there come the safety failure in the Google Pay App. I havent changed anything. And now i only hide magisk Manager and Google pay work again.
[Magisk] nunytes:
Apparently it's working well with latest riru and EdXposed. Need some days to test, but by now I should had security issues with GPay app and it's working fine until now!
[Magisk] pndwal:
Just a heads-up:

I read here some had G Pay working without SQ Lite fix.

I've just rooted my Redmi Note 8T, and thought I'd check this, and was surprised to find G Pay works fine!... it's found in PlayStore, runs and is set up without issue (no warnings about modded device etc), and NFC payment works fine too.

I have it toggled ON to hide root from it in MagiskHide list of course, but NO modules as yet, SafetyNet fully passing w/ BASIC evalType, and PlayStore 'Device is Certified'; no other mods. Running Shock MIUI 12 / Android 10.

I don't know what's changed, but seems I don't / others may not need SQ Lite fix to have G Pay with root any longer!

Of course, this may well prove to be a temporary reprieve. 🙄

Perhaps Google is just getting soft?... Shucks, I feel all warm 'n fuzzy... 🥰 PW
[Magisk] 73sydney:
No one would be happier than me if it turned out the SQLite fix was no longer needed.

I imagine it would make you even happier @pndwal , as you do most of the support for my module :)
[Magisk] pndwal:
Well, I / others really appreciate your efforts...

Edit: AND @BostonDan's!

... but thats a bit generous... 😁

Didn't think you'd mind the changes either, but I'm not yet sure what they mean going forward... PW
[Magisk] 73sydney:
How very dare you forget @BostonDan :) :P :P
[Magisk] choczplays:
This doesn't work for me. I have Poco X3 NFC rooted with xiaomi.eu rom. Not set up error. Can someone help me ?

After services data delete it works now nice.
[Magisk] pershoot:
This process is confirmed working on the Pixel 4A-5G (latest patch set), standard GPAY application (not the new one), Magisk Beta.
[Magisk] simplepinoi177:
Hey all!

How does this method and/or the magisk module work on the Pixel 5? I apologize if it seems I didn't do my due diligence and use the search function, but I actually did try but since the site's upgrade the "search in forum" option isn't showing; but I did find that you can set the search toggle to "this forum" or "this thread". In any case, I did try to search the term of "pixel 5" within the thread/forum and none of the results pertained to this process.

When I did this process on my Pixel 2, I did what was on the OP and did things manually and that's how I got things to work. Should I do it manually again or has there been success with the module on the Pixel 5?
[Magisk] 73sydney:
Doesnt really matter what the model is, as long as you can pass safetynet, it will work

You can do the original method or the magisk module method... i recently updated the module post with a prerequisite checklist and step by step process to make things (even) easier (hopefully)
[Magisk] BostonDan:
I still do my original, but all that is required is changing the permissions, as long as GPay hasn't failed before first launch. But I'm glad to see the community's support and interest in this.

Cheers,

B.D.
[Magisk] 73sydney:
Hehe i have to marvel at how ive taken what is a fairly brief OP by you and turned it into what @Didgeridoohan once called "the most wordy post on XDA" :) in my post for the module - a month back i actually hit the character limit, and had to remove a few paragraphs when i rejigged it :)
[Magisk] osm0sis:
Hi! Nice work here!

Yesterday I switched to my OnePlus 8T as my DD and unfortunately ran into the "Not set up" Google Pay issue for the first time on any of my devices. I flashed your latest zip, and even cleared the GPay data but it didn't seem to make any difference. I noticed the following as the log:

System boot completed

/system/bin/chmod....accessible

/data/data/com.google.android.gms/databases/dg.db....accessible

[titanium] SQLite3 binary found in: /data/data/com.keramidas.TitaniumBackup/files

Google Pay stopped successfully

Chmod 440 command completed successfully
Permissions reported as: 440

And I noticed no SQLite stuff so took a look into the script and noticed it's all behind $runsql -eq 1 but nothing ever seems to set that? Just confused as to how that's supposed to work. I just went ahead and set runsql=1 above it, rebooted, checked the log and it ran and then Google Pay started working, so 🤷‍♂️