[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[pigbait]

I put the 6.0.0.1 openelec on my mxq using HD18Q and it is red LED bricked now. I have used it a handful of times for my friends and myself with no issues but the new box my friend brought me is an OTT box MXQ with red stripe LEELBOX. I tried to recover using USB Burning Tool but cannot get a connection at all. It is just plain dead and won't respond. Any ideas for recovery and anybody know which ROM i should have used? Also strange enough, it would not boot into recovery from new so i had to go through the update app, something i hadn't done before but the .img fully installed and rebooted to nothing. No lights or anything. The board inside is labeled MXQ-805 VER. 1.0 DATE 151122. I looked through board pictures on google and have not found one that looks the same?

you might need to short your nand pins, you can google how to do that or try to find the thread that talks about it here, I think its pins 7-8 and try to load an img with amlogic burning tool ***NOTE this is at your own risk***

[gcsuri]

EDIT: MXQ build reported not to boot, deleted. A new build will be available soon.

You may provide only the nand_env instead of the full bootloader. I think it's more safely.

[pigbait]

kszaq, I flashed 2 OTT all black with the 6.0.0.2-2 test HD18Q and they are stuck at the OE splash, reverted to 6.0.0.1 and everything is good. let me know if you need a log or something. and I understand it difficult to build without a device.

Thanks for all your work

[kszaq]

You may provide only the nand_env instead of the full bootloader. I think it's more safely.

Thank you for the tip. Can you share some more information on this, an example? Does it allow to change u-boot scripts, like in this commit: https://github.com/kszaq/u-boot/comm...59c86b3a217216 ? This is the only thing I need to make booting from SD card work.

[sonofdibnah]

Reverted back to 6.0.0.1 with no problems on the MXQ beelink red. Now I know I can do it, I'm looking forward to the next attempt kszaq. I'm more than happy to test as I can understand how difficult it can be without your box.

[PatrickJB]

Possible CPU overload / over heating!

This relates to the MXQ 6.0.0.1 build and possible the previous build which also had this glitch on a number of occasions. It's an all black MXQ box. My TV screen flashes black for a second and then reverts to Kodi it does this several times and sometimes keeps doing it forcing me to reboot. It may be something to do with the refresh rate switching on my TV stumbling but I'm slightly concerned it may be the CPU. And yes all four cores are running. K's recent comment about having two boxes die is slightly worrying!

I was going to review the 6.0.0.1 build but it seems we all agree it's fine and seems slightly improved mainly because of the incremental update of Kodi.

I've had a nightmare with my box until recently so I'm not rushing to update until I know a build is reasonably stable. Having said that I'm looking forward to the Jarvis release which will obviously be sometime coming and will probably be the point at which I will accept that my box has reached it's full potential.

As a side note: it would be nice to get the Wifi working but it's not a deal breaker as I'm pretty happy with K's build. This post will help new people decide which version of K's build to run on their MXQ, also note that the Wifi is mentioned as being crap which I've heard several times in the past. Will photo my box when I get a mo and add it to the thread. http://freaktab.com/forum/tv-player-...736#post551736

[miguelf]

kszaq Looks like ethernet speed improved a bit in this last version like +6/7Mb!

Some of the things that i noticed that are missing or not working properly:
- Only english is available for system languages.
- Menu transitions are not smooth yet.
- In sports devil add-on (this happened also in previous versions) the time displayed in the games list is allways one hour in advance.

Thanks for your work kszaq amazing

[kszaq]

Reverted back to 6.0.0.1 with no problems on the MXQ beelink red. Now I know I can do it, I'm looking forward to the next attempt kszaq. I'm more than happy to test as I can understand how difficult it can be without your box.

With first and second build of 6.0.0.2 I assumed that MXQ would work fine with updated MMC kernel driver. I remember having had that bug with the kernel we use in 'stable' releases so for the third release candidate I reverted the MMC driver once again. I'm providing you with tar update package only:

http://s805.eu/test/6.0.0.2-3/

Works fine on my MK808B+.

Possible CPU overload / over heating!

This relates to the MXQ 6.0.0.1 build and possible the previous build which also had this glitch on a number of occasions. It's an all black MXQ box. My TV screen flashes black for a second and then reverts to Kodi it does this several times and sometimes keeps doing it forcing me to reboot. It may be something to do with the refresh rate switching on my TV stumbling but I'm slightly concerned it may be the CPU. And yes all four cores are running. K's recent comment about having two boxes die is slightly worrying!

I was going to review the 6.0.0.1 build but it seems we all agree it's fine and seems slightly improved mainly because of the incremental update of Kodi.

I've had a nightmare with my box until recently so I'm not rushing to update until I know a build is reasonably stable. Having said that I'm looking forward to the Jarvis release which will obviously be sometime coming and will probably be the point at which I will accept that my box has reached it's full potential.

As a side note: it would be nice to get the Wifi working but it's not a deal breaker as I'm pretty happy with K's build. This post will help new people decide which version of K's build to run on their MXQ, also note that the Wifi is mentioned as being crap which I've heard several times in the past. Will photo my box when I get a mo and add it to the thread. http://freaktab.com/forum/tv-player-...736#post551736

It seems like NAND-brick bug happens mostly - or only - with HD18Q "V3" board. For future releases I will make NAND ZIP not update bootloader so that uses can safely try my ROM. Unfortunately the only way to make SD booting work is replacing bootloader and that's what bricks the devices. I will try to find device's manufacturer and reach out to them for u-boot source code so that I may compile updated kernel. I hope they will want to cooperate.

As for CPU-related issues, you may want to downclock your CPU a little bit by adding the following command to autostart script:

echo 1250000 > /sys/bus/cpu/devices/cpu0/cpufreq/scaling_max_freq

or try switching CPU governors.

[gcsuri]

Thank you for the tip. Can you share some more information on this, an example? Does it allow to change u-boot scripts, like in this commit: https://github.com/kszaq/u-boot/comm...59c86b3a217216 ? This is the only thing I need to make booting from SD card work.

Hi,

I think there is more way to write the uboot variables on S805.
- if you are root on factory android firmware you can use setprop ubootenv.var.VARIABLENAME 'VALUE' syntax - I think there is a limitation, because longer values aren't written...
- recovery binary has a function set_bootloader_env("name", 'value') function. you can put it into the updater-script.
- there are fw_setenv/fw_printenv tool - need to compile the binaries.
- dump the whole nand and write back - I don't know how because on some kernel it's a character device.

best regards, gcsuri

[sonofdibnah]

Good morning. Tried 6.0.0.2-3 just now. It boots to the Openelec screen and stops there. I've tried a couple of reboots but its the same each time. There's nothing more I can say about it apart from it looks better than the screen full of text!

I've got guests staying with me but I'll do my best to be prompt in reacting to updates.

[mylle]

I just updated to OpenELEC-Amlogic.MXQ.arm-6.0-devel-20160124000647-r21605-gadbddbe.tar but unfortunately it does not boot. Just a bunch of errors on screen

Picture attached. Dont know if its any help? I have a red stripe MXQ

http://imgur.com/NKFgUR6

[sonofdibnah]

I just updated to OpenELEC-Amlogic.MXQ.arm-6.0-devel-20160124000647-r21605-gadbddbe.tar but unfortunately it does not boot. Just a bunch of errors on screen

Picture attached. Dont know if its any help? I have a red stripe MXQ

http://imgur.com/NKFgUR6

That's odd because the screen looks to be the same as I got with kszaq's first release that he pulled after I reported it. I am getting a different behaviour with this as I've reported above. Are you running off SD card or nand. I'm on SD now but initially reported incorrectly that I was on sd (sorry kszaq, I run two in different rooms and I got them mixed up.) Mentioning this because I think it may be relevant.

[mylle]

Im running of Nand. Update ftom the 6.0.0.1 release

[MeleTest]

Good morning. Tried 6.0.0.2-3 just now. It boots to the Openelec screen and stops there. I've tried a couple of reboots but its the same each time. There's nothing more I can say about it apart from it looks better than the screen full of text!
.

I have the same issue.
kszaq : if this can help, on my RED mxq, i have:
1. Tried the TV110 version : same issue as mentionned up.
2. Tried the MK808B+ version and:
- It boots correctly
- HDMI CEC works
-- the only issue i notice ; there is no sound with HD videos when Passthrough is enabled.

Regards

[mike77]

I just updated to OpenELEC-Amlogic.MXQ.arm-6.0-devel-20160124000647-r21605-gadbddbe.tar but unfortunately it does not boot. Just a bunch of errors on screen

Picture attached. Dont know if its any help? I have a red stripe MXQ

http://imgur.com/NKFgUR6

same for me , mxq red stripe , boot stay at openelec logo.
but for testing i tried install update .tar for mk808b+ on my mxq and works ok , boot up normally