1. Updated test image for Minix (20170514).
2. Question to those who uses the image MXIII_Plus, please compare how it will work the way LAN1000. Is there a difference in behavior. I want to leave one of these options. I have both work the same.
Posts by balbes150
-
-
Unfortunately I haven't been able to get this Minix to boot from USB, and had a lot of different suggestions to try.That is why I bought the sdcard which seems okay. The 04 file boots okay though. Odd
Write what steps you did to activate the multi-boot.
Just an FYI, I can't get anything except the n200 AP firmware to work...n200 and n200C a different platform
i opened system folders and the Minix bcm is showing as bcm 4339 not 4335
Then it turns out You module 4339 this WIFI module AP6335 (bcm4339) ? -
Tried the new 05/13 file. unfortunately same error when booting starts then says corrupted file.Use a USB flash drive.
-
For those who have versions of the images 20170510 and they do not run external drives, try replacing the script s805_autoscript at the root of the first partition to this.
The audits found that very often the reason for the poor run LE from SD card is poor compatibility of different SD cards with the card reader in the TV box. Therefore, anyone having problems running LE from the external media, we recommend to test the startup with USB stick.
-
Uploaded a corrected version of the image MXIII Plus (20170513).
[hr]
Anyway, here are the 1G/8G dts and dtb files for both the AP and BCM versionsI'll see what I can use from these data.
-
I found in the error images with the launch. Please don't use images version 20170510.
-
Anyone can try the new test version for Minix\bcm4335.
Pay attention, I have not tested this way. -
hi I have tried several files on my mxq s812 m10 m8s and I cant seem to enable multi boot if my life depended on it. I have tried using s805 auto_script and it errors right off the bat. I do what you say and update inside of android and nothing always error even with the universal. also yesterday I had got it to flash using usb tool but its a different rom (m8s) and its a (mxq) also I cant find any device tree files. its using n200 so I'm lost haha I'm sorryto activate the multi-boot you need to use the SD card. After a one-time activation multi-boot , you can use USB media to embed the image.
-
I have tried the new image from 05-10 and I get the screen below.You are trying to run from external media to new system or it is the result after upgrading ?
[hr]
I installed your build 20170418 as perfect works except wifi and bluetooth. How can I use it?Unfortunately, I can't check, I have no such equipment.
[hr]
I'm sorry but I can't follow you... I downloaded the image for my minix x8-h plus and try to boot. Impossible. Well, I changed one file named s805_autoscript with another downloaded from your directory. Also I changed the name for aml_autoscript. Boot again and now, minix said that can't mount flash...
Now I read I must downloaded boot.src? Excuse me but at this point I need, please, somebody makes clear information about the method to use libreelec with minix x8-h. ThanksTo run these images, you need to activate multi-download.
[hr]
I have a LeeBox MS9 812 TV Box. When I use the tooth pick method with any of the newer images it just boots to the LeeBox Image screen, then to a black screen, I see a "reboot" message flash in the bottom left of the screen and it will continue the cycle over and over again. Any suggestions?delete from media (after one time use) script aml_autoscript.
-
I've taken a bit of old @surkovalex and mixed in a bit of current kszaq and come up with this LE 8.0.2 Kodi 17.2RC1 image for the MINIX X8H+Hi. I have a suggestion, why the image does not start. I can see several files that were used for Assembly ?
-
-
The steps are: download de test img en put it on a sd card with imges progam, and put the dtb file on the card (dtb.img)With dtb file i get black screen em without also. No working i guss
I uploaded the new version of the test image TEST_DTB for direct work with a separate dtb. Try it. In the DTB section on the website updated files for the different models.
Thanks for the answer, my TV was not able to switch to the native resolution probably . I see listing text unreadable static logo or picture would look better. Nothing it is just detail
For information
I installed on my box MXIII-G 2/8 update 20170418 completely disappeared Wifi drivers on both versions (LAN1000,MXIII_Plus)Try the version M8S . If that doesn't work, you can try a test version TEST_DTB with a separate dtb file (NOT use the version TESD_DTB for installation in memory).
-
Version 20170418. Changes in the structure of the dtb data in the images MXIII_Plus , LAN1000 , M8S
I test the test image on my m8s, but it not work also with the dtb file.
Can someone help me?I have a ott m8s
Describe in detail what steps You did and what the result of these steps.
Display More
Dear balbes150!
I have MXIII-G (2/8G) first version and I used the installation LibreELEC-S812.LAN1000.arm-8.0.2.img.gz and LibreELEC-S812.MXIII_Plus.arm-8.0.2.img, both firmware work fine all peripherals (Lan, WIFI), the only problem at the start, I see attach. photo and not logo libreelec, then appears Kodi.
It's alright?
I have tried boot loader for Android 4.4 KK and 5.1LP the same result
Thanks for the info, I apologize for my English
Huge thanks for the effort, balbes150!If You mean that the screen with the strata run-line with the text of the boot - that's normal.
MXIII Plus on 4-14 having trouble pairing with Bluetooth remote. I don't recall this being an issue with 3-22 build however it looks like you deleted that build folder?
Any chance you still have that build saved so I can confirm? Thank you
Try the latest versions of the images (LAN1000 MXIII_Plus M8S). I have limited space, so I don't keep backups.
I have a MXIII 4k S802 2G/8G box with the ap6234 WiFi chipset my wifi is not working any idea if this is supportedSorry, but I have no such equipment, so I won't be able to help You.
-
How can I do this?Start LE, enable SSH in the settings to connect via SSH, execute the command "fw_printenv".
Are you saying your build will recover the dtb from the android box and use it? If that's the case, that's pure genius.The principle is the same as in s905. Pay attention, it does download dtb from internal memory to external memory in the form of an independent file, and only the use of these dtb data (from internal memory) to run the LE and Armbian.
Does it means: One image to rule them all?Yes, it is planned that-it was not a monolit system (which is not possible to change without rebuilding the entire image), and modular design, the user can combine yourself. Kernel + dtb + SYSTEM.
-
I uploaded the test image LibreELEC-S812.TEST_DTB.arm-8.0.2.img.gz and a set of test dtb files for separate use. This version of the image allows to use a separate c file dtb data. To use. After writing the image to media you can try running the system WITHOUT the dtb file. The script will try to dtb data from the internal memory and try to run them the system. If within 5 minutes of not going on the appearance of images on the screen, you need to add to the media one of the matching files, and rename it in the "dtb.img". You can try all the dtb files from the site, trying to get a working system.
Pay attention, this image is NOT INTENDED to be installed in the inside memory. If you try to run setup - you will receive a brick that need to be recovered.
In the near future I plan to upload additional versions of SYSTEM files with different content and settings WiFi network and BT. These files SYSTEM can be combined with different dtb files, is to try to pick up a working system (WiFi and BT).
Link to the test directory.
Yandex.Disk
[hr]
What am I doing wrong?
I tried both ways on my m8s and get same thing.Note that multi download version works on Android >5 on version 4.4 is not working.
[hr]
When I remove SD card system boots normally form box RAM with old Kerber's Libreelec 7.0.2.001 (Kodi 16.1) which work perfect.Show the output of fw_printenv after completed the multi-boot activation.
-
I just downloaded the latest build and I still can't get it to install.What specific image are you trying ?
1) Would it be possible for you to post the latest install instructions in the first post?When I can find time, I'll try to rewrite it under new conditions.
2) Could you also include a troubleshooting section that addresses such as manually activating multi-boot?ok
3) Finally, what is the easiest way to get the dtb? Is it a single file I can pull off the restored box?Sorry, I don't understand the question. (I use a computer translation).
Also for m8s?These points do not depend on the model of the TV box, they are common to all images.
is there any way to produce LAN1000 image which could be booted as AlexELEC?
I didn't succeed to boot any of your images, but AlexELEC work fine with SD card.In the image AlexElec used the old scheme of a multi-boot that can run only the image AlexElec from the external media. To run all the system from removable media, you need to preactivate-boot on new version (using the script aml_autoscrip from the composition of my images LE or Armbian). Run all the images are universal. To start AlexElec will need to add to the media with its additional script s805_autocript (assembled specifically to support AlexElec).
-
Update images Krypton\20170413. Fix reboot in NAND and Recovery.
-
The box use to show the start picture of the Finless Bob Rom for nearly 15 seconds while reading the usb stick. After that libreelec picture is shown with error.I understand that LE starts, but gives an error that can not mount the desired partition ?
Gave it a shot but no luck on BCM4335. I had also tried the Alexelec build which was supposedly built for BCM4335, also didn't work.Would it help if I got you DTB? If so how do I extract it from firmware?
Send me your dtb, I'll try to put the version from this file. But I can't guarantee it will help. To find the error to test on real hardware to see at what stage it fails. I don't have that model TV box, that is to perform validation and debugging.
[hr]
hi, I have the same problem with M8c s812 1gb box. The box fails to install libreelec from card. It hangs or goes into a loop if reset button held to long.1. No need to hold the button for a long time, this does not help run.
2. If the screen is black for a long time, then activate the multi-boot is gone. So you can try as a USB flash drive. USB sticks are not so capricious as SD card when you run the system from external media.
[hr]
I started from scratch did a factory reset then put files on SD card then removed aml_autoscript to prevent boot loop as instructed then tried both SD card and USB flash drive attached is the error message my device is T8 AML V3 S812 any ideas?What version of Android firmware 4.4 or 5.1 ?