Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes

Quote from dtech

Sure, you can easily do this with the installtointernal script.

Unfortunately, I haven't used these yet, so I can't comment.

The uboot bootloader parameters can be checked with fw_printenv under my images. However, the installtointernal script does not modify the uboot bootloader or its parameters, it only modifies these partitions:

• /dev/boot: kernel partition,
• /dev/system: the SYSTEM file (root squashfs) goes here, it is mounted as /flash under LE,
• /dev/dtb: the DTB's partition,
• /dev/data: this is data particion, it is mounted as /storage under LE.

Is installtointernal still heavily discouraged on random boards?

New LE even dropped the command.

dtech

I'm trying to watch via analog composite on SDTV, but I get no audio (video is perfect, subtitles work).

Anything I can do?

Did a test in CE 9.2.8 and I get audio and video, but it doesn't handle m3u8 properly, whereas LE 9.2.8.18 handles them nicely, so if I could get analog audio to work it would be perfect.

Quote from dtech

Unfortunately, the GXBB SoC (S905) does not have an internal stereo audio DAC, so it needs an external I2S DAC chip for analog audio output. I admit that I did not test it much because my WeTek Hub and Odroid C2 do not have analog audio output, my WP2 has a faulty audio part, and my KI Plus is also broken.

The last chance is my Videostrong KII Pro, which is equipped with an S905. I will try to check this weekend to see if it has analog sound output.

If you have disassembled your box before, do you have a good quality photo of the PCB in the box? It would be good to know what DAC chip is in it. (But, if the box has not been opened yet, do not disassemble it just for that reason.)

Edit: I tested the analog audio output on my KII Pro and it works perfectly. The DAC chip in this box is ES7134LV.
(I think I have never had so many things connected to this box at once.)

However, the fact that I haven't experienced the issue you describe makes it a bit more difficult...

Question #1:
Is it just the videos that have no sound, or are the system sounds missing as well?

Question #2:
Are you sure everything is set to default?
I mean, the selected output is analog, audio passthrough is disabled and the number of channels is limited to 2?

Display More

You have a lot of ruined devices, I admire that

My box has been disassembled to hell and back, still haven't poked it with a soldering iron tho...

Images as requested + I see your cable management and challenge you with mine:
https://imgur.com/a/pbHDvdk

It seems I have the same DAC, maybe dtb is the issue?
While I wait, I'll go thru all working dtbs that also have working networks to see what is happening.

Regarding #1:
No sounds at all, period.

Regarding #2:
Yes, but I've tried changing outputs too, nope.
Oddly the default when HDMI is connected is "P201 analog" but I still get sound thru HDMI.

Quote from dtech

Unfortunately, I have no luck with the WeTek boxes, but I can assure you that they did not break down by me, unfortunately I received them in bad condition. The WP2 above was probably dropped earlier, but apart from the sound, its other functions work. The KI Plus got a power surge, and I received it defective as well. I tried to repair it, replacing a bunch of SMD components on it, but unfortunately it broke down again a year after the repair.

There is an SGM8905 operational amplifier after the DAC and this is probably the cause of the problem, because it is probably controlled and either does not receive power or is in mute mode.

I found a reference that is only present in the dts of the p201, and may refer to this:

"P201 analog"? I think you checked it under the current version based on the mainline kernel, because under LE 9.2 its name is AML-M8AUDIO Analog.

1. First of all, please update the version you are currently using to this snapshot version:
   https://libreelec.dtech.hu/snapshots/2025…rm-9.2.8.19.tar
   This version includes some diagnostic messages in dmesg that were previously missing (e.g. detected CPU type, used device tree identifier). This is important now, because we are apparently in quite different time zones, so I don't have to ask basic things every time, such as what dtb you are currently using. These will be printed out by dmesg now.
2. Please select Reset above settings to default at the bottom under Settings -> System -> Audio, then turn the volume all the way up to maximum and check if there is really no sound, and give me a feedback.
3. Please send me the output of dmesg or pastekodi.

Display More

Well, bad news, box is fried... or at least in the process of frying - no I didn't turn it on while it was disassembled on that fan grille, nor was it powered to a brick while it was on that fan grille (the entire extension cord was turned off), but maybe that grille shorted something, so oops if it was my fault.

OTOH maybe the power button maybe went kaput from all on/off cycles, because as I start pushing the power button the power LED changes not only green/red but also in varying intensity until I push it completely in, which wasn't the case before.

But then CPU/memory heatsink starts to heat up rapidly, and the scary part is that a noise is starting to come out of it, as in from the board itself (nothing is plugged in except power), it sounds like a quiet coil whine that is increasing in frequency and volume, but I see no coils on that board, so yeah creepy, something will probably go up in smoke if I leave it turned on longer.

I'm not gonna try to (re)solder and/or measure stuff, not worth it, it's a 2nd hand, old, cheap S905 (not even X model) chinesium/russinium box that I was trying to keep alive for almost no other reason other than to see how far can I push it past it's lifetime.

Unfortunately I have no other box to play with, so I hope your efforts here will help someone else someday, and I really appreciate you dedicating your time into this, I truly mean it, thank you.

Hello,

Having two android boxes S905D and S905H, both with DVB-S2 tuner AVL6211, couldn't find a way to make the tuner work am coming from CoreELEC in hope that LibreELEC will do better with this tuner.

