yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
Thats a different issue, he doesnt mention it wiping his loyalty cards....but perhaps it has the same root cause:

In any event, apart from making the cache/storage clearing option via keycheck, i cant do much, dont have loyalty cards, and dont plan to get one - i dont want to be on their marketing radar thanks (they are largely scams here (i.e. you end up paying more than the value you get in return by orders of magnitude), maybe elsewhere too)
[Magisk] pndwal:
Totally agree, and point taken! I haven't got any / don't plan to get any, but each to his own.

Just thought it worth mentioning. You did say 'issues with loyalty cards have never been mentioned before that im aware (but its a long thread)'.

Still reckon yours is a top mod / utility. Best return for the payment. By orders of magnitude. Kind regards, PW
[Magisk] bonbonboy:
Hi there,

Google still refuses me to add a card, i'm looking for help please.

I:

Installed sqLite via magisk Repo (i have ARM64-v8a) - no error

Rebooted system

installed Gpay Sqlite fix (fulle edition) v.1.9 via magisk manager - no error

Quitted Magisk manager

Went to my Revolut app, tried to add a card to GPay

Confirmed the google prompt (i want to use this card with Gpay, Confirmed my address)

Then i've got an error telling me that these features cannot be added to my phone because it seems rooted or modified

I don't really understand what's wrong is the process :(

Any clues?
[Magisk] pndwal:
Please say:

How did you get GPay App on device?

Did you clear cache & data for GPay after applying fix?

If you check Playstore, settings, about, do you see 'device is certified'? PW
[Magisk] bonbonboy:
Thanks for your reply.

- i don't have the gpay app on my device. (i guess the app revolut calls gpay via google services or something like that)

- no cache clearing because i don't have the gpay app

- For the last question, i guess you talk about play protect certification. So my current status is "device not certified" (play protect is currently not activated because i'm using lucky patcher). But i activated play protect to get the status "device certified" and tried again to link a card with gpay, but i've got the same issue.
[Magisk] pndwal:
OKAY, I think you are missing the purpose of this thread and SQLite Fix. This is 'Working: Magisk with Google Pay as of gms 17.1.22 on Pie by BostonDan' and it's purpose is to 'allow one to add cards and pay in store' using G Pay with NFC card readers, using a device rooted with Magisk.

This works by spoofing a legitimate Attestation state by editing a few lines on a database included in Google Play Service storage, and by locking it down so the state cannot easily be changed again by Play Services, allowing G Pay to both appear in Playstore, and work. The point of this fix is to install and use G Pay!

Seems you are trying to add card to G Pay through a third party App. - You can't add a card to G Pay if the app is not on your device!

This fix will not help adding a card to your Google account as far as I know if that's your aim or problem. I may be wrong, but I think neither root nor Uncertified Device for that matter, prevents this. You problem is different from the one this thread addresses. Others here may be able to help, but probably you'd be best to keep Googling. :) All best, PW
[Magisk] bonbonboy:
Yeah, this is my purpose :)

Installed gpay app from the store, and in the gpay app, i succeeded to add my card. Good to know for the next time, it works only in one way, even if you have a both way choice!

Thanks again for your clue! :good:
[Magisk] YoshiFan501:
I'm having a weird problem with my gpay. everything is ok. safetynet is ok. but whenever i add my card, no matter what card i have, it says double check card details. i can add my paypal account fine, but i cannot add my cards.
[Magisk] drup88:
No worries sir, we all take risks when doing this kind of stuff. I thank you for your detailed and empathetic reply. :good:
[Magisk] pndwal:
Glad you got G Pay and it's working now!

I still don't understand what you mean regarding other way it can work. What other choice did you want to use? PW.
[Magisk] 73sydney:
Still, i wasnt happy to read about your issues

Apologies again
[Magisk] bonbonboy:
I've got one purpose, add my card on gpay to be able to pay with my phone in shops.

For this, i tried two ways to install a card in gpay.

- when you want to add a card in gpay without the gpay app BUT through a third app (like my bank Revolut which propose you to do), it calls well gpay to follow the process (i don't know how but i've got the gpay screens. Maybe web pages integrated in the app or called through Google services...) and failed at the end with the issue "rooted or modified device"

- But If you install the Gpay app, and inside it, add manually a card (from my bank Revolut), you've got the same process and screens that you have to confirm like above, and it achieves the operation at the end.

