Hey guys I recently made a pair of backups, (A) being very early and close to my liking and (B) recently made Tuesday & has all my settings,etc.
Well a tried Textra and decided I didn't like it but made backup B before I installed it (this was J.I.C. due to another previous text app breaking my read receipts upon removal on Tmob...thank God). Well Textra broke read receipts and I went to simply restore the B backup from the SD card and got the
Error 255 as soon as I swiped restore.
When I made backup B, I added _Feb to the end of the file name (preserving the date generated name) inside of TWRP to easily spot it, could this have ruined this back up?
Backup A restores just fine and sits on the SD Card with Backup B
Tried:
Removing _Feb, deleting a few internal pics
Internal space is at 42GB free
SD Card is at 210GB free
TWRP is 3.0.2-1
Backup A = 9.11GB
Backup B = 10.08GB
Related
Just go S5 yesterday. I have an S3 that fell down and ended up with a crashed screen. Lucky me I have done Titanium Backup yesterday morning. Now I moved the extSD Card to my new phone, rooted my S5, installed Titanium Backup and pointed it to the folder existing on my extSD card, which has the backup files I have done on my S3. Also I had a copy of my Internal Storage of the S3 on my extSD Card, so I pasted this to my Internal Storage of my new S5. I restored half of the apps but then all of them get error at opening 'Unfortunately, xxx has stopped'
I am now on my Play Store uninstalling each one of them then installing it again. So far the ones I have installed have worked. But ofcourse without my settings. So I am starting from scratch.
What is the reason for the above error ? Is there any fix for it ?
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.
Hi guys....
Is there a way to undo an overwrite on a file? I've overwritten a file on my sdcard in my S5 but realized I shouldn't have.....
It all started when my game data (Google Play game data) wasn't showing up properly....I selected the save location to be the device but when I started playing this afternoon all data was gone. Now in my game I was on level 10 with 2 cars and a nice amount of cash but after this afternoon I was still on level 10 but my cars were gone and my cash....AND I had to start over (but my level was still 10). How is that possible?
Ok fortunately this morning I had made a Titanium Backup of the game and data so I should be able to restore that to this morning's status.....wrong! THAT's the backup I've overwritten with a new Titanium backup. I actually made a backup of the first Titanium backup on my SD card but with the whole confusion I copied over the new backup to my SD card, overwriting this morning's good backup......
Anyone know how to recover my good backup files??
Hello
I made a full backup with philz and transferred it to my pc. Tried to delete the backup folder from my internal sd card but can't. Get this message:
Cannot delete backup: the storage is write-protected. Remove the write-protection and try again.
BTW, I'm on stock kk 4.4.2
Thanks for your help
By default, CWM and Philz protect the nandroid data from being deleted since they utilize an incremental backup scheme rather than the older image file setup. For example, let's say you have three nandroid backups: A, B, and C. If the nandroid data wasn't write protected and you delete backup A, you would screw up ALL your nandroid backups. A is the master backup. When the recovery makes backup B, it only backs up the changes made between A and B. If you then made backup C, it would back up the changes between A AND B, and C. Since the possibility of screwing up all your backups by deleting the oldest is a major problem, CWM and Philz write protect the storage.
Go into Philz, then enter the backups menu. Delete the existing backups using its delete function, then select "free unused storage data" to recover the space. After doing that, switch to TWRP 2.8.6.0, as it doesn't make incremental backups and thus doesn't write protect the storage space. Also, unlike CWM and Philz, you can place the backups on your MicroSD card..
Done....thanks very much Strephon
hi, i have the same problem and it work, thanks!
Using GS4 I9505, and my internal storage is getting shorter shorter, day by day. almost like its vanished. i've check emulated 0 and legacy drives nothing there. but as i gethered it coz of CWM, now using twrp, uninstalled CWM but still storage isn't available for usage.
Your space is still lost because it's still allocated to CWM for nandroid backups, even though you no longer have CWM on the device. Therefore, you need to put CWM back on the device, go into its backups and storage menu, delete any existing backups it made, then free the allocated space.
When you put TWRP back on to the S4, your space should return.
He can delete the CMW folder from the storage. The backups are there and they are not hidden.
I provided an in-depth explanation of this in an earlier thread on the same topic, but in essence CWM protects the nandroid backups space so nothing else can write to that area. This is because CWM performs incremental backups by default, and deleting older restore points messes up all of them. The protection persists even after CWM is removed, so when switching recoveries, all backups need to be deleted in CWM, and all allocated space freed using the "free allocated space" option in the backup and restore menu.
EDIT: To point out the obvious, there would be no need for a "free allocated space" option in CWM if the space weren't protected.
Well, that's stupid. With TWRP I can simply go inside the folder and delete the backups (without the need of booting into recovery and deleting them from there).
Calling it stupid is a bit harsh, and besides, Koush probably will disagree with you.
By default CWM is set to do incremental backups and does this as a space-saving feature. For example purposes let's say a nandroid backup is 2GB. Using the standard .TAR method four nandroid backups would take up 8GB. Switch to .DUP and those same four backups may only take 3GB. This is because .DUP only backs up the files that have changed between the current system and the previous backups, rather than backing up the entire partition. Since CWM in .DUP doesn't back up the entire partition when making its backups, it's vitally important that the backups be protected. Otherwise, deleting an older backup makes it impossible to restore any later backups.
The example I used in my other discussion to illustrate this was four backups, labeled A through D. A is the master backup and B through D are the incremental backups. If the space wasn't protected, deleting backup C in a file manager would render backup D invalid because of missing files. Naturally, deleting backup A would render all subsequent backups invalid, as it is the master backup.
In CWM it is possible to switch from .DUP to .TAR and thus stop CWM from allocating space for backups. The OP didn't do that, which is why his space disappeared even after switching to TWRP. There may be a manual method of removing the allocation through a terminal, but it's simply easier to restore CWM, delete the backups, free the space, then switch back to TWRP.