Device and build identity
Build Identity applies a complete device template to the fingerprint and supported app visible Build fields.
Where to find it: Identity. Where is each feature?
What to do
- Enable Build identity on Dashboard.
- Choose a template or run Auto Identity in Identity, save the choice, and reboot.
- Security Patch is configured separately.
Details and limits
It is optional and requires Identity Engine. Early-boot system property changes require a device reboot. With Build system properties disabled, the working Zygisk Identity companion applies Java Build fields to new target app processes.
Build fields without system property changes
On Dashboard, enable Identity Engine and Build Identity. The Build system properties sub-toggle appears directly below Build Identity. Turn it off to keep Build-derived Android properties unchanged while the selected template still changes app-visible Java Build fields through the working CleveresTricky Zygisk Identity companion. The companion must be loaded in the target process; an installed provider alone does not prove this.
Attestation Identity, keybox selection, Security Patch, Region Identity and Custom properties remain independent. Explicit Region or Custom property overrides can still change their selected properties. Existing configurations keep Build system properties enabled by default. Use this optional control to limit which identity layer CleveresTricky changes, rather than as a required payment setting.
Turning it off restores the saved live Build property baseline when available. Reboot if the result requires it, and restart target apps to load the new Java fields. In app-scoped mode, check the intended app/profile assignments, including any service process used by the app.
Payment compatibility
A successful integrity test does not establish that Google Wallet will accept a payment. Check Wallet's own payment setup and error message: NFC, the default payment app, screen-lock verification, a supported and verified card, Play Protect certification and device security requirements are separate conditions. Google does not support contactless payments on rooted devices, custom ROMs or devices with unlocked bootloaders. No Identity toggle guarantees approval. See Google Wallet troubleshooting and Play Integrity verdicts.
Template content
A template contains manufacturer, model, brand, product, device, fingerprint, Android release, build identifier, incremental value, build type, build tags, and security patch information. Built in templates can be extended through a validated local template file.
Selecting a template writes the complete supported identity into spoof_build_vars. Arbitrary Android properties are rejected. This keeps the feature bounded to fields the module actually consumes.
Auto Identity
Auto Identity is an optional helper for Custom ROM users. It reads Google public Android developer and Flash Tool metadata, selects a current Pixel beta device, resolves the matching canary build identity, and saves the resulting build fields locally.
The helper is intended for Play Integrity compatibility testing on Custom ROMs. It does not enable Spoof Engine automatically. Enable the identity engine and reboot only when you want the saved build identity exposed.
Auto Identity updates the build identity snapshot. Component patch policy is configured separately under Identity > Security Patch.
Synchronized activation
The early boot script applies the active identity snapshot before Zygote captures Build fields only when Identity Engine, Build Identity and Build system properties are enabled. The service loads the same snapshot for identity substitution decisions.
When Refresh Identity on Boot is enabled, the running snapshot is never rotated after early boot. The service prepares a separate randomized snapshot with atomic protected storage. The next early boot phase promotes that prepared snapshot before applying identity properties. Build fields and attestation identity values therefore use one synchronized identity for the entire boot.
Manual identity edits discard an older prepared snapshot so a stale random value cannot replace a newer user choice.
Compatibility policy
Automatic mode detects common overlapping fingerprint providers and leaves optional Build properties untouched. Core boot and Keystore protection continue operating. Force mode is available for users who intentionally want CleveresTricky to own the build identity property layer.
Limits
Build Identity changes supported userspace views. It does not change the real hardware model, firmware, kernel, verified boot measurement, or hardware trust root.
Feature separation
Device and Build Identity is an optional feature with its own lifecycle. It covers supported Build fields such as manufacturer, brand, model, product, device, fingerprint, build identifier, incremental value, release, type, and tags. Values captured during early boot still require a reboot when changed.
Security Patch is not part of Device and Build Identity. Build Identity can be enabled while System, Vendor, and Boot patch authorizations remain genuine. Security Patch can also be enabled while Build Identity is disabled. Region, Telephony, Attestation Identity, and Identity Refresh are resolved separately.