yashsingh1/xdaforums huggingface dataset:
[Magisk] arda99:
killall com.google.android.gms.unstable && logcat -c && logcat | grep PIF
[Magisk] V0latyle:
You can't set up 2fa through text? not doubting you, just think it's a really really dumb strategy for a bank to try to force you to use their app with no alternative

Doesn't hurt to try

My mistake, you said

I read that as "not only do I pass"

tired dyslexic is tyred
[Magisk] zgfg:
Devices with First API Level 26 did not have TEE, hence cannot enforce Hardware/Strong attestation

Thats the whole point, and without that there will be no module and no point in spoofing
[Magisk] bakaekze:
Most likely not, they had to have been launched with A7.1 or older and received an A8 update. Though you are still supposed to use FPs fom A7.1 or older builds.

They *might* work though. So it doesn't hurt to try.
[Magisk] revengineer:
This is getting frustrating but appreciate the community effort to overcome Google's countereffort. I have kept up reading the thread and have a good understanding of the technical issue and solution. However, I have not clue how to find these old fingerprint. I some is willing to pm me a solution while I dig into this deeper, I would very much appreciate it. I promise that I do not work for the big G. Thank you!
[Magisk] osm0sis:
Please edit to remove your hint. You think the search engine giant can't play fill in the blank?

A lot of those prints, especially in Google's folder fall under being the final releases for each device so seem banned for spoofing. Note some have had some success with them by adjusting first API level up/down by one/some however. Hence all that being alluded to in my guide.
[Magisk] dnfm:
Fair enough.

I understand that it only spoofs for gms, so getprop may not be my friend, but how can I find some indication it's working vs just having an invalid fingerprint and I need to try again?
[Magisk] HippoMan:
IMO, that is the only viable way to go.

Even if you find some fingerprints that work, it's extremely likely that over time (and probably not very much of it), the Googlefrinchian Telephone Sanitizers will learn about them and end up "banning"/"blocking"/"rejecting"/"invalidating"/whatever-word-you-prefer all of them. And then, the whole rigamarole would have to be repeated.

There's some interesting technical knowledge being shared here, and it's indeed been somewhat fulfilling for me to write some code which helps in this effort. But this is a game that's requiring more and more pain and effort to play, and we're definitely going to lose.
[Magisk] V0latyle:
those who adamantly declare something about themselves are inevitably the opposite of what they proclaim

group meeting!!!!

nah.

Get a donor build.prop from firmware of your choice and follow the PixelFlasher guide

I don't hear a fat lady singing yet my dude. Unless I'm mistaking what sounds like a strangled drowning cat in heat

They build a better mousetrap, we learn to be better mouses
[Magisk] prot-:
I'm getting Device not certified now with v14 after clearing playstore and play services and rebooting a few times.

Integrity checks work ok tho
[Magisk] arda99:
I think you mean less than 26. Anyway if the theory is true then any fingerprints from such device would work even it's updated to A8/A9 later? obviously not the case.
[Magisk] revengineer:
Following the Pixelflasher guide is not the problem, this is: "Get a donor build.prop from firmware" because I do not know where to look and what to pick.
[Magisk] Nergal di Cuthah:
Did you find a fingerprint ?14, if i understand correctly, has no fingerprint and we must supply our own.
[Magisk] xSnowLeopardx:
I rarely give up. I am quite the savvy tech guy, but this became just too much.

Maybe it's because I am sick irl right now, but finding fingerprints, thinking about first API levels, knowing and not know which models are banned, it's just too much.

I appreciate everyone (devs, staff, other users) for helping the rather nooby people out, but I think I give up now :)

Especially since I do this all for GWallet. If it were to break again even if I had a working pif.json, I would not be able to fix it if I were in an "about to pay somewhere" situation, lol.

This sucks, Google.

Got more than one working in the end!

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] sawdoctor:
Ok so find a device which has been updated to Oreo and one that's as obscure as you can think of 👍
[Magisk] Bobb_o:
Yep, the nightmare scenario is you thinking it'll work and then it doesn't. It may be time to figure out if the root features are worth not having NFC payments.
[Magisk] Claus….:
Who did find these fingerprints?
[Magisk] V0latyle:
Android version of print you used?

Download firmware for donor device. I'll use the Pixel 5 since it's current and the prints won't work

