Search the Community

Hello Im a begginer and dont know Linux. I have a tv box : enyBox x98q Cpu amlogic s905w2 2g ram 16g rom My need to install MetaTrader5 on linux on this tv box. I downloaded both files on site this link: debian 13 ubuntu 26.04 I need to learn the install way by watching a video clip. I request you for making it

Comprehensive Guide: Installing Armbian on the TX10 PRO (Allwinner H313) Introduction This technical guide documents the complete process for deploying Linux on the TX10 PRO Android TV Box (Allwinner H313). Due to hardware variations and kernel compatibility issues common on these devices, establishing a functional Armbian environment requires specific images, DTBs, and configuration steps. This documentation is designed to streamline the installation process and avoid common hardware compatibility problems. Technical Specifications & Environment The procedures in this guide were validated on a TX10 PRO with the following hardware: Component Specification ---------------- ----------------------------------- SoC Allwinner H313 (sun50iw9p1) CPU Quad-core Cortex-A53 (ARM64) Memory 1 GB LPDDR3 (Samsung eMCP) Storage 8 GB eMMC Board Revision WFTECH_V2.0 Device Codename titan-p1 Product walley Stock OS Android (Modified Build) Bootloader U-Boot Tested Kernel Linux 6.12.64 (bookworm) Tested working image: Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz Kernel: Linux 6.12.64 bookworm Base OS: Debian Bookworm Server Target: X96Q DDR3 / Allwinner H313 Although this image is labeled for the X96Q DDR3, it successfully booted on my TX10 PRO with the WFTECH_V2.0 board and Allwinner H313 SoC. Hardware revisions vary, so compatibility with other TX10 PRO units is not guaranteed. ⚠ Crucial Hardware Warning TV box manufacturers frequently change internal components (RAM layout, Wi-Fi chipsets, and board revisions) without changing the product name. Always verify your board revision before proceeding. Using the wrong Device Tree Blob (DTB) can result in an unbootable system. Advantages & Disadvantages of Running Linux Advantages: Cost Efficiency Much cheaper than a Raspberry Pi or other SBC. Enclosure Included Comes with a case and power supply. Low Power Consumption Runs quietly with very low power usage, making it suitable for lightweight servers. Disadvantages: No Official Support Linux support depends entirely on community-maintained images. Thermal Throttling Cheap passive cooling causes overheating during heavy workloads. Weak eMMC Storage Internal storage may wear out under frequent writes. Slow I/O USB ports are usually USB 2.0 only. No SATA, NVMe, or native Gigabit Ethernet. Driver Problems Wi-Fi, Bluetooth, and hardware video acceleration usually require manual setup. Prerequisite Hardwares: MicroSD Card (8GB or larger) MicroSD Card Reader (Cost: 0.45 USD ) HDMI Monitor (Tv) USB Keyboard Ethernet Adapter Integrated Wi-Fi rarely works immediately on bookworm Linux. A wired Ethernet connection is strongly recommended for initial setup. Installation Process Step 1 — Download Armbian Official Armbian images generally do not include all hardware support for the H313. Download a trusted community image designed for Allwinner H313/H616 boards using the 6.12.64 kernel. USE THIS: Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz Step 2 — Flash the SD Card ⚠ Warning Avoid using the Linux dd command if you are unfamiliar with it. Selecting the wrong drive can permanently erase your computer. Instead, use BalenaEtcher. Flashing Steps: Install and open BalenaEtcher. Insert your MicroSD card. Click Flash from File. Select the downloaded .img.xz image. Click Select Target. Choose your MicroSD card carefully. Click Flash! Wait until flashing and verification reach 100%. Safely eject the card. Step 3 — Hardware Setup Before powering on: Insert the MicroSD card. Connect HDMI. Connect USB keyboard. Connect USB Ethernet. Connect power. Step 4 — First Boot The first boot performs: Filesystem expansion Initial setup System configuration This may take several minutes. Expected boot sequence: U-Boot ↓ Linux Kernel ↓ Armbian Login Prompt Step 5 — Initial Login Default credentials: Username: root Password: 1234 After logging in you will be required to: Change the root password Create a normal user Configure timezone Configure locale Step 6 — Verify Network Built-in Wi-Fi will probably not work. The board uses the SSV6x5x / SV6256 chipset which requires extra drivers. Verify Ethernet: ip a ping -c 3 1.1.1.1 Step 7 — Update the System Enable network time: sudo timedatectl set-ntp true Then update: sudo apt update sudo apt upgrade -y Step 8 — Install to eMMC (Optional) Once everything works from the SD card: sudo armbian-config Navigate to: System ↓ Install ↓ Boot from eMMC Follow the installer. After completion: Shut down Remove the SD card Boot from internal storage Hardware Compatibility Working - perfectly HDMI Output USB Ports USB Ethernet Known Issues Wi-Fi - Not working Requires manual compilation of the SSV6256 driver. Graphics No hardware acceleration. Software rendering only. DTB Compatibility Boot success depends heavily on selecting the correct DTB. Different board revisions may require different DTBs. Best Practices Test from SD First Never install to eMMC before confirming that everything works. Backup Android Create a backup of the original Android firmware before modifying internal storage. DTB Troubleshooting If the device: Boot loops Shows a black screen Fails to boot Mount the SD card on another computer. Open: armbianEnv.txt Try different H313/H616 DTB files until the system boots successfully.

