View Single Post
Old 12-30-2023, 12:26 AM   #62
rashkae
Wizard
rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.rashkae ought to be getting tired of karma fortunes by now.
 
rashkae's Avatar
 
Posts: 1,274
Karma: 5935030
Join Date: Jun 2011
Location: Ontario, Canada
Device: Kobo Aura HD
Quote:
Originally Posted by DNSB View Post
Basically? Factory reset a Kobo Glo and fake registered it using the SQL kludge. Safely ejected and checked it seemed to be working okay. Reconnected, copied 20 or so books over from calibre, safely ejected, let them import, reconnected and let calibre update the metadata. Checked and looked okay. Reconnected to my computer, copied the newest at that time firmware version, safely ejected, appeared to complete the update, rebooted, popped up an error message and factory reset itself.
You will appreciate that there is not nearly enough detail here to even try replicating.,. (What firmware versions, what SQL kludge, etc...).. in any case, the I think you are mistaken. Not about the sequence of events, but cause and effect. Kobo forcing a Factory reset is almost certainly to be because of an error reading the root partition, or very corrupt filesystem on the user partition. If there is a critical error with the database, kobo simply deletes and re-creates it. (Errr, assuming it doesn't not detect the problem and does other weird thinks like not save book positions, )
rashkae is offline   Reply With Quote