diff --git a/README.md b/README.md index 5e65e53..aabd7a7 100644 --- a/README.md +++ b/README.md @@ -128,9 +128,9 @@ The advanced spoofing options add granular control over what exactly gets spoofe - The "spoofBuild" entry (default 1) controls spoofing the Build Fields from the fingerprint; the "spoofProps" entry (default 1) controls spoofing the System Properties from the fingerprint; the "spoofProvider" entry (default 1) controls spoofing the Keystore Provider, and the "spoofSignature" entry (default 0) controls spoofing the ROM Signature. -- For spoofing locked bootloader and attempting to pass Play Integrity STRONG verdict I recommend using my [Tricky Store v1.0.3-mod](https://github.com/osm0sis/TrickyStore) fork builds, though the last [official](https://github.com/5ec1cff/TrickyStore) build with spoof_build_vars disabled (i.e. file deleted) will also work. +- For spoofing locked bootloader and attempting to pass Play Integrity STRONG verdict I only recommend using the latest official [Tricky Store](https://github.com/5ec1cff/TrickyStore) build. -- Note: Using Tricky Store to achieve STRONG integrity (with an unrevoked hardware keybox.xml) requires the Advanced Settings "spoofProps" and "spoofProvider" disabled, but to achieve DEVICE integrity (with Tricky Store default AOSP software keybox.xml or a revoked keybox.xml) requires at least "spoofProps" enabled, and some fingerprints may also require "spoofProvider". More known working private fingerprints can achieve DEVICE integrity using these Advanced Settings in conjunction with Tricky Store than is possible with Tricky Store alone since they require fingerprint props spoofing. +- Note: Using Tricky Store to achieve STRONG integrity (with an unrevoked hardware keybox.xml) requires the Advanced Settings "spoofProps" and "spoofProvider" disabled, but to achieve DEVICE integrity (with Tricky Store default AOSP software keybox.xml or a revoked keybox.xml) requires at least "spoofProps" enabled, and some fingerprints may also require "spoofProvider". More known working private fingerprints can achieve DEVICE integrity using these Advanced Settings in conjunction with Tricky Store than was possible with Tricky Store alone since they require fingerprint props spoofing.