Search the Community

(sorry for bad english) i'm looking to boot in an armbian bookworm by sicxnull on my mxq pro 4k 5g, i checked the aida64, it showed the allwinner h313, i tried the toothpick method to the recovery menu (which have a boot option?) i'm novice to android 😕 by the way here are the images of the tv box pcb:

­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 thread is to give stable and mature long-term range support to rk3318/rk3328 found in many tv boxes in Armbian project as Community Supported Configuration (CSC). The current work is mainlined into Armbian project, but your mileage may vary; most recent developments live on my personal fork on github -> here <- Important notes: is just a personal opinion, but apparently widely supported, that rk3318 chip is not an official rockchip part. They probably are scrap rk3328 parts which have not passed conformance tests but are sold anyway to tv boxes manufacturers. They don’t reach the same operating frequency of the rk3328, have much higher leakage currents (and thus higher temperatures) and often the boards they are installed on are low quality with low quality components, in fact a very very common issue is the eMMC failure due to bad parts and bad soldering. So said, I personally suggest not to buy any rk3318 tv box, but instead find a properly supported SBC (Single Board Computer) if you need a reliable product. In the unfortunate case you already have such product, this thread may help you have some fun with them. What works: • Works on RK3318 and RK3328 TV boxes with DDR3 memories • Mainline u-boot • Mainline ATF provided as Trusted Execution Environment • All 4 cores are working • Ethernet • Serial UART (configured at stock 1.5Mbps) • Thermals and frequency scaling • OTG USB 2.0 port (also as boot device!) • EHCI/OHCI USB 2.0 ports and XHCI USB 3.0 ports • MMC subsystem (including , SD and sdio devices) • Hardware video acceleration (fully supported via RKMPP on legacy kernel, support via hantro and rkvdec kernel driver on mainline) • Various WIFI over SDIO are supported • Full acceleration on legacy kernel and mainline kernel • U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal ; you can install u-boot (and the whole system) in the internal and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the clock pin on the PCB. The procedure is explained here for rk322x, but for rk3318/28 is the same. In most of the rk3318/28 boards, shorting the clock pin is difficult or impossible because eMMC are BGA chips with no exposed pins. Pay double attention when burning something on the internal flash memory and always test first the image booting from the sdcard to be sure it works before burning anything in internal flash. This is a list of posts where forum users have been able to spot the eMMC clock pin to trigger the maskrom mode: H96 Max+ (board signature: RK3318_V1.4) by @Gausus X88 PRO 10 (board signature: X88_PRO_B) by @mathgaming HK1 Max (board signature YX_RK3318) by @Constantin Gatej Ninkbox N1 Max RK3318 by @enigmasphinx Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Legacy kernel: If you need multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to /TVB/ boards and select "rk3318-box" from the list. Prebuilt images: Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Multitool: Multitool - A small but powerful image for RK3318/RK3328 TV Box maintenance. Download it from here Quick installation instructions on eMMC: Build or download your preferred Armbian image 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 power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. 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 rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in , the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal flash; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; 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 rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal ; Congratulations, Armbian is running from SD Card! Tutorial - How to install Armbian on your TV Box (by @awawa) : https://www.hyperhdr.eu/2022/01/tv-box-mania-i-part-x88-pro-10.html A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal The Multitool does not boot / How to burn image directly on eMMC: Some boards have the sdcard attached to an auxiliary (called also sdmmc_ext or external) controller which is not the common one. Forum findings declare that those boards are not able to boot from sdcard with stock firmware and they neither do in maskrom mode: the stock firmware always boots even if you put the multitool on sdcard. In such case, burning images directly on eMMC is the only way to have a working Armbian installation. You can follow these instructions by @fabiobassa to burn images directly on eMMC: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=130453 Notes and special hardware: Script to change DDR memory frequency here Wireless chip AP2734, SP2734, HY2734C and similars: they are clones of AmPAK AP6334 which is combo wifi + bluetooth of broadcom BCM4334/B0 chips. You may need a special nvram file, instructions by @paradigman are here Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk3318 into armbian would not have begun without his support! @hexdump for his precious support in early testing, ideas and suggestions @MX10.AC2Nfor his patience in testing mxq-rk3328-d4 board support All the rockhip64 maintainers at Armbian project who have done and do most of the work to support the platform

🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! This Armbian adventure was summarized in my Public Github Repository. H96 MAX V56 RK3566 8gb Ram SD-Card unofficial images: Tutorial SD-Card Version v0.5 ARMBIAN BETA unofficial H96 MAX V56 RK3566 8gb EMMC Chainloader to mainline HotnikQ unofficial images: Tutorial EMMC Version V0.7 ARMBIAN BETA unofficial H96 MAX V56 RK3566 8gb EMMC Mainline Boot Hzdm unofficial images: Tutorial EMMC Version v0.8 ARMBIAN unofficial H96 MAX V56 RK3566 8gb EMMC Mainline Boot Hzdm unofficial images: Tutorial EMMC Version v0.9 ARMBIAN BETA unofficial H96 MAX V56 RK3566 8gb EMMC Chainloader to mainline HotnikQ unofficial images: Tutorial EMMC Version v1.0 ARMBIAN unofficial H96 MAX V56 RK3566 8gb EMMC Hzdm Mainline Boot Custom unofficial images: Tutorial Build Your own Armbian EMMC unofficial image H96 MAX V56 RK3566 EMMC Raspiblitz HotnikQ unofficial images: Tutorial Build Raspiblitz on EMMC Armbian Bullseye unofficial H96 MAX V56 RK3566 8gb EMMC Hzdm Mainline Boot unofficial images: Tutorial Build Your own V1.1 Armbian EMMC unofficial image H96 MAX V56 RK3566 8gb Vendor Kernel 5.1.16 Tutorial Build Your own Armbian Rockchip Kernel vendor Kernel 5.1.16 Armbian Joshua Riek Ubuntu Rockchip Images kernel 5.1 H96 MAX V56 RK3566 8gb Vendor Kernel 6.1.43 Tutorial Build Your own Armbian Rockchip Kernel vendor Kernel 6.1.43 Armbian Joshua Riek Ubuntu Rockchip Images Kernel 6.1 H96 MAX V56 RK3566 8gb EMMC Ning Mainline Kernel: Armbian EMMC official image Armbian Desktop Gnome kernel The Latest official Debian BookWorm Server Kernel Minimal The Latest official Desktop Test Images: Pre-Build Desktop 22.04 Armbian Test Image (PT-BR) Community Official Images: Armbian_community_25.2.0-trunk.410_H96-tvbox-3566_bookworm_current_6.12.11_minimal.img.xz Armbian_community_25.2.0-trunk.410_H96-tvbox-3566_noble_current_6.12.11_gnome_desktop.img.xz Bleding Edge images: Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_noble_edge_6.13.0_cinnamon_desktop.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_jammy_edge_6.13.0_cinnamon_desktop.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_bookworm_edge_6.13.0_cinnamon_desktop.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_noble_edge_6.13.0_minimal.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_bookworm_edge_6.13.0_minimal.tar.xz Armbian-unofficial_25.02.0-trunk_H96-tvbox-3566_jammy_edge_6.13.0_minimal.tar.xz Joshua-Riek Vendor Images: Joshua-Riek-ubuntu-22.04-preinstalled-desktop-arm64-h96max-v56 Joshua-Riek-ubuntu-22.04-preinstalled-server-arm64-h96max-v56 Joshua-Riek-ubuntu-24.04-preinstalled-desktop-arm64-h96max-v56 Joshua-Riek-ubuntu-24.04-preinstalled-server-arm64-h96max-v56 Software description: V0.5 = @armbian The Armbian SD card image "Compiled From Armbian Project" V0.8 = @hzdm Project with Mainline Bootloader "Boot the 64gb Emmc Armbian with Mainline Rockchip" V0.9 = @hzdm Release Mainline Bootloader "Boot the 32gb and 64gb Emmc Armbian with Mainline Rockchip" V1.0 = @hotnikq The Armbian SD card inside the Android Legacy Rockchip Image "Two Original Glued Images: Android boot for Linux" V1.2 = @ning Release Device Tree and Bootloader to longterm 6.6.27 Kernel "Boot with Mainline Rockchip" V1.3 = @Hqnicolas Github PR Enable h96 Rk3566 TV-Box device for Kernel 6.8 V1.4 = @pocosparc Github PR Enable OpenVFD and IR controller V1.5 = @dfahren Github PR Update U-boot 2025.01 for Kernel 6.12+ Video drivers: https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html Wifi Driver: https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view?usp=sharing UEFI: https://github.com/hqnicolas/h96v56_uefi/releases/tag/v1.2.1 Or Just Live install Wifi Driver: cd /lib/firmware/brcm/ sudo wget https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml/raw/master/firmware/brcm/fw_bcm4335b0_ag.bin sudo ln -s fw_bcm4335b0_ag.bin brcmfmac4335-sdio.h96-TVbox,rk3566.bin sudo reboot now nmcli dev wifi sudo rmmod brcmfmac_wcc brcmfmac brcmutil modprobe brcmfmac Topic description: This topic aims to demonstrate the path taken to the Armibian EMMC solution. In our path we create a lot of ready-to-use ROM files, some users burn an use this images without learning with the Linux compilation process. the name of the topic is efforts but that's no effort at all, you should try compile your own images. Device Capability Test: Using Rockchip SoCs NPU. Drivers: https://github.com/rockchip-linux/rknpu2 User Guide: https://github.com/rockchip-linux/rknpu2/blob/master/doc/Rockchip_RKNPU_User_Guide_RKNN_API_V1.4.0_EN.pdf OpenCV: https://opencv.org/blog/2022/11/29/working-with-neural-processing-units-npus-using-opencv/ A discussion on Reddit: https://www.reddit.com/r/OrangePI/comments/12b3jmj/accessing_the_npu_on_the_orange_pi/ Transformers models: https://github.com/usefulsensors/useful-transformers Usage: https://www.crowdsupply.com/useful-sensors/ai-in-a-box/ Usage: https://youtu.be/pN8mKZ5wpdQ

Has anyone been able to use the remote control that comes with the tv bos under Armbian? Does it reqire additional driver(s)? I want to run Kodi (or any better mediacenter) under Armbian.

Currently working on a build for this device. It boots and is about 90% functional on 6.6 and 6.7 Kernel https://github.com/sicXnull/armbian-build/tree/X96Q-TVBOX-LPDDR3 Working - Desktop - Ethernet - Wifi Not working - DTS could use some work. Right now it does not detect internal EMMC so installing to EMMC is not an option. - Likely other things i've missed. I've uploaded two images to my git. Full w/Mate Desktop Minimal/Server Feel free to compile this yourself if you don't trust my images, it's encouraged. Changes are on the X96Q-TVBOX-LPDDR3 Branch Full W/Desktop ./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm Minimal/Server ./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm

Hello, it's been months since I've said to myself "I've got to get a cheap TV box, since SBCs are now so expensive and my Raspberry Pi 3 is showing its I/O and memory limits", and I think I'm now finally forced to, because 2 weeks ago my Pi started to show some strange (load/power) issues, and even started to emit a funny burned smell (!!!), slowly with hours of continuous (even if light) uptime. It still works, but I fear that some component is dying, maybe having kept an USB HDD connected for months has fried something: the smell strangely is always coming even after changing PSU and disconnecting the HDD (apart from that, there are now no other connected peripherals except for the microSD), and it appears to come from the micro-USB port section of the board. Point is, I don't trust this thing to keep working 24/7 after this incident, I have to get a new small homeserver. Indeed, I mostly used the Pi as a server these years, and after reading "Status of Armbian on TV Boxes" I think I can at least give a shot at trying to buy a TV box as a Pi substitute for this kind of task. Since today and tomorrow the Amazon Prime Day takes place, and I'm finding some more-decent-than-usual deals (yes, I did check with Keepa, some boxes are really on discount today), I thought I might as well buy now and stop postponing. So, my requirements are about the following, and they seem easy enough to get on today's TV boxes with Android, but I don't know what happens if I was to desire Armbian: 4 GB RAM or more (unlike the Pi's 1 GB) USB 3.0 ports (unlike the Pi's 2.0), to add big additional storage with minimal bottleneck (but maybe we don't rely on an USB-Y cable anymore if connected to a separate PSU...) WiFi, preferably 5 GHz, because I don't have a good place to put the box near my router, and can't have Ethernet cables going from one corner of the room to the opposite... Now, I probably don't really need bare-metal pure Linux, since the majority of the software I have to run can do so in a proot container in Android (in the past I did use an half-broken Android smartphone as a server actually), but I would have to sacrifice Docker (which sometimes is really useful) and also Pi-Hole (since to work it has to bind on a privileged port, and I wouldn't bet on being able to root these Android boxes), so I am at least making an attempt at buying something that can run Armbian. From what I'm gathering from the forum, the best choices are usually Rockchip boxes (most supported), next come those with some Amlogic SoCs (driven by a small community), and lastly there are some Allwinners. However, it's a bit chaotic trying to infer what's the best choice from browsing semi-random threads, and that's why I'm asking any potential TV box expert (now that's hyperspecialization!) what could be the best choice among what I found for an acceptable price (some are on Prime Day discount, some aren't but still have a good price): X88 Pro 10, X88 Pro 12: RK3318 chip, I understood that it's good support-wise (https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/#comment-122715), WiFi works too if I'm reading correctly, but hardware-wise it's kind of crap, wastes energy, and can fail. Oh well, I'll be honest: I know I should be worried, but I don't know how much worried! X88 Pro 13: RK3528, is it a very new SoC? I can't find anything on the forum about it, and so I fear there is no support. Magcubic thingy, Magcubic 8K Ultra HD, Tanix thingy (Allwinner H618); T95H, Q Plus (Allwinner H616): It appears these are not well supported, there are some experimental builds around but many things are broken. Would be happy to discover that I'm wrong on this and support is actually good for my standards, though. TUREWELL T95 Max+: Amlogic S905X3, here I kinda don't understand at all if there's enough good community support or not, but there are many threads about issues and solutions. To be clear: I can tinker if something doesn't work out-of-the-box with Armbian, I have a bit of experience with embedded devices like routers or Android smartphones so I think I could solve minor issues if they arise, but I'm really looking for a quick replacement for my Raspi and don't want to spend more than a few days after getting the box to make Armbian work. That's why I'm thinking so hard on getting a device with good compatibility. Anyways, thank you to anyone who comes here to help, I would appreciate it. If no help comes, I think I will bet on a box with the RK3318 and hope for the best.

TV Box Name MXQ MBX Model M201 CPU (example: amlogic s805 Meson 8B 4 cores 1.5 Ghz Armbian build file name:Armbian_5.67_Aml-s805_Ubuntu_bionic_default_3.10.108_desktop_20181207 DTB file used: Kernel Version:3.10.108 #14 SMP preenpt Distribution Installed (focal, buster, etc):Bionic Working Ethernet not tested Max Ethernet Speed that works (100/1000): Does wifi work Yes sort of, makes breaks connection continually, it will download updates Does bluetooth work (Yes/No):NA I don't know if the box has it Does HDMI audio work (Yes/No):Not tested Additional Comments (provide any additional information you feel is important): Headphone audio works although it is not perfect. Keyboard and mouse work fine, I have no remote to test Sound:AML8AUDIO Video playback is slow, I'm not sure if accelerated video is working Video:Mali-450 MP Booted fine, and updated fine 815 available memory

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?

Aliexpress item: https://pl.aliexpress.com/item/1005006249858881.html Extracted dtb and dts files attached. It boots Warpme/miniarch image for X96 with LPDDR3 RAM https://github.com/warpme/miniarch/releases/download/f3b14fbae071/MiniArch-20240715-6.16.1-board-h313.x96_q_lpddr3-SD-Image.img.xz However internal Ethernet port is silent. It can work through USB->ETH adapter though. Any Idea on how to make Ethernet working? sun50.dtb sun50.dts

🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! Product Specification: Chipset: Rockchip RK3576 Octa Core ARM Mali G52 MC3 WIFI: WiFi6 11ax 1x1 80 MHz wifi controller: AP6275P RAM: DDR4 4GB/8GB ROM: eMMC 32GB/64GB/128GB OS: Android 14.0 || Armbian Vendor 6.1 Ethernet: 1000M Standard RJ-45 Bluetooth: BT 5.0 The RK3576 is indeed a lower-cost SoC but features four Cortex-A72 and four Cortex-A53 cores instead Android Base Files: H96-RK3576-ANDROID.dts H96-RK3576-ANDROID.dts H96-RK3576-BOX.dtb H96-RK3576-BOX.dtb RK3576_MiniLoaderAll.bin Mainline status: Verify wifi controller: AP6275P Wifi Driver: https://drive.google.com/file/d/1n6x4tg5Xh24nWllOTJTq1ldVyDkK8W2Q/view?usp=sharing Flashing Tools: https://drive.google.com/file/d/1nLgPCBN0qmbzufWDFmISYc92JUpvwMPc/view?usp=sharing build_armbian.csc: https://drive.google.com/file/d/1VNR5QJlPylPsce9PI9O2TB3wOpshK2Bh/view?usp=sharing @hzdm Stock Firmware: method https://drive.google.com/file/d/1zLGvIxLE6vf8iSTjsyEr-Ly4MZ6ZahBB/view?usp=sharing Flashing Firmware Tutorial Factory Firmware for H96 Max M9 https://disk.yandex.ru/d/pWGEtRel0P9ejg https://drive.google.com/drive/folders/1g63F8fGSLEA9iK2_Mqzd6F0xfaTRnGlm?usp=sharing Factory Firmware for H96 Max M9S https://disk.yandex.ru/d/H17eGTYCjgmCsg https://drive.google.com/drive/folders/1Q360l5XbTVsWIvWkqy2xJ0sLpqHRSApM?usp=sharing TTL debug: RX TX GND pins: Enable SDCARD Reader: @rustamt method from 4pda Force board Maskrom Mode Maskrom Pins:

Hello, sorry for my very bad english. I recently I bought a TV box with an h618 processor And I want to install Linux to make it a server but I only find images for the h616 processor, can I install one of these images on my TV box? It seems that the h616 processor and the h618 procesador are almost the same Thanks :D

R-TV Box S10 – I realize this is an older topic, but I’m trying to fix an S10 box for an old colleague.. After an update, it no longer boots, stuck on the startup animation, and won’t load Android. I can’t seem to find any firmware download. Thanks in advance.

Thanks for sharing your installation. Really, the Rockship in TV BOX seems the easier Armbian installations that I already tested, although, I use a TVBOX with ab AMLOGIC S912.

@Ducdanh Nguyen I don’t write the mainline linux kernel or patches. You should ask the sunxi developers or Piotr Oniszczuk aka warpme. Allwinner does not support open source mainline Linux. Most of the work is reversed engineered by a very few smart people that give their free time to Linux community. Android uses a very old modified Linux kernel so it takes a lot of work to update drivers. Sometimes these drivers have no source code or documentation. tv boxes are a whole different beast. Components are cheap. If you buy the same model tv box they might have different wifi, memory, emmc chips and sometimes the cpu is not allwinner at all. if you want to have a perfect running tv box you’ll need to learn how to tweak the dts and edit the Linux kernel source code. https://oftc.catirclogs.org/linux-sunxi/2025-08-24 https://github.com/warpme

Sorry for being late to the party on this, but I can confirm that rockchip is better supported than Amlogic. My old Android 7 1GB/4GB MXQ TV box works great out of the box with the latest build after installing the step-nand loader.This is a rockchip 32xx build, great menu-driven setup tools, literally working within 15 minutes. Kudos to Jock and co. This is a hobby for me, I'm more interested in learning Linux than having a home server doing real work, I thought about SBCs but pi looked like a boy scout project and other SBCs too expensive with features I don't need. Modern MXQ boxes are cheap and my online vendor has a great return policy, so why not? I just ordered an updated box with 4GB ROM for $10. Running with a class 10 64GB SD card, this will be another fun opportunity. Take care!

I would like to know if anyone has had the opportunity to try the new Tanix TX1. The dimensions are really small, only 58mm x 58mm x 25mm and it only has 1 USB port in addition to the HDMI port and the classic power jack. I know there are no Armbian images for H313 soc yet, too bad. This small TV box could be interesting for creating small servers connected exclusively via WiFi. Button 1 is the flash button, while button 2 is used to enter recovery mode. I tried images for H313 miniarch and others for H616 but I can't boot in any way. I'm using a USB stick obviously without using a USB hub but only the USB stick and for now only Android starts.

DISCLAIMERS (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. THIS POST explains very well the troubles with TV Boxes and why they are not suitable for everyone 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). Following the recent thread on LibreElec forum about an unofficial image for rk3229 devices, I would like to make public the work made by me and @fabiobassa about bringing rk322x support to armbian. The project is now in -> mainline Armbian <- development fork -> here <- This first page and the last 3 or 4 pages of the thread are enough to get up to date with recent developments. Many useful experiences are scattered through the thread, but the most important things are collected here in the first page, so please read it carefully! Mainline kernel is fully supported and will receive most support in the future. Legacy kernel 4.4 is deprecated, but is kept around only for special purposes. What works: Should boot and work flawlessy on all boards with RK3228a, RK3228b and RK3229, with either DDR2 and DDR3 memories. Mainline u-boot Proprietary OPTEE provided as Trusted Execution Environment (needed for DRAM frequency scaling) All 4 cores are working Ethernet Serial UART (configured at 115200 bps, not 1.5Mbps!) Thermals, CPU and DRAM frequency scaling OTG USB 2.0 port (also as boot device!) EHCI/OHCI USB 2.0 ports MMC subsystem (including eMMC, SD and sdio devices) Hardware video acceleration NAND is available only on legacy kernel. To fully boot from NAND, use the Multitool and its steP-nand installation (instructions are below) Various WIFI over SDIO are supported (SSV6051P, SSV6256P, ESP8089, Realtek chips, etc...), ssv6256p driver is available only on legacy kernel Full GPU acceleration U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal eMMC; you can install u-boot (and the whole system) in the internal eMMC and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the eMMC clock pin on the PCB. Here there is the procedure, but you can also google around if you get stuck on a faulty bootloader, the technique is pretty simple and requires a simple screwdriver. There are however some unfortunate cases (expecially newer boards) where shorting the eMMC clock pin is difficult or impossibile, like eMMC or eMCP BGA chips with no exposed pins. In those cases pay double attention when burning something on the internal eMMC/eMCP and always test first the image from the sdcard to be sure it works before burning anything on eMMC/eMCP. Some useful links with pins, pads or procedures for some boards: Generic procedure for boards with non-BGA eMMC MXQPRO_V71 - eMCP H20 - eMCP ZQ01 - eMCP NAND vs eMMC vs eMCP difference: RK3228 and RK3229 tv boxes comes with three different flash memory chips: eMMC, NAND and eMCP. It does not depend upon the market name of the tv box and neither the internal board; manufacturers put whatever they find cheaper when they buy the components. NAND chip is just the non-volatile memory eMMC chip contains both the non-volatile memory plus a controller. eMCP chip contains the non-volatile memory, a controller for the non-volatile memory (like eMMC), but also contains a bank of DDR SDRAM memory on the same physical chip. The difference is very important, because eMMC and eMCP are far easier to support at various levels: the controller deals with the physical characteristics of the non-volatile memory, so the software has no to deal with. NAND chips instead are harder to support, because the software is required to deal with the physical characteristics and non-standard things that depends upon the NAND manufacturer. If you have a NAND chips you're unlucky because mainline kernel currently cannot access it, but also because you need special care and instructions explained later. You can discover if you have a NAND, eMMC or eMCP chip looking on the board are reading the signature on the flash memory chip. The Multitool (see later) also can detect which chip you have onboard: the program will warn you at startup if you have a NAND chip. NAND bootloader upgrade: IMPORTANT: don't do this is you have an eMMC or eMCP; skip this paragraph if you are unsure too! For very expert people who are having issues when (re)booting images, there is the chance to upgrade the bootloader on NAND. The NAND bootloader is nothing else than a regular idbloader (see official rockchip documentation) but contains some bits to correctly access the data on your flash memory. Upgrading requires to erase the existing flash content, in the worst case will require you to follow the Unbrick procedure above or restore an older but more compatible bootloader. If you are not mentally ready to overcome possible further issues, don't do this! The detailed instructions and the binaries are available at this post Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Deprecated legacy kernel: multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post An effective tutorial from @Hai Nguyen on how to configure a box as a hi-quality music player using an USB audio card, and controlling it via remote control is available in this post Brief explanation about kernel naming: current kernel is the mainline LTS kernel version, most maintained and tested. This is the suggested version for production devices. If you don't know what to pick, pick this. legacy kernel (version 4.4) is provided by manufacturer; it is deprecated, unmaintained and not suggested. edge kernel is the development mainline kernel version, with experimental features and drivers; usually stable but perhaps suitable for production devices. You can switch from one kernel flavour to another using armbian-config or manually via apt. Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to CSC/TVB/EOL boards and select "rk322x-box" from the list. Download prebuilt images from the following links: Archive builds (GPG-signed) - https://imola.armbian.com/dl/rk322x-box/archive/ SUGGESTED - Nightly built from trunk each week by Armbian servers (GPG-signed) - https://github.com/armbian/community Old images provided by me (unsigned and outdated) - https://users.armbian.com/jock/rk322x/armbian/stable Archived/older images: https://armbian.hosthatch.com/archive/rk322x-box/archive/ Multitool: The Multitool is a small but powerful tool to do quick backup/restore of internal flash, but also burn images and general system rescue and maintenance via terminal or SSH. Compressed images will be uncompressed on fly. Multitool - A small but powerful image for RK322x TV Box maintenance (instructions to access via network here) Quick installation instructions on eMMC: Build or download your preferred Armbian image 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 power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. 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 sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC, etc... Run sudo armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed and configured! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in eMMC, the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions on NAND: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian legacy kernel 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 Armbian image via steP-nand" from the menu, then select the destination device (usually rknand0) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. 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 sudo rk322x-config and select your board characteristics to enable leds, wifi chips, etc... Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Alternative: you can install the bootloader in NAND and let it boot from SD Card or USB: Download a copy of the Multitool and burn it on an SD card; 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; RECOMMENDED: make a backup of the existing firmware with "Backup flash" menu option; Choose "Install Jump Start for Armbian" menu option: the Jump Start uses the internal NAND to boot from external SD Card or external USB Stick; Follow the general instructions to boot from SD Card below, skip the first erase eMMC step. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; 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 sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC or NAND, etc... Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal eMMC; Congratulations, Armbian is running from SD Card! A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian or just the bootloader in the eMMC or the Jump Start on internal NAND, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal eMMC Installation (without SD card, board with eMMC) If you have no sd card slot and your board has an eMMC, you can burn the armbian image directly on the internal eMMC using rkdeveloptool and a male-to-male USB cable: Download your preferred Armbian image from Armbian download page and decompress it. Download the rk322x bootloader: rk322x_loader_v1.10.238_256.bin Download a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everything went well, run lsusb: you should see a device with ID 2207:320b Run sudo rkdeveloptool rd 3 (if this fails don't worry and proceed to next step) Run sudo rkdeveloptool db rk322x_loader_v1.10.238_256.bin Run sudo rkdeveloptool wl 0x0 image.img (change image.img this with the real Armbian image filename) Unplug the power cord Done! Installation (without SD card, board with NAND) If you are in the unfortunate case you can't use an SD card for installation and your board has a NAND chip, you still have an option to use the quick Multitool installation steps via USB. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b Run sudo rkdeveloptool wl 0x4000 u-boot-main.img (download u-boot-main.img.xz , don't forget to decompress it!) Unplug the power cord Now you can follow the instructions on how to install on eMMC/NAND via SD card, just use instead an USB stick to do all the operations and plug it into the USB OTG port. Once you reboot, USB OTG port will be used as a boot device. NOTE: NAND users without SD slot may be unhappy to know that it will be difficult to do extra maintenance with Multitool in case something breaks in the installed Armbian system: installing u-boot-main.img makes the installed system unbootable because it is missing the NAND driver. Alternative backup, restore and erase flash for EXPERTS: These backup, restore and erase flash procedures are for experts only. They are kept here mostly for reference, since the Multitool is perfectly able to do same from a very comfy interface and is the suggested way to do maintenance. Backup: Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b change directory and move into rkbin/tools directory, run ./rkdeveloptool rfi then take note of the FLASH SIZE megabytes (my eMMC is 8Gb, rkdeveloptool reports 7393 megabytes) run ./rkdeveloptool rl 0x0 $((FLASH_SIZE * 2048)) backup.data (change FLASH_SIZE with the value you obtained the step before) once done, the internal eMMC is backed up to backup.data file Restore: first we have to restore the original bootloader, then restore the original firmware. Running rkdeveloptool with these switches will accomplish both the jobs: ./rkdeveloptool db rk322x_loader_v1.10.238_256.bin Downloading bootloader succeeded. ./rkdeveloptool ul rk322x_loader_v1.10.238_256.bin Upgrading loader succeeded. ./rkdeveloptool wl 0x0 backup.data Write LBA from file (100%) Download here: Erase the flash memory: clearing the internal eMMC/NAND memory makes the SoC look for external SD Card as first boot option. If there isn't any suitable SD Card, the SoC enters maskrom mode, which can then be used for full eMMC/NAND access using rkdeveloptool. This is perfectly fine if your box has an eMMC flash memory. NOTE: In case you have a NAND flash memory this option is however discouraged. The original bootloader contains some special parameters to correctly access the data. Clearing the flash memory will probably garbage the NAND data and restoring the bootloader may require some special instructions. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the board Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b run ./rkdeveloptool ef and wait a few seconds once done, the internal eMMC is erased and the device will boot from the sdcard from now on Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk322x into armbian would not have begun without his support! Justin Swartz, for his work and research to bring mainline linux on rk3229 (repository here) @knaerzche for his great contribution to libreelec support and mainline patches @Alex83 for his patience in testing the NAND bootloader upgrade procedure on his board @Jason Duhamell for his generous donation that allowed researching eMCP boards and esp8089 wifi chip

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box). You can now build your own builds directly with the Armbian build system. This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework. If you are not familiar with the Armbian build system check out the Armbian developer documentation. If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see. I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well. Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.

Hi everyone. What I would like to do is install Armbian on the X98H TV box. I tried many ways to do that, but I was not successful. If you know how to install Armbian on it, plz suggest to me Thanks

Hello, Thru various and sundry means, I have acquired this unusual specimen; a ZeroDesktop MiiPC M1140. This was originally intended to be a "family desktop PC" that runs on Android Jelly Bean and was released in 2013. It looks like a TV box had a child with a NUC. The machine runs a Marvell Armada 1500 Plus processor with 1GB of RAM and 4GB of storage. The company, Zerodesktop, ran a Kickstarter campaign to fund producing these - my model is one of the Kickstarter Editions. I know that the Marvell Armada 1500 was used in the Google Chromecast 2, along with a bunch of set top boxes. ZeroDesktop no longer exists as a company, having only produced these machines between 2013-14 then going belly up. There are no software updates to the Android system available (nor any mention of the device or the Armada 1500 as a supported processor for Android distributions at all). The only resources online about this device are about 7 out of date (mostly negative) tech reviews from the era. I want to make this thing run Armbian. Does anyone have a clue how to do it? I see that there are 2 development boards made by Marvell listed here but they are vastly different processors. I'm definitely an advanced user but have never compiled my own build before, especially when the system components are so mysterious and info is unavailable like this. I am up for the challenge if anyone can assist. Thank you!

Download Armbian with HA (v25.2) Then boot the image, wait few minutes and login via http://ip_address_of_armbian_running_ha:8123 (official onboarding manual) Home Assistant Supervised is, more or less, a full blown Home assistant. Install Home Assistant on any Armbian Bookworm (experimental) Main difference between HA OS and Armbian with HA is that underlying OS here is clean Armbian Debian Bookworm and there is custom dedicated buildroot OS that is provided for a few single board computers, primarily for Raspberry Pi. We provide HA on a small selection of single board computers, but in theory, its possible to run this on (almost) all that are possible to build. I am running HA on Odroid N2+ and it works without any problems. I have z-wave network with sensors and switches, air humidifier, Android TV, Android phones, dishwasher, ... Things works flawlessly, much better then few years back when I started with home automation for a first time, with OpenHab. This time it was setup from scratch and in a matter of days, most of devices are in function, playing with automation. Tested on: Odroid N2/N2+ Odroid M1 Nanopi R4S Rock 5B Uefi-x86 Orangepi 5 Nanopi M6 Rpi400 Khadas VIM1S Khadas VIM4 (Amlogic vendor kernel trouble, failing / need inspection) Bananapi M2 Pro Provided for but untested (images you find on board downloads locations, seek them here https://www.armbian.com/download/😞 DIY Contribute Support: The supervised installation method on Armbian is not officially supported by the Home Assistant project. Additionally, installation on hardware that is not officially supported is also outside the scope of support provided by the Armbian team. You are welcome to report high-level application issues that are reproducible on the official Home Assistant Operating System (HAOS) within the Home Assistant community or here on this forum. For any hardware-related topics, you may use the this forum; however, please be aware that official support from the Armbian team is not guaranteed. single board computer hardware https://www.armbian.com/bugs home assistant functions https://community.home-assistant.io/ (make sure to bring up only issues that are application related, high level issues, that are likely present in official HAOS software)

Help for install ambian 22 or 23 in box TV with soc rk3528 i have instaled in box with amlogic no problème but with rockchip no support no boot......

Hello, I found this guide: https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md I followed the steps and built an Armbian image with current 6.12 kernel and now TV OUT (CVBS, Composite Video), after soldering a cable to the video pin on the board, is working on my Orange Pi One with an Allwinner H3 CPU (the patches might work for other H3/H2+ boards). I would like to get that functionality incorporated into Armbian.

Hi everyone, I’m experiencing a recurring and very specific issue with my TX2 TV Box, with the following specifications: SoC: Rockchip RK3229 RAM: 2GB DDR3 Storage: NAND flash (not eMMC!) Board: Generic TX2 board 🛑 Main Issue The system shuts down abruptly at exactly 29 minutes and 47 seconds of uptime (i monitoring via htop). It always shuts down at this time. It’s not a clean shutdown or reboot — it behaves as if the power was cut off. No meaningful logs appear in journalctl or dmesg, and the shutdown is instantaneous and silent. 🧪 What I’ve Tried: Disabled idle and sleep functions: Masked systemd-logind Set IdleActionSec=0 and HandlePowerKey=ignore Tried different kernel versions: Legacy: Armbian 22.02.0-trunk Focal legacy 4.4.194 Mainline: Armbian Jammy kernel 5.15 Attempted to disable the watchdog: Boot parameter nowatchdog Kernel parameter rcu_cpu_stall_timeout=0 Created a systemd service to periodically write to /dev/watchdog Tried to remove dw_wdt module (modprobe -r), but it either auto-loads or refuses to unload (watchdog did not stop) Tried building a custom kernel with CONFIG_DW_WATCHDOG=n, but the process failed due to gcc-arm-linux-gnueabi toolchain issues. Used config-rk322x to properly set RAM, NAND, and Wi-Fi chip before first boot + update/upgrade. Tried adding sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target ⚠️ Additional Critical Note: The system does not work at all when flashed to eMMC/flash — only boots properly from NAND or SD card. Any image written to internal flash does not boot. Therefore, booting from NAND is required, which may be related to the watchdog being active by default on NAND-based boards. ❓ My Question: Has anyone with a TX2 or RK3229-based NAND board experienced this same issue? Is this a known watchdog timer issue on NAND models? Is there any stable image or device tree overlay known to work for this configuration? Any tips to fully disable the watchdog either via software or kernel patch? Thanks in advance for any help or suggestions!

I Have an A96X with rockchip RK3228 and i tried booting armbian on it, but I got no display on HDMI. I connected a serial adapter to it and here is the information it displays when trying to boot: ▒▒▒▒DDR Version V1.05 20160805_dbg In 300MHz DDR3 Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB mach:2 OUT Boot1 Release Time: 2016-03-15, version: 2.31 ChipType = c 275 No.1 FLASH ID:2c 64 44 4b a9 0 ECC:60 SdmmcInit=0 0 BootCapSize=0 UserCapSize=76f5000 FwPartOffset=2000 , 0 StorageInit ok = 1520008 SecureMode : SBOOT_MODE_NS hdr 0x0:ff a1 0 0 1b 0 0 0 f0 f2 2e 68 f0 f2 2e 68 hdr 0x0:a4 81 0 0 4e 23 0 0 f0 f2 2e 68 f0 f2 2e 68 hdr 0x0:ff a1 0 0 3 0 0 0 f4 f2 2e 68 f4 f2 2e 68 hdr 0x0:a4 81 0 0 44 0 0 0 f4 f2 2e 68 f4 f2 2e 68 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SecureMode : SBOOT_MODE_NS Loder code check ok! theLoader 0x60000000, loadaddr: 0x2000 Loder code check ok! theLoader 0x68400000, loadaddr: 0x4000 INF TEE-CORE:init_primary_helper:319: Initializing (1.0.1-63-g23e91df-dev #16 Tu e Mar 7 10:07:15 UTC 2017 arm) INF TEE-CORE:init_primary_helper:320: Release version: 1.8 INF TEE-CORE:init_teecore:79: teecore inits done U-Boot 2017.02-RK322X-06-02276-ga7c7ca8-dirty (May 19 2017 - 11:16:15) CPU: rk322x cpu version = 3 CPU's clock information: arm pll = 600000000HZ periph pll = 600000000HZ ddr pll = 600000000HZ codec pll = 500000000HZ Board: Rockchip platform Board Uboot as second level loader DRAM: Found dram banks: 1 Adding bank:0000000060000000(0000000040000000) Reserve memory for trust os. dram reserve bank: base = 0x68400000, size = 0x00100000 128 MiB GIC CPU mask = 0x00000001 rk dma pl330 version: 1.4 remotectl v0.1 pwm freq=0x11e1a3 pwm_freq_nstime=0x355 SdmmcInit = 0 0 SDCard Update. storage init OK! Using default environment Writing env to storage... done GetParam W: Invalid Parameter's tag (0x00000000)! Invalid parameter No pmic detect. SecureBootEn = 0, SecureBootLock = 0 #Boot ver: 0000-00-00#0.00 empty serial no. normal boot. no fuel gauge found no fuel gauge found read logo on state from dts [0] no fuel gauge found 'recovery' does not seem to be a partition nor an address Unable to boot:recovery try to start backup 'backup' does not seem to be a partition nor an address Unable to boot:backup try to start rockusb Can anybody point me to the right direction? I'd really like to turn this piece of junk into something useful 😄 Any help will be greatly appreciated! Thank you.