Backing up (applications and settings) an Android tablet?

[John Doe]

Did you take your meds today?

Too busy getting sucked off by your mom, Assfur.

 

[SC Tom]

I don't expect it to be easy as Macrium Reflect, but the restore must
work 100% of the time, whether it's that method or some other method.
The problem with partial backups is they get confused. And I'd rather
not root the device, especially if the maker installs Android free of
bloatware.

OK. The backup of 1.8GB is correct because the "-system" switch is not used
in the example command line (I wrote a little batch file to perform the
backup, naming it <today's date>.ab). I may try one later with that switch
added, but I wonder then, if the internal memory is wiped, would adb (or
even a Macrium-like program) be able to restore the backup, including the
file system? Unfortunately, it's not like a PC where I could throw in an
empty hard drive and test how well the backup/restore works. I really don't
feel like trying to do a restore over my existing (working) tablet.

I have a regular Cloud backup scheduled, and I know that I can restore the
OS to the original JB4.1, then let it update itself to JB4.2. Once that's
done, it'll automatically restore my apps, settings, and data from the
cloud. I had to do that a couple of months ago, and it took about 45 minutes
from start to finish. Since I have no way to easily test out the adb method
of backup/restore, I think I'll stick with a method that I know works. I do
think I'll create a full backup (including system files) just to keep on
hand so if something does happen, I can test it out before using the tried
and true method

Thanks for your help and interest in this. It's always good to try out
something new, as long as you can get back to where you were when you want

 

[Astropher]

Too busy getting sucked off by your mom, Assfur.

Do you often have fantasies of being fellated by geriatrics? That is
pretty sick. I think you need more meds.

 

[Gene E. Bloch]

I used to put a little nutmeg in my netmug with my netcoffee, but it
tended to irritate my throat and make me a little netcoughy.


Sensibility is highly overrated.

OK, I have to say that you managed to net a win with that post.

I especially liked "nutmeg in my netmug" - it twisted my brain nicely.

 

[Gene E. Bloch]

It's little things like that which make the world a better place.

Thanks. I agree, even if that other guy can't.

 

[John Doe]

Here are two more sources of information on doing a complete
Android tablet backup without rooting (or before rooting).
Apparently all require "the Android SDK, and updated the Android
SDK Platform Tools to the latest version using the SDK Manager".
The Titanium Backup page scantily refers to it as "your ADB".

http://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-howtos.html#backup-without-root

http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351

 

[John Doe]

I disabled power settings and used the Titanium Backup recommended
command...

adb backup -f FullBackup2.ab -apk -all

The backup process was clear enough, including "backup finished"
overlaid on the home screen. It took a few seconds. The backup
file was about 35 MB (no user apps installed).

My Samsung USB driver file name...

SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail

I'm a bit suspicious, but finding multiple instances of those
files has been difficult. There is supposed to be one on Samsung's
site, but the link doesn't work for me...

http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows

 

[John Doe]

Looks like doo doo to me. Doesn't even replace the Device name on a
restore. Doesn't remove downloaded apps. Resetting the device removes
downloaded apps, but then you have to go all the way to the developer
options again or it won't communicate. This backup method apparently
isn't anywhere near complete. I suppose I'll try Titanium Backup with
the thing rooted.

 

[John Doe]

The following writeup sounds like a good summary for backing up
an Android device...

http://android.stackexchange.com/qu...complete-backup-rooted-nexus-4-with-stock-rom

I'm afraid there isn't really a "one-stop solution". As you
already noticed, all the different backup types have different
goals, all of them have their pros and cons (see also our backup
tag-wiki for an overview):

while a Nandroid backup covers the entire system at
partition-level, it's not the easiest when you want to only
restore parts. On its own, it's an all-or-nothing. Luckily,
there are other tools which can deal with those backup files:
you can restore single apps with Titanium Backup, and even
read single files from them (see: How do I view/mount nandroid
file on device?).

Titanium Backup covers almost everything on an
app-and-settings level, and can read from Nandroid backup
files -- but it cannot create a full Nandroid backup. Also,
restore between different ROMs can be a little tricky (but
that applies to all solutions), at least when it comes to
system files. Still, it does a good job even then when using
its "migration mode"

ADB backup is a good thing, but only available with Android
4.0 upwards and also restricted to "apps and settings".
Additionally, it requires a computer to attach the device to
for backup/restore. The latter can be avoided using apps like
Helium - App Sync and Backup, which run directly on the device
and use ADB as backend.

I found the best solution on rooted devices is a combination of
Nandroid (offered e.g. by ClockworkMod Recovery) and Titanium. For
non-rooted devices, choices are rare: neither of the two are
available there, which leaves the user with ADB backup as the only
half-way complete solution.

 

[John Doe]

I'm getting into the TWRP recovery and root stuff. Found a stock
firmware/ROM for my device and installed it using Odin. Seems very
strange that everything went well but my settings appear to be
intact. I would think that overwriting the ROM would erase
everything. Uhg.

Next, I will try installing the TWRP thing, make a backup, reset
the device to factory, and then restore the TWRP backup.

 

[Paul]

I'm getting into the TWRP recovery and root stuff. Found a stock
firmware/ROM for my device and installed it using Odin. Seems very
strange that everything went well but my settings appear to be
intact. I would think that overwriting the ROM would erase
everything. Uhg.

Next, I will try installing the TWRP thing, make a backup, reset
the device to factory, and then restore the TWRP backup.

You would hope what you just did, didn't overwrite the entire
ROM. A machine like that, needs to keep the boot loader and
firmware updater, intact. Plenty of stuff must be preserved
between attempts to load an OS. Otherwise, the thing could
become "bricked".

Paul

 

[SC Tom]

The following writeup sounds like a good summary for backing up
an Android device...

http://android.stackexchange.com/qu...complete-backup-rooted-nexus-4-with-stock-rom

I'm afraid there isn't really a "one-stop solution". As you
already noticed, all the different backup types have different
goals, all of them have their pros and cons (see also our backup
tag-wiki for an overview):

while a Nandroid backup covers the entire system at
partition-level, it's not the easiest when you want to only
restore parts. On its own, it's an all-or-nothing. Luckily,
there are other tools which can deal with those backup files:
you can restore single apps with Titanium Backup, and even
read single files from them (see: How do I view/mount nandroid
file on device?).

Titanium Backup covers almost everything on an
app-and-settings level, and can read from Nandroid backup
files -- but it cannot create a full Nandroid backup. Also,
restore between different ROMs can be a little tricky (but
that applies to all solutions), at least when it comes to
system files. Still, it does a good job even then when using
its "migration mode"

ADB backup is a good thing, but only available with Android
4.0 upwards and also restricted to "apps and settings".
Additionally, it requires a computer to attach the device to
for backup/restore. The latter can be avoided using apps like
Helium - App Sync and Backup, which run directly on the device
and use ADB as backend.

I found the best solution on rooted devices is a combination of
Nandroid (offered e.g. by ClockworkMod Recovery) and Titanium. For
non-rooted devices, choices are rare: neither of the two are
available there, which leaves the user with ADB backup as the only
half-way complete solution.

Yeah, I was finding that out from my own attempts. Seems like without it
being rooted, you cannot BU the OS, but if you root it and something goes
wrong, you can't restore it to the original OS. Damned if you do, damned if
you don't. I think I'll stick with my apps being backed up locally, and on
Google Cloud (since it's an Android). If it gets too broken to fuss with,
I'll get another one and restore my apps. After all, they're getting cheaper
(I read your other thread, too).

 

[John Doe]

"John Doe" <jdoe usenetlove.invalid> wrote
Yeah, I was finding that out from my own attempts. Seems like
without it being rooted, you cannot BU the OS, but if you root
it and something goes wrong, you can't restore it to the
original OS.

Well... In the last 12 hours, I've done that twice. There might be
two different ways. Use either CWM (ClockworkMod) or TWRP (Team
Win Recovery Project) to make a complete backup before rooting
your device (rooting might be required before the restore, I
dunno). Or find the stock firmware for your device like I have and
use Odin to restore/write it.

My understanding isn't thorough, but I've crammed a lot in the last
24 hours. A combination of a custom recovery like CWM or TWRP and
Titanium Backup might be in the same ballpark as Macrium Reflect
with its ability to browse and copy from backup archives.

https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackupPro&hl=en

 

[John Doe]

My job... Figure out which one is best to go with, either CWM
(ClockworkMod) or TWRP (Team Win Recovery Project). There is no
generic answer because the versions of those differ by device.

 

[John Doe]

John Doe wrote:

You would hope what you just did, didn't overwrite the entire
ROM. A machine like that, needs to keep the boot loader and
firmware updater, intact. Plenty of stuff must be preserved
between attempts to load an OS.

Yes that spells it out. Some stuff must be preserved. On a PC,
that's easily understood as what's on the motherboard versus
what's on the harddrive. That isn't so easy to see on the tablet.
I just want functionality similar to Macrium Reflect on a PC. I
know it won't be as easy or complete, but my backup system for
Windows rocks and (if possible) I will apply it to tablets from
the get-go.

Perhaps the best resource is here...

http://forum.xda-developers.com/galaxy-tab-3/development

(they probably have the same for most models)

 

[John Doe]

I think it goes like this...

Restore the factory firmware.

Reset all settings (I don't understand why the factory firmware
doesn't do that).

Use a program called "Odin" to install/write CWM or TWRP (that is
"custom recovery firmware" I guess, I'm going with TWRP 2.7).

Make a backup.

Configure settings and install programs, then make another backup,
and so on. At some point it can be done systematically using
notes.

Rooting might not be required to make or restore backups. But
rooting is required for Titanium Backup and other stuff.