Step 1 of 5 Device & build

Choose your device to see the builds made for it.

LibreEcho

Browser one-shot installer · preview

Install LibreEcho from the browser.

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.

Preview, not a supported install path. Read-only device query tested on hardware; unlock and install writes are not.
Read this before starting

This page runs the install from your browser: it verifies a published release, asks the browser for USB access to the device, and drives the same stages the reviewed host installer drives — fastboot identity, the no-short unlock submission, the recovery-side initial install and a readback receipt after every write.

No Python, no platform tools, no drivers: the browser is the host. Only Chromium-based desktop browsers expose WebUSB.

Image safety is the release publisher's responsibility; this page verifies the published files and hardware target before installation. Hardware-acceptance and recovery-protocol checks still apply. These operations can make a device unrecoverable; the supported route remains the published release and its installation guide.

Browser capability

Checking this browser…

Capability details

Device & build

waiting

Nothing selected yet.

Choose your device first, then the build you want. Nothing is downloaded until you ask for it.

Build state: not loaded

Download & verify

waiting

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

Advanced: use files I already 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.

Connect the device

waiting

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.

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.

Install

waiting

Blocked until the steps above are done.

Query the device and verify its published build before installation.

Before Install can be pressed:

    The 11 install stages and what each one verifies
      • Release — both checksum inventories and the recovery ZIP/manifest are verified against the release API's digests before any write.
      • Bundle — every selected file is hashed in the browser and compared with the release digest.
      • Device — getvar product, unlock_status and the LK build description are read from the device itself; an unknown target stops the run.
      • Unlock — the pinned build-specific payload is checked locally; an unpinned LK build is refused unless the operator ticks “Allow untested LK build”, which sends the archive's default image and says so before the write. fastbrick itself changes early boot-chain storage. A timeout is not accepted as proof of success and is never auto-retried.
      • Recovery — TWRP's ADB serial must match the fastboot serial, and the Kaeru header in expdb must be intact before staging files.
      • Stage — only files that matched the API-anchored normal and TWRP checksum inventories are pushed and re-hashed on the device.
      • Install — the recovery installer's machine-readable receipt is read back after each run; the installer reshapes userdata first when the layout does not match the image contract, and asks for a reboot in between.
      • Verify — after the final reboot the page re-attaches to the running image over USB, checks the same serial came back and that LibreEcho reports ready, then closes the connection and shows how to open setup.
      install progress
        Before you start: what this page can and cannot tell you

        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.

        Report a problem

        This opens a new bug report on GitHub with what you write here and the installer log filled in. Nothing is sent until you check it and press Create on GitHub, which needs a GitHub account.

        The log masks your device serial. MAC addresses, local IP addresses and anything that looks like a password are removed too, but please read the report before you submit it. GitHub rejects prefill links over about 7 kB (the installer keeps them under 6 kB), so in a long report the log — or, if you pasted a lot of text, the description — is shortened to fit, and whatever was cut is copied to your clipboard to paste in.