From 12b55630fb66c3fdb00cf93df738d5a69e106628 Mon Sep 17 00:00:00 2001 From: Chris Renshaw Date: Thu, 7 Mar 2024 13:52:44 -0400 Subject: [PATCH] README: emphasize the flexibility and futureproofing in the json --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 715fcc6..ea0af2c 100644 --- a/README.md +++ b/README.md @@ -24,6 +24,8 @@ The purpose of the module is to avoid hardware attestation. 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 (/data/adb/modules/playintegrityfix) 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 (none included currently). +Note this is just a template with the current suggested defaults, but with this fork you can include as few or as many android.os.Build class fields and Android system properties as needed to pass DEVICE verdict now and in the future if the enforced checks by Play Integrity change. + As a general rule you can't use values from recent devices due to them only being allowed with full hardware backed attestation. Older formatted custom.pif.json files from cross-forks and previous releases will be automatically migrated to the latest format. Simply ensure the filename is custom.pif.json and place it in the module directory before upgrading.