mirror of https://github.com/chiteroman/PlayIntegrityFix.git synced 2025-04-29 01:22:07 +08:00

Thisisauser6443 b9df941b1b

Better explanation for strong integrity

2025-03-01 17:51:52 +00:00

4.4 KiB

Raw Blame History

Play Integrity Fix

This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation.

NOTE

This module is not made to hide root, nor to avoid detections in other apps. It only serves to pass Device verdict in the Play Integrity tests and certify your device. All issues created to report a non-Google app not working will be closed without notice.

Tutorial

You will need root and Zygisk, so you must choose ONE of this three setups:

Magisk with Zygisk enabled.
KernelSU with ZygiskNext module installed.
APatch with ZygiskNext module installed.

After flashing and reboot your device, you can check PI and SN using these apps:

Play Integrity -> https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck
SafetyNet -> https://play.google.com/store/apps/details?id=rikka.safetynetchecker

NOTE: if you get an error message about a limit, you need to use another app, this is because a lot of users are requesting an attestation.

NOTE: SafetyNet is obsolete, more info here: https://developer.android.com/privacy-and-security/safetynet/deprecation-timeline

Also, if you are using custom rom or custom kernel, be sure that your kernel name isn't blacklisted, you can check it running uname -r command. This is a list of banned strings: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89308909

Verdicts

After requesting an attestation, you should get this result:

MEETS_BASIC_INTEGRITY ✅
MEETS_DEVICE_INTEGRITY ✅
MEETS_STRONG_INTEGRITY ❌
MEETS_VIRTUAL_INTEGRITY ❌ (this is for emulators only)

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

And in SafetyNet you should get this:

basicIntegrity: true
ctsProfileMatch: true
evaluationType: BASIC

A word on passing Strong Integrity

While this module only returns passing verdicts for as far up as MEETS_DEVICE_INTEGRITY (Soon to be only up as far as MEETS_BASIC_INTEGRITY by the new verdict requirements for Android 13 and later), it is possible to achieve a passing verdict for MEETS_STRONG_INTEGRITY by using 5ec1cff's TrickyStore, to spoof a valid certificate chain (Often distributed as a file named keybox.xml and just called a keybox) to your device's Trusted Execution Environment (TEE) module.

However, it must be stressed that a keybox is hard to come by, given that they're leaked (Usually inadvertently) from OEMs and vendors. Even then, they are also often quite quickly revoked, due to a combination of people sending a deluge of server requests (Mostly for flexing their strong verdicts, which they probably didn't need anyway... You know who you are) and Google deploying specialised crawlers for detecting said keyboxes. You'll know you're using a revoked keybox when you're only passing MEETS_BASIC_INTEGRITY, at which point you'll need to find another to return to Strong Integrity, or use the publicly available AOSP keybox/just remove TrickyStore to return to Device Integrity

TL;DR: Until May 2025, you are completely fine only passing up as far as MEETS_DEVICE_INTEGRITY, and unless it is absolutely necessary for your use case(s), you are better off not diving into this rabbit hole