Search the Community

Hello guys i want to use linux on mx pro tv box from pendrive when i flash armbian image to pendrive and click the secret button on box nothing boots up can any one guide me on this thankyou:)

DISCLAIMERS (PLEASE READ): - Everything in this post is provided AS-IS. This is not an official Armbian-supported target, and neither the Armbian project nor I am responsible for any damage, data loss, or broken devices caused by flashing or testing these images. - As with other TV boxes, please assume there may be board variants, undocumented hardware changes, weak power supplies, and marginal NAND/eMMC chips. Test carefully before writing anything to internal storage. - Please keep discussion and support in the forum thread, not in the official Armbian issue tracker. Hi all, I would like to share my work on bringing Armbian to Rockchip RK3128 TV boxes. These boxes are quite old now, and I do not think they are especially common anymore. Still, I suspect a lot of people may have one lying around somewhere in a drawer, unused after Android updates stopped or the original firmware became too slow to care about. I also had several of them lying around at home, which is what pushed me to start this project in the first place. Since I could not find an RK3128 Armbian effort comparable to the RK322x one, I decided to try doing the port myself. Another important motivation was simply to reduce e-waste: if even some of these old boxes can be turned into usable Linux machines again instead of being thrown away, that already feels worthwhile to me. First and foremost, I want to send special thanks to @jock and @fabiobassa for their RK322x TV box work on this forum. Their work was the foundation that made this RK3128 effort much easier to start from. 1. Main references and source code: Blog post with the full write-up: https://chieunhatnang.de/p/building-armbian-for-rockchip-rk3128/ Follow-up post for kernel 6.6.89 work: https://chieunhatnang.de/p/building-armbian-for-rockchip-rk3128-part-2/ Build scripts and releases: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts RK3128 kernel 4.4 tree: https://github.com/chieunhatnang-personal/linux-kernel-4.4-rk3128-tvbox RK3128 kernel 6.6 tree: https://github.com/chieunhatnang-personal/linux-kernel-6.6-rk3128-tvbox 2. Current status At the moment I have two kernel lines: `4.4.194`, the older vendor-based line, which is already usable in practice `6.6.89`, the newer line, which allows these boxes to run a more up-to-date Armbian userspace What works in the current build: Custom U-Boot based on Rockchip U-Boot 2017.09 All four CPU cores, up to 1.2 GHz CPU frequency scaling and governors DRAM frequency control, both dynamic and fixed NAND, eMMC, SD card, and USB booting. The booting order is: USB >> SD Card >> NAND/eMMC (NAND and eMMC cannot be enabled at the same time because they share pins) OTG and EHCI/OHCI USB support Ethernet Wi-Fi support for SSV6051P, ESP8089, and several Realtek chips GPU acceleration UART1 and UART2, configurable Kernel `6.6.89` status in a bit more detail: CPU DVFS is stable after replacing the inherited/leakage-based OPP assumptions with a board-specific RK3128-safe table. The stable points I ended up using are `216 / 408 / 600 / 816 / 1008 / 1200 MHz` DMC / RAM devfreq works. In practice, simply enabling `dmc` works much better than I first expected, and boards can settle at different normal rates such as `396 MHz` or `456 MHz` GPU on `6.6.89` uses `Lima`, not the old Mali blob stack. That gives a maintainable Mesa/DRM path and hardware-accelerated OpenGL ES instead of depending on a legacy userspace blob VPU/video decode is still the weak point. I tried both `RKMPP` and `Hantro/V4L2` directions, but video processing is still limited, so I do not consider this a polished media-playback setup yet What does not work yet / known limitations: Bluetooth: not implemented or at least not validated, because I do not have a board with Bluetooth to test VPU / hardware video decoding is not in good shape yet SD card and SDIO Wi-Fi are currently using PIO mode on both kernel lines. This is slower than DMA, but stable enough for normal use 3. Image implementation I also made two RK3128 Armbian images based on existing RK322x Armbian images rather than building everything from scratch: Armbian 22.02: Based on the build provided by @jock, running kernel 4.4.189 Armbian 26.02: Based on the official Armbian build for rk322x, running kernel 6.6.89 In both cases, the idea was the same: keep the working RK322x Armbian userspace as a base, then replace the RK322x-specific parts with RK3128 ones, while the kernels themselves are based on Rockchip kernel sources. Compared with the original RK322x images, the RK3128 work mainly replaces or adds: boot.cmd / boot.scr changes so the boot flow can handle NAND and USB properly RK3128-specific Wi-Fi drivers and boot-time module loading logic rk3128-config a delayed Wi-Fi loader service RK3128-specific motd information the RK3128 kernel, DTB, and overlays For the `6.6.89` image specifically, there is some extra image-level cleanup and repackaging: remove the RK322x kernel / dtb / u-boot / BSP packages from the donor image pin those RK322x packages so they do not come back on upgrade install the RK3128 `6.6.89` Debian kernel packages rebuild the BSP package under the RK3128 name 4. Quick installation notes All required files are available from the releases page: The releaes page: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases Armbian 26.02 image: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases/download/kernel-6.6-armbian-26-v1.0/A26-release-20260415.zip Armbian 22.02 image: https://github.com/chieunhatnang-personal/RK3128-Linux-SupportingScripts/releases/download/kernel-4.4-armbian-22-v1.1/release-20260412.zip There are three installation layouts that are currently supported: 1. SD card only Pros: safest option, does not touch internal storage, easy to test and easy to remove, and if a board has an SD slot it can still be useful even when NAND/eMMC is completely dead Cons: slower than internal storage, and not every board has an SD slot Best for: first boot, testing, and boards where you want to keep the original Android install untouched 2. Full install to NAND / eMMC Pros: fastest and cleanest setup, uses the internal storage already present on the board Cons: overwrites the original Android install, and old NAND/eMMC may already be unreliable Best for: boards with healthy internal storage when you want a fully self-contained install 3. Hybrid install: bootloader on NAND / eMMC, rootfs on USB or SD card Pros: usually the most practical option for old TV boxes, works well when internal storage is only reliable enough for bootloader pieces, and can also help on boxes with problematic Android boot behavior Cons: more manual than the other methods, still depends on internal storage for the bootloader, and performance depends on the USB drive or SD card used Best for: boxes with weak or aging internal NAND/eMMC, or boxes where you want to avoid a full install to internal storage I describe each method in more detail below. 4.1. Install and boot from SD card Prepare: idbloader.img uboot.img trust.img rootfs.img Create an MBR partition table on the SD card, leave the first 16 MB empty, create one Linux partition, then write: idbloader.img to the raw device at seek=64 uboot.img to the raw device at seek=16384 trust.img to the raw device at seek=24576 rootfs.img to the first partition, not to the whole disk Example: DEV=/dev/sdX sudo parted -s "$DEV" mklabel msdos sudo parted -s "$DEV" mkpart primary ext4 16MB 100% sudo partprobe "$DEV" sudo dd if=idbloader.img of="$DEV" seek=64 conv=fsync sudo dd if=uboot.img of="$DEV" seek=16384 conv=fsync sudo dd if=trust.img of="$DEV" seek=24576 conv=fsync sudo dd if=rootfs.img of="${DEV}1" bs=4M status=progress conv=fsync sync I also provide a bootcardmaker.sh helper script in the same release directory to simplify this process. 4. 2. Full install to NAND / eMMC Prepare: rkxx_loader_vx.xx.xxx.bin parameter.txt uboot.img trust.img rootfs.img Then: Boot the board normally Connect a USB cable to the OTG port Open RKDevTool v2.69 In Advanced Function, erase the first 0x10000 sectors with Start LBA = 0x0 and Count = 0x10000 Press ResetDevice Wait for the board to return in MaskROM mode Go to Download Image Flash Loader, parameter, U-Boot, Trust, and rootfs 4. 3. Hybrid install: bootloader on NAND / eMMC, rootfs on USB or SD card This is the layout I use most often, and in practice it is probably the most useful one for old TV boxes. It is especially useful when internal NAND/eMMC is still good enough for Loader / parameter / U-Boot / Trust, but not reliable enough for a full root filesystem. A common symptom on these old boxes is that Android starts to boot and then hangs, or that the internal storage is simply too unreliable to trust with a full install. In this hybrid layout: Internal NAND/eMMC stores Loader, parameter, U-Boot, and Trust The root filesystem lives on USB or SD card Important: rootfs.img is a filesystem image, not a full disk image Write rootfs.img to a partition such as /dev/sdX1, not to the whole device Tools like BalenaEtcher are the wrong fit for this particular image layout Example: sudo dd if=rootfs.img of=/dev/sdX1 bs=4M status=progress conv=fsync sync 4.4. Post-install configuration After the board boots successfully, you can configure it either from the local console over HDMI or remotely over SSH if Ethernet is connected. Default login: user: root password: 1234 The first login will ask you to change the password. After that, run: rk3128-config This is the board-specific configuration tool for enabling and adjusting hardware features that may differ between RK3128 boxes. The most important options are: Wi-Fi chip selection RAM dynamic frequency: disabled by default. Enabling it can improve performance, but on some boards it may cause kernel hangs. If that happens, switch it back to disabled SD card storage enablement when booting from another device Display resolution OTG mode selection 5. Testing feedback is welcome If anyone here has RK3128 boards and wants to test, feedback would be very useful, especially for: Board photos and PCB markings Whether the board uses NAND or eMMC Boot method that works: SD, USB, NAND, eMMC Which Wi-Fi chip is present Serial logs, dmesg, and failure reports If there is enough interest and enough board coverage, I would be happy to keep improving this, cleaning it up further, and making it easier for other people to test. 6. Credits - @jock and @fabiobassa for the RK322x TV box work on the Armbian forum, which provided the main starting point, the images and practical reference for this RK3128 effort - Rockchip for the original kernel code base used as the foundation for both kernel lines

