[ROM][RK3066/RK3188][SD/HD] Factory firmware - share place link with all

[ensy3k]

Car Keys Dont Work

Hello,

i have update my Pumpkin Navigaton with update_5_1_1_FUSE_1024X600_RK3188 Everything works beautifully.
One problem I have, the steering wheel control does not work. I can not also prove someone has information or tip?

Thanks.

 

[typos1]

Hello,

i have update my Pumpkin Navigaton with update_5_1_1_FUSE_1024X600_RK3188 Everything works beautifully.
One problem I have, the steering wheel control does not work. I can not also prove someone has information or tip?

Thanks.

Not yet, there seems to be a problem with some units and SWC on later versions of L. Malaysk doesnt seem to be around at the moment, I can only suggest you monitor this thread :

http://forum.xda-developers.com/and...p-mtcb-units-tested-courtessy-t3389906/page98

to keep up to date with things.

 

[ensy3k]

My friend have the same Firmware and same Radio he have the 800x and Im have the 1024 Resolution.
From my friend the Keys works... cant understand this Problem!

 

[typos1]

My friend have the same Firmware and same Radio he have the 800x and Im have the 1024 Resolution.
From my friend the Keys works... cant understand this Problem!

Yes it does seem strange.

 

[tariqkhan.co.uk]

I have a 800x480 Quad Core RK3188 MTCB-KLD1-V2.77 Eonon system.

I have a couple of questions if anyone can help (preferably typos1 as you seem to have a lot of knowledge)?

Based on what was written in the OP, I can update my system to any MCU as long as it matches MTCB/QuadCore and the resolution 800x480. After reading posts in other threads, I think I can also update to MTCC? With all that in mind which is the best MCU to use? A link would be great, but happy to find that myself if you could let me know which is the best you have used and with the least amount of problems. If something is not broken, then I don't like to try fixing it and so if changing the MCU does not enhance my system I would rather leave it alone. But updating to a higher version should be safe... so if there is a higher version than 2.77, I would really appreciate a link.

Thanks

 

[typos1]

I have a 800x480 Quad Core RK3188 MTCB-KLD1-V2.77 Eonon system.

I have a couple of questions if anyone can help (preferably typos1 as you seem to have a lot of knowledge)?

Based on what was written in the OP, I can update my system to any MCU as long as it matches MTCB/QuadCore and the resolution 800x480. After reading posts in other threads, I think I can also update to MTCC? With all that in mind which is the best MCU to use? A link would be great, but happy to find that myself if you could let me know which is the best you have used and with the least amount of problems. If something is not broken, then I don't like to try fixing it and so if changing the MCU does not enhance my system I would rather leave it alone. But updating to a higher version should be safe... so if there is a higher version than 2.77, I would really appreciate a link.

Thanks

Youre mixing ROMs and MCUs a little - you can update your system to any ROM as long as it matches QuadCore and the resolution 800x480., not any MCU. You can only use KLD MCUs as you have a KLD unit.

Because you have a late KLD MCU version you MAY be able to update your it to MTCC KLD6 v2.91 and turn your unit into an MTCC unit, it is on the fileserver in my signature in firmware/mcus.

Try it, make a note of your tuner type in factory settings and after updating check it is has not changed, also check all other settings in factory settings are as they were before the update. If everything works then great you can run an MTCC ROM (or an MTCB ROM if you want).

If things do not work and you cannot get them working, then you will have to use @dsa8310's mod (see the "Lollipop for MTCB/MTCC head units" thread to use an MTCC ROM.

Having said all that this thread is for Malaysk's ROMs and I think so far all his are MTCB based, so if you want to use his, just try the MTCC MCU and dont worry about the rest. Personally I would at least attmept updating the MCU, if it works you will get minor radio improvements, if it doesnt just reflash your original MCU.

 

[tariqkhan.co.uk]

Thanks for the quick reply typos1, didnt expect you to be so fast!

