Try downloading the file again and formatting the flash drive to fat32. Or your device has a different way of changing the resolution, contact your dealer, they may advise.
this method does not work for me, fortunetly i managed to make it work by holding 5 fingers on the screen and that way worked. thanks for the help. also i changed my mcu to GS instead of HXD. i removed the mismatch error with the proper app
Now that everything works, save the settings to the dmcu.cfg file and save it to the external storage, in case of problems with it, you can return everything. Factory setting / export. You will find the file in the root of the device.
Compiled list of MCUs for MTCD from 4pda.ru- the website is in Russian.
Exact version numbers of each MCU is currently unknown; only the release date was provided.
These MCUs are for MTCDs with RK3188 CPUs, compatibility with the newer MTCD with Intel x86 CPU is untested.
What is the MCU? MCU stands for Microcontroller Unit- wiki. The MCU acts as the bridge between the hardware on the head unit and the android system. This allows for special interactions between the vehicle and the head unit that would otherwise be impossible through Android. For example, backup camera view can be activated even if the android operating system hasn't finished booting up. However, the nature of the setup inherently includes a major drawback because the MCU is proprietary. This means software relating to the MCU can only be updated by the specific manufacturer/seller of the head unit. Any problems or bugs in the MCU are unlikely to be fixed unless the manufacturer releases an update- i.e. the bluetooth problem. This thread serves to help remedy this issue by consolidating the scarce amount of information available on MCUs and to build on related community efforts. There has been some progress on modifying the MCU for MTCBs in the XDA and 4PDA forums by kumarai, darkleo, and Dark Simpson. No progress in modifying the MCU has been made for MTCD.
How to find your specific MCU? On your MTCD head unit, go to the 3rd line under "MCU Version" in Settings > About. In the image below, the MCU is "KGL".
This image was taken from a MTCB thread, don't worry if the other specifications are different because your unit is MTCD- not MTCB.
Only use MCU that matches your MTCD head unit's MCU or risk malfunction! Update at your own risk!
Again, dmcu.img files are not interchangeable like dupdate.img files regardless if your head unit is MTCD or MTCB/C! It would be greatly appreciated if you can post feedback after updating your MCU.
List of Updated MCUs:
KSP (CUSP?)
Accessing Recovery: Press and hold the volume dial until the head unit LEDs flash 3 times. Then immediately release and press the dial 1 time.
Factory Settings Password: 121212 or m123456
JY (Joying) JY_9-27-2016_dmcu.img (version 1.90)
Changelog:
-5 second delay shut down (fixes "shutting down" message when starting engine if android is already booted)
-Sub-woofer control added
-"Fixed some bugs." (from Joying's website)
Update Instructions
In order to flash the updated MCU, you must rename the downloaded "*.img" to "dmcu.img" then place it in the root directory of your SD Card or USB drive.
Insert the medium into your head unit then access your its recovery and choose to update and wipe- it's the same process with dupdate.img files.
If the provided MCU is zipped with "dmcu.ext" and/or "dmcu.cfg" files, include them in the same root directory as your "dmcu.img" file and flash in recovery.
If you have ANY additional information or older/newer MCU .img files, please post here.
Thread will be updated regularly as relevant information is posted.
For those who are looking for updates for their MX/MX2 MCU:
Attached are four MCU updates for MX and MX2 MCUs. The MTCE_MX2_V2.87 update is very new (dated June 7).