Home

Share this Story

Root Android 2.1 the Easy Way with New DMUpdater

The DroidMod team has been quiet over the last few months working behind the scenes, but trust me when I say it appears as if they are gearing up to explode back to the forefront.  We just received a beta version of their DMUpdater app which easily roots Android 2.1 on a variety of devices including the Droid 1, Droid X and EVO.  Yes I just said “easily roots” 2.1 for the Droid 1.  No more SBF file, no more RSD Lite, and no more Motorola USB drivers.  I guess we’ll need to update our rooting guide, again.  And I’ll let that soak in for a second…

Just be warned that this is definitely a beta version of the app and is by no means official.  I’ve tested this twice on my Droid 1 and ran into zero problems.

Update: To clarify, I have not tested this on the Droid X or EVO.  I have no idea if it will in fact root either but have been told it “should.”  I only said “root” there, not root and recovery image.  Until I get further confirmation, Droid 1 owners should probably be the only testers.

Your comments and shared experiences will be greatly appreciated.

*Warning* – This will void your warranty, possibly brick your device, and who knows what else.  We are not liable should any of those things happen.  Enjoy!

Download:  *LINK PULLED AT REQUEST OF DEVELOPER*

Instructions…

*The process outlined is for rooting the Droid 1.

1.  Download and install the new DMUpdater.  Open it.
2.  When prompted, tap the button to “Root my phone.”

3.  When prompted to give access to DMUpdater, tap “Allow.”

4.  DMUpdater will then prompt you to flash SPRecovery onto your phone.  Allow it to.

5.  Once that finishes, you are rooted 2.1 with a custom recovery image.
6.  Close DMUpdater and enjoy your new phone!

Your next step is to boot into recovery (Power+X) and create a full nandroid backup.  From there, prepare to start flashing custom ROMs, having fun with Froyo and so much more.

Huge props are in store for  the entire DroidMod team, Camel, trevorjay, sgx (tax), [mbm], and birdman for getting the root method to work.  Visit DroidMod.org for the future support and an official release of this.

