SteeMan

First start by reading this: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Note that of the non-supported tv boxes, allwinner is the least supported. Second note is that the H6 and H616/H313 are different allwinner cpus. You can't use a build for one with the others as the dtbs are very different.

A note that cheap android tv boxes are known to report fake data to the os. The best think to do is to open the box and directly inspect the board/chips. But even then, some manufacturers will alter the markings on their chips to falsify the board makeup. The goal for TV box manufacturers it so produce the lowest price box, so corners are cut everywhere. That is why it is impossible to support these boxes well, as any two boxes can have different internal components.

@Jaume Palomer García Please detail what box do you have, what build you are using, what instructions you are following, what dtb you are using and what uboot. You haven't provided any information that would allow anyone to help you.

armbian-config doesn't work for these amlogic tv box builds. Please follow the instructions here: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

What hardware? What dtb are you using? What exact build (filename)? What instructions to install did you use?

Did you install the armbian-firmware-full package?

Are you using Armbian? What version?

That is not the full log. Look at the last line of the output: Please post this.

Mpved to the correct forum.

@ison You are using the wrong image. No TV boxes I'm aware of support uefi. Please read the following two FAQ items: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

What build are you using?

There is a bug in armbian-install in this version that will likely cause your scenario to fail. You can manually fix/verify the issue by looking at the armbianEnv.txt file installed on the nvme drive and look for the uuid of the drive. It should be prefixed with UUID= (compare to the armbianEnv.txt on your sd card). Or you can use a nightly image which will already contain the fix to armbian-install and retry.

@Thang The weekly images should work. Are you installing a weekly image, or upgrading to it? If you are upgrading, then you will need to edit the extlinux.conf file and change uImage to Image.

@tepo The Banana PI M2 Zero is not supported by Armbian maintainers. It is "Community Support" status, which means that it is available for the public at large to support. There is currently no one in the community that has stepped up to say they will be a maintainer for that board. So the board is languishing for lack of support by anyone interested enough to contribute. Armbian is first and foremost a platform for building images for the many different Arm based boards that are out there. But with limited resources (both people and money) only a handful of boards get officially supported by the project. The majority end up supported (or not supported) by the community of volunteers interested in the particular boards.

Maybe if you provided more than a one sentence description on what your problem is and what you have tried, you would get a better answer. u-boot logs are really useful in debugging booting issues for example.

Here is the line from the script install-aml.sh: mv -f $DIR_INSTALL/u-boot.ext $DIR_INSTALL/u-boot.emmc No u-boot.mmc

If you are using the community armbian build, then it will first try to boot from the sd card if present and then boot from emmc if no sd card. I don't know, I've never tried it. If you install to emmc, you should have a backup of your android firmware and know how to reinstall it if something goes wrong. Otherwise your box could end up bricked.

I'm not aware of anyone actively (or even within the last few years) working on these old 32bit amlogic cpu based TV boxes.

@kaattaalan What version of armbian are you using? Also you mention u-boot.mmc, there shouldn't be a file by that name, was that a typo?

That sounds like you have then properly enabled multiboot and it is trying to boot from the sd card. Have you done this step to enable the boot process from the sd card?

That is pretty good. Better than many tv boxes. Have you read: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Have you tried all the meson-sm1-* dtb files? The idea is to find the one that is the best fit for your hardware where there isn't an exact match in the linux kernel. Maybe. dtb files are kernel version specific (but not alot changes between linux versions) so if the dtb is from a recent linux kernel it may be compatible. There would be no harm in trying.

Moved post to new topic

@iloveomv The location you posted is a fork of armbian. Their developers use the Armbian name without permission. We discourage people from posting links to that project in these forums as we can't help people with those builds as the code isn't armbian. Because they use the armbian name people get confused and think they are using armbian code and come here for support. Those developers do not participate in these forums, nor do they support armbian development. Feel free to PM the the information but direct followup questions should be directed to their support methods.

Moved post to correct location

The install instructions has a link to the current build