Community hardware liberation project

Free the hardware.
Keep the voice.

LibreEcho is building an open operating system for Amazon Echo Gen 2β€”turning capable, locked-down hardware into a useful, hackable platform.

Linux 6.1 development Β· Developer Preview preparation

Release status: LibreEcho is preparing a bounded Developer Preview. Open Beta has not launched, and no public download should be treated as a stable consumer release.

  • MT8163MediaTek platform
  • Gen 2Initial hardware target
  • OpenCode and research
A stylised tall smart speaker with an illuminated open-source ring
AirPlay, now supported
No cloud account needed
Music equalizer built in
Local-first voice control
No subscription, ever
OPEN SOURCE ✦ REPAIRABLE ✦ LOCAL-FIRST ✦ COMMUNITY-LED ✦ HARDWARE REUSE ✦

From black box to open platform.

Statuses separate what is implemented from what is supported; a working component is not automatically a supported feature.

Working under hardening

Boot and recovery

The Linux 6.1 development line has a repeatable boot, recovery and A/B rollback path. Public installation remains gated on release documentation and tester validation.

Working under hardening

Wi-Fi and networking

Association, DHCP and gateway-liveness supervision are implemented. Driver-state recovery and longer-duration acceptance remain active work.

Working under hardening

Bluetooth media

Bluetooth SDP, A2DP sink and AVRCP service paths are implemented. Client compatibility and pairing hardening remain release work.

Working under hardening

Audio and AirPlay

AirPlay playback is hardware-validated through the current PCM path. Stream-start volume precedence remains an open safety investigation.

LibreEcho is active Linux 6.1 development for a specific Echo Gen 2 target β€” not a general-purpose upstream Linux port and not an unrestricted Open Beta.

What is implemented, and what is not promised.

Last reviewed .

Beta-supportedWorking under hardeningExperimental / developer-onlyPlannedUnsupported
LibreEcho feature status as of 15 August 2026
AreaStatusCurrent status
Boot, recovery and A/B slotsWorking under hardeningValidated on the development target; public installation and recovery guides are required before preview.
Wi-Fi association and local networkingWorking under hardeningAssociation and gateway supervision work; prolonged recovery and driver-state issues remain open.
AirPlay playbackWorking under hardeningHardware playback validated; stream-start volume safety is not yet a release claim.
Bluetooth A2DP / AVRCPWorking under hardeningService records and playback path exist; client pairing compatibility is still being hardened.
Wake word, local STT and TTSExperimental / developer-onlyImplemented development service chain; not a supported voice-quality or privacy guarantee.
Assistant provider integrationExperimental / developer-onlyProvider choice controls what leaves the device; see the privacy section before enabling it.
Microphone capture and physical muteExperimental / developer-onlyDo not treat software state or a UI indicator as proof of a hardware-derived privacy boundary.
LED control and Web Control CentreWorking under hardeningLocal UI/API and LED paths are implemented; physical-control integration remains under review.
Signed A/B OTAWorking under hardeningSigned update flow exists; release identity, payload identity and recovery gates remain mandatory.
SSH and Home AssistantPlannedNot required for the bounded Developer Preview and not a current support promise.
Developer Preview warning: only install on hardware you can recover. Do not expose the device control plane to the public Internet, and do not upload owner-local firmware, credentials, serials, MAC addresses or private diagnostics.

Start with the exact target.

Initial development targets the Amazon Echo Gen 2 family on the MT8163 platform. A similar chipset, product name or enclosure does not prove compatibility.

Before downloading

  • Confirm that the device is an Amazon Echo Gen 2, not an Echo Dot, Show or another generation.
  • Record the model and board revision privately; never post the serial or MAC address.
  • Have a known-good USB data cable, a Linux/macOS/Windows host with documented USB tools, and a recovery path.
  • Back up owner-local state and connectivity firmware before any destructive operation.

