Database Info

Titanium Backup: "Batch backup interrupted: insufficient free storage space"

Titanium Backup: "Batch backup interrupted: insufficient free storage space"
I was using TB without issues until SuperSu (Pro) updated to version 2.00. Now TB gives me constantly the "insufficient free storage" error. I have disabled Dropbox (and other) online backup, I have uninstalled/installed the app several times (including the Pro license).
My ROM is SlimRom 4.4.3 v5.9 (latest weekly). Other root apps are working ok. I want to save to external sdcard: /extSdCard/TitaniumBackup
SuperSu (Pro) latest version 2.00.
Of course I have free space (more than 2Gb).

Seems a 4.4.3 flood of issues is coming...
I've tested several symlinks to use sdcard, no one is working:
/storage/sdcard1/TitaniumBackup
/mnt/extSdCard/TitaniumBackup
/extSdCard/TitaniumBackup
/external_sd/TitaniumBackup
If anyone has an idea how to use TB with 4.4.3 and external sdcard I would thank so much if he/she posts how could solve the issue.

I also have the same problem using Android 4.4.2. All the proposed fixes (platform.xml edit; change directory to emulated/legacy; SDFix app; etc.) DO NOT WORK.
Please help us!

Into Titanium advanced settings, configure it to use your ROM's Busybox and not the one shipped with Titanium.
Restart the app and check if it helps.

Do you have an ext4. on your sdcard?
Sent from my SCH-R970C using XDA Premium 4 mobile app

noslippin said:
Do you have an ext4. on your sdcard?
Click to expand...
Click to collapse
No, the factory one, default, exFAT.

Technical said:
I was using TB without issues until SuperSu (Pro) updated to version 2.00. Now TB gives me constantly the "insufficient free storage" error. I have disabled Dropbox (and other) online backup, I have uninstalled/installed the app several times (including the Pro license).
My ROM is SlimRom 4.4.3 v5.9 (latest weekly). Other root apps are working ok. I want to save to external sdcard: /extSdCard/TitaniumBackup
SuperSu (Pro) latest version 2.00.
Of course I have free space (more than 2Gb).
Click to expand...
Click to collapse
Did you get this fixed? I was having same issues and finally got it resolved. Let me know.

twentynine30s said:
Did you get this fixed? I was having same issues and finally got it resolved. Let me know.
Click to expand...
Click to collapse
It went away the same way it comes. Right now, I think the change of the Busybox to system (and not to the TB Busybox) did the job.
What do you think it solved your problem?

Technical said:
It went away the same way it comes. Right now, I think the change of the Busybox to system (and not to the TB Busybox) did the job.
What do you think it solved your problem?
Click to expand...
Click to collapse
What solved mine was after updating to 4.4.2 (I have a Note II), it changed the way external was written to. I noticed the tibu folder was not writable and I wasn't even allowed to change permissions via root explorer. After some digging, I found this thread http://forum.xda-developers.com/showthread.php?p=44370296 which explains to modify platform.xml.
After editing the file and rebooting, no more issues with "insufficient free storage space".

twentynine30s said:
What solved mine was after updating to 4.4.2 (I have a Note II), it changed the way external was written to. I noticed the tibu folder was not writable and I wasn't even allowed to change permissions via root explorer. After some digging, I found this thread http://forum.xda-developers.com/showthread.php?p=44370296 which explains to modify platform.xml.
After editing the file and rebooting, no more issues with "insufficient free storage space".
Click to expand...
Click to collapse
Thanks, but that was my ROM default platform.xml file, so it's not the same. My problem could be somewhere else as the .xml file was always in the correct form on how is suggested in that thread. Thanks anyway.

I currently have the same issue, which just happened recently, with v 4.4.2 on my TMO Galaxy S5. Currently Stock rooted with Philz Recovery.
Did you solve your issue?
Did you try the flashing of SuperSU and Superuser?

It could be androids new security feature that doesn't allow apps to write to SD cards. One of the main reason google removed the code for SD card support from stock android.

Soved the problem by installing Alliance ROM because it has the following feature: • Enabled External Sd-Card Read/Write Functionality

