Search the Community

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, 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

Okay I gave up on it and done a fresh install.. Took me 5 hours to get it back up and running, to reconfig x11vnc and samba stuff. Starting a freshly baked image proved to be a nightmare - for whoever is interested I share my story; For some reason it did not detect wireless dongle for keyboard. So I could see it over hdmi but no input was possible. Did not have a wired keyboard at hand. at first run it did not became accessible over ssh. but an ip address was assigned to it by dhcp router; I could see a new ip when I'd start it up. but it would not respond to ssh requests. But serial connection saved the day. Luckily I did have a serial adapter. Created username/password and then it was accessible over ssh and I could ditch the crappy tv screen I was using Selected wrong locale on setup, was unable to get rid of it without commenting wrong locale lines in ~/.bashrc Then I spent some few hours to get vnc up and running with lightdm and crapload of other dependencies, packages. Thanks AI for assistance. When asking quality questions and sharing messages/outputs it was super useful (I dont keep anything confidential there) Manually created /home/domas/startxfve_headless.sh script, made it executable, the whole orderal Not to mention xfce was not installed by default on this debian/minimal image. It was fun one too. https://docs.armbian.com/User-Guide_Armbian-Software/Desktops/ - armbian-config --cmd XFCE01 just ran the script and nothing happened without any error Had to do it manually but I think it worked the first or second time. And the most fun one since it included multimeter and soldering iron: then it did not detect my disk over sata no matter what I do. Apparently measured 0v at hdd power connector. Not sure how I killed it. After some fiddling around I connected jst connector's for hard drive 5V power to one of gpio pins that supply 5v. HDD spins up - YAAAY. It was short-lived. Disk Still undetected. Probably usb to sata controller is not powered on since 5v regulator fried. (thanks AI for ideas) So then I jumped a wire from said gpio 5v pin to the back of what used to be 5V connector for hard drive so it both feeds the disk and backfeeds the boards 5v regulator with the needed usb to sata controller. I don't use gpio. ITS ALIVE. No, I did not believe it would work. But at this point I had nothing to lose. Sketchy? Yes. Have I ever pulled worse? Sure. Proud of myself? You bet.

i have an android tv box. model name: tx 10 pro. i want to install ARMbian on it. there is a reset button under the av port. it has 2 gb of ram and 4 gb of rom (though the internet says 8G ram and 128G rom, also the android ui too). i have enabled both usb debugging and oem unlocking from the android developer option menu. the tv box can go to recovery mode using adb command. until going to the recovery mode, the adb connects perfectly but whenever it goes into recovery mode, the adb cant connect to the tv box. it consists option for fastboot inside the recovery mode but whenever i try to apply any command (e.g. fastboot/adb) the tv box doesnt show up among the devices when the device is in recovery mode. As there is no zip file for direct linux installation that i can use with flash from usb option. and the reset button beneath the av port does nothing, ive tried to flash multiple ARMbian Img files using both rufus and etcher but the screen just goes black whenever i press and hold the reset button beneath the av port. there is no option to install twrp as neither adb nor fastboot can connect whenever the device is in recovery mode. what to do?

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

