OpenELEC for s82, M8, MXIII, Tronsmart S89

[Dukman]

I have the MXIII with 1gb memory. I managed to install openelec 5.01 once, but after an unsuccesfull attempt to upgrade to 5.06 everything i tryed to get amlinux running again failed. I can install stan's amlinux, this install gives me no problems. I also can install any suitable android image, goes also without a hitch.

What i do, i place the OpenELEC-Amlogic.MX3.arm-5.0.6-update.zip file on a sdcard. Boot into recovery, select install from ext->sd card. Then it says:
-- Install /sdcard ...
Start copy /sdcard/OpenELEC-Amlogic.MX3.arm-5.06-update.zip to /tmp/sideload

and nothing happens.

I also tryed extracting the files from within the zip file to a scdard, boot into recovery. The android image appears and the device automatically starts updating. The progress bar then runs to about 80% and the whole thing stops.

Can anyone please help me fix this mess, cause it drives me crazy

The last method you used is correct. I have and MXIII 2/8 and I had the same problem. The update gets to around 80% and stops. This was discussed somewhere on this thread or another thread here. When it gets to 80% then stops...pull the plug and replug....it will then restart and start the update again. Keep doing this and eventually it will complete the update. Mine completed on the 5th restart. It's weird, I know.

[Dukman]

I just updated through a toothpick, but it would be nice to know how to update through tar, could you pls provide a
simple steps process. Has any one being able to power off/on there box with TV remote?

To update through .tar: Assumes that you have Openelec 5.0.x already installed. Don't do this from 4.9.x.

If you are on Windows 7 there are 2 ways.
1. Use WinSCP
Make sure you have SSH enabled in your Openelec box: It should be enabled by default.
Find your box's IP in System>System Info
In WinSCP create a new site:
File protocol: SFTP
Host Name: (box IP) 192.168.xxx.xxx
Username: root
P/W: (default) openelec
Port: (default) 22

Log in to your box.
In the right hand frame navigate to /storage/.update
In the left hand frame navigate to the folder where you stored your Openelec.tar file
Drag & drop the .tar file
Reboot the box.
After 20 secs the box will restart with the update installed.

2. Windows 7 network
In Windows 7 explorer address bar type in your box IP as "\\192.168.xxx.xxx
You should see the SMB share folders of your box. Open the "Update" folder and copy the Openelec.tar file to that folder.
Reboot your box. Done

[Ichijoe]

I have the MXIII with 1gb memory. I managed to install openelec 5.01 once, but after an unsuccesfull attempt to upgrade to 5.06 everything i tryed to get amlinux running again failed. I can install stan's amlinux, this install gives me no problems. I also can install any suitable android image, goes also without a hitch.

What i do, i place the OpenELEC-Amlogic.MX3.arm-5.0.6-update.zip file on a sdcard. Boot into recovery, select install from ext->sd card. Then it says:
-- Install /sdcard ...
Start copy /sdcard/OpenELEC-Amlogic.MX3.arm-5.06-update.zip to /tmp/sideload

and nothing happens.

I also tryed extracting the files from within the zip file to a scdard, boot into recovery. The android image appears and the device automatically starts updating. The progress bar then runs to about 80% and the whole thing stops.

Can anyone please help me fix this mess, cause it drives me crazy

First off before jumping the Ship / Shark... I'd recommend to anyone who wants to start...
What I'd term as "ROM hopping", to go and, get themselves a better Recovery. Sadly this wasn't a real possibility till now. Thankfully another User on this Site Abdul_pt has managed to give us poor K200 (M82 1G/8G), users a working TWRP: See HERE: http://www.freaktab.com/showthread.p...ery-06-03-2015

Same idea holds you need to rename the k200.img File to read as recovery.img, and then place that File (for the beginning...), on a large enough MicroSD Card 2GB+ to ensure you have enough to make a test Backup. If you find that it works... (AND IT SHOULD!), you can permanently flash that recovery though the 3e Recovery, and start using TWRP instead.*

