SteeMan

@adrian0541 It would be helpful if you mentioned in this thread which box you have? (I realize that you may have originally posted that information but after moving things around it isn't in this thread). Also to your original question, in the extlinux file you should just reference the /dtb/ directory (not the kernel specific one). The install/upgrade to new kernels will potentially remove that kernel and replace it with a new one and then your box won't boot as that specific file will no longer exist. The files in the /dtb/ directory are a copy of those for the latest installed kernel, so by using that directory you are isolated from upgrades.

@adrian0541 In answer to your question on what uboots map to which cpus and dtbs, I just updated the FAQ instructions with such a mapping (based on your question and other posts in that thread).

Cleaned up the instructions thead, moved this content to its own thread.

Cleaning up the install instructions thread (that thread is meant for comments/corrections on the instructions, not general questions). Moved this to separate thread

What build are you using? What instructions are you following? What uboot are you using? What dtd?

This forum is for armbian. Since you are not running Armbian, you need to post your question elsewhere, someplace that supports your distribution.

Moved to correct forum. Please read: The standard way to load firmwares on amlogic boxes is to use the Amlogic usb_burning_tool along with a male usb to male usb cable (along with the correct firmware of course). There are many examples on the internet of how to use this tool to burn an android firmware on an Amlogic tv box.

@Jumperbillijumper I'm responding to your latest comment in the other thread. The short answer is no, no one seems to have gotten this box to work yet with armbian. And until someone provides the requested info jock is asking for from the beginning of this thread, there isn't going to be any progress.

@avigrinberg The source you are downloading from is not armbian. They are a fork of armbian that uses 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.

That is not an Armbian image (no official images from this site have that name). You apparently are downloading from a non armbian source. What download are you using?

From your log: BUILD_REPOSITORY_URL=https://github.com/Mellow-3D/build 22.08.0-trunk You are using a fork of Armbian that is a year behind current armbian code. We can't help you in these forums as we support official armbian. You need to contact the maintainer of the fork you used for any questions.

Updated title and tags to reflect the board being used

That is the default for armbian. What sbc are you working with? And just to confirm that you pulled the build framework from the official armbian sources? (Not one of the forks that may have different defaults)

This thread is over a year old. Closing the thread.

@theslydog That image is not a release image and therefore isn't archived anywhere. This is known by the word "trunk" in the name. You can always get the latest development builds like that one from here: https://github.com/armbian/community or you can pull the build framework and build your own build from latest source. Release builds are located here: https://redirect.armbian.com/aml-s9xx-box/archive/

@n3o As a moderator of these forums, I have been watching your postings. You are abusing these forums and the people that contribute to them. (Everyone, especially @RaptorSDS and @jock have been very willing to invest a lot of time to help you) However, repeatedly you have been given specific information that you ignore, been given advise that you ignore and then you come back with more and more questions. There are very limited people resources working on Armbian (and even less with TV boxes). You alone are consuming way more developer time than any one individual has the right to receive. This is open source, and therefore users are needed to contribute as much as they consume in resources from the community in order for this to work. This is not a school where you can come to be taught how everything works, demanding the attention of everyone else to teach you. Your latest questions are now venturing into very deep and difficult areas of code (none of which is expected to work on these TV boxes as has been mentioned to you). If you want to continue down the path you are going, you first need to become an expert at these topics on known working platforms, then you can try to apply that expertise on TV boxes. You may not realize it, but the questions you are asking, are essentially asking for weeks if not months of developer help to get working, if it is at all possible.

There are a lot of tv boxes called hk1. What cpu does your box contain? And what build of armbian are you using?

@soned This is an armbian forum, why in your first post do you post a link to a non armbian build? What are you trying to accomplish in this thread?

@thielj its community supported, make the change to the build framework, and submit a PR

That topic is over 4 years old, is written for amlogic based boxes. Nothing there is relevant for a Rockchip based box.

What exact image are you using?

There are multiple tutorials on the internet on how to flash an android rom on am am logic box. Note you will need a male to male USB cable.

I would recommend you reinstall an original Android firmware onto emmc to restore the box back to original configuration and then continue from there.

How are you installing Home Assistant? You may need to install the docker version on Armbian (at least that is how I run it). It has been a couple of years since I installed it, so I don't remember why I chose that method.

wifi isn't expected to work, but with the correct dtb ethernet should. What dtb files are you trying? The dtb file is the file that describes the hardware to the linux kernel, so it is important to have a dtb file that correctly maps to your hardware (or as close as possible).