Showing posts with label Nandroid. Show all posts
Showing posts with label Nandroid. Show all posts

Friday, 23 October 2015

Updating Exodus Nandroid Restore Issue



Sorry if this has already been asked; I tried searching, but I couldn't find anything.

I'm running Exodus version 5.1-20150911-NIGHTLY-bacon, TWRP 2.8.6, Exodus stock kernel
I'm trying to update to a new nightly, but I always get stuck in a bootloop.

Here's what I do:
Reboot to recovery
Nandroid backup
Wipe data, system, cache, Dalvik
Flash the new ROM (I tried COS 12.1 once, but it didn't work; I mostly try flashing the latest Exodus nightly_
(sometimes) Flash xposed-v74-sdk22-arm-by-romracer (it doesn't make a difference if I don't flash it)
Restore only the data from the last nandroid

Now when I reboot I'll just be stuck in the boot animation or I'll be able to pass the animation and I'll just be stuck in a loop setting up the apps.

If I don't flash xposed, but still restore the nandroid I'll boot up faster, but I get System UI has Stopped and then the phone goes into a boot animation loop
If I don't restore the nandroid it works fine and boots up way faster.

How can I update while keeping my app data (my xposed data isn't that important to me if that'll make a difference)?



Thursday, 22 October 2015

TWRP Nandroid backups of /data won't restore



None of my /data backups from the past month will restore. Instead, each restore will end with "extractTarFork() process ended with ERROR=255" (more from log below).

Code:


file: //data/data/com.android.externalstorage/lib
  ==> extracting: //data/data/com.android.externalstorage/lib (symlink to )
symlink(): No such file or directory
FAILED RESTORE OF FILE i: //data/data/com.android.externalstorage/lib
E:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/04ce21cdcfd6c9c3/2015-10-22--16-35-10/data.f2fs.win000'
I:Error extracting '/data/media/0/TWRP/BACKUPS/04ce21cdcfd6c9c3/2015-10-22--16-35-10/data.f2fs.win000' in thread ID 0
E:Error extracting split archive.
E:extractTarFork() process ended with ERROR=255


Here's the setup:
Recovery: Multirom TWRP (2015-06-30 2.8.7)
ROM: CM12.1 nightlies and more recently crDroid (CM12.1 based)
F2FS formatted /data, /cache, /sdcard

Here's what I've done to investigate:
1. Thinking the problem had to do with compressed backups, I uncompressed using Nandroid Manager. No difference.
2. Thinking the problem had to do with the backup being spread across multiple .win tar files, I concatenated them into one .win tar file. No difference.
3. Thinking that perhaps I could unarchive the tar and adb push the /data partition. It pushed fine and booted, however the davlik cache wasn't rebuilt when booting and the OS was unusable due to FC.
4. Thinking that I just needed to remove the files/directories that were throwing errors during restore, I used tar --delete to remove files/directory from the nandroid backup. This was somewhat successful in that the restore would progress further before failing, but it would just throw a similar error for another directory.

I haven't figured out why these backups won't restore, but I've thus far resorted to just restoring my most recent backup that will restore. The problem with this is that my future backups seem to have this same problem of not being restorable.

What to do?



Wednesday, 21 October 2015

Not Able to Take Nandroid BackUp in TWRP (V2.8.7)



Hi

When i try to take backup in TWRP it says E:Unable to mount storage
Then BackUp Failed

Pls Help need to take a Backup


Thanks & Regards
Tharun Gowd :(



Nandroid backup for the G3, is it "safe" (CloudyG3 2.5, TWRP)?



Hi Guys,

I need to return my G3 for fixing the bezel crack under warranty.

Assuming that I'll get the same device back, is it safe to do a Nandroid backup with TWRP (v2.8.7.0), return the device to stock and when I'll get it back do a restore to the backup?

Can it cause a "weird" problems (I know from experience that other brands are ok with nand backup&restore)?

Thanks



Performing NANDROID on S3 with no display



So I dropped my beloved S3 and the display is dead. The screen is blank, but I can still answer calls since touch still works and I remember where to slide to answer calls.

It's probably just a connector that's come loose and I can probably fix it by disassembling it over the weekend but I really can't do without my contacts, messages and app data until then.

I'd like to do a NANDROID and transfer the contents over to another S3.. Is there any way to do this without looking at the screen? For e.g. in download mode with odin? I believe I had cwm 6.0.4.x touch and neatrom installed.

Any suggestions would be much appreciated!