[A] Titanium Backups working with Perm-Root - HTC EVO 3D

So, it seems that everything I have tried after s-OFF, installing perm-root, etc has gained root access without issue, except Titanium Backups.
it's the only thing that says it can't obtain root. just wondering if anyone else noticed this, have fixed it. etc.
UPDATE: answered by WillJitsu
I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.

I'm having the same problem. Tried everything I can think of, but no luck.

Install BusyBox

HSadler93 said:
Install BusyBox
Click to expand...
Click to collapse
I have BusyBox 1.18.4 installed in /system/xbin/

HSadler93 said:
Install BusyBox
Click to expand...
Click to collapse
Nope, Titanium backups will tell you if Busybox is installed or not and give you that option.
it doesn't even get the the point of seeing if busybox is installed or not. flat out says "NO ROOT" and that's that.
I have busybox installed.

felacio said:
Nope, Titanium backups will tell you if Busybox is installed or not and give you that option.
it doesn't even get the the point of seeing if busybox is installed or not. flat out says "NO ROOT" and that's that.
I have busybox installed.
Click to expand...
Click to collapse
I'm not trying to be a ****, but you do have Superuser installed right?

Yes. All of our other root apps work just fine. I'm blocking ads, Root Explorer works, etc. Titanium Backup is the only app that doesn't recognize root.

HSadler93 said:
Install BusyBox
Click to expand...
Click to collapse
Like WillJitsu, I also have Busybox installed in /system/xbin, and terminal can access root, and busybox functions, however TitBack says it doesn't have root.

mine works fine weird

The only thing I can think of is that one of the temp root methods I used in the past has messed something up, but I have no idea what to do to remove all remnants of that.

