How to Root Your Droid X***Updated (v2)***

[nkair360]

Why would I go back to iPhone forums when I don't have an iPhone? And I really blame the guides that are so vague. Maybe 2-3 more sentences per step to explain them more would help?

What issues are you having with SDK and ADB??

If it helps, check this video out to give you a visual of whats going on. I watched this first and followed the steps here afterwards.

[Droid-X-Forums]

[Sam]

See? That is the stuff they left out of the guides. They can't seriously expect new Android users to be able to find that out if they are trying to make an "easy" guide.

yeah.. just wait a month or so when there are a bunch of ROMs running around and rooting/flashing them is as easy as clicking a button. that's what happened with the original droid. i rooted when the guide looked like this. it was scary, to say the least. i should have just waited for the push-button option.

[BOWIE]

Wow Gunslinger, go easy on him. It always drives me nuts when tech savy aren't willing to help the aspiring. If you can't help him, holster your gun and walk away.

Agreed. Thank you! Some of us have lives away from the internet and haven't spent hours modding phones! lol
Insulting someone who is asking for help only makes you look small.

And, bravo to Sam for being one of the few helpful, level-headed people people in this whole thing (esp when he closed the insurance scam thread!)

[chris2k5]

yeah.. just wait a month or so when there are a bunch of ROMs running around and rooting/flashing them is as easy as clicking a button. that's what happened with the original droid. i rooted when the guide looked like this. it was scary, to say the least. i should have just waited for the push-button option.

Most likely going to wait for the one button push to root feature.

Anyone know if rooting will be needed to bootload ROMs?

[Sam]

yes, it will be necessary (but likely much easier)

[Steven.RN]

What drivers where you using when you did this? Can't get XP SP3 to recognize the usb drivers for the phone. Still only comes up as Motorola MTP "portable device" and when I try to update the drivers, to the ADBdriver_v3, says the inf. file has nothing to do with the hardware???

Go to your home screen.

Hit settings.

Go to applications.

Go to development.

Turn on USB debugging.

Go Home.

Slide down the USB notification.

Don't be in "PC mode" on the Droid X's USB choice screen. Use "charge only" or maybe "mass storage"; one of em works.

Install the drivers. It'll work. (It'll fail in "PC mode" every time); it will install the ADB interface device no problem.

Go back to OP and do the deed ;-)

Cheers!

Steve RN

[RolandDeschain]

See? That is the stuff they left out of the guides. They can't seriously expect new Android users to be able to find that out if they are trying to make an "easy" guide.

Well, the Droid X is my first Android phone; I never even touched one until I bought the Droid X at Costco last Thursday. That being said, the initial guide on here was rather lacking...the one at alldroid.org was much better, but it's not like it was hard to find that. I guess I got a little annoyed at your "Android cult" comment. If there is any "cult" mentality in the entire world of technology, it is Apple followers; not Windows/Android/etc. Coming here and saying iPhone forums are more helpful and saying Android followers are cult members is not a great way to try and actually get help, it's just a quick route to a virtual @$$-kicking. Did you not find the post on alldroid.org on how to root the Droid X? It's linked in the original root thread here...

[thesnowgod]

Feeling like a total moron here but I'm at the command prompt and when I type in adb devices, it tells me: "adb devices is not recognized as an internal or external command, operable program or batch file."

I know I'm missing a very obvious step here but can someone point me in the right direction? It feels like I'm so close and yet I'm sure I've done something wrong early on.

[RolandDeschain]

Feeling like a total moron here but I'm at the command prompt and when I type in adb devices, it tells me: "adb devices is not recognized as an internal or external command, operable program or batch file."

I know I'm missing a very obvious step here but can someone point me in the right direction? It feels like I'm so close and yet I'm sure I've done something wrong early on.

Make sure you're in the directory that the adb executable is located in. It's in the Tools subfolder in the Android SDK folder. (even though the guide says to extract the Droid X root files to c:\droidxroot or whatever, I just extracted mine to the Android SDK > Tools folder, and it worked fine)

All of my commands were run from the Tools folder because that's where the adb file is, and where I extracted the root files to. Keeps it simple.

[Steven.RN]

Feeling like a total moron here but I'm at the command prompt and when I type in adb devices, it tells me: "adb devices is not recognized as an internal or external command, operable program or batch file."

I know I'm missing a very obvious step here but can someone point me in the right direction? It feels like I'm so close and yet I'm sure I've done something wrong early on.

The problem is that adb is not in your "path".

Without knowing what system you're using in particular, try this:

Whatever directory you used to install the android sdk
(let's say c:\android) go to the "tools" directory. (c:\android\tools). Use windows whatever to put all the files from the droidxroot2.zip in that directory too. They won't overwrite anything.

Then, get a command prompt (start-run "cmd" without the quotes.)

if it IS c:\android\tools, type at the prompt: cd \ (the letters cd then a backslash) and hit return.

then type : cd c:\android\tools

the prompt will now say- c:\android\tools:

if you are in the same directory with the adb.exe file, it will "see" it now, and do what you tell it.

Again, the simpler way is to add c:\android\tools to your "PATH" variable, but this is a quick and dirty workaround.

Good luck.....

Steve RN