Database Users

[Q] Rooting a rooted Verizon Droid 2 to Gingerbread 4.5.601.A955.Verizon.en.

Does GingerBreak work with this version of Gingerbread 4.5.601.A955.Verizon.en.us? My phone is currently rooted with Z4Root 1.3. Is there an easy way of doing this?
Sam

Use the d3 root method. Works fine.
CM7GB-601

The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?

acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I have the phone in PC Mode (instead of Mass Storage.) I don't know if that makes a difference.
The D3 Method worked great for me and my wife's phone.

Hi everyone,
I have the same question as CSSZiegler, but want to expand on it a little bit...
I have a Droid 2 that was rooted with Z4Root 1.3 several months ago. I also have SetCPU, SuperUser and Titanium Backup. No custom ROMs installed. Big Red just pushed down GB, and of course, I've lost root access. I'd like to regain root again without losing any contacts, Handcent messages, etc. I've read on several forums that the D2 can be rooted just like the D3 with a simple "one-click" operation referenced by quarky42 earlier.
Any opinions or experience with this? I greatly appreciate any and all assistance!

update
My phone downloads the update, I click install now... it reboots and starts the install, then about 35% of the way through, it turns to a triangle with ! Inside. Phone reboots and displays message software update failed. Anyone know where to find a logfile or have any suggestions?
Droid2 android 2.2.. rooted. No custom rom.

Did you fully SBF to stock using RSDLite?
Also http://forum.xda-developers.com/showthread.php?t=1246673 has a flashable version.

I will as soon as I get a computer again, thanks for the link. Unfortunately my mobo died yesterday. So I was hoping for an alternative solution. It would also be nice to keep all my texts.. I'll google that one.
So any ideas on the logs or an alternative solution?

Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.

Ardalee said:
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Click to expand...
Click to collapse
I answered the thread you started with the process to un root and put your phone back to stock.

acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.

808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
Awesome! That did the trick, thanks for the info

808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.

droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
I would SBF back to Froyo with RSDLite and install the OTA GB from phone info updates. After that use the D3 one click root method and you're golden.

droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.

acavallini said:
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
Click to expand...
Click to collapse
I searched the phone's sd card.. I couldn't find it... do you know where adb.exe is located?

The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.

idefiler6 said:
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
Click to expand...
Click to collapse
Finally got it to work... now.. I used motorola one click root.exe where you use the exe on the computer. Just out of curiosity, is there a one click method to unroot? Thanks!

Problem in Rooting DDJP6(after Indian official update)

Need Help for rooting my G3,
Baseband I5801 DDJP2
Kernel: 2.6.32.9
[email protected]#2
Build FROYO.DDJP6
I've rooted earlier, but since official update in India of DDJP6 all the applications which need root access have stopped working, now I'm unable to root or unroot again with superclick(2.1 and 1.7) as it doesn't detects my cell.
Help please, here a snapshot of root checker, it might help.
Superuser.apk -com.noshufou.android.su -version 3.0.6 is installed! System Environment PATH: /sbin /system/sbin / system/bin /system/xbin The adb binary is set to default shell user access as a standard non-root user Standard su binary location: ls -l /system/bin/su: /system/bin/su: No such file or directory Standard su binary location: ls -l /system/xbin/ su: /system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su: /sbin/su: No such file or directory Alternate su type binary location: ls -l /system/ xbin/sudo: /system/xbin/sudo: No such file or directory SU binary not found or not operating properly Results provided on your GT-I5801 device by Root Checker version 3.9 from joeykrim in the
Sent from my GT-I5801 using XDA App

Flash cf-root kernel and you get root instantly, no hassles

Thanks for reply, that was my first post here, will search about flashing that kernel, just got a question, will my phone application and data will get wiped out as I can't use titanium back up now(I'm new to flashing).
Sent from my GT-I5801 using XDA App

Also check if "usb debugging" is enabled, you need that root.
You can also try "z4root"

ashutoshbpl said:
Thanks for reply, that was my first post here, will search about flashing that kernel, just got a question, will my phone application and data will get wiped out as I can't use titanium back up now(I'm new to flashing).
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
No, its just a kernel, it wont wipe anything
umangsagar said:
Also check if "usb debugging" is enabled, you need that root.
You can also try "z4root"
Click to expand...
Click to collapse
z4root wont work on froyo, it uses an old exploit

Since we are talking about it, anyone has link for I5801DDJP6?
And anyone knows the changes between DDJP5 and DDJP6?

[Q] After JB update, have partial root; only for existing approved apps [SOLVED]

So I seem to be having odd rooting issues, and I can't find anything that really explains it. Apologies that some of this might be obvious...
I rooted without any issues before the Jelly Bean update. Since then, I did the Voodoo Rootkeeper, updated to Jelly Bean, and have since restored root. Everything that had root before seems to still work, however, I can't provide new root access to any applications (it doesn't even ask), SuperUser can't update the SU binary, Root Checker reports me as not rooted, but I can adb shell and do "su" and that works....and the binary is clearly there with the su bits set. And things like ES File Explorer are clearly getting root access....just not anything new. Seems like I have "partial root". Any ideas on what I need to tweak?
thanks!

You did a good job of explaining the situation. I am in the same position.

Here, more information, below. Again, looks like I have su available (/system/sbin/su), but nothing seems to work...superuser is not granting root....strange. Thoughts?
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2012-11-12 10:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your XT907 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market

I agree good job explaining. But I think a lot of us are in this situation right now. I miss the root! But also love jb (;
Sent from my XT907 using Tapatalk 2

FIXED!
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Nice,
I am going to try using SU and Superuser.apk from that site and rooting JB with those files replaced in motofail2go run.bat Think I'd still have to change permissions that way?

Not sure....I don't think so. Good luck!

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Any chance you could provide step-by-step details starting from where you pushed the files into data/local/temp?
I'm not a total novice with android but rooting is something I prefer to be very careful with! Sorry to bug you.

I had the same issue. Wiping Cache, Factory Reset, and re-root with JB exploits solved it.

I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!

RoboCuz said:
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
Click to expand...
Click to collapse
This fixed the "half-root" on my Razr Maxx HD, thanks!

Titanium backup can't get root permissions

I have the 16 gig Nexus 7 which I have rooted but having tried to backup my ROM I find I am unable to reboot into Recovery to perform a ROM backup. I also cannot flash to the latest version of Clockworkmod, I have version 6.1.0 when I am told that 6.2.3 is available. When I try to flash the download reaches 100% and says flashing before telling me an error has occurred. Also Titanium backup can't get root. Is it possible I am not fully rooted and is there a way to check? Thanks in advance.
Sent from my Nexus 7 using xda app-developers app

There is an app called "Root Checker" ... Do you have SuperUser installed and does it open?
Sent from my Nexus 7 using xda app-developers app

Yes I have superuser installed and it does open OK and does list some apps as having root permissions. I will try the checking root app and thanks.
Sent from my Nexus 7 using xda app-developers app

Just tried Root Checker and sure enough it says my device is not rooted correctly. Now to find out why with the pro version!
Sent from my Nexus 7 using xda app-developers app

Just run root checker pro and got the following output:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.99 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwxr-xr-x root shell 380532 2008-08-01 13:00 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-07-18 20:47 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Nexus 7 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn
Can somebody please tell me how to fix this

Have you tried wugfresh's root toolkit? It's easy to use. I've rooted, and reset and rerooted several Nexus 7s with it and never had a problem.
Sent from my Nexus 7 using xda premium

Why do you have 2 SU apps installed? That's probably what is messing you up.
Remove super user and re flash supersu from fastboot. The supersu flash will make it work.

[Q] F320k updated to kitkat, show rotted, but cannot access root

Hi!!
Really need a hand right here.
I have got the f320k, and it successfully updated to 4.4.
After that, I tried to root it, but it kept showing:
Mounting system RW and pushing SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
I tried couple of times, it turned out to be the same as the above.
Then I got into download mode, it shows the phone is rooted.
Does it mean that I have rooted the phone only with a shell privilege but not root?
coz in the cmd, it didnt show as # but $.
Could anyone please give me some advice?
Thank you so much!

Hey,
Have you had any luck resolving this issue i have the exact same problem when tring to root.