I started getting this message about a month ago after using TiBu for years. I use SlimRom on a Note 2. It does work to backup and restore to the internal card.
I don't have a problem accessing the external sdcard (sdcard1) from any other app. Rom Toolbox Pro and Helium do not have a problem creating or restoring backups to it. Titanium Backup will usually backup a few apps, as many as 5 or more to as little as none, before it bombs out and displays the insufficient storage message. It is not a problem with storage since I have over 20gb free. My permissions.xml file already has the sdcard permissions set correctly. I have tried updating superuser and forcing system busybox to no avail.
Any ideas as to what the problem could be?

twentynine30s said:
What solved mine was after updating to 4.4.2 (I have a Note II), it changed the way external was written to. I noticed the tibu folder was not writable and I wasn't even allowed to change permissions via root explorer. After some digging, I found this thread http://forum.xda-developers.com/showthread.php?p=44370296 which explains to modify platform.xml.
After editing the file and rebooting, no more issues with "insufficient free storage space".
Click to expand...
Click to collapse
Works for my Xiaomi Redmi Note. Thanks so much.

Got the solution
I did everything but the solution was provided by TB itself when it gave an error message at startup. Just uncheck the mount namespace separation option in supersu. Done.

adnanschat said:
I did everything but the solution was provided by TB itself when it gave an error message at startup. Just uncheck the mount namespace separation option in supersu. Done.
Click to expand...
Click to collapse
I've loaded on the stock Nordic latest (N7105XXUFNL2) from for my N7105 (Note II INTL LTE) and I'm getting the error everyone else is :/
I tried this one htere, with the namespace separation, no dice, should I start editing XML files?
Frustrating.

adnanschat said:
I did everything but the solution was provided by TB itself when it gave an error message at startup. Just uncheck the mount namespace separation option in supersu. Done.
Click to expand...
Click to collapse
Now fixed by a tool called "SDFix" - go grab it, it helped me.

Whizzing : Do you have lollipop ??
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

KitKat sdfix works on lollipop

Galaxy S7 SM-G930F (6.0.1) - System Partition Size

Hi All
I am hoping someone can help... I have the Galaxy S7 (SM-G930F / 6.0.1 / UK / EE) and have come up with an issue.
I use Cerberus Apps in case my phone is lost - you are able to install this into the system to avoid someone wiping the phone and removing the software. To do this the phone must be rooted and then I usually use Link2SD to transfer the app to make it a system app. This has always worked on my old phones - but alas not this time.
The problem is that the system partition (4Gb) is full!! I have deleted all the language packs to try and clear some space - but it is still full! Strangely enough I also uninstalled an "Amazon" app which was listed as being a system app and quite large (from memory I think it was just under 100Mb)... but when I removed it and rebooted the system partition free space remained unchanged! It's possible that Amazon was a user app and I mis-read it... but anyway - I thought that the only way to clear some space was to resize the system partition - so I installed TWRP (3.0.2), have done a complete backup (system/efs/etc) apart from \data as this showed 0Mb and "failed to mount" when I tried to back it up originally.
So, my question is - can anyone help me to free some space from the system partition to allow Cerberus App to be stored there? I did think about uninstalling the VR Gear files as I dont have a VR device and assumed I could re-load these from Google Play if needed - but I do have the Galaxy Gear watch - so decided not to remove these files in case it screwed this up. Not sure which Google Apps I can remove and re-install if needed... so if anyone knows this, then that would be a help too
I thought you could resize the partition in TWRP but cant find any clear details on how to do this, so thought I'd ask here before I screw the phone up :silly:
Any ideas/help greatly received.

TWRP doesn't support encryption so that's likely why /data won't mount. Resizing partitions is typically done via Odin with PIT files, but it's very dangerous, so I wouldn't recommend it.
Luxembourg ROMs have around 130mb free system space, so there must be a ton of carrier bloat in yours. This doesn't sound right though, it's required that there is some space for expansion. Could you run the following command in a root terminal and post the results please?
df -k | grep system

