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

Search This thread
By:
Advanced…
m0e_03

m0e_03

Senior Member
May 7, 2012
481
190
KL / M'sia
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:
Saint AAI said:
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
Click to expand...
Click to collapse


Useful feedback:
buu1152 said:
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 ;)
Click to expand...
Click to collapse

============================
Hit THANKS if this helped. :good:
 
Last edited:
  • Like
Reactions: aaanadie, ROMAD27, stef0707 and 50 others
Sort by date Sort by votes
BobDiaz

BobDiaz

Member
Dec 22, 2014
44
8
http://lavairisx8.blogspot.com.br/2015/09/solution-titanium-backup-backup-failed.html

---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
cwhiatt said:
Open SuperSU and move to Settings tab.
Now scroll till you find Security.
Notice that Mount namespace separation is already checked, now uncheck it and reboot your device.
Done.!!
Click to expand...
Click to collapse
This is the only thing that worked for me. Please op, add-it to the main post.
I've noticed this in the following link:
http://lavairisx8.blogspot.com.br/2015/09/solution-titanium-backup-backup-failed.html
 
  • Like
Reactions: cwhiatt
Upvote 0 Downvote
A

attituderocks114

New member
Apr 11, 2016
1
1
None of the suggested methods helped ..this is what helpled me .
If you are using lolipop based ROM : here is the solution .

This is due to the 'Mount namespace separation' setting in SuperSU being turned on (by default). Untick that, reboot and try your Titanium Backup operation again.

This happens because of permissions to app-created folders being restricted in newer Android versions, I believe. Ironically, I didn't have this issue on Marshmallow-based CM13, but I did face it in the Lollipop-based OxygenOS for the OnePlus One.

Finally Titanium backup is back for me !!:eek:
 
  • Like
Reactions: 3kokoten
Upvote 0 Downvote
cwhiatt

cwhiatt

Senior Member
May 8, 2014
872
317
Minneapolis
attituderocks114 said:
None of the suggested methods helped ..this is what helpled me .
If you are using lolipop based ROM : here is the solution .

This is due to the 'Mount namespace separation' setting in SuperSU being turned on (by default). Untick that, reboot and try your Titanium Backup operation again.

This happens because of permissions to app-created folders being restricted in newer Android versions, I believe. Ironically, I didn't have this issue on Marshmallow-based CM13, but I did face it in the Lollipop-based OxygenOS for the OnePlus One.

Finally Titanium backup is back for me !!:eek:
Click to expand...
Click to collapse

That's a great idea. I'm glad I posted it.
 
  • Like
Reactions: tb417
Upvote 0 Downvote
Justice.Dazzle

Justice.Dazzle

Member
Jul 11, 2011
24
8
Schenectady, NY
justice-dazzle.com
LG Nexus 5X
Motorola Razr (2019)
Hmm...(Post Name is) [SOLVED!!][ROOT ONLY] Insufficient Storage Space: Titanium Backup Error

I think that you are the one that is confused there bud...

m0e_03 said:
thank you for your support Mr.Saint, but I believe this thread was to solve the issue of NOT being able to install TB..then how is someone even supposed to run TB if its not even installed on the device, right? o_O"
Click to expand...
Click to collapse
 
Upvote 0 Downvote
D

desrod

Member
Nov 27, 2012
13
1
Just a quick heads-up: /storage/emulated/0/ and /storage/emulated/legacy/ are the same exact folder, and they reside on the device's internal flash, not the external SD card, which is what the original issue is about. So far, not a single person has come up with a workable fix:

1.) Deleting *.odex files does not fix it
2.) Disabling the namespace separation in SuperSU (or enabling it) does not fix it
3.) Changing the path to /storage/emulated/0/ or /storage/emulated/legacy/ does not fix it
4.) Removing, reinstalling does not fix it
5.) Using Link2SD does not fix it
6.) Setting the write bits to the SD card with ES-File Explorer or Root Explorer does not fix it

So anyone else have any ideas? Because it's still an open issue.
 
Upvote 0 Downvote
JensAmi

JensAmi

Member
Jun 12, 2011
19
7
Fix for those not fixed by the standard fixes

desrod said:
Just a quick heads-up: /storage/emulated/0/ and /storage/emulated/legacy/ are the same exact folder, and they reside on the device's internal flash, not the external SD card, which is what the original issue is about. So far, not a single person has come up with a workable fix:

1.) Deleting *.odex files does not fix it
2.) Disabling the namespace separation in SuperSU (or enabling it) does not fix it
3.) Changing the path to /storage/emulated/0/ or /storage/emulated/legacy/ does not fix it
4.) Removing, reinstalling does not fix it
5.) Using Link2SD does not fix it
6.) Setting the write bits to the SD card with ES-File Explorer or Root Explorer does not fix it

So anyone else have any ideas? Because it's still an open issue.
Click to expand...
Click to collapse

I was having the same problem: none of these fixes worked. I was guessing it was a permissions problem/error. What I did:
  • Created a new folder in the standard internal storage area called "TiBu"
  • Changed the path to /storage/emulated/0/TiBu (TiBu copies the existing backups over to the new folder)
  • Restarted Titanium Backup
  • Started/completed backup successfully
  • Completed victory dance
  • Killed TitaniumBackup in Apps (Forced to end)
  • Renamed orginal folder (TitaniumBackup to _TitaniumBackup)
  • Started TitaniumBackup (I think it automatically creates the standard folder "TitaniumBackup" if not there) and chose the standard folder
  • Started/completed backup successfully
  • Deleted the _TitaniumBackup folder (in recovery as the permissions were locked down even for root)
  • Thanked various gods
 
Last edited:
  • Like
Reactions: m0e_03
Upvote 0 Downvote
robotapocalypse

