yashsingh1/xdaforums huggingface dataset:
[Magisk] shoey63:
Yeah it's busted.

Soon as you spoof a locked bootloader with MHPC, Shamiko or whatever, everything passes. Momo, Key Attestation and now Play Integrity API Checker
[Magisk] mko000:
Thank you!

You have a typo in the app name 😗

"Play Intergrity API Checker"
[Magisk] 1nikolas:
That's what happens when you rush to publish an app 😂

I fixed it but it will take some time for Google to approve this groundbreaking change
[Magisk] martyfender:
Com.google.android.gms.unstable is hidden by default, even in Magisk v18.1. And don't mistake that for the beta version only of play services. I believe it has to do with safetynet.
[Magisk] Evo_Shift:
A Google play services update of some kind today (can't remember exact wording of the notification) fixed the issue for me. I never tried any work around and after the update I was able to buy a snack at a vending machine. Play services is on version 15.1.80.
[Magisk] deepak8151:
Thanks for the workaround. Just wanted to check.. Is it gms or gsm???
[Magisk] joeyddr:
gms
[Magisk] krs360:
Same here. Been working fine for a week or so, then failed embarrassingly on me this morning when I didn't have my cards with me.
[Magisk] coolbeans2016:
Never had to post on Magisk. Fresh install of kdz bringing security patch up to 3-1-2019 for Nougat 7.0 on a LG Stylo 3 Plus. Flashed 18.1 zip and nothing. Installed MM 7.0 but it didn't detect it. It downloaded 18.1, flashed, everything is fine with root & safety net check. But Google pay detects root. I always go under 'hide' and put all Google services as hidden from root.

Is this the issue everyone's reporting? And is there a fix?

Sorry if this is 'noobified'...

zach

I have the log file if this is the correct place to post...
[Magisk] nnjimmy59:
I had the same problem. I used TiBu to clear data for Google Pay, Google Services Framework, Google Play Services, and Pay Pal. That did the trick and GPay works again. I use PayPal because my bank doesn't support G Pay.
[Magisk] pedritopl:
In my case uninstalling Magisk 18.1 and installing Canary build 18.2-8893cbd6 (18119) fixed the problem without any other actions necessary.
[Magisk] BetaHydri:
I used for my Mi Mix 2s a custom kernel like polaris-canting-4.9-0.2.zip without Magisk or other rooting method. I was able to enroll afterwards my card into Gpay but I didn't tried yet if payment will succeed.

Gesendet von meinem Mi MIX 2S mit Tapatalk
[Magisk] stefr07:
Same for me. It's fixed.
[Magisk] mezerr:
Ugh. I upgraded to Magisk Canary.. and now I don't get the root error In Google pay, but instead get this.. wtf?
[Magisk] x-raf:
In my case too LineageOS 16.0 shamu :)
[Magisk] caluz78:
Here everything works with GPS 14.7.99 and app disable services to prevent GPS updating.

No magisk and app hide.

Magisk 18.1
[Magisk] RealZac:
I followed the instructions in post #5 yesterday, except I didn't need to install Google Play Services 14.7.99 apk, because after "uninstall updates" it already was on 14.7.99.

Registered Paypal "card" again and everything worked fine since then. No auto-update, no errors.

I'm on OxygenOS Open Beta 14, OnePlus 6.
[Magisk] cbarai:
I had issues with Play Beta, tried steps described in this thread and still didnt work. I Uninstalled and reinstalled Play services updates, GPay and even the disable background data.

Finally just upgraded to Magisk Canary & within magiskhide enabled all of Google play services. Thats all of it now back working and I'm even back on the Play Services beta (16.0.86) again without any issues. Looks like it was just magiskhide not hiding all the modules for GPay within Google Play services.
[Magisk] gennadii:
Canary build. Made everything as in the 5th post, but no result, cant add cards. Does root access required?
[Magisk] sash11:
If your phone is not rooted, what are you doing in this thread?)
[Magisk] gennadii:
I've just unlocked bootloader, flash twrp and pixel experience rom. Everything worked fine, until few days, when google pay stopped. So I flashed magisk, but what a about root - I don't know. So it's required? If yes, is there any guide?

