yashsingh1/xdaforums huggingface dataset:
[Magisk] GGYT_YT:
i still don't get it. I have tried like 50+ pif/prop fingerprints from android 8-9 phone stock rom dumps over last like <9 hours and none of them work (always basic). what should I do? I also don't have any android devices to use (I only have a Mi 10T that is also rooted + pif doesn't work).
[Magisk] digger16309:
Also Microsoft apps, hotel apps, probably airline apps, transportation apps - any app where the developer thinks security of identity is critical. This isn't limited to pay/NFC. That becomes a choice between locking down or severely crippled functionality. I got ripped for this earlier, but that is a practical lockdown of Android if not a technical one.
[Magisk] mates21:
Even if I set the correct values in the zip file and enabled the module in magisk? I'm asking because when installing the module, an error occurred about transferring the file, but after resetting the phone I have 2/3 pass
[Magisk] BrimoFan123:
Yeah :) and today I am so happy that a few years ago I didn't sell my old phone because the price was too high...:)

Now that phone made a work playing a role of donor for pif file :)
[Magisk] BROKEN1981:
With V14.0 you need a working PIF to move to data -adb
[Magisk] kodein:
Hi guys, I would like to ask where and how to look for fingerprints so I can try it? Thank you
[Magisk] HRSE:
In my country, GPay has limits, and the bank accounts or cards linked to GPay have even stricter limit than GPay, but more than enough for your daily groceries shopping. Contactless payment is not intended for high-value transactions or replacing the bank cards.
[Magisk] hayvan96:
All good after trying 4 FP, the last one did it. Had difficulties to add the cards of my main bank but it appears to be a temporary bug on the bank side, no problem for cards issued from other banks.
[Magisk] AlesiBoss:
Write build.props dumps into google and follow your instincts
[Magisk] BROKEN1981:
I'm having a huge issue figuring that out. Figured TCL is hardly known. So might not be on Google's radar. I know a 60 year old lady who has one. I never heard of it.
[Magisk] mates21:
I understand, but why do I have a 2/3 pass if I completed the file with my fingerprint in the zip file and only enabled the module without moving the file to adb?
[Magisk] BrimoFan123:
How to enable?
[Magisk] Dark_Diver:
Downloaded several fastboot FWs for several old phones with old Android versions (not the last versions, one of the first for device).

Extracted build.prop from them (only one was in the FW), created pif.json, tried.

7th pif worked. "Device is certified", [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY].

GPay is working.

But, last time, then I tried to add my main card to Wallet, it failed and my bank called me to ask - is all right with me? Why so many tries to add card to contactless payments? ;)

Thank you, people.

BTW, I'm using Magisk Delta with SuList.

All my banking, med and gov apps, which don't like rooted phones, are working.
[Magisk] V0latyle:
Stop using YASNAC

Use TB Checker or use native Play Store integrity check

Fingerprint will not appear in checker apps as the print is spoofed ONLY for GMS

Check PI response...

Only if device is broken; modified or custom kernel will fail verity checks and be untrusted

Moot because your previous assertion is untrue, you must not lock bootloader unless:

You are on clean unmodified unrooted stock ROM

You are on unmodified custom OS with custom root of trust - CalyxOS or GrapheneOS

No

Print must be from a device that launched before Android 9, but was updated to at least Android 8 during its lifetime. First API level (aka SDK version) must be at least 21, can be no higher than 27

Yes

Make sure GMS is NOT in DenyList

Don't modify the module. Edit pif.json in /data/data/adb

Clear data for GMS and Wallet or reboot

Wallet should cooperate pretty quickly if you start passing
[Magisk] xdatin1:
With v14 my banking apps works but Gpay wont
[Magisk] mates21:
What if I completed the file with my fingerprint in the zip file and just turned on the module and despite the error I got 2/3 pass? should I not change anything? :)
[Magisk] hassanhassan:
how do you search for them
[Magisk] Dark_Diver:
I did it after updating pif, all is working, as I said.

My bank blocked my card for adding to Wallet temporarily and called me to ask, what's happening. Because there were several tries to add card to GPay in last days - unusual thing for them, their security department reacted.

Another card from the other bank was added without any problem.

Already tried NFC, it's working.
[Magisk] xc112:
what is th difference PlayIntegrityFix_v14.0-resetprop.zip and PlayIntegrityFix_v14.0.zip
[Magisk] dank_spieler:
Hey, I have a question. Where can I get these fingerprints from? AND is it possible to find them somehow on the internet?
[Magisk] okij:
Since this has been asked not only by you but by many other users in the past two days:

