yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] chaveiro:
What is the cause of "version unmatched" ?

It checks MCU with what?

I've not touched mcu and it started after aplying a vendor update on my PX6.

MTCE is LY 3.56 tryied updating to 3.65

Previous android 10 from 2020 now on gs16_rk3399_10.0_ota(20220517) px6.zip
[MTCD Android Head Units General] crienz90:
Hi, I have unfortunately changed the DEFAULT POWER STATUS setting of my PX5 for Ford Focus 2012 to OFF from the factory settings, now the device no longer turns on, I have carried out updates without success, I desperately need the dmcu.cfg file which you can obtain by entering settings from the factory and exporting the configuration, can anyone share it with me? I will be grateful to you
[MTCD Android Head Units General] Pavel-71:
If you have a DVD drive, try inserting the disc, when it starts up, immediately change the default state of the power to ON, or it remembers the last state. If someone gives you a dmcu.cfg, it must be from the same device with the same MCU and extension, which determines the customer's version, otherwise other errors may occur. It is best to try to write to the seller, maybe he has this file. Or at least post your MCU and customer version, preferably if you have screenshots and photos of the unit, maybe someone will respond.
[MTCD Android Head Units General] FMode:
Please help me identify this unit!

For me it is an LM with 3.01c version.

which you will find here:

MTCD

Посмотреть и скачать с Яндекс Диска

disk.yandex.ru

I was able to break the readout protection of the STM32F091VCT6 with the known STM32 security hole. 🥳

And this is my test unit.

Problem: the readout memory is not 100% the file from the server.

Any ideas?

Yes I can repeat my download and it is not changeing - so the algorithm should work (and it it not my discovery/work).

I will start an own thread for this soon.

(grab a Raspberry Pi Pico!)

...and certainly we have the mtcdmcutool for both files:

PS C:\work> .\mtcdmcutool.exe .\mcu_readout.bin

mtcdmcutool: a tool to decode/encode/info MTCD MCU firmware images for RK3xxx/PX3/PX5 headunits.
v.1.2, (c) 2018, Wadzio

MCU image looks like DECODED firmware!

Info from MCU image:
Manufacturer F: LEI_MA
Manufacturer S: LM
Version: V3.01c
PS C:\work> .\mtcdmcutool.exe .\dmcu.img

mtcdmcutool: a tool to decode/encode/info MTCD MCU firmware images for RK3xxx/PX3/PX5 headunits.
v.1.2, (c) 2018, Wadzio

MCU image looks like ENCODED firmware!

Info from signature:
Image bytes: 240636
Manufacuter: LM
Version: V3.01c

Info from MCU image:
Manufacturer F: LEI_MA
Manufacturer S: LM
Version: V3.01c
[MTCD Android Head Units General] marchnz:
That's great, but what is the question and why discuss mcu?
[MTCD Android Head Units General] FMode:
Please identify this unit.

Is it an LM?

If yes: then Why I have these differences?

If I would flash Malaysk/Hal9K on this unit I would have flashed an LM MCU Image and this would have CHANGED my MCU.

For me this is disturbing as I would recommend ANYTIME breaking the protection, saveing the image BEFORE trying to flash to Malaysk/Halk9k/...
[MTCD Android Head Units General] marchnz:
Yes LM, that's an extreme way to find out when it's listed in android system information, MCU.

I think you may have confused MCU for Android, the ROM is not MCU and their kanged ROM does NOT install the MCU. So no, you would not have flashed an LM MCU unless you added an LM MCU image, and even then, you would have had to specify flash MCU.

Also, this is not the thread for discussing kanged paid ROMs, please take your commentary to their threads.
[MTCD Android Head Units General] FMode:
I added a screenshot of this android system.

Everything here relies on the MCU version (hacking, rescueing, ...) incl. die MTCx forums - it is not only about ROMS. I bet these ROMS require some new versions and may have problems on older.

The problem is I have doubts now about the trustworthiness of the displayed MCU Version.
[MTCD Android Head Units General] guma53:
Hmmm, I've read all messages in this topic and still I don't know what MCU file can I use... maybe someone got HTC MTCD MCU, from BonRoad seller? Or someone know how to activate volume knob.
[MTCD Android Head Units General] typos1:
You have an NCT MTCD unit, therefore you can use any HCT MTCD MCU and if you read [MENTION=4974080]marchnz[/MENTION]'s thread you will see that he has found a way to use other MTCD MCUs on units they werent designed for, ie using a JY MTCD MCU on a GS MTCD unit.