WillJitsu said:
The only thing I can think of is that one of the temp root methods I used in the past has messed something up, but I have no idea what to do to remove all remnants of that.
Click to expand...
Click to collapse
I would probably just wait till reliable roms release and perform a factory data reset =(
EDIT: I should probably add that I'm running 1.11 and never did any of the temp-root methods and mine is working fine after installing the latest version of SU/BusyBox

i have Superuser installed but TB wont work says no root :/

Did you upgrade the su binaries with the ones listed on the revolutionary site? I was having the same problem till I i flashed that.

I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.

WillJitsu said:
I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
Click to expand...
Click to collapse
Worked great. Thanks for tracking down the missing link.

Compusmurf said:
Worked great. Thanks for tracking down the missing link.
Click to expand...
Click to collapse
Sure thing. Glad I could help.

See PM.

WillJitsu said:
I fixed it. Here's what I had to do:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/showthread.php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
Click to expand...
Click to collapse
worked perfect !!

Related

[FIX] Titanium Backup not working after S-OFF/Root

After obtaining S-OFF and permanent root, I was still having trouble getting Titanium Backup to work.
Here's what I had to do to fix it:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/show....php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
I believe that all u need was to reinstall busybox. Which you can download in the market.
Sent from my PG86100 using Tapatalk
jzmjr said:
I believe that all u need was to reinstall busybox. Which you can download in the market.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I tried that and it did not fix it. A few people have confirmed that what I did fixed it for them. I imagine it will help some others.
jzmjr said:
I believe that all u need was to reinstall busybox. Which you can download in the market.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you believe wrong lol
Busybox dl didn't work. What's happened is one of the temp root methods put the files in a place that TB could find and they're no longer "registered" in that location. Deleting out the junk fixes the patch issues and helps most folks.
Download busybox from inside TB by pressing problems. It should fix after that.
I Haz 3D!
Worked for me Thanks WillJitsu!
Thanks WillJitSu!!!
I had been racking my brain on what I did, this fixed it!!!
knowledge561 said:
Download busybox from inside TB by pressing problems. It should fix after that.
I Haz 3D!
Click to expand...
Click to collapse
nope TB did not offer the BB download only an option to update SU .. the OP's method worked fine
I just uninstalled, reset, installed and it worked as well.
tapa tapa tapa
Thanks it works now
Sent from my PG86100 using XDA Premium App
This worked. You rock!
This worked perfectly for me. Thanks a million!
good call OP! Worked like a charm! didnt realize that stuff was still in that directory.
WillJitsu said:
After obtaining S-OFF and permanent root, I was still having trouble getting Titanium Backup to work.
Here's what I had to do to fix it:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/show....php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
Click to expand...
Click to collapse
you sir are a genius!! thanks for this, it fixed my TB issues
WillJitsu said:
After obtaining S-OFF and permanent root, I was still having trouble getting Titanium Backup to work.
Here's what I had to do to fix it:
I had used this to obtain temp root in the past: http://forum.xda-developers.com/show....php?t=1151735
Those steps had me create this directory: /data/bin/
Within that directory, I had sqlite, su, etc. so I simply deleted all the files in that folder, rebooted, and Titanium Backup now works!
I hope it helps everyone else.
Click to expand...
Click to collapse
mine working without deleting any file from /data/bin/
so wired
someone help. after doing the revolution i cant make calls recive calls send txt , internet... NOTHING
All I did was reinstall tb
Sent from my PG86100 using XDA Premium App
I am trying to install TB and rom manager, it is installed (i have a premium license also), but the apps are telling me that im not rooted. I know i have s-off, and i though i was permanently rooted.
I tried to install the SU app, but it tells me that i need to flash the su,zip file and clockwork wont let me install it.
my bad, found the answer here...
This method fixed it up perfectly for me too. Thanks!

[Q] titanium back up won't aquire root, I'm rooted.

Although I have superuser operating fine with terminal emulator, and when I type SU into terminal it gives me "#" sign, Titanium Backup won't acquire root. Does anyone have any ideas?
Edit: I've tried reinstalling TB and seeing if it's upgraded/patched.
Edit2: I've installed busybox and made sure SU is updated. TB still won't find root even though it says i'm rooted in TB.
toneman1984 said:
Although I have superuser operating fine with terminal emulator, and when I type SU into terminal it gives me "#" sign, Titanium Backup won't acquire root. Does anyone have any ideas?
Edit: I've tried reinstalling TB and seeing if it's upgraded/patched.
Click to expand...
Click to collapse
Busybox installed? Update your Su?
Sent from my PG86100 using Tapatalk
aray92 said:
Busybox installed? Update your Su?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
How do you do those things?
toneman1984 said:
How do you do those things?
Click to expand...
Click to collapse
Market search for both. Then go into superuser and update binary
Sent from my PG86100 using Tapatalk
aray92 said:
Market search for both. Then go into superuser and update binary
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
super user is fully updated. Busy box is installed and still titanium back says there is a problem with root, even though it says that i'm rooted in TB.
toneman1984 said:
Although I have superuser operating fine with terminal emulator, and when I type SU into terminal it gives me "#" sign, Titanium Backup won't acquire root. Does anyone have any ideas?
Edit: I've tried reinstalling TB and seeing if it's upgraded/patched.
Click to expand...
Click to collapse
Use es file explorer from the market.go into settings and check box to show hidden files then look in /data/bin/ delete any files in that folder then reboot and TB should be fine.
pittn8ve said:
Use es file explorer from the market.go into settings and check box to show hidden files then look in /data/bin/ delete any files in that folder then reboot and TB should be fine.
Click to expand...
Click to collapse
There is nothing in /data/ ...hmmm
toneman1984 said:
There is nothing in /data/ ...hmmm
Click to expand...
Click to collapse
did you check the show hidden files box? after you do close es file explorer then reopen and check.
pittn8ve said:
did you check the show hidden files box? after you do close es file explorer then reopen and check.
Click to expand...
Click to collapse
Thankyou. I checked show hidden files. Still didn't see anything. Than I checked "root explorer" and "mount system files". Than I found data/bin and deleted everything in side. Rebooting now.
toneman1984 said:
Thankyou. I checked show hidden files. Still didn't see anything. Than I checked "root explorer" and "mount system files". Than I found data/bin and deleted everything in side. Rebooting now.
Click to expand...
Click to collapse
sweet, hope it works did for me! let me know.
That worked. Thank-you everyone!
i had the same problem. uninstalling tb and reinstalling fixed for me.
wizsenseisablur said:
i had the same problem. uninstalling tb and reinstalling fixed for me.
Click to expand...
Click to collapse
I tried uninstall and reinstall, that didn't work. I'm trying the /data/bin delete now.
pittn8ve said:
Use es file explorer from the market.go into settings and check box to show hidden files then look in /data/bin/ delete any files in that folder then reboot and TB should be fine.
Click to expand...
Click to collapse
This works!
Another way to fix it is to clear data. Go to settings-applications-titanium backup and press clear data.
toneman1984 said:
Thankyou. I checked show hidden files. Still didn't see anything. Than I checked "root explorer" and "mount system files".
Click to expand...
Click to collapse
Did this but still no file /data /bin

[SOLVED] Titanium backup problems on the Mediapad

I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
nightanole said:
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
Click to expand...
Click to collapse
I don't have to run ROOT CHECKER because i have already other root apps and they function flawlessly (SD maid, quick boot, Busybox installer...) but i run the ROOT CHECKER anyway and it says i do have root privileges.
i forgot to mention that i already used Titanium B to backup apps and data, everything was stored on the external sd card. i could also restore. after all this app is for all android devices.
hamdimo said:
I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
Click to expand...
Click to collapse
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Stransky said:
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Click to expand...
Click to collapse
that's what makes the app perfect, BACKUP and RESTORE between different android devices.
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
{SOLVED}
ferdz33 said:
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
Click to expand...
Click to collapse
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaries are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
hamdimo said:
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaried are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
Click to expand...
Click to collapse
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
ferdz33 said:
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
Click to expand...
Click to collapse
I fear that my hack could led to believe that searching for the "su" binary only in predefined positions is a good thing ...
I still believe applications should gather the correct informations from the PATH environment variable, as good ol' *NIX does.
But as you said it's kind of addressed, let's hope the hack will have a story
These problems arise only if one updates the "Superuser" application past the 3.0.7 (with "su" binary 3.0.3.2).
That one version is the latest one working as expected.
And yes I am a bit sceptical about my own choice of including 3.1.3 instead of the 3.0.7 in my latest update.
The "su" binary executable alone has grown from a mere 22Kb to 380Kb and "apk" has doubled it's size too (1.5Mb).
Related to these changes in "Superuser" several applications does not work any more for many users and upgrades are needed.
The process of getting "root" privileges for any application has turned tremendously slow. From almost immediate to 2/3 secs. each time.
this solution worked for me
Since superuser is working and granting root permissions to other apps (except TB). Using root explorer, I tried renaming the original su file from /system/bin/su and replacing it (copy-paste) with the su file from /system/xbin
Reloaded TB and it worked =)
Actually i have no problem in my 1st install for titanium backup. but soe how i uninstall accidentally. when i reinstall, it prompt memory not enough but i hve abt 3.5 gb left. my fone is rooted S3. can anybody help. tks in advanced...