You can also find them in IRC at #droidmod.

  • Chasemcwilliams

    can anyone please tell me how to unroot my droid after i did the above steps.

  • Chasemcwilliams

    can anyone please tell me how to unroot my droid after i did the above steps.

  • Dupijuez

    If I root my D1 will i be able to do tether via wifi? Since verizon said the phone doesnt have capabilities wondering if just usb works.

  • Dupijuez

    If I root my D1 will i be able to do tether via wifi? Since verizon said the phone doesnt have capabilities wondering if just usb works.

  • Awehunt

    i searched the market on my droid, and could not find DMUpdater

  • LovelyLJ

    Ok so should I use this or not? Im still stock 2.1

  • CJ

    So why is creating a nandroid backup so important? I'm rooted, running bb v0.4, did a full system titanium backup.

    • Mrpicolas

      think of ot as a safety net a good image you know that works

      • CJ

        Should I still run it then, even if my phone is currently a 'bugless beast' with no problems?

        • Mrpicolas

          Well its always good to make a backup because you have something to go back
          too in case of problems

  • Trapstar3o2

    Theoretically, will this work on the Eris running 2.1?

  • JimmyD

    This is a post from a mod over at DroidForums…. he contacted the DroidMod guys and as you will read, the DMupdater is NOT ready!
    ________________________
    POSTED Today, 12:20 PM
    BY pilotcharles747
    DROIDFORUMS RESCUE SQUAD

    Do not use droidmod updater
    It was leaked and can potentially brick devices.

    From convo from DroidMOD;

    [12:05] == pc747 [add91ae7@gateway/web/freenode/ip.173.217.26.231] has joined #droidmod
    [12:06] <pc747> importatnt question The new dmupdater is that an approved app you guys put out or did it get leaked and its not finished. Poeple putting on their devices and want to know as im being asked
    [12:06] <@vulc4n> it was leaked.
    [12:07] <pc747> and are u guys charging 20 bucks for it. it does not seem like you guys to be doing some stff like that
    [12:07] <@vulc4n> lol. where did you hear that?
    [12:07] <pc747> its all over the forum people saying they are now being charged 20 bucks
    [12:07] <pc747> droidforum'
    [12:07] <@vulc4n> link?
    [12:08] <pc747> so i rooted using DM uploader a few days ago
    [12:08] <pc747> DMUpdater updated to root Droid 1, Droid X, and EVO 4G within app
    [12:09] <pc747> want to get this stuff straighten out. If people aint suppose to have it i need to tell the admin to pull those links
    [12:09] <@vulc4n> no, they aren't supposed to have them.
    [12:10] <@Ronen> vulc4n, can't really “leak” something that was posted in a (then public) IRC channel…
    [12:10] <@TheDeathly> Ronen, but it wasnt supposed to leave the channel.
    [12:10] <@TheDeathly> although it was on the git, so its “fair play”.
    [12:10] <@vulc4n> Ronen: I suppose. I think Camel may have made this into a bigger mess than it needed to be
    [12:10] <pc747> thanks can you have some one for you group let droidlife know that so the can disable the links. If they can potentially mess up phones
    [12:11] <@vulc4n> pc747: are you in touch with the guy who runs droidlife?
    [12:11] == carden [~shiggins@gw-105.extranet.sea01.isilon.com] has quit [Quit: Leaving.]
    [12:11] <pc747> brb ill get his gmail
    [12:11] <@vulc4n> pc747: and yes, it absolutely has the potential to brick phones.
    [12:13] == cystic850 [~cystic850@173-18-179-91.client.mchsi.com] has quit [Ping timeout: 276 seconds]
    [12:13] <pc747> kellex@droid-life.com
    [12:13] <pc747> ima let the mods and admin on droidforum know to pull those links.
    [12:13] <@Ronen> Whoops…that wasn't supposed to happen.
    [12:13] <pc747> thanks.
    [12:14] <pc747> do you have a problem if i copy and paste our convo to the admin
    [12:15] <@vulc4n> pc747: sure. actually, can I get into contact with him, too?
    [12:15] <@vulc4n> I wanted to see about getting some sort of official account for the droidmod team over there
    [12:15] <@Ronen> Neat, FRG01B is out.
    [12:16] <DLister|work> vulc4n: dmupdater is in the market for $20
    [12:16] <@TheDeathly> i dont even see it.
    [12:16] <pc747> http://www.droidforums.net/forum/pri…p?do=new…
    [12:16] <@vulc4n> hah. I bet I know what happened.
    [12:17] == freehood4all [~freehood4@ip72-210-76-219.mc.at.cox.net] has quit [Ping timeout: 276 seconds]
    [12:17] <pc747> i did not see the app either but people are saying hitting the link takes them there. I do not know because I am rooted manually. I will post a thread telling people to not get any apps dealing with dmupdater unless the get it from you guys webpage. is that an acurate statement
    [12:17] <JoeTheGuest> Yea love the dmupdater update
    [12:18] == G8orDroid_ [~GatorD@fl-64-45-208-7.sta.embarqhsd.net] has joined #droidmod
    [12:18] == _G8orDroid [~GatorD@fl-64-45-208-7.sta.embarqhsd.net] has quit [Read error: Connection reset by peer]
    [12:18] <@vulc4n> pc747: it was prerelease software, we are just trying to keep people from bricking their phones. Its something that still needs testing.
    [12:18] <@TheDeathly> UncleRuckus, i read scroll up. Because, so stuff cant get leaked again.
    [12:19] <pc747> ok ima copy and paste this . Got to go to work. But people were raving on it, but it was weird it was not on ur page
    ________________________

  • JimmyD

    KELLEX!!! THE DROID MOD FOLKS WANT YOU TO PULL THE LINKS OFF!!!! LOOK AT THIS THREAD!!!!

    http://www.droidforums.net/forum/droid-general-

    This DMUpdater is NOT OFFICIALLY READY for public consumption per the DroidMod people!!!

  • whowland

    WTH!! Sends me to the market to buy DMupdater for $20 bucks? For real?

  • arirang

    in light of this being yanked, but i already used it to root, will uninstalling revoke root?

  • http://profiles.yahoo.com/u/N54HRZXMI6N7HCHXWEPSCZUGRY brain

    yea that did not work for me either how did you get back to stock because i do not like this its not that special to me i would rarther just wait a few days and have the ota update

  • JFKempf

    I went through myself, and it was confusing. Looks like it took a bit for the permissions program to 'spin up' as it were and give the permissions. Since titanium is running in the background, it 'remembers' not having permission. Bring up the menu, select 'more' and then 'reload app'. I did actually have that not work once, but a reboot of the phone resolved it.

  • Jager07

    None of that worked for me. Not sure why, but think it had something to do with a baseband. I had a long process getting back to unrooted “stock” 2.1. Also discovered this morning that Google only backed up about 70% of my contact information. Luckily I had it backed up through Lookout, so I'm in the process of restoring it now.

  • http://YourWebsite Brendon

    I tried this too… I am an ameture, but thought I understood enough to try it out. Guess not! I am really needing some help now though! Please! I got rid of the DMUpdater and ‘reset’ my phone. I had to reactivate because the update-stock that I used wouldn’t install as has been the problem with the root. I keep getting errors no matter what I try.I just want it back to stock! My phone says that It is 2.1 Update 1 after I factory reset and reactivated. (is there any problems with doing that?) But i still have the Superuser Permissions…. Can I get that off? Something is messed up with my phone but I dont have a clue what it is. It still works fine but I havn’t been able to root (or unroot) at ALL seems like i’m kinda stuck in the middle if that is at all possible?! I swear I have been on every forum on the internet and they all seem about as clear as mud to me… Any help will be greatly appriciated!

  • JimmyD

    KELLEX!!! THE DROID MOD FOLKS WANT YOU TO PULL THE LINKS OFF!!!! LOOK AT THIS THREAD!!!!

    http://www.droidforums.net/forum/droid-general-

    This DMUpdater is NOT OFFICIALLY READY for public consumption per the DroidMod people!!!

    • JimmyD

      This is a post from a mod over at DroidForums…. he contacted the DroidMod guys and as you will read, the DMupdater is NOT ready!
      ________________________
      POSTED Today, 12:20 PM
      BY pilotcharles747
      DROIDFORUMS RESCUE SQUAD

      Do not use droidmod updater
      It was leaked and can potentially brick devices.

      From convo from DroidMOD;

      [12:05] == pc747 [add91ae7@gateway/web/freenode/ip.173.217.26.231] has joined #droidmod
      [12:06] <pc747> importatnt question The new dmupdater is that an approved app you guys put out or did it get leaked and its not finished. Poeple putting on their devices and want to know as im being asked
      [12:06] <@vulc4n> it was leaked.
      [12:07] <pc747> and are u guys charging 20 bucks for it. it does not seem like you guys to be doing some stff like that
      [12:07] <@vulc4n> lol. where did you hear that?
      [12:07] <pc747> its all over the forum people saying they are now being charged 20 bucks
      [12:07] <pc747> droidforum'
      [12:07] <@vulc4n> link?
      [12:08] <pc747> so i rooted using DM uploader a few days ago
      [12:08] <pc747> DMUpdater updated to root Droid 1, Droid X, and EVO 4G within app
      [12:09] <pc747> want to get this stuff straighten out. If people aint suppose to have it i need to tell the admin to pull those links
      [12:09] <@vulc4n> no, they aren't supposed to have them.
      [12:10] <@Ronen> vulc4n, can't really “leak” something that was posted in a (then public) IRC channel…
      [12:10] <@TheDeathly> Ronen, but it wasnt supposed to leave the channel.
      [12:10] <@TheDeathly> although it was on the git, so its “fair play”.
      [12:10] <@vulc4n> Ronen: I suppose. I think Camel may have made this into a bigger mess than it needed to be
      [12:10] <pc747> thanks can you have some one for you group let droidlife know that so the can disable the links. If they can potentially mess up phones
      [12:11] <@vulc4n> pc747: are you in touch with the guy who runs droidlife?
      [12:11] == carden [~shiggins@gw-105.extranet.sea01.isilon.com] has quit [Quit: Leaving.]
      [12:11] <pc747> brb ill get his gmail
      [12:11] <@vulc4n> pc747: and yes, it absolutely has the potential to brick phones.
      [12:13] == cystic850 [~cystic850@173-18-179-91.client.mchsi.com] has quit [Ping timeout: 276 seconds]
      [12:13] <pc747> kellex@droid-life.com
      [12:13] <pc747> ima let the mods and admin on droidforum know to pull those links.
      [12:13] <@Ronen> Whoops…that wasn't supposed to happen.
      [12:13] <pc747> thanks.
      [12:14] <pc747> do you have a problem if i copy and paste our convo to the admin
      [12:15] <@vulc4n> pc747: sure. actually, can I get into contact with him, too?
      [12:15] <@vulc4n> I wanted to see about getting some sort of official account for the droidmod team over there
      [12:15] <@Ronen> Neat, FRG01B is out.
      [12:16] <DLister|work> vulc4n: dmupdater is in the market for $20
      [12:16] <@TheDeathly> i dont even see it.
      [12:16] <pc747> http://www.droidforums.net/forum/pri…p?do=new…
      [12:16] <@vulc4n> hah. I bet I know what happened.
      [12:17] == freehood4all [~freehood4@ip72-210-76-219.mc.at.cox.net] has quit [Ping timeout: 276 seconds]
      [12:17] <pc747> i did not see the app either but people are saying hitting the link takes them there. I do not know because I am rooted manually. I will post a thread telling people to not get any apps dealing with dmupdater unless the get it from you guys webpage. is that an acurate statement
      [12:17] <JoeTheGuest> Yea love the dmupdater update
      [12:18] == G8orDroid_ [~GatorD@fl-64-45-208-7.sta.embarqhsd.net] has joined #droidmod
      [12:18] == _G8orDroid [~GatorD@fl-64-45-208-7.sta.embarqhsd.net] has quit [Read error: Connection reset by peer]
      [12:18] <@vulc4n> pc747: it was prerelease software, we are just trying to keep people from bricking their phones. Its something that still needs testing.
      [12:18] <@TheDeathly> UncleRuckus, i read scroll up. Because, so stuff cant get leaked again.
      [12:19] <pc747> ok ima copy and paste this . Got to go to work. But people were raving on it, but it was weird it was not on ur page
      ________________________

    • JimmyD

      MOST IMPORTANT COMMENT FOR THOSE WHO DIDN'T READ THE WHOLE CONVERSATION ABOVE….

      [12:11] <@vulc4n> pc747: and yes, it absolutely has the potential to brick phones.

      [12:11] <@vulc4n> pc747: and yes, it absolutely has the potential to brick phones.

      [12:11] <@vulc4n> pc747: and yes, it absolutely has the potential to brick phones.

      [12:11] <@vulc4n> pc747: and yes, it absolutely has the potential to brick phones.

      [12:11] <@vulc4n> pc747: and yes, it absolutely has the potential to brick phones.

      That's a comment straight from DroidMod.

  • whowland

    WTH!! Sends me to the market to buy DMupdater for $20 bucks? For real?

  • http://profiles.yahoo.com/u/N54HRZXMI6N7HCHXWEPSCZUGRY brain

    ok so i rooted my phone using this method and now i am not all that satisfied with it as i thought i would be and would like to unroot and go back to stock could someone please tell me how to do so i would be very happy thanks so much

    • Mrpicolas

      rom manager and stock image easiest way to go

      • http://profiles.yahoo.com/u/N54HRZXMI6N7HCHXWEPSCZUGRY brain

        so all i have to do is go into rom manager and download the stock image and install it and i will be back to stock unrooted? because i was reading down below and on other websites and some people say its extremely hard and a long process

        • Mrpicolas

          yeah there is a stock image option with or without root so when it asks choose without root and it will reboot unpack the stock image and flash it when done you will be on 2.0.1 then update to 2.1 after checking the update setting on your phone

          • http://profiles.yahoo.com/u/N54HRZXMI6N7HCHXWEPSCZUGRY brain

            thanks i am going to try this now and hope it works

          • Jager07

            None of that worked for me. Not sure why, but think it had something to do with a baseband. I had a long process getting back to unrooted “stock” 2.1. Also discovered this morning that Google only backed up about 70% of my contact information. Luckily I had it backed up through Lookout, so I'm in the process of restoring it now.

          • http://profiles.yahoo.com/u/N54HRZXMI6N7HCHXWEPSCZUGRY brain

            yea that did not work for me either how did you get back to stock because i do not like this its not that special to me i would rarther just wait a few days and have the ota update

  • AndroidForMe

    First time rooting…used the DMUpdater, loaded Rom Manager, then BBv0.4. Tried to then use Barnacle WIFI, but can't see SSID on computer. Do I need some sort of WIFI fix?

    • CJ

      I had the same problem. Try going to settings and check the “skip wpa…”, then refresh your wireless networks on your computer, and while your computer is searching start your wifi tether and select the associate option on the main screen of barnacle.

      Hope it works for you!

  • CJ

    So I just rooted, thanks to this wonderful site!!! I'm running bb v0.4 and I'm wondering how do I overclock above the 800mhz, which is the max I'm getting with SetCPU? I've downloaded ROM manager and tried a couple of kernels but once my phone is done rebooting my kernel remains the same.

    Thanks in advanced for any help!

    • Chris Nimon

      i think that is the max for the kernel that comes with BB. You can always download a new kernel from rom manager(i dont know about the free version but definitely with the paid version). (dont wipe data and cache). when phone reboots open setcpu, click menu, device selection, auto detect speeds (do not pick Droid). then sometimes you have to slide your max speed to 0 then back up to where you want it.

      • CJ

        Seriously, thanks for the help! Unfortunately it didn't work for me, still have the same kernel.

        I noticed that when I reopen rom manager (paid version) that there is a pop up window that says recovery failure. There are three options to choose from

        1. Recovery is “broken”
        2. ROM manager doesn't reboot
        3. Other

        Could this have something to do with it?

        • Chris Nimon

          open RM, scroll to the bottom, click Flash Alternate Recovery, then go back up top and Flash ClockworkMod Recovery and try to load your new kernel. If you are unable to do this because it keeps saying recovery failure, reboot your phone and try again.

          • CJ

            Thanks! It worked like a charm! Any idea what themes work for bb v0.4? I like the “clean” look if that helps.

          • Chris Nimon

            sorry, cant help this time, but BB is very popular and someone will surely post their favorite themes for it. Lately ive been sticking to CM and JRummy. With Jrummy's you pick your theme, kernel, extras, then it installs. His user interface for his roms currently has no equal.

          • CJ

            How stable is it? Part of the reason I chose bb is because after reading around it seemed to consistently get good remarks about stability.

          • Mrpicolas

            they are usually pretty solid but it is beta they are known for testing till its idiot proof

          • Chris Nimon

            been runing jrummy lithium for a full day doing lots of browsing and so far not a single hiccup. its been very smooth. opted for the 1.25 Ghz kernel running it at 900.

          • Mrpicolas

            oh i know it is running alt black theme love it clean and smooth on p3 1 ghz kernel

          • Mrpicolas

            google 928droid and follow the link forget what site it is but there are alot of themes there for bugless as well as others enjoy

        • CJ

          Okay, I figured out what I needed to do. Needed to do alt flash and then flash back to clockwork. Worked like a charm and now I'm clocked at 1ghz.

        • Mrpicolas

          its still beta give it time still a few bugs

  • Sigmundroid

    ……THIS POST IS FOR ANYONE WHO *FEELS* THEY ARE STUCK ON A NANDROID BACK-UP……

    First I want to say I cannot believe the most advanced users on this board/forum/comment section
    simply refused to reply to those who needed real help, or just ignored them???? Not cool.

    So, without further adieu, This is what to do if you felt stuck on performing an advanced nandroid backup:

    1.Boot into recovery (Power on, but hold down only X) No one said this here…check.
    2.Select: Back up/Restore> Advanced Nandroid Back up

    THIS is what NO ONE told you (and I figured it out)

    3.You do NOT have to name the back up….
    (meaning navigate using your volume button to “perform backup”

    4.You can also choose to back-up
    -Cache
    -Data
    -Misc
    -Recovery….if you wish.

    Now, IF you want to name your back-up?

    Choose “Set Back-up name”
    Write anything but do NOT use spaces…. This: _ instead of spaces…

    Once you have done this (do not use the power button) because it won't work.
    -hit the “enter” key on the keypad

    Now, select “Perform backup.”

    • The Rob

      Thank you!!!!

    • Sigmundroid

      Your welcome Rob!
      The funny part is that they said this release wasn’t ready…but I must have ran that DMU about 20 times
      before I figured it all out and installed Bugless Beast (which btw) is sofa king bada$$!!!!!!!!!!!!

      Rom manager did *NOT* work, so…..
      -Once I flashed sprecovery
      -Once I flashed clockwork recovery
      -I downloaded straight from the bugless beast thread (at droidforums.net)
      -renamed it to update.zip (when you reboot into recovery it looks for this file name: update.zip)

      which btw was NOWHERE to be found from within ROM manager (because I looked)

      If I was supposed to rename it?
      NO ONE told me haha!

      So, once you rename it to update.zip?
      Run recovery again (the clockwork recovery) which is found within ROM manager

      It will find the update.zip and bam….there it is!

    • Sigmundroid

      Your welcome Rob!
      The funny part is that they said this release wasn’t ready…but I must have ran that DMU about 20 times
      before I figured it all out and installed Bugless Beast (which btw) is sofa king bada$$!!!!!!!!!!!!

      Rom manager did *NOT* work, so…..
      -Once I flashed sprecovery
      -Once I flashed clockwork recovery
      -I downloaded straight from the bugless beast thread (at droidforums.net)
      -renamed it to update.zip (when you reboot into recovery it looks for this file name: update.zip)

      which btw was NOWHERE to be found from within ROM manager (because I looked)

      If I was supposed to rename it?
      NO ONE told me haha!

      So, once you rename it to update.zip?
      Run recovery again (the clockwork recovery) which is found within ROM manager

      It will find the update.zip and bam….there it is!

  • Heresteve2

    Still Trying to Decide if I should root or not. I love my phone the way it is. The only reason I might consider rooting is to get a little more speed. Quick question: Is there a site I can find videos of what different roms look like/what features they have? A rom review site? Thanks in advance!

    • Jager07

      If you love it the way it is, don't root. I loved my phone, too, and was just looking for a few upgrades that I *thought* rooting would give me. But be advised that just because someone has created a simple procedure to root your phone, DO NOT get trapped into believing this is a simple thing. Rooting did not give me what I wanted but instead took the phone I loved and turned it into a quirky, high-maintenance beast. I've spent the last 48 hurs trying to UNroot and it's been a nightmare, searching for the needle-in-a-haystack that would solve the problems I had. And I'm still not certain I've solved all the problems and apparently won't know until I *don't* get the official 2.2 OTA. What I quickly learned through this process (which I've outlined below in this thread in case anybody else has the same issues) is that I was very ignorant about rooting the phone and should have never done it in the first place (even though it “was easy”) simply because I didn't understand what all it involved. Props to the devs who create this stuff and give it to us for free. But before you root “the easy way,” you better know what the hell you're doing, otherwise you will find out the hard way if anything goes wrong.
      <stepping off soapbox>

  • Zrochek

    i can unroot my phone the same way with just a push of the button

  • Bones

    If I do this, do I lose everything I have on my phone?

  • Mantis75

    I have a rooted D1 and I am looking to down grade back to 2.1. Does anyone have any thoughts on this. Since I rooted I have been having battery issues, media not being able to play, 3D gallery not always working. Any thoughts?

    • Jager07

      I rooted and immediately wanted to go back to non-rooted because of compatibility and stability issues. Took me all day to employ a process that actually worked, but after 24 hours of root, I am back to non-rooted. See my post below (or above, depending on how you're viewing this thread. ha!)

  • thedonxr

    Reboot and hold power+X and do your restore, then in ROM Manager, Flash Clockworkmod then SPRecovery, then back to Clockwork mod, then flash clockworkmod one more time just for kicks and try to reload the CM6 Rom

  • Zeadaplaya

    Someone rooted help! i just rooted my phone and was following the steps to get the alternate dark theme on my phone, however after I installed the CM6 RC2 and rebooted my phone it just kept showing the droid eye and the droid logo over and over, what did i do wrong?

    • thedonxr

      Reboot and hold power+X and do your restore, then in ROM Manager, Flash Clockworkmod then SPRecovery, then back to Clockwork mod, then flash clockworkmod one more time just for kicks and try to reload the CM6 Rom

  • Zeadaplaya

    when i do the nandroid backup, do i do the simple nandroid backup, or the advanced?

  • guest

    Tried this yesterday. I wanted to root my phone but the day I bought my droid 1, my computercommited suicide. This worked like a charm and I am running bb with froyo. So happy now! Thanks devs! I love this website :)

  • Sittingbill

    Wish I Had Known This Before I Bricked My Phone Using sbf file

  • http://pulse.yahoo.com/_GPFMHN3BALHY75DRFNJY3WXBIQ Samuel

    HELP! I rooted last night with the DM Mode Beta lastnight and it did not go well, so I went to the back up recovery 2.0.1 and now I can't receive calls, and the home and search button on the phone don't work. Plus, the touch screen key pad does not come up and the market app is no longer on my phone What do I do?l

    • givemesomeadobo

      u should probably do a factory reset and just flash a new rom or something. start over

  • liquidamber99

    I'm having problems. I rooted the phone and was in the process of installing a custom ROM. I get the message 'Installation aborted'. Anybody know what I did wrong or what I do next?

  • http://twitter.com/Heynewgirl Katherine

    Will I still be rooted after 2.2 comes out?Or do we have to wait for root access again. If I root do I still get the ota push? I know there are 270 much more intelligent questions then this, but I just don't remember and I can't wait for tues. All of the Droid-Life family is the best.
    peace

  • OLD DAWG

    Help!!!! I followed the instructions and got rooted.I did the nandroid backup. I installed Rom Manager Premium and tried to install the new Dark theme from this Friday. I assume I tried to install as a ROM. I did the all I knew to do then rebooted. It hangs on the Motorola symbol. I have tried pulling the battery. I have tried Power+x. I can get the triangle symbol to appear and then hit Alt+l. Nothing is working and I am in panic mode. Please help.

    • OLD DAWG

      It looks as if everyone is taking the weekend off. All of our help experts are absent when I make a brick out of my Droid.

      • http://twitter.com/Heynewgirl Katherine

        I can't help but this is the best site. I am sure you diidnt brick your phone. Someone will answer soon.

        • OLD DAWG

          Nobody helped me and I wound up with a BRICK. Verizon was unable to fix also. I had to get a new phone. I see today that the developer asked Kellex to pull the links. I wish he had done this sooner.

        • OLD DAWG

          Nobody helped me and I wound up with a BRICK. Verizon was unable to fix also. I had to get a new phone. I see today that the developer asked Kellex to pull the links. I wish he had done this sooner.

      • Chris Nimon

        most of the “phone smart” guys take the weekend off because there normally isnt too much posted then.

    • Chris Nimon

      i dont know too much about the new rooting techniques but it sounds like stock recovery to me. If thats the case i think its camera button and vol up or power. SPrecovery brings you up to a green or blue list format. once you get back onto your phone check for the super user ninja in your app drawer.

  • Jager07

    Still trying to unroot. Here's my unsuccessful process thus far, trying to follow this advice:

    “Download RomManager from the Marketplace. Get the Stock 2.0.1 rom from the extras category. Be sure to install clockworkRecovery from rom manager too. Install 2.0.1. When it updates to 2.1 it will also overwrite the recovery partition. :-)”

    >Go to Rom Manager and download stock 2.0.1
    >Wipe Data and Cache
    >Press Ok to reboot into ClockworkMod Recovery and continue the installation <ok>
    <reboot> <Motorola symbol>

    ClockworkMod Recovery v2.5.01

    Preparing to install ROM
    Formatting CACHE:…
    Formatting DATA:…
    Formatting SDEXT:…
    No app2sd partition found. Skipping format of /sd-ext

    – Installing: SDCARD:/clockworkmod/download/droidk.macleod-web.net/motorola/sholes-2.0.1.zip
    Finding update package…
    Opening update package…
    Installing update…
    assert failed: !less_than_int(1259199777, getprop(“ro.build.date.utc”))
    E: Error in /sdcard/clockworkmod/download/droidk.macleod-web.net/Motorola/sholes/sholes-2.0.1.zip
    (Status 7)
    Installation aborted.
    /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM manager to report the issue.

     reboot system now
     apply sdcard:update.zip
     wipe data/factory reset
     wipe cache partition
     install zip from sdcard
     nandroid
     partitions menu
     advanced

    After booting with Nandroid, I tried to open sholes-2.0.1 manually through Rom Manager:

    >Go to Rom Manager
    >Browse to sholes-2.0.1 and select
    >Wipe Data and Cache
    >Press Ok to reboot into ClockworkMod Recovery and continue the installation <ok>
    <reboot>
    Takes me to a screen with an exclamation point inside a triangle, which hangs.

    Reboot phone using Turn Off/Turn On, open Rom Manager and get an error box:

    Recovery Failure:
    Recovery mode is “broken”
    ROM Manager doesn’t reboot
    Other

    I don’t even know what I’m supposed to choose from this menu, but none of it helps. So I pulled sholes-2.0.1 off my SDCard and renamed it update.zip. Tried to manually install it off ROM Manager and get same error as listed before, except with the new name update.zip instead of sholes-2.0.1.zip. So I moved update.zip to the root directory and tried to select “apply sdcard:update.zip” from the recovery menu and still get the same errors. So my assumption at this point is that the Stock 2.0.1 from ROM Manager is bad. Found this in another thread:

    “yes if you look through this site you will find the 2.0.1 sbf file this is the stock verizon file untouched using rsd lite you can flash this and reboot it will unpack and load then once up and running it will ask you to update to 2.1 since 2.2 isnt out yet select accept and you will be back to normal and yes i believe you can use astro for this not sure how it excatly works because i dont use it for that”

    So unless somebody has some other brilliant idea, I will try to find the 2.0.1 file elsewhere…

    Geez, what a pain in the ass.

    • Jager07

      So I took this advice:

      “From the best of my knowledge (no actual experience) the 2.0.1 stock image <in ROM Manager> works…
      BUT, you can always trust this guy, right?

      http://www.peteralfonso.com/p/downloads.html

      So I downloaded the Odexed version of 2.0.1. I successfully installed that using Recovery Manager and now have 2.0.1 on my phone. The bad news is, it didn't prompt me for my gmail accounts or anything and booted straight into Android. It also didn't prompt me to install 2.1. My build number reports it is ESD56 by Pete, so I'm guessing this is NOT stock 2.0.1 since I downloaded it from Peter's website. Can anybody offer a solution? I just want to get back to stock, unrooted 2.1. My phone is a business tool and I would appreciate any help getting it back to a state that doesn't require so much upkeep. Thanks!

    • BAoxymoron

      check out box option 5:
      http://www.droidforums.net/forum/hacking-faqs/3
      note: it will get rid of everything on your phone although a factory reset/wipe won't hurt either

      • Jager07

        Ok, thanks, will try that. Based on advice buried in another thread, I downloaded a nandroid of the stock 2.0.1 here:

        http://www.megaupload.com/?d=72T0I27Y

        Then I rebooted into Recovery via ROM Manager and chose to nandroid restore from that file. Got this result:

        Checking MD5 sums
        Erasing Boot before restore
        Restoring Boot image
        Restoring system
        Error while restoring system…
        <back to main menu>

        So I just restored again to my pre-2.2 nandroid. I have RSD Lite installed, so I will try to flash the sbf and see what happens….

      • Jager07

        That worked! Set me back to a factory install, so I had to initiate my phone again. Still haven't been able to manually OTA to 2.1, but that's ok–I'm no longer rooted and everything works like it should! Thanks! :)

        • Jager07

          Still haven't gotten the 2.1 OTA push, but having a stable, low-maintenance unrooted version of 2.0.1 is MUCH better than having an unstable, high-maintenance rooted version of 2.2 and hopefully I'll get the OTA soon to bring me back to 2.1 (or maybe even 2.2, if I'm lucky). Thanks again for your help!.

          • Jager07

            So apparently flashing 2.0.1 didn't get me back to “factory” after all, even though it unrooted me and installed the proper version of Android. I did a little more investigating on why I wasn't getting 2.1 OTA and found this:
            “I decided to unroot and go back to stock 2.1-update1, so what i did was flash 2.0.1, then boot to stock recovery and wipe data/factory reset and wipe cache, so then it booted to a fresh 2.0.1, few minutes later, i received the OTA update for 2.1-update1 and now im back to stock, waiting for FroYo.”

            Even though I flashed 2.0.1 via RSD Lite, I didn't boot into stock recovery–didn't even know I was supposed to–until I got saw this little insert about doing it. So after getting some help, I was able to boot into recovery (Power + X, then Up Volume + camera at the exclamation screen). This allowed me to do a factory reset and wipe cache, which was successful, but made me activate my phone again. And still no OTA 2.1 update…

            So I did a little more investigation, which got me here:

            http://www.droidforums.net/forum/rescue-squad/5

            I don't know how to check whether my baseband is the “proper” version or not–apparently it
            is a rare problem and I've never even read anybody mentioning it until I found that site–but the symptoms were the same as mine. No auto 2.1 OTA., etc. So I followed their recomendations and went to this site:

            http://androidforums.com/motorola-droid/58150-h

            Downloading the 2.1 update and installing it manually successfully got me back to 2.1 and everything is running smoothly, as far as I can tell (random baseband issues notwithstanding). Hopefully I'll still get the 2.2 OTA, and hopefully that will resolve a baseband issue, if that's what my problem has been this whole time…

          • Anonymous

            yeah I had done it once before and it worked perfectly… but I had to do this last night and I didn’t get the update… Honestly don’t know what to you… @kellex @tom anyone got any ideas?

  • NorCalDroid

    It worked. Just rooted

  • http://profiles.yahoo.com/u/N54HRZXMI6N7HCHXWEPSCZUGRY brain

    ok so i did everything it tells me to do but now i am trying to use titanium backup and its telling me i am not rooted so what have i done wrong please help!!!!!

    • JFKempf

      I went through myself, and it was confusing. Looks like it took a bit for the permissions program to 'spin up' as it were and give the permissions. Since titanium is running in the background, it 'remembers' not having permission. Bring up the menu, select 'more' and then 'reload app'. I did actually have that not work once, but a reboot of the phone resolved it.

  • angrydroid4!!

    I really hope in the near future thier will be easier wasy to root all 2.1 devices like….allly,moment,hero,mt3g,ETC…but for those who have higher end devices & the devs who work on them much love.I just fell like some lower end devices have much potiential,dont 4 get the little people..but anyways keep up the good work

  • Jager07

    Ok, I rooted and quickly realized I was in over my head. Have spent the last few hours trying to unroot. I tried several fragmented methods that I found scattered throughout the threads, but I could not get any of them to work–short story is that after running through some command screens, the phone kept booting back into cyanogen 6 rc2. Finally I reloaded my nandroid backup. It boots into stock 2.1 and all of my data and apps are there (woohoo!!!). But I get the feeling I'm still rooted. How do I tell for sure? I still have Superuser Permissions, Rom Manager and DM Updater installed (none of which I want, but I'm not uninstalling them until I make sure I'm unrooted). Here's my system info:
    Firmware Version
    2.1-update1
    Baseband version
    C_01.3E.03P
    Kernel Version
    2.6.29-omap-g7fa8788
    android-build@apa26#1
    Build number
    ESE81

    So am I unrooted or not? How can I tell? And if I'm still rooted, how, specifically, do I unroot from here? Thanks!

    • Hasbrobot

      try the one “cache mate” for root users free version from the market. if it works your rooted still if not….well your back to where you started.

      • Jager07

        Apparently I'm still rooted. :/ This is part of what I've been trying:

        “Download RomManager from the Marketplace. Get the Stock 2.0.1 rom from the extras category. Be sure to install clockworkRecovery from rom manager too. Install 2.0.1. When it updates to 2.1 it will also overwrite the recovery partition. :-)”

        Rom Manager looks like it's downloading 2.0.1 and reboots the phone when the download process is complete. But it doesn't install 2.0.1. Instead, my phone just boots to some sort of menu with green lettering and gives me options like “Install update.zip” or “install rom from sd card” or “Wipe cash and factory reset” or “nandroid backup.” I tried looking for the downloaded 2.0.1 on my sd card, but I don't see it (not sure what I'm looking for, actually). So I chose to install update.zip sinc eI figured that was a default naming scheme and maybe the 2.0.1 I downloaded via Rom Manager was, perhaps, “update.zip.” But it said it couldn't find update.zip. Then I chose “Wipe case and factory reset,” thinking maybe that would reset my phone to stock unrooted 2.0.1, but instead it just booted me back to rooted 2.2/cyanogen 6. So then I tried backing up from Nandroid, which actually worked and recovered all my lost data, but still, apparently, leaves me rooted. How do I unroot? Thanks!

  • CORYK333

    Rooted my droid using this method and it worked flawlessly………but, now when i try 2 DL roms in ROM MANAGER, the ROMS successfully DL (says ROM DOWNLOAD COMPLETE in notification menu)….i click on it and it proceeds to give me the backup/wipe option, i select both and proceed…..it reboots my droid, it restarts, it goes through a very fast black loading screen where i san see it say something about “unable to find” , something about “sd card” (its very fast so i cant make out the exact)…..it then proceeds to boot in2 CLOCKWORK RECOVERY SCREEN with the reboot, apply, wipe, etc…this happens EVERYTIME and NONE OF THE ROMS I DL FROM ROM MANAGER SHOW UP IN SD CARD EITHER, even though ROM MANAGER says DL COMPLETE(obviously if they dont show up in sd card i cant load them)…..SOME1 PLEASE HELP, IT WOULD B SOOOOOOO APPRECIATED….was so happy this method worked for me without a hitch to gain root access, but now i am rooted but unable to flash a new rom, THANKS FOR HELP IN ADVANCE

    • arf24

      sounds to me like you need to flash an alternate recovery then reflash clockwork mod recovery. ive had this happen before and all i did was what i described then rebooted and everything worked just fine. good luck.

      • CORYK333

        thanks 4 the tip….gonna give it a try right after work, much appreciated

  • SergeyZh

    I've tried this on Milestone with success!
    Was unrooted SHOLS_U2_02.36.0, now it's rooted.
    But I didn't allow to flash recovery partition, only root my system.

  • Miles

    Oh no! It made my mother cry!