WebUI navigation and access
Navigate the module, choose a language, and manage WebUI access.
Where to find it: Guide / Dashboard. Where is each feature?
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.
What to do
- Install the official ZIP through your root manager.
- Open WebUI (Magisk: Action).
- Add authorized key material in Keyboxes.
- Keep optional identity controls off until needed.
Details and limits
KernelSU and APatch open the packaged WebUI directly. Magisk uses Action and the standalone host. The manager native bridge is used; no local TCP port is opened. File input and writes are validated by the service, and a success message follows a completed operation.
Identity appears when an identity feature is enabled on Dashboard. Core Keystore, boot and RKP protection are separate from these optional controls.
- Open Logs & Support, or use Get Support on Dashboard. Enable Debug Logging only if needed, reproduce the issue, then refresh the logs. Viewing, copying and downloading logs still work independently.
- Expand Report Preview. System Summary is a bounded state snapshot, not a log. Copy System Summary copies exactly the displayed summary. The report preview separately shows the recent module logs.
- Press Share Basic Report to create a ZIP with
system-summary.txtandmodule-logs.txtand open Android's sharing picker. Choose the destination yourself. If file sharing is unavailable or fails, the same ZIP is downloaded; cancellation does not trigger a download. Nothing is sent to Telegram automatically. - Refresh Report refreshes both report snapshots. Copy/share stay disabled if preparation fails. Disable Debug Logging when finished.
The summary uses a fixed allowlist: module/version/environment state, interceptor state, aggregate counts, CPU/RSS, feature flags and basic Android/device metadata. It excludes package/keybox names, credentials, server configuration, private keys and identity identifiers. Its schema=2 field names and machine values stay stable across languages. The ZIP also includes real module logs, which may contain device or app names: review both parts before sharing. Report limits are 8 KiB for the summary and 1 MiB for UTF-8 module logs; oversized or unreadable data is rejected. This basic ZIP is separate from the larger emergency .tar.gz report.
Native sharing uses a private Android Shell provider copy (mode 0640) and a temporary read grant. The primary Android user is supported; other users or hosts without a usable provider receive the download fallback. At most 32 basic-report copies are retained; copies older than 24 hours are removed only after a new export succeeds. Downloaded ZIPs are not removed by this cleanup.
WebUI lock compatibility check
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.
When enabling WebUI Lock on Dashboard, complete two Android prompts within two minutes. The first tests an authenticated signature. The helper is then restarted, and the second prompt must sign with the same saved key in the new process. The service saves enrollment only after verifying both proofs. An unsupported device leaves the toggle off and shows the unsupported-device notification. Cancellation or temporary errors also leave it off and allow retry, without claiming permanent incompatibility. This check cannot predict later screen-lock or key changes. An already enabled lock is never disabled by an authentication failure; use owner recovery below if necessary.
Normal WebUI unlocking uses one Android prompt. If its signed result arrives before the WebUI is visible again, it waits up to 10 seconds for the foreground return instead of starting a second prompt. Protected content stays blocked while hidden; cancellation, leaving the page or a return timeout revokes the unused session.
Diagnostics when the module service cannot start
When the native daemon is unavailable, the WebUI shows a service-unavailable gate rather than implying a user-enabled lock. Create emergency report runs the packaged emergency-report.sh using the root manager, without relying on the daemon or unlocking settings. The file path appears on the gate after completion. The report is saved locally and is not automatically shared; inspect it before sharing because it can contain sensitive system logs. If the kernel lacks the required pidfd features, resetting module data will not resolve that incompatibility.
WebUI lock recovery
If the Android screen lock was removed, restore a secure device credential first. Removing or resetting the Android screen lock may invalidate the enrolled key. A failed proof does not disable protection. The device owner can reset only WebUI enrollment with the root commands below, then reopen WebUI, enable the Dashboard lock, and complete both Android authentication prompts to enroll again. Keyboxes, settings and encrypted backups are preserved; WebUI lock remains off until re-enabled.
su -c 'rm /data/adb/cleverestricky/webui_auth.json'
su -c reboot
Reset all module data
If Android verification cannot be opened, Reset module is available beside Unlock. Read the warning for five seconds, then explicitly choose Delete all data and restart. You can cancel before confirming; leaving the WebUI cancels the warning.
This removes the local verification helper for all Android users and schedules deletion of /data/adb/cleverestricky, legacy keyboxes/ and Encrypted/ folders inside the installed module, and loose *.xml / *.cbox files in the module root. The module-owned persistent region override is also cleared. Settings, profiles, keyboxes, encrypted backups in those folders, logs and WebUI enrollment are permanently deleted. Installed module binaries and copies exported elsewhere are kept.
Deletion runs at the next boot before module configuration starts. The module then creates fresh recommended defaults with WebUI Lock off. A pending or failed reset blocks runtime startup until cleanup succeeds. If restart fails, choose Restart now. If preparation cannot be confirmed, retry or restart to finish any pending reset; an error does not prove the request was cancelled.