Help please! 'adb' is not recognized as an...

[zuperjamez]

I followed these steps from the droid-life.com website found here: How to: Root DROID X Running Official Android 2.2 - Droid Life: A Droid Community Blog

Instructions:

Download: DoRootForWindows.zip
1. Extract and Update Android SDK package to your computer. (Our instructions here.)
2. Next, extract the files from the DORoot zip file to the tools folder of Android SDK.
(Take them out of the folder they came zipped in and place in tools.)
Ex: C:\android-sdk-windows\tools
3. Install Motorola Drivers: (32-bit or 64-bit)
4. Enable USB Debugging on your phone and plug it into your PC. (Settings>Applications>Development)
5. Double-click and run doroot.bat
6. Let it run.
7. It will let you know if it has finished completely.
8. Reboot your phone and you are rooted!
If these instructions don’t seem all that clear, follow the step-by-step guide which includes adb commands. Our instructional post can be found here.
Enjoy your newly rooted official 2.2 Droid X!

The only thing I did differently is that I used the correct Motorola driver for Windows XP. But After I click doroot.bat the following occurs and the phone doesn't root.

Welcome to DarkOnion Root

Presented by: darkonion and facelessuser

Special thanks to: Sebastian Krahmer at C skills

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled, and you are set to PC
mode

Checking for devices...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Transfering payload.
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->rageagainstthecage-arm5.bin
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

We will begin to apply the tears of 1000 unicorns to root your phone.
This could take as long as 5 minutes. Please be patient...
10 seconds.
5 seconds.
4
3
2
1
'adb' is not recognized as an internal or external command,
operable program or batch file.
Reconnecting in 20 sec...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Checking for device...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Remounting system as RW
'adb' is not recognized as an internal or external command,
operable program or batch file.

Copying files to system
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.

Setting permissions
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Clean up: deleting temp files
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->rageagainstthecage-arm5.bin
'adb' is not recognized as an internal or external command,
operable program or batch file.

Congralations, you should now be rooted.
No Errors

Enter exit once to exit terminal.
Press any key to continue . . .


What did I do wrong? Any suggestions would be greatly appreciated.

Thanks,
James

[tatuud]

if your goal is to root the phone why not try other simpler methods. there is Z4root, you can also try the rooting without a pc method posted in this forum. that's the one i use, very simple, literally takes 5 minutes.

with adb if the drivers aren't correct you will have a problem you also need the correct version of java, there's a lot to it.

[fpatano]

I followed these steps from the droid-life.com website found here: How to: Root DROID X Running Official Android 2.2 - Droid Life: A Droid Community Blog

Instructions:

Download: DoRootForWindows.zip
1. Extract and Update Android SDK package to your computer. (Our instructions here.)
2. Next, extract the files from the DORoot zip file to the tools folder of Android SDK.
(Take them out of the folder they came zipped in and place in tools.)
Ex: C:\android-sdk-windows\tools
3. Install Motorola Drivers: (32-bit or 64-bit)
4. Enable USB Debugging on your phone and plug it into your PC. (Settings>Applications>Development)
5. Double-click and run doroot.bat
6. Let it run.
7. It will let you know if it has finished completely.
8. Reboot your phone and you are rooted!
If these instructions don’t seem all that clear, follow the step-by-step guide which includes adb commands. Our instructional post can be found here.
Enjoy your newly rooted official 2.2 Droid X!

The only thing I did differently is that I used the correct Motorola driver for Windows XP. But After I click doroot.bat the following occurs and the phone doesn't root.

Welcome to DarkOnion Root

Presented by: darkonion and facelessuser

Special thanks to: Sebastian Krahmer at C skills

If the following command takes too long to connect, close your terminal.
Disconnect your phone and make sure debugging is enabled, and you are set to PC
mode

Checking for devices...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Transfering payload.
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->rageagainstthecage-arm5.bin
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

We will begin to apply the tears of 1000 unicorns to root your phone.
This could take as long as 5 minutes. Please be patient...
10 seconds.
5 seconds.
4
3
2
1
'adb' is not recognized as an internal or external command,
operable program or batch file.
Reconnecting in 20 sec...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
Checking for device...
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Remounting system as RW
'adb' is not recognized as an internal or external command,
operable program or batch file.

Copying files to system
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.

Setting permissions
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
'adb' is not recognized as an internal or external command,
operable program or batch file.

Clean up: deleting temp files
-->su
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->busybox
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->Superuser.apk
'adb' is not recognized as an internal or external command,
operable program or batch file.
-->rageagainstthecage-arm5.bin
'adb' is not recognized as an internal or external command,
operable program or batch file.

Congralations, you should now be rooted.
No Errors

Enter exit once to exit terminal.
Press any key to continue . . .


What did I do wrong? Any suggestions would be greatly appreciated.

Thanks,
James

Did you install the Android SDK? Are you logged in as Admin?

the ADB not recognized is typical if you did not install the SDK and did not place the files in the Tools folder of the Android SDK folder.

[donballz]

Alright Ironman, lets get you set up on ADB step by step.

1. Go to Android Developers website, and download the SDK setup from the link HERE.
2. Unzip the SDK files into the root of your C:\. (So C:\android-sdk-windows is mine)
3. Run SDK Manager, to do this you MUST have Java installed (if you don't Google it).
4. It'll pop up a cmd prompt window, then pop up another window asking you which packages to install. Press 'Accept All' on the right under the list of available installs and let it install.
5. After it is all installed, open up your Start Menu, and right click on Computer. Choose properties.
6. On the left, click Advanced system settings. On the bottom right, click Environmental Variables.
7. Under System variables, click new. Variable name is adb, Variable value is C:\android-sdk-windows\tools
8. Click Ok to exit out of that, and Ok again. And Ok again.
9. Now, go over to your android-sdk-windows folder. Open up tools.
10. Copy adb.exe (first thing listed) and AdbWinApi.dll to your C:\Windows\System32 folder. Now you can run adb from any directory (it's the easy way so when you open cmd prompt you can just press adb devices).
11. Plug in your DX, make sure USB debugging is enabled (this is toggled by going to Settings>Applications>Development).
12. Now lets make sure you have the right ADB drivers installed on your system. Go to Control Panel, click on Device Manager, and you should see an ADB Interface drop down at the top of the devices. If it reads 'Mot Composite ADB Interface' that is the right driver.
13. Lets confirm all this worked! Open Start menu, type 'cmd' in the 'Search programs and files'. Should read C:\Users\(your name or whatever).
14. Type in adb devices (it'll start up daemon), and it should show a list of devices.

Bam! At this point, follow the directions for root, and you can root through ADB. I'm a firm believer of hands on methods for doing stuff...so I prefer doing ADB instead of one-click. Hope this helps!

Make sure you have done all this first. Sounds like you aren't set up to run adb commands from anywhere but the adb/tools directory.