Other Echo generations and unverified board revisions are unsupported. Hardware compatibility must be proven against the exact board and artifact, not inferred from marketing names.

Support contract

Supported target
Amazon Echo Gen 2 / MT8163 development target.
Supported release state
Bounded Developer Preview preparation; Open Beta has not launched.
Untested
Other Echo, Dot and Show generations; unverified board revisions; unsupported host/cable combinations.
Recovery expectation
Users must retain the ability to restore the original device state before experimenting.
Read installation and recovery guidance

One platform today. More hardware next.

This compatibility matrix separates hardware LibreEcho already runs on from devices with boot access, promising SoC reuse, or entirely new platform work. It is a porting roadmap, not a promise that every listed device will be supported.

βœ… LibreEcho working🟒 Access implemented🟑 Potential β€” supported SoC🟠 Research candidateβšͺ New platform
Show the full hardware compatibility matrix
LibreEcho hardware compatibility and porting matrix
CodenameProductSoCLibreEcho / porting statusAccess / research basis
radar / Puffin platformAmazon Echo 2nd GenMediaTek MT8163Vβœ… LibreEcho working β€” current reference platformLibreEcho-Build
biscuitAmazon Echo Dot 2nd GenMediaTek MT8163V🟒 Access implemented β€” strongest next LibreEcho portAmonet mt8163-biscuit / amonet-koboreru
sonarAmazon Echo Plus 1st GenMediaTek MT8163V🟑 Potential β€” supported SoCamonet-koboreru β€” MT8163 platform
rookAmazon Echo Spot 1st GenMediaTek MT8163V🟒 Access implementedAmonet mt8163-rook / amonet-koboreru
checkersAmazon Echo Show 5 1st GenMediaTek MT8163🟒 Access implemented β€” strong first display-equipped targetAmonet mt8163-checkers / amonet-koboreru
crownAmazon Echo Show 8 1st GenMediaTek MT8163🟒 Access implementedAmonet mt8163-crown / amonet-koboreru
cronosAmazon Echo Show 5 2nd GenMediaTek MT8163🟒 Access implementedAmonet mt8163-cronos / amonet-koboreru
donutAmazon Echo Dot 3rd Gen β€” Rev 1MediaTek MT8516BAAA🟒 Access implemented β€” establishes MT8516 as a viable second LibreEcho SoC familyamonet-koboreru
crumpetAmazon Echo Dot 3rd Gen β€” Rev 2 / refreshMediaTek MT8516BAAA🟒 Access implementedamonet-koboreru
cupcakeAmazon Echo InputMediaTek MT8516BAAA🟒 Access implementedamonet-koboreru
cupcakeAmazon Echo Input PortableMediaTek MT8516 family🟑 Strong potential β€” supported SoC/platform familyamonet-koboreru
lidarAmazon Echo Plus 2nd GenMediaTek MT8516B🟑 Potential β€” supported SoC β€” high-value speaker targetamonet-koboreru β€” MT8516 platform
pascalAmazon Echo 3rd GenMediaTek MT8516🟑 Potential β€” supported SoC β€” high-priority full-size Echo candidateamonet-koboreru β€” MT8516 platform
octaveAmazon Echo Studio β€” 2019MediaTek MT8516 family🟑 Potential β€” supported SoC β€” high-value targetamonet-koboreru β€” MT8516 platform
octaveAmazon Echo Studio β€” 2022 refreshMediaTek MT8516 family🟑 Potential β€” supported SoCamonet-koboreru β€” MT8516 platform
doebriteAmazon Echo Dot with Clock 3rd GenMediaTek MT8516BAAA🟑 Strong potential β€” supported SoC, closely related to donut / crumpetamonet-koboreru β€” MT8516 platform
croissantAmazon Echo FlexMediaTek MT8516BAAA🟑 Potential β€” supported SoCamonet-koboreru β€” MT8516 platform
sapphireAmazon Echo LinkMediaTek MT8516B🟑 Potential β€” supported SoCamonet-koboreru β€” MT8516 platform
kyaniteAmazon Echo Link AmpMediaTek MT8516B🟑 Potential β€” supported SoCamonet-koboreru β€” MT8516 platform
pabloAmazon Echo SubMediaTek MT8516B🟑 Potential β€” supported SoCamonet-koboreru β€” MT8516 platform
douglasAmazon Fire HD 8 7th GenMediaTek MT8163🟒 Access implemented β€” useful MT8163 reference/test platform, not primary LibreEcho productamonet-koboreru
karnakAmazon Fire HD 8 8th GenMediaTek MT8163🟑 Potential β€” supported SoCamonet-koboreru β€” MT8163 platform
mustangAmazon Fire 7 9th GenMediaTek MT8163V/B🟑 Potential β€” supported SoCamonet-koboreru β€” MT8163 platform
laserAmazon Echo 4th GenMediaTek MT8512 + Amazon AZ1🟠 Research candidate β€” investigate whether the MediaTek bl2_ext verification weakness applies; not proven on EchoFenrir β€” bl2_ext research / Sprig
brownieAmazon Echo Dot 4th GenMediaTek MT8512BAAV🟠 Research candidate β€” investigate Fenrir applicability; not proven on EchoFenrir β€” bl2_ext research / Sprig
ganacheAmazon Echo Dot with Clock 4th GenMediaTek MT8512BAAV🟠 Research candidate β€” investigate Fenrir applicability; not proven on EchoFenrir β€” bl2_ext research / Sprig
cannoliAmazon Echo Dot 5th GenMediaTek MT8519 + Amazon AZ2🟠 Research candidate β€” investigate Fenrir applicability; no Echo-specific access provenFenrir β€” bl2_ext research
churroAmazon Echo PopMediaTek MT8519 + Amazon AZ2🟠 Research candidate β€” investigate Fenrir applicability; no Echo-specific access provenFenrir β€” bl2_ext research
baklavaAmazon Echo Spot 2024 / 2nd GenMediaTek MT8519 + Amazon AZ2🟠 Research candidate β€” investigate Fenrir applicability; no Echo-specific access provenFenrir β€” bl2_ext research
maverickAmazon Fire HD 10 (2019)MediaTek MT8183🟠 Research candidate β€” Kaeru has MT8183/Amazon LK groundwork; initial access still needs provingKaeru β€” MT8183 + Amazon groundwork
persimmonAmazon Echo Studio 2025Amazon AZ3 Pro platformβšͺ Entirely new platform β€” unrelated to the promising MT8516 Studio platformNo relevant current R0rt1z2 Echo access implementation

