My computer seemed to communicate fine with my D4. I could view/edit the contents of the internal storage, but in my quest to root and install a ROM, I tried installing the USB drivers linked in the FAQ first as written in the root instructions. The install failed and now my laptop can't communicate with it and any time I plug it in, it says driver installation failed. I tried removing the drivers, rebooting, installing drivers straight from Motorola, and their Motorola Device Manager. Nothing is working.
Related
I've searched and tried everything I found but my phone just can't be read as a Mass Storage Device....which means I can't transfer any files.
When I plug the phone in the USB debugging icon shows up on the phone but the option to transfer files isn't there. And on the computer it says USB Device not recognized and it's listed as an Unknown Device.
What I've tried so far is uninstalling the driver completely and plugging the phone back in....some sort of software automatically installs itself whenever I do this. However it still doesn't fix the problem. Also, I've downloaded some drivers from the internet but when I try to "Install driver from specific location" and direct it to the folder, it says there was no updated drivers found.
Help
Here you go
Try searching http://forum.xda-developers.com/showthread.php?t=595150
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?
Am trying to unlock my n1 so I can get to install cyanogen rom but am stuck after installing Android sdk and Usb drivers, am following some steps but am stuck trying to locate the USB driver, this is part of what was stated in the direction (You can check if your Android USB drivers are installed by going to “Printers & Devices” on Windows 7.* (and I think you can check Device Manager for other versions of Windows). I check the device manager on my pc and still didn't locate it,anybody have an idea like where I can find the USB drivers.
this has been discussed 100 times and is also in the "informative links" sticky.
Please do a search. The driver comes with the SDK.
I have the hardest time getting my computer to use the right driver for ADB. When I setup my wife's phone on a vista-64 operating system I first connected with USB enabled and it took me a week of trial-and-error to get the system to use the ADB driver (I don't know the steps that made it work - but it involved several attempts at uninstalling every USB device).
I just got another G1 for a Windows-7 laptop (64-bit) and I did the same thing (hooked up with the USB driver) and I fear another week of trial and error. I know that if I knew what I was doing I could do it in 10-minutes.
Can someone please provide the step-by-step instructions for having it use the ADB driver once it has already found, and is happy with, the regular USB driver? I'm not even sure how to tell which of my multiple installed USB [devices] is for the phone.
Step 1. Install a linux distribution.
cloverdale said:
Step 1. Install a linux distribution.
Click to expand...
Click to collapse
Step 2. Download the SDK and put it in a directory (I use "Android")
install the sdk from http://developer.android.com/sdk/download.html?v=android-sdk_r05-windows.zip
let it update (make sure that usb drivers are selected for download)
plug your phone in
if the drivers aren't automatically installed, point it to the drivers directory (<sdk>\usb_driver)
if your sdk is already installed, just download the drivers using the steps described here http://developer.android.com/sdk/win-usb.html
4.) Give me a huuuuuug!
Windows 8.1, Rooted 4.4.4
I have recently done a factory reset and at some point my computer stopped recognizing my phone. If I let windows run through its own attempt at installing the driver, its recognized as a generic Samsung android device which Windows lists as a modem.
I have read the other xda threads, downloaded drivers from samsung site, kies, installed, uninstalled, rebooted, checked, unchecked options including USB debugging (which is not even what I'm trying to do), deleted all non-working driver instances in Device Manager, changed usb cord & port, tried other PC, removing microSD, all to no avail.
I have double-checked what I have frozen in Titanium Backup, but no relevant apps are affected. I tried wiping the cache/Dalvik cache, just because I thought it might help somehow. I'm thinking it must be a phone-side issue because nothing in windows is getting me anywhere. Has anyone here any ideas of what could be the culprit?
Did you try to connect to a different PC?