So, if you cant find any HCT MCUs in the MTCD MCU thread and on the fileservers in my signature, then read [MENTION=4974080]marchnz[/MENTION]'s thread and try an MCU from another MTCD manufacturer on your unit.
[MTCD Android Head Units General] guma53:
HCT mcu is nowhere to be find. I know there is cros compatibility, but I don't understand what other MCU i can instal for my Sofia (not rockchip) unit, but thank you for your help, I'll try to get it work :) (or get used to my "Navi" and "Src" key to work as vol + and - on my HU ;p)
[MTCD Android Head Units General] typos1:
The processor you have is not relevant - an MTCD unit is an MTCD unit regardless of the processor, without the SoM they are all the same - you could put a Sofia SoM in your machine or an RK3368/PX5 SoM.

If there are no HCT MCUs in any of the MTCD MCU threads in the forum (I take it youve searched them all ??) then you will have to read this thread and follow the instructions, only when you have red ALL OF IT will you understand. If no one has tried cross compatibility on an HCT MTCD unit then you will have to experiment yourself.
[MTCD Android Head Units General] guma53:
Believe me, I've searched everywhere for this MCU. On russian 4pda forums they say (according to Google translator) that update for HCT mcu from Bonroad IS HXD! But they also have problem to program volume knob, tommorw i'll try something that they say on 4pda to set in factory settings. I don't feel like experiment with diffrent mcu, i need that radio and i do dont want to brick it, for now at least ;)
[MTCD Android Head Units General] typos1:
If its any help, I ve just discovered (by coincidence while searching for something else) that HCT stands for "Heng Chang Tong", maybe that will help you find an MCU ?
[MTCD Android Head Units General] marchnz:
HCT http://www.hctsz.com/

I can see the sophia boards but not the PX5, perhaps due to dated site. Ive emailed them.
[MTCD Android Head Units General] bluemask69:
Has anyone tried to install the GS mcu (version unknown) dated 22 may? It is included in the new GS stock rom package dated 14 juni

https://drive.google.com/drive/folders/0B9Ep0Y1FILulQTFlSVMxcU9NN0E?usp=sharing

https://xdaforums.com/showpost.php?p=73042729&postcount=877
[MTCD Android Head Units General] basmand:
https://xdaforums.com/showpost.php?p=72948329&postcount=1526[/QUOTE]
[MTCD Android Head Units General] bluemask69:
Did you see if version 2.51 has the ACC OFF DELAY function?
[MTCD Android Head Units General] basmand:
Yes it is, ACC OFF DELEY function are as I remember in "Extra Settings"
[MTCD Android Head Units General] bluemask69:
perfect so i don't need the HA MCU version :good:
[MTCD Android Head Units General] typos1:
The MCUs are the same whatever processor in the unit so it shouldnt matter.
[MTCD Android Head Units General] solmer:
Unit freezing...

Hi, actually I'm running HA 2.56 on my JY ul135. I've been testing it since 7 of July and I've experimented more than 7 freezea of my unit. First time I thought could be a problem withe the mp3 player (player pro) so I uninstalled it but the problem is there. I'll try with 2.52....Has someone suffer the same problem?

Thanks in advance
[MTCD Android Head Units General] guma53:
Damn guys... It was SO simple ;) thank to russian 4pda forums i have did activate volume knob after upgrade from hct MCU to xhd... Just go to factory settings and change "customer version" to "version 2". Volume knob is working ;) thanks all to guide me to that forum. Best Regards ;)
[MTCD Android Head Units General] typos1:
Lol, cool. :)
[MTCD Android Head Units General] marchnz:
Agree, what I was meaning is that this contact might be a line of supply for PX3, PX5 and Sophia core boards. I didnt see the px5 listed on the site, which might be due to not being updated. Changing between English and chinese renders different info too. Great to see chinese QA at its best here too.
[MTCD Android Head Units General] bettuccio:
Hello to everyone, I have a Witson (MX) Px5 mtcd i would like to try to change the MCU with another manufacturer. Say that it will be possible? What do you recommend me?
[MTCD Android Head Units General] marchnz:
What version is yoeur current? If lower than HA 2.56, try HA latest per OP, but what is it you are wanting to achieve? I originally investigated (read 1st post/OP) to enable sleep options menu. I havent seen any other tangible advantages
[MTCD Android Head Units General] bettuccio:
I have a MCU MX v.2.55 (witson), I want to know if other MCUs are compatible with my drive. Has anyone tried to change with MCU GS for example? In your explanation you are talking about "GS, HA, KGL, KD" but not MX. I wanted your opinion.
[MTCD Android Head Units General] typos1:
From what I saw on the English version of the site they only had the RK3066 SoMs in stock.
[MTCD Android Head Units General] marchnz:
Suggest comparing your MX against the same revision of either HA, KGL, KD, GS with a hex editor. If largely identical, suggest it could be OK to apply (the MCU update verifies MCU code anyway). What is likely to be different is the manufacturer options which I suspect is the only diferences (i.e. the factory options - e.g. knob setting, hardware button settings etc..)

