Play Integrity Fix Next

This is a fork of PlayIntegrityFix, created by chiteroman. The aim of this fork is to achieve valid attestation on rooted devices under the new PlayIntegrity API rules.

⚠️ To use this module properly, please install Tricky Store beforehand.

⚠️ NOTES

The purpose of this fork is to ensure, by all means possible, that DEVICE_INTEGRITY is obtained. However, in some cases, users with versions > Android 14+ may experience some unexpected crashes in the Play Store. This is due to the fact that SpoofVendingSDK is active. To fix this problem, there are two ways:

1. Access the module’s WebUI and disable the “Spoof sdk version to Play Store” option.

2. Manually change the pif.json file inside the module:

  "spoofProvider": true,
  "spoofSignature": false,
  "spoofProps": true,
  "DEBUG": false,
  "spoofVendingSdk": false

If you are running a custom ROM or kernel, make sure that your kernel name is not blacklisted. You can check this by running the command uname -r. You can find the list of prohibited strings here: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89308909

💡 Tips and Tricks

There are a few tips you can use with this Fork:

• TrickyStore - You can use it to secure better certificates (e.g. security patch, and a beeebox, if you know what I mean).
• TrickyAddon - An excellent Front-End for TrickyStore, useful for security patching, configuring boot hash and also target.txt

🗃️ How to Install

PIF Next only works with ONE of the solutions below:

• Magisk with Zygisk enabled.
• KernelSU with ZygiskNext or ReZygisk module installed.
• KernelSU Next with ZygiskNext or ReZygisk module installed.
• APatch with ZygiskNext or ReZygisk module installed.

✅ How to Check Veredicts

After flashing PIF Next, you can check your verdicts using:

• Play Integrity API Checker (PlayStore) *or by enabling Developer Options in the Play Store by going to Settings > **About > Click 5x on “Play Store Version”, then go to ‘General’ > “Developer Options” *and click on “Check Integrity”.

NOTICE: If you encounter a limit error message, try using a different app. This issue occurs due to high demand for attestation requests from many users.

After requesting an attestation, expect the following outcomes:

Basic Integrity: ✅ Passed
Device Integrity: ✅ Passed
Strong Integrity: ❌ Not Passed
Virtual Integrity: ❌ Not Passed (applies only to emulators)

Learn more about these verdicts in this post: https://xdaforums.com/t/info-play-integrity-api-replacement-for-safetynet.4479337/

WARNING: It is not theoretically possible to obtain STRONG_INTEGRITY on devices with an unlocked bootloader, but there are some exploits that allow you to obtain it in an unconventional way. In many cases, just a Locked Bootloader Spoof attestation is enough, eliminating the need for STRONG. If you are using a leaked Keybox, there is a huge risk that it will be revoked within a few days.

chiteroman tribute’s

Be happy not because the original project is over, but because it happened. A living form of community resistance and as a developer to bring the best possible to rooted users. Many complain, few do, but we thank Marcos (chiteroman) for his efforts and the remnants of a dev who is very good at what he does. Thank you Marcos for your contribution to the Android community.

Acknowledgments

• PlayIntegrityFIX (Site is down) by chiteroman author of original PIF module.
• kdrag0n & Displax for the original idea.
• osm0sis for his original autopif2.sh script, and backslashxx & KOWX712 for improving it (action.sh).
• Update Security Patch by Papacuz
• TrickyStore by 5ec1cff
• PlayIntegrityFix (Fork) by KOW

Changelog

NOTE: This update aims to improve the module’s infrastructure and ensure future stable updates.

• Updated Fingerprint;
• New Keybox (only for DEVICE_INTEGRITY);
• Added Google Services Framework to the target.txt list;
• Now the module detects if your device is running Android 14 or higher and asks whether you want to apply SpoofVendingSdk;
• Improvements to the organization and structure of the module
• The module now supports “OTA” updates via your root solution (Magisk, APatch, KernelSU/Next).