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.
Related
I just backed up a ROM (Malladus) in prepararation for reverting to a previous version. I received a failed error after completing the system restore on the old backup. I then wanted to test my newly made backup before further flashing and I got a similar restore error on a backup that was only 30 minutes old and on which no system revisions were made.
Any ideas?
Try restoring only system, data and cache.
Gnarfsan said:
Try restoring only system, data and cache.
Click to expand...
Click to collapse
I just tried that. The failed message pops up again immediately at end or in midst of system restore. Thanks for your reply.
Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.
I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."
Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!
chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it
Hello,
when I try to restore my TWRP backup of Lineage 17 on my Samsung Galaxy A5 2016 I run into the
extractTarFork() process ended with ERROR: 255issue, and have tried several methods which I have found when googling for fixes, but none has worked so far.
This is what I've tried:
- unmount the data partition before restoring backup
- just restore system, data and boot, tick off the others
- wiped data/system/cache, flashed rom+gapps, flashed backup with all sections activated (radio, system, data,...)
- wiped data/system/cache, flashed rom+gapps, flashed backup with only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, wiped dalvik/cache after, flashed backup w/ only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, reboot, clicking next on every configuration screen, reboot to recovery, restore only data from backup
The issue seems to always occur at the same point in the process, in the progress bar its either at ca 45% or 58%, depending on if only data or everything is supposed to be restored. Restoring everything _BUT_ the data partition works, but the stuff I need to access is the data.
Kind regards
Hello,
I managed to fully restore the backup follwing this guide
Now my phone boots up to the point right after the Lineage logo is shown, where it says "starting the phone" and would probably ask for sim pin if I had a sim card in it. Then it reboots and does the whole thing again.
Does anyone have an idea how to fix this?
Kind regards
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