Quote:
Originally Posted by nobody-knows-me
Hey, I just registered to say thanks a gadzillion to everyone who posted here with info help get this working.
A couple of notes for anyone else having trouble (especially re using map_data_storage.db) -
I did this on an android device, not with an emulator. So set everything up, rooted device, using 4.16 then -
adb backup com.amazon.kindle
my device insisted on a password, which meant the ab file is encrypted, so dedrm could not read it, so I then had to install abe-jar and do
java -jar abe.jar unpack backup.ab backup.tar password
I then tried several ways to stuff the decrypted backup.tar file into dedrm, but none seemed to take. No error, but also no text saying the file had been accepted - it looked like dedrm simply didn't see it as an appropriate file and ignored it.
I then found the posts about manually removing the map_data_storage.db file from the tar archive and using that (its in the db subfolder).
This worked!
But - if you are trying this - dedrm WILL NOT accept the map_data_storage.db unless it is named map_data_storage.db and nothing else. This took me a long time to work out!
I had stupidly renamed it as I extracted it because I figured the name didn't matter.
IT DOES.
So for the next idiot who does that - rename map_data_storage.db and all will be well.
Thanks again everyone.
|
Did you try changing the extension of the
.tar to
.ab? If you didn't, please try it. You probably seen that the backup has multiple
.db files, so it makes sense to only allow the correctly named file to pass. Haven't looked at the code of the plugin myself, but I would program it to attempt to unpack the backup first (the logic most likely is to look if the extension is
.ab), then go to the next step to specifically look for
map_data_storage.db.