I recently I bought a TV box with an h618 processor And I want to install Linux to make it a server but I only find images for the h616 processor, can I install one of these images on my TV box? It seems that the h616 processor and the h618 procesador are almost the same

Thanks :D

root@transpeed-8k618-t:~# ls /dev/dri
by-path  card0
 

root@transpeed-8k618-t:~# lsmod | grep panfrost
panfrost               90112  0
drm_shmem_helper       28672  1 panfrost
gpu_sched              57344  1 panfrost

Is this dmesg error correlated with panfrost disfunction? 

Any ideas about this?

I wanted to share what I did to get a recent Armbian build working reliably on my Tanix TX6 (Allwinner H6), in case it helps other users or developers.

My TX6 would not boot the recent Armbian image normally.

The image I was testing was based on Debian 13 Trixie with:

Linux 6.18.50-current-sunxi64

The Linux/rootfs part itself was usable, but the board would not boot correctly with the boot chain included in the recent image.

1. Getting the recent image to boot

What finally worked was creating a hybrid image.

I kept the recent Armbian Linux partition/root filesystem unchanged, but replaced the low-level boot components with those from an older TX6-compatible image.

In practice, I transplanted the older:

SPL
U-Boot
TF-A / boot chain

into the recent image.

The older working bootloader was based on U-Boot 2022.10, while the newer image contained a much newer U-Boot.

After doing this, the recent Debian 13 / kernel 6.18.50 system started booting successfully on the Tanix TX6.

So in my case the first problem did not appear to be the Debian root filesystem itself, but rather compatibility between the newer boot chain and this particular TX6.

I am currently keeping the working boot-related packages on hold so that a normal upgrade does not overwrite the configuration that boots correctly:

armbian-bsp-cli-tanix-tx6-current
armbian-firmware
linux-dtb-current-sunxi64
linux-image-current-sunxi64
linux-u-boot-tanix-tx6-current

This is only a temporary precaution while I test stability.

2. Cold boot problem

Once the hybrid image was booting, I found a second problem.

If the TX6 had been completely disconnected from power for several hours, the first boot would sometimes stop around:

Scanning for Btrfs filesystems

At first I thought Btrfs might be involved, but the root filesystem is actually EXT4.

If I waited several minutes, the system eventually produced a kernel panic with a blocked task.

The visible stack trace contained MMC-related functions including:

mmc_rescan
mmc_attach_mmc
mmc_add_card
mmc_blk_probe
mmc_blk_alloc_req
disk_scan_partitions

The strange part was that if I then removed power and immediately powered the box again, the second boot normally succeeded.

So the pattern was basically:

Long power-off
    ↓
First cold boot → hangs / kernel panic

Immediate power cycle
    ↓
Second boot → works normally

3. Storage identification

After a successful boot I checked the MMC devices.

On my TX6:

mmcblk0 = microSD containing Armbian
mmcblk2 = internal eMMC

The internal eMMC identifies as:

MBG4GC

and was operating as:

MMC HS200
150 MHz
8-bit bus
1.8 V signalling

The loaded Device Tree contained:

/soc/mmc@4020000  -> microSD
/soc/mmc@4021000  -> Wi-Fi / SDIO
/soc/mmc@4022000  -> internal eMMC

4. Disabling the internal eMMC

As a test, I disabled only the internal eMMC controller in Linux while leaving the microSD controller enabled.

I created this Device Tree overlay:

/dts-v1/;
/plugin/;

/ {
    fragment@0 {
        target-path = "/soc/mmc@4022000";

        __overlay__ {
            status = "disabled";
        };
    };
};

Compiled it with:

dtc -@ -I dts -O dtb \
    -o /boot/overlay-user/tx6-no-emmc.dtbo \
    tx6-no-emmc.dts

and enabled it in:

/boot/armbianEnv.txt

with:

user_overlays=tx6-no-emmc

I tested the overlay against a temporary DTB first and confirmed:

mmc@4022000 = disabled
mmc@4020000 = okay

After rebooting, Linux no longer detected the internal eMMC, while Armbian continued running normally from the microSD.

No Android/eMMC partitions were erased or modified.

5. Results so far

Since disabling the internal eMMC, the cold-boot issue has not returned.

The box has successfully booted on the first attempt after being completely disconnected from power for:

~3 hours
overnight
~2 days

and additional cold boots have also succeeded.

Before disabling the eMMC, the first boot after a long power-off could fail repeatedly.

This makes the eMMC initialization strongly suspicious in my case.

However, I cannot say whether the root cause is:

- the eMMC hardware itself
- HS200 timing
- the H6 MMC controller
- Device Tree configuration
- kernel 6.18.x MMC behaviour
- or some interaction between these

So I would not claim that the eMMC itself is faulty.

What I can say is:

disabling mmc@4022000 has made this particular TX6 consistently boot so far.

6. Bluetooth

I also had repeated Realtek Bluetooth errors such as:

hci0 command 0xfc61 tx timeout

so I blacklisted:

hci_uart

The Bluetooth errors disappeared, but the cold-boot problem still occurred before I disabled the eMMC.

Therefore I do not currently believe Bluetooth was the cause of the boot hang.

Current setup

The system is now running as a small home server with:

Armbian / Debian 13
Linux 6.18.50-current-sunxi64
Docker
Caddy
Portainer
Tailscale

from a microSD card.

The internal eMMC is disabled only at the Linux Device Tree level.

So far the machine has been considerably more reliable with this configuration.

If it is useful for debugging, I can provide:

- photos of the kernel panic / stack trace
- the exact DT overlay
- boot logs
- the working hybrid image layout
- details of the old and new bootloader versions

I would be interested to know whether anyone else with an H6 / Tanix TX6 can reproduce the cold-boot problem with the eMMC enabled.

model name: tx 10 pro.

i want to install ARMbian on it. there is a reset button under the av port.

it has 2 gb of ram and 4 gb of rom (though the internet says 8G ram and 128G rom, also the android ui too).

i have enabled both usb debugging and oem unlocking from the android developer option menu.

the tv box can go to recovery mode using adb command. until going to the recovery mode, the adb connects perfectly but whenever it goes into recovery mode, the adb cant connect to the tv box.

it consists option for fastboot inside the recovery mode but whenever i try to apply any command (e.g. fastboot/adb) the tv box doesnt show up among the devices when the device is in recovery mode.

As there is no zip file for direct linux installation that i can use with flash from usb option.

and the reset button beneath the av port does nothing, ive tried to flash multiple ARMbian Img files using both rufus and etcher but the screen just goes black whenever i press and hold the reset button beneath the av port. there is no option to install twrp as neither adb nor fastboot can connect whenever the device is in recovery mode. what to do?

I got it from https://www.temu.com/goods.html?_bg_fs=1&goods_id=601099525915611

the specs are
CPU: Allwinner H313 Quad Core ARM Cortex A53
GPU: G31 OPenGL3.2
OS: Android 10.0
RAM: 1GB/2GB
ROM: 8GB/16GB
Wi-Fi version: 802.11b, 802.11g, 802.11n
Resolution standard: 4K
 

How would I go about installing this.

I read that bigtreetech-cb1 works, but no wifi. Is this the best option?

I bought it on tiktok shop

My dts file can be downloaded by url below
https://drive.google.com/drive/folders/1SZ6bRcxhPlqeblpoxxSb9PELKUIWABQN
OR
https://disk.yandex.com/d/tJ1GpInvt8dMUw

Tanix TX6S firmware 

https://drive.google.com/drive/folders/1CJEsZ6jdRGFC7XpOFVp8eG-DO0tbrOOb

I want to try armbian on my tvbox.

I managed to build image using orangepi-linux 4.19 and u-boot-orangepi v2018.05 sun50iw9

i copied dts from my tvbox

decompressed my stock firmware to get boot0_sdcard.fex, sys_config.fex

replaced files with these from official armbian github.

replaced orangepizero2.dts in linux 

build image without any errors

used balenaEtcher to write to sdcard

but

I am not able to get it to boot on my tvbox

any help??

thank you

Mostly just for fun. I really doubt it would be an improvement to have Linux on a projector, with most likely missing hardware decoding of codecs and other things, rather than having the original Android.

However, I haven't really found any information about the H713 chip in any of the different forums with Linux on Arm.  

Have any of you any information or think that it would be a fun project? If so, please respond.

Github

What's Working:

Ethernet

WiFi

USB

Ir-Receiver

What's Not Working:

Nothing,Right Now.

Untested:

Bluetooth (As my TV Box Doest Have Bluetooth So Its not possible for me to test)

