[youngmax]

Originally Posted by davidfor

What sort of notification? One the device? Or in calibre?

Originally Posted by GeoffR

Is it possible the new device was runing 3.19.5761 but you applied a patch for 3.19.5613?

Although the notification about the firmware was originally in Calibre (pretty sure it was the Kobo Utilities notification of an available update for the device, though not 100%), I disconnected the device and updated by touching the sync tile on the home screen. Unfortunately the firmware status of the replacement device is unknown since it could have been sitting in its box since November for all I know. I don't have a backup of the new device's .kobo folder before I overwrote it.

Possibly of note, while setting up the new device I first tried logging into my kobo account and got to the home screen. Would that have been enough to trigger a check for available firmware updates? If so, there seems to have been no reason for the device to download an update, which I saw it doing. If a bare initial login without hitting the sync tile even once isn't enough to trigger an update check, it sounds like I was running a database from the most recent firmware on a 'new' device with older firmware.

Here's the contents of the version file from my backups of the original device:

N250553006736,2.6.35.3,3.19.5761,2.6.35.3,2.6.35.3,00000000-0000-0000-0000-000000000370

Here's the version file off the new device the day I received it, but I'm not sure if this is from before or after I overwrote all the files:

N2505B3901229,2.6.35.3,3.19.5761,2.6.35.3,2.6.35.3,00000000-0000-0000-0000-000000000370

Here it is from two days ago, just before I hit the sync tile and everything went to hell.

N2505B3901229,2.6.35.3,3.16.17,2.6.35.3,2.6.35.3,00000000-0000-0000-0000-000000000370

David, thanks for the restoration procedure. It seems my options right now are:

-Restore reading positions, RIP bookmarks
-Attempt a downgrade to 3.16.17? Not frequently done, might brick the kobo.
-Reset device, export user table from fresh DB to a CSV file, then load a backed-up DB and replace the user table from CSV. sqlitebrowser doesn't seem to have the ability to open two databases at once, which I suppose makes sense with the embedded focus of sqlite, so this is the best I could come up with.