SteeMan

You shouldn't be getting into android recovery. How did you burn the image to the SD card? On what platform? The fact that I'm seeing things like "System Volume Information" and "box-config" which aren't directories that should exist on an Armbian image, it looks like something strange has happened to your SD card image.

Get an SD card. That is what 95% of people use on these boxes. Also if you want help, you need to be a lot more detailed than 'but reported it couldn't find the installation package'. Logs/Screenshots are needed to even begin to help.

Have you tried all of the uboot binaries as I suggested above? Also, you didn't answer my question about SD card. Does the box have an SD card slot and have you tried that?

Does the box have an sd card slot and have you tried booting from that? (That is the common method). Also are you sure the box has an s905x3? Have you opened the box and inspected the chip? You might want to try all the uboot binaries just in case.

The s905x3 one. Also, how are you booting this? You say it doesn't recognize usb, so what are you using to boot Armbian?

The screen shot you have shows you are using the Ugoos X3 version of uboot. That will not work as that is specific to that box.

moved post to correct forum

I don't own that box so I can only give you generic help. You really would need to hook up a usb-uart adapter to access the uboot debug output to see what is happening. The second thing I would say is that I have no idea what ophub builds do as they are not Armbian builds, ophub is a fork, they don't contribute to Armbian development nor do they participate in these forums. So per the Armbian amlogic TV box instructions, the boot environment must be a clean android boot environment. Installing or running any other distribution may cause Armbian to not boot. So I'd recommend either reinstalling a clean Android image to test from, or investigate any differences in boot scripts to see what might be going on. But again getting access to the new boot serial console would help a lot.

You need to apply the patch to newer sources to build a newer uboot. But the patch will need to be modified (ported) to newer sources as code in uboot changes. That is the whole point of the suggestions I'm this thread. Port the patch to newer uboots and build them to see if newer uboots fix the problem.

Please be specific, what patch are you referring to?

@Jugo Slaven it seems you are running Android not Armbian. These forums are for Armbian Linux not Android. You should ask your question at a site that deals with Android.

@Jugo Slaven What version of Armbian are you running?

Have you mounted the image to verify that the problem isn't with the image? (You assume that the issue is with imager but you should first verify that the issue isn't with the image that imager is copying to the storage media.

As a moderator having watched this thread, I'm going to close it down, as I don't think anything else productive will be said at this point. However I do want to thank both @bedna and @eselarm for their time and effort to help. Armbian appreciates all the volunteers who make these forums possible.

You need to provide a lot more information. Lets start with logs/screenshots of what you are experiencing. What Box, what uboot, what dtb are you using? What armbian image are you using?

You are not running Armbian. Ophub is a fork of Armbian. They do not contribute to Armbian development nor do they participate in these forums. You need to direct your questions to their support sites.

What about the step of selecting the uboot?

Those are not the correct instructions. Please follow the instructions linked off of the download page: https://www.armbian.com/amlogic-s9xx-tv-box

truck.xxx builds are daily/weekly rolling release builds and are not archived.

First some logs would be helpful. You may have to solder a usb-uart connector to the debug uart pads on your board to get boot log information. Without knowing what is going on, diagnosis is difficult. Second, you don't say which u-boot you are using. Can you provide that information? Finally, why are you using the wetek-play2.dtb for this box?

That is true that there are images that target server vs. desktop. But they share the same kernel. I find what you are working on an interesting idea. Good luck getting it working.

Ultimately, once you have this working, you should submit a PR and justify the inclusion of this feature with details on the pros and cons.

How much size does it add? Remember there are a wide variety of boards supported some with limited storage and ram.

@naceur abdelkader Your post has nothing to do with Armbian. Please find a more appropriate site to ask your question. This site is for Armbian linux.

Have you tried all of the gxm dtb files? Per the instructions (https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus)