Database Info

Can i safely update my MCU using an upgrade PX5 board without updating the ROM also?

I bought a while back a Chinese MTCD PX3 'ouchuangbo' unit with as MCU: MTCD_HLA_V1.88_1 running on android 5.1
I then upgraded this PX3 system with a PX5 board from wilson and installed this on my system, it was a matter of plug and play and it works fine, the unit is now working for several weeks on the new PX5 board using the Malaysk PX5 rom on android 6
Because the MCU is an older version I contacted the seller and asked if there was and update available for the MCU.
It seems 'ouchuangbo' indeed had a newer MCU version available with number MTCD_HLA_V2.46.3 but they answered to me the following after i asked if i could receive the update files:
'Our engineers said: If you want to upgrade the MCU software, you need to upgrade the main program at the same time. If the operation is not correct, the upgrade may fail. If the upgrade fails, you need to return to China to repair, all costs you need to bear. Because our main program and MCU software are updated. While upgrading the two software, the system more stable. Our software is android 5.1. '
I also received from seller the 2 following files: dmcu.img (189kb) and dupdate.img (850mb).
Is his answer true and can i NOT update my MCU with the current PX5 board with this new MCU update safely without flashing the ROM aswel?
Must i first place back my old PX3 board before i update my unit?
Or can i only update the dmcu.img running Malaysk PX5 ROM and keep the current ROM without risking to brick my unit?
Who can advise?

You can safely use dmcu.img without flashing dupdate.img.
Before updating MCU, make a backup of MCU config
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

colostro said:
You can safely use dmcu.img without flashing dupdate.img.
Before updating MCU, make a backup of MCU config
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
Thx.
Any idea how do make a backup of the mcu config?

Go into factory settings and you Can find the "export settings" button
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Also, maybe search thru some of my recent threads. I have accomplished the same for my mtcd-kd unit with some pretty interesting experiences. If you have a 1024x600 unit, you should have no issues.
Use the dmcu file by itself, do not flash the PX3 dupdate image on the PX5. At this time we have franken machines. Use the dMCU file from your manufacturer or known compatible unit and the PX5 dupdate image of your choice. However, I would perform any updates individually.

B3rt said:
Any idea how do make a backup of the mcu config?
Click to expand...
Click to collapse
In factory settings you can export mcu.cfg
To re-apply the settings, just put the mcu.cfg file on the SD card with the mcu.img. Or, once mcu has been upgraded, you can remove the mcu update (.img) from the root of the SD or USB Stick card and apply the config (.cfg) on the root of the SD or USB Stick separately - by running the 'upgrade MCU', it will see .cfg file and apply it.

etulio said:
In factory settings you can export mcu.cfg
To re-apply the settings, just put the mcu.cfg file on the SD card with the mcu.img. Or, once mcu has been upgraded, you can remove the mcu update (.img) from the root of the SD or USB Stick card and apply the config (.cfg) on the root of the SD or USB Stick separately - by running the 'upgrade MCU', it will see .cfg file and apply it.
Click to expand...
Click to collapse
IS this a safe operation? I can see restoring the dmcu.cfg for the same version of MCU Code that was originally installed. HOWEVER, I can see how an application of a dmcu.cfg file may not function appropriately if a different version of MCU Code is in place.
Anyone have a 100% answer on this?

screwey said:
IS this a safe operation? I can see restoring the dmcu.cfg for the same version of MCU Code that was originally installed. HOWEVER, I can see how an application of a dmcu.cfg file may not function appropriately if a different version of MCU Code is in place.
Anyone have a 100% answer on this?
Click to expand...
Click to collapse
I upgraded my originally JY PX3 MCU to HA after installing my PX5 board (see cross-compatible MCU thread.)
Unfortunately there are no guarantees in this risky process.
Your concern appears to be around factory settings/dmcu.cfg - to mitigate this risk, document all of the settings as they are found in the factory settings menus. E.g. "knob mode", volumes, customer version, radio, bluetooth type, hardware keys.
I had to manually set some of these factory settings after applying a backup from my Joying config, as it appears that the vendor mcu contains some configuration which takes precedence.
Good luck.

i got no luck.
When i started the update it fails with:
do not Match mount /mnt/external_sd
Installation hctextcfg aborted.
do not Match mount /mnt/external_sd
Installation mcucfg aborted.
do not Match mount /mnt/external_sd
Installation mcuimg aborted.
updata fail!
System works further normally, but the mcu version is still the same.
Contacted the seller and they insured me it was the correct version, they would as the enigineer on monday.

