View Single Post
Old 07-29-2023, 01:27 PM   #414
rogerinnyc
Addict
rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.rogerinnyc ought to be getting tired of karma fortunes by now.
 
Posts: 229
Karma: 944808
Join Date: Apr 2009
Device: Kobo Libra 2, Forma and Aura One; Kindle Voyage; Galaxy Note 10
@hchris Just ran into this and fixed it (running a rooted OnePlus 9 with Android 13 and Kindle 4.16)
.
I was trying to import the backup.ab file directly from where it was stored on my Windows PC -- deeply nested folders -- e.g., Users/[my name]/AppData/Local/Virtual Storage....etc. I think the plug-in struggles to import from there and throws up the error message we each got.

Instead, copy the backup.ab file to a common, low security, folder, such as "downloads" and try to import it from there. You'll know it's done correctly if, after you click "choose back up file" and then choose your backup.ab file, the name backup.ab appears immediately to the right of the "choose back up" file tab in the plug in configuration dialog.

In other words, the error message was appearing because NO file was loading, not because the backup.ab file we generated is not a backup for kindle android file.

Hope that works for you too.
rogerinnyc is offline   Reply With Quote