Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,732,914 Members 49,476 Now Online
XDA Developers Android and Mobile Development Forum

Titanium Backup cannot backup to micro sd

Tip us?
 
fincan
Old
#1  
fincan's Avatar
Senior Member - OP
Thanks Meter 76
Posts: 273
Join Date: Dec 2007
Location: around VA
Default Titanium Backup cannot backup to micro sd

Hi all,

For the past month or so, Titanium Backup cannot backup anything to my external sd any more and reports "Insufficient storage space". When I look at the folder location under TiBu preferences, it says "folder is not writable", however when I check the permissions with Root Explorer, it says it is writable, and everything else can really write to it anyway (e.g. google music can write there just fine).

If I switch the backup location to internal storage, it works fine but that defeats the purpose, I want to use my external microsd.

I've already tried uninstalling/re-installing, updating my SuperSU, rebooting the phone etc.

Any ideas?
- Galaxy S4 Google Edition
- Nexus 7 FHD (2013)
The Following 2 Users Say Thank You to fincan For This Useful Post: [ Click to Expand ]
 
AnaMajhol
Old
#2  
AnaMajhol's Avatar
Senior Member
Thanks Meter 52
Posts: 205
Join Date: May 2012
Location: YOUR BACKYARD
Hi. . Your can try "Helium" as even the free version supports backup and restore from sd card.. here's the link:
https://play.google.com/store/apps/d...ikdutta.backup
Good luck

Sent from my GT-I9505 using Tapatalk
 
dratsablive
Old
#3  
Senior Member
Thanks Meter 37
Posts: 358
Join Date: Feb 2011
Quote:
Originally Posted by fincan View Post
Hi all,

For the past month or so, Titanium Backup cannot backup anything to my external sd any more and reports "Insufficient storage space". When I look at the folder location under TiBu preferences, it says "folder is not writable", however when I check the permissions with Root Explorer, it says it is writable, and everything else can really write to it anyway (e.g. google music can write there just fine).

If I switch the backup location to internal storage, it works fine but that defeats the purpose, I want to use my external microsd.

I've already tried uninstalling/re-installing, updating my SuperSU, rebooting the phone etc.

Any ideas?
Could be related to the update to 4.3 which changed permissions for writing to the external SD Card.

Check this thread out.

http://forum.xda-developers.com/show....php?t=2436494
The Following 2 Users Say Thank You to dratsablive For This Useful Post: [ Click to Expand ]
 
fincan
Old
#4  
fincan's Avatar
Senior Member - OP
Thanks Meter 76
Posts: 273
Join Date: Dec 2007
Location: around VA
Quote:
Originally Posted by dratsablive View Post
Could be related to the update to 4.3 which changed permissions for writing to the external SD Card.

Check this thread out.

http://forum.xda-developers.com/show....php?t=2436494
You are right. I rolled back my platform.xml thinking that the sd card issue has been fixed in 4.4, changing it back did the trick. Thanks
- Galaxy S4 Google Edition
- Nexus 7 FHD (2013)
 
dratsablive
Old
#5  
Senior Member
Thanks Meter 37
Posts: 358
Join Date: Feb 2011
Quote:
Originally Posted by fincan View Post
You are right. I rolled back my platform.xml thinking that the sd card issue has been fixed in 4.4, changing it back did the trick. Thanks
Your welcome!
 
Alpine-
Old
#6  
Alpine-'s Avatar
Senior Member
Thanks Meter 182
Posts: 771
Join Date: Aug 2007
Quote:
Originally Posted by fincan View Post
You are right. I rolled back my platform.xml thinking that the sd card issue has been fixed in 4.4, changing it back did the trick. Thanks
I updated to Kitkat 4.4 and am rooted. Im having the exact same issue with Titanium. It tells me the target dir is full and that it cant write/access the SD card. I changed permission of the SD Card with Root explorer but it doesnt stay.

How do I "roll back" platform.xml? I have no idea how to fix this. Never had any issue like this before in all my years of swapping roms and upgrading android builds.

Sac Rom 4.3 - build 5.6
Kernel: UF's Modded Stock MK2

 
fincan
Old
#7  
fincan's Avatar
Senior Member - OP
Thanks Meter 76
Posts: 273
Join Date: Dec 2007
Location: around VA
Quote:
Originally Posted by Alpine- View Post
I updated to Kitkat 4.4 and am rooted. Im having the exact same issue with Titanium. It tells me the target dir is full and that it cant write/access the SD card. I changed permission of the SD Card with Root explorer but it doesnt stay.