Downloads:

Minimal Server

[I do recommended people to build/compile their own image from sources and not to trust any random build on internet. You can build your own image from my forked githubs add-tanix-tx6s-axp313 branch your own image]

In my test in CLI I found almost all the things working correctly.I will test the GUI/Desktop Interface later.

./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm

Minimal/Server

./compile.sh build BOARD=x96q-tvbox BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm

After format with esayjtag not turning on, help me,

I want to share the experience I have had bringing Armbian to life on my own Q8 tablet with an Allwinner A33 SoC.

This is not an official Armbian-supported device and it is not a universal image for every tablet sold as “Q8”. It is a community experiment based on one specific hardware revision. I am sharing it because these tablets are often discarded, even though they can still become useful Linux devices with patience, testing and good documentation.

Why I started

My goal was not to turn this tablet into a modern desktop computer. I wanted to reuse it as a small portable Linux machine for learning, lightweight entertainment, retro games and hardware experimentation.

The tablet has limited resources, especially memory, so every decision had to be made with that limitation in mind. The result is now a usable system that boots from microSD, presents a touchscreen-oriented desktop and includes a small software store built specifically for this device.

Base system

The current setup uses:

• Allwinner A33 SoC
• ARMv7 / armhf userspace
• Debian 12 Bookworm on a community-built Armbian system
• Linux 6.12.100-legacy-sunxi
• Device tree: allwinner/sun8i-a33-q8-tablet.dtb
• 1024 × 600 LCD
• Approximately 457 MiB of usable RAM
• Boot from microSD
• X11 with IceWM and a custom GTK3 interface

Hardware bring-up

Display

The 1024 × 600 LCD is working correctly. Getting a stable picture was one of the first important milestones because it gave me a reliable base for testing the rest of the hardware.

Touchscreen

The Silead touchscreen is working. I also experimented with a small uinput-based helper that can present touch input as a relative pointer when that behavior is more convenient for older applications.

Wi-Fi

The RTL8723BS Wi-Fi interface is functional. On this board it required the correct power and GPIO sequence, followed by an MMC reprobe. This was a good reminder that a driver being present is only one part of the job; the board-specific initialization also matters.

Bluetooth

Bluetooth from the same RTL8723BS module can be initialized, powered on, made visible and used for pairing. I still consider long-term reconnect behavior and compatibility with different peripherals an area that needs more testing.

Audio

Audio is working through the Allwinner A33 audio hardware using the a33-audio overlay. ALSA exposes the sun8ia33audio card, and I added touchscreen-friendly controls so the tablet can be operated without depending on a physical keyboard.

Battery

Battery information is available through the axp20x-battery driver and is integrated into the interface. Being able to see charge status directly in the shell makes the tablet much more practical as a portable device.

Accelerometer

The STK8312 accelerometer is detected and exposed through IIO. Sensor data is available, but complete and reliable automatic screen rotation is not finished yet.

Camera

The GC0308 camera is detected and I have captured test frames through the sensor → sun6i-csi-bridge → capture pipeline. This part remains experimental because format coordination and stability still need work.

Video decoding

The Cedrus driver is detected. I have not yet certified real hardware-accelerated playback in every application, so I prefer to describe this as detected rather than fully validated.

Building a usable interface

Because the screen is small and the tablet has very little RAM, I created “Q8 Shell”, a fullscreen Python/GTK3 interface designed for 1024 × 600 and touch input.

It provides large launchers, system information, Wi-Fi and Bluetooth controls, volume, weather, calendar, power options and a simple taskbar. Underneath, the system still uses X11 and IceWM, but the normal experience feels closer to a dedicated tablet interface.

I kept the project intentionally lightweight. On hardware with about 457 MiB of usable RAM, a beautiful feature is not useful if it makes the system unstable.

Tienda Q8

I also built “Tienda Q8”, a small software catalog for the tablet. It does not give the graphical application unrestricted root access. Instead, it calls a restricted helper that only accepts packages from an explicit allowlist and protects packages that are part of the working Q8 environment.

The store can:

• show whether a catalog application is installed
• install approved lightweight applications
• remove only applications managed by the store
• refresh APT package information
• display the complete APT output during an operation
• prevent multiple simultaneous operations

I tested the complete install/remove cycle with ace-of-penguins. The package installed correctly, was registered as managed by Tienda Q8, and was later removed correctly. After the round trip, the package inventory returned to the expected state and dpkg reported no pending operations.

Applications tested

Among the applications and environments I have tested are DOSBox, ScummVM, Xash3D with Half-Life/Counter-Strike content, FreeAOE, Chromium in kiosk-style use, PCManFM, MPV and other lightweight utilities.

What I learned

The most important lesson is that “Q8-A33” is not a precise hardware identity. Different tablets can share the same commercial name while using different displays, touch controllers, cameras, Wi-Fi modules or board wiring.

For that reason, I strongly recommend:

• identifying the exact board and hardware revision first
• keeping a known-good backup of the boot files and device tree
• changing one thing at a time
• checking logs after every change
• testing package operations in simulation before allowing real changes
• never assuming that a DTB or image for another Q8 variant is safe for your own tablet

I also learned that working with very limited hardware changes the meaning of optimization. Memory use, process count and startup time matter just as much as adding features.

Current status

Today the tablet boots and works as a small Linux system. Display, touch, Wi-Fi, audio and battery reporting are functional. Bluetooth works at a basic level. The accelerometer and camera are detected but still need additional work. Cedrus is present but hardware decoding still needs proper application-level validation.

The next stage is to continue reducing unnecessary packages while preserving the working kernel, device tree, firmware and hardware support. I am treating this as a gradual “Q8 Armbian Slim” phase rather than a risky one-step cleanup.

Project files and documentation

I have published the scripts, notes, configuration details and screenshots in this repository:

Q8-A33 Armbian project on GitHub

Tienda Q8 is documented here:

Tienda Q8 documentation on GitHub

I hope this experience is useful to anyone trying to recover a similar tablet. I am also interested in comparing notes with other Q8-A33 owners, especially about hardware revisions, device trees, cameras, sensors and low-memory optimization.

Thanks to the Armbian community and to everyone who has documented Allwinner hardware over the years. This project would have been much harder without that shared knowledge.

This repository contains my working port for Linux kernel 6.12 and newer, with updated mac80211/cfg80211 integration so the driver can build and run on recent Armbian systems.

The chipset is commonly used in many low-cost TV boxes and embedded devices, but the original driver only supported legacy kernels (4.4).

Now it’s functional again on modern systems, at least on my tested hardware (Allwinner H616 / X96 Q via SDIO).

Repository link:
https://github.com/cdhigh/armbian_sv6256p

I’m quite excited to finally see this old Wi-Fi chip working on a 6.x kernel 🙂
 

[    4.774151] ssv6x5x: importing configuration from /lib/firmware/ssv6x5x-wifi.cfg
[    4.778281] tu_ssv6xxx_sdio_init, probe @(____ptrval____)
[    4.779483] TU_SSV6XXX_SDIO mmc3:0001:1: Probing SDIO bus
[    4.779513] ssv6xxx_set_sdio_clk: set sdio clk 25000000Hz
[    4.799668] TU_SSV6XXX_SDIO mmc3:0001:1: vendor = 0x3030 device = 0x3030
[    4.825421] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020
[    4.849181] TU_SSV6XXX_SDIO mmc3:0001:1: dataIOPort 0x10000 regIOPort 0x10020
[    4.849530] TU_SSV6XXX_SDIO mmc3:0001:1: CHIP ID: SSV6006C0
[    4.850373] ssv6x5x ops chk: tx=1 start=1 stop=1 config=1 add_if=1 rm_if=1 conf_filter=1 wake_txq=1
[    4.850402] ssv6x5x chanctx chk: any=1 all=0 emulate=1 add=1 rm=1 chg=1 assign=0 unassign=0
[    4.850409] ssv6x5x chanctx ops set but not complete
[    4.850424] Attach SSV6006 family HAL function
[    4.858285] MAC address from e-fuse
[    4.858311] EFUSE configuration
[    4.858315] Read efuse chip identity[79000000]

ip link show:
6: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

I would like to share an updated experiment with an old MX9 Android TV Box based on the Allwinner H3.

There are older discussions in this forum about running Armbian on the MX9/H3, so I decided to revisit this hardware in 2026 using a much newer Armbian userspace and kernel.

This is NOT officially supported Armbian hardware. This is a community experiment using the Orange Pi PC platform as the base.

CURRENT HARDWARE

