SteeMan

You can try them all. But it may be the case that none of them work. I just did a search of the forum archives, no one has ever reported getting armbian working on your box. You seemed to have some success with the ophub fork, so you could try using their dtb with armbian or just trying their builds.

Shouldn't you be using the odroidhc4 images?

No that is not normal at that point. Most likely the dtb you are trying isn't compatible with your hardware. I would suggest trying other dtbs

If you click the button on that page labeled: Community Maintained Builds? (it is just above the selectors for all of the builds), then on the github page that link takes you to, click on Download Latest Image? Or to save you the work you could use the link at the top of the FAQ instructions. Or just go here: https://github.com/armbian/community/releases (latest build is 211, note they are listed in alpha order so the newest is not at the top)

Use the u-boot-s905x3 found in the current rolling releases. Why are you trying to use an old archived release?

It uses a different filesystem identifier that windows doesn't understand/ support.

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

Ophub is a fork of Armbian. They use the Armbian name without permission. They do not contribute to Armbian development nor do they participate in these forums. You need to contact them for support of their software. We can't help you here.

Where are you getting these images? That second one isn't anything from Armbian.

What exact version? Yes you can try different dtbs.

Try a different SD card. I've seen this happening more recently, especially with high capacity SD cards.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. This doesn't look like an Armbian kernel. What image are you using?

I'd recommend submitting PRs for what you think is necessary. You will get better feedback there than here in the forum as more developers follow the GitHub activity than the forums.

I'd recommend starting by submitting PRs for the board. Build up some knowledge and experience with Armbian development and processes. Then when you feel comfortable with the requirements expected of a maintainer, make that final commitment (https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/)

I'm assuming the image is using an ext4 filesystem, and macos isn't able to read a Linux ext4 filesystem. I'f you were to use the SD card on any Linux box it should be readable. Or install ext4 support on your Mac.

The quick fix is to use armbian-config to go back to the older working kernel, and then freeze kernel updates.

@alidaf what build are you trying to image? Why do you expect a Linux image to be readable on macros? Does the SD card work on the target sbc?

Buster was recently moved to end of support status in Armbian (Debian ends support in a couple of months too). Buster was released nearly five years ago. It is time to upgrade.

I should also add: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

I personally would say no. No one has submitted anything to Armbian related to these TV boxes. So none of the progress you see discussed in the forums is Armbian based. It is all done on forks of Armbian or other outside work. Until you start seeing someone step up and begin submitting PRs to Armbian for any of this work, I wouldn't say it has a future for you to consider it a replacement for anything. However if you only need to get something working once and don't care about receiving future kernel updates, then taking a build you see here would be fine.

Please provide all the information I asked for. What build are you using? What steps have you taken? Please provide exact steps? Why are you using recovery mode? That isn't a step in the instructions.

@thantien what box? what build? What steps have you taken?

I don't know if this is your problem, but in the text you copied into your first post you are missing a \ after the first line

Post the log of your build

Your title is misleading. You don't want to disable Ethernet. What is happening is that uboot is failing to boot and as a last resort trying a network boot. Your problem is that you can't just take a build for a different box and expect it to work for your box. In general TV boxes are not supported by Armbian. You need to search the forums or the wider Internet to see if anyone has had any success with installing on your specific box and how to do that. If no one has them you always have the option of adding the support for your box using the Armbian build framework, but that is a daunting task if you are not already familiar with porting Linux and uboot to sbcs/tvboxes.