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:
Related
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.
Hi guys, during install of a HZC 2.58 firmware on my xtrons td101as (which had an older HZC version which I replaced with a GS version) I saw that there were 4 android files updated - so it seems that there are dependencies between android rom and mcu firmware version - and now I get the "version unmatched" message on my screen (but everything seems to work fine?)
So when I first install a new mcu firmware and then (after that) install an android rom it would override the changes made by the mcu installation?
What is the correct installation order when installing both android rom and mcu file and do I have to re-install mcu after updating the android rom?
Greetings
Detlev
First, I'm not an Android expert and I can't answer your question...
But I've never heard of dependencies between the 2 upgrades. If it's true, it's absolutely something worth to investigate!
You know what are the file changed?
I'm waiting for experts answer too.
OnkelDeffe said:
Hi guys, during install of a HZC 2.58 firmware on my xtrons td101as (which had an older HZC version which I replaced with a GS version) I saw that there were 4 android files updated - so it seems that there are dependencies between android rom and mcu firmware version - and now I get the "version unmatched" message on my screen (but everything seems to work fine?)
So when I first install a new mcu firmware and then (after that) install an android rom it would override the changes made by the mcu installation?
What is the correct installation order when installing both android rom and mcu file and do I have to re-install mcu after updating the android rom?
Greetings
Detlev
Click to expand...
Click to collapse
Set factory settings after updating MCU. Assume you documented your MCU settings before changing MCU to a differing manufacturer? Did you not realise that MCU update contains manufacturer/model factory settings config?
Unfortunately I don't know, what files where updated - there was only a message "Updatin android files 1/4"
I always installed without mcu config file and did the settings manually after install.
I installed the "HA" 2.59 mcu file (corresponding to the HA android file): "Version unmatched -01
Then I installed the old "GS" 2.56 mcu file - NO ERRORS!
What I don't understand: thougth the "Version unmatched -01" error was shown on the screen EVERYTHING worked without any problems? Strange ...
Now I do have a working system with HA 2.59 android version and GS 2.56 mcu - curious that the original "HZC" mcu file did not work too (I bought it with "HZC" mcu file installed, version 1.4 or so)
Greetings
Detlev
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
I've searched and searched and searched, but I can't seem to find a clear answer...
I recently purchased an Eonon-branded PX5 Android 8.0 MTCE_WWW unit (which I believe is VERY similar to MTCE_KLD). I really want to start "tinkering" with the unit (Viper4Android, custom ROMs, etc), but I want to make sure I have backups of the stock MCU and stock Android install before I start messing with anything - so that I can always get back to where I started if need be. Unfortunately, I'm having a hard time getting the MCU and Android firmware files from Eonon (still trying though!) - so I want to see if there is any way that I can create backups of the unit myself.
If I root the unit, can I then make full backups of the MCU and Android? Meaning backups that I can use to recover the unit if something goes wrong? If so, what applications should I use to create such backups? I've very familair with Android devices and rooting in general, but I'm used to having and using a custom recovery for stuff like this - but my understanding is that there is no custom recovery for these units (TWRP, CWM, etc).
Can someone please help me out here? I feel comfortable rooting the device via the adb method. But once I have it rooted, how do I create full MCU and Android backups?
Thank you very much!
Hi,
1. Android ROM - use OTG method to get ROM extract.
2. MCU - you can't. Get original MCU or later from forums or vendor.
Thanks for the response... That's what I was afraid of - no way to back up the MCU. Unfrotunately, my unit is an MTCE_WWW (Eonon) and I haven't had much luck finding recent stock MCU's online - and so far, Eonon hasn't cooperated either (what's the big deal??). <sigh>
I'm not familair with the "OTG method" (did a few searches, but what I saw was just custom revoery to OTG device?). I did finally just root it and at least got a full Titantium Pro backup - better than nothing I guess.
Hello
Hello, I have a unit auto media 9 inch for vw golf 5, android 6.0.1. Cpu 4 quadcore gpu 4D MALI 450 MP4 1024X600. MCU VERSION : K_(6851)_90_C9_K3_CAN(DAZHONGO)_AMP . I do not know the processor frequency, is quadcore 1.2 mhz or 1.4 mhz or 1.5 mhz or 1.6 mhz. I dont know . My unit have 1 gb ram and 16 Gb Intern memory. Unit not have a name. Is made in china. I want update android to 7 version or another version android 6, because I have problem with this version. This version not respond gut. . Please very much can help me someone?
How to use otg method?
Hi, let me take back this conversation, because I have the same problem and no solution: what is the best way to backup my original ROM?
What means otg method?
Thank you...
marchnz said:
Hi,
1. Android ROM - use OTG method to get ROM extract.
2. MCU - you can't. Get original MCU or later from forums or vendor.
Click to expand...
Click to collapse
Just Wonder, about Mcu there are different like MTCE GS, KSP, LM and So on. My 2din had before trying to update MCTE KSP v3. 0.1 running Px30 with Android 8.1.
Trying to upgtade to Android 9.
And Wonder as the player is erased if can change from ksp to LM, or Wonder what is different?
Reg
Alex
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.)