14

I have written some tools for exactly this purpose, due to similar frustrations: https://github.com/dlenski/tetherback These tools are written in Python and use adb to create either nandroid-style backups (raw partition images from dd if=/dev/block/mmcblk0pXX) or TWRP-style backups (mixture of raw partition images and tarballs for ext4 partitions). They ...


13

The two are actually quite different. Titanium backs up apps and settings only. Nandroid backs up everything including the OS. Titanium is useful when messing with apps and settings, since you have the option of restoring only what you want. Nandroid backups are largely for when you totally b0rk your phone and need to restore it to a more or less pristine ...


13

The answer can be found in the backup tag-wiki. In short: ADB Backup is the newer file based backup scheme introduced in Android 4.0. It creates a backup of the file system tree and files. Better explanation would be it's a logical backup, as files are mainly grouped by apps. Side-effect is that files not having a clear relation might be missing from such ...


11

The easiest way is to make the nandroid via a third party recovery (E.g. CWM, TWRP, PhilZ etc.) and copy that onto your PC of course. If this option isn't possible: From XDA Developers on Nandroid to PC This guide is intended to make a full backup of your android phone (the entire memory block with all partitions) or a single partition (including sdcards, ...


8

A thread on XDA developers describes How to make a nandroid backup directly to your computer without using sdcard. Of course it only works on rooted devices. Further requirements include either a Posix OS like Linux/MacOS (Windows users can emulate this with Cygwin), and ADB (so either the entire SDK, or at least a minimal install). Moreover, busybox must be ...


7

The size of your NANDroid backups is directly related to the amount of apps you have installed on your phone, and amount of data these apps store on your phone's internal memory. Even though CWM excludes the /data/media folder (which is usually mounted as /sdcard on newer Android OS versions,) the contents of /system and /data partitions alone will take ...


7

According to: https://wiki.cyanogenmod.org/w/ClockWorkMod_Instructions#Making_a_backup ClockworkMod's backup/restore feature will generally only back up the /system, /data, /cache, /sd-ext, and /dalvik-cache areas. Other partitions such as /emmc, /sdcard, and /media won't be backed up. In fact, the backed up system will typically be saved to ...


6