B3rt said:
I bought a while back a Chinese MTCD PX3 'ouchuangbo' unit with as MCU: MTCD_HLA_V1.88_1 running on android 5.1
I then upgraded this PX3 system with a PX5 board from wilson and installed this on my system, it was a matter of plug and play and it works fine, the unit is now working for several weeks on the new PX5 board using the Malaysk PX5 rom on android 6
Because the MCU is an older version I contacted the seller and asked if there was and update available for the MCU.
It seems 'ouchuangbo' indeed had a newer MCU version available with number MTCD_HLA_V2.46.3 but they answered to me the following after i asked if i could receive the update files:
'Our engineers said: If you want to upgrade the MCU software, you need to upgrade the main program at the same time. If the operation is not correct, the upgrade may fail. If the upgrade fails, you need to return to China to repair, all costs you need to bear. Because our main program and MCU software are updated. While upgrading the two software, the system more stable. Our software is android 5.1. '
I also received from seller the 2 following files: dmcu.img (189kb) and dupdate.img (850mb).
Is his answer true and can i NOT update my MCU with the current PX5 board with this new MCU update safely without flashing the ROM aswel?
Must i first place back my old PX3 board before i update my unit?
Or can i only update the dmcu.img running Malaysk PX5 ROM and keep the current ROM without risking to brick my unit?
Who can advise?
Click to expand...
Click to collapse
Hi, I have MTCD MCU HLA unit and I do not get firmware or MCU from the vendor, you could send me the updated files (firmware and MCU you have).
my email: [email protected]
Thank you

Is it possible to make a full backup off the mcu? I mean a mcu.img. I have the mcu.cfg already.
Also got the update of a HLA PX3 unit with 7.1 from the manufacturer, nupdate.img and mcu.img.
But to be sure I want a backup from the original mcu.

Any updates here? I have also al HLA unit, a PX3 7.1 than I have upgraded with a PX5 board. I would like to update MCU...

GoNzCiD said:
Any updates here? I have also al HLA unit, a PX3 7.1 than I have upgraded with a PX5 board. I would like to update MCU...
Click to expand...
Click to collapse
Appears all of the questions asked by OP were answered.

Android Radio update MTCD_KGL RK3188

Hello,
I have a car radio on the Android MCU system version MTCD_KGL_V1.53a_1 compilation number rk3188-userdebug 27052016.
Can I update to a newer version of android, because it is 5.1.1 now?
On the forum I found MCU updates for KGL v.2.83. Where can I find a ROM for my radio.
I tried to update the MCU, but unfortunately I'm making a mistake. I do not know what I'm doing wrong. I downloaded the MCU from the site
https://forum.xda-developers.com/showthread.php?t=3246386
I copied to the card and changed the mcu.img file to dmcu.img. Unfortunately, it lights up the error.
I do not know if I should update the ROM first and then the MCU first.
Greetings Piotr Z

Lollipop
piotr_waw said:
Hello,
I have a car radio on the Android MCU system version MTCD_KGL_V1.53a_1 compilation number rk3188-userdebug 27052016.
Can I update to a newer version of android, because it is 5.1.1 now?
On the forum I found MCU updates for KGL v.2.83. Where can I find a ROM for my radio.
I tried to update the MCU, but unfortunately I'm making a mistake. I do not know what I'm doing wrong. I downloaded the MCU from the site
https://forum.xda-developers.com/showthread.php?t=3246386
I copied to the card and changed the mcu.img file to dmcu.img. Unfortunately, it lights up the error.
I do not know if I should update the ROM first and then the MCU first.
Greetings Piotr Z
Click to expand...
Click to collapse
I have read that if you upgrade your android system to the newer version; something about the GPS maps will no longer work. Not sure but you might want to look for that.
I have the same system A-Media Auto, MTCD-KGL_v1.53a_1
I found a newer version KGL_10-20-2016_1.92a_4_dmcu.img but I can't get the Head to find the .img file
I tried the SD card in the slot, GPS slot and a USB cable. Still System Update cannot find the .img file. Frustrated I gave up.
I did find that the SYGIC maps works good with the unit. I didn't like the IGO that came with it and wiped the map SD.
I also loaded Car Launcher v2.4.074 which is more appealing.
The backup camera is kind of squirrelly, works when it wants to.
Thinking about getting a new head unit with a flat screen, no buttons and knobs, but not sure if I want to go with a name brand or pure android version.
Will try to insert an image of my unit but I am new at this. The image wants me to put in a http url
/home/pok1/Downloads/20190316_134105.jpg

