View Single Post
Old 05-16-2014, 11:45 AM   #4
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: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Unless it's a 3G device, or it downloaded the OTA beforehand.

In any case, in the K5 family, and since FW 5.3, the update format changed, and the code path used to apply it too. The factory updater does a battery level check before proceeding with the update. I've never actually tested it myself, so there's still the possibility of a bug somewhere, but I'd look somewhere else for the initial cause of the issue.

The whole MfgTool mess on Windows has always been awful, which is (partly) why Kubrick was born, so it couldn't hurt to try from Kubrick dropped to a CLI shell, see if you can get any further.
NiLuJe is offline   Reply With Quote