Requirements

Please make sure you have the following modules installed before using Integrity Box:

1. • Official Tricky Store or TEE Simulator (use any one)
2. • Zygisk Next or ReZygisk (use any one)

FAQ

• What is IntegrityBox?
  A complete Play Integrity compatibility and system-signal management toolkit.

• Who should use IntegrityBox?
  Rooted users and custom ROM users who care about Play Integrity reliability.

• Why was IntegrityBox created?
  Honestly? It started because so many people were selling keyboxes and I thought, “this is bad, everyone should have access to this for free.” So I made a tool that just gives you keyboxes without paying a cent. Then, well… I kept adding stuff. I kept improving things, fixing bugs, adding new ways to spoof, hide, clean, and optimize. And before I knew it… it turned into a beast of a module, probably the most powerful Play Integrity Fix anyone’s ever seen. It has so many features now that even I sometimes forget half of them 😭. But yeah, that’s the story: started small, got greedy with features, and now it’s the one-stop solution for anyone who wants STRONG or DEVICE integrity without the headaches. Just flash & forget, no need to do anything manually.

• Does IntegrityBox replace Play Integrity Fix/Fork module?
  Yes! Starting from v28, PIF is fully integrated into IntegrityBox. The module ID was changed to playintegrityfix to avoid conflicts, because honestly, using both at the same time doesn’t make sense. IntegrityBox now handles everything PIF did, plus all the extra features I’ve added along the way

• Does IntegrityBox improve compatibility with banking apps
  Yes.

• Does it support DEVICE and STRONG integrity?
  Yes, make sure you have installed tricky store or TEE simulator module.

• Is IntegrityBox safe to use?
  Yes.

• Does it modify user data?
  No.

• Does it modify installed apps?
  No.

• Does it run constantly in the background?
  No.

• Is it lightweight?
  Yes.

• Does it increase CPU usage?
  No, it may reduce it by optimizing targets.

• Does it drain battery?
  No.

• Is everything configurable?
  Yes.

• Can features be disabled individually?
  Yes.

• Is there a global safety option?
  Yes, the Kill Switch.

• What does the Kill Switch do?
  Disables all experimental features.

• Can I recover easily if something breaks?
  Yes.

• Is it safe to uninstall?
  Yes.

• Does IntegrityBox collect any data?
  No.

• Does it include telemetry or tracking?
  No.

• Are any network connections required?
  No (except optional downloads).

• Are downloads verified?
  Yes, using hash verification.

• Does it automatically manage target.txt?
  Yes.

• Does it reduce unnecessary Play Services load?
  Yes.

• Does it handle keybox management?
  Yes.

• Does it support multiple keybox injections?
  Yes.

• Does it help with “Device not certified” issues?
  Yes.

• Does it work on all ROMs?
  It works best on clean, enforcing AOSP-based ROMs.

• Is SELinux enforcing recommended?
  Yes.

• Does it support Pixel spoofing?
  Yes.

• Can fingerprints be customized?
  Yes.

• Does it handle ROM-specific spoofing conflicts?
  Yes.

• Is this module actively maintained?
  Yes.

• Is it beginner-friendly?
  Yes, with built-in guidance.

• Is it suitable for advanced users?
  Yes.

• Should I reboot after changes?
  Only if you see a popup saying "Reboot to apply changes".

• Should I reboot after flashing?
  Yes.

• Where should issues be reported?
  Through the WebUI report option.

Module Features

This module provides a wide range of tools designed to improve compatibility, integrity results, and overall system cleanliness. All features are optional and fully configurable.

Core Utilities

• Built-in assistant to help answer common questions and guide setup
• Option downloads recommended tools from their official release sources with hash verification
• Detects flagged, suspicious, or spoofed applications
• Fixes “Device not certified” issue in playstore
• Terminates GMS Vending process when required

Spoofing & Integrity Enhancements

• Spoofs Android and boot security patch levels
• Spoofs ROM release keys and build tags
• Spoofs LineageOS-specific property detection
• Spoofs debug fingerprint detection
• Supports custom pixel beta fingerprint configuration
• Disables inbuilt PIF spoofing on various custom ROMs when needed
• Fixes abnormal or invalid boot hash values

System & Environment Masking

• Spoofs SELinux status
• Spoofs storage encryption state
• Spoofs custom recovery detection
• Hides PIF hook detection
• Prevents detection of debug or modified system states

Keybox & TEE Management

• Updates and maintains a valid keybox.xml
• Supports multiple keybox injections via TEE Simulator
• Automatically updates target.txt based on current TEE status
• Blacklists unnecessary packages from target.txt (this reduces cpu usage)

