LibreELEC & OpenELEC for Tronsmart Vega S95

[balbes150]

Hello balbes150, I have tested this LE version on the S95 Meta.
Tested WiFi, BT, LAN and basic function. In the shutdown menu, "Reboot from NAND" rebooted to LE. Maybe I misunderstand that option.
Everything else just worked, outstanding. Let me know if you want me to test something specific.

Thanks for your work on this.

Also thanks to kszaq.

Hi RISCy Dude
The menu item "Reboot in NAND" does not work with my version of multi-boot (using the file s905_autoscript). In the near future I plan to add this feature in my script. If you can, make please a screenshot on your Meta, with a window that displays the system load (as did trebor in the topic i7)

[RISCy Dude]

Screenshot on Meta...

[Altstart]

Can someone please explain how to swap a dtb file with win 7. What software and drivers do I need. Thanks

[balbes150]

Can someone please explain how to swap a dtb file with win 7. What software and drivers do I need. Thanks

You have the dtb file available ? Or a question about how to get this file from firmware (or TV box) ?

[Altstart]

Yes I have the correct dtb.img file downloaded and ready to swap.

[balbes150]

The file dtb.img needs to be on the first partition (FAT). Connect the media LE to your PC and copy (with replacement) your file dtb.img for a media LE.

[balbes150]

The renewal of the image. Added support for restarting the system from the internal memory (menu item "Reboot in NAND"). The paragraph now correctly works with external media. Added in - test support the dtb file from the platform p201 (system based on NAND). For those who have such equipment, please check how would work this way. In the image on a FAT partition, added the files (aml_autoscript aml_autoscript.zip) to activate multi-boot mode "Update&Restore" from the regular firmware Android.

https://yadi.sk/d/Tnbwje1JubcxR

[e123enitan]

The renewal of the image. Added support for restarting the system from the internal memory (menu item "Reboot in NAND"). The paragraph now correctly works with external media. Added in - test support the dtb file from the platform p201 (system based on NAND). For those who have such equipment, please check how would work this way. In the image on a FAT partition, added the files (aml_autoscript aml_autoscript.zip) to activate multi-boot mode "Update&Restore" from the regular firmware Android.

https://yadi.sk/d/Tnbwje1JubcxR

balbes150, Excused my ignorant, this image is for USB? If so any hope Internal drive soon?

Thanks

[balbes150]

This image to external media (SD card and USB flash drive). Image for installing to internal memory is not yet ready for use. The files to install to the internal memory is, but when you try to install to the internal memory , at startup I receive an error that the file system on disk /dev/data is corrupt and the boot process stops. I'm trying to figure out why. Likely to have been changes in source code when migrating from version 004 to version 006. These modifications inhibit the normal operation of the system on models with eMMC memory. About the same write error many users on the forum LE. Perhaps the reason for the updated version of check disk or its settings.

[e123enitan]

This image to external media (SD card and USB flash drive). Image for installing to internal memory is not yet ready for use. The files to install to the internal memory is, but when you try to install to the internal memory , at startup I receive an error that the file system on disk /dev/data is corrupt and the boot process stops. I'm trying to figure out why. Likely to have been changes in source code when migrating from version 004 to version 006. These modifications inhibit the normal operation of the system on models with eMMC memory. About the same write error many users on the forum LE. Perhaps the reason for the updated version of check disk or its settings.

Thanks for your response, it exciting to know that efforts is ongoing on internal eMMC version, I trust with certainty you will come out with solutions to all issues you noted in due cause, thanks again for your continuous support of Tronsmart OE/LE.

Cheers!

[Doggyofone]

You can check these options
1. to try to run LE without replacing the dtb file (use the one that is in the image)
2. if the system does not work, replace the dtb file to the one that is in the current firmware of
3. if it doesn't work with dtb file from the firmware, in turn, try all files in this directory
4. if none of the options does not work, then we need to collect personal dtb file from source

Unfortunately I don't have a dtb file. The install of sd-robots firmware was not from an img file. sd-robots created a restore zip with all of the necessary files to run Android on the MXQ Pro+. Those files were then restored in TWRP. With his firmware the box shows that it is running firmware for a Vega S96_Meta, kernel version CGL@tronsmart Thu April 14.04.32:13 UTC 2016 and Build p200_2g-201604140414.
So in this case if I can get a copy of a dtb for a Meta I should be able to load you LE on this box.
I would appreciate a copy of the dtb from anyone who might be willing to post/pm me a copy.

[balbes150]

The data dtb.img for the new kernel Libreelec, for model Telos Meta Pro are in the dtb.img file which is included in the composition of the image. You need to initially try to boot without modifying the file dtb.img. If that doesn't work then try the files from KSZAQ from consoles with similar parameters.

[Doggyofone]

The data dtb.img for the new kernel Libreelec, for model Telos Meta Pro are in the dtb.img file which is included in the composition of the image. You need to initially try to boot without modifying the file dtb.img. If that doesn't work then try the files from KSZAQ from consoles with similar parameters.

OK, thanks for clearing that up for me.
Well I've tried on two different working SD cards and a good USB stick and all I get is a blank screen.
I'm not sure dtb's kszaq has listed would be close to what I have. I'm surprised that the Meta Pro dtb doesn't work. Your 6.95.3 works really well on this box. I tried the dtb from that img and got a blank screen.
After all that I put in my original 6.95.3 sd card in with your image and OE boots right up.
Its a mystery.

[balbes150]

Which files have You copied on the card with OE ? Which file system start ? The problem with the new image LE (006) that now uses a new kernel with a different algorithm use the dtb data. For new kernel you need to use the new dtb file (which added and changed data).

[Doggyofone]

Which files have You copied on the card with OE ? Which file system start ? The problem with the new image LE (006) that now uses a new kernel with a different algorithm use the dtb data. For new kernel you need to use the new dtb file (which added and changed data).

I used your image with the supplied dtb from 2016 08 30 on 2 different formatted SD cards and a formatted USB flash drive. I just rebooted the SD on my MXQ Pro+ that has the sd-robots rom ( Vega S96_Meta, kernel version CGL@tronsmart Thu April 14.04.32:13 UTC 2016 and Build p200_2g-201604140414) installed. The screen went blank.
When these attempts didn't work I tried the dtb.img from your OE 6.95.3 which did not work. When I put the 6.93.3 sd card back in OE loaded no problem.
kszaq's instructions are to download a dtb from a list of available dtb.img for different boxes. There are no vega dtb available.