MobileRead Forums - View Single Post

nobody-knows-me · 04-02-2023, 10:34 PM

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.

04-02-2023, 10:34 PM	#265
nobody-knows-me Junior Member Posts: 2 Karma: 90 Join Date: Apr 2023 Device: None	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.