Please help me get root # shell

[Kamron]

Okay, noob here trying to install a custom rom. I think I thoroughly read the guides, but I'm still having difficulty at the custom recovery stage.

I have a stock Optimus S, it was V9 when I purchased it and I accepted the OTA VC. So, I used the guide to successfully revert the radio back to V9 with KP500 and the LG Support tool. No problems. I installed z4root, rooted, seemed fine. Installed superuser, seemed fine. Installed Android SDK, but I cannot seem to get a root # shell to install xionia recovery. I tried the old non-z4root method also posted by Kenny, seems fine until I'm suppose to get the root # prompt and still get the $ shell. An ideas would be appreciated. Thanks!

 

[heckja11]

Make sure to type 'su'

 

[Kamron]

"permission denied" every time. Do I not have root?

 

[Kamron]

nevermind. got it!

 

[porpherion]

Could you enlighten me as to how you got past permission denied? I'm having the same issue atm.

 

[view9234]

I'm having the same problem. I am trying to install Xionia Clockwork custom recovery, but am unable to follow the installation steps because I can't get to "root # shell" from z4root.

I am admittedly a noob...but would greatly appreciate help!

 

[sfhub]

After you permanent root with z4, make sure your phone is on and not on the lock screen.

In your adb shell, type "su" and look for a prompt on your phone asking for root privileges. Accept that prompt.

 

[view9234]

That did it--I can't believe I didn't think to unlock the screen.

THANK YOU!!!

 

[ichihollow]

make sure your phone is on and not on the lock screen.

now that this is brought up i wonder if this might have been one of the reasons i had problems rooting this last time, though when i did it back in november it was easy and had no problems. don't know or care at this point, but it's something funny to learn.

 

[dvine1]

I too used z4root (perm root) and cannot get to root in adb to install Xionia Clockwork custom recovery . system keeps saying "su is not recognized as an internal or external command"

 

[ichihollow]

I too used z4root (perm root) and cannot get to root in adb to install Xionia Clockwork custom recovery . system keeps saying "su is not recognized as an internal or external command"

can you copy your code in here so we can see what you're doing?

 

[dvine1]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>cd c:\android-sdk-windows\platform-tools

c:\android-sdk-windows\platform-tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.

c:\android-sdk-windows\platform-tools>#
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\android-sdk-windows\platform-tools>

The phone was rooted with z4root, but I cannot get the xionia recovery installed. Above is what I see when i try to access root from adb

 

[ichihollow]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>cd c:\android-sdk-windows\platform-tools

c:\android-sdk-windows\platform-tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.

c:\android-sdk-windows\platform-tools>#
'#' is not recognized as an internal or external command,
operable program or batch file.

c:\android-sdk-windows\platform-tools>

The phone was rooted with z4root, but I cannot get the xionia recovery installed. Above is what I see when i try to access root from adb

this is an easy fix, this is why we try to get people to root with adb and not with z4, if you had rooted by hand you would know you need to type in adb shell

your window should look like this

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>d:

D:\>cd android/platform-tools

D:\Android\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
#

you may get a message saying daemon was not started so it's starting the daemon now, but thats ok, what we don't want to see is

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>d:

D:\>cd android/platform-tools

D:\Android\platform-tools>adb shell
$

this means you do not have root access

on a side note, the only time you have to use the switch user command, su, is when you're trying to gain root access while in a terminal emulator on the phone itself.

EDIT: not trying to make you out to be an idiot sorry for coming across that way.

 

[dvine1]

I kinda figured it was screwed up I rooted my evo with adb when I first got it last summer. This LG is my wife's phone and I had it rooted via adb before but she downloaded a sprint update which broke root. I was trying to re-root it the easy way, but I guess I'll have to do it the old way and hope that I still remember how to do it. Thanks for your help. PS: I didn't take your comments personally, I apprecriate the help!

 

[ichihollow]

I kinda figured it was screwed up I rooted my evo with adb when I first got it last summer. This LG is my wife's phone and I had it rooted via adb before but she downloaded a sprint update which broke root. I was trying to re-root it the easy way, but I guess I'll have to do it the old way and hope that I still remember how to do it. Thanks for your help. PS: I didn't take your comments personally, I apprecriate the help!

Z4root may work on the vc and std updates but im not sure as no ones given me a straight answer yet. If not youll have to flash down to v8/v9 with kp500 to root again.

 

[drewwalton19216801]

Z4root may work on the vc and std updates but im not sure as no ones given me a straight answer yet. If not youll have to flash down to v8/v9 with kp500 to root again.

Z4root does not work on any version higher than V9. Period.

 

[sfhub]

z4root does *not* work with ZVC or ZVD.

su stands for "superuser", not "switch user"

It is not true that "su" is only used on the phone terminal.

If you are running stock recovery you will not be root when you start your adb shell session. Therefore you would type "su" to gain root privileges.

"$" means you are not *currently* root. By itself it doesn't say anything about whether you are rooted.

 

[ichihollow]

z4root does *not* work with ZVC or ZVD.

finally an answer, thank you

su stands for "superuser", not "switch user"

misconception, as you know, android is linux, in linux terminal, su is a command to switch users, ie, on my machine it would have been
> su ichihollow
password: XXXXX
$ichihollow>

however, if you just type in su you get
> su
password: XXXX
$root>

this is because linux assumes su by itself is su root, proof of this, when you enter su before super user is installed you don't get anything saying command not understood, just that permission is denied.

It is not true that "su" is only used on the phone terminal.

If you are running stock recovery you will not be root when you start your adb shell session. Therefore you would type "su" to gain root privileges.

"$" means you are not *currently* root. By itself it doesn't say anything about whether you are rooted.

i wouldn't know, i think i've always immediately installed a recovery so i'm not really sure, if i didn't it was back in november and i can't remember what did and didn't happen in a terminal then. Guess i just forgot

 

[sfhub]

Regarding su, you are correct, I was wrong to say it wasn't switch/substitute user.

However su has also been referred to as superuser in the early days:

http://en.wikipedia.org/wiki/Su_(Unix)

 

[ichihollow]

Regarding su, you are correct, I was wrong.

no need for formalities you help a lot of people on here, and you most certainly know a lot more then me about android. The only reason i know about su is it's one of the first things i learned when i first started playing with linux years back. That and yum but thats a red thing. i was playing with fedora one day went to update yum and when i went to terminal and typed su root my friend fell out laughing at me, lol, after a few minuets he finally stopped laughing and explained the su by itself thing. he's 4.5 years younger then me and i was 18 at the time so it's stuck we me since.