In any case, document your Factory settings before updating the MCU and review post#1.

Best of luck.
[MTCD Android Head Units General] bettuccio:
What should I check exactly? What sign? I already have a backup of the MCU file made from factory settings. I have another question: do you think the MCU also controls parking sensors?
[MTCD Android Head Units General] martyuk:
Update

Thanks to both Basmand and syk02jcb.

I've updated to the latest GS Android and MCU, and that seems to work pretty well now!

I did figure out the 'Prohibit Reverse' thing too. I found that I had a connection issue from the wires in the head unit loom into the connector I fitted to connect to the wiring I'd installed in the vehicle, so once this was sorted and found I was definitely getting the correct signal to the correct pin, I then did the update to Android/MCU and found it still didn't work.

After some searching online, and checking the unit, to find the 'Prohibit Reverse' was set to 'disabled'. Swapping it to 'Enabled' got it working properly!

So now have the unit working 99% how I want it. One of the USB outputs seems to keep randomly dropping out - which has my DAB receiver, 3G modem, and an extra USB cable run into a cubby box to plug a stick into. I think the problem is my USB hub on there as looking on the unit with a 'host controller' app the whole thing disappears, not just one device.

I know one of the outputs had 3G/wifi written on the sticker, but I've used this one for my DVR Dash cam, as I found I was having issues running the dash cam through the hub with other devices - I ended up getting a messed up image. I have a new, powered USB hub on the way - so fingers crossed that will fix any remaining issues with the USB.

Again, thanks to the contributors on here who have helped out so far! Much appreciated, and again, one of the reasons I went for one of these units - as it seemed to be there was a lot of owner input in the forums - which is amazing, considering the Xtrons forums STILL haven't even approved my initial question about the reversing camera!

Cheers!
[MTCD Android Head Units General] typos1:
Do you have a front USB ? On the very closely related MTCB/C units the front USB is the best one to use as its wired directly to the SoM.

You may also want to check the cache for the usb as I ve heard it not very big, of course it may also be your usb hub, I have problems with the cheap ones sudddenly un mounting themsleves on my desktop.

Forget support from retailers like Xtrons/Eonon/Pumpkin/Joyimg etc, theyre useless - they havent a clue what theyre talking about and even the manufacturers dont know that much, the best and only proper support comes from XDA and 4pda.ru.
[MTCD Android Head Units General] martyuk:
No front USB, No. The unit just has 4 touch buttons, a hole for the 'reset' button, and a microSD card slot on the actual face panel.

I'll see about checking the cache for USB - though if it were that, then surely the DVR Dash cam which is also USB based would also fail (this keeps on recording happily)? When the 3G/DAB/USB stick all disappear, so does the hub (and it was a cheap hub anyway!) - I figured for the cost of a 4 port powered hub it was worth trying that. I have also considered seeing if there was another USB port accessible on the board somewhere that I could tap into (like where the units that have a front USB port) for one of the other devices, to then try and avoid using a hub at all.

I might try stopping the dash cam recording automatically, and see if that makes a difference.. would rule in/out cache issues then too.
[MTCD Android Head Units General] typos1:
Sounds like it could be the hub then.

There are some pins for usb on the MTCB SoM, there may also be for the MTCD ones.
[MTCD Android Head Units General] martyuk:
At some point when I have time, I was planning on having a hunt over the board to see what's there... it has a port labelled for 'Ipod' and though it has the app available internally to do iPod connectivity, Xtrons also say it won't do it and the connector on the back won't do anything/they don't have a cable for it... but my guess is that the ipod port will probably just be a USB port aswell, so thinking that I should be able to trace if it is, and then see if I can use the port on the back for my own devices :)

