View Single Post
Old 10-18-2015, 11:55 AM   #94
Nephiel
Member
Nephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolateNephiel is generous with chocolate
 
Nephiel's Avatar
 
Posts: 19
Karma: 33334
Join Date: Feb 2014
Device: Kindle Keyboard 3G
Looks like the panel is not reporting the correct ID.

IMHO your best bet would be opening it up and checking if the connector of the panel to the LCD is properly seated.

If that doesn't solve the problem, then the EEPROM data probably got corrupted somehow. You could try to fix that by reflashing it. And if that in turn doesn't work, then the EEPROM chip is probably damaged and you'd need to replace it or the whole panel.

For a software-based solution, you could try to force the waveform to load by editing the panel ID on the wbf file to match the ID your panel is (mis)reporting, but that requires rooting. I'd at least try reseating the connector first.
Nephiel is offline   Reply With Quote