Vincenzoernst1

Hi all,
Inspired by this thread, I've built mainline Linux images for the H96 MAX M9. (Images here: https://github.com/gregordinary/boot2deb/releases/tag/20261005-snapshot) Thank you to everyone who posted factory DTBs, boot logs and board photos, it really helped jumpstart the process!
 
Quick disclosure: While this post was written by me (gregordinary), the project build tool, patches, and documentation relied heavily on AI (Claude Code).
 
My Particular H96 Max M9: 8 GB RAM / 128 GB eMMC, AIC8800D80 Wi-Fi, factory firmware from September 2025 (Android kernel 6.1.75).
 
In Short
The box runs Debian forky on mainline Linux 7.2.9 and mainline U-Boot 2026.07 (plus patches, Rockchip's rkbin DDR init, and BL31 blobs). Most components work, including the GPU, NPU, hardware H.264/HEVC decode (8-bit and 10-bit), Wi-Fi, Bluetooth, all three audio outputs (3.5mm audio jack, S/PDIF, HDMI), HDMI-CEC, IR and suspend. Remaining gaps are hardware video encode, 4K60 output, and Vulkan. I thought I'd share things I've made in hopes that it is useful for others to advance their development with this device.
 
More Detail
For some context, I mess with a bunch of SBCs and other devices, so I used Claude to build boot2deb, a tool that can build Debian images using recipes for devices. So far I've used it for the Asus C201, Turing RK1, and now the H96 Max M9.
For those who just want to test some images out, I've made a snapshot with pre-built images for all the devices listed above. Additionally, it has some U-Boot images with Ethernet, HDMI, and USB all working.
Things of Interest:
Device Tree, written against the in-tree rk3576.dtsi; hopefully useful if you're building Armbian or your own kernel. Kernel and U-Boot patches for the RK3576. The README should detail what each patch is for. U-Boot that can recover the box without a serial cable. Reference notes for the H96 Max M9 and the RK3576 SoC. Observation: My H96 had 16 partitions, I think ones on this forum thread had 15. My firmware revision was RZX.V01.20250924.1643. Mainline Status
I've tested a number of components across builds, mostly kernels 7.1 and 7.2. The enablement status page tracks what works and what doesn't.
NPU: The images I built are mainline and have the rocket driver. Separately, I've been working on rocket-userspace, which together with ggml-rocket let's you build & run llama.cpp/whisper.cpp on mainline with support for the Rockchip NPU. I've mainly tested it with RK3588 but have made decent progress on the RK3576. The NPU on the 3576 isn't as powerful so it's use cases are probably geared more towards things like object detection. For that I've made tflite-rocket. Audio: HT5010 on SAI1 is correct, the ES8388 in the factory DTB is a leftover from Rockchip's EVB. WiFi/BT Chip: Similar to the audio situation above, the ap6275p label in the DTB is seemingly boilerplate. My unit and the one in the boot logs posted somewhere in this thread run an AIC8800D80 under that label. The SDIO vendor ID shows: 0xC8A1, which is AICSemi. The AIC8800D80 driver is out of tree; I used the radxa-pkg/aic8800 fork to build it into images produced with boot2deb. USB Port for Flashing: is the blue USB 3.0 port, (Maybe this was obvious to many but I had a dumb moment or three troubleshooting with the 2.0 port). Remotes: Although the box has an IR Receiver, the remote is a 2.4 GHz RF remote that speaks to a USB receiver soldered inside the box and shows up as a standard USB keyboard and mouse. Works with no additional configuration. The IR receiver is on gpio0 PC4; I tested it successfully using gpio-ir-receiver and an IR Remote bundled with an older H96 Box. Recovery Button: This was interesting, it seems what the recovery button does depends on the factory firmware build. Several people here reach Loader mode by holding it before connecting USB. On my unit (a newer firmware build) the same button booted Android recovery instead, and "reboot to bootloader" landed in fastboot. Shorting the two pins at power-on though, reaches maskrom as expected. One tweak I made my U-Boot build was remapping the recovery button so it goes straight to maskrom without having to manually short pins. Failed Backups: When I first got the device I tried dumping the factory firmware, however backing up the eMMC over rockusb silently stopped at 32 MiB. Every read at or past sector 65536 returned 0xCC filler with a success status, so the dump looked complete, but wasn't. I think cmuki reported of a dump "full of cc" as well. I ended up dropping to U-Boot, running ums 0 mmc 0 at the prompt and dd the resulting block device onto my laptop.  
There's probably a lot more to add, but I'll leave it here for now and hope others find this work useful. Will try and add some screenshots, pictures, logs, etc. in the coming days.

I came here to thank @jock

https://github.com/armbian/build/pull/8679
 
and ask you to make the test @Vincenzoernst1 @GBEM @guenter
you don't need to install external driver anymore

merged 2 commits into armbian:main from paolosabatino:update-tm16xx  4 days ago

Available since https://github.com/armbian/build/tree/v25.11.0-trunk.258
rockchip rk3566: h96-TVbox: Include i2c Led Pins into dts. by @hqnicolas in armbian/build#8666
rockchip64: update tm16xx driver from kernel mailing list. by @paolosabatino in armbian/build#8679

 
 

PR:
included fd6551

https://github.com/armbian/build/pull/8666

@fevangelou
 
nice guide. THX!

but maybe it would be best to have the instruction in an separate topic! in best case it gets also pinned.
so new users can find it much easier than scrolling though 18 pages (in this thread. there is also the 4gb thread) to find it......

For anyone looking for simple instructions to install the official Armbian image for "H96 Max V56" (as of August 30th, 2025) using a Linux PC (e.g. Ubuntu Desktop 24.04):
 
1. Install the "rkdeveloptool" tool first, as instructed in: https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdeveloptool?host-os=debian
 
sudo apt-get update sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget git clone https://github.com/rockchip-linux/rkdeveloptool cd rkdeveloptool autoreconf -i ./configure make -j $(nproc) sudo cp rkdeveloptool /usr/local/sbin/  
At the time of writing, this installed version 1.32. If you installed "rkdeveloptool" from Ubuntu's repos, it would install version 1.0 which may work, but let's be on the safe side here...
 
2. Connect and boot the device to loader/maskrom mode
 
2.1 While pressing the reset button (back/right) with a pin, connect the USB 2.0 port (back/left) and the power cable. Gotta be careful here not to miss the reset button pressing while connecting the cables.
 
2.2 Use the rkdeveloptool tool to identify the device and the mode it is on ("loader" or "maskrom").
    $ rkdeveloptool ld
   
    ...should show the connected device if point 2.1 was successful - e.g. on my 8GB RAM device it printed this: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Loader
   Or after I had already flashed Armbian, it would show: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Maskrom
 
    (If you installed "rkdeveloptool" from Ubuntu's repo, the command is "rkdeveloptool list" if I recall correctly - every other "rkdeveloptool" command following though is the same)
 
    Now grab the latest release of Armbian for this device. At the time of writing it was: https://github.com/armbian/community/releases/download/25.11.0-trunk.106/Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz (the name of the device is on the filename)
 
    Extract the included .img file with (sudo apt install xz-tools):
    $ unxz Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz
 
2.2.1 If in "loader" mode (see the last part of the command's output above), simply flash Armbian directly. E.g.
    $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img
   (if you attempt to flash the attached bootloaders, you'll get a "device not supported" error - Armbian already contains a bootloader)

2.2.2 If in "maskrom" mode (e.g. if you are re-flashing Armbian), flash the bootloader first:
    # For the 8GB RAM device use the attached (in this post) H96-MAX-8gb-MiniLoaderAll.bin file
    $ sudo rkdeveloptool db H96-MAX-8gb-MiniLoaderAll.bin
 
    # For the 4GB RAM device use the attached (in this post) H96-MAX-4gb-MiniLoaderAll.bin file
    $ sudo rkdeveloptool db H96-MAX-4gb-MiniLoaderAll.bin

    ...and then re-flash Armbian as you did the first time:
    $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img
 
2.3 Reboot the device with:
    $ sudo rkdeveloptool rd
 
Done!
 
If all goes well, once you reboot the device you will be asked to set a root password and optionally a sudo user. Rebooting afterwards you should now be greeted with:
 
_ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.11 rolling for h96-tvbox-3566 running Armbian Linux 6.12.44-current-rockchip64 Packages: Debian stable (bookworm), possible distro upgrade (trixie) Updates: Kernel upgrade enabled and 2 packages available for upgrade Support: for advanced users (rolling release) IPv4: (LAN) 192.168.1.10 (WAN) 1.2.3.4 Performance: Load: 3% Uptime: 2 min Memory usage: 2% of 7.50G CPU temp: 40°C Usage of /: 3% of 57G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop Last login: Sat Aug 30 12:47:54 2025  
Key points:
- If you do this the first time, it's obviously a matter of just flashing the latest Armbian image directly.
- You don't need to open the device or compile Armbian.
- It's simpler than 2 years ago when I bought the device thanks to people like @Hqnicolas (muito obrigado Nicolas!)
H96-MAX-4gb-MiniLoaderAll.bin H96-MAX-8gb-MiniLoaderAll.bin

@tnt

i also didnt get the the sd slot running. i soldered 3 NEW slots and none of them worked. since i ordered a 10 pack from china i didnt mind to dump them after unsoldering.
i always got a dmesg error (logs somewhere above).
 
there are 2 errors possible:
bad china quality slots there is something on the board missing.  
also i dont think there was somthing wrong with the soldering since im an enineer and solder on daily basis. btw. i uses a hot air gun for solderding, therefor it i also should be working.

if there are now 2 of us having problems i might thingk its no problem on my side.....

chip seems to be have driver support already.
 
discussed here
 
what says ip a?

@Hqnicolas
 
update
 
 

@Vincenzoernst1 thanks for the advice,
i made a Pull Request (PR) to enable kernel 6.9 Current and 6.11 Edge

https://github.com/armbian/build/pull/7310/files

now the community releases will build 6.9 and 6.11 for this box, Please test and keep a copy of it.

Hi all.
When I saw this page (thanks @Hqnicolas) - looked at the specs of this board, and looked at its price ($85) - I knew I had to try to install Linux on it.
 
   
First things first - I did an Android backup.   
====================================
1. Turned on  Android box. I connected it to the local network 2. Turn on developer mode. Turn on debugging. 3. On the Linux computer, run $ adb connect 192.168.0.20:5555 $ adb root $ adb shell rk3576_box:/ # cat /proc/partitions | grep mmcblk  179        0  122142720 mmcblk2  179        1       4096 mmcblk2p1  179        2       4096 mmcblk2p2  179        3       4096 mmcblk2p3  179        4       4096 mmcblk2p4  179        5       4096 mmcblk2p5  179        6       1024 mmcblk2p6  179        7      65536 mmcblk2p7  179        8      98304 mmcblk2p8  179        9     393216 mmcblk2p9  179       10     393216 mmcblk2p10  179       11      65536 mmcblk2p11  179       12        512 mmcblk2p12  179       13       1024 mmcblk2p13  179       14    4194304 mmcblk2p14  179       15  116905440 mmcblk2p15  179       32       4096 mmcblk2boot0  179       64       4096 mmcblk2boot1 rk3576_box:/ # exit adb pull /dev/block/mmcblk2 /home/user/full-big.iso Next - using the dd utility, reduce the resulting file to 6Gb, since the image takes 120Gb dd if=/home/user/full-big.iso of=/home/user/H96_MAX_M9_RK3576-android-full.iso bs=512 count=11895122 
Getting the dtb file
-----------------------
$binwalk --signature --term full_mini   Find the largest Flattened device tree.   DECIMAL       HEXADECIMAL     DESCRIPTION                                                                                                                                                                    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ………………..…… 55363843      0x34CC903       Unix path: /sys/kernel/debug/%pd/%s                                                                                                                                            55438666      0x34DED4A       Unix path: /lib/firmware/updates/6.1.57                                                                                                                                        55440137      0x34DF309       Unix path: /dev/disk/by-id/ may cause data corruption                                                                                                                          55466136      0x34E5898       Neighborly text, "NeighborAdvertisements6ip6t_REJECT: ECHOREPLY is not supported"                                                                                              55496752      0x34ED030       Unix path: /sys/kernel/debug/rk628/2-0050/hdmitx_color_bar                                                                                                                     55555249      0x34FB4B1       Unix path: /sys/kernel/debug/rk628/2-0050/dsi_color_bar                                                                                                                        55760043      0x352D4AB       Unix path: /sys/kernel/debug/%s                                                                                                                                                55760097      0x352D4E1       Unix path: /sys/kernel/debug/%pd/%s                                                                                                                                            55846910      0x35427FE       Neighborly text, "Neighborenabling vblank on crtc %u, ret: %d"                                                                                                                 55855620      0x3544A04       Unix path: /lib/firmware/6.1.57                                                                                                                                                55878704      0x354A430       Unix path: /sys/firmware/devicetree/base                                                                                                                                       55913424      0x3552BD0       Unix path: /sys/kernel/debug/rk628/2-0050/scaler_color_bar                                                                                                                     55913634      0x3552CA2       Unix path: /sys/kernel/debug/rk628/2-0050/gvi_color_bar                                                                                                                        56002822      0x3568906       Neighborly text, "neighbor %.2x%.2x.%pM lostrward_delay_timer"                                                                                                                 56003414      0x3568B56       Neighborly text, "NeighboraversalTime"                                                                                                                                         56031712      0x356F9E0       Unix path: /sys/kernel/debug/rk628/2-0050/dsi_color_bar                                                                                                                        56031782      0x356FA26       Unix path: /sys/kernel/debug/rk628/2-0050/gvi_color_bar                                                                                                                        56538119      0x35EB407       MySQL ISAM compressed data file Version 3                                                                                                                                      58589623      0x37E01B7       mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit                                                                                                   58682916      0x37F6E24       ASCII cpio archive (SVR4 with no CRC), file name: "dev", file name length: "0x00000004", file size: "0x00000000"                                                               58683032      0x37F6E98       ASCII cpio archive (SVR4 with no CRC), file name: "dev/console", file name length: "0x0000000C", file size: "0x00000000"                                                       58683156      0x37F6F14       ASCII cpio archive (SVR4 with no CRC), file name: "root", file name length: "0x00000005", file size: "0x00000000"                                                              58683272      0x37F6F88       ASCII cpio archive (SVR4 with no CRC), file name: "TRAILER!!!", file name length: "0x0000000B", file size: "0x00000000"                                                        58782120      0x380F1A8       Intel x86 or x64 microcode, pf_mask 0xf4401f01, 2001-09-12, rev 0x30000000, size 1                                                                                             58888000      0x3828F40       AES S-Box                                                                                                                                                                      58888256      0x3829040       AES Inverse S-Box                                                                                                                                                              63311872      0x3C61000       gzip compressed data, from Unix, last modified: 1970-01-01 00:00:00 (null date)                                                                                                64777216      0x3DC6C00       Flattened device tree, size: 262377 bytes, version: 17                                                                                                                         65039872      0x3E06E00       PC bitmap, Windows 3.x format,, 220 x 110 x 8                                                                                                                                  65046528      0x3E08800       PC bitmap, Windows 3.x format,, 220 x 110 x 8                                                                                                                                  65053184      0x3E0A200       PC bitmap, Windows 3.x format,, 220 x 110 x 8                                                                                                                                  65059840      0x3E0BC00       PC bitmap, Windows 3.x format,, 220 x 110 x 8                                                                                                                                  65066496      0x3E0D600       PC bitmap, Windows 3.x format,, 220 x 110 x 8                                                                                                                                  65073152      0x3E0F000       PC bitmap, Windows 3.x format,, 220 x 110 x 8                                                                 ^C ~$    ~$dd if=full_1_mini of=h96-m9_original.dtb bs=1 skip=64777216 count=262377  ~$dtc -O dts h96-m9_original.dtb -o h96-m9_original.dts    
How to burn an Android image to a box:
==================================
Press the reset button. Turn on the power.
$rkdeveloptool db RK3576_MiniLoaderAll.bin
$rkdeveloptool wl 0x0 full_mini
 
cc @El308
 
Armbian
=====================
Copy the file h96-m9.csc directory to the directory build/config/boards/
Create build/packages/blobs/h96-m9/ directory and copy h96-m9_original.dtb file into it
 
Run the build
------------------
build debian 12 DESKTOP
./compile.sh BOARD=h96-m9 BRANCH=vendor BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=noble KERNEL_GIT=shallow BUILD_DESKTOP=yes DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base
 
build debian 12 server
./compile.sh BOARD=h96-m9 BRANCH=vendor BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow BUILD_DESKTOP=no EXPERT=yes KERNEL_CONFIGURE=no

Installing
----------------
Press the reset button. Turn on the power.
 
$rkdeveloptool db RK3576_MiniLoaderAll.bin
$rkdeveloptool wl 0x0 Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop-test_1.img
 
Warning! This build has a very important drawback. After flashing, the reset button stops working. Without it it will be difficult to flash the console. If you don't have a console cable - don't flash with this firmware yet. I'll be working on finalizing it now. Wait for a while.
 
If you have a console cable and you need to install another image.
1. Connect the console cable.
2. Start the console.
3. At the same time try to stop loading by pressing ctrl+c in the console. It may not work the first time.
3. Enter in the u-boot console
part uuid mmc 0:1 partuuid
4. Reboot the  box.
5. Flash
$rkdeveloptool db RK3576_MiniLoaderAll.bin
$rkdeveloptool wl 0x0 Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop-test_1.img

Test debian 12 DESKTOP  and debian 12 server.
==================================================
It works
-----------
1. USB2.0 and USB3.0 are working
2. WiFi6 works: router shows 11ax 1x1 80 MHz

Not working
-----------
1. Reset button in UBOOT
2. When turning off the box, the lights are still on. Probably - it is not really turned off.
3. video acceleration does not work.

Tests
==============
$ glmark2-es2-wayland  ----------------------------- MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) libEGL warning: egl: failed to create dri2 screen =======================================================     glmark2 2023.01 =======================================================     OpenGL Information     GL_VENDOR:      Mesa     GL_RENDERER:    llvmpipe (LLVM 17.0.6, 128 bits)     GL_VERSION:     OpenGL ES 3.2 Mesa 24.0.9-0ubuntu0.1     Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=32 stencil=0 samples=0     Surface Size:   800x600 windowed ======================================================= [build] use-vbo=false: FPS: 85 FrameTime: 11.857 ms [build] use-vbo=true: FPS: 86 FrameTime: 11.747 ms [texture] texture-filter=nearest: FPS: 128 FrameTime: 7.842 ms [texture] texture-filter=linear: FPS: 120 FrameTime: 8.345 ms [texture] texture-filter=mipmap: FPS: 104 FrameTime: 9.689 ms [shading] shading=gouraud: FPS: 63 FrameTime: 15.886 ms [shading] shading=blinn-phong-inf: FPS: 58 FrameTime: 17.303 ms [shading] shading=phong: FPS: 51 FrameTime: 19.827 ms [shading] shading=cel: FPS: 50 FrameTime: 20.407 ms [bump] bump-render=high-poly: FPS: 42 FrameTime: 24.208 ms [bump] bump-render=normals: FPS: 108 FrameTime: 9.273 ms [bump] bump-render=height: FPS: 99 FrameTime: 10.157 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 58 FrameTime: 17.272 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 34 FrameTime: 30.001 ms [pulsar] light=false:quads=5:texture=false: FPS: 96 FrameTime: 10.481 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 21 FrameTime: 48.463 ms [desktop] effect=shadow:windows=4: FPS: 50 FrameTime: 20.021 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 59 FrameTime: 17.063 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 66 FrameTime: 15.303 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 50 FrameTime: 20.203 ms [ideas] speed=duration: FPS: 48 FrameTime: 20.963 ms [jellyfish] <default>: FPS: 37 FrameTime: 27.768 ms [terrain] <default>: FPS: 2 FrameTime: 558.207 ms [shadow] <default>: FPS: 50 FrameTime: 20.170 ms [refract] <default>: FPS: 8 FrameTime: 127.994 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 80 FrameTime: 12.594 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 63 FrameTime: 15.980 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 85 FrameTime: 11.845 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 67 FrameTime: 14.929 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 54 FrameTime: 18.690 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 49 FrameTime: 20.822 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 50 FrameTime: 20.299 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 47 FrameTime: 21.386 ms =======================================================                                   glmark2 Score: 61  =======================================================  
First of all, you need to solve the problem with non-working reset button in U-boot.
If possible, enable USB booting. This can be very useful if the emmc chip fails over time.
Thanks for the links to RK3576_MiniLoaderAll.bin and the firefly repository.
The firefly image in u-boot has the reset button working. Will have to look at their u-boot build settings.
 
I continue to study...
 
Links:
 
RK3576_MiniLoaderAll.bin
https://drive.google.com/file/d/1gkOdYMaqUBe0iykbIoBcTa5c-fZcjRQU/view?usp=sharing
 
h96-m9_original.dtd/h96-m9_original.dts
https://drive.google.com/file/d/1tIcK2nWX6hHQY66p1k4BiWnw3CCXRhFd/view?usp=sharing
https://drive.google.com/file/d/1OkZhmmadyvwdTw7zIzExARgoYgO-JVs9/view?usp=sharing
 
h96-m9.csc
https://drive.google.com/file/d/1Eghh1MmzQoi8KTOPBHQS6i38db3YvF_-/view?usp=sharing
 
H96 MAX M9 RK3576-android-full.iso.7z
https://drive.google.com/file/d/1i4geoEatD7bagCkkIiRvYSBYGGELivWV/view?usp=sharing
 
Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop-test_1.img
https://drive.google.com/file/d/1smumqfmyCDFFaQjoVCFVgQfWG4MN0Shc/view?usp=sharing
 
Armbian-unofficial_24.8.0-trunk_H96-m9_bookworm_vendor_6.1.75-test_1.img
https://drive.google.com/file/d/1kfLxSNcN3ZJp8iKUVgtncFxhD2TsoNo3/view?usp=sharing
 
Here are the pictures of the board:
=============================
 
 
 
 
 
 
 
 

Learn how to build, flash, and initial-configure Armbian Ubuntu 24.04 for the Shenzhen Haochuangyi Technology Co., Ltd. H96 MAX V56 RK3566 8GB/64GB TV Box:
 
https://green.bug-eyed.monster/armbian-on-the-h96-max-v56-android-tv-box/
 
This was written by a complete novice, so any corrections or suggested additions would be greatly appreciated, via the page comment section.
 
GBEM 👽

I have added rk3566-h96-max-v56 to the repo. You could try with this one.
 
I think the JianPian is very similar to H96 Max V56 so I made this config file from this post.
 
This is a blind attempt... I have no much info on the JianPian and I have no way to test the config. Let me know if it works for you.
 

@maka @paradigman @pessimism Look at this: 
https://github.com/armbian/build/releases/tag/v24.8.0-trunk.474
rockchip64-edge: add rkvdec2 for rk356x by @amazingfate
rockchip64-edge: disable hantro g1 h264 decoder on rk356x by @amazingfate
 
Video Acceleration....

@paradigman
@xuandat09
 
fixed for kernel 6.6: Github Pull Request
it will be present on next release,
h96-tvbox-3566.tvb
 
 
In kernel 6.10+ I think Desktop Rockchip Will became Viable
Fell free to fix kernel 6.10.2 

i did an 32gb image today,
taking advantage of the fact that I dismantled my 32gb TTL enabled server.
I took the opportunity to create a 32gb image.

instruction
32gb-desktop-example.img
 
@paradigman please give feedback if it works

oh. sorry didnt notice that it was a X6 version he was asking for.
 
@loi xin
this thing is 135€ in germany and imho not worth it. the v56 is much cheaper with the same functionallity (but "only" having single WIFI). so imho if u have the chance to send it back, replace it with the v56 unit if u can. then u have a ready to go unit.
 
@Hqnicolas opened a topic for the H96 MAX M9 RK3576 TV Box 8G/128G which i find the much more interesting unit, with much more power. but the pricing of this unit (top notch) is holding me back right now.