DVB-S2 Tuner AVL6211 support on S905D rev c

Android DVB-S2.pdf (1.8 MB) android_original.dts.txt (47.3 KB) coreelecdvb.dts.txt (59.6 KB) coreelecdvb_ser.dts.txt (59.6 KB) After installing CoreELEC…

discourse.coreelec.org

I’ve been trying to run LE 12.2 on an S905D device, but it seems that Kernel 6.x.x is not working properly with it. The system gets stuck on the LE logo during the first boot, and I’m unable to get it running. I mention this because the LE 12.2 download page indicates support for GXL (S905X/D).

So tired legacy 9.2.8.18 generic with kernel 3.14.29, so far my experience has been the same with CoreELEC, any suggestions would be greatly appreciated. Thanks in advance for your help!

Installed LibreELEC-Generic_S905.arm-9.2.8.18.img.gz from https://libreelec.dtech.hu/images/S905/ dunno if this is the correct version to go for since I think S905D can handle newer version like in CE 21.3 kernel 4.9.

Using gxl_p231_2g_dvb.dtb and dvb-latest (from CE got better detection with CrazyCats driver) pastekodi :

https://paste.libreelec.tv/divine-owl.log

We are in the correct path since by default 9.x.x get DVB-S2 tuner detected even before installing DVB drivers
ls /dev/dvb/ adapter0, which is not the case for other builds I tried, the issue is 9.x.x only include AVL6862 driver not AVL6211, maybe we just need to swap drivers but I don't know how to do that.

In attachement are the dtb files of both boxes + S905D box layout + images of S905D box and S905H box.

Any help or guidance on how to swap or add the correct drivers would be greatly appreciated!

Thanks for your time and assistance!

DVB support in the 3.14 vendor kernel generally requires an image that targets a specific box/device. There are quite a few different tuner/demod component combinations in circulation and device-tree describes most (but not all) of the required hardware variables used in drivers, so the individual drivers for a particular manufacturer are hacked to compile a working monolithic dvb-frontend that only works for that box. afl1 made a start on abstracting the missing device-tree bits to untangle code mess, but he went radio-silent one weekend (and has never been heard of since) so the effort stalled and nobody else ever picked up the challenge. The 4.9 kernel codebase is largely a forward-port of the same bad code used in 3.14 (which is a forward-port from 3.10) but newer hardware from that era tends to copy the Amlogic reference designs closely so less variation of tuner/demod combinations and a small amount of code improvement results in a single (still hacked-together) image working for a wider range of no-name boxes.

TL/DR; You likely need the original kernel sources for the box(es) to make a working image because the device-tree files on their own only contain part of the detail needed to make the hardware (as implemented in that box) work properly.

I have the images of the boxes (the S905D image is unlocked bootloader) but I have no idea how to extract kernels/drivers, is it possible to just swap kernel/driver files form images to LE, are there guides on how to do that ?

From this thread : Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes
WeTek Play 2 (a.k.a. WP2) with S905-H SoC (2 GB RAM, 8 GB eMMC) and a modular removable tuner AVL6211 DVB same specs as the S905H box except for Gigabit Ethernet instead of 100M so using that image couldn't connect to the internet, in the other hand the Generic_S905 image working internet but AVL6862, maybe if we can get 100M ethernet support on the WP2 image, I can test the tuner in S905H box using that image also I think the Mecool K2 Pro also has AVL6211 DVB-S2 tuner but I don't know why when tested with S905D box it's showed as AVL6862.

Installed from scratch same version LibreELEC-Generic_S905.arm-9.2.8.18.img.gz using gxl_p231_2g_wetek-dvb.dtb from first boot (dindn't install anything no dvb drivers) :

LibreELEC (dtech): 9.2.8.18 (Generic_S905.arm)
LibreELEC:~ # ls /dev/dvb/
adapter0
LibreELEC:~ # dmesg | grep -i dvb
[   10.487528@0] aml_dvb_init: aml dvb init
[   10.487783@0] aml_dvb_probe: probe amlogic dvb driver
[   10.487810@0] aml_dvb_probe: dmx rst ctl = ffffffc05d81f6c0
[   10.487820@0] aml_dvb_probe: asyncfifo rst ctl = ffffffc05d81fd40
[   10.487830@0] aml_dvb_probe: ahbarb0 rst ctl = ffffffc05e151a00
[   10.487837@0] aml_dvb_probe: uparsertop rst ctl = ffffffc05e151f40
[   10.487847@0] aml_dvb_probe: ts0: parallel
[   10.487934@0] aml_dvb_probe: ts0_control: 0x0
[   10.487943@0] DVB: registering new adapter (amlogic-dvb)
[   10.487946@0] aml_dvb_probe: Registered adpter: amlogic-dvb
[   10.492259@0] aml_dvb_dmx_init: demux0
[   10.549116@0] aml_dvb_dmx_init: demux1
[   10.552013@0] aml_dvb_dmx_init: demux2
[   10.552285@0] aml_dvb_asyncfifo_init: af:0 irq:51
[   10.552358@0] aml_dvb_asyncfifo_init: af:1 irq:57
[   10.561670@0] DVB FE: Init AVL6862 frontend 0
[   11.385876@3] DVB FE: avl6862_attach attach failed!!!

Still showing AVL6862.

pastekodi