DEVICE STATUS
Launch locally for USB operations.
This hosted interface shows the application workspace. Device detection, firmware inspection and writes run on your computer.
Download full application Open local runtime ↗ Setup guideSOVEREIGN DEVICE OPERATIONSFlash. Recover.
Flash. Recover.
Customize.
A modern, secure, and open Android flashing toolkit
for every device, built for freedom.
● ●
◼
LOCAL◼
CONTROL
BOOTLOADER STATUS
Unknown
Connect a device to detect statusBATTERY LEVEL
—%
Minimum verified charge: 60%
Firmware workspace
01 / INSPECT & PLANFIRMWARE INSPECTOR
Verify before you write.
Enter the complete archive hash from an independently trusted publisher.
- Target Device
- Unknown
- File Name
- —
- File Size
- —
- SHA-256
- Required
- Manifest
- Not inspected
- Signature
- Not verified
Operation pipeline
IDLE1Inspect2Verify device3Review plan4Execute5Evidence
Awaiting a verified package and device.
Device Verification
Check all conditions
Confirmations
A verified plan is required.
Connected devices
USB discovery comes directly from the local ADB and Fastboot tools.
Reboot manager
Applies to the selected device. Unlocking and relocking are deliberately outside this guided workflow.
Operation evidence
Signed execution records preserve writes, command outputs and failures. A signature proves record integrity, not successful device boot.
Verify an exported record
Runtime settings
Configuration and capabilities reported by the local runtime.
Diagnostics
Operation policy
Writes require DH_FLASH_ENABLE_EXECUTION=1 when starting the runtime. Firmware trust is configured through independently verified publisher keys on this computer. The browser cannot disable verification or add trusted publishers.
Available capabilities
Set up your workstation.
1. Install platform tools
Install Android SDK Platform-Tools on the computer physically connected to your device. Enable USB debugging and accept the device authorization prompt.
2. Trust your firmware publisher
Place the independently verified 32-byte Ed25519 public key in ~/.dh-flash/trusted-keys/KEY_ID.pub. A package includes manifest.json, manifest.sig and raw partition images. Ordinary factory ZIPs, Odin TARs, payloads and sparse images require dedicated adapters and are blocked.
3. Inspect and review
Supply the publisher archive SHA-256, inspect the signed package, select the device and build a plan. This release requires bootloader Fastboot, confirmed unlock, ≥60% reported battery, exact product and bootloader revision, and sufficient partition sizes.
4. Enable writes deliberately
The runtime defaults to inspection mode. Start with DH_FLASH_ENABLE_EXECUTION=1 to enable approved writes. Plans expire after five minutes; approvals after one minute. No automatic wipe, unlock, relock or reboot follows flashing.
5. Verify the device
Acknowledged writes remain unverified until independent readback or boot qualification. Use the reboot manager only after reviewing the record. Backup, root and OEM-specific recovery are not implemented.
Activity stream
Connecting to local runtime…