yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
But PI API Checker didn't run yet out if quota today yet- it would show that it cannot test then

And G does not fight against the Checker(s) but against spoofing Device Integrity

But ok, not important.to dissect further, maybe it was misunderstanding about that quota
[Magisk] DanGLES3:
That's not what I'm talking about, I was talking about how they were mentioning that people were seemingly overloading the Play Integrity check app the previous days but they thought it was timing out Google's servers when that's not the case

I'm not saying Google is against the checkers, never have I said that, I just wanted to correct them on the matter related to Play Integrity checker quota he seemingly confused for Google's servers timing out
[Magisk] Pietplezier:
Hope chiteroman can fix it. Donation page is waiting. 😁
[Magisk] sdzkhelince:
Pixel 6, latest Sep Android 13, does not pass.
[Magisk] Prof. Yaffle:
Test build doesn't pass on Pixel 8 Pro.
[Magisk] MMETMA:
Doesn't pass on HyperOS A14
[Magisk] bartes9:
no passs, android 11 :<
[Magisk] rafix96:
Xiaomi Mi11, AOSPA 13 not pass.
[Magisk] oOEDGUYOo:
Pixel Experience 12 on OnePlus Nord - not pass
[Magisk] pacofrancisco:
Hi there thanks a lot for your work but, just tried it on poco x3 pro with crdroid 9.11 (A13), wallet still saying phone doesn't meet security requirements 😑
[Magisk] scottlam1:
I have the same phone it's down for me down for all of us I would suggest updating magisk to 26.4 and using shamiko your setup might make gpay not work also you use shamiko instead of built in deny list enforce
[Magisk] sdzkhelince:
nah it doesn't work
[Magisk] xSnowLeopardx:
Unfortunately no...
[Magisk] pacofrancisco:
Well just try your new fix homee... Not better unfortunately 😟.
[Magisk] Prof. Yaffle:
Still no I'm afraid
[Magisk] Gilg@mesh:
wtf is wrong with Google? do they want people to start buying iPhones??
[Magisk] DanGLES3:
EvoX changed their properties to spoof bullhead, could this also work for Play Integrity Fix? Just curious as I'm not an EvoX user so I have no way to test this

PPU: Another day, another cat and mouse chase · Evolution-X/frameworks_base@bc67db6

The Evolution of Android! Contribute to Evolution-X/frameworks_base development by creating an account on GitHub.

github.com
[Magisk] MarkusTieger:
Still no device integrity...

No pressure ofc
[Magisk] chiteroman:
Seems like EvoX devs found the way to pass DEVICE, I will try to find another fingerprint and update my module.
[Magisk] sdzkhelince:
I'm sorry to ask this, but how long will it take?

Not that I really need it, I'm just curious.
[Magisk] mcreuter83:
Hey, I have to be happy with my Samsung A52s with Magisk root. Everything works perfectly here with PiF

I HOPE with Android14 is the same.
[Magisk] sawdoctor:
Once again i reiterate this. What you do for the community is taken for granted by far too many people and it doesn't get said often enough. Thank you for all your hard work, atm you are more or less keeping the modding community going single handedly, that's an awful lot of pressure on one man's shoulders
[Magisk] chiteroman:
If Google doesn't f*ck us again, maybe 1-2 hours.
[Magisk] Atrumitos:
Fun fact, I was at the grocery store, with my freshly working-again google wallet, when they decided to screw us over... again...

You are doing god's work. Thank you!
[Magisk] ninjakira:
Not sure if it should be mentioned or has been already but using yasnac, I'm still technically passing safetynet, it's just play integrity I'm only getting basic passing, I know there different in implementation but figured that should said lol
[Magisk] joeyhuab:
Big thanks to @saikiran001 for the original change.
[Magisk] DanGLES3:
Good that there's still many people looking into these Play Integrity issues
[Magisk] Utini:
Is there any place to get notified about updates? E.g. a Telegram channel?
[Magisk] xcl1pse:
Yeah using trick from EvoX Dev team made DEVICE_INTEGRITY green again. THANK YOU!!!View attachment 6033771View attachment 6033772
[Magisk] sdzkhelince:
well, now we wait for the module
[Magisk] xcl1pse:
Here's the zip file if you want to test this out...