I hope it's a bit more clear :)
[Magisk] pndwal:
Yes, I'm starting to get the picture. :) Thanks for the explaination! I was unaware other banking apps could make G Pay transactions without G Pay app installed.

I now understand that even with SQLite Fix and fully passing CTS (device certified), your bank app still sees root / modified Device (as is often the case).

So it was your Bank App all along that was causing this problem, not G Pay's detection. This means they have their own detection methods, and don't simply look for CTS pass, or the Attestation value fixed by SQLite Fix (although this fix does reportedly help some banking apps). In saying that, Bank apps (like G Pay) invariably will NOT run without CTS which is why many need MagiskSafetyPatch or MagiskHideProps config modules in addition to SQLite Fix if on custom ROM or Chinese stock uncertified ROM. In your case, neither your Bank app, nor G Pay app were ever going to work without getting past your Lucky Patcher problem to get CTS pass.

The good news:

Very likely you can still hide root / mods from your Bank app fairly easy. It's likely looking for the same simple signs many Bank apps look for, so:

- Add bank app to Magisk hide list (to hide root from it). Also, M hide can't work on adopted storage, so ensure app is on Internal.

-Use Magisk feature that repackages Manager with random name to hide this from apps that look for it.

-Clear data for the app since some apps “remember” root after finding it the first time.

-See below for info re Xposed, EDXposed and MANY MORE TIPS c/o [MENTION=4667597]Didgeridoohan[/MENTION]:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Hope this helps. PW
[Magisk] bnwg:
Under the phone setting you can find G Pay without G Pay app

Phone setting -> Google services & preferences -> Account services -> Google pay

The main different I found is with G Pay app you can look at your purchase history
[Magisk] bonbonboy:
Thanks for all, i'll keep this in mind ;)
[Magisk] TheMrM00n:
It wont lwt me add my card, says configuratiom couldnt be finished. Probably something magisk related
[Magisk] 73sydney:
Magisk Method Gpay SQLite Fix.....

General Notice:

GPay SQLite Fix (440 Only Edition) removed

Now only one GPay module for download, Full Edition renamed to just: GPay SQLite Fix vx.x

Changelog:

GPay SQLite Fix:

v2.0 12/11/2019

Magisk Module Upgraded to extended newer format - Magisk Module Template Extended (MMT-Ex) [TEMPLATE] - https://xdaforums.com/apps/magisk/magisk-module-template-extended-mmt-ex-t4029819 Thanks to [MENTION=6037748]Zackptg5[/MENTION]

Thanks to [MENTION=5318756]heatl0rd[/MENTION] a fellow Aussie who alerted me to the possible loss of loyalty cards (anything under the Passes tab in Google Pay) if using the previous format of the module. It was this that prompted the use of the new MMT-Ex as it provides, amongst many things, a keycheck function....

common/install.sh:

- Added: Keycheck choice for whether to clear cache and storage of Google Pay - this prompted by [MENTION=5318756]heatl0rd[/MENTION]'s experience with loyalty cards.

The display looks like this during this segment of install:

Clear cache and storage for Google Pay?

WARNING: This *may* clear data used for Loyalty Cards & Passes

Vol+ = Yes, clear, i understand the RISKS

Vol- = No, DONT clear, i understand it *may* prevent the module from working

- Added: Credits to [MENTION=6037748]Zackptg5[/MENTION], [MENTION=6315410]Skittles9823[/MENTION] and [MENTION=4487388]jcmm11[/MENTION] for their help during the changeover to the new module format. Worth noting [MENTION=4667597]Didgeridoohan[/MENTION] also, having already helped out with parts of the script previously, helped out again during this stage too.

- Removed: Copy of service.sh or gpay.sh to $NVBase/service.d (/data/adb/service.d) - it was pointed out to me during changing to MMT-Ex that i didnt need to do this, that i should leave service.sh in module root, i had previously been told to do the $NVBase copy....leaving it in root works, so the cp lines were removed.

service.sh:

-Renamed from gpay.sh, and left in module root so it works correctly

uninstall.sh:

- MMT-Ex has standard lines, under the following comment heading:

# Don't modify anything after this

any custom requirements are added above these, so my previous uninstall lines are added above this (Top tip: uninstall.sh is only copied to module root and therefore processed on unitsall if there are lines ABOVE the comment above) and are largely unchanged apart from the below:

-Removed lines to remove the former $NVBase/gpay.sh (/data/adb/service.d)

