Quantcast
Channel: MobileRead Forums
Viewing all articles
Browse latest Browse all 50080

3rd Gen PW bricked after water damage; recoverable?

$
0
0
I have a Paperwhite 3/2015 (purchased November 2015) that was the victim of water damage. At first, the screen indicated the device needed repair. I put the device in rice for a week, then plugged it in. It appeared to reset successfully -- LED lit up, error message disappeared from screen, and it began to boot up. Shortly thereafter, however, it switched to an ad screen and it has been nonresponsive ever since. I have not been able to get the LED to turn on again, and nothing happens when I hold the power button for long periods of time.

I have some hope that it is not completely dead, however, since when I connect it to a Linux box there is USB activity:

Code:

kernel: usb 6-1: new low-speed USB device number 2 using uhci_hcd
kernel: usb 6-1: device descriptor read/64, error -71
kernel: usb 6-1: device descriptor read/64, error -71
kernel: usb 6-1: new low-speed USB device number 3 using uhci_hcd
kernel: usb 6-1: device descriptor read/64, error -71
kernel: usb 6-1: New USB device found, idVendor=1949, idProduct=dead
kernel: usb 6-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
kernel: usb 6-1: Product: USB Charger
mtp-probe[891]: checking bus 6, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1"
mtp-probe[891]: bus: 6, device: 3 was not an MTP device
kernel: input: USB Charger  as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/0003:1949:DEAD.0001/input/input12
kernel: hid-generic 0003:1949:DEAD.0001: input,hidraw0: USB HID v1.11 Device [USB Charger ] on usb-0000:00:1d.0-1/input0
kernel: usb 6-1: USB disconnect, device number 3

The device does not, however, show up at all in Device Manager on any Windows box.

I tried the Kubrick Live CD and was never able to get it to see the device.

Physically, the device looks completely fine.

I am wondering what my chances are of getting it to work again -- I believe I have exhausted all the USB-based options for troubleshooting but if I am missing something, please point me in the right direction. I am willing to try a USB-tty rescue if it is likely to bear fruit, but I'd rather not buy the adapter and spend hours taking the device apart if in the end I just have a permanently broken Kindle.

Is there anything more I can do to figure out whether the device can be saved? Anyone have similar experience with water damage?

Viewing all articles
Browse latest Browse all 50080

Latest Images

Trending Articles



Latest Images