Develop Bugs

Upgrading MCU..

HI ,
Looking at upgrading MCU My unit is GS so I was going to flash this..
FOR GS
GS v.2.55 with sleep and redesigned sound processor from darkleo - MCU_GS_2.55_Sleep_Musik.rar
Im just a little confused about the following instructions as they talk about resolution, does this apply only when flashing the rom and not the MCU?
BEFORE UPGRADING YOUR UNIT YOU MUST KNOW
MCU your unit, there are many (KGL, KGL1, KGL2, KGL3, KGL4, KGL5, KLD, KLD1, KLD2, JY, GS, KYD, MD, BN, HA, MX), If you install the wrong MCU, you will brick your unit.
To know which one you have. Go to Settings -->About
If still not clear, see: here or here.
If you cannot find it here, it probably means that you are in the wrong thread.
Resolution of your unit. 800x480 or 1024x600. If you install the wrong ROM, you will brick your unit.
Chip of your unit RK3066 or RK3188. It does not really matter, ROMs and MCU are compatible between chips.
Thanks

Does not matter for mcu. Just make sure you use the correct mcu (same letter combo) and you may need to change settings in your factory settings menu for radio. Make note of your old mcu so that you can go back if required

Thanks, I'll try it tomorrow. There is only one available mcu on here for the GS model.
I'll go with that.

frontpanel buttons not function anymore after update

hi all!
i post for the first time in this section so apologize if i'm wrong or post in the wrong section.
I'm having issue with my RK3066 MTCB KGL 1024*600 HU (which commercial name is erisin ES9007a) since a ask manufacturer to send me new update to fix some bugs on my HU.
Since a putted in the MCU and update.img and make update, i lost my physical button in front and can't open front panel to access SDcar slots behind. Other physical buttons in front don't function anymore too like : vol+, vol-, power, eject....
I tried several other mcu find in the forum and i'm actually with : MCU v2.83 but i did no changes. I also tried v2.78 and v2.80....
The error i've done is that i haven't make any save before updating. Erisin don't ask me to do this.
SWC mapping is OK.
Anyone can help me please ?

kaygone said:
hi all!
i post for the first time in this section so apologize if i'm wrong or post in the wrong section.
I'm having issue with my RK3066 MTCB KGL 1024*600 HU (which commercial name is erisin ES9007a) since a ask manufacturer to send me new update to fix some bugs on my HU.
Since a putted in the MCU and update.img and make update, i lost my physical button in front and can't open front panel to access SDcar slots behind. Other physical buttons in front don't function anymore too like : vol+, vol-, power, eject....
I tried several other mcu find in the forum and i'm actually with : MCU v2.83 but i did no changes. I also tried v2.78 and v2.80....
The error i've done is that i haven't make any save before updating. Erisin don't ask me to do this.
SWC mapping is OK.
Anyone can help me please ?
Click to expand...
Click to collapse
You need to ask the manufacturer for the correct MCU.

kaygone said:
hi all!
i post for the first time in this section so apologize if i'm wrong or post in the wrong section.
I'm having issue with my RK3066 MTCB KGL 1024*600 HU (which commercial name is erisin ES9007a) since a ask manufacturer to send me new update to fix some bugs on my HU.
Since a putted in the MCU and update.img and make update, i lost my physical button in front and can't open front panel to access SDcar slots behind. Other physical buttons in front don't function anymore too like : vol+, vol-, power, eject....
I tried several other mcu find in the forum and i'm actually with : MCU v2.83 but i did no changes. I also tried v2.78 and v2.80....
The error i've done is that i haven't make any save before updating. Erisin don't ask me to do this.
SWC mapping is OK.
Anyone can help me please ?
Click to expand...
Click to collapse
Did you try and grab a few KGL mcu's from here? I would try a couple more, you should be able to use any of them.

i have tried 3 different MCU, should i try other MCUs ?

kaygone said:
i have tried 3 different MCU, should i try other MCUs ?
Click to expand...
Click to collapse
No, you should ask the manufacturer for the correct MCU.

halloj said:
No, you should ask the manufacturer for the correct MCU.
Click to expand...
Click to collapse
You think i have the wrong one ? I can't find the good one here ?

