Posts by doggyofone

    I am having a tough time trying to find the original recovery image for my MXIII Plus. If anyone has this and can share it I would appreciate the help.

    I'm trying to use USB Burning tool to put the original firmware back on the box to clean up the U-boot (per balbes150's advice post #739). I have TWRP (which replaced the original recovery) on the MXIII, which seems to prevent me putting the MXIII into recovery mode so that I can use USB Burning Tool. USB Burning Tool does not find the MXIII. I have uninstalled and reinstalled USB Burning Tool and the drivers.

    I'm not sure if there is a different way to get USB Burning Tool to recognize the MXIII, but if someone knows of one please let me know how.

    Thanks for any advice and help.

    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.

    balbes150, is the "please_resize_me file" problem resolved? I don't have a Linux machine to resolve this problem.

    Thanks roel. Not sure where I missed that post. You can use Ext2Fsd in Windows to edit Linux.

    balbes150, is there something I've missed here with regards to installation? I cannot get your Leia to boot.

    Balbes150, I downloaded this file Libreelec-S812.arm_18.0_20180522-MXIII_Plus.img.gz. and flashed it to a formatted MicroSD card using win32diskimager. This was a fresh flash, not a .tar update.


    1- I attempted a toothpick boot into LE. The first attempt the Android splash started then the screen went blank and the LE splash came up on screen. There was no progress from this point, just an error at the top left:

    Nothing progressed from the # shown on the last line.


    forum.libreelec.tv/core/attachment/3747/


    2- I pulled the plug and did another toothpick reboot and the Android splash came up, flashed off then flashed on and this repeated until I pulled the power plug. No progress towards the LE splash screen was made.


    3- I gave up and restarted the box without toothpick. The Android splash came up, then the Libreelec splash opened and a full page of data flashed quickly on screen (too quickly to record), then the boot dialogue started on the left top of the page, it counts down 3 seconds and then reboots and restarts the whole process again, over and over. LE never completes the loading and opening Leia.

    forum.libreelec.tv/core/attachment/3749/


    4- I reflashed the card and tried another toothpick boot. This time the box went right to step 3 and continued rebooting.

    I'm not sure what is wrong and could use some help. I have a Beelink MXIII Plus with 2g 16g

    I'm not sure if I was to activate multiboot in a different way -

    "To start the system from external media, you must use a universal multi-boot. This variant of multi-loading system is fully compatible with Armbian etc systems for TV boxes. If it is already activated with the previous images, you do not need to repeat the activation".


    Would be helpful if you could start another thread for Leia S802/S812.

    I have two older boxes, a Beelink MXIII Plus (S812, 2g/8g) and a generic MXIII G. I have been able to update via tar on the MXIII G

    through all 8.0 versions up to and including 8.2.3. The box boots with the LE logo in the upper left corner and seems to run well. This is with the 8.2.3 MXIII Plus tar zip.

    I just got the MXIII Plus back off loan and started the update process. I tried multiple ways to boot to the 8.2.3 MXIII Plus zip, including with the img.gz and updating progressively from 8.0 versions up to the 8.2.3 tar. Either way, 8.2.3 would not boot past the LE screen in the upper left corner. The logo appeared and after a few seconds the screen went blank. I went back to my basics on this process and 8.2.3 still doesn't boot:

    S802/S812-My Instruction Post

    So currently on the MXIII Plus I am running 8.2.2 and I notice some audio/video stuttering on that version. I'm just wondering if there is a different version I should use.
    Has anyone been successful with a different zip?

    Checked the MXIII-G this am and noticed that it is on 8.0.2b, not 8.2.3. I cannot boot it up with the 8.2.3 tar file. Sticks at the upper right corner LE and then goes blank. I was able to install 8.2.2 and it works well.

    Any chance to get Kodi 18 on s802 (MXIII-1G) ?

    Its my understanding from posts on the kszaq and CE sites that LEIA will not support the older 8## series boxes. Will future LibreELEC for Kodi 18 Leia work with S812 processor?


    So 17.6 will probably be it. wrxtasy is supporting 8.2 and has released 8.2.4.1 for S912 and has suggested that he will provide an S905 version. We will have to wait for those updates.

    I have two older boxes, a Beelink MXIII Plus (S812, 2g/8g) and a generic MXIII G. I have been able to update via tar on the MXIII G

    through all 8.0 versions up to and including 8.2.3. The box boots with the LE logo in the upper left corner and seems to run well. This is with the 8.2.3 MXIII Plus tar zip.

    I just got the MXIII Plus back off loan and started the update process. I tried multiple ways to boot to the 8.2.3 MXIII Plus zip, including with the img.gz and updating progressively from 8.0 versions up to the 8.2.3 tar. Either way, 8.2.3 would not boot past the LE screen in the upper left corner. The logo appeared and after a few seconds the screen went blank. I went back to my basics on this process and 8.2.3 still doesn't boot:

    S802/S812-My Instruction Post

    So currently on the MXIII Plus I am running 8.2.2 and I notice some audio/video stuttering on that version. I'm just wondering if there is a different version I should use.
    Has anyone been successful with a different zip?

    I'm trying to revive an older Beelink M18, which has the S905 processor, gigabyte lan and 2g/16g memory. I'm pretty sure the correct DTB is gxbb_p200_2G_1Gbit.dtb, but I can't get the box to boot into Corelec.

    Can this box run Coreelec and have I chosen the right dtb?

    Set up of my new Sony XBR75x85e was kinda strange. Its a UHD set, 3840 x 2160. Everything runs through my Denon AVR and then HDMI out to the TV. I hooked up a couple Abox A1Max boxes loaded with Coreelec to the AVR and then checked resolution. One defaulted to 1280 x 720 and the other to 1920 x 1080P. neither would change to 3840 x 2160 and I tried several times with and without reboots. Finally tried 4096 x 2160 @60hz and the boxes accepted it. I then tried to change them to 3840 x 2160 and they accepted that. Not sure why, but everything seems OK for now.

    That looks right.


    Shoog

    Thanks again for your help Shoog.

    I didn't see a way to save/exit, so I searched it out and did the following:

    1- In putty enter the following:

    nano /storage/.config/.autostart.sh

    2- then entered the following via copy/paste:

    reboot)

    # ir-keytable -D 600 -P 200

    ;;

    3. Then press CTRL+x, then press "y", then press 'enter'

    Hopefully all is good.


    A question, if I want to add a second command would I add it on the next line below the first command - IE:

    reboot)

    # ir-keytable -D 600 -P 200

    # next command

    ;;

    Thanks again for your help.

    Not at all familiar with autostart.sh, but looked at the libreelec page and an openelec page and tried entering in the putty window:

    Sorry I need to correct myself, the line (ir-keytable -D 600 -P 200) needs to be added to the /storage/.config/autostart.sh file to stick between boots, sorry for the omission.


    Shoog

    nano /storage/.config/.autostart.sh


    then entered the following:

    reboot)

    # ir-keytable -D 600 -P 200

    ;;

    I'm guessing I'm way off with this and can't google a way to check. Is this the command set that is required?

    Thanks again.

    Thanks for the help. It worked for me. Something I can tweak a bit as well.

    Shoog, is this a general command for any remote, or specific to yours. I have the same issues with the OK button and the arrow keys on my Mecool Pro+ and Abox Max. Hit the arrow key quickly several times quickly and the remote will overshoot a lot. These remotes worked really well on 8.2.3.1.

    Thanks