yashsingh1/xdaforums huggingface dataset:
[Magisk] Bad Bimr:
Guys, as a noob I am super confused. Can some please post a guide on what some of us without the know how need to do to get this all working again?

Trying to get wallet working on My Pixel 7 and Pixel 6A.

Currently on PIF 14.1

Have no idea on what "fining a fingerprint" means or how to do it.

Thanks in advance.

BB
[Magisk] asisandroid:
To verify that, my idea would be, that simply someone tests if verification passes on their newly banned, but not modified ancient device. (or someone has already done that?)
[Magisk] GiraffeCubed:
PM'ed you some useful links from this thread, and elsewhere
[Magisk] Fishawy:
I have since shifted to @osm0sis's fork, and all is well. I may have argued the use of secondary backup options with @V0latyle, but what was highlighted here about curling a generic pif.json sounds a bit more risky.

Not sure if a one-size-fits-all method is the optimum one in such a hostile Big G environment. For now I prefer the slightly safer individualistic solution.

Again thankful for both methods, and for every contribution XDA has to offer for this.
[Magisk] neelchauhan:
I agree with the individualistic solution. A one size fits all solution makes it very obvious that Google has to ban a certain fingerprint.

In the past the one size fits all approach worked fine when we shared a fingerprint with many people using a legacy device. Now a legacy device used in a Play Integrity fix might be mostly out of use, so Google knows its all modders. With individual fingerprints, its less obvious since it's a mixed audience for a particular fingerprint.

Heck, I had a stock OxygenOS 13 blacklisted by Google, that unrooted with a locked bootloader, but an OTA fixed that, and I later re-flashed LineageOS when I got the custom fingerprint.
[Magisk] locolyric:
can you post the link here?

is there any tools that we can find / generate our fingerprint?
[Magisk] Lu5ck:
I think I know where Chiteroman got his prints from, I just hope he don't burn up that repo because I'm using a print taken from the said repo.
[Magisk] Nergal di Cuthah:
Pixel flasher will help generate the final json but you have to find your own print, or use the pull from the new 14.1
[Magisk] locolyric:
yes, i am using 14.1 now but still i cant find any post about the fingerprint. is it inside build.prop?

or we need it from some where else?
[Magisk] locolyric:
so the print come out from repo ?? is not come with the phone itself?
[Magisk] Nergal di Cuthah:
No one wants to burn their good fingerprints by giving out their location. Search google for oreo system dumps. I can't help much because my, usually impeccable, search skills have turned up nothing so I'm using 14.1 with the json deleted (read the changelog to find out where and how) so it downloads the fingerprint from the developer.

Edit/off topic: maybe i need to chill out lolView attachment 6040040
[Magisk] makeyourself:
See here under "resources" for guides to what you want to know.
[Magisk] Fishawy:
You're not alone, lol.
[Magisk] Nergal di Cuthah:
I like yours better, would rather be top 20 helpful that top ten talkers
[Magisk] BROKEN1981:
This new system and emoji reaction system is wack.
[Magisk] Nergal di Cuthah:
You mean xda's current system? Yeah i've been reduced to using the app for notifications and web for viewing, because the move broke the app, even though it still gets notifications :(
[Magisk] Lu5ck:
Is a repo of dumps so is from the phones. There are only build.props for android 7 and below so if you want to avoid his burning of prints then you have to look for android 8 and above.
[Magisk] locolyric:
something i not understand, i not saying i don't understand all the information on all the page.

i check play integrity the key is my phone key (while i use 14.1 module)

and i pull out buildprop from /product/etc , system , vendor .

only buildprop from product/etc able to compile as pif.json (the other two return blank result)

so the program do the rest of job,upload the files to /data/adb ,when i run again the play integrity check in playstore, it now showing "meets basic integrity" only . when i use yansac , it failed cts too.

but just using only 14.1 module itself, i get meet device integrity. and cts pass too.

This confused me ,what i did wrong and i get worst result using file i generate using build prop?
[Magisk] naitik2012:
Now our custom stable FP that we found are not even safe..... because of this :p

speedrun fingerprint bans :p .... lets just hope it does not select the fp i found after searching 2-3 hours
[Magisk] frank93:
this is something i still don’t understand as well. there are reports of ~that~ (asus-device) fingerprint being banned (banana-ed, not working, whatever), yet it still does (work) for me and many others. i’m using a more individually found print currently, still .. maybe there’s something happening between the "mismatching" of the hardware and the pif.json when play integrity decides a result? or some serious delay/lag? right now all of this is a bit vague tbh.

(also, the fact that the developer options get invisible when using this module.) 🥴

well at least those last few days haven’t been boring .. :)
[Magisk] Lord Sithek:
The tool is very useful, however it is difficult for me to use it because it doesn't fit well to the screen with custom scaling. I use 125% scale on Ubuntu and 150% on Windows and in both cases, I can't see some buttons to test pif.json. Of course, I can change the scale, but doing this every time is bit tedious. Anyway, thanks for the tool
[Magisk] dmenezes:
With all due respect to @chiteroman and all his great work: What the actual EFF!?

