Related
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).
i am trying to install the driver for my mytouch.
when i plug in my phone for it to install the drivers, all the drivers install normally except for the adb driver.
this is the error message i get:
"C:\Windows\system32\wdfcoinstaller01005.dll is either not designed to run on Windows or it contains an error. try installing the program again using the original installation media or contact your system administrator or the software vendor for support."
i tried searching for this problem and found nothing, anyone out there have the same problem? it must be some issue with vista, ugh
i also get this screen after it fails.
Hi all,
I am noticing something with nexus s.
When in recovery or in normal homescreen, my nexus s communicates properly with adb commands
But there seems to be no communication from the nexus s when in fastboot mode.
Everytime I enter a fastboot command, I always get a "waiting for device" and nothing happens.
Am I missing something?
Thanks.
Heeter
If your PC is running Linux then you will need to be root.
No I am running windows 7
I got the Android 1.0 driver. Windows Device manager recognizes that my phone is hooked up,
But when I type in "fastboot devices" it is not listed there.
Thanks
Heeter
When I hook up my Nexus S in fastboot mode, I see this at the bottom:
Code:
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Everytime I unplug/replug USB wire, another "STANDARD_SET_CONFIGURATION" line gets added
I type "fastboot devices" into fastboot, and my Nexus S does not show up.
The phone is currently unlocked, but I would like to lock to reset it and start from factory rogers setup again.
Any help would be greatly appreciated.
Thanks
Heeter
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
rubbamade said:
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
Click to expand...
Click to collapse
I do have that already, rubbamade.
My Device Mangler is recognizing Android 1.0, and has the drivers for that I took from PDAnet.
The PDAnet itself couldn't install properly, so I extracted the drivers from the package and manually installed them through the Device Mangler.
I still cannot connect to fastboot.
Heeter
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
I guess you made your decision already in getting rid of windows lol. Anyway goodluck with the fastboot issue. And I hope the 3G issue is looooooog gone from your life. Take it easy
Arnel
Sent from my Nexus S using Tapatalk
LOLOL,
A whole bunch of thanks for that radio to you again
Heeter
Good choice ditching windows. Lol
Offtopic: how is debian compared to Ubuntu concerning repo n 3rd party drivers? Seriously considering switching to debian since Ubuntu adopted the crapy Unity
Sent from my Nexus S using Tapatalk
The driver isnt right if your phone wont show. You have to let windows find the correct driver out of the drivers you point it to. Either point it to x64 or x86 directory only. No further. Windows will find it.
Go to the fastboot thread in development and get the drivers.
Uncle Jimmy says hello
Heeter, it's maybe a bit late but unless you're really strapped for disk space you can keep Windows and create a separate partition for Linux, using the grub bootloader to choose between the two. I'm a Linux user myself (mostly Arch but I love to test most new distros) but I have lots of disk space and I keep an up-to-date Windows 7 installed for testing purposes and gaming.
Since - I have to admit it - I suck at most games, my Windows doesn't get used much but I don't begrudge the space it takes up. On Debian you should have less trouble with the adk and drivers - here's a good post at Howtoforge about using the adk http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-debian-squeeze
Heeter said:
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
Click to expand...
Click to collapse
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
bender_123 said:
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
Click to expand...
Click to collapse
I tried that like 50 flippin times! everytime, PDAnet stays locked up during the pulling driver area. I have come back half hour later, still not complete. Then, when I unplug the cable, it spits out an error, and uninstalls itself.
What I ended up doing was, during the PDAnet install, it creats a root folder in C:/Program Files/PDAnet (or whatever it is). Now when it got stuck there, I went into that root folder, copied the "usb-win" driver package from there and set it aside. Then I went into the Device Mangler, and right clicked and manually installed the PDAnet driver.
Hiya Gun26, Thanks for that link. I am actually a site supporter on that site, if you search up "Heeter" over there. Been for a couple of years now.
I guess I could go back to dual booting, haven't done that in a long while either.
Heeter
That was just a suggestion about the dual booting - if you enjoy gaming, why give it up? Linux and Mac may be great (and BSD let's not forget) but for gaming it's either Windows or a console. I don't think you'll have any trouble with the adk and drivers on Debian. Good to hear about your connection to Howto Forge - it's a really useful site.
Thanks for that Gun,
I haven't had time to move back to Debian, and I really do like gaming once in a while.
I should be up and running dual boot this weekend.
Thanks again, guys.
Heeter
i'm having this same problem, it's rather annoying
Hi To All Members. My HTC Explorer is unable to communicate with Windows 10 (64 Bit) in Fastboot Mode. Although i have installed the propers drivers for my Pico. In Device Manager, HTC Explorer is recognized as "ADB INTERFACE DEVICE" but whenever i connect it in FASTBOOT MODE. My PC says"Device Not Recognized" . I am using Windows 10 (Enterprise) and tried different USB CABLES. Also, whenever i connect it to install applications with APK INSTALLER. It Says "Connection Exception". .
Any help would be appreciated
help me tooo
My HTC sync is not recognising my device
Although the phone shows fastboot usb the computer doesnot recognise it
i am trying to unlock my bootloader but in cmd after the "fastboot oem get_identifier_token" command
I only see "<waiting for device>''
plZ HELP!!!!!!!:crying::crying::crying:
Hi their seems to be an error with usb registry since Windows 8 so some devices are not being recognised properly, thankfully their is a fix that works for Windows 8/8.1/10 right click on the attached Fasdtboot.txt file and "save target as" change the drop down option from "text" to "all files" then change the file extension from .txt to .reg (Fastboot.reg) so it can be added to your registry, once done simply double click on it and add it to your registry, then installed your drivers via device manager for fastboot and adb.
anonymous-user said:
Hi their seems to be an error with usb registry since Windows 8 so some devices are not being recognised properly, thankfully their is a fix that works for Windows 8/8.1/10 right click on the attached Fasdtboot.txt file and "save target as" change the drop down option from "text" to "all files" then change the file extension from .txt to .reg (Fastboot.reg) so it can be added to your registry, once done simply double click on it and add it to your registry, then installed your drivers via device manager for fastboot and adb.
Click to expand...
Click to collapse
Tried It. Same issue persists
syedbilal07 said:
Tried It. Same issue persists
Click to expand...
Click to collapse
Should work, just make sure your manually adding the drivers back in device manager one for adb and one for fastboot. (right click on unknown/malfunctioned device update driver, point to drivers)
I have manually added registry key and also installed drivers but it says, windows has determined the best driver for you and it is up to date. Feeling hated with windows 10
Try to update your windows ...
Fastboot working fine in my window 10..PC..
I am using enterprise edition.
Please can you properly guide me about every step with screenshots. I am trying to solve it since many days but now frustrated. Please, i will be thankful to you @vaibhav1
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.