Search the Community

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

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

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

­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

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!)

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.

Good day to you))) I have a TV BOX TX9Pro. Chassis (Main Board): H616/H313mini84 V2.0 kernel 4.9.170 I would like to run one of the armbian builds on it. But I can’t figure out how to do this, here are the logs when starting the console... Is there support for this device? tell me what to do and how... Thanks in advance. U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) DRAM:This DRAM setup is currently not supported. resetting ... [70]HELLO! BOOT0 is starting! [73]BOOT0 commit : 803d783 [75]set pll start [78]periph0 has been enabled [81]set pll end [83]unknow PMU [84]unknow PMU [86]PMU: AXP1530 [88]dram return write ok [90]board init ok [92]DRAM BOOT DRIVE INFO: V0.645 [96]the chip id is 0x5d00 [98]chip id check OK [103]DRAM_VCC set to 1500 mv [106]DRAM CLK =600 MHZ [108]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [116]Actual DRAM SIZE =1024 M [118]DRAM SIZE =1024 MBytes, para1 = 30eb, para2 = 4000000, dram_tpr13 = 6041 [132]DRAM simple test OK. [134]rtc standby flag is 0x0, super standby flag is 0x0 [140]dram size =1024 [143]card no is 2 [145]sdcard 2 line count 8 [147][mmc]: mmc driver ver 2020-09-10 15:32 [157][mmc]: Wrong media type 0x0, but host sdc2, try mmc first [163][mmc]: ***Try MMC card 2*** [202][mmc]: RMCA OK! [204][mmc]: bias 4 [207][mmc]: MMC 5.0 [209][mmc]: HSSDR52/SDR25 8 bit [212][mmc]: 50000000 Hz [214][mmc]: 7456 MB [216][mmc]: ***SD/MMC 2 init OK!!!*** [291]Loading boot-pkg Succeed(index=0). [294]Entry_name = u-boot [304]Entry_name = monitor [307]Entry_name = dtbo [310]Entry_name = dtb [314]tunning data addr:0x4a0003e8 [317]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):a0d3abd NOTICE: BL3-1: Built : 17:32:02, 2020-10-20 NOTICE: BL3-1 commit: 8 ERROR: Error initializing runtime service tspd_fast NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 U-Boot 2018.05 (Feb 15 2023 - 17:22:04 +0800) Allwinner Technology [00.391]CPU: Allwinner Family [00.394]Model: sun50iw9 I2C: ready [00.398]DRAM: 1 GiB [00.401]Relocation Offset is: 35ebf000 [00.442]secure enable bit: 0 [00.444]pmu_axp152_probe pmic_bus_read fail [00.448]PMU: AXP1530 [00.454]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz [00.462]drv_disp_init [00.492]__clk_enable: clk is null. [00.497]drv_disp_init finish [00.500]gic: sec monitor mode [00.522]flash init start [00.524]workmode = 0,storage type = 2 [00.528]MMC: 2 [00.529][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00 [00.535][mmc]: get sdc_type fail and use default host:tm4. [00.546][mmc]: SUNXI SDMMC Controller Version:0x40502 [00.590][mmc]: Best spd md: 4-HS400, freq: 3-100000000, Bus width: 8 [00.596]sunxi flash init ok [00.600]Loading Environment from SUNXI_FLASH... OK [00.609]usb burn from boot delay time 0 weak:otg_phy_config [00.623]usb prepare ok [01.426]overtime [01.430]do_burn_from_boot usb : no usb exist [01.434]boot_gui_init:start FAT: Misaligned buffer address (7be7be58) 32 bytes read in 4 ms (7.8 KiB/s) tcon_de_attach:de=0,tcon=2[01.567]boot_gui_init:finish [01.570]bmp_name=bootlogo.bmp 2764854 bytes read in 40 ms (65.9 MiB/s) [01.633]update dts ** Unrecognized filesystem type ** [01.642]load file(ULI/factory/rootwait init.txt) error. ** Unrecognized filesystem type ** [01.655]load file(ULI/factory/snum.txt) error. [01.659]name in map mac ** Unrecognized filesystem type ** [01.668]load file(ULI/factory/wifi_mac.txt) error. ** Unrecognized filesystem type ** [01.680]load file(ULI/factory/bt_mac.txt) error. ** Unrecognized filesystem type ** [01.692]load file(ULI/factory/selinux.txt) error. ** Unrecognized filesystem type ** [01.704]load file(ULI/factory/specialstr.txt) error. [01.713]update part info [01.738]update bootcmd [01.740]No ethernet found. Hit any key to stop autoboot: 0 [02.050]Starting kernel ... [02.053][mmc]: mmc exit start [02.101][mmc]: mmc 2 exit ok [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.170 (akrd6@R740XD) (gcc version 5.3.1 20160412(Linaro GCC 5.3-2016.05) ) #80 SMP PREEMPT Wed Feb 15 17:22:30 CST 2023 [ 0.000000] Boot CPU: AArch64 Processor [410fd034] [ 0.000000] bootconsole [earlycon0] enabled [ 0.027874] BOOTEVENT: 27.858249: ON [ 0.242175] sunxi_i2c_probe()2209 - [i2c3] warning: failed to get regulator d [ 0.243164] sunxi_i2c_probe()2209 - [i2c5] warning: failed to get regulator d [ 0.244517] axp2101-regulator axp2101-regulator.0: Setting DCDC frequency fo unsupported AXP variant [ 0.244601] axp2101-regulator axp2101-regulator.0: Error setting dcdc frequecy: -22 [ 0.279245] [ac200] get ave_regulator_name failed! [ 0.279751] [ac200] pwm enable [ 0.363211] gpio_pin_4(229) gpio_request fail [ ▒[ 0.369727] uart uart1: get regulator failed [ 0.402346] [NAND][NE] Not found valid nand node on dts [ 0.411005] sunxi-wlan soc@03000000:wlan: get gpio chip_en failed [ 0.417894] sunxi-wlan soc@03000000:wlan: get gpio power_en failed [ 0.550010] hci: request ohci1-controller gpio:232 [ 0.742282] axp2101_pek: axp2101-pek can not register without irq [ 0.752785] sunxi_ir_startup: get ir protocol failed [ 0.761135] VE: get debugfs_mpp_root is NULL, please check mpp [ 0.761135] [ 0.769395] VE: sunxi ve debug register driver failed! [ 0.769395] [ 0.784659] mmc:failed to get gpios [ 0.865627] mmc:failed to get gpios [ 0.901895] FD655: ==fd655_driver_probe==================== [ 0.908284] FD655: : (null) [ 0.909038] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 0.912260] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 0.926757] FD655: : (null) [ 0.929915] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.935814] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.941713] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.947606] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.953859] FD655: register_fd655_driver: Successed to add fd655 module [ 0.973520] failed get gpio-spdif gpio from dts,spdif_gpio:-2 [ 0.983217] [audio-codec]dachpf_cfg configurations missing or invalid. [ 0.990865] lineout_vol:26, linein_gain:3, fmin_gain:3, digital_vol:0, adcdr_cfg:0, adchpf_cfg:0, dacdrc_cfg:0, dachpf_cfg:0, ramp_func_used:1, pa_msleep_tme:160, pa_ctl_level:0, gpio-spk:0 [ 1.014903] sndhdmi sndhdmi: ASoC: CPU DAI (null) not registered [ 1.021698] sndhdmi sndhdmi: snd_soc_register_card() failed: -517 [ 1.035293] sunxi-ahub-cpudai 5097000.cpudai3-controller: ahub cpudai id invlid [ 1.068733] ERROR: pinctrl_get for HDMI2.0 DDC fail [ 1.078344] tv_probe()1435 - of_property_read_string tv_power failed! [ 1.174637] cpu cpu1: opp_list_debug_create_link: Failed to create link [ 1.182156] cpu cpu1: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.189771] cpu cpu2: opp_list_debug_create_link: Failed to create link [ 1.197234] cpu cpu2: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.204828] cpu cpu3: opp_list_debug_create_link: Failed to create link [ 1.212279] cpu cpu3: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.684491] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 context=u:object_r:default_prop:s0 tclass=property_service permissive=1 [ 1.684491] [ 1.702686] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 context=u:object_r:dalvik_prop:s0 tclass=property_service permissive=1 [ 1.702686] [ 2.576915] FAT-fs (mmcblk0p15): bogus number of reserved sectors console:/ $ [ 8.720978] apexd: Failed to walk /product/apex : Can't open /prduct/apex for reading : No such file or directory ^C 130|console:/ $ [ 22.711942] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 22.913822] SSV6XXX_SDIO mmc2:0001:1: vendor = 0x3030 device = 0x3030 [ 22.947618] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 22.958352] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RE RCE !! [ 23.030814] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 23.057388] SSV6XXX HCI TX Task started. [ 23.135876] Enable HCI TX aggregation [ 24.042450] SSV WLAN driver SSV6006C: Set new macaddr [ 24.060821] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e4 of type 2 is added. [ 25.361805] SSV WLAN driver SSV6006C: Set new macaddr [ 25.386662] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e5 of type 2 is added. [ 27.173711] selinux: avc: denied { set } for property=sys.config.rootservice pid=2978 uid=0 gid=0 scontext=u:r:rootservice:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=1 [ 27.173711] [ 27.207603] audit: rate limit exceeded [ 30.214797] apexd: Can't open /product/apex for reading : No such file or directory U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) /system/bin/sh: syntax error: unexpected '(' 1|console:/ $ DRAM:This DRAM setup is currently not supported. /system/bin/sh: DRAM:This: inaccessible or not found 127|console:/ $ [ 34.750480] selinux: avc: denied { set } for property=supolicy.loaded pid=3902 uid=0 gid=0 scontext=u:r:toolbox:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=1 [ 34.750480] U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) /system/bin/sh: syntax error: unexpected '(' 1|console:/ $ DRAM:This DRAM setup is currently not supported. /system/bin/sh: DRAM:This: inaccessible or not found 127|console:/ $

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

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

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

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

Recently has appeared some 3566 tv boxes in the wild, would be doable to run armbian on them? Since Rockchip seems kinda dedicated to openness the same goes for the RK3566?

🏆 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 EMMC Ning Mainline Kernel: Armbian EMMC official image Armbian Desktop Gnome kernel The Latest official Debian BookWorm Server Kernel Minimal The Latest official 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+ @fevangelou Linux Flash Tutorial @WINEDS Build Armbian for Maxios Lan Chip Board unofficial images: Edge: [Link] Desktop Resolute Server Resolute Server Trixie Current: [Link] Desktop Resolute Server Resolute Server Trixie How to Flash it: [Link] Emmc 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 For Boards Newer than 2025: Follow @WINEDS method to compile Armbian with the ethernet and wifi drivers Front Panel Display: Tutorial Repo: https://github.com/jefflessard/tm16xx-display 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

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

Hi everyone! 👋 I managed to get Armbian running on a generic RK3518 TV box — mainline U-Boot, onboard Ethernet, and AIC8800D80 SDIO Wi-Fi all working. I couldn't find a single RK3518 thread here when I started, so I wrote everything up to help the community. Full step-by-step guide, device tree, and the loader binaries I built are in my GitHub repo: 👉https://github.com/juliovendramini/rk3518_armbian Happy to answer questions. Hope it helps someone! 🙂

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

After initially and successfully booting Armbian 23 jammy from an SD memory card in the TF slot or from a USB flash device in the blue 3.0 port, I had installed Armbian using the /root/install-aml.sh, removed the SD card/USB flash and rebooted Armbian easy peasy. It worked fine for a while. My thread about it is here at this link. But it got bricked, seemingly by itself after a power failure in the home. I managed to recover it with an image of Android, however, all of Armbian was deleted (and no backup either haha 😉). Here is a tutorial to recover this box and the steps may also work for other tv boxes that have the S905x / S905x2 / S905x3 chip. Download Amlogic Burn Card Maker v2.0.3 (not other versions) from Here or Here. Download stock android firmware T95MAXplus-X3-9.0-2GB4GB-6330-0720-20200616-Android.rar from Here or the same firmware but as img a file from MEGA Unpack the archive file in 7zip, if you have the rar file. But there is no unpacking to do if you have the img file. Insert a new good micro-SD memory card into the SD card adapter, and plug it into your PC - be sure there is only one single partition on the SD memory card formatted as FAT32 Run the 'Burn_Card_Maker.exe' executable file. Make sure it is version 2.0.3 Change language to English if it is not already in that: - Click on the Chinese menu (or garbled text menu) in the upper-left corner, and choose the second option. - Dialog screen appears and now simply select 'English Version' and click OK button. Select your SD memory card drive letter under 'Choose Disk:' - you may need to use Disk Management in Windows and apply a drive a letter to the SD memory card. Check mark the Yes box on under 'To Partition and Format' or tick the box 'Formatting SD card' - a new menu pane will popup. follow through and format the SD memory card. Check mark the Yes box on under the Normal SD bootloader for Erase Bootlooader Check mark the Yes box on under the Erase Flash for Normal Flashing Do NOT check mark the Yes on (click to Uncheck it) under 'reboot'. Click 'Open' button under 'Select Burn Package f:' and select the factory stock Android file T95MAXplus-X3-9.0-2GB4GB-6330-0720-20200616.img - make sure there are no spaces in the file name of the img Last step in Burn_Card_Maker: Press 'Make' button and wait to finish. Go to the TV box. Disconnect the power cable from the tv box device. Then insert the micro SD memory card in your tv box device and power on the device. If it didn't boot at all, the you may need to use the toothpick method. Disconnect power cable again. Put a toothpick into the audio jack, press and hold the reset button while you insert the power cable. The tv box will enter into recovery and the firmware will be flashed automatically. Be patient and wait up to 10 minutes. After the TV BOX fully starts, remove the micro SD Card. and the update will completed. The T95 Max (whatever it is) graphic logo will appear and stock Android 9 will start.

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

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

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

I'm getting this weird graphical artifact on a Radxa Rock 4SE connected to a TV via HDMI. It covers roughly a third of the right side of the display, note that the terminal window is covered by the artifact but the cursor is above it. I started from a Debian minimal image and added the desktop environment via armbian-config. The artifact is visible on both GNOME and KDE Plasma (with fully updated system on both rolling and stable) but not with XFCE. It also disappears with resolutions lower than 4K or switching to tty. Any idea what might be causing this?

Hi, I need help with flashing my tv box or installing it on linux. I would also be happy if you could run an armbian or similar minimal system. I would like to run a website on it at home. I already did it for an old venz v10 for a friend and installed armbian on it and he really liked it, but my couldn't install it with a memory card, the on new box 1. System Information Google Android Tv Box - Android 14 Android Version: 14 (Upside Down Cake) API Level: 34 Android Security Patch Level: 2025-01-01 Rooted Device: No Android ID: 5c4aa62950194797 Build ID: rk3528_box_32-userdebug 14 UTT2.241219.001 eng.hxws.20260124.163421 release-keys Codename: REL Fingerprint: google/blueline/blueline:14/UTT2.241219.001/eng.hxws.20260124.163421:userdebug/release-keys ID: UTT2.241219.001 Incremental: eng.hxws.20260124.163421 Java Runtime Version: Android Runtime 0.9 Java Virtual Machine Version: ART 2.1.0 Java Virtual Machine Heap Size: 128 MB Kernel Architecture: armv7l Kernel Version: 6.1.118 (hxws@PowerEdge-R720-8) (Android 10087095, +pgo, +bolt, +lto, -mlgo, based on clang 17.0.2 of r487747c (https://android.googlesource.com/toolchain/llvm-project d9f89f4d16663d5012e5c09495f3b30ece3d2362), LLD 17.0.2) #124 SMP PREEMPT Wed Jan 21 10:25:12 CST 2026 Tags: release-keys Type: userdebug Google Play Services Version: < None > Huawei Mobile Services Version: OpenSSL 1.1.1 (compatible; BoringSSL) OpenSSL Version: 1.2.13 ZLib Version: 1.2.13 2. Hardware and Processor (CPU/Device) Device Type: TV Manufacturer: Google Model: android_tv_box Brand: google Motherboard: RK3528 Device: blueline Hardware: rk30board Platform: rk3528 Product: blueline Processor: RK3528, 4 cores SoC Model: RockChip RK3528 Core Architecture: 4x ARM Cortex-A53 @ 2016 MHz Instruction Set: 64-bit ARMv8-A (32-bit mode) CPU Version: r0p4 CPU Cores: 4 CPU Clock Range: 408 - 2016 MHz CPU Utilization: 5% Scaler Controller: Interactive Supported ABIs: armeabi-v7a, armeabi Supported 32-bit ABIs: armeabi-v7a, armeabi AES/ASIMD/NEON/PMULL/SHA1/SHA2: Supported 3. Memory and Storage (RAM/Storage) Installed RAM: 2 GB Total Memory: 1920 MB Available Memory: 1221 MB Memory Used: 707 MB (36% of 1.9 GB) Total Internal Storage: 11.00 GB Free Internal storage: 10.11 GB Storage usage: 914 MB (8% of 11 GB) 4. Display and GPU (Display) Display: 1920 x 1080 (Full HD, 16:9) Screen resolution: 1920 x 1080 xdpi / ydpi: 320 / 320 dpi GPU manufacturer: ARM GPU renderer: Mali-450 MP Refresh rate: 60 Hz Default orientation: Landscape OpenGL ES version: 2.0 GPU version: OpenGL ES 2.0 OpenGL ES extensions: (List: GL_EXT_debug_marker, GL_OES_texture_npot, GL_OES_vertex_array_object, GL_OES_compressed_ETC1_RGB8_texture, GL_EXT_compressed_ETC1_RGB8_sub_texture, GL_OES_standard_derivatives, GL_OES_EGL_image, GL_OES_depth24, GL_ARM_rgba8, GL_ARM_mali_shader_binary, GL_OES_depth_texture, GL_OES_packed_depth_stencil, GL_EXT_texture_format_BGRA8888, GL_OES_vertex_half_float, GL_EXT_blend_minmax, GL_OES_EGL_image_external, GL_OES_EGL_sync, GL_OES_rgb8_rgba8, GL_EXT_discards_framebuffer, GL_OES_get_program_binary, GL_ARM_mali_program_binary, GL_EXT_shader_texture_lod) 5. Network and Connections (Network/Bluetooth/USB) Network: WiFi Telephony: None Wi-Fi Status: Enabled SSID: BSSID: 02:00:00:00:00:00 Hidden SSID: No IPv4 Address: 192.168.1.35 IPv6 Address: fe80::5ef3:83b1:27d0:574a Signal Strength: -46 dBm (Excellent) Link Speed: 54 Mbps Frequency: 2427 MHz Gateway: 192.168.1.254 Netmask: 255.255.255.0 DNS1: 192.168.1.254 DHCP Lease Time: 24 hours 5 GHz Band: Supported Wi-Fi Aware: Not Supported Wi-Fi Direct: Supported Bluetooth: Enabled Bluetooth Version: 4+ USB Device - Linux 6.1.118 ehci_hcd EHCI Host Controller: (Serial Number: ff100000.usb, ID: 1D6B-0002, Class: 09/00, Speed: 480 Mbps) USB Device - Linux 6.1.118 xhci_hcd xHCI Host Controller: (Serial Number: xhci-hcd.4.auto, ID: 1D6B-0002, Class: 09/00, Speed: 480 Mbps) USB Device - YICHIP Wireless Device 6. Other Data Audio: HDMI 7.1 Codecs: Widevine L3 (SD only) Wireless Debugging: Enabled IP Address and Port: 192.168.1.35:40729 Wi-Fi pairing code: 642947 IP address and port (for pairing): 192.168.1.35:40035 Device features: (List: android.hardware.audio.output, android.hardware.bluetooth, android.hardware.bluetooth_le, android.hardware.camera, android.hardware.camera.any, android.hardware.camera.external, android.hardware.camera.front, android.hardware.cetherandroid.hdware.mi android.hardware.keystore.app_attest_key, android.hardware.location, android.hardware.location.network)

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

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

Hi, I can't find an image for my TV box and I was wondering if anyone has one that I could use on the device. Thanks for your help