-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.
Related
I get to the part where it would restore the .android_secure part and it gives me this error this is with 3.0.2.4 and I can properly wipe and such...
"error while making a yaffs2 image of /sdcard/.android_secure"
and this prevents it from making a md5 sum so I basically hve no backups at all, is anyone else having issues with this? I'm going to try and toubleshoot back to 3.0.2.2 and see if i can get that to back up but if anyone can help it would be appreciated
I can make nandroid backups no problem. Do you use Clockwork recovery?
ERIFNOMI said:
I can make nandroid backups no problem. Do you use Clockwork recovery?
Click to expand...
Click to collapse
uh... your intelligence exceeds you
as for OP, I would try, if you haven't, in rom manager, hitting menu, delete cache, then menu again, settings, delete recovery, then reflash 2.4 and see if you can backup then.
nosympathy said:
uh... your intelligence exceeds you
as for OP, I would try, if you haven't, in rom manager, hitting menu, delete cache, then menu again, settings, delete recovery, then reflash 2.4 and see if you can backup then.
Click to expand...
Click to collapse
I have uninstalled 2.4 installed 2.2... same thing.. all while delete recovery every flash... still nothing... not being able to nandroid means having to start from scratch if I get a loop... I dont know when this started to happen but my past weeks nandorids are all screwed up... and I deleted the 1 nandroid I had that worked cause I thought the newer one was good
ok to anyone having this issue it seems to be a problem with my sd card... I plugged my sd card into my computer via a card reader and the "there may be errors on this storage device" came up... I did a nandroid with my 2g sd card just fine so it not an error with CWM atleast...
scanning for errors on my computer brought up a bunch of errors within .android_secure and corrected them and now I can backup... it said the errors are from removing the sdcard while its being written... how can we do that when its under the battery? and I only did a battery pull when I got a ten minute hang on bamf 1.2...
hope this will help someone if they get the same error
Thanks for posting this! This helped, thank you!
Hi, im having some issues with CWM. When i attempt to make a nandroid backup in recovery it says error making boot image of /data. Previously after restoring a backup the rom was running ok but some of the apks were not restored correctly, i believe the ones that had been moved to sd before making backup. I used nullifier to wipe phone before flashing that backup. You can probably tell i dont know what im talking about.
I have done the following things to try to solve problem:
Formatted sd using computer
Transferred saved cwm files to sd
Redownloaded oneclickrecovery to make sure files intact
Reinstalled cwm to phone
Booted into recovery to make backup
Error persists. I have not attempted to flash any of my previous backups because i dont understand the problem well enough and dont want to make it worse.
I would be grateful for suggestions on where the problem likely lies
colorized by kitten spit
irukandjiandme said:
Hi, im having some issues with CWM. When i attempt to make a nandroid backup in recovery it says error making boot image of /data. Previously after restoring a backup the rom was running ok but some of the apks were not restored correctly, i believe the ones that had been moved to sd before making backup. I used nullifier to wipe phone before flashing that backup. You can probably tell i dont know what im talking about.
I have done the following things to try to solve problem:
Formatted sd using computer
Transferred saved cwm files to sd
Redownloaded oneclickrecovery to make sure files intact
Reinstalled cwm to phone
Booted into recovery to make backup
Error persists. I have not attempted to flash any of my previous backups because i dont understand the problem well enough and dont want to make it worse.
I would be grateful for suggestions on where the problem likely lies
colorized by kitten spit
Click to expand...
Click to collapse
So your problem is you came make a backup? If so make sure you have enough free space first in you sdcard for more than 1 backup then try again...already 1GB I'd say, maybe a little less.
Sent from my Porn Infested G2x using Tapatalk 2
Yes, cant make backup. The sd card has 30 free gigs.
colorized by kitten spit
Just a last ditch, wondering if anyone has gotten this error in any cwm versions before and if they figured out the problem?
colorized by kitten spit
Try the new touch cwm
Sent from my LG-P999 using xda premium
For benefit of anyone experiencing similar problem, was solved by performing factory reset and formatting emmc. Did both at once so do not know if either was solution indepently or if both necessary.
Obvious from this question i dont know how partitions work and will research myself but since it is a related topic, would anyone care to comment on if after using computer to format sd its necessary to use cwm to format internal?
Sent from the heart
irukandjiandme said:
For benefit of anyone experiencing similar problem, was solved by performing factory reset and formatting emmc. Did both at once so do not know if either was solution indepently or if both necessary.
Obvious from this question i dont know how partitions work and will research myself but since it is a related topic, would anyone care to comment on if after using computer to format sd its necessary to use cwm to format internal?
Sent from the heart
Click to expand...
Click to collapse
As long as you chose FAT32 on your computer you're good with your actual SD. Formatting emmc is up to you, you can format it from settings or if you want more formatting options, do it in CWM.
[email protected]
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Have a look at and/or post your log from twrp. You can find this under advanced options then copy log or use the command adb pull /tmp/recovery.log.
Also, I know in the past titanium backup hasn't been great at extracting nandroids. Try https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore and see if it makes a difference.
runner1717 said:
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Click to expand...
Click to collapse
Have you actually tried using the backup to restore? You sure the app you are using to check isn't the issue?
runner1717 said:
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Click to expand...
Click to collapse
Switch to Philz it will handle twrp bu's too. You can watch the md5 check going on before you command the restore to take place. At least on 624.
Thanks for the help and suggestions. Here's what I found:
Tried TWRP 2.6.3.1, 2.6.3.0 and 2.7, all with the same result. Corrupt files. I verified this using Android File Verifier (great utility, used for years). When running Calc MD5 checksums on the individual backup files, some would verify and others would not.
Running multiple backups with each version resulted in failed backups. On a weird note, I could not remove the TWRP directory using either Root Explorer or ES file explorer. Both would cause the phone to reboot. The only way I could remove the directory was using file manager in TWRP.
Switched to Philz recovery and ALL backups verified just fine! Although it doesn't have the fancy interface or some of the features of TWRP, it gets the job done!
My conclusion is that there's some sort of issue with TWRP writing to the internal SD as proven with the incomplete backups and the directory problem it caused on the SD. I would recommend others use the Android File Verifier to make sure they are getting complete backups!
Mike
I just installed twrp and completed my first nand, the adv program said everything was fine. So I should be safe finally
Hi, 2 days ago with the help of App Inspector and MiXplorer i was debloating my phone from all those useless apps like Huawei ID, HiCare, Swiftkey, ecc. and while I was doing it i took the chance to remove some other service packages that I'm sure I'd never used in future, like Geofence, Mapcon, Fido client, ecc. Everything worked nice in the phone, overall because obviously i paid an extreme caution while removing packages since that we're talking about system files, and i fact i didn't noticed incompatibilities or other issues while using the phone in these 48h.
The only problem that i encountered is that now my TWRP isn't able to restore a nandroid backup without getting a failure accompanied by the error mentioned in thread title.
Code:
[COLOR="red"]extractTarFork() process ended with ERROR: 255[/COLOR]
When i reboot to system however, everything is fine except the theme that i have to set again, the list of previous SMS empty (but i have contacts, system settings, apps, notes, everything else) and a leftover of Swiftkey app that i have to remove again. I tried with 2 different backups: one made before debloating the phone 2 days ago, and the second is a backup took today on the phone already debloated. Anyway making some searches around i found this topic https://github.com/TeamWin/Team-Win-Recovery-Project/issues/964 in which i read that a possible cause could be the amount of free space on the phone, but i have more than 17GB free and I'm restoring the backup from external SD, so i can exclude for sure this cause... Another solution standing by what i read elsewhere could be to unmount the "data" partition on the phone before restoring the backup, but neither that changed a single thing and i keep getting the same error. I think that what could provoke this issue is related to some files linked to missing apks, like data of an app removed but it's the only clue i have about now.
I hope that someone can really help me out on this because TWRP backups for me are essential. Looking forward for your answers guys! Any help will be extremely appreciated!!
EDIT: i can provide logs obviously if someone could be able to detect the error by reading them, i can't so let me know if someone would like to dedicate some minute on reading a log
Other things noticed: i had to reflash again Magisk Modules and even Magisk V14.3 zip to being able to flash modules stored on my SD, even if Magisk was still installed. This is surely due the fact that the restore of data partition started and then it got stopped by fault of error 255, so data partition wasn't fully restored. The thing that i just can't understand is why even the older backup isn't working, maybe I'll have to format data dalvik and cache to get the older backup working..? Damn
Bump. C'mon guys, really no one??
RedSkull23 said:
Bump. C'mon guys, really no one??
Click to expand...
Click to collapse
Haven't seen yet bro
shashank1320 said:
Haven't seen yet bro
Click to expand...
Click to collapse
Dammit that's bad, i known from beginning that it's a complex issue but i thought that someone here could help...
RedSkull23 said:
Other things noticed: i had to reflash again Magisk Modules and even Magisk V14.3 zip to being able to flash modules stored on my SD, even if Magisk was still installed. This is surely due the fact that the restore of data partition started and then it got stopped by fault of error 255, so data partition wasn't fully restored. The thing that i just can't understand is why even the older backup isn't working, maybe I'll have to format data dalvik and cache to get the older backup working..? Damn
Click to expand...
Click to collapse
May be you need to format data, dalvik and cache and then reboot to recovery again from recovery.
I am facing such issue these days and had to opt for this to mount data again. Never understood this concept with huawei phones. my old Yu Yureka was hell easier to flash all these.
shashank1320 said:
May be you need to format data, dalvik and cache and then reboot to recovery again from recovery.
I am facing such issue these days and had to opt for this to mount data again. Never understood this concept with huawei phones. my old Yu Yureka was hell easier to flash all these.
Click to expand...
Click to collapse
The only thing that stops me from trying to solve this by wiping data, dalvik and cache is that if after wiping the issue will persist, other than not being able to restore my backup I'd find myself with a phone where i have to restart from scratch too. And so it could be even worse... I really don't know what to do at the moment, but i must fix this.
RedSkull23 said:
The only thing that stops me from trying to solve this by wiping data, dalvik and cache is that if after wiping the issue will persist, other than not being able to restore my backup I'd find myself with a phone where i have to restart from scratch too. And so it could be even worse... I really don't know what to do at the moment, but i must fix this.
Click to expand...
Click to collapse
May be a twrp backup... once all restored then restore data
So, some day ago i managed to solve my problem trying once again to restoring a copy of a TWRP backup, this time an older one dated 2 weeks ago other than 1 like the previous backup... (for safety reasons i always keep 2 backups, and i overwrite these weekly one after another, by the most recent) and this time it worked. I seriously can't understand why this error happened only on the 1st and more recent backup, since that i started to debloat some system apks and packages only 1 week after the latest backup, and so without system modifications the error shouldn't have to be already present on the backup took exactly 1 week before starting to remove files... but i'm out of this now
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