Thanks for clarifying the mixup; KLD it is then. I have a KLD1, but I don't think this is a late KLD as I bought it sometime ago. It used to be a KLD1 less than version 2.55, but I upgraded to 2.77. I didn't think you can update from KLD1 to a KLD6? Never dared to either as I didn't want to risk bricking my system. The radio improvements would be good if it enhances the reception, even slightly (it is not that bad in my opinion). I did take screenshot of all the factory settings so no concerns there.


I am currently using @dsa8310's mod; don't really like the launcher much and the video player no longer works in the background. When playing music videos and if I then move to the navigation app the video stop playing. I converted from listening to mp3 audio to mp4 videos sometime back and don't fancy acquiring audio files for all the music videos I listen to.

Didn't realise this thread is for Malaysk's ROMs only. I've been using DSA's ROMS for a couple of years now as they are close to factory, with the changes most needed like increased partitions size, but the ROM you mentioned is not as fast as v4.4.4. Quite like the new version so have not been tempted to downgrade.
With regards to "I would at least attmept updating the MCU" to KLD6, what is the worst that could happen if things were to go wrong?

Really appreciate the response by the way.

 

[typos1]

Thanks for the quick reply typos1, didnt expect you to be so fast!

Thanks for clarifying the mixup; KLD it is then. I have a KLD1, but I don't think this is a late KLD as I bought it sometime ago. It used to be a KLD1 less than version 2.55, but I upgraded to 2.77. I didn't think you can update from KLD1 to a KLD6? Never dared to either as I didn't want to risk bricking my system. The radio improvements would be good if it enhances the reception, even slightly (it is not that bad in my opinion). I did take screenshot of all the factory settings so no concerns there.

I am currently using @dsa8310's mod; don't really like the launcher much and the video player no longer works in the background. When playing music videos and if I then move to the navigation app the video stop playing. I converted from listening to mp3 audio to mp4 videos sometime back and don't fancy acquiring audio files for all the music videos I listen to.

Didn't realise this thread is for Malaysk's ROMs only. I've been using DSA's ROMS for a couple of years now as they are close to factory, with the changes most needed like increased partitions size, but the ROM you mentioned is not as fast as v4.4.4. Quite like the new version so have not been tempted to downgrade.
With regards to "I would at least attmept updating the MCU" to KLD6, what is the worst that could happen if things were to go wrong?

Really appreciate the response by the way.

No probs.

TBH I have never heard of KLD1, only KLD then KLD2 - 6. The worst that can happen if you upgrade your MCU is that some things wont work, like radio or wifi, if this happens you just go back to your previous MCU. Its worth trying. One thing to do is to make sure you know what tuner type your unit has as after the new MCU is flashed you have to go into factory settings and re check the RDS box, re set radio to Europe and reset the radio IC.

It did used to be so that if you have a numbered MCU you should only update to a numbered MCU that matches yours (only KLD2 MCUs if you have a KLD2 for instance), but many people have recently found that this is not the case - my unit was a MTCB KLD 2.78 and then I upgraded to MTCB KLD6 v2.85 and from there I went to an MTCC KLD6 v2.91. Each time I upgraded I got improvements to the radio.

You can change the launcher (I like the Roxio one as you can remove/re-locate the MTC widgets). Personally I listen to .flac files for all my music because they are full quality, lossless files, not lossy like mp3s, mp4s, aac etc, so I ve never tried to listen to videos in the background while driving - did the previous dsa versions do this because you did a mod or was it always like that ?

"The ROM I mentioned" - do you mean dsa's latest L ROM ? Cos I find L a little faster than KK.

Actually I was wrong - this thread is not for Malaysk ROMs its his thread for factory firmware. This thread :

http://forum.xda-developers.com/and...lollipop-mtcb-units-tested-courtessy-t3389906

is for Lollipop and @dsa8310's ROMs, (careful, it gets a little heated at times )

 

[tariqkhan.co.uk]