Device: MX9 4K TV Box
SoC: Allwinner H3
CPU: 4x ARM Cortex-A7
Architecture: ARMv7 / armhf
RAM detected: ~1 GB
Original system: Android
Boot device: microSD
Display: HDMI

CURRENT ARMBIAN SYSTEM

Image originally installed:

Armbian_community_26.11.0-trunk.19_Orangepipc_trixie_current_6.18.45_minimal.img.xz

After updating:

Kernel: Linux 6.18.48-current-sunxi
Userspace: Debian Trixie
Device-tree platform: Orange Pi PC / Allwinner H3

GRAPHICAL ENVIRONMENT

I intentionally kept the graphical environment lightweight because of the limited H3 hardware and ~1 GB RAM.

Currently installed and working:

- Xorg
- LightDM
- lightdm-gtk-greeter
- Openbox
- Tint2
- jgmenu
- PCManFM
- LXTerminal
- NetworkManager
- MPV
- RetroArch
- Firefox ESR

The desktop currently runs at:

1360x768 @ 60 Hz

This resolution provides a good compromise between usability and GPU/CPU load on the H3.

GRAPHICS

The display pipeline currently looks like:

Allwinner H3
    |
sun4i-drm
    |
/dev/dri/card0
    |
HDMI-1
    |
Xorg
    |
LightDM
    |
Openbox

The Mali-400 GPU is also detected through the Lima driver.

An interesting issue occurred while experimenting with Plymouth.

After installing Plymouth and rebuilding the initramfs, Xorg started exposing an unexpected output:

None-1 (primary)

while the real HDMI connector appeared separately.

This caused problems with the graphical login.

After removing Plymouth and rebuilding the initramfs, the correct configuration returned:

HDMI-1 connected primary 1360x768

The working DRM devices are currently associated with:

card0 -> sun4i-drm
card1 -> lima

So, at least on this particular MX9/H3 + current-sunxi configuration, I decided to leave Plymouth disabled.

CUSTOM LIGHTDM / OPENBOX ENVIRONMENT

I also created a lightweight custom login/desktop environment specifically for this MX9.

The LightDM screen uses an MX9/Armbian design and I am implementing a small script that dynamically generates system information for the login screen, including:

- CPU
- RAM
- storage
- network

The objective is to make the box behave more like a small dedicated Linux computer than an Android TV Box.

CURRENT STATUS

WORKING:

- microSD boot
- Linux 6.18.48-current-sunxi
- HDMI video
- sun4i-drm
- Lima / Mali-400 detection
- Xorg
- LightDM
- Openbox
- Ethernet
- PCManFM
- Tint2
- jgmenu
- terminal
- MPV
- graphical login

UNDER TEST:

- RetroArch / emulation performance
- HDMI audio
- hardware video acceleration
- USB devices
- temperatures under sustained load
- long-term stability
- Wi-Fi
- Bluetooth

The internal Android storage has intentionally NOT been overwritten.

For now, the complete Linux environment remains on the microSD while I test stability and hardware compatibility.

WHY THIS PROJECT?

The goal is not to pretend that an old Allwinner H3 TV Box is a modern desktop computer.

The interesting question is:

How useful can these inexpensive and often abandoned Android TV Boxes still be with a current Linux stack?

So far, the result has been surprisingly usable.

I will continue documenting the experiment and can publish a complete step-by-step installation guide, including the Openbox/LightDM configuration, graphics troubleshooting and RetroArch setup.

Thanks to the Armbian community and to the people who experimented with MX9/H3 hardware years ago.

More results coming soon.

Next steps

I plan to continue testing RetroArch performance, HDMI audio, Lima/Mali-400 acceleration, Wi-Fi, Bluetooth, USB devices, thermal behavior and long-term stability.

If anyone still has an MX9/Allwinner H3 or similar H3 TV box, I would be very interested in comparing hardware revisions, especially Wi-Fi chipsets and device-tree differences.

Hello everyone, 

I have an S96Q+ H616/H313 TV box and I am looking for a working Linux/Armbian or OpenWrt image, or the correct DTB configuration to boot. I am fully ready to test any trial images or boot configurations you send over!

**Hardware Details:**
- **Device Name:** S96Q+ (Marked as 6K on the plastic shell)
- **SoC:** Allwinner H313 / H616 Family (Reported as h313/616 in system apps)
- **GPU:** ARM Mali-G31 MP2
- **RAM/Storage:** 4GB RAM / 64GB eMMC
- **Physical Ports:** 3x USB ports, 1x Ethernet (RJ45), 1x Headphone jack, 1x DC Power

**Networking Setup:**
- **Wi-Fi:** Confirmed to be standard Single-band 2.4GHz Wi-Fi only. The exact chip model is unverified from the shell (likely XR829 or RTL8189 based on common configurations).
- **Bluetooth:** Broken/Non-functional in original OS (the physical board likely lacks a Bluetooth controller entirely).

Please send over any compatible community builds, bootloader setups, or DTB configurations that fit this single-band H616 layout and I will flash them to test! Thank you!

Forgive me but I am a novice in Armbian.

What I would like to do is install armbian on the T95Max box I have purchased.

I have attached a pic of the Box and it's specs.

I have tried to "upgrade" using the SD method but couldn't make that recognise the SD card even with the original firmware "T95max-H618-A9.img" that I sourced using Google.

I have also tried to get the T95 Max recognised via the USB method but the box wasn't even recognised using that method either.

I used the "Universal_ADB_Driver_v6.0" drivers but that made no difference.

If I could get the correct method sorted and an upgradeable firmware for Ambian that would be a great help.

I can compile the firmware if needed but I am unsure of what Ambian image would be the best starting point.

Any help would be gratefully received.

TIA

Steps:

1. on android become developer

2. enable oem bootloader unlocking in developer options

3. adb reboot bootloader

4. fastboot oem unlock

5. reboot, the system will be wiped clean

6. install Magisk apk from github releases

7. get Teclast T60 AI firmware from their site it contains Firmware.img

8. ./sunxi-fw extract -n "wty:init_boot.fex" -o stock_init_boot.img Firmware.img

9. transfer to device and patch with Magisk app

10. adb reboot bootloader

11. fastboot flash init_boot_a /path/to/magisk_patched_init_boot.img
12. fastboot flash init_boot_b /path/to/magisk_patched_init_boot.img

13. fastboot reboot

Now do people know about what needs to be done to get xfce with armbian booted on this apparatus?? I think I need better AI agent for this than Deepseek as it is a bit sloppy as usual, Gemini Pro 2.5+ or some Claude probably. I ended up battling with this for a few days.

The Problem

The Physical Reset Button is Broken: The recovery button inside the AV port does not work at all. It does not feel like it's clicking, and holding it while powering on does absolutely nothing.

The Terminal Quirks: Because I can't use the hardware button, I am trying to trigger the boot via software from inside Android using a terminal app.

Typing reboot update just reboots the box straight back into standard Android.

Interestingly, if I type a typo variant like reboot updare, the box crashes its regular boot sequence, skips Android, and attempts to scan the USB ports. However, it always throws a firmware error or goes to a black screen—it never successfully loads Linux.

My Exact Device Specs

Box Model: X96Q Pro

Processor (SoC): Allwinner H313 (sun50i-h313)

CPU: Quad-Core ARM Cortex-A53

GPU: Mali-G31 MP2

RAM/Storage: 1GB or 2GB DDR3 / 8GB or 16GB eMMC

Stock OS: Android 10

Ports Used: I have tried flashing images to a USB drive plugged into the data-capable USB-2 port.

What I Have Tried So Far

Flashed various community images using BalenaEtcher/Rufus.

Checked the armbianEnv.txt file on the flashed image. I noticed one image had overlay_prefix=sun50i-h616. I manually edited it to sun50i-h313 and added fdtfile=sun50i-h313-x96q.dtb, but the box still refuses to boot.

Could anyone point me to the exact working Armbian image, specific DTB file, or a known u-boot bootloader workaround that actually works for this specific H313 motherboard revision?

I’m trying to flash a firmware on a generic Android TV Box and I’m stuck at a hardware/bootloader compatibility issue.

Device technical details:
- SoC: Allwinner H618
- Board / PCB: FX-H618-D4_V10
- RAM: 4GB DDR4
- Storage: eMMC (unknown size, likely 32GB)
- USB FEL ID: VID_1F3A PID_EFE8
- Original OS: BigdroidOS (Android generic)
- Commercial name: Transpeed 8K618-T

