Help! Unrooting Attempt Failure! Lost Super User status.

Discussion in 'Android Hacks and Help' started by omarcastz, Mar 30, 2010.

  1. omarcastz
    Offline

    omarcastz New Member

    Joined:
    Feb 11, 2010
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    0
    To my fellows and gals from Droid nation,

    I had installed the Cyanogenmod ROM a few weeks ago using droidmod and ROM manager. Here's what I'm currently running

    Baseband Version: C_01.3E.01P
    Mod Version: CyanogenMod-5.0.5.4-Droid
    Build Number: voles-userdebug 2.1 ERE25 23960 test-keys

    Upon hearing that Verizon and Moto will finally be releasing an OTA update for the Droid. I attempted to unroot my phone and go back to the verizon stock 2.0.1. I though it would be an easy process...

    Needless to say I've royally borked my unrooting :icon_eek:.

    My process consisted of the following:

    1. Use ROM manager to do a Flash Clockworkmod Recovery
    2. Use DroidMod to go back to 2.0.1

    something went wrong in the process. I rebooted holding the X button to go into recovery. I applied the update.zip (which was the update.zip for the stock 2.0.1 I realized much too late) and now it appears that I lost my superuser access and settings on ROM manager and DM updater are borked. see below:


    Flash ClockworkMod Recovery
    Current Recovery: Unknown
    Latest Recovery: ClockworkMod 1.7.8.9

    when I attempt to do a FlashClockworkMod Recovery I obtain the following message:
    "An error occurred while attempting to run priviledged commands"

    Using Droidmod Updater gives me the following message:
    "Looks like your phone is rooted, but you have not given DM updater access yet. You *must* check the remember box!"

    when I press check again the same box keeps opening in an endless loop.

    I went to the Superuser Permission program by touching the Ninja icon. When this program opens up and it gives me a black screen with nothing else. I figured this is where the super user permissions needed to be fixed.

    I've still got a clockworkmod directory in my SD card with a backup directory and a
    download directory.

    So my phone still works but it appears that it's stuck on Cyanogen 5.0.5.4 (which is an excellent ROM). I've run out of options after doing some googling. I just want to go back to stock 2.0.1. Please help! Any suggestions will be greatly appreciated.

    Thanks you all for your time. I'm proud to be part of the droid community!
  2. pc747
    Offline

    pc747 DF Administrator Staff Member Rescue Squad

    Joined:
    Dec 23, 2009
    Messages:
    17,393
    Likes Received:
    999
    Trophy Points:
    113
    you tried unrooting back to stock with the latest rom manager.
  3. Tanknspank
    Offline

    Tanknspank Beta Team Premium Member

    Joined:
    Jan 13, 2010
    Messages:
    3,506
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    North Carolina
    Can I get you to reboot your phone and tell me what happens when you reboot into recovery?
  4. Tanknspank
    Offline

    Tanknspank Beta Team Premium Member

    Joined:
    Jan 13, 2010
    Messages:
    3,506
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    North Carolina
    He can't now, he can't even flash Clockwork.
  5. PJay801
    Offline

    PJay801 New Member

    Joined:
    Feb 1, 2010
    Messages:
    32
    Likes Received:
    0
    Trophy Points:
    0
    In ROM Manger you were supposed to flash alternate recovery..its located on the very bottom. That would flash the SPRecovery. Then you can go in DroidMod and revert back to stock 2.0.1. You flashed the wrong recovery.
  6. omarcastz
    Offline

    omarcastz New Member

    Joined:
    Feb 11, 2010
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    0
    Yes, I realize now (too late for me) that this is what I was supposed to do. Still kicking myself :mad:

    However, I saw this thread which did help me get back to stock.

    http://www.droidforums.net/forum/rescue-squad/33628-pretty-sure-i-just-bricked-my-droid.html

    Thanks everyone for pitching in. I knew someone would have the answer quick. And yes, I believe that what happened is that I tried going back to 2.0.1 using ROM Manager.

    Thanks everyone. You guys are awesome!
  7. StingRay
    Offline

    StingRay New Member

    Joined:
    Dec 10, 2009
    Messages:
    498
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Dallas
    Glad to hear that you were able to get out of your mess...:icon_ banana: