Thread: Aura Sideloading issue
View Single Post
Old 10-15-2016, 09:13 PM   #5
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 DNSB View Post
As far as I recall, the sign out/sign in will not remove any ebooks on the internal storage nor will it change the running firmware version.
No, this will trigger an update check. It is done whenever setting up a user. If Garu wants to stay on a particular firmware version, he will have to use the desktop app.
Quote:
Using Calibre and davidfor's Kobo Utilities plugin, you can backup the database and in theory revert to a copy before the corruption. I've never used the restore procedure myself since I think of my ereader as device for reading books so losing the reading stats doesn't bother me.
Restoring a recent database backup should work. And the plugin can store the reading status of the books but not the actual statistics.
Quote:
The pinhole reset is like resetting or power cycling your computer and will not repair existing corruption. I've used it when I managed to hang my Kobo so badly that holding the power switch to power it off did not work.
There is a chance that a pinhole reset will cause the database corruption. If it happens the wrong time, then it will. Of course, it is just as likely that whatever caused the need to do a pinhole reset had already messed up the database.
Quote:
Generally, I'll try a sign out/sign in. If that doesn't fix the issue, I'll try a factory reset. If that doesn't work, if the device has an internal uSD card, time to rewrite the card otherwise hope for a miracle.
That's about right. Depending on the exact problem with the database, sometimes you can fix it. This mainly works if the indexes are corrupt. Rebuilding the indexes or doing a compress can fix it. I doubt it is the case here.
davidfor is offline   Reply With Quote