Will try to remember to update once I've swapped the hub, especially if that fixes the issue!
[MTCD Android Head Units General] typos1:
Yes, all MTCB/C/D devices can handle ipods, not very well from what I ve read, but they can.

As I said, I wouldnt take any notice of Xtrons theyre only good for new firmware, theyre just a seller and know **** all.
[MTCD Android Head Units General] solmer:
Hi, Could someone put the original config MCU settings from JY-UL135? I think something is wrong with my unit and I've lost the MCU backup file....

Thanks in adavance
[MTCD Android Head Units General] makes2068@gmail.com:
Updated my Erisisn 3015 LM unit from PX3 to PX5 with the witson upgrade-board.

Installed LM 2.52.2 MCU.

Unit always goes to sleep ;-(

Auto-sleep-setting is available in the settings menue, but not working.

Can i use the 2.56 mcu from here without any risk?

Is my unit now a MX (Witson board) one instead of LM
[MTCD Android Head Units General] marchnz:
Try HA MCU. Suspect HA is closest to reference HCT design.
[MTCD Android Head Units General] makes2068@gmail.com:
HCT Design? What do you mean?
[MTCD Android Head Units General] WarSpaz:
Hello. I saw that you have a mx unit. I just wanted to ask you, how is the bluetooth music streaming quality? I am wondering since i am thinking of buying a mx device for my kia ceed 2010.

Skickat från min MI 5 via Tapatalk
[MTCD Android Head Units General] makes2068@gmail.com:
So it is not longer possible to recognize the unit developer!?

At the moment i got an Erisin Unit = LM

MCU = LM 2.52

After flashing HA mcu it looks like an HA unit.
[MTCD Android Head Units General] bettuccio:
The quality is not very good for calls. There is still a slight echo in transmission. This seems a problem for all units.
[MTCD Android Head Units General] WarSpaz:
But for music? Is it clear and high quality or does it sound low bitrate and bad? Btw, there is a fix for the echo problem by f1x. ([PX5] Solution for the bluetooth echo)

Skickat från min MI 5 via Tapatalk
[MTCD Android Head Units General] Bose321:
I used to have an old Pioneer AVIC before this. It looks and works a lot faster, but the sound quality is horrible compared to that. The built-in amp is rubbish. But it should be better if you connect it to an external amp. I am planning to do that.
[MTCD Android Head Units General] typos1:
Or you could replace the amp chip with a Pioneer one, or indeed many others - most car stereos have the same pin out for their amp chips.
[MTCD Android Head Units General] Bose321:
Do you think replacing the amp chip is easy? Doesn't sound like something you just do.
[MTCD Android Head Units General] typos1:
Yeah, its pretty easy, a few people have done it, you need to desolder it.
[MTCD Android Head Units General] Bose321:
Interesting. Do you have more information regarding this? Are all chips compatible or are there certain rules for this?
[MTCD Android Head Units General] typos1:
Just find the data sheet of your chip and then check the pin outs with the one you want to replace it with, as long as everything is on the same pin it ll work.

Its been talked about on here and people have don it on 4pda.ru. I d use google to try and find where its been mentioned in these forums.
[MTCD Android Head Units General] bettuccio:
I know about f1x fix but I have not tried it yet. For me it is not a priority. The important thing is that I understand. The bluetooth sound from the cellphone seems good to me.
[MTCD Android Head Units General] marchnz:
Has it been proven fixed? Posts suggest it might be a work in progress.
[MTCD Android Head Units General] marchnz:
This has been discussed this in another thread where both original and pioneer amp ICs were compared with supporting bench tests. (Oscilloscope, power output tests at onset of distortion.)

The results indicate that the gains from swapping the amp IC are so insignificant, its not worth it. It sure seems to have a placebo effect though!

BTW the pioneer amp is probably manufactured by the same vendor, with the pioneer a result of binning.

Suggest installing external amps to improve power output.
[MTCD Android Head Units General] typos1:
Well youre right about it being made by the same people - STMicroElectronics make amp ICs for loads of manufacturers, including OEM and aftermarket ones.

But they dont make them all to the same spec and they are literally hundreds of amp ICs with different specs and the same pin out that would work, so when you say "with the Pioneer" you mean the one they were testing, there are many many different Pioneer amp ICs some may well perform better in tests.

My first and second MTCB units had different amp ICs and the second one did sound better and there were a lot of people moaning about the sound quality on the earlier MTCB units.

I m not saying I doubt the test results, but clearly not all the amp ICs on sale today are the same, otherwise a £35 Lidl car stereo would same exactly the same as the top of the range one from a known brand. Of course there are cheap stereos that sound good and expensive ones that dont, just like in home hifi some amps are better than others.

And thats before you factor in personal preference - tests said CD sounded better, but some people prefer vinyl.

Changing the amp IC can improve the sound, but like you I have a separate amp. I ve also done the 7floor sound mod which is one of the best things you can do to these units whether your using an internal or external amp.
[MTCD Android Head Units General] marchnz:
Checkout binning when you're bored sometime :).

Note that I couldn't find any 'better' difference in terms of slew, THD (distortion) etc. This seems to limit the perceived 'better' to confer output power.

Power (watts) = volts x amps

The technical problem for any onboard amp such as the one found in our units, is that they are limited by the supply. The amp ICs in our units are BTL and the 'better' performing chips simply have 'better' output MOSFETs (lower. RDSon resistance.). A simple power calc will identify the maximum possible output power that could be a achieved if the MOSFETs had a therotical zero RDSon.

External units overcome the supply issue by switchmode supply inverters/boost converters to increase the supply voltage thus the maximum output is increased.

Again both the TDA(stmicro electronics) and Pioneer IC are limited by the supply in our units, there is no boost converter.

The I2C mod sounds very good, what are the cons if any?
[MTCD Android Head Units General] typos1:
I agree about the limits for power, but sound quality isnt all about power - you can have a less powerful amp sounding better than a more powerful one.

But my point was that not all amp ICs on the market sound the same, some are better than others.

Cons to the 7floor mod ? None, unless you count doing a little soldering as a con. :)
[MTCD Android Head Units General] makes2068:
My problem still exists.