Now that said there appears to be three sets of Files listed on the http://amlinux.ru/image Site:

A *.tar (Thanks Dukman for explaining what that was good for, as I just assumed it was likely just Source Files..)

A *.zip File (The Three File MicroSD Version: factory_update_param.aml, <UPDATE>.zip & the 3e recovery.img)

And the update.zip that's just the same File as above, but without the factory_update_param.aml, and the recovery.img Files

For most cases you could just use the *-update.zip, and just point to that from with-in 3e or TWRP, and update from there.

Again you update the MXIII (or other such Boxes?), by sticking in an old disused Q-Tip with the Cotton ends striped off, pressing deeply into the AV Port behind the Device till you can fell the Reset Switch being depressed. You either need to hold this till you get into the Recovery mode, or you can just release it after the Google TV / Tronsmart Screen, YMMV. (Sadly I've only seen the Two MXIII my old Mans, and my own, and the both have oddly different ways to get into the Recovery).

Once there point the update towards the MicroSD and, run the update. TWRP will ask you afterwards if you want to install SuperSU. I choose yes. At which point the Box just restarts into OpenELEC.


*HIGHLY RECOMMENDED if your a Google Music User! Since "ROM hopping" can quickly burn up your 10 allotted Devices, very quickly if your not paying attention. I know that 'cause its already happened to me...

[And1337]

Hi,

i downloaded OpenELEC-Amlogic.M8.arm-5.0.3 and was able to install this to my box.

I cant get wifi to work.

Is there someone who had the same problem?

[Ichijoe]

Hi,

i downloaded OpenELEC-Amlogic.M8.arm-5.0.3 and was able to install this to my box.

I cant get wifi to work.

Is there someone who had the same problem?

What kinda Box are you trying to use? A MXIII 1G or, 2G or some other kind?

As a bit of general advice... (Since I had it connected anyway. No thanks to TWRP), would be to use a Mouse instead of the stock remote to input your Wi-Fi Key... Which also seems to fail me. That or try taking your time inputting your Key so that you do not have to use the Backspace / Delete / Back Button. Which I suspect the problem here is.

*System M82 MBX MXIII (1G/8G - AP-6181 b/g/n @ 2.4Ghz, with 20Mhz Channels (Single Channel ONLY), currently on OpenELEC 5.0.6

P.s. Does anyone know if its possible to add a remote.conf & rc_keymap File(s) from a different Linux System an HTPC running VDR, and use this from with-in OpenELEC. IIRC it was a Imon MCE. About the only thing I miss about it was the ability to input Text via a T9 method.

[dipswitch]

MXIII 1gb working again (finally)

I finally got the mxiii working again, and i only was able to do this with the help from the posts earlier. Thank guys!! I was only moments away from throwing the d*mn thing trough the window .

What i did: first tryed repeatedly flashing from recovery, after about 20 times i gave that strategy up. Whilst trying this method, the device once rebooted on it's own, only to start flashing again.

In my second attempt of getting the mxiii to work again, i installed the alternative recovery as suggested. And it worked! Not with the remote, i had to connect a usb mouse to the mxii to be able to press the buttons in the recovery. First i permamently installed the alternative recovery, after that, from the new recovery, i installed the openelec update zipfile (the zip from within the zip...). This all went very smootly. Just one reboot and the device booted up openelec/amlinux like never before.

This again shows the importance of forumes (and their members) like these. So again, thanks!!

[And1337]

What kinda Box are you trying to use? A MXIII 1G or, 2G or some other kind?

As a bit of general advice... (Since I had it connected anyway. No thanks to TWRP), would be to use a Mouse instead of the stock remote to input your Wi-Fi Key... Which also seems to fail me. That or try taking your time inputting your Key so that you do not have to use the Backspace / Delete / Back Button. Which I suspect the problem here is.

Thx for reply =)

The problem is, i cant even use wifi. I guess the system cant find the wifi module (?)

I bought this system: "
Descriptions:
Amlogic S802 AML8726-M8 Quad Core Smart TV Box Android 4.4 Kitkat
DDR3 2G 8G Rom 4K*2K HDMI Output XBMC Media Player

"
I guess i have a amlogic M8? The System tells my i have a Meson8 (i think m8 is just the short form of this?

I tried three different openelec roms, all with some problems.

The first, like i already said in my post before. OpenELEC-Amlogic.M8.arm-5.0.3.zip
Problem: I cant use my remote and cant use the wifi (i even cant activate wifi in the system settings) and every ~2-3 min my kodi restarts.

The Second: OpenELEC-Amlogic.MX3.arm-5.0.6.zip
I can use my remote and wifi. But i can´t use my 2gb of ram, only 1 :/. Thats the ony "problem"

The third: OpenELEC-Amlogic.S82.arm-5.0.6.zip
It freezes at the boot sequenz and only shows me Transmart or something. Thats it.



For now i installed the mx3 zip. But i still dont know if theres a rom witch supports my 2gb of ram.

[Ichijoe]

Thx for reply =)

The problem is, i cant even use wifi. I guess the system cant find the wifi module (?)

I bought this system: "
Descriptions:
Amlogic S802 AML8726-M8 Quad Core Smart TV Box Android 4.4 Kitkat
DDR3 2G 8G Rom 4K*2K HDMI Output XBMC Media Player

"
I guess i have a amlogic M8? The System tells my i have a Meson8 (i think m8 is just the short form of this?

I tried three different openelec roms, all with some problems.

The first, like i already said in my post before. OpenELEC-Amlogic.M8.arm-5.0.3.zip
Problem: I cant use my remote and cant use the wifi (i even cant activate wifi in the system settings) and every ~2-3 min my kodi restarts.

The Second: OpenELEC-Amlogic.MX3.arm-5.0.6.zip
I can use my remote and wifi. But i can´t use my 2gb of ram, only 1 :/. Thats the ony "problem"

The third: OpenELEC-Amlogic.S82.arm-5.0.6.zip
It freezes at the boot sequenz and only shows me Transmart or something. Thats it.



For now i installed the mx3 zip. But i still dont know if theres a rom witch supports my 2gb of ram.

I could be wrong here... But isn't the AML8726 the Dual Core Chip that's inside the MX2?
I'd advise caution till you have that worked out, if I was you. 'Cause I'm sure that the S802 is to my knowledge at least refered to as such. Though it seems to that it really is a S802, Quad Core given the other descriptions.

BTW: If You look at http://amlinux.ru/images the first thing you'll notice is the amount of ROMs they have. Its kinda up to you to figure out which version you might need. It may also help if you posted a Pic of what it looked like as well. For example is the Device square, or round?

If you really think you have an M8... Then you'll need to use the ENY version of OpenELEC. As the MXIII has somewhat different Hardware in it, and so can NOT work, I'd dare say that you've been lucky so far that you haven't bricked it yet.

[annguyen4]

Unable to install OpenElec on my MXIII

Hello Everyone, I've downloaded file OpenELEC-Amlogic.MX3.arm then unzip and copied them on sd-card and USB drive (tried on both) but my box gave me error "After I boot the MXIII box in recovery mode and choose sdcard but I've got error: "E: read-only mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory) please help. Please help

[annguyen4]

Unable to install Flash file. Please help

Post one Updated with auto script flash add the 2 files to the root directory of sd + the zip from zip

After I boot the MXIII box in recovery mode and choose sdcard but I've got error: "E: read-only mount /dev/block/mmcblk0p1 on /sdcard failed (no such file or directory) please help

[And1337]

I could be wrong here... But isn't the AML8726 the Dual Core Chip that's inside the MX2?
I'd advise caution till you have that worked out, if I was you. 'Cause I'm sure that the S802 is to my knowledge at least refered to as such. Though it seems to that it really is a S802, Quad Core given the other descriptions.

BTW: If You look at http://amlinux.ru/images the first thing you'll notice is the amount of ROMs they have. Its kinda up to you to figure out which version you might need. It may also help if you posted a Pic of what it looked like as well. For example is the Device square, or round?

If you really think you have an M8... Then you'll need to use the ENY version of OpenELEC. As the MXIII has somewhat different Hardware in it, and so can NOT work, I'd dare say that you've been lucky so far that you haven't bricked it yet.

Yes, i guess im very lucky so far^^

I bought the box from ****, here is the link http://www.****.de/itm/281617012245

I hope this helps to figure out witch rom i realy need :/.


thx 4 help =)

[MikeD]

If you have 2GB RAM you have to use S82 version. This must be same hardware. Just try to install again (maybe older releases) and make factory reset after flashing rom.

[Ichijoe]

Yes, i guess im very lucky so far^^

I bought the box from ****, here is the link http://www.****.de/itm/281617012245

I hope this helps to figure out witch rom i realy need :/.


thx 4 help =)

