As part of the CoreELEC install process you are required to copy a device tree from the device_trees folder on your sdcard/flash drive to the root folder of your sdcard/flash drive and rename it to dtb.img, failure to do so will result in either your box being unable to boot or network problems.
Every device is built differently and there is so many to choose from on the market, you can find a list of some of these devices along with the corresponding DTB you must use on our download page here.
If your device is not on the list then and you know which device tree is compatible then reply to this topic and help us keep the list updated.
I’d like to contribute to this list, but how do I find out which dtb is in use? (I tried a few before I finally found one which worked as my box has fake ram)
You can just ignore this message.
Sometime in the past your volumes were not cleanly unmounted (power failure, Kodi crash, …) and a “dirty bit” was set on your file system.
Because your installation obviously works as expected, you don’t need to do anything.
It is possible to remove this dirty bit using fsck, but it’s not worth the hassle, because after the next failure, it’s back again.
MXQ PRO 4K is totally irrelevant as far as Brand Hardware goes.
The relevant Hardware specs to determine which dtb.img will HOPEFULLY boot your box are the soc and the ethernet speed.
You might want to disclose these details when posting.
Hi. I own a XORO HST 250 S and would like to run CoreELEC on it, but my device is not listed.
Can I use the DTB for the XORO HST 260 S?
If not, could you create a DTB for the 250?
Thanks in advance
If this box doesn’t have a S905 or newer SoC, it won’t run CE.
Looking at specs, quad core ARM A5 CPU doesn’t sound like a S905 or newer. So it won’t run CE.
I have Venz V10 Pro, it uses Amlogic SOC S905x, 2G (2G/16G internal memory), 100 Mbps ethernet. DTB that I used and that should be used for it is gxl_p212_2g.dtb.
Successfully used CoreELEC-Amlogic.arm-9.0.1-Generic.img.gz on SD card with gxl_p212_2g DTB image. After few days of testing successfully installed to internal memory on first try. So far it seems to be running solid and fast.
From Official Venz firmwares you can confirm it uses p212, 2g model so obviously gxl_p212_2g (original Android FW for unrooting and restoring to factory even contains p212 in its name).
I previously used original and official Venz FW dual boot LibreElec / Android combo but found out I almost never booted or used Android, LibreElec (8.0.2) was more responsive and overall better for my needs.
Recently found out about newer versions of LE and later of CoreElec, decided to try it out and I’m most satisfied with it.