If you can't pass DEVICE with this module, wait official release from chiteroman

PS: I remove the file since chiteroman already release the fixes. See https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89166033
[Magisk] simplepinoi177:
reminds me of THIS POST :ROFLMAO::ROFLMAO::ROFLMAO:
[Magisk] sdzkhelince:
yup, works!
[Magisk] boneszbo:
Works ;) Thanks you
[Magisk] pwn1ca:
Hmm doesn't seem to work for me. P7P latest qpr beta. Will give it another try, maybe I have to remove the previous version first.
[Magisk] rapidm:
Is this fixed the same way as before? Meaning it is easy for google to block it again really soon?
[Magisk] xcl1pse:
Honestly I don't know. Since the zip is not encrypted, maybe google will take a look if quota PI (using apk) reach limit because the spam PI test
[Magisk] ai024:
Doesn't work for me. Pixel 6, Android 14.
[Magisk] xcl1pse:
Just wait official from chiteroman...
[Magisk] mac796:
That did it for me 👍
[Magisk] pwn1ca:
Did a fresh install. Doesn't work for me :(
[Magisk] spida_singh:
Is it worth keeping this locked down (the source)? We could just be kicking the can down the road?
[Magisk] MrLumin:
I can confirm that it is working for me (Redmi Note 11 - PE+ A13 with KSU)

(funnily though, play store still reports the device as allegedly not certified for play protect, will have to clear data again (for play store) to make the play protect certificate status displaying correctly)
[Magisk] MikeZh:
Works on A12+MIUI13, doesn't work on A10+MIUI12
[Magisk] sxaaa:
Works on Poco F3 (AOSPA) , Thanks!
[Magisk] Clasimodo:
Works on s23 ultra after clear data of Wallet, Google Play and Google Play Services. Yesssss
[Magisk] TraderJack:
Just tried to add a new card today and got an error. Checked and sure enough Wallet said it didn't meet requirements.

Device Integrity also failed. Came right here, got this ZIP and all fixed (for now).

Pixel 3 XL A11

Thanks!
[Magisk] yursub:
На Redmi Note 10 Pro работает.
[Magisk] Koile:
Pixel 4a (sunfish) with Pixel Experience plus: works.

But as this workaround is also publicly available, I fear, that it will also be fixed soon by Google. 😖
[Magisk] TraderJack:
I'm not sure this would do anything. My understanding is that we are just changing the fingerprint, right?

I would think that Google can probably track that they have 10K new users authenticating with a specific fingerprint now.

But maybe I'm wrong. I haven't bothered to look through the code so I'm not sure what else is there, but I think anything we are changing on the device to fix the issue is being transmitted to Google. So even if they don't see the source, the data is all in the packets anyway.
[Magisk] yursub:
СПАСИБО!!!
[Magisk] ELAD098:
Not work for me oneplus 6t

After the update it doesn't let me do the testView attachment 6033801
[Magisk] TraderJack:
I'm sure I knew this at one point, but maybe someone can refresh me.

How is Google "fixing" the issue. Aren't we just mimicking some other device's fingerprint?

If Google fixes is, doesn't that mean they are also blocking a bunch of legitimate devices from use as well?

Is Google just blocking fingerprints? Because it seems to go from working to broken without any updates on the phone end, so it must strictly be what is being reported from our devices, no?
[Magisk] TraderJack:
That is an error with the Play Integrity app, not the fix. Been discussed many times...too many people using it.

Turn on dev options in play store and use the checker there from General > Dev tools.
[Magisk] g1b50n:
What a funny situation...

8:53 PM - payment successfull