Ok so its the round 2G version then... (i.e. its a S82.. Or at least an S82 Clone...)
I'd really like to know where you got the AML8726 from, as its a totaly different SoC (System on Chip), to say the S802. The basic idea I'm trying to push here is that One of these Chips is like the old Galxay S, and what you have at the moment would be more like the Galaxy S5. They may be both Galaxy Phones. But you couldn't use either of their Firmwares on them without risking permanent damage (i.e. bricking), said Device.

/pontification

Knowing that you have the 2G/8G styled "Puck"... The most likely version of OpenELEC to install would be the S82 Version. In fact unlike me your actually kinda lucky to have that version, as you have way more Custom ROMs that you could also try out. Namely this Finless ROM that I've been reading so much about on this Site. It was basically made for those 2G/8G units. Having only the 1G/8G version sadly I'm not able to really run those kinds of ROMs.

P.s. Having read the Sellers "Ad" I know where your confusion sprang up from.. It seems to me that, this may well either be a "Clone" or, that the Seller just doesn't know Jack!

For Ex: "Please note it''s amlogic S802,only support Dolby and DTS software decode, Customer need use XBMC to play Dolby and DTS, For 4K video with DTS and Dolby, this tv box can''t support."

Is clearly full of sh--! Now I wouldn't care to take a guess at Software Decoding, as I use a very capable.... If also very old (+10 Years now!), D-PL / DD-5.1 / DD-5.1EX / DTS Decoder though my 7.1 Speaker System, and I can tell you that when my MXIII (S802), is setup to use the SPDIF-Out I can use such Formats where they exist, with NO PROBLEMS WHATS SO EVER!

