Rockchip CPU Boxes Latest Topics

CSC Armbian for RK322x TV box boards

Wed, 08 Jan 2020 20:31:33 +0000

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

Rupa X88 Pro 13 - RK3528 board with images

Fri, 05 Apr 2024 03:20:18 +0000

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

Ambian TV box rk3528

Thu, 14 Sep 2023 16:43:34 +0000

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

CSC Armbian for RK3318/RK3328 TV box boards

Fri, 16 Apr 2021 10:30:36 +0000

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

Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G

Tue, 20 Jun 2023 23:56:34 +0000

🏆 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]

Current: [Link]

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

Quote

sudo cat > /lib/firmware/brcm/brcmfmac4335-sdio.txt << "EOF"
# bcm94335wlcspMS_ES50_RC171p24p23_04052013_AM_mdfy_PAparam.txt -- 4/5/2013 by Murata, based on bcm94335wlcspMS_ES50_RC171p24p20_04022013_AM.txt, changed PA parameters and txidxcap parameters and ccode.
# bcm94335wlcspMS_ES50_RC171p24p20_04022013_AM.txt -- 4/2/2013 by Broadcom Corporation
# Use with AARDVARK_REL_6_30_171_24_23 -- Murata BCM4335 WLCSP 11AC Module
# Sample variables file for Murata Type-XJ ES5.0 (0x00 0x11) -- bcm94335wlcspMS_AM_P400.txt as original
sromrev=11
boardrev=0x1500
boardtype=0x064b
boardflags=0x10401001
boardflags2=0x0
#updated boardflags3 for forcing to enable external LPO
boardflags3=0x0800c08b
macaddr=00:90:4c:c5:12:38
#ccode modified by Murata
#ccode=0
ccode=XS
regrev=0
antswitch=0
pdgain5g=1
pdgain2g=1
tworangetssi2g=0
tworangetssi5g=0
femctrl=4
vendid=0x14e4
devid=0x43ae
manfid=0x2d0
#prodid=0x052e
nocrc=1
#otpimagesize=502
xtalfreq=37400
extpagain2g=1
extpagain5g=1
rxgains2gelnagaina0=2
rxgains2gtrisoa0=6
rxgains2gtrelnabypa0=1
rxgains5gelnagaina0=3
rxgains5gtrisoa0=5
rxgains5gtrelnabypa0=1
rxchain=1
txchain=1
aa2g=1
aa5g=1
ag0=0
ag1=0
tssipos5g=1
tssipos2g=1
#PA parameters (2G20M/2G40M/5G20M/5G40M/5G80M)
#PA parameters modified by Murata
#pa2ga0=-208,6208,-764
#pa2ga1=-203,6429,-793
#pa5ga0=-167,5736,-685,-157,5669,-670,-157,5548,-665,-141,5621,-664
#pa5ga1=-101,6543,-735,-99,6452,-731,-147,5743,-695,-75,6468,-723
#pa5ga2=-172,5903,-708,-160,5868,-698,-113,6264,-722,-125,5915,-684
pa2ga0=0xff31,0x1759,0xFD1D
pa2ga1=0xff35,0x18BB,0xFCEC
pa5ga0=0xff78,0x1715,0xFD49,0xff89,0x1714,0xFD57,0xff86,0x1652,0xFD62,0xffa9,0x1760,0xFD5E
pa5ga1=0xff56,0x1596,0xFD5F,0xff88,0x1764,0xFD45,0xff89,0x1632,0xFD65,0xff69,0x160E,0xFD49
pa5ga2=0xff5a,0x1667,0xFD4E,0xff5f,0x15F7,0xFD5E,0xff5a,0x1531,0xFD68,0xff6e,0x1587,0xFD6A
# Default Target Power for 2G -- 17dBm(11)/14dBm(54)/13dBm(MCS7,MCS8)/16dBm(6,MCS0)
maxp2ga0=74
cckbw202gpo=0
cckbw20ul2gpo=0
dot11agofdmhrbw202gpo=0x6666
ofdmlrbw202gpo=0x0022
mcsbw202gpo=0x88866662
# Default Target Power for 5G -- 14dBm(54)/13dBm(HT20-MCS7,VHT20-MCS8)/12dBm(HT40-MCS7,VHT40-MCS9)/11dBm(VHT80-MCS8/MCS9)/16dBm(6,20HT-MCS0)
maxp5ga0=74,74,74,74
# Low
mcslr5glpo=0
mcsbw205glpo=0x88866662
mcsbw405glpo=0xAAA88884
mcsbw805glpo=0xCCCAAAA6
# Mid
mcslr5gmpo=0
mcsbw205gmpo=0x88866662
mcsbw405gmpo=0xAAA88884
mcsbw805gmpo=0xCCCAAAA6
# High
mcslr5ghpo=0
mcsbw205ghpo=0x88866662
mcsbw405ghpo=0xAAA88884
mcsbw805ghpo=0xCCCAAAA6
#20MHz High Rate
sb20in40hrpo=0x0
sb20in80and160hr5glpo=0x0
sb20in80and160hr5gmpo=0x0
sb20in80and160hr5ghpo=0x0
#40MHz High Rate
sb40and80hr5glpo=0x0
sb40and80hr5gmpo=0x0
sb40and80hr5ghpo=0x0
#20MHz Low Rate
sb20in40lrpo=0x0
sb20in80and160lr5glpo=0x0
sb20in80and160lr5gmpo=0x0
sb20in80and160lr5ghpo=0x0
#40MHz Low Rate
sb40and80lr5glpo=0x0
sb40and80lr5gmpo=0x0
sb40and80lr5ghpo=0x0
dot11agduphrpo=0x0
dot11agduplrpo=0x0
tssifloor2g=80
tssifloor5g=160,190,240,260
#rpcal:use with 171.17 or later, compensates filter ripple
rpcal2g=0x0
rpcal5gb0=0x0
#cckdigfilttype[0-7] 0:default
cckdigfilttype=2
phycal_tempdelta=25
#GPIO 0 for SDIO HW OOB interruption
muxenab=0x10
#sd_gpout=0
#sd_oobonly=1
rssicorrnorm_c0=-3,-2
rssicorrnorm5g_c0=-1,0,-3,-1,0,-3,-3,-2,-4,-3,-2,-4
#txidxcap2g and txidxcap5g modified by Murata
#txidxcap2g=32
#txidxcap5g=44
txidxcap2g=36
txidxcap5g=36
paparambwver=1
EOF

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

A guide to installing Armbian on the H96 Max V11

Thu, 20 Jul 2023 12:41:41 +0000

A guide to installing Armbian on the H96 Max V11 (RK3318_V1.4 blue PCB)

What you will need

