SteeMan

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

? - What sbc are you working with? Generally you burn to SD card and then use armbian-config to move that install to emmc when you are happy with it.

This forum is for Armbian not arch. This sub-forum is for amlogic based devices (not rockchip). Everything about your post is not appropriate. Please post arch questions in an arch forum. Don't hijack a post that is completely unrelated to your question.

Upgrade to what newer version? A userspace version (i.e. ubuntu focal to ubuntu jammy) or a kernel upgrade (i.e. 23.02 based armbian kernel to 23.05 armbian kernel)? For userspace it is recommeded to do an install, as upgrades are not tested (but I just did a focal to jammy upgrade last night and they generally do work). For the kernel, you can just do apt update/upgrades to continue following the builds over time (assuming you don't have your kernel frozen in armbian-config).

@helios thanks for posting that. One thing that has changed between the two versions is the name of the kernel image. It used to be uImage and is now Image. Can you look at the extlinux.conf files on the two versions to make sure they are changed appropriately for the kernel name change?

The u-boot-s905x2-s922 file hasn't changed. So it shouldn't be necessary to copy that. Can you look at the file size of the two and also run diff on the two files. Again they should be the same as that file hasn't changed. If they are different, then something in the build process is causing a problem.

Did you patch the Makefile so they build? For example a patch that adds dtbs: patch/kernel/archive/meson64-6.2/boards-g12-add-spi-nor-flash-enabled-dtbs.patch

Can you add the version information for the builds you are trying that are not working. I'm otherwise just guessing.

*minimal* is the key there, it really is minimal, you need to install armbianconfig if you want to use it: sudo apt install armbian-config (Note: since you have installed 23.05, the apt repositories don't yet have the 23.05 packages available (some issues still being addressed) so the apt install may not currently work until that is resolved)

userspace app issue, moved post to correct forum

These instructions are for Amlogic CPUs for TV Boxes. Note: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attempting the install. coreelec changes the boot environment in ways that are incompatible with these Armbian builds. Download links: Weekly Community Rolling Builds: https://www.armbian.com/amlogic-s9xx-tv-box/ or build your own image using the Armbian build framework Once you download your chosen build, you need to burn the image to an SD card. Generally balenaEtcher is recommended as it does a verification of the burn. Also be sure to use high quality SD cards. Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card. In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. There will also be a extlinux.conf.template file to use as a reference. You will need to add a line into the extlinux.conf file for the Device Tree (dtb) file you will be using for your box. Place this line before the APPEND line as shown in the .template file. Basically you need to have the correct dtb for your box. You may need to attempt to use different dtb files until you find the one that works the best for your box's hardware (there are a bunch of dtb files in /boot/dtb/amlogic/... to try depending on your cpu architecture and hardware). It is unlikely that there will be a matching dtb file for your TV box. The idea is to find the one that works best for your box. This may mean that you try booting with different dtb files until you fine one that works good enough for your needs. By searching the forums you will find information about what dtbs other users have found work best for different boxes. Because you are booting from an SD card, you can easily try different dtb files. The dtd files are named by cpu family. So for example dtb files for the s905x2 cpu are named meson-g12a-*. Below there is a table that shows the identifiers for each familiy (g12a for s905x2 in this case). Next you need to copy the correct uboot for your box. This is needed for how these builds boot on amlogic boxes. There are four different u-boot files located in the /boot directory: u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922, u-boot-s905x3 You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named u-boot.ext in the /boot directory So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext: cp u-boot-s905x-s912 u-boot.ext (See table below for more details on which u-boot to use for which cpu) Once you have your SD card prepared you need to enable multiboot on the box. There are different ways documented to do this, but the most common is the "toothpick" method. The "toothpick" method means to hold the reset button while applying power to the box. The reset button is often hidden and located at the back of the audio/video jack connector. By pressing that button with a toothpick or other such pointed device you can enable multiboot. What you need to do is have the box unplugged, have your prepared sd card inserted, then press and hold the button while inserting the power connector. Then after a bit of time you can release the button. (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times). You should now be booting into armbian/linux. Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card. After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). (Note: Installing to emmc has some risks of bricking your box. Don't do this unless you feel you understand how to reinstall your box's android firmware) You install armbian to emmc by running the shell script in the /root directory: install-aml.sh. Note: It is not possible to install into emmc on boxes with the s905 cpu (s905x, s905w, s905x2, etc however should all be supported). It is recommended that you make a backup of emmc first. Also be prepared if anything goes horribly wrong with your emmc install to reinstall the android firmware using the Amlogic USB Burning Tool to unbrick your device. If you have or can find an original android firmware on the internet and you can generally (but not always) recover a bricked box using the Amlogic tool and the original firmware file. Mapping from CPU to uboot and dtb: u-boot-s905 s905 - gxbb u-boot-s905x2-s912 S905X - gxl S905W - gxl S905D - gxl S905L - gxl S805X - gxl S912 - gxm A311D - gxm u-boot-s905x2-s922 S905X2 - g12a S922 - g12b u-boot-s905x3 S905X3 - sm1 Not supported or not tested S805 - S905W2 - S905X4 - S805X2 - s4 A113D - axg A113X - axg Note: Followup posts in this thread should be limited to comments to improve or better understand these instructions. Other issues should be posted as new questions in the Amlogic CPU Boxes sub-forum.

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box). You can now build your own builds directly with the Armbian build system. This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework. If you are not familiar with the Armbian build system check out the Armbian developer documentation. If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see. I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well. Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.