I recently destroyed the screen of my OnePlus One and had to send it in for repair. I used TWRP to make a Nandroid Backup before packing the device. Yesterday, I received a new device, obviously not having my apps and data. So I moved my backup onto the device, but when I try to restore it, I get errors. When restoring the data partition, it will get to 79% and then say E:extractTarFork() process ended with ERROR=255. I tried it multiple times with the same result. Unfortunately, I obviously cannot try creating a new backup. All other partitions restore without trouble. According to the log files, the file causing the issue is //data/dalvik-cache/arm/data@app@com.instabridge.android-2@base.apk@classes.dex. What can I do? I thought it might help to delete the file as the Dalvik Cache is just a cache that will be recreated, but how do I delete files or folders from a Nandroid Backup?

I am using Cyanogenmod with CWM and am currently doing a manual weekly Nandroid backup (plus daily scheduled TitaniumBackup runs). Needless to say, it is easy to skip or forget. Is there a way to have the nandroid backups automated? I.e., I would like the phone to shutdown into recovery once a week, do a backup, and reboot.

Is it possible to boot up Android so flight mode is activated? When I set airplane mode before rebooting or creating a nandroid backup the setting will stick. Are there any files like init.d that are easy to modify where these kinds of boot options are stored? Another alternative would be a modified Custom Recovery. But I haven't heard of one. *Use case:* *Restore an old Nandroid Backup, but before the system fetches all the updates (messenger...) the user wants to restore certain app data so nothing gets lost.* That is only possible when in flight mode.

My objective is to be able to create a master 'image' of an android tablet, and then duplicate that image across about 200 identical tablets to streamline the administration of a university's pool of loan tablets (e.g. to roll out updated/new apps, to 'clean' them when they are returned, etc.) What would be the best way to do that? (I've seen a number of posts around the subject, using nandroid backup, adb, zen toolkit, and so forth, but all rather old and nothing definitive) - Currently the tablets are Samsung Galaxy 10.1 (GT-P7510) running stock Android 4.0.4 - but it'd be nice to have a procedure that ought to work if these are replaced by some other tablets. - The tablets aren't currently rooted, but could be if that made things much easier. It'd have to be a real advantage, though, as that might compromise the warranties on future new stocks of tablets. - These tablets don't have external SD storage, but it'd be great to have a process that would re-initialise ALL aspects of a tablet, even if it did have external (or ancillary internal) SD storage. - I'd ideally like to create/document a procedure that someone in basic first-line tech support could follow. - If it could avoid having to buy 200 paid app licenses, then that'd be great too :) I'd appreciate any pointers you folks could give on how best to do this: I would imagine with android tablets becoming much more popular over the past year, that there must be corporations, education establishments and the like doing this...

I'm running Android 13 on a device for which there is no TWRP nor OrangeFox recovery module: it's a Pixel 7 Pro. I'd like to perform the equivalent of nandroid backup/restore, and I'm wondering if there are any ways to do this. To be clear, I'm not looking for any "backup" apps (*e.g.*, SwiftBackup, TitaniumBackup, *etc.*) which only back up apps and maybe call logs and messages. I want to be able to back up and restore all the OS partitions such as /system, /boot, *etc.*, which a working nandroid implementation can do. I know that partitions can be backed up using dd-based methods, but if I take a dd backup, then upgrade my OS, and then decide that I want to return to the earlier OS, I can't use dd to restore, because the encryption would have changed. Is there perhaps an EDL-based method for doing what I'd like to do? Thank you in advance for any ideas and suggestions.

I want to switch ROM for testing purpose. Before that I want to make a NANDROID backup of current ROM so that if anything goes wrong with the new ROM, I can restore the backup to remain at the same point at which I made the backup. I had been doing this before when I had phone with Android 4.1 (jelly beans) with TWRP. Now the system is: - Phone: Redmi Note 10 Pro - Android 13 - MIUI 14 - TWRP 3.7 Can we still make backups and restore then as we do in older Android versions? Best Regards

