CleveresTricky

CleveresTricky is a KernelSU, APatch, and Magisk module for Android 12-17. It brings Android keystore and attestation compatibility, Keybox/CBOX management, application targeting, optional identity controls, patch-level controls, and privacy tools into one mobile WebUI.

Start with the defaults and enable only the features you actually need.

Official builds and documentation are available from GitLab Releases and GitLab Pages. See our Source Policy for why development access is restricted and Licensing for the GPL, third-party and independent-material distinctions. The module ZIP contains the English LICENSE, LICENSING.md, NOTICE, preserved GPL-3.0-only.txt, and SHA-256 sidecar checksums. Root-level changes can cause boot loops, data loss or device damage; see the no-warranty and liability provisions in LICENSE, without overriding GPL rights.

Dashboard shows a short runtime status. CPU, process RSS and Resource Monitor are in Advanced Details, closed by default. Get Support opens Logs & Support. Device Checks keeps Play Integrity, Wallet, RCS and Security Scanner. Log viewing, copying, downloading and Debug Logging remain in Logs & Support.

In Logs & Support, Share Basic Report bundles System Summary and module logs as a ZIP and opens Android sharing. Copy System Summary copies only the previewed summary. CleveresTech Telegram Group.

What you can do

• Manage, verify, select, and rotate Keybox/CBOX files.
• Use Global Mode or target individual applications with per-app rules.
• Configure optional device/build, attestation, telephony, region, and security patch presentation.
• Protect Remote Key Provisioning flows and reduce supported DRM identifier exposure without pretending to bypass DRM.
• Back up settings, inspect effective state, and collect diagnostics from the WebUI Logs & Support page or by running /data/adb/modules/cleverestricky/emergency-report.sh.

Quick start

1. Download the latest release ZIP from the official Releases page.
2. Install the ZIP from KernelSU, APatch, or Magisk while Android is running.
3. Open the CleveresTricky WebUI from your module manager (on Magisk, from the module Action button).
4. Add only a Keybox or CBOX that you own or are authorized to test.
5. Keep the default setup first, then enable identity, application rules, or privacy options only when needed.

No usable Keybox or private attestation key is bundled with the project.

Supported environment

• Android 12-17 / API 31-37
• ARM64 and x86-64
• KernelSU, APatch, and Magisk

WebUI recovery: The lock screen offers Reset module beside Unlock, with a five-second warning and explicit confirmation before erasing module data and restarting. WebUI lock is tested on the device before it is enabled on KernelSU, APatch or Magisk. A PIN, pattern or password is accepted; a numeric PIN is not required. If secure verification is unsupported, the lock stays off and a localized notification explains the failure. WebUI access and recovery

Kernel requirement: Android 12-17 support describes the Android API level, not every legacy kernel. The runtime requires working pidfd_open and pidfd_send_signal system calls (checked at startup). Older kernels without these features cannot start the supervisor, even on Android 12. If the service is offline, use Create emergency report on the WebUI gate; factory reset cannot add missing kernel support.

Minimum kernel baseline: Linux 5.3 or newer with functional pidfd_open and pidfd_send_signal. The installer rejects older release numbers even when features have been backported. Android 12 GKI commonly uses 5.10, which is recommended; Android API 31 alone does not guarantee kernel compatibility.

Important to know

CleveresTricky improves the local compatibility path, but remote results still depend on the real device, firmware, certification state, Google Play services, server policy, and the data you configure. It cannot guarantee a particular Play Integrity or attestation verdict.

It does not physically relock the bootloader, rewrite verified boot measurements, change the hardware root of trust, modify the modem/baseband, or turn DRM privacy controls into a DRM bypass.

Use only configuration and credentials that you are authorized to use.

Learn more

• Strong Integrity Guide - quick-start guide to passing Google Play Integrity (MEETS_STRONG_INTEGRITY) across Official, AOSP, and Custom ROMs.
• Keybox Manager - Keybox/CBOX loading, verification, selection, and revocation checks.
• Application Scope and Application Rules - choose where features apply.
• Build Identity, Telephony Identity, and Patch Levels - optional identity controls.
• RKP Protection and DRM Privacy - platform compatibility and privacy behavior.
• Backup and Restore - encrypted configuration backup and recovery.
• Security Model and Installer - trust boundaries and installation details.

Need help?

Open Logs & Support to review System Summary and module logs, then use Share Basic Report. For a larger emergency report, run /data/adb/modules/cleverestricky/emergency-report.sh. Review reports before sharing; they may contain device and system information.

See Diagnostics for common problems and troubleshooting steps.

Project

Changelog · Source Policy · Licensing · Contributing · Languages · Donate · Telegram