[Q] My phone semi-died after using calculator... not funny.

Hi,
As you can see on my signature, i'm using an official ICS ROM without modifications as my daily drive... and was using it without problems util today.
I was on my math class using the calculator and suddently my phone freezed. I rebooted it several times without success... sometime after it starts (i can see the home screen and launch apps, or push notification bar) ... it freezes again.
There is anything that i can do to recovery or see what is doing this? I can access the phone via adb shell... i doesn't want to flash my cellphone again and configure everything... and yes, i have titanium backup but i was waiting my feel to flash JB again to make a backup... :cyclops:
If anyone can guide me to trace what is making my phone freeze, i'll be greateful.
SkzBR said:
Hi,
As you can see on my signature, i'm using an official ICS ROM without modifications as my daily drive... and was using it without problems util today.
I was on my math class using the calculator and suddently my phone freezed. I rebooted it several times without success... sometime after it starts (i can see the home screen and launch apps, or push notification bar) ... it freezes again.
There is anything that i can do to recovery or see what is doing this? I can access the phone via adb shell... i doesn't want to flash my cellphone again and configure everything... and yes, i have titanium backup but i was waiting my feel to flash JB again to make a backup... :cyclops:
If anyone can guide me to trace what is making my phone freeze, i'll be greateful.
Click to expand...
Click to collapse
If you have made adjustments to build.prop or init.d scripts i would suggest to remove the ones you're not sure they work ok...
I didn't changed nothing, i was just using it as a normal user does! Maybe is a divine call to me flash JB again... but i'll wait to debug this error and trace what app or service is breaking me.
Have you fully wiped between your flashes?
From android 4.1 for example to 4.0.4..?
Yes, i did a full wipe when i rolled back to 4.0.4...
If you're running 4.0.4 can you upload your build.prop or init.d? I'm using samsung stock rom, not a custom one.
Thanks for your enforces to help!
Yes mate,gimme 2 minutes...
I'm on LH3 but it should do just fine...
By the way remember to wipe cache and dalvik after you push the files and also delete the init.d folder and delete your build.prop!
There you go!
I'm using these setting for 2 weeks now they seem stable and quite fast...
Do let me know if this worked or not!
Hi,
Thanks for your help, i tried to put your build.prop and didn't resolved, BUT, i managed to see something...
My SuperUser (su) was broken... i tried to execute "su" into adb shell and frozen my shell, so i did remount my system and copy my su again to /system/bin/su.
Time to take a full backup with Titanium!
Thanks for your help!
Edit:
What's the correct permission to su? 0755? I did it and i still without superuser now... i need it to use titanium but for now, freeze was gone!
SkzBR said:
Hi,
Thanks for your help, i tried to put your build.prop and didn't resolved, BUT, i managed to see something...
My SuperUser (su) was broken... i tried to execute "su" into adb shell and frozen my shell, so i did remount my system and copy my su again to /system/bin/su.
Time to take a full backup with Titanium!
Thanks for your help!
Edit:
What's the correct permission to su? 0755? I did it and i still without superuser now... i need it to use titanium but for now, freeze was gone!
Click to expand...
Click to collapse
No problem mate!
Glad to see you found the issue!
EDIT:If you have cwm try to flash this!
http://forum.xda-developers.com/showthread.php?t=1538053
been using it since forever...it's very good...
Also take a look at this!
http://forum.xda-developers.com/showthread.php?t=750806
Boot into safe mode.. Uninstall supersu.. Then reboot.. Root again
You have been zooo==>ted
nfsmw_gr said:
No problem mate!
Glad to see you found the issue!
EDIT:If you have cwm try to flash this!
http://forum.xda-developers.com/showthread.php?t=1538053
been using it since forever...it's very good...
Also take a look at this!
http://forum.xda-developers.com/showthread.php?t=750806
Click to expand...
Click to collapse
Removed root with toolkit 5.0 and installed SuperSU, everything seems fine now.
Thanks all!

