How do I confirm if my phone is successfully rooted...


  1. dsphoto

    dsphoto Member

    I'm a bit of a wanna be geek here so forgive me if this is obvious. I just followed the sticky instructions for going from 1.5 to 2.1 root on the Eris. I'm not confident that I did it correctly though. I am wondering if by accident I just simply upgraded my operating system to 2.1 instead. Is there any way I can tell by looking at the "about phone" information if my phone was for sure successfully rooted or not? Thank you for your help.

    Advertisement
  2. mobil3gen

    mobil3gen Well-Known Member

    Which 2.1 file did you use - the file you moved to your sd card?

    Read off the info on the about section in settings - if you are on the same one I'm using - quick indicator is that you'll see the HTC quietly brilliant logo at start up.

    Also your Android Market will look different than it did before.
  3. dracozny

    dracozny Well-Known Member

    plus if you open "adb shell" in your command prompt and type "su" a window will pop up on your phone asking if its ok click allow and then in your command prompt will change from $ to #
  4. GrdLock

    GrdLock Well-Known Member

    If he's using the original ROM image and not a newer custom ROM, it will drop him into a root (#) shell as soon as he does "adb shell", in that one you don't have to su.

    But for the OP, yes, like dracozny said, type "adb shell" in your command prompt (while in your tools directory of course).

    If you have a $ prompt, try typing "su" enter. If you see a # prompt, you're rooted.
  5. dsphoto

    dsphoto Member

    Thanks guys. I tried connecting the Eris to my PC and doing the command prompt "adb shell" and it says the device can't be found. I've made sure USB debugging is on and the phone is in charging mode.

    I looked in the device manager and it shows an adb device with the yellow exclamation mark. I installed the drivers before when I was doing the 1.5 to 2.1 root tutorial and it seemed to be successful so I don't know why its saying it needs a driver now.

    I've attached an image of my phones software information. Maybe you guys can tell whats going on?

    [​IMG]
  6. GrdLock

    GrdLock Well-Known Member

    You're running the new kernel that changes the devices hardware id's.

    Download android_winusb.zip from Sendspace.com - send big files the easy way

    Download that .inf file and replace the one that's in your USB Drivers folder of the SDK with that it.

    Then reinstall the driver in Device Manager using that .inf file.
  7. dsphoto

    dsphoto Member

    Thanks so much. I got the driver installed successfully.

    Now...back to the command prompt.

    after typing "adb shell" an $ appears.

    Then after typing su, I have a blinking curser below it. No # to be seen.

    Did I just upgrade to the unrooted 2.1? If so, its not the end of the world...it just means I don't get to play.
  8. Murphy

    Murphy Well-Known Member

    Check to make sure that USB Debugging has been turned on.
  9. GrdLock

    GrdLock Well-Known Member

    Look on your phone to see if you get a popup that says Superuser Permissions after you type "su"

    Or better yet, since you're using that kernel, did you ever install Amon's recovery partition? If not, you installed a non-root rom, because in order to get that kernel you have to install a rom using the recovery partition. In that case, you don't have root and you don't be able to get it for now until 2.1 is rooted.
  10. dsphoto

    dsphoto Member

    Ok...I looked at the phone and saw the sp permissions screen with several buttons to allow, always allow...etc. I hit always allow.

    Now the # comes up in the command prompt. Can I play now!?
  11. GrdLock

    GrdLock Well-Known Member

    Ya you're good. :)
  12. dsphoto

    dsphoto Member

    Sweetness. Thanks a bunch guys.

Share This Page