@Sergioclr Well that is the u-boot root directory. Where the main Makefile is located. I added my own root_key.pem in the patch. You don't have to generate one. The root_key.pem for Allwinner H616/618/313 devices is not a single, universal file, but rather an RSA private key file used for signing bootloader images (TOC0) in secure boot implementations. In many commercial H616-based TV boxes, Secure Boot is enabled by the manufacturer, but the efuses (which store the root key hash) are not permanently locked, allowing the use of custom keys openssl genrsa -out root_key.pem

This week, Collabora is at the YouTube Device Partner Summit in Tokyo showcasing our ongoing work with YouTube, notably on their TV app and the RDK platform, which has resulted in the RDK's integration as a core platform for Cobalt development. View the full article

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!

Debug (Phoenixsuit) original software loaded (emmc) Photo from TV Box recovery menu: Thanks in advance.

@savznkvo if you followed my compile.sh steps from above, you should have a file Armbian-unofficial_26.05.0-trunk_Orangepirv2_trixie_current_6.18.21_minimal.img in ./output/images ready to be flashed to your SD card. Insert and boot. At this point you need TV / Kbd or UART to finish the wizard (set root PW etc). Now start armbian-install (see screen shot). Transfer *.img to /dev/nvme0n1, use netcat or similar. Then power down, remove SD and eMMC (if plugged). Restart from NVME, now you have to complete first time wizard again. Tested with current main and it works flawlessly. Addon: if you apt-get dist-upgrade, a newer kernel package from Armbian nightly builds is installed and the bcmdhd wifi kernel driver module is recompiled - which needs some time. This will DOWNGRADE from 6.18.21 to 6.18.20 currently - this works as designed. HTH // Sven-Ola