Current situation:
- Device enters FEL mode correctly (VID_1F3A PID_EFE8)
- PhoenixSuit detects the device but firmware upgrade hangs at “Beginning Firmware Upgrade”
- Tried multiple PCs (Windows 10 and 11), different USB ports and cables
- Allwinner FEL driver installed correctly
- SD card flashing with PhoenixCard (Startup mode) is ignored, device boots normally to Android
- Reset timing variations tested (short press / long press / no reset)

Tested firmware:
- sbx_transpeed_h618_atv_12_11.img
- H618.apollo-p3.T-H618_100M_12_FD650.2023.09.13.1720.img

Both firmwares show similar behavior (FEL detected but no successful flash).

I believe the issue is bootloader / DDR4 initialization mismatch.
I’m specifically looking for:
- A firmware confirmed to work with board FX-H618-D4_V10
- Or the original BigdroidOS firmware dump for this board
- Or confirmation whether this board requires a specific boot0/boot1

Any help, working firmware, or dump from the same board would be greatly appreciated.

Thank you!
 

Allwinner H618, FX-H618, DDR4, PhoenixSuit, FEL, Transpeed
 

Armbian-unofficial_26.02.0-trunk_Mxqpro-h313_trixie_current_6.12.74_cinnamon_desktop.img.xz

Needed: a way to add a secure patch to the referred image (may be building through git).

Thank you.

This is the specs:

Model on case: MX9PRO 5G ONLY 8K

Board Model: Hibox 1344_v1.0 (IK3160805)

Date Model: 2020. 12. 08

RAM: physical 1G (On the android dectets 970 MB)

SOC: Allwinner H313/H616

Device space: 8

GB

I am looking for help to boot Armbian on a generic TV Box sold as "MXQ Pro 4K 5G". I have tried multiple images (including official and community builds from sicXnull), but I only get a black screen or signal loss immediately after the boot attempt.

Device Specifications:

Model on case: MXQ Pro 4K 5G

Board ID: IK316Q-EMCP_V4.1

SoC: Allwinner H313 (identified as sun50iw9p1 in Android)

RAM: 1GB (Single chip configuration)

Storage: 8GB eMMC

Current Status: I am able to boot into the stock Android. To attempt the Armbian boot, I am using the reboot update command from a terminal emulator within Android.

The issue: Upon executing the reboot command, the Android system shuts down, the display signal cuts off (or stays black), and the device never initializes Armbian (no HDMI output, no LEDs blinking differently).

What I have tried:

Builds from sicXnull repository (Kernel 6.x).

Ophub community builds (H616/H313 variants).

I have updated the extlinux.conf / uEnv.txt to point to the sun50i-h313-x96-q-lpddr3.dtb (and others like x96-mate), but the result is always the same failure to initialize.

Has anyone successfully booted this specific board revision (IK316Q_V4.1)? Is there a specific bootloader argument or a different DTB required for this MXQ clone?

Photos of the board are attached. Thanks!

I'm trying to get Armbian fully working on an MX10 F1 TV Box (Allwinner H313, 2GB LPDDR3, 16GB eMMC).

The box boots using the X96Q LPDDR3 DTB (X96Q TV-Box LPDDR3), but several onboard devices are not working:

❌ Ethernet

❌ Built-in WiFi

❌ Bluetooth

❌ CPU frequency scaling

Working:

✅HDMI

✅GPU (Panfrost / OpenGL ES 3.1)

✅USB

✅SD card

✅eMMC

I've extracted the original Android DTB and DTS, and I'm attaching them together with the Armbian dmesg.

Could someone familiar with Allwinner Device Trees help identify what is missing or needs to be changed to create proper support for this board?

Thanks!

dmesg.txt mx10-f1-android.dtb mx10-f1-android.dts

i'm looking to boot in an armbian bookworm by sicxnull on my mxq pro 4k 5g, i checked the aida64, it showed the allwinner h313, i tried the toothpick method to the recovery menu (which have a boot option?) i'm novice to android 😕

by the way here are the images of the tv box pcb:

limea1000 boot ok

pcduino1 ok

cubieboard ok

olimex a10 lime stuck at boot os stage, same with official debian 3.4 kernel images of olimex

enabled video output for desktop environment. It boot but will take a lot of time to finish 

CPU: Allwinner H616

RAM: 4GB

ROM: 32GB

Board: AXP313A V3.0

The box was freezing after boot, so I tried to reflash the firmware using PhoenixCard / suit.
 

What I’ve Tried So Far:

Downloaded and flashed T95-H616-A27.img & T95-H616-A29.img through FEL mode and Flashing completed successfully but the box only shows a black screen on both HDMI and the small front panel screen.

Tried other firmware images labeled for T95 Max H616 AXP313A

Tried re-burning the SD using different cards and readers

I found a working Armbian img that worked from SD card:

https://github.com/NickAlilovic/build/releases/download/v20240716/Armbian-20240716-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_Secure_Boot.img.tar.xz

I want to restore the TV box to a working firmware (Android 10 or 12) if possible. And is there any method to revive bootloader if it's corrupted

Any working image file would be a huge help.
 

Board Image attached:

If you have any information on how I can install Armbian, or any other Linux distro on this board, please let me know.

Note that the device specifications have been checked and I am sure that these are the specifications.
The GitHub repository for this project is: GitHub_Repository (ARMX9ProMax_Project)

U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200)
DRAM:This DRAM setup is currently not supported.

resetting ...
[70]HELLO! BOOT0 is starting!
[73]BOOT0 commit : 803d783
[75]set pll start
[78]periph0 has been enabled
[81]set pll end
[83]unknow PMU
[84]unknow PMU
[86]PMU: AXP1530
[88]dram return write ok
[90]board init ok
[92]DRAM BOOT DRIVE INFO: V0.645
[96]the chip id is 0x5d00
[98]chip id check OK
[103]DRAM_VCC set to 1500 mv
[106]DRAM CLK =600 MHZ
[108]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[116]Actual DRAM SIZE =1024 M
[118]DRAM SIZE =1024 MBytes, para1 = 30eb, para2 = 4000000, dram_tpr13 = 6041
[132]DRAM simple test OK.
[134]rtc standby flag is 0x0, super standby flag is 0x0
[140]dram size =1024
[143]card no is 2
[145]sdcard 2 line count 8
[147][mmc]: mmc driver ver 2020-09-10 15:32
[157][mmc]: Wrong media type 0x0, but host sdc2, try mmc first
[163][mmc]: ***Try MMC card 2***
[202][mmc]: RMCA OK!
[204][mmc]: bias 4
[207][mmc]: MMC 5.0
[209][mmc]: HSSDR52/SDR25 8 bit
[212][mmc]: 50000000 Hz
[214][mmc]: 7456 MB
[216][mmc]: ***SD/MMC 2 init OK!!!***
[291]Loading boot-pkg Succeed(index=0).
[294]Entry_name        = u-boot
[304]Entry_name        = monitor
[307]Entry_name        = dtbo
[310]Entry_name        = dtb
[314]tunning data addr:0x4a0003e8
[317]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):a0d3abd
NOTICE:  BL3-1: Built : 17:32:02, 2020-10-20
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05 (Feb 15 2023 - 17:22:04 +0800) Allwinner Technology

[00.391]CPU:   Allwinner Family
[00.394]Model: sun50iw9
I2C:   ready
[00.398]DRAM:  1 GiB
[00.401]Relocation Offset is: 35ebf000
[00.442]secure enable bit: 0
[00.444]pmu_axp152_probe pmic_bus_read fail
[00.448]PMU: AXP1530
[00.454]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.462]drv_disp_init
[00.492]__clk_enable: clk is null.
[00.497]drv_disp_init finish
[00.500]gic: sec monitor mode
[00.522]flash init start
[00.524]workmode = 0,storage type = 2
[00.528]MMC:     2
[00.529][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.535][mmc]: get sdc_type fail and use default host:tm4.
[00.546][mmc]: SUNXI SDMMC Controller Version:0x40502
[00.590][mmc]: Best spd md: 4-HS400, freq: 3-100000000, Bus width: 8
[00.596]sunxi flash init ok
[00.600]Loading Environment from SUNXI_FLASH... OK
[00.609]usb burn from boot
delay time 0
weak:otg_phy_config
[00.623]usb prepare ok
[01.426]overtime
[01.430]do_burn_from_boot usb : no usb exist
[01.434]boot_gui_init:start
FAT: Misaligned buffer address (7be7be58)
32 bytes read in 4 ms (7.8 KiB/s)
tcon_de_attach:de=0,tcon=2[01.567]boot_gui_init:finish
[01.570]bmp_name=bootlogo.bmp
2764854 bytes read in 40 ms (65.9 MiB/s)
[01.633]update dts
** Unrecognized filesystem type **
[01.642]load file(ULI/factory/rootwait init.txt) error.
** Unrecognized filesystem type **
[01.655]load file(ULI/factory/snum.txt) error.
[01.659]name in map mac
** Unrecognized filesystem type **
[01.668]load file(ULI/factory/wifi_mac.txt) error.
** Unrecognized filesystem type **
[01.680]load file(ULI/factory/bt_mac.txt) error.
** Unrecognized filesystem type **
[01.692]load file(ULI/factory/selinux.txt) error.
** Unrecognized filesystem type **
[01.704]load file(ULI/factory/specialstr.txt) error.
[01.713]update part info
[01.738]update bootcmd
[01.740]No ethernet found.
Hit any key to stop autoboot:  0
[02.050]Starting kernel ...

