Browser one-shot installer · preview
Five steps, in order, with one thing to do at a time. The status bar above always tells you what is happening now and what to press next.
Checking this browser…
Nothing selected yet.
Choose your device first, then the build you want. Nothing is downloaded until you ask for it.
Build state: not loaded
Nothing downloaded.
Every file is checked in your browser against the release's published checksums and GitHub's own record of it; if anything does not match, the download stops.
Download state: nothing downloaded
Only needed if this page cannot reach the download mirror (for example you are offline, or a download failed). Download the files for your device from the release page, then select the …-SHA256SUMS files together with the other files. They are checked against the same published checksums — nothing unchecked is ever used.
No device queried yet.
Query the device in fastboot before any install decision. This reads selected getvar values only; it does not send download, flash, erase or a reboot. The model is inferred from the bootloader-reported product, not independently proven silicon identity.
The full serial appears only in the local panel below so you can verify the target; the terminal and the saved log mask it. If the chooser lists nothing, use the unfiltered chooser — these devices report device class 0, so a class-based filter cannot match them. More in the installer notes.
Which of these two is your Echo in? They are different USB modes and only one can work at a time — pressing the wrong one cannot answer.
Echo is in fastboot (first install) — the black bootloader screen saying “fastboot mode”. Press Query device (read-only fastboot) below.
Echo is already in recovery — the TWRP screen with a big “Reboot” button. Press My Echo is already in recovery below. A device in TWRP cannot answer a fastboot query; if you chose it from a fastboot query anyway, the page carries on from recovery with that same device.
Your Echo is identified, so step 3 needs nothing more from you. The two choices above apply only until a device is identified.
Already unlocked and sitting in TWRP? My Echo is already in recovery reads the device's identity from recovery itself, so a reloaded page can still continue. It checks the TWRP version, the board and the LK → Kaeru header chain in expdb (the same checks as the command-line installer) before accepting anything, and it never sends an unlock payload. It works while the build is still downloading. Choose the USB device named “Echo” in Chrome's list — there is no serial to narrow the list with yet, so every check is done from what the device itself reports. If the Echo is already running LibreEcho (Chrome lists it as MT8163-ARM32-ADB), it is not in recovery: choosing it shows that LibreEcho is installed and how to open its setup page. An install that stopped part-way, or already finished, continues from what the Echo itself recorded; nothing whose outcome is unknown is repeated.
Device state: not connected
Query the device to determine whether an Amonet unlock ZIP is needed.
Not needed.
Select the matching amonet-*.zip; the browser verifies the entire archive, extracts the exact LK-build fastbrick member and verifies that member's size and SHA-256. With an approved CORS mirror configured, the fetch button obtains the same pinned ZIP automatically. No archive or payload is sent to USB by these preparation controls.
Payload state: none selected
Blocked until the steps above are done.
Query the device and verify its published build before installation.
Before Install can be pressed:
getvar product, unlock_status and the LK build description are read from the device itself; an unknown target stops the run.expdb must be intact before staging files.The read-only query reads selected getvar values only. It does not send download, flash, erase or a reboot.
The model is inferred from the bootloader-reported product, not independently proven silicon identity.
If the chooser lists nothing, the device is not presenting an identity this page knows. Use the unfiltered chooser — these devices report device class 0, so a class-based filter cannot match them.
Long-form limitations are kept in the installer notes rather than repeated here.