yashsingh1/xdaforums huggingface dataset:
[Magisk] sotirone:
Looks like chiteroman changed the custom.pif.json location and name to match yours:

custom.pif.json check, use and restore; enable custom branch module updates, and more (custom) by osm0sis · Pull Request #103 · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] Ayle Kalani:
Hello, I don't understand version 1.14. (I don't know how to find the data to put in the file.)

Where can I find? Is there a specific term?Where can I find? Is there a specific term?

I understand that you cannot publish the certificates here, but I wanted to know how to find them. (I know where I have to put them, I just don't know where to find them.)
[Magisk] immortalwon:
Download random firmwares / roms off the internet, extract build.prop and search the values to match P.I.F json file. Read osmosis thread and use his script if necessary.
[Magisk] iruiz2:
Read.

For example, 2 posts before yours.
[Magisk] Ayle Kalani:
I want to use it for my own use, I don't want to disclose the certificates. (I just need to know how to find them to add to my device.)
[Magisk] Lubo99:
yeah duude you got me there LDLDLD
[Magisk] wrongway213:
Read the thread, info is already here.
[Magisk] Ayle Kalani:
ok, I'm checking the information provided.
[Magisk] xSnowLeopardx:
Honestly, it helps me with time. I constantly had to clear every app's data and then reboot.

Now I just try a build, edit if necessary inside PF, then check with SPIC for example and continue.
[Magisk] rseiler:
When I used that tool a few days ago, I could never get "Process build.prop" to handle anything more than the date field, so it was of very limited use. Tried it on multiple files. If I was doing something wrong, I'm not sure what.
[Magisk] alonsoj636MW:
yeah... in 30 minutes i found 10 working prints... thanks to the wonderful guide by @osm0sis !!!

also thanks to PixelFlasher by @badabing2003 this was really easy... thanks to him too :)

and of course @chiteroman for his work on the module :)

i'm really happy with the results and will keep hunting for more...

don't give up guys!!
[Magisk] simo2001:
When I modify the pif.json do I have to clear all Google data or killing gms unstable is enough?
[Magisk] iruiz2:
To check if you pass Play Integrity, killing unstable is enough.
[Magisk] V0latyle:
While I'm flattered, I can guarantee my wife is cuter than you are so...your feelings of amorous are sadly not reciprocated

Shouldn't...7zip can handle IMG files as well as the typical zip
[Magisk] badabing2003:
You're doing something wrong, most likely your build.prop is not proper build.prop
[Magisk] Alex2008Ex:
Hey guys, I have installed v14.0 on my Huawei Watch 2 with custom ROM but it looks like I'm missing something because GWallet still does not work
[Magisk] dmenezes:
Finally, EFFING FINALLY I managed to get one working:

View attachment 6039464

View attachment 6039463

A few tips to try and help those still struggling:

* DON'T GIVE UP. You CAN do it!

* When you get a working one, DON'T TELL ANYONE which one it was, nor give any specific details. I know we all try and be helpful, but if you give info to ANYONE, you will end up RUINING EVERYTHING, both for you and the person you're trying to help, and for EVERYONE ELSE.