[02.053][mmc]: mmc exit start
[02.101][mmc]: mmc 2 exit ok
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.170 (akrd6@R740XD) (gcc version 5.3.1 20160412(Linaro GCC 5.3-2016.05) ) #80 SMP PREEMPT Wed Feb 15 17:22:30 CST 2023
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
[    0.000000] bootconsole [earlycon0] enabled
[    0.027874] BOOTEVENT:        27.858249: ON
[    0.242175] sunxi_i2c_probe()2209 - [i2c3] warning: failed to get regulator d
[    0.243164] sunxi_i2c_probe()2209 - [i2c5] warning: failed to get regulator d
[    0.244517] axp2101-regulator axp2101-regulator.0: Setting DCDC frequency fo unsupported AXP variant
[    0.244601] axp2101-regulator axp2101-regulator.0: Error setting dcdc frequecy: -22
[    0.279245] [ac200] get ave_regulator_name failed!
[    0.279751] [ac200] pwm enable
[    0.363211] gpio_pin_4(229) gpio_request fail
[ ▒[    0.369727] uart uart1: get regulator failed
[    0.402346] [NAND][NE] Not found valid nand node on dts
[    0.411005] sunxi-wlan soc@03000000:wlan: get gpio chip_en failed
[    0.417894] sunxi-wlan soc@03000000:wlan: get gpio power_en failed
[    0.550010] hci: request ohci1-controller gpio:232
[    0.742282] axp2101_pek: axp2101-pek can not register without irq
[    0.752785] sunxi_ir_startup: get ir protocol failed
[    0.761135] VE: get debugfs_mpp_root is NULL, please check mpp
[    0.761135]
[    0.769395] VE: sunxi ve debug register driver failed!
[    0.769395]
[    0.784659] mmc:failed to get gpios
[    0.865627] mmc:failed to get gpios
[    0.901895] FD655: ==fd655_driver_probe====================
[    0.908284] FD655: : (null)
[    0.909038] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !!
[    0.912260] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !!
[    0.926757] FD655: : (null)
[    0.929915] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !!
[    0.935814] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !!
[    0.941713] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !!
[    0.947606] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !!
[    0.953859] FD655: register_fd655_driver: Successed to add fd655  module
[    0.973520] failed get gpio-spdif gpio from dts,spdif_gpio:-2
[    0.983217] [audio-codec]dachpf_cfg configurations missing or invalid.
[    0.990865] lineout_vol:26, linein_gain:3, fmin_gain:3, digital_vol:0, adcdr_cfg:0, adchpf_cfg:0, dacdrc_cfg:0, dachpf_cfg:0, ramp_func_used:1, pa_msleep_tme:160, pa_ctl_level:0, gpio-spk:0
[    1.014903] sndhdmi sndhdmi: ASoC: CPU DAI (null) not registered
[    1.021698] sndhdmi sndhdmi: snd_soc_register_card() failed: -517
[    1.035293] sunxi-ahub-cpudai 5097000.cpudai3-controller: ahub cpudai id invlid
[    1.068733] ERROR: pinctrl_get for HDMI2.0 DDC fail
[    1.078344] tv_probe()1435 - of_property_read_string tv_power failed!
[    1.174637] cpu cpu1: opp_list_debug_create_link: Failed to create link
[    1.182156] cpu cpu1: _add_opp_dev: Failed to register opp debugfs (-12)
[    1.189771] cpu cpu2: opp_list_debug_create_link: Failed to create link
[    1.197234] cpu cpu2: _add_opp_dev: Failed to register opp debugfs (-12)
[    1.204828] cpu cpu3: opp_list_debug_create_link: Failed to create link
[    1.212279] cpu cpu3: _add_opp_dev: Failed to register opp debugfs (-12)
[    1.684491] selinux: avc:  denied  { set } for  scontext=u:r:vendor_init:s0 context=u:object_r:default_prop:s0 tclass=property_service permissive=1
[    1.684491]
[    1.702686] selinux: avc:  denied  { set } for  scontext=u:r:vendor_init:s0 context=u:object_r:dalvik_prop:s0 tclass=property_service permissive=1
[    1.702686]
[    2.576915] FAT-fs (mmcblk0p15): bogus number of reserved sectors
console:/ $ [    8.720978] apexd: Failed to walk /product/apex : Can't open /prduct/apex for reading : No such file or directory
^C
130|console:/ $ [   22.711942] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !!
[   22.913822] SSV6XXX_SDIO mmc2:0001:1: vendor = 0x3030 device = 0x3030
[   22.947618] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020
[   22.958352] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RE RCE !!
[   23.030814] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020
[   23.057388] SSV6XXX HCI TX Task started.
[   23.135876] Enable HCI TX aggregation
[   24.042450] SSV WLAN driver SSV6006C: Set new macaddr
[   24.060821] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e4 of type 2 is added.
[   25.361805] SSV WLAN driver SSV6006C: Set new macaddr
[   25.386662] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e5 of type 2 is added.
[   27.173711] selinux: avc:  denied  { set } for property=sys.config.rootservice pid=2978 uid=0 gid=0 scontext=u:r:rootservice:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=1
[   27.173711]
[   27.207603] audit: rate limit exceeded
[   30.214797] apexd: Can't open /product/apex for reading : No such file or directory
U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200)
/system/bin/sh: syntax error: unexpected '('
1|console:/ $ DRAM:This DRAM setup is currently not supported.
/system/bin/sh: DRAM:This: inaccessible or not found
127|console:/ $ [   34.750480] selinux: avc:  denied  { set } for property=supolicy.loaded pid=3902 uid=0 gid=0 scontext=u:r:toolbox:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=1
[   34.750480]
U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200)
/system/bin/sh: syntax error: unexpected '('
1|console:/ $ DRAM:This DRAM setup is currently not supported.
/system/bin/sh: DRAM:This: inaccessible or not found
127|console:/ $

I am looking for the original firmware for my Q1 TV Box.

Board information:

Board: Q1-V4.0

CPU: Allwinner H313

RAM/Storage: 2GB + 16GB eMCP (Foresee)

WiFi: SV6256P

Sticker on PCB:

Q1-H313-111-ATV-8800

XH20251014024

I have already tried searching on Needrom, but the available firmware is for Q1-V3.0 / A32 / A33 boards, and I am not sure it is compatible with my Q1-V4.0 board.

Does anyone have the original firmware (.img) or know where I can download it?

Thank you very much.

board: IK316Q-EMCP_V4.1

i belive it's apart of the h6 familly, correct me if i'm wrong. Well, i'm trying to boot from a sd card, but it doesn't work, i tried the toothpick methof but it still don't work. I tried with the sd and without the sd card, but it doesn't enter into android recovery mode, the only way i can get into fastboot is by using adb, however if i try to enter the bootloader by selecting it on the andorid recovery or fastboot menu it just crashes. Do you guys know any way of how can i proceed? Will be better if i change the firmware? Should i just buy ice cream and cry in the shower? I need help, the img i'm using is Armbian_community_26.2.0-trunk.886_X96q_trixie_current_6.18.28_minimal.img, because i believe it's the most compatible to my board. Feel free to ask any questions.

I have an Allwinner H313 (confirmed) box that I want to to use as a basic Samba server.

 CPU:Allwinner H313Quad Core ARM Cortex A53 
 GPU:Mali-G31 OPenGL ES3.2
 Memory:2GB
 Flash:16GB
 OS:Android 10.0

The actual firmware is a secure image and, no matter what procedure I do, I can't  load any other image but

the secure one.

Debugging shows that 'fastbootd' has the "secure" flag set.

My intention is to create a  basic secure arm64 Debian image but I am having a hard time in doing so.