Seriously, either everything I learned here over the past week or so is wrong, or this "auto-update" thing will just accelerate fingerprint exhaustion until there's none left and we're all screwed. And I strongly suspect it's the latter.

Let's just hope @chiteroman has the good sense to stop putting new fingerprints up when that becomes obvious.

Meanwhile I'm keeping v14.0-resetprops here and my own custom, hard-won pif.json file -- I know v14.1 would use it when present, but as v14.0 is absolutely not broken, I for one am not going to fix it.

And perhaps I will move to @osm0sis fork before long, as he seems to be doing the sensible thing -- and I definitely don't need more crazy in my life...
[Magisk] olik2000:
The 14.1 fp got banned. I guess the only way is for everyone to find their own fp because it's pointless to find a fix only for it to get banned in few hours.

Still working.
[Magisk] Athanatos154:
A question about extracting a working fp from a valid android device, if I have a rooted device with a custom ROM can I use that fp straight up?

If not, if I install the latest official firmware of the device will that fp then work?

Or will this only work with unrooted devices that have never had a custom ROM installed?
[Magisk] dmenezes:
Sadly, as expected. In less than 12 hours! And now we all have one less useable fingerprint.

@chiteroman, please PLEASE stop burning our fingerprints while it's still time. I understand you want to help the busy/lazy/ignorant/can't-be-bothered people that can't/won't find their own prints, but this auto-update thing will just ruin everything for everyone, including them.
[Magisk] maxmax0:
Appreciate your effort but not sure if I see this as a good thing.

Google will ban the fingerprint within 24-48 hours (edit/update: nevermind, seems to be more like 12 hours 😂)

Solution working intermittently, unreliable (manual trigger needed to update the fingerprint after ban, in the meantime devices using it will get a rejection on validation)

Large number of prints being burned will lock everyone out of this solution rather sooner than later

Large number of users using this spoof may trigger additional actions from G (more consistency checks, new methods of detection etc.), lowering the likelihood people with custom prints can fly under the radar

Additional security consideration: is curl running as root? is the process parsing the data running as root? how is the data sanitized? Opens up new vectors of attack.

Feels like trying to ride a dying horse by beating it harder.
[Magisk] xcl1pse:
Honestly it's 2 days before him publish that fps in latest version, but yeah another one burning in hell
[Magisk] EuK_V:
@chiteroman I would agree with the above statements, that adding every few days another working fingerprint is rather pointless. You take care of people who are too lazy to read, to make an effort to find working fingerprint themselves. I thougt the idea was to convince all people to use different fingerprints to slow down google to ban them.
[Magisk] Lord Sithek:
I don't know what's going on here, but 14.1 fp still working for me...
[Magisk] zgfg:
Ok, so did you test if you can pass Basic and Device Integrity without this PI Fix module?

If so, you don't need the module
[Magisk] totalolage:
Unfortunately even with latest OTA and magisk canary, this issue persists.
[Magisk] famusc:
No, without this module I only pass basic. Device passes only with this module installed
[Magisk] pndwal:
Nb. Magisk root will break deviceIntegrity without hiding from GMS... If ROM is capable of spoofing deviceIntegrity out-of-the-box, after installing Magisk you will need to add GMS droidguard (attestation) and possibly main processes (com.google.android.gms.unstable + com.google.android.gms) to a working hidelist to pass the verdict...

You won't need any PI deviceIntegrity fix modules, but must hide root from GMS (since a 'fix' module isn't doing it.) 👀 PW.
[Magisk] famusc:
This happened till 2 or 3 weeks ago on 13 ultra xiaomi.eu 14.0.17. I was just hiding and passed everything (except strong, obviously) . Then suddenly lost device integrity.

