Search the Community

I failed to flash the firmware of my TV box and it's now bricked. I need to re-flash it. Please tell me where the shorting point of this TV box is and how to flash it using the shorting point. Thank you.

Hello good people. I honestly had given up on that thing, until last weekend, where I set my mind to finally get it to work. And work, it does! eMMC works, display output works without a trouble, and only today I've seen @eloirotava's comment about the 6051. And I'm calling for help again on that one. I currently am using the kernel 7.0.8-meson64 (the current edge for the tv box) and no matter what i'm doing, there's no way for me to get the correct linux-header files, to compile and install that module. May a kind soul help me? I'll post a full documentation very soon, and will probably push my work to the armbian git, once everything is clean. Thank you very much in advance!

Hello, I have H96 Max TV box with RK3528 chip (4GB RAM, 64GB eMMC, Android 13, build RZX.V01.20240924). Board: RK3528_DDR3_8X4_V12. Problem: Box does not boot from TF card at all. No HDMI output, no DHCP lease, nothing. What I have: TF card slot on the box 1x USB 2.0 port, 1x USB 3.0 port No serial/UART adapter (DEBUG header visible on PCB but not connected) Android 13 still working on EMMC ADB access with root What I tried: Built Armbian with BOARD=rk3528-tvbox BRANCH=legacy BUILD_MINIMAL=yes RELEASE=trixie Extracted DTB from Android boot partition, added to image Wrote image to TF card with dd Verified RKNS header at sector 64 - correct Tried replacing idbloader with one from our custom U-Boot build Original U-Boot on EMMC appears to ignore TF card completely Question: How to make original U-Boot boot from TF card? Or is there a way to install Armbian to EMMC safely while keeping ability to recover? Device AIDA64 info: Model: H96_Max_RK3528 Device: rk3528_box Hardware: rk30board Thank you!

Hello everyone, I am reaching out to see if anyone in the community has successfully managed to get the internal Wi-Fi working on a box with the Realtek RTL8703bs chip. I have a MXQ Pro max (t9-RK3328) and I am using the latest Armbian build (Armbian_community_26.2.0-trunk.904_Rk3318-box_trixie_current_6.18.30_minimal.img.xz) provided by @jock for RK3318/RK3328 TV boxes. Here is the situation: 1. Using `rk3318-config` with `rk3318-box-led-conf1`, the chip is correctly powered and detected on the SDIO bus. 2. `dmesg` shows: `mmc1: new high speed SDIO card at address 0001`. 3. The hardware ID is confirmed as `024c:b703`. My questions : - Has anyone ever managed to make this specific chip (RTL8703bs) work on Armbian? - Does anyone have a patched driver (`.ko`), a specific `.dtbo` overlay, or a workaround that doesn't require recompiling the entire kernel from scratch? Here is my system log for reference: https://paste.armbian.com/ecadekazaz Thank you very much for your time and any advice you can share!

@ssdm2nvme Hi, whats up? I tried everything you recommended, including following some other tutorials beforehand, but I still can't get past the TV box's "BIOS" screen. It keeps restarting repeatedly, and I can never actually access the system. Do you have any idea what it could be?

