- Hey. Try to install the coreelec 9.01 image on the sd card from https://coreelec.org/. My Vorke Z5 device is also based on the p281 platform so it can work for you. You can also try the image from https://test.libreelec.tv/ by selecting S905. For the image to work, it may be necessary to copy the p281 dtb tree to the root directory and change its name to dtb.img. How will it not work, combine, try again.
Vorke Z5, Amlogic S905W. For me, images for Kodi Leia 20190114 kernel_4.x does not work network / wifi card. I did not check the cable.
I hope that there will be. It takes time to fix the errors that I have when building new images for S812.
I think, that need create a new subject for models s812\805. Because this topic was discussed in the version for the S9xxx. Infa about s8xxx confuses them (it is absolutely different versions).
The new version of the images for the S9xxx 20190114. Pay attention. The names of the images have now changed to refer to the whole group for which these images are suitable S905 (S905 S905X S905D S905W) S912 (S912). All previous images were also universal, but apparently many users were confused by the use of a specific model name (Khadas_VIM\VIM2). So I changed the name of the images to universal. The principle of use has not changed. To select the desired dtb, edit the file "uEnv.ini "(or " extlinux.conf" for those who switched to using the new u-boot-2018).
Thank you. In that case, I am waiting for new images for S812.
If you have a problem with booting from the SD card try to start the system using Android and the file from the update.zip pendrive.
Hello. Try balbes150 images for s812 ( Test LibreELEC images with KODI-18 for S9xxx )
Start with the image LEIA-18/20180910 and update to the next version with the TAR file. I have a similar box, i.e. M8S with the same remote control, and here the remote does not work. You must find or create configuration files yourself.
These do not seem to be SOC dependent.
I would try the 'boot from SD card, use internal memory' guide first.
I'm not balbes125 (obviously), but on his behalf, can you expand on what you mean by "The "installtointernal" command also does not work".
I've had issues with this recently and could suggest two things:
1) DON'T install to eMMC is the preferred option apparently.
See this thread on how to boot from SD/USB, but still get the speed benefit from running off the eMMC.
2) If you REALLY want to boot of eMMC as well, fetch the file manually and try again.
See this post for more details
The new version Libreelec (20190108) on the basis of the kernel of 4.19 works with HW at S912.
It's not all ready yet, but it's working. Tested on VIM2 Basic (everything works except BT), WiFi\BT does not work On VIM2 Pro\Max. On Tronsmart Vega S96 with DTB VIM2 works from remote but not working wired network (and of course WiFi\BT), with native dtb Vega S96 wired network works , but no remote control (I hope soon finished dtb for Vega S96, something was wired network and remote control). All models rotate video up to 4K inclusive, KODI interface has small glitches, but works without brakes. So that can be considered these images sustainable alpha. By the way, ran on all TV boxes with a simple USB flash drive.
hi [user = '350'] balbes150 [/ user]
testowałem twoje LibreELEC-Khadas_VIM.aarch64-9.1-devel-20181229084111-79c10ab.img jądro 4.x z wetek play2, ale nie uruchamia się
i radzę sobie z plikiem boot.ini w pamięci podręcznej boot libreelec
Edytuję nazwę dtb wetek play 2 w pliku uEnv.ini (nazwa_ dtb = / dtb / meson-gxbb-wetek-play2.dtb)
ale nie uruchamia się dla mnie to keep in logo wetek
Dobrze. Wierzę, że są są tym tym wątku. Myślę, że nie robię tego źle, ale wszystko zacznie od początku, ponownie, aby rozwiązać rozwiązać ten problem. Dzięki!
Ok. I believe the steps are in this thread. I think I'm not doing it wrong, but obviously I'll start from the beginning, again, to try to solve this issue. Thanks!
Hi everyone. I installed the latest images for S812 on my M8S from balbes150 on my M8S
and I started with the image LibreELEC-S812.arm-9.0-devel-20180910103037-bdb5a5b.img.gz. I noticed that after unpacking to an SD card using the Rufus application the dtb file is in the root directory and has a capacity of 176kb and in a newer compilation, i.e. LibreELEC-S812.arm-9.0-devel-20181116095151-cbfbde4.img.gz after unpacking by Rufus dtb files, and there are a lot of them, are in a separate directory and have about 21kb each. The method of starting from an SD card with a toothpick was not successful. The only image that started with me is LibreELEC-S812.arm-9.0-devel-20180910103037-bdb5a5b.img.gz but only using the txt file update.zip with Android KitKat enabled. Strange, but only yes. Similarly, I had with the older model Android Box Tronsmart Vega S89 Elite. After starting the system, I updated the system via samba using ES File Explorer, the LAN tab using my Android phone.
PS. Hey balbes150, Is there a newer picture for S812 that I could successfully install on my Android M8S Box. I'm not sure which dtb image fits my model, but I suspect that n200C.
For everyone interested. Libreelec, which works with Tronsmart S89 standard & Elite 2GB, can be found here: Loading site please wait.... I had a problem with starting from an SD card. I used the previously created "update.zip" peak launched from a pendrive / portable disk. I greet everyone.