View Single Post
Old 11-05-2014, 11:27 PM   #118
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
Quote:
Originally Posted by Inkblot View Post
I'm not sure why, but installing this patch (in the first post) with only a few modifications caused my Aura to factory reset. (Not a big deal for me as it took all of a few minutes to get back up and running with calibre; except for sideloaded fonts—Recycle Bin to the rescue!)

However, installing the same patch after the factory reset with the exact same modifications except to add the three extra patches in the second post worked perfectly. Any idea what's up? Could a corrupted database cause this? (I ask because once when connecting to my PC prior to installing the patch the first time it gave a bad database error and wouldn't connect immediately.)
(Edit: In another thread it was suggested that if the database is corrupt, the device might continue to function normally until it is restarted, and then do a factory reset. Since patching causes the device to restart, this could fit what happened to you.)

It could happen if the device was running the wrong firmware version before the patch, and then updated to the correct version after the factory reset.

But my Glo did a spontaneous factory reset when testing a faulty patch in firmware 3.3.0, so I know it is possible for a bad patch to cause the problem too.

Last edited by GeoffR; 11-06-2014 at 02:11 AM. Reason: Cause could be a corrupt database too ...
GeoffR is offline   Reply With Quote