Develop Bugs

S-Off but not Root? Help!

i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.

djtoonjr said:
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
Click to expand...
Click to collapse
Have you tried using Rom Manager to install a recovery?

xNotta said:
Have you tried using Rom Manager to install a recovery?
Click to expand...
Click to collapse
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.

If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.

djtoonjr said:
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
Click to expand...
Click to collapse
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?

xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Click to expand...
Click to collapse
i cant get to recovery lol
i go to the bootloader, scans for a PC36IMG file but it donesnt find it, even tho the file is there! lol. maybe i shold format my sdcard. hmm.
but i scroll down to recovery, and it senss me to the default recovery, not clockwork or amen ra. the stock htc recovery. lol.

xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
Click to expand...
Click to collapse
lmfao. yeah i have S-off.

drmacinyasha said:
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
Click to expand...
Click to collapse
ive been trying dat but when it comes to the part to flash the first PC36IMG, it doesnt find it, i formatted my sdcard and trying it again.

I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.

xNotta said:
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
Click to expand...
Click to collapse
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol

djtoonjr said:
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
Click to expand...
Click to collapse
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.

t3project said:
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
Click to expand...
Click to collapse
lmfao. damn. now u tell me haha.
well i went ahead and re-rooted and got it woking now but thxs for the help.
if PC36IMG isnt getting picked up by boot loader, just format SDCARD and run it again lol

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.

Major problem with rooting

Hello All,
I followed the tutorial on how to root HTC One X with Hasoon2000's HTC One X All-In-One Toolkit.
I encountered a little problem installing CWM 5.8.2.7, so I manually installed 5.8.4 (which works great).
then I went on and did the root thing through the software.
It all seems good - I got the SU file under System/xbin, and got Superuser app on my phone. But when I try to work with things that need root, it tells me that I don't have root permissions. Even downloaded Root Checker - and it also says I don't have any.
now, when I try to install SuperSU from the recovery mode (install from zip), it tells me I can't, probably because Superuser is installed.
and ofcourse I can delete the SU file and Superuser, cause I don't have root permissions.
What can I do?
Thanks all!
P.S
I'm new to all the rooting and stuff, so go easy on me

noodlez04 said:
Hello All,
I followed the tutorial on how to root HTC One X with Hasoon2000's HTC One X All-In-One Toolkit.
I encountered a little problem installing CWM 5.8.2.7, so I manually installed 5.8.4 (which works great).
then I went on and did the root thing through the software.
It all seems good - I got the SU file under System/xbin, and got Superuser app on my phone. But when I try to work with things that need root, it tells me that I don't have root permissions. Even downloaded Root Checker - and it also says I don't have any.
now, when I try to install SuperSU from the recovery mode (install from zip), it tells me I can't, probably because Superuser is installed.
and ofcourse I can delete the SU file and Superuser, cause I don't have root permissions.
What can I do?
Thanks all!
P.S
I'm new to all the rooting and stuff, so go easy on me
Click to expand...
Click to collapse
I had the same problem after returning to stock to install OTA update, uninstall everything to do with SU then place the file below on your SD card and flash via CWM, it work for me
View attachment CWM-SuperSU-v0.96.zip

seanicca said:
I had the same problem after returning to stock to install OTA update, uninstall everything to do with SU then place the file below on your SD card and flash via CWM, it work for me
View attachment 1395633
Click to expand...
Click to collapse
How can I uninstall it if I don't have root permissions? Thanks. (I'd really appreciate a list of files and how to uninstall them )

noodlez04 said:
How can I uninstall it if I don't have root permissions? Thanks. (I'd really appreciate a list of files and how to uninstall them )
Click to expand...
Click to collapse
just transfer the file onto your phone, reboot into CWM then flash zip via CWM. reboot phone and root should be done, that's all I did

It worked! Thanks alot

Accidently flashed wrong SU binary, need help!!

My phone is a Huawei u8160 (AKA Vodafone 858) and I rooted it a long time ago with z4root and have had no problems eversince.... until recently when my mate got hold of my phone and accidently flashed an experimental/beta (possibly a binary for x86 systems) SU binary through CWM recovery. I thought I could fix this quite easily by using z4root to uninstall root and then do a fresh reinstall, but it would force close on me after a few seconds. I tried this method with both temporary and permanent root options but nothing worked. The button that pops up saying ''unroot'' wasn't there even though there is still a SU file in /system/xbin as it showed in Rom toolbox. I soon realised that the version of android i was running on my custom rom was not compatible with z4root, so i searched for how to root android version 2.3.9 pro. I dont know the name for that version and it must have been a bit of a flop because google didnt know it either. I dont know how akiro-E (the developer that cooked up the rom) got his hands on version 2.3.9 pro but i recommend to other devs reading this to not use it as there is not much compatibility.
Anyway, i found this apk made by chainsDD called gingerbreak and decided to give it a go. It said that it needed debugging on and that it might take a while, so i did that and pressed the root button. I left it to do its business, but 15 minutes later it was still trying to run the exploit so I stopped and removed it. When i got home later on i searched up how to root any phone and it came up with the pc program 'superoneclick'. I got it, opened it and clicked unroot. It did its thing but failed to remove su and the superuser app like it was meant to. So then i clicked on root and shell root but it did not reinstall properly and got the same error as in unroot error. I did all the steps multiple times but it still wouldnt remove/replace su from the xbin folder. I then reinstalled superuser 3.1.3 and tried using the binary updater on there. I noticed that the su installed was called 'legacy'. The updater was having a spaz and didnt want to update so i tried manually removing su with the root explorer in rom toolbox butvrealised that you needed root (a working one) to do that. Then i found an app on my sd called root cleaner. I tried quick and full cleaning but to no results except for a force close multiple times. I tried to fi the foce close issue by running the script for this in rom toolbox but you need root (surprise surprise) Then i tried flashing cwm recovery through fastboot as i have done lots of succesful times before. It flashed after putting my phone in download/debug mode (power and volume down) but i cant boot to it as you need proper root rights to do that.
I am going to use total commander to check if the permissions are set to 644 for the su binary, if not ill attempt to change them.
I know this a long desciption and technical question but does anyone know any ways to delete the retarded root from my phone and help me restore root as normal? This is a question for the more experienced users and devs on this forum but any help will be appreciated, cheers.

If you've got recovery, you can install one of these zips in recovery mode.
Google "superuser 3.1.3 arm signed zip" and click the first link that comes up - the androidsu one. Then download the superuser zip package that suits your device to your phones internal storage, reboot into recovery, install the zip and there you go! Your root is fixed.
Sent from my LG-E400 using xda app-developers app

Thanks
@odigITECH thanks for the help. I fixed the problem using your method. . . kind of. I flashed recovery via fastboot and then just flashed another rom from my sd card via cwm after I rebooted. Thanks for the help anyway, much appreciated!

No probs
Sent from my LG-E400 using xda app-developers app

Superuser Turned Off?

Hi
I am new to the forums. Quick question, I just rooted my Gs3 att running Android 4.4.2 with clockwork mod and odin and all that good stuff. I originally downloaded a superuser.zip file which was installed with CWM. However when I opened it up it would crash everytime. I went to drag and delete it, but i accidentally turned it off. That superuser dissapeard from my apps page. So I downloaded a different superuser.zip and did the process over again, CWM confirmed the install and I rebooted. But when I go to open superuser it isnt anywhere. I have tried looking in the application manager, and all of my files and I cannot find it! Any help?
Thanks,
-Eric