yashsingh1/xdaforums huggingface dataset:
[Magisk] V0latyle:
What you say on Telegram isn't really an issue here so long as you aren't trashing members of XDA or posting derogatory things about staff.

My personal opinion: As has been discussed ad nauseum, it may be best to be willing to listen to the wisdom of other developers, especially when it comes to the good of the community. There are a finite number of prints available, and a popular consensus is that it is best that everyone finds their own to use, because bundling one with a module, and/or a large number of people using the same print, seems to be what gets that print blacklisted quickly. Again, that's just opinion, and the consensus of the staff is to stay hands off for the most part; we will only intervene when the Forum Rules are violated.

Otherwise I hope people will try to be smarter about this. Just because you can do something a certain way (like making something really easy for the average user) doesn't mean it's the right thing to do, or that you should.

Exactly.

There's a lot of laziness and entitlement going around here, quite frankly, The information needed to find prints and try them is readily available. I'll be honest - I haven't figured out how to use your script either - but I'm not above admitting that I need to educate myself and learn before I start asking repetitive questions.

To everyone else: There are many great minds hard at work finding out which prints work in which combinations. While the general consensus is that we aren't going to hand out any prints to anyone, we WILL make our findings in criteria available to make it easier for you. @badabing2003 even went so far as to provide the ability for Pixel Flasher to make a custom print for you, and all you have to do is supply a build.prop.
[Magisk] D€INOS:
I'm favor on a poll here with an vote option to update with a new fingerprint for testing something that would work indefinitely
[Magisk] Nodens:
You do have a point but you don't really have to go for the really old and/or obscure devices. I did because I already had a local collection of dumps, before this, and I know perfectly well what I'm doing and where to find what I'm looking for even if it's not in a standard location. You don't have to do that though.

From a point on, in time, things are kinda standardized and if you follow @osm0sis guide and look at the Oreo era devices, as he suggests, his directions are very accurate and easy to follow for people who have no idea about the insides of android. Also you have tools available to simplify things for you. You don't have to dig manually when people made jackhammers for you to use. If you get my drift. And even this non-standard finding of mine osm0sis will add to his script so even that will be supported if you happen to hit such a firmware image.

The bottom line is, if you're just interested in getting a working fp, use the tools.

If you want to learn and explore the insides of android, then go manually but be advised that there is a learning curve. In which case I'd suggest starting with reading the documentation of AOSP. Different goals have different paths to take :)
[Magisk] wfred:
Yeah, but if he's going by majority rules

View attachment 6041378
[Magisk] D€INOS:
Well , let's poll the majority for clarity:

yes

or

yes , but only if the update have ideas to make it work indefinitely
[Magisk] ziddey:
Not sure if this has been reported, but I didn't find any hits.

Using dev v1 and pif.json, I'm seeing:

12-07 14:58:41.911 7891 7891 D PIF/Native: Couldn't find '__system_property_read_callback' handle. Report to @chiteroman

Logs show it still attempting to spoof, so I may just have a banned fingerprint. I'm assuming that checking integrity in the play store will show the original data?

Pixel 7 running the latest beta, AP11.231020.016.A1
[Magisk] BrimoFan123:
Everyone who is voting for the PIF with fingerprint included is like this man with a saw on this picture:

View attachment 6041379
[Magisk] sawdoctor:
Unfortunately atm there is no other way simple as that. No one knows of any other way to spoof PI and there's a finite number of prints. Quicker we burn prints quicker EVERYONE FAILS play integrity. It's that choice whether we like it or not
[Magisk] HippoMan:
Yes, so voting for a print to be included for everyone to share means that you're voting for the entire procedure to stop working altogether at an earlier date.

Maybe people want that.
[Magisk] wfred:
Ditto here.

I gradually built up a stockpile, but have been using the same print since pif.prop was all the rage 😁
[Magisk] Vision:
Oh understand. Classic 😎
[Magisk] V0latyle:
Well, the potential pool is much bigger than that. Much, much bigger. One of our members tested upwards of 50,000 prints and came up with over 6500 working ones.

Minimum Android version: 5

Minimum API level: 21

Max launch Android version: 9.0

Max launch API level: 28

Note: The "max" is by no means a hard and fast rule. I've personally tested Android 12.1 prints that work, although generally only with the API changed to 25.

Device must have launched with Android version no higher than 7.1

Device must have been updated to at least Android 8.0.0

