yashsingh1/xdaforums huggingface dataset:
[Magisk] downhere:
We don't have insight to what Google is doing. What everyone sees is that Google is trying to fix every hole that was found here. So their intention is a proper working PI implementation which means: No foresight. No guess. It is a game.

Until today this PIF used public prints, and Google was able to defeat them within one day recently.

If you depend on proper PI "forever", forget this thread and use stock phone.
[Magisk] Nergal di Cuthah:
Days, weeks, minutes. None of us are google spys, or if we are we'd be stupid to say.
[Magisk] Nezorflame:
Took me around 2 hours to find the working combo, but finally found one, so the method definitely works.

Big thanks to @osm0sis for the guide, @Bonoboo for the Tasker tip and of course @chiteroman for making this possible and continuing the fight.
[Magisk] digger16309:
Agreed - the greatness of Android is the ability to customize it (and block ads). If this is the beginning of the end of that, what's the point, other than, it's not Apple? If my choice is: locked down Android device, unlocked Android device that has crippled functionality, or locked down iOS device, I might as well go with iOS. They certainly hold their value better.

I'm hopeful though that this isn't the end of the reasonably simple solution.
[Magisk] DarkestSpawn:
Running on Lineage OS 20 TD Based GSI.

Have Magisk Delta installed and PIFs newest versions.

Used the Build Prop info from for the LOS GSI first (Failed) and the original ROMs (Also failed).

The only thing that's failing to work for me is Gmail and I have wiped Play Store, Services, and Gmail. Even removed my Google account and nothing was fixing the Gmail crash.
[Magisk] aNGERY:
I couldn't have gotten lucky on my first try, could I have?

Deleted
[Magisk] zgfg:
Yesterday when I estimated that about 5% of users will be successful in mining, it was strongly opposed by some, that I was underestimating the people, that all theory was posted and tools published hence one must just try and so on

So how about that success rate now?

Counting on all today's responses here. And what about the silent majority (did they try or not, succeed or not)

Btw, I didn't say that 95% of users are too stupid to make it.

There are many factors here. Even if you understand things very well and you grabbed the tools and know where to look for the prints - it still goes very slow and you must be lucky to pick up a working one

---

Eg, about myself. So far I spent the free time that I had today for mining for the prints and to prepare the JSON files for testing (first of all to prepare the tool to make me all those JSON files)

I have how 64 JSON files prepared with prints from devices that were originally released with KitKat, Lollipop and Marshmallow

If I will still be hungry, I have 62 more with Nougat, and 93 with Oreo.I don't know about the cholesterol side

So far I tested only 6 and none of them was good.
[Magisk] dlads:
For me, I'll just use my card... Being able to pay on my phone really isn't worth the hassle.

It's a bank card at the end of the day.. not exactly a weighty object.

Good luck with your future endeavours. 👍🏼
[Magisk] osm0sis:
I'd focus more on Nougat and early Oreo if I were you... Lots there, and don't even require a SECURITY_PATCH.
[Magisk] adriantc_ro:
Guys - after some 4h of trying I finally managed to find a PIF that works for me. Some things to be aware of in your search:

1. It seems on my phone installing a new version does not overwrite the pif of the old one. Took some time to figure out I have to manually delete the pif.json file from /data/adb. After you install the custom Play Integration Fix always check the pif it actually installed and double check the content is what you expect.

2. I haven't had success with Xiaomi build.props although I have tried 6 or 7 (starting from 8.1 down to 7.1). Don't know if I am unlucky or they banned a lot of them.
[Magisk] Immortalis:
I just succeded too. The method definitely works, don't give up guys
[Magisk] Virnik0:
I am honestly thinking about giving true Linux phone a go. There are few options, none great HW/feature-wise, but still good to try. I am also annoyed by constant restrictions Google and others tries to enforce on me. Company BYOD was also a hell to do properly so they won't notice anything...

For now, I do pass the checks, found a FP I can hopefully use for some time.
[Magisk] V0latyle:
You need to find these values in build.prop:

Then using a root file manager, navigate to /data/data/adb, open pif.json in a text editor, and fill in the values

