View Single Post
Old 06-02-2012, 11:20 AM   #3
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by ixtab View Post
Generally, if you're only using the device (i.e. if you only used tested and verified methods to modify your device), and don't poke around a lot in the system internals by yourself, the risk of a real FUBAR brick is low. And even then, there is always a remedy.
There have been a LOT of reports of official amazon updates bricking kindles that did not have any jailbreak or hacks installed.

There have also been reports of bricks caused by registering a newer kindle to an amazon account that has too many books linked to it. Something as symbol as synchronizing your kindle to your amazon account can apparently brick a kindle (probably caused by the 30MB persistent user storage limitation).

The debricking tools have been downloaded MANY hundreds of times, so I think that a most of successful debricking goes unreported, and a lot of this happens to people who use their kindles ONLY to read books.
geekmaster is offline   Reply With Quote