Titanium Backup not granted SuperUser permission.

jamestheartist

New Member
Joined
Dec 19, 2011
Messages
26
Reaction score
0
Hey all. Recent OTA update on RAZR left root intact but Titanium Backup denied permissions. Anyone else familiar with this issue? I uninstalled re-inatalled etc. No dice. Any ideas? Thanx!

Sent from my DROID RAZR using DroidForums
 

Kimo91

Member
Joined
Jan 15, 2011
Messages
400
Reaction score
11
Have you tried re-rooting? I've read how some people noticed after the lastest update it somehow un-rooted their phones.

Sent from my Rooted and Safestrapped Moto DROID RAZR
 
OP
jamestheartist

jamestheartist

New Member
Joined
Dec 19, 2011
Messages
26
Reaction score
0
Plus I want to get back in there and unfreeze some apps.

Sent from my DROID RAZR using DroidForums
 
OP
jamestheartist

jamestheartist

New Member
Joined
Dec 19, 2011
Messages
26
Reaction score
0
Okay. Ran Superuser but how do I tell if I have root access in there? I tried running sqlite editor as well and it wont access root either. So since it looks like Ive lost root what do I do with bionic bootstrapper if I reroot using a different method? I used zedomax and all he had at the time was the bionic bootstrapper but i want to get safestrap. Thanks guys!

Sent from my DROID RAZR using DroidForums
 
OP
jamestheartist

jamestheartist

New Member
Joined
Dec 19, 2011
Messages
26
Reaction score
0
Okay. Still had Superuser but not root go figure. Uninstalled updates to su, uninstalled bionic bootstrapper that came with zedomax method. Re-rooted using doomlord v2. Ill be danged if the phone doesnt seem to run a lil better! Next step safestrap! Thanx for the help guys!

Sent from my DROID RAZR using DroidForums
 

crackfeen

New Member
Joined
Jan 10, 2012
Messages
2
Reaction score
0
I just had the same problem where i randomly lost root.. but i can't reroot it with doomlord v2... it goes
--------------------------------------------------------------- Easy rooting toolkit (v2.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------

[*] This script will:
(1) root ur device using latest zergRush exploit (10 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)

[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush"
cannot stat 'files\zergRush': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
cannot stat 'files\busybox': No such file or directory
--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/data/local/tmp/busybox: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
cannot stat 'files\su': No such file or directory
--- correcting ownership
Unable to chmod /system/bin/su: Read-only file system
--- correcting permissions
Unable to chmod /system/bin/su: Read-only file system
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed File exists
--- pushing Superuser app
cannot stat 'files\Superuser.apk': No such file or directory
--- cleaning
rm failed for *, No such file or directory
--- rebooting


please to help!!
 

crackfeen

New Member
Joined
Jan 10, 2012
Messages
2
Reaction score
0
never mind.. i used the new doomlord root and it worked.. something must have glitched with mine... problem solved!
 
OP
jamestheartist

jamestheartist

New Member
Joined
Dec 19, 2011
Messages
26
Reaction score
0
Good for you crackfeen...yeah, I've heard of people having issues for some reason with doomlord v2, but it worked fine for me. My guess is it's a driver issue...
 
Top