I am using eMMC install and 20260712 nightly and it seems mostly fine and functional.
I came across problems trying to watch the latest episode of the anime One Piece, 1080p H264 1.4GB. Video kept on freezing directly from the start and is totally unwatchable. This is strange because I finished an entire 1080p remux and 2160p remux with no issues at all. I tested that this One Piece episode plays with no problems at all outside CoreELEC on Jellyfin LG A1 OLED webOS client and direct play no transcoding.
How should I provide logs to debug this, should I do dmesg | paste or like what is recommended I provide.
First thing to check would be if USB is the problem or if something else is, try booting from USB and seeing if it plays back properly or also has issues.
CoreELEC Toolbox v1.1.1 fixes a issue where a library was called incorrectly causing the toolbox to fail to open for some users, please update to it if you have issues using the below command:
Update: SSH in (ssh root@YOUR-BOX-IP, default password coreelec) and paste one line:
New CoreELEC Toolbox v1.1.2 fixes a issue where user-update.sh called a unavailable module in the boot phase causing the gate to fail to be re-asserted
Please update to it using the below command:
Update: SSH in (ssh root@YOUR-BOX-IP, default password coreelec) and paste one line:
This may be incorrect as I tested 20260711 nightly which likely does not have this commit applied and it has problematic playback too on anime opening songs with subtitles on top and bottom. However beta1 has no issues with such a video. Possibly a commit even earlier than this one is the root cause.
Would it be possible to get rid of the android partitions entirely? I have no interest in android, so it would allow having a bit more space fore CoreELEC
I donât think itâs possible yet but CoreELEC uses pretty much super low space like less than 1 GB so Iâm curious what you plan to do with the storage space from removing Android as itâs not like you can comfortably put entire remuxes on the eMMC. If youâre worried about accidentally booting Android that wonât be a problem since you can use toolbox to set default reboot OS to CoreELEC.
Not sure if removing android is the best option for now, because thats the only way we can flash and repartition the eMMC (not sure about the complete capabilities of fastboot)
Would be great if we can flash a custom recovery image of some sort
I followed the instructions on my mi box and now it worked perfectly. Then last week one of my kids accidentally reset my mi box and now it doesnât reboot into coreelec. I followed the guide again to see if I can resolve the issue but I canât. Then I thought I will just restore to default but I canât even do that because I installed a fresh copy of windows onto my PC and the âpulled_backupsâ folder is gone. Is there anyway to restore it without the âpulled_backupsâ or can someone kindly send their âpulled_backupsâ folder to me so I can restore to default and reinstall coreelec. Thanks.
Iâm not completely sure if this is the same issue youâre having, but something similar happens to me sometimes.
In my case, Android still boots normally, but Reboot to CoreELEC stops actually booting into CoreELEC.
What fixes it for me is going into Android:
Settings â Apps â Reboot to CoreELEC â Force Stop â Clear data/storage
Then I open Reboot to CoreELEC again and run it normally. After doing that, it starts booting into CoreELEC again.
I havenât found this particular fix documented in the official CoreELEC instructions, so itâs just something that has consistently worked for me.
Iâd try that before attempting a full restore.
Also, I would be careful about using someone elseâs pulled_backups folder. As far as I understand, those backups are created from your specific device during the installation and contain device-specific/original partition data, so another personâs backup may not be safe to restore to your box.
By the way, I speak Spanish and translated this message using a translator, so I hope everything is clear and understandable.
Hi. I was about to install this, but my newly acquired box came with older firmware than the supported one. I also noticed that Xiaomi had already released a newer firmware, which I assume isnât supported either. So, I tried to manually sideload the correct versionâs OTA package via adb sideload, but the issue is that neither my PC nor Mac recognize the box when itâs in recovery/adb sideload mode. No USB signal detected by either computer at all, so no drivers to install either. USB debugging works fine with USB-A - USB-A cable on both computers, when booted to android. I spent couple of hours debugging yesterday, and came to a dead end. Any ideas? Or any ideas how to update to the UKG3.250826.001/V816.0.7.0.UZFAABX firmware besides adb sideload? I already unlocked the bootloader and installed magisk, I wonder if that could have something to do with it?
I managed to update by buying a USB hub, attaching a keyboard & usb stick, which I used to flash the ota update zip. However, after completing all the installation steps, CoreELEC refuses to boot with any method. When trying to boot, it flashes a black screen for couple of seconds, reboots and boots to android. I did bunch of debugging with the help of LLMs, ran some of the scripts again etc., but it still doesnât boot. None of the scripts show errors when ran, it just doesnât boot when all is done. Any ideas what could be the cause?
Yo probarĂa otro hub USB antes de repetir la instalaciĂłn de CoreELEC.
Tuve un problema muy similar con mi Xiaomi Box S 3rd Gen. Con mi hub anterior, el pendrive no siempre quedaba enumerado/disponible lo suficientemente rĂĄpido durante el arranque, por lo que algunas veces el equipo omitĂa CoreELEC y arrancaba directamente Android.
Por eso, antes de modificar nuevamente la instalaciĂłn, probarĂa el pendrive de CoreELEC directamente en el Xiaomi o con otro hub. Si ademĂĄs necesitas Ethernet, el TP-Link UE330 funciona muy bien en mi configuraciĂłn.
In English:
I would try a different USB hub before redoing the CoreELEC installation.
I had a very similar problem with my Xiaomi Box S 3rd Gen. With my previous hub, the USB drive was not always enumerated/available quickly enough during boot, so the box would sometimes skip CoreELEC and boot straight into Android.
I was actually able to reproduce the hub behaviour on Windows: if I connected the hub with the USB stick already plugged into it, Windows sometimes didnât detect the stick at all. If I connected the hub first and then inserted the USB stick, it appeared normally.
I replaced that hub with a TP-Link UE330 (3Ă USB 3.0 + Gigabit Ethernet) and it has been working very reliably with CoreELEC, including reboots.
So before changing the installation, I would try the CoreELEC stick directly in the Xiaomi, or try another hub. If you need Ethernet as well, the TP-Link UE330 works very well in my setup.
I am following the dualboot guide on GitHub for the Xiaomi TV Box S (3rd Gen) running the latest stock firmware version.
I got to the Magisk step and ran:
python installer/install.py stage_magisk
The script runs and the device automatically reboots into Android as expected. However, once inside the system, I cannot patch the correct init_boot.img inside the Magisk app (the patching process fails / Magisk doesnât allow me to patch the file properly).
Because of this, Magisk doesnât complete its setup and root access is not working, so I canât proceed to the next stages. Has anyone encountered this issue on the latest firmware version, or is there a workaround to get the init_boot.img properly patched/installed here?
the installation is not updated for the latest june security patch update, so you have to wait until it gets update, I also wait for it as I have three boxes to install.