The only way to pass both device and basic integrity again is play integrity fix v7 (7.4 works randomly, as I was saying)

If in the last few days something has changed again, I don't know. I'll test again without fix.
[Magisk] hope-faith:
I have a Samsung galaxy s9 running stock Android 10. After installing "Play integrity fix" I am able to pass: "Meets_device_integrity" & "Meets_basic_integrity." However, I failed to pass "Strong_integrity." -using integrity checker from playstore.

Also yasnac shows: "something went wrong, attestation response timeout."

Any help is greatly appreciated 🙏

Thanks in advance.
[Magisk] pndwal:
My guess is that integrated fix in your XiaomiEU ROM If ROM is no longer capable of spoofing deviceIntegrity out-of-the-box... You could test by flashing back unpatched boot.img...

As @Displax has noted, the XiaomiEU deviceIntegrity fix is strange and difficult to make compatible with Magisk deviceIntegrity fix modules... If it's now not working you may need to wait for XiaomiEU update or use a ROM that doesn't spoof + a Magisk deviceIntegrity fix module...

If ROM is actually still capable of spoofing deviceIntegrity out-of-the-box (without Magisk installed) we may need to re-think this... Eg. There may be other changes made on your device... 🤠 PW
[Magisk] pndwal:
So working perfectly... Why do you think you should have strongIntegrity with unlocked B/L? 🤪... (Clue: 'strong' means tamper proof.)

YASNAC issue seems to be network issue only... 🤠 PW
[Magisk] simpleatom7:
The fix was strong integrity got patched by Google a week ago so u can't pass it. U don't need strong integrity to get ur play protect/playstore verified. Same for yasnac.
[Magisk] ashok:
Google has set a DL and it wont be long until Strong integrity passing devices will only be able to use banking and security apps. Hope some one will find a fix then
[Magisk] simpleatom7:
U can still use banking+ security apps.
[Magisk] ashok:
For now. yes.But i am talking abt future
[Magisk] simpleatom7:
It's a rat & mouse game. I hope with kernel su, we would see something different & beneficial.
[Magisk] sawdoctor:
It's nothing to do with Google, the ability to use strong has been there for ages. It's app developers choosing to use strong, Google isn't trying to force anyone. If Google didn't want you rooting they'd lock bootloader on pixels
[Magisk] ashok:
They are transferring to play integrity. Developers have been given a deadline. See here

Discontinuing the SafetyNet Attestation API | App quality | Android Developers

