[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[md22]

For MAC address issue, please try the following:

1. Download two files from http://s805.eu/test/readmacfromusid/ and copy them to SD card.
2. Connect SD card to the box and use toothpick method to flash the file (don't worry, it doesn't delete anything!).
3. Check if MAC address issue is solved. You can also post a result of cat /proc/cmdline.

For Power LED, I decided to remove LED-managing code from HD18Q builds. There are many boards on the market and every board has different GPIO mappings so it'll always be working for some and not for others. For my board (HTC-MXQ-v4) factory-supplied bootloader manages switching power LED and it does that well.

I flash the file above and it does not solve the problem.

OpenELEC (community) Version: 6.0.1.1
OpenELEC:~ # cat /proc/cmdline
init=/init console=ttyS0,115200n8 no_console_suspend storage=1 cvbsdrv=0 vdaccfg =0xa000 logo=osd1,loaded,0x7900000,720p,full hdmimode=720p cvbsmode=480cvbs andr oidboot.firstboot=0 hdmitx= reboot_mode=normal console=tty0 consoleblank=0 scali ng_governor=interactive scaling_min_freq=96000 scaling_max_freq=1536000 hdmitx=c ecf BOOT_IMAGE=/dev/boot boot=/dev/system disk=/dev/data

[jed]

For MAC address issue, please try the following:

1. Download two files from http://s805.eu/test/readmacfromusid/ and copy them to SD card.
2. Connect SD card to the box and use toothpick method to flash the file (don't worry, it doesn't delete anything!).
3. Check if MAC address issue is solved. You can also post a result of cat /proc/cmdline.

For Power LED, I decided to remove LED-managing code from HD18Q builds. There are many boards on the market and every board has different GPIO mappings so it'll always be working for some and not for others. For my board (HTC-MXQ-v4) factory-supplied bootloader manages switching power LED and it does that well.

kszaq So I tried flashing that bootloader, not sure if it worked or not, the android robot came and the line under looked like it only went about a third of the way across. Still incremental IP addresses on reboot. I tried flashing a few times and same thing. here is the result of that command you asked for:

init=/init console=ttyS0,115200n8 no_console_suspend storage=1 cvbsdrv=0 vdaccfg=0xa000 logo=osd1,loaded,0x7900000,720p,full hdmimode=720p cvbsmode=576cvbs androidboot.firstboot=1 hdmitx= reboot_mode=normal console=tty0 consoleblank=0 scaling_governor=interactive scaling_min_freq=96000 scaling_max_freq=1536000 hdmitx=cecf BOOT_IMAGE=/dev/boot boot=/dev/system disk=/dev/data

By the way where did you get HD18Q from with that configuration, perhaps I should get the same one as you make life easier :-)

[PatrickJB]

Didn't seem to work for me either still random MAC addresses for ethernet connection, if any! Sorry can't do the techie bit and I don't think the Kodi log is any good to you. I can also add that the wifi does seem to drop-of-a-cliff for some reason, don't know how to get data on this, but it does seem to slow up i.e Connecting to the BBC news normally a second on ethernet but on wifi can take as long as 4 seconds.

Hmm I didn't choose a good day to give up drinking!

Or smoking!!

[Mudda_funkA]

Some strange things happening on my MxQ OTT. I have updated from 6.0.0.2 to 6.0.1.1 and now my box just randomly powers off. Red standby light is always on but was ok on 6.0.0.2. After I originally unbricked my box back to a version of Android, the led is a mix of red/blue creating a strobe like effect. Sequence was red standby, powering up blue, then turns red/blue just before homescreen shows. This was the case in Android and also running OpenELEC 6.0.0.2. Now its all gone tits, box just shuts down. Its a shame because I could see the speed improvement over 6.0.0.2


H MAn

is the led on your unit off centre to the right?

[felixob]

I'd say you need to update TVHeadend to the latest version.

