Boot properties
Boot Properties provides the core userspace property view used for application compatibility.
Where to find it: Dashboard. Where is each feature?
What to do
- Review the core protection status on Dashboard.
- Optional identity switches do not disable the core Keystore, boot or RKP paths.
- Use Logs to investigate a failure.
Details and limits
It reduces exposure of common unlocked, debug, warranty, verified boot, and recovery indicators that applications read through Android properties.
Early boot behavior
Core property updates run before Zygote so later application processes inherit a consistent view. Every property name and every core value is fixed in code.
The core view covers common verified boot state, flash lock, warranty, debug, build type, build tags, secure boot, original equipment manufacturer unlock, and recovery boot mode indicators. This protection is always active while the module is installed and its early boot script can use the property tool.
Optional region identity and template build identity remain separate. Those identity values require Spoof Engine.
Identity compatibility policy
The boot_props_mode setting is retained only for optional template build identity compatibility. It accepts auto, force, or disable.
Automatic mode avoids overlapping build identity providers. Force mode applies configured template build identity even when automatic conflict checks would defer. Disable mode skips optional properties when top-level Identity is off. None of these values disables the core boot property protection path.
Safety and recovery
If the property tool is unavailable, the script logs the condition and leaves the property path unchanged. Unsafe configuration files are ignored or rejected according to the module file safety rules.
The core property view has no WebUI off switch. Identity controls can still be disabled independently without stopping boot protection.
Limits
Userspace properties do not physically relock the bootloader, repair verified boot, rewrite vbmeta, clear hardware fuses, or modify the TEE root of trust.
While top-level Identity is enabled, a saved disable setting is treated as auto; it cannot switch off the required Global Identity dependency. Turn Identity off on Dashboard to disable its property changes. App-specific profile overrides do not enable device-wide properties.
The same ZIP installs the optional CleveresTricky Identity (Optional Zygisk) companion as a separate module. The core module never requires Zygisk. Without an active provider, the companion starts disabled; enable Zygisk and then enable the companion in your root manager for app-specific overrides. Companion disable choices survive updates. Removing the core removes its companion, and a disabled, removed or mismatched core prevents companion hooks.