@savznkvo Installing headless (blind / via network) on a board this new will fail probably. Get a TV and connect an HDMI display or get a serial adapter and connect that for debug. I'll check later with a spare NVME, but I am pretty sure it works (provided, that you compiled the correct firmware). HTH // Sven-Ola

First of all thanks to the people maintaining armbian for helios64. I recently upgraded (well I reinstalled) to trixie and everything mostly runs stable for me. However I have a problem with the 2.5GB adapter. It is connected to a 2.5GB switch and when for example running iperf3 I get proper results close to 2.5 GBit. So in general it seems to be running ok. I have a DLNA server (minidlna) running on that machine and when I stream from my TV (streaming via VLC from my laptop triggers the same problems) the network connection drops for a moment and works again after a few seconds (which you can guess is super annoying when watching something). I am not sure what exactly is triggering this. most of the time the network is super stable but during streaming I get hickups. This is what my kernel log spits out when this is happending: ``` Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f10 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f20 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f30 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f40 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f50 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f60 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f70 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f80 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f90 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8fa0 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0 Apr 09 17:45:59 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: NETDEV WATCHDOG: CPU: 0: transmit queue 0 timed out 5152 ms Apr 09 17:45:59 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx timeout Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2 Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2 Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2 Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2 Apr 09 17:46:02 hermann-walter kernel: r8152-cfgselector 2-1.4: reset SuperSpeed USB device number 3 using xhci-hcd ``` the usb related messages are not always there but the r8152 related messages are always there. I found a similar problem here: https://github.com/openwrt/openwrt/issues/22130 I tried replacing the firmware but that didn't help and I later found out that the helios64 uses a different firmware so that explains why it didn't help: ``` Apr 10 05:48:30 hermann-walter kernel: r8152 2-1.4:1.0: Loaded FW: rtl_nic/rtl8156a-2.fw, sha256: 7b50f4a307bde7b3f384935537c4d9705457fa42613eb0003ffbc4e19461a1e0 Apr 10 05:48:30 hermann-walter kernel: r8152 2-1.4:1.0: Loaded FW: rtl_nic/rtl8156a-2.fw, sha256: 7b50f4a307bde7b3f384935537c4d9705457fa42613eb0003ffbc4e19461a1e0 ``` does anybody know what is going on? I am quite sure that the problem wasn't there before the upgrade (but I might be mistaken because I only started observing the helios64 again after the upgrade. also it seems to be related to the amount of network traffic going on. i.e. lower bitrate streams seem to not trigger the problem). Streaming via the 1GBit NIC is working fine.

3D Graphics Acceleration on T95N (A98X Jackbox) - RK3229 with 2GB RAM / 16GB eMMC - Educational Project for Schools Hi, I’m working on a project using a specific TV Box model (A98X Jackbox) to repurpose these boxes as low-cost computers for schools. The goal is to provide students with a platform to use AI tools and basic productivity, but I need better browser rendering. Hardware Specs (Confirmed via board teardown and logs): Board ID: T95N-RK3229_512X4_V1.5 CPU: Rockchip RK3229 RAM: 2GB (Confirmed via free -m) Storage: 16GB eMMC (SanDisk SDIN9DS2-16G) OS: Armbian 21.08.8 Bullseye (Legacy Kernel 4.4.194-rk322x) What I have done so far: Installed the Minimal image and set up LXDE with LightDM. Optimized the system (Governor set to performance, swappiness set to 10). Ran glxinfo -B which confirms it's currently using llvmpipe (Accelerated: no). Tried searching for Mali drivers via apt, but armbian-config is not available in the repositories for this specific build/architecture. Verified Wi-Fi functionality (working fine with LED config 2 via rk322x-config). The system is stable and surprisingly fast thanks to the 2GB RAM, but the CPU is struggling with 100% spikes during browser rendering (Epiphany WebKit) because it lacks GPU acceleration. Question: Is there a way to enable Mali-400 MP2 drivers for X11 on this Legacy 4.4 kernel? Are there any specific packages, blobs, or workarounds to get hardware acceleration working and replace llvmpipe? I’m available to run any tests or provide further logs if needed. Thanks for this amazing project!

Hey everyone, I’ve cross-flashed a MXQ 4K 5G (Allwinner sun8iw7p1 / H3) firmware onto a different H3-based TV box. Everything works surprisingly well, except for the IR Power-On/Wakeup. Since the hardware is different, my box's IR receiver is sending a scancode that the MXQ firmware doesn't recognize as the "Wakeup" key. Because this is an Allwinner (sunxi) build and not Rockchip, I know I can't just edit a remote.conf file in the system partition to fix the cold-boot power button. My questions: Where exactly is the Hardcoded IR Wakeup/Power-on scancode stored in these Phoenix-style Allwinner images? Is it buried in the Device Tree Blob (DTB) under a specific IR controller node, or is it hardcoded in the U-Boot/SPL? If I unpack the boot.img or kernel, what hex patterns should I search for to find the Power-key scancode table? If anyone has experience patching the primary boot scancode for sun8i chips, I’d love some guidance on which partition/file to hex-edit. Thanks!