Inside firmware zip is image-redfin-buildnumber.zip. Extract system.img then open with 7zip or other program that can handle .img. Open the /system folder inside system.img, you'll find build.prop. Extract this, and process with Pixel Flasher
[Magisk] xSnowLeopardx:
Well in my case: I can just use my physical cards. That's it. Yeah, GWallet is convenient, but not gonna lie: I don

t pay that much. Wish I was that rich LOL.
[Magisk] V0latyle:
There are prints that still work, I'm using one.

Doesn't have to be obscure, but just keep it to yourself

Quite a few of us have, you have to do the work though.
[Magisk] HippoMan:
Thank you for the encouragement! But between work and my personal life, I just don't want to spend what little spare time I have engaging in the drudgery of searching over and over for prop fingerprints.

And in any case, even since long before this current PIF issue cropped up, I have been avoiding using my phone for banking and contactless payments. My wallet is and always has been my preferred payment device.

I've been participating here because of being interested technically, and also to try to help in some small ways, if possible. I'm still willing help when I can, but as I mentioned, being a prop searcher just isn't my cup of tea.
[Magisk] Ginosius:
Same here.. Google can just go **** themselves.. I'll make sure to carry all of my bank cards with me from now on.
[Magisk] arda99:
my workflow:

adb connect to phone

edit the json in pc and save

adb push pif.json /sdcard/download/ && adb shell "su -c 'cp /sdcard/download/pif.json /data/adb/modules/playintegrityfix/pif.json && killall com.google.android.gms.unstable'" && adb logcat -c && adb logcat | findstr PIF

change /data/adb/modules/playintegrityfix/pif.json to /data/adb/pif.json if you're on recent release.

also findstr -> grep if you have one.
[Magisk] Claus….:
For me it seems a lot of bs. Did you find one?
[Magisk] Varrkan82:
Same thing even as I've fixed it this time no any warranties Google will break this fix just tomorrow. I've moved to Xiaomi.Eu from the stock Mi 9T Pro ROM after around a year using it of a reason what Google broke SafetyNet. Even for stock! And there wasn't any news from Xiaomi when they fix that. But now, I hope, they fixed it in update after I was moved from the stock. And now I'm thinking about to move back to stock with boot locking. Only thing I need a root now - just to use AdAway and backups with Titanium backup (yes, it still works). But i could drop it if rolling back will fix a GPay. Ah, forget, I also using automatic call records from MIUI dialer...
[Magisk] sawdoctor:
Ok I'm the least tech savvy guy around and although ive not tested the fingerprint yet a simple Google "devices that have been updated to Oreo" gave me a nice list of devices to choose from. I picked the most obscure one i could think of and then googled firmware for it and downloaded it. There's plenty of programs that will extract the firmware i used a kitchen, now i have to test it.

What might be useful is a list of known blocked fingerprints @chiteroman so people don't waste their time
[Magisk] V0latyle:
Totally get it

If only there was an online database of props

Yes.
[Magisk] HippoMan:
... that the Googlefrinchians would be unable to access.
[Magisk] dmenezes:
I can't get SMS when I'm overseas (which happens A LOT).
[Magisk] arda99:
and most likely this wouldn't work, in many cases you need one from odm or vendor img. "getprop" from a live system is accurate, getting from rom dump is another story and can be quite complicated.
[Magisk] V0latyle:
Except that we have to spoof prints of CTS approved devices....so they already have them all. Literally every GMS approved Android device in existence
[Magisk] revengineer:
I understand the technical procedure perfectly well. I need to find a donor device with a working fingerprint. I have no clue where to start looking.
[Magisk] downhere:
Took me about 20 minutes to find, setup (manually), test and succeed.

It's not impossible.
[Magisk] Claus….:
Okay, lucky you. Sell me yours? Pm your price.
[Magisk] Claus….:
Please don’t bs with 20 min.
[Magisk] dmenezes:
I think this is a bit too paranoid, but paying respect to all your good work I just removed it.

OK, thanks for the tip. I tried subtracting one from FIRST_API_LEVEL a couple of times, but the problem remained.

Anything else I can try?
[Magisk] DP FH:
Me too! ahah
[Magisk] V0latyle:
You'll have to do some research, because the device has to have been launched pre Android 9, but IIRC has to have been updated to Android 8 at some point in its lifetime