Hi, I need help identifying the Maskrom/eMMC short points for an RK3528 TV box. Device: - TV box sold as H20 Pro - SoC confirmed as Rockchip RK3528 - Board marking: M16-R6B-L3-V1.0-260121 - RAM detected in Linux: 963 MiB - eMMC detected in Linux: 7.83 GB / 7.30 GiB - eMMC name from Linux: P1J95K - eMMC CID: fe014e50314a39354b12739109744200 What happened: - The box originally booted Android from eMMC. - Armbian booted successfully from SD using a customized joilg/x88pro-based image. - Later I wrote U-Boot/idbloader to eMMC: - idbloader.img at sector 64 - u-boot.itb at sector 16384 - After reboot, the board no longer boots from SD or eMMC. - LED stays red. - No HDMI output. - No Ethernet link/activity. - RKDevTool on Windows shows "No Devices Found". Recovery attempts: - Tried the reset/recovery button behind the AV/P2 jack while connecting power and USB. - Tried both USB ports. - Tried RKDevTool v2.86 with Rockchip drivers installed. - No Loader or Maskrom device appears. - Tried UART pads marked GND/TX/RX using ESP32-C3 as bridge, but output is not readable. Question: Can anyone identify the eMMC Maskrom short point for this board? I need to force RK3528 into Maskrom mode so I can restore the first bootloader area of the eMMC. Attached photos: - Front of board - Back of board - Macro photo of the eMMC/storage chip area - Macro photo of test pads near the storage chip

Please note that ophub is not Armbian. They use the Armbian name without permission, do not contribute to Armbian development nor participate in these forums. Having said that, android TV boxes are a community supported effort under Armbian. It would be appreciated if you took the time to submit a PR to include your efforts into Armbian.

Hi! I've been using the latest build on my H96Max TV Box (H313, 2GB LPDDR3) for a while and it works just fine. Recently tho, I've noticed that a more up to date community build for the X96Q DDR3 TV-Box popped up on the main boards page on armbian.com. So I got curious and tried booting that one, and it boots, but the built in ethernet port doesn't work there for some reason? I checked in the config file, and the kernel does seem to have the right drivers built in (dwmac-sun8i ig?). What should I try to get ethernet working on the more recent community builds? Thanks in advance!

Please read the Armbian TV box FAQ and the installation instructions for amlogic TV boxes. https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

Please move to Allwinner https://forum.armbian.com/topic/56539-how-to-install-armbian-on-mx10-f3-tv-stick/ https://xdaforums.com/t/how-to-use-otg-in-twrp.3097688/

