How to Flash Custom Recovery on Amlogic TV Boxes

Updated 2026-10-21

If you have ever attempted to root an Amlogic-based Android TV box, you likely encountered the dreaded “black screen of death.” Unlike standard Android phones, where you can easily enter fastboot mode or download mode, Amlogic chips (such as the S905, S912, and S922X) are notoriously unforgiving. A failed root attempt, a corrupted bootloader, or even a bad OTA update can render your device completely unresponsive. The built-in recovery partition is often too small to hold a custom image like TWRP, and the standard ADB commands often fail to write directly to the recovery partition due to strict permission restrictions on modern Android versions.

This is where flashing a custom recovery via a computer becomes essential. It is not just about gaining root access; it is about having a safety net. With a custom recovery installed, you can wipe the cache, perform factory resets, and most importantly, install Magisk or SuperSU to gain root privileges without risking a permanent brick. However, this process requires precision. One wrong sector address, and you may corrupt the bootloader, requiring expensive professional reprogramming. This guide walks you through the safe method of installing a custom recovery on Amlogic TV boxes using the Amlogic USB Burning Tool and a specific recovery image designed for these chipsets.

Preparation: Gathering the Right Tools and Drivers

Before you attempt any flashing, you must ensure your workstation is correctly configured. The Amlogic USB Burning Tool is a powerful utility, but it is picky about drivers. If the tool does not detect your TV box, the process will fail immediately. You need to install the correct USB drivers for your specific chipset. While generic drivers might work for some older models, it is highly recommended to use the drivers that came with your specific box’s firmware or download the latest chipset-specific drivers from the Amlogic developer portal. Without these, the computer cannot communicate with the box’s UART or USB interface during the flashing sequence.

Next, you need the correct recovery image. You cannot simply use a standard Android TWRP image meant for Qualcomm or MediaTek devices. Amlogic requires a specialized recovery image, often referred to as “Amlogic Recovery” or a modified TWRP that includes the correct kernel modules for your specific SoC. If you use a generic image, the recovery will not boot, or worse, it might overwrite your EMMC storage incorrectly. Look for a recovery image that explicitly states compatibility with your chip (e.g., S905X3 or S912). Save this .img file to a known location on your computer.

You also need a micro-USB or USB-C cable that is capable of data transfer. Many charging-only cables will not work, leading to confusion when the device is not detected. Ensure you have a backup of your current Android system if possible, though Amlogic boxes rarely allow easy backups of the full system partition without root access already established.

The Hardware Trigger: Entering Maskrom or Recovery Mode

The most challenging part of flashing Amlogic devices is entering the correct mode to receive the flash commands. Unlike phones, you often cannot just press a key combination while the device is off. You must trigger the hardware to enter a low-level programming state. This is typically done by shorting two points on the motherboard or holding a specific button combination while plugging in the USB cable.

For many S905-based boxes, you need to locate the recovery button or the two metal contacts labeled “Rec” or “GND.” You must short these contacts while the device is unplugged from power. Then, plug the USB cable into the computer. The USB Burning Tool should detect the device in a “maskrom” or “recovery” state. If the tool does not detect the device, try a different USB port on your computer, preferably a USB 2.0 port, as some USB 3.0 controllers have compatibility issues with the burning tool.

If your box does not have accessible test points, you may need to open the case and look for a small push button labeled “Recovery” or “Reset.” Holding this button while plugging in the power or USB cable often forces the Amlogic chip into the necessary boot mode. Once the device is detected by the USB Burning Tool, the interface will usually show a progress bar ready to accept images.

Flashing the Custom Recovery Image

With the device in the correct mode and the tools ready, you can proceed with the actual flash. Open the Amlogic USB Burning Tool and click the “Import Image” button. You will be presented with several partitions, including Boot, System, Recovery, and EMMC. Do not flash the entire firmware unless your device is severely bricked and you want to restore it to stock. For our purpose, we only need to flash the recovery partition.

Locate the “Recovery” field in the software. Click the “Select” button and choose the custom recovery .img file you prepared earlier. It is crucial to ensure that the “Erase Flash” option is unchecked at the top of the window. Checking this option will wipe the entire EMMC storage, including your apps, settings, and system partition, effectively factory resetting the device and potentially causing boot loops if the system partition is corrupted. You only want to overwrite the recovery partition.

Once the recovery image is loaded into the Recovery field, click the “Start” button. The software will begin writing the data to the device. You will see a progress bar filling up. Wait for this process to complete. Do not disconnect the USB cable or turn off the computer during this time. If the process fails, the tool will give an error code. Common errors include “Write Error” or “Erase Error,” which usually indicate a bad USB connection or insufficient power. Try using a powered USB hub if the device seems unstable.

Verification and Next Steps

Once the burning process completes successfully, the USB Burning Tool will display a success message. You can now disconnect the USB cable. To verify that the custom recovery is installed, you need to boot into the recovery mode. This usually involves holding the recovery button (or shorting the contacts) while plugging in the power or USB cable again.

If you are successful, you should see the TWRP or custom recovery interface on your TV screen. From here, you can proceed to install Magisk. Open the Magisk manager app on your TV (if you have it installed) or push the Magisk APK via ADB. Use the “Install” option within Magisk, which will automatically patch the boot image and install the necessary binaries. Reboot the device, and you should now have root access.

If the device fails to boot into recovery, do not panic. It may have booted into the standard Android recovery or the system. Try wiping the cache partition from the menu. If it remains bricked, you may need to flash the stock boot image again using the USB Burning Tool to restore the original recovery, then try the custom flash again with a different image version. Always remember that this process carries risks. Ensure you have the correct image for your specific board revision, as even devices with the same chip can have different memory layouts.

Related reading: more Android TV notes