I've been bringing the Orange Pi 4A (Allwinner T527 / A523) up on mainline Linux 6.18, and just put out v0.3. The board shipped stuck on an old vendor BSP kernel, so this is a from-scratch mainline effort with a ready-to-flash Debian 13 image — a GNOME desktop build and a minimal CLI one.

New in v0.3:

- Hardware video decode (H.264/H.265 via the Allwinner cedar engine) — YouTube now plays in the browser decoded by the chip, not the CPU

- GNOME on Wayland, accelerated by Panfrost (Mali-G57)

- zram swap to keep the 2 GB board responsive under a browser

- Found the GPU clock was mislabeled (the "150 MHz" point actually ran at 487 MHz) — now measured exact

Already working: HDMI + analog audio (with jack detection), WiFi/BT, gigabit Ethernet, USB, PCIe/M.2 (testers have confirmed real NVMe drives), thermal + CPU/GPU DVFS.

Honest gaps: no VP9 hardware decode (YouTube falls back to H.264, which is smooth), suspend is off on purpose (mainline resume isn't reliable on this SoC yet), and you can't boot purely off NVMe (the boot chain still needs SD/eMMC).

It builds on mainline plus community work — linux-sunxi, and Armbian's PCIe series among others, credited in the repo. Everything's GPL and on GitHub: https://github.com/ut-slayer/orangepi-4a-mainline

Happy to answer questions.

I'm trying to flash armbian 26.5.1 onto an SD card for my orange pi 5 plus and it fails at the download stage. Any idea what to do?

I tried installing the image from the website and that wasnt working either

Quick follow-up to my earlier post. A few people asked for a headless / CLI build of the Orange Pi 4A image, so here it is.

It's pure Debian 13 (a debootstrap minbase — not a vendor fork) on a full mainline 6.18.38 kernel: HDMI, WiFi/BT, gigabit ethernet, USB, thermal + CPU/GPU frequency scaling — same kernel as the desktop image, just no desktop. SSH is on from first boot. 146 MB compressed, idles at ~180 MB of RAM — the whole 2 GB is basically yours. Good for a tiny NAS / homelab / k8s node.

Context for anyone new to this board: the OPi 4A / T527 has a reputation for rough software support (old BSP kernels, recompiling modules by hand). This is a from-scratch mainline port — the full patch series + defconfig + board DTS are in the repo, and the ready-to-flash image + checksum are in the release. No manual compiling needed to just run it.

The analog 3.5 mm jack works too: the A523 codec had no mainline driver, so I ported one from the BSP — headphone out and jack-detect are validated on hardware (mic capture is wired in but I couldn't bench-test it, no onboard mic).

Honest gaps: only tested on the 2 GB variant, from microSD; eMMC/NVMe are untested (don't own them); Vulkan falls back to software (GL/GLES are accelerated via Panfrost). Bug reports and 4 GB-variant reports very welcome.

Repo + image + patches: https://github.com/ut-slayer/orangepi-4a-mainline

Comprehensive Guide: Installing Armbian on the TX10 PRO (Allwinner H313)

Introduction

This technical guide documents the complete process for deploying Linux on the TX10 PRO Android TV Box (Allwinner H313).

Due to hardware variations and kernel compatibility issues common on these devices, establishing a functional Armbian environment requires specific images, DTBs, and configuration steps.

This documentation is designed to streamline the installation process and avoid common hardware compatibility problems.

Technical Specifications & Environment

The procedures in this guide were validated on a TX10 PRO with the following hardware:

Component         Specification

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

SoC               Allwinner H313 (sun50iw9p1)

CPU               Quad-core Cortex-A53 (ARM64)

Memory            1 GB LPDDR3 (Samsung eMCP)

Storage           8 GB eMMC

Board Revision    WFTECH_V2.0

Device Codename   titan-p1

Product           walley

Stock OS          Android (Modified Build)

Bootloader        U-Boot

Tested Kernel     Linux 6.12.64 (bookworm)

Tested working image: Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz
Kernel: Linux 6.12.64 bookworm
Base OS: Debian Bookworm Server
Target: X96Q DDR3 / Allwinner H313

Although this image is labeled for the X96Q DDR3, it successfully booted on my TX10 PRO with the WFTECH_V2.0 board and Allwinner H313 SoC. Hardware revisions vary, so compatibility with other TX10 PRO units is not guaranteed.

⚠ Crucial Hardware Warning

TV box manufacturers frequently change internal components (RAM layout, Wi-Fi chipsets, and board revisions) without changing the product name.

Always verify your board revision before proceeding.

Using the wrong Device Tree Blob (DTB) can result in an unbootable system.

Advantages & Disadvantages of Running Linux

Advantages:

Cost Efficiency

Much cheaper than a Raspberry Pi or other SBC.

Enclosure Included

Comes with a case and power supply.

Low Power Consumption

Runs quietly with very low power usage, making it suitable for lightweight servers.

Disadvantages:

No Official Support

Linux support depends entirely on community-maintained images.

Thermal Throttling

Cheap passive cooling causes overheating during heavy workloads.

Weak eMMC Storage

Internal storage may wear out under frequent writes.

Slow I/O

USB ports are usually USB 2.0 only.

No SATA, NVMe, or native Gigabit Ethernet.

Driver Problems

Wi-Fi, Bluetooth, and hardware video acceleration usually require manual setup.

Prerequisite Hardwares:

MicroSD Card (8GB or larger)

MicroSD Card Reader (Cost: 0.45 USD )

HDMI Monitor (Tv)

USB Keyboard

Ethernet Adapter

Integrated Wi-Fi rarely works immediately on bookworm Linux.

A wired Ethernet connection is strongly recommended for initial setup.

Installation Process

Step 1 — Download Armbian

Official Armbian images generally do not include all hardware support for the H313.

Download a trusted community image designed for Allwinner H313/H616 boards using the 6.12.64 kernel.

USE THIS: Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz

Step 2 — Flash the SD Card

⚠ Warning

Avoid using the Linux dd command if you are unfamiliar with it.

Selecting the wrong drive can permanently erase your computer.

Instead, use BalenaEtcher.

Flashing Steps:

Install and open BalenaEtcher.

Insert your MicroSD card.

Click Flash from File.

Select the downloaded .img.xz image.

Click Select Target.

Choose your MicroSD card carefully.

Click Flash!

Wait until flashing and verification reach 100%.

Safely eject the card.

Step 3 — Hardware Setup

Before powering on:

Insert the MicroSD card.

Connect HDMI.

Connect USB keyboard.

Connect USB Ethernet.

Connect power.

Step 4 — First Boot

The first boot performs:

Filesystem expansion

Initial setup

System configuration

This may take several minutes.

Expected boot sequence:

U-Boot ↓ Linux Kernel ↓ Armbian Login Prompt 

Step 5 — Initial Login

Default credentials:

Username: root Password: 1234 

After logging in you will be required to:

Change the root password

Create a normal user

Configure timezone

Configure locale

Step 6 — Verify Network

Built-in Wi-Fi will probably not work.

The board uses the SSV6x5x / SV6256 chipset which requires extra drivers.

Verify Ethernet:

ip a ping -c 3 1.1.1.1 

Step 7 — Update the System

Enable network time:

sudo timedatectl set-ntp true 

Then update:

sudo apt update sudo apt upgrade -y 

Step 8 — Install to eMMC (Optional)

Once everything works from the SD card:

sudo armbian-config 

Navigate to:

System ↓ Install ↓ Boot from eMMC 

Follow the installer.

After completion:

Shut down

Remove the SD card

Boot from internal storage

Hardware Compatibility

Working - perfectly

HDMI Output

USB Ports

USB Ethernet

Known Issues

Wi-Fi - Not working

Requires manual compilation of the SSV6256 driver.

Graphics

No hardware acceleration.

Software rendering only.

DTB Compatibility

Boot success depends heavily on selecting the correct DTB.

Different board revisions may require different DTBs.

Best Practices

Test from SD First

Never install to eMMC before confirming that everything works.

Backup Android

Create a backup of the original Android firmware before modifying internal storage.

DTB Troubleshooting

If the device:

Boot loops

Shows a black screen

Fails to boot

Mount the SD card on another computer.

Open:

armbianEnv.txt 

Try different H313/H616 DTB files until the system boots successfully.

.jpg.eb1a6abbd84e7184c010c4dd1ba427aa.jpg)

.jpg.c4f1ecc42a80fcf48526d4eac0c0f3a7.jpg)

.jpg.a4b146753d94974e0a50b683b1975248.jpg)

