[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[hockeycraze]

kszaq i can confirm that wifi driver now loads successfully for every reboot in your last test build. wifi is very slow now though but hopefully this will be fixed in the final 6.0.1.2 release. in 6.0.1.1, when the wifi driver would load, the wifi was very fast and very stable. let me know if you require logs. thanks kszaq

[kszaq]

thanks work great now with the color buton, but with this new version have black screen whenn i play a video, audio works, need restart to become video, i have 3 time this bug, i thing is a bug.
waiting for new release, thanks for your good job,
i spend you a beer...

burimek I need logs to tell what's happening when no video comes out.

Help ! Bricked my MXQ_A. I updated the bootloader using kszaq instructions a few pages back and then went to reboot and noticed something I don't normally see and that was no flickering whatsoever on TV. No matter what I do there is no image on TV. Now I've tried USB update method using Amlogic USB Burning Tool but no matter what I do the box does not register. The LED is still on though (blue). Is there anything I can do ? EDIT: Scarily, with nothing to lose I had it connected to PC and Burning Tool running and shorted some pins on what I thought might be the Nand chip and then, by complete suprise I heard Windows10 detect a device and I looked up and it had started programming it! Strange why it would suddenly mess up like that, all I did was flash a bootloader !

jed A hard-learned lesson then then: don't flash bootloader on an unknown device. I decided to remove all bootloader-updating packages from my site to avoid that kind of situations in the future. From now on, users should only update uenv which is 100% safe. I took another look at the boot image you posted and your box uses m201C_1G board for which device tree is a little bit different than m201_1G we use. I bet that is the reason for the lockups. To support this board, I would need to introduce multi-dtb support...

kszaq i can confirm that wifi driver now loads successfully for every reboot in your last test build. wifi is very slow now though but hopefully this will be fixed in the final 6.0.1.2 release. in 6.0.1.1, when the wifi driver would load, the wifi was very fast and very stable. let me know if you require logs. thanks kszaq

hockeycraze Thanks for reporting that the driver loads every time now. For 6.0.1.2-test1 I changed one thing in the driver - disabled power saving - what ironically may have decreased your WiFi performance. I'll revert that change for 6.0.1.2 final.

[Hercules Man]

Looking forward to testing 6.0.1.2, especially if it fixes scaling governor and CPU voltage related issues, many thanks kszaq for your hard work :-)

[jed]

jed A hard-learned lesson then then: don't flash bootloader on an unknown device. I decided to remove all bootloader-updating packages from my site to avoid that kind of situations in the future. From now on, users should only update uenv which is 100% safe. I took another look at the boot image you posted and your box uses m201C_1G board for which device tree is a little bit different than m201_1G we use. I bet that is the reason for the lockups. To support this board, I would need to introduce multi-dtb support...

kszaq The bootloader flashed was the stock one ! But I learned how to short pins and recover a box, now thats a valuable lesson :-) For the m201C, I no longer have this box but from another thread (Clones Directory) others do and perhaps this chip is what people will get now if they buy an "all-black-MXQ". Can you tell us what is multi-dtb support ?

[hockeycraze]

kszaq it may have been my WiFi connection yesterday, but today the WiFi works perfectly and very fast. Hd iptv streams working with no buffering. I don't think you need to revert the change

[hockeycraze]

kszaq never mind I spoke too soon again lol, the WiFi is again excruciatingly slow after about 30 minutes of usage. Might be best to revert the change after all. thanks kszaq

[kszaq]

kszaq The bootloader flashed was the stock one ! But I learned how to short pins and recover a box, now thats a valuable lesson :-) For the m201C, I no longer have this box but from another thread (Clones Directory) others do and perhaps this chip is what people will get now if they buy an "all-black-MXQ". Can you tell us what is multi-dtb support ?

Multi-dtb support allows to include more than one device in single kernel image. A correct device tree should be picked by bootloader so in theory I can support "regular" and "m201C" boxes with one build. This can be done when Amlogic's board name is different, e.g. m201_1G vs m201C_1G and not when name printed on board differs so I can't include device tree for every board on the market since there will be no way for uboot tell which device tree to pick.

Can you please give me a link to factory firmware for that m201C box?

hockeycraze I'll revert that change for 6.0.1.2.

[jed]

