[ROM] Unofficial OpenELEC for MXIII-G & Tronsmart MXIII+

[MinixCrazy]

Wilro,

Just tring the new test beta 6.95.1, did a toothpick install from a fresh KitKat wipe and I'm getting similar CPU issues from some of your earlier builds, CPU2 & CPU3 are frozen not cycling like normal. They worked fine on the 7.0 test build...

Edit I was wrong, its on the OE 7.0 as well... I'm stepping back to 6.0.3b (Its working fine)

[MinixCrazy]

Hi MinixCrazy ,

This is rather unfortunate, as the original MX3-G (which I have) came with Kitkat. Another way to prove if the box is a genuine MX3-G, is to try loading the Tronsmart L106 firmware on it, as this is the rom that I derived most of the MX3G port of OE from, & as such has the greatest chance of working 100% with my builds.

It looks like the sheer variety of "MX3-G" devices flooding the market at the moment are suffering the same identity crisis that the "All Black MXQ" are. My hats off to kszaq for being able to get so many varieties of it (mostly) working with his build - He's certainly been able to delve far deeper into it than I have to date (Happy owner of 4 x "All Black MXQ" that work almost faultlessly with his 5.0.8 build - Purchased for family so that they all have a common box for me to support

Wilro, tI tried the L106 Tronsmart and many others, nothing worked. The funny thing is the box would not toothpick boot to revovery without the sdcard, it was like they didn't want the box reprogramed? The performance was very sluggish. The hardware is not even close as you can see in the photos. I played with them for two nights straight and gave up. I'm steamed because I'm certain the seller is trying to pull a fast one on the public and just wondering how many people have these clone boxes that have experienced problems with your ROM.

Frank

[vn800art]

I love the 805 soc!

[wilro_6276]

I'm in the process of returning the fake MXIII-G's I purchased and I would like to warn everyone DO NOT BUY any KitKat versions of MXIII-G's that are now flooding the market. If you do you will be stuck in the land of KitKat as the box will not toothpick flash or enter recovery. I've tried... The attached photos show the differences...

Hi MinixCrazy ,

This is rather unfortunate, as the original MX3-G (which I have) came with Kitkat. Another way to prove if the box is a genuine MX3-G, is to try loading the Tronsmart L106 firmware on it, as this is the rom that I derived most of the MX3G port of OE from, & as such has the greatest chance of working 100% with my builds.

It looks like the sheer variety of "MX3-G" devices flooding the market at the moment are suffering the same identity crisis that the "All Black MXQ" are. My hats off to kszaq for being able to get so many varieties of it (mostly) working with his build - He's certainly been able to delve far deeper into it than I have to date (Happy owner of 4 x "All Black MXQ" that work almost faultlessly with his 5.0.8 build - Purchased for family so that they all have a common box for me to support

[wilro_6276]

This is what I did. I reset openelec to defaults, then I copied into the update folder and booted. the update worked fine. however, to me it seemed to run alot slower. i got alot of the "working" popup while loading addons and lists, and it took a long time for OE to update addons to current. installing addons took longer than usual (i'm hardwired to gigabit ethernet). Menu navigation was a bit slower too. I was also having trouble getting real debrid links to work (kept getting some extra character error). So I reset back to default and did the toothpick install of OE 6.0.3 and it's definitely faster.

that being said, the best way to update to this would likely be to flash to android, do a full reset in recovery, and then do the flash to OE.

I might try again with a full reset via android, or I might just wait for the final release of OE7.

Thanks for the feedback red-i - Have you tried my kszaq based build? As I'd like to determine if your problem is related to the new kernel or the new version of kodi in the beta1 build (both these builds use the same kernel + MX3G patches - I have only done very minimal testing of ethernet with these builds, so I'd hardly be surprised if something has regressed in this area.

My other thought is that the beta build may work better if you set it to use the "ondemand" scheduler via autostart.sh.

In my case, I've found the beta to run better overall than 6.0.3x - But then, I use no addons, & pull my library off a central nas box with a mysql database - While the database issue appear to be fixed in 16.1rc2, again, I wouldn't be surprised by any regressions related to the addons

[MinixCrazy]

I'm in the process of returning the fake MXIII-G's I purchased and I would like to warn everyone DO NOT BUY any KitKat versions of MXIII-G's that are now flooding the market. If you do you will be stuck in the land of KitKat as the box will not toothpick flash or enter recovery. I've tried... The attached photos show the differences...

[red-i]

so we may just drop the openelec 7 beta zip inside the .update folder and upgrade from 6 to 7 this way? You rock every day more and more :-)