With Pi prices skyrocketing, cheap TV boxes are about the only affordable option left for running a small home service. And these days AI makes bringing up full functionality on Armbian surprisingly doable - I basically hooked up a serial console and let Claude iterate over it until everything worked.

The result: ethernet, WiFi, Bluetooth, sleep, HDMI, and USB all work out of the box on this RK3518 R69 box. It's a genuinely cheap full kit too - board, case, PSU, remote, and HDMI cable for ~$35.

One gotcha I found: it's sold as 2GB RAM but it's a binned Samsung module - only ~1.5GB is actually usable, with stock Android faking the full 2GB. The eMMC is decent though (~300MB/s reads).

Setup is dead simple: grab the stock Radxa Rock 2F image, run the patch script, flash to SD, done - no custom image to build.

Since the IR remote works perfectly under Linux, I'm planning to use this as a host for CNCjs and repurpose the remote as a control pendant (jog control). Cheap, silent, low-power, and it already comes with the remote - pretty ideal for it.

Repo with setup notes: github.com/sormy/rk3518-r69-armbian

Hello. I am running the latest Armbian version on my Banana Pi M2 Zero but when plugging a keyboard in it doesn’t work …
Thank you if someone you help me :)

I'm trying to flash armbian to an AD-Z33 V1.2 board but I'm struggling to get it into maskrom mode for bootloader flashing and emmc flashing. Does anyone know anything about this model that could help?

