Thread: Aura H2O Critical Errors on DB restore
View Single Post
Old 05-29-2016, 08:17 PM   #9
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 youngmax View Post
Okay, I must have been confused about what firmware version I was using. There hasn't been a firmware update since January? Why did I just receive a notification about the new firmware version this week - is it because I updated Calibre to 2.57.1 this week, but had been using 2.55.0 since April?
What sort of notification? One the device? Or in calibre? Calibre displays a warning if the firmware version on the device is later than the firmware version programmed in the driver. As there hasn't been a firmware version released since January, you would need to be using a version of calibre from before this for this to happen. The Kobo Utilities plugin has a firmware check that can be run automatically. This will trigger if you haven't upgraded the device.
Quote:
I wonder if this is the source of the problem. I guess I'm not sure what versions of the firmware I was using at all, I was basing all those numbers on the presumption that the firmware update was this week, and until then I had the most recent firmware. Apparently not true?
If you were syncing with the Kobo server, you had the latest version. The sync always checks for an update and downloads and installs it before the rest of the sync. You can't stop this. Unless there is a patch that turns it of.
Quote:
Is there a way to pull that information from the backed up DB's?
Not really. The table "DBVersion" has the database version. But, that doesn't change for every firmware version. If you look, the value will probably be 125.
Quote:
I wonder if something crazy happened like I was using an old firmware version on the original device (not sure how, since it displayed a successful wifi sync in february) and that DB was copied to a device that was new in box with a different version, possibly the latest, but tried to upgrade itself incorrectly because the device firmware and DB were not in agreement?

There's probably a good reason David suggested to copy the user info from a new DB to the old backup DB, but with this much confusion I wonder if it might not be better to start a new DB and copy the reading positions over. Of course, if something mysterious in the firmware is rejecting data from other devices, this might not work either...
No, the reason I suggested copying the user info is that there is at least one key in the table that is generated on the device using information that is unique to the device. The firmware is probably validating this information against the device. Or it is sending it to the Kobo server to validate during the sync. I don't know exactly what is happening as I don't have access to the source. It is an informed guess based on inspection of the tables and the behaviour people are seeing.

If the point of all this is to get the reading statuses back on the device, then there is a way to do it. Use the Kobo Utilities plugin "Store/Restore reading status" function (can't remember exactly what I used for the menu). The quick and dirty steps are:
  1. Backup you calibre library (just in case).
  2. Configure the store/restore custom columns.
  3. Close calibre.
  4. Connect the device.
  5. Restore your full backup of the old device. This is everything: the database, the books, everything.
  6. DO NOT DISCONNECT THE DEVICE.
  7. Start calibre.
  8. When the connect jobs are finished, select all the books that are on the device and do a store of the reading status.
  9. Disconnect the device and let it redo the setup.
  10. Reconnect the device.
  11. Select all the books on the device and do a restore of the reading status.
  12. Disconnect the device and restart it.

If all goes right, then you will have the reading status set for all the books on the device. But, you won't have the reading stats or the bookmarks. If you use calibre to manage the collections, they should be back.
davidfor is offline   Reply With Quote