developer.android.com
[Magisk] pndwal:
DL = deadline?... Where?... I'd be very surprised if Google force banks to use strongIntegrity at all... They've given banks the means via the API but rigged it to favour us modders... (Read "banks can't use this without accepting all users of devices launched with Android 7.x or earlier as well as so many relatively recent modern devices with broken keymaster implementations like OnePlus or other AVB chain-of-trust issues, as collateral damage.) So they've really been our friends in this regard AFAICS... Of course there are ways banks can use hardware-backed key attestation w/o using Google's API or accepting this trade-off...

😜 PW
[Magisk] zgfg:
OMG

Deprecating SafetyNet (by the way, notes from Google are around for more than a year, so your 'news' is nothing really new) and replacing by Play Integrity DOES NOT FORCE anyone and by an means to require Strong Integrity.

Please read again and better understand things

Strong Integrity does not equal to Play Integrity. Strong Integrity is just one of three (four if counting also Virtual Integrity) tiers of Play Integrity

Google themselves, a year ago or so, switched from SafetyNet to PlayIntegrity for Google Wallet but Wallet requires ONLY Device and Basic Integrity, never Strong Integrity

We know (for sure) only for one or maybe two/three apps (you never know since the app does not tell you what they detected) that require Strong Integrity

For all others apps, Basic and Device Integrity are enough. Some apps detect further hints or artefacts of root but those are absolutely not related to Strong Integrity. One has to properly use DenyList/MagiskHide/UnmountModules, Shamiko (if using Zygisk), HMA, or switch to Riru (and Delta or Alpha fork of Magisk) instead of Zygisk and those banking apps will no more detect/complain/force-close although Strong Integrity would still be failing

Moreover, Strong Integrity practically equals to CTS Hardware Attestation (read Google tech docs, they have been posted and discussed here on XDA a year ago, they have even a chart how to compare SN and PI levels) hence developers who wanted, could have required CTS Hardware Attestation with SafetyNet if/when they wanted two years ago - did they?
[Magisk] pndwal:
Yeah, we've all been aware of this for some time, but it really changes nothing regarding device integrity attestation APO implementations or use...

Practically all banks have already migrated to Play Integrity API but the equivalent of S/N ctsProfileMatch w/ basic-only evaluationType, PI deviceIntegrity, is easily bypassed with only two additional prop changes needed to bypass hardware-backed evaluationType enforcement... Banks never moved to S/N ctsProfileMatch w/ hardware-backed evaluationType required and haven't used it's new equipment, PI strongIntegrity, for the reasons I mentioned above...

And when the 'turn-down' deadline is reached, nothing will change either except users of old bank apps with be forced to update to bank apps using PI... No problem!

Nb. AFAIK the only app to begin us strongIntegrity is a photo editing app with face detection, and then the implementation is very strange and looks almost accidental as it is only apply to one (or more) editing template...

👀 PW
[Magisk] westruk:
Google's defenders are here)
[Magisk] westruk:
Uber driver app also
[Magisk] purgy:
It seems like that's been the way to go for a while now.

Meanwhile, I don't use gpay unless I forget my actual wallet, and my bank app will happily run with unlocked bootloader etc.

One day I'll get around to searching for a viable fp, but this seems a temporary fix at best, and I'm also waiting to see if individually set fps are getting axe before I invest too much into this
[Magisk] HippoMan:
I've been using a fingerprint that's a result of searching, and it still hasn't been banana-ed, even though it's been installed for longer than 14.1 has been in existence. And there are others who can say the same thing.

To those of you who assert that the Googlefrinchians aren't paying attention to these PIF releases and aren't able to banana the associated fingerprints soon after their release, how do you account for the lower longevity of these PIF fingerprints in relation to individually found and non-publicized fingerprints, each of which is used by many fewer people than the officially released PIF fingerprints?

The Uncertainty Principle?

Sunspots?

Capitalism?

Socialism?

Climate Change?

Nostradamus?

Vaccination?

Beer?

The Atomic Mole People?

... ???
[Magisk] dmenezes:
Yeah, that happened to me in the past (with 13.x PIF versions).

I think it's some kind of cache somewhere, or Google backend servers not all being updated at the same time. Or perhaps because of other props in your device. No one outside Google really knows.

But it won't last long, once Google gets its claws on a fingerprint, it's gone at least for most people in a matter of minutes.
[Magisk] maxmax0:
Agreed! I would just like to add that solutions like "just give everyone a random print from a pool" are totally stupid, because it's literally a matter of five minutes of scripting to compile the (almost) full list by repeated requests (using different IPs if needed, in case anyone bothered to implement a throttling solution, which I'm sure they haven't).
[Magisk] d4m4s74:
With 14.1 you can still throw in your own. I have one and 7 more ready to go.
[Magisk] dmenezes:
You forgot "5G cell towers irradiating mind-control thoughts" 🤣

Seriously, v14.1 initial online fingerprint getting banned in less than 12 hours since being put out for wider distribution should be more than evidence enough for anyone sane to see auto-distributing new fingerprints is NOT a good idea.

I just hope @chiteroman and others that are attempting this stop it before it's too late.
[Magisk] deechte:
Is this all relevant if you do not have a custom ROM installed but use this module to hide root only?
[Magisk] dmenezes:
Yep, I explicitly stated that in my post. But that's not the point.

The point is, good luck with that once v14.1 and later go thought them and get them bananaed along all the others like it just did with its initial one
[Magisk] maxmax0:
Of course, but I understand his point to be that there is a high chance those 8 are also somewhere in chiteromans list, waiting to be pushed to thousands of noobs and be banned by Google within 12 hours. They wont do you much good then.
[Magisk] xcl1pse:
This module isn't design to hide root, but maybe set some sensitive props from your rom since you already unlock your bootloader and some app using this method to determined that your device is rooted
[Magisk] User_15357:
Why does the same print work for some people and not for others? Why on two of my devices, using PIFv14.1, does the verification pass the second or third time?

Why does "banana" public print still work on some devices?

I spent all day yesterday and still couldn't find a working print for me, even though I've tried the prints that others have that work.

Perhaps the misinformation was initially launched that you need to find prints for yourself and not show them to anyone? Perhaps this misinformation was started by Google's office staff to get as few people as possible to use rooted devices or to throw us all off the right track?
[Magisk] dmenezes:
A lot of "perhapses". But we have ONE certainty: auto-updated fingerprints are getting bananaed in less than 12h, while self-mined ones are lasting days at least (and perhaps more as long as they don't get trampled by this auto-updating madness).
[Magisk] User_15357:
For those who argue otherwise, I suggest someone donate their old and non-public print for public use to see if it turns into a banana or not.
[Magisk] brainshaker:
can you pm me the same links on how to do these fingerprints?
[Magisk] xcl1pse:
Just testing the latest version and still working bruh. Note that I'm not clear data gms, play store or anything. Delete my custom pif, flash and reboot
[Magisk] dmenezes:
From my post just a few minutes ago:
[Magisk] deechte:
Thanks. Does that mean I'll be screwed too, having to find a working pif, or does that not apply to me cause I'm using a stock ROM albeit rooted.
[Magisk] GabbyWC:
As strongly as you feel about this, there's no need to make false statements. The supplied fingerprint from v14.1 is still functional and has been since it was temporarily posted by chiteroman days ago in the Telegram channel.
[Magisk] dmenezes:
Looks like you're not reading this thread very closely, so I refer you to the original report:

So it's not me "making false statements"...
[Magisk] xcl1pse:
Maybe config or rom in their phone (like MIUI by EU). If mine works, so others should
[Magisk] sawdoctor:
Just checked with play integrity checker and still got 2 green ticks so not sure what is going on. Im not on 14.1 but tested the fingerprint from 14.1 on 14 so maybe Google is blocking some other way?
[Magisk] VeDoxe:
Where can we find the Telegram channel?

I found it
[Magisk] HippoMan:
14.1 comes with an empty /data/adb/pif.json, and it only uses the fingerprint(s) from its central database if that /data/adb/pif.json remains empty. If we install our own /data/adb/pif.json, that one gets used in 14.1, just like in 14.0.

So, I have a suggestion: fill the 14.1 central database with fingerprints which are known not to work. This way, if the Googlefrinchians run the default 14.1 in order to learn what fingerprints it utilizes, they'll always end up with faulty values.

This puts the onus back on us to install privately obtained fingerprints, but we've already been doing that since 14.0 and earlier.
[Magisk] dmenezes:
You're the third report that the 14.1 original fingerprint is still working. So perhaps @ollik2000 is mistaken or it's something else affecting his phone?

Let's wait and see.
[Magisk] GabbyWC:
I've read through dozens of pages from this thread over the past couple of weeks and generally appreciate the contributions and opinions from the members here. It's still too soon to say that this fingerprint is no longer valid. When the ban on the fingerprint in v13.9 happened, it was confirmed by many people on TG and XDA within minutes. That isn't the case here.
[Magisk] carlese:
I tried both PIF and its fork but Google Wallet is always failing.. Deleted cache and also Wallet data but still no luck. There's nothing we can do? I don't have my own fingerprints, using the ones from the module..
[Magisk] dmenezes:
Agreed. As per my last post before this one, let's wait and see.
[Magisk] HippoMan:
It's not functional for everyone. It already has started failing for some, although not all users.

Question: does 14.1 always supply the same fingerprint all the time? Or does it choose from a collection of fingerprints and supply different ones at different times?

If it's the latter, that could explain why it works for some people and has already started to fail for others.
[Magisk] bombadier:
I am totally lost with the fast moving ****uation, I am using version 14 which is working, I saw the new version 14.1 was released yesterday and so I flashed it, did not remove the version 14 default pif.json and I failed one of the integrity checks (cant remember which one) on version 14.1, went back to 14 and got my two ticks back, I thought version 14.1 would use an existing file therefore why did one of the checks fail ? I am trying to keep up with the thread but its hard with the number of posts and the incessant bickering........

bet this post gets lost in all the bickering
[Magisk] olik2000:
I reinstalled it and now it's working again. Not sure what was the problem before. Sorry for my quick conclusion that it got banana-ed.
[Magisk] dmenezes:
Good hypothesis. Perhaps @chiteroman will chime in?

I don't really know as I'm not using v14.1 and after the v13.x serial bananas I don't need any more proof that distributing the same prints widely will get them bananaed.

But let's wait and see -- I just hope we don't burn too many still-good prints while we're waiting.