can you tell me how to add the Autoscript line into Boot.ini pls?
Odroid C2 Temporary run images from USB - Amlogic - Armbian forum
Please note, the script s905_autoscript is in all my images, download it further is not necessary.
can you tell me how to add the Autoscript line into Boot.ini pls?
Odroid C2 Temporary run images from USB - Amlogic - Armbian forum
Please note, the script s905_autoscript is in all my images, download it further is not necessary.
Update images 20180622.
I have a box hardware is S812, 1G ram, 4G Nand, 100M lan, RTL8189 WIFI, I tried the ROM you provide in the thread, but it can not boot up, I burned it in TF card, but the sytem reboot all the time, evenI replaced the dtb file from original Android ROM.
Try to delete the aml_autoscript script after activating multi-boot. It is also desirable (after activation of multi-boot) to check the launch from the USB drive.
The only thing I couldn't get running is booting from SD / USB. When I was trying to install it, it only reached the LibreElec Splashscreen and then rebooted.
Describe in more detail what steps you did to check the startup from SD or USB.
Update - I reloaded a formatted SD card with demetris's 8.2.2 for MXIII_plus and a .nocompat.zip that I have been using for his builds and installed Libreelec successfully via toothpick. I gave the box a few minutes to update and then tried installing the balbes150 June 1 tar update for the MXIII_plus a couple different ways:
- In Windows I opened the box IP and added balbes150's June 1 Leia for MXIII_plus and a .nocompat.zip (used for installing demetris builds). I toothpicked the SD card. The install failed as before, per the picture in post 781. Eventually the box rebooted back into 8.2.2.- The second attempt I opened the update folder and copied balbes150's June 1 Leia for MXIII_plus. I then extracted the .nocompat.zip I use for demetris's builds and copied that file into the update folder. I then booted the box, Libreelec installed successfully this time, rebooted and then got stuck on the boot/Libreelec splash screen. I restarted the box and it got stuck on the same splash screen again.
I'm not sure what to try next or if I am following the right steps. Should the .nocompat.zip be installed prior to running balbes's image?
I have already written to you many times that Demetris's multi-boot system is incompatible with my images. Therefore, all your "hybrid" experiments do not give results. You cannot upgrade Demetris image SD \ USB to my version and Vice versa, its images do not have the necessary s805_autoscript scripts, without which multi-start does not work. I do not understand why you ask questions and ask for step by step instructions, if you still do it on your own (not following the step instructions). If you want to get the result - follow the instructions exactly. Note that those users who exactly perform the steps get the working system or to SD\USB, or eMMC.
Update version 20180621.
Pay attention. When run first the configuration wizard, it may take a long time to poll existing networks (the more networks around, the longer the survey may take). You can wait until the survey is complete or go further and set up the network later.
Took the image for a spin. Here's how it went down on my box
Booted up. Couldn't read the top ( off the screen) Somethng about I don't know what your are doing. and didnt' want to load the kernel modules.
Different settings are used for different systems. If the system works fine, do not pay attention to such errors.
Test variants of Libreelec KODI-18 (Leia) images for s812.
There is a separate theme for the s812 models. If multi-boot is enabled, you can try to delete the aml_autoscript script or use a USB drive.
Hi ... the latest version of Leia from 06.13 does not run through a toothpick ... when the first version was launched .... what could be ???
Mini MX 1/8
Possible cause: you have not added the correct dtb.
Does it work on Odroid C2 ? which dtb file should i use if i am coming from kszaq 8.2.3.1 ?
I didn't check on the Odroid C2. In theory, it is possible that you want to add the "s905_autoscript" script line to "boot.ini".
Latest test version of the LE for s912 (which is located in the catalog 20180613).
When you mention "perform the activation of the universal multi-boot" I'm assuming you mean to toothpick boot the SD image?
I burned the latest image you posted for the MXIII Plus dated 0601 with Win32DiskImager and then toothpick booted the image. The only complication is that this box has an on/off switch which has to be pushed after toothpick - power - then the switch pushed on.
The problem is as follows - if I keep the reset switch on waiting for the LE splash to appear it never appears. The Beelink splash image comes on and then off every 3 seconds. If I release the reset switch the Beelink splash stays on for about 7 seconds then goes off and about a second later the Libreelec splash comes on for about 17 seconds and then goes off. 3 seconds later the Beelink splash starts again. That is all that happens and I've tried numerous times.
The SD card I had Demetris's 8.2.2 running on this box on no longer boots into Libreelec.
1. According to the description, multi-download is already activated. Try renaming the aml_autoscript file to old_autoscript or deleting it. And try running without this file.
2. If that doesn't work, try to run the KODI version-17 with that of the memory card, and write the result.
I downloaded your Armbian build: Armbian_5.44_S9xxx_Ubuntu_xenial_4.16.1_mate_20180515
Use images with kernel 3.14.
Is it normal that, as above: "aml_dt=gxm_q201_unsupport" even though I have the gxm_q200_3g.dtb in place on SD root as dtb.img?
Could this explain why my ethernet is completely messed up?
Try to run one of the Armbian (Mate\XFCE) variants from an external media and see how the network works with different dtb. Armbian is a normal Linux installation and it can easily change and store different settings for Internet and to check network performance. Boot to activate is no longer necessary (it is common with Libreelec of my assemblies).
Its always the same with every build i tested.
several reboots and tries to save manual wired network.
then it doesnt reboot.
restarting box and then i can save network settings.
What medium is used ? What dtb is used ?
Am I correct in having no dtb.img in the root of the SD card?
If you have any problems with the hardware, be sure to check the use of different dtb from the image.
So far, everything seems to work fine, though my remote controller is not working (buttons seem remapped). PS4 controller connected with USB cable works fine, though.
For the remote control you need to create your own version of the settings. and put it on a carrier. Description is earlier.
I installed
LibreELEC-S905.arm-18.0_20180608.tar on my T95n 905x, which was running previous libreelec stable from internal memory.
Reboot and hangs at the AMD image. Probably have to do everything all over again.
These are test builds, so I recommend checking from the beginning to run from external media.
just a thought, but I remember when I installed the first time coreelec on my khadas vim, I had to update my dtb file. With the old dtb, my remote didn't work. Maybe there should be done something there.
There may not be enough parameters in the dtb file, I am studying this option.
Hi! For me everything works in sd, but I cannot get the installtointetnal to work, I mean, after I do installtointetnal, then reboot and then Recovery screen, what am I doing wrong?
You have tried to use the installation through the shutdown menu ?
does your leia build still use remote.conf?
No
is it possible to turn off amlogic noise reduction? For example like it's made in alexelec? Or this could be default setting without GUI
Does AlexELEC use Leia (KODI-18) ?
is the "please_resize_me file" problem resolved? I don't have a Linux machine to resolve this problem.
I think this problem is related to the garbage in your u-boot. Try to install the standard Android firmware from your TV box via USB Built Tool (to clear all the accumulated errors in the internal memory). And then perform the activation of the universal multi-boot.
So it seems meson-ir is not used by the system.
I have not yet published the changes to git that are used to build the latest s812 image. The meson-ir driver is built into the kernel.
can it be possible you should change
Option "amremote" disabled in the settings.
-> on your github page it's still there
Now I will try to remove " remote.conf " and collect a new image.
Is it possible to install your S802 Leia build on internal storage?
It's in the process of checking. Maybe in the next release it will work.
The new version 20180601.
Working repository Addons Libreelec (thanks chewitt for the added link for s812).
Added support for the remote control, but I can not figure out what is the reason that "ir-keytable" does not accept codes from the remote control. Perhaps need additional settings, but I do not know what is missing. I will be very grateful if more experienced users will tell me the reason. By the way, there is "mc" in the image (which can be run via SSH), for quick editing of settings.
Maybe it is indeed missing module meson-ir as stated in the error message of systemd.
I haven't checked the remote control yet. I may be able to do this check soon.
Display MoreI have a box S905D p230 2G/8G, I had try LE8.0 and LE8.2.3 and LE8.9 all dont work,can not startup.
and then use yours Armbian 5.4.4 mate 20180523, I could start whth "meson-gxl-s905d-p230.dtb",but when into startx have a error Tip, in left up coner just have firefox , not more, so could not do anything,and cannot shutdown reboot. i can play desktop test.mp4 and test1.mp4 . too slow graphy.
at time,I find this ,yours LE
I just download your LE, hope fun
sorry for my poor english
can you tell me how can i boot LE8.2 use which dtb file ?
1. That would not confuse users Libreelec, discussion Armbian need to do on the forum Armbian.
2. For the image LE you may try all options dtb gxl_p212* gxl_p230* gxl_p231* gxl_p281* .
For all. Update versions S905 and s912 arm 50180601.
Thanks for the tests. Yes, a problem with different aml_autoscript is possible. Therefore, it is desirable to run with clean firmware. In this case, there will be no impact from old "tails" (incorrect data). Errors in systemd are not critical, it is from different module variants. Installation in the eMMC is still in the process of verification. I have only one unit of TV box with S812, which is intensively used for different tasks and therefore has some problems with the healt of the eMMC.
I'm struggling getting the Netflix Add-On working on my Minix UH-9 with CoreELEC. Is it worth trying to update with LibreELEC-S905.arm-18.0_20180522.tar?
So you can not update, it's different systems.
Would be helpful if you could start another thread for Leia S802/S812.
Perhaps the moderators can split this topic and make posts about Leia in a separate topic.
I see on the download page there is a folder for the 100Mb network with two folders, both with an image. What is the difference between all the 100Mb images. I used the one from the front page.
Try to test all three variants of images. They use different kernel and configuration options.