Database Info

[Q] ADB not connecting

Not sure when USB stopped working but nothing I've done let's my HTC One X (AT&T) connect via usb. I'm running CM10.1 and have tried both MTP and USB Storage and none of my PC's will see my phone.
I'm running TWRP 2.5, which I just updated today. When I boot into recovery and mount USB, my PC shows nothing. I boot the phone into recovery and the fastboot line says fastboot AC instead of fastboot USB. I've tried 3 different cables, an older cable that came with a MyTouch 4G, the HOX cable, and a generic USB cable. All three cables work with my wife's HOX, though hers is stock.
I've also tried on two different laptops (one vista, one win7), my PC (win7), even ran an Ubuntu VM on my PC and nothing.
HTC Sync Manager has been installed and is currently uninstalled though I do see the HTC Driver in Programs so it is there. Some times when I plug the phone in I get an error from Windows about the USB device not installing right. One odd thing is I don't see the device anywhere in device manager, nothing other Other, Android Devices or anything like that.
Developer options are turned on, with Android debugging, USB debugging notify turned on. Root access is set to Apps and ADB.
I've tried other things I've found such as turning the phone off and plugging it into the USB and letting windows detect that way. Pretty much at a loss at this point.

al_g said:
Not sure when USB stopped working but nothing I've done let's my HTC One X (AT&T) connect via usb. I'm running CM10.1 and have tried both MTP and USB Storage and none of my PC's will see my phone.
I'm running TWRP 2.5, which I just updated today. When I boot into recovery and mount USB, my PC shows nothing. I boot the phone into recovery and the fastboot line says fastboot AC instead of fastboot USB. I've tried 3 different cables, an older cable that came with a MyTouch 4G, the HOX cable, and a generic USB cable. All three cables work with my wife's HOX, though hers is stock.
I've also tried on two different laptops (one vista, one win7), my PC (win7), even ran an Ubuntu VM on my PC and nothing.
HTC Sync Manager has been installed and is currently uninstalled though I do see the HTC Driver in Programs so it is there. Some times when I plug the phone in I get an error from Windows about the USB device not installing right. One odd thing is I don't see the device anywhere in device manager, nothing other Other, Android Devices or anything like that.
Developer options are turned on, with Android debugging, USB debugging notify turned on. Root access is set to Apps and ADB.
I've tried other things I've found such as turning the phone off and plugging it into the USB and letting windows detect that way. Pretty much at a loss at this point.
Click to expand...
Click to collapse
Helping a gentleman with the same issue in another thread, it sounds to me like a hardware issue.

[Q] Win7 system reports slow USB port when in CM Recovery

I'm loading a ROM on this Nexus S i9020A. I have unlocked the bootloader and flashed CM 5.0.2.0.
When I boot into recovery, the Windows 7 host reports "This Device Can Perform Faster" and recommends moving the phone to a different port. However all ports on the computer are USB 2 or USB 3. I have tried other ports just in case and I get the same warning.
When I try to download files with ADB PUSH, it takes forever (5-10 minutes), indicating that it is probably running at USB 1 speeds.
Windows Device Manager reports that it is using the "Android Composite ADB Interface" as the USB driver for the phone.
I have performed a ROM update using the same procedure on another Nexus S on the same computer with the same drivers, and I did not have this issue.
Why does this happen, and how can I solve it? Is there something wrong with the phone or its USB port?

As a workaround, it seems to be possible to unplug the USB cable and plug it back into the same port. In the few times I tried it, it would correctly connect at full speed. There must be some timing issue when the USB port is initialized in CM Recovery that causes the problem with Windows.

Phone not detected by PC yet charges?

HTC One S4
Alright, I've looked into this for quite a bit. There's 3 things I've found:
- Change charging cable (done)
- Install HTC Sync (done)
- The USB connector port on the phone could be broken (hope not)
Anything else I can look into?
- Rom is ViperOneS JB
I believe I've tried ADB devices, I haven't really done any sort of ROM changing so I've forgotten much of this, but I believe ADB devices doesn't show any available devices.
EDIT: Another thing to add is that the PC recognises the phone when in CWM but doesn't mount the device such that I can access the files.
EDIT 2: I tried Fastboot USB, only comes up as Fastboot AC :/