* I found it via the "prop dumps site" method. Looked for a not-very-well-known-nor-popular phone that I previously determined had been upgraded to Oreo 8.1, then got both vendor and system prop files from the dump site, and fed them to @osm0sis `gen_pif_custom.sh` script. Copied the resulting custom.pif.json file to my phone as /data/adb/pif.json (as I'm using @chiteroman' s v14-resetprops version, and not @osm0sis' s fork).

* I turned on airplane mode, then force-stopped and cleared all storage/data for both Google Play and Google Play Services, then turned off airplane mode.

* Initially I tried the `killall com.google.android.gms.unstable`, which always fails in my case with "no such process". Regardless, I then ran `logcat -c && logcat | grep PIF` in a Termux window;

* I then tried "Check Integrity" under General Options / Developer Options in Play Store: it did NOT work, only showed BASIC.

* I then repeated the airplane-mode-on/clear-storage-data dance for both Google Play and Google Play Services, and with airplane mode STILL ON, REBOOTED the phone.

* After the reboot, I reopened Termux and re-run `logcat -c && logcat | grep PIF` , THEN turned airplane mode OFF, and imediatelly started seeing PIF messages on the logcat output, and MANY MORE messages (and mentioning other attributes than *.security_patch and *first_api_level) than I was seeing before.

* I then tried again "Check Integrity" under General Options / Developer Options in Play Store, and this time IT WORKED!!! Both BASIC and DEVICE integrity are showing at both Play Store Integrity Check and SPIC.

Thanks again to (in no particular order) @chiteroman, @osm0sis, @V0latyle, @pndwal , @badabing2003, and all the great developers and contributors, and of course to all of you who came back here to tell us it worked and encourage us to keep trying.

Now let's wait and see how long that lasts. Will check at least once a day, and when it's gone I will come back and report.
[Magisk] dosbuddy:
That one is working,... lets see how long :(
[Magisk] xSnowLeopardx:
While I am very happy it also works for you, my experience was waaaaaaay simpler than yours. It was finding a prop, reading its properties myself or letting PF do it, then using PF for changing and killing the process, checking with SPIC, done.

Glad it did work for you, but I hope people don't get discouraged by this more complex method of yours.

Status update: have 5 working ones and looking for more.
[Magisk] dmenezes:
You will have to do the same thing everyone here did already, and go read this thread, the entire thread if need be. I know, it's long and boring, but no one can do it for you. Start from here and go backwards, before long you will reach the posts that matter.
[Magisk] dmenezes:
Interesting. Perhaps there are other factors involved? The fact is, killing the process did not work ("no such process" error message) and I had to reboot.

Also, it also happened that before all this (when I was already rebooting), I was using the latest version of the ROM (instead of the older 8.1 which worked) for the build.prop file. So that was sure another factor, but as I reported above, a reboot was also needed.

I also hope that, if they try the simpler method and it does not work, they do not get discouraged and instead of giving up, try the more complicated method instead ;-)

But seriously, if the simpler method works for them, more power to it. The reason I posted my "more complex" method is because the simpler one simply didn't work for me, and I'm pretty sure I'm not the only person that is having / will ever have this same problem.

TL;DR: if killing the process does not work, REBOOT! :)
[Magisk] xSnowLeopardx:
Very fair, thanks for the explanation as well.
[Magisk] Bonoboo:
2 All

Recently I posted solution to beforehand know when GPay became broken due failing Play Integrity / SafetyNet (e.g. banning fingerprint).

That was just a sketch for savvy people. Now I made simple app that monitors Google Pay availability.

You will be warned in advance and can take action: find another fingerprint or take cash / card.

Bonus: also it checks existence of any bank card in case they wiped e.g. when disabling lockscreen.

Download here

@voetbalremco, @xSnowLeopardx, @Nezorflame, @esatch, @HippoMan, @Qnorsten, @arda99

You liked that post, here ready-to-use solution.
[Magisk] viniciuskmv:
Found one FP working. Thanks you all.

Now I'm gonna search for more FP to use as backup
[Magisk] iruiz2:
I case is useful for you or anyone else, I did the following to kill unstable:

Ps - A | grep unstable

And then kill the process number that appears
[Magisk] dmenezes:
Thanks for that. Unfortunately this command shows nothing here (empty output) so it seems I indeed don't have com.google.android.gms.unstable, nor anything with `unstable` in it, running.

EDIT: tried running both with `sudo`, and by first running `tsu` and then running it in the resulting root shell. Neither shows any `unstable` process.

If anyone can try and point to me what I may be doing wrong, I would be much obliged -- next time I have to search for a working fingerprint, not having to reboot every time I try a new one would be a real time saver.
[Magisk] Lubo99:
I did like 23 different build.props all failing... apis between 25-27
[Magisk] cubandanger05:
I wanted to piggy back off of your post. It gave me that last push I needed to keep trying pifs after trying several to no avail, and I found one myself. Fingers crossed it lasts.View attachment 6039501
[Magisk] dmenezes:
Glad to have helped!

Amen to that, brother!
[Magisk] dmenezes:
You should be able to find one in 10 or so, if in 20 you don't find it, you should carefully revise your procedure because you are almost surely doing something wrong: I didn't find one in my first 20+ tries either, then I rechecked everything, found my mistake and managed to find a working one on the 3rd try. Above all, don't give up!
[Magisk] double_jumper:
Did some props cause even basic to fail for anyone else? It seemed weird but not complaining, what I'm wondering mostly is if the fact that the next prop "fixed" it back to basic, means that the procedure at least is sufficient. Because I already tried 15 without success (well, later i realized 3 of those were outside of the API range)