No one to help me please ?

Have you asked the manufacturer how to get to android recovery screen?
How do you get to the recovery screen ?
Try doing a wipe cache.

PX5 Rockchip Tools - FW recovery without Hardware Mods

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

MCU wanted for MTCE_GS_V2.84._3 (dmcu.img)

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.

Dasaita - Latest MCU and Updates for Dasita PX6 1280x720 MAX10

For Dasaita PX6
Updates on Dasaita website: https://www.dasaita.com/blogs/news/update-firmware
-----
Older versions:
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment MTCE_HA_V3.57.zip
v3.60: View attachment MTCE_HA_V3.60.zip
v3.62: View attachment MTCE_HA_V3.62.ZIP
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment dmcu-1280x720.zip - use it if you got a wrong resolution after flashing MCU image and you need to restore your unit to 1280x720 resolution
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)

orik13 said:
For Dasaita PX6
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment 5111231
v3.60: View attachment 5111233
v3.62: View attachment 5111235
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment 5111237 - use it if your unit has 1280x720 resolution, otherwise you can get 1024x600 or lower instead (no worries in this case - just reprogram)
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
Click to expand...
Click to collapse
Before even considering this read in the other thread what happen to my unit. User name halloj,

orik13 said:
For Dasaita PX6
Android 10:
HA3_rk3399_10.0_ota(20200915)升级包 : https://yadi.sk/d/ylg0cKBTQo4P1Q
HA3_rk3399_10.0_ota(20200724)升级包 : https://yadi.sk/d/AWDSmBsznvL3gQ
MCU images - unzip and copy "img" file to flash (sd/usb):
v3.57: View attachment 5111231
v3.60: View attachment 5111233
v3.62: View attachment 5111235
DMCU - unzip and copy to flash (sd/usb) together with MCU image:
for 1280x720 units: View attachment 5111237 - use it if your unit has 1280x720 resolution, otherwise you can get 1024x600 or lower instead (no worries in this case - just reprogram)
All works for me on Dasaita PX6 MAX10 (the unit came with Android 10 from the factory)
Click to expand...
Click to collapse
Anyone reading this
*** Do not flash the DMCU.ext listed here together with the MCU ***
OP please edit this post, there is NO reason to flash dmcu.ext when flashing the same vendor MCU.
Suggest expanding on the comment "no worries just reprogram", with clear examples if making this statement.

marchnz said:
Anyone reading this
*** Do not flash the DMCU.ext listed here together with the MCU ***
OP please edit this post, there is NO reason to flash dmcu.ext when flashing the same vendor MCU.
Suggest expanding on the comment "no worries just reprogram", with clear examples if making this statement.
Click to expand...
Click to collapse
I edited it to make it more clear. Your comment is not absolutely correct: it is based on my own experience. Similar issues can be found by googling and even here at xda

Hi all I am a bit confused by how many different downloads please excuse me as a noob and first time flashing my PX6
My question is can I just jump from 3.5.8-1 to the latest 3.6.2 I believe and what files exactly do I need to load onto a flash drive.
Your help in advance is much appreciated. Cheers J
I am running a MTCE HA running 3.5.9

ToyotaJay said:
Hi all I am a bit confused by how many different downloads please excuse me as a noob and first time flashing my PX6
My question is can I just jump from 3.5.8-1 to the latest 3.6.2 I believe and what files exactly do I need to load onto a flash drive.
Your help in advance is much appreciated. Cheers J
I am running a MTCE HA running 3.5.9
Click to expand...
Click to collapse
Suggest NOT changing your MCU unless resolving a known issue. Same for Android. This is a head unit, constantly updating isn't necessary.

Update for mic issue
Hi Experts! If I want to update my Dasaita PX6 Max10 is there any preferred order which update to do first OTA or MCU? In case of OTA update at starting is it necessary to click on WIPE AND FORMAT FLASH option? Somebody is doing this, somebody is doing that... When is it suggested?
The reason why I planning to switch to latest update because during calls my mic is working strange, sometimes the others cannot hear me properly. They are complaining about low volume and faded voice. (If they are calling back they says it is better...) Have you experienced the same thing?