9:02 PM - different store payment locked...

So i cross the fingers and waiting for update (:
[Magisk] casouzaj:
Thank you! It's working in an old Moto G5S, running LineageOS 18.1 (Android 11).
[Magisk] esatch:
Seems to work on Mi9 lite + EvoX rom
[Magisk] neelchauhan:
Works great on a OnePlus 11 running LineageOS 20 unofficial. Probably won't work forever, but thanks!

I had to clear Google Play Store and Google Play Services, and re-add my credit card PINs, which I remember very well 😁.
[Magisk] BillGoss:
Use Play Store to check the status, not the PI checking app.

See https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89150915
[Magisk] gfast99:
Not working on OP5T
[Magisk] ELAD098:
Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY]

Build fingerprint: OnePlus/OnePlus6T/OnePlus6T:13/TQ3A.230901.001.B1/1554:userdebug/release-keys

Brand: OnePlus

Device: OnePlus6T

Model: ONEPLUS A6013

TestId: dGVzdGluZy05YWMzMThlMy1kMDBhLTRjYzgtODZmMi02ZjZiODU1MTU0ZDE=

Is ok?
[Magisk] TraderJack:
I notice this fix doesn't have the service.sh and system.prop files that the normal PIF file has.

And yet it seems to work. I assume because the dex file is different (though I don't know exactly how that works).

That being said are those things set by the missing 2 files still necessary?

Also @chiteroman what is the logic behind removing all code and assets all the time? Are you trying to hide what was previously done from Google? Are you taking it down so people don't use a version that doesn't work? Seems a strange way to handle a public open repo. Luckily I still had a copy of an older file I could use to compare, but I'm just curious as to your mindset on this? Plenty of other software goes out of date and needs to be updated, and most (if not all) other devs don't just pull all the old stuff off, they just version appropriately.
[Magisk] TraderJack:
Yes, that's what you want. You may need to do the set date ahead/clear cache for wallet/reboot trick to get wallet to allow. Otherwise you might need to clear all wallet/play storage.
[Magisk] xcl1pse:
Yeah I remove those file since I don't need that. The only difference is the dex file
[Magisk] andronedev:
Labels: [MEETS_BASIC_INTEGRITY]

Build fingerprint: google/raven/raven:13/TQ1A.230105.002/9325679:user/release-keys

Brand: google

Device: raven

Model: Pixel 6 Pro

TestId: dGVzdGluZy0yMTUzOTRlMi00OGMyLTQxYjgtOTNiNy1kMDIzMTA3ZWRkYTM=

Doesn't work for me

With Rosemary (redmi note 10s)
[Magisk] sawdoctor:
Previous versions were removed because he got fed up with people posting that they didn't work. His repo went private today to try and stop Google looking at his code yes
[Magisk] katalinscrob:
Works again! Thanks for your work!
[Magisk] linux.alucard:
Doesn't work on Realme GT NEO2 (RUI4/A13)
[Magisk] TraderJack:
I can easily look at those files and see what they change, but to save me time in tracking down what each thing actually does...can you or someone else comment on why those may or may not be needed (on a per device basis)?
[Magisk] xSnowLeopardx:
Passes both via Play Store check. Wallet misbehaving still :P
[Magisk] TraderJack:
Ok. For the former I would just say...ignore stupid people. The fact that he puts a big disclaimer on the top of his site with something like "Latest version doesn't work" should be enough for someone to realize they need to wait.

I can understand re moving it from here to prevent downloads from random posts, but totally wiping out GH repo data seems extreme.

As far as going private...I mean it's his project and he can certainly do what he wants. But if we can download a Dex file, Google certainly can and I doubt it is very hard for them to see what it is doing.

I don't mean to complain. I appreciate all the effort @chiteroman is doing. Just doesn't seem that this strategy really will have desired effect....but maybe I'm wrong :/
[Magisk] immortalwon:
Guys, Chitero has not even updated P.I fix yet, please be patient and stop spamming the thread. The people sharing the EvoX fix should make their own thread.
[Magisk] xSnowLeopardx:
Don't see why you would say spamming. Besides, making a whole new thread for the EvoX fix is not really efficient, either. We should indeed have patience, but let's not attack people who want to test things. Of course, those who are impatient and only write about that - sure.
[Magisk] xcl1pse:
From May 2023, service.sh made more detection since /sys/fs/selinux/enforce: busybox is modify the time access file, so I remove that (but already fixed by using toybox, but I still remove that). For prop, I don't need that since there's no prop value on my build.prop
[Magisk] attitude12:
I can confirm this works on surya with EvoX rooted.

Was the same here too. I cleared all data of Play Store, Play Services, Play Services Framework and Wallet, rebooted, then it worked.
[Magisk] chiteroman:
An emergency update... Let's see how long it lasts. I imagine that in less than 1 or 2 weeks we'll be here again.

My phone has locked bootloader (I need it that way) and I don't have another device until tomorrow. Let's see if I can find another fingerprint....

By the way, thanks to the EvolutionX devs for this!

The Xiaomi phone I'll have tomorrow will be a special test subject, I'll do all kinds of tests... Hardware_backed, Strong, that sort of thing...

Edit: https://github.com/chiteroman/PlayIntegrityFix/releases/latest
[Magisk] oOEDGUYOo:
Works😃
[Magisk] immortalwon:
That was quick, working as normal once again. But I have doubts about how long it will last since EvoX has it open sourced on github.
[Magisk] chiteroman:
Also I'm thinking about how to implement what @osm0sis mentioned before. It will be very interesting to have everything that can be manipulated in one file, for example "pif.prop"
[Magisk] rErEaT:
Works on Miatoll!
[Magisk] BillGoss:
So I woke up this morning to see Google's changes things again. And, sure enough, I now only pass Basic integrity (see screenshot).

Note that I'm still running PIF 12.3.

I open Google Wallet and, surprise!, it's not complaining.

So I went shopping and used Google Wallet to pay for it and ... the payment went through without a hitch! (see screenshot).

So, on PIF 12.3, only passing Basic integrity, and Wallet payments still work!
[Magisk] Lada333:
Apologies if my question makes no sense, I'm not a developer, but would love to understand what these fixes actually do under the hood and how Google can detect them.

So back when they first started blocking contactless payments on rooted devices, I remember having to need to use a Magisk module and spoofing the device fingerprint (was it the fingerprint?) via a Terminal. But that also meant that if I spoofed my device that way, every app would think I have a completely different device than what I actually do.

To my understanding, kdragon's SafetyNetFix, then Displax's mod, and now your PlayIntegrityFix does also spoof the device fingerprint, but in a way that all other apps aren't made to believe that your phone is a different device from what it actually is.

So, my question is (as has @TraderJack asked in #2071), what does this module actually do, and more importantly, how can Google tell users who use a fix such as yours and users whose device's aren't rooted apart?
[Magisk] xSnowLeopardx:
Do know that you are risking having butchered notifications with deleting data of PSF. I had that and it's not fun.
[Magisk] attitude12:
Yeah, i didn't have that happen to me, thankfully. I'm using nikgapps, maybe that's why. And i kept clearing the data of everything i could to try to "fix" the wallet.
[Magisk] liyafe1997:
I can share a fingerprint from one of my devices I guess it should work. I installed Magisk on that and without any modules like PlayIntegrityFix, just use MagiskHide for GMS, it can pass the DEVICE_INTEGRITY. You can test it if you like.

This phone is LG V20, originally came with Android 7.0, and this is an official Android 8.0 rom.

I guess just need fingerprints from official ROMs of devices that ship with Android 7- (without TEE), the fingerprints from further versions of Android upgrades like 8.0 9.0 10 also should works.

An idea is to make a collection of fingerprints, with different devices and different versions of Android of them, at the first time install the module, it will choose one of them randomly.

I deleted the screenshot as you guys asked... But my opinion: if Google wants to block fingerprints in this way, it is really easy to know the fingerprint from the module zip file we made (just install it and see what the fingerprint is).

And also, if it block lots of fingerprints, it also blocks lots of legal devices...
[Magisk] ai024:
Last update works (unlike 12.3_test) on Pixel 6, Android 14.

Thanks a lot!
[Magisk] chiteroman:
I recommend you to remove the screenshot...

It's better to send all props: adb exec-out getprop > props.txt

Send me that file by private message.
[Magisk] g1b50n:
I can confirm Fix 13 worka

View attachment 6033827
[Magisk] sc00bydoo:
Working great on pixelos 👍 thanks for your hard work
[Magisk] Ostroveni:
Still fails on my S22 Ultra :(
[Magisk] neelchauhan:
Deleted on request.
[Magisk] rodken:
Agreed as to we do not need prying eyes to gain another foothold.
[Magisk] liyafe1997:
I can give you a quick and short answer based on my knowledge, maybe it is inaccurate.

Background story: Google requires supporting TEE if the device ships with Android 8.0+. If you don't know what is TEE you can google that. Shortly, TEE is kind of a "hardware"(actually it is a branch of software running on a secured hardware-supported environment, aka. ARM TrustZone), that can verify some signature from Google, also, if the bootloader is unlocked, it can tell the upper-level software, and also the answer is signed and can be verified. Shortly, the TEE is uncrackable at this moment, at least.

If GMS detects your fingerprint is a new TEE-supported device, it will try to verify the "security" with TEE. If your fingerprint is an old device (ships with Android 7-), probably it does not support TEE, so it will not try to talk with TEE, just do some "simple" verification then it can give you DEVICE_INTEGRITY.

So the things we are doing here is tricking the GMS with a fingerprint that comes from old devices... I don't really think this can be a long-term solution.... Like this time, Google just block it within 1 week. But, who knows...
[Magisk] rodken:
Even though randomization and noise addition, can make it more difficult for third parties to identify and track fingerprints, they don't guarantee complete anonymity from Google with all of it's vast resources and expertise in machine learning, but it's a step in the right direction.
[Magisk] xSnowLeopardx:
Don't want to delete data for GPS and GSF, since I will have broken notifications again lol.

How do others go about deleting cache and/or data after installing this latest update?

Some screenshots added.
[Magisk] simplepinoi177:
I love how Play Integrity API Checker is putting up a message when checking saying "Error getting token from Google" "The calling app is making too many requests to the API and hence is throttled" "this shouldn't happen".....hmmmm i wonder why?😅😅😝
[Magisk] DD3Boh:
That's not a very bright idea to be honest. What if instead of going for some random unknown fingerprint each week, you and other guys working on these Play Integrity / Safety Net modules, gather around and start actually debugging what Google changed to break stuff? It's pretty clear that the change wasn't just revoking random fingerprints, as that is not doable and it would break those builds even on stock, which is definitely not what Google is doing.

So, since Google is most likely going to continue killing these fingerprints periodically, what if you actually try to focus on something useful, like finding out why these fingerprints are breaking, instead of doing parkour every week and closing sources because you're afraid other people might start using the same fingerprints?

Also, spoiler alert, if Google is actually "onto the community", just flashing your module and figuring out what is happening is a 5 minutes job at most. Just sayin'.
[Magisk] liyafe1997:
I deleted it, actually the first time I wanted to share with you by PM, but if I click your name, it says "This member limits who may view their full profile. ". Is there any other way to PM you?
[Magisk] forum_dyskusyjne:
Mi 9 Lite version 12.3 works perfectly.

ROM: xiaomi.eu_multi_MI9LiteMICC9_V12.5.5.0.RFCCNXM_v12-11

But I had have (the same problem) with Zygisk w version 24.6 Link

I sholud do update to version 13...?? The addition is brilliant.
[Magisk] liyafe1997:
Check this for restoring FCM push notifications: https://github.com/chiteroman/PlayIntegrityFix#make-fcm-push-back-to-work-after-cleared-gsf-data
[Magisk] chiteroman:
View attachment 6033835View attachment 6033834

Thank goodness we still have the Play Store 😂
[Magisk] quini2k:
View attachment 6033838v13 not working for me (oneplus 9 pro)...
[Magisk] HippoMan:
Based on what's explained in the this referenced post, even with knowing the structure and logic of the app, the Googlefrinchians would have a hard time telling whether any given signature which looks like it comes from an older device might actually be a spoofed signature:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89166102

Of course, there might still be other ways for the Googlefrinchians to figure out what's going on.
[Magisk] Lada333:
That makes sense, thank you for explaining it!

I'm left wondering though, if Google bans a certain fingerprint (which if I understand correctly can only be from devices that shipped with no TEE "hardware"), wouldn't devices that are officially carrying that fingerprint that we're all spoofing our devices to have become also "banned"?
[Magisk] chiteroman:
The module does work, but you are all sending requests to Google's servers and they are getting angry 😂
[Magisk] andronedev:
Work nice on redmi note 10 s

Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY]
Build fingerprint: google/raven/raven:13/TQ1A.230105.002/9325679:user/release-keys
Brand: google
Device: raven
Model: Pixel 6 Pro
TestId: dGVzdGluZy02MWUzZmEwMy03YmYwLTQ3MjYtOThlOS0xNjk1MWI4ZTkyOGI=

Thanks !!
[Magisk] watoan:
Latest one works on Moto Edge 30 Pro

BASIC and DEVICE passed

However, as I have cleared the wallet data so I have to add cards again

It prompted "Check your network connection" (screenshot attached) after I entered the card details and confirming my address info.

I checked and confirmed my phone has no connection issue, everything else working normally, never see this before...

If anyone else faced the same?

Thanks!

Edit: Sorry it should be the problem with the specific card only. I tried with another card it is fine. Probably the bank freezed something as adding to Google Pay frequently in the last few days...thanks Google I need to contact my bank now...
[Magisk] xSnowLeopardx:
I mean, is deleting data for GPS and GSF really necessary? Have read how a lot of people deleting their cache at max. have had the same good results. I don't wanna bother restoring FCM if it's not absolutely needed for this to work, but hey, that's me.
[Magisk] heathrow1:
Working like a charm on Redmi Note 9 pro. Thanks for your hard work!
[Magisk] Unn113:
V13 still doesn't work for me on nothing phone 2. I am checking it in playstore, it meets basic integrity only. Is it something I have to do to get it to work?
[Magisk] Bec de Xorbin:
Well, then don't do it and report back if it works.
[Magisk] liyafe1997:
WTF you even got STRONG_INTEGRITY????
[Magisk] TraderJack:
I've had multiple success simply going into airplane mode, clearing cache, reboot, put date forward 1 week, take out of airplane mode, wait about 3-5 mins. Then set time back once verified.
[Magisk] TraderJack:
He said previously his bootloader is not unlocked
[Magisk] zgfg:
Also fine for Lisa, Xiaomi.eu 12.5/11

(And not for Xiaomi.eu 14/13 but ok)
[Magisk] liyafe1997:
I think deleting Google Play Service data (But NOT Google Service Framework) is safe and no other side effects except your Google Pay card will be deleted, at least for me.

It is necessary to delete the Play Store's data to refresh the cache of "certified" status in About Play Store. And it is 99.999% safe without any side effects, only only one thing is the settings of Play Store will be lost, like disabling automatically update apps, something like that.
[Magisk] xSnowLeopardx:
Well in that case... I will try it soon, thanks for letting me know.
[Magisk] zgfg:
You have KSU or what?