Thank you very much for your help!
1 Like
Bammm! It works! Thank you very much!
I downloaded full HD movies in Mpeg2, H264, H265, V9, AV1 from
and tested them with your 22-NO dev build. They seem to play in hardware flawlessly. Nice.
What will be the upcoming path to preserve this working system? Can I update to 22 piers nightlies in the next days and stay on that dtb?
1 Like
To find out if you have a box with an S905X5M or an S905A chip, here’s a simple way: On Android, enter the following query in a terminal app:
cat /proc/device-tree/amlogic-dt-id
Result for my box: s7d_s905a_bm221-4g
So, it’s an S905A.
Or in CE checking serial number (third byte S905X5M 01, S905A 03)
dmesg | grep -i serial
Or dump Android dtb.
Or DeviceInfoHW.apk on Android
It’s simple. It says S905A or S905X5M there.
This does not require terminal knowledge.
From build 20260323 this device (and SoC) is now supported.
5 Likes
Hi ,
I just wanted to report a small issue. On X96M200 boxes (both S905A and S905X5M variants), when trying to boot CoreELEC from the SD card using the newest recovery.img, the system doesn’t start.
It looks like the factory U-Boot on these specific boxes is restricted and doesn’t support the autoscr or source commands. Because of this, they rely entirely on the recovery.img fallback to boot from external media.
When using the newest recovery, the UART log shows a kernel panic related to usb_phy_init right after it tries to load the kernel.
As a test, replacing the new recovery.img on the SD card with an older version fixes this, and the boxes boot up perfectly.
I just wanted to share this information in case it helps with future updates. Thank you for all your hard work!
(This could have gone to, say, the Amlogic-NO discussion thread)
1 Like
congera , your post is not very clear.
You are saying recovery.img from current nightly doesn’t boot? Which means fresh device can’t be set with nightly?
You also mention autoscr and source commands: if they are removed then fresh device can’t even boot CE even if previously set up with older recovery.img ?
On X96M200 boxes (S905A and S905X5M), the factory U-Boot is restricted by the manufacturer. It simply does not understand the autoscr command.
Because of this, the box cannot boot using aml_autoscript. Instead, its only way to boot CoreELEC from the SD card is by using the recovery.img as a fallback.
The issue: The recovery.img that gets written to the SD card when burning the CoreELEC image was changed recently (I’m not sure of the exact date). This new recovery.img causes a kernel panic (usb_phy_init) on these boxes, so it doesn’t boot.
If I manually replace the new recovery.img on the SD card with an older version of recovery.img, CoreELEC boots perfectly.
I just wanted to report that the newest recovery.img breaks the fallback boot method for these specific boxes due to a kernel panic. Everything else on the SD card is fine
Got it.
recovery.img is build just like real kernel.img. The difference is that it is very stripped.
Not long back we bumped the kernel version which introduced something. Will look in next days.
Thanks for the explanation.
1 Like
Thank you very much!
This is something that owners of these new s905x5m devices should be reporting to the companies like x96. If you ever decide that you want to use your box for another open source project, that project may not be willing to go to the extra effort of creating a custom recovery.img.
Complaining to x96 about these missing commands a year or more from now isn’t going to matter because they will have moved on to selling their next box.
Adding the autoscr and source commands back to uboot is a simple 1-2min job for the developer.
Of course I agree with that.
I just indicated here. Unfortunately, manufacturers usually do not deal with this.
I indicated here because I don’t know what U-Boot the other manufacturers use.
All the s905x5m device manufacturers are using the same uboot source provided to them by Amlogic. Amlogic probably made the choice to remove autoscr and source commands by default, and the manufacturers are compiling it as is because they aren’t aware there’s a problem.
People who have bought these boxes or are considering buying, need to report this to the manufacturer. One person so far has contacted BuzzTV, and BuzzTV is looking into it. But that will have no impact on x96 boxes, x96 compiles their own uboot.
The Odroid C5 (s905x5m) already fixed this problem a long time ago, their uboot has the commands.
20260317 is no longer good. And neither does the one after that.
20260314 is the last one that works.
1 Like
Yes, with linux 5.15.196 on 15.3.2026.
1 Like
In few days I’ll have x96m200 DTS for Android from manufacturer (original reference board for X96 devices is AData company and they’re selling it to OEM/ODMs). ODM/OEM can replace components like ddr, emmc licenses for widevine, hdcp etc. I’ll share it with @Portisch so he can compare it. I won’t have time to test it yet, maybe over weekend this one or second one.
Did you tried latest nightly? I though this issue was solved with build 20260423.
I checked the DTS for S905A and it’s same as S905X5M, so it should work.
But maybe in future it does change…
Has anyone been able to install or copy the CoreELEC installation to the eMMC? (I wouldn’t mind deleting everything related to Android; I’m only interested in Linux with Docker itself).