Hi Y'all,
I can't open the device on start screen (can't pull the silver ring to unlock the phone).
I tried factory reset...nothing
I tried flashing a stock RUU i bought from football....nothing
does this mean I have a HW issue with the touch screen or could it be yet another SW issue
I might somehow repair?
any help will be much appreciated
joffe.tal said:
Hi Y'all,
I can't open the device on start screen (can't pull the silver ring to unlock the phone).
I tried factory reset...nothing
I tried flashing a stock RUU i bought from football....nothing
does this mean I have a HW issue with the touch screen or could it be yet another SW issue
I might somehow repair?
any help will be much appreciated
Click to expand...
Click to collapse
It looks like a hardware issue. On my one v the screen stops responding sometimes but after a reboot it starts working again.
Hi everyone, there are a lot of guides on this forum to solve a brick HU. But I can figure out what is really my problem.
I have a PK5 Rev4 and I suppose is a KLD unit from Eonon. No power on, just a blink on buttons and any more. No SDboot reaction, no SOM OTG reaction, and no voltage over SOM pins from MCU.
I try several guides, but cant figure out if my HU has a MCU bricked or a SOM bricked or another problem...
Is there some way to determine which is my problem before apply a flash method??
Thanks in advance
Your post doesn't mention if you've used a schematic and first checked the unit power supplies. If the MCU has always on 3.3v and sends a power on signal to the SOM +5 supply, then MCU is probably OK.
You could also try removing SOM and manually triggering SOM+5 to check via a resistor.
If stuck with any of this advice, suggest talking with a local expert to walk you through.
marchnz said:
Your post doesn't mention if you've used a schematic and first checked the unit power supplies. If the MCU has always on 3.3v and sends a power on signal to the SOM +5 supply, then MCU is probably OK.
You could also try removing SOM and manually triggering SOM+5 to check via a resistor.
If stuck with any of this advice, suggest talking with a local expert to walk you through.
Click to expand...
Click to collapse
Well, I didnt check unit power supply on MCU because I cant found my MCU model with presicion. Now Im on the way to try to flash MCU with this method https://forum.xda-developers.com/android-auto/mtcd-android-head-units-general/guide-how-to-unlock-bricked-mcu-units-t3748646
Is a possibility that MCU are bricked and dont supply any voltage to SOM? Thats my point. I get today a ST-LINK/V2 programmer to try flash it.
Suddenly I didnt have success with your method of flashing SOM OTG outside of MCU, but I can confirm that SOM dont get any voltage from MCU when 12v is apply. I saw schematics from your signature here, and cant realise what to test..
Look for an expert is a must I think, but before that I would try my last with flashing MCU.
Thanks @marchnz
Ok, what that means?? I cant make mcu flash with my st link cose I use winxp and drivers and app doesn’t work, so I put my hand to meassure voltages and something change. Can somebody explain that state??
If I put SOM in place, display go off, VCC pin 1 of som get 1.4volts and a tinny sound like frying come up. If I put SOM like picture, frying stops, I get 5volts on pin 1 of SOM and display become active.
My HU has recovered the ability to turn on and off, as well as flash 3 times with a long press of the power button. but thats all..
polgoz said:
Ok, what that means?? I cant make mcu flash with my st link cose I use winxp and drivers and app doesn’t work, so I put my hand to meassure voltages and something change. Can somebody explain that state??
If I put SOM in place, display go off, VCC pin 1 of som get 1.4volts and a tinny sound like frying come up. If I put SOM like picture, frying stops, I get 5volts on pin 1 of SOM and display become active.
My HU has recovered the ability to turn on and off, as well as flash 3 times with a long press of the power button. but thats all..
Click to expand...
Click to collapse
Might be defective SOM, dragging +5v supply down or a defective +5v supply. From your description, sounds like the MCU is OK.
You could try connecting the SOM to a bench supply with current limiting/ammeter to validate but more likely that the SOM is defective.
marchnz said:
Your post doesn't mention if you've used a schematic and first checked the unit power supplies. If the MCU has always on 3.3v and sends a power on signal to the SOM +5 supply, then MCU is probably OK.
You could also try removing SOM and manually triggering SOM+5 to check via a resistor.
If stuck with any of this advice, suggest talking with a local expert to walk you through.
Click to expand...
Click to collapse
marchnz said:
Might be defective SOM, dragging +5v supply down or a defective +5v supply. From your description, sounds like the MCU is OK.
You could try connecting the SOM to a bench supply with current limiting/ammeter to validate but more likely that the SOM is defective.
Click to expand...
Click to collapse
Thanks @marchnz. MID SOLVED!
Still trying and discover that if I put a heavy pressure over the MCU on SOM pins zone (zone not identified) HU power up without problem.
Fraying sound was reduced but not eliminated.
Isn't a software or brick problem. Is a internal contact in the MCU, cose I check contacts and nothing look on bad solder.. so my last chance is to try install a prothesis to pull down the zone and still in place.
Any idea?
@marchnz
Well I f..ked up. All was ok till I decide to go to android 8. First, I update android 6 ok, I update MCU to last version for my KLD ok, all was fine.. so I decide to go to Android 8. WRONG!..
I was follow the the kumarai video and stuck after ERASE display. No more reaction after that boot.
I cant get into recovery page, (note that I cant goin into recovery before this event... ) so, whats the problem? how can I recover the recovery state? OTG?...
Please help..
regards
Pol
polgoz said:
@marchnz
Well I f..ked up. All was ok till I decide to go to android 8. First, I update android 6 ok, I update MCU to last version for my KLD ok, all was fine.. so I decide to go to Android 8. WRONG!..
I was follow the the kumarai video and stuck after ERASE display. No more reaction after that boot.
I cant get into recovery page, (note that I cant goin into recovery before this event... ) so, whats the problem? how can I recover the recovery state? OTG?...
Please help..
regards
Pol
Click to expand...
Click to collapse
Otg
Enviado desde mi SM-G950F mediante Tapatalk
ikerg said:
Otg
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
OTG succes! I got Android 8 from SVA now. But I had to made some magic with the MCU board. I has some internal path with problems of contact related with display and touch sensitive pad. I solved it with little sticks of cork under the motherboard. but times to times fails... I thinking on put it in the oven...
polgoz said:
@marchnz
Well I f..ked up. All was ok till I decide to go to android 8. First, I update android 6 ok, I update MCU to last version for my KLD ok, all was fine.. so I decide to go to Android 8. WRONG!..
I was follow the the kumarai video and stuck after ERASE display. No more reaction after that boot.
I cant get into recovery page, (note that I cant goin into recovery before this event... ) so, whats the problem? how can I recover the recovery state? OTG?...
Please help..
regards
Pol
Click to expand...
Click to collapse
Hi polgoz, I seem to have same problem as you on KLD Eonon after go to 8.0 from 6.01. That is: no more reaction after that last boot. Get blank/black screen but when Hold Power button 9 secs it works to flash LEDs only-nothing else.. I cant get into recovery page too so, blank screen was your problem after Hold Power/Flash LED was your issue too?
I see you use this method here:
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Any specific tips if no Win 10 but only Win 7 or XP?
Please help fellow KLD-Eonon owner
Thanks polgoz
hapoll said:
Hi polgoz, I seem to have same problem as you on KLD Eonon after go to 8.0 from 6.01. That is: no more reaction after that last boot. Get blank/black screen but when Hold Power button 9 secs it works to flash LEDs only-nothing else.. I cant get into recovery page too so, blank screen was your problem after Hold Power/Flash LED was your issue too?
I see you use this method here:
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Any specific tips if no Win 10 but only Win 7 or XP?
Please help fellow KLD-Eonon owner
Thanks polgoz
Click to expand...
Click to collapse
Hi mate, I solve the black screen problem doing the SOM flashing with the Marchnz method from the link that you point. But before try to flash som, repeat the sd method with the first sd step, maybe this help.
I didnt flash SOM on XP.. I was able to only on Win10 I dont know why..
Hope this help.
Regards
Hello everyone
I bought recently a MTCE PX5 from Witson (MTCE_MX2_V2.87 - android 8 - 8 cores -32giga flash).
It worked perfectly and rooting it was a success.
But Yesterday... the HU rebooted and then nothing : the Oreo screen and then it's locked on the carmaker logo...
I would like to enter in the recovery mode but there is no physical button or reset hole, onlu the touchscreen.
So I tried the method with the keyboard and the Right AltGr+PrintScreen an then pressing rapidly the E... but it didn't work until now.
Before going to step 2 (STM32 programmer), does anybody have tried successfully this method ?
If yes can you tell me if there a sort of trick to get it work ?
Thanks a lot.
fabrice92800 said:
Hello everyone
I bought recently a MTCE PX5 from Witson (MTCE_MX2_V2.87 - android 8 - 8 cores -32giga flash).
It worked perfectly and rooting it was a success.
But Yesterday... the HU rebooted and then nothing : the Oreo screen and then it's locked on the carmaker logo...
I would like to enter in the recovery mode but there is no physical button or reset hole, onlu the touchscreen.
So I tried the method with the keyboard and the Right AltGr+PrintScreen an then pressing rapidly the E... but it didn't work until now.
Before going to step 2 (STM32 programmer), does anybody have tried successfully this method ?
If yes can you tell me if there a sort of trick to get it work ?
Thanks a lot.
Click to expand...
Click to collapse
Ask your seller
They must have a procedure for the case the unit get bricked
Enviado desde mi SM-G950F mediante Tapatalk
My unit is a PbA ES7815, which I believe is identical to an Erisin ES7815. The original MCU was MTCE_LM_V2.88, which I upgraded to MTCE_LM_V3.01c without a problem. I recently saw MTCE_LM_V3.30 was available on Yandis so I downloaded it and did an MCU upgrade.
The result was a blank screen. I can't boot into recovery with the reset button and on a long press of the on/off switch I get a LED flash, but that is all I can get it to do.
How can I recover back to MTCE_LM_V3.01c? Sorry if this is something I should be able to find..
andychapman said:
My unit is a PbA ES7815, which I believe is identical to an Erisin ES7815. The original MCU was MTCE_LM_V2.88, which I upgraded to MTCE_LM_V3.01c without a problem. I recently saw MTCE_LM_V3.30 was available on Yandis so I downloaded it and did an MCU upgrade.
The result was a blank screen. I can't boot into recovery with the reset button and on a long press of the on/off switch I get a LED flash, but that is all I can get it to do.
How can I recover back to MTCE_LM_V3.01c? Sorry if this is something I should be able to find..
Click to expand...
Click to collapse
Hi, you will need to upload older firmware via ST-link. There is some tutorials on the internet, search for "PX5 bricked MCU fix".
Hello everyone, I hope you understand me, my English is not so god und Google help me with translation.
I have a problem with my Android navigation system. Device designation: Erisin ES9000A.
Unfortunately, the device gets stuck with the Android logo when starting and then does not go any further. I can get into recovery mode and now wanted to reinstall the MCU. Unfortunately I don't know which version I need. I can not look in the settings because the system does not start.
Is there another way to find out the correct MCU version?
On the Mainboard is a designation:
Kd-hct-mb 2014/06/24 Rev-1.5
On the circuit board where the Rockchip is on it is a designation: MTC_RK3066_Revo. 3a 2014.03.27
It was very nice when you can help me.
FloSchel said:
Hello everyone, I hope you understand me, my English is not so god und Google help me with translation.
I have a problem with my Android navigation system. Device designation: Erisin ES9000A.
Unfortunately, the device gets stuck with the Android logo when starting and then does not go any further. I can get into recovery mode and now wanted to reinstall the MCU. Unfortunately I don't know which version I need. I can not look in the settings because the system does not start.
Is there another way to find out the correct MCU version?
On the Mainboard is a designation:
Kd-hct-mb 2014/06/24 Rev-1.5
On the circuit board where the Rockchip is on it is a designation: MTC_RK3066_Revo. 3a 2014.03.27
It was very nice when you can help me.
Click to expand...
Click to collapse
If you can get into recovery, have you tried to factory reset? That should get you back to booting so you can get mcu and system details to better address your issue of updating.