Newbie on Armbian. I have an Allwinner H313 (confirmed) box that I want to to use as a basic Samba server. CPU:Allwinner H313Quad Core ARM Cortex A53 GPU:Mali-G31 OPenGL ES3.2 Memory:2GB Flash:16GB OS:Android 10.0 The actual firmware is a secure image and, no matter what procedure I do, I can't load any other image but the secure one. Debugging shows that 'fastbootd' has the "secure" flag set. My intention is to create a basic secure arm64 Debian image but I am having a hard time in doing so. Any ideas (specific Wiki, procedures) on how to create the secure image or "reset" the "secure" flag will be very appreciated. Thanks in advance.

And the email system for is emailing with me erroneos info about bedno report 2x a day, so call off the quard dogs, it been solved without any help from this forum. you've been yelling about dhcp w/out once offering me a single clue as to how I should configure it even when I showed you the results. FYI I have been doing odd things with little machines for a lot longer that most of you have been breathing on your own starting with an rca 1802 in 1978. Do any of you have a track record that long? That bit of production tooling for a medium market tv station was still in use 20+ times a day when the station burned to the ground in the late 90's. I prefer to call it efficiency since most production equipment at a tv station is so heavily used & long since worn out before the IRS lets them amortize the cost. I am also a CET, a test 95% of the EE's out there cannot pass. I call a backup server that draws 19 watts at full song in the middle of backing up 8 machines here, efficient. Took me a while to figure it out the hardware and around $1500 in hardware. But it works as fast as my cat6 wired local net can run.

