TV standby light flash once after plug-in AC power. Then silent. No backlight, no LCD image on flash light test, no SPDIF light.
All PSU voltages to main looks good (12v, 20v (label says 18v but is 20), standby voltage) Probing main board shows what appears to be a DCDC converter (MSH6103A can't find datasheet) providing 5v, 3.3v and 1v. 5v present to the standby light power switch board.
These HiSense TVs appears to have lots of firmware corruptions that takes out the main board either through smartTV use or firmware update. Used main board prices are quite high probably due to so many main boards failing from poor firmware. Since I only get 1 blink on the standby light, probably even basic boot firmware has corrupted (>1 blinks will indicate some failure status)
Main SOC is a MStar msd6886NQHT (MStar bought out by MediaTek in 2019 according to Phillips lawsuit docs in US ITC court filing link p48 )
Found this 2018 service guide for MSD5886 showing UART access to the TV to flash various boot/firmware bits
https://www.manualslib.com/manual/16...roduct-MSD6886
p28 shows a serial port connection to the earphone port. My TV has both an earphone and service port (also earphone plug shape) right next to it. Service port plug solder points appears to show its just a TRS 3.5mm plug port
https://www.headphonesty.com/2019/04...uctor_plug_TRS
Looks pretty easy to make the DB9 to TRS 3.5mm cable (pin 2/3/5) and can buy these off the shelf programming cables
https://www.youtube.com/watch?v=4riU...elliteTrackers
Then its onto finding software and this TV's boot/firmware bits.
Flashing in boot/firmware via serial ports is pretty standard Android flashing process. Recently did this on my Chinese Android HeadUnit for the car. Just need the cable, Flashing firmware (usually from main SOC maker) and trigger SOC to reset.
Anyone has experience with this? Also probably unlikely to get boot/firmware bits from HiSense so probably need a flash in a raw dump?
I'll try heating the main SOC slightly to see if any help but given the % of firmware failures on this TV, corruption boot/firmware seems the most likely candidate.
All PSU voltages to main looks good (12v, 20v (label says 18v but is 20), standby voltage) Probing main board shows what appears to be a DCDC converter (MSH6103A can't find datasheet) providing 5v, 3.3v and 1v. 5v present to the standby light power switch board.
These HiSense TVs appears to have lots of firmware corruptions that takes out the main board either through smartTV use or firmware update. Used main board prices are quite high probably due to so many main boards failing from poor firmware. Since I only get 1 blink on the standby light, probably even basic boot firmware has corrupted (>1 blinks will indicate some failure status)
Main SOC is a MStar msd6886NQHT (MStar bought out by MediaTek in 2019 according to Phillips lawsuit docs in US ITC court filing link p48 )
Found this 2018 service guide for MSD5886 showing UART access to the TV to flash various boot/firmware bits
https://www.manualslib.com/manual/16...roduct-MSD6886
p28 shows a serial port connection to the earphone port. My TV has both an earphone and service port (also earphone plug shape) right next to it. Service port plug solder points appears to show its just a TRS 3.5mm plug port
https://www.headphonesty.com/2019/04...uctor_plug_TRS
Looks pretty easy to make the DB9 to TRS 3.5mm cable (pin 2/3/5) and can buy these off the shelf programming cables
https://www.youtube.com/watch?v=4riU...elliteTrackers
Then its onto finding software and this TV's boot/firmware bits.
Flashing in boot/firmware via serial ports is pretty standard Android flashing process. Recently did this on my Chinese Android HeadUnit for the car. Just need the cable, Flashing firmware (usually from main SOC maker) and trigger SOC to reset.
Anyone has experience with this? Also probably unlikely to get boot/firmware bits from HiSense so probably need a flash in a raw dump?
I'll try heating the main SOC slightly to see if any help but given the % of firmware failures on this TV, corruption boot/firmware seems the most likely candidate.
Comment