Armbian for H313 X96-Q LPDDR3 TV-Box

[Nick A]

@SecLyzer You can find everything you need here 

 

[Morales Morales]

@Nick A Hi, I was wondering if you plan to update your distro since it hasn't been updated since 2025.

[Jorge Henrique]

I created this account just to thank you, man. Thank you so much, it worked perfectly here. Finally, my old TV box has another use besides collecting dust.

[Nick A]

@Morales Morales when I have more free time.. busy with work the next couple of months.

[SecLyzer]

@Nick A TY very much for your reply, I've managed to create my first build but I am a bit confused because it made an IMG with a FAT32 boot partition, is it right or did I miss something?
 

[Nick A]

@SecLyzer U-Boot can boot from a FAT32 or Linux file system. You can change this in your board configuration file.

[kimo]

On 11/18/2025 at 11:38 AM, Nick A said:

My build uses the miniarch patches. https://github.com/NickAlilovic/build/releases/tag/20250306

 

Here's a direct link to X96q ddr3 server image.

https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz

 

 

 Hello i hope everone is good, i have this X96Q with motherboard reference BA301_141 V4.1 20244 and after trying this image Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz led turned blue but nothing on screen when i tried to connect uart to read data, for some reason it did boot and work but when i turned off and turn on the device this time with lan attached it didnt want to boot again only blue led, this remember me of miniarch image i have to turn on and off de device like 15 to 20 times for the image to boot, this is what happen with this Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz maybe because you use miniarch patches, but i found other images that works so good at first time here is the images that works on this device and i hope this might help fix this boot problem with armbian image

 

https://github.com/velvet-os/imagebuilder/releases/tag/230910-02

and this 

https://mega.nz/file/DBUHiZRZ#F_wx89EJ9i4LvCsO2VrTYglx5SrfQGrLxs_DLr6mTUo

[Nick A]

@kimo Can you post your uart data?

[hexdump]

just for reference: the velvet-os image mentioned above is using some old mainline u-boot with patches from warpme minimyth2 from that time - here is how it was built: https://github.com/hexdump0815/u-boot-misc/blob/230127-01/readme.h616 ... the default u-boot of this image is the tx6s one

 

best wishes - hexdump

[William Bulchi]

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

[Uzair902]

Hey guys, I just wanted some help from you regarding my X96Q. It is a 1+8GB Model with PCB Revision V1.1. It has a H313 processor but sunxi-fel reports H616.

A few weeks ago I repaired the USB port of this box and I was successful in it and everything worked perfectly after that(the device booted up to android and worked perfectly) but Then I started to play with that Hidden button in AV port and I randomly clicked it and I thought it would be harmless but after that the device stuck in Red LED and didn't booted anything(possibly an EMMC Corruption). I tried Phoneix Suit first but it stuck on ram init.

Then I brought a CP2102 Adapter to read the serial logs, and it turned out to be a Dram calibration errors where: Boot0 starts > Initializes The Emmc, the Board and the CPU -> Then the PMU(reported as AXP806 but physically AXP305) sets ram voltage to 1500mV -> Then it tries to Dram training -> fails and throws  [...] "Read calibration error" multiple times —> keeps retrying until it gives up with "[...] Restraining final error."

 

I investigated further and found that my emmc chip's critical sectors are corrupted. I used sunxi-fel to read the emmc and found that it fails to read after 16MB mark, means emmc got corrupted when I repeatedly pressed the AV port button.

Now I tried a Armbian via sd card and it says:

[...] Your Current DRAM Config isnt supported...

Retrying...

And keeps doing In a endless retry loop.

Same for Miniarch, Armbian and many other builds...

 

 Any idea what's the problem with my box?