halloj said:
Before even considering this read in the other thread what happen to my unit. User name halloj,
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=83671635&postcount=3655

gomoriz said:
Hi Experts! If I want to update my Dasaita PX6 Max10 is there any preferred order which update to do first OTA or MCU? In case of OTA update at starting is it necessary to click on WIPE AND FORMAT FLASH option? Somebody is doing this, somebody is doing that... When is it suggested?
The reason why I planning to switch to latest update because during calls my mic is working strange, sometimes the others cannot hear me properly. They are complaining about low volume and faded voice. (If they are calling back they says it is better...) Have you experienced the same thing?
Click to expand...
Click to collapse
Are you sure it is not a h/w issue? Did you try other mic?

orik13 said:
Are you sure it is not a h/w issue? Did you try other mic?
Click to expand...
Click to collapse
I use the internal microphone, not yet tried an external one. I checked the mic with apps, basically it is working however its volume seems to be a little bit low, but it is not faded. I feel it is rather a noise suppression issue (coming from sw side), therefore I hope that an update could help.

orik13 said:
I edited it to make it more clear. Your comment is not absolutely correct: it is based on my own experience. Similar issues can be found by googling and even here at xda
Click to expand...
Click to collapse
I respectfully disagree based on years of experience: there's no need to flash the MCU configuration file DMCU with an MCU that matches the manufacturer of your head unit. I.e. HA to HA, JY to JY etc.
Your well meaning advice resulted in a configuration not appropriate (which messed up the screen) for another members screen type/resolution.
The 'similar issues' stated are probably your misunderstanding of what the DMCU file is and possibly where others have installed a different vendor MCU. E.g. GS on HLA

Hello, with dasaita px6 android 10 1024/600 firmware HA3, the update "HA3_rk3399_10.0_ota (20200915) 升级 包" and MCU "MTCE_HA_V3.62": all is ok , thank you

A few questions...
1) Anybody able to modify steering wheel controls? I open the app and it is blank.
2) Also, can you summon siri/google via the steering wheel when in carplay/android auto?
3) I have an OBD dongle but am unable to get the headunit to connect to it. I see it in the available devices but nothing happens after i select "yes" to connect.
I have the max10 600p resolution version for highlander. A canbus was included and I am able to change vol/toggle modes.

h0va4life said:
A few questions...
1) Anybody able to modify steering wheel controls? I open the app and it is blank.
2) Also, can you summon siri/google via the steering wheel when in carplay/android auto?
3) I have an OBD dongle but am unable to get the headunit to connect to it. I see it in the available devices but nothing happens after i select "yes" to connect.
I have the max10 600p resolution version for highlander. A canbus was included and I am able to change vol/toggle modes.
Click to expand...
Click to collapse
When you install a harness with a CAN adapter the steering wheel signals a routed for you to the CAN decoder box. It worked for me to reroute them to my own circuit. It should be equally fine to connect them to the KEY1 and KEY2 inputs, that is if your car has resistive buttons and only one or two. Then you can program them as desired.

Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?

woggles said:
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
Click to expand...
Click to collapse
I noticed that the first time I installed that update, then I went back to the prior version I had, one more time I gave it a try and I started to try to remove that annoying notification, but then I thought why waste time on that, also I notice that saving a screenshot was giving me an error, so once again I went back to the prior version I had installed.

I can’t decide whether to put this up or Malayk’s ROM. I don't really need pre-installed programs, I know which launcher, music player, etc.. I want to use, but there may be settings in it that I can't solve on this ROM.

woggles said:
Flashed 20200915 and the 2.62_1 (with a different dmcu.ext provided by dasaita that had screen:18 inside it). Everything has been working great but there is an annoying notification everytime I switch the car on that shows the version number - is there anyway to get rid of this?
Click to expand...
Click to collapse
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694

bad for me
thienthanty said:
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
Click to expand...
Click to collapse
hello, with this firmware "HA3_rk3399_10.0_ota (20201016) 升级 包", I can no longer make a call with "google voice".

thienthanty said:
Try
https://forum.xda-developers.com/showpost.php?p=83767241&postcount=3694
Click to expand...
Click to collapse
Thanks, the annoying pop up is gone but as another use mentioned using call x from Google Assistant doesn't work anymore!