(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:

Hi everyone, i am impressed by the great knowledge found in this forum. I have been playing for years with a Bealik SEA I tv box with, with great results: a rooted Android system a full Ubuntu distribution 20.04 running in chroot environment kodi v17 android verrsion Recently I bought a X88 pro 10 box (4gb ram and 64gb rom) and started playing with armbian, and I will use this thread to record my progress with this box, still not working at 100% of its capabilities. Using multitool I am able to load and start images on the box, did several install and was able to boot and run: Armbian_23.11.1_Rk3318-box_jammy_current_6.1.63 Armbian_23.11.1_Rk3318-box_bookworm_current_6.1.63_xfce_desktop DietPi_ROCK64-ARMv8-Bullseye_RK3328_RK3318 <- now I'm working on this one > The box has a Mali450 GPU but i cannot run hardware decoding neither on kodi and in Xorg server. When I play an x264 movie on kodi, I see the cpu load increasing up to 100% and the video si dropping frames and shuttering. I have gone through the whole 52 pages of this thread, but seems quite old and all the indications work on debian buster armbian img, which I was unable to find buster img all around. So I stick to my bullseye distribution. Fisrt i had to downgrade kernel to legacy, and just went with apt-get: linux-dtb-legacy-rockchip64/bullseye,now 23.8.1 arm64 [installed] linux-image-legacy-rockchip64/bullseye,now 23.8.1 arm64 [installed] xserver-xorg-legacy/oldstable-security,now 2:1.20.11-1+deb11u8 arm64 [installed] uname -r 4.4.213-legacy-rockchip64 Compiled armbian-media eollowing this github: https://github.com/teacupx/armbian-media and installed: apt-get install libdrm-dev apt-get install libgbm-dev apt-get install libegl-dev Started X11 successfully, but kodi crashes. sudo apt-get install mesa-va-drivers MESA 3D wget https://archive.mesa3d.org/mesa-18.0-0-rc1.tar.gz tar xf mesa-18.0-0-rc1.tar.gz apt-get build-dep mesa

­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 Hongtop H50 (board signature t98-3318-221-v11) by @GmP 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

These instructions are for Amlogic CPUs for TV Boxes. Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds. Download links: Weekly Community Rolling Builds: https://www.armbian.com/amlogic-s9xx-tv-box/ or build your own image using the Armbian build framework Once you download your chosen build, you need to burn the image to an SD card. Generally balenaEtcher is recommended as it does a verification of the burn. Also be sure to use high quality SD cards. Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card. In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. There will also be a extlinux.conf.template file to use as a reference. You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box. Place this line before the APPEND line as shown in the .template file. Basically you need to have the correct dtb for your box. You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware). It is unlikely that there will be a matching dtb file for your TV box. The idea is to find the one that works best for your box. This may mean that you try booting with different dtb files until you fine one that works good enough for your needs. By searching the forums you will find information about what dtbs other users have found work best for different boxes. Because you are booting from an SD card, you can easily try different dtb files. The dtd files are named by cpu family. So for example dtb files for the s905x2 cpu are named meson-g12a-*. Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case). Next you need to copy the correct uboot for your box. This is needed for how these builds boot on amlogic boxes. There are four different u-boot files located in the /boot directory: u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3 You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext (See table below for more details on which u-boot to use for which cpu) Once you have your SD card prepared you need to enable multiboot on the box. There are different ways documented to do this, but the most common is the "toothpick" method. The "toothpick" method means to hold the reset button while applying power to the box. The reset button is often hidden and located at the back of the audio/video jack connector. By pressing that button with a toothpick or other such pointed device you can enable multiboot. What you need to do is have the box unplugged, have your prepared sd card inserted, then press and hold the button while inserting the power connector. Then after a bit of time you can release the button. (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times). You should now be booting into armbian/linux. Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card. After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box. Don't do this unless you feel you understand how to reinstall your box's android firmware) You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported). It is recommended that you make a backup of emmc first. Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device. If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file. Mapping from CPU to uboot and dtb: u-boot-s905 s905 - gxbb u-boot-s905x2-s912 S905X - gxl S905W - gxl S905D - gxl S905L - gxl S805X - gxl S912 - gxm A311D - gxm u-boot-s905x2-s922 S905X2 - g12a S922 - g12b u-boot-s905x3 S905X3 - sm1 Not supported or not tested S805 - S905W2 - S905X4 - S805X2 - s4 A113D - axg A113X - axg Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions. Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

Please help, I'm stucked (or, may be stupid). I use my tv-box as printserver (Klipper), it works fine. Now I attempt to use accelerometer ADXL345 usb board, and I havnt success. It must be simple task, but something went wrong here. Board works, flashed normally without any errors and shown as should by lsusb: klipper@transpeed-8k618-t:/usr/lib/udev/rules.d$ lsusb Bus 003 Device 002: ID 1a86:7523 QinHeng Electronics CH340 serial converter Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 013: ID 1d50:614e OpenMoko, Inc. rp2040 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Also, it must be appear as serial device, but... klipper@transpeed-8k618-t:/usr/lib/udev/rules.d$ ls -l /dev/serial/by-id total 0 lrwxrwxrwx 1 root root 13 Nov 8 18:47 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0 ...here is my "Ender" only. dmesg: [30617.149526] usb 4-1: new full-speed USB device number 22 using ohci-platform [30617.358206] usb 4-1: New USB device found, idVendor=1d50, idProduct=6177, bcdDevice= 1.00 [30617.358227] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [30617.358235] usb 4-1: Product: rp2040 [30617.358242] usb 4-1: Manufacturer: katapult [30617.358249] usb 4-1: SerialNumber: E6647C7403433637 [30663.467079] usb 3-1: new full-speed USB device number 3 using ohci-platform [30663.665820] usb 3-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64 [30663.665867] usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [30663.665891] usb 3-1: Product: USB Serial [30663.668223] ch341 3-1:1.0: ch341-uart converter detected [30663.680198] usb 3-1: ch341-uart converter now attached to ttyUSB0 I've search solutions, but have not resolve.

So I bought this chinise Android TV Box and would love to install armbian on it. I am new on this and discovered armbian just after buying it. I didn't know there was no support and not official open source for the Rockchip RK3528, otherwise I would have chosen any other. The box works fine but it has that known malware that send packets to suspicious links (I scanned activity with pi-hole). Description says it has 2GB RAM and 16GB storage (Hynix H26M51002KPR) WiFi chip is LGX8800D I attach images of the board and all of it's componentes, including IR sensor and display. It also has a red LED that turns on when in stand-by mode. I hope this help to develop or patch a working version of armbian for it. I have already read about some patches around that would probably work, but I' new to this and I'm not sure how to start. What I would like to do first is a completly ROM backup, and start doing test with a pendrive or SD card, not writting directly to the eMMC (if possible) until the important things get working. And any help would be appreciated. Edit: I will keep posting in this thread with my progress (or attemps!)

The wifi and ethernet both are not working for my transpeed 8k tv device. it has a rk3528 chipset. 1. I tried resetting it from its android factory setting. it did not work. 2. I found its image which i flashed via RKdevtool. Still the both wifi and lan did not work. 3. i tried external usb wifi dongle but it did not detect it. 4. I tried to install debian OS i found somewhere on internet designed for rk3528 on it as alternative but rkdevtool did not identified the image Any suggestions would be welcome. Thanks in advance,

I came from 4pda to armbian and I came from there already being a prejudiced person. this is just another normal day in the TV box section. Many other users have already encountered similar problems with Chinese boxes. you can solder a better module like @Deoptim

Hi. I installed Armbian Server on my TV box (Ugoos X3 Pro 4/64 x905x3) to the NAND, and I have some trouble with the RAM size in the system. I use meson-sm1-ugoos-x3.dtb. It turns out that only 1.8GB of 4GB RAM is available in the system. On the Russian forum 4PDA, I found some information on how to fix this. I repacked the DTB file and changed memory@ from 0x40000000 to 0xFF000000. After that, 3.8GB RAM appeared in the system, but it turned out the system was unstable and randomly froze. However, when I installed Armbian from an SD card, all 3.8GB RAM was available in the system, and the system worked fine and stable. I also used meson-sm1-ugoos-x3.dtb. Is it possible to fix this and use all available RAM?

Welcome to TV-Box section, that's the real size of your RAM: 4gb https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/rkbin

Hi, First of all thank you very much for all the support and efforts you have taken to provide with the extensive documentation and images to flash on the android tv boxes. I am here in hope of some help and guidance, since ive not been able to solve this particular issue since past 2 months and with bare minimum sleep and enough efforts. I have a SDMC Tech STB which is DV8549 - Processor: Amlogic S905X2 - RAM: 2GB - EMMC: 8 / 32Gb (not sure but will share part number) - WiFi chip? Unsure since the part is rubbed off, and its not even necessary to run the wifi. It does not have the SD card slot unlike the normal TV Boxes. it seems to be locked? or rather would not go into any mode. it has a debug port, but it would not show any data apart from some wifi related things. in which if we keep pressing CTRL + C it will stop displaying that. There is some button given, unlike the TB Boxes, but that button upon pressing only takes into the recovery mode which leads to nothing but only would ask to Wipe Data and factory Reset, that is all. Just behind the EMMC Chip, there seems to be a Placment for a small Pushbutton which is not populated, but when we do short it, while plugging in the Power Supply, it would take the device in the WorldCup Mode. **What have i tried?** 1. Did put the device in worldcup mode and followed with a alot of files from Ricky Divjakovski, to try and flash some android images which were provided by other people online, but it would not do anything or would not lead to any flashing to the board. 2. Tried the Amlogic USB Burning tool, but even that would not lead to any of the flashing, did follow a lot of videos online but all the steps were made for the generic TV Boxes and none for my specific, but considering my electronics and embedded knowledge i tried my level best to do all the combinations to check if the usb burning tool would help to flash any rom it did not. So, both the standard ways which are meant to be used for the Generic TV Boxes are not available for me. The last step which im planning to do is, pull out the EMMC from the board, install it on the external EMMC Reader like the allSocket bga153/163 and copy all the files from the EMMC and erase it. but i have no idea after erasing, re-soldering the EMMC, where do i start and how do i install the armbian or any OS onto the board again? what do i expect from you or other users over here from the community? what should i do next? is there any way i can get this up and running? are there any steps i might be missing? Back of the board. Highlighted in RED is the button i would short and it would take me into the worldcup mode Highlighted in Blue is the button i would press, and it would take me to recovery. Front Of the Board from over here i was not able to attach any more photos to the post, so a humble request to follow up over here https://github.com/ophub/amlogic-s9xxx-armbian/issues/3214 for all the pictures. any help in regards to this shall be very very much amazing. thanks in advance.

well @SteeMan i tried all the possible instructions and everything i could possibly try. Usb does not power the board, which most of the generic chinese TV Boxes do, we plug the usb, power it , it can detect the things and we put the sd card and we are good to go, that does not happen on this board since, the SDCard slot is not there, and apart from that you have to power it externally it will not detect the USB power. Upon trying to short the pins which are shown, would only take me into the WorldCup mode, but even after going into that, and following with all the possible files, which are meant to update it, like in some videos, it would not take up the file honestly, rather it would get stuck to the point where it is mainly trying to read the emmc block. would not go any further ahead of that. The other option is to use the amlogic usb burning tool, now again, that tool like so many videos online would not show me any details whatsoever, it will not show up my box for me to be able to flash it. there are uart pins, it only shows the following things. no matter what key strokes i give it will never stop nor do anything fancy for me, it will straight boot into its OS. so all the provided instructions already online are not at all of any help for this. Instead im wiling to go multiple steps further, like i had mentioned initially and those would be the following. Try and pull out the EMMC from the board and use a reader to read it? But i am lost even after i read the data, and if i wish to put back anything lets say armbian, what should i do next? flash it from the emmc reader? or put it back on the board and try to see then what all burning method works? apart from the EMMC pull out, i am unsure what else might as well work here, i am least interested now to even run android back on it since i would require multiple files which only the factory can provide maybe? (heard this from my linux developer friends who make roms) which i do not have. my final call would be to simply design my own custom PCB and pull out the Processor, RAM and EMMC and build our own DTB and use it, but again, i am not sure and unaware of the fact that if there are things flashed on the S905X itself or everything that is stopping me is on the EMMC? and if making my own board which is the last option, would even be worth it?

Hi @SteeMan, Thanks for the response. Yes i do know that, perhaps, im trying to get help from anyone and everyone to get this up and running, i had even tried to buy the MXq5 TV boxes before, and it failed, rather including you and some other mods had asked me not to continue with it since it has a processor which would not do much of the great deal for my Touch screen solution. hence now that ive got hands on this board which im even able to get for cheap honestly, i would like to get into it. thats all. so anything which can help to get this up and running would be helpful. apart from that, since i could not post more than 1 image i added the link to the github. Thanks in advance.

Hello everyone! First of all, thanks for the useful thread. I'd like to know if you got the files for the SD card, Guillaume lopéré. And if installing this armbian I'd be able to use the tv box as a home server, deploying a Node.js project and using Docker. Best Regards, Gilliard

Hello SliTaz community, I would like to know how I could install SliTaz on an Android TV box powered by a Rockchip RK3229 processor. I understand that the standard SliTaz ISO is for x86 architecture, but my device uses ARM. Is there any ARM-compatible version of SliTaz that could run on this hardware? Or is there a way to build a custom ARM rootfs with the SliTaz ARM toolchain and use it with a compatible kernel and bootloader? Any help, guidance, or example would be greatly appreciated! Thanks in advance!

Hi, welcome everyone. I’m using an H50 TV box that I was about to throw away because I thought I had completely bricked it. I disassembled it and found the pins to activate maskrom mode. I think this could be useful for everyone. I then installed the current image, and everything seems to work except for the HDMI output (blank screen). Do you have any suggestions? Thanks. Some data and photo below. In case you want to install please note that also multitool fails to activate the HDMI, so you will need SSH to config. SOC: RK3188 (Hopefully - I did not remove the heatsink) eMMC: Samsung KLMBG4GEAC-B001 32GB (64x4) eMCP: Samsung KMQN10006B 8 GB eMMC + 1 GB LPDDR3 RAM Wi-Fi IC 339S0209 2.4G/5G LAN working WIFI Working ---------------------------- root@rk3318-box:~# lscpu Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: ARM Model name: Cortex-A53 Model: 4 Thread(s) per core: 1 Core(s) per cluster: 4 Socket(s): - Cluster(s): 1 Stepping: r0p4 CPU(s) scaling MHz: 60% CPU max MHz: 1008.0000 CPU min MHz: 600.0000 BogoMIPS: 48.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid Caches (sum of all): L1d: 128 KiB (4 instances) L1i: 128 KiB (4 instances) L2: 256 KiB (1 instance) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-3 Vulnerabilities: Gather data sampling: Not affected Indirect target selection: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Reg file data sampling: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Not affected Spectre v1: Mitigation; __user pointer sanitization Spectre v2: Not affected Srbds: Not affected Tsa: Not affected Tsx async abort: Not affected Vmscape: Not affected root@rk3318-box:~# free -l total used free shared buff/cache available Mem: 1504636 291372 1037440 46940 297848 1213264 Low: 1504636 467196 1037440 High: 0 0 0 Swap: 752316 0 752316 SOME TESTS ON THE HDMI ISSUE: hdmi_debug_20251008_230528.log hdmi_test_20251008_230948.log

There should be a big difference in speed and powerconsumption; As I indicated in earlier post, edge kernel has no video encoding working, so at least is is SW encode. Debian/standard ffmpeg for aarch64 only had/has v4l2m2m, no dedicated RKMPP also no old OpenMAX rpi methods (in the past). I think this works for Qualcomm SoCs, but no others I am aware of. If you use RK35xx RKMPP I see almost 5x real-time speed for 1080p50 and low CPU load. See example below: root@rock5b:~# ffmpeg -hide_banner -codecs | grep -e h264_v4l2m2m -e h264_rkmpp DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m h264_cuvid) (encoders: libx264 libx264rgb h264_nvenc h264_v4l2m2m h264_vaapi h264_vulkan) root@rock5b:~# /usr/share/jellyfin-ffmpeg/ffmpeg -hide_banner -codecs | grep -e h264_v4l2m2m -e h264_rkmpp DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m h264_rkmpp h264_cuvid) (encoders: libx264 libx264rgb h264_nvenc h264_v4l2m2m h264_rkmpp) root@rock5b:~# /usr/share/jellyfin-ffmpeg/ffmpeg -y -hide_banner -c:v hevc_rkmpp -i /lan/record/2025-11-04-NPO-1.ts -map v -c:v h264_rkmpp -f mpegts /dev/null Input #0, mpegts, from '/lan/record/2025-11-04-NPO-1.ts': Duration: 06:59:01.58, start: 14798.887378, bitrate: 4058 kb/s Program 1 Metadata: service_name : NPO 1 service_provider: KPN Stream #0:0[0x1b63]: Video: hevc (Main) ([36][0][0][0] / 0x0024), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn Stream #0:1[0x1b64](dut): Audio: aac_latm (HE-AAC) ([17][0][0][0] / 0x0011), 48000 Hz, stereo, fltp Stream #0:2[0x1b69](dut): Audio: aac_latm (HE-AAC) ([17][0][0][0] / 0x0011), 48000 Hz, stereo, fltp (visual impaired) (descriptions) Stream #0:3[0x1b65](dut): Subtitle: dvb_teletext (libzvbi_teletextdec) ([6][0][0][0] / 0x0006), 492x250 No Program Stream #0:4[0x12]: Data: epg Stream mapping: Stream #0:0 -> #0:0 (hevc (hevc_rkmpp) -> h264 (h264_rkmpp)) Press [q] to stop, [?] for help Output #0, mpegts, to '/dev/null': Metadata: encoder : Lavf61.7.100 Stream #0:0: Video: h264 (High), nv12(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 2000 kb/s, 50 fps, 90k tbn Metadata: encoder : Lavc61.19.101 h264_rkmpp ^C[out#0/mpegts @ 0xaaaaea74fce0] Error writing trailer: Immediate exit requesteds speed=4.86x [out#0/mpegts @ 0xaaaaea74fce0] Error closing file: Immediate exit requested [out#0/mpegts @ 0xaaaaea74fce0] video:61287KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 6.096897% frame=12559 fps=244 q=25.0 Lsize= 65024KiB time=00:04:11.16 bitrate=2120.9kbits/s speed=4.87x ^C^CReceived > 3 system signals, hard exiting

I have a RK3228A TV Box which is able to properly boot armbian when flashed to its eMMC (no rknand) . However I don't use Armbian much often, probably a maximum of two to three times a month. I want to keep stock Android on eMMC, for video playback on the YouTube app is much faster compared to in firefox and Android has proper remote support which Armbian lacks. I tried flashing the armbian community image on the sdcard but the device didn't boot from sdcard unless the eMMC was wiped. I found that multitool is able to always boot from sdcard irrespective of whatever is in the emmc. After doing some research on the multitool build process, I think I need a properly configured idbloader, uboot and tee binary and then place them at proper offsets in the image, however the Armbian image already contains different data at those offsets. So, how can I build an Armbian image that can be booted from sdcard without wiping the eMMC ?

@Ducdanh Nguyen, if you mean usb<->uart converter, virtually anything with cmos/ttl 3.3v. i/o levels (5v. probably is fine too) will work. Based on ch340 or pl2303 or cp2101 or some FTDI chips - all they should work. But don't use usb<->rs232 converters or COM port directly. If you talking about soldering some sort of connector to tv box board, then I can't suggest anything, except some straight separate pin. This test points are just separate pads and they don't suit any of connectors I familiar with. IMO better way is to solder thin flexible wires (preferably in PTFE or silicone insulation) to the board, and then solder any kind of connector to them. You need uart connected only if you wish to interact by it means with tv box. Through uart you can interact with u-boot bootloader, inspect kernel output and have access to shell console with 'su' enabled. But, just to simply boot tv box, you don't need uart.

Hello, I have an X96q 2/16 TV Box. I installed the build "Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_server" on a 64GB microSD card, and everything is working fine. However, when I run armbian-install -m yes and select "Boot from eMMC — system on eMMC", I get the error: Error: Partition(s) on /dev/mmcblk2 are being used. Too many primary partitions. mount: /mnt/armbian-install.kYpi5v/rootfs: WARNING: source write-protected, mounted read-only. mount: /mnt/armbian-install.kYpi5v/bootfs: WARNING: source write-protected, mounted read-only. rm: невозможно удалить (Can't be deleted) '/mnt/armbian-install.kYpi5v/bootfs/bat': Файловая система доступна только для чтения (File system is read-only) rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/bootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/fastbootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/font24.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/font32.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/bootfs/magic.bin': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/bat': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/bootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/fastbootlogo.bmp': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/font24.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/font32.sft': Файловая система доступна только для чтения rm: невозможно удалить '/mnt/armbian-install.kYpi5v/rootfs/magic.bin': Файловая система доступна только для чтения Partition too small. Needed: 1896 Mb Available: 128 Mb. How can I fix this? Output of sudo lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk2 179:0 0 14.6G 0 disk ├─mmcblk2p1 179:1 0 32M 0 part /mnt/armbian-install.38Slfn/bootfs │ /mnt/armbian-install.38Slfn/rootfs │ /mnt/armbian-install.3JZfHI/rootfs │ /mnt/armbian-install.Mqemrx/rootfs ├─mmcblk2p2 179:2 0 16M 0 part ├─mmcblk2p3 179:3 0 32M 0 part ├─mmcblk2p4 179:4 0 2G 0 part ├─mmcblk2p5 179:5 0 16M 0 part ├─mmcblk2p6 179:6 0 32M 0 part ├─mmcblk2p7 179:7 0 640M 0 part ├─mmcblk2p8 179:8 0 16M 0 part ├─mmcblk2p9 179:9 0 16M 0 part ├─mmcblk2p10 179:10 0 16M 0 part ├─mmcblk2p11 179:11 0 16M 0 part ├─mmcblk2p12 179:12 0 16M 0 part ├─mmcblk2p13 179:13 0 512K 0 part ├─mmcblk2p14 179:14 0 15.5M 0 part ├─mmcblk2p15 179:15 0 16M 0 part ├─mmcblk2p16 179:16 0 16M 0 part └─mmcblk2p17 179:17 0 11.7G 0 part mmcblk2boot0 179:32 0 4M 1 disk mmcblk2boot1 179:64 0 4M 1 disk mmcblk0 179:96 0 58.2G 0 disk └─mmcblk0p1 179:97 0 57.7G 0 part /var/log.hdd / zram0 254:0 0 986.1M 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 0B 0 disk Output of sudo fdisk -l: Disk /dev/mmcblk2: 14.56 GiB, 15634268160 bytes, 30535680 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AB6F3888-569A-4926-9668-80941DCB40BC Device Start End Sectors Size Type /dev/mmcblk2p1 73728 139263 65536 32M Microsoft basic data /dev/mmcblk2p2 139264 172031 32768 16M Microsoft basic data /dev/mmcblk2p3 172032 237567 65536 32M Microsoft basic data /dev/mmcblk2p4 237568 4431871 4194304 2G Microsoft basic data /dev/mmcblk2p5 4431872 4464639 32768 16M Microsoft basic data /dev/mmcblk2p6 4464640 4530175 65536 32M Microsoft basic data /dev/mmcblk2p7 4530176 5840895 1310720 640M Microsoft basic data /dev/mmcblk2p8 5840896 5873663 32768 16M Microsoft basic data /dev/mmcblk2p9 5873664 5906431 32768 16M Microsoft basic data /dev/mmcblk2p10 5906432 5939199 32768 16M Microsoft basic data /dev/mmcblk2p11 5939200 5971967 32768 16M Microsoft basic data /dev/mmcblk2p12 5971968 6004735 32768 16M Microsoft basic data /dev/mmcblk2p13 6004736 6005759 1024 512K Microsoft basic data /dev/mmcblk2p14 6005760 6037503 31744 15.5M Microsoft basic data /dev/mmcblk2p15 6037504 6070271 32768 16M Microsoft basic data /dev/mmcblk2p16 6070272 6103039 32768 16M Microsoft basic data /dev/mmcblk2p17 6103040 30535646 24432607 11.7G Microsoft basic data Output of (parted) print: Model: MMC R821MB (sd/mmc) Disk /dev/mmcblk2: 15.6GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 37.7MB 71.3MB 33.6MB fat16 bootloader msftdata 2 71.3MB 88.1MB 16.8MB env msftdata 3 88.1MB 122MB 33.6MB boot msftdata 4 122MB 2269MB 2147MB super msftdata 5 2269MB 2286MB 16.8MB misc msftdata 6 2286MB 2319MB 33.6MB recovery msftdata 7 2319MB 2991MB 671MB ext4 cache msftdata 8 2991MB 3007MB 16.8MB vbmeta msftdata 9 3007MB 3024MB 16.8MB vbmeta_system msftdata 10 3024MB 3041MB 16.8MB vbmeta_vendor msftdata 11 3041MB 3058MB 16.8MB ext4 metadata msftdata 12 3058MB 3074MB 16.8MB private msftdata 13 3074MB 3075MB 524kB frp msftdata 14 3075MB 3091MB 16.3MB empty msftdata 15 3091MB 3108MB 16.8MB media_data msftdata 16 3108MB 3125MB 16.8MB fat16 Reserve0 msftdata 17 3125MB 15.6GB 12.5GB f2fs UDISK msftdata Has anyone encountered this and knows how to fix it? Do I need to repartition the eMMC? If so, what is the safest way to do it without bricking the device? Any guidance would be greatly appreciated.