I am using my laptop for ADB currently, but I want to know if it is possible to run ADB through windows in a Virtual Machine? I have gotten to where I have ADB running and the VM reconizeds the phone but as soon as I type,
Code:
adb devices
There is no response. Side note: I am using VMware and am running Tvall's CM7 on my phone.
Edit: solved was a driver issue
adb works when drivers for adb were installed
did you install drivers from Android SDK Tools?
at second you need turn usb debugging on (settings/applications/development)
5[Strogino] said:
adb works when drivers for adb were installed
did you install drivers from Android SDK Tools?
at second you need turn usb debugging on (settings/applications/development)
Click to expand...
Click to collapse
Yes I know this. The virtual machine knows the device is there(ADB drivers are installed) but in cmd it doesn't work. USB debugging is on, another option is the wireless ADB from CM7, but I have no idea how that works. Thanks for the help.
acseazzu said:
Yes I know this. The virtual machine knows the device is there(ADB drivers are installed) but in cmd it doesn't work. USB debugging is on, another option is the wireless ADB from CM7, but I have no idea how that works. Thanks for the help.
Click to expand...
Click to collapse
When connecting phone through usb debugging there is 'Android USB Devices' section in Device Manager (My Computer / Manage / System Tools / Device Manager). Do you have this section while connecting?
Wireless adb application establishes connection via custom port and adb can use this port to communicate with phone.
5[Strogino] said:
When connecting phone through usb debugging there is 'Android USB Devices' section in Device Manager (My Computer / Manage / System Tools / Device Manager). Do you have this section while connecting?
Wireless adb application establishes connection via custom port and adb can use this port to communicate with phone.
Click to expand...
Click to collapse
In device Manager it has "Android Composite ADB Interface" and a "HTC Android Device" My VM connects to HTC Android device, not letting me connect to it in ADB. Before I connect my device and before it installed the drivers I installed the Google driver package from AndroidSDK. Thanks for your help.
How did you fix it?
acseazzu said:
In device Manager it has "Android Composite ADB Interface" and a "HTC Android Device" My VM connects to HTC Android device, not letting me connect to it in ADB. Before I connect my device and before it installed the drivers I installed the Google driver package from AndroidSDK. Thanks for your help.
Click to expand...
Click to collapse
So how did you end up fixing this? I want to connect my phone to the VM.
This is happening to me right now. I have a VM Windows 7, it can detect a "HTC Android Device" but the platform-tool command line cant detect my phone. Even with ADB USB drivers, platform-tools, as well as HTC-sync installed.
How did you fix it? Please tell me
kazzarok said:
So how did you end up fixing this? I want to connect my phone to the VM.
This is happening to me right now. I have a VM Windows 7, it can detect a "HTC Android Device" but the platform-tool command line cant detect my phone. Even with ADB USB drivers, platform-tools, as well as HTC-sync installed.
How did you fix it? Please tell me
Click to expand...
Click to collapse
I uninstalled all the drivers (with USBdeview) and instead of installing with the Google Driver I used the HTC one for MyTouch 3G. I think I installed the drivers before I plugged in the phone. And also what software are you using to run your VM?
acseazzu said:
I uninstalled all the drivers (with USBdeview) and instead of installing with the Google Driver I used the HTC one for MyTouch 3G. I think I installed the drivers before I plugged in the phone. And also what software are you using to run your VM?
Click to expand...
Click to collapse
I am using Oracle VM Virtualbox. Doing VM Windows 7 under Ubuntu 11.10.
I have been trying a few times in the VM Windows 7. I tried the lastest HTC Sync 3.0.0.0 as well as the older version 2.0.3.3 that worked when I was using full Windows 7.
But in VM, nothing works
The VM win 7 can detect a USB Composite Device, but it cant find the correct driver.
edit:
Oh my god!! hopefully you still havent read this post yet because I just got it working!
In the settings of the VM, theres an option to enable USB 2.0
But to enable that, we must install the Oracle VM VirtualBox Extension Pack
It works!
edit2:
but somehow the transfer speed is really slow...
i guess i will just install windows again dual boot it
Yay! Congrats if I helped at all please hit the thanks button.
Sent from my Dream/Sapphire using XDA
acseazzu said:
Yay! Congrats if I helped at all please hit the thanks button.
Sent from my Dream/Sapphire using XDA
Click to expand...
Click to collapse
Not until you tell me about your VM
I want to know that because at the moment the transfering and intallation of APK files in Oracle VM VirtualBox is utterly slow (comparing with my old Win7 days), I am interested in other alternative VM which might be faster.
I see you mentioned VMware in you first post, I went to their website (link) but I see a lot different products... can you tell me which one you used, can you please tell me more about your VM?
Thanks in adcance.
edit:
Hey there again, I fainlly got VMware working.
I went for VMware Player 4.0.2. But for Ubuntu 12.04, we need a custom patch the VMware before it can run gracefully.
Not I have got it running now, VMware is so much faster than Oracle VM.
Thanks for the suggestsion!
kazzarok said:
Not until you tell me about your VM
I want to know that because at the moment the transfering and intallation of APK files in Oracle VM VirtualBox is utterly slow (comparing with my old Win7 days), I am interested in other alternative VM which might be faster.
I see you mentioned VMware in you first post, I went to their website (link) but I see a lot different products... can you tell me which one you used, can you please tell me more about your VM?
Thanks in advance.
edit:
Hey there again, I fainlly got VMware working.
I went for VMware Player 4.0.2. But for Ubuntu 12.04, we need a custom patch the VMware before it can run gracefully.
Not I have got it running now, VMware is so much faster than Oracle VM.
Thanks for the suggestsion!
Click to expand...
Click to collapse
I personally use Workstation. But for me VMware is alot faster than Oracle VM VirtualBox. Glad I could help
adb driver won't connect
I'm running windows parrallel on my mac. On the windows side I have the samsung drivers downloaded but when I go to root my phone the command line says doesn't recognize. Anyone know away I can get drivers to recognize phone when running virtual on a mac?
Related
Does Eclipse+ADT support HD2 android development?
That is to say,does the USB Driver in Android SDK recognize HD2 in order to enable USB debugging?
thanks.
haha i was wondering the same thing! I am building apps and need mass storage~!
arshcaria said:
Does Eclipse+ADT support HD2 android development?
That is to say,does the USB Driver in Android SDK recognize HD2 in order to enable USB debugging?
thanks.
Click to expand...
Click to collapse
Yes.
I cant get it to work for me im using the google labs app maker thing and it connects to my device and everything just doesnt bring all the stuff over to it only text..
Developing on Eclipse right now and it's reading LogCat no problem.
Metastable said:
Developing on Eclipse right now and it's reading LogCat no problem.
Click to expand...
Click to collapse
so you mean when i connect hd2 to pc and select the drivers from "*\androidSDK\usb_driver" folder, it'll show up in Device Manager windows named ADB interface?
What I did to use my HD2 as a Android debugging Device.
1. Install the USB drivers. I had to "de-recognize" the device first, since I unsuccessfully tried to install the drivers before. Just as explained in h*t*t*p*://*w*w*w*.downloadatoz.com/driver/articles/how-to-install-and-set-up-adb-usb-drivers-on-android.html .
2. Keep the phone connected. The windows will eventually recognize the phone and try to install appropiate drivers. When that happened, I selected to install drivers from a specific location [C:\android-sdk-windows\usb_driver]. Windows recogned my phone and installed the drivers.
3. Run the app from eclipse. The app will automatically download and run on the phone.
I have a folder for android stuff like fastboot and adb that I keep for fixing my phone. I keep the minimum files required for fastboot to work... adb.exe, adbwinapi.dll, fastboot.exe and the 64bit usb drivers.
I used to be able to use fastboot even after formatting my computer (and reinstalling the drivers), but it's been a long time and when I tried to do the same again, it no longer works.
Windows says the driver is not compatible with the device. I download Android SDK Tools to download the usb drivers there. They install, but fastboot still doesn't detect the phone.
I tried following tutorials out there to get fastboot to work, but I tried on 2 HTC Dreams and they don't get detected. What am I missing?
Only thing I remember being different is that I'm using Windows 7 x64 SP1 now and before I was using plain Windows 7 x64.
You need to use the usb driver removal tool and install the usb driver from SDK.
yes you've got my same trouble.
this is my thread.. http://forum.xda-developers.com/showthread.php?t=1032249
i solved with backtrack 3.. don't ask me why because i don't know.. i just have a try with bt3 because i use bring it with me on my pendrive (it can ever be useful )
BeenAndroidized said:
You need to use the usb driver removal tool and install the usb driver from SDK.
Click to expand...
Click to collapse
The old drivers I had were never installed. For some reason, Windows did not recognize a compatible driver. I did download a fresh set of drivers from SDK and windows did install them, but fastboot devices is not listing anything.
P4p3r1n0 said:
yes you've got my same trouble.
this is my thread.. http://forum.xda-developers.com/showthread.php?t=1032249
i solved with backtrack 3.. don't ask me why because i don't know.. i just have a try with bt3 because i use bring it with me on my pendrive (it can ever be useful )
Click to expand...
Click to collapse
I see no reason why I can't use fastboot on Windows if it worked before. Perhaps if there is no other way, I'll try Linux distros.
It sound like there is no compatible driver for Windows 7 x64 SP1. Check google to see may be they might have an updates.
BeenAndroidized said:
It sound like there is no compatible driver for Windows 7 x64 SP1. Check google to see may be they might have an updates.
Click to expand...
Click to collapse
So there is an actual difference between win7 and sp1 in regards to the drivers and not that I set it up wrong?
From my experience on working with Windows. Every version always different. As far as how much different, I can't tell.
If you had it working with W7 before SP1, then there is a change in driver that causing it not to work correctly. Do you required to upgrade to W7 SP1? Or is that your preference?
BeenAndroidized said:
From my experience on working with Windows. Every version always different. As far as how much different, I can't tell.
If you had it working with W7 before SP1, then there is a change in driver that causing it not to work correctly. Do you required to upgrade to W7 SP1? Or is that your preference?
Click to expand...
Click to collapse
Well that's all I can think of. Just wanted to know if anyone else had problems with sp1. I think faastboot should work with my winxp vms.. gonna try that next time I try to use fastboot..
I am having issues with adb getting to work. I have tried every tutorial under the sun. I have uninstalled, reinstalled and stopped windows from automatically updating the driver yet it keeps installing the stupid mass storage driver for it. Any help on this would be greatly appreciated.
Thanks
You didn't mention what version of windows. It is fine for me with XP sp3.
However,if I have virtual box running then I get the driver install dialog.
I am running win7 64 bit I think I might end up trying virtual box with xp on it and if I don't get it then I will be back it seems no one has responded to any of my threads. Any ideas would be great though.
I can't get adb on Ubuntu under virtual box on XP to work. Stop virtual box and adb on XP is fine. Leave virtual box running and adb fails - windows insists on trying to install the virtual box (or other) driver when I connect the NC.
For me, the Nook Color has always be troublesome to get the ADB to connect and work.
I seem to find that the app adbWireless works all the time for me. Instead of trying to connect adb through the USB port which always seems to have driver issues for me, it connects it through the wireless connection. No drivers needed.
bytte said:
I can't get adb on Ubuntu under virtual box on XP to work. Stop virtual box and adb on XP is fine. Leave virtual box running and adb fails - windows insists on trying to install the virtual box (or other) driver when I connect the NC.
Click to expand...
Click to collapse
Hope this help
http://forum.xda-developers.com/showthread.php?t=1329983
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
'USB Debugging' enabled?
Of course. It will install drivers for the ADB device, it just won't be detected by adb.exe.
I tried the 'switch to Photo MTP' mode trick too. I am having no issues with adb to a One XL, One V, Defy, Aurora II or U8800. This is really bizarre.
Do you have java jdk installed correctly?
http://www.oracle.com/technetwork/java/javase/downloads/index.html
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Yep, I too went the virtual machine route.
Ridiculous. The only two developer devices I've owned (Nexus S and Nexus 4) and they've both been impossible to get the adb drivers going...
Passa91 said:
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
Click to expand...
Click to collapse
Yes you have to have installed the java jdk to run adb, it doesn't work without it. Java jdk is supposed to be setup first before you install the sdk so that it finds it. One issue why people can't get adb working is that the path environment variables are not set up and need to be manually entered.
Example of setting your windows path environment variables for jdk version 6 windows 32 bit on Windows Vista.
right-click on My Computer, and select Properties
under the Advanced tab, hit the Environment Variables button
in the dialog that comes up, under System Variables double-click on Path
Add ;C:\Program Files (x86)\Java\jdk1.6.0_18\bin to the Path variable (or wherever the jdk was installed)
Add ;C:\android\android-sdk-windows\platform-tools to the Path variable (or wherever you installed the sdk)
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I posted a solution some time a go find it in my posts
Sent from my Nexus 4 using xda premium
davehunt83 said:
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Click to expand...
Click to collapse
The linux guides include editing the udev rules so that you manually enter the Nexus 4 into the list of devices in order to get adb to recognize the phone. Could be the same issue with windows. I only have the sdk installed on a Linux box and haven't used it on windows since I installed it on a Vista box a few years ago but I would imagine windows would have the same problem recognizing the phone.
Linux Install Instructions
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
RacerXO said:
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
Click to expand...
Click to collapse
You shouldn't even be able to install the sdk properly without having java jdk installed first as the windows installer checks to see if its there.
http://developer.android.com/sdk/installing/index.html
Edit: and by installer I meant SDK Manager, what you use to download and install the android usb drivers. I suppose you can get past the java limitation by just downloading the sdk and copying the needed files into the c directory then using 3rd party drivers but java jdk is what controls the phone once its connected so I don't know how you are getting it to work.
Edit 2: I guess I was wrong in part, I installed the sdk without java jdk on a windows xp box, used the universal drivers linked to above, and it recognized my phone in adb devices and I was able to reboot it. But I can't use sdk manager as it requires java jdk to be installed.
had the same issue... you must be using a usb port on the front/side of the computer
use one of the usb ports on the back, and you should be just fine.
This happens to me too. On all windows computers I have used for ADB and all phones it will work the first few times, and then it won't work no matter what. I can usually get fastboot to work reliably but that is it.
Sent from my Nexus 4 using Tapatalk 2