SteeMan

@Victorhtf yes it is always located there. What build are you using?

It sounds to me as if you may have used armbian-config to copy the root filesystem to emmc, but didn't copy the boot environment over. So you may have had a working environment with boot from SD, but everything else on emmc. Then when you forced the change of the boot uuid, you now have a broken system as there may not be a boot environment installed on emmc. But since I don't know the exact options you used in armbian-config this is only a guess.

@hex_messer submit a PR. https://docs.armbian.com/Process_Contribute

@Mancas Welcome. You should start here: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first and then here: https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus/

Updates to the website can be a manual process for many things. And with any manual process, there are bound to be many mistakes. The most accurate info for any board is to look in the board config file. The board maintainer is automatically maintained from a database of maintainer information. $ grep BOARD_MAINTAINER orangepizero2.conf BOARD_MAINTAINER="krachlatte AGM1968"

I would suggest you read some of the other threads on the orange pi zero 3 in this forum. This board is very new and under active work. But don't expect everything to work yet.

Moved to Community/Unsupported and added orangepizero3 tag.

The answer to this question will likely come out of the 24.02 release planning meeting: https://forum.armbian.com/topic/33605-armbian-2402-release-planning The approval of the developer community is a requirement for standard support of a board. I would suggest you attend this meeting. One thing you may not be aware of that is in the background is the relationship (or lack thereof) between Armbian and Orange Pi. You might notice that they were not mentioned in the Vendor Appreciation section in today's Armbian Leaflet #18. Along with having a maintainer for a board to be supported, it also needs: For a SBC to be considered supported: - must be beneficial to the Armbian project - Armbian team must confirm and agree upon all supported boards statuses Currently I would say the lack of a relationship between Armbian and Orange Pi will make it difficult to demonstrate how the added support workload is beneficial to the Armbian project. (my opinion, not official statement) The zero 2 currently has two maintainers listed.

Anyway you are comfortable with. Armbian comes with a utility called ddbr to create a backup.

It works for me. When I mount that image I have a fully populated armbi_boot partition.

@CODER2127 in the same directory /boot. I have updated the instructions to clarify

The item description pretty much has all the information you need: Q Plus Android Box H616 Quad-core So the box name is the Q Plus And it has an Allwinner H616 cpu

When you have been involved with Armbian for a length of time (and read a few of igor's rants 🙂 ) you will realize why what was said here will not be received well by many within Armbian. It isn't that what you are saying isn't a reasonable comment. The problem is that Armbian is under resourced by probably an order of magnitude. Discussions are continually occurring on how the project can survive let alone move forward. Many of those conversations involve discussing how more can be done with less resources, ways to cut features/scope to make what exists manageable. So by you saying to "put [more work] onto developers in Armbian is far better than ..." you are hitting a nerve. In the current environment that will never pass muster. Any proposed solution needs to maintain or reduce developer work in the long term. So any feature suggestion is going to be measured first against that metric, then secondarily by the merits of that feature. This whole dtd discussion is fundamentally a request for a new feature for Armbian. Regardless of the merits of your focus on the end user experience, that isn't the way Armbian has handled dtbs in any of the existing boards that are supported. I'm not saying that what exists is good or desireable, but it is what it is. Can it be improved, sure. Can it be improved and at the same time not increase maintenance costs going forward, maybe.

I have no other suggestions. I've not run into your situation before. And no there is no way to restore a firmware via uart.

What do you mean by this? You have the usb burning tool running when you plug the male usb to male usb cable into the tv box correct? And also you are not connecting the tv box to power, but letting it be powered from the usb cable?

There is no work being done currently to support this ancient cpu for TV Boxes. You might be able to find something four or five years old by searching the archives.

Have you tried all of these things I have recommended? What different versions of usb burning tool have you tried?

How do you know the box is going straight to uboot? When you are connecting usb burning tool from a pc, there are no other items connected to the box other than the male usb to male usb cable.

Yes as sure as I can be. I have replaced u-boots on emmc and still been able to run usb burning tool to recover the android firmware. But there are hundreds of different TV Boxes, so I can't speak for all, just the ones i have worked with.

Note that this thread is archived. Current information can be found at: https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus

Here are the reasons to run off of emmc: emmc is faster than SD emmc is more durable than SD. Both emmc and SD have limited lifes due to the number of write cycles they support. But emmc should last longer than SD before wearing out Reasons to stay with SD: The ability to pop out the SD card and replace it with another or to move it to another device to read/write the contents is sometimes very useful SD cards can give you more storage than the onboard emmc

This issue should now be fixed. The s905x2 and s905x3 chain loaded u-boot has been updated to address the issue introduced with 23.02 and later builds. Any build after 2023/01/31 should incorporate the fix (so the current community builds as of today have the fix) and this will appear in the 24.02 release builds.

The uboot has nothing to do with the Amlogic burning tool, the tool connects before uboot starts. I have needed to try different versions of usb burning tool for different boxes. Tried different usb ports (generally only one usb port will work with the tool), And sometimes need to press the reset button for different lengths of time to get it to register.

So I guess getting back to your original question: Did you make a backup of the EMMC before you overwrote it? Do you have an original android firmware for your box? Yes you can restore the box, but how you do that depends on what you are restoring from.

Interesting. I didn't know that existed. It must be a wrapper for the functionality available through armbian-config (or vise-versa). Either way the standard Armbian functionality doesn't work with the amlogic TV box builds and will not leave you with a working EMMC install. That is why the amlogic TV box install instructions give the correct alternative. Regardless of that, your logs show that you are booting from sd card. And the state of your EMMC shouldn't cause the type of error you are seeing.