Log & Trace Cleanup

• Removes logs generated during GApps installation
• Removes logs generated by KSU / AP / Magisk modules

Additional Controls

• Disables EU injector by default
• Spoofs storage-related and ROM-specific identifiers
• Spoofs debug-related signals
• [Deprecated] Switch Shamiko & NoHello modes

Many more features exist, but these are the most notable ones.

(Honestly, I got tired writing them 😭)

About Module Settings

• Kill Switch : Enable this & reboot your device if you face any issue after flashing integrity box, this will disable all experimental settings.
• Debug Fingerprint : cleans debug tag from fingerprint to bypass custom rom detection and pass play integrity with stock fingerprint
• Debug Build : spoofs developement build as user
• Build Tag : spoofs build tag to bypass custom rom detection
• Storage Encryption : spoofs device storage as encrypted to fool banking apps
• Spoof Custom Recovery : spoofs custom recovery folder to bypass root detection
• Get Recommended Modules : the most easiest and trusted way to download modules which are recommended to use with IntegrityBox
• No Redirect : you won't be redirected to release source on installation

About Module Description

• 🟢🟢🟢 means the current keybox can pass STRONG integrity
• 🟢🟢🔴 means the current keybox can pass DEVICE integrity
• 🔴🔴🔴 means the current keybox is REVOKED and cannot pass play integrity

Common Failure Reasons

Play Integrity may fail if any of the following conditions are present:

• SELinux is set to permissive
• Higher Play Store version (higher than 40.xx)
• Conflicting Magisk / KernelSU / LSPosed modules
• Revoked or invalid keybox
• Banned fingerprint
• ROM inbuilt GMS spoofing is enabled (create /sdcard/zygisk & flash IntegrityBox if you want to use ROM's inbuilt spoofing with IntegrityBox)
• ROM inbuilt Play Store spoofing is enabled
• Root access is visible or not properly hidden
• IntegrityBox is not updated to the latest version
• Tricky Store is out of sync and requires reflashing

Ensure all requirements are met and recheck this list before reporting an issue.

About WEB UI Dashboard

• Profile : Your current PlayIntegrity Profile
• Vending : Your current PlayStore version
• Lineage : Tells whether any lineageos prop exists or not
• Spoofing : Tell whether you're using ROM's inbuilt GMS spoofing or not
• Spoof : The name of pixel device, your playstore spoofed to!
• Patch : Your Android, Vendor security patch date
• SELinux : Your ROM's selinux status. It should not be PERMISSIVE
• Target : Number of apps in tricky store's target.txt file
• Android : Your android version
• Zygote : The zygisk implementation you are using

Credit & Acknowledgement

This project uses code from the following external open-source work:

• ezme-nodebug
• PlayIntegrityFork
• Shamiko (open source late start service)

Report a Problem

• Use Report a bug/issue button in WebUI to report bugs/issues/feedback
• Enable KILL SWITCH toggle from webui > module settings and reboot your device if you're facing any issue after flashing IntegrityBox. This wil disable all experimental features.

Troubleshooting

Google Play Integrity has fully replaced SafetyNet and is now the only attestation system used by modern apps. It checks whether a device looks trustworthy and close to a certified Android environment. Because of this, failures are common on outdated, heavily modified, or poorly configured systems.

Play Integrity checks do not only look at root status. They evaluate multiple system signals, including ROM configuration, SELinux state, system hooks, and how Google services behave at runtime.

To reduce false negatives and improve reliability:

• Use a ROM with SELinux set to enforcing.
  ROMs running in permissive mode are frequently flagged. Even if everything else looks fine, permissive SELinux alone can cause integrity checks to fail.

• Keep Google Play Services and the Play Store fully up to date.
  Play Integrity relies on Play Services to perform attestation. Old or mismatched versions can break communication with Google’s servers and lead to unexpected failures.

• Avoid system-level frameworks that hook core services.
  Xposed, LSPosed, or similar frameworks, especially modules that interact with Google Play Services or the Play Store, are a common cause of integrity failures. Even “harmless” hooks can be detected.

• Minimize invasive system modifications.
  Changes such as aggressive build.prop spoofing, signature spoofing, or runtime code injection increase the likelihood of detection unless they are carefully handled.

• Keep the system as close to stock behavior as possible.
  The closer your device behaves to a certified, unmodified Android environment, the more consistent Play Integrity results will be.

Play Integrity is stricter than older systems and is actively updated by Google. Passing checks today does not guarantee passing them forever, especially on custom ROMs. Treat integrity passing as something that requires maintenance, not a one-time setup.

Preview