Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle

Notices

Reply
 
Thread Tools Search this Thread
Old 10-21-2011, 10:36 PM   #1
jimmythesaint
Junior Member
jimmythesaint began at the beginning.
 
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)
  • Soft reset
  • Hard reset
  • Factory reset
  • redownloading the file

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.
jimmythesaint is offline   Reply With Quote
Old 10-22-2011, 12:20 AM   #2
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 4,656
Karma: 4440239
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2
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.
NiLuJe is offline   Reply With Quote
Old 10-22-2011, 12:42 AM   #3
jimmythesaint
Junior Member
jimmythesaint began at the beginning.
 
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:
11022:030854 init: Switching to runlevel: 5
111022:030854 No USB/Charger found ... entering low power idle
111022:030854 Charger: Turning on CPUFreq
111022:030855 system: I wifi:def:WiFi Device mac = 28:EF:01:33:67:BD
111022:030855 ar6000: Shasta Atheros Ar6000 WiFi Driver
111022:030855 ar6000_probe: initializing!
111022:030855 kernel: I perf:wifi:wifi_driver_loaded=24.29 seconds:
111022:030857 AR6000 Reg Code = 0x80000348
111022:030857 system: I wifi:def:loadAR6000 finished, args=()
111022:030858 system: I wpa_supplicant:def:wpa supplicant started
111022:030859 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=31C:from pmic
111022:030900 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=31C:from pmic
111022:030900 system: I otaup:defrocessing update /mnt/base-us/Update_525120101-611680021.bin
111022:030900 system: I otaup:def:version is "FC02"
111022:030928 system: I otaup:def:update image checksum OK
111022:031004 system: I mntroot:def:Making root filesystem writeable
111022:031004 EXT3 FS on mmcblk0p1, internal journal
111022:031004 webupdate: I def:webupdate::hop path:
111022:031004 webupdate: C def:webupdate::update path for device (06/536720111) does not exist
111022:031005 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=31C:from pmic
111022:031006 system: E otaup:def:image update failed
111022:031007 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=31C:from pmic
111022:031008 system: I mntroot:def:Making root filesystem writeable
111022:031010 system: I S30network:def:initializing network configuration
111022:031010 system: I S30network:def:Installed Firewall
111022:031011 system: I S60dbus:def:starting system message bus
111022:031011 pmond[2521]: W def:nopid::No pid file specified
111022:031011 pmond[2521]: W def:nopid::No pid file specified
111022:031011 pmond[2522]: I def:init:mond running
111022:031011 lipc-set-prop[2569]: I lipc:ssprop=start, source=com.lab126.pmond:Set string property
111022:031012 powerd[2572]: I def:accel:found=0:Accelerometer
111022:031012 powerd[2572]: I def:acc::Turn acc port on
111022:031012 Accessory port enable
111022:031012 mxc_keyb: I def:unlocked1:status=unlocked:
111022:031012 fiveway: I def:unlock1:status=unlocked:
111022:031012 powerd[2572]: I def:battinfo:cap=49%, mAh=755mAh, volt=3773mV, current=-192mA, temp=86F, bp=3773mV, lmd=1526mAh, cycl=1, cyct=6:
111022:031012 powerd[2572]: I lipc:evts:name=battLevelChanged, origin=com.lab126.powerd, fparam=49:Event sent
111022:031012 system: I S70cmd:def:starting CMD daemon
111022:031012 lipc-set-prop[2702]: I lipc:ssprop=start, source=com.lab126.pmond:Set string property
111022:031012 cmd[2717]: I def:starting::Starting Connection Manager
111022:031012 system: I S70wifid:def:starting wifid
111022:031013 lipc-set-prop[2726]: I lipc:ssprop=start, source=com.lab126.pmond:Set string property
111022:031013 cmd[2717]: I lipc:gsprop=state, source=com.lab126.powerd:Get string property
111022:031013 cmd[2717]: I lipc:giprop=driveModeState, source=com.lab126.volumd:Get int property
111022:031013 cmd[2717]: E def:drivemode:error=3:Cannot get the lipc property
111022:031013 cmd[2717]: E def:baddrivemode:error=3BUS returned bad value for USB drive mode
111022:031013 cmd[2717]: I lipc:gsprop=cmState, source=com.lab126.wifid:Get string property
111022:031013 cmd[2717]: I lipc:gsprop=cmState, source=com.lab126.wan:Get string property
111022:031013 cmd[2717]: I def:intfna::No connected network interface
111022:031013 cmd[2717]: I lipc:giprop=isCharging, source=com.lab126.powerd:Get int property
111022:031013 cmd[2717]: I def:started::Connection Manager started
111022:031013 No Accessory Found
jimmythesaint is offline   Reply With Quote
Old 10-22-2011, 09:33 AM   #4
dwig
Guru
dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.
 
dwig's Avatar
 
Posts: 953
Karma: 1351860
Join Date: Dec 2004
Location: Paradise (Key West, FL)
Device: Current:Kindle 3/WiFi Retired:Clie - UX50, T415, ...
Quote:
Originally Posted by jimmythesaint View Post
T... 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.
...
Sounds similar to the failure I encountered. (see: http://www.mobileread.com/forums/sho...d.php?t=153888 ) This update cycles through 2 or 3 such partial updates.

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.
dwig is offline   Reply With Quote
Old 10-22-2011, 02:23 PM   #5
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 4,656
Karma: 4440239
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2
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.
NiLuJe is offline   Reply With Quote
Old 10-25-2011, 10:52 PM   #6
jimmythesaint
Junior Member
jimmythesaint began at the beginning.
 
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?
jimmythesaint is offline   Reply With Quote
Old 10-26-2011, 10:38 AM   #7
misling
Connoisseur
misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.misling ought to be getting tired of karma fortunes by now.
 
Posts: 92
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.
misling is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

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


All times are GMT -4. The time now is 09:42 PM.


MobileRead.com is a privately owned, operated and funded community.