CurtisMJ said:
df -k | grep system
Click to expand...
Click to collapse
Thanks Curtis - I left my phone at home today, so will try this tonight and post results. After deleting all the unwanted language files I have about 40Mb space free, but this still doesnt seem to be enough as when I run Link2SD and reboot the phone, Cerberus has vanished and has to be re-installed... although when it re-installs it shows it as an "update" which would indicate that it is installed already - just 'lost' ???
Will update tonight when I get a moment.
Thanks

That's interesting actually. It seems to be indicative of permission issues. The app was successfully moved to the system, but the permissions on its files were wrong and the system refuses to load it(Link2SD's fault, essentially) . It's still acknowledged by the app manager though, which is why it can be "updated". Can you try move it with something apart from Link2SD? I recommend titanium backup.

CurtisMJ said:
Can you try move it with something apart from Link2SD? I recommend titanium backup.
Click to expand...
Click to collapse
Thanks Curtis - I have Titanium Backup (free version) installed already so can give it a go - I have only used it for backups (a long while ago) and have never used it to relocate an app... is it fairly self explanatory how to do it?
Will look tonight when I get in
Thanks

Just tried with titanium myself and it fails in a similar manner. Seems Marshmallow is a little fiddly and Link2SD puts out a generic message when it has issues. Titanium just freezes. You'll have to do it manually
First you'll need to clear the system of failed attempts. Look in the /system/app and /system/priv-app with a root Explorer for Cerberus apks or folders. Next, look in the /data/app folder and find the Cerberus folder. Take note of this path.
Next, fire up a root terminal and enter the following commands. In my case I was moving Greenify.
mount -o remount,rw /system
cp - a /data/app/com.oasisfeng.greenify-1 /system/app/Greenify
Replace the data folder with your noted path. The system path can be anything.
Then reboot and the app should be system.

Hi Curtis
Thanks for spending so much time on this.
OK, I skipped straight to the manual relocation method that you said. Whilst the app is Cerberus the APK etc is called System Framework as I have installed the 'hidden' version rather than the one which shows as Cerberus on the phone. However using OI File Manager, when I look in /system/app and /system/priv-app folders there is nothing called Cerberus or System Framework... so I am assuming that there are no orphaned APKs or other files.
But, this is where the strange thing starts, when I look in the /data/app folder, it is empty... so I am guessing I am looking in the wrong place as there are loads of apps! I am looking from home then selecting data, etc... any thoughts?
Oh, I have checked that hidden files are shown too!
Thanks again

i used to install the same app on my S7
please follow this guide & let me know the result.
1- uninstall Cerberus App, Link2SD, TTb, etc. and reboot
2- install SystemCleanup.
3- from the app SystemCleanup swip to tab apps and remove some bloatware like Google books, music, games, google TTS.
4- Reboot & install Cerberus App, do not run it.
5- from the app SystemCleanup go to apps tab and move Cerberus App to system/app & reboot again.
6- That's all.
Click to expand...
Click to collapse

Hi Abuzar
Thanks for the help... I tried using System Cleanup and initially it didn't work... it didn't show System Framework after cleaning up which made me think it was uninstalled properly. But when I tried to re-install it I got a message asking if I wanted to update the the built in application... so I said yes and re-checked in System Cleanup and it was visible, so I tried uninstalling it and after a couple of attempts it succeeded.
Then I re-installed and it installed it as a new app and it was visible in System Cleanup as installed in /data. So, I moved it to /system and configured it. It now lists in System Cleanup as being installed @auto system+data... so I am assuming it has installed properly... but not 100% sure as it lists some of it in data - so not sure if after a reset it will wipe the user profile from Cerberus or not.
I took a backup in TWRP and thought I would do a factory reset and test it... but on the S7 using factory reset in O/S it asks for my samsung password etc so looks like it may delete my Samsung/Google account's so didn't proceed as I didn't want to delete any online info. So... I tried factory wipe in TWRP but it just said failed "could not mount /data and unable to find crypto footer" and a few more "failed to mount /data" errors... so I gave up and will have to assume its installed properly as a system app
Thanks for all your help.

Just as a final note, the system+data combo sounds normal. Under regular conditions, the system partition is read only, so in order to install any updates to system apps, Android actually installs them as data apps, but cross-references them to system apps and gives them the relevant permissions. You can remove the data part by selecting "Uninstall Updates" in the app info page.

