Turgus

Which armbian version did you try? Which dtb did you set in configuration file? On all x96mini (ver. 4.x) I got, there are no issues installing bionic (with added desktop) on internal, but I don't know which chips those got(could check it the days..)..

..the dtb files are where they always were!? ..I just burnt the 20201002 version on card and p281 & tx3mini dtbs are there: ..and your extlinux.conf (in the folder /BOOT/extlinux/) should look either: LABEL Armbian LINUX /zImage INITRD /uInitrd #FDT /dtb/amlogic/meson-gxl-s905w-p281.dtb FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 or LABEL Armbian LINUX /zImage INITRD /uInitrd FDT /dtb/amlogic/meson-gxl-s905w-p281.dtb #FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

Yes, the size doesn't mean anything as it just initializes use of the aml_autoscript ..which android version is your rom? if its android 9.x try burning nougat rom as startpoint..

Did you try to get a rom or update via seller or from tanix? When your nand is already formatted, maybe try all official roms from tanix for tx3 mini/max and tx9 (since it has an s912 too).. Or try to install the armbian you could boot on eMMC.

..crazy world, okay-then you have to use s912 files as you did..I think the problem is that you used other systems which use other bootloader(then uboot is messed up for the mechanisms used with these armbian builds). Try starting with fresh android install (preferably nougat rom as it brings the best startpoint for armbian attempts..) to get un-tweaked bootloader..

Are you sure that the specs are right?! ..all tanix tx3 minis I saw had(like the x96mini too) a s905w (not a s912) and there is a dtb meson-gxl-s905w-tx3-mini.dtb for tx3m (also meson-gxl-s905w-p281.dtb should work better than p201 which works just basically) then it should work. Is there a special reason you choose such an old image(better try one of the newer the extlinux-variants..) ??

Yes, there are some android 9 versions without update tool, but on all x96minis(mine and from others) I could install armbian when using the nougat rom as startpoint(once you got armbian on the device newer armbian versions will boot flawless..)..

Hi @fergian94, to run/install armbian on the x96mini is not that difficult: after burning the image onto card you have to edit extlinux.conf to point to /dtb/amlogic/meson-gxl-s905w-p281.dtb (added my extlinux.conf). Also you need to rename u-boot-s905x-s912 to u-boot.ext then you plug in ethernet cable (or USB-WIFI) to have network(built in wifi doesn't work on +90% of devices..) and keyboard (and sure the prepared card) to start via toothpick-method or via update-tool in android. Once started from card everything should work as expected and if you configured/installed/localized all stuff you want/need, you could burn it on eMMC via sudo /root/install-aml.sh If you get problems to start from card and got android 9.x on the device, try burning(via card or via cable) android 7 version as startpoint.. You will find one linked for example here: https://www.getdroidtips.com/stock-firmware-x96-mini-tv-box/ extlinux.conf.x96mini

Armbian_20.09_Arm-64_bionic_current_5.8.5.img.xz (with added desktop) runs without problems for around 24 hours from eMMC on some of my x96mini 2/16G devices.. When testing Armbian_20.09_Arm-64_bionic_dev_5.9.0-rc4.img.xz (where usb works now) before, I had problems installing the desktop(installation via armbian-config started, but stopped after 2 seconds without any message), also system complains that filesystem needs resize on next boot(but this was already done on first boot..fs and size were okay when checked with fsck on linux laptop..), but I'm not sure if those issues came from my card, which was an older one with already 500+ write-cycles!?..

Try those dtbs you get with the image you use and find out which works (best) for your board-that one you try to use doesn't fit to kernel and stuff and there is no chance to boot with wrong dtb..

While Ver 20200820 & 21 (bionic + Desktop) works like a charm from internal and card on my x96mini 2/16 boxes, I can't get the dev-builds (Ver 20200821-dev or Ver 20200818-dev working as I got no USB and so no Keyboard.. On U-Boot keyboard is shown and soundcard (same without it) has LED on, but with booted system all USB devices are dead. Tried several gxl-dtbs..

on a tanix tx3 mini (also p281 board) I had issues with an android 9 FW too, maybe burn an android 7 variant like this one as startpoint!?..

Yes, I install most builds to eMMC on the x96minis and never had any problems using sudo /root/install-aml.sh Which system did you have on eMMC when you bricked the device? Could you revive it via usb burning tool and android?! Does it still boot from cards?

Cool thing with the new u-boot on s905...! The bionic Version 20200816 (+ Desktop) runs nice from card and internal eMMC on (a part of) my vast of p281 x96mini 2/16 boxes.

Thank you @hexdump & @balbes150 with your help I managed to boot with success! ..maybe others could avoid through my experience running into stupid issues because an simple equal sign.. By the way (even when I tweaked the u-boot with uEnv.txt) I like the output on screen..it a really cool feature-is there anything like this for H6 cpu too?!