Thread: Firmware 4.31.19086
View Single Post
Old 02-04-2022, 02:12 AM   #235
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by jfp555 View Post
This update bricked my kobo clara hd and i had to to a manual sd image restore using the image provided by the kindness of Davidfor on this forum. I want to know if I should attempt the update again? I want to read a bunch of articles through Pocket and everytime i click on the sync button, it tries downloading the update again.

Is there a way to stop the update? Also, I used the sql trick to never sign into the device when I initially set it up. Would that be the reason for the bricked update?
It is unlikely that an update actually bricks a device. About the only way for it to happen would be to lose power at exactly the wrong time. Your post where you requested the image mentioned doing a manual restore by holding the button down for 30 seconds. All that does is forcibly turn the device off. A manual factory reset requires the device to be connected by USB when turn on and the power button is pressed down.

The other reason a device might seem to be bricked by an update is if the SD card is failing. And if that was the case, then it would only be a matter of time before it happened. The update might trigger it, but, mainly because it is writing to different parts of the SD card.

Others have reported issues with different updates. But, from what I can tell, the issues are already there and the reboot needed to install the update just means that the actual problem is finally noticed.

At this point, you may as well try the update. It will probably work. But, if it fails, then you have the image and can restore it. If the update is a problem for you, there is probably a patch to block it.
davidfor is offline   Reply With Quote