Well I uninstalled tvheadend (the service, not the client). Then I've installed unofficial OpenElec repository and reinstalled tvheadend service from this repository. And now, after rebooting, it works again!!!
I don't know what tvheadend version I had before, but it was working until the last update.

Thanks a lot for all your work.

[jed]

This **** seller claims only his all black MXQ is "genuine" (v4 ?) and the difference is in which way up the network socket is. If this is true - which I doubt, then mine is a "clone" - I thought they were all "clones" but not sure of what !? Will the real MXQ please stand up !? It would be good if there were a standard/genuine version then I could buy one and we might have a "standard" HD18Q build perhaps for openelec. Here's the link: http://www.****.co.uk/itm/1118943372...%3AMEBIDX%3AIT what do you think ? Does anyone know if this is true or just a sales claim ?

[bromilow746745]

JoeyDaPhish bromilow746745 Power on is handled by bootloader and to fix your issue you need to flash bootloader from an Android firmware for your box. The easiest - albeit longish - way to do this is:

1. Backup OpenELEC settings to an external drive.
2. Flash Android firmware.
3. Flash OpenELEC back (6.0.0.2 or later).
4. Restore OpenELEC settings.

The fastest way, but you need to do this carefully:

1. Download a bootloader update ZIP from this folder: http://s805.eu/releases/6.0.0.1/Bootloader/
2. Replace bootloader.img in ZIP file with the one from Android firmware.
3. Sign the ZIP (use any Android APK sign tool you can find or download from https://github.com/kszaq/OpenELEC.tv.../tools/signapk and use java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 bootloader.zip bootloader.signed.zip command.
4. Flash bootloader in recovery - you can reboot to recovery by either using toothpick or issuing reboot recovery command.

I'd say you need to update TVHeadend to the latest version.

@Everyone Before anyone reports it, I discovered a non-working Bluetooth issue. I'll try to fix it for the next release.

my box had the original firmware on it still so would this make any difference?

[PatrickJB]

This **** seller claims only his all black MXQ is "genuine" (v4 ?) and the difference is in which way up the network socket is. If this is true - which I doubt, then mine is a "clone" - I thought they were all "clones" but not sure of what !? Will the real MXQ please stand up !? It would be good if there were a standard/genuine version then I could buy one and we might have a "standard" HD18Q build perhaps for openelec. Here's the link: http://www.****.co.uk/itm/1118943372...%3AMEBIDX%3AIT what do you think ? Does anyone know if this is true or just a sales claim ?

Sounds like BS to me, especially the bit about HDMI cables! I have the same as you jed and mine came in a OTT box with a little manual, the seller also claimed theirs was the real deal although didn't give any reasons. Ours doesn't have the heat-sink, that's the only thing I wonder about but perhaps they don't need one, think quad core tablets obviously no heat-sinks in them. I think there's a glut of these boxes and sellers are having a job to get rid of them as well as dealing with lots of returns. Basically the Android versions are crappy but that's just my opinion.

Just for the record jed did you get a dispatch email for that ghostly MXQ deal yesterday? Not sure whether to wait or just get my money back?

As for the current situation with K's build I've downgraded to 6.0.0.2 and now the time works with my ethernet dongle again. Fingers crossed it doesn't go tits up again! For some reason it's take a minute or two to sort the time out but it does work. I'll upgrade when the MAC/Wifi thing is sorted as 6.0.0.2 works OK for me. Yes be nice to get things sorted, wifi etc but, all things in time.

EDIT: Oh and just for the record the newer build seem to have a greater load on the cpu than the 6.0.0.2 build. Not sure what upped the load so much. Older around 35% total playing video newer was over 50% total playing video. Pretty sure the were the same vids.

[jed]

Just for the record jed did you get a dispatch email for that ghostly MXQ deal yesterday? Not sure whether to wait or just get my money back?

Yes, I did ! But on the phone they hinted at "unusual activity" and wouldnt tell me if fraudulent or not but I assume its just a money coiner as if somethings half the price, of course they're going to sell hundreds within hours and if so I doubt very much the dispatch note means anything ! It would be a simple matter to play nice for a few weeks and get good feedback and then "go in for the kill". Anyway, I have a refund and **** wouldhave seen dispatch note too and yet still refunded immediately the case was raised (on phone as the listing and seller no longer exist on mainstream ****. If it did arrive then I will certainly refund the refund as it will be a bargain but if I were a betting man and all that !

[jed]

kszaq You hinted in one of your posts that on your HD18Q you use the original bootloader which works the LED so my question is how can I flash you OpenElec but maintain the original (Android) Bootloader ? I would like to try if this works in my case for the LED. The usual flashing overwrites bootloader I think - which is how I lost my "MXQ" bootup screen - its just blank now until the Openelec screen comes up.Thanks.

[PatrickJB]

kszaq You hinted in one of your posts that on your HD18Q you use the original bootloader which works the LED so my question is how can I flash you OpenElec but maintain the original (Android) Bootloader ? I would like to try if this works in my case for the LED. The usual flashing overwrites bootloader I think - which is how I lost my "MXQ" bootup screen - its just blank now until the Openelec screen comes up.Thanks.

Just for the record I still get the Google TV splash screen on startup. There was a few roms I tried that didn't give me the google screen, think the main one was the droid player rom (android). http://www.droidplayer.co.uk/

[jed]

Just for the record I still get the Google TV splash screen on startup. There was a few roms I tried that didn't give me the google screen, think the main one was the droid player rom (android). http://www.droidplayer.co.uk/

I've never had the GoogleTV splash only MXQ splash. Do you know what Android you had on there just before you first flashed Openelec ?

[jed]

kszaq So here is something interesting, I was playing around trying to regain my lost MXQ splash screen so I flashed original Android firmware and then immediately flashed your MXQ 6.0.1.1. This retained the MXQ splash screen and so I believe the original Android bootlader - ok so far so good but now I have lost the ability to power off and it just does a displayoff/suspend AND it works the LED but the wrong way round - Blue when suspended and Red when on, AND the IP address is no longer incremented - so it must be picking up MAC address now OK. So all this is linked to what bootloader/splash screen is in place clearly. So either its a clean poweroff OR its happy/constant IP address but not both together :-( Well at least we know its all linked now and bootloader dependant and I guess now the LED is working (in the wrong direction) this might also be possible to reverse ? Thanks, I hope this new info helps or maybe just tells you what you already knew. [EDIT] So the LED being RED but the device actually on allowed me to get a difference in the cat /sys/kernel/debug/gpio runs and so from a fresh bootup, with LED Blue there was no reading for gpio-1 (aml-sysled) but after going to standby and on again, so the device was on but the LED was Red the reading was gpio-1 (aml-sysled ) out hi so at least that identfies where its at. Clearly the bootloader is controlling the LED but the OpenElec (both HD18Q and MXQ 6.0.1.1 versions) are reversing something somehow. Note that in the Android where this bootloader came from, the LED works the correct way round but it only goes to standby when clicking on the OFF button on the Remote - so its the same poweroff/standby behaviour in Android as it is in 6.0.1.1 using the same bootloader. I think a little progress this evening :-)

[PatrickJB]

Here's the Droid Player ROM. Use at own risk! Don't think our remote works with it, can't remember about wifi as it was way before Christ-thing. Not sure if the attachment uploaded!!!!!

Hmmm, sorry don't think that worked! Sure it's around on the web somewhere.

EDIT: Yes it does seem that the bootloader is the key to many of these problems. Not sure if K can sort this out, probably not but, I don't know and I'm having another bottle of beer an to hell with it!

[flolow]

I see you removed the latest version, so maybe the following is known? MXQ box with 8188ETV will not connect but AP's are seen. Tried all build versions (hd18q and mxq) down to MXQ 5.95.5.2 which works fine.
Thank you for your work.