You can also do this remotely via ADB shell, or you can create the file on your computer (use Notepad and save as "pif.json" then ADB push to /data/data/adb

I've tried to make this clear to you: I'm not going to hand you a ready made solution. That seems to be part of what gets this defeated so fast. Learn to do it yourself; it's Friday night and you have all weekend to figure it out.

Maybe someone else will but there might be some safety in diversity with everyone finding their own print that works for them; if a bunch of people start using the same one, that increases the liklihood that it'll get banned.

Your alternative is flash back to stock and lock your bootloader.

As I have tried to explain many MANY times, this has absolutely no bearing on the openness of Android. Play Integrity is NOT part of AOSP; it is a Google proprietary API, and they are not obligated to allow people like us to use the API, or apps that depend on it, outside of their prescribed security environment.

Google isn't locking Android down or preventing us from modding our phones. What they are doing is making THEIR OWN SOFTWARE, not Android, more secure.

They aren't even preventing us from using Google Mobile Services, but I think it's worth reminding you that they don't owe us the ability to do so, and we're ultimately complaining about a few apps that aren't supposed to be working for us in the first place.

If you want Google out of the picture, swap to a ready made custom ROM like CalyxOS or GrapheneOS. They're deGoogled. You probably won't be able to use apps that depend on GMS or other Google APIs but you get Android without Google.

Gmail most likely has nothing to do with Play Integrity

Despite many warnings you've posted something that can be used to identify your phone and revoke the print you're using. Good job.

Again, I feel the need to point out the only restrictions they're enforcing is with their own apps and APIs. They aren't restricting Android

If a company wanted me to use my own device for work, I'd tell them to kick rocks. If you want me to be reachable on the go, you're going to provide me with a company phone. I will NOT use my personal phone for company use, no exceptions.

DO NOT share it with ANYONE, please.
[Magisk] aNGERY:
But that's not actually the fingerprint I'm using. That's showing my stock Oneplus 10 Pro fingerprint.
[Magisk] Virnik0:
Don't worry, I am not going to share it. As for company asking me - they didn't - I was just annoyed for having to use corporate phone, which was inadequate, slow, and was basically a pain to use. But since they were changing the BYOD model which demanded higher access rights and basically root, I wiped out its sandbox partition and got rid of it. Lazyness + convenience pushed me to test my limits, successfully. But then it was too much of a hassle.
[Magisk] V0latyle:
Fair, but I think we should avoid posting anything identifiable.
[Magisk] Umgak:
That testid can (maybe) be tracked back to you. I'd black it out, personally.
[Magisk] famewolf:
This is all subjective....if they make it where I can't easily use google pay then I just won't use google pay...life will go on.
[Magisk] aNGERY:
Part of me wants to argue. The other part of me wouldn't be surprised if they had nothing better to do.
[Magisk] kevinwu128:
When I update the pif.json file, i reboot my phone and it still has old fingerprints when i do a check in playstore. does Pixel Flasher generate Fingerprints for my device? it's very confusing. I'm not even sure how I can extract a fingerprint without another phone of my model (Samsung S20FE) SM-G781B. Or am I able to use

"PRODUCT": "r8qxxx",

"DEVICE": "r8q",

"MANUFACTURER": "samsung",

"BRAND": "samsung",

"MODEL": "SM-G781B",

And then for the rest:

"FINGERPRINT": "ANY FINGERPRINT OF ANY MANUFACTURER

"SECURITY_PATCH": "STILL UNSURE HOW TO SEE THIS ONE"

"FIRST_API_LEVEL": ""NOT SURE WHERE TO FIND THIS TOO"

I"m definitely not a developer, so some of these terms are way over my head, but i'm determined to get it working! If anyway wants to PM me also, happy to pay for their time
[Magisk] Umgak:
LOL, exactly. We know that they definitely see us, they might have some bored intern on this thread.

Glad to see it's working for you though. More success stories will hopefully drown out some of the catastrophizing.
[Magisk] Nergal di Cuthah:
The fingerprint visable, to you,on your play integrity check will be of your actual phone, not the spoofed values.
[Magisk] zgfg:
They don't require Sec Patch if I would have prints from their original ROMs from 2016, 2017 or arly 2018

But if it is eg Eva (codename), First API level 23 but where I only have prints from the Nougat FOTA from the summer of 2018, then by theory, Security patch is needed (I'm prepared to edit the JSON and test also without)

The problem is in the validity of the input -:the table that I used to programmatically create hundreds of pif JSON files

With all respect to the retired XDA developer (and later retired moderator) I found the flaws in his table. For Huawei devices (few that I checked and I know more about from those times) he lists eg original (Android) version 7 but device had original EMUI version 7, meaning that the original Android version was one less, so 6.

I think I even asked him back then to fix but he was unfortunately already leaving XDA.and Magisk community. Nevertheless, his excellent documentation, and that abandoned thing (with that table) still remain (now, frozen in time)

Hence I must also test with those variations. But I would be surprised if it results with more than few working ones
[Magisk] HippoMan:
I'm sincerely glad for your success, but my big question how long-lasting your success will be.

The Googlefrinchians have been rather quick lately at discovering and then demobilizing fingerprint-based solutions.

I hope yours will endure! ... and if so, could you let us know here, in order to help give us hope?
[Magisk] Umgak:
The fingerprint in pif.json is passed to DroidGuard to force a BASIC attestation. It doesn't need to have anything to do with your actual phone - and shouldn't! It won't show up anywhere else, either.

You're looking for the build.prop file from an older (think Nougat/Oreo era) phone.

I found my props from an actual phone (running the command getprop in an adb shell) but a lot of system image dumps of various phones exist online. @V0latyle has a good rundown on which props go where here.
[Magisk] simo2001:
In all the firmwares I download, Oreo mainly, I always find the system build.props but vendor never have a build.props. Do you know where can I find it?

(I've just mounted system.img ~ I have also the following View attachment 6039179

How system mounted appear.

View attachment 6039176

View attachment 6039177
[Magisk] HippoMan:
Maybe instead, we could only post lots and lots of pif.json which superficially *looks* identifiable, but which actually contains totally faulty fingerprints which could never work.
[Magisk] adriantc_ro:
Why don't we develop a pif building app that would scrape known build.prop dbs, random check them against Play Integrity and then return it to the user. That way we would have a fair distribution of fingerprints, users would have an easier life and Google can have a harder one.
[Magisk] HippoMan:
You and I have had our miscommunications and misunderstanding-related differences in the past, but that's water under the bridge, and I just want to let you know that I'm totally with you on this.

Card-based payment is where it's at.
[Magisk] Homeboy76:
Welp, I just read the last ten pages of this thread. There are many insightful comments, but none from the thread starter. I could be wrong, but it seem to me he no longer has any interest in it. His loss of interest in this thread may be caused by his 'new' Telegram "channel/thread". I don't know. I do know he deleted all versions of Play Integrity Fix but 14. Some, of the versions deleted were reported as still working by XDA members in this thread.

Maybe, it is time to read @osm0sis How to create and use his gen_pif_custom.sh file.

While we wait for him to release a fork.

Just my 2¢
[Magisk] digger16309:
Technically correct but not practically so. If it was that easy, everyone would just use an unrooted device with a de-Googled custom ROM, right?
[Magisk] HippoMan:
... and then people here could report how great many of these prints work ... with others posting admonishments to please keep our successful prints private.

After all, given how much the Googlefrinchians have bern inconveniencing us lately, we might ad well have some fun inconveniencing them in return.
[Magisk] Nergal di Cuthah:
Isn't that just like a hour ago? (reality it was 8 hours)

He literally released a version today

He deletes old because they are "banned" (i got lost did we come up with a new term)
[Magisk] kevinwu128:
OMG thanks. I managed to get one from somewhere and it was a complete different model. Works fine and i understand what you mean now! THANKS.
[Magisk] HippoMan:
That TG thread is much less useful than this thread. It gets 1,000 or more messages every day, and it's impossible to keep up with. And it has a much higher percentage of off-topic posts than what we get here.

And yes, I agree that the other fork you're suggesting would definitely be beneficial.
[Magisk] fillwithjoy1:
just go cash lol
[Magisk] HippoMan:
I kind of like the term "banned" actually. But given there's a push to stop using it here, I propose that we still use it, but just spell it differently.

Let's just start saying that prints and modules have been "banana-ed". :)
[Magisk] HippoMan:
... or better yet, simply barter.
[Magisk] Nergal di Cuthah:
I'll give you three snegs for one bobble
[Magisk] fillwithjoy1:
lmfao, i could imagine the conversation being

"yes how would you like that smartphone for 20 cows"

"deal"
[Magisk] fillwithjoy1:
Either way, both Play Integrity apps are API throttled so, I think Google knows that they have done something right for once
[Magisk] raulci:
After 4 or 5 hours investigating, reading, learning, searching, I've found a PIF that works for me.

Tips I learnt:

I was using Osmosis script that could be great, but some of the dumps I found they didn't have the vendor-build.prop file, so the script didn't work (at least for me), BUT the one that finally worked didn't have that vendor, so I finally learnt how to create that pif.json file manually, it's very easy. Just create one with Osmosis' script with the 2 build.prop files (the system and vendor files) and then look for those values in your .prop files. Then, if you find a firmware with just the system-build.prop, you can manually create it. As said, that was the case for the PIF I found that worked for me.

I found some Oreo 8.1 images that had first_api_level = 26, none of them worked. You need to find one that its first_api_level is 25 or less.

That is the hardest part for me. Looking for build.prop files.

The easy way for me to test it was:

Install PIF v14 and reboot.

I built the pif.json file in my computer.

Phone & PC connected via USB.

Copy the generated pif.json file to phone.

Then in the phone, copy the pif.json file in /data/adb folder. You can do that via command line.

And then to test the new file, you don't need to restart the phone, just kill GMS and test it, as I've learnt reading the thread. From termux as root execute command

killall com.google.android.gms.unstable

. Now you can test it, in my case, I used Play Store > Config > General > Dev Options > Check Integrity (you need to enable this option, it's not visible by default).

Sometimes in Labels, I saw empty list [], sometimes just [MEETS_BASIC_INTEGRITY], and finally the desired [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY]!

If you don't have [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY], just build another pif.json file and repeat the process.

Hope this helps someone as it helped me to read all the info in the thread!

Thanks!
[Magisk] chiteroman:
PPU: Make CTS/Play Integrity pass again (again and again and again) · Evolution-X/frameworks_base@63ab5a3

[someone5678] Adapt to this project Co-authored-by: Dyneteve <dyneteve@hentaios.com> Change-Id: If3a865849c7c99a9c7080114ba94a8f8878bb4f2 Signed-off-by: someone5678 <someone5678@users.nor...

github.com

EvolutionX rom now downloads the fingeprint through online Github repo so there isn't need to reinstall new rom.

This give me an idea. As many of you don't know how to modify this. We can do the same.

I can create a repository on GitHub that contains the JSON with a valid fingerprint, the module would read this file and use these properties. I could designate several administrators of the repository so that if I am not online, someone can modify it in case Google bans it.

Obviously the custom JSON would be preserved, if the /data/adb/pif.json file exists it would use the properties of that file and not the online one.

What do you think of the idea? This would be better than releasing 4 versions per week xD.
[Magisk] Homeboy76:
Was that version released in this thread?

The last version is 14, the previous version was 14 beta.
[Magisk] HippoMan:
Is this a new meaning for the word "right"? :)
[Magisk] Nergal di Cuthah:
Fourteen was released today in my time zone (or overnight whilst i slept)
[Magisk] V0latyle:
Did you completely miss the point of the last several pages?

This module used to include prints. Google has quickly been blacklisting them. So, instead of including prints, we now have to find our own.

The module isn't dead, there's just no reason to update it because the only part that would be updated are the prints that we have to find on our own anyway

Not if you want to use the Google ecosystem, which most third party developers require.

Eh...I think part of the problem we've been having is everyone using the same print. Don't know for sure of course but I think there is strength in numbers so if everyone is using different ones, just maybe it'll make it harder for Google to blacklist?

At least until they start checking every single device for mismatch
[Magisk] HippoMan:
It certainly would be helpful!

I'm just concerned that the repo would have to be frequently updated as the Telephone Sanitizers keep banana-ing the props that initially work.

The moderators would be very busy, and it would be an ongoing race condition between the Googlefrinchians and us normal people.

But it's still definitely an improvement, IMO.
[Magisk] adriantc_ro:
I suggest compiling a big list of working fingerprints (could be a crowdsourced operation) and whenever a user installs the PIF is just randomly uses one. That would be harder for Google to ban.
[Magisk] Homeboy76:
No, I did not miss the point. I just added my 2¢.
[Magisk] HippoMan:
Agreed. And we could come up with a utility that we could run manually (and maybe also even automatically at boot-up time) which would download and install another randomly selected print.
[Magisk] Nergal di Cuthah:
I love the idea (having been as yet unable to find these mythical databases) but like the others, fear a mass banana could occur.
[Magisk] dcarvil:
How would that stop Google from banning that fingerprint, further depleting the pool of working fingerprints? I think the current situation of having everyone find their own fingerprint, is the best way of keeping the pool of working fingerprints as large as possible. Yes, it is a real PITA, but it is a workable solution, for those willing to invest the time.

All the information needed is in this thread, but it is obscured by all the inane comments posted here that have no value.
[Magisk] jabennett:
I'm afraid your module has become a victim of its own success, and any further attempts at centralized distribution of functional fingerprints will just accelerate their blocking and ultimate exhaustion.

I know many users have been spoiled by how simple you initially made this for us, and are understandably confused and freaking out at the new requirement to provide our own pif.json. But we're now engaged in a rapidly escalating game of "whack-a-mole" with Google (with a finite and dwindling number of "moles" available), and focusing all your users on a single fingerprint at a time just makes it easier for Google to whack.

TL;DR: I think the current "roll your own" pif.json solution is likely the best possible compromise between functionality and accelerated extinction.
[Magisk] neelchauhan:
I kinda just reverted to OxygenOS and locked the bootloader, for now at least. Surprisingly, the version from the EDL failed Play Integrity even when I locked the bootloader, but after an OTA now passes it.

On a test HW-attested device (Pixel 7 or 3) I will try it to make sure it works or not.

While it may be overkill, but I strongly feel European Android modders should push their MEPs to investigate Google over this. Use the points that (a) Google is checking our hardware directly to ban our access (privacy laws) and (b) LineageOS and custom ROMs are a "competitor" to Android and should have equal access to Google Play (DMA), especially since Play Services are a "gatekeeper" service.

Why? Look at how the EU is regulating Apple, regulating the iPhone with RCS, USB-C, and sideloading. If we have the political will, why not use this opportunity to fight against Google's HW-attested Play Services? Even if we all know LineageOS isn't actually an Android competitor, it's still a competitor to the stock ROM, and (hopefully) that's good enough for the EU.
[Magisk] HippoMan:
Just keep in mind that it's not simply a one-time investment of time. The discovered prop is very likely to be banana-ed in the not too distant future, which means another time investment ... and then soon another ... and another ... and another ... ad infinitum.
[Magisk] jabennett:
Unfortunately, the main reason the current solution still works, is its decentralization and relative obscurity. Any central valid fingerprint or list of valid fingerprints becomes another target for Google to invalidate, and the bigger and more useful that list gets, the bigger and more conspicuous target it becomes for Google to strike down all at once.
[Magisk] HippoMan:
How about if we come up with a tor-like, decentralized randomized prop delivery network whose contents are constantly being crowdsourced?
[Magisk] V0latyle:
Or Google just bans the whole list

Exactly, I think decentralizing this would be better. Any sort of central list would be quickly found and would just make it easy for THEM

So let's not make it easy for THEM and each find our own prints
[Magisk] SOCOM-HERO:
Looks like this is getting to be the end of root/unlocked bootloaders for me. Been doing this for 10 years and am just burnt out on the constant war on root users. May as well just get an iPhone.
[Magisk] V0latyle:
Then you still have a master list that they can easily use.

DMCA trolls set up torrent clients that participate in swarms of popular torrents to find IP addresses of other clients. In the same way Google could easily set up their own client and get full access to the list. For all we know there might be a few XDA members who are Googlers

I know this sounds ridiculously paranoid

But the only safe way to prevent mass blacklisting is for everyone to find their own prints
[Magisk] Bobb_o:
I'm looking at avbroot, at this point it doesn't look too bad.
[Magisk] Undam:
I found one :), If I don't respond to this reply assume it's still working.

PIF v14.0, Shamiko v0.7.4, Google Play Services NOT in Magisk Deny List, base device is Pixel 7 Pro with Evox 7.9.8