Is it possible to export all phone data (phone settings, installed apps, app data...) and import it to another device (different model) in one shot? What I'm looking for is a way to "mirror" all data in a device to another device (e.g. when I buy a new phone, or when I have to repair my current phone and use a spare phone in the meantime), avoiding losing time restoring manually all phone settings, reinstalling every app from the Play Store, restoring app data with Titanium Backup, configuring all icons and widgets on my home launcher, and so on... I'd like to switch on the new device and find it the same (except for hardware differences). I'm thinking about PCs with Linux OS. If I take apart the main hard drive from a PC and put it in a new PC, most of the time it works flawlessly (and I find exactly everything I had before). I always root my phones and install LineageOS. So I'm thinking: I could - nandroid backup the /data partition from the first phone with TWRP - unroot the new phone and install *the same* LineageOS ROM in the /system partition (obviously not the same file, but the same nightly for this new device) - restoring the old /data partition to this new phone Do you think it could work? Or are there limitations I don't know about?

Every so often, I need to extract files from a backup. I'm aware Titanium Backup can do this, and there are no doubt other apps capable of the same, but I want to do it on my PC where the backups actually reside. Files with the .ext4.win extension are simple enough -- just open in WinRAR or similar -- but .emmc.win files are another story. Are there any tools to extract, or, ideally, mount .emmc.win files in Windows?

I embarked on a planned factory reset and hence started the procedure with a Nandroid backup (via TWRP) of all available partitions. Following the reset, after restoring the data partition from the backup, the boot sequence gets stuck on "Phone is starting...". After five minutes (or so) the phone restarts and then says: > Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device. ...providing the option to "Try again" or "Factory data reset". Restoring any other partition from the Nandroid backup produces no issues, it's only when the data partition (the most important to me) is restored does this issue occur. The backup is not corrupted, as the digest verification succeeds. Do I have any other options other than: 1. Discard the backup and start from a blank slate. 2. Start from a blank slate and manually extract the most important data from the data partition. ? Ideally I'd like to be able to diagnose the root cause of the "Phone is starting..." issue, address it and continue to use my phone as it was prior to the first factory reset. I have done this restore process successfully before, but this time it's just not working for me. - Phone: Fairphone 3+ - OS: Stock - Bootloader: Unlocked Restoration procedure I do (following a factory data reset): 1. Boot phone. 2. Follow prompts to set same screen lock as prior to reset. 3. Restart phone into fastboot mode. 4. Boot into TWRP (using screen lock credentials to decrypt data partition). 5. Restore from backup.

I installed: Samsung_USB_Driver_v1.7.23.0, opened: odin3_v3.14.4 and started Odin 3. In AP I uploaded the file: twrp3.1.1-1_J330. I booted my Samsung Galaxy J3 2017 SM-J330FN in download mode; I connected it to the PC via the data cable and clicked START in Odin 3. The smartphone restarted in mode: TWRP. I tried to backup the system to SD card with TWRP, but every now and then it gave me errors and in the end it appeared: Backup Failed. Where is the mistake? Can someone help me? Thanks

I've been trying to find information on what's included in the **data partition** when doing a nandroid backup. I couldn't quite figure if it includes: + Media files (images, videos, music) + User apps + Configs + System Apps + Configs + Whatever else... Reason being, I wondered if I could just backup system and boot: + The media files are synced using rsync. + The system apps are updated anyway when flashing new ROM. + The user apps are backed up using titanium or whatever. This could save some space of my backups, since I don't have much to spare - having no external sd slot and only 16gb of storage...

On Rooted Android 4.1, I have it set up to be able to make NAndroid backups through terminal emulator. What I hope to do is schedule a Tasker job to create a NAndroid backup and then copy/move it across wifi to my PC, so I can schedule it to run once a week in the middle of the night. I know MV will move files/directories, but I'm not sure how to specify the network share as the destination. I'll keep looking into it, but if anyone has already solved this one I would love to hear about it!

