MobileRead Forums - View Single Post - Help

NiLuJe · 11-14-2010, 01:09 PM

@quimby: That's the first I've heard of an update failing like that :/.

(Well, not exactly, there's a very few number of reports of things like that with official updates, but still, it's very, very, very uncommon, and more to the point, should *never* happen

.).

The Error 3 on restart is completely normal, on the other hand

. (The update process than run at the boot of the Kindle doesn't handle our custom update files).

Unlike official updates, killing the Kindle in the middle of the update proces with any of my hacks shouldn't leave the Kindle in a weird state, so you should be mostly good... (It'll probably leave some crap in the tmp folder, though, not sure if the boot process cleans up /tmp from time to time...)

My guess would be that, for some reason, your /tmp partition was full, and things went kablooey. What's strange is that the update process should handle these cases and fail, not lockup... But even that is somewhat strange, because the SS hack is not that big... :/

(Note that the number of custom SS you have doesn't change a thing, they're not part of the update process).

I'd very much like to take a look at your logs, see if something pops out...

(Type ;dumpMessages in the search box on Home screen, and attach the all_logs_as_of_* file created in the documents folder).

11-14-2010, 01:09 PM	#5
NiLuJe BLAM! 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	@quimby: That's the first I've heard of an update failing like that :/. (Well, not exactly, there's a very few number of reports of things like that with official updates, but still, it's very, very, very uncommon, and more to the point, should never happen .). The Error 3 on restart is completely normal, on the other hand . (The update process than run at the boot of the Kindle doesn't handle our custom update files). Unlike official updates, killing the Kindle in the middle of the update proces with any of my hacks shouldn't leave the Kindle in a weird state, so you should be mostly good... (It'll probably leave some crap in the tmp folder, though, not sure if the boot process cleans up /tmp from time to time...) My guess would be that, for some reason, your /tmp partition was full, and things went kablooey. What's strange is that the update process should handle these cases and fail, not lockup... But even that is somewhat strange, because the SS hack is not that big... :/ (Note that the number of custom SS you have doesn't change a thing, they're not part of the update process). I'd very much like to take a look at your logs, see if something pops out... (Type ;dumpMessages in the search box on Home screen, and attach the all_logs_as_of_* file created in the documents folder). Last edited by NiLuJe; 11-14-2010 at 01:15 PM.