Posts by dtech

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

    Quote from chewitt

    Legacy images use different boot-scripts and boot files to the AMLGX image so you MUST invoke recovery mode boot so the vendor u-boot searches for aand finds/loads/stores updated boot-scripts that tell it what files to use. If this is not done u-boot is looking for boot files that don't exist and .. it isn't going to boot. Similarly if you have been running AMLGX and want to revert to the legacy image you need to do the same else u-boot is looking for the AMLGX boot files and won't find/use the legacy ones.

    chewitt

    You described the reason, but you didn't detail the solution. :)

    tecc

    In short: it is necessary to execute the "toothpick method" again, because aml_autoscript is executed only in this case.

  • No WiFi at MXQ PRO 4K 5G

    Unfortunately, the Android ROM developer ( willie.xu ) didn't respond to my numerous inquiries, so I might end up trying to compile my own uboot for this box, to fixing these errors, if that's possible. (I haven't done this before, so it might not work.)

    But CEC will probably never work because it doesn't seem to even be physically connected.

    At least I have a small sense of success that I was able to carve out a hole for the UART socket at the bottom of the box:

    So don't have to leave this piece of garbage all the time disassembled... 8o

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

    Quote from tecc

    Thanks for replying with this to my question from some time ago. I've been running LibreELEC (dtech) 9.2.8.8 - Kodi 18.9 Leia ever since but for the life of me can't remember exactly what dtb.img I actually did use (here's the MD5: 4c723801b797f26828caed55ebec8b32 in case that helps).

    The answer:

    Code
    LibreELEC:~ # find /usr/share/bootloader/device_trees -type f -exec md5sum {} \; | grep 4c723801b797f26828caed55ebec8b32
4c723801b797f26828caed55ebec8b32  /usr/share/bootloader/device_trees/gxl_p212_2g_nand.dtb
    Quote from tecc

    Since CEC sudddenly does no longer work on a friend's TV of mine (who owns the same box), I was planning to use the original remote, so I've downloaded LibreELEC-AMLGX.arm-11.0.3-box.img.gz and tried renaming each of these ...

    For versions based on the mainline kernel (LE10+), the dtb setting is different compared to legacy versions.

    Please check if you have done the settings correctly as described in the description:

    https://wiki.libreelec.tv/hardware/amlogic#box-images

  • Bricked Wetek Hub ... now what

    I'm not sure if the kernel in the WeTek Hub LE11 image is working. I tried booting from an SD card with it and it didn't work either.

    However, the box image boots flawlessly from the SD card.

    chewitt Is it possible that the Hub image is not compatible with the WeTek factory u-boot?

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

    Quote from AppleCross

    I am looking for kernel source code (DTS, kernel Config and some other files for building Linux) . Can you give me hint where to find those files?

    The information you need can be found in the leading post in this topic:

    Post

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

    Latest version: LibreELEC 9.2.8.18 (Release date: 2025-05-20)

    IMPORTANT NOTICE!

    Due to the switch to GLIBC v2.34, all binary addons have been rebuilt. The main version of the add-ons has been changed from v9.2.0 to v9.2.1, so after the system update, the binary add-ons will also be updated. In addition, the default transfer protocol in the repository has also changed from HTTP to HTTPS.

    NOTICE: If the auto update is enabled, but the installed version is not the latest, then the supported devices…
    dtech
    February 7, 2021 at 2:33 PM

  • Bricked Wetek Hub ... now what

    chewitt

    IIRC that the UART on my Hub still works during uboot loading, and it only starts producing random output when the kernel is loaded.

    But I'll check in the afternoon because I'm not sure I remember correctly. :/

    thegooddoctor

    Maybe the standard 3-pin ("stereo") 3.5 mm Jack will also be good, because the inner ring on the sleeve side is not connected anywhere:

    Edit: Confirmed, so it works with the 3-pin Jack, and there produces UART output with the LE v11.0.3 box image.

    A simple 3.5 mm to 2.5 mm Jack adapter was used with Play's factory RS232 cable:

    However, something is wrong with the Hub image, because it refuses to boot for me either.

  • Bricked Wetek Hub ... now what

    Quote from thegooddoctor

    took the meson-gxbb-wetek-hub.dtb and renamed it to dtb.img and moved it to the root of the filesystem and rebooted and this worked

    ^ This step was completely unnecessary. With the mainline kernel-based versions, you no longer need to rename anything.

    Anyway, that's not what's causing your problem...

    Quote from thegooddoctor

    Verify pinout --- above images are correct

    I have my UART cable

    The factory UART cable uses a 4-pin Jack. Although I suddenly don't remember the wiring, I also have a DIY version that I built.

    But if you need it, I can measure the correct wiring when I'm home.

    By the way, the WP2 uses a 2.5 mm jack, which is not compatible just because of its size.

    Quote from thegooddoctor

    edit: tried a bunch of different settings; switched RX and TX (reduced output); and even another UART device,
    checked my wires for connectivity and shorts (all good); went to manufacturer's website to download new drivers ... no change

    It's not a TTL-level thing, so it has to be connected directly to a serial port with a DB9 connector. Do not use an RS232-TTL converter.

    Regardless, under LE11 the UART doesn't work on the Hub for some reason. I also only get static noise, and if the serial cable is plugged in, the image does not start. However, under LE 9.2 I can see everything on UART perfectly.

    So, if you're testing an LE11 image, please don't use UART, the Jack connector should be empty.

    Questions:

    • Does the Hub logo appear on startup?
    • If you put the SD card back in does it boot?

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

    Quote from jim_p

    Honest noob question. It has to do with the all black s805 mxq that has le installed to its internal rom.

    What would/should happen if I do the toothpick method without having an sd/usb plugged in? In plain english, Just insert the toothpick in the av port, click the reset button inside it and plug the power supply in the wall outlet.

    Nothing special happens except that the Android recovery loads. Although it can be used to cause damage (e.g. wipe data/cache partition), it is not a harmful thing in itself.

  • No WiFi at MXQ PRO 4K 5G

    Quote from someoneelse

    Thanks. Really works perfectly.

    P.S. HDMI-CEC also doesn't work. Nothing can be done about it? :) The biggest inconvenience when using a TV box is to replug the power supply every time to turn it on.

    I made a dump from the eMMC, and after a short analysis I found out who could be the author of this ROM (M8-20221108).

    I will try to contact him, and if he replies, maybe we can move forward from this point. ;)

    Edit:

    In the meantime, it seems that I managed to burn in the MAC address, which is on the label at the bottom of the box.

    ^ However, this should have been done by the distributor, not the end user... :P

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

    Quote from jim_p

    So the 9.2.8.10 is the fixed image? Or a newer one is on the way?

    I revoked the first release (20220716) and released a new image (20220718) for S805 and S8X2 devices only. But the main version is not changed, it is still v9.2.8.10. (The release date is checked for the automatic update, not the major version number.)

    Quote from jim_p

    Also, le-aml has automatic updates? What do I use then as custom url under the update settings?

    In early June I was trying to teach my friend how to update it manually by downloading the right file and transfering it to the box...

    Sometimes it's worth turning the page back to the leading post. :)

    Quote from dtech

    Automatic updates have been enabled for all devices except WeTek_Play because it had an update bug until v9.2.8.7.

    NOTICE: If the auto update is enabled, but the installed version is not the latest, then the supported devices will automatically download and install it after restarting. If anyone has any issues with the update, please let me know in the comments.

    You don't even need to use a custom url, just turn on the update and that's enough.

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

    Quote from crazyazz

    That would be awesome, I don't expect anything but if its possible that's great!

    In the meantime, I already found a workaround yesterday, but it was hidden in one of my answers, which I think you didn't notice. :)

    Quote from dtech

    Try this:

    echo "echo \"audio_off\" > /sys/class/amhdmitx/amhdmitx0/config" >> ~/.config/autostart.sh

    ^ This disables the HDMI audio output immediately after each startup. I know it's not as convenient as setting it from the menu, but the end result is the same. ;)

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

    Quote from jim_p

    mdns does not seem to work

    Now we just need to find out under which version it broke because the avahi-daemon won't start under any of my v3.10 boxes.

    (However, it is flawless under all v3.14 devices.)

    Code: avahi-daemon
    Found user 'avahi' (UID 495) and group 'avahi' (GID 495).
Successfully dropped root privileges.
avahi-daemon 0.7 starting up.
Loading service file /etc/avahi/services/sftp-ssh.service.
socket() failed: Permission denied
socket() failed: Permission denied
Failed to create server: No suitable network protocol available
avahi-daemon 0.7 exiting.

    But if I start the daemon with the --no-drop-root argument, it works fine.

    Quote from crazyazz

    One question, how do I disable HDMI audio output as I use the analog output?

    Try this:

    echo "echo \"audio_off\" > /sys/class/amhdmitx/amhdmitx0/config" >> ~/.config/autostart.sh

    ^ This disables the HDMI audio output immediately after each startup. I know it's not as convenient as setting it from the menu, but the end result is the same. ;)

  • No WiFi at MXQ PRO 4K 5G

    someoneelse

    The "new" version (2022) S805-based MXQ box has also arrived for me, and quite a lot points to an inconsistent design:

    • The control of the blue LED (GPIOAO_13) is not handled by uboot, so a kernel patch is needed. Although the absence of a blue LED light when the box is turned on is rather an advantage.
    • The remote GPIO pin is the same (GPIOAO_7), but something different happens during shutdown. When tested on UART, it seems that the device stays on even when turned off under Android, and simply restarts by pressing the button on the remote control. This is not exactly the best solution and indicates a lack of another uboot feature.
    • The clock signal of the SDIO bus is limited from 50 MHz to 37.5 MHz. This may also be related your SD card R/W errors, IDK.
    • The MAC address of the Ethernet is not burned into the efuse, so even under Android it gets a different address during every boot. This is quite annoying.

    I originally planned a separate build for this device, but unfortunately it makes no sense. It would make more sense to compile a bootloader without the above issues. :(

    PS: Regardless, the RTL8723AS wireless chip works perfectly, and it has already been included in the stable version 9.2.8.10. So now you can safely turn on the automatic update again.