Database Users

[Q] Help with finding driver for adb

Two quick questions; any help is much appreciated. As a newbie I am unable to get adb to detect my device; running 'adb devices' always yields an empty list under Windows 7. Searching different threads lead me to the recommendation to uninstall the mass storage device driver with USBdeview and then reinstall with the android usb driver (which is said to be under tools in the SDK); however, I can't find the driver file anywhere., nor is there an USB available package in the SDK. If someone could point me in the correct direction regarding how to run adb I'd be much appreciative; I have the SDK installed and the adb daemon appears to be running.
A quick second question is if I can get the device to be detected under adb, can mass storage driver and the android driver run simultaneously? Thanks again.

Duffyxy said:
Two quick questions; any help is much appreciated. As a newbie I am unable to get adb to detect my device; running 'adb devices' always yields an empty list under Windows 7. Searching different threads lead me to the recommendation to uninstall the mass storage device driver with USBdeview and then reinstall with the android usb driver (which is said to be under tools in the SDK); however, I can't find the driver file anywhere., nor is there an USB available package in the SDK. If someone could point me in the correct direction regarding how to run adb I'd be much appreciative; I have the SDK installed and the adb daemon appears to be running.
A quick second question is if I can get the device to be detected under adb, can mass storage driver and the android driver run simultaneously? Thanks again.
Click to expand...
Click to collapse
Look about 1/2 way down in the first post here:
http://forum.xda-developers.com/showthread.php?t=827209

Two quick questions; any help is much appreciated. As a newbie I am unable to get adb to detect my device; running 'adb devices' always yields an empty list under Windows 7. Searching different threads lead me to the recommendation to uninstall the mass storage device driver with USBdeview and then reinstall with the android usb driver (which is said to be under tools in the SDK); however, I can't find the driver file anywhere., nor is there an USB available package in the SDK. If someone could point me in the correct direction regarding how to run adb I'd be much appreciative; I have the SDK installed and the adb daemon appears to be running.
A quick second question is if I can get the device to be detected under adb, can mass storage driver and the android driver run simultaneously? Thanks again.
Click to expand...
Click to collapse
i downloaded "pda net " to my windows 7 64 bit pc when i was having the same usb issue, it then recognized my adb device(of course you have to uninstall the drivers that windows assigned to it first)... question 2 is yes!
Sent from my VEGAn-TAB-v1.0.0b2 using Tapatalk

You can always try Wireless ADB:
http://www.appbrain.com/app/adb-over-wifi-widget/bohlool.net.wifiadb

Wiki entry on setting up adb here: http://wiki.tegratab.com/index.php/Setting_up_ADB

aver2one said:
i downloaded "pda net " to my windows 7 64 bit pc when i was having the same usb issue, it then recognized my adb device(of course you have to uninstall the drivers that windows assigned to it first)... question 2 is yes!
Sent from my VEGAn-TAB-v1.0.0b2 using Tapatalk
Click to expand...
Click to collapse
You mentioned that you had to first uninstall the drivers that Windows assigned to it first.
Would you please share how you went about doing that? I've been stuck on this part (adb not recognizing my device) for quite a while now and can't seem to get past it.
Any help would be greatly appreciated.

Thanks much for the replies.....
Thanks. I tried each one but only the pad net worked. Regarding the second reply, there was no usb_driver folder in my Android SDK folder. I downloaded the inf file anyway but when I pointed to it during installation it gave me a 'file not found' error although it recognized the driver. PDA net worked fine. The adb wireless widget connected to my PC but the list of devices remained blank.
Thanks again for l the suggestions; perhaps as I become more knowledgeable I'll appreciate why the first and third suggestions didn't work, but I really appreciate your willingness to help.

Duffyxy said:
Thanks. I tried each one but only the pad net worked. Regarding the second reply, there was no usb_driver folder in my Android SDK folder. I downloaded the inf file anyway but when I pointed to it during installation it gave me a 'file not found' error although it recognized the driver. PDA net worked fine. The adb wireless widget connected to my PC but the list of devices remained blank.
Thanks again for l the suggestions; perhaps as I become more knowledgeable I'll appreciate why the first and third suggestions didn't work, but I really appreciate your willingness to help.
Click to expand...
Click to collapse
The reason you had no usb driver folder is because the android sdk was not fully setup. You need to run the sdk setup file in the android sdk folder first and download the rest of it. There are a bunch of different packages available. Follow the prompts.
To connect by wifi you need to use one of the adb wifi widgets on your tablet. When it is ready it should give you an address to connect to.
Then on your pc from a command line change the directory to your tools folder in the android sdk. Then type adb connect "address from adb wifi widget" and hit enter. Should then connect.

Sprdtyf350 said:
The reason you had no usb driver folder is because the android sdk was not fully setup. You need to run the sdk setup file in the android sdk folder first and download the rest of it. There are a bunch of different packages available. Follow the prompts.
To connect by wifi you need to use one of the adb wifi widgets on your tablet. When it is ready it should give you an address to connect to.
Then on your pc from a command line change the directory to your tools folder in the android sdk. Then type adb connect "address from adb wifi widget" and hit enter. Should then connect.
Click to expand...
Click to collapse
Thanks again! The wireless adb directions worked, although I should note that adb.exe is in the "platform-tools" folder and most references suggest it should be in the "tools" folder.
I thought I had installed the SDK correctly using the .exe file but, after downloading a number of packages, no USB package was available. After seeing your post I uninstalled, downloaded the zip version, ran android.bat update SDK and it again installed available packages but no USB; these included Android SDK tools, rev 8, SDK Platform tools, rev 1, documentation for SDK API 9, SDK Platform for vers 1.5 - 2.3, and several sample packages. Under 'Available packages' no USB package is listed, and there no .inf file in any of the installed directories.
Any thoughts? Could the inf file be located somewhere else?

Duffyxy said:
Thanks again! The wireless adb directions worked, although I should note that adb.exe is in the "platform-tools" folder and most references suggest it should be in the "tools" folder.
I thought I had installed the SDK correctly using the .exe file but, after downloading a number of packages, no USB package was available. After seeing your post I uninstalled, downloaded the zip version, ran android.bat update SDK and it again installed available packages but no USB; these included Android SDK tools, rev 8, SDK Platform tools, rev 1, documentation for SDK API 9, SDK Platform for vers 1.5 - 2.3, and several sample packages. Under 'Available packages' no USB package is listed, and there no .inf file in any of the installed directories.
Any thoughts? Could the inf file be located somewhere else?
Click to expand...
Click to collapse
I have seen the same thing with the locations. I just copied the files in the platform-tools folder to the tools folder. Send me a pm with your email and i will send my USB folder if you want.

Hi. I 'figured' it out (if it could be called that). rather than click on 'update all' in SDK manager, I selected Android SDK tools, then clicked 'update all' which gave me a series of archives options, one of which included the USB package. This was very non-intuitive but worked.
Thanks!

Cool.. Don't forget to use the modded info file.
Sent from my VEGAn-TAB-v1.0.0b3 using Tapatalk

adb no longer working

I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?

duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
Click to expand...
Click to collapse
Go into the directory and see if there is a file called adb in there...if it's not check the other folders like tools or something like that i'm at work so i don't know the exact name of the directories...

duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
This is a PC error message stating that the file adb.exe is no longer in the AndroidSDK directory. As zervic mentioned, check and see if the file adb.exe is in that directory.

We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.

duckredbeard said:
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
Click to expand...
Click to collapse
Just reinstall (or unzip if I remember right) the Android SDK into that directory

I started the "update all" in the "installed packages" window. If that doesn't fix it, I shall follow your advice.
Edit: The "update all" didn't fix it.

I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.

duckredbeard said:
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
Click to expand...
Click to collapse
Just so you know that may be a little unstable. It may be worth your while to check the "platform-tools" folder and see if adb is in there, i believe that's where it is by default and it also may be worth your while to run adb from that folder instead of where you jerry rigged it to run. But, on the other hand, it may work the way you have it. You never know. Just figured I'd throw that out there.

While rooting my Nook Color, I came across a recommendation for a free app in the market called adbWireless.
It's AWESOME! No need to use USB or worry about drivers, just install the app, push the big huge button and then type the adb command it shows you to connect to your device. Worked absolutely perfectly on my Nook... haven't tried it on my Aria, but next time I need to ADB something on it, you can bet I will!

did anyone check their tools directory?
ie: C:\android-sdk-windows\tools
LOL

Trying to root but can't get ADB working

I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.

66 people have read this and nobody has any suggestions to help?

i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....

I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?

Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'

juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.

Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer

If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!

I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.

Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer

OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."

ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number

Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?

First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.

Kindle Fire Root so HARD !!!!!!

hello
i just see how to root KF and it's so hard !!
i don't know how to use ADB

This seems pretty helpful in figuring out adb
http://forum.xda-developers.com/showthread.php?t=502010

When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.

http://rootkindlefire.com
Watch the YouTube video or do the step by step method. You do need to download Android SDK and install an USB driver as well. Took maybe 15 minutes all together

Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)

I just did it following this guys video. Quality is great and so are the instructions.
Shows:
-how to install adb
-how to edit the appropriate files
-how to root KF with superoneclick
http://www.youtube.com/watch?v=f409qNgpzSA&feature=related

mewshi said:
When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.
Click to expand...
Click to collapse
I'll second this. It's extremely simple and straight forward. Much simpler than the Windows method if you're at all comfortable with the command line. And as the OP said you don't even need Linux installed you can use a live CD.
Sent from my HTC Flyer P512 using Tapatalk

sum182 said:
Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)
Click to expand...
Click to collapse
This is what I had to do basically.
I created a folder android, and wouldnt let me name it .android
So in command prompt i renamed it, then I put an empty txt file, renamed it to the necessary ini, pasted that line they tell you and it worked first try.

[Q] Another ADB Poblem

I have read every post I can find pertaining to setting up ADB. On the first try, I was able to get my computer to recognize the device as an Android Phone with Android ADB Interface. However, whenever I try to execute an admin command prompt I get the following error:
'adb' is not recognized as an internal or external command, operable program or batch file.. I haven't done command prompts in 20 years (back when that was the only way to get the computer to do anything). It is probably a syntax error but I can't figure it out. I know how to change directories. Do I need the Android SDK and the Java JDK installed? I currently have a rooted Nook Tablet and all I want to do is sideload a few apps on this HD+, I'd rather not root until we get all the 'bugs' worked out. Thanks in advance.
Windows 7 - 64

macultra20 said:
I have read every post I can find pertaining to setting up ADB. On the first try, I was able to get my computer to recognize the device as an Android Phone with Android ADB Interface. However, whenever I try to execute an admin command prompt I get the following error:
'adb' is not recognized as an internal or external command, operable program or batch file.. I haven't done command prompts in 20 years (back when that was the only way to get the computer to do anything). It is probably a syntax error but I can't figure it out. I know how to change directories. Do I need the Android SDK and the Java JDK installed? I currently have a rooted Nook Tablet and all I want to do is sideload a few apps on this HD+, I'd rather not root until we get all the 'bugs' worked out. Thanks in advance.
Windows 7 - 64
Click to expand...
Click to collapse
Go to my HD+ tips thread linked in my signature. There is a file attached there, adb.rar. Download and extract that. There should be three files there. Put them in the folder on your PC where you want to run adb. That error you discussed is that it could not find those adb files in the folder you were running in.
Sent from my HD+ rooted stock using Tapatalk