yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] typos1:
Actually no, I m having more problems - the screen always reverts back to 1024x600 resolution after rebooting, even though I ve flashed an mcu.ext file. Radio just will not work. I tried flashing the original MLT MCU and I get the "version unmatch" error . . . but in recovery - the MLT MCU will not flash like normal, instead of flashing straight away it goes to recovery and and says its flashing MLT customer version then says "version unmatch" and will not flash it. I managed to successfully flash a GS MCU and I hoped the problem would go away, but it still wont flash the MCU and has the version unmatch message in recovery. And the radio still doesnt work with the GS MCU.

I cant find anywhere in that thread about how to change the tuner type in factory settings and unlike MTCB/C units theres just a yes/no option for radio (MTCB/C units have a drop down list where you can choose from 5 or 6 tuner types), strange really when you consider that the MTCB/C units have a less intelligent 8bit MCU compared to the 32bit MCUs on MTCD/E devices. Anyway its seems my problem (and anyone else that has the non working radio issue) could be that the manufacturers of the units whos MCU weve flashed our units (HA and GS in my case) use a different tuner than the manufacturers of our units (MLT in my case) and thats why the radio doesnt work and the MCU only contains code for one radio tuner, this is my theory. But because we cant just go into factory settings and look, we cant tell what tuners our units use . . . I guess we could use dmesg as you say in your tuner post to find out what radio tuner we have ? If so would I be able to see what tuner this MLT has by using dmesg even though its not working/possibly has the code for a different MCU ? Or would I need to find someone with an MLT unit with working tuner and ask them to use dmesg to find out what tuner MLT units use ? If my theory is correct we could compile a list of which units use which tuners and then advise that people only use MCUs from manufactures who use the same radio tuners as their unit.

Some units have a dual wifi/BT chip, with 2 antenna points but only one antenna, have you looked inside ? Soldering an extra antenna could solve your problem.