robotapocalypse

Senior Member
Nov 7, 2011
87
13
That's still backing up to the internal storage and not to the external SD card isn't it? Trying to find a way to offload all this data to the 200GB SD card that is sitting pretty empty.

JensAmi said:
I was having the same problem: none of these fixes worked. I was guessing it was a permissions problem/error. What I did:
  • Created a new folder in the standard internal storage area called "TiBu"
  • Changed the path to /storage/emulated/0/TiBu (TiBu copies the existing backups over to the new folder)
  • Restarted Titanium Backup
  • Started/completed backup successfully
  • Completed victory dance
  • Killed TitaniumBackup in Apps (Forced to end)
  • Renamed orginal folder (TitaniumBackup to _TitaniumBackup)
  • Started TitaniumBackup (I think it automatically creates the standard folder "TitaniumBackup" if not there) and chose the standard folder
  • Started/completed backup successfully
  • Deleted the _TitaniumBackup folder (in recovery as the permissions were locked down even for root)
  • Thanked various gods
Click to expand...
Click to collapse
 
Upvote 0 Downvote
robotapocalypse

robotapocalypse

Senior Member
Nov 7, 2011
87
13
I found a solution that works for me. Found on Reddit.

Go to Menu-Preferences-Backup Folder Location.
At the top it says "Storage Provide." Click on it and then click on DocumentProvider Storage.
Find your external card and map the folder you want to use.

That did it for me.
 
  • Like
Reactions: kiwigi and allroy1975
Upvote 0 Downvote
A

AniLeo

Senior Member
Jan 11, 2017
61
7
I backed up all the uset apps and data ...And then switched to lineage from Resurrection ....I wiped system and data...
When I reinstalled titanium backup for restoring apps and their data ..It was showing no backup.....Even though I had the backup in my internal storage....
How to restore apps and data ...When you switched ROMs??
 
Upvote 0 Downvote
B

bobo46

New member
Oct 2, 2011
3
0
I tried many ways, and I found this will actually work.
open /system/etc/permissions look for the file name : platform.xml

open it and find this：
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />

add this:
<group gid="media_rw" />


it will become：

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

Then, make sure you uninstall the Titanium app, and reinstall. Then it will work!
Not only for Titanium, even for any other app cannot download to the sd card, it will work as well.
 
Upvote 0 Downvote
S

sgtslaughter64

Senior Member
Feb 17, 2012
477
83
Samsung Galaxy Watch 4
bobo46 said:
I tried many ways, and I found this will actually work.
open /system/etc/permissions look for the file name : platform.xml

open it and find this：
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />

add this:
<group gid="media_rw" />


it will become：

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

Then, make sure you uninstall the Titanium app, and reinstall. Then it will work!
Not only for Titanium, even for any other app cannot download to the sd card, it will work as well.
Click to expand...
Click to collapse
I did this and now I get force close when trying to open TB. Any suggestions?
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

S
[Q] Root for Asus Fonepad
Replies
2K
Views
1M
Willjoe2442
Willjoe2442
Boskan
All about HUAWEI Ascend Y530 (Q&A, Root,Unlocking, etc)
Replies
4K
Views
1M
V
vista_user
s7yler
[How to/MTK65xx] ROOT, Backup & Flash (MTKDroidTools, Spflashtool, CWM) [MTK Only]
Replies
81
Views
273K
R
ramunsa
D-FUSE
New Galaxy Avant G386T & G386T1 - We have root and recovery
Replies
3K
Views
574K
G
greggit1986
F
[HOW TO ROOT]Tinji I9300
Replies
1K
Views
367K
Willjoe2442
Willjoe2442

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 53
    m0e_03
    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:
    Saint AAI said:
    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
    Click to expand...
    Click to collapse


    Useful feedback:
    buu1152 said:
    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 ;)
    Click to expand...
    Click to collapse

    ============================
    Hit THANKS if this helped. :good:
    View
    14
    S
    Saint AAI
    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
    View
    7
    opscsd
    opscsd
    A possible Solution

    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:
    View
    4
    joemamahey
    joemamahey
    SOLVED for SGS4 4.4 w/root ext SD card

    So I was having this same problem but the aforementioned fixes didn't address the external SD card. I figured out that the error message is a bit misleading and that the actual problem was that the backup storage location wasn't writable by TiBU. searching on that issue I found the below post and modified the platform.XML file using root explorer. The original platform.xml on my phone looked a bit different than bleez99's. This is how I changed the file:

    Before mod:
    <permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
    <group gid="sdcard_r" />
    <group gid="sdcard_rw" />
    </permission>

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

    A reboot is required for changes to take effect.

    All credit to bleez99 for this fix. If this helps you please thank his post below.

    http://forum.xda-developers.com/showpost.php?p=44370296&postcount=357
    bleez99 said:
    I have a fix. I did a little research and found that you can edit /etc/permissions/platform.xml and add a group to WRITE_EXTERNAL_STORAGE

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

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

    Done. Doing a TiBU right now to my external card.
    This _may_ fix other apps that have issues writing to the card, I personally didn't find any.

    Suggest that you do an adb pull of the file for safekeeping before doing this.
    If you pull the file, edit it, and push it back make sure the permissions are set to 644.

    Thanks to everyone who made this "OTA" happen.
    I was able to do a no wipe update to MH1 :)
    Click to expand...
    Click to collapse

    edit:
    For those worried about moding system files I haven't seen any adverse side effects from this mod. This might be anecdotal but I figure if anything does go screwy I(or you) can always change the file back in 2 min.
    View
    4
    Sushi3110
    Sushi3110
    Saint AAI said:
    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
    Click to expand...
    Click to collapse

    Exactly my Problem, perfectly solved. Thanks!
    View

New posts