SteeMan

@ioncube I think you mean legacy 5.10 (not 5.1). The code to build legacy 5.10 is still there (https://github.com/armbian/build/blob/b8dbe607e59a9eb23c70f129b60e2df2b08cdb01/config/sources/families/rk35xx.conf#L19-L27) But as igor commented above: So it is unmaintained and may no longer build. To use the legacy branch you need to specify it on the command line: BRANCH=legacy

Moved post to Raspberry Pi sub forum and added the Rpi5 tag.

Moved post to Community Maintained Alwinner

Moved post to the Kahdas Vim1s forum

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Have you tried the standard (not minimal) image? Where the other environments also minimal images that worked? Specific versions of images would be helpful info.

@NickB 6.1 is a 'vendor' kernel and 6.10 is a mainline kernel. Generally mainline is far behind a vendor kernel in support of any specific CPU.

Moved post to the community/unsupported section as this is not a supported board. And reset the tag to 'Other'

Start here: https://www.armbian.com/amlogic-s9xx-tv-box/

Moved post to the correct sub-forum (Amlogic TV Boxes)

You still haven't provided even basic information about your box. I for example don't know the name or even what CPU you are using. And as Werner indicated what image you are trying to use.

Well, I'm keeping the Amlogic TV box builds alive as I have a bunch of personal servers running on that hardware.

Have you tried installing armbian-firmware-full?

@c0rnelius Have you submitted those dts patches upstream? and/or should they be added to Armbian? I don't have those boxes so I can't test, but maybe helpful to others.

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first I'm not aware of this working on any boxes I have.

Moved post to Community Maintained section.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

The ones with Rpi4 in the name. But there aren't any right now because apparently the builds are failing for this board.

https://github.com/armbian/os/releases

That is the stable version not the rolling releases. The rolling releases would be 24.8 (not 24.5)

You need to provide the exact name of the image you downloaded. You question can't be answered from the information you provided.

@Yfrain Gelvis These are forums for Armbian not Android.

It looks like the mirror you are using was (is?) out of sync. The mirror I am routed to has the files: http://mirrors.jevincanders.net/armbian/apt/pool/bookworm/b/base-files Try apt update again to fetch current content from the mirror and if that doesn't work, try a different mirror.

@Andrea what is it you are trying to accomplish? The reason I ask is that given what i see from those systems there are some significant challenges in having a boot A and boot B. The first being that u-boot lives outside of the partitions at a specific location on the device(SD/emmc/etc). So you really only can have one uboot, so that will be an area that won't be possible to have something to fall back to if an update of uboot fails. The second issue I see is that Armbian and the underlying Ubuntu/Debian push frequent software updates out via apt. Their is no concept of firmware updates that are complete sets of updates, you get a few updates each week. Which is good for security reasons as security updates are made available as soon as possible. But for what I suspect you are trying to do, you will need to create a mechanism to periodically package all available apt updates into a firmware bundle to get installed into your other partition. But I'm just guessing on what you are trying to accomplish. So a better explanation of your goals might be helpful.

Having said that, if those upstream changes don't fix the issue, then there may be a deeper problem that could be Armbian related.