Backlight issue LG 50ln5600

[Steve L]

Re: Firmware eeprom LG 50ln5600

Well, for 50LN5600, LG.com support has no software upgrades available, either. It means if no upgrades, then no software file available there.

Seems strange that data pins are grounded on this samsung:



I would just find a used bd on ebay or something. Just saw one for $28. /free ship.

[Shane711]

Re: Backlight issue LG 50ln5600

Yes, you are right, no software available for the 50LN5600. I even contacted LG and they couldn't help. Of course the TV is working now because I bought a used board but I have another board here that is no good without a new EEPROM. For the time being it is on the back burner. One day when my knowledge increases it will be fixed. I am guessing the EEPROM is not the normal IC and may even be located in the Main IC.

[Steve L]

Re: Backlight issue LG 50ln5600

Ya. Doh, doh. I was not up to speed on this still. On my Samsung schem, the data pins--p1,2,3(A0,1,2) are really logic inputs--not data inputs-- for like chip enab, output enab, write enable-- so SDA is serial data input and SCL is the clock for that--all that's needed for read/write.

So--eeprom IC IS normal (24c256)-- but you can either replace IC, get upgrade firmware from LG, or find .rar file on internet. Sometimes repair kits with eeprom are available on internet/ebay. I doubt there's memory for this file in CPU on board.

A bad eeprom is not all that common, though--especially on stuff not made in very cheap places.

I usually replace main board for 25-$125. because time is money--but interesting all the same.

Best of luck! What is symptom with this TV? You probably googled it to death already.

[Shane711]

Re: Backlight issue LG 50ln5600

The TV would turn on and be stuck on the LG logo, after about 1-2 minutes the TV would turn off.

[Agent24]

Re: Backlight issue LG 50ln5600

IC100 is apparently the EEPROM, a 24C256. Why they marked it with the cryptic code of "4HA7" I have no idea. All other SMD EEPROMS I have ever seen have the standard part number on them.

If you're feeling keen you could try copying the data from the working board's EEPROM to the bad one and see if it fixes it.