FIRST_API_LEVEL can in some cases be left blank but it MUST be no higher than 30
[Magisk] HippoMan:
And I, for one, would vote "yes" for something like the following:

We come up with a simplified procedure to automatically find and return prints to requestors.

The person can go to some sort of "http://find-me-a-unique-print.net" web site, and after supplying an email address, what gets sent back to that address would be a print that has never been issued to anyone else from this web site. And there could be restrictions on how many prints could be sent to the email address during a given time period.

This would take a lot of work for the developers of this proposed web site, but it would make it a lot simpler for people who don't want to hunt for their own prints.
[Magisk] zgfg:
You have spoofs that will work indefinitely?!

(Like perpetuum mobile)
[Magisk] rom-g:
or maybe those who voted yes are google employees
[Magisk] D€INOS:
14.2 had adjustments, and even though I'm not using it as I use a custom fingerprint, I believe 14.2 still works, that's much longer than 14.1.

In other words, there is this to test in the future, and I'm in favour of potentially burn a fingerprint for that reason.

But not because users aren't doing research in how to use a custom fingerprint.
[Magisk] xSnowLeopardx:
Still chilling with my first found FP on v14.

I know I keep saying this, but I want people to know this, and since the thread gets like 5-10 new pages a day, it gets snowballed.
[Magisk] D€INOS:
No, like I said, moving forward, ideas will come up adjusting code , and testing this may result in a burned print or two. I would be for that.

Everything isn't white or black, there are shades of grey.
[Magisk] Compass Linux:
I've made/tested around 10 PIF's and none of them work, so either they're blocked and/or I'm doing it wrong. So in this regard I'd rather have the PIF included in the module than make my own fails.

If this isn't appealing to other people, I'll pester Google to enforce MEETS_STRONG_INTEGRITY, so the idea above is better. 🤣

Compass.
[Magisk] D€INOS:
What's the difference between outing developers.google.com/android/images and other repos? I thought it was frowned upon linking the actual source?
[Magisk] Claus….:
@chiteroman I think the best way forward is own prints, eventhough I have struggled myself with it for a week! It pays off.
[Magisk] V0latyle:
It's pretty common knowledge where Pixel firmware is available. I would generally say repos are OK (my opinion, not moderator policy) in this case as long as we don't mention specific devices and/or builds. With the proper criteria, users will know what devices to check

What we don't want to do is link a repo that's full of working prints, for example.
[Magisk] arda99:
Now if he add one more option:

release without FP and publish FP in TG.
[Magisk] zgfg:
There are also good ones among those launched with A 8 1 (API level 27)
[Magisk] D€INOS:
I ask because that pixel firmware repo was the first result for me a week ago when picking up a print. Took me < 30 minutes to setup.

But I figured that one should do each own research to I didn't link it here.
[Magisk] Nodens:
The problem is that the wording is severely lacking in proper explanation of the choices. If you ask people if they want to keep getting fps that work they will always say yes.

The wording should be this instead:

"Do you want me to keep updating the module with working fps as they are banned, being fully aware that the pool is limited and doing so helps drain the pool with the guaranteed effect that no one will have working prints, AT ALL, in a couple of months?

If you say no then you would have to follow the detailed guides and use the tools freely available to get your own fps that will last for a very long long time."
[Magisk] sawdoctor:
It's not about what is appealing it's about understanding if chiteroman keeps supplying prints they will run out quickly and then that's it they've gone and the module is dead simple as that. As long as people who want him to supply prints understand you've got a couple of months and then it's gone for good . If people are happy with that then don't worry
[Magisk] Nodens:
This is not what you think it is. It is a hooking failure.
[Magisk] alonsoj636MW:
View attachment 6041393

still rocking with osm0sis fork and my 1st print found the past saturday!

pd: first time i got so interested on a xda thread... reading this has become a daily task now :)
[Magisk] Vision:
No one has even a little basic knowledge to search fingerprint and make the pif.json on their own ? All say yes to this ? yes mean bad for users who found hard a working fingerprint

I know the saying goes: Those who know should help those who don't know

Is 2 sides of the same coin

Unfortunately

View attachment 6041407
[Magisk] Nodens:
Yes it is, the point was to point people not familiar with the internals to builds that are easy to find where the props are and those that are more complete in what they include in their build.prop files. The further back you go things can get.. weird.

