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 to all, I have a tv tdsystems 50-inch 4k with android tv 7.1.1
I recovered from the manufacturer the firmware of the TV which is called install.img
I wanted to ask if there is someone willing to help me I have to edit the firmware himself with the official app google is root, thanks
Send me yours install. IMG.
My email [email protected] Ru.
I will do edit.
timersky said:
Send me yours install. IMG.
My email [email protected] Ru.
I will do edit.
Click to expand...
Click to collapse
hello sorry but I only read your answer now, I am very grateful for your help since you don't find anything on the internet about this soc, do you have the same TV or a similar one ?? I'm sending you all the content by email
Hello there, i have been searching for the install.img for my Star-X RealtekATV 43" but i cant seem to find it. Mine is stuck in Android LOGO and I cant any other ways to force reset it. please share the Install.img so i can try, thanks
ReagNkyaIV said:
Hello there, i have been searching for the install.img for my Star-X RealtekATV 43" but i cant seem to find it. Mine is stuck in Android LOGO and I cant any other ways to force reset it. please share the Install.img so i can try, thanks
Click to expand...
Click to collapse
hello, you have to ask your producer because almost all the .img files are different according to the manufacturer, I'm looking for a way to root my
I also have a problem like this (freezes in boot animation)
the device is gosonic gled-4350 model and it freezes when I simulate the secondary screen from the developer settings of this device
and I thought to solve the problem by opening the service menu with the service code, but I do not know the code of this device. What should I do?
ErrorVelet said:
I also have a problem like this (freezes in boot animation)
the device is gosonic gled-4350 model and it freezes when I simulate the secondary screen from the developer settings of this device
and I thought to solve the problem by opening the service menu with the service code, but I do not know the code of this device. What should I do?
Click to expand...
Click to collapse
I did the same mistake to my TV. However, I was able to recover from such freeze by forcing the TV to start in safemode. As I remember, I plugged off the TV from the power source. After that I plugged it in again and turned ON the TV from the remote while pressing at the same time on the [Vol-] button. Once I got into the system, I turned off the secondary display and rebooted again. This time everything was fine.
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".
Hello, i have a problem on my Thomson 55US6106. After touching in developper mod in show pointer or something like this the TV has freeze and after shutdown she always turn on the android logo.. i see few person in my case but i don't find any solution for my TV.
I have tried to downland new software on mytomson but after the installation it's always the same.
Tried to wait 48 hours but after 48 hours it's always on the boot logo.
Tried to click all the buttons on the back of TV (remote don't work in the boot).
Thomson don't want help me cause it's not guaranted.. I hope somewone can help me thank you in advance and nice day.
Few tips about my TV :
Ticket on the back of TV 55US6106
On the main board :
MT58CU
Soft V
40-MT58CU-MAB4HG
55UC6596
08-MT58011-MA200AA
08-CS55CUN-OC407AA
08-MT58011-MA300AA
V8-T658T01-LF1V176 12V
It's all I find on the main board and if you need more, just ask. Thank you so much for who can help me. For 1 300€ i hope the TV will work more than 2,5 years.
Best regards
Flashed PKG file?
I don't really know how flash pkg file or what is exacly
Is complete wipe previous firmware and install new ...as factory reset.
Attached ....
Oh this, yes I have already tried. I download the software on Mytompson but it's always the same :/ The boot android logo loop loads
Thank you friend