[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[kszaq]

no dice on my device went from 6.0.1.1 to 6.0.1.3 and just stuck at MXQ logo. i will try and send you a twrp copy of the original firmware. thanks for all your tine and help

A copy of boot.img would be sufficient if you still have an original firmware on NAND. Can you tell whether MXQ version of this development build works for you at all? If you check that, I will know if the problem lies in multi-dtb support or simply a wrong device tree. Thanks.

I hope that you're aware that when booting from SD card you can simply replace kernel.img and SYSTEM using your computer instead of tedious toothpick-install-reboot process?

Edit: If you have original firmware on NAND, you can also make a backup in OpenELEC. For example, to backup kernel and recovery:

dd if=/dev/boot | gzip > /storage/downloads/boot.img.gz
dd if=/dev/recovery | gzip > /storage/downloads/recovery.img.gz

Edit2: Please also get me your env variables and uboot. You need to do this in OpenELEC, one of these commands will not work, don't worry:

dd if=/dev/bootloader | gzip > /storage/downloads/bootloader.img.gz
dd if=/dev/env | gzip > /storage/downloads/env.img.gz
dd if=/dev/nand_env | gzip > /storage/downloads/nand_env.img.gz

Resulting files can be found in Downloads Windows share. Thanks!

[sonofdibnah]

For all of you getting issues with booting 6.0.1.2, here's a build to test: http://s805.eu/test/6.0.1.3-devel-20160219/

Changelog:

• reverted device trees to those used in 6.0.1.1 and prior
• m201C_1G and m201C_512M device trees in HD18Q build replaced with what I found on Baidu

sonofdibnah This should also fix your S/PDIF issue.

Yes it does. Many thanks. Sounds like these device trees are a bit tricky.

[pigbait]

A copy of boot.img would be sufficient if you still have an original firmware on NAND. Can you tell whether MXQ version of this development build works for you at all? If you check that, I will know if the problem lies in multi-dtb support or simply a wrong device tree. Thanks.

I hope that you're aware that when booting from SD card you can simply replace kernel.img and SYSTEM using your computer instead of tedious toothpick-install-reboot process?

Edit: If you have original firmware on NAND, you can also make a backup in OpenELEC. For example, to backup kernel and recovery:

dd if=/dev/boot | gzip > /storage/downloads/boot.img.gz
dd if=/dev/recovery | gzip > /storage/downloads/recovery.img.gz

Edit2: Please also get me your env variables and uboot. You need to do this in OpenELEC, one of these commands will not work, don't worry:

dd if=/dev/bootloader | gzip > /storage/downloads/bootloader.img.gz
dd if=/dev/env | gzip > /storage/downloads/env.img.gz
dd if=/dev/nand_env | gzip > /storage/downloads/nand_env.img.gz

Resulting files can be found in Downloads Windows share. Thanks!

6.0.1.1 boots up on my device no problem. unfortunately i did a nand flash a long time ago and never got a nand back. luckily i have a friend with the same box i will try and get a backup with twrp.

its honestly not a huge deal. as i think this is a Frankenstein board. the marking on the board is TY_T2_v1.1 and cant find the factory firmware

[kszaq]

6.0.1.1 boots up on my device no problem. unfortunately i did a nand flash a long time ago and never got a nand back. luckily i have a friend with the same box i will try and get a backup with twrp.

If you can generate these files for your box, it may also help me see where the issue is. Please generate the files using code I provided in OpenELEC. Thanks.

[pigbait]

no problem

[vn800art]

As first apologies for misinformation posted: Superceleron 1.4b has TWRP recovery included ( but we were talking about MK808b Plus). Without considering this I took a MXQ S85 (Beelink) I had with Superceleron 1.4 and shove in the Sdcard an old build from You devel 6.0.01 maybe, all well. Then loaded your last 6.0.1.2 and everything is working. Bluetooth support is initial I believe, as it turns on but cannot connect ( ZenFone 2 551ml). I will try later with Nexus5 stock to see if there are differences.
One question: I can connect with Wi-Fi but apparently I do not find a way to connect via Ethernet, which is also connected. Thought that on your old November build (6.0.0.1) the wired connection appeared too in Openelec settings!
Thanks a lot!

[phinc]

Does anybody have an advice for a USB WIFI stick that works with this build?

[vn800art]

Will try 6.0.1.3 in a small while!
Edit one hit: Ethernet is back! One miss: this time Bluetooth doesn'connect, even if the interface is there, and crashes openelec settings interface,. On the two builds the words from Bluetooth interface not connecting are: Bluetooth error: protocol not available.
Loaded .tar via SSH in android! Impossible for my noobness to use putty in windows!
Trying new Ethernet connection.
Thanks for your work, Kszaq!
Edit 2 Second HIT! Remote working, shutoff=> red light . Wasn't working before! Yeahhh!

[pigbait]

kszaq Here is a TWRP backup of the TY_T2_v1.1..... I also got arround to generate the files from 6.0.1.1 for you.

https://www.dropbox.com/sh/ugluth8l8...JiNdGyy5a?dl=0

[rev6]

Jarvis released today.

[kszaq]

As first apologies for misinformation posted: Superceleron 1.4b has TWRP recovery included ( but we were talking about MK808b Plus). Without considering this I took a MXQ S85 (Beelink) I had with Superceleron 1.4 and shove in the Sdcard an old build from You devel 6.0.01 maybe, all well. Then loaded your last 6.0.1.2 and everything is working. Bluetooth support is initial I believe, as it turns on but cannot connect ( ZenFone 2 551ml). I will try later with Nexus5 stock to see if there are differences.
One question: I can connect with Wi-Fi but apparently I do not find a way to connect via Ethernet, which is also connected. Thought that on your old November build (6.0.0.1) the wired connection appeared too in Openelec settings!
Thanks a lot!

Wired connection drivers are still there and work OK for me. Maybe you mistakenly loaded a MK808B+ build which doesn't have ethernet driver built-in?

Will try 6.0.1.3 in a small while!
Edit one hit: Ethernet is back! One miss: this time Bluetooth doesn'connect, even if the interface is there, and crashes openelec settings interface,. On the two builds the words from Bluetooth interface not connecting are: Bluetooth error: protocol not available.
Loaded .tar via SSH in android! Impossible for my noobness to use putty in windows!
Trying new Ethernet connection.
Thanks for your work, Kszaq!
Edit 2 Second HIT! Remote working, shutoff=> red light . Wasn't working before! Yeahhh!

Bluetooth may be not working if it's a newer chip - I tested my builds only on AP6210 and AP6212 - or if it's not available in your device.

kszaq Here is a TWRP backup of the TY_T2_v1.1..... I also got arround to generate the files from 6.0.1.1 for you.

https://www.dropbox.com/sh/ugluth8l8...JiNdGyy5a?dl=0

Thank you for the files. The funny thing is that 6.0.1.1 works for you because of my mistake in build script... HD18Q version got a MXQ device tree and that makes it work for you.
Can you try using this build: http://s805.eu/test/6.0.1.3-devel-20160221/

Jarvis released today.

There's no official OpenELEC Jarvis release, not even a beta. Like I said before, I need to make 6.0.1.3 work well and then I'll move to building Jarvis.

[kostaman]

I have the ALL BLACK MXQ "Board AM_MXQ-A 20150825 8189etv wifi chip" It came with the SAME remote control supplied with the red stripe MXQ'S.
I have used the MXQ Arm Builds with no problems. With the HD18Q builds the remote did not work and i tried the MXQ Build which works.
I am currently on 6.0.1.2 all working. (Blue light always on but that is known issue).
Just letting people know.

[pigbait]

kszaq I flashed the MXQ version of 6.0.1.3 and perfect. everything is booting up nice. Thanks for all your time

[sammaz]

kszaq Can you add this open source linux Ubuntu 15 Broadcom 43xx (b43) driver https://help.ubuntu.com/community/Wi...Driver/bcm43xx and http://www.linuxwireless.org/en/users/Drivers/b43/ to the next test release? It will be sweet to use my wDNA3100v2 USB stick with Openelec on the MK808B plus.

lsusb from my stick :

Bus 002 Device 002: ID 0846:9011 NetGear, Inc. WNDA3100v2 802.11abgn [Broadcom BCM4323]

Forums say I would need this driver :

Broadcom_bcm43xx_USB_32_64bit_v2

and I see that it does exist on the latest version of openelec :

OpenELEC:/lib/modules/3.10.94/kernel/drivers/net/wireless/b43/b43.ko

[phinc]

kszaq: Thanks for your efforts on HDMI CEC on old Samsung TVs. I installed 6.0.1.2 as well as the libcec test build. Both with the CEC enabler addon and the line added to autostart.sh. Unortunately the TV can`t find the MK808+. Maybe my TV is too old...