View Single Post
Old 05-16-2014, 11:13 AM   #2
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by KingD View Post
My Kindle PW stops working several days ago. The device was jailbroken long before. Nothing particular is done recently and I'm using the native reader on that day. I pressed power button to start reading, but the device did not respond immediately. I tried several times before giving up. Minutes later it suddenly shows the content of the book that I last read. It does not respond to anything since then, however, including long pressing the power button.

I first thought it was due to low battery. So I charged it overnight. No luck. Then I took apart the device and gave the battery an full charge. Now it could be recognized on Windows as a USB HID device. I checked several forum posts. It seems that my device is in USB download mode.

I tried with the "simple debricking methods". I used Mfgtool from a Windows 7 guest VM (Mfgtool does not work on my 64bit PC as it always crashes on selecting USB ports). Mfgtool reports success on switching to fastboot, but when I use the fastboot tool, it stuck on "waiting for device". The driver generated by inf-wizard is already installed.

Any clue for this? or maybe it's an hardware issue? The device is already out of warranty. Thanks in advance.
Without the device in hand, I can only offer a guess -
but a very reasonable guess based on your details.

"I pressed power button to start reading, but the device did not respond immediately."

It was busy with an OTA update.

"I first thought it was due to low battery. So I charged it overnight. No luck. Then I took apart the device and gave the battery an full charge."

Yup - it was a low battery (low storage capacity battery due to age and/or use patterns).
Not enough stored charge to complete the OTA update.

So now your flash chip is corrupted.
https://www.mobileread.com/forums/sho...49&postcount=3
I.E: Your Kindle just "self destructed".

What you see is the firmware's "fall back" response to its inability to load and run the (trashed) firmware image.
knc1 is offline   Reply With Quote