yashsingh1/xdaforums huggingface dataset:
[Magisk] Lord Sithek:
Plus setting up WearOS watch from the scratch, as for side effects
[Magisk] chiteroman:
Private build. 🤣
[Magisk] liyafe1997:
Thanks for letting us know! I don't have a WearOS watch :(
[Magisk] liyafe1997:
I don't know actually, I think it shouldn't be, I guess Google has other checks...
[Magisk] Dehumanizer77:
I'm getting device integrity again with Poco F3 on Pixel Experience ROM.

But is there a way to get google wallet working again without clearing all data? I've read someone was talking about some tricks...
[Magisk] mac796:
I just wait. Usually starts working for me. But I'm not in any hurry
[Magisk] forum_dyskusyjne:
I have to do update information.

Mi 9 Lite version 12.3 not works (Stopped working 10 minutes ago).

Version 13.0 works.

ROM: xiaomi.eu_multi_MI9LiteMICC9_V12.5.5.0.RFCCNXM_v12-11
[Magisk] MASAN:
It did work for me (Samsung A52s running PE). I have just one question. Is this a band-aid solution likely to be fixed in 48 hours or will it last?
[Magisk] TraderJack:
Ask Google.
[Magisk] bakaekze:
What I don't understand is why XEU made it that way so it's impossible to fix by a module. I wonder what they will do now, rebuild all roms again with the new fix or remove the fix altogether so that users can patch themselves via module? Or just say f... it and keep it non-working as it is haha
[Magisk] luqman98:
Thanks for the fix, hopefully it will last longer, who knows 👀

Both my Redmi Note 11S 5G & Redmi 7A now passes "MEETS_DEVICE_INTEGRITY" again
[Magisk] G-ThGraf:
Thank you very much @chiteroman.

All works good on Pixel 7 with A13.

Wallet is back :love:
[Magisk] TraderJack:
Would be nice to get some clarification from someone in "the know" as to how this fingerprint check thing works.

Again, to recap (and I may be getting something a bit wrong here), but using a classes file we can inject a different fingerprint to a certain app, in this case the Google apps (not sure which ones we inject into specifically, GSF?). This fingerprint basically causes the TEE verification to failback to say the device only supports basic integrity and therefore that is all that is required to pass the checks.

My understanding is that fingerprints are per device TYPE, not per device. Meaning they are not unique. A specific device running a specific ROM has a specific fingerprint and every user with that device/ROM combination has the same fingerprint.

Correct?

If so, as has been asked more than once in this thread: If Google blocks a fingerprint... and I'll pause here to make sure we understand what that means.... I'll assume it means that they either block that fingerprint entirely from working or at least they block it from only being able to use failback to BASIC/DEVICE integrity? But, in any case, if they block it - doesn't that mean that every legitimate user of that specific device/ROM type is going to be blocked as well? Even if they aren't unlocked and rooted? If so, how can Google do this? I don't mean technically, I mean are they really preventing all users of this fingerprint from being able to pass PI then?

It is clear that a working fingerprint (and whatever else is being done by this fix) can stop working only due to changes on Google's side. By that I mean they are not updating anything on our devices when they suddenly stop working.

So the question here is:

Are they changing the request? I.e. whatever is being sent in the PI API? I don't think so (?)

If not, that means our devices are sending the same thing as before, again meaning absolutely nothing changed on our devices (including how they receive and respond to the authentication requests).

The only thing changing is how Google responds to that request, and in this case it seems the response is to fail device integrity when they break the fix.

So, is all they are doing to break the fix just blacklisting a fingerprint? And, if so, refer to the questions above about BL legitimate devices as well.

What else is going on that I'm missing?

@chiteroman - your input is appreciated :)
[Magisk] Srebb:
Thanks! Much appreaciated. It works on xiaomi.eu v12.5.2 (had before USNF Mod by displax, which I uninstalled and installed this integrity fix v13)
[Magisk] xSnowLeopardx:
I can officially say, everything I need/want works now :)

