Where can I find the dtb.img file for WP2?
For WP2, you need to use a different image.
To all
Update image 20180814 (kernel 3.14).
Posts by balbes150
-
-
I have successfully installed and run your Kodi 18 (Leia) images for S812 - on an M8S OTT box (AP6330) on a USB stick.
I have tried both the MXIII_Plus and LAN_100 images and they work fine...except for the remote control.
I'm using the original remote control that came with the M8S.
I have tried a couple of "remote.conf" with no luck (from an M8 and an M8S)
Do you know of any "remote.conf" file that might work?
In the current version of the kernel S812 no support for the remote control.
This topic is for discussion of the version for S9xxx . For version s812 used another topic.
Hi balbes: your Version is not compatible with COreelec Version. i cannot simply update your latest development Version on Coreelec latest Version eventhough both are of 64bit Version.
These versions are not compatible, do not try to upgrade, the original system will be destroyed.
The image LE-9 with the kernel 4.18.
I am looking for volunteers to test the system installation mode in eMMC. A prerequisite is the presence of the UART console connection.
Please note, this is a test version and it has a lot of mistakes. I strongly recommend not to use it for beginners.
-
X96 mini -> S905W -> dtb p281
-
Hello, Thank you for your explanation on the latest version. I just installed it. I see that my AZERTY keyboard is still not recognized as a AZERTY keyboard by LE. It's disturbing
Do you think you can solve the problem?
The LE developers are aware of this problem and are working to solve it.
-
All versions that I collect are designed to be written to external media and the initial launch of LE is necessarily performed from external media using universal multi-boot (the standard firmware in the eMMC remains unchanged). If after testing the LE system from an external media you are satisfied with the LE operation, you can run the installation or copying of LE to eMMC. If you select "Reboot from install eMMC", LE will replace (erase) the Android in eMMC. Choose this option only when you exactly know that you will be able to restore the TV box when it crashes. If you select "Reboot from copy to eMMC", LE will be additionally copied to eMMC and Android will be saved as it is. Please note that the copy mode works only with the new version of the universal multi-boot (which is part of the latest images). Therefore, if you have previously activated multi-boot and want to use copy mode, you need to re-activate multi-boot using the latest LE images. In case of any errors in the copy mode, you can still run regular Android. I mean if the copying is not correct, only Android will be started. But since this mode is new, there are no standard situations and you need to be ready to restore the system using a USB cable and USB Built Tool programs.
-
Updated version of 20180726.
In this version added a "parallel" installation Libreelec with Android in eMMC (menu off "Reboot from copy to EMMC"). In this mode of installation, Libreelec is copied to eMMC without removing Android and can be run in turn from eMMC either Android or Libreelec. Due to the fact that Android does not have a reboot mode in LE, LE always starts first, to start Android you need to select "Reboot from Android" in the menu to turn off Libreelec and the system restarts in Android. Pay attention, in the copying LE in the eMMC completely remains the whole Android system (all modes Recowery, etc.). Please note that this is only a "copy to eMMC" test, it may be errors. It is currently only tested on the regular firmware Khadas VIM1\VIM2.
-
Update to v20180717
-
Then I tried with a nocompat.zip extracted to the sd card
The @AN instruction is intended ONLY for starting the system from the eMMC (all steps must be performed accurately).
So my question is, how do I boot your Leia build? Which steps "Note that those users who exactly perform the steps"?
I repeat for the last time. Download. Unpack. Write an image to the SD card. Once to start the system using the toothpicks (to start the system or not). Pay attention NOT to run any images of Demetris using a toothpick until you check all the following options of the startup of my images. If the system does not start from the Sd card, burn the image to a USB flash drive. WITHOUT using the toothpick method, only connect the flash drive and power on the TV box. If after 5 minutes the system does not start, turn off the power, move the flash drive to another connector (during the tests, turn off all USB devices). If the system does not start. Download the second version of the image (LAN_100), write on a flash drive and check it. If no manipulation helps, run the Demetris image through the toothpick method and don't try to run my images (dtb in my images is not suitable for your TV box model).
and a new dtb.img,
Where do you get the new dtb ? Have you tried running with the standard dtb from the image ?
-
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/8Possible 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) ?
