You've already forked PlayIntegrityFork
mirror of
https://github.com/osm0sis/PlayIntegrityFork.git
synced 2025-09-06 06:37:06 +00:00
README: add WearOS caveat, new example template, badges (thanks @zgfg)
This commit is contained in:
11
README.md
11
README.md
@@ -1,6 +1,11 @@
|
||||
# Play Integrity Fork
|
||||
*PIF forked to bring back the custom.pif.json restore feature and develop more methodically*
|
||||
|
||||
[](https://github.com/osm0sis/PlayIntegrityFork/releases/latest)
|
||||
[](https://github.com/osm0sis/PlayIntegrityFork/releases)
|
||||
[](https://github.com/osm0sis/PlayIntegrityFork/releases/latest)
|
||||
[](https://github.com/osm0sis/PlayIntegrityFork/releases)
|
||||
|
||||
A Zygisk module which fixes "ctsProfileMatch" (SafetyNet) and "MEETS_DEVICE_INTEGRITY" (Play Integrity).
|
||||
|
||||
To use this module you must have one of the following:
|
||||
@@ -16,9 +21,9 @@ The purpose of the module is to avoid hardware attestation.
|
||||
|
||||
## About 'custom.pif.json' file
|
||||
|
||||
You can create this file in the module directory to spoof custom values to the GMS unstable process. It will be used instead of any included pif.json.
|
||||
You can fill out the included template [example.pif.json](https://raw.githubusercontent.com/osm0sis/PlayIntegrityFork/main/module/example.pif.json) from the module directory then rename it to custom.pif.json to spoof custom values to the GMS unstable process. It will be used instead of any included pif.json.
|
||||
|
||||
You can't use values from recent devices due them triggering hardware backed attestation.
|
||||
You can't use values from recent devices due them triggering full hardware backed attestation.
|
||||
|
||||
<details>
|
||||
<summary>Resources</summary>
|
||||
@@ -55,6 +60,8 @@ Follow these steps:
|
||||
- Clear Google Play Services (com.google.android.gms) cache and data (Optionally skip clearing data and wait some time, ~24h, for it to resolve on its own)
|
||||
- Reboot
|
||||
|
||||
Note clearing Google Play Services app ***data*** will then require you to reset any WearOS devices paired to your device.
|
||||
|
||||
### Read module logs
|
||||
|
||||
You can read module logs using this command directly after boot:
|
||||
|
||||
Reference in New Issue
Block a user