• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Can't SU on ADB in Command Prompt

ndh777

Android Expert
I'm used to rooting on my Evo so this is a bit different lol

I am able to run Command Prompt on my Windows 7 computer and use ADB and successfully get root on my Evo however when I try for my dad's G1, it goes to ADB shell and has the "$" sign, but then when I try "su", it says "Access denied" or whatever it says telling me that it isn't allowing root access.

Am I doing anything wrong here? I am almost positive that the phone is rooted because I went through the process and have Amon-Ra recovery flashed but no way of really knowing whether or not I am really rooted.

I am trying to achieve root because I am trying to unlock the G1 for AT&T.
 
Okay, now this is weird. I used a differing rooting method and now it seems that it rooted except I'm still having problems such as in ADB.

First problem, Amon-Ra seems to be gone and is back to the stock recovery.

Second problem, in ADB, I type in "adb devices" and it says that there are no devices BUT when I go into ADB shell, it successfully goes in AND...there's no $ sign but a # sign. When I hook my Evo and my G1 to my computer and run ADB and try to ADB shell, it says that it can't do it because there is more than one device connected.

Really weird to me. I'm not even certain as to whether or not it is really rooted or not. I can't get a terminal app running because the only one that pops in the Market is BusyBox and it always force closes (like most downloaded apps do on open) and the Terminal Emulator app that I downloaded in .apk form won't work for it either. So I can't tell if its rooted from there either.

Anyone out there that can help??
 
Back
Top Bottom