[Q] Titanium Backup

Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
I have the same problem. Initially, I thought that the sdcards were not mounted (for su root) but that wasn't the issue.
TB will currently backup VIRTUAL items (e.g. Accounts, WiFi access points) which have the TB logo next to it. It seems to fail for all other items.
gale2000 said:
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
Click to expand...
Click to collapse
Same problem here. According to this post:
http://forum.xda-developers.com/showthread.php?t=2391363&page=7
the small app called sdfix could solve the problem. I haven't tried yet.
cr2069 said:
Same problem here. According to this post: http://forum.xda-developers.com/showthread.php?t=2391363&page=7 the small app called sdfix could solve the problem. I haven't tried yet.
Click to expand...
Click to collapse
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Anybody have luck with Helium?
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
iammudd said:
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Click to expand...
Click to collapse
Too bad, seems to be TB's problem. Waiting for any progress...The main reason I want rooting is to use TB, but it's not working...
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/ascend-mate2/orig-development/2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
iammudd said:
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
foltz61 said:
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Yes, fastboot boot TWRP_MT2-L03_RECOVERY.img allowed me to try it out first. If it had failed, then hopefully I would still have had the stock recovery. (After playing around with TWRP a bit, I DID eventually flash it.)
foltz61 said:
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
iammudd said:
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
Click to expand...
Click to collapse
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
Click to expand...
Click to collapse
Same problem and this also fixed it for me thanks
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
Click to expand...
Click to collapse
This workaround has been made obsolete. See next post:
I didn't know what the drawbacks are to using this folder so I was initially reluctant but I've given up and went down this path as well. However, I've reduced some permissions and here's what appears to be working for me:
Use ES Explorer to create the new folder and change its permissions to rwx for group and others. (I didn't need to change owners for any of the folders.)
Use ES Explorer to TEMPORARILY add read-only permission to /data for OTHERS.
Change TiBu backup folder location by manually navigating to the new folder.
Once the new folder has been selected, I restore /data to its original permissions. (The read permission was only needed temporarily for TiBu to find the new folder.)
Copying the files back to my PC, I can see that the zip files for the apks appear to have "reasonable" apk sizes (i.e. not zero-length as before).
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
kemonine96 said:
In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Click to expand...
Click to collapse
Thanks, this appears to have done the trick. It was very baffling when TiBu would work for some tasks but not others. Glad you stumbled onto this thread.
And another follow up for those using Helium or looking for an "adb backup" based solution
This device does not appear to include the full adb backup stack. From some limited testing tonight the pop-up prompt when running "adb backup' or using Helium Backup does not produce prompt on the device so it just fails. This is a known problem on some devices and it's too bad Huawei decided this wasn't a necessary inclusion.
kemonine96 said:
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
Click to expand...
Click to collapse
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
nrfitchett4 said:
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
Click to expand...
Click to collapse
Were you able to get adb backup to work at all? I never was able to get it to work.
I solved my titanium backup issues by going into SuperSU, then settings for SuperSU, and unchecked the mount namespace seperation box, then reboot
kemonine96 said:
Were you able to get adb backup to work at all? I never was able to get it to work.
Click to expand...
Click to collapse
It worked just fine for me. Used it to backup kids unrooted phones. That's been a couple years though.

Categories

Resources