View Single Post
Old 12-29-2023, 07:16 PM   #56
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
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.
Yes, I was there, *i* was the one who reported it. (The fake registration that caused the issue was the one that was included with the Nickelmenu add-on.)

The SQL line posted here, however, works on all versions of Kobo firmware, and has never caused a problem. I've tested it on every firmware versions update since. (err, that is, until sideload mode became available).

And as I've already said, the *worse* case scenario is a database reset, that happens to kobo *all* the time. It is almost a 1st troubleshooting step people suggest here for any number of weird problems that crop up. It's a very silly thing to get hysteric about. If you care about your Kobo database, regular backups required regardless.
rashkae is offline   Reply With Quote