I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
LOL, I just switched back from Ubuntu to Windows 7 just to see how things have progressed. There are so many little Windows 7 quirks that drive me crazy that drove me back to Ubuntu almost instantly. Give Linux a try. A good starting Linux OS would be Linux Mint:
http://www.linuxmint.com/index.php
I had a similar issue when I tried it. Despite the fact that there are 64-bit drivers for Vista/7 available, I don't believe they actually work for ADB currently. I'm pretty sure everyone who has ADB working is using Windows XP 32-bit.
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
ch4dr0x said:
I apologize if this is not the right forum and I would request that it be moved, not deleted, if possible if its the wrong forum. I'm kind of stuck here.
Have a bit of an interesting situation. I am running Windows 7,
got the USB driver successfully installed... boot up the command prompt and BAM:
C:\android>adb remount
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
C:\android>adb devices
List of devices attached
Here is the weird thing...
C:\android>fastboot devices
HT97JLV05321 fastboot
It looks like the fastboot is recognizing that my phone is attached but the adb shell will not. Any ideas what the issue could be?
Click to expand...
Click to collapse
I faced the same problem a few days ago. I have Windows 7 Ultimate x64 and in a first installations the drivers work fine and the device has been displayed, but BAM when I try to use ADB no way.
After many tries I resolved the issue running the Command Prompt as "Run as administrator" and VOILA worked fine.
I hope this can help you.
ch4dr0x said:
I actually burned a copy of Ubuntu that I was just going to run off of the CD. I'll give that a shot and see if it lets me do what I need to do. Thanks for the quick responses.
Click to expand...
Click to collapse
Try Mint instead of Ubuntu. Mint is Ubuntu based. The big difference with Mint is that it already has all of your codecs installed - great for beginners.
If you installed first the htc sync, you have to remove the current drivers..
and had the drivers from the androidsdk pack! There's is a a lot of program who delete usb installed hardware/drivers.. delete all from htc on this programs!
Hope this solves ur issue!
I use Win7 64bit(rc1) .. i have the amd64 driver installed..
I see the phone from adb (not fastboot) when it's normally connected with USB debugging turned on.
I see the phone from fastboot (not adb) when it's in fastboot mode.
I have no choice but to laugh at myself, just realized I was IN FASTBOOT on my phone and not recovery. Fail me.
Now if I could just edit this apps2hd code /sigh.
ricardomega said:
If you installed first the htc sync, you have to remove the current drivers..
Click to expand...
Click to collapse
and remove htc sync, there are a process than cause problem with adb (i don't remember the name)
I kill this process and adb 100% work fine, or unistall HTC Sync..
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
ricardomega said:
GOOGLE KNOWS EVERYTHING!!
http://www.google.com/search?hl=en&rlz=1C1CHNB_enUS326US327&q=remove+usb+drivers+programs+android+htc&aq=f&oq=&aqi=
Click to expand...
Click to collapse
Except that... that wasn't my issue Its ok thanks for the input.
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
parrot5 said:
I am using Windows 7 final (RTM) (64-bit) and also Windows 7 Beta (32-bit) on two different computers. They all work fine with adb commands.
Click to expand...
Click to collapse
The same confi, the same result
Everything works fine here with Win 7 Ultimate x64, you just install the driver in the Android SDK.
make sure u have usb debugging checked... cause i have windows 7 rtm ultimate and my adb works fine... i just loaded the needed file into windows/system32 and also put my fastboot.exe in there and added the tools folder to the environment variables and have no problems
What do I load to the system32 folder? I can't install the drivers from the SDK package. Is there a way to overwrite the ones Windows automatically installs and thinks is more up to date?
detonate said:
"error: device not found"
I can't get ADB to work with my Windows 7 X64 Ultimate. Windows automatically install a driver for the phone when I plug it in. When I try to install my own driver with the one in the SDK, I get:
"....doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Doing a update to the driver, it says the one I have installed is already up to date.
I have the latest Win 7 with all important Window updates.
Click to expand...
Click to collapse
Make sure your phone is in recovery mode and NOT fastboot mode.
Finally, I experienced that error you people had been reporting. It MAY have to do with the HTC Sync driver, as suggested, but it really had worked fine with other roms before, so I am not sure. I tried uninstalling and reinstalling the driver, tried to push the ADB driver manually, but that didn't work. And, before I try to uninstall the HTC Sync driver as suggested (I don't even know if I have that installed), I got it working by just plugging in another USB flash drive. Go figure.
So for anyone still having the issue after trying all other solutions, try this bizarre one:
1. Go to device manager and uninstall the HTC disk drive device. (This alone won't work, I tried)
2. With phone still plugged in, plug in a USB disk drive (or maybe just any USB device?) into another USB port.
3. Suddenly Windows 7 detect that unknown ADB driver, as it should. Now you can go ahead to install the correct ADB driver.
As a side note, this computer running Windows 7 Beta/RC have had a lot of problems with USB disk drives in general. The problems disappear after Windows 7 RTM (final).
for the life of me i can not get the drivers installed on my netbook with windows starter 7. can anyone help me with adb drivers.
Did you download the Android SDK and download the ADB driver off of it?
please, android sdk tools and adb is many many mb of software and not all is important for fastboot options... can someone please post the drivers only necessary installable on windows 8.1 x64 (tested) so a newbye can mod very simply?
same thing for fastboot motorola, please, can post only necessary and tested for windows 8.1 x64
very very thanks
Wrong thread dude.
You'll find your answers here in Q6.
No need to download the complete SDK.
You need the original motorola drivers only to flash sparsechunk partition.
Here they are.
Edit: Motorola fastboot attached to this post.
Ever since I installed the windows 10 upgrade on my desktop computer, it doesn't recognize the oneplus one anymore. It was working fine in windows 8, and now the device manager shows a USB composite device that is in yellow status failed to start. I have tried pointing the driver update to the google usb driver from the android sdk and that fails, insisting the proper driver is already loaded. Any ideas on this?
if I turn off android debugging on the phone in developers options, it cycles over and over that device is not recognized. I have the samsung drivers from previous posts in this thread installed.
Are you using MTP or PTP? I think I had to move to PTP to get it to work for both access to the storage and for ADB.
i dont have any problems if i connect my one plus to my pc with windows 10
Windows 10 is very buggy and im having problems with it on my laptop and when trying to use bootcamp it says my partition osnt formatted correctly.
Sent from my SM-N910V using XDA Free mobile app
wmunn said:
Ever since I installed the windows 10 upgrade on my desktop computer, it doesn't recognize the oneplus one anymore. It was working fine in windows 8, and now the device manager shows a USB composite device that is in yellow status failed to start. I have tried pointing the driver update to the google usb driver from the android sdk and that fails, insisting the proper driver is already loaded. Any ideas on this?
Click to expand...
Click to collapse
Any screenshots?
madchainsawer said:
Windows 10 is very buggy and im having problems with it on my laptop and when trying to use bootcamp it says my partition osnt formatted correctly.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
What you mean is Bootcamp doesn't support Windows 10 yet. Give Apple 5 years and they may patch it.
Had no problems at all with Windows 10 on 4 machines.
Try to delete Drivers and clean all the install again
I made a clean install of Windows 10, installed the standard Google ADB drivers, then the Samsung ADB drivers, connected the phone to the PC, went to the device manager and replaced the "unknown ADB device" by "Samsung composite ADB device" driver. After doing that, it recognizes perfectly the phone either in MTP, ADB or Fastboot modes with no issues at all. I always did it this way in clean installs of Windows 7 and 8.1 and works exactly the same in Windows 10. Try it this way, it will work.
Enviado do meu A0001 através de Tapatalk
I keep trying to install the fastboot android drivers on windows 10 but every time I connect my shield tablet original to windows 10 laptop. It's already recognized and is put under the Category "Universal Serial Bus Devices" as the name "Shield Tablet". Then after I try to install the adb drivers, I try the command fastboot reboot, but it stays at "waiting for device". What should I do now? Im just trying to flash the official build version of TWRP on my Shield tablet original WIFI. Thanks for the help!!!!
Grab the Shield drivers from here: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
koop1955 said:
Grab the Shield drivers from here: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Click to expand...
Click to collapse
That is only compatible with windows 7,8,8.1
RunicGamer said:
That is only compatible with windows 7,8,8.1
Click to expand...
Click to collapse
Did you try installing them? I am running Windows 10 and have those drivers installed.
Here is a guide to installing drivers on Windows 10: http://en.code-bude.net/2015/08/19/how-to-install-unsigned-drivers-in-windows-10/
I had to do the manual install on Win10. Hit browse, show list, pick folder, etc. I think it comes up as Android Device Interface or something to that effect.