Hi Ive just installed the latest version of Armbian (Ubuntu Noble+KDE) and everything works fine except it looks like it is not detecting my TV resolution correctly. I can choose 1920x1080@120hz but if I try yo go to 4K I can only select 24Hz I attach armbian monitor logs url, modetest and kscreendoctor My cable is HDMI 2.1 Any help would be appreciated modetest -c trying to open device '/dev/dri/card1'... is not a KMS device trying to open device '/dev/dri/card0'... done opened device `RockChip Soc DRM` on driver `rockchip` (version 1.0.0 at 0) Connectors: id encoder status name size (mm) modes encoders 83 82 connected HDMI-A-1 1880x1060 35 82 modes: index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot #0 4096x2160 24.00 4096 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #1 4096x2160 23.98 4096 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #2 3840x2160 30.00 3840 4016 4104 4400 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #3 3840x2160 29.97 3840 4016 4104 4400 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #4 3840x2160 25.00 3840 4896 4984 5280 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #5 3840x2160 24.00 3840 5116 5204 5500 2160 2168 2178 2250 297000 flags: phsync, pvsync; type: driver #6 3840x2160 23.98 3840 5116 5204 5500 2160 2168 2178 2250 296703 flags: phsync, pvsync; type: driver #7 1920x1080 120.00 1920 2008 2052 2200 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver #8 1920x1080 119.88 1920 2008 2052 2200 1080 1084 1089 1125 296703 flags: phsync, pvsync; type: driver #9 1920x1080 100.00 1920 2448 2492 2640 1080 1084 1089 1125 297000 flags: phsync, pvsync; type: driver #10 1920x1080 60.00 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver #11 1920x1080 59.94 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver #12 1920x1080 50.00 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver #13 1920x1080 30.00 1920 2008 2052 2200 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver #14 1920x1080 29.97 1920 2008 2052 2200 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver #15 1920x1080 24.00 1920 2558 2602 2750 1080 1084 1089 1125 74250 flags: phsync, pvsync; type: driver #16 1920x1080 23.98 1920 2558 2602 2750 1080 1084 1089 1125 74176 flags: phsync, pvsync; type: driver #17 1680x1050 59.88 1680 1728 1760 1840 1050 1053 1059 1080 119000 flags: phsync, nvsync; type: driver #18 1600x900 60.00 1600 1624 1704 1800 900 901 904 1000 108000 flags: phsync, pvsync; type: driver #19 1280x1024 60.02 1280 1328 1440 1688 1024 1025 1028 1066 108000 flags: phsync, pvsync; type: driver #20 1152x864 75.00 1152 1216 1344 1600 864 865 868 900 108000 flags: phsync, pvsync; type: driver #21 1280x720 60.00 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver #22 1280x720 59.94 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver #23 1280x720 50.00 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver #24 1280x720 30.00 1280 3040 3080 3300 720 725 730 750 74250 flags: phsync, pvsync; type: driver #25 1280x720 29.97 1280 3040 3080 3300 720 725 730 750 74176 flags: phsync, pvsync; type: driver #26 1280x720 24.00 1280 3040 3080 3300 720 725 730 750 59400 flags: phsync, pvsync; type: driver #27 1280x720 23.98 1280 3040 3080 3300 720 725 730 750 59341 flags: phsync, pvsync; type: driver #28 1024x768 60.00 1024 1048 1184 1344 768 771 777 806 65000 flags: nhsync, nvsync; type: driver #29 800x600 60.32 800 840 968 1056 600 601 605 628 40000 flags: phsync, pvsync; type: driver #30 720x576 50.00 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver #31 720x480 60.00 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver #32 720x480 59.94 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver #33 640x480 60.00 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver #34 640x480 59.94 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver props: 1 EDID: flags: immutable blob blobs: value: 00ffffffffffff004dd9057901010101 011e010380bc6a780a0dc9a057479827 12484c2108008180a9c0714fb3000101 01010101010108e80030f2705a80b058 8a005a227400001e023a801871382d40 582c45005a227400001e000000fc0053 4f4e5920545620202a33300a000000fd 0017790e883c000a20202020202001bf 020367f05861605d5e5f621f10140513 0420223c3e1203110265663f402f0d7f 071507503d07bc570601670403830f00 006e030c004000b8442b008001020304 67d85dc401788003eb0146d000480382 88627697e200cbe305df01e40f030030 e6060d018aac10011d007251d01e206e 2855005a227400001e000000000000a3 2 DPMS: flags: enum enums: On=0 Standby=1 Suspend=2 Off=3 value: 0 5 link-status: flags: enum enums: Good=0 Bad=1 value: 0 6 non-desktop: flags: immutable range values: 0 1 value: 0 4 TILE: flags: immutable blob blobs: value: 84 max bpc: flags: range values: 8 8 value: 8 kscreen-doctor -o Output: 1 HDMI-A-1 ea40cb77-73bf-4175-8970-22f84927f147 enabled connected priority 1 HDMI replication source:0 Modes: 1:4096x2160@24.00*! 2:4096x2160@23.98 3:3840x2160@30.00 4:3840x2160@29.97 5:3840x2160@25.00 6:3840x2160@24.00 7:3840x2160@23.98 8:1920x1080@120.00 9:1920x1080@119.88 10:1920x1080@100.00 11:1920x1080@60.00 12:1920x1080@60.00 13:1920x1080@59.94 14:1920x1080@50.00 15:1920x1080@30.00 16:1920x1080@29.97 17:1920x1080@24.00 18:1920x1080@23.98 19:1680x1050@59.88 20:1600x900@60.00 21:1280x1024@60.02 22:1152x864@75.00 23:1280x720@60.00 24:1280x720@60.00 25:1280x720@59.94 26:1280x720@50.00 27:1280x720@30.00 28:1280x720@29.97 29:1280x720@24.00 30:1280x720@23.98 31:1024x768@60.00 32:800x600@60.32 33:720x576@50.00 34:720x576@50.00 35:720x480@60.00 36:720x480@60.00 37:720x480@59.94 38:720x480@59.94 39:640x480@60.00 40:640x480@59.94 Custom modes: None Geometry: 0,0 1821x960 Scale: 2.25 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 100% and dimming to 100% Color resolution: automatic (10), range: [8; 8] bits per color Allow EDR: unsupported Sharpness control: unsupported Automatic brightness: unsupported Thank you

