Hi,
I need help because my android car unit is currently stuck on the Android splash screen, before that problem the unit has worked well during 5 months.
I have sent a mail to the seller but i'm waiting for a response.
Here is the unit, this is exactly the same but mine running on android 6.1 :
search on aliexpress -> Uniway ZLKLZ7071
My question is : How do i can enter in the recovery mode ?
I mean that i proceed to a hard reset with a wipe cache...
But i have tried some combination key but not chance i can't enter to the recovery mode.
The canbus link is ok i can increase or reduce the sound and i can hear only one band on radio but android won't start and i see only the android splashscreen.
Can you help me ?
Thank you.
the seller never responds to me.
I have purchased other unit.
Don t buy uniway gps unit stay away.
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
Hi i have a problem with my mtce Mx px3 unit. These days I was in the factory settings in others I do not know exactly what I changed but since then I have the black screen and only the key lights are seen. I managed to get into recovery mode and install the original firmware but on reboot is still in the same situation.: Eek: Can someone help me? Sorry about my bad English. Thanks in advance
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".
Sorry, I am a idiot and My phone was in perfect condition until I run
fastboot erase recovery
Click to expand...
Click to collapse
fastboot reboot recovery
Click to expand...
Click to collapse
and now my phone doesnt have charging logo on, doesnt boot to bootloader
It is basically black and no response
however, the noti LED is on when charging. and I saw COM6 in device manager once then disappeared
AND in some combination of phone key the LED blink 'while charging condition'
In addition, I tried unplug internal battery but it doesnt work
Any idea how to fix it?
P.S. I have seen the repairing MB need 102 pounds (it's nearly 70% of the price I bought it
This phone have NFC, IR control, 64MP camera which is perfect in this price range
If this phone cant repair, any suggest of non-xiaomi (chinese) phone recommend?
(samsung A52s is top of the hill too but it is a bit old in late 2022)
hheylau said:
P.S. I have seen the repairing MB need 102 pounds (it's nearly 70% of the price I bought it
This phone have NFC, IR control, 64MP camera which is perfect in this price range
If this phone cant repair, any suggest of non-xiaomi (chinese) phone recommend?
(samsung A52s is top of the hill too but it is a bit old in late 2022)
Click to expand...
Click to collapse
Kirasu2080 said:
Click to expand...
Click to collapse
Thank you sooooo much. This tutorial works and save me lots of money and worries.
Btw, is it only available/ apply for note 8 pro cuz it is mediatek cpu?
How do they extract/ do I find the auth file that used in SPflash.exe ?
hheylau said:
Thank you sooooo much. This tutorial works and save me lots of money and worries.
Btw, is it only available/ apply for note 8 pro cuz it is mediatek cpu?
How do they extract/ do I find the auth file that used in SPflash.exe ?
Click to expand...
Click to collapse
Yep. It just works for some old mtk devices. It's based on MTK-bypass github, but it didn't get update for long time. For auth file, I got no idea, didn't search that deep.
Same Situation. Got My Device Bricked (Begonia). Hard Brick, I Tried The Method Mentioned Above.
But When Using Bypass Tool it give the following error...
Please Help....
ahadjutt7 said:
Same Situation. Got My Device Bricked (Begonia). Hard Brick, I Tried The Method Mentioned Above.
But When Using Bypass Tool it give the following error...
Please Help....
Click to expand...
Click to collapse
There's some tricks:
- Use only port that you added Libusb. If you change port, you need to add again.
- Close and open new bypass, hold Power until notification light turn off and on then hold Power + Volume up until it show "Protection disable"
- If bypass error, redo all steps again.
- If sp flash tool not flash after 20s, press Stop. Bypass success again. Then press Download. Usually it will work in 2nd time