The screen blank button is a Klyde thing, they also use it on their MTCB/C units, like you its a feature I like but also like you I also wish it didnt turn the screen back on when you press the volume up/down keys ! But, at least with MTCB/C units, factory Klyde ROMs and Klyde based custom ROMs also have the feature even if flashed on non Klyde devices. So, you could try a Klyde RK3368/PX5 ROM (or maybe Malaysk's ROM if its Klyde based) with an HA MCU and see if you get the feature back.

Sorry, but youre wrong here - its been verified that the 4Gb units can be flashed with any RK3368/PX5 ROM.
[MTCD Android Head Units General] SkyBeam2048:
My KLD unit uses realtek combined radio. I have soldered antennas to both soldering points. Attahed 2x +9dBi 2.4/5GHz anyennas. Receptionis superb. Just not when both are used. I rather suspect a driver issue here.

This is exactly what I truied and what I reported not to work. I am running at stock KLD ROM. As soon as I flash HA or any other MCU I am losing the screen blanking feature.

This is why I stick to KLD MCU now.

I think you misunderstood. I did not say they cant be flashed technically. It was reported that Android 8 is using different partitioning and might require different tools. So if someone bought an Android 8 unit then just installing Android 6 on it might not work. Or, if the image changes the partition layout there is no way back to Android 8 at the moment. So I just poimted out that this might cause issues and likely is a one way street at the moment.

But somebody with a PX5 Android 8 unit might just try and report.
[MTCD Android Head Units General] typos1:
KLD are one of the biggest producers and update their MCUs regularly, usually with all the latest features, so theres no reason for you to use another MCU anyway really, using other MCUs is mainly for people who have a rare MCU or one that hasnt been updated for ages, or lacks features.

A dev should be able to change the partitioning layout, as [MENTION=5092263]Hal9k_[/MENTION] did to make Nougat work on 1Gb RK3188 devices.
[MTCD Android Head Units General] marchnz:
First try factory settings and from memory [customer version] change.

It sounds like the recovery is detecting mismatch and preventing downgrade/change. What ROMs have you tried to flash MCU with? Suggest trying latest MLT and also HA then GS. Would also suggest full powercycles by completely removing power to unit in between flashing.

Sorry I dont have definitive advice or suggestions here, its a matter of trial and error.

In future and thanks to another member (who wrote app to decrypt MCU file) I can now fully check MCU code with IDA. In hoping to learn disassembly and make modifications.
[MTCD Android Head Units General] marchnz:
Hi,

Re: [sdfirmware tools] - the PX3 tool doesnt work, hence my hardware mod - but - goodnews is that I have located a PX5 SDCARD create tool - see my new post in this forum.

Re. Radio/MCU - appears that the Android ROM contains radio device selection as can be seen from DMESG on HA/HCT firmware when I did the mod to change the radio module (sorry for giving incorrect advice re. chaning type in MCU.) If yours does not work, suggest that the android ROM is the issue, or the MCU cannot communicate with the radio mcu over I2c bus.

Would be great if we could get someone to dump PX5 Oreo, or HA provide an an upgrade image file, as the upgrade zip cannot be used by SDCARD create tool or OTG/Loader.

Cheers,

- M
[MTCD Android Head Units General] SacredDeviL666:
Thread cleaned.

Could we please stay on topic of this thread?

Thanks :highfive:
[MTCD Android Head Units General] typos1:
Yes, but your cleaning removed some stuff that was relevant to the discussion, why couldnt you just remove the stuff that you didnt like from the posts rather than the entire posts ?
[MTCD Android Head Units General] SkyBeam2048:
Hmm, can't find much relevant data which is lost. Can you be more specific or re-post it?

Looks like he mainly removed our pointless and stupid rants (yes, my one too).

I apologize for my inappropriate wording. It was not my intention to offend you in such a way. We don't agree on upgrade/downgrade ability of PX5/4GB/Android 8 SoM at this moment but fair enough as none of us owns such a device as of my knowledge.

I rather would like to focus on getting PX5/2GB units upgrade to Android 8. The discussion perhaps will continue here.

This thread is for MCU cross compatibility only and I think all relevant discussion is still here.
[MTCD Android Head Units General] typos1:
My theory re the radio tuners cant be right - you changed yours without changing the MCU and as youve mentioned its in the ROM, I guess some ROMs contain only the info for 1 radio tuner type.

For some reason in Lollipop recovery I cant press "ok" - I can move up and down but theres no "ok", I m gonna have to take teh unit apart and put in a SoM with Lollipopoin it, just to be able to downgrade the MCU.

I m guessing that Oreo recovery will be at least as advanced as Nougat, so in future I think the recovery is going to mostly prevent us from flashing a different MCU.

AFAIK know, no one one here has a n Oreo unit yet.
[MTCD Android Head Units General] SkyBeam2048:
Let me update you. In fact this is where all our misunderstandings started.

In Post #434 uer [MENTION=5101246]mum1989[/MENTION] pointed out he has an Android 8 PX5 unit on MTCD/E and asked for MCU upgrade compatiblity. Of course MCU is independent from ROM and therefore he can upgrade.

In Post #437 he also asked whether he can install Malaysk (Android 6).

As a reply to this I recommended not to do it as installation of Malaysk might break due to different partition layout or other issues. See my post #438.

In Post #445 you started correcting me:

I think here the misunderstanding started. Your statement is true for any PX5 2GB/4GB SoM with Android 6 shipped on it. But the discussion was based on someone owning an Android 8 board with different partition scheme where I still believe it's a risk to downgrade to Android 6 (Malaysk) as for sure re-upgrading to Android 8 would be impossible and even downgrading might brick the unit.

Soon we will likely have an option to flash Android 8 using recovery tools on any PX5 unit, but until then I am afraid Android 8 PX5 owners don't have options to up/downgrade right now.

I hope this clarifies some things. I am aware that the ROM-discussion went into completely wrong direction and even more is completely off-topic here.

MCU updates are independent from the SoM or ROM and therefore actually not to be discussed here.
[MTCD Android Head Units General] typos1:
[MENTION=4974080]marchnz[/MENTION] - its [MENTION=5101246]mum1989[/MENTION] that has an Oreo unit he has offered to try and dump the ROM.

---------- Post added at 02:37 PM ---------- Previous post was at 02:34 PM ----------

When I said that no one had Oreo yet I had simply forgotten about the earlier posts you just mentioned about the user with Oreo - I follow this thread so I am aware of the posts, they simply slipped my mind, so yes I can see where some of the mis-understadings between us started.

I dont think that Malaysk's ROM will brick an Oreo unit - I think it simply wont flash because of the different partition layout, just as Nougat ROMs wont flash on 1Gb RK3188 units without re-partitioning, although I understand why you suggest he doesnt try it.

Just for your information - RK3368/PX5s with 4Gb are deffinately a different revsion (4), this is no rumour, it has been confirmed - I have one and so do other members.

I am aware that Oreo is being worked on and I m also subscribed to [MENTION=4974080]marchnz[/MENTION]'s new thread. Myself, [MENTION=4974080]marchnz[/MENTION] and [MENTION=744370]ikerg[/MENTION] were one of the first to have a copy of the Oreo ROM, in discussion with these members it was decided that I should not try and flash it on a revision 4 SoM yet as [MENTION=4974080]marchnz[/MENTION] had the eperience in recovering Px5s with his modifed motherboard.

It remains to be seen if the revision 4 SoMs can flash Oreo without repartitioning, I very much doubt they can, or they surely would not be able to flash Marshmallow without repartitioning, but I do think its very unlikely that SoMs with Oreo are a further revision. Of course once Oreo has been re-partitioned upgrading and downgrading between MM and O will be possible.
[MTCD Android Head Units General] it00x32:
anyone knows what manufactor my device is

MTCE_TONE_V2.65f_1 ?

bought from here https://www.mic-autoradio.com/

regards
[MTCD Android Head Units General] typos1:
No, not heard of it before.
[MTCD Android Head Units General] karolp1993:
Hello. I've just upgraded my KD unit from PX3 to PX5. MCU Update from KD_1.95 to HA_2.65 done fine. It's just necessary to remap physical buttons in factory reset settings.

And for people like me who wondering how to export MCU settings - it can be done by factory settings menu :D
[MTCD Android Head Units General] montrelim:
I did install HA 2.7.1 MTCE on my HU. But I forgot to export the config before upgrade. Now I got "Version Unmatch-01" message. Can you send me the dmcu.cfg for KSP MTCD?

Thanks in advance.
[MTCD Android Head Units General] mum1989:
my MTCE Android 8.0 4Go ram :
[MTCD Android Head Units General] BlueVan:
Does anyone have a link to the GS_V2.76 MCU ?
[MTCD Android Head Units General] semcoinc:
Forgive me if this is in error being posted here, but I thought I would note in this thread that I just upgraded my MTCD KBT with upgraded PX5 4GB SoM with the HA V2.75, that was reported to be able to be used on a KBT unit by this post from [MENTION=8603573]abagos[/MENTION]

https://xdaforums.com/showpost.php?p=75498871&postcount=591

I used the HA 2.75 MCU update linked here

https://xdaforums.com/showpost.php?p=72622240&postcount=2

After flashing the dmcu.img to my unit all the front side buttons of the head unit were inoperative and had to be re-established in Factory Settings. This occurred despite placing a saved dmcu.cfg file in the same GPS card at the same time as the MCU dmcu.img file was flashed.

I got past the buttons issue but the bigger issue is that the radio has no reception whatsoever. Yes, the factory settings are correct for "America1" settings.

Has anyone seen this inoperative radio issue before in MCU updates?

Thanks,

Mike
[MTCD Android Head Units General] typos1:
You managed it then - I was just thinking that you might not be able to - I updated an MLT unit to HA as it said in teh first post that someone had successfully done it, but Iost the radio. I read the whole thread and another user also lost the radio going from MLT to HA. So then I tired a GS one, that also had a non working radio. then I tred to go back to MLT and Nougat and Lollipop recoveries would not let me - they were too "clever" - I got a version unmatch error from recovery and I could not flash any other MCU including the original MLT one. So I thought that this may mean that on units with MM up changing the MCU would not be possible. I had to use a SoM running Lollipop to flash the original MLT MCU.

It may be a question - if you cant find a later KBT MCU - of finding another manufacturer's MCU that works. On MTCB/C units you can select the radio tuner type in factory settings, I cant see why they removed that function on MTCD/E units.
[MTCD Android Head Units General] semcoinc:
Thankfully, I have a battery maintainer on board so I am able to plug in at night in my garage but extended inactivity in a public space could prove troublesome if the unit is never really shutting down.

The PX3 SoM with Lollipop 5.1 had up to a 2 hour shutdown option. This is the MCU that I restored.

Come to think of it, when I installed the PX5 SoM over the 5.1 MCU/PX3 is when I lost the shutdown option. So, does this suggest that the shutdown option is SoM related?????? To my logic it would see that this could be the case.

I will check tomorrow morning to see if there is a "hot" instant start or a cold boot after a night of power off.

I have noticed that my battery maintainer still turns green by the morning so the battery is brought to a top level of charge, so the maintainer is able to overpower any drain of the unit.

In a few days, when I get time, I may try the Android 6.0 upgrade dated 20180201.

Mike
[MTCD Android Head Units General] typos1:
Other people have had the problem with shut down on RK3368/PX5s, I think youd have to look in the HA thread or the general PX5 thread, if I remember correctly later MCUs sorted it.
[MTCD Android Head Units General] semcoinc:
After a full night's sleep, I started the vehicle this morning and received an instant start up. Not what I was hoping for since I thought my BMW control brain had an independent shutdown circuit for the head unit power connections.

So, I may run an experiment where I measure the battery voltage at the end of my driving day with a digital voltmeter and then measure again in the morning to see if there has been any appreciable drop so that I can get an idea of what level of difficulty I might be in for with an extended non-use without my battery maintainer.

Until such time as an MCU or ROM is identified that can give me the shutdown option.

Mike
[MTCD Android Head Units General] typos1:
Sorry if I ve asked before, but have you contacted your seller and asked for an MCU update ?
[MTCD Android Head Units General] semcoinc:
No, I don't think you've asked before.

But in January I did receive an MCU and ROM update for my original 5.1/PX3 system from the seller when I complained about the slow 1GB performance and it is dated 20170327. This is the KBT V2.42_1 MCU which does have a shutdown available of up to 2hrs.

This was my PX3 5.1 system running on [MENTION=5092263]Hal9k_[/MENTION] ROM V1.2 that was really awesome for a 1GB system. I loved that ROM and wish he would make one compatible with the PX5/6.0

I will check with the seller again but they sold me a PX3 5.1 system (which did have a shutdown menu feature) so I'm not sure anything they would give me would work with the PX5?

Mike
[MTCD Android Head Units General] typos1:
Did I soz !

The MCU is totally separate the processor, so, whatever MCU you use it will work (although you may have a problem if you used a very early MCU with Oreo).

There have been issues with the shut down delay menu not appearing on some RK3368/PX5 SoM/mobo combos, yours seems to be one of those. :(
[MTCD Android Head Units General] semcoinc:
Lucky me! :crying:

Mike
[MTCD Android Head Units General] catu:
I just flashed the GS 2.73 MCU, and included the cfg file from the op. I probably shouldnt have done that, because now my panel buttons are unresponsive. I had the inverted x asis problem, but managed to remap the touch screen. When i try to remap the panel buttons, they are unresponsive. Have I bricked it? It wortks perfectly, apart from no buttons. I have a version without any hardware buttons - just some on screen buttons at the bottom (Xtrons PB96MTVAPL)
[MTCD Android Head Units General] rstwingo:
Hello

I would like to know if you have an PX5 MTCD LM headunit and what type of MCU is compatible with it, and you can relax with it to work

Thank you in advance for your answers

* Toni
[MTCD Android Head Units General] ekduyan:
Hi guys i have thiş weird mcu that i can't find anywhere. It's WLGK and here is my settings screen. Can anybody help me ? :confused:
[MTCD Android Head Units General] typos1:
No, it has not been tried before, you will have to read the thread then try other MCUs.
[MTCD Android Head Units General] AudiA4B7:
xtrons D719AS

Android 7 on the radio. runs P3. at the moment I can?android 8 updating it enters an android 8 for the radio?
[MTCD Android Head Units General] jbleasdale:
I have a new 4GB Oreo HU running MTCE_XRC_V2.79k_1 and have problems with canbus for my VW (works for only a second or two on start-up then no more afterwards) and wonder whether this might be MCU related so considering trying another MCU.

I was considering installing a HA MCU (2.80 now available) and wondered whether:

1. Anyone has successfully installed a HA MCU on an XRC unit?

2. What happens if you install an incompatible MCU? How do you roll back?

Many thanks!
[MTCD Android Head Units General] typos1:
Have you tried other XRC MCUs ?

A search or read of this thread will answer your question about whether anyone has tried HA on XRC.
[MTCD Android Head Units General] marchnz:
JY / HA / GS re-validated. Went from MTCE HA to GS 2.78 and back to HA 2.80 without any issue, other than having to reconfigure factory settings.
[MTCD Android Head Units General] jbleasdale:
XRC MCU's seem to be very rare - very little mention on here.

Fortunately I have resolved my problem by using the old canbus adapter off my previous headunit.
[MTCD Android Head Units General] typos1:
I have 2.60 XRC if you wnat it.

Can you add to the first post that MLT - is not guaranteed to work ? I lost the radio on one and so did another user, so only a 33% success rate.
[MTCD Android Head Units General] marchnz:
Sorry to hear, will update post.
[MTCD Android Head Units General] marchnz:
What happened when you flashed it? If it's still running did you try latest updates?

I've seen references to 'mismatch' but never experienced them.
[MTCD Android Head Units General] typos1:
All the details are in the thread.

The radio didnt work as happened to another user, everything else did and no mismatch error.

So I tried some others including a GS one, then I couldnt go back to MLT cos everytime I tried, the Nougat recovery would report a mis-match error and not flash it. I had to change the SoM and use a SoM with Lollipop on it to be able to flash MLT again.

I think thats also something that you should add to the first post - changing MCUs may be a problem with Nougat on recoveries as theyre becoming too clever and wont flash MCUs if they spot a mis-match.
[MTCD Android Head Units General] typos1:
What version of Android does your unit have ?

I ask because MarshMallow and Nougat (and probably Oreo) have different, more intelligent recoveries that wont flash an MCU if they detect a mismatch error (as opposed to earlier recoveries that would flash the MCU then give the mismatch error afterwards). I had a similar problem (couldnt flash the correct MCU after getting mismatch errors) and my solution was to downgrade to Lollipop, re-flash the correct MCU and then go back to MM or N. If youve got an RK3368/PX5 then going to L wont be an option.
[MTCD Android Head Units General] rwgau:
I downloaded 5.1 ROM and will install it. Then re-update the MCU and report back. Thanks for the suggestion.
[MTCD Android Head Units General] fifthelement:
Hi guys, Currently I am on the 2.41 KD dmcu. unfortunately there is no newer KD dmcu and I want to try a cross compatible dmcu firmware. what is the latest dmcu which is compatible with KD ? I saw a 2.80 HA dmcu, do you think it would work ?
[MTCD Android Head Units General] typos1:
Read the first post and search the thread, if there is no mention of anyone trying another MCU on KD units then you will have to experiment yourself with other MCUs.
[MTCD Android Head Units General] gimc:
Hi typos1,

I have the same problem with MCU MLT unit as you (screen resolution and radio), but i don´t find MLT dmcu.img. Who can I download it? At the moment I use Lollipop.

Thank you.
[MTCD Android Head Units General] gimc:
Finally I have found an MLT dmcu.img, but cann't install it. I have tried from recovery Lollipop with SD. But no luck. Maybe I buy a PX5 mcu.
[MTCD Android Head Units General] fifthelement:
I successfully installed HA 2.80 on a KD head-unit. although I had provided the dmcu.cfg but it was not restored and I had to reprogram the steering wheel keys and front panel. everything is working fine :)
[MTCD Android Head Units General] markgeary:
Hi,

I think i have the same problem. Just upgraded from 6.0 to 8.0 and without realising i used a HotAudio 8.0 image. I have a Xtron GS unit.

All was working well (except bluetooth) and i had read that upgrading the MCU could solve the bluetooth issue. I therefore flashed the latest HA MCU 2.80 - which flashed fine. (I also thought it was cross compatible?)

I now get the mismatched error... The unit will no longer let me flash any other MCU's other than a HA ones.

I am wondering if i need to flash a rom that is GS compatible in order to flash a GS MCU file??

Its really annoying as after i have set the button maps - everything is working fine except the mis-match sign at the bottom of the screen. If only you could force flash a dmcu.img file via adb?? Or just turn the sign off as everything is working!!

If anyone has any ideas - please let me know.

Thanks
[MTCD Android Head Units General] typos1:
A PX5 wont help - MCUs are the same for all MTCD/E processors, there no such thing as a "PX5 MCU".

Have you got a link to this MCU ?

What error did you get when it didnt flash ?

All ROMs are compatible with all MCUs and you have successfully flashed a different MCU which is also noneither of these things are the problem I was describing in the post you quoted, you have totally not understood that post !

And it appears that you have not read this thread either ! - The problem you are getting is to be expected after flashing an MCU from a different manufacturer, just read the thread to find how to solve it.
[MTCD Android Head Units General] gimc:
I cann't read the error, because with the wrong screen resolution the line is under the readble field. But I can flash succesfully any version of HA (i have tried 2.80, 2.52, 2.40).

The MLT version I unknow what version is. I have try to share the link, but at this moment I cann't (must write more posts to prevent spam on this forum).

I have this problem since two weeks, and searching a lot of time. Only this MLT firmware found. The original version was MLT V1.61a_1.
[MTCD Android Head Units General] fifthelement:
Have you tried to flash mcu through recovery ?
[MTCD Android Head Units General] gimc:
Sorry for my bad english, I would mean PX5 SoM.