Today I searched the web and finally found a very convenient guide to capture your own custom fingerprints, please see here: catpture fingeprints easily

I already generated ten custom fingerprints by this ingenious method, now I just need a way to put these into working pif.json files. 🤔

Any help on this would be greatly appreciated! 😇

If my ten fingerprints shouldn't work, I will just try my ten toeprints as well. I'm pretty sure that I'll get PIF working in the end. 🤣

@kodein: On a more serious note, you could just have a look at @osm0sis' comprehensive guide here: How to create and use a custom.pif.json!
[Magisk] GGYT_YT:
YAAASSS! AFTER HOURS OF TRIAL AND ERROR I GOT A FINGERPRINT THAT WORKS!!

-

I won't be sharing that fingerprint (obviously), but after setting the working one I can now use Wallet (I haven't added any cards since I tried way to much and it blocked me for 2 days)

and it meets DEVICE_INTEGRITY.

-

I would like to seriously say thanks to all of you who helped me through this rollercoaster (especially @V0latyle and @osm0sis , you're legends 💪).

Just need to test NFC payment at my futsal game today but in general, everything's amazing. ❤️❤️❤️
[Magisk] cyycolin:
O MY! Your post clear all my doubts then the first FP i found worked!!! LOVE YOU MAN
[Magisk] wrongway213:
This is all basically Google propaganda, as we've yet to see one single substantiated claim of root-assisted fraud. Telling the people you aim to control that it's for their own good is par for the course, imo we really shouldn't be helping them spread their lies, given we're the targets.
[Magisk] dmenezes:
Congrats!!!👍

Can you tell us if you got the build.prop files from a dump site, or from a stock ROM zip?

If the latter, what did you use to open the embedded system.img file?

TIA!
[Magisk] frank93:
his fork expects the file at /data/adb/modules/playintegrityfix/ btw, not in /data/adb/ (just saying in case you missed it).

7zip can open/extract those img-files just fine btw.
[Magisk] mumuli:
Do i have to modify all included pif.json or just fingerprint inside of that?
[Magisk] GGYT_YT:
Thanks!

From a dump site, though I don't want to get in trouble on this forum, so you will need to search it up.

As for ROMs tho, I tried to open it by default in Windows 11 and Mac OS file browsers, and it didn't work, soo I would suspect that you need a specialized software like Android Studio to open them
[Magisk] eXtremeDevil:
Sorry guys, I'm a bit lost here after too many google changes. They've been pushing them so frequently that I'm having trouble keeping up to date.

For what I've been reading, latest PlayIntegrity Fix along with a custom pif.json provided by final users should fix things for now.

But I have a question. I'm using an old xiaomi.eu ROM from 2020, MIUI 12 and Android 10. Am I affected by latest Google changes? Will the PIF 14 + custom pif.json work for me? Or will the ROM's old integrated fix break PIF and therefore I'm out of luck forever now?

Thanks in advance!
[Magisk] qwertyu123:
I have v14 installed and I'm editing the pif.json in /data/adb with the stock firmware fingerprint. But when i check the reported fingerprint in play store it still reports the fingerprint of my custom firmware. What am i doing wrong? I also tried to edit the pif.json inside the data/adb/modules/playintegrityfix folder, but same result. Of course i cleared data of gms, store and wallet and reboot...

By the way I have a Xiaomi Mi 9T
[Magisk] dosbuddy:
By the way, this seems not to work on Xiaomi devices, they don't have an avb_custom_key partition.

Also confirmed here: pda.ru
[Magisk] Utini:
This is exactly my concern. Can live without gpay and Google wallet but not with 50% of my apps that decide not to work anymore. Oh boy.
[Magisk] dosbuddy:
Why not try it out?

You may also check the feature description "Our ROMs features (what's not in Global)" of the ROM: it there is no "Play Store Certified" mentioned, PIF should work.
[Magisk] eXtremeDevil:
I will check, thanks.
[Magisk] kodein:
Can you guys explain this? View attachment 6039373View attachment 6039374View attachment 6039375View attachment 6039376
[Magisk] Vision:
@chiteroman so the v14 with pif.json is the final ? (thinking of upgrading from v13.3 pif.prop still work for me)
[Magisk] eXtremeDevil:
Actually they have (or had) something in their ROMs to pass Google Play Certification. I've tried latest changes as you suggested and for now, I can pass both device and basic integrity (let's hope that doesn't change soon) but, although Play Store shows as certified, I cannot find Netflix on it.

Anyone else with the same problem? Thanks!
[Magisk] Serinor:
I'm on a Google Pixel 5, Android 14 (UP1A.231005.007) and I can't seem to find /data/adb path with MiXplorer to begin with. I cannot create a folder with that name. Can someone please help me with this?
[Magisk] frank93:
there’s a setting in mixplorer to turn on root features, you need to turn this on for mixplorer to "see" /data/ (and more), i think.
[Magisk] Serinor:
D'oh! Thank you for your help. Totally forgot to change that.
[Magisk] Dachfenster:
After putting pif.json with all necessary information into /data/adb using PlayIntegrityFix_v14.0.zip... how can I verify/check if my fingerprint in there gets "loaded"?
[Magisk] frank93:
logcat | grep PIF

should display some "spoofed" action (from your fingerprint) after a reboot.
[Magisk] HippoMan:
And more and more non-"banking" app developers keep jumping onto the "let's cripple our apps on modded phones" bandwagon. Even the McDonald's app does it nowadays.

The reason for my choice of Android over iOS ages ago was because I could easily root my Android phone to get extra functionality without limiting its standard functionality.

Those days are gone, and as more and more developers start checking integrity in their apps, the usability of Android continues to deteriorate.

And imagine how undesirable the Android experience will be once lots of apps are routinely checking for Strong Integrity!
[Magisk] qwertyu123:
You can enable developer options in the play store, click several times on the playstore version field until you enable it, and check it from there
[Magisk] Typical0:
Hey,

I've tried fingerprints from 2 separate devices that I own – one is Huawei P9 Lite, which still passes device integrity and is on Android 7, and the 2nd one is my Lenovo Tab4 10, which uses 8.1 (originally came with 7) and also passes device integrity. Neither of those work and no, there isn't any kind of a mismatch in the JSON, I've copied the values directly from adb shell getprop command. Is there any way to fix this?
[Magisk] chichino84:
Sometimes the most simple advice is really the best one!

I was almost giving up after trying a dozen of wrong fingerprints, but then reading this just made me realize I was doing it in the wrong way!

So in 5 min I found two working ones, thx!

And of course the biggest thanks to @osm0sis and @chiteroman (and @badabing2003 too!)
[Magisk] PandarianFury:
Are there any other apps that I could possibly use to make contactless payments with?
[Magisk] AlesiBoss:
I think you are simply out of luck, no idea how they do it, but only some fingerprints work. I had no luck with any lenovo or huawei device on my phone...
[Magisk] intel_core_i7:
Just found out that there's a telegram group for this xda topic, there's a pif.prop file of another asus phone and a promised 14.1 update about something related to droidguard reading vendor data
[Magisk] blu.italia:
One question before i get wrong:

Lock the bootloader and use a custom rom doesn't help to get back the device integrity?
[Magisk] psychoela:
View attachment 6039388v14 thanks 😘
[Magisk] Virnik0:
Well, I would have one reply, and that would be 'neser ;-)'

Honestly, this could happens, because Wallet makes remote auth checks every so on hours, so it is not instant. I would check for it tomorrow, being you - and I would bet that Wallet will complain.
[Magisk] iruiz2:
If you lock the bootloader with a custom ROM will almost surely brick your device
[Magisk] wilsonhlacerda:
Edit your pif.json file.

On terminal type:

su

killall com.google.android.gms.unstable && logcat -c && logcat | grep PIF

Switch to checking app (Play Store for instance) and run test.

Switch back to terminal and read the logs that appeared.

Close terminal.

Test fail? Repeat.
[Magisk] Virnik0:
what was mentioned there was an idea dev had - to mimic an approach custom rom builders do - fetch updated fps from their hidden git repository google couldn't access directly.

That could work, as anything presented here is being accessible to Google, and if not that, then too many users using the same fingerprint with the same side-effects - we were simply too easy to detect and FP get banned. So this idea could resolve this, for a time.
[Magisk] Lubo99:
i did it and doesnot appear to work on my motorola edge 30 *dubai*

after reboot device integrity still fail even with pif.json looking like this now

{

"PRODUCT": "motorola",

"DEVICE": "dubai",

"MANUFACTURER": "motorola",

"BRAND": "motorola",

"MODEL": "moto g200 5G",

"FINGERPRINT": "motorola/dubai_g/dubai:11/S1RD32.55-33/0e1d4:user/release-keys",

"SECURITY_PATCH": "2022-04-01",

"FIRST_API_LEVEL": "30"
[Magisk] xSnowLeopardx:
I know I have given up on this, but I really wanna try it all again.

What I learned: that API level is way too high.
[Magisk] AlesiBoss:
You need fingerprint from older phone, this is too new, api level is way over recommended 27 and less
[Magisk] sas46:
Do you gave to look for fingerprints specific to your device? Ex I have a Pixel 6 Pro so I have to look for those specifically?
[Magisk] Rootk1t:
It was a 5 hour journey for me today to find a right one.

It doesn't correspond with your device manufacturer and a working fingerprint.

It just a way to check all of them following recommendations here and here workflow from here to find a right one.
[Magisk] Lubo99:
just to be sure. I edited pif.json file directly in its folder using vi editor and now i have changed api level to 27 and rebooted device

"DEVICE": "dubai",

"MANUFACTURER": "motorola",

"BRAND": "motorola",

"MODEL": "moto g200 5G",

"FINGERPRINT": "motorola/dubai_g/dubai:11/S1RD32.55-33/0e1d4:user/release-keys",

"SECURITY_PATCH": "2022-04-01",

"FIRST_API_LEVEL": "27"

still my device integrity fails

when I take a look at screenshot from TB checker it loads different fingerprint from somewhere

I use in json file this motorola/dubai_g/dubai:11/S1RD32.55-33/0e1d4:user/release-keys

while as you can see different is loaded
[Magisk] dmenezes:
Congrats, one more winner! Thanks for letting us know.

I must be doing it the wrong way too. Yesterday I tried exactly that, but at least for the dumps site I found, ALL 20+ fingerprints I tried failed, and all in the same way: `catlog | grep PIF` shows PIF is working and passing the spoofed values to gsm, but I still get the same error. And yes, they all fit the "FIRST_API_LEVEL" <28, and none of them were for Google phones (which I understand brings additional issues).

@osm0sis told me it was because the ROMs I got the prop files from were too new... so from reading everything all over again, I think I need to get a ROM from the time the device was still on Oreo -- but no dumps site I can find have these, they only have the latest version.

Can anyone offer any additional clues? I don't want to quit and let Google win this, not without a fight.
[Magisk] lysaer:
Will give the new update a try

Am beginning to wonder if rooting and using google pay is feasible nowadays, multiple times over the last few weeks I have gone to pay and been presented with the "device doesn't meet security standards", fortunately I have my watch with me, but it seems rooting and using the device to pay with just isn't reliable enough nowadays sadly
[Magisk] AlesiBoss:
Changing api level wont help, you need fingerprint that is from phone that has lower api as a default
[Magisk] devilsshadow:
Hey, just chiming in to say I think I got it the first time (I think? Dropping screenshots here for confirmation)

Thank you for the very detailed explanation @osm0sis

I'll be honest, I just skimmed through your explanation and went with a device that launched with 7.1.1 and was upgraded to Android 10. Seems to work fine (for now).

Seems to me like we're fighting a losing battle against root-hiding. Time's ticking until we won't be able to use gpay with rooted devices.
[Magisk] AlesiBoss:
Yeah, i am having one physical card on me for this reason, I mean i dont really care, i still like to use cash also, but its pain in the crapper
[Magisk] dmenezes:
Congrats, another winner!

I'm also following his post, but to no avail so far.

Can you tell us what method you used, ie did you pick the prop files from an old physical phone you already owned, or did you find it at some props dump website, or did you download a stock ROM zip file for it and opened it?
[Magisk] Lubo99:
yeah i get it now ROFL
[Magisk] wrongway213:
Please read the thread and stop trying to post prints here
[Magisk] devilsshadow:
Oh, like I said, I was sleepy while reading instructions so I just picked a phone manufacturer at random, googled the manufacturer name + build.prop, found a collection of them on github for that specific manufacturer. Couldn't find a device that released with android 8 and was upgraded to 9 for that specific manufacturer so I picked the next best thing (in my mind) android 7.1.1. Honestly I didn't think it'd work but it did. Finding build.props isn't that hard, but I probably got lucky with my pick.
[Magisk] chichino84:
Definitely, this small win really got a bittersweet flavor...

It really must be (in my case was not searching for appropriate "donor" devices).
[Magisk] dmenezes:
OK, digged a little more and found out how to get the old Oreo versions from one of the dump sites.

But at least the ones I'm looking at don't have a vendor/build.prop file, just a system/build.prop.

I think a vendor/build.prop file was needed too?

Can anyone shed some light on this?
[Magisk] xSnowLeopardx:
I did it!!!

I wanna thank two people right now:

1) @AlesiBoss

2) @osm0sis