An example would be the Taimen (Pixel 2 XL) which previous versions of PIF/USNF Displax Mod used. Launched with Android 8.0, was eventually updated to Android 11
[Magisk] DP FH:
I tried many of them and all of them gave me basic integrity :(
[Magisk] Nergal di Cuthah:
I can't even get duckduckgo search to find fingerprint all i get is sensor articles. Even tried props fingerprint to no avail. That said, even though i only have basic and not device, playstore is still certified and my banks apps don't give a fig, so for now will stay with 13.8.
[Magisk] V0latyle:
Nope. Sorry. It's something you can find yourself given enough research and legwork, and the only people who I'd share the print I use with are people I know personally and trust. I hate saying that because i've always been of the mentality of "share anything that can help the greater good" but in this sort of cat and mouse game you can't be too careful

I won't lie, it's a PITA but it's not impossibru. There's entire websites dedicated to firmware for Samsung and Google phones
[Magisk] downhere:
All required information is written in this thread. Even where to find build.props.

So, reading takes more than 20 minutes, sure. But the process itself is a quicky.
[Magisk] HippoMan:
Yes, they have all the prints, but if this hypothetical DB of usable prints was somehow available and hidden from them, they at least would have a harder time figuring out *which* prints we'd be randomly using for spoofing.

But even in that scenario, it will just be a matter of time before they'll learn.
[Magisk] HippoMan:
Impossible challenge of the week: how to tell each other where and how to find build props to use without the Googlefrinchians figuring out what we're telling each other.
[Magisk] revengineer:
There is a whole post in this thread on which versions work and which don't but not sufficient for me to locate them. I am technically very savvy but I am not able to dedicate my life to rooting my phone. Maybe this is the point when I just need to bow out. Google won.
[Magisk] prot-:
This is indeed a sad day.. if anyone wants to pm.me a working code id be most grateful. I don't know wtf to do without tap to pay working.
[Magisk] Bonoboo:
UPD: app and all info here
[Magisk] V0latyle:
Dude at this point it's Among Us

Any one of us could be one of THEM

@V0latyle kinda sus
[Magisk] Qnorsten:
Thank you that is very helpful, even though I would still love to be able to find a way to trigger a proper PI test directly from shell.

Will be interesting to see how long this finger print works. I found one in my 3rd try (lucky I guess) then it took me about 2 hours and a lot of testing to find 4 more. So at least I have some backups when they crack down again.
[Magisk] Nergal di Cuthah:
I mean i am Sundar Pichai,'s close nephew and have been telling him everything but that doesn't mean I'm the leak. Lol
[Magisk] HippoMan:
That's precisely why I named it an "Impossible" challenge.
[Magisk] Claus….:
I hope you see it is weird, I don’t need it for some bs bank app. So time is money for us, using it our solution. Can’t afford losing time. If you have it, you can find another one. If serious, pm me with a price.
[Magisk] Claus….:
Okay, you telling me that playing violin takes 20 min. Nothing else.
[Magisk] rseiler:
But they must currently be on 8 or higher, right? So, pulling an Android 6 or 7 will not work (if it can't be upgraded). Or so I gather, could be wrong.
[Magisk] prot-:
So just so I'm clear.

This mod is now no longer a working solution- unless we find an old device with a working fingerprint ourselves and follow some complex guide that's hidden away in pages of these forums to fix the fingerprint ?

Otherwise we are our of luck to ever use Google wallet again?
[Magisk] Marvin732:
Yep
[Magisk] HippoMan:
I think that's correct. We now have to be untrusting, paranoid prop-hunters on an ongoing basis if we want to be able to use our modded devices for any kind of contactless payment.
[Magisk] Utini:
So my old Nexus 6P hidden away in a drawer could save my day since I could use its props and won't have to worry about it being banned?
[Magisk] HippoMan:
I think it's just a matter of time before the Googlefrinchians block it. But if it works, you are at least buying some time at the present.
[Magisk] jurluk:
Tried two fingerprints for two devices I own and no luck whatsoever

Thanks to @chiteroman and the whole community for hard work, but I think it's over now :(

Or at least until we find some better solution :confused:
[Magisk] V0latyle:
Not allowed on XDA...

I think so but @osm0sis or @pndwal could say for sure

It is....You just have to supply your own working print. So, if you aren't willing to put the effort forth, you're back to using cards.

For now.

Until someone figures out some sort of catastrophic breakthrough, or better yet figures out how to defeat PI without Google figuring out how. From what we currently think we know, not so likely, but not impossible

I think you misunderstand

Yes, using one of the prints from that device could work.

Until Google figures out that there's a mismatch between the print and your actual device, and blacklists that print

It's a matter of time for every single print, none of them are safe. I imagine Google will eventually start checking for mismatches on ALL devices, at which point this won't work for us anymore
[Magisk] V0latyle:
It's like mining gold my dude. There's prints that work. You just have to find them. You're going to strike out a lot of times before you find one that works.
[Magisk] Alpha U:
Currently what from I understand is that there will be tools to easily insert the fingerprint and to double check if it will pass intergrity eventually but we have to do it, it makes sense logically that the only way the mouses stop getting smashed is to spread out as much as we can, then google can't do anything they will give up well until they force strong_intergrity then we all ****ed.
[Magisk] jurluk:
Anyway, how does integrity check works under the hood? Why does it goes to google api at all?
[Magisk] prot-:
Is downgrading google play store something that might help or is it server side checks irregardless of playstore version? Assuming you can downgrade that is.
[Magisk] HippoMan:
Exactly. So, the game is pretty much over now (or at least soon) for contactless payments.

As I've mentioned, I never got into using my phone for that, but I'm sure that it's been fun while it lasted for lots of other people.
[Magisk] neelchauhan:
If you live in the EU, you could (read: should) complain about Google to your privacy regulators.

YouTube has been in hot fire from the EU in trying to see if an ad blocker is being used: https://www.wired.com/story/youtube-ad-blocker-detection-eu-privacy-law/

Similarly, we could do the same for Play Integrity.

I'm an American, but for Europeans, complain about Play Integrity checking device values. Complain about Google disallowing your software of choice.
[Magisk] iakoboss7:
Hello everyone

I dont know why but i cannot find the "adb" folder anywhere.

i will share some screenshots with my setup and i am glad to answer any questions.

please help >.<

View attachment 6039136View attachment 6039137View attachment 6039138View attachment 6039139
[Magisk] downhere:
Yup. The game takes 20 minutes.

Learning / practising / reading takes longer.

I assume you tinkered your phone (otherwise you wouldn't follow this thread), so you know how to get the information to reach your goal.

Therefore there is a shortcut in disguise: G*

Even G* doesn't like it, it will bring you to the desired information re build.prop.

None will / should publish the working prints on here as each public print is shorten the lifetime of this hack. If you need it, you'll have to do some effort (as you did for tinkering before).
[Magisk] Claus….:
Well, tell me in pm where to find you, I guess that is within the rules? I need help, if your claim is true.

One rule that is a must for all forums, bull**** filter.
[Magisk] Catarsi:
Tried setting a custom pif from build.prop pulled from 3 old phones I had and none worked... damn Google.

I really hope we can find some workaround sometime
[Magisk] HippoMan:
Looking for a software-based solution for this is pretty much a dead end now.

I think we are going to need a hardware solution. Here's one possibility:

https://xdaforums.com/t/discussion-...ding-cat-and-mouse-game.4425939/post-87189689

It would take someone like Elon Musk to afford to implement something like this on a large scale, but maybe he can be convinced. Does anyone here know him?

... or anyone else who might be in a position to fund the development of such a device?
[Magisk] Nergal di Cuthah:
Well there goes one of my two old devices and am pretty sure the srcond is too old
[Magisk] Claus….:
You are right about the first, not the last. I did not do anything to my phone. I need this for our solution. So need help.
[Magisk] downhere:
Your untinkered stock phone doesn't pass PI???
[Magisk] Lu5ck:
The end of custom rom is near~

Either use Pixel phone that let you lock bootloader or use stock rom without root~
[Magisk] acwcanada:
Tried with your new update 2.1, same result, Shamiko 0.7.3 installed enforce deny list disabled. Failed all even device and basic. One more thing to mention that I am on Magisk canary-26104, don't know if this matter.

P.S. The strange thing is that even they all failed but I found that Google Wallet and all my banking apps are still working. Google service is working also and Google store showing that device is certified. It looks like it is actually working with false error that all integrity are failed.
[Magisk] Stillhard:
v2.1 failed on my device - returned to v1.1 but still failed the Strong, disabled it and use Displax - all green

weird :D
[Magisk] Displax:
Nice work with zygisk implementation ;)
[Magisk] Stillhard:
any chance you'll make a guide for this? :love:
[Magisk] Spartacus500:
Not working for me for Samsung

View attachment 5960115
[Magisk] chiteroman:
Your device doesn't support attestation through TEE, it will never work.
[Magisk] Displax:
Weird things... According to user reviews - some devices pass with delete prop, but some devices need set it >= 33 and vice versa. It seems that there is no universal solution here.
[Magisk] Displax:
I played with it, ro.product.first_api_level can be even 50 or 100, doesn't matter.
[Magisk] chiteroman:
When I installed one of your test modules, I managed to hook (modifying framework.jar) the getString method from SystemProperties and I log a call for ro.vendor.build.fingerprint property. In my POCO X3 Pro with LineageOS 19.1 I didn't pass any, but when I modified this prop to google walleye fingerprint I passed basic and device but not strong.

So I think we need to change more props in few devices. The question is, why this only happen in few devices?
[Magisk] zgfg:
Is it also SNFix for Xiaomi module version - I grep nothing in the logcat
[Magisk] Stillhard:
Failed Strong still

Back to Displax's and all turned Green

FYI, i'm using:

- Delta with SuList

- No Shamiko oc :LOL:
[Magisk] chiteroman:
Which Displax version are you using?
[Magisk] Stillhard:
This one, the one that i changed that work for my device
[Magisk] Stillhard:
Dug in to my archive, just installed and test your v1.1 that used to work again, all green o_O

Same conditions:

- Delta /w SuList

- No Shamiko oc :cool:
[Magisk] sawdoctor:
This one is the only one that passed strong for me on the pixel fold too. No Idea what's different but definitely need to keep this version available
[Magisk] Stillhard:
Lol, just the same, i just disabled it to test @swer45's version and when thing go wrong, just reverted it and all the green comes back
[Magisk] chiteroman:
@andy242 @Stillhard I know where are the problem, this should work for you, don't need to install Shamiko neither to add any GMS process to deny list.

EDIT: Download in first post
[Magisk] Stillhard:
Finally! This is Green :alien:

But funny how this v1.1 showed the same

What's the difference(s) after so many attempts?
[Magisk] sawdoctor:
Thanks I'll test in a minute. @Stillhard fix is the only "strong fix" that actually booted on the pixel fold. All the others got stuck on "android is starting". Would love to know what is different between the pixel fold and pixel 7 pro as there shouldn't really be any difference with the fixes
[Magisk] Johnn78:
Such I understand the safetynet kdragon is deprecated but what is better the safetynet Displax (https://github.com/Displax/safetynet-fix/releases) or PI Fix module ? Also to suppose that if we flash any of these modules via Magisk they we should remove the safetynet KDragon and also to remove the Magiskhide Props Config ?
[Magisk] zgfg:
What is better may depend on your ROM. Install, reboot, test and decide, you must pass Device and Basic Integrity - that's it. And uninstall the old modules as you said
[Magisk] sawdoctor:
If you are already passing basic and device integrity and have no issues with WiFi calling then my advice is to leave everything as it is. If it's not broke don't fix it lol , but both modules do pretty much the same thing but this one has a few fixes for xaiomi and other devices
[Magisk] pndwal:
The point is not that @kdrag0n's USNF is deprecated; it isn't!... It just has issues and remains unfixed... The point is that the whole S/N device integrity API in Google's GMS framework is deprecated; Nb. Checkers like YASNAC are also now insufficient and users now need to check for new Play Integrity API's verdicts using the likes of Play Integrity API Checker...

End of January 2025	Full turndown (timeline extended)	SafetyNet Attestation will no longer work for any version of your app. Your app will receive an error.

https://developer.android.com/training/safetynet/deprecation-timeline

With 2.4.0 officicial USNF actually became a PI fix... @Displax had already added PI fixes to support deviceIntegrity verdict in earlier forked/modded builds, so all of these solutions are really partial Play Integrity fixes now (nb. Not full fixes since we won't pass strongIntegrity).

Both the recent (currently updated) solutions are viable fixes for deviceIntegrity verdict... Modded USNF seems to be more stable although mod_2.0 remains broken for devices launched with Android 13; mod_1.3 can be used for these however... PIF seems to be quite experimental with frequent revisions but adds some interesting fixes that may help with a subset of the devices with broken keymaster implementations, eg OnePlus, and more...

Yes and yes... 🤠 PW