Note: there is NO reason for anyone currently using the module to upgrade to this version, the new features only benefit new installs

Downloads as always via the original post here: https://xdaforums.com/showpost.php?p=79643248&postcount=176 or via the link in my signature
[Magisk] Skittles9823:
Wew
[Magisk] Snuuuuupy:
It seems every update I have to re-add all my cards again. Does anyone know of a fix?
[Magisk] pndwal:
Do you mean ROM update, or SQLite Magisk module update? PW
[Magisk] Snuuuuupy:
Sorry, I mean every Google Play Services update it seems.
[Magisk] pndwal:
Oh... Strange. PW
[Magisk] sadiku:
I don't have this problem on my pixel4.
[Magisk] 73sydney:
Never had that issue, ever, sorry

And im flashing on average 2-3 ROMs a week to test and upgrading from my old zip of G-Apps on ext-sd to latest online
[Magisk] pndwal:
Perhaps more details would help us diagnose...

- What phone is it?

- Do you need SafetyPatch or MagiskHideProps to pass CTS with your ROM / phone?

- Are you using G Pay app from Playstore, or adding cards for G Pay via a third party banking app?

Thanks, PW
[Magisk] Snuuuuupy:
OnePlus 6T

Yes, I use MagiskHideProps, on Havoc2.9 custom ROM (Pie).

GPay app from Playstore, not adding via 3rd party banking app.
[Magisk] ultradj83:
deleted
[Magisk] godzulu:
Quick question. I've searched Google etc and haven't quite figured this out. Essential Ph-1, stock, February update. Magisk canary installed, Google pay installed, did the SQL fix. I'm able to add cards and pass safety net. I'm unable to use gpay. When I tap vending machine, gpay doesn't open. Any ideas helpful, thanks
[Magisk] godzulu:
I didn't have play play services hidden. Will try again
[Magisk] QkiZMR:
Sometimes Im getting Response validation fail error when I'm testing Safety Net. I can install Netflix and pay by phone in shops. Does anyone have a similar problem?
[Magisk] pndwal:
There's mixed results with 3rd party test apps. What's that one? - Just use the inbuilt Magisk manager test. PW
[Magisk] sliding_billy:
CTS is borked as of about 12 hours ago. Take a look at the [MODULE] MagiskHide Props Config thread... https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Magisk] QkiZMR:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

I checked in Magisk Manager and got ctsProfile: false. That's strange. I paid normally by phone today.

After soft reboot Magisk Manager shows all true but mentioned app still show same validation error.

How? On Google side?
[Magisk] sliding_billy:
That is the million $ question. Nobody has anything more than conjecture that ranges from a Google system issue to Google looking for unlocked BL with a new method and failing devices.
[Magisk] pndwal:
Yes, thanks, interesting last few pages re. unstable CTS. Looks like it will need some analysis to fix, esp. if G added extra unlocked bootloader detection methods.

Happy [MENTION=4667597]Didgeridoohan[/MENTION] seems to be on to it, albeit with limited time till next week. Hope John Wu - [MENTION=4470081]topjohnwu[/MENTION] is on it too - he'll certainly do his best. Here's hoping...

This is indeed the likely explaination for [MENTION=3834462]QkiZMR[/MENTION]'s issues above. Interesting that others also report still being able to use G Pay despite CTS showing'false'. PW
[Magisk] sadiku:
Yes, same problem here, it happen after Google play store update recently....
[Magisk] MrBrady:
Was working fine with no root, but just got this notice a few minutes ago while checking email. Maybe unlocked bootloader detection?View attachment 4965929
[Magisk] sliding_billy:
As Didg.. mentioned, this could be a Google glitch like amount of CTS checks. Who knows.

Hard to believe it is Play Store update related since it is still certified. Easy enough to check if that was the sole issue by reverting to the factory version of Play Store by "uninstalling" and testing CTS before it updates.
[Magisk] zencooler:
On my patched Note 9 phone I am still able to use GPay despite SafetyNet test showing 'false'. That is really weird. The SafetyNet check was working fine (with Magisk and custom kernel) and few days ago apparently (probably after Google Services updated) it changed into failed status. The interesting point: it says: the CTS profile match failed (see attached screenshot).

Does anybody knows what is the reason and how it could be patched? (if any).View attachment 4966239
[Magisk] pndwal:
Please read last posts here.

