All MTCB and MTCC ROMs by the DEVs and Mods

[Oldpapa49]

Ok, I decided that we need to collect the different ROMs made by the DEVs and sort them into 1 place.

What I like to do here is to try to explain the different ROMs Kit Kat and Lollipop by Malaysk, ###8310 and Booroondook.
And while we now know that MCU's need to stay via KLD, KLD2, KLD6 etc, you can upgrade within those parameters with only changing factory settings (KLD6-V2.83 to KLD6-V2.97 is ok)
I have played with these roms and follow an certain rule.. Before you go from Factory to a custom rom, take pictures of settings and factory settings.
Don't update unless you are sure you know how to revert back. Know what buttons to push. Know what screen resolution your unit is! All those minor points.

All the roms we are talking about look like a filename as "update.img". 4.4.4 and 5.1.1 all for MTCB and MTCC are called out this way. I do believe MTCD is something different (dupdate.img ???)
MCU for MTCB and MTCC are "mcu.img".. and are found on the file servers as KLD?-V2.?? .. sub your version (others are available)
The fileserver can be found under typos1 name on most posts. I will link it soon.
I would suggest you read his very informative wiki as well.

Malaysk (MTCB 4.4.4 and 5.1.1) is probably the most popular ROM here. He and like the other DEVs make the ROMs to their liking's. They will on occasion add suggestions to the ROM image if they think it is beneficial.
Malaysk and ###8310 (MTCB to MTCC fake out via xPosed does a reboot once to complete loading) will have 2 files to chose from which are for resolutions. 800x480 and 1024x600. Choosing the wrong one will make the your display look awkward. (reason to know how to get back into recovery if you make this mistake)
Booroondook has a setup that creates the resolution size, thus 1 file to get and run and answer questions.

Bloatware may be added to customize roms. The reason they are customized.. Right Even factory roms have it, don't like it.. well...

So little memory, so many apps.. 1g, 2g.. well Malaysk does the FUSE trick which opens up the full memory. Booroondook, I don't recall, maybe maybe not. ###8310 has it set to 3g right now I think, but I think there might be choice of default.
Malaysk has customized Launchers. JY5.1.1 typically (one other too)has a speed display on his 4.4.4 and 5.1.1 roms
Booroondook has a few and DSA8310 is mostly clean and factory based (Klyde)
###8310 uses what factory firmware uses. The Windows like and some other with the old time flip card time piece.

You may install the rom image via MicroSD card (plugs normally into the GPS slot) or the USB port 0 (Normally the Mini port front plug thingy behind the door)
If you have update.img with mcu.img, both will get programmed to the device.
If you are going from factory to any rom, you should do the wipe data/factory cache option after the rom is flashed. You can do this anytime after the reboot. And the 1st reboot takes a long time.

If you go from and DEVs rom to another, do the data/factory cache wipe option as well, in fact you can do this anytime you update.

Stopping here since at work and will edit and add later. This is the start.
##8310, Typos1 and others, I like input..
If you had a problem and fixed it, let me know
Hands Free Messaging
If you want to hear and reply to messages on your radio from your cell, get the app from Google Playstore readitotme and install on your phone

Under Profiles: Make sure you link it as "CAR KIT" and enable it
And set to BT Mono
If you want voice reply, enable that (you get 2 weeks free) and you'll need to download addition app

It will automatically use your Messages app on the phone for the app. So under the Apps, do not enable it.
But you can select additional apps and how you like to hear them Header, message etc
Under Contacts, you can also what to hear.. One area has ALL, so selecting anything under that will enable ALL contacts with that feature.
Other features and more stuff are listed, but this should work fine.

 

[Oldpapa49]