I'd like to start making scheduled backups to my rooted OnePlus 3T (Oxygen OS 5.0.1) in order to prevent the loss of data from any reason that could occur. I want to save everything: the entire content of /sdcard and the apps+data. I know doing a Nandroid Backup with TWRP is the best way to make a complete backup of an Android device quickly, but i have a question: Is it possible to recover data without the original device? If i had a totally new device, would it be possible to extract some specific data from the backup? (For example, read and extract the /sdcard/download directory from the backup, or also extract the data from a given app)

I recently had to reflash my phone. And am now missing my old default notification sounds. I originally flashed CM10 and later upgraded to CM11. Now I wiped the phone and CM11 directly. In this new installation I am missing the notification sounds I used before (namely something like "cm-chime" and "cm-prechime"). How can I get them back? 1. Is there a repository on the internet, where I could download them? 2. Where in the ClockworkMod backup I made before wiping are the notification sounds stored?

I have a Xiaomi Redmi Note 4x (mido) with the stock ROM installed – never flashed another ROM. I have bootloader unlocked, TWRP (3.6.0.9-0), and root access with Magisk. I have also made a NANDroid backup of all of my partitions, except the 0mb cache partitions. I want to try out a custom ROM, but might want to revert to the stock ROM using the NANDroid backup if something goes wrong. **My question is**: which partitions will be rewritten if I flash a custom ROM? Arrow OS, for example. If I want to revert back to my stock ROM using the NANDroid backup, which partitions will I need to recover? I am a beginner here, sorry if this a bad question.

Can someone help me with a crashing TWRP backup. I am using twrp 2.8.6.0 I have installed TWRP recovery for Samsung Galaxy Grand Duos gt-I9082, but it keeps failing and rebooting to the phone in the middle of 22% of the backup. I am running Jellybean 4.2.2 Stock Samsung Android dist. Has anyone ever faced this problem ? Can anyone help ?

I've been backing up my device (128GB internal storage) fully through: adb exec-out "dd if=/dev/block/mmcblk0 2>/dev/null" > H:\mmcblk0.img (I specifically need a full system image this way, that's why I'm doing it) As you know, adb has no progress bar. Right now, the file on my PC mmcblk0.img seems to be stuck at 125GB and has been for about 25 minutes or so, and I'm not sure what this means. The properties tab also shows the last modified date as about an hour ago, which is pretty strange. (mmcblk0.img = 125136398.233 kilobytes) When I run cat/proc/partitions, mmcblk0 on my phone is 122142720 kilobytes My napkin math says the PC image is about 3GB larger, but I haven't yet disconnected the cable since I'm afraid if I don't let the image complete till the end, it could end up as unreadable due to missing important information from the partition structure. However, if the last modified date is accurate, it might mean it spent an hour basically doing nothing. Does anybody have an idea of what I should do in this case? Is the image file useless or corrupt then if I unplug my cable? I'd rather not restart the whole thing again, as backing up 128GB of data takes an insane amount of time. If there's a way to somehow view or mount the image to check for that, it would be really amazing. Maybe like a Windows tool, or if not Linux even. I just want to view it basically and check that everything is fine.

I want to extract the Call/SMS App and the Remote controller App to install them in to a lineage OS version of the same phone. I have a original KDZ and nandroid made it with TWRP bootloader. The phone is not rooted. I was not able to do this. The phone is an LG G4 H815 (T-Mobile)

Years ago, I was able to make nandroids using CWM Recovery or TWRP. Is that possible on more modern versions of Android which encrypt /data by default?

I want to create a full backup. I have TWRP installed. But the problem is, part of my screen is not working, so I can't tap on options to enable storage (photos and stuff) backup as it doesn't do that by default. Basically, I want to tick everything on the backup options. And I can't do it through ADB because I don't have a computer right now.