Great, I'll upgrade to MTCB KLD6 v2.85 and let you know how it goes.
I've got to build up the confidence to upgrade to MTCC KLD6 v2.91 as I really don't want anything to go wrong it being a different type of MCU.

I've just installed Car Launcher Pro v1.5.1 and I have to say... I'm impressed. Is it worth using root to remove old launcher for a performance gain if any or does removing the original launcher cause problems?

The previous dsa versions did this and the stock version played videos in the background also, so don't know whats to blame here as I installed an old version of the MTCMovie app and no joy.

 

[typos1]

Great, I'll upgrade to MTCB KLD6 v2.85 and let you know how it goes.
I've got to build up the confidence to upgrade to MTCC KLD6 v2.91 as I really don't want anything to go wrong it being a different type of MCU.

I've just installed Car Launcher Pro v1.5.1 and I have to say... I'm impressed. Is it worth using root to remove old launcher for a performance gain if any or does removing the original launcher cause problems?

The previous dsa versions did this and the stock version played videos in the background also, so don't know whats to blame here as I installed an old version of the MTCMovie app and no joy.

Lol, ok, theres really nothing to worry about with the MCU - if some functions break you just reflash another one, I ve done it loads.

Its ok to keep the original launcher.

As for video, post in the forum I linked to earlier and @dsa8310 may be able to help you.

 

[tariqkhan.co.uk]

Lol, ok, theres really nothing to worry about with the MCU - if some functions break you just reflash another one, I ve done it loads.

Its ok to keep the original launcher.

As for video, post in the forum I linked to earlier and @dsa8310 may be able to help you.

Hey typos1, so I did what you recommended and flashed my system with MTCC KLD6 v2.91 and it works :good:

What I did notice though is that the system button colours (element in settings) are not as they should be. I selected RGB in factory settings as that is what it originally was set to, but when selecting the blue colour, the button lights up as red, and selected red it lights up as blue. It's like RGB switched to BGR. Not a big deal though.

Sound quality seems to me as though it is a lot better; it sounds a little more crisp. I prefer the new Radio App and the signal quality does seem a little improved, but still not as good as standard systems (it is not as bad for me as some people have reported).

I reflashed DSA Lollipop ROM in post #873 or similar, but still wont play videos in the background. The only thing I'm missing really.

 

[tariqkhan.co.uk]

Hey typos1, so I did what you recommended and flashed my system with MTCC KLD6 v2.91 and it works :good:

What I did notice though is that the system button colours (element in settings) are not as they should be. I selected RGB in factory settings as that is what it originally was set to, but when selecting the blue colour, the button lights up as red, and selected red it lights up as blue. It's like RGB switched to BGR. Not a big deal though.

Sound quality seems to me as though it is a lot better; it sounds a little more crisp. I prefer the new Radio App and the signal quality does seem a little improved, but still not as good as standard systems (it is not as bad for me as some people have reported).

I reflashed DSA Lollipop ROM in post #873 or similar, but still wont play videos in the background. The only thing I'm missing really.

Videos are now playing in the background again and now that I have been running this for a while... the wifi connection is a lot more reliable!!! I tether of my phone so this was a long term annoyance till now.

This may be the ROM and not the MCU, but sometimes while video is playing in the background, after the video is finished it does not move on to the next track (clicking next fixes this so not a big deal) and sometime coming back to the video it displays the video player but no video even though it is playing. Again clicking next fixes this.

Overall, a lot happier with my system.

 

[Goaz]

typos1 I've noted that you often suggest people to update their MCU, the MCU should not be updated unless "strictly reccomended", if the head-units are properly running with their default MCU there is no need at all to updated MCU imho.
Before updating any MCU new users should try to firsty get some confidence with updating of firmware procedures, so basically it is highly reccomended to just update the ROM and not the MCU.
Furthermore as you know the MCU is only needed to control the head-unit buttons/lights/hardware so I would initially onyl update the ROM, test it, see if it does run smoothly, then eventually update the MCU alone.
As many old users posted many times, flashing of a wrong MCU could brick the unit!!

