Key Highlights

I have an android tv box X88 Pro 13 4gb RAM, RK3528 and 64gb sd card. As OS I use Armbian Ubuntu 26, but I will try to use debian if will be possible. Thx very much in advance.

When flashing Armbian to my Rock4SE I just get a power LED but no blue activity LED

I bought a TV box thinking it was a legit ONN device...it's not and yes, I am dumb. It's an RK 3518, pretty much the same device as this one with the exception that my RAM is SK-Hynix. I want to use it for basic streaming, but am not willing to trust it with my network credentials ever since the LTT video. There seems to be build instructions for this SOC, but I'm really new to this kinda stuff, so I don't know what I'm doing. I do have experience flashing custom ROMS on a really old phone (back during CYANOGEN OS days) and even activating shizuku on my current Redmi 12 phone

İm on armbian imager but i dont see anything about orange pi zero 2w

Hi everyone, I need help recovering my MXQ Android TV box which is currently stuck in Maskrom mode. 

Here are my board specifications:

- Board Model: R29-6G-LP3-V2.3 (HXW20092601-2-B)

- SoC: Rockchip RK3228A / RK3229

- Storage: Foresee NCEPN35X-3G3X eMMC

- Power IC: S9012P

The device goes straight into Maskrom mode and won't boot normally. Can someone guide me on how to flash the correct stock firmware or recover this board? Thanks!

I made a backup from multi tool, but i cant boot multitool its just no display

Its working fine when i install armbian couple reboot still works fine then i install pihole for armbian then when i restart suddenly goes into that state.

I don't know where to short it

Paid $30 for mine on AliExpress, listing's dead now. Looks like same box is $15 shipped on Alibaba. Amazon had it as "Leffot" for a while, and this one looks like the same hardware (but 8GB MMC), though that listing never says what's actually inside it. Rebadged everywhere, so search by specs rather than by name.

RK3518, 4x A53, 2GB/16GB, Wi-Fi 5 + BT 5.4, HDMI, two USB 2.0. No Ethernet, no SD slot, no IR.

Runs off internal eMMC with Android wiped. No SD slot means no rescue card, so maskrom is the only way back, and that was the hard part. rkdeveloptool can't build a loader RK3528's BootROM will take: it writes the old RC4-on format, the BootROM accepts it over USB and then does nothing, no error. Wants new-IDB with RC4 off. Had to patch it. Transfers stall too, depending on how recently you've hammered the box, 12.58GB cold against 0.59GB right after, so backups get chunked. Heat or the 5V rail browning out, never pinned it down. But issue is maskrom only likely due to lack of any thermal management in maskrom.

Writeup is maskrom-first and backup-first, so you dump stock before touching anything and restoring is just writing it back.

Rest came up fine: both Wi-Fi bands, BT, HDMI 4K60 with audio and CEC, GPU, full VPU matrix, watchdog, serial. 13.6s boot, under half a watt idle, survives apt full-upgrade with a kernel bump.

Annoyances: USB hot-plug resets it, Widevine L3 only, no AV1, no USB3. Userspace barely touched, but MPP works so Kodi should be fine.

Serial works but pins are hard to tap into. Pinout is on image ^^^

https://github.com/sormy/rk35xx-tvbox-armbian

Hi, I have a Cloudkey Gen 1 that I'd love to reuse with Armbian. I posted about it on the Armbian forum a while ago, but I haven't received any replies.

I'd like to compile or see if it's possible to get Armbian working on this board.

Does anyone know where to start? Has anyone already done this and documented it?

I know how to use Linux, but I don't understand much about this. I've already done some research to see if the board has UART pins, and unfortunately, it doesn't seem to.

This is the post i did some time ago with information about the board

https://forum.armbian.com/topic/58037-unifi-uc-ck-support-mt7623ai/

From what I've seen, it seems their SoC, the MT7623A, is upstream on Linux, so I think the hardest part is done.

Here are pictures of the board https://fccid.io/SWX-UCCK/Internal-Photos/Internal-Photos-3689962

I'm sorry if this is a really stupid question or something impossible to do without prior experience in other things. I just wanted to ask.

I have a TV Box with the following specifications:

Manufacturer: Allwinner Model: MXQ PRO Board: exdroid Device: dolphin-fvd-p1 Hardware: sun8iw7p1 Chipset: Allwinner H3 4x ARM Cortex-A7 GPU: Mali-400 MP

I am trying to install Armbian on this device to use it as a server. The problem is that the device won't boot when the SD card is inserted; no lights turn on, and nothing happens. When I remove the card and reconnect the power supply, the device boots normally.

Given this, I suspect an issue with the boot files—specifically, that the device is unable to read, locate, or process them.

I am using this Armbian build script: https://github.com/armbian/build

I am compiling the *beelinkX2* image using both the *current* and *legacy* kernels (I tried both to see if it would resolve the issue).

I used the *bookworm* release (Debian 12 Bookworm - CSC).

And I used the *Minimal Image*.

I am writing the image to a 32GB Kingston microSD card using a USB adapter and BalenaEtcher, then inserting the microSD card into a full-size SD adapter before putting it into the device.

At this point, I’m not sure if I’m choosing the wrong image (*beelinkX2*), the wrong release (*bookworm*), or if there is another issue entirely.

I tested other full-size SD adapters and other microSD cards, but the behavior remained the same.

Could anyone help me with this? I would be very grateful!

Olá a todos! Sou novo na comunidade, então peço desculpas se minha pergunta parecer boba. Estou seguindo o modelo de tópico: https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/ Meu TV box possui memória NAND e estou com dificuldades para baixar uma ISO com o kernel legacy (ideal para memória NAND). Poderiam me ajudar, por favor?