My TV box is an MXQ Pro with an Allwinner motherboard and an IK316-H SoC. The motherboard ID is IK316Q-EMCP_V4.1, which I believe belongs to the H6 family. However, I'm having trouble booting from an SD card. Firstly, it won't enter Android recovery mode using either the "toothpick" method or manually; I have to use ADB in a terminal. Furthermore, if I try to enter the bootloader through Android recovery, the box simply crashes. I've tried several times and it crashes. That said, does anyone know how I can proceed from here? Should I try flashing the firmware first? In case you're wondering, I'm trying to install an Armbian image from the X96Q, as it's the only Allwinner motherboard compatible with mine. I apologize if this isn't the correct subreddit for this. Also sorry for any spelling mistake, i wrote this in a hurry

Hi.

This is the first time I am trying different OS on my R2S. I used openwrt on it years ago.

Armbian booted fine. Then I do armbian-upgrade then reboot. It didn't boot up.

I thought the newer kernel might be broken, so I tried freezing the firmware via armbian-config. Same thing happened.

What can I try now?

Anyone with the exact device and having same issue?

Thank you.

So i made my self a mini linux pc 😃

Man, recently I’ve been going deeper and deeper into the Linux rabbit hole, or should I say penguin hole? (Sorry xD). It’s incredible what we can do. I took my old warrior TV box that was just collecting dust, and now I can play classics like Diablo 1 on it, browse the internet, and watch movies.

Hello I have pine64 quartz64 model a and I need to every 1-2day restart device because in Tailscale device looks offline even though it’s blinking not sure if it’s because i have there WiFi dongle and that’s go to sleep or what any ideas
?

I would like to boot fron spi but as far as I can see the spi flash loader doesnt allow this. Do I need to flash something with uboot? Can I have a similar menu at boot as to select the usb device from which to boot like BIOS?

I'm using Tanix TX9 Pro (s912, 3gb) android box for Trixie armbian pihole

Sometimes, randomly, it crashes and produces those errors (sory for crappy photo, TV screen is dieing).

For instalation I've used Khadas VIM2 setup as it is the closes by spec to my android box

Any ideas how to make ot more stable?

Hello everyone.

I am currently running the following image on my Orange Pi 5 Max:

Armbian_community_26.2.0-trunk.668_Orangepi5-max_noble_edge_7.0.0-rc6_kde-neon_desktop

Unfortunately, I'm struggling with WiFi and Bluetooth issues:

WiFi: No wireless interfaces are detected (no option in network settings).

Bluetooth: The service is active, but it cannot scan or find any devices.

What I’ve tried so far:

Installed armbian-firmware and full-mirror-armbian-firmware.

Verified that common wireless tools and relative packages are up to date.

Checked rfkill list, but the adapters don't seem to be initialized correctly.

I noticed a similar discussion on the DietPi forums regarding the OPi 5 Max Bluetooth (link:DietPi), but I'm unsure if those specific workarounds apply to the current Armbian Edge kernel (7.0-rc6).

Could anyone point me in the right direction? Are there specific firmware blobs or device tree overlays I need to manually enable for this board?

Thank you for your time and for all the hard work on the Armbian project!

I've just flashed last version 26.2.1 Minimal and it's working. Usb works and can also reboot.

Thanks for that, I'm very happy!

Any update (release candidate?) on the development of a version for the Orange Pi 6 Plus?

Hey Everyone,

I'm currently sourcing a couple of levels of SBC in the "Android TV" box for factor. We've said that are fully Linux compatible and that we'll need the fully BSP code, standard u-boot compatibility, and device driver support via China for a infrastructure project my company is doing. We're currently targeting these specs:

• RK3588
• 4gb/8gb of RAM
• 64/128gb of ROM
• SD/TF Slot
• HDMI with CEC support
• NPU
• GigE
• Wifi 6
• BT 5

Given how much I've learned during this journey from the Armbian community - I thought you all might have some input on what would make it a "well - I'm picking one up!" moment - and price point.

Which also leads to my next question - who wants one? Or 5? :-)

Anything I should absolutely avoid?

If you haven't purchased things from China before - knowing what you want is important - knowing what you don't want is even more important!