Upd: okay, magisk rooted the device, noticed :)
[Magisk] DanRyb:
I had gotten this working on Magisk Canary (build 18119) a few hours ago (at least in term of adding/activating cards) with Google Play Services 16.0.86 beta. There was then an update to Magisk Canary to build 18120, which I applied. After that I went into Google Pay and tried to add a new card, and got the rooted message. I had to wipe data on Google Play Services, which in turn reset all my cards in Google Pay (I did NOT wipe data for Google Pay FYI). I tried adding in my debit card back to Google Pay and it did work. So just a heads up, YMMV.

EDIT: I thought it was the Magisk Canary build update that triggered the failure, but it looks like it was a simple reboot. I just rebooted phone, tried to add in a new card and got the rooted message :/ The instructions said 16.0.86 beta worked with canary but this doesn't look to be true. At least not surviving a simple reboot of the device.

EDIT 2: So I went back into Magisk Hide and noticed I didn't have Google Play Services framework checked off. Did that, wiped data on Google Play Services and Google Play Services framework, rebooted, and it seems to still be working (added a new card). Rebooted again and tried adding another card, still worked.

EDIT 3: Nope, lol. Something else going on. Not working again after a few reboots.
[Magisk] Itachisasuke:
Just had an issue trying to pay for gas.

"You can no longer pay in stores with Google Pay"

I just had a successful transaction on Tuesday 12 March at the same place.

Pixel 2 XL

March 2019 Security Update

Magisk 18.1

Magisk Manager 7.0

Google Play Services 15.0.90

Going to attempt the Magisk Canary Build and try the vending machine at work Monday.

Based on all your testing looks like we'll be waiting on a fix from the main man [MENTION=4470081]topjohnwu[/MENTION]

Edit: I should note that SafetyNet and CTS Checks all pass no problem.
[Magisk] borisSweden:
With the recent changes I still don't see a gappsless fix. Thx and have a good day, will get a third party devices for payment.
[Magisk] okij:
What are the steps to spoof a locked bootloader with MHCP or with Shamiko to get hardware attestation (meets_strong_integrity)?
[Magisk] intellq:
is that even possible? if so, i'm up for it :)
[Magisk] pndwal:
🤔... A Google-app-less fix? For Google Pay? ... It's a Google app too... SafetyNet API and new Play Integrity API are part of gms (Google Play Services) also... PW
[Magisk] shoey63:
Just activate and test. It's device dependant. You might get lucky.
[Magisk] 73sydney:
I had too much respect for you to do some sort of "ermahgerd you have so much intergrity" meme thing

also im the king of typos due to nerve issues in my left arm meaning what my brain sends to hands isnt what always appears onscreen :)
[Magisk] 1nikolas:
Thanks Google! So apparently I can't put Google's docs links on my description but I can put random GitHub links.. And this took like 4 days
[Magisk] loshabih:
how to run this test??
[Magisk] zgfg:
The author of the Play Integrity API test has answered about his app right the last post before your

Follow his posts back, read and you will find the link to his Early (Beta) version of the app on Playstore
[Magisk] loshabih:
Thanks for your reply, I'm not asking about API checker, I'm asking about how to run test from GPay or wallet on the post i replied to.
[Magisk] 1nikolas:
Menu -> Tap To Pay setup
[Magisk] Vivek_z0o:
How to fix this
[Magisk] Displax:
Update GMS and Play Store or install GAPS if not installed.
[Magisk] zgfg:
ROM with GApps (Google Play Services)?

If not, not sure would it work (something like MicroG) for the Play Integrity API
[Magisk] Vivek_z0o:
gms updated but I'm not using gapps

