Quote:
Originally Posted by davidfor
To be completely successful when restoring the database from a backup (I assume that is what you meant by "database made by calibre utilities"), the books need to be back in the same place as before. Otherwise, the first thing the device will do is compare what is in the database with what is on the disk and start removing the missing books from the database and adding the ones that aren't in the database. And you should shutdown the device as soon as you can after restoring the database and disconnecting the device.
I have done this enough times to know it works if I take care. And I have messed it up enough to now that I need to pay attention to what I am doing. Also, I don't use KSM and don't know if it would affect this, but, I wouldn't expect so if you are using a recent version of KSM.
My guess would be that if a large number of books couldn't be found, the process doing the cleanup might have been seen by sickel as hung and sickel triggered a reboot. I wouldn't have expected a continuous reboot, unless it hadn't actually removed any books from the database before the reboot happened or possibly if the database was corrupted.
|
Yes that is exactly what I was doing. I was transferring over the database and then it started processing the books. I think I messed up as it started deleting over 1000 books as I knew I had deleted them. My intention was to have the database with the books reading status and not the actual book link but I guess it did not work out. But I found it even easier to do what I do now and just import the reading stats with kobo utilities. It also seems that reading progress with kepubs is broken on current firmware so no big deal for me to restore the database.
Quote:
Originally Posted by tshering
I am not sure what you mean by bootlooping in this context. KSM does not care about the books and the sqlite database. Therefore I guess, what you are seeing is that nickel reboots, when you call it. But this does not force you to factory reset the device. It is however different, when you configured KSM so that it calls nickel immediately after boot (a setting that is asking for trouble).
I think I do not understand what you are doing. Just for clarification, to "register with the activation thing in KSM" means to bypass activation, unless you edited the scripts so that they contain your personal data. What exactly do you "transfer over KSM"?
|
The database loop was probably caused by sickel. The reader was also prompting me to factory reset as KSM was not installed on that try. It said something like ereader damaged, factory reset and there were two options to either deny or accept. I have never gotten that prompt before. But I have reinstalled again successfully and it works properly now. I am just going to be wary in the future with how I handle the database backups and decided that kobo utilities restoring read stats are a much better way of doing it.