Hello all,
I'm having trouble getting adb to work in win 7 64 bit...maybe someone can shed some light?
I downloaded and unzipped the Android SDK for windows from http://developer.android.com/sdk/index.html to C:\Android and set the path to C:\Android\Tools
I downloaded Daemon tools lite and installed it
I downloaded Java Development Kit for 64 bit (and the runtime environment for good measures) and installed them
Now, I need to download the drivers for my G1 and utilizing the instructions on the developer website I opened my cmd prompt and typed android and this is the output:
Starting Android SDK and AVD Manager
Access denied
SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
When I go to C:\Android\tools\lib\x86_64\ there IS a swt.jar file in there....
What gives??
GREAT...the second I post this message I have a revelation...
Going through windows explorer to the android.bat file and right clicking it to run as administrator works...
Related
I am running ubuntu and im am trying to install the sdk, i searched on the internet and messed around with it for 2 hours last night and still could not figure it out, it is a tgz file, Any help would be great. Thanks
deleted
Im having the same problem except I have everything installed just need to figure out how to get my computer to recognize my phone
if i remember correctly,cd to the directory where you saved the sdk tarball, then as mentioned above extract it using tar zxvf
cd to the extracted directory and you should see /tools
cd into /tools and you should be able to load the sdk by typing ./android
if you add the /tools directory to your path in your .bashrc, you will be able to type android straight in the terminal to load up the sdk.
hope that helps
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
Alright i have the the sdk installed i just need abd commands to work now
Don't forget to add the tools directory to your PATH
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
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Has winxp, tmobile GT
I had this same exact problem, but I was just able to get it working. First, this website is helped a lot:
http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
Also, make sure you download the Java SDK package from the link given on that website.
Second, when the website says to "Run Windows command line tool (cmd) and go to D:\android-sdk-windows\tool" open command prompt and enter this code:
cd (enter the path to where the android SDK was installed), for example:
cd C:\android\android-sdk-windows\platform-tools
Notice how I entered "platform-tools" instead of just "tools" because this is the folder where the adb file is download with the android SDK. After you do this, you should then be able to apply adb codes (make sure the screen on your tab is on because you will have to accept superuser prompts, therefore your tab needs to be rooted).
Every time you open command prompt, you will have to enter:
cd thentheplacewheretheandroidSDKisinstalled
as stated above before you are able to enter adb commands.
Hope this helps!
@caveman999 is giving good advice. Working in the command window is weird to those who did not use old pc-dos environment.
You have to be in the tools directory or you have to edit your PATH in windows so you can use adb from any prompt.
thnaks for both of you guys i installed the java jdk and also specified the path in environment variables but still error message!
I could only get adb to work error-free when I was in the same directory as adb.exe program. Just change directories cd..(enter) etc until you are in that directory.
tabing said:
Error: adb is not recogzined as an internal or external command, operable program or batch file???
i successfully installed the android sdk 08 and still got this message.
Click to expand...
Click to collapse
I had the same error, until I downloaded and placed the .adb files accordingly.
Source: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
"UPDATE: If it says adb not found or something similar, download the ADB files and extract them into the Tools folder of the SDK (they were taken out by Google in the R08 version for some reason and need to be put back)."
download adb files from here: http://www.megaupload.com/?d=RTEY0Q97
The important thing is to put the files really under the "tools" folder.
When you check out above Source I am sure your problem will be solved
Thank you all problem solved
tabing said:
Thank you all problem solved
Click to expand...
Click to collapse
Glad to here it. Why not hit a few thanks buttons?!
Hello everyone
Have you ever been bored in a borrowed pc and wanting to try out a new library/idea on your android but dont have admin privileges to install all the needed android tools? I was in this exact same situation, so i decided to engineer a solution (After all, i AM an engineering student ) to this boring problem. This solution works almost entirely like a standard Android SDK install (Only downside: Eclipse won't run your application) and has only been tested on Ubuntu Linux so you are on your own on other platforms, but the principle is the same, it might work after all.
Whenever prompted for a platform choose x86 , x64 needs ia32-libs which you cant install due to not having admin privileges
1. Create a directory for all the files and folders (I'll name mine "Development")
2. Download the JDK tar.bz file from http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html (You'd better search for an updated link when you read this tho) and extract it into Development
3. Download eclipse from http://eclipse.org/downloads/ (I used the Eclipse IDE for Java Developers) and extract it into the Development folder
4. Download the Android SDK from http://developer.android.com/sdk/index.html (If you are on windows, choose the zip!. Again, i've only tested on Linux so you are on your own) and extract it into the Development folder
5. Open the tools/android (It's a shell script) file with gedit/any other editor and edit the line containing java_cmd=".." to read java_cmd="/home/xxx/Development/jdk1.7.0_06/bin/java" (This is my case, make sure this line actually points to the place where you extracted the jdk zip, else this will fail)
6. Open a terminal, cd to the location where you extracted the android sdk, then type "./tools/android" and press enter (Without the quotation marks) to start the sdk manager, install the platform-tools package, the Jellybean (4.1) SDK, and any other SDK you may want, then close the SDK manager.
7. cd to the Development folder and run this "./eclipse/eclipse -vm jdk1.7.0_06/bin" (Assuming you kept the stock folder names from the zips) to run eclipse, then install the ADT as described here http://developer.android.com/sdk/installing/installing-adt.html.
8. When eclipse restarts, it will ask you for the android sdk, just point it to the location where you extracted it.
That's it, your eclipse installation is ready for you to write code.
Now, to debug you'll need to do so manually as eclipse won't somehow recognize this workaround to the usb priviliges (Linux won't allow adb to communicate with the phone unless it's ran as root [Which you can't, that's why you are here] or a configuration file [Again, written as root] is present) system so you need to do this to make adb work:
1. Disconnect your phone from 3G (Optional)
2. Connect your phone to your pc via usb
3. Enable usb tethering on your phone
4. Enable ADB over Network on Application settings
5. On the terminal emulator, run "ip addr show" and look for the usb section
6. On your computer, open a terminal and cd to the tools directory fo the android sdk, then type "./adb connect xxx.xxx.xxx.xxx" (Replace the x's with the IP of your phone, as it appears on the output of the previous command. Remember to use the one on the USB section)
7. Verify adb picked up your device by runing "./adb devices", if it lists an IP as a device, you are ready
Each time you want to test your app, export a signed apk from your project (I may write a small guide for that later, google will help you if you dont know how to do it) and run "./adb install xxx.apk" (Obviously, replace xxx with the path to your exported apk). The icon(s) for your main activity(ies) will promptly appear on your launcher. Again, Eclipse won't run nor debug your app using this method. (Maybe it's an SDK bug?)
I know it's not exactly streamlined but it's something for when you are on the go.
Hope you find this guide useful someday. Until next time.
Hi,
I patched the adb source code to allow for syncing a device tree to my local system (e.g. only copy files that are not already copied before) so I can do incrmenetal backups of the phone sotrage and externa sdcard.
The linux binary I build from that source works fine!
However, I also want to build the adb for windows. At first site all seems well, but when I run the adb.exe on a windows host it just does nothing. I just gets back to the command prompt without any output, not even the usage info when you run adb without andy command line options. I added a small debug printf as the first thing it does, but still no output.
So I'm seeking help on hwo to properly build adb.exe.
Here is what I have.
Development environment on a Fedora-20 64-bit machine
Installed the mingw-32-gcc toolset.
Setup 'repo' and downloaded the sdk sources.
. build/envsetup.sh
lunch sdk-eng (also tried aosp_arm-eng and aosp_x86-eng)
make adb -> gets me a working linux adb
USE_MINGW=1 make adb -> gets me an adb.exe (and api dlls) but it just does nothing, no output now window1s errors, nothing
The file type seems fine:
file adb.exe
adb.exe: PE32 executable (console) Intel 80386, for MS Windows​
which is the same as an older working adb.exe I downloaed form xda-dveloppers
Any help is much appreciated,
Thanks
How to rebuild adb tool for mac machine?