Any ideas (specific Wiki, procedures) on how to create the secure image or "reset" the "secure" flag will be very appreciated.

Thanks in advance. 

Has anyone found an Armbian image that works properly with the Tanix TX6-A, including Wi-Fi support?

Driver was installed successfully , but what i did that was not mentioned on the tutorial was plugging the usb cable  after the power cable whipe holding the reset button as it didnt detect it via usb cable alone . Any way to unbrick ? Anyhelp would be appreciated 

Can I install armbialn bookworm on  x96qpro+ h728?

I know there are other versions without UART ports, mine was lucky enough to have them. 

To build this image (adjust the compile command to your liking)
 

git clone https://github.com/sicXnull/armbian-build
cd armbian-build
git checkout MXQ-PRO
./compile.sh build BOARD=mxqpro-h313 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=cinnamon DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base EXPERT=yes KERNEL_BTF=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm

Prebuilt Images

Armbian-unofficial_26.02.0-trunk_Mxqpro_bookworm_current_6.12.65_cinnamon_desktop.img

Armbian-unofficial_26.02.0-trunk_Mxqpro_bookworm_current_6.12.65_minimal.img


Unfortunately this board was already flashed with MiniArch by the time i got it, so i was unable to get the original DTB. Therefore, wifi does not work

Is someone able to get the DTB from this board so we can get wifi working?

I noticed that x96q lpddr v1.3 is now an official (or something close to that) release, as it appears on the main page when searching. I used to use @sicxnull fork but now I have the impression that his changes were incorporated and he is the official maintainer of this device. I installed the Armbian 26.02 in an SD card and tested it in my X96Q lpddr v1.3 device and it works great!

The problem is when I installed it to the internal eMMC, it will not boot anymore. I have the serial cable attached and I can see that very very early in the boot process u-boot cannot read from flash and the boot hangs.

I know this has been discussed to some extent in another thread but I wanted to start fresh on this one since now we're talking about the Armbian official release and not the fork anymore. My intent with this thread is focus exclusively on fixing eMMC on the official release.

My tests:

Test 1

Download latest release, from here, more specifically this one. Direct link to the image here (name: Armbian_community_26.2.0-trunk.858_X96q_resolute_current_6.18.27_xfce_desktop.img.xz). Write to SD card using balena etcher, boot in my x96q device. It works well, boots through the initialization process, create user account, etc. The, run armbian-install and install it to internal eMMC. Remove SD card. Reboot. It will not boot, with the following error:

Trying to boot from MMC2
MMC Device 1 not found
spl: could not find mmc device 1. error: -19
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

Booting from SD card again, re-running the installer and forcing to update the eMMC bootloader does not help.

Test 2

I swapped only u-boot for the one from miniarch/minimyth2 project, compiled for the same hardware.

Miniarch project can be found here. An image that works on this hardware (in my specific device) can be found here, more specifically this one. This image works well, and it also works well when installed to eMMC. The reason I don't use it is that I prefer Ubuntu over Arch, which I can get with Armbian instead.

Download that image, and extract the file u-boot-sunxi-with-spl.bin from the first partition of that image. I used unxz + losetup + loopback mount the image's first partition in linux, but it may be easier for you to just write that image to an SD card, then copy the file from it. It is in the first partition in the path /bootloader/u-boot-sunxi-with-spl.bin. Copy it to a usb stick and plug it into the x96q device or scp it directly.

Now, boot the x96q with the SD card, go through all initial setup. Run armbian-install, and install it to eMMC. Finish the installer (quit).