Edit: stuck to the same procedure of just setting a new .prop, clearing play services storage/cache and force stopping it, and checking, and found a working one
[Magisk] stereo007:
I also have a question. if someone has the same phone as me and is not rooted, can I simply use `adb shell getprop` to read the data and use it on my phone? Or do I have to keep looking for an image that works?
[Magisk] xSnowLeopardx:
Today, I found 3 in 12. Before today, I did not understand what I was doing and was giving up. A lot can change hahah.
[Magisk] LaboDJ:
It took me 5 minutes to find a working FP, the hints in @osm0sis post is everything you need.

View attachment 6039505
[Magisk] Lubo99:
lol and what was the mistake? i have connected my phone in pixel flasher loaded build.prop file edit pif.json file with setting i found in build.prop file and run integrity check from from within pixel flasher running TB checker installed on the phone. of course you have to have unlocked screen on the phone. and app opened and device integrity always failed. sometimes with some devices props even basic integrity failed most of the time it passed but device integrity always failed...
[Magisk] bigknowz:
Could file or folder permissions screw things up? I have folder 755 json file 644
[Magisk] Lubo99:
dude delete this asap. for your own sake as tomorrow you may end up yelling and screaming this not working again

but how in the gods name you got this working on android 14 :D:D:D:D
[Magisk] mumuli:
This forum is nowdays kinda guys jerk of others.

There is pages and pages and pages people asking help. There is "secret" put that in google, not even working. etc crap.

Can we pls get step by step instructions

What pages? Where is that dump archive?
[Magisk] dmenezes:
My prediction would be, not very long... even something more restricted like a Telegram channel will be sure to be compromised eventually, and even if it isn't, the sheer number of people that will start using this fingerprint will certainly light up in Google's radar and doom it before too long.

It bears repeating: there is no easy way out here, people. If you want PIF to work, you have to go and do your homework and find your own fingerprint, just like everyone here did. Using other people's fingerprints may sound tempting but will end up just getting you (and everyone else) screwed in the end.
[Magisk] LaboDJ:
That fingerprint is from my device...

There's no sensible info in that screenshot
[Magisk] Kutunf:
No. Device - Poco X3 Pro
[Magisk] westruk:
Broken TEE
[Magisk] Kutunf:
I'm sorry. And what is this?
[Magisk] pndwal:
Do you have basicIntegrity but no deviceIntegrity? Or other? PW
[Magisk] kjllmeplz:
mi13 eu stable 14.0.31. Version 7.4 not working, only version 7.0 working
[Magisk] zgfg:
Xiaomi.eu -have you tested without?

Eg, on my Lisa with 14.0.10, passing Basic and Device with no need for a module
[Magisk] pndwal:
Interesting issue...

Being OnePlus, I'm wondering if it's connected to the strange 0nePlus issue exposed with 26105 Magisk:

Magisk Manager freezes after upgrading to 26105 APP regression #7214 opened 2 weeks ago by humbleoxygen12

Not sure if this will prove to me a Magisk issue/regression or a module issue...

Please say if you tested with public 26.1 or canary 26105 Magisk installed...

👀 PW
[Magisk] Xennet:
As said above xiaomi eu rom 7.0 working 7.4 not working...

Without any safetynet fixes it passed checks till 3 weeks back after which most of all xiaomi eu roms of all recent devices failed these tests...
[Magisk] quasyl:
For me version 7.4 works well. I have a Poco X5 pro with xiaomi.eu stable 14.03. Where is version 7?
[Magisk] quasyl:
It's true!!! I just tested without any module (safetynet related) and "meet basic and device integrity" pass perfectly! (Poco X5 pro with xiaomi.eu stable 14.03).
[Magisk] totalolage:
View attachment 5982237

I'm on public, but it was working before the Lineage OTA update. I can try Canary, finaling that I can wait for Tuesday's OTA and see if it's fixed with that.
[Magisk] pndwal:
strongIntegrity:

https://xdaforums.com/attachments/img_6676-jpeg.5982249/

Sounds like unique identifiers (numbers) in persist partition may have been messed up by a custom ROM etc... (Can break ctsProfileMatch/deviceIntegrity)... Poco users seem to get this issue particularly...

Hopefully you backed up this unique partition for your device earlier... Generic persist images in ROMs don't have unique IMEI, Mac, BT, WiFi numbers etc)... There are other ways to fix this however depending on device...

Please see comments/links I put in a thread reporting a similar issue in poco device (and note the thread title):

- https://xdaforums.com/t/cts-fail-even-with-locked-bootloader.4613007/post-88837771

- https://xdaforums.com/t/cts-fail-even-with-locked-bootloader.4613007/post-88839819