Unable to create folder /data/media/0/TWRP/BACKUPS

I've read a few posts that seem similar but nothing too recent. I'm trying to backup what I have now so I can flash another ROM but it keeps failing. I even used es file manager with root and created the folder needed and gave it root permissions but it still fails in TWRP to backup.

Switch on „mount namespace separation“ in super su

jeffrimerman said:
I've read a few posts that seem similar but nothing too recent. I'm trying to backup what I have now so I can flash another ROM but it keeps failing. I even used es file manager with root and created the folder needed and gave it root permissions but it still fails in TWRP to backup.
Click to expand...
Click to collapse
Are you decrypted? Else you won't be able to back up.

alexS123 said:
Switch on „mount namespace separation“ in super su
Click to expand...
Click to collapse
Thanks guys, I was wondering about if I'm decrypted or not. How do I check? It's probably a dumb question =/. I ended up installing another ROM and it uses Magisk baked into it so I don't see an option for mount namespace separation. Maybe I can attempt to backup now just to see if it works with this ROM or maybe it's not decrypted still. For some odd reason it refused to let me install Facebook, or Facebook Messenger from the play store and one of my apps won't start. It just tries to start then crashes. I downloaded a couple "updates" from a site that says they are stock ROMs. "update_full_hw_usa.zip" is 544 mb and "update" is 1.72gb. I'm thinking of going back to stock but that would probably lock the bootloader and erase twrp right?
Edit: I tried to back up again but it does the same thing. I did notice it also says "failed to unmount /DATA". It might have said that before.
Edit: I see under security the encrypt phone section. At the bottom the "Encrypt Phone" button is faded out and above it I see "Charge your battery and try again" and "Plug in your charger and try again" so I'm not too sure but guessing that means I'm not encrypted but it is faded out so maybe it is?

jeffrimerman said:
Thanks guys, I was wondering about if I'm decrypted or not. How do I check? It's probably a dumb question =/. I ended up installing another ROM and it uses Magisk baked into it so I don't see an option for mount namespace separation. Maybe I can attempt to backup now just to see if it works with this ROM or maybe it's not decrypted still. For some odd reason it refused to let me install Facebook, or Facebook Messenger from the play store and one of my apps won't start. It just tries to start then crashes. I downloaded a couple "updates" from a site that says they are stock ROMs. "update_full_hw_usa.zip" is 544 mb and "update" is 1.72gb. I'm thinking of going back to stock but that would probably lock the bootloader and erase twrp right?
Edit: I tried to back up again but it does the same thing. I did notice it also says "failed to unmount /DATA". It might have said that before.
Edit: I see under security the encrypt phone section. At the bottom the "Encrypt Phone" button is faded out and above it I see "Charge your battery and try again" and "Plug in your charger and try again" so I'm not too sure but guessing that means I'm not encrypted but it is faded out so maybe it is?
Click to expand...
Click to collapse
Go to twrp, advanced, file manager. Browse to /data/app and see if you see normal folders or randomly named folders. If the latter you are encrypted.
Same if you tap install then try to install from internal sd.

ante0 said:
Go to twrp, advanced, file manager. Browse to /data/app and see if you see normal folders or randomly named folders. If the latter you are encrypted.
Same if you tap install then try to install from internal sd.
Click to expand...
Click to collapse
Thank you. I should have checked that before I put another ROM. I did see randomly named folders when I connect it to my laptop but I can't remember when but I bet it was in that folder. I ended up within TWRP formatting data I think but it did have my type "yes" and said it would eliminate encryption, then I installed the new ROM. I should check and see if the new ROM has encryption. So far data on the root drive isn't encrypted and data in the android folder isnt' encrypted when I check with my laptop.
Edit: It's backing up so must not be encrypted. I check using the file manager in twrp and can see all the files in data. Thanks for you help. I guess if I had sensitive info on my phone then it would be something to do but I don't have a need to encrypt.

