My nandroid backup screws my Nexus everytime. I backed my Nexus first with TWRP, restored the backup after installing franco kernel and supersu just to check and behold it 'failed to restore system' don't exactly remember the code. It was 25x. I flashed the factory image, installed CWM, installed SuperSu made the backup installed the same kernel and installed xposed. Xposed caused my device to be caught in a soft brick so i restored the backup again and, it again failed to restore system. What exactly am i doing wrong.:silly: Im tired of having to restore factory images.:crying:
I think I've found the problem. :good:
Related
So my Nexus was acting really slow (I'm on 4.2.1), so I decided to backup via CWM and then factory reset, and do an Advanced Restore to restore my data. I backed up and did factory reset, but when I went to restore my backup, it couldn't be found. Apparently 4.2 moved the default CWM location to search "data/media/" and I didn't have my backups there (obviously). So I moved the clockworkmod folder from /sdcard/ to data/media/ and tried to restore. It gave me an MD5 mismatch, so I researched that, found a solution, and did restore. Unfortunately, that bricked my Nexus 7 so I had to restore via the ToolKit.
My question is…is there any possible way I can restore my data to my now factory-fresh (4.2.1) Nexus 7 from the backup I made? I have the backup and the blobs.
Bump, the same thing just happened to me and I dont want to create a new thread. Is there any way to restore a 4.1.2 backup from a device running 4.2.1? Thanks in advance
EDIT: I solved it by booting into CWM and then pushing the rom, full wiping and installing again
Hi experts,
I would very much appreciate some help regarding the following:
I have a Samsung Galaxy S5 SM-G900F with factory installed stock rom G900FXXU1BPA2 (Android 5.0). I used the SkipSoft Unified Android Toolkit 1.4.5 to root the phone and install TWRP recovery (2.7.1.0-klte as recommended by Unified Android Toolkit). I made a first Nandroid Backup and was able to successfully restore this backup (I restored boot, system and data to verify that Nandroid restore works). I then used Titanium Backup to restore my apps from another phone, and all was well.
A week or so later I wanted to modify something I wasn't sure I wanted to keep (using apktool). I therefore made a second Nandroid backup and then proceeded to make modifications to the phone. After I saw the result, I didn't like it, and therefore restored the second Nandroid backup. After rebooting, the phone gave a flurry of forced stops ("Unfortunately XXX has stopped"). It is not a bootloop but I can't do anything meaningful with the phone other than restart it.
To try and resolve this, I used TWRP to wipe cache and dalvik cache and rebooted. The phone went through the lengthy "Android is upgrading" process but the result was the same: all my apps force stop.
I then decided to try and restore the original first Nandroid backup (which I had been able to restore successfully earlier), and this resulted in the same issue. Since I have several backups of this first backup I was able to verify that the files were good. Also did MD5 checksum verification in TWRP and it all checked out.
Using Odin, I was able to restore a stock ROM from SamMobile (G900FXXU1BOL1_G900FOJK1BOL1_ILO) and after restart, the phone works as usual, but of course all my apps and data were gone.
I was then able to use TWRP to restore only boot and system from the second backup, so I would be back on the exact same ROM that my phone came with, and this worked just fine; the phone started as if factory restored.
I then used TWRP to restore only data, and this resulted again in the same problem: all apps force close. Note that this is a restore of data only to the same phone running the exact same ROM that the Nandroid backup was made on, and it still did not work.
I have been thinking about this issue and searching through the various forums but I did not find anyone having this same exact issue. Here are some questions I came up with:
1. Is TWRP 2.7.1.0 completely compatible with this phone and with Android 5.0? Would it help if I installed a newer version of TWRP? Would I be able to restore Nandroid backups made with TWRP 2.7.1.0 with TWRP 3.X?
2. Assuming my second Nandroid backup is not corrupt, is there a better (less intrusive) restore I can do of the apps? Can Titanium Backup read TWRP 2.7.1.0 backups and restore them, including SMS?
3. What could be the reason for TWRP 2.7.1.0 restore not to be working properly? I did activate the fingerprint reader after the first Nandroid Backup, but if that is the issue I would have expected that first backup (in which fingerprints were not yet enabled) to restore properly and it doesn't.
Would appreciate any help!
Thanks,
AH
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
https://dl.twrp.me/klte/
Flash .tar version with ODIN 3.10.7
TiBu can read Nandroid backups and restore apps yes
Not sure about SMS
The method you used to root and flash TWRP is not a usual method used here, most of us use ODIN to flash TWRP and then flash SuperSU from recovery
or use CF Auto Root to root, and then flash TWRP with ODIN
I'd flash stock again, factory reset, and then flash TWRP and SuperSU, then try restoring your apps with TiBu
*Detection* said:
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
dl.twrp.me/klte
Flash .tar version with ODIN 3.10.7
Click to expand...
Click to collapse
Thanks *Detection*! I installed TWRP 3.0.0.0 as per your instructions and restored just data. Same result as before.
Then I used TWRP 3.0.0.0 to restore the entire backup including system, boot, recovery, and data. Same result (of course I lost TWRP 3.0.0.0 and was back on TWRP 2.7.1.0).
This exercise was useful for one reason: I now know that TWRP 3.0.0.0 is able to read Nandroid backups from TWRP 2.7.1.0.
This is quite crazy but I seem to be unable to restore a full Nandroid backup and get a working system.
Am going to try Titanium Backup.
Thanks again!
AH
Long story short, I tried to install MultiROM on my Nexus 6P, and it failed. So I tried to restore my backup using TWRP 3.0.2.0, and it keeps failing at exactly 7800MB with the error E:extractTarFork() process ended with ERROR=255. I have seen posts talking about checking the log when this happens, but I'm not sure exactly how to do that.
What exactly do I need to do to restore my backup?
I guess I should add some detail. I first tried booting to recovery and restoring the backup. The phone rebooted into a boot loop part of the way through the restore process every time I tried that. Then, I tried flashing the phone completely back to the stock image, and then restoring. I got the error 255 above. Then, I tried flashing back to stock completely, wiping Dalvik/cache, and restoring the backup. I still get the same error message. I tried restoring everything except userdata, and the phone reboots part of the way through the restore.
I could easily reroot, reinstall Xposed, and reflash TWRP if for some reason my system backup partition is corrupted. However, I don't want to lose my data partition at all. That was the whole reason I made the backup in the first place.
I just rooted my S5 to PB1 (have '11 eMMC so no MM) per another thread in this forum and had set everything up, then decided to make a full backup with SafeStrap. I loaded Safestrap-G900V-4.04_LL_MM, installed it, went to recovery and then made a full backup to the SDCard.
After completing the backup, I ended up in a SS loop and somehow back to a completely reset phone (however still rooted). I am looking for how to reinstall the backup correctly.
I plan to load all the necessary apps to once again get SS installed and to recovery. Is there anything special to do once I RESTORE my backup? Do I need to also install LL_KERNEL_SS-FF_Flashable.zip again after the RESTORE?
EDIT: THE ABOVE IS WHAT NEEDS TO BE DONE. INSTALLED SUPERUSER.APP, THEN BUSYBOX, THEN SAFESTRAP FROM THE PACKAGE USED TO ROOT. ONCE IN SS INSTALLED MY BACKUP, THEN INSTALLED THE LL_KERNEL_SS-FF_Flashable.zip WITHOUT WIPING ANYTHING. GOT IT TO BOOT, STILL ROOTED, ALL FILES BACK...
Thanks
Frank
I'm getting enablefilecrypto_failed error after restoring nand backup in TWRP. Is there any solution? I know I can format data and install any ROM but I need some data from that backup.
How can I at least restore some data like sms, contacts from this backup? It seem Titanium Backup PRO cannot extract anything from it. I can't extract it with 7zip either (I read it somewhere it's probably TWRP's method of packing - f2fs.win000/win001/etc files, with matching sha2 files). Does it mean TWRP incorrectly encrypted this backup or is it incorrectly decrypting while restoring? I didn't get any error while backing up nor restoring (besides above, but that's after not while)
I'm also not sure if I had Magisk in this backup or not (maybe incorrectly uninstalled, which I tried to do apparently and lost device certification after and couldn't use gpay before said bootloop)
Failing to update Magisk was the reason that forced me to restore nandroid backup in the first place. But I'm getting above error even if I try to restore it from MIUI or any other lineageos.
you have backup, so copy it to PC, format data, install ROM and restore backup
My first sentence: "I'm getting enablefilecrypto_failed error after restoring nand backup in TWRP"
Solved it by uninstalling Magisk after restoring backup, even before first reboot