[S812] MIII Plus 2Gb\16Gb eMMC

  • I was already to sleep yesterday, so I didn't see your post. You have to put them all on the root of the sd-card and then do the toothpick method. If everything is alright you should see the picture of the droid with a spinning wheel in his body. If you are still on TWRP it will not work. Then you have to install the recovery.img first from TWRP (if I remember correctly) and then do the toothpick method again.

    If you are not sure you can do following command in a linux terminal: cat factory_update_param.aml

    It will show you the text inside of the file. With a little imagination, you can read what files the update needs and what it will do.

    You can do the same for the aml_autscript: cat aml_autoscript (make sure you cd to the folder where the files are located).

    I did figure this out by looking way back on some Freaktab posts. However, the Tronsmart rom failed via the SD card method. Luckily the box still booted into recovery, as the Beelink firmware was damaged/cleared when trying to boot the Tronsmart ROM. I'm a bit worried to try the USB Burning Tool method, as I am not sure if I will brick or not. I installed an old ROM, 115K4 which was what I was using. Tried an LE 7 rom which would not boot. So a long day spent getting nowhere. Its raining today so perfect day to try again.

    Thanks roel.

    Edited once, last by doggyofone: Spent a few hours yesterday at this. Reinstalled the Beelink firmware so that I could get an original recovery installed, versus running it of an SD card. Once I did that I booted up Demetris's 8.2.3 successfully. I could not find a way to boot up a balbes150 build. I had trouble using USB Burning Tool until I used the attached method (June 14, 2018 at 4:29 PM).

  • I did figure this out by looking way back on some Freaktab posts. However, the Tronsmart rom failed via the SD card method. Luckily the box still booted into recovery, as the Beelink firmware was damaged/cleared when trying to boot the Tronsmart ROM. I'm a bit worried to try the USB Burning Tool method, as I am not sure if I will brick or not. I installed an old ROM, 115K4 which was what I was using. Tried an LE 7 rom which would not boot. So a long day spent getting nowhere. Its raining today so perfect day to try again.

    Thanks roel.

    I finally got USB Burning Tool to work and reloaded the Beelink firmware followed by Demitris's 8.2.3 build. I could not get a balbes150 build to load no matter how old a version I used. I found a tutorial that worked for me to get USB burning Tool to work and expanded on it. Several others did not work.How to USE USB Burning Tool to Burn Images to Android Boxes.txt

  • Hi,balbes150,

    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.

    Could you it possible to compile a ROM if I provide the dtb file?

    Or I have to build it by myself according to your source code. thanks!

    the dtb file link:

    https://drive.google.com/drive/folders/1yh31djzzzsxvmxtk4efihs2jixvkfbtq?usp=sharing

  • balbes150

    I got your Leia build working on an Orbsmart S82. It works like a charm, even Netflix and Amazon Prime work with 720p!

    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. To install it I installed Demetris Build first and then updated with the 100M tar file.

    It's now installed on my internal storage. I'm just worried about updates, hopefully this won't crash the whole system.

  • balbes150

    I got your Leia build working on an Orbsmart S82. It works like a charm, even Netflix and Amazon Prime work with 720p!

    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. To install it I installed Demetris Build first and then updated with the 100M tar file.

    It's now installed on my internal storage. I'm just worried about updates, hopefully this won't crash the whole system.

    So just to confirm, how did you get this build installed on internal storage, step by step? Which Demetris build?

    I mostly gave up on the build, as the reboot issue with the SD card didn't seem to have a solution.

    Thanks

  • Here are the steps:

    1. Download drieschels build libreelec-s802.s82.arm-8.0.0-2-alpha-devel.zip

    2. Unpack the files and put them in the root directory of your SD card / USB drive (don't burn them with an image tool !!!!)

    3. Start the box in recovery mode (toothpick) with the inserted SD card / USB drive

    4. Choose Wipe/factory reset, and then Update from EXT. Choose your SD card / USB drive and the zip file which is on it

    5. LibreElec should be installed on your device now

    6. Start the SAMBA service and put this build in the update folder (\\libreelec\update) and reboot Loading site please wait... (dont know if it is necessary to perform this update but I did so)

    7. Now you're on LibreElec 8.2.3

    8. Download the "LibreElec-S812.arm-18.0_20180601-LAN_100.tar" file and put it into your update folder and reboot Nothing found — Yandex.Disk

    9. Now youre on LibreElec 9.0

    10. Be happy

  • Thanks for the nice step by step guide. I did this a little differently. I'm running off an SD card and worked the update that way. As I was already on demetris's 8.2.3 build for the MXIII Plus I copied the balbes150 update 0601 for the MXIII Plus into the update folder and rebooted.

    Some time ago Ii tried to update an older demetris build with an older balbes150 build and I got an error. I don't remember the error then, but I had to rebuild everything over again. I also got an error when I tried to update demetris 8.2.3 with Leia 18.0. I attached a picture showing the error.

    Luckily the box booted back to 8.2.3.

    I'm not sure why the error occurred, as the MXIII Plus is what I have and both the demetris and balbes150 MXIII plus builds are what I am working with. I originally thought it was something different about the builds, but since you updated demetris 8.2.3 with balbes150's Leia build I'm not so sure that is the problem. The Beelink MXIII Plus specs - 2g/8g, gigabyte LAN

    Beelink MXIII Plus components-1.txt


    I'm looking for some help with this problem and appreciate any comments/corrective actions. Thanks


    Edited 2 times, last by doggyofone: I had tried this before with a demetris build running on the SD and then updating with a balbes150 image. It failed then and again with this Leia build. (June 18, 2018 at 4:23 PM).

  • doggyofone

    I'm sorry to hear that. Did you try to to create the file and disable the compatibility check? This message didn't appear during my upgrade process. But the S802 and the S812 are very similar so you could give this a try. Did you install the 8.2.3 from my link? There is a build for the MXIII Plus from Demetris. Maybe this could solve your problem.

  • doggyofone

    I'm sorry to hear that. Did you try to to create the file and disable the compatibility check? This message didn't appear during my upgrade process. But the S802 and the S812 are very similar so you could give this a try. Did you install the 8.2.3 from my link? There is a build for the MXIII Plus from Demetris. Maybe this could solve your problem.

    I already had Demitris's 8.2.3 on the SD card and that is what I tried to boot with. This time I will add the .nocompat.zip that we normally need to boot a demetris build.

    Thanks guys for your help.

    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?

    Edited 2 times, last by doggyofone: Update (June 18, 2018 at 11:14 PM).

  • 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.

  • I have followed your instructions per post 771 and post #766 and reinstalled the stock firmware. I tried booting from your builds from the stock firmware with no success, April 2017, June 2017 and your 8.2.3 build. If one worked I was hoping to update to Leia. None would boot.

    As a last resort I tried following An's instructions, but the step 6 image link is for a demetris build. I tried anyways with demetris's 8.2.2 build but had little success. Then I tried with a nocompat.zip extracted to the sd card with your Leia 6/1/2018 build. I toothpick booted the image and it installed but got stuck on the Libreelec screen. This is the closest I have been to installing your build.

    I have tried again with your 6/1/2018 build on a fresh install of the original firmware to toothpick boot the image and nothing happened. I formatted the card and booted demetris's 8.2.2 build and it loaded successfully first try.

    So my question is, how do I boot your Leia build? Which steps "Note that those users who exactly perform the steps"?

  • 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.

    I tried your new release "LibreELEC-S812.arm-9.0-devel-20180622135859-5287365-LAN_100" after setup muti-boot(due to the box don't have reset button, so I input "reboot update" in adb connection, then the system reboot and go to boot logo. ) and a new dtb.img, I removed aml_autoscript and aml_autoscript.zip one by one, but the system still reboot again and again, if you need UART log, I'll paste it later.

    • Official Post

    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 ?

  • The @AN instruction is intended ONLY for starting the system from the eMMC (all steps must be performed accurately).

    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).

    OK, thanks. I will give this a try. One question, is it possible to update from Krypton to Leia on your build by .tar update? I have several M8S LAN 100 devices to update.

    Edited once, last by doggyofone (June 26, 2018 at 4:07 PM).

  • Can someone help me.

    I have the Akaso M8S.

    I have the version LibreELEC-S812.LAN1000.arm-

    I want Kodi 18 but in all versions there is no wifi.

    Can someone help me copy wifi into the new version

  • Can someone help me.

    I have the Akaso M8S.

    I have the version LibreELEC-S812.LAN1000.arm-

    I want Kodi 18 but in all versions there is no wifi.

    Can someone help me copy wifi into the new version

    This doesn't look like a balbes150 image. Not sure where you got it. Can't say for sure, but I believe your box is only LAN100. So in summary, I don't think you have the right image for that box. Go back to page one of this forum and open the link to balbes150's images. Pick the right one for your box and then install it. balbes150 gives some instructions in post 790.