Do your due diligence, but I'd try the second suggestion before flashing /persist (unless you have a backup from your device as this will include unique numbers unlike the generic /persist image in ROM), especially if you've never actually messed with that... (Nb. Seems issue can occur simply due to downgrading directly from A13 to A11 or similar... Go A13, A12, A11 etc).

Hope this (or clues linked) helps... 🙂 PW
[Magisk] Ginosius:
View attachment 5982301

All good here after updating to 7.4
[Magisk] kjllmeplz:
without module, my phone only pass basic.
[Magisk] intel_core_i7:
Another day I thank the banking people here not implementing SN/PI. I don't root my devices, but have BL unlocked and on stock ROM, so DEVICE fails by default
[Magisk] simpleatom7:
Mad respect to both of u, @Displax & @chiteroman

including @kdrag0n ! On my Redmi Note 8 pro, i could pass Basic & CTS profile match in YASNAC & Playstore also says Device is certfied however in Intergity checker app, Strong Integrity doesn't pass which ig is fine for me.

The main issue is banking app Yono SBI crashes whenever i try to launch it. It worked with twrp, the sec i installed root, it crashes automatically.

I pray someone is there to check this issue.
[Magisk] simpleatom7:
bro how did u pass strong integrity?????????

Edit: No need to pass it. Use Hide my app and shamiko.
[Magisk] m0han:
His month-old reply: https://xdaforums.com/t/module-play-integrity-fix.4607985/post-88780971
[Magisk] simpleatom7:
How did u pass strong?

Bro ig u tagged the wrong reply above.
[Magisk] dmenezes:
No one here is going to tell you that, because if we do, it will just ruin everything for you and for everyone else.

Go and do your homework, there's no easy way out of this.
[Magisk] DarkestSpawn:
Update:

Got device and basic to pass. Gmail and messages force close tho. Anyone else getting this?
[Magisk] dmenezes:
I'm not familar with PixelFlasher, as I prefer to run things command-line and not GUI, so I can't help you figure out where you are mistaken. But other people here have succeded with PixelFlasher, so rest assured that it can be done. You just have to find that mistake and fix it.
[Magisk] dmenezes:
I saw one other person reporting issues with GMail too, but here it's working flawlessly, no FCs nor any other issues.
[Magisk] xSnowLeopardx:
What else can we say? It's as easy as knowing what to do, then searching, applying what you know, getting results (good or bad), continuing.
[Magisk] dmenezes:
Please do, because if I ask for something obvious and already discussed ad nauseam like you just did, and to make matters worse something that if shared will ruin it for everyone (as also explained ad nauseam too), and even so I keep asking like you are doing, then I will certainly deserve it. 🙃
[Magisk] Lubo99:
lol i get it now... u used different device for spoofing. however since you are on google device you may suceeded with props where I will not as I have motorola edge 30 phone
[Magisk] okij:
For me, killall com.google.android.gms.unstable also often fails with error "No such process", but imho that's only caused because com.google.android.gms.unstable isn't running at that time.

So after changing/editing pif.json in /data/adb, I just always run killall com.google.android.gms.unstable and don't care if this error occurs, because com.google.android.gms.unstable will then be freshly started anyway when doing a Play Integrity check, thus using the new pif.json file.

BTW, I found two working fingerprints out of about 15 that I tried. :) I might check for more tomorrow.
[Magisk] NikiX_:
Does anyone here have a guide to finding working fingerprints? I would like to find my own one please
[Magisk] LaboDJ:
Interesting... any source?
[Magisk] Lubo99:
look for buil.props file on internet and try.... try... and try... different keys...
[Magisk] xSnowLeopardx:
LMAO

I have a -8 Integrity API error. Making too many requests with SPIC, apparently?
[Magisk] mumuli:
NO. If someone know, he not tell you. It is your own protection. Pls go away here. (im just like others)
[Magisk] dmenezes:
I thought so too, but here it's not "often", it *always* fails.

Glad it worked for you. In my case, as I reported, it did not -- kept getting only BASIC until I rebooted my device.

Way to go! (y)
[Magisk] dmenezes:
Use the integrity check function built into Play Store, it suffers (so far at least) from no such limitations.
[Magisk] dmenezes:
Not sure if permissions can be an issue, but I just checked and mine are 700 for the /data/adb folder and 644 for the pif.json file.

Hope that helps!
[Magisk] okij:
Strange. Please try this command right after doing a PI check, as the process should be running then.

And ofc you must enter su before using killall, but you surely know this.
[Magisk] dmenezes:
But why would I do that? Isn't the whole reason for killing that process to force GMS to refresh, *before* checking PI?

