yashsingh1/xdaforums huggingface dataset:
[Magisk] bakaekze:
It doesn't have anything to do with Google as far as I understand. It just checks an active state on your device, and if the state has changed you will get a notification.
[Magisk] olivercervera:
I finally have found a way to make it working.

Thanks to both of you who made the guides.
[Magisk] Bonoboo:
I see what you mean. At least it's more safe to use same "app" via Tasker. Added warning.
[Magisk] dmenezes:
Please remove that piece of info (marked with XXXXXXXX), as otherwise Google can/will eventually read this and then just blacklist all XXXXXXXXXX.
[Magisk] dmenezes:
I agree 100%.
[Magisk] Nubidubi23:
I've tried 3 different fingerprints and none of them worked. The last rom i got the build.props from meets the criteria i've read around here, won't specify since google is probably lurking here. Someone please help me with this because i'm going insane :(

I put the pif.json in /data/adb/pif.json and restarted my phone but still nothing
[Magisk] flawless911:
Big thanks to @osm0sis @chiteroman @badabing2003 for the module, guides and tools.. I got mine working in 3 tries without rebooting (thanks to Pixel Flash tool).. Now passing DEVICE INTEGRITY!!!

All banking apps working + Netflix works/shows in Playstore
[Magisk] maxmax0:
Hey gang, so I finally got some time and found a working print. Now before I did that, my Google Wallet started acting up, saying phone is insecure.

Now that I have DEVICE_INTEGRITY again, do I need to reset wallet and add all cards again, or will it resume working in a couple of days (I can wait...)...

Thanks!
[Magisk] ScubadooX:
It seems that the latest version of Play Integrity Fix (v14) has been banned by Google. Google Wallet will fail until a new PIF version is released that passes Google's Play Integrity test.
[Magisk] ArzZenic:
After trying like 50 build.props, I finally found one, that is working. Thank you all for guides and devs for awesome work! If you still have issues, just try some more, you'll find the one, that you need (atleast for now!)

Using chiteroman's PIF v14 via osm0sis PlayIntegrityFork v3 & Pixel Flasher by badabing2003.

Thank you all!
[Magisk] fede2782:
Are there some OEM's fingerprint which are better than the others? I tried 4 different fingerprint of some devices from Lenovo, Huawei, Samsung and Xiaomi. None of them worked. Am i doing something wrong?
[Magisk] ArzZenic:
Try some more, it took me like 50 tries.
[Magisk] D€INOS:
Is start with { and end with } necessary in custom.pif.json ?

I've got a fingerprint working from 30 minutes of work a few days ago, but find the subject interesting to I'm following the process. You have been a huge juggernaut for the community 🏆
[Magisk] maxmax0:
OK if anyone else faces the same issue, to answer my own question: I deleted wallet app data and cache, rebooted, strangely my cards were still there, and wallet works again (for now!!!)
[Magisk] fede2782:
Do I need to reboot every time I change the file, right?
[Magisk] Qnorsten:
Read the thread/release notes. V14 does not include any spoofing data. You need to fill out pif.json yourself if you want it to work.
[Magisk] YMatrix:
Hey

I have an old LG G2 device which still runs - how can I take its FPto my Samsung S20fe?

I read osm0sis post but got lost in the words
[Magisk] maxmax0:
No. Just kill GMS.
[Magisk] rseiler:
My horrible luck: both old phones I have access to began life with 8.0.
[Magisk] ArzZenic:
Nope, use the Pixel Flasher. It kills GMS when you save the pif.json, There is a guide few pages back. Also used PIFork by osm0sis, Pixel Flasher didn't work with me mostly, when I was using original PIF by chiteroman (I had to manually move/copy pif.json from /data/adb/modules/playintegrityfix/ to /data/adb/pif.json on chiteroman's)
[Magisk] Skander1998:
PIF 14.0 doesn't ship with new fingerprint. You're supposed to find your own and add them to the file.

Read instructions and changelogs next time.
[Magisk] osm0sis:
That's json. Yep. 😛

And thanks, between me having to push here to get my idea for a pif.prop implemented - at - all, pushing to get security patch added, then pushing for pif.prop/json to still - remain - implemented (since I could already see it was a clear necessity), and then struggling to get more script fixes properly - added here before they got reverted again, (scripts which were taken without credit from Displax's USNF, which included fixes from me, and my fixes in kdrag0n's USNF before it), I figured I've been involved the whole way down and might as well fork it properly to stop the insanity. 🤪
[Magisk] trol0lo:
Got it working thanks to chiteroman PIF, and osm0sis guide.