Thanks you
[Magisk] Vivek_z0o:
Thanks you
[Magisk] patrickneil:
Hello helpful folks, I've been stumped by a very specific issue since Google made this recent switch to Play Integrity API. One specific credit card still does not work at one specific retailer. It worked before the switch, when I seem to have been one of the first here to notice their contactless pay failing on June 20. Like others, I got things working again with Props Config and then USNF 2.3.1-mod, except at this one retailer with this one card. The card works in Google Pay at every other retailer I've tried, and I can use other cards in Google Pay at this retailer. And I can tap the physical card at this retailer and that works. I've tried dozens of terminals all with the same result. I've removed the card completely from my Google account and re-added it twice, which gets me a new virtual account number each time, and that's all that the retailer should be seeing, so I don't know how this retailer remembers to reject it, even if they saved the old virtual number in some database of cards on rooted phones to reject.

This is very frustrating because the retailer is the public transit system in my city, and holding up the line while I fish into my wallet or try to change some setting on my phone is unappreciated here. Also because this is the card that I get 5% back for using there plus an added discount for using it mulitple times in a week. I know how petty this is, that I can either use a different card on Google Pay or just not use Google Pay here, so I'm mostly posting in case someone else is running into a similarly specific issue now or at some point later and has ideas.

If it matters, I'm on a Samsung S10e, Android 12, passing SN, Play Store Certified, all the checkmarks in Google Pay's contactless settings page plus Device Integrity and Basic Integrity on 1nikolas's checker. Thanks!
[Magisk] Fishawy:
Just an FYI, Google Pay - now Google Wallet - gave me the "Your device doesn't meet the security standards" warning when I attempted to activate the "https filtering" option in the App Management section of AdGuard. Disabling it allows the app to run normally and restores the ability to add cards again.

Thought I might share this here - as one of the million reasons why - if anyone comes across similar issues.
[Magisk] vMAC:
Is there a fix for this? I have Pixel 6 Pro and I have the same things checked. Can't pass MEETS_STRONG_INTEGRITY.
[Magisk] zgfg:
Not. It's been extensively discussed.

Hints to search and read: TEE = Trusted Execution Environment.

Particularly, if you 'fix' that for the last TItan, you could ask for 250K - 1.5M $ reward from Google
[Magisk] pndwal:
Since many are asking:

I've posted some information about Play Integrity MEETS_STRONG_INTEGRITY being akin to SafetyNet Evaluation type HARDWARE with CTS Profile match, but since it became a WOT, I put it here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87274009

😜 PW
[Magisk] shoey63:
Anyone have any information on whether or not Google intends to (eventually) enforce MEETS_STRONG_INTEGRITY

for contactless payments via Wallet/Google Pay?
[Magisk] zgfg:
Apparently not because many peoples confirmed using Wallet by passing only DEVICE, not STRONG

But they can change anytime they want - for the phones they decide to
[Magisk] pershoot:
I just upgraded to Android 13; Bramble. No issues (USNF 2.3.1-MOD, Latest Magisk + Zygisk, new Wallet app.).
[Magisk] tangcla:
I just updated to Android 13 final on my Pixel 5, and now Google Wallet won't work.

It was working fine on 13 Beta 4 though, and Safetynet passes.

Safety Net Request: success

Response signature validation: success

Basic integrity: success

CTS profile match: success
[Magisk] zgfg:
SafetyNet per se is not relevant for Wallet but Play Integrity.

And you need USNF 2.3.1-mod

If you are not up to the discussion here over the last month, please read the posts
[Magisk] tangcla:
I already had the USNF 2.3.1 module. As I said - it was working yesterday, now no longer working.

