View Single Post
Old 11-26-2016, 11:00 PM   #9
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
There is a reboot counter in "/var/local/upstart/lab126_gui.restarts" -- the contents of that file record the number of times the Kindle has unsuccessfully rebooted. After a couple of times, it goes to the repair screen.

The only way to get back out, is to overwrite the contents of that file, with the number "0" (right now it probably has a "2").

...

So assuming your Kindle is otherwise fine, that should fix it. As for the potential bad block, I cannot say... the Kindle should automatically detect broken storage blocks and remove them, but really, the diags partition shouldn't be getting frequently modified, enough to wear out the blocks, anyway???
eschwartz is offline   Reply With Quote