In addition to the well-known Titanium Backup app (for which you must purchase the Pro key to unlock the CWM/TWRP nandroid backup support), there is another app now: Nandroid Manager, which according to its description can restore apps from nandroid backups even with the free version (there is a Pro key too, but it is required if you want to restore special ...


6

To add to other answer, your back up has ALL the information in your back up image as the phone has when you took back up /system refers to your ROM /data refers to your data created by apps both that came with phone and user installed apps (/data/data) /data/cache (the cache) refers to app data stored for quick access /data/dalvik-cache (the Dalvik cache) ...


5

A nandroid backup is a full device backup – so you could ask the same question about a full backup of your PC: After restoring the backup, you'd be at exactly the state the device was in when you performed that backup – all changes done between making the backup and restoring it are lost. Reading between the lines of your question, you're rather asking how ...


4

I tested this, and your concern is valid. I added a dummy file to /system and then did a nandroid restore. The dummy file survived. Repeated the same test on /data with same result. So I don't know why CWM doesn't wipe those partitions first. The CWM author probably made an assumption it doesn't matter or there may be a valid reason they don't get wiped....


4

I noticed that (if you already have ADB configured, your phone is rooted and you're working on a Linux system or similar) it is possible to dump the partition content by a single one-liner: adb pull /dev/block/mmcblk0 This is the same as what is described in the XDA thread for getting the bit-for-bit contents of flash memory, except without the dance with ...


4

Unlocking the bootloader performs a factory-reset on the phone, deleting all the user data. It doesn't wipe the ROM. If you're just trying to back up the stock ROM before flashing (a sensible precaution), then you can safely do that after unlocking the bootloader. If you want to back up your user data (i.e. installed apps and their data, contacts, etc.), ...


4

That is the way nandroid works. Its NOT some bug. Yes, it does include /data partition but your data is stored in /data/media/0 which it skips during backup as this would lead it to backup everything inside internal memory increasing backup size significantly. In other simple words, nandroid backup's /data option includes only apps and their data, not your ...


3

Titanium Backup Pro can do that. [✔] Restore individual apps+data from CWM backups! Similar question.


3

ClockworkMod needs to be updated to properly understand Android 4.2's new filesystem structure so it can see its previous backups. Technically, everything stored on the sdcard is actually stored under /data/media, however Android uses bind to essentially make a really fancy shortcut to various other places. This includes /storage/emulated/ and /sdcard. As ...


3

Titanium Backup is able to read from Nandroid backups, so you can use it to restore parts from them -- and then use Titanium Backup again to backup those restored parts. However, as there's no Titanium Backup for PC, this has to be done on an Android device. If your goal however is to separate some apps from a Nandroid backup, there are other ways to ...


2

Recovery images are hard coded to use the first partition of an SD card are the main FAT partition. As such, you need to ensure that the first partition on the card is the FAT partition, or recovery will try to mount the ext partition as the fat partition. You can use any partition tool to modify the card. You also said that fastboot wouldn't work - this ...


2

For certain devices, such as the Nexus 7, that is not possible because the stock ROM unifies /data and what would normally be used as an SD card with FUSE mounts. If the restore program erased the /data partition, it would wipe out the backup because it's stored within /data. For example, with TWRP it'd be at /data/media/0/TWRP/BACKUPS/(deviceSerial)/ in a ...


2

Show Developer Options (Settings > Developer> tap build 7 times) Enable USB Debugging (Settings > Developer > USB Debugging) use recovery to avoid OS root limitations ./adb reboot recovery do the pull ./adb pull /dev/block/mmcblk0 mmcblk0.img


2

That's because you backed up the older Android version, so when you update from 5.1 to 5.1.1 you install a new version then you try to restore the backup, you will got the previous version 5.1. You can try to restore data only, but i think it will crashed. For future updates use Titanium Backup to backup all of your data and then when you install the new ...


2

[Can I just use my 4.4.4 Nandroid on my current 5.0 OS to get all my apps and stuff back?] Take a look at Nandroid Browser: With Nandroid Manager you can restore data from your nandroid such as apps+data, text messages, call logs, and much more. ... Nandroid Manager currently supports nandroid backups created by TWRP and Clockworkmod (v5.xx and v6.xx) ...


2

My experience tells me that for TWRP to detect backup files the latter should be in a directory whose name would be shown as the name of the backup and that directory in turn should be under: /sdcard/TWRP/BACKUPS/<serial>/ Here, replace <serial> with the serial number of your device. You can find the serial number of your device using the ...


2

ext4.win is a posix tar archive according to the file command. The only partitions I have in a TWRP backup that are emmc.win are boot recovery and system. Those are basically the same as boot.img, recovery.img, and system.img but renamed. These are ext partition images and you can read the contents of them with ext2read tool.


2

I can confirm that TWRP -- the latest version as of writing, at least -- recognizes, decrypts, backs up, and restores the contents of adoptable storage correctly. Note, though, that just as it ignores /data/media/, it also ignores /external_sd/media/, so be sure to backup that folder manually.


2

Is it technically possible to do a block-level (dd) backup of a file? - Yes Is it technically possible to do a block-level (dd) backup of a folder? - No


2

Answer to your question is dm-verity: The dm-verity feature lets you look at a block device, the underlying storage layer of the file system, and determine if it matches its expected configuration. It does this using a cryptographic hash tree. For every block (typically 4k), there is a SHA256 hash. So /system and /vendor partitions are always mounted ...


1

I once extracted single apps and apps data using a normal archiver explorer in my Arch Linux system. In Windows, 7-Zip FM or Winrar should do the trick. Obviously it is quicker done if you restore the full backup all at once with a custom recovery (but I believe you already merged the archive parts the backup is done in), but I once made a backup after the ...


1

To restore a nandroid backup, the device cannot be in "normal operation mode". You have to boot into your (custom) recovery (see our tag-wikis on: recovery-mode / clockworkmod / twrp), from where you can trigger a full restore. With ClockworkMod Recovery, it is e.g. found in the Backup & Restore sub-menu. Stock recoveries don't offer taking/restoring ...


1

Stock recovery's don't offer this feature, you would need a custom recovery to backup and restore.


Only top voted, non community-wiki answers of a minimum length are eligible