|
If it's rooted, plug it to your computer, enable debugging on the device and run adb logcat on the computer. Maybe you can see something in the logs that will help you deduce what the problem is.
Two possible reasons that I can think of:
- Maybe the filesystem where you have your books is corrupted. Check it.
- Maybe the database is corrupted. This happened to me once and this is how I fixed it. Look for a file ending in .db (I don't remember the name, I don't have the reader with me). To try to fix it, you can rename it and then use a sqlite client to dump it and immediately import it back to a file with the original name of your .db file. On gnu/linux you'd just use the sqlite3 client on the command line (mv yourfile.db tmp.db; sqlite3 tmp.db .dump | sqlite3 yourfile.db). On windows I don't know.
Good luck!
|