SoC family summary

  • MT8163 / MT8163V: established LibreEcho platform family with multiple device-specific access targets.
  • MT8516 / MT8516B / MT8516BAAA: strongest candidate for LibreEcho’s second platform family; device-specific access exists on several Echo products.
  • MT8183: active research family; Kaeru contains explicit MT8183 support and Amazon-specific LK groundwork, but an Echo initial-access route still needs proving.
  • MT8512: active boot-chain research candidate; investigate whether bl2_ext verification behaviour is susceptible to the Fenrir technique.
  • MT8519: active boot-chain research candidate for the same reason; no Echo-specific access implementation is currently proven.
  • AZ3 Pro: substantially different newer Amazon platform with no relevant access route currently identified.

Suggested porting priority

  1. Echo Dot 2nd Gen (biscuit)
  2. Echo Dot 3rd Gen (donut / crumpet)
  3. Echo 3rd Gen (pascal)
  4. Echo Plus 2nd Gen (lidar)
  5. Echo Studio (octave)
  6. Accessible MT8163 display devices, then other MT8516 products
  7. MT8512 and MT8519 generations

Access support is not the same as a LibreEcho port. Every target still needs device-specific kernel, display/audio, recovery, packaging and runtime validation work. Links point to the relevant external bootloader/access projects and are provided as technical references.

