Root New to rooting, need some help

[rfxcasey]

Hello, I've rooted my LG Optimus Slider using the LG_Esteem root tool. After the tool finished doing its thing it said root was successful and everything seems to be working fine and I have the Superuser app installed. The problem is I am trying to shell into the phone using adb.exe from my desktop computer. I can connect to the phone typing adb shell at the command prompt and I can see all the goodies on the phone but I can't actually change anything. If I try to cd to root for instance it tells me I "can't cd to root". If I type login it tells me I need to be suid in order to. If I type in suid it tells me access denied. How can I log into my phone via the shell? Am I missing something?

 

[gbiggie]

Hello, I've rooted my LG Optimus Slider using the LG_Esteem root tool. After the tool finished doing its thing it said root was successful and everything seems to be working fine and I have the Superuser app installed. The problem is I am trying to shell into the phone using adb.exe from my desktop computer. I can connect to the phone typing adb shell at the command prompt and I can see all the goodies on the phone but I can't actually change anything. If I try to cd to root for instance it tells me I "can't cd to root". If I type login it tells me I need to be suid in order to. If I type in suid it tells me access denied. How can I log into my phone via the shell? Am I missing something?

System Variables
Right-click the

 

[rfxcasey]

System Variables
Right-click the

 

[critusodem]

SUID (Set User ID) Bit

SUID stands for Set User ID. This means that if the SUID bit is set for any application then your user ID would be set as that of the owner of application/file rather than the current user, while running that application. That means in case I have an application whose owner is ' root ' and it has its SUID bit set, then when I run this application as a normal user, that application would still run as root. Since the SUID bit tells Linux that the the User ID root is set for this application and whenever this application executes it must execute as if root was executing it (since root owns this file).

URL to source of above quote: Tips For Linux - What are the SUID, SGID and the Sticky Bits?

I had to look up what SUID does and means


If you open up Superuser, does it list your ADB app or whatever is permitted for the role of the server?

When you launch the ADB server, does it get the "<application name> has been granted Superuser"?

What happens if you try to send su?
It seems that SUID needs to be set in the first place and that suggests the thing that initializes it either did not execute or could not execute.

Hmm are there logs from the ADB server you can look at?

I ran adb.exe and the command list has this:
adb root - restarts the adbd daemon with root permissions

Any chance that could be a part of the process to resolve this?



Without more knowledge (about 3 hours of linux experience over 5 years ago haha) on these topics that is about all I come up with at the moment.

 

[AndyOpie150]

Have you tried opening up a command prompt with your phone plugged in to your PC, and then type in: adb devices
If you have ADB established in your system path correctly it will give you a number after you hit the enter key.
If not established correctly it will not find any devices. Try googling "Pre-packaged ADB Installer". Delete everything you initially installed (Android SDK, JavaSE, etc.). Make sure you delete the path to the adb.exe you put in the environmental variables. Follow the Tutorial. It has a 100% success rate.
Make sure your LG Drivers are installed properly. Turn off PC then plug in the phone and turn the PC on. You should see the Drivers detected msg.
Try opening up a command prompt in the SDK/platform-tools folder (find a spot in the folder that will allow you to right click it with out messing with the folders in it. Then select the open command prompt option. Then type in: adb shell. If you get # your good, if you got a $ type in su right after. If you still didn't get a # but got a $ your not rooted properly. Check your /system/bin and /system/xbin folders to see if you have the su in any one of those. Check the permissions and make sure it reads rwsr-sr-x or at the very least rwxr-xr-x.