AlexanderTN

@yopp Forgot to tell you that in my case the Android OS works well on the same 2K monitor but the Armbian does not.

Try different monitor indeed helps. So this is my case (just have time to test it this morning) that explain the issue I met): - in 2020 I tried a full HD Dell monitor and I can see the boot screen and logs from that monitor - in 2023 I tried again on a 2K LG monitor and it shows nothing on screen So as SteeMan said : SD card quality and monitor type are the factor we need to check when we encounter this 'HDMI boot issue' Cheers.

Hi @SteeMan Really thank you for taking the time to help me. The SD card I used was the one I used to install Manjaro on another box so I think it's ok (although it's not class 10). I want to update you that I finally found out that somehow the HDMI signal does not work, but it actually boots. - I go to check the router and from the DHCP section, I found out that the armbian device is running with an IP. - then I ping/ssh to that IP and voila` I can control it (using the default username password root/1234). Now it's time to modify the dtb (as with my box, I have to change the max_frequency value inside dts to 50000000 so that I can recognize the eMMC disk) and try to install to eMMC. Again, thank you!

@SteeManBecause I thought that I should bring the box back to its original state by reinstalling the Android ROM (I use USB Burning tool to flash the Android ROM). Then from that starting point, I do install the Armbian using the toothpick method. So my assumption is wrong?

@SteeManThank you for the reply. I tried different lengths of time between 2 and 10 seconds, and the result is the same: - If I hold it too long it boots forever. It can only boot into android recovery if I ejected the SD card. - If I release the toothpick it will be "No signal" from the screen monitor (while the box shows blue light). P/S: I tried different ROM like TX3Mini-20171220-Tanix_Box_Com.img, X96_Mini_Amlo_S905W_290421_9.0_Amlo.zip - do you think the Android ROM could be the issue? What is the Android ROM you are using for your X96W boxes?

Since I meet the same issue with the thread owner, then I reply this thread. Historical data: On the same box I made it successfully with the steps (but I do not remember that I make it works either using an sd card or USB, or the exact image), I remember I used u-boot-s905x-s912 , then I move all the data to eMMC successfully too (I remember the LAN works ok, wifi worked with a Wifi USB Dongle). Now after 2 years the OS was broken because the disk is full, I tried again and see this issue. I actually do not set high expectation for this box: Just a place where I can install small tools like Pihole, I do not need wifi just the Ethernet. As I tried and failed many times so I tried to flash the eMMC to Android & now I can use the Android OS. Here is my configuration: Hardware: X905W 2G RAM, 16GB eMMC storage. Software: Try this Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz (both Balena Etcher & Rufus 3.12) Also try this: Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11.img.xz u-boot.ext copied from u-boot-s905x-s912 (635kB) (copied not moved) extlinux.conf (also tried with meson-gxl-s905x-p212.dtb) LABEL Armbian LINUX /uImage INITRD /uInitrd #FDT /dtb/amlogic/meson-gxbb-p200.dtb #FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb #FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb FDT /dtb/amlogic/meson-gxl-s905w-p281.dtb #FDT /dtb/amlogic/meson-gxm-q200.dtb #FDT /dtb/amlogic/meson-g12a-x96-max.dtb #FDT /dtb/amlogic/meson-g12b-odroid-n2.dtb append root=UUID=afbf3a1b-d905-4b27-b78a-3682d3db0dca rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles Note: The above extlinux.conf is generated with the build Armbian_23.02.2_Aml-s9xx-box_bullseye_current_6.1.11.img.xz, for Armbian_20.10_Arm-64_focal_current_5.9.0_desktop.img.xz the last line is slightly different: root=UUID=ROOTFS ... Tried on both SD Card(32GB & 64GB) & USB (16GB) and get the same issue, I cannot boot to the install screen. - Using Method 2 I got the same error as the thread owner shows. - Using Method 1 (the toothpick method): I hold the toothpick and see that the screen show X96 Mini screen (same as when I boot to the Android OS) then it boot again to that screen and make it a forever loop, if I withdraw the toothpick there will be no HDMI signal, the monitor will turn off. Thank you so much if you have any suggestion.