I am facing similar issue with this board and now I am stuck with it.

Hi I am trying to breathe some life into an older generic Amlogic TV box on my workbench and am hitting a brick wall with modern mainline images. I’m looking for a copy of a legacy, community-archived Armbian image (Kernel 5.4.y, 5.10.y, or 4.19.y) tailored for the S905X / S905W (meson-gxl) architecture. The newer automated GitHub builds (6.12+ kernels) completely purge the old asset files, and modern multi-stage boot configurations (boot.scr) are being entirely bypassed by my box's legacy onboard bootloader. Hardware Specs & Current Context: SoC: Amlogic S905X / S905W variant (Generic budget clone box, likely 1GB RAM) Target DTBs I'm testing: meson-gxl-s905x-p212.dtb or meson-gxl-s905w-tx3-mini.dtb The Baseline (Crucial Detail): CoreELEC-Amlogic.arm-9.2.8-Generic boots instantly and functions flawlessly from a Class 4 MicroSD card on this box. CoreELEC The Problem: Modern Armbian ophub images (6.x mainline kernels) fail to engage the bootloader at power-on and skip straight to the internal, native Android OS, even with aml_autoscript renames or script adjustments. Because CoreELEC 9.2.8 catches immediately, I know the physical hardware, SD slot bus, and basic external boot priority work perfectly. It confirms this specific box requires a primitive build structure that still utilizes the true legacy u-boot.ext chain-loader file on the root partition and simple text configuration (uEnv.ini or early uEnv.txt configurations) which these stubborn eMMC controllers require to handshake. CoreELEC If anyone has a preserved .img.xz or .img.gz file sitting on a local drive or a private cloud mirror (like an old balbes150 or flippy build from 2020–2022), I would greatly appreciate a download link! Thanks in advance for keeping the legacy hardware archive alive.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

I guess dirty spi. wipe it and try again

Hello, I am attempting to run armbian off of UFS on an a7z and running into issues. I don't know if I'm missing something fairly basic. - Board is unmodified by me. I don't know how commonly sellers mod these boards themselves, but there is a bit of scuffing on the ram and UFS chip. It has 8gb ram, the official hsf, and the official power supply. Display over HDMI, USB hub for IO. - I can boot the official radxa image from the ufs, flashing it with sudo dd if=<path_to_image> of=/dev/sda bs=4M status=progress conv=fsync - I have successfully built and booted armbian trixie 6.6 kernel with kde on the sd card. I had to do some tty backflips to get kde to launch once it booted, but it did run. I have also booted the released armbian xfce build from sd, which I had no problems with at all. - Currently I have the official radxa image booted off the sd card, and I have been attempting to build and flash armbian for ufs. - I built with ./compile.sh, board selection: radxa-cubie-a7z-ufs, vendor 6.6, trixie, desktop, kde, no extras - Flashed to the ufs with the same command from above from my session on the radxa build sd card, and rebooted without the sd card. The green LED comes on solid, then the fan kicks in, then the LED turns off. My display comes up out of sleep, black screen for a second, then no signal. - After about 25 minutes, I disconnected power, and booted back into the sd card. Here is the boot.log from the ufs: https://pastebin.com/ASpndqVU