Quote:
Originally Posted by AlanHK
Not a big deal if I have to re-sort the books manually to collections.
I'll do the one for currently reading and sort the rest to genres later.
|
OK. Then the quickest and easiest fix is to:
backup documents directory
"factory" reset
restore documents directory
But since you manupulate metadata in ways that risk fouling cc.db I think it would be worth your while exploring the contents of cc.db to get insight into what is going on.
If you jailbreak, you can rename cc.db and let your kindle rebuild it. If something goes wrong, you can rename the original back to cc.db
You could also make a backup copy of cc.db before doing something risky. If you retrigger the problem, you could remove the offending book then restore the backup cc.db
I will also reply with more information in your Developer's Forum thread, but it will require some research and I have some pressing requirements on my time.
Quote:
|
I did a little SQL in the 70s, but even if I could get up to speed, I think less work to just let it rebuild from scratch, if the only info lost is collections.
|
I think your previous SQL experience will make it easier for others to help you track down the root of the problem.