I followed this tutorial:
ttp://dottech.org/tipsntricks/21534/how-to-install-adb-and-fastboot-on-your-windows-computer-for-use-with-your-android-phone/
I made sure I did everything right
I dl it
extracted to the C:
Changed the Path
And yet when I go to Command Prompt to type in a simple adb commands I always get this
D:\Profiles\Administrator>adb shell
not recognized.......
Do i need to connect my device to make sure it is recognized?
If u look at the tutorial you don't need to. You get a response like Daemon Starting...Port XXXX
This is like my third attempt to try installing adb from different guides. PLEASE HELP
Try this tutorial.
http://forum.xda-developers.com/showthread.php?t=879701
Related
I am pulling my hair out. I have SDK installed and whatever I was instructed to install on SDK, for the life of me I can't get the command shell to work. When I open a command shell and type adb. I get a message 'adb' is not a recognized as an internal or external command, operable batch or program file.
My phone is plugged in debugging checked, I have it set to mass storage, not kies. What am I doing wrong.
Sorry for the noob question. I have been reading every forum I can find, every document I can find. I am trying to learn and I like to mess with my phone and should know how to use adb command shells.
Can someone tell me what I am doing wrong?
Thanks.
Rhiannon224 said:
I am pulling my hair out. I have SDK installed and whatever I was instructed to install on SDK, for the life of me I can't get the command shell to work. When I open a command shell and type adb. I get a message 'adb' is not a recognized as an internal or external command, operable batch or program file.
My phone is plugged in debugging checked, I have it set to mass storage, not kies. What am I doing wrong.
Sorry for the noob question. I have been reading every forum I can find, every document I can find. I am trying to learn and I like to mess with my phone and should know how to use adb command shells.
Can someone tell me what I am doing wrong?
Thanks.
Click to expand...
Click to collapse
PC or mac?
On a PC cd /Android/Tools then use adb commands
on a Mac: cd /Android/Tools then use ./adb then the command
PC. Thanks I will try that.
update
system cannot find the path specified
I am ready to delete everything and start over, maybe the path is wrong and I borked something in the download. There should be an Android for dummy's book or something, for us noobs.
where did you install the files? You had to download the SDK and unzip it.
Then you use a command window to change directories to where ever you installed it. Then run the commands.
If you don't know how to move around directories using DOS commands, you better find a tutorial on that first.
Your problems sound like you are not in the tools directory - CMD issues not Adroid - CMD is the windows shell btw.
alphadog00 said:
where did you install the files? You had to download the SDK and unzip it.
Then you use a command window to change directories to where ever you installed it. Then run the commands.
If you don't know how to move around directories using DOS commands, you better find a tutorial on that first.
Your problems sound like you are not in the tools directory - CMD issues not Adroid - CMD is the windows shell btw.
Click to expand...
Click to collapse
downloaded and upzipped. It's in a folder named Android, in my c;/drive. I watched a tutorial and put it where I thought I was supposed to, then I made sure to edit the path. I can undo that. I know it's a CMD issue. Great DOS commands, this is a little over my head.
I's probably easier for me to delete everything and start over.
Is there an ADB for dummies or anything. I find them for other devices not Captivate?
if you change directories to the tools directory, do you see adb.exe listed? I am not sure which tutorial you used, but there is no reason to edit the path if you change directly into the android sdk/tools directory.
In a CMD window, change to the tools directory and do a DIR and see if the first file is adb.exe
Deleting and starting over is not going to change things at this point. Also ADB is a command that works the same regardless of which phone you have. The only things that are different is if you can mount the system partition - depends on your kernel - is it custom. Not phone dependent though.
alphadog00 said:
if you change directories to the tools directory, do you see adb.exe listed? I am not sure which tutorial you used, but there is no reason to edit the path if you change directly into the android sdk/tools directory.
In a CMD window, change to the tools directory and do a DIR and see if the first file is adb.exe
Deleting and starting over is not going to change things at this point. Also ADB is a command that works the same regardless of which phone you have. The only things that are different is if you can mount the system partition - depends on your kernel - is it custom. Not phone dependent though.
Click to expand...
Click to collapse
Thanks I did this and no it isn't listed. the Android folder is, that is where I extracted all the files. Should I move from the folder. After extracting the files did I need to install anything from it?
Rhiannon224 said:
Thanks I did this and no it isn't listed. the Android folder is, that is where I extracted all the files. Should I move from the folder. After extracting the files did I need to install anything from it?
Click to expand...
Click to collapse
You should have extracted everything. You should have a folder that extracted:
android-sdk-windows and in that a tools folder. In the tools folder is ADB.exe
It is one big zip file - nothing to install - just unzip where you want it.
hold shift and then right click on that tools folder(wherever you put it), select open command window here from the menu, then type adb to make sure it worked
Kagoshema said:
hold shift and then right click on that tools folder(wherever you put it), select open command window here from the menu, then type adb to make sure it worked
Click to expand...
Click to collapse
Thank you. That did the trick. It is there and it worked. So I am guessing that when I want to open a command shell and use ADB this is how I will be able to do it. Thank you so much for all of your help everyone.
I am very new to Android and smart phones, 7 weeks now and I am trying to learn as much as I can and I try to find the information without asking too many questions.
Last night with SRE and it's sleeping death made me realize that I need to know how to use ADB and a command shell should things go wrong.
Again, thanks to everyone for the help.
I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?
I just made a folder in my c drive called ADB, and placed the entire folder with adb and the dll files required in it, along with superuser, busybox, etc.
Right click on command prompt and run as administrator.
once at system32 type: cd C:\ADB
then you will have navigated to the folder containing your ADB files.
your command prompt should now read: C:\ADB
then you can type: adb devices
it will say something about starting daemon services, and then list attached devices.
you are free to proceed with whatever instruction or operation you are doing after that.
also, make sure you have the drivers for the phone installed, or your computer wont recognize the android debugging bridge.
LowRentTechGuy said:
I am trying to get adb to work. I am doing it on a x64 vista system and I think I am getting the Path wrong. I am trying to get it to run like the page says to initialize it to read the device so I know it is working.
I can't get it to start from command prompt with out navigating to the directory it resides in. Is that right for the newer versions of ADB or am I just a monkey and can't figure out simple pathing?
Click to expand...
Click to collapse
Android Development is not for questions or Problems
Please post in the correct Forums
Moving to General
Well thanks for moving it, I will keep a closer eye on which forum I am browsing when I post.
Sent from my SCH-I510 using Tapatalk
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 I Follow this guide but cant get to Command Prompt... I Do Shift-Right Clic and Nothing. I Have a Windows XP.
First stop creating new threads for every issue you have please. Just use the thread you've already started or lumins thread that you linked to.
Second make sure your just in the folder when you do this. Nothing in the folder should be selected.
Click start
Click run
Type cmd or command.
Now in widows xp you cant open a command prompt from within a folder so you will need to change directories to the folder you have heimdall in.
Normally it will be something like this
Code:
cd c:/computer/username/downloads
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Ironcheeks said:
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Click to expand...
Click to collapse
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Lgrootnoob said:
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Click to expand...
Click to collapse
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Ironcheeks said:
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Click to expand...
Click to collapse
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Lgrootnoob said:
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Click to expand...
Click to collapse
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Ironcheeks said:
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Click to expand...
Click to collapse
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Ironcheeks said:
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Click to expand...
Click to collapse
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Lgrootnoob said:
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Click to expand...
Click to collapse
Thank you for all your help!
I need to manually root a lot of devices in as short a time as possible. I would like to do this with ADB but I don't know how to use ADB to perform the same commands on more than one device at a time. I found this Stack Overflow (that I'm not allowed to post the link to) and this Github (that I also can't post a link for call adb-wrapper) so I've been trying to use these shell scripts in Ubuntu (I am a complete noob at Linux). I wrote a simple little "Hello World" shell script and ran it from CMD prompt just to see how they work. And I managed to get the Stack Overflow script to work (I think) to call ADB devices and engage the debugging authorization on 5 devices at a time. That was great! I just copied the script into the Ubuntu Bash and called it in CMD Prompt and then ran the command: ADB devices. But when I tried adb reboot-bootloader I got the more than one device is attached warning. So I tried implementing the Github one and I just can't get it to work. I was close but my $ANDROID_HOME path was wrong and when I tried to fix it I think I just broke everything. Now whenever I run adb (anything) it just prints out ADB guidelines like commands to use and what they do. I'm at the point where any bug I Google is returning nothing useful.
I need to run the following ADB commands in parallel:
adb reboot-bootloader
fastboot oem unlock
fastboot boot recovery.img
Help?
run adb command in parallel
jaynesbluewish said:
I need to manually root a lot of devices in as short a time as possible. I would like to do this with ADB but I don't know how to use ADB to perform the same commands on more than one device at a time. I found this Stack Overflow (that I'm not allowed to post the link to) and this Github (that I also can't post a link for call adb-wrapper) so I've been trying to use these shell scripts in Ubuntu (I am a complete noob at Linux). I wrote a simple little "Hello World" shell script and ran it from CMD prompt just to see how they work. And I managed to get the Stack Overflow script to work (I think) to call ADB devices and engage the debugging authorization on 5 devices at a time. That was great! I just copied the script into the Ubuntu Bash and called it in CMD Prompt and then ran the command: ADB devices. But when I tried adb reboot-bootloader I got the more than one device is attached warning. So I tried implementing the Github one and I just can't get it to work. I was close but my $ANDROID_HOME path was wrong and when I tried to fix it I think I just broke everything. Now whenever I run adb (anything) it just prints out ADB guidelines like commands to use and what they do. I'm at the point where any bug I Google is returning nothing useful.
I need to run the following ADB commands in parallel:
adb reboot-bootloader
fastboot oem unlock
fastboot boot recovery.img
Help?
Click to expand...
Click to collapse
Hi jaynesbluewish,
I too want to run adb commands in parallel. Can you let me know if you have found the solution to this..
Please share the steps you followed..