SDK manager failed to install - General Questions and Answers

Im trying my best to install 4.04 on my Galaxy Nexus because Verizon is taking their sweet time with the update. It says I have to install SDK manager to do this. I have it opened and am trying to download the sdk tools and the google usb drivers but it gives me an error message stating that
The following processes
cmd.exe
java.exe
are locking the following directory
C:/android-sdk-windows/tools
Please close these applications so the installation can continue
I use ctl + alt + del and end the process but it closes the installer
any ideas?

Still an issue? I am seeing the same on Win8 64bit -- I am not surprised as I have an unholy total of eight adb.exe files on my system. Trying to thin them out and keep all of them quiet and dormant while I try to update to v19.
No one device is the same, hence my reason to have more than one adb.exe --

Related

[Q] How to install Market ?

Sorry to be a noob about this but could someone post a how to install on a new Apad?
I've installed superuser already which I assume is working??
This is one of the new IMX 515's Android 2.2 800 mhz tablets with 10.1 flash etc.
Where do I go from here to get the Market installed?
Sorry folks but I'm kind lost.
Thanks for your help.
I got one of those 9.7" iMX515's and I have the same question...
If you need the market installed search the forums for market.apk.
Please use the forum search feature before posting next time.
Have any more questions, msg me on gtalk at androidsamurai.
Sent from my Hacksung - M910 using Tapatalk
I managed to get part way there. Basically I followed the instructions here (http://www.androidtablets.net/forum...tall-instructions-imx515-cnddu.html#post37829)
and here (original post: http://www.padbbs.net/thread-2909-2-1.html).
I had problems getting the adb to work on my Mac, but finally managed to figure that one out:
Download the sdk and unzip in a folder of your choice.
Set your slate to USB debugger "on" and plug in to your mac. I think I didn't actually mount my slate when I did this (neither memory was mounted on my desktop when I executed the process), but have a go and see if there is a difference in adb behaviour.
Run the Unix executable called "android" in the "tools" sub-folder. Then run the "adb" executable.
These should both open up their own terminal window. Then open a new terminal window. The fastest way to insert adb commands is by dragging the adb file into the window and follow up with your adb command.
Start off with "adb shell", which gives you a hash (sorry, my keyboard won't give me the sign) as line start. Then start using adb command lines (drag drop adb into the window, followed by "push", followed by drag-dropping the file you want to push into the terminal window, followed by typing where you want it to go, e.g. /systems/app.
Do this for all the files mentioned and you should be there.
Now, this is as far as I got myself! When I restarted, I had the market app in my app list, but when I start the google sign in service, I continuously get the message "can't connect to server", and I have no idea how to get passed that point. SO suggestions for that one will be welcome!
I have a mac. How do I install a firmware without recovery mode? I don't have recovery mode, doesn't exist on my unit

[GUIDE] adb for your gtab (windows)

hello all,
i had some small trouble setting up adb for my viewsonic gtab, so once i figured it out i thought i'd share.
so far, this is confirmed working only on windows 7 32 and 64 bit. vista should be the same, but i'm not sure, i'll keep you posted. EDIT: we've confirmed these steps for at least vista 32 and xp 32-bit. there shouldn't be any differences between the 32 and 64 bit systems as far as the instructions go.
most of my information comes from nvidia's tegra site, here. that's a pretty technical-minded page though, so i wanted to condense it.
make sure usb debugging is turned on for your tablet (settings -> applications -> development -> usb debugging)
1. open your device manager (right click My Computer -> Manage -> Device Manager)
if you haven't done anything to set up drivers yet, skip to step 4.
2. find your gtab. depending on your previous attempts, this may be under "Android Phone" at the top (Android ADB Interface, make sure it's your tab and not your phone), or under "Universal Serial Bus controllers" on the bottom (called Android somethingorother. should be at the top of the list.)
3. uninstall it. right click, uninstall. check the box that asks you if you want to delete driver software. i didn't need to use usbdeview to uninstall the drivers, but if you're running into issues on this step try it. usbdeview must be run as administrator, thanks droidjunkie.
it looks like most people should just skip right to usbdeview to uninstall any old drivers. like i said, i didn't have any issues using windows' "delete driver software" option, but apparently i was just lucky. rcgabriel recommends usbdeview, and he knows stuff.
4. unplug, and plug your tablet back in. now your device should be under "Other Devices" near the middle (will have a yellow exclamation icon, called NVIDIA harmony). good.
5. hopefully you have the android sdk installed. if you don't, go find a generic guide on setting up adb and then come back. when you have the sdk installed, you need to run "SDK Setup.exe" from where you installed it and use it to download and install the usb drivers (currently r8).
6. open the "usb_driver" folder in your sdk directory. right click "android_winusb.inf" and open it with notepad or your favorite text editor.
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
8. go back into device manager. right click your tablet, select update driver, and click "browse my computer...", then "let me pick...", then "next", then "have disk"
if you're confused on this step, check this post.
9. browse to your android sdk, under the usb_driver folder, and select the "android_winusb.inf" file.
10. of the three choices, the bottom should say "Android Composite ADB Interface". choose it. click next, and allow the driver to install even though you get a big scary red warning.
11. open a command prompt, preferably in the tools directory of your sdk. type the following:
Code:
echo 0x955 > "%USERPROFILE%\.android\adb_usb.ini"
and hit enter. it will just return a new prompt line.
12. test it out.
Code:
adb kill-server
adb devices
you should see your device's serial number. all is well. congrats.
let me know if i should add or clarify anything here. thanks!
Just in case anyone doesn't know what ADB is:
http://developer.android.com/guide/developing/tools/adb.html
Thank you so much! Great info!
this is great! thanks for the concise writeup
I had trouble too. I was unable to get uninstall device to work and put the device under Other devices. I was advised to use usbdeview from pershoot. I used this program to remove the device and was able to get it moved to Other devices in Device Manager.
HTH
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
THANK YOU!!! after trying many different guides this one worked...other then the fact that I had to right click usbdeview and click "run as administrator" in order to delete the driver it keep installing when i would plug in my tab. I am on windows 7 32 bit, for anyone else having problems getting adb working that is using windows 7.
Thanks
I am finally connected via adb.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined by iammuze, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
I had the same experience on Windows 7 that you are having now. Like you, I tried following all the instructions similar to the ones listed above plus advice from other forums and still could not get it to work. I was finally able to get mine working after I discovered Windows still had some drivers from previous failed attempts stored in its system files. These old drivers were interfering with the proper installation of the new usb driver.
To get rid of the old drivers completely, do a file search for the file named android_winusb.inf in your Windows/System32/DriverStore. If your search results show several file folders with the same driver, try to delete each of the those folders completely. After those folders are deleted, you can do a clean install following iammuze's instructions.
NOTE: To delete those folders you will have to change the folder permissions. It won't be easy to do, because Windows doesn't like having its system files messed with. Unfortunately, I can't give you exact instructions on this, because I don't currently have a Vista machine.
rlapela said:
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Click to expand...
Click to collapse
where does your gtab show up under device manager?
Thanks, it worked great! ADB screen shots!
Look at this mess I have crammed onto one page.
[UPDATE: Problem solved: I had two versions of adb in my PATH and the old version (1.0.20) was being executed instead of the new version (1.0.26). Apparently the old adb silently fails and returns no devices when used in conjunction with the current drivers. I worked this out by accident. But if you're looking for ideas, there are lots in the ADB for Dummies thread: http://forum.xda-developers.com/showthread.php?t=502010 ]
Hi All
I've been banging my head against this for hours with no luck. I can't get adb to recognise my gTablet. Here's what I've done:
I'm on WinXP. gTablet is running zTab Clean 3.0
- I've downloaded the latest ADB USB drivers using the Android tools (driver verion 4.0, December 12 2010).
- I've made the modifications to android_winusb.inf noted above.
- USB Debugging is enabled on the gTab
- adb_usb.ini contains a single line containing: 0x955
I've followed various instructions and the driver install ~seems~ to go ok, but adb doesn't work.
Windows Device Manager lists the following devices which are associated with NVIDIA Harmony:
Android Phone > Android Composite ADB Interface
Universal Serial Bus controllers > USB Composite Device
Universal Serial Bus controllers > USB Mass Storage Device
USBDeview lists three devices:
NVIDIA Harmony NVIDIA Tegra 2 USB Device
NVIDIA Harmony USB Mass Storage Device
NVIDIA Harmony Android Composite ADB Interface
The first is listed as connected. The others aren't.
When run adb i get this:
> adb kill-server
> adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
No devices are listed.
I have tried many combinations of uninstalling these devices (with Device Manager and with USBDeview). When I reconnect I get prompted to install drivers. I have tried installing at this point, cancelling and then installing in Device Manager, not cancelling so the Plug and Play window stays open and uninstalling with device manager. None of this has worked. Also the device drivers seem to linger on my machine as they seem to auto-reinstall even after I have uninstalled them (I've also tried the suggestion of searching and deleting the .inf and .dlls from C:\Windows -- that didn't work out either).
I have also been careful to make sure adb is not running when I change the drivers. I have tried rebooting the computer and the gTablet after various installs.
The only way I can get the gTablet to appear in "Other devices" is to plug the device in (the PnP window pops up, I leave it open and ignore it). Then I delete the drivers in USBDeview. Then I unplug and replug the gTablet. Now there is one device in "Other devices": NVIDIA Harmony. Problem is, if I right-click "Update driver..." it won't let me install from the Android .inf, it says "The specified location does not provide information about your hardware." and forces me to install "USB Composite device". Once that's installed, two more NVIDIA Harmony devices appear in "Other devices". The first requires me to install "USB Mass Storage Device" (once again won't accept the .inf). The third does allow me to install "Android Composite ADB Interface". That gets me to the point where the drivers are loaded as listed above. But adb still lists no devices.
When I first started trying to set this up I had old drivers for the original HTC android phone installed. I deleted these with USBDeview.
I think that's all the information I have. Please let me know if you have any suggestions, I'd love to get this working.
Thanks!
A real plus would be screenshots, I'm getting a little confused at the device manager window, especially the part where it's supposed to give you the option "let me pick" > "have disk" > locate the .inf > choose the last of the three choices
I'm not getting any of those windows/options. Also, when I uninstall it, unplug the gTab, and plug it back in, it just re-installs the default Tegra driver. Any help?
Right now my device is showing up under "Disk Drives" as "NVIDIA Tegra 2 USB Device", and then also under "Portable Devices" as "G:\"
EDIT: Fixed! (Sorta)
I found another forum that told me that in Device Manager, select "Add Legacy Hardware" from the "Action" menu. After going through there, I was able to complete the steps you told me to. If anybody's having the same problem I had before, I am using Windows 7 64-bit, so that may be part of the problem? I'm not sure. But it's installed now and in Device Manager it's under the "Android Phone" section as "Android Composite ADB Interface".
However this raises a new problem, it has a yellow triangle with an exclamation mark over the icon, and it comes up with the error "Error code 10: Device cannot start".
Any help?
you edited the .inf file to contain the three lines specified, and selected the modified driver when adding the driver, correct? i'll try to add some screenshots for the dev manager section
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Hi,
FYI, one thing to be careful of: In the thread where there's info about adding the 3 lines to the .inf, there's also a full .inf file.
If you try to use the full .inf file, note that it has references to various DLLs, which may, or may not match the DLLs in the driver install directory, so, if you use that full .inf from the thread, you have to adjust those DLL references to the ones for the DLLs you actually have on your machine.
In my case, I found it easier to just add the 3 lines to the .inf that came when I installed the USB driver files from the Android development website, which then worked.
Just an FYI...
Jim
iammuze said:
after right clicking your gtab in device manager and selecting "update driver software" you should follow these steps to get going on win7 64-bit
http://dl.dropbox.com/u/5541925/drivergtab.png
Click to expand...
Click to collapse
THIS IS PIVOTAL... This is where I had the hang up. Make sure that you are looking at iammuze's pic here, especially the 2nd image. by default most of us are used to just pointing to the correct directory where we DO have the modified .ini and it grabbed the wrong one. You HAVE to select 'let me pick'
Thank you iammuze for pointing this out. I think that's where most get lost. It haunted me for weeks as I was just 'skinning' through directions and missed this important step!
Just a quick suggestion - instead of trying to hunt around and fix drivers that are already installed and broken, I highly suggest using USB Deview (http://www.nirsoft.net/utils/usb_devices_view.html) which lets you nuke out the old drivers easily on a Windows Vista/7 machine.
I had old ADB drivers from my Nexus One sitting around, and I was unable to uninstall stuff with Device Manager.
Just run USBDeview **as administrator** if you are on Windows Vista/7 and you can uninstall old drivers for USB devices with a single click (in this case, just nuke any old Harmony drivers or other ADB drivers). Then the next time you plug in your G Tab, you should be able to select the proper drivers as suggested in the first post.
doesn't work
So i have also been trying for days and can't get it working right.
Running Windows Vista, have ADB installed, and can connect to other Android devices. I have setup the android_winusb.inf properly, but when I connect my device it shows up in Device Manager as a Portable Device->Tegra.
I have uninstalled the tablet and every other android device using usbdeview as admin
I have searched and destroyed all other usb.inf files.
i am running VEGAn-1.0.5B
No matter what happens, as soon as I plug in the tablet it immediately installs it as a Tegra Portable.
any help is appreciated!
that's very odd, i haven't seen that device description before. it doesn't sound like a vista issue... do you have another computer with vista on it anywhere that you can plug your gtab into? just to see what it reports to dev manager on a super clean system.
Old drivers were conflicting from previous installation attempts for me as well. All is working well once USBDeview was finally able to uninstall the device, however, it took multiple attempts and reboots for it to actually remove them. All is well now, and my Device is connected to the ADB. Thanks Everyone!

[Q] Not able to install the SDK packages, coz SDK blinks for a sec and then closes.

So, I am sorry, if this is a stupid question, I am novice here. I am trying to run SDK manager on windows 7, 32-bit os. It's already installed. Whenever I try running SDK manager, It flashes for a sec and disappears. When I tried executing android.bat from tools, what I got was :
C:\Program Files\Android\tools>android
[INFO] Starting Android SDK and AVD Manager
'xcopy' is not recognized as an internal or external comman
operable program or batch file.
No command line parameters provided, launching UI.
See 'android --help' for operations from the command line.
Exception in thread "main" java.lang.NoClassDefFoundError:
ts/Display
at com.android.sdkmanager.Main.showMainWindow(Main.
at com.android.sdkmanager.Main.doAction(Main.java:2
at com.android.sdkmanager.Main.run(Main.java:99)
at com.android.sdkmanager.Main.main(Main.java:88)
I have java 6 up date 25 already installed and the path is already added to environ var. Also I am interested in developing for android, If anybody is interested in showing me how, I wud be very greatfull. Thanks in advance. Plzzzzzzz........ HELP.
Currently Using : HTC Desire Z.
And yes, I am having eclipse 3.2 already installed on my system. PLzz help................................., somebody......................, anybody.
General tip
If you double click some techie program on Windows and see it just appear and disappear like that, it usually means that this program is meant to be run in a command line window.
So go to All Programs -> Accessories -> Command Prompt and open that
Then go to wherever that program is installed and run it from there.
Oh, and note that Android development needs the JDK, not the JRE version of Java, The JDK contains all the extra parts needed for Java software development in general, including key parts needed by the Android SDK.
While the JRE can be downloaded from www java com , the JDK is only available from java.sun.com .
P.S.
Sorry for not making proper links, but I have not made enough posts to allow them yet.

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] Having trouble installing adb for Windows

Problem getting adb installed.
Installed the JDK.
Installed the Android SDK, revision 15.
Now I am stuck, not sure how to install ADB, don't know if it's done from within the SDK manager.
I've got a Rogers i727R. It's running 2.3.5. It's the stock ROM, rooted. I was figuring that I would have to tick the checkbox in Android SDK Manager for 2.3.5 and download those components, and that would give me everything I need.
But there is no 2.3.5. There is 2.2, and 2.3.3, and of course Android 4.
I do have drivers for my phone installed through Kies if that matters. Any pointers in the right direction would be appriciated.
Harry
Thanks goes to Silver<<<<<<
1- Like always enable your Debugging. you can enable that by going to your Settings -> Application -> Development
2- Install the android SDK . you can download it Android SDK
3- Extract the SDK to any folder, Example : C:\Android
4- Make sure you have the drivers installed- In that way your OS can talk to your phone!
now that everything is installed we can go ahead and perform a command :
1. Open the 'run' dialog by pressing the 'Windows' + 'r' buttons on your keyboard (minimize the browser & other non-windows programs) 2. cmd (this will open a DOS prompt) 3. cd c:\Android\tools (go to the directory where you extracted the SDK) 4. adb shell 5. Now you'll see just a '$' 6. logcat
You can now just press the power button on your phone to see what happens. It displays everything the device is doing.
So the thing is: leave your device connected for a while and see what is actually going on when you're not using it. Boom
__________________
OP,
Just install the 'Tools' listed there in the sdk downloader. you dont need to worry about anything else
It seems to also want me to install the Google USB Driver package. Any reason to do that?
harry_fine said:
It seems to also want me to install the Google USB Driver package. Any reason to do that?
Click to expand...
Click to collapse
just do it, it wont affect anything negatively
By the way, it worked great. I can now talk to my phone using the emulator on my PC. I see the list of adb commands, lots of stuff. Seems I can even install apk files, run a remove shell. Very cool.
Lol good luck

Categories

Resources