I'm getting "extractTarFork( ) process ended with ERROR: 255" whenever I try to restore the back up. I'm able to successfully restore system and boot without any issues, so it seems to be something to do with the data section.
I recently upgraded my TWRP to the latest so I tried to downgrade back to the previous version but it still doesn't let me restore it.
From googling, I've seen posts suggesting that people have been deleting a line by finding it in their log, but I'm unable to find the log nor do I understand how to edit it to try and solve the issue.
Any help would be appreciated
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255 when I tried to restore it. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.
sir..please help me.. I have a twrp backup of system image vendor image data boot recovery persist but im unable to recover because it shows an error extract tar fork process ended up with error 255
i also have a backup of my internal storage in twrp but im not able to restore because of this error
Related
I was deleting crap on my sd card to free up some space. I cant remember everything i deleted but now i can not get the card to read in the phone. It says it it not mounted. I have tried to remount it in settings but nothing happens it just says i can remove the sd card. I can not plug it in to the computer because the phone will not enter disk drive mode. I tried a nandroid back up but it says something about md5 sums mismatch.
I am running ARHD xd 3.6 with the kernal that comes with it as well as the preferred radio.
Htc said to do a factory reset of the phone. Which i would rather not do. Is there a way to reformat the SD card there is little on there that i really care about. Reformatting would be my last resort but if that is the only fix then sure. Thanks guys!
I would not reformat it unless you take the files to your computer. See if you can get a hold of an as card adaptor for your pc and transfer your files so you can transfer them back. Reformatting will completely erase everything and I don't know how your device will react to you having your custom Rom removed.
It won't have anything to go off of I would think. I've never had this problem but I'm giving you my heat advice. But reformat before you factory reset.
First you can try and use an sd card reader and reformat the sd card. If you dont have that you can do nandroid backup through recovery to save your system data and apps. Then do a factory restore, maybe even a EXT4 reformat. after that you can reflash your rom and restore your backups.
PS If you dont want to use recovery backups for any reason you can always use titanium backup for apps (I wouldnt recommend backing up system data), make sure your accounts are synced, and even use an sms backup app for your text messages.
I was scared the actual phone was not reading the sd card or that the ROM had stopped it from reading correctly so i grabbed my wifes 2gig card threw it in there and the phone read it no problem at all. I just put my card back in and did a wipe of it was clear of any errors and worked perfectly. Immediately after i made a nandroid backup.
I could restore a nandroid backup because they are stored on the SD card and since it was connected i was getting a md5 checksum error. I looked up the error and tried to push the back up through adb shell but once again with out the sd card reading correctly no restore could be done. All my contacts are saved through gmail, photos are all uploaded the gogole+ as soon as they are taken so really the only stuff i lost was my nandroid backup from the stock rom.
thanks for the help guys.
Ya it happens some times it sounds like your weren't too attached to anything on the card so that's good.
I've said it before make a back up of your back ups. Put em ib a safe folder on your pc if you can. Hope. You can get back to normal good luck.
I made a previous clean backup prior to rooting the phone using the Odin method posted by Copperhed. Still running the stock at&t rom.
All was well. I moved the backup file over to my computer hd to free up space on my external sd card. I was tinkering around with different sd cards last night and accidentally formatted my main sd card that I usually use on my phone. No big deal.
I decided to try out some new roms and kernels so I wanted to make a nandroid backup. Instead of using the odin method to install cwm, I downloaded rom manager and flashed clockworkmod recovery.
I formatted the sd card to make sure space wasnt an issue. I clicked on Backup Current ROM, it was given superuser access and the phone rebooted into CWM. I thought this part was automated but it wasnt. Once the phone booted into CWM, it just sat there at the menu system.
No problems, I navigated down to backup and restore, then hit backup. I did some google searching and people have said this version (5.0.2.7) of CWM does not show a progress bar while backing up.
After clicking backup, I get the usual screen of it mounting the card and displaying how much space is free, then saying it is backing up boot image, recovery image, and system.
Takes a long while then just gives me this:
Error while making a backup image of /system!
Click to expand...
Click to collapse
Any idea of why this would be happening? I searched around but did not find any solutions. The only core things I have installed on my phone currently is Titanium Backup Pro and SetCPU. The rest are just day to day apps, todolists, camera, games.
I've attached what it looked like below. In case the attachment doesnt work (http://i.imgur.com/2ZIPM.jpg)
Forgot to mention, after rebooting the phone when I get that error, I check the external sd card and see a backup folder, but there are only about 3 files in there, so it makes sense because it failed making a full backup.
I just now tried "back up to internal sd card" and it started working right away.. showing files and progress bar moving.
I guess this works too, I can still move the backup file over to my pc.. but this kind of worries me.. is CWM not seeing my sd card correctly?
Another update..
At the end of the backup run (to internal sd card) I get:
No sd-ext found. Skipping backup of sd-ext.
Click to expand...
Click to collapse
When I mentioned formatting the card earlier, I used the phone itself to format it.
I think it has something to do with the variance between the T-Mobile version of CWM we are using on our Skyrockets and what should actually be on the CWM version for the Skyrocket (which still doesn't exist--wtf?! )
Disregard the error message, it's looking for a folder on the T-Mobile version that isn't on the Skyrocket.
If you used the "Backup to Internal SD Card" from CWM you should be fine. I've backed up this way and restored backups without incident.
so if your phone went through a soft brick or something bad happened messing with different roms and such, youre still able to boot into cwm and restore from the backup file that is stored on your internal sd?
i just want to make sure, in the case that we cannot boot from cwm / access internal sd, that we will be able to do so from the external sd.
I don't have a whole lot of faith in our CWM (which was built for a T Mobile variant). I've had a ton of weird messages any time using it and I'm surprised there isn't more talk about it here. I've seen a lot people casually mention the error messages so I know it isn't just me.
I don't know you'd lose the backup if restoring from a soft brick where you'd have to go back to stock first to fix it (never tried it). But I can tell you that if you flash a rom you don't like or doesn't work right you should be able to successfuly restore a backup made in CWM (after wiping data, etc., of course).
Sent from my SAMSUNG-SGH-I727 using XDA App
All you have to do is install the rom you had when you made the backup for the data going to the advanced options in backup recovery and restore data only and ready
understood. but in the case that the phone does mess up and for some reason it doesnt read the external sd card, would i still be able to access the internal sd card for my backup with cwm?
Just got my G2SR from ATT. Going through the motion of rooting it following instruction here: http://forum.xda-developers.com/showthread.php?t=1340526
I also tried to do a backup to external SD and get the same "Error while making a backup image of /system"
I searched around and I tried the instruction here http://forum.xda-developers.com/showthread.php?t=1472954 by adding clockworkmod/.hidenandroidprogress in both /sdcard and /sdcard/external_sd/
It's still stuck in "backing up system". I have tried reformatting the SD card and perform error checkin on Windows, but that doesn't fix it.
Has anybody back up to the external SD card with CWM successfully?
And how exactly do we back up to the internal "/sdcard". When I go backup, it would complain I don't have an sdcard if I don't have the external SD card.
[update] I am on ClockworkMod Recovery v5.0.2.6 and I don't see any "backup to internal SD' option. Do I need to update my CWM and how do we do that?
Thanks in advance.
Hello,
I installed the latest cyanogenmod nightly. There were issues with the google play store so I had to switch back to a cyanogenmod 11 nightly from december. Unfortunately there was a problem with CWM and based on the information on the forums I flashed the old nightly manually in CWM. Unfortunately, my phone became stuck in a bootloop. I was not thinking clearly so I did not make a backup at the right time. I am trying to recover some data. I have first done a backup within CWM, it has apparently created a backup file in the /sdcard/. I then used "adb pull /sdcard/" to copy the contents of the /sdcard/ to a safe location on my PC. It seems to have worked but I am not sure. I do not know in which folders the data is actually stored.
(I don't know if reflashing the most recent nightly will work)
I was wondering if this solution will work, and if I will be able to keep the app data this way as well as retrieve a few pictures. Ideally I hope this will allow me to put the phone back to its original state at some point. I hear a factory reset deletes the contents of the internal sdcard on the moto g so that is why I am trying to copy it back to PC. But I wonder if I will be able to restore it afterwards. Any adivce would be greatly appreciated.
edit: uh oh seems adb pull sdcard has not completed successfully so I am at a loss at what to do
Is there an option in CWM or TWRP to mount partitions for access by a PC?
audit13 said:
Is there an option in CWM or TWRP to mount partitions for access by a PC?
Click to expand...
Click to collapse
Thanks for your help. I'm sorry I couldn't get back to you earlier. Thankfully I have been able to solve the problem by reflashing the cm12 nightly, retrieving the data from that, and then wiping the phone and reflashing an old snapshot. Now I will be careful with backing up my data in the future.
I don't understand why the cm12 don't work though. I get weird scan lines on everything, including the boot screen. I think it may be due to the google apps because they keep quitting. I will try something else.
edit: I will post this issue in a separate thread
Hello,
I made a backup of my phone using TWRP. When I try to restore from the backup I created, I get a "E:extractTarFork() process ended with ERROR=255" error message when it tries to restore the data.
Anyone know the fix for this?
Not much information there to even begin.
Did you back up to SD or internal storage? Did you back up everything except SD card? Is the phone set to use system storage as default install and storage space?
IMO, it works best when you don't allow the phone to use the SD card as install/storage, then a backup to SD, including all partitions is easy to restore. Also allow it to write an md5 checksum.
Most likely, you can't fix it now and will have to start again.
-Hello, today i wanted to restore a recent TWRP backup but i encountered an error while restoring datas (54%). I tried other backups many times and same error , i made a new backup from current ROM and again same error.
-Perhaps TWRP is making corrupted backups or is corrupted itself.
- If i delete the data.f2fs.win001 partition from backups or untick data before restoring it works but important system files are missing. Here is what i get in TWRP log:
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/00867e6ad793a5eb/2017-05-21--08-51-47_LMY48T/data.ext4.win000'
Error during restore process.
I:Error extracting '/data/media/0/TWRP/BACKUPS/Rooted Xposed customized LineageOS 05.12/data.f2fs.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
Any help/advice would be greatly appreciated
Nobody has a clue? :/
I got the same error time ago on my 6X, i solved it thanks to an old backup made before debloating some system files and no one could gave me some help about, so at the end, this is the only idea that I've got; I've surely deleted some system path while debloating, and TWRP wasn't able to restore that path anymore. Give a look to this https://github.com/BuildingAtom/CleanTwrpTar/blob/master/README.md it's a software which i was almost trying, if i wouldn't solved before do that. Hope it could be helpful!
I'll try tommorow, thanks a lot for your time
No problem, as you can see even in my thread https://forum.xda-developers.com/honor-6x/help/twrp-extracttarfork-process-error-255-t3692826 I've got no useful answers, and it's like this in EVERY extracttarfork() error 255 thread here on XDA. Even other phones obviously got this error, and there was only some vague ideas about the reason of this issue... Maybe writing directly to TWRP team could provide a valid answer to this
Yes I saw this huge lack of answers about this issue, you're right that could be a great idea
I have same issue and can't found a solution the restore backup is not trust-able, beware!
mrhamed said:
I have same issue and can't found a solution the restore backup is not trust-able, beware!
Click to expand...
Click to collapse
me too facing same issue
It seem the compression procedure is problem, so I never use compression.
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.