[Android Head-Units] danngrigore:
Hi guys and thanks for giving me the opportunity to share my experience here of my four days and four nights of hard work to make my head unit to work in proper mode and to have the Tomtom working.

First of all I want to thanks to MALAYSK for his big and invaluable work for making me and maybe many others happy of having a powerful piece of technology working as it is meant to work.

Secondly I want to THANKS to every person from here that gave me an even small hint that helped me to achieve my task which was apparently a very difficult and risky task for me, trying to make my (not cheap) device to work properly.

I will try, based on my long and tiring experience, to be as clear and tidy as possible, to help even those not very experienced in writing custom software on their devices, to make them working properly.

I want to warn everybody that everything they will do based on my experience, they will do it on their own risk and I will not be responsible for anything gets wrong to their devices. I will be very sorry for this but nothing more. I will try my best to be very clear and to give as detailed instructions as possible to make you happy :o. I will mention on every procedure to follow if I am SURE or I BELIEVE that the procedure or action works on EVERY similar device with mine.

So lets go!

1. (I BELIEVE) This procedure works on every MTCD device no matter what brand it is based on RK3188 platform (can be checked in ABOUT section of you device settings)

2. (SURE) This procedure work perfect on my device called PF7539BA made by XTRONS for BMW X5, E39 or in my case Range Rover L322 Vogue 2002-2005. They are many other devices made by Xtrons or JoYing based on the same platform.

3. (SURE) The list of materials and files you need to make it done are:

- SD card formatted in windows (FAT 32) minimum 4Gb in size

- Two files called dupdate.img and dmcu.img. (IBELIEVE) These files are called the same no matter what brand is the device made by. The files can be found on the manufacturer website on FIRMWARE UPDATE section. For example XTRONS has on their website allocated on almost every device this section if the device is updatable. Find your device and download this files on your computer first. (http://www.xtrons.co.uk). I recommend to make a folder for original firmware and another folder for custom files that you will download from here!:silly: If the files are in archive format, unarchive them. So in the ORIGINAL FIRMWARE folder created by you on your computer you will have two files: dupdate.img and dmcu.img. They are many MCU device types so please be vary careful not using other than the one is yours. For more informations check this http://xdaforums.com/android-auto/mtcd-discussion-questions-development/comprehensive-updated-mcu-list-mtcd-t3476880. Even the dmcu file on this website is newer than yours I encourage you to use the one downloaded from the manufacturer website.

- Now download the newest dupdate.img file from here (Thanks to MALAYSK!!!) http://huifei.fs-fileserver.de/content/firmware/MTCD%20CUSTOM%20ROMS%20ONLY%20NOT%20FOR%20MTCB%20/RK3188/ and unzip it into the CUSTOM FIRMWARE folder also created by you on your computer.

- Write the file called dmcu.img (ORIGINAL) and dupdate.img (CUSTOM) on the SD CARD

- Put the card into the GPS slot of your device

- Next step is uncertain for me because I do not know if all devices have the same button combination for getting into RECOVERY MODE. I will give the way of doing my device. If does not work please do some research about how to get into your device's RECOVERY MODE. So first thing make sure the device is on and has the button lights on. PRESS POWER button until the button lights flash few times and when they stop flashing (3 to 4 times will flash) release the POWER button and press it again for one second and release it. At this point the device after few seconds will get into recovery mode. It must look like this picture (ignore the error messages at the bottom. I have used this picture from internet as example)

[IMG="Ignore yellow error messages"]https://i.ytimg.com/vi/P0zCzFRwDMs/maxresdefault.jpg[/IMG]

-Press once at a time the power button until you get to the third position called "update system/mcu image from sdcard and clear all". At this point press long the POWER button until the device starts checking the files on sdcard. It will take some time doing the firmware writing. If the flashing procedure was fine, it will reboot and say ERASING and after that will reboot and start as normal the booting process. DO NOT LET IT FINNISH booting as it will not boot properly but do the previous procedure again to get into the RECOVERY MODE again. Once there go to the sixth option called "wipe all data/factory and cache reset" and press long the POWER button until it execute it. The cache clearing will start and after this will reboot normally.

If everything worked well you will get after few minutes into the DESKTOP of the device having a ROOTED and working almost perfect your device!!:highfive:

I want to mention that some of the application are not the same as your original ones but this ones are working and looking better! The custom firmware is based on Lollipop 5.1.1 !!! I do not know if does work on the ones loaded with KitKat.

For those who want to have the (bloody) TOMTOM working you have to install and activate (put check mark on in after installation) the mtcservice-2.28.apk application in XPOSED FRAMEWORK page application which is already installed on your device. Get this https://docs.google.com/uc?export=download&id=0B9YiDhcSP2veZkhMOGQ2T0FNU0U and install. Reboot. Start Xposed manager and go to module and check this application. Reboot. Now you can download TOMTOM from here https://docs.google.com/uc?export=download&id=0B9YiDhcSP2vebzVyT2p0NnhDc1k and install. make sure you have internet on device when starting Tomtom as it will need it for map downloading.

Based on my research and experience this is all I've done to my device and I have a good working device and working (bloody) TomTom. :silly:

Enjoy!!