I’m getting “CreateTarFork() process ended with ERROR: 255 Backup Failed” on my BTV-W09 using the greatslon TWRP US version while doing a backup. I’ve tried internal storage and external SD card. Haven’t tried an external USB drive yet though. Flashing SuperSU worked fine with this TWRP, I did get the error about the 3rd modem but this may be because this is a Wi-Fi only device? I’m going to try it again and then try pulling the recovery.log to see if this gives some indication of the failure. Is anyone else receiving this error?
I received this error last night in my data section as I was creating a nandroid backup in my preparation to install the xposed framework. I was backing up to the external SD card and what fixed it for me was to delete the existing TWRP directory and make sure compression was not checked. After that the backup completed successfully. I did receive the 3rd modem error, but like you, I believe that is due to not having a cellular modem (WiFi only). I also received an "unable to unmount system" error at the very end, but I don't think that is any cause for concern.
Thanks for the feedback johe. I checked the recovery logs and the backup was failing on different files each time on the data partition. So I added a larger SD Card and the backups work now. So turns out it was just a space issue. The backups take a lot more space than what I thought originally, presumably for caching.
Related
I'm running deodexed build from this post: http://forum.xda-developers.com/showpost.php?p=40232503&postcount=43 and CWM bootloader. I'm using link2sd and 16GB external CD card.
Strange things started to happen (I think) after using my phone in the swimming pool. Apps from my external card vanished and I couldn't fix this issue, so finally formatted SD card (minitool didn't work, partition toolkit did). Meanwhile every now and then "no place on disk" error while installing apps popped up. Approx. 400 MB of internal storage was free...
After format things started to look promising, but "no place on disk" error still bugged me, so I thougth about workaround, and tried adb shell pm set-install-location 2. After restart I got bootloop. Tried several options and finally was able to flash firmware with odin 1.85. While I was at it, I flashed bootloader with CWM mod and odin 3.09. (Before flashing I was getting an error after restart and had to reboot manually:
E: failed to verify whole-file signature
E: signature verification failed
Click to expand...
Click to collapse
). Well, that worked, and no data was lost, but my external card is unusable, link2sd warns me about my second partition not being automounted and every time I restart phone I'm in the bootloop again, having to flash firmware to be able to unbrick it.
I tried to fix second partition from within partition toolkit, but no luck, formated it, again, but now link2sd doesn't see it mounted at all (partition toolkit does). I've reverted install location already, set it to 0, and later to 1, but no luck... I mean it works, but doesn't solve the problems.
I'm running out of ideas. I backed up everything with titanium backup and I'm considering factory reset, but not sure if it will help at all...
UPDATE:
I bought 32 GB SD card and replaced the old one. Formatted it and things seemed to work, but in roughly 50% of cases I couldn't install application due to "usufficient space on disk" error.
And another issue: yesterday my phone hung, so I restarted it. Basically it entered bootloop, but starts normally as soon as SD card is removed. Recovery log says "can't partition non mmcblk device" regarding SD card.
It looks as if SD card was mountable only when fresh formatted, any application moved to it (link2sd) and things end up as described.
Tried to boot without SD card and insert it later when system starts, but no luck (card is not discovered at all).
I'm seriously considering selling this phone - without external space for installing apps it's next to unusable, and it seems I am not able to solve the issues with SD card.
I flashed my i9500 with TWRP 2.8.1.0 using Odin and it wrote an undeletable backup onto my internal memory. To get rid of that, I backed up the "BACKUPS" folder and formatted the internal storage only for it now to cause the entire internal storage to be write protected to my android apps. I can copy and delete stuff to it through PC but my apps wont work, those that require to download pics and videos or make backups to the internal storage, web browsers can't download anything to the internal storage yet I now have over 7GB free space.
It's clear TWRP is write protecting the internal storage selectively (first it wrote protected the storage to both the phone and pc, now to the phone only). How should I sort this problem out?
I have also just tried using root explorer to change permissions to the internal storage but it doesn't work. It's failing. Titanium backup shows its own backup folder is unwrittable. It cannot be changed by Root explorer
I just tried fixing permissions in twrp but to no avail. I uninstalled Clean master only to try and re-install it and it won't install now, it gives a failed install error. Kingsoft office continually shows "stopped working" and fails to work completely. All this started with flashing Twrp. I can't view pics in whats app or send them, neither can I edit documents. Any help to rid of this issue will be gladly appreciated.
People please please avoid twrp at all costs!, i have now lost all my data and apps are all failing. I deerly deerly regret why i ever flashed twrp recover in the first place!
I seem to have solved the issue after a very grueling experience.
TWRP has its flaws and it is quite notable here. Here is how I have gotten around the issue:-
Immediately after I installed TWRP I made a system backup of the entire phone as of its state at the time.
I copied it to my pc and tried to delete the backup that TWRP had made. It was completely write protected, nothing could delete it.
I then decided to use TWRP to format my internal storage after backing it up. Then restore the data back which I did successfully.
Little did I know what had happened. TWRP had assigned the internal storage attributes that even Root explorer (paid) could not undo.
The internal storage had become unusable to the system and user apps.
Slowly my apps began to collapse one after the other failing. From frustration I tried to salvage the data the apps held at the time so that I can factory reset and restore but Titanium backup could not access its own folder. That's where all the frustration begun.
I later flashed CWM and accidentally formatted all my data instead of the data partition.. this was now hell.
One last try which was about 5 hours later I returned TWRP recovery, wiped the data partition and got hold of my prior backup with TWRP, restored it and am 9 hrs back from total loss of data. So the internal storage now has its initial attributes prior to the predicament.
Am actually back exactly to where all this mayhem began when I decided to delete the "BACKUPS" folder and there was absolutely nothing else that was wrong, which now I will attempt to delete hoping that I won't experience deja vu.
This is a problem worth reporting to TWRP developers and I don't know how
TWRP recovery Fix Permissions
I couldn't delete back ups from the internal storage at all. I couldn't even copy saved back ups from my pc to my Note 3. I went into TWRP recovery, under Advanced select Fix Permissions
Now I can delete folders in the TWRP main folder with a ES file explorer or on my PC via usb cable.
Never had any problems like this with TWRP on my S4+. For me the backups taken and its folders can be handled just fine, copied, deleted, moved etc. Must be som compatibility issue with your setup.
So, things have massively escalated today and my phone appears to be soft bricked. Joy. I'll run through what happened.
1. I encrypted my phone using the built in tool in Cyanogen Mod. After it rebooted, it was glitchy and I lost a load of apps, the phone really wasn't working well. Rebooted again, but no improvement.
2. I went into TWRP (2.8.x) to restore my old backup, which was on the SD card. After the initial wipe of the internal storage, the log showed
E: Can't mount storage
Click to expand...
Click to collapse
and the restore failed.
3. I reboot and phone goes straight into recovery mode as there is no OS installed (the recovery wipes the internal storage first). Internal Storage is now showing as '0 MB'. I cannot find a way of mounting this storage anymore. Have tried factory reset (doesn't work because file system isn't mounted), and rebooting a few times but no avail.
* There seem to be some options about flashing a .pit file using odin, but I do not have this file. My phone is the Note 4 SM-N910F Model. If I can do this through Odin then maybe this will resurrect the file structure and make this storage mountable?
* There may also be another option using ADB but I still don't know what commands to use.
Any help would really be appreciated as it seems there is some possibility of a fix. That being said my hopes are not that high...
I believe I may have fixed this. I would like to keep this up here in case in helps anyone in the future, I would imagine this is only useful for people who have encrypted their device. I'm not an Android expert so can't be responsible for any damage to devices or data loss etc.
It seems that the encryption must have gone wrong somewhat and this is likely to have impacted on the file system.
Although I couldn't wipe on the device, I was able in recovery to FORMAT data (not just wipe). Go to the wipe menu, then format. After this, reboot into recovery again and you should be able to mount again. It rebuilt the filesystem too.
This should be a quick fix that may help a few people with the issues with not being able to mount the file system. I hope this can help at least one person!
I managed to restore from my backup after and phone is now working. Thanks anyway!
Is there any way to set the default storage of play store apps to the sd card?
I have an unlocked bootloader, but I'm not rooted. I upgraded to MM via OTA and set my SD Card to be used as internal memory. I've had some problems since:
1) The first real issue is that Evernote is giving me a database read/write error and not working. It seems that to resolve that, I'll probably need to root. So, I went to do a MM nandroid before rooting
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
3) When i go into the Mount screen and select storage, it is showing Internal as just 2+GB free (which is correct), but 0MB for my Micro SDCard. So, it can't mount it.
4) Looking around, the fixes for this seem to be a bit severe in terms of formatting the SD Card again, etc. (ex. http://forum.xda-developers.com/showthread.php?t=2354029)
So, my questions are:
1) If anyone knows of a solution to that Evernote issue, that would be great
2) More importantly, what my options are for fixing the Backup problems
3) Specifically, with my SDCard now supposedly acting as internal memory, if i format the card per the common fixes, will that cause other unexpected problems with apps and other functions that are now using my SD Card as usable storage?
How did you set SD card as internal storage. Me: stock, no root, MM
Sent from my XT1575 using Tapatalk
I'm giving up on combined storage until twrp is fixed.
You just go into settings, storage, then click on the SD card. I'm back to lollipop at the moment, so I cant say exactly what to do next, but I think from there it should be clear. It may be an option up in the overflow menu at the top right. It will make you reformat your card as part of the process .
Thanx Chuck! Need to b.u. before formatting as internal...
I had the same issue with the SD card set as internal, couldn't make a twrp backup, so I had to reformat as storage and it works. Only bad part is now I can't move apps to SD
Is there a twrp fix in the works??
chuck-fu said:
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
Click to expand...
Click to collapse
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.
ScaryBugThing said:
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.
Click to expand...
Click to collapse
It's a known issue that the version displayed stays on 2.8.7.0 after updating.
Sent from my Moto XPE
Hello everyone,
I encounter a problem when trying to restore backup in TWRP. All md5 checksums are successfully verified, backup restores "Boot" and "System" partitions, then proceeds to "Restoring Data". After about 85% the process stops, and "Restore Complete Failed" message appears. The phone reboots OK but all data is missing. Essentially, that's like a fresh install: the basic setup has to performed. All apps are there but all settings are gone.
I see that people have similar problems but unfortunately I could not find a solution how to restore data partition. Is there a way to successfully restore data? What is causing the problem?
Here is just a bit more info about the device:
1. Rooted LG G2 D801 (lollipop, Android version 5.0.2)
2. Custom recovery TWRP 2.8.6.1 installed with AutoRec.
3. After rooting and installing the device was fully functional.
4. The initial backup was done in TWRP. The process completed successfully with no warning or errors.
Hope someone could help. Thanks.
Try to update TWRP to 3.0.2-1 and check will it help. Also... do you have enough of free space on your device? TWRP zip backups so it need to have a place to unzip it.
Try to update TWRP to 3.0.2-1 and check will it help.
Click to expand...
Click to collapse
Where do you get TWRP 3.0.2-1 for LG G2? The TWRP website says that LG G2 is no longer updated and the latest version for D801 is 2.8.6.0.
Also... do you have enough of free space on your device? TWRP zip backups so it need to have a place to unzip it.
Click to expand...
Click to collapse
That might be the issue.
I was trying many different ways to restore the data partition. The only way I was able to successfully do it if I wiped or formatted the internal storage (/data/media) in addition to TWRP defaults (data and cache; TWRP excludes /data/media). Somehow, the internal storage interferes with the restore process. I had to backup the internal storage separately to my computer before all the wipes.
The cause might be insufficient disk space (there is less than 1GB available). However, TWRP backups are uncompressed and kept on external storage via USB-OTG. The backups for data, cache and system seem to be regular TAR archives:
Code:
$ file data.ext4.win000 cache.ext4.win system.ext4.win000
data.ext4.win000: POSIX tar archive (GNU)
cache.ext4.win: POSIX tar archive (GNU)
system.ext4.win000: POSIX tar archive (GNU)
One would think the data is directly extracted from TAR archives to the data partition. Even with compressed TAR archives, decompression can be be done "on the fly" (eg. tar xzvf) without decompressing to disk first.
Not sure what exactly happens. The restore sort of works now (I do have to backup internal storage prior to this, which is a big inconvenience). I should have examined recovery.log after failed restore.
sakej said:
Also... do you have enough of free space on your device? TWRP zip backups so it need to have a place to unzip it.
Click to expand...
Click to collapse
Just did few more experiments and insufficient disk space is certainly the issue. This time I did nothing to the internal storage (/data/media). I have two backups: a larger one (includes an initial state of the device) and a smaller one (in which a lot of pre-installed LG G2 stuff was purged from the device). The larger backup consistently fails, the smaller one works like a charm. Of course, it would be great to know in advance whether the backup is going to fail during restore
Thanks for the help!
I've had bad backups in the past, despite completing successfuly.
ursus107 said:
Where do you get TWRP 3.0.2-1 for LG G2?
Click to expand...
Click to collapse
You will find it here on XDA
https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
But if you using it, KEEP IN MIND THAT: https://forum.xda-developers.com/showpost.php?p=70091412&postcount=9
ursus107 said:
One would think the data is directly extracted from TAR archives to the data partition. Even with compressed TAR archives, decompression can be be done "on the fly" (eg. tar xzvf) without decompressing to disk first.
Click to expand...
Click to collapse
It's more the case of how recovery works I think, it cannot directly override files from backup in case if anything went wrong, so rollback is possible.
Turbine1991 said:
I've had bad backups in the past, despite completing successfuly.
Click to expand...
Click to collapse
Restoring from the larger backup only fails if I do not wipe '/data' entirely (including '/data/media'). Otherwise, everything completes successfully. So it has something to do with the available disk space.