How to Install Openelec on MXQ Pro+ Dual Boot Via SD Card

I received a lot of help from people when I decided to install openELEC on my MXQ Pro+. The install method is via a dual boot method. OE is run via SD Card, while Android remains when the SD Card is removed. The original link is here: Openelec for Tronsmart Vega S95 - Instructions for Openelec
FYI, I also installed Tronsmart firmware on this box which resolves lots of issues with the firmware that came with the generic S905 2/16 gig boxes. Check this link: SD ROBOTS mxq pro plus firmware link. - FreakTab.com
You can reference all of the posts there and there is lots of great help. I needed lots of help, so after resolving problems and getting OE installed and working I decided to post installation instructions for Dummy's (me). Note that OE is very resource friendly, a much simpler version of KODI. It runs extremely well and you will probably see a lot of the issues with Android KODI disappear.
I will apologize now if the links don't work Copy/paste might be needed.

How to Install Openelec on MXQ Pro+ Dual Boot Via SD Card
Step 1 – Installing Dual Boot capability on MXQ Pro+

• Format your SD/SDHC card using FAT 32. Its recommended that you use a good formatter for this purpose, SD Formatter - https://www.sdcard.org/downloads/for.../eula_windows/
• Go to this site: https://yadi.sk/d/gZW-PXc7qU4v7
• Download the file at the bottom called update_uboot.7z
• Extract the file and you should see two files within the extract - aml_autoscript and aml_autoscript.zip
• Copy/paste or extract aml_autoscript and aml_autoscript.zip to the formatted SD Card
• Boot your MXQ Pro+ box to Android, insert the SD card containing the files (aml_autoscript and aml_autoscript.zip). Open Apps and then Update and Backup, Under the Local section click select, locate aml_autoscript.zip click it and select update. Your box will reboot. You won't notice much and it will reboot to Android.
• The process can take some time, so be patient. A few minutes is all it takes.
• That is all for step one. u-boot should now have been modified and dual boot enabled.
• The SD Card can be used for step 2.

Step 2 – Creating an openELEC Boot SD Card

• It is recommended that Windows users use Win32DiskImager to format your SD Card for this step.
  • https://www.sdcard.org/downloads/for.../eula_windows/
  • Download and install SD Formatter
• Open this link - https://yadi.sk/d/gZW-PXc7qU4v7/Openelec
  • Download this file - meta_openelec_v20160419.img.7z
• Extract this file - meta_openelec_v20160419.img.7z onto your computer. The name will be the same with .img as the extension
• Create a bootable SD Card using Win32DiskImager
• Format your SD Card again with SD Formatter, or your chosen formatter, use FAT 32.
• Run WIN32DiskImager. Locate your file and the location of the SD Card you inserted. Select write.
• You can open the SD Card and check it. You should see 4 files, SYSTEM, dtb.img, kernel.img and S905_autoscript
• Shut down your MXQ Pro+ - I pulled the plug. Insert the SD Card into the box. Reboot the box.
• Within a few minutes openELEC should boot into the setup screen.
• After 5 or so minutes of failing to boot, try a reboot on the same card a couple of more times before trying a card reader or different card. It has taken me as many as three attempts to get to OE on first boot. As you have seen, once past the first boot, OE boots very quickly, runs very well (thanks RISKy Dude).
• If it doesn't boot after several attempts, try using a USB card reader and/or a different SD Card.
• If problems persist, got to this post for help: http://freaktab.com/forum/tv-player-...ega-s95/page12
• If you want to update to openELEC 6.9.5.3.its pretty simple. Go to https://yadi.sk/d/gZW-PXc7qU4v7/Openelec, look for the 20160504 folder and open it and the next. Download dtb.img, kernel.img and SYSTEM. When downloaded you can then copy and paste these onto your openELEC boot SD Card. Then reboot the box and you should be updated to OE 6.95.3.0.
  • Do not do this with the devel.7 folder contents.

My thanks go to all who helped me when I had problems, including scooter1214, RISKy Dude, Trebor, kanacnik1 and to balbes150 who wrote the awesome scripts.