Adding Launchers from 5.1.1
5.1.1 update.img:
Both Malaysk and Booroondook load their images with a few launchers. If a launcher is in their ROM image, you can grab it from the image by using a program called "RK3xxx Firmware tools" (google it)
Simply load the update.img via the tool (select Img... box) , extract it (Extract under Firmware image tools), then extract again under System.img tools.
Then "Open folder..."
Locate folder "priv-app"
Find the launcher you like (Launcher2mtc3_5_1_1) example
copy to a USB flash drive
Some launchers use weather on their screen, so grab the weather one too folder "app" (MTCWeather) and copy to the USB Flash drive
take the flash drive and reverse the procedure.
To copy from the USB flash drive to the system, look for "mnt" in root of the device. Find the usb drives and locate your drive.
Copy the MTCWeather to "app" (this will make it appear in the apps folder) and set permission to 755 for folder and the apk in the folder 644 using Root Explorer
Copy the (Launcher2mtc3_5_1_1) launcher to "priv-app" folder and set permission to 755 for the folder and the apk in the folder to 644
Reboot

I have been trying to get the JY5.1.1 speedo to work.. ran out of time.. WIP

 

[Oldpapa49]

Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)

Radio had MAL 5.1.1 800x Aug file.
Fuse vs Standard RAM

1st: Flashed MCU from V2.97 to V2.91
2nd: Flash Factory ROM.
Reboot had issue,
3rd: Did a Data/Factory Cache and Wipe..
4th: Flash Factory ROM again.
5th: System rebooted to Factory Images

Results are that V2.91 and Factory 5.1.1 works fine. Will be adding apps and place JY5.1.1 launcher soon. (Can't, no root!)
The settings retained Factory settings
The About Device says MTCC -KLD6-V2.91 5.1.1 800x480
Its all good from MTCB

 

[eblackie]

Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)

Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...

Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?

 

[Oldpapa49]

Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...

Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?

MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image.
I use to have KLD6-V2.81, Pumpkin told me they had a newer one and it is KLD6-V2.91. I have installed KLD6's 2.83, 2.85. 2.91, 2.95 (I think) and 2.97
Just remember to get your FACTORY Settings recorded. so you can set the right info.

MCU file are not attached to any ROMs by any Dev.
Dev roms are rooted and they supply a remap apk for keys. I have never used it.
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1. But make sure you have all the info settings in factory, Very important!

I'm just a basic person and like certain things... So I look and set my HU to my likings.
I change my ROM evrytime a DEV makes a change to tests. I'm on MALs latest 4.4.4 ..
Note: I rarely use radio, I use Sirius App. Radio signals stink where I live.

 

[eblackie]

MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image. *i did*
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1.
I'm just a basic person and like certain things... *so am i*

Thanks for this detailed answer! As i know now i can step back to 4.4.4 i will give it a try, maybe things are a bit faster then.... i also read in a Xposed thread, dsa8310 plans something about resoldering bigger RAM's, sounds interesting! Maybe i can find one who can do this for me and take away the laggyness, but first i want to do this Sound-Chip-Mod which looks easy to do, as this unit here has only poor sound and settings to offer... If the device survives, i will play around with the rk3xxx_firmware_tools

 

[dhmsjs]

MCUs are improvements...
Just remember to get your FACTORY Settings recorded. so you can set the right info.
... But make sure you have all the info settings in factory, Very important!

Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.

So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.

Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).

2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).

Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.

 

[pa.ko]

Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.

So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.

Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).

2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).

Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.

Ina cases of issues with/after loading mcu.cfg (problems, incomparibility,...) you may reset my to default (factory default / clear) state by creating empty mcu.cfg (don't forget to check permissions)

Empty MCU.cfg forces MCU to reinitialise ... At least Russians are saying so, in some previous MCU vers, I didn't check in code for myself

Truck with empty MCU.cfg reset us better than reglazing my as reglazing is not overriding that particular memory area of config params

 

[Oldpapa49]

Call Home...

Ok, I have tried this on 4.4.4 and 5.1 (both roms)
1. Works better on 5.1 and not 4.4.4. It seems to crash google using 4.4.4 unless I did something incorrect.
2. You need to get the mtcservice (headunit 2.34 or 2.35) to make it function. I tried the one off playstore and I just don't really know about it.

When you use the mic to call the 1st time, make sure you select 'mtcsevice' (steering wheel icon) to make calls. It should complete after.