A safe path before a fast path.

The public release page will contain the downloadable release inventory when the next release is ready. The steps below explain the owner-facing installation and recovery process; destructive commands remain release-specific.

01

Prepare and back up

Confirm the supported model, host tools, cable and recovery method. Save original boot/recovery-critical state and owner-local calibration/connectivity inputs in a private, backed-up location.

02

Verify the release

Download only from the linked GitHub release. Verify the *-SHA256SUMS file and the published OTA public key before extracting or writing anything. Never use a raw image from a chat, branch or private path.

03

Install deliberately

Follow the release-specific partition and slot instructions. Stop if model, partition geometry, checksum, signing identity or owner-local inputs do not match. Destructive writes must name the exact target and require explicit confirmation.

04

First boot checklist

Confirm the product version, active slot, expected services, local Web UI response, read-write userdata and basic network/audio health. A Linux banner or ADB connection alone does not count as acceptance.

05

Update and rollback

Use the signed A/B updater only for an already-running compatible image. Keep the confirmed opposite slot. If health confirmation fails, preserve logs and use the documented recovery path; do not improvise a direct fastboot write.

06

Report safely

Include the exact public release identity, a smallest reliable reproduction and a redacted diagnostic bundle. Remove Wi-Fi secrets, provider tokens, serials, MACs, IPs, SSIDs, private paths and signing material.

Installation is not open yet: the public installation bundle and two independent first-time dry runs are still in progress. This guide explains the safety boundary; the Developer Preview is not yet open for general installation.

Explore the interface without a device.

This is a browser-local simulation. It does not connect to LibreEcho hardware, send configuration off-device or prove hardware capability.

Simulated LibreEcho Control Centre dashboard
Simulated dashboard
Simulated LibreEcho Control Centre System page
Simulated system and OTA view
Real-hardware proof: boot, media and voice captures from real hardware are not published yet.

Local-first is not the same as local-only.

LibreEcho can keep substantial processing on-device, but configured providers and network services can receive data. Choose integrations deliberately and treat the Web Control Centre as a local network service.

Wake word and DSPIntended to run locally in the device service chain; quality and hardware privacy acceptance remain experimental.
STTLocal STT is an experimental development path. A configured external STT provider receives audio or transcript data according to that provider's contract.
AssistantProvider requests can contain the transcript, context or selected configuration. Review the provider before enabling it.
TTS and mediaLocal TTS payloads and AirPlay/Bluetooth media are separate paths; external sender/provider traffic follows its own network boundary.
Web UI, diagnostics and OTAKeep the control plane on a trusted LAN. Exports and diagnostics must exclude passwords, tokens and private telemetry; verify release signatures before updates.

Physical microphone privacy

Current state: physical mute is not a beta-supported privacy guarantee. The end-to-end hardware-derived input, capture-disable boundary, LED state and restart behavior remain release-gate work.

Software mute, a UI label or a daemon status field must not be interpreted as proof that the microphone hardware is disconnected or that capture cannot occur.

Secret handling

  • Use local account/session controls and protect credential files with restrictive permissions.
  • Do not place Wi-Fi credentials, provider tokens or signing keys in backups, issues or diagnostics.
  • Never expose the device API directly to the public Internet.
Track privacy acceptance

One page for what is public.

Publication, host verification, hardware acceptance and beta support are separate states.

Public GitHub releases

Releases are being refreshed

There are no public downloads available right now.

Coming soon

We’re tidying up the release line before the next public images and OTA bundles are posted. We’re also actively working on a one-shot installer to make setup easier alongside the public release. Check the GitHub Releases page for updates.

Coming soon

The next public release will be posted here when ready.

Checksums included

Future downloads will include checksums and release notes.

Hardware notes

Each release will include the relevant validation status.

Open Beta

Not launched yet; preview and tester gates remain open.

For now, please use the product repository for project updates and discussion. Private candidates and development artifacts are not public downloads.

