Hey tparys! Thank you very much for your reply and apologies for my delay getting back to you. I haven't had much time to play with this board, but lately I've managed to do some very good progress. Basically I've got Armbian 20 Bullseye working with kernel 6.19. that was a victory! Versions that work/don't: [WORKS] Armbian_20.07_Arm-32_bullseye_current_5.7.7_desktop.img (From a MiQi board) [NOPE] Armbian_25.11.1_Tinkerboard_bookworm_current_6.12.58-homeassistant.img [NOPE] Armbian_25.11.1_Tinkerboard_noble_current_6.12.58_minimal.img [NOPE] Armbian_25.11.1_Tinkerboard_trixie_current_6.12.58_minimal.img [NOPE] Armbian_26.2.0-trunk.370_Tinkerboard_noble_current_6.18.8_xfce_desktop.img [NOPE] Armbian_26.2.1_Tinkerboard_trixie_current_6.18.8_minimal.img Armbians 25 up, some times hangs at Starting Kernel, and majority of the times stops at Loading Ramdisk, all of them tested with most of the DTBs provided The android that runs on the other working board has a kernel with version 4.4 Havent test that because I believe it stops earlier than that I have extracted the DTB from the working Android and got a frankenstein EVB DTS working with some of the features. So far I've got working: *4Cores *2GB Ram *Wifi (using rtw8723d_fw.bin ) *Status LED What doesn't work for sure: -Ethernet -FE2.1 USB Hub 2.0 Untested: ? LVDS 1/2 Panel ? EDP 1/2 Panel ? Speaker ? MIC ? SIM Card Module (Attached to the FE2.1 Hub, so defo not working) And maybe some other peripherals that I was not able to test. I'm still to make the FE2.1 USB Hub work as the 4 only USB physical ports are not working. Also ETH has an issue on stmmac that returns the reset value. and this was merged recently to the kernel. (I'm trying to build v6.19 from source with my patch, but thats being painful too ) Here is my stmmac patch: diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c index 01ede5148163..9f0ee9ea96fa --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c @@ -3208,8 +3208,7 @@ static int stmmac_init_dma_engine(struct stmmac_priv *priv) ret = stmmac_reset(priv); if (ret) { - netdev_err(priv->dev, "Failed to reset the dma\n"); - return ret; + netdev_warn(priv->dev, "Failed to reset the dma, device will work with reduced throughput\n"); } I have also attached my current DTS built on top of the EVB version based on the Android with logs from both. Once again, thank you very much for your help! Best Regards, Mauricio. Armbian 20 Bullseye booting log.txt Android Boot Full log.txt android_check.dts rk3288-evb-rk808-armbian-fixed36.dts

Finally managed to restore the box to stock official Android firmware, everything works as expected. I also tested a firmware for the H96 Max M1, with this one the WiFi is not working, they seem to use a different wifi chip. Any recommendations on where to start with flashing Armbian on this device?

OMV 8+ doesn't support 32bit architectures anymore (including Helios4). https://forum.openmediavault.org/index.php?thread/58798-helios4-omv-8/ Given it seems to be stuck on kernel 6.6, it does feel like it's on life support unfortunately.

which of course fails as nmtui it will not accept the dot separators in an ipv4 address needed to be entered in an ipv4 only situation. I'll repeat as I have said quite a few times already, that I, in weston wv, am at least 100 miles from ANY ipv6 enabled net access. There surely are some ipv6 in pittsburg pa., 150 miles north, maybe in Charleston, 100 miles south. I have battled this using armbian-config and in using that microscopecly tiny moving radiation symbol at the top right of the xfce4 screen. If that is a defense to prevent ipv4 addresses where ipv6 is expected, change the box color so we know it can be skipped in real estate not yet blessed with ipv6 addresses. We are NOT mind readers any more than you are, but this particular group off us is about a 3/4 million in the whole state where flat ground to build a house on is measured in the gallons of diesel fuel to make it flat enough to build on. Fix nmtui so its actually usable and do a respin. while at it, fix whatever prevents our mounting it to edit such stuff before 1st boot. That restriction is a huge pain in the ass too. fdisk tells us its dos partition for sdc with an ext4 sdc1, but when we attempt to mount it, the ext4 cannot be found. That restriction is also present in the 25-5 release. Yet it boots & almost runs. next try?

just go threre: https://forum.friendlyelec.com/viewtopic.php?f=93&t=4691