[ROM] Unofficial OpenELEC for MK808B+ and MXQ

[ace9094]

Hi folks,

Is it possible to revert back to Android from unofficial Openelec on the MXQ, I have flashed Openelec for a friend, however they prefer Android and would like me to revert it back if possible.

I tried to revert back using the "Toothpick" method and stock firmware on a micro SD card from Geekbuying.com, but it just boots back to Openelec and does not start the flashing process.

I have used the Openelec version 5.0.8.18 by kszaq from this thread. I have been looking around online for a solution but have so far been unsuccessful.

Has anyone ever managed to revert back to Android from Openelec before or have ideas I could try?

Thanks
ace

[pigbait]

Hi folks,

Is it possible to revert back to Android from unofficial Openelec on the MXQ, I have flashed Openelec for a friend, however they prefer Android and would like me to revert it back if possible.

I tried to revert back using the "Toothpick" method and stock firmware on a micro SD card from Geekbuying.com, but it just boots back to Openelec and does not start the flashing process.

I have used the Openelec version 5.0.8.18 by kszaq from this thread. I have been looking around online for a solution but have so far been unsuccessful.

Has anyone ever managed to revert back to Android from Openelec before or have ideas I could try?

Thanks
ace

have you tried SSH to your box with PuTTY and loging in with username:root password: openelec and once in the cmd window try reboot recovery. and try flashing your android rom

[ace9094]

have you tried SSH to your box with PuTTY and loging in with username:root password: openelec and once in the cmd window try reboot recovery. and try flashing your android rom

I have not tried that, I will give it a try.... I am guessing "Reboot Recovery" a command I type... Thank you, I will report back if it works or not

[ilgimmy]

Hi folks,

Is it possible to revert back to Android from unofficial Openelec on the MXQ, I have flashed Openelec for a friend, however they prefer Android and would like me to revert it back if possible.

I tried to revert back using the "Toothpick" method and stock firmware on a micro SD card from Geekbuying.com, but it just boots back to Openelec and does not start the flashing process.

I have used the Openelec version 5.0.8.18 by kszaq from this thread. I have been looking around online for a solution but have so far been unsuccessful.

Has anyone ever managed to revert back to Android from Openelec before or have ideas I could try?

Thanks
ace

your solution is USB firmware download.
Get 110k4 for USB download from here: https://mega.co.nz/#!bhtH3BrK!mtmPJV...W0ty2mYIriKoN4
Get USB download tool from here: http://probox2.com/wp-content/upload...grade-tool.zip (requires windows 8 driver signature enforcement disabled)
Follow those instructions:

