[Resolved] [SOLVED!!][ROOT ONLY] Insufficient Storage Space: Titanium Backup Error

[m0e_03]

If you have Titanium Backup installed on your previous version, 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 (ForceClose). Reinstalling the app might lead to an "insufficient storage" 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 in the system.

Disclaimer
This information comes with no warranty! What you're going to do is completely at your own risk!
I shall not be held responsible for any damage to your device if you had chosen to follow the steps below. Cheers!!

Here's how to do it:
## Make sure your phone is rooted. :good:
1- Use any file explorer like Root Explorer or ES File Explorer, etc.
2- go to /data/app,
3- find and delete "com.kermidas.TitaniumBackup-1.odex".
4- Now you can install Titanium Backup again!
[source: Insufficient Storage Space]


Another Solution:

If deleting ODEX files does not work, or there are none. Try the following:

1. In TitaniumBackup press menu, then press preferences under the general section.
2. Next, under backup protection settings, press backup folder location.
3. When the new menu appears, press back to get to a file browser. It should say something like /storage/emulated/0 for the path.
4. Press back again and then select legacy, so the path is now /storage/emulated/legacy
5. Then scroll to your TitaniumBackup folder and select it.
6. Then press use the current folder, and press yes when the popup appears.

Then try doing your normal backup procedure.

I've had this problem for days now on my HTC One and it has been doing my head in. Found a similar solution in the galaxy S4 forums, so thought I would share as this solved it for me.

Source: http://forum.xda-developers.com/showthread.php?t=2391363

Useful feedback:

If you have done like me, and tried deleting ODEX files, changing path of folder to /legacy and trying reinstall and still get insufficient free space, then changing file location back to emulated/0...should solve the problem..

OH BTW i'm running PA 3.99 RC-2 with franco's r184.. so if your running earlier versions of those, you may need to stick with emulated/legacy.. all in all, try both paths and which ever works for you is where your power lies

============================
Hit THANKS if this helped. :good:

 

[Techminator]

Sorry. I have no other suggestions. Good luck. I was able to get a response from the devs at Titanium Track. Keep on trying to contact them. My email failed the first time but I did get an email to get to them.

Well I think I'll take this up with them but could you please email them and tell the that their email bounces back messages? Or if they have any other alternate way of contacting them?

 

[nastypup]

Well I think I'll take this up with them but could you please email them and tell the that their email bounces back messages? Or if they have any other alternate way of contacting them?

I Go to http://www.titaniumtrack.com/ and click on Support.

 

[Techminator]

I Go to http://www.titaniumtrack.com/ and click on Support.

Thanks pal! I just sent them a message via the website you provided and I got confirmation in email. I've described my problem to them and also told that I've followed all the solutions mentioned on this thread to no benefit.

Thanks

 

[nastypup]

Thanks pal! I just sent them a message via the website you provided and I got confirmation in email. I've described my problem to them and also told that I've followed all the solutions mentioned on this thread to no benefit.

Thanks

Glad my 67 year old brain is good for something ; -)

 

[John.Massiass]

Titanium track support finally got back to me. SDFix corrects the problem with Lollipop as it did with KitKat.

SDFIX made it for me. Thank you soooo much...

 

[wizzbang3]

If you are with Kitkat, try this app: https://play.google.com/store/apps/details?id=nextapp.sdfix


Abrcs

Just wanted to clarify, I installed latest Nordic ROM (N7105XXUFNL2) for the Note II (N7105 4G LTE INTL) and SuperSU and was having same problem. I tried the "mount namespace" fix in SuperSU, no luck.
I tried the link above and indeed SDFix has fixed the problem! thank you.

 

[offwhite]

thnks

Just wanted to clarify, I installed latest Nordic ROM (N7105XXUFNL2) for the Note II (N7105 4G LTE INTL) and SuperSU and was having same problem. I tried the "mount namespace" fix in SuperSU, no luck.
I tried the link above and indeed SDFix has fixed the problem! thank you.

 

[-V-O-Y-A-G-E-R-]

