Thread: Kobo Sage and Libra 2 released (pre-order)
View Single Post
Old 10-19-2021, 10:34 PM   #221
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 mbovenka View Post
I didn't really expect the DB copy to work; I have tried that twice before when migrating to a new Kobo (from an Aura HD to a H2O, which did work, and from the H2O to a One, which didn't). I don't know what the initial firmware version was; I forgot to look, and it started updating (to 4.29.18730) as soon as I connected it to my WiFi.
The issues I have seen with copying the database are around the contents of the "user" table. It might work to copy that to the old database before putting it on the device. That would be to do the setup, export the contents of the user table, import it into the old database and then try to restore that.

I can see some other differences in the database for the new firmware. But, they shouldn't block this and the automatic migration should cover them. I am assuming the the old device was on firmware 4.28.18220. The older it was, the less likely it would work.
Quote:
It had to import about 1100 books, so I think it just took too long and sickel kicked it over the first two times (at 40 and 63% done).
That will be particular books. Sickel should not kick in for the overall import. In fact, I had one running for several days importing over 10000 books. But, it can kick in for a particular book. Those are probably different books as it should have done the import for the ones before it hit these. It's possible the books were borderline for causing the problem, but, when done after a lot of others, triggered them the sickel reboot.
davidfor is offline   Reply With Quote