Hello, I have Tronsmart S89 (S802H) box.
Which is the latest libreelec firmware for my box which fully works? (I would like to put it internally (not on SD))
Posts by dankec
-
-
Hello, I have Tronsmart S89 (S802H)
Which is the latest libreelec firmware for my box? (I would like to put it internally (not on SD))
Does "LibreELEC-MXIII_Plus.arm-9.0-devel-20190207022938-5e27f15.tar" work with that box?
Or "LibreELEC-S82.arm-9.0-devel-20190206212910-5e27f15"?
Thanks in advance!
-
Start LE, enable SSH in the settings to connect via SSH, execute the command "fw_printenv".
Ok, here's the result:
LibreELEC (community) Version: 7.0.2.001
LibreELEC:~ # fw_printenv
Cannot access MTD device /dev/mtd1: No such file or directory
LibreELEC:~ # -
[hr]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.
Does it means: One image to rule them all?
-
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.How can I do this?
-
Demetris, I have M8S PLUS box with Ap6330 bt/wifi chip.
When I tried to upgrade to Libreelec 8.0.1 with your 8.0.1 m8s plus image with .tar (from Libreelec 7.0.2) I ended this way:Do you have a clue what went wrong?
-
is there any way to produce LAN1000 image which could be booted as AlexELEC?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).
I simply cannot understand what you're trying to tell me or I cannot get multiboot mode with my M8S+
Here's my steps, could you trace what I'm doing wrong:
1. download LAN1000 image
2. burn image to SD card using Win32diskImager
3. Put SD card into box
4. Plug out box, press toothpick, plug in box
5. It finished with black screen in my case
6. plug out boxNow when I tried to boot with the same SD card it always ended with black screen and no loading at all (with or without toothpick)
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.
When I insert USB with the same image box just ignores it and boot image from RAM.
What am I doing wrong?
-
balbes150, 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. -
Alas, still no build working with the BCM4335.The older OpenElec build from Codesnake and Surovalex is actually the only one that worked.
MEGAWould it be possible to obtain the Wi-Fi drivers from that build?
I'm talking about the X8HP builds, which work perfectly well on my Minix X8-H Plus.Arcee, AlexELEC 2.2.2. here: Releases · AlexELEC/AlexELEC-AML · GitHub should work with BCM4335 (try with M8S+ version which is made for that chip).
Unfortunately, I have M8S+ with AP6330 and it won't work with any of the builds. Only full working version (with kodi 16.1) is Kerber's 7.0.2.001 from here: Index of /image/LE8
Version 8.0.1. from the same folder should work with BCM4335, you could try it.
-
Yes the 7.0.2.001 version was also working fine.
New version 8.0.1 is perfect no issues at all checked wifi, bluetooth, 1080P, remote control etc. Everything is spot on.
I think you have Alexelec version kodi 17.1 working so you should be good.
No good. AlexELEC is working except Wifi and bluetooth.
But I still don't understand how 7.0.2.001 could work fine with both BCM4335 & AP6330 chip?
Couldn't it be the same with 8.0.1? -
I have tried it and all working fine with BCM 4335 not sure about AP6330
It is strange that previous Kerber's version (7.0.2.001) works perfect with my M8S+ (including wifi), but 8.0.1 nada (same symptoms as pepperami).
So if I have AP6330 how it's possible that 7.0.2.001 works great which is working great with BCM4335 also?
-
Anyone tried new Kerber's version (8.0.1) for M8S+?
-
Hi mate
I can send you the Libreelec 7.0.2.001 updated file. let me know if you would like that.
I have tried ALEXELEC version 2.1.8 and have been advised that the device tree is not for ACEMAX m8S+
there is a new version out just today version 2.2.0 which i have yet to be tried but i was told that it probably should work ok on ACemax M8s+ so i can let you know how i go when i test it in a day or 2
AlexELEC 2.2.0 should work with BCM4335 now.
I'll check in my M8S+ if it's still working with AP6330 and what's with bluetooth...Here's what's new in 2.2.0:
kodi: up to 17.1-rc2-9637da6
vdr-plugin-vnsiserver-615a077
S812: add support BCM4335B0 wifi & other firmware
S812: fix rtl8723bs_bt firmware
S812: add device MXIII_G -
the remote or power on/off. I will post my remotHave you been trying to restore settings from kodi 16.1? Is it working when importing it to Kodi 17?
-
HI mate
Can you please advise which firmware works best for acemax M8s+ (i ahve tried 2 links and the remote control does not work)
If you could share a working link that would be great
Thanks
This one: Releases · AlexELEC/AlexELEC-AML · GitHub (kodi 17) and
This one: MEGA (kodi 16.1) -
petgil: Is it working with balbes150's remote.conf?
-
bnj86, My original RC does not work with that version but now I plugged in a wireless USB mouse/keyboard and this works fine.
Still I want my original RC to work again.AlexELEC available here: Releases · AlexELEC/AlexELEC-AML · GitHub should work great with M8S+, but I think there's KODI 18 rc (not the final one).
-
Hi everybody,
I upgraded my M8S+ box: Yandex.Disk
All works fine except the RC.
What do I have to do to get my RC working again?
Thanks in advance for your helpWhich version exactly did you put on M8S+?
Is it possible to import KODI 16.1 settings into 17?