jeffrimerman said:
Thank you. I should have checked that before I put another ROM. I did see randomly named folders when I connect it to my laptop but I can't remember when but I bet it was in that folder. I ended up within TWRP formatting data I think but it did have my type "yes" and said it would eliminate encryption, then I installed the new ROM. I should check and see if the new ROM has encryption. So far data on the root drive isn't encrypted and data in the android folder isnt' encrypted when I check with my laptop.
Edit: It's backing up so must not be encrypted. I check using the file manager in twrp and can see all the files in data. Thanks for you help. I guess if I had sensitive info on my phone then it would be something to do but I don't have a need to encrypt.
Click to expand...
Click to collapse
If you did format data again now, flash the data files supplied by your rom. (Public and Hw data) else you will have problems with themes and stuff.
If you didn't format data now, disregard this message

ante0 said:
Are you decrypted? Else you won't be able to back up.
Click to expand...
Click to collapse
You can take a backup using this thread
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482

mansi0312 said:
You can take a backup using this thread
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
That's for OPO6.

WhatsApp backup restoration without google account?

WhatsApp downloaed today 2.18.358
old device:
Running local backup - works well - all 113 MB file is properly created with the name msgstore.db.crypt12
new phone same WhatsApp .apk
Then copying this to a new phone putting on folder WhatsApp/databases - all good
installing whatsapp - all fine
runing WhatsApp on a new device:
- License agreement screen (ok),
-two more pop-ups with permission access to contacts/storage/etc. All permissions were granted.
number verification (same number) (ok - entering the code) then asking if it should get permission to access google drive.
- skipping it - moves to app without attempt to restore local backup
- giving permission moves to pop-up of creation the google drive account, so I can select only "none" and in the end also application is also starting without attempt to restore local backup
Any ideas, Dear Friends?

lady_kasia said:
WhatsApp downloaed today 2.18.358
Any ideas, Dear Friends?
Click to expand...
Click to collapse
TB done the trick to me moving from old to new phone (and from Nougat to Oreo same way), plus manual copying content of Android/data/ [whatever is whatsapp dir in you old phone)

spamtrash said:
TB done the trick to me moving from old to new phone (and from Nougat to Oreo same way), plus manual copying content of Android/data/ [whatever is whatsapp dir in you old phone)
Click to expand...
Click to collapse
was it described by you somewhere?
able o copy/paste it here, please?

lady_kasia said:
was it described by you somewhere?
able o copy/paste it here, please?
Click to expand...
Click to collapse
list to do: install (if you do not have it) Titanium Backup on the OLD phone. In Preferences, set Backup app external data as Enabled (Always).
Check where the backup folder is created on the phone. Typically, it would be TitaniumBackup in root folder of the card.
Copy the folder to new phone.
Install TB on the new phone
Run it, scroll down, or input in the search: Whats (shall find it now), then click Restore.
Check if it works now, if not (e.g. android different version on old and new phone) - reinstall (do not uninstall from settings, go to GooglePlay and reinstall from there).

spamtrash said:
list to do: install (if you do not have it) Titanium Backup on the OLD phone. In Preferences, set Backup app external data as Enabled (Always).
Check where the backup folder is created on the phone. Typically, it would be TitaniumBackup in root folder of the card.
Copy the folder to new phone.
Install TB on the new phone
Run it, scroll down, or input in the search: Whats (shall find it now), then click Restore.
Check if it works now, if not (e.g. android different version on old and new phone) - reinstall (do not uninstall from settings, go to GooglePlay and reinstall from there).
Click to expand...
Click to collapse
That could be a great idea.
Here is what worked for me:
1. (creating) and connecting google account to old phone
2. backing up all WhatsApp to Google account as defult option by app
(message after upload of 100% of 1GB : FAILED)
3. connecting same google account to new phone
4. trying to download backup
reported: NOT FOUND
so I found this could be a problem with backup file itself upon it was being generated.
What helped for that:
Going to classic memory (no root folders) and removing ALL folders of WhatsApp (this from SD_card - images, videos, etc).
And then doing backup again.
This time it worked.
Maybe not as intended (without google participation) but at least the case is solved and reason probably found (some old file preventing backup to be recognized as proper backup - even when done with good size of 100MB+ each time).
Next time will try with Titanium Backup

New Pixel 3 setup: Restoring backups fails with both Titanium and MyBackup Pro