Anyway, I resolved it, by clearing Google Services Framework, Google Wallet and Google Play Store data. Not sure which clearing made the difference.
[Magisk] zgfg:
Primarily Wallet. Maybe Services Framework. Less likely, Play Store - Play Services is relevant
[Magisk] tangcla:
Wasn't just Wallet (did that a few times to no avail). So probably the framework.
[Magisk] pndwal:
Out of interest, can we assume you mean you do have @Displax USNF 2.3.1-mod (modified USNF), not official @Kdragon USNF 2.3.1 module?... It would be surprising if the latter fixes Play Integrity w/ Android 13... (I don't need the modded version w/ my Android 10 device however.)... PW
[Magisk] tangcla:
OH. I am using the official one. (I thought you meant module)
[Magisk] pndwal:
Ok, so please get new Play Integrity API checker if haven't already, check and say if you have basicIntegrity and deviceIntegrity... PW
[Magisk] tangcla:
YASNAC?
[Magisk] pndwal:
No... As written, but also in Play Store... PW
[Magisk] tangcla:
Thanks, got it. Pass device and basic, not strong.
[Magisk] rodken:
I always thought that messing with GSF changes the primary ID by which Google knows the device. As far as the servers are concerned, said device was basically factory reset. There are many downstream effects of this, but a major one is that this invalidates the tokens used by any app that uses GCM

-- Which is nearly all the Google apps, and maybe loads of 3rd party apps.

-- Play store won't recognize said device for a few hours or days aside from the fact that logging out and logging in can fix.

-- Whether or not it can cause various Google services to not work is a YMMV issue.

N.B.: Besides the fact that it will not cause Nuclear Warfare - it has the chance of a creating a load of nuisances on said device.
[Magisk] Entity 0:
Hoping push messaging is still working okay for your apps after clearing Google Services Framework, otherwise you'll need to wipe all the affected apps too.
[Magisk] niko26:
Hm, i hab tried this.. No luck this time. Any idea what I am missing? Google Play Store shows that the device is certified.

I have reset Play Store as well as Play Services multiple times. No luck :(

Almost everything related is hidden magisk...

Any idea?
[Magisk] niko26:
Do we need 2.3.1 necessarily?
[Magisk] CSX321:
For Pay to work? Yes, I think it's been the general experience that you need the custom USNF v2.3.1-mod for Pay or Wallet to work.
[Magisk] meiser:
For me, the solution was to also clear the Google app data.
[Magisk] niko26:
You mean the one which is just titled "Google"?
[Magisk] niko26:
2.3.1 is not available publicly yet, right?
[Magisk] zgfg:
Please distinguish 2.3.1 ('official') and 2.3 1-mod (NAMED EXACTLY as that) from Displax - you need that latter one for Wallet

Everything is in the posts in this thread - story about Wallet starter like 3 + weeks ago - hence please read and you'll find
[Magisk] niko26:
@pndwal I think it would be tremendously helpful if you could (re)post the exact steps and order in which to execute them. :)
[Magisk] niko26:
Worked for me without having to clear the data.
[Magisk] niko26:
Let me explain... I had to replace my Pixel 6 Pro and I didn't have any issue with my older Pixel 6 Pro - so I missed all the troubles the others have experienced. So I expected everything to be working as before and I have expected a mistake on my end.

Thanks for the pointers. :)
[Magisk] pndwal:
Well I don't think there's much need to repeat that, but for those searching:

This issue was

contactless payment failure with Google Pay / Wallet stating "Your phone does not meet the security requirements"

irrespective of SafetyNet or Play Integrity status. (Several of us experienced this suddenly, and it predated both new Wallet upgrade an Play Integrity implementation.)...

Further, in tackling this I experienced two issues restoring a working setup;

- Issue where '

Google Pay/Wallet is currently updating' fails to complete

, and

- After restoring app,

Activity list fails to populate

.

I put steps to fix these here:

Initial fix:

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

Resolved Activity list won't populate:

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

Summary (scroll to 'In short...'):

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

😛 PW
[Magisk] meiser:
Yes.
[Magisk] mingkee:
FYI

Previous iteration also affected if you have latest Play Store.

This killed Magisk 23 in Yoga Smart Tab (Q).

Solution: switch to latest Magisk (25.2)

Patch the boot with latest version.

Enable Zygisk and Deny List, and configure.

Add USNF 2.3.1 modified module

Wipe both Play Store and Play Service

Reboot after finished