Hi everyone, I am trying to install Armbian on my X96 Max Plus TV box, but I'm having trouble getting the Wi-Fi and peripheral power management to work correctly. I disassembled the box to gather the exact hardware specs from the PCB. Could you please advise which specific DTB file I should use for this hardware revision? Here are my exact hardware specs and chip markings: SoC: Amlogic S905X3 RAM: 4GB LPDDR3/DDR3L (Micron, FBGA code: D9PQL) Storage: 32GB eMMC 5.1 (SanDisk SDINADF4-32G) Ethernet (LAN): 1000M / Gigabit (Realtek RTL8211F transceiver) Wi-Fi/Bluetooth Module: Broadcom/Ampak under a metal shield marked AM7256 (Android logs show it as a Broadcom chip using bcmdl firmware utility). Power Management / Audio: Uses VT2921 logic, Audio DAC is GS7903F. Front Panel LED Display: Driven by AIP1628 / TM1628 (display sticker: 56BT120). PCB Marking / Revision: G24PO2S (or Q5X3_G24_P02_S variant, post-2021/2022 board). Should I go with meson-sm1-x96-max-plus-q1.dtb, meson-sm1-x96-max-plus.dtb, or is there a better option for this specific "AM7256" hybrid power-routing board to wake up the Broadcom Wi-Fi? Thanks in advance for your help!

Thank you for moving my post to the appropriate section. I apologize for posting in the wrong area initially. To reiterate my question for this General forum: I have a Skyworth TV box with a Realtek RTD1325. I am looking for any guidance on whether it is possible to run Armbian on this hardware, even experimentally. Has anyone here worked with similar Realtek-based devices, or could someone point me toward resources for building a custom image for the RTD13xx family? I understand this is outside the usual supported hardware, but any advice would be greatly appreciated. Thank you.

Hello everyone, I am hoping to get some advice on the possibility of running Armbian on a TV box I have. I understand this is a niche device, and I am new to this process, so any guidance would be greatly appreciated. Device Information: Device Type: TV Box Manufacturer: SkyworthDigital Model: SK Hailstrom Ref 1325 Board: HPR3E1325_4k Hardware/Platform: rtd1325 Product: HPR10X Hardware Details (from system info): Core Architecture: 4x ARM Cortex-A55 @ 1700MHz Instruction Set: 64-bit ARMv8-A (32-bit Mode) Supported ABIs: armeabi-v7a, armeabi Scaling Governor: schedutil I have done some preliminary research and learned that official Armbian support for Realtek SoCs is not available. However, I noticed that there is some ongoing community development for the RTD13xx family. My questions are: Has anyone had any success with a similar Realtek RTD1325 device? Would it be possible to adapt an existing build (perhaps one intended for the RTD1319) to work with this hardware? If so, what would be the main challenges (e.g., DTB files, drivers)? Could someone point me toward the best resources or forum threads for building a custom Armbian image for this kind of Realtek platform? I have experience with the command line and following technical guides, but I am not a developer. I am prepared for the possibility that this might not be feasible, but I am eager to learn and experiment. I will, of course, proceed with caution regarding the risks (e.g., bricking the device). Thank you in advance for your time and expertise. Additional Context: I have the device rooted and can access ADB.

Thank you very much. Thanks to your detailed guide—as well as the one by "Chiều Nhạt Nắng"—I successfully installed Armbian on my TV box. I had struggled for a long time previously, following outdated instructions without fully understanding them; I kept unplugging and replugging the power cable, which ended up damaging the power IC (so now I have to use the USB port for power). However, thanks to your specific guidance (user 0757), I followed the steps and finally succeeded. Thank you!

