SteeMan

@John Taylor I finally had some time to test this today and it is working fine for me. I built a fresh image on an ubuntu laptop, copied the image to a SD card, it mounted fine on ubuntu, where I edited the extlinux.conf file and then used the SD card to boot on an amlogic based TV box. You mention etcher as your sd card tool. Etcher in recent versions (recent being the last two years or so) is known to have problems. It is no longer recommended for use with Armbian images. I have noticed that in particular if Etcher is burning a compressed image it doesn't work for me. But I have had some success if the image is uncompressed first. But others have reported that it fails in general.

But it is that extra money that is paying for the better support after the sale that you see in the RaspPi ecosystem. All the other SBC vendors compete on low price and can't afford to provide any support after the sale and rely on open source volunteers to provide their long term support.

@Malay Your board isn't a board supported by Armbian. It is status "Community Support" which means there is no maintainer for the board and it is people like you from the user community submitting PRs that keep it active.

Does this happen if you are running from an SD card also? Or is it specific to running off of emmc?

No clue if it will work. There are hundreds of different TV boxes. It is unlikely anyone here has that exact model So just try. The general rule as the instructions on this site indicate are to try different dtbs until you find one that works the best.

moving to Amlogic TV Boxes as I believe (via a quick google search) that this is amlogic cpu based.

These are forums for Armbian Linux, not Android.

What image are you trying to load?

Have you installed armbian-firmware-full package?

https://docs.armbian.com/User-Guide_Getting-Started/#first-boot

@Maurizio Finesso Try editing on a linux machine instead of windows. I've seen some windows machines not be able to read the boot partition

Moved to the correct sub-forum

This site deals with Armbian Linux not android. You should direct your question about restoring Android to a more appropriate forum

Please provide more information on what your are experiencing and what you have tried already

moved

I just noticed from your screenshot that you aren't using Armbian. You need to ask support questions for non-armbian software from where you got your software. Ophub is a fork of Armbian that used the Armbian name without permission. They do not contribute to Armbian development nor do they contribute the these forums.

So you are saying that when you copy the working SD card install (by working I mean that it has the correct memory amount) to emmc that the problem occurs?

I am going to just point you first to the installation instructions on this site. What dtbs have you tried? What build are you using? What uboot are you using? This is important: have you ever booted anything other than the native android on this box? (Is so read the instructions about that). You really need to hook up a USB uart to get the boot output to understand what is happening. And if the button you labeled blue gets you to recovery that should be the button you want

Note that ophub is a fork of Armbian. They do not contribute to Armbian development nor do they participate in these forums or in anyway do they support Armbian.

Try a build using a newer edge kernel as a test

You can try different dtbs, different sdcards (older/smaller/slower = more compatible) and potentially a newer or older kernel. These failure to read the sdcard have been occuring more and more recently. No one has had time to reproduce and figure out the cause. I didn't see where you mentioned what build you are using, that would be helpful information

From what I see online that box has an s905 amlogic CPU

What settings have you tried? dtb, uboot?

Armbian does not support the s905x4

I don't think you understand how Armbian works. This board is community supported. It does not and hasn't been an Armbian supported board. Given the hundreds of boards out there Armbian only has the resources to officially support a handful. The rest end up being supported by the user community like this board. Thus support is only as good as the community volunteers who have the board and wish to volunteer their time to support it. Armbian provides the tools and infrastruction to make supporting boards easier, but the work still needs to be done by someone for community supported boards like this.