Yep, of course -- that's why I reported doing it both with `sudo` and then under `tsu -` --- both run it as root, albeit within a slightly different environment.
[Magisk] Nubidubi23:
Same issue here
[Magisk] dmenezes:
From the log you posted (and please delete it as it shows the device you're trying), I would bet the ROM you chose is too old (API level 23). Here, I succeded with 25.
[Magisk] Lubo99:
thanks to guys who provided tutorials. and thanks

alonsoj636MW a lot!!!!​
[Magisk] dmenezes:
This is normal, as already explained here a couple of times, only Droidguard sees the spoofed values.
[Magisk] viniciuskmv:
No, in my tests with working Fingerprints it remains with the data of my phone in this screen but passes the IC
[Magisk] dmenezes:
See, we told you you would make it 😁 . Seriously, congrats! 👍
[Magisk] Nubidubi23:
There's a minimum API level requirement? I thought there was only a maximum
[Magisk] ipilcher:
Anyone know of a good guide to the different build.prop files and properties?

I've read through osm0sis's guide several times, and I just don't get it. What is the difference between "system build.prop" and "product build.prop", and how am I supposed to know which one I need?

Also, is it possible to do this without a Windows system?
[Magisk] dmenezes:
In theory yes, but it seems not in practice: quoting from @osm0sis excellent post:

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 vendor build.prop; the earliest working devices I've seen have First API Level 23

So, 23 is cutting it really close, as it's the minimum ever seen working.
[Magisk] okij:
Just to check if you manage to get it killed when it's most likely to run. :)

Yes, of course.
[Magisk] dmenezes:
IME these are the directories under which you need to look for the respective build.prop files.

Also, I never used a "product build.prop", here what worked were "system build.prop" and "vendor build.prop".

Hope this helps.
[Magisk] manjaroid:
With PlayIntegrityFix v14 /data/adb/pif.json is what's working for me, for now. PixelFlasher processed the props and the FIRST_API_LEVEL field was left blank. Haven't tried PlayIntegrityFork-v3 yet and still more prop files to experiment with if/when I lose device integrity next time (I'm fairly confident there will be a 'next time').
[Magisk] dmenezes:
Ditto here. But I think this is a heads-up for when we install @chiteroman's (or @osm0sis') next release.

Unfortunately we all have to agree with you, as indeed Google seems hell-bent in making modded ROMs unusable (shame on you, Google).

Well, one day at a time, as they say... and I'm pretty sure we will all be able to cross that bridge when we reach it.
[Magisk] osm0sis:
No, that's incorrect. That's what he originally merged, which I submitted, then he immediately effectively undid it all before release, which lead me to make my fork active. You're looking at old commits from days ago which are tagged v14.0, meaning they came before that release.
[Magisk] figroll27:
I just updated my module. tried to pay in a store and it didn't work. could someone link to the thread or comment that explains what I have to do to fix this?
[Magisk] dmenezes:
Thanks for setting me and @sotirone straight. So I gather that the PIF.JSON file will be keeping its location, ie /data/adb/pif.json on @chiteroman's and /data/adb/modules/playintegrityfix/custom.pif.jso on yours.
[Magisk] osm0sis:
In chiteroman's, yes. And mine will remain self-contained in the module directory as custom.pif.json as I had intended.
[Magisk] iruiz2:
Read OP. There's a link to a tutorial by osm0sis that will put you on track
[Magisk] yaqib:
Play Integrity Fork and Play Integrity Fix What's the difference? Am I supposed to use one of them？
[Magisk] bakaekze:
If you know how to extract your own fingerprints, yes. If not, move along.
[Magisk] neelchauhan:
I got mine working also, yay! Back to LineageOS for me.

I did need to use the script and a stock ROM dump of an old device.
[Magisk] bakaekze:
@Bonoboo has made an app to check Play Integrity state in background so you know beforehand if your fingerprint is "banned": https://xdaforums.com/t/gpay-checker-app-that-monitors-google-pay-availability.4643969/
[Magisk] dmenezes:
With all due respect to @Bonoboo and his hard work, I would be wary of using something like that; it could end up creating a pattern in Google's logs, and a pattern is everything the mofos need to keep banana-ing our fingerprints.

I will check mine manually, on random days and times (ie, when I remember to do it) and using one of the many methods available -- this way there's no pattern for effing Google to detect and stick their busy bananas into.
[Magisk] dmenezes:
Thanks for the clarification. Already edited my post to make it clearer.