Hi,
Sharing these tools which were kindly shared on the Joying Forums (STT / STT-TEC) firmware for upgrading/recovering PX5 SOMs using the SDCARD create tool. On review, the zip contains additional tools to customise, create, unpack, repack firmware.
These tools may be of a breakthrough to both recovery and customising PX5 Firmware - the SDCARD create tool may be able to recover corrupt/bootlooping PX5 units without hardware mods, as the PX3 version results in a black screen when trying.
Note: change [config.ini] to Selected=2 to force english.
[Language]
Kinds=2
Selected=2
LangPath=Language\
Note Joying PX5s are STT and not HCT, the SOMs may be similar but the MCU code/comms may be different. e.g. Joying doesnt use MTC style apps, but this may be similar - unknown. Also note that the Joying MCU is different in terms of the filename/structure, but probably the very same hardware. If someone has one of these Joying PX5 units, would appreciate any info such as PX5 SOM module PICs, MCU pics/type, mainboard Pics. I havent attempted to flash a Joying MCU and Px5 update over my HCT as probably nothing to gain.
Download HERE
Note - Make your own OTG cable from a USB cable and two resistors!.
This indeed looks very promising. In fact if I understand properly it's able to create the directory structure on an SD card to recover even from completely busted ROM content.
It basically turns an update.img into sdupdate.img which can be flashed from an sdcard. I currently can only assume that the PX5 SoM respectively Rockchip boot process checks if certain files exist on any attached file system and if they do it will start recovery. Just like almost any mobile phone or ARM based hardware like routers, access points or similar I ever recovered.
Given this it will be a matter of time to figure out how to recovery-flash Android 8 on PX5 SoM. I started to have a look at what is available but the Android 8 ROM found in some file shares seems to be an OTA image and not a recovery image. Using those tools and tools like the included AFPTool (or 3rd party imgRePackerRK) it might be possible to build a recovery image. Although I am not sure if the OTA image even contains all required files. Probably not. The system image perhaps only contains updated files and might be incomplete.
Also the fact that this Android 8 image is an OTA image yields the question who is providing OTA images for PX5 units. At least I am not aware about any manufacturer distributing OTA updates.
The tools you provided also includes an interesting utility: RKOsConfig.exe
Unfortunately it's all in Chinese only but some items are obvious. It looks like a tool to pre-configure the Android ROM for specific device. Allowing to set DPI, system language, time zone, video decoder, USB and UART type and specifically also the screen type where there are 2 presets in lcdlist.ini for 1024x600 and 800x480 screens.
The toolset also contains a command-line tool (RKImageMaker.exe) and a sample batch script (mkupate.bat) which shows how update.img can be converted to sdupdate.img as well as how the update.img is packed.
Unfortunately the Android 8 OTA image seems not to include some of them like kernel.img, misc.img, recovery.img and resource.img. Likely since the OTA update does not ship them. Moreover system.img might be covered by system.new.dat but this might contain only the files which are updated via OTA and might not include some of the files.
So it needs a bit of further analysis and perhaps we also need to wait for the first update image for Android 8 units (not OTA) to appear. I have also extracted an older Android 6 update.img which contains all the required files, so I guess the Android 8 OTA update is likely insufficient but future full-image updates will provide all the data to create recovery sdupdate.img to be flashed on Android 6 units.
SkyBeam2048 said:
This indeed looks very promising. In fact if I understand properly it's able to create the directory structure on an SD card to recover even from completely busted ROM content.
It basically turns an update.img into sdupdate.img which can be flashed from an sdcard. I currently can only assume that the PX5 SoM respectively Rockchip boot process checks if certain files exist on any attached file system and if they do it will start recovery. Just like almost any mobile phone or ARM based hardware like routers, access points or similar I ever recovered.
Given this it will be a matter of time to figure out how to recovery-flash Android 8 on PX5 SoM. I started to have a look at what is available but the Android 8 ROM found in some file shares seems to be an OTA image and not a recovery image. Using those tools and tools like the included AFPTool (or 3rd party imgRePackerRK) it might be possible to build a recovery image. Although I am not sure if the OTA image even contains all required files. Probably not. The system image perhaps only contains updated files and might be incomplete.
Also the fact that this Android 8 image is an OTA image yields the question who is providing OTA images for PX5 units. At least I am not aware about any manufacturer distributing OTA updates.
The tools you provided also includes an interesting utility: RKOsConfig.exe
Unfortunately it's all in Chinese only but some items are obvious. It looks like a tool to pre-configure the Android ROM for specific device. Allowing to set DPI, system language, time zone, video decoder, USB and UART type and specifically also the screen type where there are 2 presets in lcdlist.ini for 1024x600 and 800x480 screens.
The toolset also contains a command-line tool (RKImageMaker.exe) and a sample batch script (mkupate.bat) which shows how update.img can be converted to sdupdate.img as well as how the update.img is packed.
Unfortunately the Android 8 OTA image seems not to include some of them like kernel.img, misc.img, recovery.img and resource.img. Likely since the OTA update does not ship them. Moreover system.img might be covered by system.new.dat but this might contain only the files which are updated via OTA and might not include some of the files.
So it needs a bit of further analysis and perhaps we also need to wait for the first update image for Android 8 units (not OTA) to appear. I have also extracted an older Android 6 update.img which contains all the required files, so I guess the Android 8 OTA update is likely insufficient but future full-image updates will provide all the data to create recovery sdupdate.img to be flashed on Android 6 units.
Click to expand...
Click to collapse
Hotaudio/Dasaita has a OTA update function since a few months. The update file is also from HA. I think that it is only a matter of time that a .img file from another reseller or even hotaudio will be published and then it should be possible to update
Oberbergler said:
Hotaudio/Dasaita has a OTA update function since a few months.
Click to expand...
Click to collapse
Oh, I didn't know. Are they shipping OS updates on a regular base now or announced to do? Perhaps even including Android security updates? (haha, this might be just a dream)
If they do that would be a real step ahead and a good reason to buy Dasaita/HA units in the future. Although the OTA updates are likely also shipped to 3rd party units if they run HA ROM. I wonder how HA deals with this as OTA updates will be tested on HA units only and if they break some 3rd party units via OTA update they might get support inquiries from customers which don't even have a HA unit.
But generally I regard this as a huge step ahead.
Oberbergler said:
The update file is also from HA. I think that it is only a matter of time that a .img file from another reseller or even hotaudio will be published and then it should be possible to update
Click to expand...
Click to collapse
This forum is quite active. Does anyone have any contacts to HCT?
I guess they might not want to talk to modders and developers directly...
I really like Dasaita/HA is present here and publishing regular updates. I just bought a car-specific unit with Anroid before actually knowing about MTCD or PX3/PX5 at all. Now after being in this discussions for a while my favorite seller would be Dasaita/HA. Unfortunately they don't have a car-specific model for me but for future purchases it will be my first address to check.
@marchnz - @mum1989 has an Oreo unit, he has offered to try and dump the ROM
SkyBeam2048 said:
.
This forum is quite active. Does anyone have any contacts to HCT?
Click to expand...
Click to collapse
Try their website :
http://en.hctsz.com/
SkyBeam2048 said:
Oh, I didn't know. Are they shipping OS updates on a regular base now or announced to do? Perhaps even including Android security updates? (haha, this might be just a dream)
If they do that would be a real step ahead and a good reason to buy Dasaita/HA units in the future. Although the OTA updates are likely also shipped to 3rd party units if they run HA ROM. I wonder how HA deals with this as OTA updates will be tested on HA units only and if they break some 3rd party units via OTA update they might get support inquiries from customers which don't even have a HA unit.
But generally I regard this as a huge step ahead.
This forum is quite active. Does anyone have any contacts to HCT?
I guess they might not want to talk to modders and developers directly...
I really like Dasaita/HA is present here and publishing regular updates. I just bought a car-specific unit with Anroid before actually knowing about MTCD or PX3/PX5 at all. Now after being in this discussions for a while my favorite seller would be Dasaita/HA. Unfortunately they don't have a car-specific model for me but for future purchases it will be my first address to check.
Click to expand...
Click to collapse
I have installed the HA ROM on my GS and tried once in November to update via OTA knowing that hotaudio has released here in the forum a newer ROM than the one I had installed on my unit but it didn't work. Don't know if it was because I have a GS or if they didn't release the update via OTA.
Don't expect security patches. They don't care about them :laugh:
typos1 said:
Try their website : http://en.hctsz.com/
Click to expand...
Click to collapse
OK. My question was rather towards the community if someone ever tried.
Their website leaves little hope that they are even open to a collaboration. The english page is very incomplete and only chinese page seems to ahve some Sofia and PX3 boards listed. As far as I can see they are manufacturing some standard SoM they market to resellers as we know. Not sure though about the design of MTCx main boards. As many sellers seem to have very similar designs this makes me believe they are perhaps also designed by HCT or at least there is some reference design available to all unit manufacturers. Moreover some apps on our units are developed by HCT directly. Apps which interface with the MCU. So I believe HCT either provides the design or is manufacturing the complete unit, not only the SoM.
Anyway we might actually need a translator or someone in china to get in direct contact with HCT and it's unlikely for such companies to collaborate with the community. Nevertheless I have sent them a mail asking about community involvement. Maybe I go the wrong direction here and chances to succeed are near-zero, but hey; you don't know if you don't try.
Oberbergler said:
I have installed the HA ROM on my GS and tried once in November to update via OTA knowing that hotaudio has released here in the forum a newer ROM than the one I had installed on my unit but it didn't work. Don't know if it was because I have a GS or if they didn't release the update via OTA.
Don't expect security patches. They don't care about them :laugh:
Click to expand...
Click to collapse
I wonder if the OTA does an MCU check as the Lollipop update on KLD MTCB/C units did ? You could try flashing an HA MCU and seeing if it updates via OTA after. If it does then it could be quite easy for a dev to work around it as @dsa8310 did to allow Lollipop on any MTCB/C unit.
typos1 said:
I wonder if the OTA does an MCU check as the Lollipop update on KLD MTCB/C units did ? You could try flashing an HA MCU and seeing if it updates via OTA after. If it does then it could be quite easy for a dev to work around it as @dsa8310 did to allow Lollipop on any MTCB/C unit.
Click to expand...
Click to collapse
I'm not playing anymore with MCU's since I've done exactly that what you've suggested me. The HA MCU converted my unit into a HA with many problems. When I tried to go back to GS I had the version unmatch error. Fortunately the seller exchanged my unit.
SkyBeam2048 said:
OK. My question was rather towards the community if someone ever tried.
Their website leaves little hope that they are even open to a collaboration. The english page is very incomplete and only chinese page seems to ahve some Sofia and PX3 boards listed. As far as I can see they are manufacturing some standard SoM they market to resellers as we know. Not sure though about the design of MTCx main boards. As many sellers seem to have very similar designs this makes me believe they are perhaps also designed by HCT or at least there is some reference design available to all unit manufacturers. Moreover some apps on our units are developed by HCT directly. Apps which interface with the MCU. So I believe HCT either provides the design or is manufacturing the complete unit, not only the SoM.
Anyway we might actually need a translator or someone in china to get in direct contact with HCT and it's unlikely for such companies to collaborate with the community. Nevertheless I have sent them a mail asking about community involvement. Maybe I go the wrong direction here and chances to succeed are near-zero, but hey; you don't know if you don't try.
Click to expand...
Click to collapse
Yes, the site is rubbish.
The motherboards are designed and made by each manufacturer to, as youve said, a set of standards that meet certain criteria so that ROMs and (most) MCUs are interchangeable, although each motherboard may be a different design.
Almost all sellers (HA is the only one who sells and manufacturers as far as I can remember) are entirely separate from the manufacturers and have nothing to do with the design or manufacturing.
It used to be though that "MTC" was behind the development of the SoM software, then it was thought htta HCT was behind it, in the light od @marchnz's first post I m not sure this is correct now.
Joying px5 units are not syu/fyt, FYI.
gtxaspec said:
Joying px5 units are not syu/fyt, FYI.
Click to expand...
Click to collapse
If not, do you know what they are?
marchnz said:
If not, do you know what they are?
Click to expand...
Click to collapse
Uncertain, would need access to a live unit.
gtxaspec said:
Joying px5 units are not syu/fyt, FYI.
Click to expand...
Click to collapse
There are no "joying" units - Joying are a seller, I take it you mean Shenzhen Joyous RK3368/PX5 units ?
Although I was under the impression that Joyous no longer made MTC units and had switched to making the "009" MCU (ie non MTC) Intel units.
I gather that @marchnz has seen ".syu" and "fyt" on he motherboard or SoM and thats why he suggested that in his first post.
gtxaspec said:
Uncertain, would need access to a live unit.
Click to expand...
Click to collapse
So without access to a unit what makes you say that ?
typos1 said:
There are no "joying" units - Joying are a seller, I take it you mean Shenzhen Joyous RK3368/PX5 units ?
Although I was under the impression that Joyous no longer made MTC units and had switched to making the "009" MCU (ie non MTC) Intel units.
I gather that @marchnz has seen ".syu" and "fyt" on he motherboard or SoM and thats why he suggested that in his first post.
So without access to a unit what makes you say that ?
Click to expand...
Click to collapse
Look at the kernel and file system. Fyt units are very specific. Joyous is a different reseller than joying also. Dunno what 009 unit is. FYT makes their own custom SoM with various cpu's.
gtxaspec said:
Look at the kernel and file system. Fyt units are very specific. Joyous is a different reseller than joying also. Dunno what 009 unit is. FYT makes their own custom SoM with various cpu's.
Click to expand...
Click to collapse
Joyous is NOT a seller, Joyous is the manufacturer of all "JY" units, its Joying that is a seller.
An 009 MCU unit is a non MTC Intel unit.
I dont think the kernel or software are relevant, we re talking about MTCD/E hardware not software.
I ve not seen any MTCB/C/D/E SoMs without "HCT" on them - HCT makes all MTC SoMs, at least thats what has been established over the last 3 years, but please if youve got any photographic evidence to the contrary post it here to prove otherwise.
typos1 said:
Joyous is NOT a seller, Joyous is the manufacturer of all "JY" units, its Joying that is a seller.
An 009 MCU unit is a non MTC Intel unit.
I dont think the kernel or software are relevant, we re talking about MTCD/E hardware not software.
I ve not seen any MTCB/C/D/E SoMs without "HCT" on them - HCT makes all MTC SoMs, at least thats what has been established over the last 3 years, but please if youve got any photographic evidence to the contrary post it here to prove otherwise.
Click to expand...
Click to collapse
It is relevant, because from a live system, you can tell what SoM the unit is using
Also, Shenzhen Joyous (which was a manufacturer/seller) does not currently make any PX3 or PX5, let alone any Intel units. This may have been true in the past, no longer.
Also, HCT does make a variety of SoM's, but they certainly don't make all of them.
gtxaspec said:
Joying px5 units are not syu/fyt, FYI.
Click to expand...
Click to collapse
Quite right, the JY PX5 is a STT, according to the RKOSTOOL: 深圳市齐顶电子科技有限公司 - Shenzhen Top Electronics Technology Co., Ltd. Top.
And a quick google lists the following (from the "russian forum"):
JOYING
Model: px5
Procecor: 8 core 64bit CUP Coretex- [email protected] G
Machine code: 050014390000AA55
Android 6.0.1
Assembly number: MXC89L release-reys V6.4
Kernel version: 3.10.0
stt-tec @ ubuntu1204 # 48
Tue Aug 22 17:22:39 CST 2017
APP-TP6735 0.0.51
MCU-TP6735 4.31
BT-SD / 2017: 09: 13: 17: 38: 49 fw: Jun 29 2017 23:57:52
.deleted
Please ask
https://www.facebook.com/profile.php?id=100010581348702
He is a member in this forum.
He can speak English and have contact to hct
Im sure he can help. I know that he listen to any wish and want help the community to get further...
---------- Post added at 03:42 AM ---------- Previous post was at 03:37 AM ----------
Also try to contact boyka from joying team his skype name is "mcloge"
Maybee he can help to
Related
I have an Eonon GA2114 - rk3188, 800*480, KLD2 2.77 MCU, BC6B BT board
With the original Eonon ROM bluetooth is unusable. There is no default device name or PIN. If I type in these, they disappear after reboot. It does not detect either phones or OBD, nor is it detected by phones.
With other KLD ROMs bluetooth is active, can be paired to both phones and OBD but all sound is muted during calls (both ways)
With Joying ROMs, including Malaysk, BT works as it should.
This is clearly a software issue, anyone has any clues about where should I start looking? Are these manufacturers using different BT stack implementations maybe?
Anybody can provide a working rk3188 800*480 Eonon ROM? Not the October 19 ROM also available on this forum, that one has the issue described above.
Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.
Sn00k said:
Hi,
I'm facing the same issue, I have an GA5153V device and contacted Eonon about that but hey keep sending me wrong MCU version and ROM. Can You please tell me which MCU version do You have?
It would be great if someone posts working version of Eonon ROM.
Click to expand...
Click to collapse
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.
m00n61 said:
waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
At present there is no need to have a bugged (and unfixed by Google) Lollipop 5.0.x on these units, Kitkat 4.4.4 is still the best IMHO.
We'll see in the future what will happen with Marshmellow...
m00n61 said:
My MCU is a KLD2.
I have requested Eonon to send a compatible ROM, even older, but they say it's the only one available. The ROM they are sending id the one available on this forum in the Factory ROM thread. Eonon appear to just brand generic units and have no technical personnel. I gave up getting a competent answer from them. For now I am on Booroondook's ROM, waiting for Joying to release a Lollipop version.
Click to expand...
Click to collapse
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!
Sn00k said:
Since Eonon is keep sending me KLD2 based mcu even I have KLD(MTCB-KLD-v2.78) by default I cannot use this version because FM radio is not working. I said that to them but again they sent me KLD2, the I gave up on them and now trying to fing some solution to make bluetooth to work.
Can You please tell me where did You download current ROM that You are using?
thx!
Click to expand...
Click to collapse
MCU and OS ROM image are independent, even if the Chinese keep sending both you can burn only the Android ROM and leave the MCU untouched.
Anyway, I am currently using this ROM. A more detailed installation procedure is in the first post of the thread.
Go to factory settings and adjust the bt module there. Code is 126.
I was seeing the same thing when I found that option and began playing around.
XTRONS TD702A
mcu version mtcb-gs-v2.73
android 4.4.4_26082015
build rk3188-eng4.4.4 26082015.16:09:23
800x480 as per product webpage spec sheet
http://xtrons.com/td702a-android-4-...itor-with-screen-mirroring-function-obd2.html
i would like to flash Malaysk ROM. i believe i'm compatible but would like some reassurance before i screw something up. do i use update_4_4_4_FUSE_800X480_RK3188_12_MAL_13_02_2016. there is also a file Launcher2mtc3_JY.apk in the directory with update_4_4_4_FUSE_800X480_RK3188_12_MAL_13_02_2016, should i install that or is the stock launcher better?
i also see discussion about updating mcu. what does mcu mean and do i need to update mine with MCU_GS_2.55_Sleep_Musik or is my current mcu more up to date?
i assume there is no twrp for android decks?
thanks in advance for anything yall can teach me about my devise.
This thread is to document MCUs found to be cross-compatible between MTCD units, which includes PX3 and PX5 variants, which share identical mainboard hardware and MCU Chip STM32F091.
The following MTCD & MTCE (as of v2.56) MCUs have been validated as cross compatible on 1024x600 units:
- MLT - 01/07/17 - caution - has resulted in issues for some @leonkernan
- JY
- KBT - 08/12/2017 - thanks @abagos
- KD (v2.40_2 - enables bluetooth hands free in both front speakers)
- KGL
- KSP thanks @Overmann
- GS - Note "version unmatch" error and fix below No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80 - March 2018
- GS compatible on MX (see post #513)
- HA (v2.56 06/07/17 - note v2.52 on enables "shutdown delay when acc off" menu) HA MTCE (30/09/17) V2.65 https://www.sendspace.com/pro/dl/ufie8k
See this thread for pics where MCU HA and KD has been applied on JY. https://forum.xda-developers.com/showpost.php?p=72737797&postcount=640
I initially upgraded to KD 2.40, then HA v2.52 after first exporting the MCU settings.
Note that I had to reapply MCU settings in [factory sertings] to configure radio, LED, bluetooth, hardware keys, volume levels between radio, bluetooth, system etc.
MCUs were previously thought to be manufacturer specific - e.g. HA, JY, GS, KD, however I have found that they are compatible and of interest where there is either a specific issue with your MCU (e.g. bluetooth out of one speaker, to enable PX5 sleep mode control) or the vendor has long ceased to support & release updates - such as JY.
MCU cross-compatibility became of interest to me when I upgraded my JY [MCU v2.06_2] PX3 with a HCT PX5 SOM and wanted to enable the MCU specific menu item [shutdown delay when ACC off] to control sleep as found on HA/Dasaita.
I first noted that from an XDA post listing JY an KD v2.06_2 being identical and on that assumption, upgraded to KDv2.40_2, which successfully applied - but had to reconfigure factory settings.
Following on, I found a post which has an image of a GS board & MCU chip - noted it was identical to the MTCD JY MCU chip [STM32F091] - then came across a post where a user had inadvertently applied a MTCD GS MCU to a MTCD JY without bricking it.
I then started comparing same version number firmware files from various manufacturer MCUs with a text compare tool. From this work, I had enough info to compare the latest HA v2.52 and conclude it 'should' be compatible. Indeed it is.
As always, check first (suggest confirming MTCD, MCU Chip part number, view/compare the fw files, ensure you have original MCU FW, backup MCU settings or document the settings to ensure your hardware controls, volume control, bluetooth, radio, canbus etc are setup correctly). Apply at your own risk.
Please post your results and I will update this thread.
Updates:
UPDATE: 26/06/2017 Users of 800x480 Users must also apply file[dmcu.ext], a text file containing:
For PX3 --> screen:3
For PX5 --> screen:1
01/07/17 - MLT
06/07/17 - KGL confirmed and new HA v2.56
30/09/17 - MTCE MCU confimed compatible
08/03/18 - MTCE JY/GS/HA compatible - No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80
GS Specific Notes:
Oberbergler said:
For all those with a GS: Our unit is compatible with the MTCE MCU but you have to restore your settings and maybe to manually reconfigure your touchscreen and buttons. There is a simple function to do this in the factory settings (126) which is called key study. My touchscreen was also swapped by the x axis. I had to go with the swapped touchscreen into the settings, configure it, reboot the unit and everything was fine. For the buttons you have also the possibility to use short press and long press buttons, which is great because our units (at least mine) has only five buttons and no return button. So I use now the power off button as return in short press mode and power off in long press
Click to expand...
Click to collapse
Version unmatch see this post where user resolved by reapplying MCU AND Software APK Fix Here
- Attached Version Unmatch APK fix to this post, thanks @Wadzio
GS Configuration Settings file:
Bose321 said:
Here it is: https://gerbenbol.com/android/dmcu.cfg.
Click to expand...
Click to collapse
Do not dilute this thread by posting "how-to" questions such as - how do I update the MCU, what unit do I have, can I do it, how do I find factory settings, etc. This thread is to document cross-compatible MCUs and the fixes they apply.
Hi! Confirmed, I've upgraded to PX5 (JY UL135). Flashed KD2.40 over JY 2.06_2 then flashed HA 2.52 and everything is working as it should be. Thanks for your work.
I can confirm a cross compatibility as well.
My Unit is a xtrons device with die MCU firmware GS 2.43 and yesterday i did flash the HA 2.52. But be sure to save your mcu config first. Otherwise the hardware buttons won't do what they were supposed to do. But after flashing the firmware and restoring the config, everything is back to normal.
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.
f1x said:
Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.
Click to expand...
Click to collapse
No, you are wrong there - the letters very definitely relate to the manufacturer, NOT the CAN Bus profiles KLD = "Klyde" KGL, = "Kai Ge Le", JY = "Joyous" etc, this has been established for years.
The seller has NOTHING to do with the software at all.
The CAN Bus profiles are named in factory settings
On MTCB/C headunits there was a slight difference in the code between MCU types so they were not interchangeable (apart from BN and HA), it would seem that on MTCD units there is no such variation in the code.
Does this also apply to LM_ (Erisin) MCUs?
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
SpeedyCarv said:
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
Click to expand...
Click to collapse
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
typos1 said:
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
Click to expand...
Click to collapse
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
SpeedyCarv said:
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
Click to expand...
Click to collapse
Maybe read it again ?
Basically, you could risk trying it - MTCB/C units can be restored if the wrong MCU is flashed, maybe MTCD units could be restored if the wrong MCU is flashed also ? But maybe not, so that is your decision whether to try or not.
Otherwise stick to what @marchnz has said and do not try it.
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Cant make it any clearer than that.
typos1 said:
Maybe read it again ?
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Click to expand...
Click to collapse
Not necessary to read again. I already knew that. That's what i tried to express in typing "my level of knowledge has not grown" Sorry if i write misunderstandable, i'm not a native speaker (German).
Thank you again for your time and patience
typos1 said:
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Click to expand...
Click to collapse
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Wout2426 said:
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Click to expand...
Click to collapse
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
Or, once mcu has been upgraded, you can remove the mcu update (.img) from the root of the gps card and apply the config (.cfg) on the root of the gps card separately - by running the 'upgrade MCU', it will see .cfg file and apply it.
Update for 800x480 users who update to the latest MCU - you must also apply a dmcu.ext
DMCU.EXT details
DMCU.EXT & screen resolution setting/howto/details
dmcu.ext details for PX5 800x480
That said - why is anyone purchasing a PX5 unit with 800x480?!?!
KD --> HA for 800x480 Screen
I have had quite an experience over the weekend, but am able to report successfully updating a PX3 MTCD_KD unit to a PX5 with the HA2.52 MCU Code.
For those of us with 800x480 screen sizes, as now noted in the main thread, we need to create the dmcu.ext file with the appropriate screen size to be flashed with the dmcu.img file.
Just a note that if you run across the issue of not having the appropriate resolution; don't freak out.
One interesting note I hadn't mentioned before is that after the PX5 started thinking it was 1024, I replaced it with the PX3. The PX3 booted thinking it was 1024 also. After reverting the PX3 to 800 (flashing with screen:3), I replaced the PX5. The PX5 however, did not revert back to 800, but remained at 1024. The PX5 did not revert back to 800 until after I reflashed the MCU, specifically stating it was to be 800 (screen:1).
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Bose321 said:
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Click to expand...
Click to collapse
Yeah, thats right - the "d" is just there to show its an MTCD MCU not an MTCB or MTCC one.
1-2-Hak said:
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
Click to expand...
Click to collapse
The shutdown option is under System Settings --> extra settings. You wont find it in the factory settings. Just FYI.
Which dmcu.cfg did you use? I might be wrong, but it seems to me it might be dangerous to use different dmcu.cfg files with different versions of the MCU Code.
Hi All,
I accidentally messed up with my unit PX5 (buttons are not working - unit does) and I would like to reflash the MCU.
The original version the unit came with is MTCE_GS_V2.84._3 but I cannot find it anywhere.
Does anyone have an idea where I can find it?
Thanks a lot
set buttons in factory menu.
Already tried and added a new post reply here https://forum.xda-developers.com/showpost.php?p=77438369&postcount=1968.
When i try i get no response. Should i long press ?
I have the files...how do i send?
You will find all the updates and MCU files for all units here: https://yadi.sk/d/umCvHqCDzHccr
Brialliant !!!!! thanks for the link
no worries glad to be of service
ThiBor1 said:
You will find all the updates and MCU files for all units here: https://yadi.sk/d/umCvHqCDzHccr
Click to expand...
Click to collapse
I see here https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 8.0/GS that only ROMS for PE series are available . Mine is a Xtrons PB series (PB68WRJP). May I use the PE ROM ?
they will be fine with your pb i have the audi TT pb unit and have used these files for mine without any problems, as far as i am aware the px5 units are all the same anyway.
ThiBor1 said:
they will be fine with your pb i have the audi TT pb unit and have used these files for mine without any problems, as far as i am aware the px5 units are all the same anyway.
Click to expand...
Click to collapse
I asked because my seller gave to me 2 versions of the update file a couple of months ago. First he sent the PE version and later, before I updated my unit, he sent the PB saying that this is the right one for my unit.
I’m new to the android radio scene, asking for some help here. I’ve been reading in the forums here about “version unmatch” and the corresponding MCUs. I have a new QCM6125 running android 12. Things were working fine, but there were a few bugs. The seller sent me an update “6125 GS16 12.0 20220928”. I uncompressed it, put it on a usb, and updated the radio with “update.zip”. Upon reboot I got the version unmatch and beep. I mentioned this to the seller, they tried to send me another update, but it quits with an error.
Am I correct in assuming I shouldve got a CHS update, and they gave me a GS? What do I need to fix this?
Have a look through MTCD forums, there's quite a lot of information covering that.
Failing that, what does the reseller suggest, have they provided any support and does that work?
marchnz said:
Have a look through MTCD forums, there's quite a lot of information covering that.
Failing that, what does the reseller suggest, have they provided any support and does that work?
Click to expand...
Click to collapse
Thanks for getting back to me. I've been scouring the MTCD forums the past few days. Learning a lot (seeing your name a lot too), but not necessarily getting where I need to yet. Frankly it seems to be leaving me with more questions than answers.
So the seller's response to my "version unmatch" problem was to ask me to downgrade (assuming A10), and sent me another file (HCT7B_SC138_10.0_OTA(20220520).zip) which quits the install and goes into recovery mode. I made a youtube vid of it here (per seller request):
Later they sent me a third update (6125 GS16 2022.3.3.zip) which by the name looks to be similar to my first A12 update, but an earlier version? It quit and did the same thing as the A10 downgrade above.
From the forums and my recovery screen I see that I DON'T have a Rockchip, and thus downgrades might not be possible? Also, the CHS seems to be more rare. I did see the MTCH_CHS_V3.80 on 4pda (my current is v3.78), but can't seem to download it (404 error). My canbus decoder box says it’s a CHS, so I'm assuming CHS is the correct MCU? If so I'm not sure where the "version unmatch" error is coming from. Could that be something I've changed in the factory settings, like the steering wheel setting?
I've tried the first update that caused the version unmatch problem (6125 gs16 12.0 20220928.zip) a second time, and it installs and completes just fine, but doesn't get rid of the problem.
I read about the version unmatch unlock app, and read it didn't work with A12, tried it anyways, and it quit like others said.
I've been ghosted by the seller for about 2 weeks now. So on one hand I feel like I'm stuck, but from reading here, it could be as simple as updating the MCU? Any help is greatly appreciated.
What processor do you have? I think Qualcomm Snapdragon 665 and that is a different processor than in these threads, PX is being addressed here. For MTCD/E, the Red "version mismatch" is an MCU problem, not a firmware problem. Did the seller not include the MCU-dmcu.img update with the first firmware update, which was also installed when you installed the firmware? You probably installed another manufacturer, first find out what you had originally, if you don't know, write to the seller. You can try McuUnmatchUnlock app, but I don't know if it works on Qualcomm Snapdragon 665, you have to try it yourself:
MTCD - Verified Cross compatible MCUs
This thread is to document MCUs found to be cross-compatible between MTCD units, which includes PX3 and PX5 variants, which share identical mainboard hardware and MCU Chip STM32F091. The following MTCD & MTCE (as of v2.56) MCUs have been...
forum.xda-developers.com
Instructions:
Solution for 'Version unmatch' (I hope final)
I know that this topic has already been discussed many times in many threads (most in MTCD - Verified Cross compatible MCUs). I also know that there is a known solution to this problem. However, there are users who report that they still have a...
forum.xda-developers.com
Or, if you haven't done any MCU update and you're sure you have CHS, then MTCH_CHS_V3.80 is also here:
Яндекс
Найдётся всё
disk.yandex.ru
There is not much about Qualcomm Snapdragon 665 here even on 4pda, I tried the search engine:
Search results for query: Qualcomm Snapdragon 665
forum.xda-developers.com
There is one Qualcomm Snapdragon 665 thread on the 4pda with MCU: MTCH_xxx, but not much here either:
Головные устройства Qualcomm Snapdragon 665 (QCM6125) 8 ядер Android 10 - Обсуждение - 4PDA
Головные устройства Qualcomm Snapdragon 665 (QCM6125) 8 ядер Android 10 - Обсуждение, [Головное устройство][Android]
4pda.to
Pavel-71, thanks for the response. Yes it is a Qualcomm Snapdragon 6125, 4G/LTE, 6GB RAM, 128GB ROM, 8-core I bought from AVIN. You are correct that they did not give me a separate MCU *.img file. All that was located in the files they provided me was the android "update.zip" file. I have never updated the MCU, until now I had assumed it was included in the update.zip file. I read more last night that it is not so. Android is update.zip, MCU is dmcu.img. The seller's instructions to me make no mention of an MCU image.
I had requested from the seller 3 days ago, when I first started reading about this, they send me the MCU image and config file. I've heard nothing back.
So if I understand what's happening here, it sounds like my MCU (CHS) is likely the original, because I never updated it with an *.img file, and it’s possible the seller gave me a snapdragon version of A12 that was meant for a different MCU, causing the mismatch? If so, wouldn't my android version be wrong, and shouldn't I need an android version made for CHS? Is there a way to tell which MCU the android version is made for?
I also read that the Wifi version can't be installed on the 4G/LTE version, and it's possible if the first is wrong, the second and third files that wouldn't install could be wifi only versions of Android, when I have a 4G/LTE.
In my opinion, you can't downgrade to android 10 using update.zip, for that you should use some QPST tool and the update.img file, which contains the recovery of android 10. And the installation is done from a computer with a usb cable, but I'm just guessing. I noticed you didn't select wipe data and flash format before updating. Try updating again with 6125 GS16 12.0 20220928, and this time mark data wipe in the table, I think when you installed the GS update on CHS, without data wipe, it gave a mismatch error. The German company M.I.C. it has its updates on Qualcomm Snapdragon and there is also a guide where it recommends wiping the data to remove any errors:
SYSTEMUPDATES für Snapdragon 665
Passt für alle Geräte mit Prozessor Snapdragon 665 (QCM 6125): AV8V7(-Pro) AV9V2(-Pro) AU10 AU7 AVT7(-Pro) AVTO7(-Pro) AF7 AO7 AO8 AB9
www.mic-autoradio.com
Pavel-71 said:
In my opinion, you can't downgrade to android 10 using update.zip, for that you should use some QPST tool and the update.img file, which contains the recovery of android 10. And the installation is done from a computer with a usb cable, but I'm just guessing. I noticed you didn't select wipe data and flash format before updating. Try updating again with 6125 GS16 12.0 20220928, and this time mark data wipe in the table, I think when you installed the GS update on CHS, without data wipe, it gave a mismatch error. The German company M.I.C. it has its updates on Qualcomm Snapdragon and there is also a guide where it recommends wiping the data to remove any errors:
SYSTEMUPDATES für Snapdragon 665
Passt für alle Geräte mit Prozessor Snapdragon 665 (QCM 6125): AV8V7(-Pro) AV9V2(-Pro) AU10 AU7 AVT7(-Pro) AVTO7(-Pro) AF7 AO7 AO8 AB9
www.mic-autoradio.com
Click to expand...
Click to collapse
Thanks for getting back to me. I looked at that MIC page you linked to, followed the instructions, checked wipe data and did the restore with the above mentioned update.zip file. The update completed successfully, it did erase all my data, apps, and settings. It did NOT fix the version unmatch issue though.
While I'm here, my CPU says, AArch64 Processor rev 2 (aarch64) @1.8GHz (x8)
Too bad it didn't help. Hard to advise now. If the seller doesn't call and send the original GS update, I would try the McuUnmatchUnlock app. If that doesn't help, try updating MTCH_CHS_V3.80. The last option, but I don't know if it's safe, is to try an update from M.I.C. I really don't know how it is with the Qualcomm Snapdragon 665, but firmware from other vendors can be installed on PX processors without any problems, I installed HCT7, HCT4, GS16, M.I.C., CHS, Hal9k firmware on the PX5 without any problems. The problem is with the MCU update, here when using another manufacturer unmatch can occur, sometimes it helps to use the original manufacturer or the McuUnmatchUnlock application. For more serious problems, a special programmer is needed. Try to register on 4pda and ask here, maybe they can give you better advice, CS-X is excellent, it has MCU thread in the message.
Pavel-71 said:
Too bad it didn't help. Hard to advise now. If the seller doesn't call and send the original GS update, I would try the McuUnmatchUnlock app. If that doesn't help, try updating MTCH_CHS_V3.80. The last option, but I don't know if it's safe, is to try an update from M.I.C. I really don't know how it is with the Qualcomm Snapdragon 665, but firmware from other vendors can be installed on PX processors without any problems, I installed HCT7, HCT4, GS16, M.I.C., CHS, Hal9k firmware on the PX5 without any problems. The problem is with the MCU update, here when using another manufacturer unmatch can occur, sometimes it helps to use the original manufacturer or the McuUnmatchUnlock application. For more serious problems, a special programmer is needed. Try to register on 4pda and ask here, maybe they can give you better advice, CS-X is excellent, it has MCU thread in the message.
Click to expand...
Click to collapse
I initially did try the mcuunmatchunlock.apk, and the app quits and fails upon opening. It was one of the first things I tried when I found this forum. I appreciate the effort and attempt, felt a little alone and on my own here until I found this forum.
If I understand what I’ve read in the many pages here, wouldn’t getting another GS android cause the same issue? Correct me if I’m wrong, but if I have a CHS MCU, I either need an android built for CHS & 4G/LTE (from seller), OR attempt to change the MCU to GS, which could potentially brick me if not compatible.
Sorry I wrote it wrong, of course I meant the original CHS firmware. Of course you are right about MCU, you should use CHS.
Well, the seller (AVIN) finally got back to me, "Sorry for the inconvenience. You can send back the unit for a replacement." I would've rather just installed the correct update.zip file, but this is better than nothing. Thanks for the help, and at least I found a new interesting forum.