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).
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, ...
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 ...
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 ...
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.
fact, the backed up system will typically be saved to ...
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) ...
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.), ...
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 ...
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 ...
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 ...
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
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 ...
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 ...
[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) ...
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.
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:
Here, replace <serial> with the serial number of your device. You can find the serial number of your device using the ...
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.
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 ...
Is there any way to do a 100% NANDROID backup without any warranty voiding?
Nandroid means using custom recovery (TWRP or CWM ) and in turn unlocking boot loader (on most devices). Whether this voids warranty or not depends on a) OEM b) Country / region specific laws. It depends on case by case so a general answer is not possible but in most branded devices ...
Since I have a MTK-6577 based phone and had to delve into repairing a broken partition table recently I thought I'd take a stab at answering this.
I want to know that when we flash specific partition images (say
system.img, data.img, cache.img, etc.), then how does the software
know where exactly to put those partition bytes?
If you flash to known ...
I looked at the onandroid script and it seems that it does a block-level copy of the data with dd only for partitions that are not mounted during the normal system operation (such as recovery partition) and copies the files on the filesystem level from the mounted ones - meaning it copies the decrypted content of the data partition and others and creates a ...
A softbrick usually renders the user unable to boot into Android OS successfully and satisfactorily, and most of the time you can boot into a custom Recovery (you would be having it if you mentioned Xposed) and then use the ADB commands to restore the backup from there.
ADB backup method isn't useful in case of Xposed Framework since ADB doesn't make any ...
An indirect possibility would be using tasker, which has the capability of performing actions "on device start" (amongst many others). So you could setup a profile that says: "on device start" → "set airplane mode on". Other automation apps like llama might have the same capability.
Note however that the action can of course only be executed as soon as the ...
Nandroid backup invloves backup of everything, including:
/system(which is your "android version and os" in rough words, also includes the preinstalled apps)
/boot(which is your kernel)
/data(all apps you installed and their data (like app settings). This does Not involve your personal files)
/cache (the application cache)
When you nandroid restore as ...
A backup created via recovery is a nandroid backup.
Yes, the nandroid backup created by any recovery (CWM, TWRP) will be exact replica of the phone state when the backup was taken- that means it'll have all the files/ data that you have on the phone.
Here is a good article about nandroid backups
You probably search for the contents of your internal SD card (the Pictures directory I assume).
Then you need to explore the data backup. Inside there should be a media directory (and then maybe a 0 directory). This should contain your internal SD card's content of your user. There you can explore all your data.
Small side note: Not all backup methods ...
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 ...