Your H96 Max V11 TV box with the power supply and the HDMI cable that came with it;
A TV or a monitor with an HDMI port;
A wired USB keyboard (or a wireless one with a USB dongle);
An Ethernet cable to connect to a router on your home network that has Internet access;
A Micro SD card (minimum 1GB, more if you're going to back up Android on your box before overwriting it with Armbian);
A USB card reader for Micro SD cards;
A Windows PC connected to your home network;

Installation steps

Download the experimental Armbian image (kernel 5.19.15 and libreelec patches — alas, that's the latest version that works correctly with our box) and a copy of the Multitool;
Burn the Multitool on the SD card using Rufus (no need to change any settings, just click "SELECT" and locate multitool.img.xz or drag and drop the file on Rufus and then click "START");
Connect your TV box to the TV or monitor, connect the keyboard, plug in the Multitool SD card and then plug in the power cord;
Wait a minute (while SD card partitions are being resized) for the Multitool main menu to appear, then select "Shutdown";
Unplug the power cord and the SD card, then plug the SD card into your PC. Two new drives should appear, labeled BOOTSTRAP and MULTITOOL. If you see both, skip the next step. If you only see the BOOTSTRAP, proceed to the next step;
Start Disk Management (press Win+X, K). Scroll down the list of disks (use the scrollbar, because mouse wheel doesn't work there) to locate your SD card, and on the MULTITOOL partition right-click, then press C, and click "Add", "OK";
Open the MULTITOOL drive in Windows Explorer (or your favorite file manager) and copy the downloaded Armbian image to the images folder;
Safely remove (eject) the SD card, plug it into the TV box and plug in the power cord. The Multitool main menu will appear in a few seconds;
If you don't care about stock Android firmware on your TV box, skip the next step. If you want to back up the Android firmware, proceed to the next step;
In the Multitool main menu select "Backup flash" and click through (there will be only one option). Name your backup file. Wait for the backup to finish. The backup file will be saved to the backups folder on the SD card's MULTITOOL partition;
Now it's time to replace Android with Armbian. In the Multitool main menu select "Burn image to flash" and click through (there will be only one option). Wait for the process to complete, then in the main menu select "Shutdown";
Unplug the power cord and the SD card, then replug the power cord. Wait a few minutes for Armbian to get everything ready for its first launch, and then follow the initial setup prompts;
You will be taken to the login prompt. Log in with the name/password for the regular user you've created;
Connect your TV box to your home network router with an Ethernet cable;
In Armbian, enter the command sudo cat /run/motd.dynamic and note the IP address assigned by the router to the TV box;
Now you will need to connect to your TV box on the home network via the SSH protocol. If you're running Windows 10 or later, press Win+X, I, Enter. A PowerShell/Terminal window will open. Enter the following command, substituting the words in angle brackets with actual values: ssh -l . Type yes at the prompt asking if you really want to connect to this unknown host. At the next prompt that appears, enter the password for the regular user you've created. Skip the next step;
If you're running an older version of Windows, you will need to download PuTTY, an SSH and Telnet client, set up an SSH connection to your TV box with the IP address above and log in with the name/password for the regular user;
Now it's time to fix the settings for the Wi-Fi chip that doesn't work out of the box on the H96 Max V11. To delete the old settings, copy the command sudo rm -f /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt and paste it by right-clicking in the SSH window, then press Enter;
To create the new settings file, enter (copy-paste) the command sudo nano /usr/lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt
The nano text editor will open with a new empty file;
Now open this small text file (a copy of nvram_2734c.txt from this forum topic), press Ctrl-A to select all text in it, then Ctrl-C to copy it to the clipboard;
Switch to the SSH window, right-click to paste the copied text to nano then press Ctrl-S to save and Ctrl-X to exit;
Enter (or copy-paste) the command sudo reboot -f to reboot Armbian. After that you can either close the SSH window and proceed with the physical console or start a new SSH session once Armbian has restarted;
Enter (or copy-paste) the command sudo apt update && sudo apt install armbian-config
After the update and installation is completed, run armbian-config to configure various software and hardware settings (including Wi-Fi). It is recommended to select "Freeze" in System settings to disable Armbian kernel upgrades because our kernel is compiled with custom patches enabling HDMI output on H96 Max V11 to work properly that are unavailable in other kernel versions.

Trying to boot Armbian on LinknLink iSG Box SE

Mon, 06 Apr 2026 13:39:21 +0000

I recently did some trying to boot Armbian on this box and eventually got it not to recognize "Loader" mode using the reset button.

It was working before I eventually flashed an not so compatible u-boot. I knew the risks, sh1t happens

I was trying to boot Armbian from USB by the way, that is why I tried to do this.

I discovered that the original firmware is the same as a H96 Max M1 PLUS as we can see from the official firmware file naming:

rk3528_l001_H96_Max_M1PLUS_6621_64BIT_TAR-20251112.2200.img

My question, as anyone had experience with this board?

The idea is to ditch the original firmware and run HA on Armbian (I previously did this with another box using docker).

I know the only option now is to "short" the eMMC in order to achieve "Maskrom" mode but there are no obvious pin points on the board.

H96 Max RK3528 - Cannot boot Armbian from TF/SD card

Tue, 14 Apr 2026 09:10:17 +0000

Hello,
I have H96 Max TV box with RK3528 chip (4GB RAM, 64GB eMMC, Android 13, build RZX.V01.20240924). Board: RK3528_DDR3_8X4_V12.
Problem: Box does not boot from TF card at all. No HDMI output, no DHCP lease, nothing.
What I have:

TF card slot on the box
1x USB 2.0 port, 1x USB 3.0 port
No serial/UART adapter (DEBUG header visible on PCB but not connected)
Android 13 still working on EMMC
ADB access with root

What I tried:

Built Armbian with BOARD=rk3528-tvbox BRANCH=legacy BUILD_MINIMAL=yes RELEASE=trixie
Extracted DTB from Android boot partition, added to image
Wrote image to TF card with dd
Verified RKNS header at sector 64 - correct
Tried replacing idbloader with one from our custom U-Boot build
Original U-Boot on EMMC appears to ignore TF card completely

Question: How to make original U-Boot boot from TF card? Or is there a way to install Armbian to EMMC safely while keeping ability to recover?
Device AIDA64 info:

Model: H96_Max_RK3528
Device: rk3528_box
Hardware: rk30board

Thank you!

Efforts to develop firmware for H96 MAX M9 RK3576 TV Box 8G/128G

Sat, 01 Jun 2024 04:58:35 +0000

If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars.

Armbian Needs you help!

Product Specification:

Chipset: Rockchip RK3576 Octa Core ARM Mali G52 MC3

WIFI: WiFi6 11ax 1x1 80 MHz
wifi controller: AP6275P

RAM: DDR4 4GB/8GB

ROM: eMMC 32GB/64GB/128GB

OS: Android 14.0 || Armbian Vendor 6.1

Ethernet: 1000M Standard RJ-45

Bluetooth: BT 5.0
The RK3576 is indeed a lower-cost SoC but features four Cortex-A72 and four Cortex-A53 cores instead

Android Base Files:

H96-RK3576-ANDROID.dts

H96-RK3576-BOX.dtb

RK3576_MiniLoaderAll.bin

Vendor Kernel DTS:
@RealAn H96-RK3576-VENDOR.dts

Mainline status:
Verify

wifi controller: AP6275P

Wifi Driver:
https://drive.google.com/file/d/1n6x4tg5Xh24nWllOTJTq1ldVyDkK8W2Q/view?usp=sharing

Flashing Tools:

https://drive.google.com/file/d/1nLgPCBN0qmbzufWDFmISYc92JUpvwMPc/view?usp=sharing

build_armbian.csc:

https://drive.google.com/file/d/1VNR5QJlPylPsce9PI9O2TB3wOpshK2Bh/view?usp=sharing

@hzdm Stock Firmware: method

https://drive.google.com/file/d/1zLGvIxLE6vf8iSTjsyEr-Ly4MZ6ZahBB/view?usp=sharing

Flashing Firmware Tutorial

Factory Firmware for H96 Max M9
https://disk.yandex.ru/d/pWGEtRel0P9ejg
https://drive.google.com/drive/folders/1g63F8fGSLEA9iK2_Mqzd6F0xfaTRnGlm?usp=sharing

Factory Firmware for H96 Max M9S
https://disk.yandex.ru/d/H17eGTYCjgmCsg

https://drive.google.com/drive/folders/1Q360l5XbTVsWIvWkqy2xJ0sLpqHRSApM?usp=sharing

TTL debug:
RX TX GND pins:

Enable SDCARD Reader:
@rustamt method from 4pda

Force board Maskrom Mode
Maskrom Pins:

Quote

Armbian for RK3128 TVBox board

Wed, 15 Apr 2026 10:03:45 +0000

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

RK3566 and Armbian

Sun, 30 May 2021 18:57:39 +0000

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?

20USD 4GRAM RK3528 host (cheap dq08 tvbox)

Thu, 11 Apr 2024 21:32:13 +0000

What you need:
- A DQ08 (got mine from aliexpress)
- An sdcard (4g if you want to use external usb3 ssd or 32g if not)

If you're lazy and trust my image (you shouln't, as I can bundle malwares inside):
- flash this using this - usb2serial included
- put in DQ08 and plug it in ethernet
- scan for the ip using this
- in windows terminal, using password=1234:

ssh root@BOXIP

To build the sd card, i've used this tutorial:
- install wsl on your windows
- apply this patch

Spoiler

sudo wget --output-document=/usr/share/keyrings/armbian-next.gpg https://apt-test.next.armbian.com/armbian-next.gpg
cat << EOD | sudo tee /etc/apt/sources.list.d/armbian-next.list
deb [signed-by=/usr/share/keyrings/armbian-next.gpg] http://apt-test.next.armbian.com armbian main
deb [signed-by=/usr/share/keyrings/armbian-next.gpg] http://apt-test.next.armbian.com armbian-$(lsb_release -cs) main
EOD
sudo apt update && sudo apt list --upgradable | grep -i armbian

- open wsl shell
- install docker on wsl:

curl -fsSL get.docker.com | sh

- run docker:

sudo /etc/init.d/docker start

- permit to use docker:

sudo usermod -aG docker $USER

- open a new shell (important)
- follow this

Spoiler

git clone https://github.com/ilyakurdyukov/rk3528-tvbox.git
cd rk3528-tvbox
git clone --depth=1 https://github.com/armbian/build armbian-build
cp -R armbian-patch/* armbian-build/
cd armbian-build
./compile.sh build BOARD=rk3528-tvbox BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm
cd ../..
cat < rk3528-tvbox/build.sh
#!/bin/bash
cd /build
IMAGE=\`ls /build/armbian-build/output/images/*.img\`
losetup -D
losetup --partscan /dev/loop0 \$IMAGE
mount /dev/loop0p1 /mnt
cd devicetree
cp orig/*.dtsi .
patch -p1 -i rk3528-tvbox.patch
make NAME=rk3528-vontar-dq08 PRESET=LINUX
cp rk3528-vontar-dq08.dtb /mnt/dtb/rockchip
sed "s#fdtfile=.*#fdtfile=rockchip/rk3528-vontar-dq08.dtb#" -i /mnt/armbianEnv.txt
losetup -D
cat \$IMAGE | gzip > /build/\`basename \$IMAGE\`.gz
EOF
chmod a+x rk3528-tvbox/build.sh
docker run -it -v /dev:/dev --privileged=true -v `pwd`/rk3528-tvbox:/build --rm armbian.local.only/armbian-build:initial /build/build.sh

- flash the img file found in Linux/Ubuntu/home/XXX/armbian-build/output/image using this
- put in DQ08 and plug it in ethernet
- scan for the ip using this
- in windows terminal, using password=1234:

ssh root@BOXIP

If, like me, you want to use an USB3 SSD:
- flash the usb3 drive with the same image
- plug to the box
-

e2label /dev/sda2 ssd

- change /boot/armbianEnv.txt:

rootdev=LABEL=ssd

- reboot
- check free size with:

df -h /

- optional: remove unused boot partition:

fdisk /dev/sda

+ d + 1 + w + q
- optional: remove unused data partition:

fdisk /dev/mmcblk0

+ d + 2 + w + q

If, like me, you have usb2serial adapters:
- follow this but remove all parameters at the end of

./compile.sh build

and during kernel configuration, enable this: Device Drivers -> USB Support -> USB Serial Converter Support -> FTDI and PL230x

RK3288 Bluetooth Initialization Error: can't parse 'BT,power_gpio' on Debian 9 (JR3288lc Board)

Mon, 20 Apr 2026 07:25:16 +0000

Hello everyone,

I'm working with a JR3288lc development board with a Rockchip RK3288 processor and I'm currently facing a Bluetooth detection issue. I'm using the official Debian 9 image provided by the manufacturer, but the system doesn't see the Bluetooth module at all.

When I check the dmesg output, I see a specific parsing error related to the power GPIO in the Device Tree. It seems the kernel can't parse the power feature, which is preventing the module from working. How can I fix this? Any help would be greatly appreciated.

Request for archived RK3318 image (legacy 4.4.213 kernel)

Sun, 15 Mar 2026 04:00:22 +0000

Hello everyone,

I'm trying to locate a specific older Armbian build for an RK3318 TV box and hoping someone in the community might have it archived.

I'm looking for:

Version: Armbian 22.05.1 (or similar from that era)

Kernel: Legacy 4.4.213

Base: Debian Buster

Desktop: XFCE (or even a CLI version is fine)

The original download link from users.armbian.com/balbes150/ is now a 404. I understand this is a very old "Community Maintained" build and that RK3318 support has moved to newer kernels .

I'm specifically seeking this kernel version for a project. If anyone has this image file or a similar legacy build (kernel 4.4.x) for the RK3318 stashed away, could you please share it or point me to an alternative source?

Any help would be greatly appreciated!

Hardware: (e.g., H96 Max RK3318 - please specify your exact box model)

Thank you

HONGTOP H50 alias T98-3318-221-V1.1

Wed, 08 Oct 2025 21:22:14 +0000

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

RK3518-D4-V1.0

Tue, 12 Aug 2025 09:56:52 +0000

hello everyone!

I bought this tv box..https://www.aliexpress.com/item/1005009346784515.html?spm=a2g0o.order_list.order_list_main.11.79e81802pgNRxu

but after starting it was not possible to log in to googleplay even though I had a connection via wifi or ethernet. the preinstalled version for applications was Aptoide TV..through it I wanted to update all applications (youtube, netflix, etc.) I managed to do that but no application could be started. the original file manager did not show the internal memory or USB disk or SD card until I managed to download ES file manager through aptoide and it showed my flash disk I installed HW info device and there I found out that it was an RK3528 chip.
so I wanted to flash the firmware and I used a rom image for H96max with the same parameters.
the firmware upgrade went OK but the device is dead. I can't find the correct firmware.
I'm attaching a photo--- maybe someone will recognize the board and identify which rom-img should be correct.
the seller can't help me in any way.

Request to adapt the compilation of shutuo-v8-rk3288 version armbian

Wed, 11 Mar 2026 01:39:02 +0000

I have dtb files used by manufacturers for compiling on the Android 5.1 system (OEM versions 2.17 and 2.19). It differs from boards like the firefly, for example: using a 100 Mbps network port, USB GPIO uses <0x50 0x0c 0x00>.

Can anyone help with adapting this board? I want to compile it for armbian.

2.17.dtb 2.19.dtb

Vontar KK MAX / HK1 RBOX R2 / R3 - RK3566 4GB/32GB(or 64GB)

Mon, 22 Apr 2024 12:42:29 +0000

Armbian 24.5.0 Bookworm images (linux-6.1/linux-6.6) for TVBoxes: Vontar KK MAX / HK1 RBOX R2 / HK1 RBOX R3

(the same dts/dtb should work for these TVBoxes)

Here is a dts and dtb files, working reworked for mainline:

hk1-rbox-r3-profile-kernel-6.1-6.6.zip

(original dts and dtb from TVBox rk-kernel-orig.zip)

Checked the following:

HDMI - works (need to check hot plugging)
HDMI sound - works
USB 2.0 - works
USB 3.0 - works
SPDIF - should work (I cannot to check)
SD-Card booting and detection - works
eMMC install on it (/sbin/nand-sata-install) and detection - works
RKDevTool installing and loading images on/from eMMC - works
GPU (bugs/frizzes on mainline are not canceled) - works
Hardware video acceleration(except for browsers) - works
Dualboot if you flash new bootloader (SD-Card boot high priority) - works

Here are the compiled Armbian images (Bookworm only) with integrated dtb:

https://www.mediafire.com/file/4dwf7ce922x7obq/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.1.87_cinnamon_desktop.img.xz/file

https://www.mediafire.com/file/fjwtxb5gjzip341/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.1.87_minimal.img.xz/file

https://www.mediafire.com/file/iuz4uijgjh5ry1r/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.6.28_cinnamon_desktop.img.xz/file

https://www.mediafire.com/file/kofyqabr5k6qxm8/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.6.28_minimal.img.xz/file

The one of this box itself is HK1 RBOX R3, the photo shows the pins for short to go to the Maskrom bootloader and UART pins:

Скрытый текст

A working bootloader(supports dualboot) on this hardware for RKDevTool tool just in case:

Loader.zip

Скрытый текст

Please note that RKDevTool flashing utility only needs to flash the .img file with the bootloader, i.e. you need to unpack the .xz archive somewhere first (for ex. you can use 7-zip).

Recommendations for installation on eMMC

Скрытый текст

It is NOT recommended to install these images using RKDevTool utility on eMMC memory card because ext4 file system is not optimized for eMMC memory lifetime.
It is recommended to install the image on SD-card and boot from it, then configure the system according to your wishes and install it on eMMC using the script "sudo /sbin/nand-sata-install" built into Armbian using the F2FS file system for eMMC - this will extend the life of this memory many times.

1. Booting from SD-card and after configuring Armbian you need to install the f2fs-tools dependency:

sudo apt update && sudo apt install f2fs-tools

2. Run the script:

sudo /sbin/nand-sata-install

Alternatively, you can pre-compile an F2FS image for SD-Card and eMMC and immediately burn such an image with RKDevTool.

Just add these parameters during compilation:

./compile.sh ROOTFS_TYPE=f2fs FIXED_IMAGE_SIZE=31744 PACKAGE_LIST_BOARD="f2fs-tools"

(Where you should use a fixed image size for F2FS - here I have chosen 31GB (+ boot partition about 250MB by default) for eMMC 32GB. Keep in mind that the image must fit on the your disk where Armbian is compiled and after installing such image on eMMC you will not be able to change its size on booted TVBox only via external SD-Card OS or etc....
See how big your eMMC is and set your value to -1GB.)

----------------------------------------------------

For those who want to build Armbian themselves, here are the instructions:

Скрытый текст

1. Basic instruction https://docs.armbian.com/Developer-Guide_Build-Preparation/

2. Before execute "./compile.sh" - copy the contents of the archive "hk1-rbox-r3-profile-kernel-6.1-6.6.zip" into next folders:

build\config\boards\hk1-rbox-r3.tvb
build\packages\blobs\hk1-rbox-r3\rk3566-hk1-rbox-r3.dtb

(where the build folder is our cloned Armbian repository and accordingly a new hk1-rbox-r3 folder should be created on the second path).

3. Before compilation, in the file hk1-rbox-r3.tvb we can edit the following:

If we use the BOARDFAMILY variable "media":

BOARDFAMILY="media"

Then when we execute "./compile.sh" and selecting our profile in the expert menu - the kernel 6.1 will build like a building block - and not compiled, it will take about tens of minutes, it will be built from precompiled distributions with the insertion of our dtb profile and only.

If we use instead of "media" the BOARDFAMILY variable "rockchip64":

BOARDFAMILY="rockchip64"

Its will already compile kernel 6.6 (on this date of publication) - it will take hours.

If you uncomment the variable:

SRC_CMDLINE="earlycon=uart8250,mmio32,0xfe660000"

The UART will display the kernel booting - useful for debugging.

UPD:
Added to images "f2fs-tools" package, added loader to support dualboot without touching the original Android(or other OS) image on eMMC - priority is given to SD-Card.
Boot will be from SD-Card if there is on boot partition exist folder and file \boot.scr or extlinux\extlinux.conf - uboot(both: original Android and compiled for Armbian) searches for this path and file if it found this file, it will load from device which contains this file. mmc1(SD-Card) - first, mmc0(eMMC) - second.
For correct priority loading it is necessary to replace the main bootloader which is in the archive Loader.zip - if you have an Android it is enough to flash only this bootloader as Loader at 0x0 offset using RKDevTool utility, the rest of the eMMC part should not be touched if the OS and settings we need are there. U-boot on eMMC must be original or Armbian and preinstalled at offset 0x4000.
Instructions:

Скрытый текст

1. Unplug power of TVBox and any SD-card

2. Press the reset(upgrade) button on the box with a paper clip and same time plug USB-A-USB-A(Male-to-Male) to USB 2.0 of TVBox

Then sequentially:

(remember, uboot must be on eMMC (even the original Android or Armbian, i.e. if you erase the eMMC - the boot will not work) and this is relevant if you have installed the original MiniLoaderAll.bin, which does not support booting from SD-Card, but only from eMMC. Some TVBoxes may already have a bootloader that supports SD-card booting.).

Feel free to test...

Armbian on Giada DN74

Tue, 03 Feb 2026 11:59:04 +0000

Hi Armbian community

I have a Giada DN74 media player and would like to install Armbian on the box.

First I try (through SD card) some community maintained images like the Orange Pi RK3399 or the Firefly RK3399, but none of them worked.

Some google search teach me the Rockchip SoCs have fixed boot order (SPI->eMMC->SD card), and this cause my boot issue.

Then search again how boot from SD card, the only solution which I find is to erase eMMC, so I erase the eMMC using: "rkdeveloptool ef".

Unfortunately the box still not want to boot, so I open the box and try to identify the UART to see what is happening during the boot.

I find a 4 pin connector (see images) which I assume this is the UART console, have a label "MCU_D" (Micro Controller Units Debug?) and have 3,3V on first pin and GND on the last pin. I try to use this connector whit some USB-to-UART (PL2303 and FT232RL) with multiple baud rate (115200, 1500000) without output.

At this point was able still connect the box through USB and recover Android because MaskRom mode work fine.

After some reading on https://opensource.rock-chips.com/wiki_Boot_option I deiced to build u-boot using evb-rk3399_defconfig and flash to the eMMC (which wan was a big mistake).

I assume the box is try to boot from eMMC, but stuck there because is only u-boot on the eMMC nothing else.

Unfortunately still no UART output (maybe is not UART connector) but also no Maskrom mode.

If I understand right jock guide Unbrick Part, the only option to recover the box if I short EMMC CLK pin to GND.

So my question is somebody could help me identify the eMMC CLK pin?

Some extra info:

According the rk3399 hardware design guide, I need to find a 22 ohm resistor near to the CLK pin.

The eMMC is a Kingstone EMMC32G-TX29, and the manual write different CLK frequency's, I am don't know what I need to look.

I have a Fnirsi dst-210 3in1 (sure not the best), which I could use measurements but I do not know how to set the oscilloscope parameters to find the CLK.

Efforts to develop firmware for X96 X6 RK3566 (8G/64G)

Fri, 12 Jul 2024 14:33:24 +0000

Hi everybody,
I just bought an X96 X6 TV box (8G/64G) to run Home Assistant. However it is not popular so there is no Armina for it. Home Assistant requires Debian 11/12 (linux kernel, no desktop version) to operate. Hope everyone can help me. Thank you very much. I only need 1 file *.img file to install Home Assistant, no need: USB, wifi, Bluetooth... because it can be difficult.

Thank you very much!

Looking for help porting to an RK3328-based device

Mon, 04 Aug 2025 09:14:08 +0000

I'm looking for help porting to an RK3328-based device, the REV Robotics Control Hub. It ships running a custom version of Android 7. The compute board's physical layout is based on the 96Boards CE spec, and is visibly extremely similar to the Dragonboard 410c (https://www.96boards.org/product/dragonboard410c/). It has these specs and ports:

- Rockchip RK3328 SOC
- Rockchip RK805-1 (I believe from my research that this is a power management chip?)

- 1GB DDR3 RAM (2x Samsung K4B4G1646E-BYMA chips)

- 16GB eMMC (Samsung KLMAG1JETD-B041)
- Oddly, the manufacturer specs list this device as having 8GB eMMC 4.51, but the chip on my board at least is 16GB eMMC 5.1.

- I seem to have managed to kill the eMMC on my board during testing, so for now, I have to boot off of MicroSD

- RTL8821CU WiFi/BT chip
- 1x USB 3.0 Type A port

- 1x USB 2.0 Type A port

- 1x USB-C port
- HDMI

- MicroSD card reader

- 40 pin low speed expansion connector

- I believe specifically the UART on this connector is what is used to communicate with the other board in the device

- Internal UART connector for debugging

- I have successfully connected to it, and can view debug output from the boot process and interact with u-boot.

- The manufacturer's u-boot: https://github.com/REVrobotics/u-boot-controlhub-android

- The manufacturer's Android kernel: https://github.com/REVrobotics/kernel-controlhub-android
- Makefile: https://github.com/REVrobotics/kernel-controlhub-android/blob/main/arch/arm64/boot/dts/Makefile
- defconfig: https://github.com/REVrobotics/kernel-controlhub-android/blob/main/arch/arm64/configs/rockchip_smp_nougat_defconfig

The ROC-RK3328-CC "Renegade" SBC (https://libre.computer/products/roc-rk3328-cc/) is similar enough that some OS images designed for it can run on the Control Hub board
- OS images are in the Downloads section of the page
- Armbian has builds available for it: https://www.armbian.com/renegade/
- Firefly also has older OS images: https://en.t-firefly.com/doc/download/65.html

- Android 7.1 boot and displays, but has no working USB
- Android 8.1 and Ubuntu 18.04 confirmed to flash successfully and have HDMI and the USB 3 port working, but no USB 2 or Wi-Fi
- `sudo ./xrock reset maskrom` needed while board is in loader mode to put it into Mask ROM mode, otherwise OS installation using `upgrade_tool` may fail

- These images won't successfully boot off of MicroSD, only the internal eMMC.

If anyone has any guidance on how to go about this port, I would deeply appreciate it. Everything I have figured out so far is just via countless hours of trial and error; I'm not even close to being an expert on any of this stuff.

Efforts to develop firmware for H96 MAX V56 RK3566 4G/32G

Sat, 22 Oct 2022 02:42:16 +0000

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

EMMC Mainline Boot Latest official images:

Armbian EMMC image official
Armbian Desktop Gnome Latest official
Debian BookWorm Server Minimal Latest official

H96 MAX V56 RK3566 8gb Vendor Kernel 5.1.16
Tutorial Build Your own Armbian Rockchip Kernel vendor Kernel 5.1.16 Armbian
Joshua Riek Ubuntu Rockchip Images kernel 5.1
H96 MAX V56 RK3566 8gb Vendor Kernel 6.1.43
Tutorial Build Your own Armbian Rockchip Kernel vendor Kernel 6.1.43 Armbian
Joshua Riek Ubuntu Rockchip Images Kernel 6.1
H96 MAX V56 RK3566 Desktop Mainline Kernel 6.6.34
Pre-Build Desktop 22.04 Armbian Test Image (PT-BR)

unofficial images:
Edge: [Link]

Current: [Link]

How to Flash it: [Link]

Emmc

SD-Card unofficial images:
Tutorial SD-Card Version v0.5 DEBIAN12 BETA unofficial
Tutorial SD-Card Version v0.5 ARMBIAN23 BETA unofficial
EMMC unofficial images:
Tutorial MMC Version V0.7 DEBIAN12 BETA unofficial
Tutorial MMC Version V0.7 ARMBIAN23 BETA unofficial
EMMC HZDM unofficial images:
Tutorial EMMC Version v0.9 ARMBIAN BETA unofficial
EMMC unofficial images:
Tutorial EMMC Version v1.0 ARMBIAN unofficial
EMMC Hzdm Mainline Boot Custom unofficial images:
Tutorial Build Your own Armbian EMMC image unofficial
EMMC Raspiblitz HotnikQ unofficial images:
Tutorial Build Raspiblitz on EMMC Armbian Bullseye unofficial
EMMC Hzdm Mainline Boot unofficial images:
Tutorial Build Your own Armbian EMMC image unofficial

Community Official Images:

From @fevangelou Tutorial Flash on linux desktop

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 "Glued Image: 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 h96 Rk3566 TV-Box 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

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 Drivers:
https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view?usp=sharing

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/LibreELEC/brcmfmac_sdio-firmware/raw/master/BCM4335A0.hcd
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

Quote

sudo cat > /lib/firmware/brcm/brcmfmac4335-sdio.txt << "EOF"
# bcm94335wlcspMS_ES50_RC171p24p23_04052013_AM_mdfy_PAparam.txt -- 4/5/2013 by Murata, based on bcm94335wlcspMS_ES50_RC171p24p20_04022013_AM.txt, changed PA parameters and txidxcap parameters and ccode.
# bcm94335wlcspMS_ES50_RC171p24p20_04022013_AM.txt -- 4/2/2013 by Broadcom Corporation
# Use with AARDVARK_REL_6_30_171_24_23 -- Murata BCM4335 WLCSP 11AC Module
# Sample variables file for Murata Type-XJ ES5.0 (0x00 0x11) -- bcm94335wlcspMS_AM_P400.txt as original
sromrev=11
boardrev=0x1500
boardtype=0x064b
boardflags=0x10401001
boardflags2=0x0
#updated boardflags3 for forcing to enable external LPO
boardflags3=0x0800c08b
macaddr=00:90:4c:c5:12:38
#ccode modified by Murata
#ccode=0
ccode=XS
regrev=0
antswitch=0
pdgain5g=1
pdgain2g=1
tworangetssi2g=0
tworangetssi5g=0
femctrl=4
vendid=0x14e4
devid=0x43ae
manfid=0x2d0
#prodid=0x052e
nocrc=1
#otpimagesize=502
xtalfreq=37400
extpagain2g=1
extpagain5g=1
rxgains2gelnagaina0=2
rxgains2gtrisoa0=6
rxgains2gtrelnabypa0=1
rxgains5gelnagaina0=3
rxgains5gtrisoa0=5
rxgains5gtrelnabypa0=1
rxchain=1
txchain=1
aa2g=1
aa5g=1
ag0=0
ag1=0
tssipos5g=1
tssipos2g=1
#PA parameters (2G20M/2G40M/5G20M/5G40M/5G80M)
#PA parameters modified by Murata
#pa2ga0=-208,6208,-764
#pa2ga1=-203,6429,-793
#pa5ga0=-167,5736,-685,-157,5669,-670,-157,5548,-665,-141,5621,-664
#pa5ga1=-101,6543,-735,-99,6452,-731,-147,5743,-695,-75,6468,-723
#pa5ga2=-172,5903,-708,-160,5868,-698,-113,6264,-722,-125,5915,-684
pa2ga0=0xff31,0x1759,0xFD1D
pa2ga1=0xff35,0x18BB,0xFCEC
pa5ga0=0xff78,0x1715,0xFD49,0xff89,0x1714,0xFD57,0xff86,0x1652,0xFD62,0xffa9,0x1760,0xFD5E
pa5ga1=0xff56,0x1596,0xFD5F,0xff88,0x1764,0xFD45,0xff89,0x1632,0xFD65,0xff69,0x160E,0xFD49
pa5ga2=0xff5a,0x1667,0xFD4E,0xff5f,0x15F7,0xFD5E,0xff5a,0x1531,0xFD68,0xff6e,0x1587,0xFD6A
# Default Target Power for 2G -- 17dBm(11)/14dBm(54)/13dBm(MCS7,MCS8)/16dBm(6,MCS0)
maxp2ga0=74
cckbw202gpo=0
cckbw20ul2gpo=0
dot11agofdmhrbw202gpo=0x6666
ofdmlrbw202gpo=0x0022
mcsbw202gpo=0x88866662
# Default Target Power for 5G -- 14dBm(54)/13dBm(HT20-MCS7,VHT20-MCS8)/12dBm(HT40-MCS7,VHT40-MCS9)/11dBm(VHT80-MCS8/MCS9)/16dBm(6,20HT-MCS0)
maxp5ga0=74,74,74,74
# Low
mcslr5glpo=0
mcsbw205glpo=0x88866662
mcsbw405glpo=0xAAA88884
mcsbw805glpo=0xCCCAAAA6
# Mid
mcslr5gmpo=0
mcsbw205gmpo=0x88866662
mcsbw405gmpo=0xAAA88884
mcsbw805gmpo=0xCCCAAAA6
# High
mcslr5ghpo=0
mcsbw205ghpo=0x88866662
mcsbw405ghpo=0xAAA88884
mcsbw805ghpo=0xCCCAAAA6
#20MHz High Rate
sb20in40hrpo=0x0
sb20in80and160hr5glpo=0x0
sb20in80and160hr5gmpo=0x0
sb20in80and160hr5ghpo=0x0
#40MHz High Rate
sb40and80hr5glpo=0x0
sb40and80hr5gmpo=0x0
sb40and80hr5ghpo=0x0
#20MHz Low Rate
sb20in40lrpo=0x0
sb20in80and160lr5glpo=0x0
sb20in80and160lr5gmpo=0x0
sb20in80and160lr5ghpo=0x0
#40MHz Low Rate
sb40and80lr5glpo=0x0
sb40and80lr5gmpo=0x0
sb40and80lr5ghpo=0x0
dot11agduphrpo=0x0
dot11agduplrpo=0x0
tssifloor2g=80
tssifloor5g=160,190,240,260
#rpcal:use with 171.17 or later, compensates filter ripple
rpcal2g=0x0
rpcal5gb0=0x0
#cckdigfilttype[0-7] 0:default
cckdigfilttype=2
phycal_tempdelta=25
#GPIO 0 for SDIO HW OOB interruption
muxenab=0x10
#sd_gpout=0
#sd_oobonly=1
rssicorrnorm_c0=-3,-2
rssicorrnorm5g_c0=-1,0,-3,-1,0,-3,-3,-2,-4,-3,-2,-4
#txidxcap2g and txidxcap5g modified by Murata
#txidxcap2g=32
#txidxcap5g=44
txidxcap2g=36
txidxcap5g=36
paparambwver=1
EOF

sudo rmmod brcmfmac_wcc brcmfmac brcmutil
modprobe brcmfmac

Topic description:

the name of the topic is efforts but that's no effort at all, you should try compile your own images.

Transformers models: https://github.com/usefulsensors/useful-transformers
Usage: https://www.crowdsupply.com/useful-sensors/ai-in-a-box/
Usage: https://youtu.be/pN8mKZ5wpdQ

CSC Armbian for RK3288 TV Box boards (Q8)

Sun, 06 May 2018 15:20:22 +0000

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.

Thank you!

This is CSC Armbian for XT-Q8L-V10 boards, also known as Chiptrip Q8, Vsmart Q8, ENY 3288 Q8, etc...

All source code has been merged into Armbian mainline project.

I still keep my personal public Armbian fork for experimental features: https://github.com/paolosabatino/armbian-build

Nightly images: download directory

Quick installation instructions on eMMC:

Build or download your preferred Armbian image from Download directory and a copy of the Multitool;
Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition;
Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears;
OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option;
Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn;
Wait for the process to complete, then choose "Shutdown" from main menu;
Unplug the sd card, then push the power button for 1 second (the led will turn blue)
After 10 seconds HDMI will turn on and you will get logging messages;
On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user
Run armbian-config to configure timezone, locales and other personal options
Congratulations, Armbian is now installed!

Boot from SD Card/USB stick (with Armbian already installed in eMMC, empty eMMC or no eMMC😞

Build or download your preferred Armbian image from Download directory;
Burn the image on your SD card/USB stick;
Plug the SD card/USB stick in the device;
Push the power button for 1 second (the led will turn blue);
After 10 seconds HDMI will turn on and you will get logging messages;
On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user
Run armbian-config to configure timezone, locales and other personal options
Congratulations, Armbian is now installed!

Boot from SD Card/USB stick (with original firmware or other firmware):

In case your box has the original firmware installed, use the Multitool to erase the internal flash.

Don't worry, you will not brick your box: once the eMMC is emptied, the box will automatically boot from SD Card. This is called Maskrom mode and is common to all Rockchip devices. Instructions and download links for the Multitool are at the bottom of this post.

After erasing the internal eMMC, just follow the "Boot from SD Card" procedure above and then you are fine.

Boot priority:

Newer images (those with mainline kernel >= 4.14.50) now support booting from multiple devices.

Priority is fixed and boot devices are probed in this order:

External SD card
External USB storage device (Any USB Stick/Hard drive attached to USB host ports)
Internal eMMC

This way even if you install armbian to internal eMMC, you can still easily test different images booting from external devices.

Experts notes: when armbian is installed into eMMC you get U-boot installed too in eMMC. This is important to know because the box won't boot in Maskrom Mode, but instead will always boot the embedded U-boot, no matter if you put an sdcard/usb stick. In practice the embedded U-boot is totally responsible for the boot priority. If you want to restore the Maskrom Mode, just erase U-boot from eMMC using this command:

dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=8128 conv=sync,fsync

Current status:

Wireless: works. pretty fast and stable, signal is strong on my box;
Bluetooth: works. I was able to transfer files and stream audio without problems
USB ports: works, with autosuspend too. A quick benchmark show that transfer rate is quite good (topped at 34 MB/s)
USB OTG: works in host mode. Transfer rate is very good (> 40 MB/s)
MMC: works and is perfectly accessible as storage device. The images above with "eMMC friendly" have been tested and work when installed in eMMC using the standard armbian-config eMMC installer
SDCard: works. legacy kernel is limited to high speed, while mainline works fine in UHS mode too. A quick benchmark with a Samsung EVO card shows the promised 48Mb/s read speed.
Gigabit Ethernet: works, fast and reliably
HDMI: works perfectly
Serial: works
Audio: both HDMI audio and SPDIF connector works
IR remote: works on legacy and mainline kernels
Reboot/Suspend process: rebooting the device is a working in progress, at the moment sometimes it works and sometimes it doesn't. Suspend is still not available.
Hardware acceleration: everything which works for rk3288 boards applies here too. This guide or maybe the Media Testing Script will help you gain an hardware accelerated X11 and Chromium (using GL4ES I enjoyed Quake 2 from the start till the end, but also Quake and Quake III Arena work flawlessy, here a quick how-to to compile and install GL4ES)

Multimedia:

On mainline kernel 3D acceleration is provided by Panfrost driver and is already enabled.

Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/

Multitool:

The Multitool is a small but powerful tool to easy operate on internal eMMC flash of RK3288 devices.

Features:

Backup the content of internal eMMC
Restore a previously backed-up image to eMMC
Erase the eMMC (via fast blkdiscard or zero-fill as fallback)
Burn an Armbian (or LibreELEC) image directly on the eMMC
Provide a recovery shell for manual maintenance
Windows-friendly: everything is placed in a NTFS partition
Image compression format autodetection: they are decompressed on-the-fly during burn process
Network support for remote maintenance via SSH (instructions to access via network here)

Instructions are simple:

Download the image from here
Burn it on an sdcard
Open the NTFS partition with your preferred file manager
Place the images you want to burn on the device in images directory (backups will be stored in backups directory)
Plug the sd card in the RK3288 device
Power the device and wait few seconds, the Multitool menu will appear on screen and can be navigated with the keyboard

Last edit: 07/06/2020 - updated installation instructions

[Project] OpenAuto RK322x (Alpha) : Android Auto Running on Rockchip SOCs

Sat, 31 Jan 2026 03:52:45 +0000

Inspired by the incredible work @jock and @ilmich have done to make the RK322x platform stable on mainline Linux, I decided to tackle the application side of things. My goal was to turn these "e-waste" TV boxes into fully functional, low-latency Android Auto head units for our cars.

This fork of OpenAuto is built as one of my "Is it possible to turn this into that?" projects. It turned out to be one heck of a nightmare to pull off, but at the same time a lot of fun because I can see the potential of these TV Boxes as something you can actually put in your car and turn into a usable head unit!

System Requirements

Target Device: RK322x TV Box (e.g., MXQ Pro 4K).
OS: Armbian Bookworm or Trixie (Kernel 6.1+ recommended).
RAM: 1GB recommended.
FFMPEG Installed: This build requires a specific build of ffmpeg that can be found here.

Release: v2.0.0-alpha

This release represents a major architectural overhaul. I have removed heavy dependencies (PulseAudio, QtAudio, GStreamer) in favor of a lean, direct-to-hardware pipeline using RtAudio (ALSA) and FFmpeg v4l2_request.

Download:
https://github.com/Harleythetech/openauto-rk3229-armbian/releases

Technical Details

Video Engine: Switched from GStreamer to a custom FFmpeg + V4L2-Request backend.
- Leverages the v4l2drmprime patch set for Zero-Copy rendering.
- Enables full hardware H.264 decoding on Rockchip stateless decoders.
- Result: Stable 1080p 60fps stream on a 1GB RAM device.
Audio Overhaul: Replaced PulseAudio and QtAudio with RtAudio. This creates a direct, low-latency path to the ALSA hardware driver.
Display: Targets linuxfb (Framebuffer) by default instead (eglfs and ffmpeg have issues when you run them together due to DRM master lock)

Configuration
This release requires a specific ALSA configuration to allow audio mixing (dmix) without PulseAudio. Create/Edit /etc/asound.conf:

pcm.!default {
    type asym
    playback.pcm "dmix_hdmi"
    capture.pcm "plug_null"
}
ctl.!default {
    type hw
    card 0
}
pcm.plug_null {
    type plug
    slave.pcm "null"
}
pcm.dmix_hdmi {
    type dmix
    ipc_key 1024
    ipc_perm 0666
    slave {
        pcm {
            type hw
            card 0
            device 0
        }
        format S16_LE
        rate 48000
        channels 2
        period_size 512
        buffer_size 4096
    }
    bindings {
        0 0
        1 1
    }
}

Known Issues

Invisible Cursor: The mouse cursor works but is currently invisible when the FFmpeg video backend is active (rendering layer order issue).
Backend Fallback: In rare edge cases where DRM initialization fails, the app may incorrectly default to Qt software output.
Probably more, i haven't tested it that much

Development Status: Active & Seeking Contributors Currently, I am the sole maintainer focusing on the RK322x platform (specifically the RK3229).

I am actively looking for developers interested in expanding support to other devices (such as RK3328, RK3399, or Allwinner H3/H6). If you have experience with C++, Qt, or V4L2/DRM and want to help turn these TV boxes into capable head units, contributions are highly welcome!

Repository: https://github.com/Harleythetech/openauto-rk3229-armbian

Credits:

@jock and @ilmich for ffmpeg patches and the csc-armbian-for-rk322x-tv-box-boards
opencardev for openauto and aasdk

X88 RK3328 android box looking to install armbian photos attached

Tue, 27 Jan 2026 11:41:03 +0000

Hi All

new here please forgive if non technical which i am , looking to install armbian into this existing X88 box I have attached photos for experts which one is the correct one to flash,

Edit ArmbianEnv.txt when machine is unable to boot?

Tue, 30 Dec 2025 15:40:26 +0000

Hello. I recently got a vontar-dq08 working with armbian. I used someone's build for a x88pro, so I replaced the dtb with the one that came on my board. After editing the ArmbianEnv.txt and resetting, it did not boot. Idk if it's a typo on my end or the tree not working, but to make it boot I would just have to change ArmbianEnv.txt, but taking the sdcard out and plugging it in my computer I can't find the file in /boot

How can I revert the ArmbianEnv.txt when my machine doesn't boot?

Efforts to develop firmware for Vontar KK Max 8gb/128gb"

Sun, 25 Jun 2023 20:49:08 +0000

Vontar KK Max 8gb/128gb:

Original Android 11 ROM image

Which tag do I put (required field) since there's no rk3566 available and the Armbian image that worked for me is the station-m3 ones?

DTB files:

01_dtbdump_rockchip,rk3566-box-demo-v10.dtb

(can't attach: "Sorry, an unknown server error occurred when uploading this file.

(Error code: -200)" message)

ok 02_dtbdump_rockchip,rk3566-box-demo-v10.dtb

ok 03_dtbdump_rockchip,rk3566-box-demo-v10.dtb

*obtained using the extract-dtb tool

I don't know how to join these into a single .dtb to point at into the working Armbian /boot/extlinux/extlinux.conf file.

the only .dtb file that worked for me with the station-p2 (not posted here because it crashes and won't boot anymore if I made run "apt upgrade" which would be desirable) station-m3 image but only recognizes 4gb RAM:

rk3566-firefly-roc-pc.dtb

(idk if this is due a kernel's limitation or the hardware information contained in this .dtb file)

if somebody could tell me...

Loader file:

ok MiniLoaderAll.bin

uBoot file:

uboot.img

(can't attach: "Sorry, an unknown server error occurred when uploading this file.

(Error code: -200)" message)

Need help and advice

Sun, 14 Dec 2025 14:47:39 +0000

Hallo everyone i really want to filn out how to install armbian onto one of 2 devices i have 2 boxes but ill focus only on one for now.

The tvox is a Tangka

Cpu = RK3228A

Storage chip = SKhynix H9TQ64A8GTMC

Wifi chip = s9012p

Where could i find the compressed file of the .iso sothat i can flash the firmware onto my tvbox and what software/drivers will i need on windows 10 or ubuntu (preferably win10) id really appreciate if you guys can help me out.

I dont have a sdcard only a makeshift working male to male usb adaptor.

Efforts to develop firmware for Lemfo HK1 RBOX K8S 4G/64G

Sun, 04 Aug 2024 23:40:17 +0000

Hello People, I Bring to you the Lemfo HK1 RBOX K8S 4G/64G.

This box came with Android 13 and can be rooted easy, follow some specs of the box:

Processor: Rockchip RK3528

GPU: Mali 450

Memory: 4Gb (micron)

Storage: 64Gb (eMMC 5.1 Samsung)

Network: PHY Integrated stmmac-0:02 Driver RK630 100Mbps

Wireless: 5G driver: rtl8822cs on gpio

Bluetooth: 5.1

USB 3.0: 01 5Gbps

USB 2.0: 01

HDMI: 01

TV-Out: 01

Power: 5v 2A

Aliexpress link: Lemfo HK1 Rbox K8S

What is Working:

HDMI: partial (read bellow)

Network: partial (read bellow)

Bluetooth: no

Wifi: no

USB 3.0: yes

Sound: yes over HDMI

Obs:

You need to use hinlink-ht2 image, but no wireless, nor ethernet, only HDMI work, and you need to turn on monitor around 15 seconds after turn on the TVBox

I get the FDT from Android, and this FDT with hilink-ht2 images boot without HDMI, but with network, if you boot with hinlink-ht2 make the initial configs and start the desktop you can replace the rk-3528-hinlink-ht2.dtb with the android FDT and the box will boot, wait around 30 seconds and turn on the monitor and you have the HDMI and network working.

I have build the image with xfce and include some drivers (mail450, RK630, rtl8822cs) and enable some DRM options (under test yet)

I Have the Andoid boot partition dump, and other partions, I will share the files later (need some dropbox os gdrive to share)

I have attached the Android.DTB and dmesg from android and armbian, if someone want take a look.

Any help and sugestion will be great!

Some pictures of the board:

Lemfo-hk1rbox-k8s.dtb android_dmesg.log linux_dmesg.log linux-syslog

QPLOVE RK3566 (X88PRO Clone)

Wed, 27 Aug 2025 16:25:02 +0000

This case is a clone of X88PRO:

However i use HK1 rom because regular x88pro lack of many features like saf and without this dolphin-emu and others dont allow use external devices

another thing added in HK1 rom is cpu thermals, cpu load and memory load in status bar

but use this rom make frontal screen in tvbox dont work

In my case armbian works using information from this themes:

armbian used is based on station-m2 image from here:

https://www.armbian.com/station-m2/

https://github.com/armbian/community

HDMI - works (need to check hot plugging)

HDMI sound - works

USB 2.0 - works

USB 3.0 - works (using now usb 3.0 hub with power adapter)

LAN - Works

WLAN - Works

SD-Card booting and detection - works

RKDevTool installing and loading images on/from eMMC - works

GPU - works

Hardware video acceleration (except for browsers) - works

Dualboot if you flash new bootloader (SD-Card boot high priority) - works

Loader* from vontar work ok for use sd boot

*For use this follow steps in vontar guide, work ok in dual boot (armbian on sd and android in emmc)

sd used is a microdata 64gb from aliexpress (work ok):

https://es.aliexpress.com/item/1005007142224952.html

rk3566-box-demo.dtb dont recognize usb keyboard but using rk3566-box-demo_x96x6_24_custom.dtb from x96 x6 theme work correctly and hub work on usb 2.0 and on usb 3.0 too

also in usb 3.0 port have a 500GB HDD Laptop USB Drive

In other things can install xfce desktop, lightdm, xorg, chromium, firefox, nm (for lan), xarchiver, dolphin appimage

also can enable panvk using this:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/panfrost_icd.aarch64.json PAN_I_WANT_A_BROKEN_VULKAN_DRIVER=1

from here:

Add some images of tvbox, i make a mod (i dont have experience with tools) for add a fan, results are very impressive this tvbox at max stay around 79 to 80 degrees but now with fan stay around 35 to 45 degrees

Images from system

Dolphin-emu 2506

X98k pro (rk3566 4gb/32gb Android11) by Shenzhen Amedia Technology. First small success.

Fri, 17 Oct 2025 16:00:44 +0000

Hi all, and thanks for your incredible work

I just received an "X98k pro" tvbox (sold as rk3566 4gb/32gb ) from T***

The box arrives already rooted.

Outside :
blue info lcd display --> Sdcard ; usb2.0/OTG ; usb2.0 ; usb 3.x --> Optical SPDIF, HDMI , hole marked "UPDATE" , power (5v 2A); external antenna female. -> EMPTY SIDE

What's Inside the black box
SOC : Rockchip RK3566
RAM : 8 Micron Technology (MT) D9QBJ memory chips
Wireless : RTL8822cs
Ethernet : RTL8211F
eMMC : SanDisk China 32G
Front lcd display controller : AIP1628
TTL rx tx gnd

Device Info HW 5.23 and CPU-z confirm it's a rk3566 4/32, mali g52

Other infos from Device info HW :
Device : rockchip X98k PRO ; Platform rk30board
Android 11 ,
Wifi rtl88x2cs,
kernel 4.19.232 (ubuntu...)
CPU : Rockchip RK3566 BOX DEMO V10 ANDROID Board

After installing termux I tried to find this box's dtb, but
the only dtb file I found until now is /sys/firmware/fdt
(no .dtb extension just "fdt")

I don't know if it's the right one.
Anyway, I de-compiled it using dtc to "X98k_pro_4g-32g_from_fdt.dts".

I'd like to try armbian on this box
If u wanna know something else let me know.

Update
1)pressing the hole with a pin + power on takes to Android recovery (see photo)
seems I can just boot froom sd from there ...

2) Trying to make Rockchip Driverassistant (modified 4.2 or 4.5) work to connect the box to a PC via usb2.0/otg. But nothing.

3) after trying to start with generic armbian for arm64 and then Station M2 (both just gave blank screen), I had a first success with a miniarch image (20240715-6.17.1-board-rk3566.x96_x6), hdmi and usb keyboard works, but ethernet is not working.
Lets see what comes next.

X98k_pro_4g-32g_from_fdt.dts

Rockchip Rk3318 X88 pro 10 - in progress

Tue, 12 Dec 2023 21:42:40 +0000

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

Beginner. Unable to build proper image for my rk3566 handheld

Sun, 12 Oct 2025 15:04:31 +0000

I decided to learn something interesting and wanted to build an image for the Anbernic RG353P console. I checked that uboot has DTS files for my model in the main branch and that there is support in the Armbian kernel (vendor) for my hardware. Unfortunately, after building the image and uploading it to the console, nothing happens. The console has dual boot Linux/Android, Linux should boot from the SD card. Unfortunately, the system immediately loads Android and skips my card. I tried various options in board config, but to no avail.

Do you have any idea what I might be doing wrong with the configuration? The board configuration is copied from the existing one for nanopi-r3s-lts. I found two things that didn't seem right to me:

- by default, rootdev was configured to mmcblk0p1 in the bootscript, I think (I'm not 100% sure) that it should be mmcblk1p1 - no improvement

- my DTB file (/boot/dtb/rockchip) is missing from the /boot partition - I manually mounted the partition and uploaded the file, but that didn't help either (I set the permissions etc. the same as for the other DTBs).

I am pasting the configuration files.

Thank you very much for any help and advice

Board config:

Quote

# Rockchip RK3566 quad core 2GB RAM eMMC 2x GbE USB3 HDMI
BOARD_NAME="Anbernic RG353P"
BOARDFAMILY="rk35xx"
KERNELSOURCE='https://github.com/armbian/linux-rockchip.git'
KERNELBRANCH='branch:rk-6.1-rkr5.1'
KERNELPATCHDIR='rk35xx-vendor-6.1'
#KERNEL_BTF="no"
BOARD_MAINTAINER="IoToys"
BOOTCONFIG="anbernic-rgxx3-rk3566_defconfig"
KERNEL_TARGET="vendor"
KERNEL_TEST_TARGET="vendor"
BOOT_FDT_FILE="rockchip/rk3566-anbernic-rg353p.dtb"
IMAGE_PARTITION_TABLE="gpt"
BOOTFS_TYPE="fat" 
BOOT_SCENARIO="spl-blobs"

function post_family_config__use_mainline_uboot() {
	if [[ "$BRANCH" != "vendor" ]]; then
    	return 0
	fi
	#unset BOOTFS_TYPE   # mainline u-boot can boot ext4 directly
	BOOTCONFIG="anbernic-rgxx3-rk3566_defconfig"
	BOOTSOURCE="https://github.com/u-boot/u-boot"
	BOOTBRANCH="branch:master"
	BOOTPATCHDIR="master"
	UBOOT_TARGET_MAP="BL31=$RKBIN_DIR/$BL31_BLOB ROCKCHIP_TPL=$RKBIN_DIR/$DDR_BLOB;;u-boot-rockchip.bin"

	unset uboot_custom_postprocess write_uboot_platform write_uboot_platform_mtd

	function write_uboot_platform() {
		dd if=$1/u-boot-rockchip.bin of=$2 seek=64 conv=notrunc status=none
	}
}

armbianEnv.txt

verbosity=1
bootlogo=false
console=both
extraargs=cma=256M
overlay_prefix=rk35xx
fdtfile=rockchip/rk3566-anbernic-rg353p.dtb
rootdev=UUID=8f8aa17e-0953-4c6c-b7bf-8cf0ebbf2b14
rootfstype=ext4

Booting Armbian from SD CARD on RK3228A board

Wed, 05 Nov 2025 18:14:29 +0000

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 ?

Transpeed 8k TV box -RK3528

Thu, 02 Oct 2025 12:17:20 +0000

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,

Installing SliTaz on a TV Box with Rockchip RK3229

Tue, 07 Oct 2025 18:45:58 +0000

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!

rom (Firmware) TX9

Wed, 21 May 2025 19:08:27 +0000

Good afternoon everyone. I need your help. I have an Android TV Box TX9 and I need the ROM (Firmware) for it because I can't find it anywhere. Could someone help me download this firmware so I can resurrect my device? Thank you all.

Request for Firmware – Device Live Broadcast V4 (Board: LIVE3588V4.2)

Thu, 07 Aug 2025 11:31:22 +0000

Dear Support Team,

I am writing to request the original firmware for my Live Broadcast V4 device, which has completely stopped working and does not boot.

Upon disassembling the device, I identified the mainboard as:

Board model: LIV@3588V4.2

Date code: 20230919

CPU platform: Rockchip RK3588 (or similar variant)

Currently, the system is non-functional, showing no signs of successful boot or display. I believe the firmware may be corrupted or missing, and I would like to recover the device if possible.

I kindly request the following:

A copy of the original firmware image for this device (IMG, update.img, or compatible format)

Any necessary tools or flashing instructions (e.g. for USB flashing or SD card boot)

If available, a recovery method or unbrick tool specific to the LIV@3588V4.2 board

Please let me know if you need the serial number, more internal photos, or any other device-specific information to process this request.

I would be grateful for your assistance in restoring this device.

Rk3128 android mxq 4k 5G

Sun, 24 Dec 2023 11:56:20 +0000

I recently purchased an Android box which has Rk3128 . I didn't find enough resources to install an armbian server on rk3128 mxq 4k pro box.

Installing armbian on Yundoo Y8 TV box (RK3399)

Fri, 14 Feb 2025 17:20:20 +0000

Hello all.

I have an Android-based Yundoo Y8 TV box, which I want to use for UPS management.

I want it to be able to run Armbian to install the UPS management software, but I cannot figure out which Armbian I should download.

The board is based on Rockchip RK3399. In cpu-z app I see the board identified as rk30sdk, and the hardware is rk30board.

Can you please help me identify the board so I can understand which version of Armbian I need?

I couldn't find anything in the forum about RK3399...

I really appreciate any help you can provide.

YY3568 - Can't erase eMMC to boot from SD card

Fri, 22 Aug 2025 00:38:27 +0000

This is a sidebar/urgent request for help.
I was previously able to install Armbian noble on my YY3568 board thanks to instructions from these forums (https://forum.armbian.com/topic/49775-board-bring-up-youyeetoo-yy3568-rockchip-rk3568/).

I now need to use the board for a Debian project to help a friend that lost their backup, and am unable to reproduce the instructions in that post to empty the eMMC and enable SD boot.
The poorly written/flawed instructions in this post involve loading a config file into RKDevTool, writing loader, parameters and uboot, then there is a line about "destroying partitions by writing wipe_part" (a file you can download in the post), with no clarity or description of how to do this.
The steps then move onto flashing another loader to the board.
I have done all of these steps in MANY different adaptions and versions and it is always unsuccessful because whatever portion involving the "wipe_part" is missing from the original steps.
I am hoping that someone else whose board uses similar procedure sees this and can correct the instructions and make SD boot possible again.
It's really aggravating that my board is being held hostage to this - the person who wrote the instructions has worked on other projects with similar steps and others have had the same issue with their incomplete/incorrect instructions in those posts, and so far will not reply regarding this.
I've tried 4 different versions of RKDevTool and worked for around 7 hours on this so far with no success. I'm hoping someone else can come save me!

mxq pro 4k / rk3228a multitool not loading

Sun, 10 Aug 2025 13:39:18 +0000

I have an old and weak mxq pro 4k TV box (fake amlogic s905w), rk3228a checked, sv6051p wifi. I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like I recorded the desired version on the micro sd via the multiboot.img adapter and it worked but did not respond to the remote control, I checked the remote for robotics, recorded libre elec and booted from it without multiboot and it even worked on wi-fi and the remote reacted, I replaced the dtb file and booted from the multiube but it no longer worked I thought that dtb was capricious and decided to replace only part of the it_receiver code in dts format and converted it and recorded it via dd on Linux, but this time the eumultool worked but the remote control did not respond again. I do not know why it stopped turning on on android 7.1.2, but I know for sure that after downloading minecraft or similar games, it will boot up and you can go to recovery, I tried two firmware for TV box in the format.zip but there was a message map location failed like that,this is off topic, but please help me fix this, I definitely need linux to make a server for the telegram bot.

Question about RK3318 armbian method usb

Sun, 03 Aug 2025 05:04:15 +0000

Hello, i am gonna make my h96 max rk3318 to NAS and download manager, so that's why i am going to install armbian,

**my question is there a way to install armbian using usb?** cause i do not have sd card and not gonna buy it cause i already have so many broken sd card, so i think sd card is not reliable for me that is why i am gonna using usb flashdrive.

My thought about how am i gonna do this, is using android tool to wipe the mmc and then making bootable armbian on usb flashdrive.

But i am not sure if the u boot gonna recognise the usb flash drive.

Sorry if my english is bad

#rk3318 #h96max

server home assistant and armbian

Thu, 17 Jul 2025 09:06:03 +0000

Good afternoon! I bought a server home assistant. The web used to open. the interface is at 192.168.1.141:8123, and now it’s reaching armbian and I don’t know what to do next and I don’t understand why this happened either. I’m asking for your help. Has anyone ever had such a situation?
If I created the wrong theme, can you tell me where to create it, or maybe there is already such a theme?

Rk3228a, zq01-v1.51 unlock

Tue, 29 Jul 2025 05:24:52 +0000

Hi, can anyone help me with this TV box? I need to unlock it, but I don't know where to short the cable because the PC won't connect.

Rk3228a, zq01-v1.51

Force resolution (again...)

Fri, 11 Jul 2025 14:41:38 +0000

Hello.

I am trying to have this new(?) tv box built around a RK3228A cpu detect the correct resolution of my monitor. In U-boot, I get a correct full HD 1920x1080p resolution. However, as soon as the U-Boot passes to the kernel, it switches to 1024x768. How can I correct this? If I can't correct the detection of EDID, can I force it?

I've tried to add this to /boot/armbianEnv.txt, but it did not work :

extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080@60

Any ideas?

Thanks!

Sudden Shutdown After Exactly 29min47s — TX2 TV Box (RK3229, NAND, 2GB)

Tue, 22 Jul 2025 13:10:06 +0000

Hi everyone,

I’m experiencing a recurring and very specific issue with my TX2 TV Box, with the following specifications:

SoC: Rockchip RK3229

RAM: 2GB DDR3

Storage: NAND flash (not eMMC!)

Board: Generic TX2 board

🛑 Main Issue

The system shuts down abruptly at exactly 29 minutes and 47 seconds of uptime (i monitoring via htop). It always shuts down at this time.

It’s not a clean shutdown or reboot — it behaves as if the power was cut off. No meaningful logs appear in journalctl or dmesg, and the shutdown is instantaneous and silent.

🧪 What I’ve Tried:

Disabled idle and sleep functions:

Masked systemd-logind

Set IdleActionSec=0 and HandlePowerKey=ignore

Tried different kernel versions:

Legacy: Armbian 22.02.0-trunk Focal legacy 4.4.194

Mainline: Armbian Jammy kernel 5.15

Attempted to disable the watchdog:

Boot parameter nowatchdog

Kernel parameter rcu_cpu_stall_timeout=0

Created a systemd service to periodically write to /dev/watchdog

Tried to remove dw_wdt module (modprobe -r), but it either auto-loads or refuses to unload (watchdog did not stop)

Tried building a custom kernel with CONFIG_DW_WATCHDOG=n, but the process failed due to gcc-arm-linux-gnueabi toolchain issues.

Used config-rk322x to properly set RAM, NAND, and Wi-Fi chip before first boot + update/upgrade.

Tried adding sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

⚠️ Additional Critical Note:

The system does not work at all when flashed to eMMC/flash — only boots properly from NAND or SD card.

Any image written to internal flash does not boot.

Therefore, booting from NAND is required, which may be related to the watchdog being active by default on NAND-based boards.

❓ My Question:

Has anyone with a TX2 or RK3229-based NAND board experienced this same issue?

Is this a known watchdog timer issue on NAND models?

Is there any stable image or device tree overlay known to work for this configuration?

Any tips to fully disable the watchdog either via software or kernel patch?

Thanks in advance for any help or suggestions!

Help booting Armbina on a A96X TV Box - with boot log

Wed, 23 Jul 2025 00:09:50 +0000

I Have an A96X with rockchip RK3228 and i tried booting armbian on it, but I got no display on HDMI.

I connected a serial adapter to it and here is the information it displays when trying to boot:

▒▒▒▒DDR Version V1.05 20160805_dbg
In
300MHz
DDR3
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
mach:2
OUT
Boot1 Release Time: 2016-03-15, version: 2.31
ChipType = c 275
No.1 FLASH ID:2c 64 44 4b a9 0
ECC:60
SdmmcInit=0 0
BootCapSize=0
UserCapSize=76f5000
FwPartOffset=2000 , 0
StorageInit ok = 1520008
SecureMode : SBOOT_MODE_NS
hdr 0x0:ff a1 0 0 1b 0 0 0 f0 f2 2e 68 f0 f2 2e 68

hdr 0x0:a4 81 0 0 4e 23 0 0 f0 f2 2e 68 f0 f2 2e 68

hdr 0x0:ff a1 0 0 3 0 0 0 f4 f2 2e 68 f4 f2 2e 68

hdr 0x0:a4 81 0 0 44 0 0 0 f4 f2 2e 68 f4 f2 2e 68

hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

hdr 0x0:0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

SecureMode : SBOOT_MODE_NS
Loder code check ok! theLoader 0x60000000, loadaddr: 0x2000
Loder code check ok! theLoader 0x68400000, loadaddr: 0x4000
INF TEE-CORE:init_primary_helper:319: Initializing (1.0.1-63-g23e91df-dev #16 Tu                                                                                                                                                             e Mar  7 10:07:15 UTC 2017 arm)
INF TEE-CORE:init_primary_helper:320: Release version: 1.8
INF TEE-CORE:init_teecore:79: teecore inits done


U-Boot 2017.02-RK322X-06-02276-ga7c7ca8-dirty (May 19 2017 - 11:16:15)

CPU: rk322x
cpu version = 3
CPU's clock information:
    arm pll = 600000000HZ
    periph pll = 600000000HZ
    ddr pll = 600000000HZ
    codec pll = 500000000HZ
Board:  Rockchip platform Board
Uboot as second level loader
DRAM:  Found dram banks: 1
Adding bank:0000000060000000(0000000040000000)
Reserve memory for trust os.
dram reserve bank: base = 0x68400000, size = 0x00100000
128 MiB
GIC CPU mask = 0x00000001
rk dma pl330 version: 1.4
remotectl v0.1
pwm freq=0x11e1a3
pwm_freq_nstime=0x355
SdmmcInit = 0 0
SDCard Update.
storage init OK!
Using default environment

Writing env to storage...
done
GetParam
W: Invalid Parameter's tag (0x00000000)!
Invalid parameter
No pmic detect.
SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 0000-00-00#0.00
empty serial no.
normal boot.
no fuel gauge found
no fuel gauge found
read logo on state from dts [0]
no fuel gauge found
'recovery' does not seem to be a partition nor an address
Unable to boot:recovery
try to start backup
'backup' does not seem to be a partition nor an address
Unable to boot:backup
try to start rockusb

Can anybody point me to the right direction? I'd really like to turn this piece of junk into something useful 😄

Any help will be greatly appreciated!

Thank you.

desktop environment?

Fri, 18 Jul 2025 14:29:24 +0000

Hello.

How can I install a desktop environment?

I've successfully installed Armbian on a rk322x tv box, but the option to install a desktop environment is missing from armbian-config utility.

Thanks!

Help identify MaskROM or UART on RK3288 POS device for Armbian installation

Thu, 03 Jul 2025 01:23:49 +0000

Hello everyone,

I have an old POS machine that uses the Rockchip RK3288 processor. It has a 1920x1080 screen and works fine, but I don’t have any root or bootloader unlock permissions.

I would like to flash Armbian on it and make better use of the device.

So far I’ve tried:

ADB access (only recovery available)

Tried using adb reboot bootloader, but the device just powers off

Identified some test points like KEY, T3, T2, T52, T51, but not sure which one is for MaskROM shorting

Found no physical recovery button, only a reset and power button

There might be a UART port, but I’m not sure

👉 Can someone please help me:

Identify which test points or pads I can short to enter MaskROM mode

Locate a possible UART debug port on the board

Any advice for dumping original firmware or unlocking bootloader

I've attached front and back photos of the mainboard. Any suggestions or experience with RK3288 boards are greatly appreciated!

Thank you 🙏

64bit build of armbian for rk322x tv box?

Thu, 10 Jul 2025 17:30:57 +0000

Hello.

I have this MX10 Box S android TV box, it works well with the latest Armbian community build (Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img).

However, I have this specific binary that is 64bit that I would like to run on my box and this build of armbian is 32bit only. Is there a 64bit build of armbian for rk322x anywhere?

Thanks!

How to setup libwc--or any alternative wayland compositors?

Tue, 08 Aug 2023 20:17:57 +0000

Hello all,

I'm trying to setup libwc (preferred) or weston on my Mekotronics R58X (2023 edition)
But when I try and build any wayland compositor, I keep gettign this error:

ERROR: Dependency "wayland-server" not found, tried pkgconfig and cmake

But I appear to be running wayland:

mekotronics-r58x:weston:% echo $XDG_SESSION_TYPE                         
wayland

And when I search for it in apt, I'm only seeing libwayland installed/available:

mekotronics-r58x:weston:% apt search wayland-server                      
Sorting... Done
Full Text Search... Done
librust-wayland-commons-dev/jammy 0.29.1-1 arm64
  Common types and structures used by wayland-client and wayland-server - Rust source code

libwayland-server0/jammy-security,jammy-updates,now 1.20.0-1ubuntu0.1 arm64 [installed,automatic]
  wayland compositor infrastructure - server library

I've tried installing libwc: https://github.com/labwc/labwc
but in order to do that I have to install wlroot--and I get the same error when trying to build

I've also tried weston: https://gitlab.freedesktop.org/wayland/weston

My overall goal is to have a basic window compositor launch kodi in fullscreen on start--but also let's me run other applications.

Please advise if you have any input, or if I am missing something

Hardware: Mekotronics R58X (2023 edition)
OS: Armbian (23.08.420-monka) aarch64 
Host: Mekotronics R58X (RK3588 EDGE LP4x V1.0 BlueBerry Board) 
Kernel: 5.10.160-rk35xx 
Shell: zsh 5.8.1 
Resolution: 3840x2160 
DE: GNOME 42.9 
WM: Mutter 
CPU: (8) @ 1.800GHz 
Memory: 2917MiB / 15970MiB 
CPU Usage: 11%

Thank you,

Efforts to develop firmware for Transpeed 8K Ultra HD MX10 RK3528 BOX

Wed, 22 May 2024 18:16:26 +0000

Purchase Link

This should be a fun one.

Bought the 4GB/128GB variant.

AP6330 Wifi

Stock software is a really, really bad Android TV port. Looks like a Google Pixel 5 image that has had RK3528 support hacked into it. Some parts report the device as Pixel 5, others MX10.

RKdumper wouldn't work.

Wifi is hardcoded to China region in the kernel commandline, so wifi doesn't work in North America. Boots into a setup wizard that can't be closed, and forces an internet connection. Since wifi is broken out of the box, had to use ethernet to get past the setup wizard.

Transpeed does not have a website or offer stock firmware. The vendor I purchased it from refused to supply a stock image.

Image was pre-rooted, so used ethernet+adb to adb pull the entire flash chip. Unfortunately the Android partitions appear to be encrypted and only show gibberish directory names. Was able to use extract-dtb on one of the raw binary partitions to get the stock DTB, which is all I cared about anyway. It is pretty close to an existing one in Armbian (rk3528-demo1-lp4-v10)

Located and soldered the tiny UART pads without destroying the box.

Tried my different garbage clone USB UART adapters to find one that could handle RockChip 1.5 megabit over serial, fake CH340G did the job, fake CP2102 would not. May the best fake product win!

Followed @Hqnicolas guidance from this thread and used the hinlink-h28k trunk release with 5.10 kernel as a base, and changed the dtb referenced in armbianenv to the stock android DTB extracted from the device, and of course it would not boot. Lots of errors, kernel panics on UART, errors from SD reader.

Changed to Kernel 6.1 base hinlink-h28k image, and tried rk3528-demo1-lp4-v10.dtb, that one almost boots but doesn't see the SD card so can't mount root filesystem.

Began DTB surgery, added pieces of the SD card initialization from the factory DTB to the rk3528-demo1-lp4-v10.dtb, got it to boot. Black USB port dead, Blue USB port working. No HDMI output on console (only UART) but does load XFCE when the GUI autostarts.

Will keep slicing and dicing DTB to gain functions. Will need to drop in proper NVRAM file to get AP6330 working as I've had to do on other boards.

	//rk3528-demo1-lp4-v10.dts  SD Not Detected
	mmc@ffc30000 {
		compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc";
		reg = <0x00 0xffc30000 0x00 0x4000>;
		interrupts = <0x00 0x85 0x04>;
		max-frequency = <0x8f0d180>;
		clocks = <0x02 0x198 0x02 0x197 0x7a 0x01 0x7a 0x02>;
		clock-names = "biu\0ciu\0ciu-drive\0ciu-sample";
		fifo-depth = <0x100>;
		resets = <0x02 0x2a9>;
		reset-names = "reset";
		rockchip,use-v2-tuning;
		status = "disabled";
		phandle = <0x10e>;
	};

//Factory DTB - SD reader stuck Busy, can't select voltage etc.
	mmc@ffc30000 {
		compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc";
		reg = <0x00 0xffc30000 0x00 0x4000>;
		interrupts = <0x00 0x85 0x04>;
		max-frequency = <0x8f0d180>;
		clocks = <0x02 0x198 0x02 0x197 0x68 0x01 0x68 0x02>;
		clock-names = "biu\0ciu\0ciu-drive\0ciu-sample";
		fifo-depth = <0x100>;
		resets = <0x02 0x2a9>;
		reset-names = "reset";
		rockchip,use-v2-tuning;
        //status = "disabled"
		status = "okay";
		bus-width = <0x04>;
		cap-mmc-highspeed;
		cap-sd-highspeed;
		disable-wp;
		pinctrl-names = "default";
		pinctrl-0 = <0x6d 0x6e 0x6f 0x70>;
		rockchip,default-sample-phase = <0x5a>;
		supports-sd;
		sd-uhs-sdr12;
		sd-uhs-sdr25;
		sd-uhs-sdr50;
		sd-uhs-sdr104;
		phandle = <0xff>;
	};

//Combo that works enough to boot
	mmc@ffc30000 {
		compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc";
		reg = <0x00 0xffc30000 0x00 0x4000>;
		interrupts = <0x00 0x85 0x04>;
		max-frequency = <0x8f0d180>;
		//clocks = <0x02 0x198 0x02 0x197 0x7a 0x01 0x7a 0x02>;
		clocks = <0x02 0x198 0x02 0x197 0x68 0x01 0x68 0x02>;
		clock-names = "biu\0ciu\0ciu-drive\0ciu-sample";
		fifo-depth = <0x100>;
		resets = <0x02 0x2a9>;
		reset-names = "reset";
		rockchip,use-v2-tuning;
		//status = "disabled";
		//from stock dtb
		status = "okay";
		bus-width = <0x04>;
		//cap-mmc-highspeed;
		//cap-sd-highspeed;
		disable-wp;
		pinctrl-names = "default";
		pinctrl-0 = <0x6d 0x6e 0x6f 0x70>;
		//rockchip,default-sample-phase = <0x5a>;
		supports-sd;
		//sd-uhs-sdr12;
		//sd-uhs-sdr25;
		//sd-uhs-sdr50;
		//sd-uhs-sdr104;
		//end from stock dtb
		phandle = <0x10e>;
	};

rk3528-transpeed-8k-ultra-hd-mx10.dts

Buying advice: H96 Max V56 or X88 Pro 20?

Thu, 08 May 2025 15:38:38 +0000

Hi all, I'm a newbie

The two boxes have similar hardware (RK3566 + Mali-G52-2EE + 8GB ram), and I've searched the forums and seen both have been experimented with Armbian.

But I'm still confused about the bottom line: on which of the two Armbian is better supported or easier to run?

That'll be the main deciding factor for me, but of course I'll be interested in any other comment or general advice.

TIA!

Not working led display X88 pro 10 128GB

Fri, 23 May 2025 14:40:32 +0000

On my TV box X88 pro 10 128 GB (Armbian 24.11.0-trunk.321 6.11.4-edge-rockchip6), the driver does not work when set to led-config 2. After studying, I performed several operations and everything worked. Maybe it will help someone!!

In armbian-config, install led-config 2 and wlan-ap6334 next

1. dtc -I dtb -O dts /boot/dtb/rockchip/overlay/rockchip-rk3318-box-led-conf2.dtbo -o /root/rk3318-box-led-conf2.dtso

2. In the /root/rk3318-box-led-conf2.dtso file, edit reg = <0x24> to <0x0>

3. dtc -I dts -O dtb -f /root/rk3318-box-led-conf2.dtso -o /boot/dtb/rockchip/overlay/rockchip-rk3318-box-led-conf2.dtbo

Wi-Fi and Bluetooth are working, the display is working too, but for some reason the lan and power symbols are mixed up.

I solved it through the display service file

display-service.txt

HELP- DQ08 RK3528 4Go RAM 64go SSD can't boot with multitool (with photos)

Tue, 19 Sep 2023 17:24:57 +0000

Hi,

i can't boot multitool and armbian on my android TV DQ08 RK3528 4Go RAM 64go SSD.

I take pictures of my card :

X96 X6 Configuration

Fri, 25 Apr 2025 16:02:31 +0000

I’m using an Android TV Box X96 X6. Right now, I want to find a way to install Armbian on it, but I haven’t been able to figure it out yet. I’d appreciate any help or guidance from the community.

Tanix TX66 RK3566 4GB/32GB 8K 2.4/5WIFI 1GiB BT USB2/3 SD IR SPDIF

Mon, 11 Mar 2024 16:39:16 +0000

Hi everyone, newbie here.

Experienced developer with some outdated embedded experience. Very little experience in nowadays embedded technologies, but it's something I'm interested in learning about.

Doing fewer hours on the day job atm and picked up one of these as a home project. Goal is to get armbian working fully on this. When (if) successful probably will do a libreElec - this should make for a powerful Kodi box.

Tanix Tx66, around €50 on aliexpress, I have the 4GB RAM 32GB eMMC flavour.

Product Specification:

CPU : RK3566 / Mali-G52 GPU
RAM : 2GB/4GB LPDDR4
ROM : eMMC 16G/32G/64G
Bluetooth : BT 5.0
DC In : DC 5V/2A
USB Host : 2 High speed USB 2.0, 1 USB 3.0
Card Reader : TF Card reader
Lan : RJ45 Ethernet port 1GiB
Wifi : Built-in Wifi, 802.1.1b/g/n/ac ; 2.4G/5G
SPDIF : Coaxial(Optical)

Vendor firmware both as IMG and zip archive:

Google Drive by Tanix

It contains a boot.img, dtbo.img and uboot.img. I dipped into some of the other threads here and armed with that I was able to extract & decompile a device tree from boot.img.

rk3566-tanix-tx66.dts rk3566-tanix-tx66.dtb

I made some half-hearted attempts sticking the device tree into some 'close enough' images (libreElec & armbian generic rk3566) and see what happens booting from SD but without success. The box just stays dark.

I guess I need to brush up on modern bootloader and kernel/device-tree concepts etc, but wrt the task at hand, am I right in saying first step is getting serial debug going to see what goes wrong where?

^^^^^^^^^^^

This here looks like the serial debug pins, bottom left next to the SD card reader. I couldn't find anything else that looks remotely like it. I ordered an FT232RL serial to USB converter and will have a go.

I'm new to this site and I hope I'm doing this right, creating a thread here. If not please be gentle

Thanks!

Armbian on H96 Max Ultra 4K (RK3318) stuck in boot mode

Wed, 26 Mar 2025 09:47:41 +0000

Hi everyone,

I'm facing an issue with my Armbian setup on an H96 Max Ultra 4K (RK3318). The system boots up normally and works fine for a while, but after running for some time, it completely freezes and becomes unresponsive. I have to power cycle the device to get it running again. This issue keeps happening consistently after some time, and I’m not sure what's causing it.

Here are a few details about my setup:

Board model: H96 Max Ultra 4K (RK3318)

Armbian version: Armbian_24.11.0_rockchip_rk3318-box_bookworm_6.1.114_server_2024.11.01.img

SD card format: BTRFS

Things I've tried so far:

Checking the power supply to ensure it's stable and sufficient.

Re-imaging the SD card with a fresh Armbian installation.

Monitoring logs, but I haven’t found any obvious errors before the system hangs.

Does anyone have any idea what might be causing this issue or how to resolve it? Any help or suggestions would be greatly appreciated!

Thanks in advance!

armbian rk3229 wouldn't show any image on my tv

Mon, 31 Mar 2025 00:45:36 +0000

hi, i recently discovered the world of linux in arm, so i wanted to test it, so i can use my retro tv to emulate, i already tried libreELEC and it worked flawlessly, but it had a lot of constrainsts so i installed armbian, first multiboot didnt showed up any image on my tv so i switched to my secondary monitor on my pc and i tworks, i wonder if theres a posibility that armbian could support composite output on the rk3229 platform

Kernel downgrade through apt and Mainline Kernels

Sat, 05 Apr 2025 05:13:04 +0000

Hello everyone!

I'm using rk322x TV box for video decoding through mpp. Mpp requires a system with 6.1 or earlier kernel. When I try to compile Ubuntu 22.04 from this repository https://github.com/armbian/build, the selection for kernel are "current" or "edge". I selected "current", and later I found its kernel is 6.12.21. I have tried to use armbian-config to downgrade the kernel, but the earliest selection is 6.6. Then I tried to downgrade the kernel through apt, but there were no 6.1 edition. Thus, I decided to change the kernel through "Mainline Kernels" and install the 6.1.132 kernel. After the installation finished, I rebooted my system and found that the kernel was still 6.12.21, I have no idea what to do next, so I am here asking for help.

Apologize for my poor English, and greatly thanks for your help.

Running 6.12.19 SMP PREEMPT kernel, seeking a path to run PREEMPT-RT (full real-time) kernel

Fri, 21 Mar 2025 16:35:53 +0000

In my H96 TV box I have been running Armbian for over an year. Works great. Today I did a fresh install of:

Armbian_community_25.5.0-trunk.256_Rk3318-box_bookworm_current_6.12.19_minimal.img.xz

uname -a shows:

rk3318-box> uname -a
Linux rk3318-box 6.12.19-current-rockchip64 #2 SMP PREEMPT Thu Mar 13 12:02:20 UTC 2025 aarch64 GNU/Linux

It is my understanding that Linux 6.12+ kernel already have all the real-time patches in the mainline kernel sources. All one needs to do is to

1. rebuild the kernel after configuring for FULL PREEMPT-RT support

or (if kernel already built with this configured)
1a. reboot after providing to 'grub' a boot option "preempt=full"

If any one has had experience running the full PREEMPT-RT kernel on rk3318 (or any Armbian box)?

What are the best steps to get and natively build a new kernel for 6.12.19 on my rk3318 box (only show 27 Gb free though, may not be enough.)

Help with Installing Armbian on RK3328 TV Box (dnetSmart-YSE)

Mon, 17 Mar 2025 14:17:16 +0000

Hello everyone,

I’m trying to install Armbian on a TV box with an RK3328 SoC, but I’m running into several issues. Here’s what I’ve done so far and the information I have:

Box model: dnetSmart-YSE, version 10

Chipset: RK3328

Kernel version: 4.4.179

PCB info: t9-RK3328-D4, ver 2.0.2018

Design by: Hugsun

I followed the instructions I found on the forum to install Armbian, but it’s not working. I’ve tried several methods:

Using the microSD card: I tried installing Armbian on a microSD card and booting it from the box's microSD port, but it didn’t work.

Using a USB drive: I also tried booting from a USB drive plugged into one of the box’s USB ports, but without success.

Connecting a male-to-male cable between my PC and the box: I couldn’t retrieve any information this way.

Connecting an UART (FTDI): The result is unreadable on the terminal.

I haven’t received any specific details from the manufacturer.

I’ll attach some photos to help illustrate the situation. My goal is to figure out if it’s possible to install Armbian on this box and, if so, how to proceed.

Thank you in advance for your help!

X88 Pro 20 (RK3566) Set top box

Wed, 25 Aug 2021 18:54:38 +0000

Hello,

Software developer (web) from the Netherlands here.

Just picked up a "X88 Pro 20" box from AliExpress: Link to AliExpress. I'm wondering if it is any good and if it will run armbian. I've looked at several other SoC's, but this one looked quite nice, especially at this price point (49 euros). I needed a bit more GPU power and RAM because i'm planning to do a electron (chromium+node.js) based home control app for the thing.

If somebody got armbian working with some features (hardware acceleration is quite important), i would be thankful if you would like to share your thoughts and methods on how to install it since i'm (very) new to this whole SoC/SoB thing. I've just placed my order and it will arrive in about 4-10 days. I am always happy to test builds for it.

Thanks so much, and have a nice week.

- Alwin

When can an embedded device be truly bricked?

Fri, 14 Feb 2025 17:57:37 +0000

Hi,

I installed the wrong image on a Rockchip RK3288 (Hannspree) Android 5.1 TV box.

Now it won't boot from internal memory or sd-card, power on, light up or anything. Like it was hit by lightning.

Is this expected? What has happened?

(This very comprehensive and helpful post says that "If the internal flash does not contain a bootable system, they will always boot from the sdcard.")

Thank you good people

(The tag on this post is wrong... I could not find a RK3288 tag)

Why armbian-install can brick the TV-box?

Fri, 01 Dec 2023 10:22:40 +0000

I installed armbian on a micro sd to be able to install it on my Dq08 RK3528.
The boot succeeded on the sd card perfectly.
I wanted to install armbian on the memory of the box with "armbian-install" I followed the instructions I did the 2. and Then I did the 5. it ask me to poweroff and since it does not want to turn on or be recognized by my peripherals connected. I've tried rebooting from an sd but it doesn't work. But I tried on another box with the same sd and it worked. So I think the box is brick. I've decided to do the tutorial from the sellers on aliexpress with the usb to usb cable. With the av button, the software doesn't even recognise it.
I don't know what to do now.

Failed install on RK3288 (Hanspree AK01) and drops to busybox... What now?

Mon, 27 Jan 2025 22:18:35 +0000

Hi,

I used multitool and installed Armbian_22.05.0-trunk_Xt-q8l-v10_jammy_current_5.15.35_xfce_desktop.img.xz onto a Hanspree AK01 miniPC.

It does not boot and drops into a busybox shell:

Starting version 249.11.0ubuntu3
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... BEgin: Running scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems 
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device. Common problems: 
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules: ls /dev)
ALERT! UUID=90fc5c5eq-35fd-44dc-97d8-a8d0cbaba4ba does not exist. Dropping to a shell!

Busybox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) Buid-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

What should I try now?

I also tried pausing the boot in u-boot, and booting a xubuntu 22.04 live USB:

U-Boot 2022.04-armbian *Apr 24 2022  16:31:34 +0000)

Model: XT-Q8L-V10-RK3288
DRAM: 2GiB
Core: 189 devices, 22 classes, devicetree: separate
MMC: dvmc0ff0c0000: 1, dvmc0ff0c0000: 0
Loading environment from MMC: *** Warning - bad CRC, using default environment

In:  serial
Out: vidconsole
Err: vidconsole
Model: XT-Q8L-V10-RK3288
Net: eth0: ethernet0ff290000
starting USB...
Bus usb00ff5400000: USB DWC2
Bus usb00ff5500000: USB DWC2
Scanning bus usb00ff5400000 for devices... 5 USB device(s) found
Scanning bus usb00ff5500000 for devices... 1 USB device(s) found
Hit any key to skip autoboot: 0

=>usb storage
   Device 0: Vendor A1:      Rev: Prod: Mass Storage
               Type: Removble Hard Disk
               Capacity: 15376.0 15GiB
=>usbboot usb 0
Loading from usbdevice 0, partition 1: Name:
ISO9660 Type: U-Boot

Unknown Image Type

How do I fix the ubuntu install fail? Is there something that can be done in busybox?

How would I boot from the SD-card, or a USB?

Thank you

HK1 MAX RK3321 bricked

Tue, 04 Feb 2025 22:17:55 +0000

I have an HK1 MAX with RK3218 CPU. I tried to install Armbian with multitool.
I erased the flash from multitool flashed Armbian and the board won't boot at all

It doesn't boot from an sd card and when I press the reset button is not entering mask mode, it is just stuck with the red light on

Is 100% dead or is anything I can do?

HK1 MAX RK3328

Tue, 04 Feb 2025 11:28:11 +0000

Is there a armbian firmware for this model? Also on the case is written RK3318
user@user-Z370-HD3P:~/Downloads/Linux_Upgrade_Tool_v2.4$ rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=101 Loader

Restore X88 PRO 10

Sat, 24 Sep 2022 13:14:35 +0000

I was trying to flash the eMMC of my X88 PRO 10, which bricked it. I need some help to unbrick it.

So far, I have managed to put it into maskrom mode by conneting the two contact pads in the red circles and pluging in a USB A to A cable in the USB 2.0 port of the tv box and my computer.
I took a backup of the firmware with the multitool from here: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/page/1 but I could not find a way to restore it.
I tried Android tool reports, which says "Found One MASKROM Device", but threw an error when I tried to load my backup.
So I searched for the origional firmware, but could not find a source that was working.
Can someone help me unbricking my TV box?

MXQ Pro 4k 5G (Rockchip Firmware RK3229 + RTL8189ES)

Thu, 16 Jan 2025 07:46:33 +0000

Hello everyone!

I'm looking for newer firmware specified on the post title.

My board is RK322x and i believe it will work with the firmware RK3228a, RK3228b and RK3229 as long as it has the same wifi chip which is RTL8189ES.

I'm also kinda interested on how to install the wifi chip driver on my tv box if ever i don't have a chance on getting the firmware that i want.
If you have recent or updated firmware for RK3229 too please let me know!

Thank you very much!

MXQ-4K, R329Q v2.0 board, NAND Flash issue

Tue, 14 Jan 2025 23:01:17 +0000

Hi there,

RK322A-box with R329Q v2.0 board, during the firmware upgrade [using Factory tool v 1.8] “Preparing IDB failed” occurred, most likely because that image file was wrong.

The box is bricked, but boot up from SD card [multitool] and also connects to the PC…

Next step: using RKAndroid Tool v 2.96 tried to restore the initial back-up image [the 14 files], but shows “U-boot file is larger than Flash size”…”ReadFlashInfo” detected the Flash Manufacturer: Micron, Flash size 0MB [?] and is disabled, see attached screenshoot:

What is the next step fix this issue? Do I have to upload some RK loader.bin file ?

P.S. the NAND is a SpecTek labeled PF I44

X88 PRO 20 RK3566

Tue, 17 Dec 2024 18:26:09 +0000

Hello i got a Android TV X88PRO 20 Ultra HD 8K (X88PRO-RK3566.4D32-v1.0), with RAM 8G, and ROM 128G. MALI G52.

Id like to install Linux on it but i'm not sure what firmware would run on it. I understand most RK356 firmwares would work; but where should i start? Is there a guide for new people?

I have enough knowledge to follow instructions in a linux pc and any guidelines would help a lot. i just want a stable linux to run some services from it.

I did found an old post that had some files that seem to be dead links now.

Thanks for your time.

pd added some images in case is interesting to someone. I guess i can make a back up of the android firmware, but in my opinion is trash. may be someone can get some drivers from it.

Power up MXQ PRO 4K RK3128_MXQ_EP_68?

Sun, 22 Dec 2024 17:54:20 +0000

I got a board and want to test if it turns on at all. Is there any way to short the pins somewhere to get it to turn on?

I don't have the remote but I suppose connecting the DC barrel should be enough to get some lights but nothing happens?

Any help is appreciated.

DEV【 Tanix TX66】 RK3566 4GB/32GB 8K 2.4/5WIFI 1GiB BT USB2/3 SD IR SPDIF

Sat, 18 May 2024 08:36:48 +0000

CPU : RK3566 / Mali-G52 GPU

RAM : 2GB/4GB LPDDR4

ROM : eMMC 16G/32G/64G

Bluetooth : BT 5.0

DC In : DC 5V/2A

USB Host : 2 High speed USB 2.0, 1 USB 3.0

Card Reader : TF Card reader

Lan : RJ45 Ethernet port 1GiB

Wifi : Built-in Wifi, 802.1.1b/g/n/ac ; 2.4G/5G

SPDIF : Coaxial(Optical)

DTB:

rk3566-slzn.dtb

Installing Armbian on H96 Max RK3399 (4Gb RAM - 32Gb ROM)

Wed, 18 Dec 2024 13:00:37 +0000

Hello everyone,

I am a new Armbian user and don't have much experience with installing Armbian (both hardware and software operations).

I have an old TVBox with an RK3399 chip as shown in the attached picture.

Although I have spent time searching the Internet about installing Armbian on this hardware, all my efforts have come to a dead end.

So I ask for help from you to install Armbian on this hardware of mine.

Thank you very much. Wishing you a Merry Christmas.

I´m willing for LXQT, aren´t you?

Fri, 08 Nov 2024 12:46:08 +0000

Gnome has win popularity for our boxes because of wayland replacing XCFE. The reason is that panfrost driver works much better with mali in wayland. But LXQT has reached wayland now and is a true lighter desktop. When 2.1 gets the repo this will become true.

XREAL Beam (1st gen) - rk3568, 4GB RAM

Wed, 04 Dec 2024 07:22:47 +0000

Here's all the information I dumped via adb:

Quote

eva:/ # cat /sys/class/net/wlan0/device/modalias
sdio:c00v02D0dA9BF
eva:/ # getprop ro.hardware
rk30board
eva:/ # cat /proc/cpuinfo
processor : 0
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

processor : 1
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

processor : 2
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

processor : 3
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x2
CPU part : 0xd05
CPU revision : 0

Hardware : rockchip,rk3568
Serial : 8393bc146a70b1ad

eva:/ # getprop ro.hardware
rk30board

eva:/ # cat /sys/class/net/wlan0/device/modalias
sdio:c00v02D0dA9BF

eva:/ # cat /system/build.prop

# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Wed Oct 16 01:39:59 CST 2024
ro.system.build.date.utc=1729013999
ro.system.build.fingerprint=XREAL/eva/eva:11/RQ3A.210705.001/EVA-202410152207-380:user/release-keys
ro.system.build.id=RQ3A.210705.001
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=EVA-202410152207-380
ro.system.build.version.release=11
ro.system.build.version.release_or_codename=11
ro.system.build.version.sdk=30
ro.product.system.brand=XREAL
ro.product.system.device=eva
ro.product.system.manufacturer=XREAL
ro.product.system.model=Beam
ro.product.system.name=eva
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=RQ3A.210705.001
ro.build.display.id=RQ3A.210705.001 release-keys
ro.build.version.incremental=EVA-202410152207-380
ro.build.version.sdk=30
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=11
ro.build.version.release_or_codename=11
ro.build.version.security_patch=2021-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Wed Oct 16 01:39:59 CST 2024
ro.build.date.utc=1729013999
ro.build.type=user
ro.build.user=nreal
ro.build.host=BJ-PC426
ro.build.tags=release-keys
ro.build.flavor=eva-user
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=eva
# Do not try to parse description or thumbprint
ro.build.description=eva-user 11 RQ3A.210705.001 EVA-202410152207-380 release-keys
# end build properties

#
# from device/rockchip/rk356x/eva/system.prop
#
service.adb.tcp.port=5555
persist.logd.logpersistd=logcatd
persist.logd.logpersistd.buffer=all
persist.nreal.usb_ip=192.168.42.129/24
ro.product.vendor.hwpn=NR-8100AGL
ro.config.media_vol_default=6
ro.ota.device=eva
ro.logd.kernel=1
vendor.gralloc.no_afbc_for_sf_client_layer=0
vendor.gralloc.no_afbc_for_fb_target_layer=0
ro.product.locale=zh-Hans-CN
persist.invn.hal.sensor.enable=1
persist.longtimesleep.poweroff.time=21600

# Property for backup NTP Server
persist.backup.ntpServer="ntp.aliyun.com"
persist.backup1.ntpServer="time.android.com"
persist.backup2.ntpServer="time.apple.com"
# end of device/rockchip/rk356x/eva/system.prop

#
# from device/rockchip/rk356x/rk356x.prop
#
ro.vendor.rk_sdk=1
# end of device/rockchip/rk356x/rk356x.prop

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
net.bt.name=Android

sdio:c00v02D0dA9BF

I'm new to this so I'm not sure if the efforts for rk3566 are 100% usable for this device, or a custom configuration is necessary.

Firmware for rockchip rk3228a wifi chip esp8089

Fri, 16 Aug 2024 08:25:13 +0000

Pls. Give fire tv like os or google tv like os for mxq pro 4k 5g processor rk3228 wifi chip esp8096

Image and multi-tool for RK322x

Wed, 23 Nov 2022 16:29:36 +0000

Good day to everyone, I was running smoothly on my tv box, rk322x, but I did something wrong and I can't boot again, then where I can download the image of armbian as well as the multi-tool so that I can again perform a clean installation on my tv box? some link maybe, thank you very much for your help.

HK1 MAX

Sun, 27 Oct 2024 10:54:25 +0000

Hello, i saw your page on the Internet and was wondering whether you could show me where the mask pins are on the HK1 MAX?

Sent from my SM-A736B using Tapatalk

Can't get usb wifi driver installed (cant get linux headers)

Sun, 20 Oct 2024 21:34:40 +0000

Hi guys I have been at this for a week now.

I came up with an idea to use MXQ pro tv box for my 3d printers as I am running klipper. Keep in mind I have klipper installed and it works perfect.

But in order to make things easier I need wifi the internal ethernet is working perfect.

I have a few beaglebone blacks that i used for another project I used wifi dongles with them and tried to install the driver on the rk3228 box but keeps on getting the following error.

v24.11 rolling for rk322x-box running Armbian Linux 6.11.4-edge-rockchip

Packages: Debian stable (bookworm)
Support: for advanced users (rolling release)
IP addresses: (LAN) IPv4: 192.168.0.153 IPv6: fe80::30e0:63ff:fed2:6c71 (WAN) 192.143.2.188

Performance:

Load: 6% Up time: 2 min
Memory usage: 13% of 977M
CPU temp: 59°C Usage of /: 70% of 7.0G

Commands:

System config : sudo armbian-config
System monitor : htop

Last login: Sun Oct 20 19:51:29 2024 from 192.168.0.148
johan@rk322x-box:~$ sudo apt-get install build-essential git dkms linux-headers-$(uname -r)
[sudo] password for johan:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-headers-6.11.4-edge-rockchip
E: Couldn't find any package by glob 'linux-headers-6.11.4-edge-rockchip'
E: Couldn't find any package by regex 'linux-headers-6.11.4-edge-rockchip'
johan@rk322x-box:~$

This is the link I have always used to install the wifi dongle driver. https://github.com/kelebek333/rtl8188fu

I'm not new to armbian but also not a pro so I have no idea hoe to install other drivers from github.

Any assistance will be much appreciated

MXQPRO 4K 5G fake S905 8GB +128GB real RK3128 1GB + 4GB

Fri, 13 Sep 2024 10:37:50 +0000

cpu: RK3128

ram: 4 x H5TQ2G43BFR 2Gbit (512M x 4) = 1GB

emmc: THGBMDG5 32Gbit = 4GB

Wifi: SV6158

heatsink also seemed fake, plastic, was not cool to touch like metal, removed to check cpu. cpu was not listed, but S905 was in photo. I claimed refund for counterfeit goods. I Expected it not to be S905, if it was a RK322X i would have kept it for armbian but RK3128 is worthless.

Wifi not working

Mon, 14 Oct 2024 09:11:10 +0000

I have and old tv box wifi is not regognized.i install

Armbian_community_24.11.0-trunk.253_Rk322x-box_noble_current_6.6.54_xfce_desktop.img.

i own tv box q9pro andowl rk3229

bluetooth not working on rk3318 running Armbian 23.02.2 Bullseye with Linux 5.15.93-rockchip64

Sun, 05 Mar 2023 16:29:17 +0000

I am new to this. I have an H96Max Android TV box which I flashed successfully with Armbian 23.02.2 Bullseye with Linux 5.15.93-rockchip64the latest armbian image. Wifi is running fine. However, I failed to activate bluetooth. I read several post around the same topic with no luck.

I am attaching several logs I collected and hope it can clarify more the case, so someone can help resolving this.

===============================================
root@rk3318-box:/# dmesg | egrep -i 'blue|firm'
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    6.838446] Bluetooth: Core ver 2.22
[    6.838756] NET: Registered PF_BLUETOOTH protocol family
[    6.838775] Bluetooth: HCI device and connection manager initialized
[    6.838804] Bluetooth: HCI socket layer initialized
[    6.838821] Bluetooth: L2CAP socket layer initialized
[    6.838868] Bluetooth: SCO socket layer initialized
[    9.513260] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43342-sdio.rockchip,rk3318-box.bin failed with error -2
[    9.525849] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43342-sdio.rockchip,rk3318-box.txt failed with error -2
[    9.693623] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43342/1 wl0: Oct 18 2016 17:43:42 version 6.25.134.25 (r662387) FWID 01-281dd9d9
[   38.183427] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   38.183447] Bluetooth: BNEP filters: protocol multicast
[   38.183468] Bluetooth: BNEP socket layer initialized

=========================
root@rk3318-box:/# rfkill
ID TYPE DEVICE      SOFT      HARD
 0 wlan phy0   unblocked unblocked

=============================================
root@rk3318-box:/# systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-03-05 19:55:27 +04; 28min ago
       Docs: man:bluetoothd(8)
   Main PID: 1867 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4587)
     Memory: 2.5M
        CPU: 97ms
     CGroup: /system.slice/bluetooth.service
             └─1867 /usr/libexec/bluetooth/bluetoothd

Mar 05 19:55:27 rk3318-box systemd[1]: Starting Bluetooth service...
Mar 05 19:55:27 rk3318-box bluetoothd[1867]: Bluetooth daemon 5.55
Mar 05 19:55:27 rk3318-box systemd[1]: Started Bluetooth service.
Mar 05 19:55:27 rk3318-box bluetoothd[1867]: Starting SDP server
Mar 05 19:55:27 rk3318-box bluetoothd[1867]: Bluetooth management interface 1.21 initialized

===============================
root@rk3318-box:/# bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available

=========================
root@rk3318-box:/# lsmod
=========================
Module                  Size  Used by
bnep                   32768  2
ir_nec_decoder         20480  0
nft_chain_nat          16384  4
xt_MASQUERADE          20480  1
nf_nat                 49152  2 nft_chain_nat,xt_MASQUERADE
nft_counter            16384  3
xt_state               16384  0
xt_conntrack           16384  1
nf_conntrack          163840  4 xt_conntrack,nf_nat,xt_state,xt_MASQUERADE
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
nft_compat             20480  2
nf_tables             212992  15 nft_compat,nft_counter,nft_chain_nat
nfnetlink              20480  2 nft_compat,nf_tables
lz4hc                  16384  0
lz4                    16384  0
brcmfmac              385024  0
brcmutil               28672  1 brcmfmac
cfg80211              876544  1 brcmfmac
snd_soc_spdif_tx       16384  1
hantro_vpu            118784  0
rockchip_vdec          32768  0
gpio_ir_recv           16384  0
rc_core                57344  3 gpio_ir_recv,ir_nec_decoder
snd_soc_hdmi_codec     24576  1
snd_soc_rockchip_spdif    16384  2
v4l2_h264              16384  2 rockchip_vdec,hantro_vpu
snd_soc_rk3328         16384  1
rockchip_rga           28672  0
videobuf2_vmalloc      20480  1 hantro_vpu
snd_soc_simple_card    24576  4
snd_soc_simple_card_utils    28672  1 snd_soc_simple_card
rockchip_iep           20480  0
snd_soc_rockchip_i2s    24576  4
snd_soc_rockchip_pcm    16384  1 snd_soc_rockchip_i2s
snd_soc_core          262144  8 snd_soc_spdif_tx,snd_soc_rockchip_pcm,snd_soc_hdmi_codec,snd_soc_rockchip_spdif,snd_soc_rk3328,snd_soc_simple_card_utils,snd_soc_rockchip_i2s,snd_soc_simple_card
videobuf2_dma_sg       24576  1 rockchip_rga
videobuf2_dma_contig    24576  3 rockchip_vdec,hantro_vpu,rockchip_iep
v4l2_mem2mem           40960  4 rockchip_vdec,hantro_vpu,rockchip_rga,rockchip_iep
videobuf2_memops       20480  3 videobuf2_vmalloc,videobuf2_dma_contig,videobuf2_dma_sg
videobuf2_v4l2         32768  5 rockchip_vdec,hantro_vpu,rockchip_rga,rockchip_iep,v4l2_mem2mem
videobuf2_common       65536  10 rockchip_vdec,videobuf2_vmalloc,videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_dma_sg,rockchip_iep,v4l2_mem2mem,videobuf2_memops
snd_pcm_dmaengine      20480  1 snd_soc_core
videodev              262144  7 rockchip_vdec,videobuf2_v4l2,hantro_vpu,rockchip_rga,videobuf2_common,rockchip_iep,v4l2_mem2mem
snd_pcm               131072  3 snd_soc_hdmi_codec,snd_soc_core,snd_pcm_dmaengine
mc                     61440  6 rockchip_vdec,videodev,videobuf2_v4l2,hantro_vpu,videobuf2_common,v4l2_mem2mem
snd_timer              40960  1 snd_pcm
snd                    94208  12 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm
cpufreq_dt             20480  0
soundcore              16384  1 snd
zram                   40960  3
btusb                  65536  0
btrtl                  24576  1 btusb
btbcm                  28672  1 btusb
btintel                40960  1 btusb
bluetooth             638976  11 btrtl,btintel,btbcm,bnep,btusb
rfkill                 36864  6 bluetooth,cfg80211
sunrpc                581632  1
ip_tables              32768  0
x_tables               49152  5 xt_conntrack,nft_compat,xt_state,ip_tables,xt_MASQUERADE
autofs4                49152  2
dwmac_rk               28672  0
stmmac_platform        24576  1 dwmac_rk
stmmac                237568  2 stmmac_platform,dwmac_rk
dw_hdmi_cec            16384  0
pcs_xpcs               24576  1 stmmac
dw_hdmi_i2s_audio      16384  0
lima                   61440  0
gpu_sched              40960  1 lima
gpio_syscon            20480  1
adc_keys               16384  0

kiauh klipper

Thu, 10 Oct 2024 17:33:33 +0000

try to run kiauh to run klipper i get an error when i try to update system arbian update the repository no longer has a release.also i install python 3 and i get an error that i need to install python3 .i install arbian using this

https://users.armbian.com/jock/rk322x/armbian/stable/

and follow this guide

https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/

maybe the arbian image i downloaded is very old which one you suggesrt me for my old tv box to install

I have a Transpeed TT TV Box (Media Player) and need help

Sun, 06 Oct 2024 07:38:35 +0000

I have used lots in my time but recently changed to this.

I can't get RKMC to access my shared folders because, when I enter the address with back slashes it changes them into forward slashes.

With VLC it works perfectly but is unusable without sorting by descending date.

Why does it swap the slashes/???

I prefer RKMC to VLC

Linux on a RK3288

Fri, 27 Sep 2024 07:11:07 +0000

Hello guys I have a rk3288 POS with Android 7 I heard that the board can run Linux on it who can help me ?

I need to reset password but can't get to grub in armbian

Thu, 26 Oct 2023 15:59:34 +0000

edit: Found the solution

Got this tv box "x88pro 10" repurposed to run armbian by someone and it demands login/password. The default one(root 1234) doesn't work. Also I can't seem to stop the loading process and get to grub to try and delete passwords manually from there(tried pressing random keys during boot, tried holding shift). Please help And also point me to an armbian image I could use in case I fail to reset the password

Armbian version it runs atm is 22.05.0-trunk Bullseye

tech specs are: RK3318 Quad-Core 64bit Cortex-A53, Penta-Core Mali-450 up to 750Mhz, 2 or 4Gb ram

G96 mini with RK3228A bricked or bad RAM

Wed, 05 Jun 2024 21:00:27 +0000

I have a "G96 mini" box that is bricked, I don't know its history but wrong firmware is a likely candidate- It contains a RK3228A and 08emcp08-el3cv100 ram & flash in a single chip. After some investigation I found how to boot from SD, boot in maskrom mode and access it with AndroidTool and capture the serial messages.

I found very little info about this specific box, only that looks similar to the H20 mentioned in this thread:

I tried all the bootloaders I could find including multitool-1.11 and the armbian indicated in that thread and this is what happens:

DDR Version V1.11 20200910_dbg                                             
In                                                                          
ID:0xFFF                                                                    
unknow device                                                         
ERR

Another older bootloader I found around there seems to go a step further:

DDR Version V1.06 20171130_1_xintu_en_rd_odt
In                                                                          
300MHz                                                                      
LPDDR3                                                                  
Bus Width=32 Col=11 Bank=8 Row=14 CS=1 Die Bus-Width=32 Size=1024MB
mach:4
rd addr 0x60000004 = 0xE0808004
ERR

Do you think it requires some special customized bootloader or is it that the RAM is not working properly?

Thanks in advance,

RK3318 cant boot after update

Sat, 06 Jul 2024 18:11:59 +0000

Installing Armbian_community_24.8.0-trunk.314_Rk3318-box_bookworm_current_6.6.36_minimal.img.xz from the github works fine.

Doing apt upgrade renders system unbootable.

Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.

Pls fix

Tv Box HK1 Rbox brick

Sun, 21 Jul 2024 16:52:15 +0000

I brick my tv box HK1 Rbox cpu3528 ram 4gb rom 64gb can someone help me unbrick this tv box, thank you very much for your help

RK3399 Old Images

Fri, 16 Aug 2024 07:15:10 +0000

Hi does anyone have backup of images by balbes150 from below topic?
All the links seems to point to a dead end. Even the web archive has nothing so would be grateful if anyone could provide the images.

Thanks!

problems to compile and boot TV Box Lenfo HK1 RBOX

Fri, 02 Aug 2024 14:26:36 +0000

Hello people,

I'm trying to compile armbian to run on my TV Box.

If I use the image Hinlink ht2 I can boot without problem, but if I try to compile my version of Armbian, the tv box does not boot.

I'm using the follow sintax to compile:

./compile.sh build BOARD=hinlink-ht2 BRANCH=legacy BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base EXPERT=yes KERNEL_GIT=shallow DEB_COMPRESS=xz

I haven't the TTL to debug.

What I already tryed:

Burn the hinlink ht2 image to SD card and change the ROOT partition to my image (no work)

Burn my image to SD card and copy the boot partition of hinlink to boot partition on SD Card (no work)

Burn hinlink ht2 image and get the dtb and put on my image (no work)

I'm accept any suggestion.

Why I'm trying to compile ? The Ethernet is not working, on my board it uses the gmac0 and the hinlink ht2 uses gmac1

regards.

Panda

LEMFO RBOX HK1RBOX with rk3528

Sun, 05 May 2024 09:38:14 +0000

Hello!

I have got the LEMFO RBOX HK1RBOX with rk3528 (https://de.aliexpress.com/item/1005006654505780.html?spm=a2g0o.order_list.order_list_main.32.7cbf5c5fIj4Quv&gatewayAdapt=glo2deu)

I have tried the following image recommended in one thread

https://github.com/armbian/community/releases/download/24.5.0-trunk.367/Armbian_community_24.5.0-trunk.367_Hinlink-ht2_bookworm_legacy_5.10.160_minimal.img.xz

I copied the rockchip folder to the boot folder and as well the a armbianEnv.txt adding dtfile=rockchip/rk3528-hlink-ht2.dtb. The original armbianEnv.txt was modified the same way.

that did not work. Did you miss any other steps?

Later on I tried I tried Armbian_24.5.0_rockchip_h28k_jammy_5.10.160_server_2024.04.25.img.gz from ophub with rk3528-hlink-ht2.dtb, unfortunately the LAN did not work, even I have tried all other rk3528

dtb's.

[LAN error: ....... eth0: stmmac_hw_setup: DMA engine initialisation failed , eth0: stmmac_open Hw setup failed]

Is there any img and dtb that works with this TV Box?

I would appreciate any hint?

Efforts to develop firmware for HK1 RBOX R2 4G/64G

Fri, 16 Jun 2023 11:05:00 +0000

Another Chinese Toy to brick

@ewww Let's find out also looking for a way to build uboot and recreate sdcard for booting.

Does h96max have analog input for microphone?

Wed, 17 Jan 2024 03:02:27 +0000

Hello everyone, I have been in this world of armbian for a year and I want to develop some projects on this OS ,and at this moment I need to record audio with h96max with rk3318 chip, the system says yes, it has analog input through the stereo plug . Is it possible to put a microphone on this board?

aplay -l
card 0: ANALOG [ANALOG], device 0: ff010000.i2s-rk3328-hifi rk3328-hifi-0 [ff010000.i2s-rk3328-hifi rk3328-hifi-0]
Subdevices: 1/1......

arecord -D hw:0,0 -f cd -t wav -d 5 test.wav works

but the output file is totally silent, using a hands-free cell phone

Where can I put a microphone on the board?

Rockchip rk3066 based tv box

Tue, 09 Jul 2024 22:48:58 +0000

Good afternoon everybody, I have a minix mini neo 5 box and I wanted to install Armbian for the home assistant. Specifications: 1G Ram and 16 nand chip rk3066. I've already tried with the multitool and I can't start it. Thank you for help

rk3318 TVBox - Upgrading linux-image to 24.8.0-trunk.332 broke bootup

Sun, 07 Jul 2024 02:01:51 +0000

Hello there,

I upgraded the newest kernel (`linux-image-current-rockchip64 arm64 24.8.0-trunk.332`) today. Something went wrong and it is failing to find the rootfs and drops in to initramfs shell. Attached are the update logs and login images. How do I fix this?

Thanks

apt-update.txt

MXQ 4k stuck and freeze

Sat, 22 Jun 2024 15:02:40 +0000

When i boot on TV box armbian jammy (mis match version on th board).
I try to reboot multitool from sd card but not work and i cann't install another version.

Time in the screen freeze in yester day.

Please told me the command to boot from sd card.