I have an H50-labeled tv box with a different board (T98-3318-V2.3) but with exactly the same problem - no HDMI even though all the software debug traces show that everything video-related gets called and works. I first tried to make it work 5 years ago and failed and a few months ago I revisited it just to see if I can make it work now in the age of AI. I made a really deep dive into reverse engineering it. I rooted the original Android firmware and dumped anything I could, extracted and analyzed with Ghidra the vendor u-boot and kernel (wasn't particularly helpful) and finally managed to execute the u-boot binary in Renode by emulating a lot of hardware stuff with code or by simply replacing functions with successful returns all the way to the point of u-boot displaying the splash screen and with various hooks and warnings about peripheral accesses I collected a comprehensive trace of everything that u-boot was doing, and in that trace, the AI noticed a certain GPIO access and suggested replacing this vcc-host-vbus { compatible = "regulator-fixed"; enable-active-high; gpio = <0x74 0x00 0x00>; pinctrl-names = "default"; pinctrl-0 = <0x76>; regulator-name = "vcc_host_vbus"; regulator-always-on; regulator-min-microvolt = <0x4c4b40>; regulator-max-microvolt = <0x4c4b40>; vin-supply = <0x77>; phandle = <0x100>; }; with this vcc-display-en { compatible = "regulator-fixed"; gpio = <0x74 0x00 0x01>; pinctrl-names = "default"; pinctrl-0 = <0x76>; regulator-name = "vcc_display_en"; regulator-always-on; regulator-boot-on; regulator-min-microvolt = <0x4c4b40>; regulator-max-microvolt = <0x4c4b40>; vin-supply = <0x77>; phandle = <0x100>; }; in the standard rk3318-box.dts which made HDMI work.

Hey everyone! I have a TV Box labeled “In Xplus”, running on an Allwinner H313 (most likely a generic/rebranded device). I was able to install Linux on it using Armbian 26.2.0-trunk (Trixie). The system boots normally, but I’m facing network issues: - Wi-Fi is not working (no interface detected) - Ethernet is also not working (only interface is lo) So basically, the system runs fine, but I have no network connectivity at all. My questions: - Is this a current limitation of Armbian support for the H313? - Is there any specific DTB or patch that could fix Wi-Fi/Ethernet? - Is there a more stable Armbian version or another distro with better support? - Has anyone managed to get networking working on this chip? Any help or shared experience would be greatly appreciated. Thanks!

Hi all, I have an RK3318 TV box (A95X R2_V20). The front panel controller is TM1628. I’m running Armbian 23.11.1 with kernel 6.19.0‑edge‑rockchip64. Problem: tm16xx is not enabled in this kernel (CONFIG_TM16XX_* not set), and there is no rk3318x-config in this image. I tried to locate tm16xx sources in current Armbian kernel trees and mainline, but the driver is missing, so I can’t build it from the local headers. I have active Docker projects (avito-bot) on this box and don’t want to reinstall the system, and previous two reinstalls ended with apt issues, so I’d prefer to avoid a fresh image. Question: Is there a known external tm16xx driver repo (or patch) that can be built as an out‑of‑tree module for RK3318? If yes, could you point me to the source and any required device‑tree overlay/pin mapping for TM1628? I already posted board photos and dtb above (my post is still unanswered), so please refer to that if needed. Thanks!

Hello. I have a problem that's been driving me crazy, and I think I'm not the only one. I'm using Armbian version v25.05.0 for Aml.S905x running Armbian Linux 6.12.19-ophub Debian stable (bookworm), and I managed to install RealVNC Connect, for which I have a license. The problem I'm having, and I can't find a solution, is that by default the GDM3 desktop launcher uses Wayland, and when I connect externally to the server, I only get a black screen with a message saying "the desktop cannot be displayed at this time." I'm using GNOME, and I've tried different desktop environments, but they never work, even after selecting them from the gear icon. It just acts like it's going to launch and then returns to the user's home page. It doesn't matter if I use Xorg; no desktop environment ever loads. Only GNOME and GNOME Classic work. If I modify the /etc/gdm3/custom.conf file by deselecting Waylan, I get a black screen and can't even log in. It's a vicious cycle that prevents me from using this server that I like. I've also tried installing other screen launchers like LightDM, but they don't work on my system; the startup process either freezes or I get a black screen. I'm quite desperate. The device where Armbian is installed is an Amlogic TV Box, which is otherwise working perfectly, but this server issue is really frustrating me. Could anyone offer a solution so I can use this server that was working before? Thank you very much.

Hi all, I’m trying to enable the front VFD/LED display on an RK3318 TV box. OS: Armbian 23.11.1 Jammy, kernel 6.18.10-current-rockchip64 DTB: rk3318-box.dtb (fdtfile=rockchip/rk3318-box.dtb) In DTB I found: fd628_dev { compatible = "fd628_dev"; fd628_gpio_clk = <0x7a 0x10 0x00>; // bank2, offset16 fd628_gpio_dat = <0x7a 0x0f 0x00>; // bank2, offset15 }; I built linux_openvfd and added an openvfd node in DTB: openvfd { compatible = "open,vfd"; dev_name = "openvfd"; status = "okay"; }; Module loads, /dev/openvfd appears with: vfd_gpio_clk=2,16,0 vfd_gpio_dat=2,15,0 vfd_gpio_stb=2,19,0 vfd_display_type=0,0,0,0 vfd_chars=0,1,2,3,4,5,6 vfd_dot_bits=0,1,2,3,4,5,6,0 dmesg shows: OpenVFD: Select FD628 controller OpenVFD: SPI 3-wire interface initialized (LSB mode) /sys/class/leds/openvfd exists, but no indicators light up. Tried multiple display_type values and STB pins (bank2 offsets 18–22 + other banks) — still no output. Question: Does anyone know the correct GPIO pins (CLK/DAT/STB) for rk3318-box VFD, or a working driver/service for FD628/FD650 on this board? Any confirmed configs for RK3318 boxes would be greatly appreciated. I’ve been working on this for ~2 weeks and tried multiple configs/drivers without success. Thanks!

Those are not the correct instructions. Please follow the instructions linked off of the download page: https://www.armbian.com/amlogic-s9xx-tv-box

Hey there, Title: Need compatible firmware / loader for XR8223518K-V1.0 (RK3518) TV box Message: Hi, I’m trying to recover a TV box with this exact mainboard: Board code: XR8223518K-V1.0 SoC: Rockchip RK3518 Symptoms: device only shows blue LED no HDMI output device can still enter MASKROM / Rockusb mode What I already tested: RKDevTool detects “Found One MASKROM Device” using my current MiniLoaderAll.bin + ExportImage.img fails with: “Download boot fail. Please check DDR.” So I believe I need: the exact stock firmware for this board or a compatible RK3518 MiniLoaderAll.bin / loader for this exact board / DDR configuration If anyone has firmware, loader, dump, or files for XR8223518K-V1.0, I would really appreciate it. Thanks.

@Nick A I have one of those T95 H616 AXP313a tv boxes. I have successfully compiled a mainline U-Boot image and it boots fine, all with UART input/output, but none of the images from your github repo work. I only managed to boot MiniArch images up to 6.19 kernel but I couldn't get HDMI, Ethernet, WiFi or Bluetooth to work at all. Got any idea what could be missing? I can help in debugging if you'd like. I attached the extracted and decompiled DTS from the stock Android 10 firmware of the device. Thank you extracted.dts

Subject: X88MAX RK3328 - Cannot boot from SD/USB, need help installing Armbian Hello Armbian Community, I'm trying to install Armbian on my X88 RK3328 TV box but facing multiple issues. Need your expert help! Device Information: Model: X88MAX.p2.0.01.d4 SoC: Rockchip RK3328 Android Version: Android 9 (SDK 28) Board: Blue PCB (Hugsun design similar to T9) Storage: 4GB RAM + eMMC Buttons: Power button only (no visible reset button) What I've Tried: 1. SD Card Boot: Downloaded: Armbian_community_26.2.0-trunk.606_Rk3318-box_trixie_current_6.18.18_minimal.img.xz Downloaded: multitool_rk3318-3328.img Flashed to Netac SD card using BalenaEtcher (verified) SD card is detected in Android environment Problem: Box always boots Android, ignores SD card completely 2. USB Boot: Flashed Multitool to USB flash drive Problem: Same result - boots Android, ignores USB 3. Reset Button Method: Tried holding reset button (inside AV port) while powering on Problem: No change, still boots Android 4. Rooting Attempts: Tried KingRoot - stuck on "checking state" forever Device confirmed NOT ROOTED (Root Checker app) Problem: Cannot root to install from Android 5. Maskrom Mode: Have AndroidTool v2.38 ready Problem: PC shows "No Devices Found" when trying to enter Maskrom Current Status: ✅ SD card slot works (Android detects it) ✅ Multitool files accessible on SD card ✅ Have all necessary images downloaded ❌ Cannot boot from SD or USB ❌ Cannot root Android ❌ Cannot enter Maskrom mode My Goal: Install pure Armbian (not Android + Linux apps) for better performance and native Linux experience. Questions: Does anyone have X88 RK3328 working with Armbian? If yes, what method did you use? Is there a specific Armbian build for X88 boards? The generic Rk3318-box image doesn't boot. How to enter Maskrom mode on X88? PC shows "No Devices Found" - am I missing something? Can I convert Armbian .img to Rockchip firmware format for USB Burning Tool? Any X88-specific instructions or device tree files I should use? What I Have Ready: ✅ Armbian image (Rk3318-box minimal) ✅ Multitool image ✅ AndroidTool v2.38 ✅ USB-A to USB-A cable ✅ Willing to backup original Android first Any help or X88-specific guidance would be greatly appreciated! Thanks in advance! 🙏 Device: X88MAX.p2.0.01.d4 SoC: RK3328 (Chip Tag: 33 32 32 48, Flag: RK322H) Storage: Samsung eMMC 64GB FlashID: 45 4D 4D 43 20 Status: Successfully in LOADER mode via RKDevTool v2.86 Android: Backed up and ready Problem: - SD/USB boot ignored by bootloader - Android not rootable (KingRoot fails) - Need Armbian in Rockchip firmware format What I Have: - Device in LOADER mode ✓ - Full Android backup ✓ - RKDevTool v2.86 working ✓ - Armbian_community_26.2.0-trunk.606_Rk3318-box_trixie_current_6.18.18_minimal.img.xz What I Need: - parameter.txt for X88 RK3328 - Armbian partitions in Rockchip format - Or .update file for X88 Tag: @jock Anyone successfully flashed Armbian on X88 RK3328?

Hi, i have amlogic s805 tv box from mxq, how do i run armbian onecloud? bc none of this helped me.

Hay, could u guys tell me how to install a custom ROM for my tv box that's using h616. I'm a absolute bigginer to this But I tried pressing the power button, to get into the downloader mode but looks like that doesn't work

@Nick A could you explain this a bit to me? i'm actually quite new to this and i just got this TV box the only thing i managed to do was installing a software version from a guy who debloated and checked it for spyware. also when i use the reset button in the av jack it just ignores everything and recovers from an internal image or something.