OpenElec & LiberElec WishList

Just some background:
I have VIM 16/2 and been using it as my main kodi device more than a month at home and it works perfectly.

This is my whish list:

  1. Nand Installation
  2. Dual Boot: OE / Android, OE / Ubuntu, Android/Ubuntu
  3. OS GUI boot Menu - Can be on shutdown Menu: Boot from Nand / Boot Android/ Boot Ubuntu.
  4. Backup and Restore.
  5. Kodi Krypton (4k Youtube)

Hi, Eli:
Thanks for your feedback.

We will release source code for Khadas VIM on our Github in these days first, so more developers can help to develop better ROMs.

I Have Vin Pro, I use mainly openelect in SD card, but righ now there are not any android image that can run fine with libreelec.
Vim_Marshmallow_Root_161213 just green screen in libreelec,
Vim_Marshmallow_Root_170121 Ican´t run libreelec presing funcion button.
VimPro_DualOS_Marshmallow_Ubuntu-16.04_170124, The Multi-OS menu don´t work with libreelec.
The only way to run libreelec is earse the ROM.

If there is a wish to try external media, regular firmware Android remains unchanged, Libreelec (Krypton-17 and Jarvis 16.1), here is a link to the images. You must activate the multi-boot. Pay attention that after the recording of the image you want to delete media file “dtb.img” (he is for other models of TV boxes). At startup the system will get dtb data from the internal memory. This way works correctly with the regular dtb data from the internal memory (Android 6.0). By the way, if you would be willing, I can gather the script activate the multi-boot for the bootloader version from dualOS (Ubuntu + Android). Working wired network, WiFi, BT. Not yet working normally with the remote control. I have not yet found the correct file remote.conf. I would be grateful if anyone can share a work file.

We have open the libreelec source code on out Github, you can check that for it.

As you can see, in current stage, different OS use different method to load the kernel image and file system:

  • LibreELEC on SD card: use boot.ini, and the u-boot need patch with extra command to support that.
  • Ubuntu on SD card: I saw many developers use boot.scr to load the kernel Image, and current U-Boot has already support the bootscr command, no extra patch is needed.
  • Android: use bootcmd with android mkbootimg tool to load the kernel Image and initrd.
  • Ubuntu on EMMC: currently, we use the android approach to built the ROM, but will research a better approach to achieve that, for now, we prefer the bootscr solution.

We tend to redesign the loader loading approach to suit android / Linux Distro and LibreELEC, and in both SD card and EMMC installation. In our imagination: users can install / uninstall any OS in our dualOS build:

  • Support both Android + Ubuntu + Libreelec at the same time(should one OS on SD card)

Important (for me) distinguish VIM from other develop circuit boards that it uses in common with the TV boxes platform. Including the presence of internal eMMC memory, which is the bootloader. From this it follows that it is possible to use a single scheme multi-download. No matter what system you to run from external media - all can be done with a script. Unlike the script for each system in the set of commands that are required specifically for each system. In this case there is no need to erase the bootloader in order to run the system from external media. By the way, the boot loader on an external drive does not need to start the system, from external media during normal operation. The boot loader on external media are needed only if you damaged the bootloader on the eMMC (to restore the bootloader in the internal memory). Here is a patch to enable multi-boot on dualOS. If you think You don’t need it, feel free to delete it.


Thanks for the commit, any contributions are welcome, and I will check the code next week when I back to office.

Hi Gouwa

I checked the other remote (from Vega S95), everything works fine on VIM . This means that all the necessary modules for IR is in the part of the image, and only need the correct file from the regular remote control. I downloaded the source code LE for Khadas, but I don’t see them in the file “remote.conf”. Perhaps it is possible to pull out of the Android firmware, but I’m not well versed in Android. Can you help me find the correct file “remote.conf” for remote VIM ? I want to collect images of LE (Jarvis and Krypton) with full support for VIM. This versatile images that can work with all external media (SD and USB) and has the ability to install to the internal memory.