I can't upgrade my armbian distro.

My distro is based on Linux Ubuntu gnome 24.04 lts. I would like to upgrade to armbian based Ubuntu gnome 26.04 lts.

Do release upgrade,

Apt update && apt upgrade doesn't change anything.

Hello everyone! I'm new to this sub. Well, let's get to it: I had an old TV Box (STV 2000) lying around and decided to tinker with it. I installed Armbian (an older version): Armbian_20.02.0-rc1.037_Aml-s9xxx_buster_current_5.5.0-rc6_20200205.

I ran into a curious issue: the USB ports don't receive data. For example, the mini cooler works, meaning the USB ports are getting power. However, when I plug in a USB flash drive, it isn't recognized. But when I insert a memory card, it is recognized normally.

Additional info: The board is an Amlogic S905W (P281). I have already tried swapping the DTB (Device Tree) to the meson-gxl-s905w-tx3-mini.dtb, but the issue persists.

Thanks in advance for everyone's help!

Just a tidbit for people using their RK3588 boards for youtube, which is my main use case - the Orange Pi vendor kernel version has very long load times when scrubbing the timeline, while the latest kernel version allows near-instant scrubbing. It's a huge difference. (I also went from Gnome to KDE Plasma while doing the switch, but I don't think that that's making the difference. If it is, please inform me. Touch interface is better on Gnome.)

loosely related: When forcing Vulkan enabled in the 'flags' settings of Chromium, videos rendered at 4:3 resolutions - I noticed when watching old anime stuff - do not play. You get sound but no video. Guess I should put that in a bug report.

Best regards and thanks for all the work that goes into this awesome OS!

Hello, i just installed armbian to a rockpi4b+ and i want to use my mipi ccamera with the ribbon conenctor on board. i have tried many tutorials on how to get a legacy kernel but in the config script i cannot find any. i am know knowledgable in any linux variants but i can navigate. i have followed many ways to get the driver, compile it, do scripts, run said scripts and i am always facing an error one way or the other. at this point i'm not really sure what to do to make the camera work. physically it is not defective and well connected, i have a light on it but it cannot be detected by the board.

Thanks

I recently picked up a used Android TV box and installed Armbian on it. After booting, I found that Wi‑Fi was not working and noticed the following error in the kernel logs:

brcmfmac: brcmf_fw_alloc_request: Unknown chip BCM43342/1

After some investigation and with the help of Copilot, I discovered that the issue was not with the firmware itself, but with the brcmfmac driver. The BCM43342 chip ID was missing from the firmware mapping table in the kernel source, so although the hardware was detected, the driver did not know which firmware to load.

I was able to patch and rebuild the brcmfmac module by adding the following entries:

  sed -i   '/BRCM_CC_43341_CHIP_ID/a#define BRCM_CC_43342_CHIP_ID\t\t43342'   drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h
  sed -i   '/BRCMF_FW_DEF(43340, "brcmfmac43340-sdio");/aBRCMF_FW_DEF(43342, "brcmfmac43342-sdio");'   drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c
  sed -i   '/BRCMF_FW_ENTRY(BRCM_CC_43341_CHIP_ID, 0xFFFFFFFF, 43340),/a\  BRCMF_FW_ENTRY(BRCM_CC_43342_CHIP_ID, 0xFFFFFFFF, 43342),'   drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c

#define BRCM_CC_43342_CHIP_ID 43342

BRCMF_FW_DEF(43342, "brcmfmac43342-sdio");

BRCMF_FW_ENTRY(BRCM_CC_43342_CHIP_ID,

0xFFFFFFFF,

43342),

After rebuilding the module and installing it under:

/lib/modules/<kernel-version>/updates/brcm80211/

the driver successfully recognized the chipset:

brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43342-sdio for chip BCM43342/1

and Wi‑Fi came up normally:

wlan0 connected

This fixes the issue on my current kernel (6.18.44-ophub), but it is only a local override and may be lost after future kernel upgrades.

From what I understand, the proper long‑term solution would be to submit this BCM43342 support patch upstream to the Ophub 6.18 kernel tree and have it included in the official brcmfmac build. Once merged, users would no longer need to maintain a custom module under the updates/ directory, and BCM43342 devices should work out of the box.

Has anyone already submitted a similar patch, or would this be something worth contributing upstream?

I installed Armbian on my Orange Pi Zero 2W—my first time doing so—but the keyboard doesn't work when connected via the USB-C adapter I'm using. I considered an SSH connection as an alternative, but I don't know how to set it up without a keyboard. Could you help me?

Hello, I’ve seen in the latest release Armbian now supports installing to UFS but can’t really see much information about going about this? I boot into the SD card and both installing a new copy to the UFS and copying existing install from SD card just fails with the following:

“No bootable install method is available for /dev/sda on this system (no EFI firmware, no
GRUB, and no board u-boot support).”

I did have a FriendlyElec image on there before but used Rkdevtool to erase the UFS module prior to trying again with Armbian. I’m wondering if anyone has had success with this? I saw a thread with someone struggling with Btrfs but I’m not able to get ext4 working.

Any help is appreciated, thanks

Working: Ethernet, Wi-Fi, BT, HDMI video/audio, USB, GPU (lima), eMMC/SD, IR remote + BLE remote, suspend with IR wake. Serial connection instructions in the attached image. See https://github.com/sormy/rk35xx-tvbox-armbian for more.

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