Another thing: I charge my phone using a dodgy eBay USB cable, I didn't use this for connecting to the PC but whenever I plug in the charger the phone says to unlock in order to access files on the PC (as it would if my PC detected the phone).

Sorry to sound desperate but I need a response, fast!

Uninstal htc sync.
Instal latest HTC drivers & adb.
PS
Windows 8.1 have a problem with driver.

It says the device connected to the PC has "malfunctioned". I deleted HTC Sync, haven't updated ADB cos I can't remember the link.

Installed latest adb, no avail.

http://forum.xda-developers.com/showthread.php?t=2217396
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/

I already have those.

Anyone at all know anything?

Bump :/

It does say unlock to access phone storage on computer and then when I do, nothing happens.

I have the same issue, and I've tried to access my One S from multiple computers (different usb ports, 2.0, hub, et.c., Windows, OSX, Linux) and nothing seems to do the trick. I'm completely locked out from switch recovery (TWRP installed but can't be accessed, possibly due to old 1.13 hboot).
Sorry not to be able to offer any help, just that I doubt it'll be fixed in your case by switching computers/os/ports et.c. since I've tried most of that already, and I must've been through 10-12 different usb cables by now.
Just about ready to ditch this phone.

Flash the original recovery.

[Q] No USB connection while booted into Android or TWRP...

Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).

Having the exact same problem. Did you find a solution?

EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.

Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB

What's your adb version?

Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.

i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment

Is my Device bricked?

All I see is a google logo, not rebooting just staying on the screen. I am pretty sure I deleted the operating system, but I can't seem to get in recovery. What lead up to this was me not being able to connect the device to windows over usb, nothing in device manager, I couldn't even get adb to connect even through twrp sideload. But now I think I caused a whole new issue. I'm just trying to get back to stock rooted lol. Advise?
Edit: unpluged battery and replugged it in, got into recovery now, still having issues connecting so I can flash a rom.
Edit: I have the google usb driver installed from the android sdk. I still can't see my device in windows device manager nor I can't see it through adb. still searching around for a solution.
Edit: I found my old rom still on the device so I was able to install that to actually use the device. I still can't seem to connect to the pc in any way though. I have usb debugging checked drivers installed. Windows just doesn't seem to think a device is there.

s101999 said:
All I see is a google logo, not rebooting just staying on the screen. I am pretty sure I deleted the operating system, but I can't seem to get in recovery. What lead up to this was me not being able to connect the device to windows over usb, nothing in device manager, I couldn't even get adb to connect even through twrp sideload. But now I think I caused a whole new issue. I'm just trying to get back to stock rooted lol. Advise?
Edit: unpluged battery and replugged it in, got into recovery now, still having issues connecting so I can flash a rom.
Edit: I have the google usb driver installed from the android sdk. I still can't see my device in windows device manager nor I can't see it through adb. still searching around for a solution.
Edit: I found my old rom still on the device so I was able to install that to actually use the device. I still can't seem to connect to the pc in any way though. I have usb debugging checked drivers installed. Windows just doesn't seem to think a device is there.
Click to expand...
Click to collapse
Try toggling MTP and/or PHP in USB options.
Your device might show up as an adb device in Device Manager.
Edit:
Some more info here:
http://forum.xda-developers.com/showpost.php?p=57205550&postcount=146

Use a different usb port, different cords, or even a different computer, until you get a pc to recognize the phone.

I had this. It was because not all USB leads have data. Even some that do are wired different. Use the original or HTC work fine with N5 as I've both brands

howard bamber said:
I had this. It was because not all USB leads have data. Even some that do are wired different. Use the original or HTC work fine with N5 as I've both brands
Click to expand...
Click to collapse
Well on my 4th cable, what do you know it works just fine. Feel a little silly but thanks everyone.