Hi all, I'm running DietPi on an Orange Pi Zero 3 (H618, sunxi64), which repackages the Armbian current-sunxi64 kernel. I use a USB DVB-T2 dongle (HanfTek Astrometa RTL2832P, VID/PID 15f4:0131) with tvheadend for over-the-air TV. After a routine update the dongle stopped working entirely, and I tracked the root cause down to missing kernel modules. ## Problem Starting from kernel 6.18.x (package linux-image-current-sunxi64 version 26.05.0-trunk-dietpi1 and all subsequent builds through dietpi5), the following modules are absent from the kernel package: - dvb_usb_v2 - dvb-usb-rtl28xxu - dvb_core The USB device is correctly detected at bus level (lsusb, dmesg) but no driver ever binds to it and /dev/dvb is never created. lsmod | grep dvb returns nothing, and find /lib/modules/$(uname -r) -iname "*dvb*" only shows RC keymap files (e.g. rc-dvbsky.ko.xz), not the actual DVB subsystem drivers. lsusb output: Bus 004 Device 003: ID 15f4:0131 HanfTek Astrometa DVB-T/T2/C FM & DAB receiver [RTL2832P] dmesg shows the device is enumerated but no driver binds: usb 4-1: New USB device found, idVendor=15f4, idProduct=0131, bcdDevice= 1.00 usb 4-1: Product: dvbt2 usb 4-1: Manufacturer: astrometadvbt2 (no further DVB-related messages) ## Verified affected range I downloaded and inspected each linux-image-current-sunxi64 .deb from the DietPi apt repo without installing them, extracted with dpkg-deb -x, and searched for dvb_usb_v2.ko / dvb-usb-rtl28xxu.ko inside lib/modules/*/kernel/drivers/media/usb/dvb-usb-v2/. Results: 26.05.0-trunk-dietpi1 through dietpi5 (kernel 6.18.x) → DVB modules ABSENT 26.02.0-trunk-dietpi8 (kernel 6.12.76) → DVB modules PRESENT 26.02.0-trunk-dietpi1 through dietpi7 (kernel 6.12.58–6.12.74) → PRESENT 25.11.0-trunk-dietpi1 through dietpi3 (kernel 6.12.43–6.12.57) → PRESENT The regression is introduced exactly at the 26.02→26.05 branch transition (kernel 6.12→6.18). ## Kernel config comparison (confirmed) In kernel 6.12.76 (/boot/config-6.12.76-current-sunxi64), the full DVB-USB subsystem is present and compiled as modules, including: CONFIG_DVB_CORE=m CONFIG_DVB_USB_V2=m CONFIG_DVB_USB_RTL28XXU=m CONFIG_DVB_USB=m (plus ~40 additional DVB USB driver modules) In kernel 6.18.29 (extracted from linux-image-current-sunxi64_26.05.0-trunk-dietpi5_arm64.deb), grep for DVB_USB and DVB_CORE returns NO output at all — the options are not present in the config file, not even as "# CONFIG_DVB_USB_V2 is not set". This confirms the entire DVB-USB subsystem was dropped from the sunxi64-current kernel config when the 6.18.x branch was opened, not selectively disabled. ## Hardware Board: Orange Pi Zero 3 (Allwinner H618, sun50i-h618) Dongle: HanfTek Astrometa DVB-T/T2/C FM & DAB receiver [RTL2832P] VID/PID 15f4:0131 Kernel broken: 6.18.29-current-sunxi64 GCC 13.3.0 (aarch64-linux-gnu), build date 2026-03-05 Kernel working: 6.12.76-current-sunxi64 USB device descriptor (from lsusb -v): idVendor 0x15f4 HanfTek idProduct 0x0131 Astrometa DVB-T/T2/C FM & DAB receiver [RTL2832P] bcdDevice 1.00 iManufacturer 1 astrometadvbt2 iProduct 2 dvbt2 bNumConfigurations 1 bNumInterfaces 2 MaxPower 500mA ## Workaround Downgrading to linux-image-current-sunxi64=26.02.0-trunk-dietpi8 restores DVB support. Package pinned with apt-mark hold to prevent auto-upgrade. Note: the downgrade via apt-get install --allow-downgrades correctly swapped the kernel image and initrd, but did NOT regenerate the /boot/dtb-<version>/ directory nor update the /boot/dtb symlink — it was left pointing to the now-removed newer kernel's dtb directory, causing a boot failure. The dtb files had to be manually copied from /usr/lib/linux-image-6.12.76-current-sunxi64/allwinner/ and the symlink fixed by hand. This may be worth a separate look at the postinst/postrm scripts for the kernel downgrade case on sunxi64. ## Requested fix Please re-enable CONFIG_DVB_USB_V2=m, CONFIG_DVB_USB_RTL28XXU=m, CONFIG_DVB_CORE=m and their dependencies in linux-sunxi64-current.config for the 6.18.x branch. These were present throughout the entire 6.12.x series and there is no apparent reason to drop them. Thanks for the great work on Armbian!