There are working fps beyond that. But they are rarer to find. So for making it easy for people, this is a good guideline to follow in general.
[Magisk] Nodens:
This requirement is technically not feasible. There are not enough fps to do this. Plus the system with emails is easily abusable by both sides of the fence.
[Magisk] zgfg:
Yeah. Silent majority
[Magisk] V0latyle:
Right, there's some outliers.

Yes. HW attestation was available 7.0+ but not required until 8.0

So as a general rule:

Device must have launched BEFORE Android 8.0, but AT LEAST Android 5

Device must have been updated to AT LEAST Android 8.0 in its lifetime

So...after Q4 2014 and before Q3 2017
[Magisk] Vision:
Yeah understand, but unfortunately yes mean bad for users who found hard a working fingerprint

I know the saying goes: Those who know should help those who don't know

Is 2 sides of the same coin

Unfortunately
[Magisk] david2089:
The new PIF file has a new value "VNDK_VERSION" - can't find it anywhere
[Magisk] HippoMan:
Well, then instead of a single recipient for each print, maybe there could be a maximum number of recipients for any given print. Not sure what a good number would be ... 10? 100?

And it doesn't have to be a web site and email address. Some other mechanism could be utilized for providing the print. Perhaps it could be via the PIF module itself. Maybe that module could install an adjunct app that the user could use to request a print for that given device.
[Magisk] maxmax0:
Check what I quoted, my post was about him putting it up for a vote, not for supplying prints.

If you check my other posts you will see I am strongly for a "bring your on fingerprint" solution. My print is working fine so far and I would like it to stay this way :)
[Magisk] stanley321:
I want to see a poll for us XDA member here. See if more people vote No.

I just voted too. If you have Telegram please vote too

https://t.me/playintegrityfix
[Magisk] V0latyle:
getprop | grep 'vndk'
[ro.product.vndk.version]
[ro.vndk.version]

I still like the randomization idea...
[Magisk] Nodens:
It refers to the NDK (Native Development Kit) and specifically the Vendor NDK version. You're looking for ro.vndk.version in vendor build.prop, like first_api. BUT, as far as I am aware, there's no evidence of this being used.
[Magisk] HippoMan:
Randomization could be utilized in my proposal.
[Magisk] glennza:
It's a bit like asking schoolchildren to vote on whether they want salad or pizza for lunch!
[Magisk] badabing2003:
Not only the wording is bad, it's worded in such a way to get favorable response for one option.

To add to that, tell me about the pool of people who frequent that TG, if your print on a platter stops working, where are you going to go looking for one? or asking for immediate serving?

People who find their own prints don't necessarily frequent a channel that is full of such noise.
[Magisk] zgfg:
I showed you the example for device launched with A 8.1
[Magisk] V0latyle:
Yes, but again that's the exception, not the rule...right?
[Magisk] zgfg:
No, there are more 'exceptions'
[Magisk] V0latyle:
I know, which is why I said there are outliers.

My point being: As a general rule, we know that prints of most devices shipped Android 5.0 > Android 7.1.2 should work. Yes, there are some exceptions to this, but they are indeed just exceptions and most devices shipped Android 8.0+ shouldn't work

Unless you know of a better way of putting it
[Magisk] sawdoctor:
Sorry really wasn't getting at you or trying to. Just trying to get some users to realise just what is going to happen if we carry on as we are. Unfortunately i don't think the majority of users realise there's no alternative once we run out of prints that's it no one ever passes play integrity of a rooted device ever again
[Magisk] V0latyle:
Never say never. Someday someone will figure out a new way to break PI
[Magisk] Nodens:
Indeed and you can find devices launching after 8.1 as well. Some OEMs launched devices that do not support HA, with newer android builds because those were available at the point. Not everyone opted in to modify their existing designs that were planned for launch but they did opt-in for the newer android version because that's good for marketing anyhow.

Still, the point is that these are much rarer and we shouldn't advise people to look there as they would easily get discouraged trying to find the proverbial needles in the haystack. If someone's bent on doing so, they should not look at the big names and flagship models. Look for budget devices from lower budget OEMs. And not necessarily phone devices ;)
[Magisk] sawdoctor:
Hopefully but you get my point. Users do need to understand what the alternative is to finding fingerprints themselves. Yes it's a pia but certainly better than not being able to use PIF at all because all the prints have gone
[Magisk] zgfg:
I would say RARE examples can be found launched even with A10 (FIRST_API_LEVEL 29)

