SteeMan

Moved to the allwinner forum

Closing this. This isn't going anywhere good. Both sides have made their points.

What steps are you doing to get this working manually? What is the overlay file you are loading (trying to load), and where does that file exist on the system?

What is your goal? 25.02 is a stable release. There is no 25.05 stable release yet (that will happen towards the end of next month). So what is out there now are daily development rolling builds of 20.05. So if you want to track development then this would make sense (note the use 0f the word 'daily' there, things can change that often, and these changes aren't well tested yet), but if you want tested stability then you should wait until the next stable release comes out.

@iTux Your posts are not appropriate for Armbian forums. You are using non Armbian code. You should post your information in the channels that they provide. Ophub is a fork of Armbian. They do not contribute to Armbian development, nor do they contribute to these forums. They use the Armbian name without permission and cause significant confusion as a result. (Like in your case where you think you are using Armbian and you are not).

I think this is your underlying issue. Focal was dropped from support a year ago (by both Ubuntu and Armbian). So the underlying packages you need are likely no longer in repositories.

If you look at the boot log, the android firmware is first looking for s905_autoscript on the SD card fat partition. So you should be able to create a boot script by that name to get the native emmc uboot to run and boot what you have on your SD card. (Your printenv shows the boot order is determined in start_autoscript, first mmc then USB then finally emmc). If this ancient uboot is capable of booting a modern Linux kernel you should be able to make this work with the proper boot commands in the s905_autoscript file.

Moved

That is not an Armbian image, you are not using an Armbian build. You should ask for help where you downloaded your fake forked image from.

There are multiple threads discussing RK3566 support on TV Boxes in this forum. You should read that content first if you haven't already.

It looks like your box is Rockchip RK3566 based, moving to the Rockchip TV Box sub-forum

Whenever you are comfortable with that. You could brick your box. Unlikely, but there are so many different tv boxes out there that there is always a chance your box is somehow different than common ones. Since the boot environment starts from what is on emmc, if you screw up the emmc completely, your box is bricked. (You should still be able to recover by using amlogic tools to reinstall an android rom, but...) No limit that I can think of. You have that all correct.

Moved the post to the correct sub-forum.

Moved

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

Some basic information would be very helpful. What image are you using (exact file name for the image please). What install steps did you perform? Can you include a screen shot/picture of what exactly you are seeing on screen? A capture of the boot log (either via uart or pictures of what is on screen can be helpful too).

You really should create a device tree overlay that just changes that attribute. The biggest downside of what you have done, is that every time you upgrade the linux kernel your change will be lost (as the new dtb file from that kernel will be installed) and you will need to redo this work with each upgrade.

moved

I'm sure it is AI powered, so if you asked it to, I'm sure it would

@arboniid Can you provide the exact filename of the image you are using? Also the name of the SBC you have that you are working with.

You need to make sure that any disk IDs get updated to the new values for you target media. Look in your armbianEnv.txt file and possibly your /etc/fstab files. But in general to solve booting issues you will need a USB uart adapter to see what is happening during the boot process that is failing.

Have you tried installing the armbian-firmware-full package? (By default armbian ships with a slimmed down set of device firmwares, but the -full package includes all the ones from mainline)

Yes I had thought of that, that should work.

yes

All of this information is very helpful. Here is what you need to try. Look at the file aml_autoscript in your armbian /boot folder. This is the script that should get run when the reset button is pressed during poweron on a regular amlogic based android tv box. But since you now have access to the uboot console, you can enter these environment commands directly. If you start with the 'setenv bootcmd... and end with the 'saveenv' you will have modified the uboot environment to run armbian from sd or usb first, and then fall back to your other os on emmc. In looking at your current uboot environment, the only command that will be modified from what you have is the 'bootcmd'. In looking at what you have both the armbian and your current bootcmd fall back to run 'storeboot'. But by installing the armbian version you will loose the abiltiy to boot osmc from sd or usb, which you probably don't care about, but I thought I would mention it.