Can't figure this one out. ADB worked fine for a long time, now it asks for ADB driver every time I connect my phone. Even if I install the driver again, it will ask for it again the next time.
Related
Ok i made a post and it was moved to trash and it says i dont have permission to post there so ill just move it here.....
Ok well i have been trying for like 2 hours now to get ADB to work. I followed all the guides, installed the 1.5 SDK and everything even did the Enviroment Variable thing as well. When i plug in my G1 i dont get any popup of a new device or anything. In device manager there is not ADB as well just Android Phone and when i uninstall it, it installs again on its own when i plug the phone in again. I went to cmd and typed in adb shell but i get "device not found".
Anyone know whats wrong? Btw im using Windows Vista SP1
I went into fastboot and that gave me the new driver notification so i have fastboot working but when i go to ADB i get device not found and device manager finds my phone as a universal usb device or w/e. Why wont this work?!?!?!?
It sounds like you didn't install the drivers.
Read this (I wrote it). You should have adb working in no time.
http://androidcommunity.com/forums/f28/what-is-adb-made-easy-17732/
Did you update the driver for the phone (should currently be showing as one of the USB Composite Device, IIRC) with the ADB driver included in the SDK (android_usb.inf in <sdk root directory>\usb_driver\)?
If you are using a 64-bit edition of Vista, alternatively, you can try the 64-bit signed driver found here. Also, you can try the updated driver I have attached.
Well, if you used your phone as a card reader at any point before you enabled USB debugging, then you'll have to uninstall the USB Mass Storage Device associated with your phone first. After that, unplug and plug the USB cord back in and it'll install the USB Mass Storage Device and then it'll ask about the ADB interface. That's your chance to install the driver that everyone is talking about but didn't spend the time to explain how to get there if you were in this situation...
never mind i got it. I used a program to uninstall all the Android USB drivers then i plugged it back in and it worked. Thanks for the help guys!
I can't seem to figure out what happened to my ADB driver. I installed HTC Sync to use USB tethering and found that ADB no longer worked. I checked the drivers and found that the ADB driver is missing. I uninstalled HTC sync and the driver, plugged in my phone and the phone automatically installs the driver for HTC Sync. Tried to perform "adb remount" and it gives me "error: device not found".
I am running Windows XP SP3 on my computer. Cyanogen 4.2.3.1 with the Buuf theme. If somebody could help me get ADB back I would appreciate it.
Anybody? Any Suggestions?
ccunningham83 said:
Anybody? Any Suggestions?
Click to expand...
Click to collapse
YOu have to reinstall the driver but don't let it choose the driver for you tell WIndows that you'll do it manually and select the win32 driver in the SDK tools.
That being said you aren't going to be able to use HTC Sync anymore.
Thanks for the reply. How can I manually install the driver? I uninstalled the HTC sync driver, plugged my phone in, and the driver automatically installs. It never gives me a chance to browse for a different driver. If there is some way I can force the driver to install without connecting the phone, that would probably do the trick. I would much rather have ADB than USB tethering anyway.
Nevermind. Next time I will google before I ask how to do something.
If anybody else has a similar problem, just google how to install drivers manually and manually install the ADB driver.
Hey, i have had this problem for a bit now, but it is really starting to bug me.
I have a dual boot computer, one is fedora, the other windows 7. When i decided to root my nexus one, i did it through windows, so i got the SDK, installed the drivers and rooted the phone.
Some time later (after flashing and restoring from desire rom back to CM 5) my computer can no longer recognise the device properly Windows will say it fails to recognise the device (code 43), and will not let me re-install the drivers. Saying they are up to date even after i uninstall the drivers then re-install them.
I have given up on fedora too, since no command ever seems to work on fedora beyond yum install xxx. Trying to get "fastboot devices" in fedora brings up "command not found" or something to that effect.
I wouldn't be too worried, but not everything comes as an update.zip, and i would like to try out the undervolted kernel some time.
Note: i can still mount the SD card fine.
EDIT: i can Mount the SD on Fedora, but not windows.
Things you can try out:
1. Completely uninstall and remove the driver from the system and connect the phone and install the drive when prompted. (try in safe mode as well)
2. Try other USB ports.
3. Try turning off USB debug, connect the phone and then turn on USB debug.
4. Try on another PC and rule out any problem with ur phone.
5. Reinstall Windows!!!
Thanks for the suggestions, i tried everything there short of re-installing windows.
As soon as i plug in the device windows will bring up the error message, it will not call it a nexus one, an unknown device. Any attempt to install the new drivers and windows will say that better drivers are already installed.
I also figured out that it will not work on fedora because it is not configured, but the only guide to fastboot and linux i have found is for ubuntu, and some of the commands wont work on fedora.
I tried it on another computer, an XP, it would not install on there either, i tried to use my mums N1 afterwards to see if it would install, it didn't but there are a number of reasons why it may not.
Any other suggestions? or could someone point me to a fedora guide for fastboot?
I do "adb devices" and nothing shows up anymore... Running Windows 7, running "cmd" in Run As Administrator. Phone USB Ddebugging is on.
Any help would be appreciated. Thanks you.
are you mounted?
I tried both mounted and unmounted...
I had this problem on Windows 7 64bit as well. I have a laptop running Win 7 64 and it's never had the issue. I used my laptop to use ADB for a while but I ended up reinstalling W7 on my desktop (for an unrelated reason), which somehow solved the problem. I think it's probably a driver thing.
Yup, it's a driver thing, happened to me on both Win XP and Win 7. Just re download the newest drivers and install.
...............nvrmnd............
It happens randomly to me too, but I'm on Win XP. Sometimes killing the adb.exe process and restarting it works. Other times I have to reboot my desktop to clear it up (without having to reload the driver).
Hey all, I hope this is the right forum.
I installed the Samsung Drivers on Windows 7 x64 and attempted to install the google Android SDK drivers. I managed to get ADB working, my phone is in debug mode and I've managed to do a lot of cool things and run linux commands with BusyBox. Problem is though, windows keeps screwing it up, so currently "adb devices" will not always show my device, even if I have debug on and such. The phone says USB connected when I plug it in, but after a couple minutes, windows says something to the effect of "Could not install USB Device" or "One of these devices has malfunctions, windows does not recognize it". And in device manager, I cannot seem to get it installed under PCI devices like most guides say, it installs under USB. This sux
I apologize if this is the wrong place, if so, I would be happy if a moderator could move this.
Please note, I think adb was just disconnecting and the solution was simply to type in...
adb connect 127.0.0.1
Thanks