Grab Play Integrity Checker from Play Store

You should get first two checks
[Magisk] gatharot:
If you rather not lose your cards: try wiping cache only (wallet, play) and paying somewhere before wiping data. Took me a week to realise that mine worked. The Monet engine and my pinkish wallpaper tricked me into thinking that I didn't meet device integrity :LOL:
[Magisk] rfkd:
The wallet app of my Pixel 5 on Android 13 still claims in the contactless paying setup menu that my phone doesn't meet the security requirements (haven't tried paying yet though).

I'm on Magisk 25.2 with USNF 2.3.1-mod (Displax).

Deny list is enabled for Wallet.

Already tried to wipe Google, Google Play-Services and Wallet data without success (credit cards are not lost anyways by wiping Wallet data).

The Play Integrity API Checker shows green checks for basic and device integrity (but obviously not for strong).

I've read through the last 15 pages or so but couldn't find a solution. Any idea what else I can try?
[Magisk] TKruzze:
For many of us it took a day or 3 and it automagically started working.
[Magisk] rfkd:
@TKruzze, you were right, now it works, thanks!
[Magisk] LedgendaryEpics:
Make sure denylist isn't enforcing, you may need to reflash and start again on airplane mode like I did
[Magisk] 73sydney:
Please dont use the term "airplane mode", you'll trigger @pndwal who hates it when i (a fellow Aussie and yet a secret Murican) use it, and he's probably up a bell tower right now (well not right now because its 5AM here in NSW, Sydney), but he might read this later when he's up in the bell tower...
[Magisk] m0han:
Hope it's not a case of bats in the belfry.
[Magisk] pndwal:
(I ain't... but I like it here.)

At least you didn't put ariplane mode here!.. (I didn't really complain about airplane...)

aeroplane modus operandi...

Spoiler content hidden.

... Good data...

Spoiler content hidden.

Plenty of pigeons but...

Spoiler content hidden.

Clock you later AM. 😜 PW
[Magisk] 73sydney:
Spoiler content hidden.
[Magisk] Stillhard:
2 aussies are 2 much

More Ponkles please
[Magisk] pndwal:
Gonna take an effort to keep this on-topic...

How about this; my boss just paid for my lunch at the local musicians club using Google Pay... And it works even in broken hill!... He's not rooted but... Ain't his pigeon... I'll try to talk him round...

It's not the Aperger's mate ...

I googled Grown Man with Teddy Bear... This has no connection with Asperger's... And my best mate is Dutch-Lithuanian-Kiwi... Let's not go there...

Kiwiland's only 3½ hrs in aeroplane mode... Perth's further!...

😂 Haha ... Wadoya spect? ...

(Which former NZ PM invited me to go here with the remark that any Kiwi's crossing said ditch would be doing two countries a service, ie. raising the IQ of both AUS & NZ at the same time?... Aw, forget it ...)

You mean Pidgeon as in Walter Davis Pidgeon?... and I thought I was getting old. 🙄

Careful, quite a few ausies here incl. staff!

🤪 PW
[Magisk] m0han:
try ruru

Spoiler content hidden.
[Magisk] pndwal:
Can I download this?... Just not sure it's the WISEST choice. 😜

Spoiler content hidden.

😝 PW
[Magisk] nikolaos8:
Using this module 2.3.1 mod

Post in thread 'MAGISK MODULE ❯ Universal SafetyNet Fix 2.3.1' https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517

And clearing data in google play services, play store and wallet, i manage to add my cards and not get any "error" messages of root and stuff. I have yet to try for payment, but so far so good.

Thanks again all 👌
[Magisk] dr4go:
@pndwal Finally find the source for it: https://github.com/byxiaorun/ApplistDetector/releases
[Magisk] 73sydney:
thanks

@m0han wouldnt share, likes to keep toys to himself :) :)
[Magisk] m0han:
Well, I got the apk from a Telegram channel (1.0.9 too). I was not sure posting a Telegram link or sharing the APK is allowed on XDA.

