-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
System OS: Win7 64bit
Nexus Details:
Android Version: 2.3.6
Build No. GRK39F
Method followed to root: How To: Root the Samsung Nexus S (Updated 01.20.11) | TheUnlockr
1. Downloaded and installed the adb driver using "installer_r15-windows.exe" from Android SDK | Android Developers
2. Downloaded adb folder "android-sdk_r15-windows.zip" and unzipped to C:\AndroidSDK\
3. Downloaded few more files to be added to tools from: MEGAUPLOAD - The leading online storage and file delivery service and added them to C:\AndroidSDK\Tools
4. connected the phone through usb and while trying to do "adb devices" from command prompt getting the error " 'adb' is not recognized as an internal or external command,"
Related Screenshots:
Kindly guide how to overcome this issue and proceed further in rooting.
Also wanted to know if we can unroot the phone later on??? My purpose of rooting is just to use some system tools to enhance CPU speed and use few other applications... not looking ahead to use any of modified ROM.
Nexus Details:
Android Version: 2.3.6
Build No. GRK39F
Method followed to root: How To: Root the Samsung Nexus S (Updated 01.20.11) | TheUnlockr
1. Downloaded and installed the adb driver using "installer_r15-windows.exe" from Android SDK | Android Developers
2. Downloaded adb folder "android-sdk_r15-windows.zip" and unzipped to C:\AndroidSDK\
3. Downloaded few more files to be added to tools from: MEGAUPLOAD - The leading online storage and file delivery service and added them to C:\AndroidSDK\Tools
4. connected the phone through usb and while trying to do "adb devices" from command prompt getting the error " 'adb' is not recognized as an internal or external command,"
Related Screenshots:
Kindly guide how to overcome this issue and proceed further in rooting.
Also wanted to know if we can unroot the phone later on??? My purpose of rooting is just to use some system tools to enhance CPU speed and use few other applications... not looking ahead to use any of modified ROM.
quantumrand
Android Expert
The problem is that ADB is not in your tools folder. I believe one of the recent updates to the SDK moved it to "platform-tools." The instructions you follow will be the same, except you'll want to be in C:\AndroidSDK\platform-tools.
quantumrand
Android Expert
Run the SDK manager and have it update your platform-tools. I believe Android SDK Platform-tools, revision 9 is the latest available.
quantumrand
Android Expert
Hmm, perhaps try downloading the SDK installer and installing it again.
Or, if that doesn't solve it, since it appears you do have the driver installed properly, here's a link to my Tools folder. It has the proper versions of ADB and Fastboot, and even a Clockwork image (though I wouldn't use it since I can't remember which phone it was for).
Link: http://quantumrand.net/phandroid/tools.zip
Or, if that doesn't solve it, since it appears you do have the driver installed properly, here's a link to my Tools folder. It has the proper versions of ADB and Fastboot, and even a Clockwork image (though I wouldn't use it since I can't remember which phone it was for).
Link: http://quantumrand.net/phandroid/tools.zip
razvan06
Android Enthusiast
You should check first and see if the drivers are good ,i had the story of my life with that one ...
Anyway ,if quantumrand's post helps you ,BUT you find out that you lack the proper drivers ,go Google and search pdanet for android ,install it and select your samsung device > all working
Anyway ,if quantumrand's post helps you ,BUT you find out that you lack the proper drivers ,go Google and search pdanet for android ,install it and select your samsung device > all working