Copy the file you extracted from miniarch to the booted system in x96q (using the usb stick or scp'ing it directly). Overwrite the file with the same name at /usr/lib/linux-u-boot-current-x96q/u-boot-sunxi-with-spl.bin with the new one.

Run the armbian-install command again, this time chose to update the bootloader in the eMMC.

Mount the eMMC temporarily at /mnt and edit the /mnt/boot/armbianEnv.txt file, add this line: 

fdtfile=allwinner/sun50i-h313-x96q-lpddr3.dtb

This is because the hardcoded path for the DTD file in miniarch is different from the one from armbian, so you need to override it. It can also be done in realtime on the u-boot boot prompt if you have serial cable attached.

Reboot, remove the SD card and let it boot from the eMMC. It should work, now you have a working Armbian on the eMMC.

This will get undone if the bootloader is updated again with the original one (and is not meant as a permanent fix).

Thoughts

Miniarch uses 2025.04 u-boot while Armbian x96q board is using 2024.01 but I'm not sure this is really relevant. My guess is that the difference is in some of the patches they apply and not in the improvements of this new version of u-boot itself. But I could be wrong.

You can find the list of patches that miniarch applies over to stock u-boot here. Many of those patches do not exist in Armbian. I wonder if it is any of those that is making the difference.

Question to @sicxnull: do you have a good idea of what is going on and have any direction for further testing? I wanted to ask before I start applying the extra patches one by one, that would take quite some time.

Thanks!

dumped dtb and boot.img and bootloader.img: https://we.tl/t-xp8WGoP80f

bootik316.txt

I leave my pictures below, and my specs:

CPU: Alwinner H313
RAM: 1GB
ROM: 8GB
PCB: Z01S-v13.3, 2025.05.20
OS: Android 7-8 ish

 

I’ve cross-flashed a MXQ 4K 5G (Allwinner sun8iw7p1 / H3) firmware onto a different H3-based TV box. Everything works surprisingly well, except for the IR Power-On/Wakeup.

Since the hardware is different, my box's IR receiver is sending a scancode that the MXQ firmware doesn't recognize as the "Wakeup" key.

Because this is an Allwinner (sunxi) build and not Rockchip, I know I can't just edit a remote.conf file in the system partition to fix the cold-boot power button.

My questions:

Where exactly is the Hardcoded IR Wakeup/Power-on scancode stored in these Phoenix-style Allwinner images?

Is it buried in the Device Tree Blob (DTB) under a specific IR controller node, or is it hardcoded in the U-Boot/SPL?

If I unpack the boot.img or kernel, what hex patterns should I search for to find the Power-key scancode table?

If anyone has experience patching the primary boot scancode for sun8i chips, I’d love some guidance on which partition/file to hex-edit.

Thanks!

I have a TV Box labeled “In Xplus”, running on an Allwinner H313 (most likely a generic/rebranded device).

I was able to install Linux on it using Armbian 26.2.0-trunk (Trixie). The system boots normally, but I’m facing network issues:

- Wi-Fi is not working (no interface detected)
- Ethernet is also not working (only interface is lo)

So basically, the system runs fine, but I have no network connectivity at all.

My questions:
- Is this a current limitation of Armbian support for the H313?
- Is there any specific DTB or patch that could fix Wi-Fi/Ethernet?
- Is there a more stable Armbian version or another distro with better support?
- Has anyone managed to get networking working on this chip?

Any help or shared experience would be greatly appreciated.

Thanks!

Q17 android tv box = Tanix TX11 android tv box = Q1 android tv box        .... Works

but ≠ X96Q android tv box      AND     ≠ Tanix TX1 android tv box     .... It doesn't work

current system firmware: Android 14

specs:

- ARM Cortex-A53 - 32 bit

- Mali-G31

- Allwinner H313

- arm,sun50iw9p1

4 GB RAM DDR3

32 GB HDD

model = "sun50iw9";
    compatible = "arm,sun50iw9p1";

Anything that does not work is not booted by the device

Does anyone have any advice on how to get Armbian running on this device. 

I am comeplety new to Armbian. Is there a generic Allwinner H6 image that I need to modify?

Any advice pls?

Thanks

I have big problem 

I have tv box Transpeed-H616_

I update with orange pi 

But i can't back to old firmware 

https://imgur.com/a/AjGX6Fv

I have installed linux-headers-edge-sunxi64_25.05.0-trunk_arm64__6.12.11 from the same repository.

I'm trying to build a custom module to get the LCD working but I keep coming up against a Exec Format Error which implies a mismatch between the build version and the installed version. But I can't find the cause. I have been following the build instructions for tm16xx-display which hasn't been a smooth process. I've had to remove some forward slashes in the Makefile so it would find the drivers/auxdisplay folder and the line-display.mod.c file it created had entries with multiple double quotes that caused errors. I had to change ""LINEDISP"" to "'LINEDISP'" before it would build. I should also mention I have previously tried OpenVFD and come up with the exact same issue so I don't think it's related to tm16xx.

uname - r

6.12.11-edge-sunxi64

Vermagic of the module

6.12.11-edge-sunxi64 SMP preempt mod_unload aarch64

uname -a

Linux x98h 6.12.11-edge-sunxi64 #1 SMP PREEMPT Thu Jan 23 11:23:05 EST 2025 aarch64 GNU/LINUX

I have little experience with building things in Linux. Am I missing something simple?

Is "PREEMPT" listed in all caps in uname -a an issue when the vermagic line is lower case?

What about mod_unload?

Any other ideas? I've been googling all day and got nowhere. Most results show different version between uname and vermagic which isn't the case here as far as I can tell. I guess I just need to know if it's possible to build custom modules with armbian images or if it's something that just doesn't work and I should forget about it.

Thanks.

T95zPlus-h618

eth ---ok

usb0&1 ---ok

wifi&bt ---ok

3.5mm headphone ---ok

hdmi&hdmi codec ---ok

ir ---ok

https://github.com/LYU4662/t95zplus-h618-build.git

https://github.com/paolosabatino/ssv6x5x/tree/master

or build from old kernel 4.4.x

I have a Multilaser tablet with the Allwinner A50 chip and I wanted to compile a DTB file for it, so I could boot Armbian, but I haven't found anything on the internet about PIN MAP or anyone who has worked with this chip.

Also, it already has an unlocked bootloader.


 

I really wanted to do a project with this tablet, as I'm a student at the Federal Institute and it would be a great project!

I've searched a lot and only found images compatible up to version V4.0. Since mine is V4.1, I haven't been able to get a successful boot from the SD card.

If anyone has any tips, a working image, or experience with this specific model, I’d really appreciate the help!

I'm trying to install Armbian on my Worldchip K16 tablet and would appreciate guidance on compatibility and installation steps.

Device Specifications:

· Model: Worldchip K16
· SoC: Allwinner sun50iw10p1 (likely A64/H5 variant)
· CPU: Quad-core Cortex-A53 (ARMv8 64-bit)
· Current OS: Android 11
· Architecture: aarch64 (ARMv8l)
· GPU: Mali-400MP2 (typical for this SoC)
· RAM: Unknown (estimated 2-4GB based on similar devices)
· Storage: Unknown (likely 32-64GB eMMC)

Boot it using the method `sudo sunxi-fel -v -p uboot u-boot-sunxi-with-spl.bin` in the terminal.

TV BOX Model: T95mini | R69 - EMCP V2.0 - H3 Allwinner.

The screenshots below show the screen freezing. I'm a total noob, guys, if you could please explain the procedures, indicate what needs to be done to make it work. Thanks in advance

libretech_all_h3_cc_h3_mem_336 - u-boot-sunxi-with-spl.bin

CPU/Chip/Idk: sun8iw7p1

PCB Model(?): H3 Q44 V4.0
Uname -a: Linux orangepipcplus 6.12.58-current-sunxi #1 SMP Thu Nov 13 20:34:41 UTC 2025 armv7l GNU/Linux

dmesg | grep -i mmc

[    0.000000] Kernel command line: root=UUID=cf60c629-17b3-4fb8-91bb-24bd021f8c6b rootwait rootfstype=ext4 splash=verbose console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=def8ba6d-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory
[    0.000000] Unknown kernel command line parameters "splash=verbose ubootpart=def8ba6d-01 ubootsource=mmc sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory", will be passed to user space.
[    4.995824] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[    5.019105] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB
[    5.031030] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB
[    5.048053] mmc2: Failed to initialize a non-removable card
[    5.063249] mmc0: host does not support reading read-only switch, assuming write-enable
[    5.067129] mmc0: new high speed SDXC card at address aaaa
[    5.071189] mmcblk0: mmc0:aaaa SC64G 59.5 GiB
[    5.080563]  mmcblk0: p1
[    5.316321]     ubootsource=mmc
[    7.603641] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq
[    7.635175] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB
[    7.687081] mmc1: new high speed SDIO card at address 0001
[    8.364751] EXT4-fs (mmcblk0p1): mounted filesystem cf60c629-17b3-4fb8-91bb-24bd021f8c6b ro with writeback data mode. Quota mode: none.
[   14.091111] EXT4-fs (mmcblk0p1): re-mounted cf60c629-17b3-4fb8-91bb-24bd021f8c6b r/w.

dmesg | grep -i mmc2
 

[    5.048053] mmc2: Failed to initialize a non-removable card

I also extracted a DTB file and DTS file from the android of the TV box, if that is useful (I used AI for that, and dont really know if they are useful)

Thanks.

dts.txt

After compiling a build for my TV box and burn it to the SD boot process stuck to 

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems

Can someone help please solving the problem?

I've installed and run Armbian_community_25.11.0-trunk.437_Tanix-tx6_trixie_current_6.12.47_minimal

Since my Tanix TX 6 is running pretty hot in my opinion I want to reduce the operating frequency. 

Please help me with some instructions how to do so, since I couldn't find any.

Thank you in advance.

U-Boot SPL 2024.01_armbian-2024.01-S866c-P4a40-H8869-Vad24-Bbf55-R448a (Nov 15 2025 - 02:36:36 +0000)
This DRAM setup is currently not supported.

How do I change the DRAM (and possibly other) configuration U-Boot is built with?

I'll be quite frank: Quite annoyed by this whole process. The build process for both Armbian and U-Boot has exhausted my patience and I'm very much not in the mood for digging through (often hard to find) documentation. (Like why is there no standard for adding a board?)

Here's the UART boot log of the device:x96q_boot_log.cap

Oh and I almost forgot! The stock firmware! https://archive.org/details/x96q_h313_mmcblk0.img.7z

Something about extracting "device trees" or something? Honestly I couldn't locate the copy of u-boot in there, but I'm probably doing something wrong there. I'm sure someone WAY smarter then me in this stuff could probably figure it out.

I have a T95MAX ver 3 board with H616 / AXP313 / 4Gb RAM.
I've compiled an Armbian from Nick repo (https://github.com/NickAlilovic/build), branch v20251014 for Transpeed-8k618 with a little defconfig patch for TOC0 and DCDC3 voltage = 1.5V (extracted from Android native image DTB).

CONFIG_AXP_DCDC3_VOLT=1500
CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y

Image booting ok, but first UBoot stage found 4Gb and second stage found only 2Gb. Someone have any ideas for make 2nd stage and kernel detect full memory?

U-Boot SPL 2025.04-armbian-2025.04-S3482-Pfbbd-H8869-V9b5f-Bb703-R448a-dirty (Nov 13 2025 - 13:20:15 +0000)
DRAM:testing 32-bit width, rank = 2
read calibration failed!
testing 32-bit width, rank = 1
Store cfg
1st writing pattern
detected 11 columns
restore cfg
reconfigure for all active rows
store cfg
2nd writing pattern
detecting row address bits
detected 16 rows
restoring cfg
end of auto detect dram size
MBUS port 0 cfg0 0100000d cfg1 00640080
MBUS port 1 cfg0 06000009 cfg1 01000578
MBUS port 2 cfg0 0200000d cfg1 00600100
MBUS port 3 cfg0 01000009 cfg1 00500064
MBUS port 4 cfg0 20000209 cfg1 1388157c
MBUS port 5 cfg0 00640209 cfg1 00200040
MBUS port 6 cfg0 00640209 cfg1 00200040
MBUS port 8 cfg0 01000009 cfg1 00400080
MBUS port 11 cfg0 01000009 cfg1 00640080
MBUS port 14 cfg0 04000009 cfg1 00400100
MBUS port 16 cfg0 2000060d cfg1 09600af0
MBUS port 21 cfg0 0800060d cfg1 02000300
MBUS port 22 cfg0 01000009 cfg1 00640080
MBUS port 25 cfg0 0064000f cfg1 00200040
MBUS port 26 cfg0 20000209 cfg1 1388157c
MBUS port 37 cfg0 01000009 cfg1 00400080
MBUS port 38 cfg0 00640209 cfg1 00200040
MBUS port 39 cfg0 20000209 cfg1 1388157c
MBUS port 40 cfg0 00640209 cfg1 00200040
=> md.l 0x047FA000 
047fa000: 80000000 000009f4 0e40ff00 0000018f
047fa010: 00000010 00103040 00000000 00000000
047fa020: ffffffff 000007ff 0000ffff 00000000
...
04800b40: 00000000 00000000 00000000 00000000
04800b50: 00000000 00000000 00000000 00000000
04800b60: 00000000 00000000 00000000 00000000
04800b70: 00000000 00000000 00000000 00000000
 4096 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.13.0(debug):armbian
NOTICE:  BL31: Built : 10:39:26, Nov 13 2025
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a0a4218, model: Transpeed 8K618-T
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    Probing for PMIC on I2C:
INFO:    PMIC: found AXP313
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9
INFO:    Changed devicetree.
ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19


U-Boot 2025.04-armbian-2025.04-S3482-Pfbbd-H8869-V9b5f-Bb703-R448a-dirty (Nov 13 2025 - 13:20:15 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: Transpeed 8K618-T
DRAM:  2 GiB
Core:  68 devices, 22 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0, mmc@4021000: 2, mmc@4022000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   Could not get PHY for ethernet@5030000: addr 16
No ethernet found.

starting USB...
Bus usb@5101000: sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus
USB EHCI 1.00
Bus usb@5101400: USB OHCI 1.0
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5101000 for devices... 1 USB Device(s) found
scanning bus usb@5101400 for devices... 1 USB Device(s) found
...

I have a/m model with 2GiB RAM / 16GiB eMMC- Wifi: XR819 (XRadio XR819).

I've download and install a .img file Armbian_community_25.11.0-trunk.437_Tanix-tx6_trixie_current_6.12.47_minimal.img.xz

I want to have a server version CLI, but I don't know where to find that.

My problem is that the WIFI is not availible after the boot in ARMbian. 

Is there any solutions for make it availible?

Thank you in advance.

Last Week, I found this box on a shelf and wanted to boot it but it was in a bootloop

So I flashed the stock firmware H616Alwinner.img and it flashed but again wifi issue...Then I made a dumb decision and asked chatgpt and it said "T95 , TX6s all share the same SoC so flash One of their .img's" So I did

It flashed but now no LED but stuck on T95 logo so I tried to flash the original H616Allwinner.img again..but now it says "Error - Download Boot 1 Failed" (Honestly I Don't know how it got Hard-Bricked But I think because of the T95 flash)

Now I tried Sunxi-fel but Time out....Now it's totally Super-Bricked Then I tried flashing the T95 image again it successfully flashes but the same thing but stock image "Download boot 1 failed"  

Can Someone Help Me to unbrick this thing and maybe install Armbian on this? 🥺

[P.S:- Even Phoenixcard wouldn't help...(When inserting SD card and normal boot or toothpick boot it does nothing ) No LED and normal boot just boots me into the failed T95]

Here Is My TV Box below

I think there's only a USB port

The name of the unit would suggest that it's a X96-Q clone,

but the revision number suggests that it's a T95 mini. Like as seen in this video 

I don't have access to console mode. I can only access adb commands as root.The RAM type DDR3 seems LPDDR3 ( version ??)

I've tried different Armbian images without success.

Unfortunately, Secure Boot is enabled.

I read this post  and test Armbian-20240716-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_Secure_Boot.img.tar.xz from Nick, without success

I have an Android image named M96-Y6.img.

EDIT1:
Also it has a AP6330 Wifi Chip ( thanks to "dmesg")
It has a internal AC300 PHY ( thanks to "Device info HW")  

Attached is the "dts" file

devicetree.dts device_tree_dump.txt

https://pl.aliexpress.com/item/1005006249858881.html

Extracted dtb and dts files attached.

It boots Warpme/miniarch image for X96 with LPDDR3 RAM

https://github.com/warpme/miniarch/releases/download/f3b14fbae071/MiniArch-20240715-6.16.1-board-h313.x96_q_lpddr3-SD-Image.img.xz

However internal Ethernet port is silent. It can work through USB->ETH adapter though.

Any Idea on how to make Ethernet working?

sun50.dtb sun50.dts

I have a T95 4Gb/32Gb box, on the motherboard it says H616-T95MAX-V4.0-20191217.

And the CPU model is sun50iw9.

Is it possible to remove ANDROID and install ARMBIAN?

Thank you in advance for your answers

I know there are no Armbian images for H313 soc yet, too bad. This small TV box could be interesting for creating small servers connected exclusively via WiFi.

Button 1 is the flash button, while button 2 is used to enter recovery mode.

I tried images for H313 miniarch and others for H616 but I can't boot in any way. I'm using a USB stick obviously without using a USB hub but only the USB stick and for now only Android starts.

What I would like to do is install Armbian on the X98H TV box. 

I tried many ways to do that, but I was not successful. If you know how to install Armbian on it, plz suggest to me

Thanks

I have a T95 Super with H2+/H3 processor. I've been successful running Armbian in the past on it and even writing to eMMC but am looking for the most updated build I can to burn to the eMMC.
I have H3droid running on it after a VERY long install process and many board reburns to fix it. 
I noticed H3droid has an "Armbian" option in it's rescue menu but there don't seem to be any instructions on how to install with the menu/use it.
What is the best new build for this setup?
Thank you!

I have a MXQ Pro 5G 4K TV Box with Allwinner H616 and the motherboard IK316-EMCP_V4.1.  
I am looking for a server (CLI only) version of the Armbian image for this device.

The previously shared Google Drive links in this topic are no longer working.  
Could someone please provide a new download link (Google Drive, MEGA, etc.) for the latest server image compatible with my device?

If there are any specific instructions for booting or the correct DTB file, please let me know.

Thank you very much!

Best regards,  
Luska1331

BTW: I generated this message with the help of Copilot because I don't speak English very well.

Tried to run a progressive web app (PWA) and just learned that PWA is not supported by Android TV OS. I've found that since it's just a SBC, I can install any other OS on it and stumbled upon Armbian.

Since I'm new, I would like to know what images is supported with this board and any related guides to install it. This board has 1 full HDMI port, 1 USB type A port for data, and 1 USB type C port for power only (this is just my assumption). No SD card slot.

I just need it to be able to run a modern and latest browser to run the PWA.

Thanks for all the help 😀

I need a little help here. I managed to compile a working version for this board. However, it does not recognize the internal disk, which in this case is a nand.

I used this repo: https://github.com/sicXnull/armbian-build.git
Branch: X96Q-5.1-DDR3
 

Could someone help me?

Firstly sorry for the bad english(By Google Translator). I've been searching for a long time on how to use linux on my tv box, without success.

I searched here on the forum in several topics, I didn't find anything related to the tx6s, the closest I came was the Orange-Pi Zero 2, which uses the same processor.

In one of the topics, from 2020 if I'm not mistaken, a user warned that because it was the same processor or similar hardware, it wouldn't necessarily work.

Even so I ventured out and tried in hopes of working, some versions of Armbian for OrangePi Z2 and other linux for ARM.

With other ARM versions the tv box, booted normally on Android, with Armbian, it didn't even start and no led lit up.

What made me believe that somehow with Armbian, the tv box recognized the SD card as bootable, but for some problem it can't boot. Maybe it's the u-boot used. if some of the versions I tried to install:

https://drive.google.com/drive/folders/1HsD11VGl-CSv98GgmWoVSlnFYEE1jMNM - Orange-Pi Zero2 IMG [Armbian_22.05.0-trunk_Orangepizero2_jammy_edge_5.17.5_minimal.img] - (No_Boot) - {Problema_com_o_U-boot?}

https://drive.google.com/file/d/1wZulOr6_Sur_btcqqzBFTpjPmhPX0fZ1/view?usp=sharing - Orange-Pi Zero2 IMG [Armbian_22.05.0-trunk_Orangepizero2_focal_current_5.15.35.img] - (No_Boot) - {Problema_com_o_U-boot?}

https://drive.google.com/drive/folders/13pY93TozoF2omgKYnCiSZrONbBvBPxAh - Orange Pi Zero2 Linux5.13 IMG [] e []

https://armbian.hosthatch.com/archive/orangepizero2/archive/Armbian_21.08.1_Orangepizero2_hirsute_edge_5.13.12.img.xz - Orange Pi Zero2 IMG [Armbian_21.08.1_Orangepizero2_hirsute_edge_5.13.12.img]

https://mirrors.dotsrc.org/armbian-dl/orangepizero2/archive/ Orange Pi Z2 IMG [FOCAL Armbian_22.02.1_Orangepizero2_focal_edge_5.16.11][Armbian_22.02.1_Orangepizero2_bullseye_legacy_4.9.255.img]

TV BOX MODEL: https://linux-sunxi.org/Tanix_TX6s

I also found this about u-boot, I don't know if it can be useful or how to use this information, I have no technical knowledge:

https://gist.github.com/heitbaum - u-boot

https://github.com/jernejsk/u-boot -u-boot

https://github.com/jernejsk/u-boot/tree/h616-v2 - u-boot

If anyone knows how to install this tv box, please show me the way to the stones. it could be the server version.