br0kenpixel/TrickyStore
1
0
Fork 0
mirror of https://github.com/5ec1cff/TrickyStore.git synced 2025-09-06 06:37:07 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Chris Renshaw
2024-07-23 12:19:00 -03:00
committed by Wang Han
parent f3a150078f
commit 8f6c2b5dc8
1 changed files with 6 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -5,8 +5,8 @@ A trick of keystore. **Android 12 or above is required**.
## Usage ## Usage
1. Flash this module and reboot. 1. Flash this module and reboot.
2. Put keybox.xml to /data/adb/tricky_store/keybox.xml . 2. Put keybox.xml at `/data/adb/tricky_store/keybox.xml`.
3. Put target packages to /data/adb/tricky_store/target.txt (Optional). 3. Customize target packages at `/data/adb/tricky_store/target.txt` (Optional).
4. Enjoy! 4. Enjoy!
## keybox.xml ## keybox.xml
@@ -42,12 +42,9 @@ format:
> **Zygisk (or Zygisk Next) is needed for this feature to work.** > **Zygisk (or Zygisk Next) is needed for this feature to work.**
If you can not pass strong integrity, you can try to enable build vars spoofing If you cannot pass strong integrity, you can try enabling build vars spoofing by creating the file `/data/adb/tricky_store/spoof_build_vars`.
by creating a file `/data/adb/tricky_store/spoof_build_vars`.
After doing that, TrickyStore will automatically generate an example config json Tricky Store will automatically generate example config props inside `/data/adb/tricky_store/spoof_build_vars` on next reboot, then you can manually edit your spoof config.
inside `/data/adb/tricky_store/spoof_build_vars` on next reboot. Then you can manually
edit your spoof config.
Here is an example of spoof config: Here is an example of spoof config:
@@ -68,9 +65,7 @@ SECURITY_PATCH=2017-12-05
## Support TEE broken devices ## Support TEE broken devices
TrickyStore will hack leaf certificate by default. Tricky Store will hack the leaf certificate by default. On TEE broken devices, this will not work because we can't retrieve the leaf certificate from TEE. You can add a `!` after a package name to enable generate certificate support for this package.
On TEE broken devices, this will not work because we can't retrieve leaf certificate from TEE.
You can add a `!` after package name to enable certificate generate support for this package.
For example: For example:
@@ -82,7 +77,7 @@ io.github.vvb2060.keyattestation
com.google.android.gms! com.google.android.gms!
``` ```
## Known issue ## Known issues
- App Attest Key is not supported. - App Attest Key is not supported.
- StrongBox is not supported. - StrongBox is not supported.
@@ -94,4 +89,3 @@ com.google.android.gms!
- [BootloaderSpoofer](https://github.com/chiteroman/BootloaderSpoofer) - [BootloaderSpoofer](https://github.com/chiteroman/BootloaderSpoofer)
- [KeystoreInjection](https://github.com/aviraxp/Zygisk-KeystoreInjection) - [KeystoreInjection](https://github.com/aviraxp/Zygisk-KeystoreInjection)
- [LSPosed](https://github.com/LSPosed/LSPosed) - [LSPosed](https://github.com/LSPosed/LSPosed)
- [Glaze](https://github.com/stephenberry/glaze)