just my 2 cents :>

---------- Post added at 03:22 PM ---------- Previous post was at 03:16 PM ----------

tariqkhan.co.uk if I were you I'd stick back with your original MCU version, you don't know if in a long term the wrong MCU could baddly affect your unit.

 

[typos1]

typos1 I've noted that you often suggest people to update their MCU, the MCU should not be updated unless "strictly reccomended", if the head-units are properly running with their default MCU there is no need at all to updated MCU imho.
Before updating any MCU new users should try to firsty get some confidence with updating of firmware procedures, so basically it is highly reccomended to just update the ROM and not the MCU.
Furthermore as you know the MCU is only needed to control the head-unit buttons/lights/hardware so I would initially onyl update the ROM, test it, see if it does run smoothly, then eventually update the MCU alone.
As many old users posted many times, flashing of a wrong MCU could brick the unit!!

just my 2 cents :>

tariqkhan.co.uk if I were you I'd stick back with your original MCU version, you don't know if in a long term the wrong MCU could baddly affect your unit.

Sorry, but are totally incorrect for a variety of reasons.

Firstly flashing the wrong MCU will not brick your unit, all it does is make some stuff not work and you can easily flash the correct MCU.

The list of people updating their MCUs successfully is massive.

Often, flashing a ROM can stop some stuff on your unit working and flashing the MCU will get them working again.

New MCUs often have new features that you would not be able to use if you dont flash a more up to date MCU (shut down delay, updating the unit to an MTCC unit that can take MTCC ROMs are 2 examples).

The MCU controls much more than the buttons and lights, it controls wifi, the radio, BT all sorts of stuff.

Flashing an MCU is so simple and easy, if you need to "get some confidence with updating firmware" then you probably shouldnt own a smart device such as this.

Some old users did have some problems with updating MCUs 2 years ago, but that was 2 years ago, our knowledge of them is rather better now.

I speak with over 2 years experience of these units, having owned 3 of them and with thanks related to helping people with them of over 400.

As @tariqkhan.co.uk said in his post above - hew updated his MCU and its working fine.

If you dont want to update your MCU, fine, but please dont try and put others off doing a useful upgrade.

 

[pa.ko]

Sorry, but are totally incorrect for a variety of reasons.

Firstly flashing the wrong MCU will not brick your unit, all it does is make some stuff not work and you can easily flash the correct MCU.

The list of people updating their MCUs successfully is massive.

Often, flashing a ROM can stop some stuff on your unit working and flashing the MCU will get them working again.

New MCUs often have new features that you would not be able to use if you dont flash a more up to date MCU (shut down delay, updating the unit to an MTCC unit that can take MTCC ROMs are 2 examples).

The MCU controls much more than the buttons and lights, it controls wifi, the radio, BT all sorts of stuff.

Flashing an MCU is so simple and easy, if you need to "get some confidence with updating firmware" then you probably shouldnt own a smart device such as this.

Some old users did have some problems with updating MCUs 2 years ago, but that was 2 years ago, our knowledge of them is rather better now.

I speak with over 2 years experience of these units, having owned 3 of them and with thanks related to helping people with them of over 400.

As @tariqkhan.co.uk said in his post above - hew updated his MCU and its working fine.

If you dont want to update your MCU, fine, but please dont try and put others off doing a useful upgrade.

+1 on that

I'll add that there is always a possibility that something changes among mcu versions but generally newer ones have improvements. For example on KGL units somewhere between 2.5x and 2.7x the buttons lighting stopped to follow headlights - on earlier units they were off with lights off but on later they are always on regardless of headlights (and it is not related to settings!). But in the same time radio reception, quality of sound and number of stations found is improved in later versions after 2.8x. so yes something was lost and so.ething us gained, and I have impression the later ones are bit more stable and better in main functional areas.