I am still sick, but it's Saturday and I have not much else to do. I started reading the last 10 pages.

Came across this response of @AlesiBoss: "Write build.props dumps into google and follow your instincts".

This has helped me. I did not search for hours today, but just did some small research and was lucky; this was the first build.prop I found today.

I did this as well, but no idea if it was needed/helpful:

- I had a pif.json in this location as well: data/adb/modules/playintegrityfix but since I don't use the fork of @osm0sis but @chiteroman - I just deleted that .json, deleted the one in data/adb as well and put the edited .json of mine in the adb location.

About the API:

- The API level was not too high but I think people have found lower ones as well. Just try and don't think: "I need to find the lowest one."

The same steps afterwards:

- Deleted Play Store and Wallet cache + data & cache + manage, delete for Google Play Services.

- Really did cross my fingers

- Rebooted

Success:

- Play Store shows basic + and device.

Finally.

I think this will break soon, but idc. I am happy my method of finding is not broken.
[Magisk] devilsshadow:
what I can tell you is, at least in my case, all the info I needed was in a single build prop (the vendor's android version build.prop). If you can find all the info required for the .json in either a vendor or a system build.prop then the .prop is correnct. I ctrl+F'd through the vendor prop and got a hit for every entry in the pif.json file. So maybe focus on vendor build.prop ?
[Magisk] wrongway213:
Moderators and contributors working on this have repeatedly asked users not to post possibly working prints publicly. Please remove the fingerprint from your previous post and stop spamming the forum with fingerprints. Users are not supposed to be posting prints in this thread and all the information you need is already here.

Again, please remove your previous post and stop posting fingerprints in this thread.
[Magisk] lysaer:
There is quite a few rooted apps I regularly use so just don't want to give it up, but I think I will also start carrying a physical card in my phone case from now on as well, sometimes I do leave the house without my watch but never without my phone
[Magisk] dmenezes:
Anyone reading this, Please, DON'T DO THAT.

The developers have explained over and over again why this would just end up ruining everything for everyone.

Again, everyone PLEASE DON'T POST ANY DETAILS (phone and android version is everything Google needs to banana it).

@Lubo99, please stop already.
[Magisk] wapsterz:
Hey. From 148 dumps i found 14 working. So i can confirm that this solution still works.

Now looking for solution how to automatically check for valid device Recognision Verdict via TERMUX and maybe cron.

Today or yesterday here one user posted this solution,but i cannot find it now. :)
[Magisk] wrongway213:
Report his posts, that's what I'm doing. He's causing a situation where mods are going to have to lock this thread sooner than later.
[Magisk] dmenezes:
Thanks, this is helpful. I proceeded with only system/build.prop which is what I got here, unfortunately it did not work.

