View Single Post
Old 05-22-2012, 10:55 PM   #6
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: 5,108
Karma: 4987077
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW & PW2
You're rebooting your Kindle with a custom .bin in the userstore. Don't.

Always use the 'Update Your Kindle' link from the Settings menu. (I get that it might be tricky with a broken screen, but there's not much else we can do about it without a shell).

FYI: That's an error from the recovery updater you're seeing, which runs at boot, and expects an amazon signed recovery update, while we're providing self-signed ota updates for hacks. The ota updater throws U00N error, not N .

EDIT: Or, apparently, updatewait can pickup custom updates, so, err, just let it sit in screensaver mode for a while, it should pick it up (too lazy to check the timers right now ;D).

Last edited by NiLuJe; 05-22-2012 at 11:19 PM.
NiLuJe is offline   Reply With Quote