Multi-dtb support allows to include more than one device in single kernel image. A correct device tree should be picked by bootloader so in theory I can support "regular" and "m201C" boxes with one build. This can be done when Amlogic's board name is different, e.g. m201_1G vs m201C_1G and not when name printed on board differs so I can't include device tree for every board on the market since there will be no way for uboot tell which device tree to pick.

Can you please give me a link to factory firmware for that m201C box?

hockeycraze I'll revert that change for 6.0.1.2.

kszaq Thanks for the info on multi-dtb. I am sorry I cannot help as I never had the factory firmware for the m201C - all I was able to send you before was the boot partition backed up by TWRP if you recall. Do you have any idea when the 001122334455 MAC address for stable IP will return please ? Thanks.

[kszaq]

Guest Thanks for the info on multi-dtb. I am sorry I cannot help as I never had the factory firmware for the m201C - all I was able to send you before was the boot partition backed up by TWRP if you recall. Do you have any idea when the 001122334455 MAC address for stable IP will return please ? Thanks.

I have a fix ready for the next release (still testing some other changes). As far as I remember, it's already included in a test1 version available here: http://s805.eu/test/6.0.1.2-test1/
You can safely update to it and check if MAC changing is gone. It's stable enough to use.

And by the way, the fix is not mac=00:11:22:33:44:55 in kernel command line as this doesn't work anymore.

[jed]

I have a fix ready for the next release (still testing some other changes). As far as I remember, it's already included in a test1 version available here: http://s805.eu/test/6.0.1.2-test1/
You can safely update to it and check if MAC changing is gone. It's stable enough to use.

And by the way, the fix is not mac=00:11:22:33:44:55 in kernel command line as this doesn't work anymore.

kszaq Yes that works - stable MAC address (not 001122334455) and same IP address on reboot - I think same IP as the Android gave me too so I guess working in a more "correct" way than the 001122334455 fix did. Thanks ! I also noticed the writing on bootup that appeared over OpenElec screen is now gone too that was in 6.0.1.1 :-) Thanks !

[phinc]

phinc I use my boxes with "F" series TV and it works well. With a "B" series TV it's a bit hit and miss but I solved it somehow by resetting CEC at boot. You can do it by adding the following code to autostart.sh:

echo 0x0 > /sys/class/amhdmitx/amhdmitx0/cec_config
echo 0xf > /sys/class/amhdmitx/amhdmitx0/cec_config

Thanks for your reply. Unfortunately it did not work for me. To be honest, i have no idea what the "F" and "B" series are. I have an old LE32C530F1W. The MK808B+ is not recognized in the TV's device list. It may also be the cable. I bought one that was specifically labelled as "HDMI CEC", but i have no way of testing if it really works.

[sonofdibnah]

I have a fix ready for the next release (still testing some other changes). As far as I remember, it's already included in a test1 version available here: http://s805.eu/test/6.0.1.2-test1/
You can safely update to it and check if MAC changing is gone. It's stable enough to use.

And by the way, the fix is not mac=00:11:22:33:44:55 in kernel command line as this doesn't work anymore.

I can confirm that the IP address stays the same after reboot when using ethernet on Beelink MXQ.

great news for Kore remote. Thanks kszaq.

[massy086]

Originally posted by pigbait View Post
I have a few Remote.config I will be posting later on

Edit: As promised these are remote.conf I found that have fixed most of my boxes with non working remotes.

https://onedrive.live.com/redir?resi...hint=folder%2c




hi i used remote 3 all working but the ok button does not work. does anyone have a fix for this??????

[fanni2]

Multi-dtb support allows to include more than one device in single kernel image. A correct device tree should be picked by bootloader so in theory I can support "regular" and "m201C" boxes with one build. This can be done when Amlogic's board name is different, e.g. m201_1G vs m201C_1G and not when name printed on board differs so I can't include device tree for every board on the market since there will be no way for uboot tell which device tree to pick.

Can you please give me a link to factory firmware for that m201C box?

hockeycraze I'll revert that change for 6.0.1.2.

Hi mate I have 2 of these m201c box's but haven't got a link for the factory firmware image but if there is something i can extract for you then let me know

[fanni2]

Right after flashing many different versions on openelec i have finally found one that works with the m201c it's OpenELEC-Amlogic.HD18Q.arm-6.0.1.1