There is no risk of making any permanent damage, even if flashing wrong MCU type. Of course learn first how to reconfigure your original MCU if anything goes wrong.

So I would also suggest to give a chance to latest MCU. With major notice! After flashing MCU always perform Factory settings reconfiguration like this:

Create empty mcu.cfg file on the GPS sd card root
Flash from recovery together after mcu.img update
(empty mcu.cfg forces MCU to reset it's internal cinfiguration which may resolve all kind of problems believe me)
Reconfigure your MCU from Factory settings (write down your original settings and really them after reset)

That way you have 'factory' clean mcu of latest version. Test and if you are not satisfied with new vs lost features / behaviours, you may always return to your good old one.

For me, new one resolved issue with poor radio reception which I was sure is caused by bad antenna but after upgrade it is proven to be mcu issues - better tuning of receiver circuitry parameters enabled better s/n gain which resulted in much beter sound quality, less noise and much more station s detected / reception on longer dustance.

 

[Luv-Kush]

Anyone have the latest factory ROM 4.4.4 for MTCB rk3188 1024*600. Seen ZD but that is 800*480. Also if I can install 800 on 1024 will be OK. Thanks

Sent from my A0001 using XDA-Developers mobile app

 

[Oldpapa49]

+1 on that

I'll add that there is always a possibility that something changes among mcu versions but generally newer ones have improvements. For example on KGL units somewhere between 2.5x and 2.7x the buttons lighting stopped to follow headlights - on earlier units they were off with lights off but on later they are always on regardless of headlights (and it is not related to settings!). But in the same time radio reception, quality of sound and number of stations found is improved in later versions after 2.8x. so yes something was lost and so.ething us gained, and I have impression the later ones are bit more stable and better in main functional areas.

There is no risk of making any permanent damage, even if flashing wrong MCU type. Of course learn first how to reconfigure your original MCU if anything goes wrong.

So I would also suggest to give a chance to latest MCU. With major notice! After flashing MCU always perform Factory settings reconfiguration like this:

Create empty mcu.cfg file on the GPS sd card root
Flash from recovery together after mcu.img update
(empty mcu.cfg forces MCU to reset it's internal cinfiguration which may resolve all kind of problems believe me)
Reconfigure your MCU from Factory settings (write down your original settings and really them after reset)

That way you have 'factory' clean mcu of latest version. Test and if you are not satisfied with new vs lost features / behaviours, you may always return to your good old one.

For me, new one resolved issue with poor radio reception which I was sure is caused by bad antenna but after upgrade it is proven to be mcu issues - better tuning of receiver circuitry parameters enabled better s/n gain which resulted in much beter sound quality, less noise and much more station s detected / reception on longer dustance.

As Gabby Johnson said.. (Blazzing Saddles) I have updated my KLD6 MCU from V2.81 (none available to return too) to V2.91 (before V2.97 came along), but my CanBus decided to go bad. Was working for sometime.
I'm now on V2.97 so far. I did RECORD my settings from the Factory. I tend to do stuff like this. And set the newer MCU's to what I had and set stuff that looks newer to active or not.
Radio now has DSA's latest rom and the V2.97.
My CanBus decoder just sends Delay ACC (parallels the cars ACC line) and Illumination control. Nothing from my radio talks to it at all. The CanBus says Ford Explorer, I have a Ford Freestyle.
My Steering wheel is decaded serial, nothing tied to CanBus.
I did fix my CanBus, as I seem to know some electronics. Guess over 55 years of it..

 

[typos1]

Anyone have the latest factory ROM 4.4.4 for MTCB rk3188 1024*600. Seen ZD but that is 800*480. Also if I can install 800 on 1024 will be OK. Thanks

Sent from my A0001 using XDA-Developers mobile app

Factory (and custom) ROMs are on @darkales's fileserver in my signature.

As Gabby Johnson said.. (Blazzing Saddles) I have updated my KLD6 MCU from V2.81 (none available to return too) to V2.91 (before V2.97 came along), but my CanBus decided to go bad. Was working for sometime.
I'm now on V2.97 so far. I did RECORD my settings from the Factory. I tend to do stuff like this. And set the newer MCU's to what I had and set stuff that looks newer to active or not.
Radio now has DSA's latest rom and the V2.97.
My CanBus decoder just sends Delay ACC (parallels the cars ACC line) and Illumination control. Nothing from my radio talks to it at all. The CanBus says Ford Explorer, I have a Ford Freestyle.
My Steering wheel is decaded serial, nothing tied to CanBus.
I did fix my CanBus, as I seem to know some electronics. Guess over 55 years of it..

Actually, you went from MTCB KLD6 v2.81 to MTCC KLD6 v2.91, so you upgraded from an MTCB MCU to an MTCC one.

I found when going from MTCC KLD6 v2.91 to v2.97 I didnt have to save settings - the settings were kept, unlike the last 3 MCU upgrades where they were reset.

Your ll probably find that the Explorer and Freestyle share the same CAN Bus system.

 

[tariqkhan.co.uk]

typos1 I've noted that you often suggest people to update their MCU, the MCU should not be updated unless "strictly reccomended", if the head-units are properly running with their default MCU there is no need at all to updated MCU imho.
Before updating any MCU new users should try to firsty get some confidence with updating of firmware procedures, so basically it is highly reccomended to just update the ROM and not the MCU.
Furthermore as you know the MCU is only needed to control the head-unit buttons/lights/hardware so I would initially onyl update the ROM, test it, see if it does run smoothly, then eventually update the MCU alone.
As many old users posted many times, flashing of a wrong MCU could brick the unit!!

just my 2 cents :>

---------- Post added at 03:22 PM ---------- Previous post was at 03:16 PM ----------

tariqkhan.co.uk if I were you I'd stick back with your original MCU version, you don't know if in a long term the wrong MCU could baddly affect your unit.

Updating the MCU improved radio and wifi. There is no way I would revert back to the older MCU so agree with what @typos1 and others have said.
@typos1 So I updated my MCU to version MTCC KLD6 v2.91 as advised previously and everything is working fine other than the reversed RGB lighting.

Is it worth updating the MCU again to MTCC KLD6 v2.97 or is it too early to highlight improvements/issues? I'm presuming you have uploaded to the server as listed in your signature.

 

[Goaz]

+1 on that

I'll add that there is always a possibility that something changes among mcu versions but generally newer ones have improvements. For example on KGL units somewhere between 2.5x and 2.7x the buttons lighting stopped to follow headlights - on earlier units they were off with lights off but on later they are always on regardless of headlights (and it is not related to settings!). But in the same time radio reception, quality of sound and number of stations found is improved in later versions after 2.8x. so yes something was lost and so.ething us gained, and I have impression the later ones are bit more stable and better in main functional areas.

There is no risk of making any permanent damage, even if flashing wrong MCU type. Of course learn first how to reconfigure your original MCU if anything goes wrong.

So I would also suggest to give a chance to latest MCU. With major notice! After flashing MCU always perform Factory settings reconfiguration like this:

Create empty mcu.cfg file on the GPS sd card root
Flash from recovery together after mcu.img update
(empty mcu.cfg forces MCU to reset it's internal cinfiguration which may resolve all kind of problems believe me)
Reconfigure your MCU from Factory settings (write down your original settings and really them after reset)

That way you have 'factory' clean mcu of latest version. Test and if you are not satisfied with new vs lost features / behaviours, you may always return to your good old one.

For me, new one resolved issue with poor radio reception which I was sure is caused by bad antenna but after upgrade it is proven to be mcu issues - better tuning of receiver circuitry parameters enabled better s/n gain which resulted in much beter sound quality, less noise and much more station s detected / reception on longer dustance.

Everyone's claiming/stating that newer MCU=better performances, do any of you have ever read a changelog file of these new MCU?No, because these file logs simply do not exist so your statements are based on personal impression only.