View Single Post
Old 12-29-2023, 02:53 PM   #54
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,960
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by rashkae View Post
This problem has never occurred using the SQL statement discussed here, (regardless of the frantic claims to the contrary here.). But is always a possibility with the way Kobo reader operates, for a variety of reasons. (including, but not limited too, someone pressing the "Log out" button in the Kobo settins to see what happens.)

Currently, sideload mode is a much easier and overall better experience.
Oddly, my memory of events does not match yours. There was a Kobo firmware update where the SQL statement required to fake register changed. If you had the old fake registration in place when you updated the firmware, it triggered a factory reset. When this was reported, I was able to duplicate it.

And yes, sideload mode is unsupported but at least Kobo is aware of it.
DNSB is offline   Reply With Quote