Problem is known, solution is not, but best experts on Magisk Hide are on it. Check last pages of thread linked in post #910.
[Magisk] Skittles9823:
From what I can tell it just seems like the SafetyNet API is broken. You still actually pass and it doesn't impact any apps from what I can tell.
[Magisk] sadiku:
Looks no function impact even safetynet checked fail, I still can use Google pay for petrol of my car.
[Magisk] pndwal:
Have you guys read last (8) pages of [MENTION=4667597]Didgeridoohan[/MENTION]'s thread (see [MENTION=4609886]sliding_billy[/MENTION]'s link in post #910)?

This is not yet affecting all rooted devices, but CTS is failing on more by the minute.

Evidence is mounting that there is some new prop check for unlocked bootloader causing this, but [MENTION=4667597]Didgeridoohan[/MENTION] is investigating. [Edit: It's actually worse than this. See my post below.]

If your device is already failing CTS, but still showing Certified in Playstore, this won't last. As he said:

Seems certification lasts until Playstore / play services updates, and afterward cannot be restored at present.

After loosing Playstore Certification, users reported:

- Outlook and other Microsoft Apps failing with message about Google Safety issue,

- Inability to add cards in G Pay,

- Other Banking Apps failing,

- Games (such as Dragilia Lost) failing,

- Apps disappearing from Playstore.

Hope there's a solution soon, but don't hold your breath! :( PW

Edit: Main Magisk Discussion thread is now filling with the same reports. No solutions:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/
[Magisk] dd805bb:
I got it working. Got a message today contactless pay will not work. My cts and basic integrity has been out for a while but gpay still worked. Today was the first time I receive a message via gpay my software fails contactless pay. Well I fixed it. Cleared data of gpay, left it hidden, restarted and followed the OP steps again. Gpay is working like normal again. CTS and basic integrity has always been off on my set-up. Pixel 3 xl running latest March Android update and Feb Google play system update.
[Magisk] CSX321:
Out of curiosity, why is your basic integrity not passing on a Pixel 3 XL?
[Magisk] dd805bb:
Mine I noticed is when I use afwall Xposed module. It fails. Works as intended with it on. But, I also used props module and reset magisk setting because it was using wasn't using default setting. So I just flipped it back to default. Now it doesn't pass but everything works as intended. Gpay works is all I care about.

---------- Post added at 10:36 PM ---------- Previous post was at 10:34 PM ----------

Also on a side note, I went back to stable magisk, left canary. Was having magisk problems with hiding itself on canary.
[Magisk] eric00x:
(redacted)
[Magisk] pndwal:
Update re. MagiskHide and SafetyNet:

"Fun is over guys" (topjohnwu) :(

Sadly, it transpires it was not simply some new prop check for unlocked bootloader causing CTS Fail:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/

I think we've all previously wondered why app devs needed to use their own methods to detect customised setups and quickly realised that SafetyNet has simply not been implemented properly. Whiie good for custom modders it has therefore obviously been unusable for developers with serious security concerns.

It seems G is now simply making SN & CTS reliable for these developers and in so doing, making Android a more competitive platform in this age of security awareness that has really become an imperative for all. Happily for MagiskSU users this has really been too long coming, but inevitable I guess.

Now, what John Wu says makes a lot of sense (sadly): "So here we go, after years of fun messing around using Magisk, it seems that Google FINALLY decided to "fix" SafetyNet to something useful, and that is to use key attestation to verify device status (after 3 years since introduced to Android's platform!)...

We might be able to hack around temporarily by forcing key attestation failure, fake report keymaster version, manipulate cached check results etc, but all of them is meaningless after this change is fully deployed AND properly implemented. Let's face it. Fun is over guys."

https://mobile.twitter.com/topjohnwu/status/1237656703929180160

Also "I actually had a nice conversation with some engineers directly working on Android platform security a few weeks ago. They are well aware of this "proper fix". In fact, many people, including myself, already knew about this stuff for quite a while."

Maybe they feel there is more to prove since they let John W slip through their fingers to work for Apple too. (...sigh.)

XDA Comment:

https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/

Long live MagiskSU and the Magisk Module.

RIP MagiskHide. PW
[Magisk] nbarrett423:
Guess it's time to start digging deeper into f-droid/aurora store... This could really cause some interesting development in the smallish (until now) community of off-the-gridders doing their best to shun the Google overlords from their lives altogether.
[Magisk] pndwal:
Like MicroG? ( https://microg.org/ )

Or 'e':

I looked into that some time ago. May well have progressed, but, unless I'm much mistaken, there's a better chance John Wu will fix MagiskHide than getting GPay, Banking, and other securitycentric apps to work on de-googled custom devices that rely on signature spoofing etc. I don't like the odds either way (though pigs might fly), but you have to admire the ideals espoused by the likes of Gaël Duval. PW
[Magisk] 73sydney:
fwiw, on my Note 4, fully up to date GPS, my Playstore is still certified and CTS and Basic Integrity are fine using Magisk Stable (i got tired of the silly new GUI of the Canary builds)

Lets see how long it lasts for though, i guess....

Have updated my OP with the news and links
[Magisk] pndwal:
https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/

It'll be interesting. PW
[Magisk] nbarrett423:
Whelp, mine was still working this morning, then tonight I installed something and got the dreaded alert I was expecting, that my device was no longer ready for contactless payments and to check my software... But it was honestly overdue, I hadnt ever even passed cts, so I can't believe it ever worked. Except when I open magisk manager just now and clicked safety check to see where I was exactly, it passed both first time ever... Weird... Then just for fun I went to Google pay every it says my device isn't blah blah and clicked check software, and this happened...

So working great now, seems like... Wonder what I did to deserve this...
[Magisk] seemebreakthis:
Someone created a new entry on Google's issue tracker about safetynet and bootloader check.

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

Let's see how Google responds. For now though they seem to have rolled back these additional checks. At least my phone is once again passing safetynet checks.
[Magisk] zencooler:
+1 here [emoji106]
[Magisk] 73sydney:
Last night, thanks to some nice devs on the Note 4 threads, my device got LineagesOS 17 (Android 10) and now i have to do this:

https://www.youtube.com/watch?v=wKYC0r-m0Mo

This fiddling was unnecessary in Android 9 (Pie) on my device, but since i saw this helpful video posted in another thread showing how to use Magiskhide Props i figured that posting it here might help others
[Magisk] pndwal:
For those who may not be aware here, we have some good news:

Currently Google have key attestation switched off for CTS status detection again, and most who had 'pass' previously have it again for now.

The bad news however, is that Twitter users report Google reverted it because OnePlus and some other OEMs messed up Key Attestation on some devices, so Google is apparently waiting for them. (Nb. I can't confirm the validity of this claim.) So sadly, it seems we shouldn't expect this reprieve from Google to last, although it may be some till affected devices get updates and are fixed.

John Wu (_@topjohnwu) earlier commented:

Check Main Magisk Discussion thread for latest, and references:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/

Sorry outlook for this looks bleak... to much bleak news of late... I'll be sure to post positive news when I can. Regards, PW
[Magisk] ItWasAllIntended:
I have not found that I've started passing SNet again. Has anyone else had this experience? I just reformatted my Pixel so it has only Magisk and a couple modules and I am not passing. Did they re-enable it again?
[Magisk] franky_z:
I tried to pay with Gpay today and it did not work. Using Magisk and hide the Google stuff. Is it still working for anyone?
[Magisk] CSX321:
It still works for me as of about 45 minutes ago. I did it all manually back when this first started last year, not using a module or anything. It's just continued to always work, without requiring me to do or redo anything.
[Magisk] warrencoakley:
Yep my Magisk still intact and GPay working
[Magisk] alphahere:
Mine is still working also. I guess it will stop working soon. Not a big loss because very few places take gpay around here.
[Magisk] sadiku:
Thanks for continue support update!
[Magisk] 73sydney:
Was amazed today to look at the download stats: 15,909.....
[Magisk] Pirateguybrush:
Stopped working for me the other day. Pixel 4, March update, with this fix installed.

Is there a known workaround?
[Magisk] 73sydney:
Not at this time, see above post....TopJohnWu's tweet. This happened temporarily a few weeks ago, but he thinks this time its permanent...and theres no easy way around it as far as he knows, he's suggested people with powers beyond his to break TEE

Some older devices seem to be unaffected, like mine..Note 4, still passes all tests
[Magisk] Pirateguybrush:
Urgh, so that's it? No more Google Pay for rooted Pixels (unless there's a major breakthrough)?

Can anyone explain why they're making this so difficult? Rooting seems to be officially allowed (on the face of it), and you do so with the understanding that it comes with increased security risk.