Hi guys,
your help please! I have a Px3 2GB head unit with the following:
- MCU MTCE_KGL_V2.70_1
- Androd 7.1.2
I was trying to update to the latest Malaysk version 5 and somehow during installation an error message appeared and the unit is now unusable. When turned on only the initial screen (Navigation system) is visible and nothing else, so I can only switch it either off, or on and it stays on that screen. I have tried to install a new software through USB and microSD but nothing seems to work.
Do you know how I can install the software again so that I can use the unit?
Many thanks for your help!!
Related
hi there i just installed my erisin es2007a to my car there was 2 problems with the unit.
1. the bluetooth will not pair and show any devices
2. 3g will not work but the signal bar is showing a signal
i got in contact with the seller and they advised me to install a update. they sent me a update and i unzipped it and put on a sd card and installed on the my head unit.
after the update the vol , navi , power , screen in and out buttons all stopped working and the update didnt even fix the problem with the bluetooth and 3g problems.
so now my sd car is stuck in the machine.
i think its a software problem but ive been looking at all the ubdates that is on this site and cant work out what one will suit my problems.
mcu version = mtcb-kgl-v2-80
android version =4.4.4_07112015
kernel version = 3.0.36+ [email protected] #1429
cpu = arm [email protected] (x4)
any advice will be greatfull
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, so i went on a little adventure with my MTCD PX3 RK 3188 unit, first i wanted to experiment with some new RAM upgrades, so I tried quite a few different manufacturers and specifications as I work for a PCB/PCA manufacturer. But I think i have a pair that works now, cant remember the exact part name but it is manufactured by Micron 1 GB modules. The unit boots, and i can access recovery and flash roms without problems. The issue arises when it tries to bot the selected ROM, the unit shows the splash screen of the rom selected and then proceeds to boot the ROM with the flashing car logo. But after the car logo has blinked for a minute, the screen shuts off and the device reboots.
So, while fiddling inside the recovery menus I've discovered what i think might be the issue, firstly I cannot wipe the device, if selected the cmd prompts: "Data wipe failed"
But if i try to install a new ROM I can also observe that it does not update uboot.img because "E: Can't find uboot".
This leads me to belive that while I was experimenting with the RAM modules, I might have overheated the internal storage chip, in turn corrupting some data.
So now i need some assistance:
1. Is there any way to flash a new bootloader?
2. Can i change the internal memory chip and just flash the MCU and rom to it? How would i do that? Will it fix the problem?
3. Is there any other fixes that I should try?
Thank you for any suggestions.
Head over to OTG thread to flash ROM directly or scenario where eMMC is corrupt or blank.
HerpyDerpy said:
Hi, so i went on a little adventure with my MTCD PX3 RK 3188 unit, first i wanted to experiment with some new RAM upgrades, so I tried quite a few different manufacturers and specifications as I work for a PCB/PCA manufacturer. But I think i have a pair that works now, cant remember the exact part name but it is manufactured by Micron 1 GB modules. The unit boots, and i can access recovery and flash roms without problems. The issue arises when it tries to bot the selected ROM, the unit shows the splash screen of the rom selected and then proceeds to boot the ROM with the flashing car logo. But after the car logo has blinked for a minute, the screen shuts off and the device reboots.
So, while fiddling inside the recovery menus I've discovered what i think might be the issue, firstly I cannot wipe the device, if selected the cmd prompts: "Data wipe failed"
But if i try to install a new ROM I can also observe that it does not update uboot.img because "E: Can't find uboot".
This leads me to belive that while I was experimenting with the RAM modules, I might have overheated the internal storage chip, in turn corrupting some data.
So now i need some assistance:
1. Is there any way to flash a new bootloader?
2. Can i change the internal memory chip and just flash the MCU and rom to it? How would i do that? Will it fix the problem?
3. Is there any other fixes that I should try?
Thank you for any suggestions.
Click to expand...
Click to collapse
I think you can try to use rockchip tools to erase the flash memory and to flash again your image.
As px3 and px5 are interchangeable....
Check on forums as there is some information of building a OTG cable for px5 to allow you to connect the coreboard to USB on PC and allows you to use rock chip tools
Enviado desde mi SM-G950F mediante Tapatalk
I have HU with MTCE_MX_V3.13 from ZNY. Certain model
It is 1024x800 PX5 4Gb 32Gb Android 8.
Please check the video of HU current state.
Seller sent me dmcu.img
It can not go into recovery mode. It can go with SD flashing procedures.
Firstly I need to clarify what is the certain problem:
1. SOM
2. MCU
3. LCD screen
How can I check LCD screen? Also SOM MCU?
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.