Skip to content
Snippets Groups Projects
Commit 05bdfd3f authored by chiteroman's avatar chiteroman
Browse files

Update v13

parent 56cbbe82
No related branches found
No related tags found
No related merge requests found
# GOOGLE BANNED AGAIN THE FINGERPRINT, I'M UPDATING THE MODULE. Be patient, I hope I can fix it.
# Play Integrity Fix # Play Integrity Fix
A Zygisk module which fix "ctsProfileMatch" (SafetyNet) and "MEETS_DEVICE_INTEGRITY" (Play Integrity). A Zygisk module which fix "ctsProfileMatch" (SafetyNet) and "MEETS_DEVICE_INTEGRITY" (Play Integrity).
...@@ -42,16 +40,11 @@ adb shell "logcat | grep 'PIF'" ...@@ -42,16 +40,11 @@ adb shell "logcat | grep 'PIF'"
``` ```
## Can this module pass MEETS_STRONG_INTEGRITY? ## Can this module pass MEETS_STRONG_INTEGRITY?
No NO
## SafetyNet is obsolete ## Play Integrity is now our problem, SafetyNet is deprecated
You can read more info here: [click me](https://xdaforums.com/t/info-play-integrity-api-replacement-for-safetynet.4479337/) You can read more info here: [click me](https://xdaforums.com/t/info-play-integrity-api-replacement-for-safetynet.4479337/)
## Current Issues
It doesn't work in Xiaomi.eu custom ROMs due their fix implementation.
Their devs are already working on it: [click me](https://xiaomi.eu/community/threads/google-wallet-stopped-working-device-doesnt-meet-security-requirements.70444/post-704331).
If Xiaomi.eu devs drop support for your device and this module doesn't work you must change the ROM if you want to pass DEVICE verdict.
## Make FCM Push back to work after cleared GSF data ## Make FCM Push back to work after cleared GSF data
Once you cleared GSF (Google Service Framework, com.google.android.gsf) data, a new DeviceID of Google Service Framework will be generated. So all the FCM tokens that have registered in the server of Apps will no longer work (it will point to your old DeviceID). You can follow these steps to make the Apps to generate a new FCM token. Once you cleared GSF (Google Service Framework, com.google.android.gsf) data, a new DeviceID of Google Service Framework will be generated. So all the FCM tokens that have registered in the server of Apps will no longer work (it will point to your old DeviceID). You can follow these steps to make the Apps to generate a new FCM token.
...@@ -82,6 +75,3 @@ find . -type f -name '*gms.appid-no-backup' -delete ...@@ -82,6 +75,3 @@ find . -type f -name '*gms.appid-no-backup' -delete
5. Reboot your device. 5. Reboot your device.
6. It is better to launch the apps that receive FCM push one time, to make sure it generates a new FCM token and registers with the server. 6. It is better to launch the apps that receive FCM push one time, to make sure it generates a new FCM token and registers with the server.
## Thanks to
- [Dobby](https://github.com/jmpews/Dobby)
# v12.3 # v13
Fixed crashing issues in recent launched devices. Device verdict is green again x2.
This should be the final build until Google "unfix" (again) the module. If you are using xiaomi.eu expect to fail all tests.
If you want to report a crash report or any other issue, please, always provide logs. \ No newline at end of file
Check README.md to know how to certify Play Store and fix Google Wallet.
\ No newline at end of file
{ {
"version": "v12.3", "version": "v13.0",
"versionCode": 123, "versionCode": 130,
"zipUrl": "https://github.com/chiteroman/PlayIntegrityFix/releases/download/v12.3/PlayIntegrityFix_v12.3.zip", "zipUrl": "https://github.com/chiteroman/PlayIntegrityFix/releases/download/v13/PlayIntegrityFix_v13.zip",
"changelog": "https://raw.githubusercontent.com/chiteroman/PlayIntegrityFix/main/changelog.md" "changelog": "https://raw.githubusercontent.com/chiteroman/PlayIntegrityFix/main/changelog.md"
} }
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment