Play Integrity Fix Magisk Module: Download & Installation Guide (2026)

Play Integrity Fix (PIF) is an open-source Zygisk module developed by chiteroman and osm0sis that injects certified device fingerprints into Google Play Services at runtime. By spoofing untampered hardware build properties, it bypasses Google Play Integrity and SafetyNet checks, enabling rooted Android devices to pass MEETS_BASIC_INTEGRITY and MEETS_DEVICE_INTEGRITY so that banking apps, Google Wallet, and streaming platforms function without restrictions.

As Google continuously tightens server-side Play Integrity API validation, traditional root-hiding solutions often fail when bootloaders are unlocked. Play Integrity Fix dynamically modifies memory structures inside com.google.android.gms.unstable to intercept DroidGuard attestation calls and return valid, trusted responses.

Technical Specifications & Compatibility Matrix

Specification	Details
Module Name	Play Integrity Fix (Universal SafetyNet Fix)
Developer	chiteroman, osm0sis (Fork / Community maintainers)
Architecture	Zygisk / Native C++ Hook
Root Compatibility	Magisk v24.0+ (Zygisk enabled), KernelSU, APatch
Android OS Support	Android 8.0 (Oreo) through Android 15 & 16
Attestation Targets	`MEETS_BASIC_INTEGRITY`, `MEETS_DEVICE_INTEGRITY`
Config File	`/data/adb/pif.json`

How Google Play Integrity Works on Rooted Devices

Google’s Play Integrity API evaluates the genuine security state of an Android device across three distinct tiers:

MEETS_BASIC_INTEGRITY: Confirms the app is running on an unmodified Android runtime environment. It fails if basic root binaries or zygote hooks are detected.
MEETS_DEVICE_INTEGRITY: Verifies the device matches a certified Android build and bootloader lock state. When a bootloader is unlocked, hardware key attestation reports this to Google’s servers. Play Integrity Fix works by forcing fallback to software-based basic attestation and injecting a valid unbanned device fingerprint.
MEETS_STRONG_INTEGRITY: Requires hardware-backed cryptographic attestation backed by the device’s Trusted Execution Environment (TEE) or Titan M security chip. Unlocked bootloaders cannot pass strong integrity without a locked factory state. Fortunately, virtually all banking, payment, and enterprise apps currently require only MEETS_DEVICE_INTEGRITY.

Step-by-Step Installation Guide

Follow these verified steps to install and activate Play Integrity Fix:

Step 1: Prepare Your Root Environment

Open the Magisk app on your device.
Tap the Settings icon (top right).
Ensure Zygisk is toggled ON.
Enable Enforce DenyList, then tap Configure DenyList.
Check all processes under Google Play Services (com.google.android.gms), specifically com.google.android.gms.unstable.

Step 2: Download & Flash the Module

Download the latest release from the verified links below:
- Play Integrity Fix
- Play Integrity fork
In Magisk Manager, switch to the Modules tab (puzzle icon).
Tap Install from Storage and select the downloaded zip file.
Allow the flashing process to complete, then tap Reboot.

Step 3: Clear Play Services Cache

After rebooting, you must clear old cached attestation verdicts:

Go to your phone’s Settings > Apps > See all apps.
Tap the three dots menu in the top right and select Show system.
Locate Google Play Services, tap Storage & cache, then Clear Cache.
Locate Google Play Store, tap Storage & cache, then Clear Storage.
Reboot your device one final time.

Customizing Device Fingerprints with `pif.json`

When Google revokes shared public fingerprints, you can supply your own private device profile using a custom pif.json file placed in /data/adb/pif.json:

{
  "PRODUCT": "walleye",
  "DEVICE": "walleye",
  "MANUFACTURER": "Google",
  "BRAND": "google",
  "MODEL": "Pixel 2",
  "FINGERPRINT": "google/walleye/walleye:8.1.0/OPM1.171019.011/4448085:user/release-keys",
  "SECURITY_PATCH": "2017-12-05",
  "FIRST_API_LEVEL": "26"
}

Modules automatically read this file during Google Play Services startup, allowing you to maintain device integrity indefinitely.

Troubleshooting Common Errors

1. Device Integrity Still Fails

Ensure Zygisk is enabled and active. If using KernelSU or APatch, ensure Zygisk Next or Zygisk-Assistant is installed and running.
Verify that com.google.android.gms cache was cleared after the reboot.
If Google launched a fingerprint revocation wave, update the module or inject a private build fingerprint using the PIF extraction script.

2. Google Wallet / Google Pay Rejection

Go to Google Play Store > Settings > About, and check Play Protect certification. It should say “Device is certified”. If uncertified, repeat the cache wipe.
Add Google Wallet to the Magisk DenyList / Shamiko hide list.

Verified Download Links & Support

Play Integrity Fix

Primary Module Download: Play Integrity Fix
Alternative Community Fork: Play Integrity fork
Official Portal: Play Integrity Fix on magiskmodule.gitlab.io
Creator Support: Donate | Support Group

Frequently Asked Questions (FAQ)

Does Play Integrity Fix pass Strong Integrity?

No. Strong integrity requires hardware-backed private keys stored within the TEE, which are invalidated whenever a bootloader is unlocked. Play Integrity Fix successfully achieves Basic and Device integrity, which is what 99.9% of commercial apps require.

Can I use Play Integrity Fix with KernelSU or APatch?

Yes. Play Integrity Fix works seamlessly on KernelSU and APatch provided you have a Zygisk implementation (such as Zygisk Next) installed and active.

How often do fingerprints need to be updated?

Google periodically blacklists public fingerprints that appear in hundreds of thousands of concurrent attestations. When this happens, a module update or custom pif.json refresh is needed to restore Device Integrity.

You also may like 〣〣