I recently replaced my Nexus S with another one and now that I have the "new" one, the USB drivers for ADB and also mountable storage are not working on one of my computers which was working with the old device. It is a problem specific to just this one machine as I am able to successfully mount the USB drive on my laptop using the same cable.
I have the Google SDK drivers, however when I tried to point the unrecognized "Nexus S" under "Other Devices" in Device Manager to that driver folder, it finds nothing compatible. When I reboot into the bootloader I am successfully able to execute commands via ADB over USB, but nothing works when the phone OS is booted. I've tried following a guide I found on Google Groups, and I got the drivers working for a minute after rebooting the phone a few times, but now they are back to not working and I can't seem to change that.
The phone is rooted and running a stock ROM of Android 4.1.2. Any suggestions?
Had the same problem, very annoying. Are you still using the original cable of the NS? I replaced mine with a quality one and that solved all my issues. You could also try to reinstall the usb drivers and/or flash a different rom and see if that fixes it.
Sent from my Nexus S
kwibis said:
Had the same problem, very annoying. Are you still using the original cable of the NS? I replaced mine with a quality one and that solved all my issues. You could also try to reinstall the usb drivers and/or flash a different rom and see if that fixes it.
Sent from my Nexus S
Click to expand...
Click to collapse
The cable I am currently using seems to work just fine when connected to my laptop, so I'm inclined to think the cable itself is okay. I'm pretty sure that the issue is in my drivers, somewhere.
I had 3 cables that all seemed to work fine at my laptop so I ruled out the cable as well. My phone worked fine everywhere but my gfs phone did not, so it had to be her phone. But after buying a new cable eventually it was solved.
But try to deinstall all usb drivers then reboot. The drivers will be installed again automatically (except the fast boot and adb of course), see if that works.
Sent from my Nexus S
[deleted]
OP did you have luck with this - i'm getting the exact same issue - computer will not see my Nexus S at all
bazpaul said:
OP did you have luck with this - i'm getting the exact same issue - computer will not see my Nexus S at all
Click to expand...
Click to collapse
Unfortunately, I did not. I ended up replacing the Nexus S with a different one and the problem went away. :/
Related
Okay I have search XDA and LG AND google search for this problem and have not found any solution to what I'm going through. Here's a little background on my phone
T-Mobile G2x rooted with the ROM HellFire Phoenix V2.1
Before today I was able to mount my SD card to my computer with no problem seeing I've had the phone since it came out. Today my computer showed it was installing the drivers but gave me a message "device drive was not successfully installed...usb composite device failed. Now I have used different usb ports and different usb cables and my computer is STILL giving me the same message!
I have even uninstalled the drivers and reinstalled them and still coming up with the same issue. I even restarted my computer after each and I keep coming to the same issue. Can someone please give me a solution to this frustrating problem? It would be greatly appreciated!
Same exact issue except on 2.2
I think you mean HFP, hfs is only up to 1.7
Sent from my LG-P999 using XDA
What about USB debugging is it checked? try the opposite of what it is with a reboot, also link where the drivers are being downloaded from.
Sent from my LG-P999 using xda premium
mt3g said:
What about USB debugging is it checked? try the opposite of what it is with a reboot, also link where the drivers are being downloaded from.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yeah I made sure USB debugging is indeed checked, and when you say try the opposite meaning what? uncheck debugging...reboot then check it again?
The drivers are being downloaded from the LG Mobile Support tool program that downloads and installs the latest drivers. Which can be found here http://www.lg.com/us/support/mobile-devices/phone-support
I even posted on the LG forum as well, got a response from an employee who told me basically what I had been doing, uninstalling , restart the computer, reinstall, restart again and then connect my device and STILL the same message. I have no idea why its doing this, its never done this before unless there was a new Windows update or something but there hasn't been. Oh and my Windows is Vista by the way in case anyone was wondering.
I used B2CAppSetup.exe From LG. I was having the exact same issue, this solved it. I uploaded it here: http://www.mediafire.com/?e2vnaw5a0ljljj4
EDIT: Vista or Seven - make sure you right-click the .exe and Run As Administrator.
I had the same issue with HFS so I just started taking the card out of my phone and putting it directly into the computer.
I had this issue a while back after re-installing the drivers. Plug the phone in and the little systray icon would tell me the usb composite device failed.
What worked was going to the device manager and installing drivers from there, but instead of browsing to the drivers as I tried many times the solution was letting Windows choose. It popped up with two choices the generic usb composite device and the LG phone. Picked the phone and I was good to go.
Hope this helps someone and if it does please hit the thanks button.
TorrentzRock said:
I used B2CAppSetup.exe From LG. I was having the exact same issue, this solved it. I uploaded it here: http://www.mediafire.com/?e2vnaw5a0ljljj4
EDIT: Vista or Seven - make sure you right-click the .exe and Run As Administrator.
Click to expand...
Click to collapse
Thats the exact program I have been using and I still have the same issue, I'm thinking of just going back to another ROM since it seems to be an issue with HFP then I'm glad to hear I'm not the only one with this issue.
On the stock ROMs you had to set it for USB file sharing only and then actually enable file sharing once it's plugged in. I can't try anything but a stock ROM (running BB 3/2012) at the moment.
Not sure if HF is the same way.....
Antivirus
Once I had driver issues because of an overzealous Antivirus. Try uninstalling the drivers, restart, disable the antivirus, and reinstall.
I have a question for you guys, I tried restoring to a previous Hellfire ROM i backed up thinking that would work and it didn't.
So what happens if I can't get this to work? Without me being able to access my external/internal SD cards I can't load a new ROM or anything even if i wanted to unroot the phone and get another one from T-Mobile I can't or can I?
Is there any other way to restore back to factory settings without connecting to my PC? This is highly frustrating and i have NO idea why my phone and PC aren't working together like they did before in the past.
Did you run as administrator?
Sent from my SGH-T989 using xda premium
Yes i have done everything. Run as administrator, restarting my computer after every uninstall and re-install of the drivers, made sure USB debugging was checked, even restored a previous ROM i saved thru clockwork-mod and when i connect the phone through the USB to my computer i keep getting the USB composite device failed.
Nothing seems to work, so I'm thinking of just accepting that its not going to work and save up and get a new phone eventually which sucks cause since rooting the G2x I love it more than when it was stocked.
quest4fire said:
Did you run as administrator?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Sometimes switching cables help. Once i used a blackberry micro hdmi cable and had problems until i switched to a LG cable. Also running Win 7 in win xp mode helps.
Sent from my SGH-T989 using xda premium
quest4fire said:
Sometimes switching cables help. Once i used a blackberry micro hdmi cable and had problems until i switched to a LG cable. Also running Win 7 in win xp mode helps.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Tried that already still doesn't work and I'm on a Vista computer don't have access to Win 7 so suggesting that won't help at all.
Sent from my LG-P999 using XDA
Ok mshoney6, Here is your solution: (you can thank me later)
After much digging and searching, searching, searching I found this driver and I uploaded it for you. Get it HERE: http://www.mediafire.com/?ahc3iklqmoa0gnc
First, go to your control panel > add/remove programs > and uninstall ANYTHING LG! This includes the Mobile Support Tool.
Second, make sure your phone and USB cable are not connected to your pc.
Now, right-click the file you downloaded above and "Run As Administrator".
DONE! Connect your phone to the PC and Viola!
I've tried installing Samsung drivers for my GS2 Skyrocket many times, but it the device drivers never install properly. This, of course, stops me from connecting my phone to the computer and stops me from rooting, etc. So, I'm looking for help on how to fix this. I'm running Windows 7
Samsung Universal Drivers
CyTheLegend said:
I've tried installing Samsung drivers for my GS2 Skyrocket many times, but it the device drivers never install properly. This, of course, stops me from connecting my phone to the computer and stops me from rooting, etc. So, I'm looking for help on how to fix this. I'm running Windows 7
Click to expand...
Click to collapse
Try this DL here they work for mehttps://www.dropbox.com/s/1dzv73dxvyzl0k8/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
:highfive:
I have the same problem. The only thing that has worked for me is a different computer. Luckily i have a laptop from work. Don't ask me why but nothing works on my home computer and i have tried every suggestion out there. I have gotten odin to regonize my device however on my home computer and successfully flashed a recovery. I like TWRP the best. Once you have the recovery you're good to go.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
It didn't work, unfortunately.
The main issue is that CDC Serial and Android_Samsung don't "install" correctly.
I have trouble connecting my phone to this laptop. It either doesn't connect or ejects while I'm transferring something, but it's fine with my netbook. I suspect it may have something to do between 32-bit (my netbook) and 64-bit (my laptop) operating systems, but I don't know much about it to actually confirm that. It may also be an issue with the stock cable.
If using another computer doesn't work, you may want to try another USB cable. I have a couple other MicroUSB cables lying around that seems to establish a better connection, but I leave important transfers (ROMs, flashing, etc) for my netbook.
What's the error log say?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I have tried everything and I can not get my device to show up in ADB for the life of me. I have verified my supercid thru adb, but can't get my device to show up. I've installed htc sync, updated drivers, even downloaded the tool multiple times. I thought I read back when I rooted that i needed to uninstall htc sync, is this correct?
Nobody? Come on guys help a brother out.
Sent from my HTC One X using xda premium
louslugger15 said:
Nobody? Come on guys help a brother out.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
TRy ending task on htc sync, a different usb port, and different usb cable, and make sure its not usb3.0.
I'm pulling what's left of my hair out over this, too. I've tried uninstalling all drivers and HTC software, and not letting Windows install the default drivers. I've changed USB ports. I've tried reinstall HTC sync only, but the phone still doesn't show up in adb. Device is recognized both booted into the ROM and in recovery/bootloader, just not by adb.
Grr
Running cleanrom 6
Windows 7 64bit
USB debugging is on.
Sent from my Transformer TF101 using xda premium
How did you ever root your phone if adb doesn't recognize it?
Sent from Xparent Red using my Venomized Evita
That's the weird part. I have root, recovery, but for whatever reason I can't get adb and my phone to talk.
Sent from my HTC One X using xda premium
Its funny you having these problems... I usually have no trouble with adb, however last night I tried to s-off my cousins hox... Fastboot works fine, when I get to the adb push it won't recognize in adb. So I tried mine, won't recognize... Rebooted both phones and my computer. No go..
So I tried my wife's computer... No go...
I don't understand either
Edit: while I was at it I tried cleanrom, dirty ROM, and cm10.1
Sent from my HTC One XL using Tapatalk 2
I have this problem too when I am trying to get adb devices with windows 8 64bit. My devices always appears offline. But when I trying with windows 7 32bit, viola.. its work! Maybe there is something wrong with 64bit platform (or just mine?)
Sent from my HTC One X
Are you guys trying adb commands? Or just stopping when "adb devices" returns nothing? Because I noticed this when I upgraded everything on my phone this past weekend.
I was able to ruu, push files, etc., but "adb devices" returned nothing. I was on 64-bit Win7 with USB 3.0.
I've tried windows XP and windows 7... Tried shooting a bunch of adb commands with no success... "Device not found"
I've always had success with adb, as I use it quite often for the custom sense lockscreens
Sent from my HTC One XL using Tapatalk 2
I had this problem a little while ago. Only a reinstall of windows helped:banghead:. During the meantime though I booted up a virtual machine and ran the commands through it.
Sent from Xparent Red using my Venomized Evita
That's an idea, a virtual machine.
I pulled an antique desktop out of the closet that ran on some ancient version of xp and solved that problem. I never got over "devices not found" on any other new computer with my hoxl or wifeys x+. I tried everything everyone will ever tell you.. Random assortment of usb cables, ports, installed HTC sync and HTC sync manager a trillion times, tried creating a file with my hexadecimal I'd number in them.. Even tried running the cmd or Adb as administrator.
In the words of jcase: windows sucks. Fix your environment.
InflatedTitan said:
I've tried windows XP and windows 7... Tried shooting a bunch of adb commands with no success... "Device not found"
I've always had success with adb, as I use it quite often for the custom sense lockscreens
Click to expand...
Click to collapse
Did you check Task Manager and kill all HTC and adb functions? HTC sync keeping stuff running even when you close it. That worked for me.
My phone wasn't coming up as "Android Phone" or "HTC" in the "Device Manager" on Windows 7. Would only show it as "G:/" under "Portable Devices" thus disabling me from installing the proper drivers.
[SOLVED]
I plugged my phone in, and uninstalled G:/ in device manager (Your letter may be different).
Then I went into "Disk Management" and found the removable drive G:/. Right click and go into which ever option was to change the letter. Go ahead and pick another letter (make sure it's different from any other drives you may have, I went with Z).
Unplugged my device, made sure debugging was on, and plugged it back in. Device Manager now shows my phone as "Android Phone" Success!
iElvis said:
Did you check Task Manager and kill all HTC and adb functions? HTC sync keeping stuff running even when you close it. That worked for me.
Click to expand...
Click to collapse
Noo I can't believe it slipped my mind.. About to be home... Will try
Sent from my HTC One XL using Tapatalk 2
I got mine working last night, but I have to be honest that I have no idea exactly what it is that worked. Here's what I did:
Uninstall HTC Sync and ALL HTC stuff.
Toggle developer modes on and off a few times
Reinstall HTC Sync
Windows tries to install drivers, but I forced it to uninstall them.
Manually install the drivers included with HTC Sync
And... it works now. I'm not sure what was different this time around, but I won't complain.
Sent from my Transformer TF101 using xda premium
I also noticed this when I tried to flash CleanROM 6 from Newt's JB. Neither Newt's nor CR6 (installed successfully without adb) were recognized on PCs and ports I had used to root my Evita. I think this has something to do with JB or the "debloated" versions.
When I connect my Evita, I no longer receive the charge/drive/tether toast notification. USB debugging is set in settings. Had to install "adbWireless" app to get adb to work properly, and of course that means that I have two devices connected via adb/fastboot if I reboot to recovery or bootloader. What a PITA, I will try on a USB 2.0 port to see if that has any more success.
****EDIT-RESOLVED****Like belyle, I had to force USB debugging off, and this took several attempts. Even with Developer Options turned off, USB debugging would turn itself on when the phone was plugged in to the computer via USB. Somehow this locked the phone from being recognized. Finally got USB debugging shut off, and manually turned it on again and adb/fastboot worked normally. I did not have to uninstall or reinstall anything. I am currently running CR6.
As I mentioned before, this is something that was set by default on a cooked ROM and think that is what is causing this issue.
I'm sorry for activating an old thread, but I've had the same issues and the fix for me was to use my USB 2.0 port instead of the USB 3.0 ports on my laptop. As soon as I plugged it into a USB 2.0 slot the phone booted right up without issue and could be seen through ADB, plugged it back into the USB 3.0 and "error: device not found" kept coming back. Moved back to the USB 2.0 slot and no issues whatsoever. Funny how USB 3.0 is supposed to be backwards compatible, but yet my phone doesn't work on it.
herschwolf said:
I'm sorry for activating an old thread, but I've had the same issues and the fix for me was to use my USB 2.0 port instead of the USB 3.0 ports on my laptop. As soon as I plugged it into a USB 2.0 slot the phone booted right up without issue and could be seen through ADB, plugged it back into the USB 3.0 and "error: device not found" kept coming back. Moved back to the USB 2.0 slot and no issues whatsoever. Funny how USB 3.0 is supposed to be backwards compatible, but yet my phone doesn't work on it.
Click to expand...
Click to collapse
This has been posted so many times.
Sent from Xparent Red using my Venomized Evita
WookieFan said:
I also noticed this when I tried to flash CleanROM 6 from Newt's JB. Neither Newt's nor CR6 (installed successfully without adb) were recognized on PCs and ports I had used to root my Evita. I think this has something to do with JB or the "debloated" versions.
Its something to do with JB. I tried to uninstall, reinstall drivers/HTC Sync, different USB port (all 2.0 on my PC), all the usual stuff. None of that worked. The only thing that got it to work was reverting to an ICS nandroid. After that, adb recognized immediately. Did the s-off and went back to the JB nandroid. Again, adb doesn't work (although fastboot does).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
NOTE: I'm on a Mac
rajah sulayman said:
(crossposting from here as this looks like a more active sub and I'm desperate).
Basically what happened was:
After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
Booted system to find endless crash dialogs
Rebooted into recovery to find TWRP gone
Did a Full Wipe under stock recovery, hoping it'd fix things
I can now get back into system, but it's glitchy
Neither adb devices nor fastboot devices see the phone
Troubleshooting I've tried:
Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear
I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.
Does anyone know what's going on or any way to remedy the situation?
Click to expand...
Click to collapse
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Sent from my PH-1 using Tapatalk
sd_shadow said:
It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.
Click to expand...
Click to collapse
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
rajah sulayman said:
But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.
Click to expand...
Click to collapse
do you know how to check which drivers are selected.?
Sent from my XT1254 using XDA Labs
sd_shadow said:
do you know how to check which drivers are selected.?
Click to expand...
Click to collapse
Is it through the Android Studio SDK manager? I remember using that way back when to get everything set up, but I haven't really used it since then.
Actually I just remembered that Mac don't need drivers, right? Per Google:
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices."
Update: Pulled out my Windows laptop and installed everything (drivers, Android Studio, et al) to see if I'd have better luck there.
To test, I first plugged in my working Nexus 5X. Windows immediately recognized it. Pulled up a prompt and adb devices saw the phone no problem.
Unplugged the Nexus and plugged in my Pixel XL. Nothing. No "hardware plugged in" chime, nothing listed under Device Manager, nada. Likewise, the phone itself doesn't acknowledge that it's been plugged in because there's no Android System pulldown.
If it were a driver issue, Device Manager would still at least be able to see the phone (it just wouldn't know what it was). But I'm getting absolutely nothing.
I can only assume that the problem is indeed with the phone itself. I don't know what the problem is exactly, but I know it wasn't there before all of this. Either way, this means my only hope for a fix would have to be through the phone itself. But since Stock Recovery doesn't seem to offer me many options, I have no clue what to do next.
Is there some sort of "secret" key combo or command or something that'll do a low-level format of the phone or something? I'm grasping at straws here, I know, but I honestly don't know what else there is I can do.
-------
Update 2: If I plug it in while in Bootloader, Windows recognizes that a device was connected, but as an "Unknown USB Device (Device Descriptor Request Failed)"
None of the solutions I can think of (or Google) seems to work. Has anyone heard of this problem before? I'm vainly hoping there's a fix out there that I just haven't found yet.
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.
bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.