I had the same issue, but in my case I wanted TB to store backups on external microSD card. By Choosing DocumentProvider and then SD Card and then subfolder TitaniumBackup on it solved the issue.

 

[cnuis2cool]

Resolved

If still anyone getting the error after all tries, do this. Just uncheck the mount namespace separation option in SuperSu.

 

[Parinibbana]

Titanium Backup with insuffiecient storage space - 1 problem , 4 solutions

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

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

2.
There is an elegant way of giving TitaniumBackup write access to the external sdcard, without having to forfeit security (as in method 3 below).
Since the time of Android 4.3, Google uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder - not to the entire card!
In order to get TitaniumBackup to work without compromising security, you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/

If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/
Lastly, go tothe preferences of TitaniumBackup, choose "Backup folder location" and choose the above specified folder.
Finish.

Very clean and safe.

3.
There is a 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. This permission was not required for access to the external sdcard prior to Android 3.2, but for security reasons this is the case now.

If you're rooted and want to make the ext. sdcard writable to all apps, please try the following:
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 problems with other apps that have issues writing to the ext. sdcard, but please be aware that in terms of security, solution two (see above) is preferable.

4.
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!

5.
From SuperSU settings uncheck "Mount namespace separation".

Good luck!

--------------------------------------------------------------------------------
If you find this post useful, pls feel free to click "Thanks".
Have a nice day

 

[Theziggy]

A possible Solution: From SuperSU settings, Uncheck "Mount namespace separation"

Tibu tried to warn me that this might not be compatible, but as always I ignored all pop-ups without reading them first. Only noticed this after I re-installed TB for the 5th time. Spend a day and a Half trying all sorts of solutions. Serves me right :crying:

This worked for me, only thing I can't figure out is how you came up with the answer - BRILLIANT

 

[drgt]

Titanium Backup with insuffiecient storage space

A possible Solution: From SuperSU settings, Uncheck "Mount namespace separation"
Tibu tried to warn me that this might not be compatible, but as always I ignored all pop-ups without reading them first. Only noticed this after I re-installed TB for the 5th time. Spend a day and a Half trying all sorts of solutions. Serves me right :crying:

Thanks opscd. :angel::highfive:
This is what "ended up" working after I tried the methods summarized below WITHOUT success.
Problem first appeared after flashing to stock-rooted 0F3 on my SM-G900A and PlayStore's automatic re-installation of TI BU
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Thanks Parinibbana.

FYI for me the methods you summarized didn't work because

Method 1: doesn't resolve lack of access to SD; as it re-directs to internal device storage
Method 2: Is elegant and preferable for security but like method #1 ultimately fails because (highlighted within TI folder location menu) can't write to SD locations..which IS the symptom I'm experiencing.
Method 3: I personally hesitated to use this for personal security concerns but more interestingly I observed the following changes/differences in my platform.xml file...

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

I attempted to used the SDfix app (again unsuccessfully even after rebooting), but after the platform.xml read DIFFERENTLY than the procedure I was following

My New: (viewing with ES Note Editor)
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" /> <== * I am guessing I could manually edit/delete this line but am a nube :silly: and was too scared
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>

Method 4: I couldn't use this method because the "com.kermidas.TitaniumBackup-1" folder existed; BUT there was no .odex files... only the .apk

To summarize, I have come across four solutions to this problem.
1.
Change the backup-location to /storage/emulated/legacy/TitaniumBackup
Just open Titanium and go to Settings/Preferences/Backup folder location
Change to: /storage/emulated/legacy/TitaniumBackup

2.
There is an elegant way of giving TitaniumBackup write access to the external sdcard, without having to forfeit security (as in method 3 below).
Since the time of Android 4.3, Google uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder - not to the entire card!
In order to get TitaniumBackup to work without compromising security, you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/
If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/
Lastly, go tothe preferences of TitaniumBackup, choose "Backup folder location" and choose the above specified folder.
Finish.
Very clean and safe.

