### Verify Module Installation

Source: https://context7.com/5ec1cff/trickystore/llms.txt

Confirm the module is active after flashing and rebooting.

```bash
# After flashing the module, reboot the device
# The module will be active at /data/adb/tricky_store/
```

--------------------------------

### List Configuration Files

Source: https://context7.com/5ec1cff/trickystore/llms.txt

Verify the contents of the configuration directory.

```bash
# List all Tricky Store configuration files
ls -la /data/adb/tricky_store/

# Expected structure:
```

--------------------------------

### XML Keybox Configuration for Tricky Store

Source: https://github.com/5ec1cff/trickystore/blob/release/README.md

Defines the structure for a keybox.xml file used to configure hardware keys and certificates for Tricky Store. Ensure the private key and certificate chain are in PEM format.

```xml
<?xml version="1.0"?>
<AndroidAttestation>
    <NumberOfKeyboxes>1</NumberOfKeyboxes>
    <Keybox DeviceID="...">
        <Key algorithm="ecdsa|rsa">
            <PrivateKey format="pem">
-----BEGIN EC PRIVATE KEY-----
...
-----END EC PRIVATE KEY-----
            </PrivateKey>
            <CertificateChain>
                <NumberOfCertificates>...</NumberOfCertificates>
                    <Certificate format="pem">
-----BEGIN CERTIFICATE-----
...
-----END CERTIFICATE-----
                    </Certificate>
                ... more certificates
            </CertificateChain>
        </Key>...
    </Keybox>
</AndroidAttestation>
```

--------------------------------

### Configure Target Package Modes

Source: https://context7.com/5ec1cff/trickystore/llms.txt

Specify attestation modes for applications in /data/adb/tricky_store/target.txt using auto, leaf hack, or generate modes.

```bash
# /data/adb/tricky_store/target.txt

# Auto mode - automatically selects best method
io.github.vvb2060.keyattestation

# Leaf hack mode - force modify existing leaf certificate
# Use when TEE is working and you want minimal modification
io.github.vvb2060.mahoshojo?

# Generate mode - force full certificate generation
# Use for TEE-broken devices or when leaf hack fails
com.google.android.gms!

# Common targets for Play Integrity
com.google.android.gms!
com.android.vending
```

--------------------------------

### Define Hardware Keybox

Source: https://context7.com/5ec1cff/trickystore/llms.txt

Configure a hardware keybox for attestation by placing an XML file at /data/adb/tricky_store/keybox.xml.

```xml
<?xml version="1.0"?>
<AndroidAttestation>
    <NumberOfKeyboxes>1</NumberOfKeyboxes>
    <Keybox DeviceID="device_id_here">
        <Key algorithm="ecdsa">
            <PrivateKey format="pem">
-----BEGIN EC PRIVATE KEY-----
MHQCAQEEIBYwJkKvCmoD3DoHvP2XoOx7MbQ8MpaXyjYgXmYWnwXOoAcGBSuBBAAK
oUQDQgAEp6Wv0v7xY5Jc5KAC5xNjrPbOMahJyYYfUY8fZBJy8BzjUqXL3SQ9Xgh2
DPVwNPVzMvfQ0P9XQfHqEUoGKi0PEQ==
-----END EC PRIVATE KEY-----
            </PrivateKey>
            <CertificateChain>
                <NumberOfCertificates>3</NumberOfCertificates>
                <Certificate format="pem">
-----BEGIN CERTIFICATE-----
MIIBkTCB+wIJAKHBfpEgcMFvMAoGCCqGSM49BAMCMBkxFzAVBgNVBAMMDkF0dGVz
dGF0aW9uIENBMB4XDTI0MDEwMTAwMDAwMFoXDTM0MDEwMTAwMDAwMFowGTEXMBUG
A1UEAwwOQXR0ZXN0YXRpb24gQ0EwWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAQm
... certificate content ...
-----END CERTIFICATE-----
                </Certificate>
                <!-- Additional certificates in chain -->
            </CertificateChain>
        </Key>
    </Keybox>
</AndroidAttestation>
```

--------------------------------

### Configure TEE-Broken Devices

Source: https://context7.com/5ec1cff/trickystore/llms.txt

Force generate mode for devices with broken TEE to handle key operations in software.

```bash
# /data/adb/tricky_store/target.txt

# Force generate mode for all Google services on TEE-broken device
com.google.android.gms!
com.android.vending!

# Force generate mode for banking apps
com.bank.app!

# Mix modes - use auto for less sensitive apps
io.github.vvb2060.keyattestation
```

--------------------------------

### Simple Security Patch Level Configuration

Source: https://github.com/5ec1cff/trickystore/blob/release/README.md

Sets a uniform security patch level for OS, vendor, and boot partitions. This file should be placed at /data/adb/tricky_store/security_patch.txt.

```text
# Hack os/vendor/boot security patch level
20241101
```

--------------------------------

### Manage Tricky Store Target Configuration

Source: https://context7.com/5ec1cff/trickystore/llms.txt

Commands to view and modify the list of target applications for integrity bypass.

```bash
cat /data/adb/tricky_store/target.txt
```

```bash
echo "com.google.android.gms!" >> /data/adb/tricky_store/target.txt
```

--------------------------------

### Target Packages Configuration for Tricky Store

Source: https://github.com/5ec1cff/trickystore/blob/release/README.md

Specifies target packages for Tricky Store's key attestation modification. Use '!' to force certificate generation mode and '?' to force leaf hack mode for specific packages.

```text
# target.txt
# use auto mode for KeyAttestation App
io.github.vvb2060.keyattestation
# always use leaf hack mode 
io.github.vvb2060.mahoshojo?
# always use certificate generating mode for gms
com.google.android.gms!
```

--------------------------------

### Advanced Security Patch Level Configuration

Source: https://github.com/5ec1cff/trickystore/blob/release/README.md

Allows granular control over security patch levels for OS, boot, and vendor partitions. Supports 'prop' to sync with system properties or 'no' to disable patching for a partition.

```text
# os security patch level is 202411
system=202411
# do not hack boot patch level
boot=no
# vendor patch level is 20241101 (another format)
vendor=2024-11-01
# default value
# all=20241101
# keep consistent with system prop
# system=prop
```

--------------------------------

### Customize Security Patch Level

Source: https://context7.com/5ec1cff/trickystore/llms.txt

Override reported security patch levels in /data/adb/tricky_store/security_patch.txt using simple or advanced formats.

```bash
# Simple format - applies same patch level to os/vendor/boot
# /data/adb/tricky_store/security_patch.txt
20241101
```

```bash
# Advanced format - customize each component separately
# /data/adb/tricky_store/security_patch.txt

# Set system/os security patch level
system=202411

# Do not modify boot patch level
boot=no

# Set vendor patch level (alternate date format)
vendor=2024-11-01

# Default value for all components (if not specified individually)
# all=20241101

# Keep system patch consistent with actual system property
# system=prop
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.