|
|
Thread Tools | Search this Thread |
10-21-2011, 10:36 PM | #1 |
Junior Member
Posts: 8
Karma: 10
Join Date: Mar 2011
Device: kindle3
|
Kindle 3 (keyboard) update failing. "Specialists" unable to help. Can you?
This will be a bit on the long side, as I will explain exactly what is happening and what I have tried.
My kindle has apparently never been updated (it is still on 3.0.1). I noticed that I am several versions behind, and that it should have been updating in the background automagically. I went to amazon and downloaded the appropriate update to 3.3. I then copied it to the root directory, and it seemed to update fine. The update process ends in success. Then, rather than reboot, it re-enters the update screen, this time failing, and I am left with the old firmware. One strange thing is that the .bin update file is renamed to a bin file, the name of which is simply a long series of numbers. Also, the number "U006" appears at the bottom of the update failure screen. To troubleshoot I have tried (both on my own and with support on the line)
After each, I recopied the un-renamed update file to the device. I run linux, but that shouldn't matter. I have not hacked or jailbroken my kindle. The only bits of software it has interacted with are Calibre and that tool to help build collections. Neither should impact the system. Has anyone heard of this happening before? Any help would be appreciated. Also, if anyone has the MD5 hash of a legitimate update file, I could see if maybe the downloads were corrupted both times, though that is highly unlikely. Thanks for any assistance! Last edited by jimmythesaint; 10-21-2011 at 11:11 PM. |
10-22-2011, 12:20 AM | #2 |
BLAM!
Posts: 13,477
Karma: 26012464
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
The lightning fast update process, then reboot => update process in the middle of the boot screen is the 'normal' process for sideloaded 3.X updates, so there's nothing strange there (hence the different .bin you found, the first update actually only extracts the correct .bin depending on your current FW, and makes it run on the next boot).
If you're running a vanilla kindle, an update failure like that shouldn't happen, and could be the sign of some kind of software or hardware fault. Or a really unlucky random filesystem corruption after a crash/harsh usb disconnect/plain bad luck. You should be able to pinpoint which file is causing issues by checking the logs (on the home screen, in the search bar, type ";debugOn", then ";dumpMessages", then ";debugOff" (without the quotes), the logfile will be written in the documents folder) right after a failed update, and look for 'patch failure' or 'checksum failure' in there. Once you know that, you *should* be able to fix it, provided you're willing to hack your Kindle, muck around a bit in the root fs over ssh, and have a sane copy of the corrupt file(s) on hand. EDIT: I'd give you the MD5 hash of the K3G update file, but my HDD is dying, so, err, probably not a good idea ;D. There's an internal MD5 check in the update process anyway, and it's another error code than U006 (which is the basic 'uh oh, something went wrong during the update script' code ^^). Last edited by NiLuJe; 10-27-2011 at 01:46 PM. |
Advert | |
|
10-22-2011, 12:42 AM | #3 | |
Junior Member
Posts: 8
Karma: 10
Join Date: Mar 2011
Device: kindle3
|
The only error I found was:
111022:031006 system: E otaup:def:image update failed The checksum verification passed and there was no "patch failure" Error is listed in red. Any thoughts? Thanks man! Quote:
|
|
10-22-2011, 09:33 AM | #4 | |
Wizard
Posts: 1,613
Karma: 6718479
Join Date: Dec 2004
Location: Paradise (Key West, FL)
Device: Current:Surface Go & Kindle 3 - Retired: DellV8p, Clie UX50, ...
|
Quote:
Mine failed on the second part during my first attempt. The cause seems to have been a still running, unfinished indexing process for a newly downloaded book. The fix for me was to wait for indexing to finish (checking with the usual search for an unfindable string like "qwqwqwq") and then rerunning the update. |
|
10-22-2011, 02:23 PM | #5 |
BLAM!
Posts: 13,477
Karma: 26012464
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Huh, that's new :}.
Check again which FW you're running, because the update script seems to think that you're on 3.0.3... Which, strangely enough, the 3.3 update forgot to handle as a starting point... A simple workaround would be to dig up a 3.1 update (hint: replace a 3 with a 1 in the amazon url ^^), run it, and them do the 3.3 update again. Last edited by NiLuJe; 10-22-2011 at 04:16 PM. |
Advert | |
|
10-25-2011, 10:52 PM | #6 |
Junior Member
Posts: 8
Karma: 10
Join Date: Mar 2011
Device: kindle3
|
That was it. I WAS on 3.0.3
Updating to 3.1 first solved the problem. Thanks!! Now how do I let Amazon know about this? |
10-26-2011, 10:38 AM | #7 |
Zealot
Posts: 106
Karma: 510000
Join Date: Nov 2010
Device: Kindle
|
Send a message to kindle-feedback@amazon.com. I've had some good responses from them doing that, even though I was bugging them for new features.
Or call the kindle customer support number & tell them - make sure it's the kindle support and not the regular amazon support. |
03-08-2016, 04:18 PM | #8 |
Junior Member
Posts: 4
Karma: 10
Join Date: Sep 2010
Device: Kindle 3
|
For what it is worth, I was able to fix this issue after months, hours of searching...
If you follow this link: https://www.mobileread.com/forums/sho...d.php?t=206064 it will get you to a Unbrick Live Image, unbrick (even if your device is not bricked), USBNet into it, let the tool runs its course and it will flash a vanilla 4.1.1 onto the kindle (disable the jailbreak option), then you can follow the normal updates. Finally my kindle is back to its factory rom |
03-09-2016, 02:00 AM | #9 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Moderator Notice
Please don't respond to 5-year-old threads. Nobody's going to be remotely interested in your answer. There's a very good reason for the warning you get that you're posting to an old thread. Don't ignore it. Thank you. |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
"28, No space left on device" - memory card, unable to fill it! | jrr | Calibre | 4 | 11-11-2010 04:47 PM |
Firmware Update No "Update your Kindle" option in "Settings" | shimoncellos | Amazon Kindle | 4 | 05-26-2010 05:37 PM |
Firmware Update "Update Your Kindle" always grayed out with custom | Karlios | Amazon Kindle | 4 | 01-22-2010 12:43 AM |
Wispernet 5 Bars: "Your Kindle is unable to connect at this time" | Richie | Amazon Kindle | 4 | 04-14-2009 03:11 PM |