How do I "roll back" platform.xml? I have no idea how to fix this. Never had any issue like this before in all my years of swapping roms and upgrading android builds.
You have to edit yoour platform.xml file so Titanium Backup works again. Since you are already rooted, you can refer to this post for what to edit, where the file is etc.:
http://forum.xda-developers.com/show...php?p=44370296
- Galaxy S4 Google Edition
- Nexus 7 FHD (2013)
The Following 3 Users Say Thank You to fincan For This Useful Post: [ Click to Expand ]
 
Alpine-
Old
#8  
Alpine-'s Avatar
Senior Member
Thanks Meter 182
Posts: 771
Join Date: Aug 2007
Quote:
Originally Posted by fincan View Post
You have to edit yoour platform.xml file so Titanium Backup works again. Since you are already rooted, you can refer to this post for what to edit, where the file is etc.:
http://forum.xda-developers.com/show...php?p=44370296
Thanks, I found an identicle How-To here: http://www.androidauthority.com/gala...rd-fix-254960/

They are the same, both work. This one is a little easier to follow. I'm shocked this bug mad it over from 4.3 and into 4.4.2 official builds. All is well now though.

Sac Rom 4.3 - build 5.6
Kernel: UF's Modded Stock MK2

The Following 2 Users Say Thank You to Alpine- For This Useful Post: [ Click to Expand ]
 
Parinibbana
Old
(Last edited by Parinibbana; 14th May 2014 at 05:46 AM.)
#9  
Member
Thanks Meter 27
Posts: 60
Join Date: Dec 2013
Info 2 Titanium Backup with insuffiecient storage space - 1 problem , 3 solutions

To summarize, I have come across three solutions to this problem.

1.
Change the backup-location to /storage...
Open Titanium and go to Settings/Preferences/Backup folder location
Change to: /storage/emulated/legacy/TitaniumBackup

2.
If you had Titanium Backup installed on a previous ROM, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working. Reinstalling the app might lead to an insufficient storage space error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup.

Here’s how:
Using any file explorer like Root Explorer or ES File Explorer, go to /data/app , find and delete ”com.kermidas.TitaniumBackup-1.odex“. Now you can install Titanium Backup again!
If there is no such file in your folder, thatīs OK. But please donīt delete any .apk file!

3.
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2). The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.

The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.

Original:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
</permission>

New:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>

Done.

After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that accesses either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.

This may also fix other apps that have issues writing to the card.

--------------------------------------------------------------------------------
If you find this post useful, pls feel free to click on "Thanks".
Have a nice day
The Following 23 Users Say Thank You to Parinibbana For This Useful Post: [ Click to Expand ]
 
idrak3
Old
#10  
idrak3's Avatar
Member
Thanks Meter 1
Posts: 57
Join Date: Mar 2008
Quote:
Originally Posted by Parinibbana View Post
To summarize, I have come across three solutions to this problem.

1.
Change the backup-location to /storage...
Open Titanium and go to Settings/Preferences/Backup folder location
Change to: /storage/emulated/legacy/TitaniumBackup

2.
If you had Titanium Backup installed on a previous ROM, doing a non-wipe install could stop the process of Titanium Backup. You might receive a pop-up notification that Titanium Backup has stopped working. Reinstalling the app might lead to an insufficient storage space error — when an app is uninstalled or modified, it leaves a .odex residue file which causes the error. So all you have to do is delete the .odex file of Titanium Backup.

Here’s how:
Using any file explorer like Root Explorer or ES File Explorer, go to /data/app , find and delete ”com.kermidas.TitaniumBackup-1.odex“. Now you can install Titanium Backup again!
If there is no such file in your folder, thatīs OK. But please donīt delete any .apk file!

3.
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.

The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart your tablet.

Original:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
</permission>

New:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>

Done.

After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that accesses either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.

This may also fix other apps that have issues writing to the card.

--------------------------------------------------------------------------------
If you find this post useful, pls feel free to click on "Thanks".
Have a nice day
thanks
Samsung Galaxy s3
Samsung Galaxy s4

Tags
insufficient storage space, tibu, titanium backup
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes