View Single Post
Old 01-05-2019, 02:39 AM   #30
Ruskie_it
Fanatic
Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.Ruskie_it ought to be getting tired of karma fortunes by now.
 
Posts: 538
Karma: 1000000
Join Date: Dec 2011
Location: Rome, Italy
Device: Kindle PW5, Kindle PW4, Kindle 4 NT
Quote:
Originally Posted by knc1 View Post
Not really, since it is a structured database.

It would take someone to keep a Kindle "in reserve" - that is, never put anything on it, update it with each Amazon image, copy what the "default" was at that time.
Or, maybe, do as you did, "reset" it after each image update.

That would be a master copy of what the database "recovery" image contains.

The database files would each contain everything an end-user script would need to review and repair any of the database files for the firmware versions our collection of "recovery" images contain.

Also, SQL has query commands to learn the schema and other metadata of each of the database files.

PLUS: This would not have to be done on a Kindle.

SQL is an interpretative programming interface (works unchanged on any machine - by design).
The database file structure is also "machine neutral", again by design.

And the Kindle comes with a choice of several interpretative programming languages.

Yeah, I know SQL (I work for SAP), I just didn't think about keeping a "reference" Kindle with nothing on it just for reference purposes on this specific task. I am not used to such a commitment to the hacking cause.

Quote:
You are interested in KOreader - did you by chance try to install KPVbooklet?
That is database Schema sensitive and the firmware you are trying to run it on is very new/recent, so most likely not supported by the current version(s).
Never heard of it. I wouldn't say I am interested in KOReader: I keep it on the kindle as an emergency escape in case I need to read something I can't read in any other way, but it never happens. I prefer to always have the same reading experience, and Koreader requires me to do things differently: put the books on kindle manually instead of calibre, not picking up the cover as a screensaver and so on.
But, I would give KPVBooklet a try.
I have a cutover this morning, so nothing right now, but if you share a link, I will look at it... Or I simply will look for it this afternoon.
Or... were you implying that it might have broken my db???
Ruskie_it is offline   Reply With Quote