Hi @Tavares R You should definetly check the "Media framework installer v0.1" by Jock, on this link -> https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/10/#comment-102655 Also, this other link contains a repo to install some patched libs to at least use decoded video -> https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ Hope it helps, but reality check is the rk3229 is just too weak to properly handle a full DE running a modern browser... Something also worth trying is to enable the "cpu-hs" overlay. it will "overclock" the rk3229 from 1200Mhz to 1400Mhz, giving some extra performance, but keep low expectations... PS: Are you brazillian by any means? Tavares is a very common last name in Brazil.

I created this account just to thank you, man. Thank you so much, it worked perfectly here. Finally, my old TV box has another use besides collecting dust.

TV Box Name: Intelbras IzyPlay Board name: DV8038 CPU: Amlogic S805X (GXL Meson, Rev D) Armbian build file name: Armbian_community_26.2.0-trunk.821_Aml-s9xx-box_trixie_current_6.18.26_minimal.img.xz DTB file used: meson-gxl-s805x-p241.dtb Kernel Version: 6.18.26-current-meson64 Distribution Installed: Debian 13 (Trixie) Working Ethernet: Yes Max Ethernet Speed that works: 100 Mbps Does wifi work: Yes Does bluetooth work: No Does HDMI audio work: Not tested (headless setup) Additional Comments: - Board has 1GB RAM (908MB available) and 7.3GB eMMC - HDMI output works (tested on a DELL P2219H) - Reset button is between USB1 and USB2 ports - USB2 port is required for booting (closest to power input) - To boot from USB: hold reset button while applying power, release after 15 seconds

Hello averyone I'm trying to download the multitool.img.xz can someone please help me find it or share a valide link?

not getting internal wifi from "amlogic s905x3" "x96 max plus" tv box wifi chip "CDTech 47W3155" board version "Q5X3-141 V4.1"

To my knowledge, there are two versions of this device: the "old" version and the new version, which has a 6031 Wi-Fi chip. Here are the two DTS files extracted from the original android tv firrmware for each hardware version. Hope it helps. Tanix_TX1_6031_DTS.txt Tanix_TX1_DTS.txt

On internet i can't find any image for this tv box. Anyone have build for this?

I installed Waydroid on an Amlogic Meson GXM (S912) TV box. The SOC has a Mali-T820 GPU, and the box has 2 GB of RAM and 16 GB of eMMC. This was easy to do and Waydroid worked, but it was very slow, even before it heated the SOC to 80°C, which is probably its throttling limit. I removed Waydroid because it was too slow. I wasn't trying anything demanding. Even navigating Android Settings was ridiculously slow. This is a bit surprising because the hardware was designed for running Android. I was not running much else, just Wayfire and one or two Alacritty consoles. I don't think I was running out of memory. Is it possible to get decent Waydroid performance on other arm64 hardware?

