SteeMan

From your log, this is the uboot that is booting and it is trying and failing to boot from your mmc1. I would expect your SD to be mmc0, so it doesn't look like it is even trying to boot from your SD card. So you probably need to replace/update the onboard uboot or perhaps wipe the mmc1. But I don't have this board and really am just guessing. But these are directions you could look into.

@remolaan I think this is the most current info that may help you:

From the boot log, the uboot can't recognize the internal emmc. It appears that the u-boot you are using is one based on u-boot 20-07. I would recommend rebuilding the u-boot-s905x-s912 based on a more current u-boot source. The instructions for doing this are in the readme.txt file in build-u-boot folder. If this helps, then report back here and I can look at including a newer build in the distribution going forward.

These forums are for Armbian Linux issues. This is not the place to ask for android firmwares.

As long as the board isn't dead it is starting to boot. That is why Werner directed you to how to capture the uboot booting messages via a uart connection to the board.

I don't understand what you are asking for. Can you be more specific?

https://docs.armbian.com/Developer-Guide_Build-Commands If I read your post correctly, I think you want ./compile.sh kernel ... which will build the kernel debs but not the full image

I think this line is wrong. I don't believe that the overlay_prefix should be included here, try with overlays=i2c1-pi I seem to recall mention of a bug in armbian-config that was doing the wrong thing regarding overlay_prefix when selecting overlays.

Thanks for investigating this. I have seen this issue reported quite a bit recently. I assumed it was something that had changed at the dtb level. Knowing this helps provide guidance to others in the same situation.

You are not running Armbian. You are running a fork of Armbian. You need to ask for help from the place you downloaded your software from.

What version of Armbian did you install (complete file name)? What do you mean by "the screen stopped working"? Did it once work and then stop? And by screen do you mean HDMI?

I'm not aware of anyplace that would exist anymore.

The documentation is for the current version of armbian-config. You are using an older version. There was a rewrite of armbian-config between what you have and the current functionality.

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.