A question that came to my mind:

If google bans a fingerprint, what happens with the users who use this fingerprint on their stock device without spoofing? Do they get banned also or are there some other checks running to detect that they're running stock and not spoofing?
[Magisk] iruiz2:
Probably the second
[Magisk] ipilcher:
So I downloaded an OTA ZIP file for a build that I thought might be promising. I've extracted the 3 build.prop files, and used osm0sis's gen_pif_custom.sh script to generate a custom JSON file. (I ran the script on my Linux desktop, rather than on a phone.)

(The script left PRODUCT and MODEL empty, so I manually added what seemed like appropriate values.)

I''ve copied custom.pif.json to both /data/adb/modules/playintegrityfix/custom.pif.json and /data/adb/pif.json and rebooted the phone, but no joy.

When I use the Play Store integrity check, I notice that it is showing the actual model of my phone, not the model specified in my custom.pif.json. Does this mean that I've messed up somewhere, and the module isn't working?

When I run the integrity check, logcat shows:

12-02 14:04:43.814 6630 6656 D PIF/Java: DroidGuard detected!
12-02 14:04:43.980 6630 6656 D PIF/Native: [ro.build.version.security_patch]: 2023-11-05 -> 2018-09-05
12-02 14:04:44.166 6630 6656 D PIF/Native: [ro.board.first_api_level]: 30 -> 27
12-02 14:04:44.166 6630 6656 D PIF/Native: [ro.vendor.api_level]: 30 -> 27
12-02 14:04:44.288 6630 6656 D PIF/Native: [ro.product.first_api_level]: 30 -> 27
[Magisk] D€INOS:
Your welcome 🤗 , the could it be that users are using the sh script that dumps the values from the build prop without {} ?

And know most for post "don't work" are doing different mistakes.

I don't think I was lucky with 30 minutes, first print success on a very popular phone print I might add.
[Magisk] ArzZenic:
Its normal to show your actual phone model in Play Store Integrity Check.

You can see, that spoofing works in logcat, just try more build.props, it took me 4hours. (also, kill GMS or use Pixel Flasher)
[Magisk] iruiz2:
Google Play PI check will always show your real phone, not the spoofed one.

Looking at your log seems like you didn't kill the unstable process or reboot before trying to pass PI.
[Magisk] trol0lo:
Did you pass Basic Integrity? I figured that its a pretty good indicator if you did something wrong in your procedure (Basic Integrity Fails) or if your fingerprint does not work (Basic Integrity Passes)
[Magisk] ScubadooX:
Sorry, didn't know that. Is that usually the case or was 14 an exception? In the past, I've simply updated PIF from within the Magisk app and that would work. Actually, PIF 14 was working for a few hours yesterday and I didn't add my own fingerprint.
[Magisk] ArzZenic:
It won't work furthermore. Google banned old fingerprints, now you have to find your own, which is still working.
[Magisk] ipilcher:
I definitely rebooted. (I've seen a number of references to killing a process, rather than rebooting. What is it that I'm supposed to kill?)

What should the logcat show?
[Magisk] ScubadooX:
Thanks for the info. Google Wallet isn't a showstopper for me but getting it working by finding usable fingerprints going forward would make the value proposition for custom ROMs significantly diminished.
[Magisk] sxaaa:
where I can find data/adb/pif.json on my phone poco F3 ?
[Magisk] ArzZenic:
When I finally succeeded, it showed me the same thing.

View attachment 6039563

Also, when I was changing build.prop in pif.json (after saving and using integrity check), it showed me, that fingerprint changed (using Pixel Flasher without reboot)
[Magisk] kocsogfax:
Hi all!

Could this v1.40 version with custom pif.json work on Xiaomi.eu rom?

I have tried to change with pif.json, with logcat|grep PIF, it's spoofed, but after that it's changed back to original values.

Play store integrity check always show the original values.

Thanks for your answers!
[Magisk] ArzZenic:
Use some root explorer, like Total Commander.

but I don't know, if PIF works on MIUI. Earlier versions didn't work on MIUI roms.
[Magisk] ArzZenic:
Play store integrity check will always show original values. You have to believe the logcat :)

but I don't know, if PIF works on MIUI. Earlier versions didn't work on MIUI roms.
[Magisk] ipilcher:
Yes. I am getting MEETS_BASIC_INTEGRITY, so I guess that this indicates that the fingerprint doesn't work.
[Magisk] ArzZenic:
Correct, you have to find another device fingerprint.
[Magisk] ipilcher:
Unfortunately, I can't use Pixel Flasher, as I don't have any Windows systems.
[Magisk] desertcat:
I give up:cry:. It would be nice to have Device Integrity pass but it's not really a big deal for me since I don't use GPay.

