Posts by doggyofone

  • [S812] MIII Plus 2Gb\16Gb eMMC

    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.

  • [S812] MIII Plus 2Gb\16Gb eMMC

    Quote from balbes150

    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.

  • [S812] MIII Plus 2Gb\16Gb eMMC

    Quote from roel

    doggyofone

    It's as I already told balbes in post 737: the .please_resize_me file could not be deleted. It's easy to fix if you have a linux pc. Just put the usb stick or sdcard in your linux pc. Go to the storage partition of your usb stick or sdcard and remove the file .please_resize_me as root (or with sudo in the terminal). After you done this, You can use gparted to expand the storage partition.

    I don't think it is possible on a windows pc as windows doesnt support the ext4 filesystem. But actualy, I don't know as I'm not a windows user.

    If you don't understand the above howto, wait for a next image of Balbes150 where he fixed the permissions of the storage partition.

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

  • [S812] MIII Plus 2Gb\16Gb eMMC

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

  • [S812] MIII Plus 2Gb\16Gb eMMC

    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.

  • S802/S812-Libreelec images for 7/8/9

    Quote from doggyofone

    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.

    Quote from deesnow

    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.

  • S802/S812-Libreelec images for 7/8/9

    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?

  • LE9.0 remote configs ir-keytable Amlogic devices

    Quote from Shoog

    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.

  • LE9.0 remote configs ir-keytable Amlogic devices

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

    Quote from Shoog

    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.

  • LE9.0 remote configs ir-keytable Amlogic devices

    Quote from Shoog

    This is specific to my VIM2 remote, but you can try it on any box.

    The first number is the most critical for me since its the delay before it starts looking for a repeat. The second is the repeat interval.

    Simply go into you box via SSH and issue the command. The settings will take effect immediately without the need for a reboot and they will stick between reboots. Mess with the two numbers (in approximately the same ratio as mine) until you get the response you want, do this going from your PC SSH terminal and your box testing the effects of issuing the command each time.

    The reason that it all worked in 8.2.3.1 is because that build used the AMlogic based system that the box came with so if you had the original box config file for the remote it would work as it did in Android (mostly). In this build it is using the Linux kernel based system which is universal to all Linux based systems and so needs fine tuning to your specific remote.

    Shoog

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

  • LE9.0 remote configs ir-keytable Amlogic devices

    Quote from Shoog

    Found I needed to run this before I got stable operation on my VIM2 VTV remote:

    ir-keytable -D 600 -P 200

    Before this the OK button was very unreliable and most operations resulted in double presses or overshoots on navigation.

    Shoog

    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

  • S802/S812-Libreelec images for 7/8/9

    Quote from gizmomelb



    so this is on a known working SD card that I can boot to libreELEC on my s905 media box.

    more reading.

    EDIT: I cannot format my SD card now so probably bad - I don't have another one to test. Will have ot buy on on Thursday (payday).

    I've used lots of different cards and never had problems with any. Right now I'm using Lexar 633X and 300X no problem. Also Sandisk cards. I look on Amazon for the faster speeds which you can compare here - Fastest MicroSD Card Speed Tests | Updated March 2018

    I think your box has an SD slot, so Samsung, Lexar and Sandisk are good choices and pretty good prices.

  • S802/S812-Libreelec images for 7/8/9

    Quote from gizmomelb

    hi all, I'm hoping someone can please help me - I have an old Beelink M8 box - one of the first round black and red coloured media players and I've tried the following images on SD card, but nothing boots.. I just have the grey boot screen (which flickers a few seconds after initial boot.. then nothing).

    LibreELEC-S8X2.arm-8.2.3-M8.img

    LibreELEC-S8X2.arm-8.2.3-M8S-PLUS.img

    LibreELEC-S8X2.arm-8.2.3-S82.img

    You likely haven't read enough of the forum posts. There is a ton of good information available in the posts.

    You can try this from post 1048 - this allows the box to boot from the SD card slot. Once done that try installing one of the M8 roms.

    1- Download "Enable SD card dual boot" zip file, copy file to sdcard/thumb drive (I used sdcard) - OpenELEC-MX3G.arm-DualBootSD.zip

    2. "Toothpick" boot your device into (original) recovery mode (took~30 seconds), select install ZIP from EXT & select "OpenELEC-MX3G.arm-DualBootSD.zip" Note that there was an error on the bottom line of the zip screen - E:/misc - I didn't write it down. It had no effect on the process.

    After the zip ran I formatted the sdcard with SDformatter v 5.0. Then burned the ROM image to the sdcard and toothpick booted into LE.

    5 seconds often isn't enough to get LE started, might take 30 or more seconds.

    If the newer roms don't work try reading through the full 1048 post and the posts from #1 up to that point..