SteeMan

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.

@FuSan The recommended way to switch kernels.in Armbian is through armbian-config

@Andrea in general, old branches are not maintained and builds on old branches are not repeatable. There are references out to third party sources that change over time. So as @Igor suggested , you should try with something more recent. (We hope in the future to make builds reproducible, there is work recently to that effect)

@Khadas and I thank you for what you have posted. Armbian is always in need of intelligent people helping in anyway they can. Things as simple as reporting your findings help others

Have you tried the Orange Pi R1 builds on the download page you linked to in your first post?

What version do you have installed? That package should be already installed on all builds (except I believe cli minimal builds)

What you may be finding is that in armbian-config you are not seeing any stable releases. That would be because your board is not supported by Armbian. It in in unmaintained/community support status. Community supported boards now only get rolling automated builds, no stable releases.

I'm not sure what you mean by this as armbian-config is available on all Armbian builds.

The info that Igor posted is for an extension to the build system that can be enabled to make an image with HA. You would need to build a custom image using the build framework to utilize this method.

But the root= in the log file is wrong.

Why did you repost the log? Have you changed your root= parameter as was suggested?

The site is forums.armbian.com. It should be obvious that these forums are for Armbian, and this particular sub forum for Armbian on amlogic TV boxes

Your problem is here. Look at the extlinux.conf.template for the correct contents. You need to add an FDT line not edit the FDTDIR line

If you look at the line trying to load you dtb file, you can see that something is wrong. Post the contents of your extlinix.conf file?

I don't understand what you are doing. You don't need to create any /boot directory. Why do you think you needed to do that? And the default password for root is 1234

What build are you using?

What does your post have to do with Armbian?

You don't need to transfer a .img. You use apt update/upgrade like any other Linux system. You can test other dtb files, but I would recommend testing those from the SD card to verify they work. If you test on the EMMC and you do something wrong, then it won't boot and it will be a pain to fix. This the recommendation to do everything on SD card first to make sure you are happy with the system before moving that configuration to emmc as a last step. ddbr is a very simple utility. I don't know if it is properly documented anywhere, but you can do an internet search to see discussions about it.

@Ariel You are looking in the wrong location. Here are where the community rolling releases are: https://github.com/armbian/community

If you have restored the android firmware, then follow the instructions in the FAQ and report back what you have done and any issues you run into (screenshots of errors during boot if appropriate)

So to proceed we would need to get Armbian running on your box, first before asking about HA. Since you have run various other os's, the first note in the instructions is relevant. You need to restore the box to a factory android firmware first before proceeding. Each is will change the boot environment in potentially incompatible ways. So you need to start from a known clean environment, by reinstalling a factory android firmware.

The entire system is now in your EMMC storage, so you just upgrade from there, no need for SD card going forward. Although it can be convenient to boot front an SD card, use the ddbr command to make an image backup of the EMMC once you have everything configured that you can always rollback to if necessary

In general I would expect the root parameter to look like: root=UUID=997635c3-00f2-4eca-aa3d-1bf187651ea3 or root=LABEL=armbi_root (obviously with the correct LABEL or UUID for your root partition)

What dtb are you using? what uboot are you using? what menthod to invoke multiboot are you using? Have you used any other build on this box? In order to help you, you need to provide every detail of what you have done. You originally posted this in the HA thread. So I was assuming that you at least had basic armbian running and you were trying to install HA on top.

So you mention the ophub builds. Just so you know those builds are not Armbian builds. They are a fork of Armbian and use the Armbian name without permission. They do not participate in Armbian development nor do they participate in these forums. So any ophub questions need to be directed to them, not here. So you say the armbian community build doesn't work, but you provide no information on what is failing. I'm not a mind reader so I can't help you if all you tell us is that it doesn't run.