Download PIF JSON File from Here

From this guide, you can download the PIF JSON file for your device. Among the various steps involved in passing Strong Integrity, one involves getting the customer fingerprint file from one of the Pixel devices. This file is known as PIF and the format is .JSON. To get them, there are two ways out:

• Install Play Integrity Fix > Download KSU Web UI > Launch it > Select Play Integrity Fix > Tap on Fetch PIF JSON.
• Install Play Integrity Fork > Flash wget2 module > Install Termux > Execute 3 commands . Left: Play Integrity Fix | Right: Play Integrity Fork

NOTE: Some rooting apps like KSU Next might give you an Action button that will allow you to get the PIF file in one tap, however, that feature might not be supported by Magisk. On the other hand, the steps mentioned above are universally supported by all rooting apps [Magisk/APatch/KernelSU].

So, when one can easily get the PIF JSON file using the aforementioned methods, why is there a need to download it from this guide? That’s a great question. The thing is, there are many custom ROMs that give you the option to manually upload the keybox and PIF JSON file, without even the need to root it in the first place.

Upload PIF JSON in DerpFest ROM

So it doesn’t make any sense to root the ROM and carry out the above steps for a PIF file. Instead, you can simply get the file from this post and upload it to your ROM, just as you do for the keybox file. So on that note, let’s make you aware of the download links and the difference in files when using Play Integrity Fix and Fork [if you are using them].

• Download PIF JSON Files from Here File 1 [From Play Integrity Fix] File 2 [From Play Integrity Fix] File 3 [From Play Integrity Fork] File 4 [From Play Integrity Fork]
• Location of PIF JSON in Case of Play Integrity Fix and Fork
• How Does a PIF.JSON File Look
• How Does a Custom.PIF.JSON File Look

Download PIF JSON Files from Here

Make sure to rename the file as pif.json/custom_pif.json [i.e., remove everything after the ‘pif’ keyword, such as numbers, underscore, etc].

File 1 [From Play Integrity Fix]

File 2 [From Play Integrity Fix]

File 3 [From Play Integrity Fork]

File 4 [From Play Integrity Fork]

Location of PIF JSON in Case of Play Integrity Fix and Fork

If you are simply loading the PIF file in the custom ROM’s designated field, you wouldn’t need any of the information in this section. However, if your device is rooted, then it is of paramount importance that you get yourself acquainted with the location of the PIF file for both the modules- Fix and Fork.

• If you are using Play Integrity Fix, then you’ll have to place the pif.json file in data/adb.
• However, if you are using Play Integrity Fork, then you’ll have to place the custom_pif.json file under data/adb/modules/playintegrityfix. Left: Play Integrity Fix | Right: Play Integrity Fork

How Does a PIF.JSON File Look

This is the file generated by the Play Integrity Fix Module and is placed at data/adb.

FINGERPRINT

"google/tangorpro_beta/tangorpro:16/BP31.250610.009.A1/13905234:user/release-keys"

MANUFACTURER

"Google"

MODEL

"Pixel Tablet"

SECURITY_PATCH

"2025-07-05"

How Does a Custom.PIF.JSON File Look

This is the file generated by the Play Integrity Fork Module and is placed at data/adb/modules/playintegrityfix.

{

// Build Fields

"MANUFACTURER": "Google",

"MODEL": "Pixel 8a",

"FINGERPRINT": "google/akita_beta/akita:16/BP31.250610.009/13905196:user/release-keys",

"BRAND": "google",

"PRODUCT": "akita_beta",

"DEVICE": "akita",

"RELEASE": "16",

"ID": "BP31.250610.009",

"INCREMENTAL": "13905196",

"TYPE": "user",

"TAGS": "release-keys",

"SECURITY_PATCH": "2025-07-05",

"DEVICE_INITIAL_SDK_INT": "32",



// System Properties

"*.build.id": "BP31.250610.009",

"*.security_patch": "2025-07-05",

"*api_level": "32"



// Beta Released: 2025-08-14

// Estimated Expiry: 2025-09-25

}

(Cancel Reply)

Δ

How to Get Fingerprint PIF.JSON File using Play Integrity Fork

In this guide, we will show you the steps to get the fingerprint PIF.JSON file using Play Integrity Fork. A week back or so, we got the unfortunate news that the Play Integrity Fix module has been discontinued by the developer chiteroman. We can’t thank him enough for the invaluable work he has done for this community. But going forward, what can be our next course of action?

Well, while this module was up and running, another developer [osm0sis] was also running a fork of this module, which goes by the name Play Integrity Fork. While we wouldn’t say that it was under the shadow of Fix, but it wasn’t being used that much when compared to its counterpart.

However, all that is about to change now, and so there are a few queries that might pop up in your minds. In this regard, one of the most common questions that I have been asked for the past week is how to get the fingerprint PIF.JSON file in the Play Integrity Fork module.

As you might already be aware, the Fix module already has this embedded in its module; you just need to launch it via KSUWebUI, hit the Fetch PIF.JSON option, and you’ll get the file. But that’s not possible via the Fork module via the direct route. Why? Let’s find out, and after that, we will list the plausible steps through which you can get this file using this module. Follow along.

• Why is the PIF JSON Fingerprint File Missing in Play Integrity Fork
• How to Get the Fingerprint PIF.JSON File using Play Integrity Fork
• Direct Download PIF JSON Files

Why is the PIF JSON Fingerprint File Missing in Play Integrity Fork

By default, the module comes with a template of a PIF JSON file that you need to fill in manually. You can get this file from /data/adb/modules/playintegrityfix. Once you fill in the values, simply rename it to custom.pif.json, and your task stands complete. But why hasn’t the dev simply added this file, as was the case with the Fix module? Here’s what he has to say regarding this:

There’s intentionally no pif.json in the module because the goal remains to be futureproof, and including something that may be banned and obsolete within days would be contrary to that goal.

However, finding these files might not be everyone’s cup of tea. Not only are a few of these remains, but finding them is also quite an effort taking task. The developer acknowledges this, and hence, he has added a script to extract the latest Pixel Beta fingerprint along with the module. The script is named autopif2, which generates a random device fingerprint from the latest Pixel Beta. So let’s have a look at the steps to make full use of this file.

How to Get the Fingerprint PIF.JSON File using Play Integrity Fork

Before starting, please take a backup of all the data on your device, just to be on the safe side. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device, and data by performing the below steps.

NOTE: There are quite a few ways of getting this job done, however, I personally found Termux to be the easiest among all of them. But if you want to try out any other method, then run the generation script from a root manager app that supports the module Action button or from a file explorer app that supports script execution.

1. To begin with, flash the wget2 module via Magisk / KernelSU / APatch .
2. Then, flash the Play Integrity Fork CI module from GitHub Actions .
3. Now, download and install the Termux app from F-Droid.
4. Then launch it and execute the following three commands: su //you’ll get a SU request, hit Grant cd /data/adb/modules/playintegrityfix //to change the directory to the module’s sh autopif2.sh –preview // this will give you the fingerprint file
5. You can also add a few other parameters to the above command, namely: su -c sh /data/adb/modules/playintegrityfix/autopif2.sh -a -m -p -s -a Advanced -m Match -p Preview -s Strong
6. Once done, head over to the below location to access the custom.pif.json /data/adb/modules/playintegrityfix

Direct Download PIF JSON Files

If you don’t want to manually carry out the aforementioned steps, then you may directly get the PIF JSON file from our below guide:

Download PIF JSON File from Here

• How to Pass Strong Integrity Using Revoked/Banned Keybox File!
• How to Pass Play Integrity in New Android 13+ Checks
• Guide to Pass Strong Integrity on Unlocked Bootloader & Root!
• How to Spoof/Fake/Hide Bootloader Unlock Status
• How to Pass Play Integrity Test on any Custom ROM [Video]

• Drw 6 months ago Reply Problem solved. Termux wasn’t prompting me to grant su user access. Found where to enable it in the KSU Next GUI under Superuser.
• Drw 6 months ago Reply I’m getting “su program not found.” Rooted with ksu and susfs. Modules installed are BKI, Play integrity fork, shamiko, susfs for ksu, tricky store, wget2, zygisk lsposed, and zygisk next. Nothing tweaked.
• mario 7 months ago Reply sorry, what do you mean with “Then, flash the Play Integrity Fork CI module from GitHub Actions.” ? i have pif v13 flashed in magisk
• Mohamed 7 months ago Reply Hi, can you please help me with a vaild keybox pleaaase 🙏
• Antonis 7 months ago Reply 1) “Then, flash the Play Integrity Fork CI module from GitHub Actions” https://github.com/osm0sis/PlayIntegrityFork/actions what do i download? 2) and then what do i do with custom.pif.json ?
• Antonis 7 months ago Reply “Then, flash the Play Integrity Fork CI module from GitHub Actions” https://github.com/osm0sis/PlayIntegrityFork/actions what do i download?

(Cancel Reply)

Δ