1 Like

Hi, Balbes150:
Thanks for your efforts on VIM.

As the remote controller, you can check the Github for the details.

BTW, current release on our Github, all the changes to support VIM just with one commit, we will tidy-up the commits and push to github again in the future.

Pulled from the firmware of the correct file “remote.conf”. Now we can that the images (the link above) there is full support for all elements of VIM. Eth, WiFi, BT, IR (RC) - everything works. You can run the system from SD card or USB flash drive. You can set the system to internal memory eMMC. Order of use 1. Write image 2. Delete media file “dtb.img” 3. To add to the media file “remote.conf” 4. To connect this device to VIM and activate the multiboot. After the automatic reboot LE to start. You can use to choose images with Jarvis or Krypton. Note that the activation system is multi-boot and install in the internal memory still only works with the standard firmware based on Android. For dualOS you need to make changes in u-boot by other means.

Links to images and a file for Remote control.

PS If there is a need and a place to put in the Internet, I can get specialized images LE for VIM (without dtb file, and included in the file for the remote).


Hi balbes150,

can you publish a link (s) to a step by step guide for dummies?

I got the VIM box from Gearbest installed with Android , I have an SD card. now what? (already installed LE on another VIM but it was not done with your method.)

Thanks a lot for your work!

1 Like

If something is not clear, ask, I will try to answer.

Even in this thread there are a number of details and description RDFTKV

Hi to all. I have some questions (especially то balbes150 Thanks in advance ). Today I got my khadas. Now it is with stock android. I want to use it with android on eMMC and libreelec on sd card and if its possible to boot in diferent images (android and libreelec) with my remote. I want to know if i will make the right steps:

  1. Make bootable sd card with libreelec image from here - without dtb file and with right remote.conf file.
  2. Make this changes in u-boot from here - usig UART for multi-boot
  3. Insert sd card in VIM and power on
    Is that all and in the correct sequence. Any advices are welcome. Regards.
  1. Yes, at this point all right.
  2. No. This paragraph needs to be other steps. If You want to use the UART to enable the multi-boot with stock firmware, Android (pay attention to the regular firmware is Android one, which is located in VIM when shipped from the factory).
  1. connect the prepared SD card
  2. power on VIM
  3. stop loading u-boot
  4. run these commands

fatload mmc 0 1020000 aml_autoscript
autoscr 1020000

This will start a script that will perform the activation of the multi-boot and automatically restart VIM, and then automatically starts the system with the prepared media. If you pull out (poweroff VIM) carrier , turning on the power supply, without external media will run regular Android

Thanks for now. I will try it. I am newbie and should read more.

Collected image LE (Krypton) for Khadas VIM. After writing the image to media - in the manual copy and delete is NOT required, all you need is in the image. To use you only need to activate the multi-boot and you can use the image. Support is installed in the internal memory (eMMC). Pay attention that this version works correctly with standard Android, for version dualOS, you must perform additional manual operation.



Can You tell me how to make this step?

Is it possible to run LE from eMMC?

You can use the standard activation procedure of the multi-download through the app “UpdateLocale”. Here is an excerpt from the description RDFTKV.

0.) To download an image, unpack, write image to media (SD or USB).

1.) With the Vim running Android, insert the prepared card (or USB flash) in to the Vim’s SD slot or use a USB card reader (or USB flash to USB).
Note: I like to use a card reader with activity LED, so I can see something is happening. The first boot can take a few minutes and the flashing LED is reassuring. :slight_smile:

2.) At Android/Settings/About Device/System/updates.
From the Update and Backup App, under the UpdateLocale section, click Select, select, click update.
Note: Leave “Wipe Data” and “Wipe Media” unchecked/unticked. To be clear, do not use those options
-The Vim will reboot, it will do so a couple of times.

P.S. I will be very grateful to those who will make a video on how to activate the multi-boot. It’s all very simple, but it is better “to see once than 100 times to read”. :slight_smile:

1 Like