//MTCE_LM not LS, can't edit the title anymore.
Changed customer version from 1 to 3 and after reboot, i have no screen and no buttons working.
Only after car power is cut off (5-10min), the unit comes back but shuts down within 10-15 sec, not enough to quickly go to mcu config and change back to "1". Then nothing works, as if it doesn't get power anymore. I unplugged it and tried to hook up a miniHDMI cable but there's no connector on this board....not sure i can even get to recovery, but i'll try again tomorrow.
I have an older v3.06 LM MCU but no working config, so i hope to get into recovery somehow and flash both.
I suppose any LM MCU version would do, along with a CFG file, as long as it's version 1 (recognizable from _1 after mcu version or check in factory settings-other-customer version "1")
does anyone have an idea where to change customer version in a dmcu.cfg using hex editor?
or is it possible to connect and edit the MCU values stored on the unit itself?
it's a PX5 MTCE LM unit, ultraslim format.
https://www.aliexpress.com/item/Eun...-Stereo-GPS-for-VW-Passat-B6/32866279122.html
Related
Hi,
so I am kinda new to this and wanted to upgrade to 5.1.1 below is the initial information.
Its a Roadmaster AN-111 GMC (if it matters)
It was MTCB - KSP 2.86
upgraded to MTCB KSP 2.89(KSP_11-28-2016_1.99_dmcu.img)
Firmware was 4.4.4_11032016
I installed the KLD - 2.1.1 december update
now the system boots up but does not show any display, if i plug in a USB it starts to play songs. All hardware button BEEP when i click so does the buttons on steering. I
I can go into recovery but I continuously receive the no sd card - cant post a picture yet
any chance of recovery please?
Hello,
Are you sure the MCU upgrade you did was to KSP 2.89 ? The filename you gave says something else: KSP_11-28-2016_1.99_dmcu.img (notice the 1.99 in the filename).
That would mean you did a MCU downgrade. Try flashing the MCU back again (i have KSP mcu too, not sure which version, i may be able to help you).
Regarding 5.1.1 update, i have the same behavior. I do not see the "desktop" with all the icons, but i see toast messages, popups, the "preparing to shutdown" window, so, maybe display driver problem ?
Hi
I recently returned my PX5 MTCD unit (purchased through Amazon) as it kept switching the speedo to kph. Since I've returned it Dasaita have sent me a sendspace link to a 500mb fix which they reckon will stop the issue. I do remember seeing others with the same problem so thought I'd share here.
This was for a Peugeot 208 UK 2015 incidentally. I'd previously tried Canbus updates, new ROM's and every Canbus setting with no luck.
If this does fix the issue please let me know as I'll probably repurchase the head unit. I've re-uploaded the file to Google Drive as i have unlimited storage there.
Here you go for the file:
Update steps：
1. Check whether the wiring is plugged rightly and the canbus is plugged in rightly.
2. Prepare a USB flash drive，format the usb, only put the CANBUS.UPDE file in the folder into the root directory of the USB flash drive.
3. Insert the USB flash drive into the navigation USB interface and check if the navigation correctly reads the USB flash drive data.
4. Enter the system settings, click the factory settings, enter the password: canupdates
5. Navigation prompt download, wait for the prompt download to complete or the machine to restart, the upgrade step is completed, then unplug the U disk
Special attention: The upgrade process is about 20 minutes, and our device is forbidden to power off during the period, otherwise the canbus will be scrapped directly!!!
EDIT: Ah, I'm new so I can't post links. If anyone wants a copy of the Canbus file, please ping me a message and I'll send over.
jamesbruton said:
Hi
I recently returned my PX5 MTCD unit (purchased through Amazon) as it kept switching the speedo to kph. Since I've returned it Dasaita have sent me a sendspace link to a 500mb fix which they reckon will stop the issue. I do remember seeing others with the same problem so thought I'd share here.
This was for a Peugeot 208 UK 2015 incidentally. I'd previously tried Canbus updates, new ROM's and every Canbus setting with no luck.
If this does fix the issue please let me know as I'll probably repurchase the head unit. I've re-uploaded the file to Google Drive as i have unlimited storage there.
Here you go for the file:
Update steps：
1. Check whether the wiring is plugged rightly and the canbus is plugged in rightly.
2. Prepare a USB flash drive，format the usb, only put the CANBUS.UPDE file in the folder into the root directory of the USB flash drive.
3. Insert the USB flash drive into the navigation USB interface and check if the navigation correctly reads the USB flash drive data.
4. Enter the system settings, click the factory settings, enter the password: canupdates
5. Navigation prompt download, wait for the prompt download to complete or the machine to restart, the upgrade step is completed, then unplug the U disk
Special attention: The upgrade process is about 20 minutes, and our device is forbidden to power off during the period, otherwise the canbus will be scrapped directly!!!
EDIT: Ah, I'm new so I can't post links. If anyone wants a copy of the Canbus file, please ping me a message and I'll send over.
Click to expand...
Click to collapse
The links send me from @jamesbruton
https://drive.google.com/open?...W_XA1nZfRiNqLyjwALBL1Q6hGi8Qot
Here's the original file:
Hi, James
Here you go for the file:
https://www.sendspace.com/file/ka4s6h
Update steps：
1. Check whether the wiring is plugged rightly and the canbus is plugged in rightly.
2. Prepare a USB flash drive，format the usb, only put the CANBUS.UPDE file in the folder into the root directory of the USB flash drive.
3. Insert the USB flash drive into the navigation USB interface and check if the navigation correctly reads the USB flash drive data.
4. Enter the system settings, click the factory settings, enter the password: canupdates
5. Navigation prompt download, wait for the prompt download to complete or the machine to restart, the upgrade step is completed, then unplug the U disk
Special attention: The upgrade process is about 20 minutes, and our device is forbidden to power off during the period, otherwise the canbus will be scrapped directly!!!
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
I've got a px5 unit in a 2013 mini Cooper and it is working well except it seems to have slowed down the mph update speed on the main factory speedo. When I set cruise control, the "cruise set speed" display shows at kph instead of MPH, after cruise speed it set, the dash display switches back to showing mph. Lol.
Tried contacting hifimax to resolve but they haven't been friendly about it.
Hello.
Help me please! Diligently!
My unit is Px5 8xA53 1.5G 4G
MCU: MTCE_MX_V2.88b_1
Android: px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180627.151600 test-keys
Ford Fiesta 2015
Unfortunately, I could not program the buttons in the "Factory settings" (nothing was visible there) and I decided to update CANBUS.UPDE but immediately he dropped the error "fail !!! 0x0e" and after the reset canbus does not work
was the canbus box damaged? Can I resuscitate this?
I disconnected the battery, reset everything to the factory settings in recovery, I have read the new MTCE ... nothing helped ... please help me quickly because the equipment is new and I do not know whether to send it to the seller ...
or maybe it hurt the new mcte and deleted the canbus settings? I do not know, help ...
Yes it does work. It is because of my pestering of Dasaita the file exists in the firstplace. I have shared the details in other posts.
The actual file is nowhere near 500mb - the file includes a number of pointless video clips. The actual required file is a few kb. Takes a few minutes to install.
I have a 2016 Peugeot 208 GT Line.
Dasaita were very helpful in working with me to provide the fix. The only remaining issue is that the fuel consumption program still only shows metric data, no matter what settings you give it.
aggiornamento can bus
can have can bus update
[email protected]
segu45 said:
The links send me from @jamesbruton
https://drive.google.com/open?...W_XA1nZfRiNqLyjwALBL1Q6hGi8Qot
Here's the original file:
Hi, James
Here you go for the file:
man please repost this file: https://www.sendspace.com/file/ka4s6h
Update steps：
1. Check whether the wiring is plugged rightly and the canbus is plugged in rightly.
2. Prepare a USB flash drive，format the usb, only put the CANBUS.UPDE file in the folder into the root directory of the USB flash drive.
3. Insert the USB flash drive into the navigation USB interface and check if the navigation correctly reads the USB flash drive data.
4. Enter the system settings, click the factory settings, enter the password: canupdates
5. Navigation prompt download, wait for the prompt download to complete or the machine to restart, the upgrade step is completed, then unplug the U disk
Special attention: The upgrade process is about 20 minutes, and our device is forbidden to power off during the period, otherwise the canbus will be scrapped directly!!!
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Click to expand...
Click to collapse
Hello everyone.
As a junior member, I'm getting wiser everyday, but still would like some advice on the steps I need to take to clear the Version Unmatch_ issue on my PX5 MTCE HU.
A friend of mine installed a wrong MCU version on my HU, but didn't export before flashing.
My MCU is a MX2 version, and i've been told that I can use the newest MX as well, but after flashing the new MX V3.08 it still comes back with Version unmatch. No sounds, and all the knobs don't work anymore.
Can someone tell me in steps which actions I should take to make the HU work properly again. Note like I said, I don't have the original config file anymore.
By reading through all the treads my head spins , I don't know where to start......
People talk about different things like McuUnmatchUnlock.apk anfd manual config, install reboot, config file will be restored etc etc.
to be sure I used to have MCU version MTCE_MX2_V3.01_01, now i've installed MTCE_MX_V3.08
I would appreciate your help. :angel::angel::angel:
Noël
İnstall the MTCE_MX_V3.08 file from USB. Do not update the MTCE_MX_V3.08 file from the SD card.
Hi all,
first post in this section, so be nice I have a very recent build Xtrons TQ700L unit that i have managed to soft(?) brick after rooting and removing a factory app ("Easy Connect"). On boot I get the initial logo, then after a long time a black screen that goes nowhere. I'm looking for advice on the best strategy to recover/rebuild it.
Hardware details...
build number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20200521.120545 test-keys
MCU version:
MTCE_GS_V3.53_3
As i understand it i have an "MTCE, GS" MCU and can ONLY flash MCU updates from the GS manufacturer. The MCU is probably not the problem here though.
I have a PX6, Android 10 build date of 20200521. Am I correct in saying i can flash any android 10 ROM designed for the PX6 that is newer than this date? Are the only differences between manufacturers cosmetic, like the nice launcher Xtrons supplies?
When i look on Yandex (https://yadi.sk/d/umCvHqCDzHccr), there is no PX6/Android 10 firmware at all from "GS", but there is from "HCT". Should i be looking at flashing the HCT/PX6/Android 10 firmware date 20200612 from the recovery menu? I can get to recovery easily enough by holding, then double clicking the reset button - i just dont know whether i should be flashing part of or the whole of the above package to fix my brick.
thanks.
So in case this helps anyone else, it was an easy fix. Baby steps below.
- grab the latest "Android 10", "PX6/RK3399" factory ROM either from threads here, or from Yandex. I found HA3_RK3399_10.0_ota(20200706).zip here on XDA.
- unzip the outer layer ZIP file and copy the inner "update.zip" to a micro SD card. The stock recovery systems dont allow any selection of ROM file names, so it must be update.zip.
- put the SD card in the "GPS" SD slot.
- with the unit on, reboot to recovery. My way was using a nail to hold the reset button in until the touch button lights began the flash, then quickly release and double click the reset again.
- in recovery, menu items can be scrolled through by either clicking the reset button, or (in my case) touching anywhere on the screen (easier).
- push and hold the rest button (or screen) to select the item.
- do a "wipe data/factory reset" (i guess) to be sure of cleaning out the old mess.
- then do "Apply update from SD card". it should automatically find the update.zip and apply it to all partitions.
- select reboot. Done.
The ROM i used was a "HA" branded generic ROM, so it didnt have the same launcher as my original "GS" (Xtrons) branded ROM. Xtrons wouldn't supply me with their stock ROM when i asked. The generic one was a little better anyway, since it has a stack of boot animations to choose from, whereas the Xtrons one only had the Xtrons logo. It also doesnt have the Easy Connect app, which is what I was trying to remove in the first place!
Additionally, i was able to obtain root easily by using the wifi ADB method here.
I did the same thing. Stupid app kept opening.
I don't have a micro sd card slot, hope it works with usb stick. Don't have one at the moment to try.
Same as yours.
Also, entering recovery mode you..
Hold reset button for 10 sec, release and immediately press it once.
I have a dicola px6 mtce
I'll update if i get it working.
Unit is a Joying JY-UQ124 PX3 - https://www.amazon.com/gp/product/B00XGEYU26
No idea what specific MCU and all that it is now as I bricked it several years ago when I accidentally put the wrong firmware on when attempting to go back to stock from a Malaysk ROM, and now only get black screen on power on with front panel lights on. Can't get into recovery, attempting to restore via SD card isn't working - never seems to start loading from the SD, screen just stays black.
Bought a new radio, put this one on the shelf, and now I'm trying to recover it again via the ST-LINK. Except that the only 5 holes empty on my board aren't marked, and I suspect it may actually be an unpopulated USB connector.
The PX3 SOM is a card edge RAM style connector, so I can't easily attach to header pins there either.
Do I have options here for recovery, or am I SOL with a paperweight on my hands?
SOM or MCU, photo show SOM. What is bricked, som or MCU
I'm _guessing_ it's the MCU? If the SOM gets bricked, wouldn't I still be seeing _something_ on the screen at boot?
It's been a while since I played with this one last, but I seem to recall that I accidentally tried to push the update image from my Sofia unit into this one, and didn't catch my mistake until after it was too late to do anything about it.
But honestly, I'm not really sure what exactly is wrong with it at this point, nor do I remember exactly what I did to it prior, other than trying to roll back to stock from a Malaysk ROM, and it didn't boot afterwards.