Installer
Install Pinna
This page installs Pinna on an Echo (2nd gen) or an Echo Dot (2nd gen) over USB, without a terminal. It checks the device first, and asks you before it writes anything.
This browser can't talk to USB devices
Open this page in Chrome, Edge, Brave or Opera on a computer. Firefox and Safari don't support WebUSB. Or install from a terminal, as described in Install Pinna.
Before you start
- A device that was unlocked before. It runs Pinna, or other firmware with adb. A device that still runs Amazon's software needs the bootloader unlock first: this page can check it, but can't unlock it yet.
- A backup, if you want to go back later. Installing replaces the current firmware and erases the device's data. Make the backup as described in What you need; this page can't make one yet.
- Chrome, Edge, Brave or Opera on a
computer, with an internet connection: the page downloads the
release from
updates.getpinna.dev. On Linux, the browser needs a udev rule; on Windows, the WinUSB driver. - A USB connection. For the Echo Dot (2nd gen), a micro-USB cable that carries data, plugged straight into the computer, not into a hub. For the Echo (2nd gen), pogo pins or a cable soldered to the USB pads on its base.
Report
If the result looks wrong, or the page can't go on, paste this into an issue. The serial number is cut short.
If it doesn't work
You can also install from a terminal.
The device isn't in the list
- The device isn't in fastboot. Start it again as described in step 3.
- The cable only charges. Try another cable, and a USB port on the computer itself.
The browser can't open the device
On Linux the browser runs as your user, and only root may open USB
devices that no rule names. Add this rule as
/etc/udev/rules.d/60-pinna-fastboot.rules:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c01", TAG+="uaccess" Then load it:
sudo udevadm control --reload-rules && sudo udevadm trigger
On NixOS, put the rule in services.udev.extraRules
instead. Then start the device in fastboot again (step 3) and
connect again.
Another program uses the device
fastboot, adb (run adb kill-server),
Android Studio, or this page in another tab. Close them and connect
again.
Windows needs the WinUSB driver
Install it with Zadig
while the device is in fastboot: choose Options › List All Devices,
select Android (USB ID 0BB4 0C01), choose
WinUSB and Install Driver. Then
connect again.
The device doesn't answer, or goes away
The page stops after the first request that gets no reply, and sends nothing more. Some devices that were never unlocked reset when they get a request and come back in fastboot. Unplug the device, start it in fastboot again, use another cable or USB port, and connect again. If it happens every time, open an issue with the report the page shows.
Leave fastboot without installing
Unplug the device and plug it in again. It starts as before.