Hitachi 42HYT42U, Vestel Mainboard 17MB95M, Panel - VES420UNDL:
Looked at this 6 months ago, booted to Hitachi Logo and with flashing blue and red Leds then back to standby red.
Checked PSU etc, caps, and concluded like everyone else here and had another thread 6 months ago that it was corrupt firmware.
Bought 2 replacement boards of ebay, 1 did the same, the other didn't go back to standby after logo just carried on flashing blue and red. Got one refunded.
So gave up. 6 Months later decided to look again and bought another board as only 8£ on ebay. - Same problem as beginning.
Spent all day today researching this.
Bricked 3 boards doing firmware updates. First 2 used top USB and then found a thread saying this bricks it, don't know if thats correct.
Third used bottom but still bricked and then found someone saying comment out the MBOOT section as then you won't risk bricking the bootloader chip U10.
First question is why it was bricked, lots of people saying the Mboot is the same for all updates?
So last board I did many updates just commenting out the Mboot.
Most just result in recurring bootloop of Hitachi logo.
One gives solid blue led with backlight but blank screen, does that mean it has booted successfully? It was for 50" panel not 42 so presumed wrong panel info for it, resulting blank screen!
Another booted to blue led but no backlight or picture!
Can some of the core updates not have worked because they need matching Mboot? How relevant is it?
Before I started any flashing from the USB I swapped the U10 chips on to opposite of 2 boards and neither did anything, totally behaved like bricked, no leds flashing! So soldered them back and then they worked again!
Why is that? The boards were for the same tv!
There is a thread on here with a 32" Toshiba update for same Mainboard and then someone said can use on any 17MB95M board if you delete Panel file but how do you do do that?
I cant extract the bin file, people say you can on linux but what about windows?
I could setup a linux laptop as last resort.
Another thread someone posted an Auto script that saved the Nand so I now have a copy but its in several bin files not the one?
How do you put that back on the tv, do I have to repack as MB95 bin?
I got that off 2 boards before bricking one of them but on both boards the conf file would not read on my pc and was said to be corrupted - maybe the reason the tv did not boot????
Can I unbrick the other boards with a cheap ebay SPI programmer? I only have the Mboot saved off 2 of them though and seeing as when I swapped chips neither booted it seams they are tied somehow???
My understanding from todays research is that the SPI with Mboot just loads the Nand.
And that corrupt SPI means bricked and no standby leds and have to unsolder to reprogram and that the fact all my boards had hitachi logo which I presume is loaded off the NAND??? means all of them had corrupt main nand?
Even if I found the correct firmware is it useless with out new NAND, is nand chip knackered now?
Can I just solder new nand and then flash from USB if U10 SPI working?
As you can see many questions so I appreciate anybody shedding light for me, I don't think I will now fix this but I spent 8 hours researching this and trying many firmwares, I really would like to understand what is going on!
Is there a generic firmware for this board?
I could not get far on the Vestal site as not English. It asks for serial no, but which one is the serial no.? I found another site that listed serial no.s for some boards but not the MB95 and they did work for finding a download.
I got another download off there someone linked for MB9x ! But it bootloops and again I thought it too risky to use the Mboot that was with it!
Many thanks, Reesy.
Looked at this 6 months ago, booted to Hitachi Logo and with flashing blue and red Leds then back to standby red.
Checked PSU etc, caps, and concluded like everyone else here and had another thread 6 months ago that it was corrupt firmware.
Bought 2 replacement boards of ebay, 1 did the same, the other didn't go back to standby after logo just carried on flashing blue and red. Got one refunded.
So gave up. 6 Months later decided to look again and bought another board as only 8£ on ebay. - Same problem as beginning.
Spent all day today researching this.
Bricked 3 boards doing firmware updates. First 2 used top USB and then found a thread saying this bricks it, don't know if thats correct.
Third used bottom but still bricked and then found someone saying comment out the MBOOT section as then you won't risk bricking the bootloader chip U10.
First question is why it was bricked, lots of people saying the Mboot is the same for all updates?
So last board I did many updates just commenting out the Mboot.
Most just result in recurring bootloop of Hitachi logo.
One gives solid blue led with backlight but blank screen, does that mean it has booted successfully? It was for 50" panel not 42 so presumed wrong panel info for it, resulting blank screen!
Another booted to blue led but no backlight or picture!
Can some of the core updates not have worked because they need matching Mboot? How relevant is it?
Before I started any flashing from the USB I swapped the U10 chips on to opposite of 2 boards and neither did anything, totally behaved like bricked, no leds flashing! So soldered them back and then they worked again!
Why is that? The boards were for the same tv!
There is a thread on here with a 32" Toshiba update for same Mainboard and then someone said can use on any 17MB95M board if you delete Panel file but how do you do do that?
I cant extract the bin file, people say you can on linux but what about windows?
I could setup a linux laptop as last resort.
Another thread someone posted an Auto script that saved the Nand so I now have a copy but its in several bin files not the one?
How do you put that back on the tv, do I have to repack as MB95 bin?
I got that off 2 boards before bricking one of them but on both boards the conf file would not read on my pc and was said to be corrupted - maybe the reason the tv did not boot????
Can I unbrick the other boards with a cheap ebay SPI programmer? I only have the Mboot saved off 2 of them though and seeing as when I swapped chips neither booted it seams they are tied somehow???
My understanding from todays research is that the SPI with Mboot just loads the Nand.
And that corrupt SPI means bricked and no standby leds and have to unsolder to reprogram and that the fact all my boards had hitachi logo which I presume is loaded off the NAND??? means all of them had corrupt main nand?
Even if I found the correct firmware is it useless with out new NAND, is nand chip knackered now?
Can I just solder new nand and then flash from USB if U10 SPI working?
As you can see many questions so I appreciate anybody shedding light for me, I don't think I will now fix this but I spent 8 hours researching this and trying many firmwares, I really would like to understand what is going on!
Is there a generic firmware for this board?
I could not get far on the Vestal site as not English. It asks for serial no, but which one is the serial no.? I found another site that listed serial no.s for some boards but not the MB95 and they did work for finding a download.
I got another download off there someone linked for MB9x ! But it bootloops and again I thought it too risky to use the Mboot that was with it!
Many thanks, Reesy.
Comment