Wich mcu / rom version for GA9151B Eonon Head unit

hello and thanks first all for the lot of rom works,
i hope its the right place,
i have a GA9151B Head Unit from Eonon with android 8, dab+, wich is the right way and rom to upgrade it to 9 or 10?
wich mcu i must flash for mazda3 (2004-2009?)
the mass of roms and how to upgrad tutorials confused me
atached the unit data

what version is right for this unit?
Яндекс
Найдётся всё
disk.yandex.ru
flash only one of this? or more to do?
thanks

Here you will find all the information, including the tools you need to successfully update. The update also carries some risk and some types of bluetooth may not work, everything is described here:
upgrade method to another android version for Rockchip unit (px6 px5 Px30 and other )
following the official Rockchip upgrade tool https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933 if you are upgrading from the same version ex android 9 to android 9 you don't need...
forum.xda-developers.com
[MTCD/E] Android 10 upgrade using official Free tools
To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads. First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported...
forum.xda-developers.com

@Pavel-71
thanks for the replay,
my unit says in factory settings i have a WQ_BC6 bluetooth device, is this compatible?

There should be no problem with WQ_BC6. Before upgrading to android 10, I recommend updating the MCU. Save your settings before updating your MCU. In the factory setting, there is an export button for this. Locate the dmcu.cfg file and copy it to external storage. In case of problems with the control or the image after updating the MCU, you will return the settings with it.
The update is the same as the MCU update, just use dmcu.cfg.
You can download the latest updates, including your current one, here:
MTCE_HT.rar
drive.google.com
II do not bear any responsibility for any errors caused by the update. You do everything at your own risk !!!
Here is a video tutorial on updating to android 10:
MicroSD(gratis):
OTG(gratis):
Modinstaller Pro, paid (10 €):

@Pavel-71 wow thanks for the information,
last question on https://disk.yandex.ru/d/umCvHqCDzHccr/RockChip PX5 Android 10 listet diferent a10 versions, but no ht, its all the same? i cant find the diference. or what for a a10 rom with the orginal look is recommendable

HT firmware unknown. I tried HCT4 and now I have HCT7. As far as I know, they all work, the difference is in the launcher. Select by launcher. Here I made screens with a description of the ones I found:

MTCE LM - > HA -> HCT MCU?

You can see from the Unit Pics the MCU and some other components are HCT.
The original firmware / mcu was LM Android 8.0, but they were so slow to update the firmware, I changed to HA.
I currently have HA 3.45 but see there is both LM and HA later versions.
I wanted to install Android 10, but the question is;
- should I go back to the LM firmware?
- should I go to the HCT firmware given multiple components are actually HCT?
In so far as upgrading to Android 10, i see there are only two full images;
- HCT7_PX5 (but there is also HCT4, HCT2, HCT - but no full image for these)
- CHS7_PX5 (but CHS3 has not full image)
What the view on which MCU to use, and which path.

gwaitsi said:
You can see from the Unit Pics the MCU and some other components are HCT.
The original firmware / mcu was LM Android 8.0, but they were so slow to update the firmware, I changed to HA.
I currently have HA 3.45 but see there is both LM and HA later versions.
I wanted to install Android 10, but the question is;
- should I go back to the LM firmware?
- should I go to the HCT firmware given multiple components are actually HCT?
In so far as upgrading to Android 10, i see there are only two full images;
- HCT7_PX5 (but there is also HCT4, HCT2, HCT - but no full image for these)
- CHS7_PX5 (but CHS3 has not full image)
What the view on which MCU to use, and which path.
Click to expand...
Click to collapse
I wanted to install Android 10, but the question is;
- should I go back to the LM firmware?
No, stay on MCU HA if it has been working OK.
- should I go to the HCT firmware given multiple components are actually HCT?
Install any available vendor MTCD (px5?) IMAGE .img Android you like then OTA to the vendor you want. It does not matter. I think it's an HX .img or something like that on yandisk and my Google drive.
Use OTG if possible, OTG is the only 100% safe method, plus you can get a full working backup of your current ROM (unlike paid hacks.)

