Play Integrity Fix

New log design in logcat 😅

v16.4 released! Changelog:

- Misc improvements in code
- Remove keybox.xml parsing due DroidGuard detections
- Add BOARD and HARDWARE fields in json

https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v16.4

Not all keyboxes are banned, I still have a working one 😎

A lot of banned certs added, including mine 😢 If you have a valid keybox, Strong still pass because it's cached in their servers. Within 24 hours... RIP ☠️

Updated banned certs! Also, I have removed the code to get the certificates directly from Google servers, sometimes it did not work correctly.

Released v16.3! https://github.com/chiteroman/PlayIntegrityFix/releases/tag/v16.3 Changelog: ``` Google fixed the bug, no more Strong pass with SW keybox 😢 - Improve C++ and Java code - Downgrade first_api_level to 24, so all devices (should) be able to pass Device - Included keybox.xml parsing! You can create /data/adb/keybox.xml to define your own keybox (Strong passing with my private one :D) By default, inside module folder, it exists pif.json and keybox.xml, do NOT delete these files keybox.xml included in the module is SW one Keybox "hack" does NOT work on broken TEE devices, like OnePlus `` `

Found another unbanned keybox :) Seems like OEMs are leaking more keys, interesting 🤔

RIP Strong pass, sailfish fingerprint still works, using v15.9.9 passes Device

Sailfish fingerprint is banned for RCS, so even passing Strong it won't work. But now you have a valid certificate chain, you can use more fingerprints, including newer ones. Also you can use your device fingerprint 😊