Px5 board with malaysk V3 and mcu 2.52.

Unit always boot up, even the ignition was of for only a few seconds. Boot logo shown and then message: apps starting...

That's horrible. With 5.11 unit came up fast for the 2 hour delay.

What can I do?

Tested HA 2.56. MCU. Did a lot of settings in factory cause unit is a LM one.

No chance. And there was a beep sound with the hard keys I can't switch off.

Please help me. Bought the upgrade board for faster boot and now it always boot up for 30 seconds.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] marchnz:
Have you tried installing the latest HA android ROM and resetting your unit by removing the power to it?
[MTCD Android Head Units General] typos1:
You tried it with factory ROM ?
[MTCD Android Head Units General] makes2068:
Tried it always with malaysk.

Got no factory Rom for LM unit. Updated old px3 unit with new board.

But malaysk is based on ha I think.

Can try to release the power cable on Monday.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
You dont need a factory ROM for an LM unit, you can use any MTCD RK3368/PX5 ROM, just like you can use any MTCD RK3188/PX3 ROM for an MTCD RK3188/PX3 SoM.
[MTCD Android Head Units General] makes2068:
Now I got a px5 unit after board update. And I want to have root. Hope malaysk will fix it if it is Rom depended.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
I mean put on a factory ROM to see if you still have the problem, to trouble shoot.
[MTCD Android Head Units General] makes2068:
Good idea. But not at the moment.

To much work to do this.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
Lol, really ? It takes about half an hour max :)
[MTCD Android Head Units General] makes2068:
Including 3gb of tomtom maps? No not really

Send from D6603 with Tapatalk
[MTCD Android Head Units General] solmer:
Look in a post related to root. You need to install kingoroot, super SU 2.79 and remove kingoroot. I've done it successfully
[MTCD Android Head Units General] marchnz:
Thanks for adding ZERO to this thread and ignoring the advice of members that have. Read the OP.
[MTCD Android Head Units General] makes2068:
???

Maybe I need to set something in factory settings.

There is a power status setting.

On, off and a third one I don't know at the moment.

Send from D6603 with Tapatalk
[MTCD Android Head Units General] typos1:
Or try MTCD ROM Builder and inject root yourself.
[MTCD Android Head Units General] makes2068:
Got an other problem, not root.

Every startup, my unit boot up with bootlogo... How to set the autosleep with intant start?
[MTCD Android Head Units General] makes2068@gmail.com:
Maybe problem solved.

Went back on a old 2.44 mcu and it seem to work.

Perhaps it works with 2.52 too but there is defenitely a setting inside the factory setting. So mcu´s are not fully cross compatible ;-(
[MTCD Android Head Units General] makes2068@gmail.com:
To good to be true. Not working.

I give up... Unit ist fast as hell and very responsive.

Always have to wait for booting up.