Question Any Car Link Update?

Hi my car link apk version is : 2.22.0512.1110 is it latest version?

You can try updating it to this version: https://drive.google.com/file/d/1hM_BCkwcYrLCwOiKJWKguxQjrAocB68p
It was compiled on 2022-09-16 11:31:20

daviddosa said:
You can try updating it to this version: https://drive.google.com/file/d/1hM_BCkwcYrLCwOiKJWKguxQjrAocB68p
It was compiled on 2022-09-16 11:31:20
Click to expand...
Click to collapse
Do you know what has changed? any changelog or smtn

No, just recently downloaded the full ROM for my M300S and this is the file I extracted from it. I doubt that anything major has changed.

daviddosa said:
No, just recently downloaded the full ROM for my M300S and this is the file I extracted from it. I doubt that anything major has changed.
Click to expand...
Click to collapse
Thanks for sharing, just updated and it's works

daviddosa said:
You can try updating it to this version: https://drive.google.com/file/d/1hM_BCkwcYrLCwOiKJWKguxQjrAocB68p
It was compiled on 2022-09-16 11:31:20
Click to expand...
Click to collapse
Not sure why but this version of CarLink doesn't work for me. I plug in my phone and it doesn't detect it. Only version 2.22.0107.1105 works for me but night mode doesn't work with headlight dimming.

Moniushko said:
Not sure why but this version of CarLink doesn't work for me. I plug in my phone and it doesn't detect it. Only version 2.22.0107.1105 works for me but night mode doesn't work with headlight dimming.
Click to expand...
Click to collapse
It’s working fine for me. I only use it wirelessly, never plugged my phone in, I’m using CarPlay. Headlight dimming works too on my M300S, but I had to change that in the settings for the headunit itself and not in the app.

daviddosa said:
It’s working fine for me. I only use it wirelessly, never plugged my phone in, I’m using CarPlay. Headlight dimming works too on my M300S, but I had to change that in the settings for the headunit itself and not in the app.
Click to expand...
Click to collapse
Same, all works for me too. never plugged my phone. wireless only.

Moniushko said:
Not sure why but this version of CarLink doesn't work for me. I plug in my phone and it doesn't detect it. Only version 2.22.0107.1105 works for me but night mode doesn't work with headlight dimming.
Click to expand...
Click to collapse
What's your firmware version? Joying mentioned somewhere in May that you have to update the firmware to make it work with the newer versions of Carlink.
Other resellers simply add it to a complete new firmware to prevent these kind of issues. That's why @daviddosa took it from the latest complete M300S firmware.

surfer63 said:
What's your firmware version? Joying mentioned somewhere in May that you have to update the firmware to make it work with the newer versions of Carlink.
Other resellers simply add it to a complete new firmware to prevent these kind of issues. That's why @daviddosa took it from the latest complete M300S firmware.
Click to expand...
Click to collapse
I'm honestly not sure how to tell. The firmware is stock from when I got it sk I assume it's dated back to 2021. My HU's brand is "D-Noble" and I haven't been able to find a website that has all the unit's firmware. Searching on XDA, there's only like 2 or 3 mentions of this brand. The seller ghosted me on AliExpress so can't get it from there. I was thinking about flashing the firmware from another brand like Joying, but I was afraid that my HU's firmware is too "custom" and I didn't wanna mess that up. By custom, I mean that it looks like it was specifically configured to work with and look like a VW HU.
Edit: Just checked my FYT.prop and my FYT manufacturer is 94. I found an FYT manufacturer list on here and it only says 94 is "VAG". Sorry if this doesn't help much.

I just flashed Joying's 8-15-22 update from their website (just the kernel, no apps) and still no luck. I plug in my phone and Carlink fails to detect it. Still only works on 2.22.0107.1105.

Moniushko said:
I just flashed Joying's 8-15-22 update from their website (just the kernel, no apps) and still no luck. I plug in my phone and Carlink fails to detect it. Still only works on 2.22.0107.1105.
Click to expand...
Click to collapse
Then I suppose the "support" for the new carlink is in the AllAppUpdate.bin. You need to adapt it for your unit before you flash it.
I can't help you further as I don't use Carlink. I have a nice uis7862 Android unit who has all functionality itself (just like you).