This is what I did. I reset openelec to defaults, then I copied into the update folder and booted. the update worked fine. however, to me it seemed to run alot slower. i got alot of the "working" popup while loading addons and lists, and it took a long time for OE to update addons to current. installing addons took longer than usual (i'm hardwired to gigabit ethernet). Menu navigation was a bit slower too. I was also having trouble getting real debrid links to work (kept getting some extra character error). So I reset back to default and did the toothpick install of OE 6.0.3 and it's definitely faster.

that being said, the best way to update to this would likely be to flash to android, do a full reset in recovery, and then do the flash to OE.

I might try again with a full reset via android, or I might just wait for the final release of OE7.

[ilfrance]

Howdy All,

OpenELEC 7 beta1 (5.95.1) has been released (link on 1st post of this thread)

This build includes kodi 16.1rc2 - It was able to upgrade my old kodi 15.2 database without error/boot loops (yipee!) - There was a lot of last minute changes in this build, so make sure you backup before installing/upgrading!

Cheers!

so we may just drop the openelec 7 beta zip inside the .update folder and upgrade from 6 to 7 this way? You rock every day more and more :-)

[wilro_6276]

Howdy All,

OpenELEC 7 beta1 (5.95.1) has been released (link on 1st post of this thread)

This build includes kodi 16.1rc2 - It was able to upgrade my old kodi 15.2 database without error/boot loops (yipee!) - There was a lot of last minute changes in this build, so make sure you backup before installing/upgrading!

While the wifi drivers for the ap6330 work really well, others may require a few more tweaks for this build to support it. If your wifi isn't working, you will need to do the following to help me ID the chipset/revision that's in use:

1. Install the new version, from the command prompt, enter "dmesg > /storage/dmesg.log" after booting - What I need is something like the following from this file:

---snip---
[ 45.616260@0] DHD: dongle ram size is set to 294912(orig 294912) at 0x0
[ 45.616654@0] dhd_conf_set_chiprev: chip=0x4330, chiprev=4
[ 45.616695@0] dhd_conf_set_conf_path_by_nv_path:config_path=/lib/firmware/brcm/config.txt
[ 45.617518@0] dhd_conf_read_nv_by_chip: nv_by_chip_count=4
---snip---

The info needed is on the 2nd line above (chip & chiprev) - I should then be able to incorporate support for your wifi chipset in my next build!

Cheers!

[vn800art]

Bigredfan post nr.2 in this thread!

[Bigredfan]

I have previously always installed directly to the box using the toothpick method and the usb drive

I just ordered a new Micro sd card so I can install and run openelec from the SD card as opposed to the internal memory

What steps do I need to do in order to boot from the sd card going forward

[vn800art]

Thanks for your interest!

Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

[wilro_6276]

awesome, thanks man question, for these zipped img files, can they only be installed to SD card? or can they be installed via toothpick method?

Hi red-i,

The .img files are purely for sdcard install (There is a tar & zip file in the same directory for upgrade/install to nand) - I'm just too lazy to post links for each one individually - And as these are very much test/beta builds, I recommend installing them clean.

When I try to load the zip I get signature errors, I have knockoff MXIII's Hardware doesn't even look the same... They are MXIII MBX not MXIII-G's...

That's unfortunate - You may have better luck trying one of the various MXIII builds...

How do you edit the SYSTEM file inside the update.tar file with windows 10? I want to add custom skin so it loads once the update is manually installed. I was using squashtools to edit the SYSTEM file and copy over the original SYSTEM file inside the tar file but it will not install. Thanks

Sorry hscotty55, I don't recommend this, as it is prone to rendering an unbootable device - There are however various posts that detail how to do this on various OE forums...

I will try these last Wilro's builds on the old MXIII Plus ( first months of 2015) with ap6335, not so quickly as I am actually in a busy moment! Thanks for your work..!

I doubt this build will help with wifi, as these new drivers change the way we ID the different wifi chips (running dmesg after install & grabbing what the driver identifies your wifi chip as will allow me to add support, however - I just don't have anything that runs the ap6335 chipset myself

[vn800art]

I will try these last Wilro's builds on the old MXIII Plus ( first months of 2015) with ap6335, not so quickly as I am actually in a busy moment! Thanks for your work..!

[hscotty55]

How do you edit the SYSTEM file inside the update.tar file with windows 10? I want to add custom skin so it loads once the update is manually installed. I was using squashtools to edit the SYSTEM file and copy over the original SYSTEM file inside the tar file but it will not install. Thanks