Develop Bugs

[Q] where'd my su go? [solved]

So heres the details. Did the unrevoked flash. Got superuser. Successful root, but wanted to flash CM6. Downloaded via Rom manager, when to reflash and got stuck in boot loader loop. Dragged and dropped eng boot loader package onto SD card from different thread (seen here: http://forum.xda-developers.com/showthread.php?t=752832). Now superuser is missing. Also, every time I reboot it reloads image from zip. Should I just remove zip from SD? Why did superuser disappear? S-off is still there. h-boot: 0.76.? Thanks for your help in advance!

Try downloading it from the market.
Sent from my PC36100 using XDA App

lol, did that, and none of my rooted apps recognize it. Rom manager said I need one in system/bin/su I tried to move via astro and root explorer but neither would let me saying it needed to be a read only file.

Remove the ZIP from your SD card, get ChainsDD's Superuser from the Market. Problem solved.

Thats the one I downloaded, however rom manager says I am not rooted and it cannot find file in system/bin/su or system/xbin/su

FIXED!!
Lol, apparently downloading from the market was the older version. I went ahead and downloaded zip file from dev original thread here:
http://forum.xda-developers.com/showthread.php?t=682828
flashed in recovery and presto chango I have my SU back.. Thanks guys!

where'd my su go?
This was ugly dude, good job on the recovery, sheez.

CWM is not working properly (LTE)

I am having an issue with cwm. when I go into rom manager i was able to succesfully flash it to my phone. Now when i reboot into recovery I get the android guy with a red exclamation point. sometimes I can get in but I cant reboot my phone from the menu and have to do a battery pull. I am able to flash .zip's and update the bootanimation for example if i get in. When I reboot from rom manager I get some error message that is stopped working before it reboots and again sometimes it works sometimes it doesnt.

should I push the recovery through the sdk again?

Yes, you should. I read that sometimes CWM won't stick if applied through ROM Manager.

There is a file on the nexus s and i believe the Gnex as well that will rewrite the stock recovery after a reboot. unless you change this file you have to flash the recovery every time you want to go into it. use a file manager and search for install-recovery i believe its install-recovery.sh and rename it to install-recovery.sh.bak ( or wtv ) may solve it.

I just did a quick search in root explorer and found a file called "install-recovery.sh"
it should be in the root folder/etc/install-recovery.sh
and i just tried going into CWM and got the same thing as the OP. I am going to rename the "Install-recovery.sh" file like Goat_For_sale suggested, then reinstall CWM and see what happens after a few reboots.
Standby.
*final* edit
So here is what I did.
1.renamed "install-recovery.sh" to "install-recovery.sh.bak" (located in the "etc" folder of the root) I used root explorer. Make sure you mount as writeable or else you cant change the file name.
2. rebooted phone as normal. went into Rom Manager and reinstalled CWM.
3. turned phone off, and booted into recovery and boom! CWM came up nicely.
Glad I found this thread, or I would have been annoyed when I go to flash a rom tonight and couldnt figure out why I wasnt able to get into CWM.
Good luck OP.

I hope you were able to resolve this issue. I was having the exact same issue and i followed the instructions in this thread and it corrected it and i havent had a problem since.
http://forum.xda-developers.com/showthread.php?t=1392336

Now cwm seems to be working but when I hit to boot into recovery from rom manger it says that something has stopped working unexpectally but it seems to boot into recovery just fine.

If you follow the steps on the link that i posted, and make sure that you follow the step of deleting the file with Root Manager once you have moutned as RW then that should get you working. If you are still having issues with I would be happy to walk you through the process tonight over google talk once i get off of work.

Thanks Angelino I will try that today. I just havent deleted that file yet. Now since im rooted and already flashed cwm, i should just go into root manager delete the file and then do the fastboot and flash the recovery again?

TSanborn79 said:
Thanks Angelino I will try that today. I just havent deleted that file yet. Now since im rooted and already flashed cwm, i should just go into root manager delete the file and then do the fastboot and flash the recovery again?
Click to expand...
Click to collapse
dude try my method, it was super easy, and doesnt require deleting anything, just renaming that file.

threepio said:
dude try my method, it was super easy, and doesnt require deleting anything, just renaming that file.
Click to expand...
Click to collapse
I did try your method but it only partially works. I still get an error when trying to boot from rom manager.

It actually says superuser has stop working. Finally was able to read it.

I am having issues with my gnex and recovery. I am rooted and can run clockwork when I boot from the app. However when I run root explorer i can find any of the recovery files to delete or rename. They arent showing up in system or etc but when i restart my phone stock recovery is still there... ideas?

TSanborn79 said:
I did try your method but it only partially works. I still get an error when trying to boot from rom manager.
Click to expand...
Click to collapse
wierd. I havent had a problem yet. Hope u get it figured out.

[Q] I have superuser installed on android 4.0.4 but I still can't get root access?

I rooted my phone at 4.0.2, then applied the update up to 4.0.4 and am still able to flash new versions of clockwork mod through rom manager... However, all my other apps won't be granted root access. In the superuser application, I'm running superuser v3.0.7(41) and my Su binary is at v3.0.3, for which there is an update available. However, when I try to apply the update, it tries to ask for root privileges and gets denied access... I tried reflashing su.zip through clockwork mod touch but I guess I may be flashing an outdated su.zip? Any insight into the matter would be greatly appreciated!

Same here
Same exact scenario, I went from 4.0.2 to 4.0.4, and even after a factory restore I cant seem to get root access for any app. I checked the bootloader, and I still am rooted.
Help appreciated for us both!

try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.

ezcats said:
try this zip...flash in recovery
http://www.box.com/s/jvcf196j7x8f8vrc9cyt
this worked for me....
if it doesn't clear superuser data first then try it again.
Click to expand...
Click to collapse
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.

Clockwork recovery does not require root if it is already installed. If not, fastboot clockwork recovery.

I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it

evanextreme said:
CWM Recovery is not working for me, and I cant flash it due to no permission for elevated commands although its rooted.
Click to expand...
Click to collapse
Flash from recovery, not an app.....
Sent from my Galaxy Nexus using xda premium

jerseyh22accord said:
I had the same issue and all you have to do is reroot the phone and all will be well then download and install ota rootkeeper for the future. The update breaks root but doesn't block it
Click to expand...
Click to collapse
This did the trick!
Had this same problem earlier

I need help
I am having the same problem. I am a noob and it sucks cause I can't figure it out. I can't even go into recovery since I installed 4.0.4 someone please dumb it down so i can understand

Install busybox free, then install titanium backup free. Open busybox and click inatall. Then run
Titanium backup, it will ask you do you want it to configure root, accept this. please note After completing busybox steps reboot. Then after titanium backup steps reboot again
Did this help?
If not pm me and il see if i can help

I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA

brightsideme said:
I can't use any of my root apps. My SU isn't working. I'm pretty sure that's causing the problem. I tried updating the binary (I read that somewhere) but the process fails. Is there a way I can do it manually?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Try flashing this:
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip

Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA

brightsideme said:
Can you please explain how to flash? I don't want to mess it up lol
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Do you have CWM installed yet?
If not...
I'd recommend simply starting from the top and using my guide.
But if you have CWM:
Just navigate to "Install Zip From SD Card"
"Choose Zip"
And find it.
Yes to install.

I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA

brightsideme said:
I tried going to clockworkmod recovery but I just get that error. Last night I went into recovery using the cmd on my computer. I tried flashing that same file but it just failed.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
boot to clockworkmod manually, than flash the superuser zip from here http://www.box.com/s/jvcf196j7x8f8vrc9cyt (this does not require busybox, that why the other su zip was failing)

I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA

brightsideme said:
I can't go to recovery from my phone. When I try I just get the Droid with a red exclamation point. I'll have to do it from a computer. Only problem is that I'm at work. I'll see if I can get to one ASAP
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.

Jubakuba said:
That is the stock recovery that you're getting to.
Use my guide.
And navigate to the part about flashing a custom (CWM) recovery and flashing SU.
The SU in my post is updated to work for all users...the one you're using won't work on 4.0.4.
Click to expand...
Click to collapse
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox

andQlimax said:
but i think the su zip in ur post, only work if there is busybox installed...and the stock rom doesn't have it...
this the updater-script of ur su.zip: run_program("/sbin/busybox"...
that work only on custom roms, that usually have busybox preinstalled
check the different syntax in the other su zip posted above, it doesn't require busybox
Click to expand...
Click to collapse
nope, he was getting a permissions error because rom manager didn't have root access, that was the issue there.
edit: re-read the post, yes, you might be right about busybox in stock recovery, although i believe cwm has a set of minimal busybox tools.
if manually booting into recovery by shutting down the phone, pressing power+vol up until Google screen appears, doesn't take him to cwm but to stock recovery, he doesn't even have cwm installed, which could very well be the case, since stock rom default behaviour overrides any existing recovery when flashing.

[Q] Seriously cannot root my EVO 4g

Hey Guys. I've been trying to root my Evo 4g for over a year and I am either messing up horribly or my EVO is just unrootable. I attempted flash/root it with revolutionary, but all I have is S-OFF.
The H-Boot Screen reads:
-Revolutionary-
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
MAR 8 2011, 17:02:15
I really hope I can get some help, I've wanted this badly for over a year.
If you need any other information, please just ask.

Dude! You are already rooted! Revolutionary flashes a recovery for you, so all you need to do is flash a rom if you want.
Hit the thanks button if i have helped you in any way today !

+1 The Revolutionary tag means your bootloaded is unlocked and you have s off. Your good to go. Just do a Nandroid Backup. And then flash away.

But when I try to flash a rom over, it never works. Not even superuser works. I downloaded Terminal Emulator and typed su, but it doesnt do anything.

Yunq Millz said:
But when I try to flash a rom over, it never works. Not even superuser works. I downloaded Terminal Emulator and typed su, but it doesnt do anything.
Click to expand...
Click to collapse
Do u have a custom recovery?
Sent from my PC36100 using xda premium

First, you probably need a custom recovery. Search for "amon ra evo" or "clockwork mod evo" follow the instructions on their page and that will get you a custom recovery. Do a "nandroid backup" so you have a backup of your original os
Second, look up SU evo, download the zip, and flash that in your recovery. That will give you su.
PS if you don't understand any or all of these terms, look up xda rooting for dummies
Sent from my PC36100 using xda premium

I tried all the steps on the recoveries, and they are all saying that I do not have access to superuser. Terminal emulator does not respond positive to su either.

Yunq Millz said:
I tried all the steps on the recoveries, and they are all saying that I do not have access to superuser. Terminal emulator does not respond positive to su either.
Click to expand...
Click to collapse
You flashed the superuser zip in recovery right?

klharalson said:
You flashed the superuser zip in recovery right?
Click to expand...
Click to collapse
I've tried, but with no success.

Yunq Millz said:
I've tried, but with no success.
Click to expand...
Click to collapse
what does it say when you flash it? Successful, errors??

klharalson said:
what does it say when you flash it? Successful, errors??
Click to expand...
Click to collapse
It doesn't even recognize the file.

klharalson said:
what does it say when you flash it? Successful, errors??
Click to expand...
Click to collapse
Maybe a bad download, try this one...this is the one that I have used successfully...also, what recovery are you using right now? I have had issues with clockworkmod on occassion that has aborted installation of zips...
superuser http://dl.dropbox.com/u/30295084/CM9/Superuser-3.0.7-efghi-signed.zip
amon ra recovery that you flash through bootloader, just rename zip to PC36IMG http://dl.dropbox.com/u/30295084/CM9/PC36IMG_ra-supersonic-4.3-smelkus-ics.zip
So try recovery first, then try flashing the superuser zip I linked above and see where that gets you.

klharalson said:
Maybe a bad download, try this one...this is the one that I have used successfully...also, what recovery are you using right now? I have had issues with clockworkmod on occassion that has aborted installation of zips...
superuser http://dl.dropbox.com/u/30295084/CM9/Superuser-3.0.7-efghi-signed.zip
amon ra recovery that you flash through bootloader, just rename zip to PC36IMG http://dl.dropbox.com/u/30295084/CM9/PC36IMG_ra-supersonic-4.3-smelkus-ics.zip
So try recovery first, then try flashing the superuser zip I linked above and see where that gets you.
Click to expand...
Click to collapse
It says no image or wrong image.

Yunq Millz said:
It says no image or wrong image.
Click to expand...
Click to collapse
ok, so it doesn't then say checking PC36IMG.zip?
edit: did you make sure to not put the zip in a folder on your sd card? it has to be on the root of your sdcard to be found.

klharalson said:
ok, so it doesn't then say checking PC36IMG.zip?
edit: did you make sure to not put the zip in a folder on your sd card? it has to be on the root of your sdcard to be found.
Click to expand...
Click to collapse
I made sure I put it in the root, its not in any folder. The bootloader does say checking for PC36IMG.zip, but it can't find it. And I am 100% sure it is spelled correctly.

Yunq Millz said:
I made sure I put it in the root, its not in any folder. The bootloader does say checking for PC36IMG.zip, but it can't find it. And I am 100% sure it is spelled correctly.
Click to expand...
Click to collapse
Either open up a file manager on your phone or mount to computer to look at the name if you added zip, delete that...I am stumped as to what else the issue would be...
This might be overkill, but you might want to ruu back to stock...redo revolutioanry and after you type yes download clockworkmod recovery in revolutioanry...boot into recovery, flash superuser zip and then boot the phone...it should work for you, but also should be working now.

klharalson said:
Either open up a file manager on your phone or mount to computer to look at the name if you added zip, delete that...I am stumped as to what else the issue would be...
This might be overkill, but you might want to ruu back to stock...redo revolutioanry and after you type yes download clockworkmod recovery in revolutioanry...boot into recovery, flash superuser zip and then boot the phone...it should work for you, but also should be working now.
Click to expand...
Click to collapse
I am ruu back to stock right now. I will tell you if I can reroot it. Btw, should I use revolutionary or unrevoked?

Yunq Millz said:
I am ruu back to stock right now. I will tell you if I can reroot it. Btw, should I use revolutionary or unrevoked?
Click to expand...
Click to collapse
I have always used revolutionary, thats not to say the other isn't good, just never used it.

Thank you so much. I restored it to 2.2 with the ruu. My phone was still S-off, but the recovery finally flash. Checked the terminal emulator and I am granted Superuser permissions. I can not thank you enough.

Yunq Millz said:
Thank you so much. I restored it to 2.2 with the ruu. My phone was still S-off, but the recovery finally flash. Checked the terminal emulator and I am granted Superuser permissions. I can not thank you enough.
Click to expand...
Click to collapse
its no problem...glad you were able to get it working finally

[Q] Rooting Help (firewater, adb, and Rum runner)

I'm trying to root my phone to install CM 10.2. I've been searching for a few hours and am getting more and more frustrated. I've read that Firewater is the easiest way to unlock the bootloader on my phone. I've downloaded Firewater, but I don't know what to do with it. Its just a file called "Firewater" with no extension. I don't know how to run it.
I've also tried RumRunner, and have had no success.
I'm not sure what ADB and Fastboot are, but I think I have some ADB stuff installed on my comp [ C:\Program Files (x86)\Minimal ADB and Fastboot ] and I have that path in my Environment Variables>path directory. I don't know what to do with it.
Please help me get started. Step by step instructions would be great. I saw a thread that isn't very old where someone was having root trouble w/ KitKat but they were able to run Firewater. I need help getting that started at least. Thank you.
Edit: Fastboot is Off
USB Debugging Enabled
HTC Sync (can't find it anywhere on my comp, or in the programs list ((control panel)) so I assume its not installed)
Drivers are installed on my comp.

I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.

Pharva said:
I've downloaded an ADB toolkit, and have it pathed. I opened the command prompt and ran "adb devices" to check. My phone showed up with no problem.
I then moved firewater to the current directory cmd was using c:\Users\MYNAME.
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
after this it displays:
127:[email protected]:/ $
I entered "su"
/system/bin/sh: su: not found
Could anyone explain what I'm doing exactly by following these directions, and explain what I can do next to correct the problem?
Edit: su means Super User, correct? I've tried installing SuperSU, but It says that there is no SU binary installed. I haven't found out how to install the binary.
Click to expand...
Click to collapse
you need temp root... goto http://firewater-soff.com/ everything is right there. If you have kitkat from the OTA the other day, i dont believe it works on kitkat yet.

Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?

Pharva said:
Thanks. I've read that temproot doesn't work on KitKat either. For now, it would seem that my only option is to wait, right?
Click to expand...
Click to collapse
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!

S-Off not working
nty123 said:
Yes you are correct temp root method does not work for the newest OTA update and unfortunately there is no method for the CDMA version of the htc one so hopefully we will see a new method soon!
Click to expand...
Click to collapse
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?

payrovi2 said:
I am having this problem also. I am trying to s-off with firewater and can't get past the SU also...it tells me SU can't be found.
Debugging enabled
Developer Mode enabled
Network band set to LTE/CDMA
No passcode or other security lock
My Fastboot and ADB are working fine. I am able to run the Temproot instructions, but it stops at SU. WHY?
Click to expand...
Click to collapse
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.

nty123 said:
just what the above post's stated, you need temp-root to, along with firewater. and if you are on the newest ota (kitkat 4.4.2) then you have no other choice but to wait. that mean's no downgrading either.
Click to expand...
Click to collapse
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.

payrovi2 said:
Thanks. Yes, I was able to temproot and firewater and get s-off.
I'm trying to load Cyanogenmod for my HTC One Verizon ( cm-10.2.0-RC1-m7vzw.zip ) through clockworkmod recovery 6.0.4.7
When I wiped the data/factory reset...it seemed to get stuck for >20minutes. I powered down and up...and it looked like some partial factory reset had happened.
I went ahead with the cyanogenmod zip update, through cwm recovery, and it seems to be stuck at Installing Update. Nothing is happening or moving.
Any thoughts?
Thanks for all the developer help.
Click to expand...
Click to collapse
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed

nty123 said:
can you power off device and boot into recovery? (not sure what the problem is yet but you could try using a different recovery, twrp instead of cwm. before you try out twrp (if you do) make sure you have the latest version of cwm installed
Click to expand...
Click to collapse
I can boot into recovery, but can't boot the phone up.

payrovi2 said:
I can boot into recovery, but can't boot the phone up.
Click to expand...
Click to collapse
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.

nty123 said:
ok, what i would try is backup to the rom you have before you tried installing CM( only if you made a backup). if you didn't then i would try clearing all data and that rom and try installing a different one, maybe the one you have has a bug and is not working properly.
Click to expand...
Click to collapse
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.

payrovi2 said:
It kept getting stuck at "installing update" no matter whether it was a previous rom or the Cyanogenmod rom. I tried it numerous times...and then finally once it said "...update complete"
I'm rebooting and loading cyanogenmod now...hope that it moves past this CM boot screen.
Click to expand...
Click to collapse
Nope. still stuck at this boot loop.
Any ideas?

payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
try restoring from you backup again but this time wipe all your data and factory reset before yo restore

payrovi2 said:
Nope. still stuck at this boot loop.
Any ideas?
Click to expand...
Click to collapse
I would do a decrypted RUU at this point, it will at least get you back on a sense rom (as long as you download the decrypted one, it wont break your SOFF and bootloader unlock). then from there i would reinstall PHILZ or TWRP, then make sure the MD5 is right on the rom you want to install