1.0.9 throws up more detections for me.

Spoiler content hidden.
[Magisk] pndwal:
'new' branch of this fork is interesting...

https://github.com/byxiaorun/ApplistDetector/commits/new

Original Dr-TSNG ApplistDetector:

https://github.com/Dr-TSNG/ApplistDetector

👀 PW
[Magisk] 73sydney:
i dont even have the Lsposed manager installed, once i set things up i do:

find / -name 'org.lsposed.manager' 2> /dev/null -exec rm -rf {} \;

to try and get round the detections, but on every boot, its back and detected

hidemyapplist merely adds a random suffix to its packagename so its trivial to detect...

and with the random naming trend also trying to hide magisk its not hard now for tools to look for a randomly named folder to pop up on a path... *sigh*
[Magisk] tangcla:
There was a new update to Google Wallet overnight.

I installed it and now Pay is broken again.

I'm now using USNF-2.3.1-mod(Displax).
[Magisk] 73sydney:
Confirmed

I just updated....it no workies anymore :)
[Magisk] samftw24:
Yeah I just didn't update, old version works fine
[Magisk] pndwal:
... Just took update (cos I'm a glutton for punishment!)... All looks the same (good) in app...

What symptoms are you seeing?... 'Device doesn't meet security requirements'?... Failed deviceIntegrity verdict?... or just fails at terminal?... PW
[Magisk] 73sydney:
"Your device doesnt meet security requirements"

I also get 3 red x's in integrity tester as pudding

and for completeness yasnac reports fail on both Basic and CTS

latest Magisk Delta...reinstalled safeynet fix, about to try clearing play data (and you know how much i love doing that as it involves resetting my watch 4)
[Magisk] pndwal:
Ah, so GPay/Wallet is only a symptom (as I suspected)... Ie. Wallet update is evidently a red herring...

I'd be surprised if Google (ever) used anything more than their own attestation APIs; that would be like an open admission that these aren't to be relied on... even though they clearly can't be!...

It'll be interesting to see why some are suddenly experiencing Basic Integrity failures (either API) with USNF enabled... I'm sure there'll be more reports... (All still fine on my Redmi Note 8T w/ A10 MIUI)...

Anyone tried disabling all modules other than USNF to see if S/N Basic Integrity is restored? 😝 PW
[Magisk] 73sydney:
My list of installed modules (i usually have more, but been busy since last clean install):

Busybox

Debloater (Terminal Emualtor)

F2FS Tune

Global Optomised GPS File Replacer (own tweaked version)

GMS Doze

Riru

Riru - IFW Enhance

Riru - Lsposed

Riru - Play Integrity Fix

Swap Torpedo

TrichromeLibrary Squoosh

Viper4Android FX

in other words, the least amount of modules ive ever had on here :)

p.s. fwiw Play Store is still certified...but im going to clear it now anyways also fwiw

p.p.s play store re-certifies fine

p.p.p.s fully unrooting to root with mainstream magisk
[Magisk] zgfg:
Since you run Riru, you don't have Zygisk. Are you running Magisk Delta or just Canary with Zygisk Disabled?

Failing only Play Integrity or also SafetyNet - if failing for SN, what does it say in JSON
[Magisk] pndwal:
So new or old Magisk?... Or Delta?

And can you turn of all modules other than Riru and Riru - Play Integrity Fix (is that @huskydg's, or 'secret' indo build?) and check YASNAC?... PW
[Magisk] pndwal:
Fails Basic Integrity for both APIs... PW
[Magisk] 73sydney:
Delta - only in Riru mode

I did try with the riru and riru-integrity only, no change

huskydgs integrity fix

now fully unrooted and about to install Magisk Canary and try zygisk...
[Magisk] 73sydney:
Okay gents,

Magisk Canary with Zygisk enabled and displax's USNF Fix (Mod) passes everything fine

did have to clear Play data to re-certify

p.s. i even used TWRP to install Magisk (because im a bad boy, and im lazy)