I'm setting up a new Pixel 3 (Android 9), and moving from a Note 4 (Android 6.0.1).
When setting up, Google installs some, but not all, apps from the store. The missing apps I expected to restore from redundant Titanium Backup and My Backup Pro backups.
I have successfully installed Magisk 18.1 using the Boot Image Patch method (no TWRP)
Titanium Backup Pro reports it has superuser rights. When I try to restore an app created with the Note 4, Titanium Backup hangs forever on the "Restoring App+Data AppName n.n.nn.n" overlay with the spinning circle. TiBk is unresponsive, although Android is still running and I can see home screen or notifications. Restart is required to clear the pending action. I have run TiBk with USB debugging enabled (if that is still required), but get the same failure.
I also have MyBackup Pro. When I try to restore an apk (or apk+data), it appears to run normally. MBP reports it has superuser rights. At the end of the process the status summary says: Appname: failed: cp: can't create '/data/app/appnamestring-1/appnamestring.apk': Path does not exist.
I tried using MBP to back up an app already installed on the Pixel 3 from the store, and then restore it. It gives the same error, except the place where there is "appnamestring-1" in the Android 6 backup, there is now something like "appnamestring-2fjdk56akjfkdye7dkfja9=="
Also, I observe that the app that was installed prior to this backup restore experiment is no longer present afterward. I re-installed from the store.
Can anyone suggest next steps for solving this issue?

timg11 said:
I'm setting up a new Pixel 3 (Android 9), and moving from a Note 4 (Android 6.0.1).
When setting up, Google installs some, but not all, apps from the store. The missing apps I expected to restore from redundant Titanium Backup and My Backup Pro backups.
I have successfully installed Magisk 18.1 using the Boot Image Patch method (no TWRP)
Titanium Backup Pro reports it has superuser rights. When I try to restore an app created with the Note 4, Titanium Backup hangs forever on the "Restoring App+Data AppName n.n.nn.n" overlay with the spinning circle. TiBk is unresponsive, although Android is still running and I can see home screen or notifications. Restart is required to clear the pending action. I have run TiBk with USB debugging enabled (if that is still required), but get the same failure.
I also have MyBackup Pro. When I try to restore an apk (or apk+data), it appears to run normally. MBP reports it has superuser rights. At the end of the process the status summary says: Appname: failed: cp: can't create '/data/app/appnamestring-1/appnamestring.apk': Path does not exist.
I tried using MBP to back up an app already installed on the Pixel 3 from the store, and then restore it. It gives the same error, except the place where there is "appnamestring-1" in the Android 6 backup, there is now something like "appnamestring-2fjdk56akjfkdye7dkfja9=="
Also, I observe that the app that was installed prior to this backup restore experiment is no longer present afterward. I re-installed from the store.
Can anyone suggest next steps for solving this issue?
Click to expand...
Click to collapse
The only way that worked for me is getting my apps installed from GDrive backup (the from settings - > security - > backup or so). Actually this only restores apps from the play store.
Restore via ADB also didn't work for me...

TGHH said:
The only way that worked for me is getting my apps installed from GDrive backup (the from settings - > security - > backup or so). Actually this only restores apps from the play store.
Restore via ADB also didn't work for me...
Click to expand...
Click to collapse
Thank you for the reply! It was rather quiet around here...
But seriously, you can't restore apps? Why?? What is the issue? Why can't an app designed to backup and restore, running with superuser permissions, restore an app?

timg11 said:
Thank you for the reply! It was rather quiet around here...
But seriously, you can't restore apps? Why?? What is the issue? Why can't an app designed to backup and restore, running with superuser permissions, restore an app?
Click to expand...
Click to collapse
I found it also quite annoying! Trying to copy apps via cable seems to be only fetching a list of apps from the old phone and then re-installing them. No settings, no data. Also - obviously - only apps from play store! So unusable.
My advise - export, backup etc. all you can from your old phone for import or so.
In regards to Titanium - there's a wayto make it work. I had this once that it got stuck: in the settings there's an option to change the processing mode - see https://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-troubleshooting.html , number 29.
You will have to ACK every app to be stored but it should work.

Not sure what I did different to you but it worked for me (titanium). Maybe try restoring app only, then data only. I think I might have done a batch restore from a nandroid originally.