I'm currently using TWRP on my XT1063. I'm having weird problems regarding TWRP's access to the data partition. When I try to do a nandroid backup of the data partition, it gets 10-30% of the way through the backup then crashes and reboots to system.
I've successfully backed up the system partition to my external SD card, so it doesn't seem to be an SD card problem. I did TWRP fix permissions and it appears to have completed successfully. I'm not sure what is causing this nor how to solve it...
I think my next step will be to reinstall TWRP and try again. Failing that, I guess I'll switch to clockwork mod recovery, which I haven't used in a long time. Do you have any suggestions on things I could try before reinstalling recovery?
So I've searched quite a bit on this one and can't really seem to figure out what is going on.
I started on TWRP 2.7.1.0 and when backing up with adequate storage space I kept getting "backup failed". I tried 2.8.0.0, same thing, and finally 2.8.4.0 failed as well. I cleared a bunch of stuff off of it and was able to backup once. Two days later when I was going to try out a new rom, I decided to make a new backup and right back to where I am now - fails every time. I have 10gb free and the backup is less than 5gb. I was getting impatient wanting to update my rom, and figured since I already had one backup I may as well try to install a new rom - I tried to wipe data/cache/dalvik, and even that failed.
I attached two logs I saved from different backups. I've tried fix_permissions and nothing. I'm assuming this may be a error with the internal storage, perhaps my next step would be to format that partition (Is this just "format data" in TWRP wipe section?)
Thanks for the help!
My TWRP nandroid backups started to fail out of nowhere with the following error message:
Code:
E:createTarFork() process ended with ERROR=255
And this appeared when doing any type of operation:
Code:
Updating partition details...
E:Unable to stat '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1'
After looking at the log, this is the full info when the error happens:
Code:
I:addFile '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1' including root: 1
E:Error adding file '/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1' to '/sdcard1/TWRP/BACKUPS/ZX1C622JHV/2015-07-22--01-07-04_cm_thea-userdebug_5.1.1_LMY48B_ef0c42eec8_t//data.f2fs.win000'
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/sdcard1/TWRP/BACKUPS/ZX1C622JHV/2015-07-22--01-07-04_cm_thea-userdebug_5.1.1_LMY48B_ef0c42eec8_t/data.info'
E:createTarFork() process ended with ERROR=255
This happened all of a sudden. I did not change anything at all, except for flashing a new CM version in between this and the last successful backup, 2 weeks ago.
Yesterday, I have then flashed the new 2.8.6(7). from a few posts above and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Just thought I'd give you a heads up in case anything like that happens to someone else, not sure what the best approach is here, probably do some regular backups of your internal storage, but that's kind of tedious...
Did you try removing corrupted file? (/data/data/com.google.android.apps.photos/cache/glide_cache/28e788985b1e0d4261cc99a18072315bef62d103bf4091ec4800778fd4212fd1)
Couldn't start up the phone anymore. And don't know how to do it via adb. I only saw that error when I went into recovery after the phone froze and wouldn't boot up anymore.
Hmm, I could have probably used the TWRP filemanager, right?
It was very weird though, at one point even TWRP was not working reliably anymore, after 3-4 reboots it didn't even start up...
using condor.. moto e twrp 2.8.6.0 and same problem for me
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Pranz... said:
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Click to expand...
Click to collapse
using motox xt1092 with twrp3.0.0.0 same problem
Pranz... said:
using bacon.... Oneplus one twrp 3.0.0.0 and same problem for me
Click to expand...
Click to collapse
Same Same : oneplus2 TWRP 3000
ericcostes said:
using motox xt1092 with twrp3.0.0.0 same problem
Click to expand...
Click to collapse
Hi try use TWRP (2.8.7.1) Link
Nexus 7 2012, CM 12, TWRP 3.0.0.0 - same problem
Oppo R7 Plus with the same problem, I´ve tried TWRP 3.0.0. and 2.8.7.
Someone solve this problem?
Note 4 / twrp 3.0.2.0 same problem
Might be a bit late for some, but I just ran into part of this problem myself ...
I did not have the trouble with recoveries, but I was getting the error 255 on backup operations. I am only trying to backup /data.
I was trying to backup to a 128GB USB OTG device, formatted to exFAT, on a OnePlus One.
The backup completed on the stick using the official TWRP, but before I wiped my data I wanted a second backup from a different recovery to ensure I was well covered. I installed TugaPower TWRP and that's when problems started.
Tried a few things, reverted back to 2.8.6 TWRP and wasn't getting anywhere.
Then I took out the stick and using a OTG adaptor I am now running a /data backup to a 32GB micro SD card, also exFAT. It hasn't completed yet, but the older ones would always stop quickly. 15% now ...
Short story ... check the media you are backing up to, there might be an incompatibility there rather than an issue with your device or the recovery.
I will try and do a backup with the TugaPower TWRP on the 32GB card after, too. If that works, then I know that some recoveries have OTG issues.
How to fix error 255 .
I cannt great back up and back up ended with error 255 plz help
Sent from my Le X820 using Tapatalk
Hello guys , i have a problem with backup restoration on my z1. I made a few days ago a full backup on my ext sd card (everything went well) and now when i try to restore it the recovery only restores a part of that backup . The backup is 3.8gb but it only restores about 3 gb and at the end i get this error "volume not found skipping restore of sd-ext error" , the phone boots up but the launcher and a lot off apps are missing . I tried to copy the backup folder by phone and pc to the internal sd card of the phone but i can't because i get an error. how i can restore the backup and what can be the problem? My bl is locked and i used xzDual recovery 2.8.21 and 2.8.23 but i get the same error when restoring. I don't have another sd card to test this. Any help is good.
Error: volume not found skipping restore of sd-ext error
Have you tried mounting the drive that gives the error manually before starting restoring?
motorazrv3 said:
Have you tried mounting the drive that gives the error manually before starting restoring?
Click to expand...
Click to collapse
Yes but same thing. i can flash and backup anything from/to sd card but the restore is not working. Don't know why since i used the recovery many times before and everything was ok
I made backup of "/data" partiton of MIUI 11 xiaomi.eu rom.
and I tried to restore the backup after doing something, I got the error "extractTarFork() process ended with ERROR: 255"
I've tried more than dozens of times to restore the backup file from more than 3 kinds of recovery but the result was same.
I've got only 2 times of successful results of restore, but I don't know why the restore was success.
I've googled as much as I can to find the solution of this problem but I was not able to find any solution that works for me.
(I've tried formatting '/data' partition, mount-unmount, install the same version rom....)
Please let me know the solution.
hey did you solve it? i didn't know TWRP won't allow me restore my backup... (
Hi, i'm having the exact same issue. Maybe an issue with TWRP? I've heard it can also be an error that shows up when there is not enough available storage, but I had at least 32gb free.
same problem when trying to create a backup. Still worked a few days ago....
update: restored an old backup and now i am able to perform backups again. Still not sure what coused it though