The problem that I do have is that somewhere between version 13.9 and trying to create a suitable pif.json file to use with version 14.0, Google Play says that my device is not certified. No amount of clearing cache and memory and rebooting helps. So far, this hasn't caused any issues with updating apps I have installed.
[Magisk] sxaaa:
Thanks
[Magisk] trol0lo:
its availiable for ubuntu and mac as well afaik
[Magisk] YMatrix:
How can I extract the build.prop from my LG G5 which isn't rooted?

Copying the file from the system ends with an error since the system partition isn't available?
[Magisk] zgfg:
His app is called

GPay Checker: app that monitors Google Pay availability​

and it does not really check status of Play Integrity in the background but the status of G Pay

It's different. Actually, when the spoofed fingerprints get banned by Google, and Device Integrity starts to fail for you, it may still take few hours before Wallet/G Pay will start to fail

---

Last time I had the following situation:

- Google has banned the spoofed fingerprints that we used by the module at around 14 PM and tons of users posted about on XDA

- Only after the work I read about that at around 18 PM, I tested Play Integrity and Device Integrity was failing for me

- Still, at 21 PM I was happily shopping and paying by NFC and G Pay was not displaying any error

- Only next day in the morning, I found that G Pay was broken

And similarly at an earlier occasion. Google banned in the morning, I read at work and checked immediately, and indeed Device was failing

However, I went to shopping that afternoon and I paid a dozen of times with no problem

First payment failed for me late in the evening, about full 9 hours after Play Integrity/Device Integrity started to fail

----

So there is the delay between the time when Device Integrity starts to fail till G Pat starts to fail

And his app warns about the second (when G Pay in the background refreshes the status) not about the first

There are might be some hours between the first and second because apparently, G Pay caches the status of Play Integrity and happily runs with the cached status for quite some hours

Only later, when it next time periodically checks PI, it will realize that it's broken.

And only then this app will earn you
[Magisk] kocsogfax:
But how can i check it?

Play Integrity API checker : token error

Play store integrity check and TB checker are always show the original values...

Maybe it's not working on xiaomi.eu rom!
[Magisk] zgfg:
adb shell getprop
[Magisk] HippoMan:
It also works on Ubuntu linux, and I believe on MacOS
[Magisk] ArzZenic:
All checkers (I used TB Checker) will show original values, only

adb shell "logcat | grep 'PIF'" will show you, what is actually happening in the background

Like 100pages ago, there was a lot of posts, regarding an internal build issue with xiaomi.eu ROMs (from MIUI side), so it might be your situation.

After I started failing BASIC/DEVICE integrity on xiaomi.eu ROM, I reflashed to customOS (ArrowOS) and (for now) it works.
[Magisk] trol0lo:
Sounds like another method one could try for spoofing 🤪
[Magisk] bakaekze:
Xiaomi.EU is rebuilding all current stable releases to include a system apk to update a fingerprint.
[Magisk] Michaelx9:
I would especially like to thank @chiteroman , @osm0sis and @badabing2003 . Their tools and guidance allowed me to find 3 individual fingerprints that pass basic and device integrity. Hopefully that will be enough for the next period.
[Magisk] xSnowLeopardx:
Congrats mate, 3 is a solid amount. Have found my 5th just now. Hope we don't have to touch our stock.
[Magisk] straightcore:
Nice, I have about 15 of them :-)
[Magisk] nil?:
As the OP post still lacks significant things, could someone who have all the steps already performed compile them in sorta instructions?

Probably if you're added links to some posts it'd be more helpful for other people. This thread goes brrrrr and it's difficult to filter valuable posts.
[Magisk] ipilcher:
So ... anyone willing to share any advice on how to find OTA files from which the build.prop files can actually be extracted? After several hours, I've managed to find exactly one OTA file that actually works with standard tooling (payload-dumper-go).

At this rate, I'll expire of old age before I find a working fingerprint.
[Magisk] JustSom:
Hey, for the lurkers out there, I managed to get a fingerprint working as well. Thanks @chiteroman and @osm0sis

My process was: find a device from 2016-2017, download stock rom, extract system.img and look up the build.prop data from there.

After that just update /data/adb/pif.json, clear data/cache from google play services and google wallet, then reboot.

Tried 4 different devices, and got it working on the last one.

Took me a while to set everything up, but this method works, just take some time and patience!