But if I didn't see with A11 (30), it doesn't mean there aren't those here who maybe did (some ppl have mined out hundredths of working FPs)

Btw, I was just investigating now about one that sites declare as A11 phone but I finally ran to the pre-release article showing its A10 specs - hence it should be still FIRST_API_LEVEL 29
[Magisk] purgy:
All up, it took me around an hour to read @osm0sis fp hunting guide a few times, update pixel flasher and read through the how-to by @badabing2003 for extracting pif files, and run through prints till I found something.

I'm pretty sure that a lot of people using the "easy" method have spent a lot more time than that trying to get a pass lol.
[Magisk] osm0sis:
Devices that shipped with 8+ still work fine, not sure where you got that part..

My guide says Android 9+ (FIRST_API 28) is where things get less likely to work, but there are definitely a lot of exceptions when you use those prints and adjust the FIRST_API value lower than it's real number.
[Magisk] xSnowLeopardx:
Interesting. One of my backup working FPs has A10. I was recently looking to push it to a later OS. Failed to find 11 or later haha. Would be a "fun" treasure hunt. Of course, only if 11 or later is obtainable.
[Magisk] Nergal di Cuthah:
@badabing2003 if parts of the needed data is in vendor instead of system. Do i just compile both into a single prop file for pixel flasher to parse?
[Magisk] osm0sis:
oriole launched with 12, so definitely obtainable.
[Magisk] xSnowLeopardx:
Oriole?
[Magisk] osm0sis:
oriole

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Magisk] Nergal di Cuthah:
Pixel 6

And that's the end of my codename knowledge, something finding a fp seems to require more of
[Magisk] xSnowLeopardx:
Hahaha thanks, I forgot that was its name
[Magisk] V0latyle:
Oh okay. I was under the impression that anything that shipped with Android 8+ would mean mandatory hardware attestation, but if we are talking about mixing and matching API versions then I think I see your point
[Magisk] zgfg:
Experimenting ruled out some of our dogmas😁
[Magisk] rom-g:
Looks like Fingerprints are the new bitcoin...
[Magisk] osm0sis:
I'm in the process of updating my guide to allude better to some of our more recent findings. 👍
[Magisk] HippoMan:
Well, no one has tried investing in them yet.

And unlike bitcoin, they actually *are* a scarce resource.
[Magisk] badabing2003:
Yes you can do that, as the current released version only processes a single file.

Alternately you could lookup the FIRST_API_LEVEL in the vendor, which is really the one missing, and just type in the value as you're pasting / editing it in "Edit pif.json" window
[Magisk] xSnowLeopardx:
Great tip, didn't even think of that.
[Magisk] beeshyams:
Thanks. I didn't know about this. Care to tell me how to do? Wonder if this trick works on Signal too
[Magisk] asripath:
And pivot to a new thread would be nice
[Magisk] osm0sis:
People are free to discuss my fork in my Odds thread, but if the rabble becomes too much there I may spin it off into its own.

Edits are done for now, by the way, here's the new wording, and hopefully it's a bit easier and more accurate now:

- The device must have at least been upgraded to Oreo (Android 8) to possibly work, which also means it should have received an ro.*.first_api_level in its system (8.0) or vendor (8.1+) build.prop; the earliest working devices I've seen have First API Level 23, which is Marshmallow (Android 6). Note you can still use the pre-Oreo fingerprints from these devices however!

- Devices launching with Pie (Android 9) or later have a First API Level 28+ and seem less likely to work out of the box, though there may be exceptions. The FIRST_API_LEVEL field should always be set to avoid the fallback to actual device value possibly triggering HARDWARE_BACKED evaluationType in SafetyNet depending on the fingerprint, and thus ensuring consistency of results across host devices. Start with it at the correct value for the fingerprint, but if the device's First API Level is 33+ you'll definitely need to lower it to 32 or less to keep BASIC evaluationType in SafetyNet, and note some fingerprints may also need it set to 25 or less to keep BASIC.
[Magisk] Compass Linux:
Many thanks for the script. It helps a lot.

Unrelated to your script: Unfortunately I've just made about 10 pif.json's and none of them worked. Now I have a total of 24 files with zero success. I've tried, I give up. Back to using 14.2.