Send the right report to the right place.

Public issues are for reproducible, non-sensitive bugs. Never publish credentials, exploit details, OTA keys, private diagnostics or device identifiers in an issue.

Bug report checklist

  • Product version, release tag and channel.
  • Generic Echo model/revision, without serial or MAC.
  • Smallest reliable reproduction and whether reboot/recovery changes it.
  • Redacted diagnostics with passwords, tokens, SSIDs, IPs and private paths removed.
  • Expected versus actual behavior and whether the issue is on the public release or a development build.

Support boundary

This is a volunteer Developer Preview project. There is no guaranteed response time, and direct public-Internet exposure of the device control plane is unsupported.

If GitHub does not show private advisory reporting for this repository, do not disclose the vulnerability publicly; wait for the maintainer-announced private route.

Different components have different terms.

The website and LibreEcho-authored code use their stated open-source licences. That does not relicense Linux, third-party audio components, models, voices, owner-local firmware or vendor boot-chain material.

LibreEcho-authored source and siteUse the licence file in the relevant public repository.
Linux and PlatformPreserve the applicable GPL/LGPL and upstream notices; corresponding-source obligations remain component-specific.
TTS voiceCC-BY-SA attribution and ShareAlike obligations apply separately.
Wake-word modelCC-BY-NC-SA means the community-noncommercial payload is not cleared for unrestricted commercial reuse.
Owner-local firmware and AmonetExtracted from and retained by the owner; LibreEcho does not upload or redistribute those materials.
Audio FPGA bitstreamFollow the documented provenance record for this component.

Source, notices and relink requests

Use the public Product repository as the release coordination entry point. Exact source, notices, SBOM and relink materials for a release are provided against the release record and matched to its immutable identity.

The UI repository is currently private and is not presented here as a logged-out source download. Its public-safety and licence review is still tracked before Developer Preview publication.

Product source and release tracker

For recoverable hardware and careful testers.

The first cohort is bounded, technical and feedback-oriented. It is not a consumer launch.

Suitable testers

  • Own the specifically supported Echo Gen 2 target.
  • Can use command-line tools and USB recovery without maintainer-only access.
  • Have a backup and a known recovery path before changing the device.
  • Use a trusted local network and will not expose the control plane publicly.
  • Can submit redacted diagnostics and structured reproduction reports.

Entry acknowledgement

Installation may require recovery or reflashing and can cause data loss. Read the supported-hardware, privacy, known-issues and release pages first; verify checksums; preserve owner-local inputs; and understand that experimental voice, Bluetooth, physical mute and networking behavior may change.

Participation can be paused or withdrawn without deleting the public documentation. Open Beta will follow independent installation, recovery, OTA and stability evidence.

Feedback loop

  1. Record the public release identity and generic hardware scope.
  2. Reproduce with the smallest safe test.
  3. Collect and redact diagnostics.
  4. Use the product issue tracker for ordinary defects and the private security route for vulnerabilities.
  5. Link any release-blocking behavior to the current known-issues tracker.
Enrolment state: Developer Preview opening soon. The independent tester and release gates are still in progress.
An exploded stylised speaker showing reusable hardware layers

Put each change in the right repository.

The Product repository is the public coordination entry point. The layer map below keeps kernel, platform, UI, documentation and private release orchestration separate.

QR code to support LibreEcho on Buy Me a Coffee

Keep the lights on.

Donations fund the device lab, build infrastructure and the kernel time that keep validation moving on real hardware. Every contribution goes directly into the next milestone.

Buy LibreEcho a beer
QR code to join the LibreEcho Discord community

Join the community.

Chat with other LibreEcho users and contributors, ask questions and follow development.

Join LibreEcho on Discord

Donate hardware.

Spare Echo Gen 2 units, compatible board revisions or test cables accelerate compatibility coverage and independent validation. If you have hardware to donate, get in touch through the product repository before shipping anything.

Offer hardware