SteeMan

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).

What internet connection are you trying? wifi or ethernet?

This is one problem. You need the boot loader from android on your emmc in order to boot armbian following the instructions you mentioned. This is not a build suitable for this box. Follow the links in the instructions you mentioned for the correct armbian build.

As that FAQ post states, don't expect to have working wifi on these tv boxes. (I don't have working wifi on any amlogic tv box I own). As far as the usb wifi, make sure you install the armbian-firmware-full package (as the default install only contains a limited number of firmwares to keep the install smaller).

Pull the build environment, make the changes, test and then submit a PR to get them incorporated

Moved to non-board specific forum, as this isn't a board specific question.

@Alex Peng https://forum.armbian.com/communitymap/?filter=getByUser&member_id=12900

I personally have multiple of that box, so I have no need for one. And currently no one else is contributing to the amlogic TV box code base in Armbian. So I'm not sure there is a need for them. But if someone wants one, they are welcome to respond to your post. Generally, however, TV boxes are cheap and easy to purchase, it is developers and their time that is expensive and in very short supply.

@Maxxim Thanks for the report. The boot partition is created as vfat. I have noticed that s905x2 and s905x3 boxes are not booting with the 23.05 builds, but I thought the issue was with the u-boot files. Your report potentially points into a different direction. I don't know when I will have time to look into this. But this is community supported software so any contributions are appreciated.

Since I don't have an s905l2 box, I'm not really in a position to integrate/test changes for such a box. If someone want to submit a PR that can test, I'd be happy to get it integrated. @Lavacat Note that your last post wasn't approved, because the site you mention is a fork of armbian that uses the Armbian name without permission and they do not contribute to the forums nor to armbian development.

@callegar The 23.05 packages have not been released to the apt update repositories yet. There are issues being worked on. No ETA. The latest packages available are 23.02 based.

Since you are installing a Ubuntu kernel not an Armbian kernel, (and these are Armbian forums), you should ask your question in a Ubuntu forum.

Create a file named aml_autoscript.zip in the /boot directory and then try selecting that in recovery. The file should be empty. Since you are using the 23.05 builds, their are reports that the u-boot-s905x2-s922 file isn't working in that release. If you run into that issue you might want to go with an older build (something from 23.02). But first you need to get past the 'recovery' problem, before you will possibly run into the u-boot problem.

First read this: Then you need to google and find out what CPU your box is using (note many boxes have the same/similar names), so start by finding boxes that look like yours and see if you can find spec listings that tell you the cpu. If that doesn't help, opening the box and looking at the physical chips. Once you determine the cpu then you can search the archives for others working on your type of box.

You don't need to be 'accepted' to help. Anyone can submit PRs and contribute. I would recommend just getting active on the forum helping others, and any code improvements you can make for the device can be submitted as PRs.

Moved to the correct forum. https://www.armbian.com/nanopi-neo

If you submit a PR with the dtb changes they could be in base Armbian.

You already have the answer to this question This is open source, you can report the problem and hope someone volunteers their time to research and fix (which is realistically unlikely to happen any time soon), you can dig in and fix it yourself and become part of the solution by contributing back to the open source communities, or you can pay for/hire someone to fix it for you. Those are realistically the only way things get fixed in open source. Complaining about something and calling into question the volunteer work others do to provide you something for free, isn't going to motivate anyone to help you.

@2hry You should post your question in this thread:

@2hry it looks like you are booting libreelec, these forums are for Armbian. Please ask in a forum site for Libreelec, we can't help you here

The balbes150 builds where never upgradable. You need to use official builds for upgrades.

Standard process, apt update/upgrade, assuming the kernel isn't frozen in armbian-config. armbian-config also has multiple options on switching kernels (current / edge, stable / nightly builds, etc)