Wetek Play 2. Is it possible to have an automatic boot to sd-card?

    Hi,

    got a Wetek Play 2 now and everytime i reboot or start the box (Without holding the power button) it boots to internal weos 3.2 on emmc.

    is it possible to always boot to sd-card without any "tricks"?

    And the ***** Kindergarten Crap Continues. :(

    I loaded "LibreELEC-WeTek_Play_2.arm-9.0.2.img" with win32diskimager to a 64gb sd card.

    AND??? ???

    WHAT ELSE ... ... It doesnt boot. :)

    WTF???

    SD Card from my Minix Neo U1 with Coreelec 9.0.1 worked perfectly only by changing the device tree to wetek play 2!

    And a libreelec image (LibreELEC-WeTek_Play_2.arm-9.0.2.img) which was extra made only for wetek play 2 doesnt boot ???

    What is wrong with libreelec?

    Can anybody pls explain?

    IIRC the WeTek Play/Play2/Hub boot mode is toggled between WeOS and LibreELEC on SD card by pressing the power or pause (can't remember which) key on the remote while the WeTek splash screen shows. The boot choice is then remembered until you either remove the SD card and it will default back to WeOS/Android or you repeat the remote-key toggle. Using this original boot flow it will not auto-boot into LE simply by inserting the SD card. If you boot CE or the dtech image using the typical "toothpick" boot method the boot flow will be modified to boot on presence of SD card, but the LE 9.0 image will not do this as the autoscript files on the SD card do not have the instructions to modify the boot flow.

    TL/DR; the issue was "PEBKAC" due to incorrect assumptions (based on some other distro) on how things work.

    I still use CE 9.0.1 and it works great on the Play 2.

    The Tuner is the most "stablest" ive ever had with my small camping dish :)

    I tried long press power button and long toothipick press "upgrade" button on the bottom and power the box.

    Both times it only loads CE once. When i then do "reboot" inside CE it then loads WE OS from internal.

    No matter, i can live with that, but if there is a trick? :)

    My LE9.2-LTS WP2 image supports the WP2 tuners as well, but Generic_S905 does not include the AVL6211 wetekdvb driver. For WeTek devices, the whereToBootFrom uboot environment variable specifies the boot media, so it can be overriding in the following way:
    fw_setenv whereToBootFrom sdcard

    Keep in mind that WP2 images do not contain autoscripts, but the Generic_S905 images do (which is also true for CE), so these nicely mess up the factory boot process, which differs from the standard Android boot order solution for WeTek devices.

    I have this file on CE 9.0.1 /flash

    aml_autoscript

    I can open it with an editor:

    But i can't edit it with an editor. When i just open and save it back, the file gets bigger and booting from sdcard doesnt work anymore.

    So i cant add: fw_setenv whereToBootFrom sdcard

    Do i have to use some kind of different software to edit it?

    Quote from wedok

    But i can't edit it with an editor. When i just open and save it back, the file gets bigger and booting from sdcard doesnt work anymore.

    It's a compiled binary file (albeit one with lots of readable strings inside) so when you 'edit' the file you break it, and because boot depends on this file, boot from SD is broken. Like all compiled code, the source file can be edited, then it needs to be recompiled when you create the image.

    Now i tested this: LibreELEC-AMLGX.aarch64-13.0-nightly-20260125-c5bb826-box.img.gz

    And with it, it worked to boot directly to sd card.

    I tested more by installing tvh, but wetek tuner isnt found :(

    Is there a trick to get the wetek tuner working in LE 13?

    Does it work with "LibreELEC-AMLGX.aarch64-13.0-nightly-20260125-c5bb826-wetek-play2.img"

    And this dedicated wetek-play2.img is for installing to emmc?

    Edited once, last by wedok (January 25, 2026 at 12:51 PM).

    Quote from wedok

    So i cant add: fw_setenv whereToBootFrom sdcard

    This is a command that can be issued under LibreELEC 9.2.

    Quote from wedok

    Is there a trick to get the wetek tuner working in LE 13?

    The built-in tuner and demod chips cannot be used under the mainline kernel because their drivers are not implemented.

    Quote from wedok

    And this dedicated wetek-play2.img is for installing to emmc?

    The short answer to this question is YES. -> https://wiki.libreelec.tv/hardware/amlogic/wetek-hub-play2
    But you have already tried LE9.0, LE9.2-LTS, LE13, CE, and on the eMMC still has WeOS. I just don't understand what your final goal is...

    1. Is the DVB tuner important? If the answer is yes, please forget LE13, otherwise use an external tuner.
    2. If you don't need WeOS on the eMMC, you can also install 9.2-LTS, the description can be found here:
      Legacy v9.2 (LTS) builds for Amlogic S805/S8X2, S905/S912 and all WeTek boxes
      (Please find the following section: "NAND install image for SD card".)
    3. If you want to use CE, then you are in the wrong forum.
    Quote from wedok

    Yeah i understand now, booting with box image and then write image to emmc. :)

    Please note that since this does not contain the factory bootloader, the toothpick method and similar solutions will not work from now on, so if you write LE13 on the eMMC, it is not guaranteed that you will be able to boot older versions.

    However, LE 9.2-LTS includes the factory bootloader, so the option to boot from an SD card still remains. The installation solution for this is different for eMMC, but I linked it above.

    Quote from wedok

    Btw, is an addon direct download possible for Legacy v9.2 (LTS) builds, like https://addons.libreelec.tv/, if yes whats the url?

    Browsing these is disabled due to protection against search bots, but since they are built for a specific version by default, they are available through the built-in repo. Also, they are binaries, so they would probably not work under another version/distro.

    Quote from dtech

    If you write LE13 on the eMMC, it is not guaranteed that you will be able to boot older versions.

    The Amlogic vendor kernel has some drivers that assume an era-appropriate vendor u-boot is installed so it can probably be done with a little manual fiddling (which there are no guides for) to fix wrong-named boot files, but I guarantee that some drivers don't work right, and as the maintainer of the AMLGX image; this is not something we have any interest in trying to support.

    Quote from chewitt

    The Amlogic vendor kernel has some drivers that assume an era-appropriate vendor u-boot is installed so it can probably be done with a little manual fiddling (which there are no guides for) to fix wrong-named boot files, but I guarantee that some drivers don't work right, and as the maintainer of the AMLGX image; this is not something we have any interest in trying to support.

    Basically, I mean that the uboot under the mainline version is not made for Android layout, so the appropriate recovery functions are missing. I can understand this in the case of a development board, but in the case of a box like the WP2, which is originally built on an Android-based WeOS, it may not be suitable in the classical sense.

    In such cases, I would draw the attention of users that the image written with emmctool may limit the full use of the box. And since the drivers for the built-in tuners will probably never be included, this is probably a dead end. That's why I don't recommend this emmctool solution for mainline kernel versions.

    It also looks a bit like the installtointernal script that was previously rejected by official versions. This is now roughly the same, just in reverse situation. However, those images didn't even have a bootloader, because the factory one was still in use.