• install upgrade tool
• disable il driver signature enforcement (windows 8 only)
• connect MXQ to PC with USB - microUSB cable
• put a toothpick in A/V port (you'll find a switch) and press power button at the same time
• after some seconds windows will detect the device (you can leave the power button now)
• start AMLogic USB burning tool and set English language
• Press "File" -> "import image" and choose the .img file you downloaded before
• wait for the operation to complete

[ace9094]

your solution is USB firmware download.
Get 110k4 for USB download from here: https://mega.co.nz/#!bhtH3BrK!mtmPJV...W0ty2mYIriKoN4
Get USB download tool from here: http://probox2.com/wp-content/upload...grade-tool.zip (requires windows 8 driver signature enforcement disabled)
Follow those instructions:

• install upgrade tool
• disable il driver signature enforcement (windows 8 only)
• connect MXQ to PC with USB - microUSB cable
• put a toothpick in A/V port (you'll find a switch) and press power button at the same time
• after some seconds windows will detect the device (you can leave the power button now)
• start AMLogic USB burning tool and set English language
• Press "File" -> "import image" and choose the .img file you downloaded before
• wait for the operation to complete

Thank you ilgimmy, I really appreciate you replying and providing links with instructions... I will give this a shot before trying the SSH method, however I do also appreciate the reply from pigbait.

Thanks again both

ace

[mbramwel]

What type of cable is required to plug the MXQ into a PC? A standard USB cable will not work, wrong connector.
I do not have a micro usb port on the MXQ.

[citizenjc]

Installed on SD version 5.0.8.18 on my two devices. Here are my finds. In Mk808b+ all is working very well, WiFi, bluetooth, and a 10$ usb 3.0 - ethernet adapter. The other devices is more problematic: it is a (beelink ???) ubox s805 I bought from gearbest, and the internal ethernet and bluetooth doesn't work; wifi is working...

Sorry to "inject" myself into the thread with a quote on a week old post, but I was looking around for info about the ubox and found this. Would this be too hard to fix? On another thread it's pointed out that the ubox and mxq are exactly the same, but apparently it's not the case. Thanks in advance.

[clarkss12]

If you are referring to the BeeLink ubox, that is a Rockchip SoC. This thread is about the Amlogic S805 SoC.

[minoccio]

The Ubox S805 is not rockchip, but Amlogic S805 SOC device

[ilgimmy]

Thank you ilgimmy, I really appreciate you replying and providing links with instructions... I will give this a shot before trying the SSH method, however I do also appreciate the reply from pigbait.

Thanks again both

ace

You're welcome, I did the same procedure to go back from 110k4 to 109k4 and it worked well.
You will find more info and videos on the net.

[citizenjc]

If you are referring to the BeeLink ubox, that is a Rockchip SoC. This thread is about the Amlogic S805 SoC.

You had me confused there for a while, but it's the S805 Ubox, like minoccio said, and it's apparently made by the same factory, nexteon.

[clarkss12]

The Ubox S805 is not rockchip, but Amlogic S805 SOC device

Do you have a link for that box? I wish they would change the names of the devices, it gets very confusing.

[kszaq]

As per usual, great work guys, OpenELEC working fine on my MXQ, though, I wanted to ask, any way to get the remote that comes with it to have a few more commands? as a number of buttons dont work/do anything, could these be made to work/do something using the keymap file for xbmc?

Thanks

Karl

karl0ss You can add keycodes in remote.conf file to make additional buttons work.

Hi, first of all big thanks for OP for his work on this, OpenELEC is awesome. I have just one question/issue - I'm using a couple of troublesome plugins which tend to freeze Kodi from time to time - this is not an OpenELEC issue, they do the same on all other platforms I'm running Kodi on - Win, iPad, Apple TV etc. So once Kodi freezes on my OpenELEC powered HD18Q box the only way to restart it is either to plug the power off or to kill Kodi via SSH. I know that on some OpenELEC setups there's a way to bind a "/bin/killall -9 kodi.bin &" command to a remote key, using lircrc and irexec. As far as I understand these builds don't support lirc and make use of amremote remote.conf instead. So my question is this: is there a way to bind a key of the native remote to a system command using remote.conf?

treyparker You may edit keycodes assigned to keys by modifying remote.conf file, I think you may be able to bind a command to a keycode.

kszaq, ok I'll try the hd18q build to see if remote works, then I'll wait for next build thanks again

So I have loaded my box with the latest HD18Q build and my remote is still the same... It wont work till i load my andriod remote.config, and once I do the same buttons cant be mapped.... I dont know if I can provide you with any useful logs if so let me know.... if you don't have time for this I fully understand this is all done on your spare time... I wish I knew how I could be more helpful to you.

pigbait You need to login over SSH, issue a cat /proc/kmsg command, press a button that doesn't work and note down anything that appeared in the kernel log. That way you can see what keycodes are not mapped or mapped improperly. If you note down a "key name"->"kernel log message" table, I may be able to help you correct the mappings.

Figured it out the screen resolution of the MXQ SD installation will be affected by Android settings. Whatever was set in Android will be fixed in OpenElec.

mickr It is true if your box does not detect your TV's EDID. In that situation, you won't be allowed to change resolution and OpenELEC will use resolution reported by uBoot.

kszaq - Android TV stick noob here. I recently bought Tronsmart MK808b Plus from GeekBuying. it came with 110k4 rom which i had it upgraded to 111k4 stock rom from Tronsmart. I am mainly using my TV stick as a media center (mostly playing media files from local network), I am very much interested in trying out your OpenElec version. Being a complete noob in this, I have few queries for which if possible you kindly clarify.

Is it possible to run your OS from a SD card without erasing the TV stick's default Rom in NAND (kinda dual-boot)?

Does your OS has working WiFi connection for ap6210 or ap6212 chipsets (not sure which one is there in my stick) of MK808b Plus sticks?

Finally, will an 8 GB Class 4 SD card suffice for this operation or do i need a larger capacity, high speed SD card?

That's it. Looking forward to your suggestions.

Thanks for your time!

mebaali Yes to all questions. You can find instructions on GitHub page. The only thing that is modified when you install SD version is uboot which can be easily reverted to stock when you re-flash Android.

Installed on SD version 5.0.8.18 on my two devices. Here are my finds. In Mk808b+ all is working very well, WiFi, bluetooth, and a 10$ usb 3.0 - ethernet adapter. The other devices is more problematic: it is a (beelink ???) ubox s805 I bought from gearbest, and the internal ethernet and bluetooth doesn't work; wifi is working...

Sorry to "inject" myself into the thread with a quote on a week old post, but I was looking around for info about the ubox and found this. Would this be too hard to fix? On another thread it's pointed out that the ubox and mxq are exactly the same, but apparently it's not the case. Thanks in advance.

minoccio citizenjc I would need a working Android firmware for that box to look whether the device trees for MXQ and UBox are the same or different.

[mebaali]

kszaq - Thank you so much for the clarification

[pigbait]

kszaq I will make the list of unmapped buttons once OE 6.0 is out, thanks.