Compass.
[Magisk] jnss98b:
Sadly I ended up using 14.2 as well. Tried about 15 fingerprints but seems like they're all burnt already. I don't think I have as much knowledge about image dumps to be able to find high quality ones
[Magisk] Imnoa:
Use Pixelflasher to quickly create, import and test pif.jsons, this way you can test more prints faster
[Magisk] purgy:
To add to this, pixel flasher just requires the .prop extension, you can copy paste build.prop into a text file, rename it to whatever.prop then run it through pf.
[Magisk] sawdoctor:
GitHub - Sakion-Team/Re-Telegram: An Xposed module to enhance the Telegram

An Xposed module to enhance the Telegram. Contribute to Sakion-Team/Re-Telegram development by creating an account on GitHub.

github.com

It's an xposed mod that works on most telegram clients
[Magisk] acwcanada:
@osm0sis

I have 3 json files and two of them are working on both your Fork v3 and @chiteroman's v14.0, one of them which come from one of my old Chinese phone which believe to be a Nougat when it first come to the market, the json which obtained from it's build.prop is able to pass both basic and device integrity on @chiteroman's v14.0 but always fail the device integrity in your Fork v3. Are you able to give idea/suggestion? Thanks
[Magisk] Emmes:
try your 24 json's with modified First Api Levels again!
[Magisk] Gersp52366:
+ I didn’t find any mention of nvdk in my build.prop
[Magisk] Imnoa:
Correct, I have just downloaded a buttload of build.prop from some obscure chinese phone brand and I had about a 30% succes rate with these trying them one by one with Pixelflasher, I didn't even bother to lower the first API level for those otherwise it might be higher.

I now have a stock of about ~20 working fingerprints to use.
[Magisk] zgfg:
Public live GitHub counters for Play Integrity Fix downloads​

https://github.com/zgfg/Etc/blob/main/PIF.md
[Magisk] dedalos91:
So after all this we must have a backup of some number of pif.json
[Magisk] Iridule:
How many prints should one person have. Do we each need to get as many as possible or will a few suffice? I've found 3 so far.
[Magisk] Imnoa:
It depends, if a lot of people are gonna use that specific print it will get banned sooner or later I guess, If you found a shiny, rare one nobody uses you're gonna be good for quite some time probably.
[Magisk] Wolfcity:
Same! But still searching. Thanks to @osm0sis for the script and the great tutorials.
[Magisk] Claus….:
How do you know what is rare?
[Magisk] Imnoa:
You don't, it al depends on how many others found it.

But my guess is a lot more people are using a Samsung Galaxy S20 fingerprint (just an example, these won't work) than there are people using a fingerprint from a YingYingYang X384y2 of some obscure chinese phone brand they extracted from the rom themselves.

80% of my working prints are from phone brands i've never heard from before.
[Magisk] Gersp52366:
The rarity of pif depends on the brand and on the popularity of the model of the donor device and on the availability of the print on the Internet
[Magisk] wfred:
Could you please edit out the link to the repo
[Magisk] wfred:
Don't need to rename it or even close the file. Just paste over whatever is already there, save, then point PF at it
[Magisk] osm0sis:
Check my previous quote for what I've found so far for people reporting similar issues. I'd be happy to take a look at yours as well if you're willing to PM me with it.
[Magisk] vindicatorr:
The only one I use and should have no bearing on passing or not is the battery charging one (ACC).

EDIT0: Since I had been seeing mention that Shamiko should also be used, I went ahead and added that with the same fails.
[Magisk] ipdev:
Hi. 🙂

I have been testing this module in between some other things today.

First time giving this module a try. 🙃

Pixel 6: Android 13 (20230705)

Magisk 26104 (6141bb5bb)

Long story short..

PlayIntegrityFix v3.0

Works out of the box with no other modules or configuration.

Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY, MEETS_STRONG_INTEGRITY]
Build fingerprint: google/oriole/oriole:13/TQ3A.230705.001/10216780:user/release-keys
Brand: google
Device: oriole
Model: Pixel 6
TestId: dGVzdGluZy1mYTFmODhjYi0zM2IxLTQ0MGItODc0ZC02MDdhYmZlMDc5YTg=

For the record.

com.google.android.gms|com.google.android.gms

com.google.android.gms|com.google.android.gms.unstable

Should be the only processes that you need to target for SafetyNet and PlayIntegrity. 😉

Spoiler content hidden.

Cheers. :cowboy: