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.
Table of Contents
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.
- To begin with, flash the wget2 module via Magisk/KernelSU/APatch.
- Then, flash the Play Integrity Fork CI module from GitHub Actions.
- Now, download and install the Termux app from F-Droid.
- 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
- 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
- Once done, head over to the below location to access the custom.pif.json
/data/adb/modules/playintegrityfix
Custom.pif.json file content for the month of June
If you don’t want to carry out the aforementioned steps, then you can simply create a new text file in data/adb/modules/playintegrityfix and paste the below values in it:
{
// Build Fields
"MANUFACTURER": "Google",
"MODEL": "Pixel 6",
"FINGERPRINT": "google/oriole_beta/oriole:16/BP31.250523.010/13667654:user/release-keys",
"BRAND": "google",
"PRODUCT": "oriole_beta",
"DEVICE": "oriole",
"RELEASE": "16",
"ID": "BP31.250523.010",
"INCREMENTAL": "13667654",
"TYPE": "user",
"TAGS": "release-keys",
"SECURITY_PATCH": "2025-06-05",
"DEVICE_INITIAL_SDK_INT": "32",
// System Properties
"*.build.id": "BP31.250523.010",
"*.security_patch": "2025-06-05",
"*api_level": "32"
// Advanced Properties
"spoofBuild": "1",
"spoofProps": "1",
"spoofProvider": "1",
"spoofSignature": "0",
"spoofVendingSdk": "0",
"verboseLogs": "0"
// Beta Released: 2025-06-25
// Estimated Expiry: 2025-08-06
}
That’s it. These were the steps to get the fingerprint PIF.JSON file using Play Integrity Fork. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution as soon as possible.