I recently got this tv box emulator thing but i now emulate games on my laptop for convineince. I decide to download armbian on the tv box so that i can set up pi-hole for network wide ad blocking. Ive tried multiple times but i cant see to get it working. Cpu: Amologic S905L Ram:2 gig DDr3 ive been downloading this version https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_jammy_arm64_server_2026.02/Armbian_26.02.0_amlogic_s905l_jammy_6.1.161_server_2026.02.02.img.gz been using this dtb meson-gxl-s905x-p212.dtb been using this u bootfile named: u-boot-s905x-s912 To reboot the system there is no button in the AV port and the box refuses to download any apk or app for terminal emulator, Developer tools are not available,threfore i prefer to do it through the update method. the file structure Ive been following these instructions from gemini https://gemini.google.com/share/1e335432197f https://gemini.google.com/share/0a6ce8a19d0c Please ask me if you need more info I also asked in reddit btw

Hi, I am assuming that you have a standard Q1 TV Box (Allwinner H313 based). 1) Download Armbian Imager here; 2) Install the version for your operating system; 3) After installing, choose "Manufacturer=ALLWINNER", Board="X96Q TV BOX", Operating system="minimal Trixie current" and Storage ( I suggest a good quality Class 10 SD card); 4) After writing the image, insert the SD card into the available SD slot; 5) Insert a wooden toothpick or a Q-tip into AV/Reset input; 6) Click (kindly) and hold the toothpick and connect the TV Box power supply to the power entry; 7) Release the toothpick after 8-10 seconds. if the HDMI connector is plugged you should see the Armbian initial boot process Note: some TV Boxes don't need items 5, 6 and 7. I hope it helps.

Can I enable wifi (SV6256P) in H616 DDR3 Tv box https://github.com/paolosabatino/ssv6x5x/tree/master or build from old kernel 4.4.x

I'm planning on buying said Tv box in order to make it as a klipper host for a 3d printer since pi alternatives are too expensive nowadays.

I created this account just to thank you, man. Thank you so much, it worked perfectly here. Finally, my old TV box has another use besides collecting dust.

I wouldn't mind open source but the problem is their prices got bumped up because of the ram and storage shortages. It's why I'm asking if someone has managed to get armbian running on this specific Tv box model or a similar one that has an allwiner H618 chip at the very least.

DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Thank you! This is CSC Armbian for XT-Q8L-V10 boards, also known as Chiptrip Q8, Vsmart Q8, ENY 3288 Q8, etc... All source code has been merged into Armbian mainline project. I still keep my personal public Armbian fork for experimental features: https://github.com/paolosabatino/armbian-build Nightly images: download directory Quick installation instructions on eMMC: Build or download your preferred Armbian image from Download directory and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the sd card, then push the power button for 1 second (the led will turn blue) After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Boot from SD Card/USB stick (with Armbian already installed in eMMC, empty eMMC or no eMMC😞 Build or download your preferred Armbian image from Download directory; Burn the image on your SD card/USB stick; Plug the SD card/USB stick in the device; Push the power button for 1 second (the led will turn blue); After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Boot from SD Card/USB stick (with original firmware or other firmware): In case your box has the original firmware installed, use the Multitool to erase the internal flash. Don't worry, you will not brick your box: once the eMMC is emptied, the box will automatically boot from SD Card. This is called Maskrom mode and is common to all Rockchip devices. Instructions and download links for the Multitool are at the bottom of this post. After erasing the internal eMMC, just follow the "Boot from SD Card" procedure above and then you are fine. Boot priority: Newer images (those with mainline kernel >= 4.14.50) now support booting from multiple devices. Priority is fixed and boot devices are probed in this order: External SD card External USB storage device (Any USB Stick/Hard drive attached to USB host ports) Internal eMMC This way even if you install armbian to internal eMMC, you can still easily test different images booting from external devices. Experts notes: when armbian is installed into eMMC you get U-boot installed too in eMMC. This is important to know because the box won't boot in Maskrom Mode, but instead will always boot the embedded U-boot, no matter if you put an sdcard/usb stick. In practice the embedded U-boot is totally responsible for the boot priority. If you want to restore the Maskrom Mode, just erase U-boot from eMMC using this command: dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=8128 conv=sync,fsync Current status: Wireless: works. pretty fast and stable, signal is strong on my box; Bluetooth: works. I was able to transfer files and stream audio without problems USB ports: works, with autosuspend too. A quick benchmark show that transfer rate is quite good (topped at 34 MB/s) USB OTG: works in host mode. Transfer rate is very good (> 40 MB/s) MMC: works and is perfectly accessible as storage device. The images above with "eMMC friendly" have been tested and work when installed in eMMC using the standard armbian-config eMMC installer SDCard: works. legacy kernel is limited to high speed, while mainline works fine in UHS mode too. A quick benchmark with a Samsung EVO card shows the promised 48Mb/s read speed. Gigabit Ethernet: works, fast and reliably HDMI: works perfectly Serial: works Audio: both HDMI audio and SPDIF connector works IR remote: works on legacy and mainline kernels Reboot/Suspend process: rebooting the device is a working in progress, at the moment sometimes it works and sometimes it doesn't. Suspend is still not available. Hardware acceleration: everything which works for rk3288 boards applies here too. This guide or maybe the Media Testing Script will help you gain an hardware accelerated X11 and Chromium (using GL4ES I enjoyed Quake 2 from the start till the end, but also Quake and Quake III Arena work flawlessy, here a quick how-to to compile and install GL4ES) Multimedia: On mainline kernel 3D acceleration is provided by Panfrost driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Multitool: The Multitool is a small but powerful tool to easy operate on internal eMMC flash of RK3288 devices. Features: Backup the content of internal eMMC Restore a previously backed-up image to eMMC Erase the eMMC (via fast blkdiscard or zero-fill as fallback) Burn an Armbian (or LibreELEC) image directly on the eMMC Provide a recovery shell for manual maintenance Windows-friendly: everything is placed in a NTFS partition Image compression format autodetection: they are decompressed on-the-fly during burn process Network support for remote maintenance via SSH (instructions to access via network here) Instructions are simple: Download the image from here Burn it on an sdcard Open the NTFS partition with your preferred file manager Place the images you want to burn on the device in images directory (backups will be stored in backups directory) Plug the sd card in the RK3288 device Power the device and wait few seconds, the Multitool menu will appear on screen and can be navigated with the keyboard Last edit: 07/06/2020 - updated installation instructions

I'm trying to install Armbian on the Tanix Tx1 Soc Allwinner H313 Mini TV Box, but this box doesn't have an SD card slot. How do I install Armbian on this box without an SD card?

@Gwainer If you haven't bought a TV box yet, stay where you are. Direct your resources to supporting companies that keep open source running. Here is a list of where you should spend your resources. https://armbian.com/partners

Hello, I have some troubles with this TVBOX: it runs armbian and other distros correctly, using the meson-gxm-t95z-plus.dtb but sometimes wifi goes into kernel panic at boot, and when it does, the whole system becomes unstable (i.e. not rebooting, eth0 hangs...). I have extracted the original .DTB from the only firmware that exists for this box, the ancient 6.0 Marshmellow Android (I guess it's a 3.x kernel...). I attach it to this message hoping someone more expert than me can help in making it work ina more stable manner. I attach a picture of the board also, it reads "M8S". Box has 2GB ram and 16GB eMMC, brcmfmac wifi/bt and ZTE PHY chip. meson1.dtb

Hi, I would like to know if its possible to boot from SD card in my model of Android TV BOX. It does not have a reset button but has an update app. Its a Giga TV Box HD890 4K. It has an Amlogic CPU I do all the process of installing Armbian in the SD card, Android starts an update and it says: "Map file is too short". I really dont know what I have to do to enable multi boot. Installation is aborted. Im getting really upset for not being able to install Armbian. Any help to this issue would be really welcome. Sorry for my bad english