mirrors/PlayIntegrityFix
1
0
Fork 0
mirror of https://github.com/chiteroman/PlayIntegrityFix.git synced 2025-01-19 11:32:39 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #98 from osm0sis/patch-1

Browse Source 
README fixes/improvements (main)
This commit is contained in:
Marcos 2023-11-28 10:32:03 +01:00 committed by GitHub
commit fc6fb5e83a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 23 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

53
README.md
View File

@ -1,9 +1,8 @@
# Play Integrity Fix # Play Integrity Fix
A Zygisk module which fix "ctsProfileMatch" (SafetyNet) and "MEETS_DEVICE_INTEGRITY" (Play A Zygisk module which fixes "ctsProfileMatch" (SafetyNet) and "MEETS_DEVICE_INTEGRITY" (Play Integrity).
Integrity).
To use this module you must have one of this: To use this module you must have one of the following:
- Magisk with Zygisk enabled. - Magisk with Zygisk enabled.
- KernelSU with [ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext) module installed. - KernelSU with [ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext) module installed.
@ -24,41 +23,35 @@ https://t.me/playintegrityfix
## About module ## About module
It injects a classes.dex file to modify few fields in android.os.Build class. Also, in native code It injects a classes.dex file to modify a few fields in the android.os.Build class. Also, it creates a hook in the native code to modify system properties. These are spoofed only to Google Play Services' DroidGuard (SafetyNet/Play Integrity) service.
it creates a hook to modify system properties.
The purpose of the module is to avoid a hardware attestation. The purpose of the module is to avoid a hardware attestation.
## Failing BASIC verdict
If you are failing basicIntegrity (SafetyNet) or MEETS_BASIC_INTEGRITY (Play Integrity) something is
wrong in your setup. My recommended steps in order to find the problem:
- Disable all modules except mine.
- Check your SELinux (must be enforced).
Some modules which modify system can trigger DroidGuard detection, never hook GMS processes.
## Certify Play Store and fix Google Wallet
Follow this steps:
- Flash my module in Magisk/KernelSU (if you already have my module, just ignore this step).
- Clear Google Wallet cache (if you have it).
- Clear Google Play Store cache and data.
- 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
## Troubleshooting ## Troubleshooting
### Fails to meet device integrity (KernelSU) ### Failing BASIC verdict
If you are failing basicIntegrity (SafetyNet) or MEETS_BASIC_INTEGRITY (Play Integrity) something is wrong in your setup. Recommended steps in order to find the problem:
- Disable all modules except this one
Some modules which modify system can trigger DroidGuard detection, never hook GMS processes.
### Failing DEVICE verdict (on KernelSU)
- Disable ZygiskNext - Disable ZygiskNext
- Reboot - Reboot
- Enable ZygiskNext - Enable ZygiskNext
### Passes device integrity, but fails in Wallet (even after clearing cache) ### Play Protect/Store Certification and Google Wallet Tap To Pay Setup Security Requirements
- Remove all data from Google Play Services Follow these steps:
- Flash the module in Magisk/KernelSU
- Clear Google Wallet cache (if you have it)
- Clear Google Play Store cache and data
- 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
<details> <details>
<summary>Guide</summary> <summary>Guide</summary>
@ -68,9 +61,9 @@ Follow this steps:
</details> </details>
## Read module logs ### Read module logs
You can read module logs using this command: You can read module logs using this command directly after boot:
``` ```
adb shell "logcat | grep 'PIF'" adb shell "logcat | grep 'PIF'"