devmfc / amlogic-bootscripts-armbian Goto Github PK

Hey [@devmfc],

I hope this message finds you well. I wanted to express my gratitude for your tutorial on installing [Armbian] via USB on TV Boxes with S905X3 and S905X2 processors. The tutorial worked flawlessly during the USB boot process.

However, I've encountered a challenge when attempting to install the system on the Box using the command "/root/install-aml.sh". After completing the installation, upon rebooting the device, the Box starts but remains stuck on a black screen.

To troubleshoot, I initiated a USB boot and accessed the /boot partition on EMMC. I noticed that during the installation process, the script copies /boot from the USB, but it doesn't add the files "aml_autoscript" and "s905_autoscript" as outlined in your tutorial.

In an attempt to resolve this, I manually copied these files to the /boot partition on EMMC. Unfortunately, this didn't resolve the issue, and the Box still fails to start after installation.

I'm using a BTV B11 TV Box with S905X3 and another with BTV Express S905X2. Both boxes boot successfully via USB, but post-installation on EMMC, they seem unresponsive. Is there any specific configuration or step I might be missing to ensure the installation on the TV Box works seamlessly?

Hi can i using this method to boot from usb or sdcard without using emmc ?
Im using HG680P ...

I'm curious if the existing tutorials are suitable for the S905X4, S905W2 and S905Y2 processors. Additionally, I would like to know if it is possible to use the following DTBs to run an Armbian image:

Experimental: S905X4 (Meson SC2)
Experimental: S905W2 (Meson S4)
Experimental: S905Y4 (S4 Meson)

Any information or guidance on this would be greatly appreciated. Thank you in advance!

Hi everyone,

We're currently using the new bootscript method for models S905X, X2, and X3, and we're encountering an issue. When we use the provided files (aml_autoscript, s905_autoscript) and perform a native installation on the TV Box, we notice that every time the TV Box starts up, the wallpaper does not get enabled and the background remains black.

Has anyone experienced this issue before? Is there a chance that a service might be getting disabled during startup, or is there a way to ensure that the wallpaper is activated on boot with this new method?

Any insights or suggestions would be greatly appreciated!

Thanks in advance!