Database Info

Need help with ADB

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.

[Q] Installing ADB

Hello,
I've been trying to install adb and root my nexus s. But I'm having great difficulty to do this, I have updated USB drivers, modified path, and done everything that I found on the net. but when I open cmd and type "adb" I just get. 'adb is not a known command or batch file..."
Does anybody have some ideas to installing and getting adb to work?
Thanks a lot!

Sounds like the file isn't in the right folder, if you downloaded the sdk recently read the text file, theres additional steps you need to take before accessing adb
Sent from my SGH-T959 using XDA App

If its the same issue I had I believe in the tools folder theres a text file that tells you adb is now located in the platform tools folder or something to that effect
Sent from my SGH-T959 using XDA App

SirPulok said:
Hello,
I've been trying to install adb and root my nexus s. But I'm having great difficulty to do this, I have updated USB drivers, modified path, and done everything that I found on the net. but when I open cmd and type "adb" I just get. 'adb is not a known command or batch file..."
Does anybody have some ideas to installing and getting adb to work?
Thanks a lot!
Click to expand...
Click to collapse
ADB file is now located in platform-tools folder, copy the adb file and the two files associated with the adb file and paste them in your tools folder. If you don't know the two associated file, just try pasting the adb file in the tools folder and you will get a prompt that will tell you which files

Super Noob question

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

[Q] Modem Driver?

So I was following along the instructions at http://forum.xda-developers.com/showthread.php?t=1255214 to root my phone. I was able to complete the install of Clockworkmod Recovery using NVFlash and boot into Clockworkmod Recovery. I mounted the phone and plugged into my computer. At this time, the LG Drivers I had previously downloaded started to install. All 8 or 9 of them installed, except for one titled LGE Android Platform USB Modem. I tried to resolve this issue, and look for additional help online, but I cannot seem to locate anything. I not actually sure if it's an issue or not.
However, when I moved along to step 6 of the root guide, when entering the ADB command prompts, I don't think it's doing what it is supposed to be doing. After I entered the any of the commands, it says, "'adb' is not recognized as an internal or external command, operable program or batch file." At this point I stopped the process.
Any ideas?
The driver issue and the command issue for the root could be separate issues.

You have to CD to the folder/dir you have adb installed to from the cmd line. Example, if it is on the root of your c drive, like my sdk install is, you would type CD c:/Android sdk/adb
Sent from my LG-P999 using xda premium

Thanks for the idea. Unfortunately, that was not the issue. I believe I had the proper directory listed when entering commands.

Ok.. The driver and adb not starting are unrelated. You should be able to start adb even with out a device plugged in. It's either your install of adb or not being in the right dir to enter the command. I have problems starting adb alot of the time but it's usually "operator error" on my end.
Sent from my LG-P999 using xda premium

[Q] Windows will not install drivers for tf101

I have a B90 TF101 and I am able to get into recovery mode. I have no ROM on my internal SD card and have wiped and formatted everything. I have read that it is possible to push a file using ADB while in recovery.
However I am not able to see my device when I use the adb devices command. I noticed that the drivers for the transformer are not installed. So I tried to install them and it tells me that windows can't install. I am pointing the installer to the MTP devices driver folder.
How do I get the drivers to work so I can use ADB or can I set up ADB in Linux and not have to worry about the drivers?
edit: I forgot to mention I am running windows vista.

Hi! Search in transformer's support page, you can find the drivers there

Are you saying that the drivers in the MTP folder are not the right ones? I got them right from Asus' website. Which drivers should I be using?

Ageesaman, did you ever get the drivers working? I had the exact same problem (got adb working as far as listing devices, but then it returned with a blank line after "adb devices" in cmd window). I downloaded the ASUS site's USB drivers download as well as every other utility from that site; I also tried external sources; finally, I tried manually updating by pointing to the unzipped MTP folder - nothing worked. I used both 64 and 32 bit Windows 7 machines. I am stuck in the cwm recovery loop so I can't do much troubleshooting. I tried searching dozens of sites for several hours but came up short.
Thanks in advance for any help offered.

Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.

Ageesaman,
Unfortunately I know nothing about Linux, but what finally got it working for me was starting the installation of PDANet for Android. I saw it look for and install the driver, then I got a ADB confirmation. I then canceled the PDANet install. If you decide to go this route and get error messages in the cmd window, retry "adb devices" up to 3 times. In the meantime, I hope you get your Linux answer. Good luck.

I will give that a try. Is PDAnet something from Asus? I will do a search and see if I can find it.

ageesaman said:
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Click to expand...
Click to collapse
Yes, I can confirm the TF101 works with ADB without drivers on Ubuntu linux [I am on 11.04]. The current [stable, with 12.04 betas] Ubuntu version is 11.10, and you can download it to a live CD and run it off the CD without installing it.
I just got my tf101 the other day and I tried using adb [and older version], and it did not show up. Then I downloaded the tf101 root.zip file, and tried the adb within that folder, and it worked.
I've uploaded it to mediafire:
adb-1.0.29 http://www.mediafire.com/?hqwxbljs2gbpfxe
md5 64c4afbab6d2f769ddbb229f0247cf8a
update: newest adb is 1.0.31 http://www.mediafire.com/download.php?vcvc4dxkdd57695
md5 ed5c8f9a221cae0cb24d6cdc8b76d396
download, and run
chmod +x ./adb-1.0.29
to make it executable

That worked! I can now connect to my device with ADB. Thanks for that pdanet advice.
Now I just need to figure out how to push the file. Can't seem to get it to work. Here is what I am typing in the cmd line.
adb push rom.zip /sdcard
The rom I am trying to push is in the Platform tools folder that I am using to access adb. Does anybody know what I am doing wrong? Any help would be awesome.

is the rom.zip in the same directory as you are in (cd <path>)?
What does it say when you try to transfer it?
You can also try to push it to the full path (/mnt/sdcard/)

The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.

ageesaman said:
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
Click to expand...
Click to collapse
It's probably because /sdcard is a soft link to /mnt/sdcard/
if you did /sdcard/, I think it should probably work.

You sir are the man! Thanks for your time.

To get the process all in the same place for anyone else who may need this here you go. Just to make it clear.... This is what I did on my device and it worked. It may or may not work for you but maybe it's worth a try.
1. Downloaded SDK and Java JDK.
2. Used PDAnet to force windows to install the correct ADB device drivers.
3. When the drivers where installed and ADB was working I used this command to push the .zip file to the internal sd card.
adb push rom.zip /sdcard/
Just a few notes for this.
ADB was not working well at first because I had Asus sync running in the background. Make sure this is off.
Also make sure you put the file you are trying to push in the same directory you are using for ADB. For instance I used C:/android-sdk/platform-tools/ to access ADB so the file had to be in that folder in windows explorer.
To make it easier to type (I had to do this a lot while troubleshooting) I changed the name of the rom I was trying to push to rom.zip. This made typos less of an issue.
Make sure that you put the file extension (.zip in my case) in the ADB command even if it doesn't say it when you look at the file in windows explorer.
I think that is it in a nutshell. I hope this helps anyone else who needs to push a rom.
Good Luck

This method in this post didn't work for me, but this one did: http://forum.xda-developers.com/showthread.php?t=1689193

I set Windows to look for driver in c:. After a while one was installed and worked.

What I did on windows 7
Go to Device manager
Find transformer , right click on faulty marked unit.
Select properties
go to tab driver
update driver
Select browse
select path to the subfolder ANDROID ( containing usb drivers from asus )
include subfolders
Windows will find to alternatives , choose xxxx ADB
Windows will complain, ignore
done
/Claes R
W