Revolut, GWallet, etc. (until it's ruined by the big G again of course)

Thanks again for the GPS tip.
[Magisk] computer_user:
As always, thank you for your work on this.

Very sad to see it closed source now though. I hope we can come up with some way to ensure the binary is always good and is never malicious. What if your GitHub account is compromised? Then a bunch of people would install this low-level module that people can't easily verify.

Perhaps consider allowing a trusted group of experienced members to have access to the source and allow them to vouch for any binaries that are released. They could do a review of any changes and make sure any binary released matches their compilation of the source you shared with them.
[Magisk] chiteroman:
I don't know but maybe...
[Magisk] xSnowLeopardx:
@chiteroman

Thanks for all the help and dedication, mate. Do you have a way of us supporting you? I want to help. Like an LTC addy? (Can't do it via PayPal, unfortunately.)
[Magisk] yoongdeer:
Yes this omg dunno how many times have to do it the part whereby have to reset wear os watches dam them

Thanks for the updates
[Magisk] Lagartixo:
Many many thanks. Works on Xiaomi Mi 9 Evox 7.9.9. After flash clean data of play services and reboot.
[Magisk] iwearthebelt:
Just in case anyone is looking for this info, the Play Integrity API checker app isn't passing for me with new version 13.0 (the app probably needs an update) but TB Checker passes all of them except strong. I went to the Bank of America and had no problem logging into my account with tap and pay. Seems to be working fine. Good job on the update!!!
[Magisk] sir_bazz:
Employee of the Week, (again).

Thanks for sharing your work.
[Magisk] bakaekze:
Google throttles API requests if many people use it. App is free so don't expect it to have enterprise limits.
[Magisk] TraderJack:
Is it actually telling you its not passing or are you getting the API error? Since it was giving everyone else the API error a few hours ago, I expect that is what it is giving you. Has nothing to do with it not working or needing an update, has to do with it being the most popular app to check and overloading their daily API limit with Google. Been mentioned at least 5 times in the last week.

The only test you really need to do is the one that is built-in from Google Play App (General > Dev) after you unlock Dev options using the build # click trick in the app.

As long as you pass BASIC/DEVICE integrity it means the PI fix is working for you.
[Magisk] Princknoby:
Guys, is Magisk in the CANARY version a requirement?

Thanks
[Magisk] bakaekze:
No, 26.4 stable
[Magisk] alk753:
Thank you for the hard work on this.

Working on OnePlus6 with crDroid 9.10 (A13), Magisk 26.4 stable.
[Magisk] Princknoby:
Thx man!
[Magisk] me_droid:
Amazing work being done here, thanks chiteroman! I haven't rooted since Pixel 2 - now I've upgraded to Pixel 8 and find that things have changed to the point that I need some advice. I rooted without much pain but now am experiencing these Play Integrity issues. I think that I may have overdone it with the Magisk deny list, so I wanted to ask, aside from banking apps and some others (even Starbuck's and Amazon app have given me some vexation), what google items need to be in the deny list?
[Magisk] WhoIsJohnGalt1979:
Except for wallet, no Google apps, no play store no gms etc.
[Magisk] TraderJack:
Wallet does not need to be in either.

Currently the only thing that you need to put in the Deny list are your 3rd party apps like your banking stuff or anything else. For some reason my County Library doesn't like root...so I need to add that...but no Google stuff.
[Magisk] iwearthebelt:
Yeah I'm getting the API error in the Play Integrity API checker app but the TB Checker app is passing Basic and Device. I figured in stead of counting on the results I'm getting from the apps I'd head to the bank and test it myself and sure enough, it's working. Still need to try it for a purchase and see what happens but have a feeling it's working fine (although I might be wrong). Guess I'll find out in the morning.
[Magisk] TraderJack:
Really there is only one thing you need to do to check:

Open Wallet, go to your icon in the top-right and click "Tap to pay setup" in the menu.

If it says something like "You're ready to tap to pay with your phone" then it is working.

If it says something about your device failing to meet requirements, then it isn't working.

If it is NOT working, then you need to verify you pass both BASIC and DEVICE integrity with one of the checker apps (or preferably the in-built Google Play check option). If you are passing those then you need to either clear storage of Wallet and reboot (and readd cards), or do the cache clear, airplane mode, move date ahead trick mentioned several times in the past week in this thread.

I think the above has been pretty definitive to me, although one other sure fire check is to remove and re-add your card (or add a new card). Yes it takes about 60 seconds (maybe up to 2-3 minutes if your bank requires you to call to get the code) but the ability to add a card basically equates with the ability to use it as well.

If you don't pass BASIC and DEVICE then either you are an Edge case, or else Google changed things again and you should re-visit this thread because likely multiple people are having the issue.
[Magisk] trax69:
Op11 android 13 works.

@chiteroman:

Thank you for sharing your work and making root functional. I appreciate your efforts . Thank you for your hard work and dedication.
[Magisk] iwearthebelt:
I'm good, It says you're ready to tap and pay with all checks.
[Magisk] digger16309:
Play Store checker says: Meets/Meets.

P6P, A13 Sep

Great work - thank you!
[Magisk] nadeemakhtar1994:
Google play services and Google play store - should I add them in magisk deny list?
[Magisk] nadeemakhtar1994:
Can someone provide a fix. i installed the modded play Store via lucky patcher and since then the 'GOOGLE play system update' option disappeared. I immediately reinstalled normal Play Store again however the google play system update option had not come back and still missing. How to get it back???
[Magisk] DougMG:
LP is a definite no go on XDA so no one is going to touch this.
[Magisk] Utini:
Working again, thanks!

I would still suggest to get a Telegram News Channel so ppl get notified about updates.
[Magisk] nadeemakhtar1994:
No go why?
[Magisk] Nergal di Cuthah:
Because it allows nonfree apps/features to run free, amongst other concerns
[Magisk] Sage:
this looks great -thanks for the efforts!
[Magisk] krkhaha:
No bro. All the time same problems
[Magisk] krkhaha:
Problem is because my device is certified, safetynet pass, basic integrity is done and still Google wallet show me randomly I can't use it because of root. There was much better on A13 and safetynet fix. Everything was worked perfectly
[Magisk] Nergal di Cuthah:
Neither of those things would have saved you this week. Google flipped switches on the server side. Android 13 and especially usnf were hit just as hard. i switched from usnf mod 2.0 to pif version 12 when the first switch was flipped.
[Magisk] clonato:
Hi All

is it correct?

View attachment 6033941View attachment 6033942View attachment 6033944
[Magisk] Koile:
looks good
[Magisk] clonato:
But, on wallet, i can see "Phone doesn't meet security requirements".

when i see that, usually i'm not able to pay
[Magisk] voetbalremco:
Only when you get the error upon opening Gpay.

This error will resolve itself and payments are fine.
[Magisk] awarexda:
In my case, I see "Phone doesn't meet security requirements" in wallet's settings (with no relevant popup message while opening the app) BUT still I can pay with it. Weird happenings...
[Magisk] 130ryokohama:
I'm getting the same thing

no other modules installed other than PIF v13
[Magisk] clonato:
Thanks

i will test it in a few hour and i let you know
[Magisk] greg.chalk:
I confirm. I have the same behavior. And I also can pay with wallet. I just tried it.
[Magisk] makeyourself:
You might have to clear data of Google Play Services. Although some have said it corrects itself in time if they just wait.
[Magisk] askylitangel:
Am on a Pixel 7 Pro with Android 14. Installed the latest fix and getting this come up. Not sure on what to do next
[Magisk] mehgancangweh:
View attachment 5964163

Hey just tested v5.0 is looking sick :D

But will this type evaluation causing any trouble? if so how to make it basic?

because i normally get it "BASIC" from old kdragon

many thanks :)
[Magisk] DanGLES3:
It showing hardware backed is fine, it's happening due to the bug in the attestation process used by this module that allows strong Integrity to pass (hardware backed Safetynet and Strong integrity are the same thing)

So the check returns hardware backed for Safetynet
[Magisk] Magdalenkaruda734:
Hi
[Magisk] mehgancangweh:
That's pretty much explain my curiosity : )

Thanks for all good contribution! (bookmarked this thread)
[Magisk] Ipsav8:
Working good on OnePlus 10 pro and OnePlus 8, both on android 13.

Thanks a lot!

It's passing all 3 and gpay is working normally (y)
[Magisk] vindicatorr:
Frustrating... I went ahead and said f-it, and did:

a factory reset on my device

flashed stock boot.img to both slots

pm installed magisk 26.1

patched boot.img

rebooted to flash patched boot.img to the active slot

enabled zygisk,

added this 5.0 module (and AAC (battery charger))

added my wifi

created my account

downloaded play integrity, and got the same "UNEVALUATED" responses I've been getting since some unknown change when I tried to use google wallet/pay a couple of weeks ago.

Is anyone else getting green passes with the regular AOSP-13 GSI?
[Magisk] JosFlix7:
Working correctly on Moto G7 Power (Ocean), LineageOS 20 Official c:

(Module v5)
[Magisk] acwcanada:
If not coming to the thread and read all the message since I left a couple days ago I wouldn't realize that the module is already to v5.0! Since it is not upgradable through Magisk's module list, would it be possible to include a version in the OP? Right now without going to the github, people wouldn't know what is the updated version. Hope this request won't get me in trouble here. Thanks
[Magisk] immortalwon:
Xiaomi.eu ROM failing strong. This module is probably next
[Magisk] osm0sis:
I mean, it was basically based on a Play Integrity bug, so it wasn't long for this world. 😛
[Magisk] Usama-CW:
Great Work!!! ... Here's my fork for Poco X3 Pro LineageOS Users
[Magisk] osm0sis:
...Why? Also, maybe read the license you deleted, it says you must include it.
[Magisk] Usama-CW:
Hide lineage props >:3 ... Thanks for reviving ':3
[Magisk] zgfg:
He made special version for Xiaomi.eu (spoofing only ro.product.first_api_level,

no.need to spoof other props as in generic case for other phones - safer, to avoid potential conflicts), find and try first with that version:

PlayIntegrityFix-XIAOMIEUONLYzip
[Magisk] wilsonhlacerda:
Better release a standalone "LOS Hidder" module, that works with Vayu, Surya and any other (official) LOS device, no matter if running LOS20, LOS19, LOS18.... module really focused on hidding custom ROM itself, LOS. This is a thing LOS misses a really good one (probably will go further than props setting only). And not mix in it any other feature, like attestation or so.
[Magisk] Lord Sithek:
So, seems like Google is quick. Strong stopped be passed on 2 of my devices, probably 3rd as well but I couldn't check yet
[Magisk] beeshyams:
Yep on Pixel 6a, strong integrity passed a few hours ago and now it fails. This fix by Google was expected but must admit it was fast
[Magisk] 에어 론 리:
module doesnot work.

exactly, works only till 4rth device reboot. next time show RED "MEETS STRONG INTEGRITY"
[Magisk] chiteroman:
View attachment 5964713View attachment 5964715

Seems Google patched this
[Magisk] Spartacus500:
Today my Samsung same 😔
[Magisk] clonato:
all cleared but still the same
[Magisk] bartes9:
Oneplus 6t, android 11

everything works

thank you!
[Magisk] samtruman:
Many thanks to @chiteroman, with v13 google wallet works again.
[Magisk] amk316:
Thanks chiteroman v13 work grate but wifi calling stoped working

V12 did not have this problem
[Magisk] chiteroman:
Which device and modules do you have ?
[Magisk] askylitangel:
Ok so ignore my previous post. But my Google Wallet comes up with the error message about not being able to use contactless and my Barclays UK app has logged me out and refuses to work anymore
[Magisk] amk316:
S23

View attachment 6034013
[Magisk] Gaalpos:
Poco F3, Xiaomi.eu. nothing is working for me: no payment, no Netflix
[Magisk] pndwal:
This is correct...

Not strictly correct... Only a mismatch (with Google listed prints for hardware backed verdict enforcement) is needed aside from being a print that will pass on a given device; many users initially used USNF + MHPC to globally spoof such mismatched props, eg many Android 11 users simply spoofed A10 props for their devices (and MHPC automatically aligned to security level prop) when Google began using fingerprint props for enforcement...

It's nothing to do with being pre-TEE or even pre-Keymaster 3. More in next post...

Even same device works...

True....

That's pretty accurate... I don't think we can say fingerprints have been invalidated for deviceIntegrity purposes across the board either..

Since devices for which they were not generated have no business using them (they are used to validate CTS/VTS for specific devices after all), it's much more likely (and hardly surprising or even unfair) that Google is simply performing some checks to invalidate passing PI verdicts where the fingerprint certification is bogus (effectively stolen)! 😆...

It's probably just a simple comparison of other props too, eg the API sees the globally set fingerprint and others per:

View attachment 6034010

... How easy would it be to compare print or other with the print GMS's PI API sees and prevent use of any mismatched prints not set globally?

Seems Google have only disqualified prints on a per-abuse basis however, likely comparing print, model or other props... This bears out @osm0sis's point that Google is really not trying to work against the 'white hat' modding community (at all), and are really inviting us to work smarter... Enough said? 🙂

I think we have a pretty good idea... Which is why user configurable USNF/PIF also has merit...

But good point, at least with that in place, I doubt closed code will be of much benefit... Google understand their own mechanisms anyway... We can hardly hide what we know of it...

Hope the comments above and the little historical synopsis in following post helps... And thanks for current fixes! 🙂

🤠 PW
[Magisk] mmbaknnba:
As expected & was stated by @chiteroman at the GitHub release page. So please kindly ask the rom developer.
[Magisk] sawdoctor:
Slightly OT but i honestly don't know the answer. If my phone fails device and Google pay stops working again will this affect Google pay on my pixel watch? I'm guessing as my watch has its own Esim isn't rooted and can be used without my phone that wallet should still work?
[Magisk] Fiufsciak:
Damn, looks like they've changed something again, Device Integrity started failing
[Magisk] zgfg:
<post below>
[Magisk] Fiufsciak:
Am I? It did work just a few hours ago
[Magisk] 130ryokohama:
i just tried this now and its the same for me.

google wallet still says i dont meet security requirements
[Magisk] zgfg:
For the record, my Device Integrity fails since yesterday and this module is not valid for my ROM

But I didn't manually open Wallet, I didn't test PI through Playstore and since yesterday I have still so far several times successfully paid by NFC

I just receive notifications from GPay and my banking app that it was paid and I swipe them aside. I even paid by scanning a QR code

Probably it will cache out soon (24h or so), but at least I was still using it for one full day
[Magisk] immortalwon:
No they didn't. It's working on my android 11, oneplus pro 9.
[Magisk] Lada333:
Might stop working in a bit, afaik Google runs a check about every 24 hours to see if they can "invalidate" your device.
[Magisk] FIERA03:
Have they already cracked v13!? WTF
[Magisk] gentano:
Which PIF version? Only 13.0 works.
[Magisk] Lubo99:
yes after I have fixed this 4 days ago it is back again. anyone knows how to fix this? edit 13 version works just update it...
[Magisk] Lubo99:
seems like it...
[Magisk] clonato:
Hi

it works
[Magisk] osm0sis:
Pixel 8 Pro still working fine with v13 here, all passing that should pass.

That said, hopefully we can get userspace modifiable props (including choosing which props to spoof) soon, and that way we can experiment more easily and make our own unique working configs.
[Magisk] chiteroman:
Google unfixed again ?
[Magisk] tutibreaker:
the op says clearly that, this WONT wont in EU roms, dont you read ?
[Magisk] shoey63:
Not a problem (yet) on Pixel 6.

A14, November security update.
[Magisk] DanGLES3:
Why you ask?
[Magisk] V0latyle:
Still passing 2/3 with v13.0 on my stock rooted Pixel 5.
[Magisk] ghedo75:
hi, I have a Xiaomi 11 t pro with elite lite 14.012 AA rom but before I had the Elena te rom 14.04 global that also stopped working with Google wallet, it tells me that the device does not meet the security requirements, I tried to mount the module PlayIntegrityFix_v13.zip on magesk but it doesn't work, it's always blocked, solutions?
[Magisk] rogers11:
Dto. with LOS rooted Pixel 7a.
[Magisk] sawdoctor:
Ditto on pixel fold android 14 beta. Just used wallet to fuel up
[Magisk] Lubo99:
yep 13 works I can confirm...
[Magisk] knasiotis:
13 doesn't work for me, mi 11 ultra eu rom latest stable

edit:I know i've read the release notes I'm just desparate
[Magisk] immortalwon:
The reason for the .EU roms not working is because they incorporate the Play integrity fix in the rom itself, which has already been patched. You will have to wait for the rom devs to fix or simply use a rom without built-in bypasses.
[Magisk] chiteroman:
Nothing important Google :D
[Magisk] immortalwon:
here we go again, please keep it secret XD
[Magisk] bakaekze:
please elaborate
[Magisk] FIERA03:
I'm convinced this is due to Bootloader Spoofer (translation: you should not be published just yet!!!).
[Magisk] chiteroman:
No lol
[Magisk] immortalwon:
I know what it is, but I don't believe writing here. Several others mention the method before but it will be patched super fast if it's written and confirmed here.
[Magisk] V0latyle:
Same.

I'm generally not a fan of closed source Magisk modules but maybe this fix should indeed be closed source.
[Magisk] thisislukas:
v13 works fine on NothingOS 2.5
[Magisk] Vision:
That is important, this mean can pass and 3 ?
[Magisk] chiteroman:
Yes
[Magisk] Vision:
Nice, I have Xiaomi Poco X3 NFC Android 10 with unlock bootloader Magisk Delta v25.2, i see in your image say have bootloader locked with hardware in android 10 i think
[Magisk] NMaverick:
Previous one worked, this one doesn't. Doogee V30T on Android 12+Magisk 26400 + PIF 13.0, 2 out of 3 pass, strong fails (like before).
[Magisk] bakaekze:
This is how it's supposed to work, without strong
[Magisk] immortalwon:
Can I send you a PM boss, want to confirm something please?
[Magisk] NMaverick:
I know that, but the Wallet fails.
[Magisk] V0latyle:
Clear cache for Wallet and GPay. Clear data for Play Services. Restart.
[Magisk] makeyourself:
Ha? Working fine here at the moment, passing Device & Basic Integrity with TB Checker and Wallet says I meet its security requirements.
[Magisk] immortalwon:
It fails because you need clear storage+cache of: Google play services, Gplay store, google services framework. Make sure you pass the 2 green check marks first. You will have to re-add your credit card.
[Magisk] GROOVYJOSHCLARK:
Pixel 6 Pro (raven), failed with the previous module, updated to today's release (v13), all set running ROOT / LOS. Meets both device/basic integrity (and of course Play Certified) with the latest version on Android 13.