3.
There is a 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. This permission was not required for access to the external sdcard prior to Android 3.2, but for security reasons this is the case now.

If you're rooted and want to make the ext. sdcard writable to all apps, please try the following:
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 problems with other apps that have issues writing to the ext. sdcard, but please be aware that in terms of security, solution two (see above) is preferable.

4.
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!

Good luck!
--------------------------------------------------------------------------------
If you find this post useful, pls feel free to click "Thanks".
Have a nice day

 

[Parinibbana]

Thanks opscd. :angel::highfive:
This is what "ended up" working after I tried the methods summarized below WITHOUT success.
Problem first appeared after flashing to stock-rooted 0F3 on my SM-G900A and PlayStore's automatic re-installation of TI BU
+++++++++++++++++++++++++++++++++++++++++++++++++++++
Thanks Parinibbana.

FYI for me the methods you summarized didn't work because ...

Thanks. I now added the method "From SuperSU settings, Uncheck Mount namespace separation" to my original post (method no. 5), since it seems to work for many users.

 

[archz2]

I have a weird problem. I tried the emulated method, it didn't work. I tried searching for com.kermidas.TitaniumBackup-1.odex but could not find it. However, I found a com.kermidas.TitaniumBackup-1 folder and deleted it after which I reinstalled titanium backup and the problem still did not solve.

My external SD card (with free space as 1.60 GB) is shown in my phone as sdcard0. My internal sdcard is shown as sdcard1 (with free space as 1.45 GB). I changed my backup location in titanium backup preferences to internal sd card and I got rid of this "insufficient storage" problem.

I want titanium backup to enable me to use external sd card for default location of backup. What should I do?

I have a rooted lenovo a7000 phone.

 

[twinkyz1979]

I have tried all the fixes in this forum and nothing has worked. I have a Nexus 7 (grouper) running the latest 5.1.1 stock android. I have even went as far as uninstalling and booting into recovery and deleting cache and dalvik cache.

 

[meyerweb]

Does Titanium actually support this app any more? I've been trying for more than a week to get them to respond to a problem report submitted via their web site, and except for an automated response that said nothing I've gotten no reply at all. What are Google's policies regarding support of paid apps? Because TT doesn't seem to offer any actual support at all.

 

[pepillogrillo]

Does Titanium actually support this app any more? I've been trying for more than a week to get them to respond to a problem report submitted via their web site, and except for an automated response that said nothing I've gotten no reply at all. What are Google's policies regarding support of paid apps? Because TT doesn't seem to offer any actual support at all.

I make the same question myself.

I write two times and the only answer I become is the automatic answer from a robot.

I have also the paid version of TB and I have the problem ion two different ROMS the last one I`m in CM13 in my HTC one m8.

I tried any solution I have found on internet but nothing works now.

---------- Post added at 07:50 PM ---------- Previous post was at 06:52 PM ----------

Hi,

I don´t know if I can´t put this here, but it works for me meyerbe, try it:

https://youtu.be/GATqU1_xzqA

 

[obverse1]

Worked

A possible Solution: From SuperSU settings, Uncheck "Mount namespace separation"


I feel bad for you, I only lost 4 hours before I saw your tip and tried it and it worked. Thanks!

 

[cwhiatt]

Just started experiencing this issue on a rooted Samsung Galaxy S6.

Installed the ext sd module via xposed and no go. Changed the preference folder and no go....

---------- Post added at 03:57 AM ---------- Previous post was at 03:50 AM ----------

A possible Solution: From SuperSU settings, Uncheck "Mount namespace separation"


I feel bad for you, I only lost 4 hours before I saw your tip and tried it and it worked. Thanks!

Disregard my post beneath this post. This worked!

 

[fr0st420]

A possible Solution: From SuperSU settings, Uncheck "Mount namespace separation"

Tibu tried to warn me that this might not be compatible, but as always I ignored all pop-ups without reading them first. Only noticed this after I re-installed TB for the 5th time. Spend a day and a Half trying all sorts of solutions. Serves me right :crying:

Thanks! This worked for me.