Good luck to everyone!
[Magisk] BROKEN1981:
Normal
[Magisk] ipilcher:
How did you extract the build.prop file(s) from the stock ROMs? Everything I've found from that era seems to use non-standard formats.
[Magisk] BROKEN1981:
HHAeXchange - Apps on Google Play

The HHAeXchange mobile app empowers...

play.google.com

I have to hide root from this..... You don't need root to spoof GPS. It's out of hand. I now work with disabled people. Pretty sure if I don't show up I'm getting reported LoL.
[Magisk] ArzZenic:
There are several. Find a website with dumps of ROMs

pif.json from build.props should be:

ro.product.name -> PRODUCT

ro.product.device -> DEVICE

ro.product.manufacturer -> MANUFACTURER

ro.product.brand -> BRAND

ro.product.model -> MODEL

ro.build.fingerprint -> FINGERPRINT

ro.build.version.security_patch -> SECURITY_PATCH

ro.product.first_api_level -> FIRST_API_LEVEL

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-177#post-89189572

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] SuperMaximus:
I used a custom pif.json, cleared Google Play & Google Play Services and it shows Device is not certified. Do I need to wait everytime I experiment with new fingerprint until my device is certified?
[Magisk] YMatrix:
Thanks.

Now for the next phase - I copied the values to my pif.json file under /data/adb (I'm using chiteroman's version) and rebooted.

Wallet still says uncertified and can't use PI checkers because of the too many requests error.

What am I missing?

Ps the fp is with api 23 - is that good?
[Magisk] BROKEN1981:
Set API to 25 or 28. I had to set mine at 28 even though it was at 27. Very odd but it worked
[Magisk] bakaekze:
github release comments has some valuable links https://github.com/chiteroman/PlayIntegrityFix/discussions/112
[Magisk] JustSom:
Run "file system.img" from the extracted rom and see what it returns.

Some roms pack it as android sparse image, it could return something like: "system.img: Android sparse image, version: 1.0, Total of 1100800 4096-byte output blocks in 5626 input chunks.", if that's the case, you have to convert it to an ext4 format, just use this tool https://github.com/anestisb/android-simg2img

"simg2img system.img system.raw.img", then you'll be able to mount the raw one.
[Magisk] ruchimes:
So, where can I search for the build.prop?

Any help in what mobile brands and android versions?
[Magisk] JustSom:
Check previous message, messed up the quote here
[Magisk] JustSom:
Check this post: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-177#post-89189572
[Magisk] nil?:
And I must to answer myself.

There is a block under the main page content, it called "TOP LIKED POSTS" and it shows exactly what I wrote about. Nowadays we have a lot of **** on websites regardless of ad blockers and the banner blindness develps as a result.
[Magisk] BROKEN1981:
Nothing he did is against the forum rules. While people may not want prints posted, you still can. Also, I highly doubt Google is monitoring this thread and banning anything.
[Magisk] wrongway213:
A lot of folks here, including several who are doing the heavy lifting, don't share that opinion.
[Magisk] Nergal di Cuthah:
Really

Really? They just happened to catch all spoofs before we went a la carte?
[Magisk] nil?:
Can someone explain what if we'll just make some random changes in fingerprints to prevent statistical detection from the G***le side?
[Magisk] D€INOS:
To all mining more than one fingerprint:

I get the idea of having some backups, but don't check if they are working because by then you have possibly activated a traced missmatch and G could possibly banned all those prints with more than 1 print. That would be BAD .

I've dl a few build.props but haven't checked them, and I won't until/if mine stops working.
[Magisk] Nergal di Cuthah:
As far as I can tell, If you change bits it won't match a cts profile and thus won't pass PI
[Magisk] BROKEN1981:
They have mixed feelings.
[Magisk] ipilcher:
The ones I'm seeing either aren't ZIP files or don't have either system.img or payload.bin in them.
[Magisk] nil?:
So is there a thing like a whitelist of all possible combinations?
[Magisk] JustSom:
I used 7z to extract the files, some were a zip, inside an lz4, inside a tar, I just kept using "7za x file.something" until it extracted to that android sparse format, then I did the image conversion thing to get it to ext4 and mount it.

If you downloaded a .bin, you have to use https://github.com/tobyxdd/android-ota-payload-extractor to get it working
[Magisk] JustSom:
You gotta search a little bit inside the extracted files from stock roms, there's not a single way to find the system.img, every device follows a different structure
[Magisk] dmenezes:
As Tonto said to the Lone Ranger: "Who is this THEY, paleface?" ;-)

Just to make my position clear: *I* don't have any "mixed feelings". Absolutely no details should be posted here or anywhere public, as we have a very limited resource that, once gone, will be gone forever.

It doesn't matter whether Google is mining this thread for fingerprints to kill -- what matters is whether we are doing all we can to avoid it or not. I am doing my part by not posting *anything* here, and I urge every single one of my brothers and sisters here to do the same.

Remember, loose lips (and keyboards) sink not only ships, but everything that needs to be kept confidential.
[Magisk] ipilcher:
I can't help but feeling that those who have successfully discovered multiple fingerprints are using a very different process. I've been at this for hours and I've only found a single manufacturer that makes their OTA updates available in a format that I can extract.
[Magisk] digger16309:
Thanks to @ArzZenic , I found my way on this. I got lucky after about a half hour of effort.

Do I need the HuskyDG resetprop.zip?

What does that do?

I'm hesitant to use it if already passing.
[Magisk] stanley321:
My device is from Google but I use a custom.pif.json from another brand.

I passed Basic Integrity, but failed Device Integrity

How can I fix the Device Integrity?
[Magisk] ArzZenic:
You don't need it. Until you don't pass anymore, it's just another game of cat & mouse. Enjoy while your pif works :)

After that, just repeat the steps and find another fingerprints
[Magisk] ipilcher:
Can you share anything about how you managed to find the OTA images from which you extracted your build props? I'm going crazy trying to even find the firmware images for phones these old, and when I do find them they seem to be in weird formats that I can't parse.
[Magisk] JustSom:
Dude, from all the stock roms that I downloaded, I just used 7zip and got to the system.img.

Sometimes they pack it inside multiple layers, starting with a .zip, then it uncompress to something.tar.lz4, then you repeat the same extraction process a couple of times until you get to the .img

And the images that I found were from those stock rom distribution websites, just googled "Device stock rom" and went to the first link there, I'm not sure how can I help you in this case though
[Magisk] pershoot:
starting today, wallet complains of 'doesn't meet security requirements'. on v14.
[Magisk] Revontheus:
I recommend getting a 2nd-hand iPhone X. I was able to get one in ebay for 50$, set up Apple Pay and now everything works. Now I don't have to worry about my main device being rooted.

You need to find a new device fingerprint which you will place in

/data/adb/pif.json

. Google is now banning older device fingerprints, so you have to search for new, unbanned ones.
[Magisk] nil?:
One more weird idea. Why do we even have to juggle this crap? I'm sure there are more than seven people from seven different EU countries here. Let's fight Go***e with the heaviest weapon in the world: the European Commission.

How it works

How it works - a step by step guide to the European citizens' initiative (ECI)

citizens-initiative.europa.eu
[Magisk] fede2782:
Unfortunately I had no luck with the other 50 props (almost every brand) I tried. This time I think it may be the end of Play Integrity Fix modules on both my rooted devices.
[Magisk] JustSom:
You need to find a valid device fingerprint to get it working again, the one that was included got banned.

Check https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-177#post-89189572
[Magisk] JustSom:
I downloaded stock roms from devices from 2016-2017, extracted the system.img and got it working on my fourth attempt

its a patience game
[Magisk] pershoot:
yea, I'll read up on the thread. thx.
[Magisk] pershoot:
yea, I'll read up on the thread. thx for direct comment link.
[Magisk] Revontheus:
I pm'ed you a device fingerprint you can try.
[Magisk] bakaekze:
Non-working print, find another one.
[Magisk] nil?:
Of course it may be a bit tricky to collect a million signatures for the initiative but probably if we start Google may cool down their holy wars with the freedom of Android.
[Magisk] Nergal di Cuthah:
Use a different fingerorint the one you have is banana-ed.
[Magisk] Revontheus:
Found this Github repo for generating custom PIF from Pixel images. Use it before it gets taken down.
[Magisk] Nergal di Cuthah:
Ubuntu only?
[Magisk] nil?:
I feel stupid but what is the point? I have a Pixel but need to spoof fingerprint because the original one doesn't pass.
[Magisk] Revontheus:
I ran it on Ubuntu VM, on Win11.
[Magisk] Nergal di Cuthah:
To get from newer than pixel 2 and older than pixel 4(?) roms
[Magisk] Nergal di Cuthah:
I'll have to dust off my vm skills from 13 years ago lol
[Magisk] nil?:
I'm sure it's cross platform as f.
[Magisk] JustSom:
You could probably use WSL too
[Magisk] nil?:
Let's imagine how long it will take for G***le to fix the problem.
[Magisk] ArzZenic:
You should consider deleting this post..