Will keep trying.
[Magisk] dmenezes:
Just did. I hope the mods lock him and not the thread.
[Magisk] PhatWalrus:
Got a working fp
[Magisk] StrifE:
Pfff I can't find one :( I'll keep searching
[Magisk] xSnowLeopardx:
I am already configuring back up props. Have 2 so far, gonna test them in a bit. If your search method is valid, then all you have to do is search. It really is that simple.
[Magisk] xSnowLeopardx:
I recommend blurring all the things below the meets. We want to help Google as little as possible.
[Magisk] immortalwon:
You do realize showing timestamps and hash ids will show them which fingerprint your actually using, right?
[Magisk] StrifE:
N00b question, do I have to reboot between the .JSON edits?
[Magisk] PhatWalrus:
Yes
[Magisk] badabing2003:
PixelFlasher Update Releases:

Dec 02, 2023 v6.3.0.4 release

Support for @osm0sis Play Integrity Fork which uses a different path for the print file: /data/adb/modules/playintegrityfix/custom.pif.json

Dec 02, 2023 v6.3.0.3 release

Make Magisk dialog resizable

Add support for PlayIntegrityFix-resetprop
[Magisk] ZzEzZ:
Found the Google Employee

😎 get 'em boys
[Magisk] xSnowLeopardx:
PixelFlasher is a godsent. Got a 2nd working prop!
[Magisk] iruiz2:
No, killing the droidguard process is enough: com.google.android.gms.unstable
[Magisk] immortalwon:
I am curious, how are u using PF exactly to find prints? Just opening random roms?
[Magisk] iruiz2:
As for myself, with the incredible help of the script made by @osm0sis and the advice of this thread, I was able to pull 4 prints out of 27 tries. 4h it took me. Damm you, Google.

Thank you @chiteroman , for building a tool to make this possible.
[Magisk] Pirateguybrush:
It worked!

Massive thanks to osm0sis, badabing2003, chiteroman

Re-linking these handy guides again to help people locate them.

Guide to locating working props

Guide for injecting/testing props