2024-03-18 01:34:07 +02:00
|
|
|
Telegram channel:
|
2023-11-21 15:34:33 +02:00
|
|
|
https://t.me/playintegrityfix
|
|
|
|
|
|
2024-02-07 12:54:07 +02:00
|
|
|
Device verdict should pass by default.
|
|
|
|
|
If not, try removing /data/adb/pif.json file.
|
2024-02-07 19:38:21 +02:00
|
|
|
|
2024-03-18 01:34:07 +02:00
|
|
|
Donations:
|
|
|
|
|
https://www.paypal.com/paypalme/chiteroman
|
2024-02-07 19:38:21 +02:00
|
|
|
|
2024-06-21 00:59:48 +03:00
|
|
|
# v16.3
|
2024-03-18 01:34:07 +02:00
|
|
|
|
2024-06-21 00:59:48 +03:00
|
|
|
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 exits 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
|
