When chiteroman discontinued the original PlayIntegrityFix, he pointed the community to exactly one alternative: Play Integrity Fork. Created by osm0sis — an XDA Senior Recognized Developer known for BusyBox NDK, AnyKernel3, and the original autopif2.sh fingerprint script — PIFork is the stable, GPL-licensed Zygisk module that restores Play Store device certification on rooted Android devices. Thoughtfully scoped to the <A13 Play Integrity device verdict, methodically maintained, and designed to adapt as Google's requirements evolve.
Core Features
A stable, methodically developed Play Integrity module designed to remain effective as Google's requirements evolve.
Custom Fields & Props
Unlike the original PIF's fixed field set, PIFork lets you include as few or as many android.os.Build class fields and system properties as needed. This flexibility allows the module to adapt as Google changes which fields are checked — without requiring a module update to add new fields.
prop Format (v15+)
Starting with v15, PIFork switched from JSON to the simpler key=value prop format for user configuration — eliminating the trailing comma and paired-quote frustrations of pif.json. PIFork is the only PIF fork that supports both pif.prop and pif.json formats simultaneously.
autopif2.sh Script
Includes autopif2.sh — osm0sis's original automatic fingerprint fetcher. Run it in a root shell to automatically generate a valid, working pif.prop configuration. Also includes gen_pif_custom.sh for generating a custom pif.prop from your own device's build.prop files.
Advanced Settings
A dedicated Advanced Settings section in pif.prop controls additional spoofing behaviors — including spoofVendingFinger (spoof fingerprint to Play Store process), signature spoofing, and provider behavior. Configured by editing pif.prop, running included scripts, or creating flag files in the module directory.
Google Wallet & RCS on A13+
While the primary target is <A13 Play Integrity, PIFork continues to help on Android 13+ devices by facilitating Google Wallet payment availability and Google Messages RCS activation — two high-value use cases that depend on device certification but use different checking mechanisms.
GPL-3.0 Open Source
Fully open source under GPL-3.0. Entire codebase is auditable on GitHub — including the Zygisk injection library, all shell scripts, and the spoofing logic. Developed methodically and transparently by an established XDA developer with 1,700+ stars.
Understanding the <A13 vs A13+ Play Integrity Split
Play Integrity doesn't work the same way on all Android versions. PIFork's README makes this distinction explicit — and understanding it is key to knowing what to expect from the module.
Uses the legacy deviceRecognitionVerdict check (formerly SafetyNet ctsProfileMatch). Build fingerprint spoofing via PIFork is sufficient to pass MEETS_DEVICE_INTEGRITY.
The new deviceRecognitionVerdict requires a locked bootloader to pass even MEETS_DEVICE_INTEGRITY. Fingerprint spoofing alone cannot satisfy this hardware check.
On Android 13+ devices, PIFork still provides value for Google Wallet and RCS activation, and can contribute to MEETS_STRONG_INTEGRITY when combined with Tricky Store and a valid keybox — the hardware attestation layer handles the locked-bootloader check while PIFork handles the fingerprint layer.
PIFork vs PIF Inject — Which to Use?
Both are community-maintained forks of chiteroman's original PIF. The practical differences for most users are minimal — both achieve MEETS_DEVICE_INTEGRITY on <A13 devices and both work with Tricky Store for MEETS_STRONG_INTEGRITY. Key distinctions:
| Aspect | PIFork (osm0sis) | PIF Inject (KOWX712) |
|---|---|---|
| Endorsed by chiteroman | ||
| Config format | prop + json (both) | prop only (inject-s) |
| Custom Build fields | Fully flexible | Fixed set |
| autopif2.sh script | Included | action.sh |
| Explicit <A13 vs A13+ scope | ||
| License | GPL-3.0 | GPL-3.0 |
Updating Your Fingerprint
Device fingerprints can become outdated — Google revokes prints that are too old or widely used. To keep PIFork working, update pif.prop when your device integrity verdict drops. Three ways to do it:
sh /data/adb/modules/playintegrityfix/autopif2.sh — automatically fetches and writes a working fingerprint to pif.prop./data/adb/modules/playintegrityfix/pif.prop in a root file explorer and paste in a fresh key=value fingerprint configuration.build.prop files — useful for developers building custom ROM prints.Frequently Asked Questions
MEETS_DEVICE_INTEGRITY and both work with Tricky Store for MEETS_STRONG_INTEGRITY.
MEETS_DEVICE_INTEGRITY requires a locked bootloader which fingerprint spoofing alone cannot bypass. However, PIFork on Android 13+ still helps activate Google Wallet and Google Messages RCS support, and can contribute to MEETS_STRONG_INTEGRITY when combined with Tricky Store and a valid keybox.
pif.prop. You can also manually edit /data/adb/modules/playintegrityfix/pif.prop using a root file explorer in plain key=value format. The gen_pif_custom.sh script additionally allows creating a custom print from your own device's build.prop files.
MEETS_STRONG_INTEGRITY, combine it with Tricky Store and a valid unrevoked hardware keybox (e.g., from Yuri Keybox Manager). PIFork + Tricky Store + YuriKey together form the complete integrity restoration stack.