[UNOFFICIAL][Le12][RK3228/RK3229][box]Libreelec builds

    Been using this for about two days now. I have an MXQ Pro 4K with a broken Android firmware, and LibreELEC works flawlessly. The Wi-Fi didn't work, which I expected since only the legacy kernel has its drivers, though it's no biggie since I had a spare Wi-FI USB adapter, which I currently use to connect to my home Wi-FI.

    There's one problem, however: booting from eMMC doesn't work, and if I want it to boot from SD card, I had to flash Armbian into the eMMC for some reason otherwise, it would just crash before the splash screen shows up. I had no issues booting Multitools from the SD card when using the Android firmware, but I had to go through these hoops so that LibreELEC could boot.

    Is there some way to flash both the bootloader from Armbian and the system files from LibreELEC to the eMMC so that I don't have to insert an SD card every time? Thanks.

    respect to the team and the comunity which contributed to these LibreELEC RK222x builds.

    Long story short:
    I purchased recently (by mistake) a cheap TVbox labeled "MX10 MX Box S - 4K Ultra HD set-top-box". The scope for which I'm using it is mainly to playback videos from external HD's connected via USB.
    Because on the original OS (fake Android 13, actually Android 7) Kodi was not able to playback smoothly 1080p videos, I searched for alternatives and landed at LibreELEC.
    My problem is that the Le11 versions do recogniize my USB-HD's but the Le12 version doesn't. My HD's are nothing special but normal WD-Elements connected via a 4x USB3 hub.
    What I did up to now:
    1. Tested LibreELEC [unofficial] Le12 on SD card and it didn't recognize the USB-disks. However, with the latest revision dated 2025-02-18 the WLAN is working, but not the USB.
    2. Tested LibreELEC [unofficial] Le11 on SD card and it worked: have LAN, have USB, playback is perfect. Don't have WLAN and file manager functions in Kodi don't work.
    3. Backed up the original firmware with rkDumper (under Win10) and MultiTool (from SD card). Tried to extract the DTB's from the img files with extract-dtb v1.2.3 (python/Win10), but I'm not sure if i did it correctly.
    4. Flashed LibreELEC [unofficial] Le11 to the internal memory, and it worked same as from SD card, but much snappier.

    Remark: If you think it is helpful, let me know and I upload the extracted DTB's or, alternativelly, the IMG's which do contain DTB's.

    Strongly hope that you can fix the USB problem, enabling me to upgrade to latest Kodi :)

    And here is the picture of the upper side of the board.

    Thanx

    Quote from meho

    There is only one "small" problem called wifi... Wifi works fine with armbian but shows no signs of life in libreelec (using generic image, I don't think others will work). Wifi adapter is Realtek 8723CS.

    meho my mistake, it was included in previous releases. I will reinsert it as soon as possible

    Quote from oldie__

    My problem is that the Le11 versions do recogniize my USB-HD's but the Le12 version doesn't. My HD's are nothing special but normal WD-Elements connected via a 4x USB3 hub.

    oldie__ I have to check but I don't often use 'complex' USB devices because since the libreelec 10 builds, I have always had problems without a separate power supply (the USB ports are not powerful enough). In any case please send a log and your dtb

    leap123 can you understand if we are talking more or less about the same board? (You may have to open the device). Unfortunately, I don't have all the boards, but I remember that pocng had solved it. If so, I'll try to do the fix you suggested

    ilmich thank you for the fast reply, pls find further down following documents:
    1. log from LE12
    2. log from LE11
    3. DTB's from multitool image extracted with extract-dtb (2 parts)
    4. DTB's from rkDumper images extracted with extract-dtb (1 part)
    Remarks:
    a. On the "tvbox-backup" image created by multitool the last extracted "09_dtbdump.dtb" was ~ 7.5GB in size and triggered an error on my computer, and on the "kernel.img" created by rkDumper the last extracted "04_dtbdump.dtb" was ~ 6.8MB in size and triggered an error on my computer - hence I discarded both of them. All other dtb's are in attached files.
    b. Each of my external WD-Elements Desktop HD's does have her own separate power supply.
    c. I personally dont't think it is a dtb problem, coz I replaced the dtb's from LE12 with those from LE11 and USB still did not work.

    thx
    oldie__

    hi oldie__ thanks for the logs

    libreelec 11

    Code
    Feb 16 18:11:14.664106 LibreELEC kernel: ntfs: volume version 3.1.
Feb 16 18:11:14.664699 LibreELEC kernel: ntfs: (device sda5): load_system_files(): Volume is dirty.  Mounting read-only.  Run chkdsk and mount in Windows.
Feb 16 18:11:14.665111 LibreELEC kernel: ntfs: volume version 3.1.
Feb 16 18:11:14.665411 LibreELEC kernel: ntfs: (device sda1): load_system_files(): Volume is dirty.  Mounting read-only.  Run chkdsk and mount in Windows.

    libreelec 12

    Code
    Feb 27 17:26:20.095723 LibreELEC udevil[580]: mount: /var/media/WD ELEMENTS 2-1: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Feb 27 17:26:20.095723 LibreELEC udevil[580]:        dmesg(1) may have more information after failed mount system call.
Feb 27 17:26:20.098361 LibreELEC kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Feb 27 17:26:20.136565 LibreELEC systemd[1]: Starting [email protected]...
Feb 27 17:26:20.150721 LibreELEC kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!
Feb 27 17:26:20.151416 LibreELEC udevil[597]: mount: /var/media/WD ELEMENTS 5-1: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
Feb 27 17:26:20.151416 LibreELEC udevil[597]:        dmesg(1) may have more information after failed mount system call.
Feb 27 17:26:20.163521 LibreELEC kernel: ntfs3: sda2: volume is dirty and "force" flag is not set!
Feb 27 17:26:20.164094 LibreELEC udevil[591]: mount: /var/media/WD ELEMENTS 2-2: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
Feb 27 17:26:20.164094 LibreELEC udevil[591]:        dmesg(1) may have more information after failed mount system call.

    you should kindly try running a file system check from windows. Libreelec 11 mounts your volumes in read-only mode, the new libreelec 12 ntfs driver refuses to do this.

    hi ilmich many thanks for the hint! :thumbup:
    I did run the system check as suggested and all volumes are now mounted by LE12. Flashed to internal memory, and all is OK :)

    However, I consider that mounting dirty volumes as read-only is more logical and definittely much more user friendly. Alternativelly there should be at least some notification not just silently ignore/drop those volumes. Hope this is just a matter of driver settings...

    In my case, the dirty bit was set because we did have several times power outage during playback with Kodi on my Android box (MiBox), but Android seems to ignore this bit. Fortunattely it seems that unplugging the power supply from this LE box during playback doesn't cause this kind of problem.

    And one last unrelated question: I noticed that even when the TVbox is powered of from remote control, the external drives continue to run, and stop running only after I unplug the power supply from the TVbox. Is this normal?

    Note that it's possible to install the NTFS-3G driver add-on; the OS will then use them to mount NTFS drives instead of the in-kernel drivers, thus replicating the experience of older LE versions.

    Quote from meho

    There is only one "small" problem called wifi... Wifi works fine with armbian but shows no signs of life in libreelec (using generic image, I don't think others will work). Wifi adapter is Realtek 8723CS.

    Is it possible to include this driver in your next build?

    Thanks

    got same problem, but then ilmich said:

    Quote from ilmich

    meho my mistake, it was included in previous releases. I will reinsert it as soon as possible

    so I decided to try older version and wifi works fine with Libreelec 11.

    Was all happy about that and even managed to run Netflix through CastagnaIT Repo, but then noticed that audio doesn't work (checked some radio addons and mp3 file).

    ilmich is there any way to fix that? or some new release is needed?
    not sure what kind of informations about my box I can provide. In Android it was shown as rk322x-box.

    chewitt thanks, it is working :thumbup:wow:thumbup:

    Set the dirty bit at one external HD (under Win7) by "fsutil dirty set r:" and (as expected) the volume wasn't mounted by LE12.
    However, after installing the NTFS-3G driver add-on the volume is mounted correctly and all Kodi file manager functions (move, copy, delete, etc.) are working.

    Funny is, that if I set the dirty bit on a normal USBstick, the stick is mounted corectly by LE12 without NTFS-3G driver add-on.
    In my opinion that means the new in-kernel-driver doesn't behave consistently and it may still needs some work... :/

    Hi!

    I am new to the world of LibreElec and Kodi. Bought an MXQ Pro 4K 5G with board revision RK3229Q-221P-V1.3 because it was a cheap box with composite video out. My plan is to run old 80s TV-shows from the box on an old Commodore CRT monitor. The stock Android managed to output a nice PAL signal in color via the AV-port (composite video) but UI is crap and I want to get Kodi on there instead. I put the LE12 image on an SD card and the box boots and runs smoothly when connected to an HDMI display. But there's no action from the AV-port and nothing is displayed on the CRT.

    I also tried with the LE11 image and noticed in the corresponding forum thread for LE11 that someone else had asked about the AV-port. So... To get to my question... Is support for the AV-port something that is possible/feasible/on the backlog?

    (There is the option of using an HDMI to composite video converter but it adds one more adapter plus the common ones seem to have some problems with PAL monitors)

    Lastly, awesome job with developing and maintaining all of this, and thanks for making it available to the rest of us!