After finally getting my TV box to boot Armbian, I'd like to provide some beginner-friendly pointers in addition to @Chiều Nhạt Nắng's installation note 4.2, Full install to NAND / eMMC: As someone who's completely new to Android TV box modding, this step took me a while to get through. What it actually means is not to literally boot your TV box into its original firmware, but to enter either Loader Mode or Maskrom Mode. If you've built or tried to poke around your PC, they are sort of like the BIOS or UEFI (technically BIOS and UEFI live on the motherboard, not CPU... but I digress), or if you have done Nintendo Switch modding, it's like entering RCM. It's not the guide's fault because there are so many ways to get your chip to enter a "maintenance/recovery mode" on so many different boards even with the same chip, it's basically impossible to list all the ways to put it into a malleable state. The way to enter Loader or Maskrom mode typically requires you to do something to the TV box while it is actively booting up, which will interrupt the process and enter the respective mode. For my TV Box (2016 - 2020 ish, Huawei EC6108V9A, RK312X), to enter Loader Mode, I need to repeatedly tap the "Front Page" or "Home" button on my TV box remote as soon as I connect the OTG USB port to my PC (the OTG port is typically the USB port that's the closest to the Ethernet port), I didn't need to plug in the barrel power connector since the board draws power through the same USB connection. If you found yourself in an Android system recovery <3e> page, this is not what we want, you might be tapping the wrong button like "Standby" or "Sleep" button. For my board, once I successfully enter Loader Node, aside from the Windows notification and the Bold text saying "Found ____ Device" at the bottom of the RKDevTool/AndriodTool, it was also showing a static logo screen through HDMI. If you do not have the TV Box's remote, or if you have messed up the install and have to redo, you will almost definitely need to take apart the Box's outer shell and gain access to the PCB itself to enter Maskrom Mode instead. (Images found online) To enter Maskrom Mode, you will need to short two specific pins (or pin holes, or capacitor pads like the first image) as you plug the USB connector from the PC to the USB OTG port on your board (The official way is to short Clock (CLK) to Ground (GRD or any metal connector housing) but good luck finding those if they're not labeled). In my experience, tweezers are the best for this. Since everyone's board looks different, there are different ways to do it, but do not try to short anything on your board before you're absolutely certain that the image of the board matches the one on your hand exactly. Unfortunately these info are incredibly niche and hard to find, your best bet is to search your TV Box's model number along with your chip's name (RK3128 in our case) on google and bilibili, there's a good chance you'll end up on a Chinese forum and have to dig through it with google translate. (Do NOT take an AI's word for it!) In case the first step in the quote isn't clear enough, you have to click the EraseLBA button after typing in these addresses below it to erase sectors. It is also worth noting that you have to be in Loader Mode to EraseLBA or use any "Read____" buttons. If your device is in Maskrom Mode because you lost the remote or botched an install, you can't directly do all that aside from Download Image. The workaround is to hit the "..." button to the right of "Boot:", select rk3128_loader_v2.12.263.bin and hit Download. Now you can use most of the Advanced Functions while in Maskrom! In Chieu's attached image for this step, there is actually an error. If you are using the files from their 20260430 release (A26-release-20260430.zip), you will need to set Boot sector's address at 0x00006000, NOT 0x00010000. I strongly encourage you to open parameter.txt and verify the addresses yourself. My setup looks like this: 0x00000000 | Loader | rk3128_loader_v2.12.263.bin 0x00000000 | parameter | parameter.txt 0x00002000 | uboot | uboot.img 0x00004000 | trust | trust.img 0x00006000 | root | armbian_rootfs_26.2.img By the way, you can click on the empty box to the right of paths to find the files. Right click - Del item to delete any extra default entries you don't need. Now before you click Run, I strongly recommend you to connect the board to a monitor/TV via HDMI and your router via Ethernet with known good cables/connections! Your board's first boot into Armbian happens immediately after Download Image finishes, therefore it's incredibly difficult to monitor the progress without them. I'm honestly not sure if the setup can complete without Ethernet because I tried to flash my board without connecting Ethernet twice and failed twice. Miscellaneous Notes: If you're 100% positive that you have done the steps to enter Loader Mode or Maskrom Mode correctly but your PC is refusing to pick up the connection, try installing the driver "Rockchip_DriverAssitant_v4.2" (should be the first result on google). Some online sources might tell you to diagnose via UART with a USB-to-ttl adapter. It did not work on mine (was completely silent during boot). Conversely, not seeing anything from UART doesn't necessarily mean your board is bricked. The board should always be able to enter Maskrom if you have access to the PCB. After your board has gone through the first boot, you will see a prompt on the HDMI output asking you to set a password for the root user. You can connect to the board via SSH at this point with IP address shown during the boot sequence; you do not need to connect a physical keyboard to the board. A handy software to manage all your UART and SSH connections is MobaXterm. The settings are straightforward and there is a portable version if you don't like installing stuff. From OP's screenshots I think Chieu is using it too!

Hello, i've just tried https://github.com/velvet-os/imagebuilder/releases/tag/230910-02 image, and boots perfectly from sd card in my x96q tv box, allwinner h313 v4.0, is the only image that worked... i've tried them all....my question is how to install it on the internal memory of the box? i've tried from the terminal with root access, but when i hit cd /root/ and ls, nothing happens.... if anybody can give any ideas i will appreciate it... thanks in advance.

I want to install an image from the sd card to the internal memory in x96q tv box, it boots perfectly from sd card, without having to press anything, and everything works ok, even bluetooth adapter and video reproduction, my question is "do i still need to modify boot files to install in emmc or is not necessary? thanks in advance....

please help me I need firmware STB MXQPRO 4K 5G ADVANCE mainbord type IK316Q-EMCP_V4.1 221024.send me FW as the same board please,i need install for android tv.and tool I'have as I flash for 8 firmware while I install program full after reboot or shutdown then start again my stb did'nt start to menu.Thank's Best Regard brothers,

I see no clear error, only something with hdmi-audio-codec, but that is somehow expected AFAIK with mainline based rockchip64 kernel. I think Xfce is X11 and others default to wayland. You can try KDE in X11. 4K is not fully mainlined AFAIK, but you need to check yourself. You can try an edge kernel, is 7.1.x based, maybe it fixes things. I have seen many such issues (RK3588 SoC) in the past, but thing are remarkably fine with 'latest Linux' (KDE6 1080p60, don't have a 4K monitor/TV).

Hi there, I followed the instructions in section 4.1 to install it onto the memory card, but when I plug it into the TV box, it won't boot from the card. Could you please provide instructions again?

@KhanhDTP There's no pull request yet but they do have a preparation PR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41654 For DQ 11S, it's about 15 fps@1080p. The FPS varies depending on the gaming scenes. You can check out my video https://b23.tv/xvsMPqD

Hello everyone, I am looking for the original firmware for my Q1 TV Box. Board information: Board: Q1-V4.0 CPU: Allwinner H313 RAM/Storage: 2GB + 16GB eMCP (Foresee) WiFi: SV6256P Sticker on PCB: Q1-H313-111-ATV-8800 XH20251014024 I have already tried searching on Needrom, but the available firmware is for Q1-V3.0 / A32 / A33 boards, and I am not sure it is compatible with my Q1-V4.0 board. Does anyone have the original firmware (.img) or know where I can download it? Thank you very much.

I just installed Armbian_community_26.8.0-trunk.170_H96-tvbox-3566_resolute_edge_7.0.12_gnome_desktop on an original board HCY-RK3566-1X32-V13 2021-03-27 I wanted to confirm the WiFi chip visually but could not do so as pulling the shield off the HCY6335 was not possible, it's very likely actually soldered so don't try. With this image out of the box: What works: LAN Display What doesn't work: WiFi Bluetooth Unknown: SPDIF Hardware video decoding Afterwards, I installed brcmfmac4335-sdio.bin and brcmfmac4335-sdio.txt from https://github.com/LibreELEC/brcmfmac_sdio-firmware/tree/master to /lib/firmware/brcm/ as per https://green.bug-eyed.monster/armbian-on-the-h96-max-v56-android-tv-box/ but I don't think you need any symlinking. This made Bluetooth and WiFi work but the speed it gets is very poor (20mb/s) so I recommend using wired connection which did get ~500mb/s. I started looking to into hardware video acceleration and this seems to be a bit of a mess. AFAICT MPP (Media Process Platform) and RGA (2D Raster Graphic Acceleration) are needed for this to work. The two options I saw were ffmpeg-rockchip and jellyfin-ffmpeg but both mention needing Rockchip BSP/vendor kernel. Does anyone have any experience here as I was hoping to turn this into a media PC? Given component costs now an that I originally paid ~$42 for the 8GB model I do think this board + armbian runs quite smoothly.

So I've got two of these old android tv boxes, both running the S912 chipset, and both are pretty much dead at this point. Trying to figure out if it's worth the effort to revive them or if I should just toss them already. On both boxes: no display through hdmi at all, not even a logo or flicker. Tried the toothpick trick for recovery screen with power plugged in, no reaction. Keyboard and mouse don't get picked up when connected. And when I hook them up to my laptop with a usb to usb cable, the boot light does turn on so they're clearly getting power, but the box itself never shows up anywhere on the laptop, not even in device manager after installing the usb burning tool drivers (one does shows up, but says USB device not recognized). Also tried the SD card method, used the correct armbian image on it, still didn't worked. Basically all I get is that one led lighting up and that's it. No video output, no usb enumeration, nothing responds. Attaching some pics of the boards and ports in case it helps spot anything obvious. Before I give up on these completely, does anyone know if there's still a way to force them into burn mode, because i know for certain that it's not a hardware related issue. Software is stopping them going into burn mode. Hardware is completely fine and working. So i wanna force them to go into burn mode so i can use armbian image on them. If there really is no option, i'm tossing them out. But there has to be a way. Any help would work. Thanks in advance.

Hi, could someone please give me a backup of the MXQ PRO 4K (5G version) WiFi EA6521QF? I need it for my Android TV box. Thanks.

Hello everyone, I am trying to install Armbian on my Android TV Box, but unfortunately, I flashed an incorrect firmware. Now the device is hard-bricked: the red and blue LEDs are blinking alternately, there is no HDMI output (black screen), and the physical reset button is not working properly. I already have an SD card loaded with the multitool to install Armbian, but I need to force the SoC into Maskrom Mode first so it can bypass the corrupted eMMC and boot from the SD card. Device Specifications: SoC: Rockchip RK3228A Board ID: T39-V1.0 Storage: eMMC (BGA type) I have attached the front and back photos of my PCB board (IMG-20260607-WA0027.jpg and IMG-20260607-WA0031.jpg) for reference. Could anyone help me identify the exact and safe test points (CLK to GND shorting points) for this specific T39-V1.0 board layout? Thank you so much for your help!

I tried but failed because I didn't understand at first, but now I understand part of it, and my TV box is malfunctioning. The problem is that when I plug in the power cord with the adapter, no lights or anything come on, but when I plug in the USB cable near the LAN port, it starts up normally (because I initially followed method 4.2. Full install to NAND / eMMC). Now I've flashed the Android firmware and it's working, but the error is as I described above. So, is the power IC dead or is the problem somewhere else?