Hi everyone!
I have Nexus S. Currently installed ICS ROM. Now I'm trying to root it, but I cannot access the folder where fastboot.exe is located.
I open CMD and type cd \nexussrootICS
nexussrootICS is a name of the folder where fastboot.exe is located.
but when I type that, it says that "system cannot find the path specified".
I've checked many times the path. It is C:\user\myname\ + nexussrootICS
but I cannot access it from CDM.
What am i supposed to do? maybe some changes are required in environment variables???
Thanx in advance!
Do you have latest sdk installed? I always cd android-sdk-windows/tools (which is where fastboot.exe is), but I think it taken out in some of the most recent updates to the sdk so I'm just usin an older fastboot
Sent from my Nexus S 4G using Tapatalk
is this the guide your using if not this guide worked for me http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Thanks guys, already fixed! It was about semicolon in environment variable>> path.
Related
This will allow you to use adb and fastboot as if they were any other DOS command by typing them in a Command Prompt window from any directory.
Thanks to MERKJONES for giving me the idea... of course it only occurred to me after he mentioned it, that this would be quite useful for a lot of people besides ourselves
There are two ways of doing this.
#1
as per MERKJONES suggestion you can just add the files to your "windows/system32" directory.
#2
I like to keep my files organized in my own folders and be able to put them on any partition that I want. So to do this we just need to add the path of your folder containing adb and fastboot files to the windows Environment path.
IN XP/WINDOWS 7/VISTA
Right click on "my computer"
Left click on "properties"
Then.........
IN VISTA/WINDOWS 7 (this is an extra step for these two OS"s ignore this if you are using XP)
Click on "Advanced System Settings" in the left hand pane.
IN ALL WINDOWS
Make sure you are on the "Advanced" tab of the System Properties Panel.
Click on "Environment Variables" button.
Look for a line/variable that says "Path" in "System variables" pane.
Double click on "Path" to open a new window that should be say "Edit System Variable" or select the "Path" variable and click on the Edit Button.
Navigate to the end of the line/value and add
;path to files (where "path to files" is the location of your adb and fastboot files)
For example for me this is
;E:\AndroidFiles
So your path should look something like this
%SystemRoot%\system32;%SystemRoot%;E\AndroidFiles
Now reboot and you can open up a DOS Command Prompt window and use these programs in any directory you want by just typing them like any other DOS command.
Awesome.... I hope this can help some folks out
or as i have mentioned to MANY people in MANY threads, place the adb and fastboot in your system32 folder and you are good. but why should you use the search function when you can just post a new thread that says the same thing many other threads say
tubaking182 said:
or as i have mentioned to MANY people in MANY threads, place the adb and fastboot in your system32 folder and you are good. but why should you use the search function when you can just post a new thread that says the same thing many other threads say
Click to expand...
Click to collapse
LOL... Was thinking the same thing. This has been talked about over and over
PS... the "other" way of doing it I think was actually written by Stericson originally
momentarylapseofreason said:
LOL... Was thinking the same thing. This has been talked about over and over
PS... the "other" way of doing it I think was actually written by Stericson originally
Click to expand...
Click to collapse
You are right of course, I probably should have checked first... so no offense to anyone there are sooooo many threads to keep up with and a search can often bring up so many threads that is easy to miss something.
Actually I am sure that although Stericson may have also written it... he is far from the first person as it is really quite a common thing ... I just wanted to help let people know there was an easier way of doing things.
or as i have mentioned to MANY people in MANY threads, place the adb and fastboot in your system32 folder and you are good. but why should you use the search function when you can just post a new thread that says the same thing many other threads say
Click to expand...
Click to collapse
No offense.... but I personally don't like throwing file after file into my system32 folder as it can get messy... hence adding it to the Environment Path
Sometimes things can be repeated over and over and still get lost in a long thread... so I tried to make it more obvious for people to find the information
pixel-painter said:
You are right of course, I probably should have checked first... so no offense to anyone there are sooooo many threads to keep up with and a search can often bring up so many threads that is easy to miss something.
Actually I am sure that although Stericson may have also written it... he is far from the first person as it is really quite a common thing ... I just wanted to help let people know there was an easier way of doing things.
No offense.... but I personally don't like throwing file after file into my system32 folder as it can get messy... hence adding it to the Environment Path
Sometimes things can be repeated over and over and still get lost in a long thread... so I tried to make it more obvious for people to find the information
Click to expand...
Click to collapse
you dont have to put it in your system32 folder.
Put your backed up img files (all files from nandroid backup) in the same folder as fastboot, then open command-prompt
you then need to change directory to the location of the folder with this command
cd c:\where ever the fastboot folder is
(if its just in the c drive then the command would look like this)
cd c:\fastboot
enter, and you will then get
C:\fastboot>
then just type these commands.
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
this is how i restore and have been doing it this way everytime no problems.
^^ Sorry but I think you missed the point entirely The idea is to avoid doing that so one can use the programs from any directory.
Both #1 and #2 are really just 2 different ways of accomplishing the same thing
hi im using 5.0.1H build and would like to have root terminal control back. all my commands come back permission denied. Fastboot works for me for nandroid but when i try to follow the instructions on gaining superuser i get this
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb push bin/s
u /system/bin
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb shell chmo
d 4755 /system/bin/su
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb uninstall
koushikdutta.superuser
- waiting for device -
what could i be doing wrong.
Hi,
Try doing:
adb devices see if your phone is recognized by the computer
adb remount enable read /write access
Now you can use your other commands.
maydaysos said:
hi im using 5.0.1H build and would like to have root terminal control back. all my commands come back permission denied. Fastboot works for me for nandroid but when i try to follow the instructions on gaining superuser i get this
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb push bin/s
u /system/bin
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb shell chmo
d 4755 /system/bin/su
error: device not found
C:\Documents and Settings\Owner.YOUR-D592011E4B\Desktop\Superuser>adb uninstall
koushikdutta.superuser
- waiting for device -
what could i be doing wrong.
Click to expand...
Click to collapse
Hey guys, I am new to this forum so apologies if I'm posting in the wrong category. I want to run some psd files I have through drawPatch9 but I can only seem to get as far as the android-sdk-windows folder in command prompt (windows 7). I have the correct jdk and can run eclipse with no probs, just can't navigate to android-sdk-windows/tools. I get "system cannot find specified path" when I try "cd tools". I also tried tabbing through android-sdk-windows folder and I only get add-ons, docs, SDK Manager, SDK Readme and uninstall, no tools or platform-tools directories. I couldn't find a solution here or elsewhere, hoping someones ran into this before. Thanks in advance.
I can't believe no one's answered this. The SDK tools were moved to android/platform-tools, and you will need to open the SDK Manager and install the platform-tools package.
u can also add the directory to your path environment variables.
Assuming your running windows rightclick mycomputer>properties>advanced system settings>environment variables.
system variables box find path click edit and add the complete path use ; as a seperator
this way you can execute the tools from any directory
Sent from my LG-P999 using XDA
Downloaded and extracted the SDK from Android's website. Copied the path to my $PATH and when I run 'adb' I get this:
dyld: Symbol not found: ___stack_chk_guard
Referenced from: /Users/Brainchild/Desktop/android-sdk-mac_x86/platform-tools/adb
Expected in: /usr/lib/libSystem.B.dylib
Trace/BPT trap
Click to expand...
Click to collapse
I've searched and nothing I find either works or is relevant. I've no idea what to do from here.
himom said:
Downloaded and extracted the SDK from Android's website. Copied the path to my $PATH and when I run 'adb' I get this:
I've searched and nothing I find either works or is relevant. I've no idea what to do from here.
Click to expand...
Click to collapse
Can you clearly explain what you did? Are you trying to create a variable to run ADB in terminal without having to write the whole path down?
if so do this:
cd ~
pico bash .bash_profile
type:
export PATH${PATH}:/where you smacked your sdk (should end with platform-tools)
control-x
Y
Close terminal and restart
Should work magical wonders and awesomeness.
himom said:
Downloaded and extracted the SDK from Android's website. Copied the path to my $PATH and when I run 'adb' I get this:
I've searched and nothing I find either works or is relevant. I've no idea what to do from here.
Click to expand...
Click to collapse
Type
Code:
cd /Users/Brainchild/Desktop/android-sdk-mac_x86/platform-tools/adb
Hit enter.
Then type an adb command with your device plugged in your computer. Make sure to put a "./" with no quotes or spaces before any adb or fastboot command.
It should look something like this:
Code:
./adb remount
Hit enter. It should say "remount successful" if it does than you are good. If not than let us know
When I CD to the platform-tools folder and type
Code:
adb devices
it says "adb: command not found" If anyone could help me that would be wonderful. I am on the Inspire/DesireHD running AOSP Gingerbread. Thanks!
You have two choices. You can either run the command prefixed with ./ (dot slash), which allows for executing an executable in the current directory:
Code:
./adb devices
Or, the other choice (which will be better if you intend to use adb a lot) is to add the platform-tools folder to your path by editing or creating the file .bashrc in your home folder (~/.bashrc).
Let's suppose your platform tools folder is: ~/.android-sdk/platform-tools
Then, you would want to add something along the lines of the following to your bashrc:
Code:
export PATH="$PATH:$HOME/.android-sdk/platform-tools"
Save the file, the run this or log out/in:
Code:
source ~/.bashrc
Et voila, you should now be able to run adb from any folder without issue.
Explanation: adding the new path (folder) to your PATH environment variable tells BASH to include that folder in its search for an executable. The reason $PATH is added at the beginning of the new string is so that your default path does not get overwritten. $HOME will simply expand to /home/your_user_name when BASH interprets it.
GENIUS! IT WORKED! Thank you! Now, one more question- how do I get superuser privileges using ADB? (device is rooted, of course)
No problem.
On my G1 you were root as soon as you adb'd in. Just tested on my Defy and '$' - shocking. So once you have run adb shell, just run 'su' (without quotes of course) and accept the permission on your phone screen as usual for root programs and you should be good to go.
Sorry to keep asking questions, but when I typed
Code:
su
into adb, it asked for a password. No popup on device screen. I do have superuser installed on the device.
That is odd. I'm not sure why that would be. I'll see if I can think of something though. Hopefully someone else can make a suggestion.
Thanks! You have been very helpful.
Don't think I can hit the thanks button from the app, sorry
Sent from my Inspire 4G using XDA App
I need help with pie. Im new to adb but new to rooting I have a verizon droid mini and I have downgraded to 19.5.3 and have adb setup i have unzipped the 1.1 and put the pie.jar and root.sh into my platform tools folder i can run adb devices and my device is recognized and online but when i run the command adb push pie.jar /data/local/atvc it says cannot stat pie.jar no such file or directory PLEASE HELP what am i doing wrong or what am i missing Thanks
ojodetigre said:
I need help with pie. Im new to adb but new to rooting I have a verizon droid mini and I have downgraded to 19.5.3 and have adb setup i have unzipped the 1.1 and put the pie.jar and root.sh into my platform tools folder i can run adb devices and my device is recognized and online but when i run the command adb push pie.jar /data/local/atvc it says cannot stat pie.jar no such file or directory PLEASE HELP what am i doing wrong or what am i missing Thanks
Click to expand...
Click to collapse
Take both (pie.jar and root.sh) out of your platform tools folder and place in same folder as platform tools folder. That is how mine is setup.
mrwinkle said:
Take both (pie.jar and root.sh) out of your platform tools folder and place in same folder as platform tools folder. That is how mine is setup.
Click to expand...
Click to collapse
When i set up my adb the only folder i got was the platform tools folder so basically i extracted the platform tools folder and renamed it android sdk for path purposes maybe i set up adb wrong like i said im new to adb but very familar with rooting so what should i do make a new folder and place platform tools in that folder along with pie.jar and root.sh
ojodetigre said:
When i set up my adb the only folder i got was the platform tools folder so basically i extracted the platform tools folder and renamed it android sdk for path purposes maybe i set up adb wrong like i said im new to adb but very familar with rooting so what should i do make a new folder and place platform tools in that folder along with pie.jar and root.sh
Click to expand...
Click to collapse
you can try that but since i'm not sure how you install android sdk here is the video that help me install it and i had no problems with PIE
mrwinkle said:
you can try that but since i'm not sure how you install android sdk here is the video that help me install it and i had no problems with PIE
Click to expand...
Click to collapse
Thanks for all your help I followed the video exactly to setup my adb i put the pie.jar and root.sh in the sdk folder and i tried it in the platform-tools folder each time cannot stat no such file or directory am i correct in saying that i first type adb push pie.jar /data/local/atvc ENTER then adb push root.sh data/local/atvc ENTER then adb shell chmod 755 /data/local/atvc/root.sh ENTER then adb shell /data/local/atvc/root.sh ENTER then PROFIT
What operating system are you running?
here is another vid that may help.