Play Integrity Fix (PIF) for Magisk: what works now
Play Integrity Fix is a Zygisk module that spoofs device properties to Google Play services' integrity check. The original by chiteroman has been removed from GitHub; two maintained forks carry on. Since Google's 2025 changes they can still restore the basic and legacy verdicts on a rooted phone, but not Android 13+ device integrity on their own. Here is what each option does and how to set it up.
Last updated 12 sourcesHow we check pages
chiteroman's PlayIntegrityFix repository no longer exists
github.com/chiteroman/PlayIntegrityFix now returns a 404, so old links to its releases are dead. Its final notice, preserved in a fork, says Google removed the legacy checks on Android 13 and later and that a valid keybox and Tricky Store are now needed for the device verdict. Use one of the maintained forks below, and never download “PIF” zips from mirror sites.
- RecommendedPlayIntegrityFork v18osm0sis, August 29, 2026
- AlternativePIF inject-s v4.9KOWX712, October 15, 2026
- RequiresZygiskMagisk's built-in Zygisk works
- BASIC verdictUsually possible
- DEVICE on Android 13+Not with PIF aloneNeeds a locked bootloader or attestation spoofing
- Google WalletNot supported by Google
Setting up Play Integrity Fix: the whole job
- Step 1 · 1 minuteTurn on Zygisk
- Step 2 · 2 minutesInstall the module
- Step 3 · 5 minutesSet a fingerprint
- Step 4 · 1 minuteApply the changes
Which Play Integrity Fix should I use?
Install only one: both forks use the same module folder, /data/adb/modules/playintegrityfix.
| Project | Status | Latest | What sets it apart |
|---|---|---|---|
| PlayIntegrityFork (osm0sis) | Maintained | v18, Aug 29, 2026 | Configured with custom.pif.prop; the autopif4 script fetches a fingerprint; detailed troubleshooting in its README. v18 drops x86 and x86_64. |
| PlayIntegrityFix inject-s (KOWX712) | Maintained | v4.9, Oct 15, 2026 | Configured with pif.prop and a WebUI. Supports x86_64 again since v4.8. Its README warns against third-party fingerprint tools. |
| chiteroman's PlayIntegrityFix | Removed | — | The original. Deleted from GitHub; KOWX712 keeps unmodified copies in its main and inject branches. |
| PlayIntegrityFix-NEXT (EricInacio01) | Archived | v3.0 | Archived on December 28, 2025. Do not install it on new setups. |
What it can and can't pass
Google's Play Integrity API reports three device labels. Since May 2025 it uses hardware-backed signals for every verdict, and on Android 13 and later the device label needs hardware proof of a locked bootloader. Spoofing properties cannot fake that proof.
| Verdict | What Google requires | With PIF on a rooted phone |
|---|---|---|
| MEETS_BASIC_INTEGRITY | Bootloader locked or unlocked; on Android 13+ the attestation root of trust must come from Google. | Usually |
| MEETS_DEVICE_INTEGRITY (Android 13+) | Hardware-backed proof of a locked bootloader and a certified manufacturer image. | No PIF alone cannot. |
| MEETS_DEVICE_INTEGRITY (legacy, below Android 13) | The older, software-based device check. | Often This is what PIF still restores. |
| MEETS_STRONG_INTEGRITY | Device integrity plus security updates in the last year for all partitions. | No |
The PlayIntegrityFork README points people who want Android 13+ device or strong integrity to attestation-spoofing modules such as Tricky Store, Tricky Store OSS or TEESimulator. Those need an unrevoked hardware keybox, which is a leaked private key: Google revokes leaked keys, typically within several days, and phones that launch with Android 16 only use Remote Key Provisioning, whose keys Google says are not affected by such leaks. In October 2026 the PixelOS team reported that devices without Remote Key Provisioning now pass basic integrity only, whatever keybox or fingerprint they use. This guide does not cover obtaining keyboxes.
Before you start
You will need
- Magisk with Zygisk enabled (Settings → Zygisk, then reboot). On KernelSU or APatch you need a Zygisk module such as Zygisk Next, ReZygisk or NeoZygisk instead.
- One Play Integrity module, downloaded from its GitHub releases page: PlayIntegrityFork or inject-s.
- A way to check the result, such as the open-source Play Integrity API Checker app.
- Google Play services kept off the DenyList. The PlayIntegrityFork README says adding it breaks the module.
Know the limits
- No Android 13+ device verdict from property spoofing. Apps that require it, and many banking apps, will still refuse to run.
- Google Wallet. Google says Wallet doesn't run on rooted phones or phones with an unlocked bootloader. PlayIntegrityFork notes Wallet checks the legacy device verdict, so it may work, but nothing guarantees it.
- It does not hide root. KOWX712's README says the module is “not made to hide root, nor to avoid detections in other apps”. Magisk itself no longer hides root either.
- Fingerprints expire. PlayIntegrityFork says Pixel Canary prints from
autopif4expire roughly every six weeks and now only suit strong-integrity setups.
Install and configure PlayIntegrityFork
These steps follow the PlayIntegrityFork README. inject-s works the same way but is configured through its WebUI and pif.prop.
-
Turn on Zygisk
1 minuteIn the Magisk app open Settings, enable Zygisk and reboot. Leave Enforce DenyList off if you also use a hiding module such as Shamiko, Zygisk Assistant, NoHello or Treat Wheel, as the README describes.
-
Install the module
2 minutesDownload the latest zip from the PlayIntegrityFork releases page. In the Magisk app tap Modules → Install from storage, pick the zip and reboot. Remove any other Play Integrity module first.
-
Set a fingerprint
5 minutesThe module reads
custom.pif.propin its folder. Either copyexample.pif.proptocustom.pif.propand fill in a working build fingerprint, or let the bundled script fetch the current Pixel Canary print: tap the module's Action button in Magisk, or run it from a root shell. The script's default--strongmode prepares a strong-integrity setup.Fetch a fingerprint from a root shell$su $cd /data/adb/modules/playintegrityfix $sh autopif4.sh --strong -
Apply the changes
1 minuteRestart the Play Integrity processes with the module's script, or simply reboot.
Apply from a root shell$su $cd /data/adb/modules/playintegrityfix && sh killpi.sh
Check that it worked
Open the Play Integrity API Checker and run a check. On Android 13 and later, Google only returns the optional basic and strong labels to licensed apps, so a sideloaded checker may show fewer labels than the real result. To see the legacy (below Android 13) verdict on a newer phone, the README says to enable spoofVendingSdk temporarily, then turn it off again, because leaving it on breaks parts of the Play Store.
For Play Store certification, open Play Store → profile icon → Settings → About. If it still says uncertified, clear the data of the Play Store, Google Play Protect Service and Google Play services, then reboot.
Errors and fixes
Only MEETS_BASIC_INTEGRITY passes on Android 13 or later
That is the expected result for property spoofing on an unlocked phone: the Android 13+ device verdict needs hardware proof of a locked bootloader. If you were using Tricky Store and passed more before, its keybox has most likely been revoked.
Basic integrity fails
The README's advice for this case: disable every other module, then try a known-working fingerprint. Xposed modules and custom fonts that hook Google Play services are known triggers.
Device integrity fails on a custom ROM
Set spoofVendingFinger to the current Pixel Canary fingerprint, run killpi.sh and test again. If the verdict improves, the ROM's own fingerprint is probably on Google's banned list. Also check uname -r for a banned kernel name and whether the ROM is signed with test keys.
Device integrity fails on KernelSU or APatch
The README suggests disabling the Zygisk module, rebooting, enabling it again and rebooting once more.
Google Wallet still refuses to add a card
Clear the cache of Google Wallet and Google Pay, and the cache or data of Google Play services, or wait 24 to 72 hours. Clearing Play services data resets paired Wear OS watches. Google does not support Wallet on rooted phones, so it may never work.
An app detects changed system properties
Some apps notice deleted or persistent props. The README offers two opt-in files, skipdelprop and skippersistprop, to turn those changes off.
Questions people ask
Is chiteroman's Play Integrity Fix still available?
No. The repository was removed from GitHub and its links return 404. KOWX712 keeps unmodified copies, and PlayIntegrityFork lists it in its credits as “no longer online”.
PlayIntegrityFork or inject-s?
Both are maintained. PlayIntegrityFork has the most detailed documentation; inject-s offers a WebUI and x86_64 support. Install only one.
Can Play Integrity Fix pass device integrity on Android 13+?
Not by itself. Google's device verdict on Android 13 and later needs hardware-backed proof of a locked bootloader.
Do I need Tricky Store?
Only if you want to attempt Android 13+ device or strong integrity, and then only with an unrevoked hardware keybox, which Google revokes when leaked. Many users settle for the basic and legacy verdicts.
What is the difference between Tricky Store, Tricky Store OSS and TEESimulator?
Tricky Store (5ec1cff) is closed source since 1.1.0; its latest release is 1.4.1. Tricky Store OSS is a GPL-3.0 rewrite that uses the same files. TEESimulator (JingMatrix) is a GPL-3.0 software KeyMint that also requires a keybox.
Should I add Google Play services to the DenyList?
No. The PlayIntegrityFork README says this breaks the module.
Does Magisk hide root by itself?
No. Magisk's FAQ says it no longer handles root hiding, and v31.1, the current stable release, removed the option to hide the Magisk app.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- PlayIntegrityFork README and releases (osm0sis)
- PlayIntegrityFix inject-s and preserved original (KOWX712)
- Play Integrity API: integrity verdicts (Android Developers)
- Play Integrity API: hardware-backed verdict improvements (Android Developers)
- Key and ID attestation: revocation and RKP (Android Developers)
- Tricky Store (5ec1cff)
- Tricky Store OSS (beakthoven)
- TEESimulator (JingMatrix)
- Play Integrity status for unofficial ROMs (PixelOS)
- Play Integrity API Checker (1nikolas)
- Google Wallet: unsupported devices (Google)
- Magisk FAQ (topjohnwu)
Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.
Report a problem with this page