Any mods viewing can hopefully change ALL forum titles to read "MTCB/MTCC" Headunits.
The new MTCD units have apparently proved "unreliable" and so at least one manufacturer (Klyde) have decided to continue selling MTCB units, with updated MCU software renamed "MTCC".
These "MTCC" MCUs are fully working on some MTCB units, although not all. So far only MTCC KLD6 v2.91 (MTCC version numbers start at v2.91, not v1.00) have been released and tested, no non numbered MTCC MCUs have been found yet
The hardware is exactly the same as MTCB units, only the software is different.
The latest KLD L ROMs look for a "C" at the end of the MCU name and if its not there will not work properly. MTCC MCUs are only for Klyde versions, later KLD 5.1.1 ROM updates ONLY work with MTCC KLD MCUs and the last version of MTCB (MTCB KLD6 v2.85), not all KLD units work with these 2 MCUs, if youve tried it and yours doesnt work or you have a non KLD unit, theres a way around it that uses Xposed to change the final MCU letter to "C" :
http://forum.xda-developers.com/showpost.php?p=68416382&postcount=810
Great info. So I can install on my MTCB with MCU KLD6 a MTCC KLD6 MCU?
Oberbergler said:
Great info. So I can install on my MTCB with MCU KLD6 a MTCC KLD6 MCU?
Click to expand...
Click to collapse
I was running KLD6 2.86 and it worked fine on mine, but it didnt work on someone elses running a non numbered KLD MCU.
Try it, if it doesnt work just go back to KLD6 2.86.
Oberbergler said:
Great info. So I can install on my MTCB with MCU KLD6 a MTCC KLD6 MCU?
Click to expand...
Click to collapse
I installed MTCC KLD6 v2.91 on a MTCB KLD unit and it works great. I think i get better radio reception if that makes any sense. Does MCU has anything to do with radio?
tolymatev said:
I installed MTCC KLD6 v2.91 on a MTCB KLD unit and it works great. I think i get better radio reception if that makes any sense. Does MCU has anything to do with radio?
Click to expand...
Click to collapse
Good to hear.
Yes it does, sometimes after a ROM update the radio stops working and the MCU needs to be updated to fix it. My unit had a KLD v2.81 and after updating to L the radio stopped working completely, only updating the MCU to KLD6 v2.86 made it work, even though previous advice was only to flash KLD6 MCUs on units that had KLD6 from the factory. Updating to MTCC KLD6 MCU deffo made the radio work better for me too.
Exactly what MCU version were you on before ?
Does this mean that pumpkin kld rockchips rk3066 have been officially been updated to lollipop? The strange thing is that my kld rk3066 runs fine on kld2 mcu up to kld6. The system sound, (when the buttons are pressed on the system) sounds different from the original beep when pressing buttons. Also, wlhere can I find the newest official update for pumpkin kld rk3066?
alexn1978 said:
Does this mean that pumpkin kld rockchips rk3066 have been officially been updated to lollipop? The strange thing is that my kld rk3066 runs fine on kld2 mcu up to kld6. The system sound, (when the buttons are pressed on the system) sounds different from the original beep when pressing buttons. Also, wlhere can I find the newest official update for pumpkin kld rk3066?
Click to expand...
Click to collapse
No, RK3066 wont be getting Lollipop, but you can update the MCU, I also noticed that the "beep" is different with later MCUs.
Thank you for the reply. Is there any benefits updating to the new mcu. I was reading previous posts that the radio sounds better. Anything else besides that?
alexn1978 said:
Thank you for the reply. Is there any benefits updating to the new mcu. I was reading previous posts that the radio sounds better. Anything else besides that?
Click to expand...
Click to collapse
Dunno, try it and see.
I updated my KLD RK3066 2.78 mcu to KLD6 2.91 and the radio stopped working. I tried each radio chip and still nothing. Flashing back to 2.78 restored the radio.
lmattiso said:
I updated my KLD RK3066 2.78 mcu to KLD6 2.91 and the radio stopped working. I tried each radio chip and still nothing. Flashing back to 2.78 restored the radio.
Click to expand...
Click to collapse
Yes, this has happened to someone else as well, it may work if a non numbered MTCC KLD MCU becomes available. Are you running Lollipop ?
typos1 said:
Yes, this has happened to someone else as well, it may work if a non numbered MTCC KLD MCU becomes available. Are you running Lollipop ?
Click to expand...
Click to collapse
No, I've got a RK3066 running 4.4.4. I saw that you had said in your earlier message that you upgraded from KLD 2.81 to KLD6 2.86 and it works (Lollipop though). I couldn't find a KLD 2.81 rom, just KLD2 2.81. Was that a mistake or did you actually use KLD 2.81?
lmattiso said:
No, I've got a RK3066 running 4.4.4. I saw that you had said in your earlier message that you upgraded from KLD 2.81 to KLD6 2.86 and it works (Lollipop though). I couldn't find a KLD 2.81 rom, just KLD2 2.81. Was that a mistake or did you actually use KLD 2.81?
Click to expand...
Click to collapse
Theres no such thing as a "KLD v2.81 ROM" - the ROM and MCU are separate.
You can try other KLD numbered MCUs and see if they work.
Cant be sure exactly the number of the KLD non numbered MCU I was on previously (probably the latest version I could find of a non numbered MCU, but its not really that relevant.
typos1 said:
Yes, this has happened to someone else as well, it may work if a non numbered MTCC KLD MCU becomes available. Are you running Lollipop ?
Click to expand...
Click to collapse
typos1 said:
Theres no such thing as a "KLD v2.81 ROM" - the ROM and MCU are separate.
You can try other KLD numbered MCUs and see if they work.
Cant be sure exactly the number of the KLD non numbered MCU I was on previously (probably the latest version I could find of a non numbered MCU, but its not really that relevant.
Click to expand...
Click to collapse
I meant MCU ROM, not the Android OS ROM. As long as you were on a non-numbered MCU, that is what's relevant. I just wanted to confirm. Either there was a newer MCU file out there that I couldn't find or the 2.81 was the KLD2 MCU file that you used. I can't upgrade to Lollipop on my 3066 so I'll just be happy with my 2.78 MCU until they release a non-numbered KLD MTCC update hopefully. Was hoping for a radio upgrade but I don't use it much anyway. Thanks for the info.
lmattiso said:
I meant MCU ROM, not the Android OS ROM. As long as you were on a non-numbered MCU, that is what's relevant. I just wanted to confirm. Either there was a newer MCU file out there that I couldn't find or the 2.81 was the KLD2 MCU file that you used. I can't upgrade to Lollipop on my 3066 so I'll just be happy with my 2.78 MCU until they release a non-numbered KLD MTCC update hopefully. Was hoping for a radio upgrade but I don't use it much anyway. Thanks for the info.
Click to expand...
Click to collapse
I d just try all KLD MCUs that are later than yours and see if any gie more features/work properly etc.
Generally in the forum MCU firmware is referred to as "MCU" and Android as "ROM".
I also updated my KLD2 2.77 to KLD6 2.91 with TDA7786 tuner and it is working fine. RDS is working too that never worked before whatever MCU i had tesetd
Billkaza said:
I also updated my KLD2 2.77 to KLD6 2.91 with TDA7786 tuner and it is working fine. RDS is working too that never worked before whatever MCU i had tesetd
Click to expand...
Click to collapse
Cool !
typos1 said:
Cool !
Click to expand...
Click to collapse
Typos1, ok, so KLD6 is the MCU (thats what I have on my Pumpkin)
V2.81 is what it says, a version number. So a higher version won't cause issues?
I always thought the V2.81 was pretty important, but now I see KLD6 is the one that is the one. Doh.. Version are improvements and the KLD6 is what is base.
Basically what I do with my software, I do not change the ports, but make coding better.. faster.. etc.
You should of been here when I was going through Chemo. After about 2 weeks when done, I looked at the software and wondered what I did..
Guess gettin old.
Oldpapa49 said:
Typos1, ok, so KLD6 is the MCU (thats what I have on my Pumpkin)
V2.81 is what it says, a version number. So a higher version won't cause issues?
I always thought the V2.81 was pretty important, but now I see KLD6 is the one that is the one. Doh.. Version are improvements and the KLD6 is what is base.
Basically what I do with my software, I do not change the ports, but make coding better.. faster.. etc.
You should of been here when I was going through Chemo. After about 2 weeks when done, I looked at the software and wondered what I did..
Guess gettin old.
Click to expand...
Click to collapse
A higher version is more up to date, if you have an MTCB or MTCC MCU you should be able to update to MTCC KLD6 v.2.91, going by the 3 people who have done so so far.
The "KLD" bit is also important, if you have a KGL MCU you CANT update to MTCC KLD6 at all.
Hi does anybody have a link to MTCC KLD6 v.2.91 please I have looked for it and I can't find it.
Related
I am an unhappy user of the 5.0.2 ROM and I am planning to downgrade to the original 4.4.4. Which ROM is the right form my phone?
My current 5.0.2 config is:
My Baseband version is:
MSM8626BP_1032.3105.93.00R EMEA_DSDS_CUST
My kernel version is:
3.4.42-g48d3b85
My system version is
22.21.28.titan_retaildsds.retaildsdsall.en.03 reteu
Build number
LXB22.46-28
I bought the phone in Greece.
It would be great if we collect info to build a map of what stock ROMs are out there, and for what regions.
kostas2010 said:
I am an unhappy user of the 5.0.2 ROM and I am planning to downgrade to the original 4.4.4. Which ROM is the right form my phone?
My current 5.0.2 config is:
My Baseband version is:
MSM8626BP_1032.3105.93.00R EMEA_DSDS_CUST
My kernel version is:
3.4.42-g48d3b85
My system version is
22.21.28.titan_retaildsds.retaildsdsall.en.03 reteu
Build number
LXB22.46-28
I bought the phone in Greece.
It would be great if we collect info to build a map of what stock ROMs are out there, and for what regions.
Click to expand...
Click to collapse
What model of phone is it? XT...?
Have a look at this tool for reverting to stock 4.4.4
Duck86 said:
What model of phone is it? XT...?
Have a look at this tool for reverting to stock 4.4.4
Click to expand...
Click to collapse
It is a XT1068. Thanks for the link.
kostas2010 said:
It is a XT1068. Thanks for the link.
Click to expand...
Click to collapse
I checked the link but found no reference for reteu. I see many posts of how to downgrade but very few of them actually mention the region. I have seen so far at least three regional labels: retin for India, retus for US and reteu for EU.
What I am hoping for is to revert my phone to the EXACT state it was when I bought it, which means it hsould also be able to receive OTA updates if needed. I am wondering if this is possible.
kostas2010 said:
I checked the link but found no reference for reteu. I see many posts of how to downgrade but very few of them actually mention the region. I have seen so far at least three regional labels: retin for India, retus for US and reteu for EU.
What I am hoping for is to revert my phone to the EXACT state it was when I bought it, which means it hsould also be able to receive OTA updates if needed. I am wondering if this is possible.
Click to expand...
Click to collapse
There is no reteu. At least not for download. Since your baseband is dsds, just go with the dsdsall version.
http://motofirmware.center/files/file/945-retaildsdsall-xt1068-444-kxb2185-14-cid7-cfc-svcxmlzip/
I have a tricky question:
How can I find out the actual, REAL hardware model I have? D5803 or D5833? When I check Settings-->About phone-->Model number, I get D5833, but I don't know if this setting shows the ACTUAL device model, or the flashed ROM's. Does anybody know? In case it's the ROM's, how can I find out the real hardware model I have? (Before you tell: I threw away the box and invoice long ago.)
Background: A few months ago I flashed a prerooted 5833 ROM (working fine, so far). However, since both 5803 and 5833 ROMs are virtually interchangeable and can be flashed to both models, the problem is now I don't remember if I flashed the version matching my actual model. (Back then, I just wanted to get the latest pre-rooted and didn't care much about matching versions.)
Thank you in advance. (I hope this is not double posting: I've searched the forums but haven't found an answer to this particular.)
zogoibi said:
I have a tricky question:
How can I find out the actual, REAL hardware model I have? D5803 or D5833? When I check Settings-->About phone-->Model number, I get D5833, but I don't know if this setting shows the ACTUAL device model, or the flashed ROM's. Does anybody know? In case it's the ROM's, how can I find out the real hardware model I have? (Before you tell: I threw away the box and invoice long ago.)
Background: A few months ago I flashed a prerooted 5833 ROM (working fine, so far). However, since both 5803 and 5833 ROMs are virtually interchangeable and can be flashed to both models, the problem is now I don't remember if I flashed the version matching my actual model. (Back then, I just wanted to get the latest pre-rooted and didn't care much about matching versions.)
Thank you in advance. (I hope this is not double posting: I've searched the forums but haven't found an answer to this particular.)
Click to expand...
Click to collapse
It shouldn't make any difference, the difference between the models is to do with the 4G bands available to the phone. If the 4G is working then you probably have the right model.
Why not use Xperiafirm to find the correct firmware for your country/provider, then download the firmware and use Flashtool to create a tft, then flash just the baseband. That will give you the correct modem, regardless of what build you have on the phone, and won't change the rom in any way.
Thank you @Didgesteve for your answer. I know what you mean (and I already did that). But my question remains:
How do I find which of the two existing Z3 Compact models am I holding in my hand?
I'd rather not engage in debating the baseband or ROM differences. The fact is: both models, D5833 and D5803, aren't identical; and I want to know which one is mine.
Never mind my country. I bought it second hand and I can't know exactly where was it bought. The information in the "About phone" settings only tells the flashed ROM, but not the supporting hardware.
My guess is, perhaps only the serial number may have that information embedded. But how do I get the model out of the serial number?
Anybody?
Thank you.
zogoibi said:
But how do I get the model out of the serial number?
Anybody?
Thank you.
Click to expand...
Click to collapse
If you open the flap where you put the sim in, look closely under the sim slot is a thin piece of plastic, you might need tweezers to pull it out.
Printed on that is the model number and serial number and a european CE mark
Excellent! That worked. Thanks a lot. I guess I'll try to label this as solved.
Hi
I bought this unit and wanted to install the malaysk rom but don't know what is this version.
is it real pumpkin? fake one?
at the boot, the logo says "fineyea"
http://www.fineyea.com/
how can i know the MCU and other information?
photo added.
Hello,
I just bought the same unit and am also confused by the MCU as it doesn't follow the naming scheme that is usually mentioned here.
Does anyone have more information what firmware might be compatible?
Hi everyone, I just replaced the car radio I had before, version 5.1. with a model 7.1 that mounts MTCE_HA_V2.71_1 PX3 (1024X600 0) 2GB RAM. Anyone can tell me where I can find the stock rom with these features, before I flash a new rom, since I still have the car radio as a guarantee? I apologize if this 3d is maybe open in the wrong section, maybe you can move it, thank you.
Hmmmm, MCTE.... That's a new one, as far as I'm aware.
There are reviews for the 3.57 MCU ?
Hello friends.
Hi have follow your hard work a long time ago and I have 2 questions
I have a eonon that actually is a MTCD_KBT_V2. 05_2 unit that i upgrade from RK3188 with 1 giga of ram to RK3066 with 4 gigas of ram and Android 6.
1° Can i upgrade the mcu version if yes can you please forward the link because i can't found it.
2° Can i upgrade to android 8 Hal9k rom i have md725 bluetooth type 2.
I have read that bluetooth type 2 won't work but this problem affects all type 2 bluetooth cards?
Some pictures to help
Thank in advance for all your work and attention.
Best regards Rui Serpa from Portugal
New Android board RK3066 4 gigas of ram.
I have order this bluetooth card from AliExpress to change my hold one.
Can someone confirm if i can do this.
serpa1982 said:
I have order this bluetooth card from AliExpress to change my hold one.
Can someone confirm if i can do this.
Click to expand...
Click to collapse
I mounted and works
Ok job done.
Android 8 Hal9k version ( Great rom) [url]https://forum.xda-developers.com/android-auto/mtcd-software-development/rom-hal9k-rom-3-mtcd-e-head-units-t3847477[/URL]
MCU update to: MTCD_KBT_2.41SP I tried other verison but no Radio staion found. [url]https://forum.xda-developers.com/attachment.php?attachmentid=4554974&d=1532195453[/URL]
Bluetooth chip update to: Type 1