BOOX NOVA3 — Seeking advice on backing up

[InspiredLife]

Hi folks,

I have a Boox Nova3. The screen has a fault, and I'll be sending it in for a warranty repair / replacement. I was told to back the device up before sending it in (in case it gets wiped/reset during repair process), yet Onyx provides no way whatsoever to actually back up their devices.

The main thing I want to backup is the Reader related data (book progress, book annotations and highlights). It would also be handy to back up the device settings, since it takes quite some time to get it set up the way I wanted it.

I've found I can access (and copy) what appears to be the system files, and also overwrite them. Such as the `Content/Android/data` folder, and all the app related sub-folders in there.

Does anyone familiar with this device have any suggestions on how to flawlessly back it up, and restore it? Ideally without having to root it (although I am open to that if there's a way to). Ideally by just saving the Reader related data files, or something to that effect.

Thanks very much ...

Jonathan

[Renate]

I'm not sure what "Content/Android/data" is, probably MTP-speak for /data?

There's a few ways to do this. One way is using adb backup.

C:\>adb backup -all -shared

"-all" means all app data, i.e /data/data/
"-shared" means /sdcard/
Add "-f whatever.ab" if you want to have the file named something besides backup.ab.
This command is deprecated but seems to work just fine. This makes a compressed (and inscrutable) .ab file.

If you're rooted your options depend on how it's rooted. If you can do adb shell and instantly get # (without using su) that's good. I'm not currently using Magisk and I'm not sure if "adb root" works on it or if you always have to use su. (I've modified so much stuff in the kernel, /vendor & /system that I can't easily boot into Magisk without restoring and it's too much bother.)

If your ADB is truly rooted all by itself (without su) then you can:

C:\>adb pull /data/data

You could also try my AdbSync.exe (in my sig) which allows bidirectional updating with many options.

If you have EDL you can save your whole data partition.

[InspiredLife]

Hi Renate,

Thanks for the assistance and suggestions.

Regarding, `Content/Android/data` ... it appears that's simply how the `/data/` folder was being presented in the Android file app I use on MacOS. Looking on the folder tree on the device itself, I can see it's the `/data/` folder.

I've now done a full backup using ADB.

If I end up needing to do a restore, it will be interesting to see what actually restores. I've read online that ADB restores some, but not all, things on Android devices.

[cicabum]

Originally Posted by Renate

I'm not sure what "Content/Android/data" is, probably MTP-speak for /data?

There's a few ways to do this. One way is using adb backup.

C:\>adb backup -all -shared

"-all" means all app data, i.e /data/data/
"-shared" means /sdcard/
Add "-f whatever.ab" if you want to have the file named something besides backup.ab.
This command is deprecated but seems to work just fine. This makes a compressed (and inscrutable) .ab file.

If you're rooted your options depend on how it's rooted. If you can do adb shell and instantly get # (without using su) that's good. I'm not currently using Magisk and I'm not sure if "adb root" works on it or if you always have to use su. (I've modified so much stuff in the kernel, /vendor & /system that I can't easily boot into Magisk without restoring and it's too much bother.)

If your ADB is truly rooted all by itself (without su) then you can:

C:\>adb pull /data/data

You could also try my AdbSync.exe (in my sig) which allows bidirectional updating with many options.

If you have EDL you can save your whole data partition.

Hi Renate. A question: What is the command to restore data? If there is already data on the device will it be automatically overwritten?

[Renate]

C:\>adb restore mybackup.ab

And yes, it will overwrite.

People are completely different in how they use their devices. For me, I have:

• hardware mods (UART & EDL switch)
• boot & recovery mods
• /vendor & /system mods
• Apps
• Content (books, tablature, references)
• Settings

I figure that if a truck ran over my Poke3 it would take me under 30 minutes to unbox and restore a new one. The hardware mods would take longer.

[cicabum]

OK, thank you Renate