Hi balbes150
The idea of your build is test the kernel 4.12 or Kodi 18?
You have choosed 2 key elements that are unstable, maybe you should downgrade one of them (based on your own interest).
If you're interested, here's the test image with kernel 3.14 and KODI-18.
Thank you for the test. This is good news. So to test with new kernels can use a lighter system.
Sorry, forgot to give the link on the right s905_autoscript.
If you don't mind, please try to check the launch of this version of the image with sheath SATO on the model Wetek. Download
sdimage-SATO-201708281721-S9xxx.img.xz . Unzip. To record on the SD card. Download and add to the first section of the script s905_autoscript. Add the script "boot.ini". Rename the appropriate file of the dtb to the "dtb.img" (all available files are in the root, it is sufficient to rename). Try to start the system. I'm interested in the system start-up. If possible, it is advisable to check out a run from a USB drive.
boot.ini from ubuntu 16.04 wetek2 iis work
The script "boot.ini" for model WETEK, which may partially replace the activation of the universal multi-boot (which uses a script s905_autoscript). The order of use. Burn image on SD card. Add the correct "dtb.img" in the root media. Add the script "boot.ini". To connect media to the TV box and turn the power on. Pay attention to the nuances. The script "boot.ini" only runs from the SD card, but the operating system (LE or Linux) can be recorded to any external media (SD card or USB flash drive). To start the system from USB stick to TV box must be connected to two media - SD card "boot.ini" and USB stick with the desired system (which uses the script s905_autoscript). If you need the system is recorded on the SD card, you can add the script "boot.ini" and to implement the recommendations that are prescribed for the system, for example , add correct dtb file. Pay attention to the use of the image LE from this thread, for Wetek need to pick up a working dtb file from the directory /dtb on the media (copy it to the root and rename to "dtb.img").
I need the output of "printenv" and "help" (u-boot), is to write the correct "boot.ini".
Maybe I'm wrong, but as I recall, there need to activate the GPIO port (by default it is off) that would have included power to SATA adapter. I have not been able to obtain from the manufacturer info, which ports are needed for this.
Yeah, there is something weird with the script that sets up the multiboot for these boxes. Also, the one from the balbes150 image does not work with the demetris image and vice versa, so it looks like there is not a standard approach to applying the multi-boot ?
On a positive note, the new image did work on a MXiii (S802 chip) by using toothpick method by SD but then inserting into USB to boot up. However, as I said, after doing this, the Demetris image would no longer boot from USB and the whole SD/Toothpick/Then_USB_Boot process had to be done again.
So I am wondering if the multi-boot thing could be looked at to get the SD card booting up and perhaps at least the method could be standardised ?
There are several multi-boot options.
1. The "old" option which strictly prescribes that the loader can run only one system (all parameters and file names as fixed in u-boot). This option is used in the Demetris.
2. "Universal" - which uses a special script (sXXX_autoscript). In this embodiment, the activation of the multi-boot is executed once and no longer required. You can run external drives any system (Libreelec Linux, Android etc). Each system is composed of the image its a script that takes into account all the specifics of this system. All the necessary data and steps provided therein, on an external drive and not change the boot loader u-boot. This option I use in all my LE systems and Linux (ArchLinux Armbian OpenSUSE etc).
3. A combined version. Which uses Kszaq. The system activate the multi-boot using the old version, but he, at my request, added to the image script s905_autoscript that allows his images to run in both systems (old and universal). True, he hasn't updated this script and he does not use the new features. To assemble a script that will allow you to run images of Demetris on any-boot options is not difficult, I have laid out a script. I already proposed Demetris to include in his images, this option (to have compatible images), but he did not answer. Perhaps he has good reasons for this.
I kept getting the 120 second error, so I did what you said here. I wrote the same image to a USB stick and did the toothpick install - GoogleTV logo comes up and after ~30 seconds the box goes into recovery with a message that E: Cannot Load Volume /misc!
I tried turning off the box, inserting the USB stick and then turning on the box. Google TV logo comes up and the Android boots.
OK, I exited from recovery (the original MXIII-G recovery) and the box booted into LE. I'm not all that confident yet, but so far so good.
That didn't last very long. The box now reboots into Android no matter what method I use.
I have written many times that the activation of multi-boot is possible ONLY WITH SD CARD. After a single activation multi-boot from SD card, you can start the system from USB stick or SD card.
Only when booting up the device and the bootscreen comes up there is some text on the left side of the screen in the new version this is solved a bit with some less text is it possible to hide this so we have a nice clean bootscreen ?
Also when you shutdown the device and and you want to power it on again you need to pull out the power cable and plug it in again and then push the power button, is it possible to fix this?
1. To remove the output of strings when you start possible.
2. With the support of the right off more difficult. Need to study the code of u-boot and the remote control, try to adapt. Unfortunately I don't have this model TV box that would perform and test these adjustments.
The last version to work correctly with an SD card was LibreELEC-S812.MXIII_Plus.arm-17.3_20170622 , is there any way you could look to see why this works and later builds do not, you would make a lot of us happy fixing this
Lately there are many changes in the kernel, maybe they're not all compatible with older models. If I get the chance (time) I will try to study the problem. For reference, I only have one model Tronsmart TV box MXIII Plus, it runs everything, so it is difficult to control the cause of these changes.
Display MoreI have only one issue - the HDMI port will not output sound correctly.
I plug my MXIII-G into a Yamaha AVR (RX-A3020), which supports DTS-HD MA, DDTrueHD etc.
Now I realise that I may not get the MA or TrueHD stream with one of these little boxes, but I SHOULD at least get the “core” audio streams being passed through HDMI to my AVR.
So in the case of:
DTS-HD MA stream, I should still get the DTS5.1 (lossy core) stream, and, for,
DD TrueHD stream, I should still at least get the DolbyDigital5.1 (lossy core).
Under Wilro’s build that’s how things worked.
Sorry, I'm not ready yet to determine the cause of this behavior.
Does this run on Odroid C2? I can supply UART output if you need.
Yes, this is possible. View this topic. It describes how you can easily add to the existing system on the SD card or eMMC module on the Odroid C2, the ability to run from USB. Or easily transfer run from eMMC to SD card without pulling the module eMMC (or Vice versa). Pay attention that the current system on the SD card or eMMC module as not changed. Ie. if connected USB flash drive is the launch of the system from it (it can be any system - any option Libreelec or Linux). If you disable USB flash drive will automatically start the "internal" system on the SD or eMMC. If not clear, ask, I work a different system on Odroid C2 in various combinations (USB SD).
Odroid C2 Temporary run images from USB - Amlogic - Armbian forum
i test sdcard and usb
I see you have the UART console and in the log there is an indication that your u-boot has the ability to use the script "boot.ini" is good. Show the output of "printenv" and "help" (you need to stop the run u-boot by pressing spacebar and execute these commands).
Be aware that 4.12 kernel has no support for hardware video decoding.
This version is only for testing. It is needed for the initial evaluation of the new kernel on different models.
i tested my device wetek play2 is not booting
how are boot this?
Can you show the output of fw_printenv (which shows variables from u-boot) ?
The main source Neil Armstrong. I added multiboot, all arranged and assembled in the desired form.
Want to try LE with the kernel 4.12 + KODI-18. Download the link image. Unzip. To record on a USB flash drive. Work with the SD card I have not yet tested, probably will work. Rename the file to “dtb.img”. To connect to TV box and run it. Need to control a connected USB mouse.
This is an alpha version so there are imperfections and bugs.
Mandatory condition - the presence of an activated universal multi-boot. If it is not already active or you are using an older version, you must update the multi-boot to the latest version. All the necessary files are in the way, use the toothpick or via the installed app "Update&Backup".
Now record the same image on any USB flash drive. Turn off the TV box. Connect the USB flash drive and turn on the power of TV Boxing.
Try this procedure. To download the image LE. To capture the image (not changing after recording). To connect to the TV box and use the toothpicks. The system shall automatically update the multi-boot and start. Pay attention, all the latest images have all the necessary files, anything in addition to download and burn don't need.
MXIII_plus 20170801
Will fw_printenv output the correct information even if I'm booting from emmc? I already installed to emmc using install.sh from the init shell.
Yes, this command will show it as prescribed for a multi-boot in eMMC. I can add the output of "cat /proc/cmdline".
I know how to force rgb with my s905x and my s912 but this setting not work on my 812.
What steps do you use to s905 ?
I've a TronSmart MXIII 2GB/16GB. Till now every new builds install without a problems (sd card), but with latest build - after 20170614 - libreelec stop on install with "file corruption error".
Trying to install the 20170704 build too, but same "file corruption error". Reinstalling build 20170614 and install works fine.Now I'm in fear when upgrading cause lost all my customizations and configuration.
Any solution for backup and restore entire sd card after a broken upgrade?Thanks
There are several backup options. 1. To create a settings backup using normal mode in KODI. 2. Make a full backup of the entire SD card through the program on a PC
Display MoreTried Demetris versions but my box will not boot from SD Card or USB. #940
I don’t have Lan 1000 Ethernet available on all your images ?I understand there are 2 Burning steps.
First i am to Burn the img.xz onto an SD Card and toothpick method to activate Multiboot.
What should happen after this first toothpick method after releasing toothpick as this is only to activate Multiboot.
I am not sure what the box will boot to ?
Will it boot to a version of LibreElec ? If it does, then i’m clear on the rest.
Second step is to then burn one of your LE Images onto an SD Card, insert into box, power up and the box will boot into LibreElec.
1. Burn image on SD card.
2. To activate the multi-boot (using a toothpick)
3. Immediately after activation, the system will attempt to boot from the SD card. If the SD card can earn, no additional steps are not required. If the system will not be able to start from SD card, you need to try to write the image to a USB drive and test to run with USB (to connect a USB drive to the TV box and turn the TV box).
How to install on internal rom (Nand)?
To install to the internal memory you can use the menu item "Reboot from install to eMMC" in the mode of shutdown\reboot. When you reboot the system will automatically attempt to install LE in the internal memory.
I can't seem to locate where the /flash mountpoint is even specified, is the aml_autoscript supposed to do this? If so, what parameters? Currently the script is mounting the internal memory's system partition with the build.prop inside for android instead of /dev/mmcblk0p1, where the SYSTEM image is located.
If we can get past this we'll have a fix for the bcm4335 variants.
You have activated the correct version of multiboot ? Show the output of fw_printenv.
For anyone who when you start from SD card with error "corrupted file system". You need to burn this image to a USB and check the run USB. To write the image to USB, connect a USB drive to the TV box and turn the TV box.
Indeed on the 2 latest builds (also MXIII-plus) the libreelec splash screen is gone. I get a "no signal" message on the screen. But libreelec works. Wait a little bit and suddenly the kodi screen appears. I had the same issue yesterday and downgraded again to the 14/06 build.
The bug of no screen saver is fixed in the new image 20170704 (now there is a download on the website).