surfer63 said:
Then I suppose the "support" for the new carlink is in the AllAppUpdate.bin. You need to adapt it for your unit before you flash it.
I can't help you further as I don't use Carlink. I have a nice uis7862 Android unit who has all functionality itself (just like you).
Click to expand...
Click to collapse
Thanks for your help! I know you wonder why people want to use AA on a full-fledged Android unit. For myself, I like the seamlessness between my phone and the screen. I don't want to fuss much on my unit, including having to use my phone as a hotspot just to get internet on the unit. AA provides a simple car-centric interface that I can use to simply navigate, get messages from my phone and listen to Spotify.

Moniushko said:
Thanks for your help! I know you wonder why people want to use AA on a full-fledged Android unit. For myself, I like the seamlessness between my phone and the screen. I don't want to fuss much on my unit, including having to use my phone as a hotspot just to get internet on the unit. AA provides a simple car-centric interface that I can use to simply navigate, get messages from my phone and listen to Spotify.
Click to expand...
Click to collapse
Its probably best to obtain a genuine Android Auto headunit instead of knockoff Kang emulator, the latter you could expect to be endlessely chasing updates for bugs.

@surfer63 I was able to figure it out. As per your suggestion, I flashed the full firmware from Joying (including the AllAppUpdate.bin) and I was able to successfully get the newer of version of CarLink to work. It even switches day/night mode with my headlights too! Unfortunately, the firmware update broke some other stuff such as
UI and MCU not matching error
I now get a "hybrid driving" page that doesn't go away every time I drive/switch drive modes on my car
RDS text no longer appearing on radio apps
I know how to fix the first error, and I think I can fix the second error by replacing the com.syu.ms.apk from my backup. Unfortunately, I have no idea how to fix the last issue but I guess I'll have to live with it. Seems like the latest FYT firmware updates may have changed something fundamental with how the MCU handles RDS text?
Anyway, thank you for your help!

Moniushko said:
the firmware update broke some other stuff such as
UI and MCU not matching error
I now get a "hybrid driving" page that doesn't go away every time I drive/switch drive modes on my car
RDS text no longer appearing on radio apps
Click to expand...
Click to collapse
If you change the FYT manufacturer id back from 43 (Joying) to your manaufacturer (I assume you saw my script at the bottom of post #1 of the "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware" thread), issue 1 should be solved. However, this might also solve issue 2 and 3.
Note that the FYT firmware also checks this manufacturer ID to send/receive different commands/codes/data to/from the MCU. The Android ms.apk, plus a few other apks, behave differently towards the MCU based on the manufacturer id.

Hi, when I get a call on carplay I just noticed quality is poor. How can I fix that.
Android Version : 10
Baseband version : FM_BASE_18B_W21.20.4|sc9863A_modem|05-20-2021 10:13:14
MARLIN3E_TRUNK_W21.27.3|uwe562_marlin3E_usbhub|07-07-2021 01:36:43
Build number : QP1A.090711.020 release-keys
System Info : APP2022-05-30 11:44:00
CPU Info : CPU:UIS8581A Octa-Core [email protected] GB(Memory) + 32GB(Storage)
MCU Version : 2022.06.24 14:34:07 NOR_53_L6315_G23P48F64_E60_V:1.0_FYTR
Bluetooth Version : BLINK_2161_RELEASE/2022:06:16:17:41:56_blink
CAN Protocol Version : VER.BG-RN11.1

Is it FYT unit,, post Android system information including MCU version

marchnz said:
Is it FYT unit,, post Android system information including MCU version
Click to expand...
Click to collapse
Yes it is.
Android Version : 10
Baseband version : FM_BASE_18B_W21.20.4|sc9863A_modem|05-20-2021 10:13:14
MARLIN3E_TRUNK_W21.27.3|uwe562_marlin3E_usbhub|07-07-2021 01:36:43
Build number : QP1A.090711.020 release-keys
System Info : APP2022-05-30 11:44:00
CPU Info : CPU:UIS8581A Octa-Core [email protected] GB(Memory) + 32GB(Storage)
MCU Version : 2022.06.24 14:34:07 NOR_53_L6315_G23P48F64_E60_V:1.0_FYTR
Bluetooth Version : BLINK_2161_RELEASE/2022:06:16:17:41:56_blink
CAN Protocol Version : VER.BG-RN11.1

v2022 oct 12