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".
Related
Hi everyone i have a problem with a Galaxy Tab S 10.5 Sm-T800. I've been using since past novemeber so i hace almost a year with this great device.
But today i have a problem two days ago i was using normally my tab when i finish using i shutdown the device so today i turn it on but the Wifi and bluetooth buttons are unable to turn it on they stuck in gray color so i don't know what happen i already do the factory reset like 3 times and no response at all?
I friend told me to reinstall the firmware with odin i don't know what to do and if that is correct!
please someone can tell what to do with.
Note: It's running on 5.0.2 and my device is already rooted
Have you deleted any system files that might control wifi and bluetooth, an normal reset will not normally replace these files.
Have a look at the link below, it mention hard reset, to replace damaged system files, though the English is poor, I dont know if this is correct or if you will need to do flash an stock rom to fix your tablet as i have not faced this problem myself, hopefully and more informed owner with help you.
http://www.hard-reset.org/factory-d...fi-lte-sm-t800sm-t805-with-safety-hard-reset/
John.
hey
Hey john well i got to say that y try to install a rom that i found in this post:
[FIRMWARE][SM-T800] Galaxy Tab 10.5 (Wifi) T800XXU1ANF8 No-Wipe Factory Image
http://forum.xda-developers.com/showthread.php?t=2800372
I try it with odin but i get an error at the on "hidden.img" it's says FAIL.
Then i try to do it with TWRP with this rom that i found here:
SM-T800+BASE+XAR+OE2+(U.S)
And i get a message "e: unable to mount system"
Somebody told me to repair it with TWRP the system partition with 4EXT and i did but now i don't know what rom use.
Please help me, i still enter to download mode
I'm sorry for the english but i'm from Mexico
[FIRMWARE][SM-T800] Galaxy Tab 10.5 (Wifi) T800XXU1ANF8 No-Wipe Factory Image
http://forum.xda-developers.com/showthread.php?t=2800372
Reinstall again, when it fails at hidden.img go into recovery and wipe cache then reboot.
i reinstall as you say but the device is stuck on the next screen:
Firmware upgrade ecnountered an issue, please select recovery mode in Kies & try again
How do i enter to recovery mode?
davidcasjim said:
i reinstall as you say but the device is stuck on the next screen:
Firmware upgrade ecnountered an issue, please select recovery mode in Kies & try again
How do i enter to recovery mode?
Click to expand...
Click to collapse
Hold POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons until recovery boots.
ashyx said:
Hold POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons until recovery boots.
Click to expand...
Click to collapse
Hi i recently download the firmware from SamMobile for Mexico and i install it, everything was ok with no problems on Odin.
But the problems remains the same i can't Activate Wifi or Bluetooth? someone already have this problem and solved.
Thanks for help
davidcasjim said:
Hi i recently download the firmware from SamMobile for Mexico and i install it, everything was ok with no problems on Odin.
But the problems remains the same i can't Activate Wifi or Bluetooth? someone already have this problem and solved.
Thanks for help
Click to expand...
Click to collapse
Someone had a similar problem with the Tab 4. It could be a missing mac file or something which causes it not to turn on. Take a look at this http://forum.xda-developers.com/showthread.php?p=56474891
Sent from my SM-T800 using Tapatalk
Has anyone find the solution? I've tried everything
Hi there,
I have exactly the same problem with the 8.4 version (SM-T705).
I didn't root it or changed the official rom and have it since a little more than a year. I suspect a hardware break.
jhraigniac said:
Hi there,
I have exactly the same problem with the 8.4 version (SM-T705).
I didn't root it or changed the official rom and have it since a little more than a year. I suspect a hardware break.
Click to expand...
Click to collapse
jhraigniac, I have the same problem (bluetooth won't turn on) on my stock SM-T705. (Wifi is fine!)
I did flash stock firmware and wipe memory but wifi and bluetooth is not working, what should I do ?
snip3r_e said:
I did flash stock firmware and wipe memory but wifi and bluetooth is not working, what should I do ?
Click to expand...
Click to collapse
I guess you didn't notice that this thread is almost a year old. Maybe you should start a new topic.
Sent from my SM-T800 using XDA-Developers mobile app
Hello, I have a stereo Pumpkin and worked perfect. Today I wanted it on and stays on and the logo will not start.
And I tried pressing the reset button and disconnect the car battery and remains unchanged.
I leave a video demonstration of what it does.
HTML:
https://onedrive.live.com/redir?resid=89B58453255521EC!446&authkey=!AKyOfVlhPymibcg&ithint=video%2cmp4
I await your response.
Cheers
Try to enter the recovery model, then choose the "recovery system from back up". The Pumpkin has uploaded a instruction video on YouTube. I am new here, can't post a link. You can search "KD Android Headunit Recovery mode update instruction".
u.r.rible said:
Try to enter the recovery model, then choose the "recovery system from back up". The Pumpkin has uploaded a instruction video on YouTube. I am new here, can't post a link. You can search "KD Android Headunit Recovery mode update instruction".
Click to expand...
Click to collapse
That requires he already have a backup...
I guess your Unit is of MTCB-Type. I will move this thread to the new section probably you will get some help there.
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
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.