Team CoreELEC recommends running from (μ)SD Card / USB Flash Drive!
The instructions bellow are for generic ARM based devices reported to work with CoreELEC.
End user support for these devices is provided by the CoreELEC User Support Forums.
Application | Function | Linux | Mac | Windows |
---|---|---|---|---|
balenaEtcher | Bootable Media Creator | X | X | X |
UNetbootin | Bootable Media Creator | X | X | X |
USBImager | Bootable Media Creator | X | X | X |
ddrescue / ddrescuegui | Disk Utility | X | ||
Disk Utility | Disk Utility | X | ||
Rufus | Bootable Media Creator | X |
gunzip -c image.img.gz | dd of=</dev/path/to/bootmedia> bs=1M conv=fsync
Table 1: Board & SoC status within CoreELEC development cycle
CoreELEC | BOARD | SoC |
---|---|---|
19.x STABLE | G12A | S905X2 |
19.x STABLE | G12B | S922X, A311D |
19.x STABLE | GXL | S905D, S905X, S905W, S905L, S905M2, S805X, S805Y |
19.x STABLE | SM1 | S905X3 |
Use the CoreELEC Download Helper to download the desired CoreELEC Edition (Stable, Nightly) onto a personal computer, then use the image writing software to create a bootable (μ)SD Card / USB Flash Drive (boot media). The Download Helper assists in selecting the DTB for use with the selected device. Make note of the DTB name, it will facilitate the nesxt step (Choosing a Device Tree). Downloaded image: CoreELEC-Amlogic-ng.arm-19.2-Matrix_rc2-Generic.img.gz If required, first extract the image.
Once completed, the (μ)SD Card / USB Flash Drive capacity should show 512MB. The remainder of the drive will be initialized during first boot and will become available as storage partition for CoreELEC user data. |
Table 2: What to look for when distinguishing between a generic and a device specific device tree
Device | SoC | RAM | Device Tree | ||
---|---|---|---|---|---|
Generic dtb | | S905X3 | 4G | sm1_s905x3_4g_1gbit | |
Device specific dtb | Odroid C4 | | | sm1_s905x3_odroid_c4 |
Browse to the device_trees folder on the boot media, and copy the .dtb image file for the device that will be running CoreELEC onto the main (root) folder of the (μ)SD Card / USB Flash Drive, then rename it to dtb.img The list is for reference only and far from complete. If your device is not listed by name, try all of the dtb matching the device hardware configuration and choose the one working best with your device. If some of the devices functionality is missing, like for example BlueTooth or HDR, and the feature is supported by the hardware, Team CoreELEC might be able to help you in the CoreELEC User Forums. |
To boot CoreELEC for the first time, one the following techniques can be used:
TV box
SBC
Some MiNiX devices
This section can be skipped if the remote works “out of the box”
CoreELEC natively supports a large selection of Infrared Remote Control Units via the NEC Infrared Transmission Protocol. If CoreELEC does not respond as expected to a functional factory remote that powers the device on and off:
The remotes repository has a Wiki which combines troubleshooting tools and tips with a comprehensive knowledge base. |
These steps are for devices with a Vacuum Fluorescent Display similar to the one in the picture
|
Currently only 1 device is known to require a custom dtb.img: the A95X-R2. The dtb.img for this device can be found in the device_trees folder of the boot media.
[1] ensure boot media is compatible with device (eq: a device with a 16Gb (μ)SD Card slot might be unable to boot from a 32Gb (μ)SD Card). 8Gb should be recognized by the vast majority of Android TV Boxes.