As to Software Decode? I for one fail to understand it, as there is NO direct way to patch up a 7.1 Speaker System to these Boxes that I'm aware of to even allow Software Decode. I think what he probably meant was "Stereo Upmixing" whereby DD-5.1 or DTS... Muchless TrueHD or DTS-HD-MA get downgraded to "Stereo". (See MX Player on Android!). But for the "SD Formats" of Pro Logic, DD5.1 (EX) & DTS The Box can pass such streams on to the External Decoder just fine! But, please buy or more expensive MINIX Neo x8-h Plus anyway...*

*Not that I'm raging on the x8-h Plus... It'll more then likely be my next upgrade away soon enough. With its 802.11ac, and Hardware decoding of h.265 >720p. The MXIII's S802 can only do Software decode on h.265 (Not sure about the "B" & "H" Versions) up to 720p. On Paper, and less so in reality.

[vermillion]

Yes, i guess im very lucky so far^^

I bought the box from ****, here is the link http://www.****.de/itm/281617012245

I hope this helps to figure out witch rom i realy need :/.


thx 4 help =)

As MikeD said i would try the s82 version again, if you had success with the MXIII version i would use the recovery from that build on the s82 version, this has worked for me in the past.

[Ichijoe]

just outta interest.. I mean I can't be the person in the Room with a Bluetooth Headset...
Does OpenELEC's version of BlueZ support the AD2P Protocol? 'Cause I'm getting the feeling that it doesn't