Database Info

[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

Custom Binary Blocked by FRP Lock Error

İ use custom rom and i disabled OEM unlocking and restart my phone. Phone cant boot. My USB port isnt work and i cant use odin. Cant open twrp. Actually isnt broken but my PC cant recognize my phone i try different cable, pc and driver but Windows says unkown device.

nereloyka13 said:
İ use custom rom and i disabled OEM unlocking and restart my phone. Phone cant boot. My USB port isnt work and i cant use odin. Cant open twrp. Actually isnt broken but my PC cant recognize my phone i try different cable, pc and driver but Windows says unkown device.
Click to expand...
Click to collapse
How did you flash TWRP and custom if your USB port isn't working?
Download Mode is independent of ROM so unless your hardware got damaged since flashing custom, there's no reason it shouldn't work
Try installing Samsung S7 driver again, remove old drivers from device manager first while phone is connected / enabled "Show hidden devices" from device manager while phone is disconnected and remove old drivers
Windows should install the correct driver itself

*Detection* said:
How did you flash TWRP and custom if your USB port isn't working?
Download Mode is independent of ROM so unless your hardware got damaged since flashing custom, there's no reason it shouldn't work
Try installing Samsung S7 driver again, remove old drivers from device manager first while phone is connected / enabled "Show hidden devices" from device manager while phone is disconnected and remove old drivers
Windows should install the correct driver itself
Click to expand...
Click to collapse
İ try 4 different PC. İ charge my phone with wall charher but phone see USB charging. İ install twrp with odin but i cant use odin now. Windows says unkown device and odin cant recognize. https://forum.xda-developers.com/galaxy-s7/help/usb-device-recognized-fast-charge-t357118/ its my problem

That link redirects me to here
https://forum.xda-developers.com/showthread.php?t=357118
If you have tried 4 PCs, and different USB cables then you need to get your USB port on the phone replaced / repaired

*Detection* said:
That link redirects me to here
https://forum.xda-developers.com/showthread.php?t=357118
If you have tried 4 PCs, and different USB cables then you need to get your USB port on the phone replaced / repaired
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s7/help/usb-device-recognized-fast-charge-t3571184/page2 you can see my comment page 2

Device not recognized in fastboot on Mac and not recognized at all on PC

I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.

I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?

windows not recognizing device?

Trying to unlock bootloader, upon opening command prompt via minimal adb fastboot, after entering "fastboot flashing unlock" instead of completeing the process, I'm getting a "waiting for any device" message instead.
I'm unsure if this newly discovered usb 3.1 port on my pc is even the right port for this usbc cable, as I've never used it before now.
Windows recognizes it as MTP usb , but I can't access anything, it's empty when I open it. So I don't know if it's the wrong port, and maybe I actually need to buy a USB to usbc cable from Google (tried the one that came with my V30, got same message) or if it's something else I'm missing.

breacherman said:
Trying to unlock bootloader, upon opening command prompt via minimal adb fastboot, after entering "fastboot flashing unlock" instead of completeing the process, I'm getting a "waiting for any device" message instead.
I'm unsure if this newly discovered usb 3.1 port on my pc is even the right port for this usbc cable, as I've never used it before now.
Windows recognizes it as MTP usb , but I can't access anything, it's empty when I open it. So I don't know if it's the wrong port, and maybe I actually need to buy a USB to usbc cable from Google (tried the one that came with my V30, got same message) or if it's something else I'm missi
Click to expand...
Click to collapse

just go to device manager in your windows pc where u see unknown device then you have to search for the driver of your phone and just manually select driver for your device i just faced same issue but after that it preety works but it can persists with other phone connection

[email protected] said:
just go to device manager in your windows pc where u see unknown device then you have to search for the driver of your phone and just manually select driver for your device i just faced same issue but after that it preety works but it can persists with other phone connection
Click to expand...
Click to collapse
hey thanks, that worked. Considering I've only had 3 rooted phones in the last maybe 8 years, I tend to forget those prerequisites

OS deleted, Can't access TWRP after.

i was trying to install a custom ROM and wiped all the partitions. I accidentally rebooted my Xiaomi redmi note 8 and now it is stuck in fastboot. i tried to flash TWRP using ADB however it shows that it is waiting for device. (I'm guessing that the USB DEBUGGING turned off). Anyone know how to fix this? Thanks in advance!

I would try possibly checking drivers on your computer, or just try a different cable. USB Debugging is not necessarily a thing in fastboot. Or, better said, there is not a toggle switch for turning on USB access. Plugging in a USB cable gives you full access to fastboot commands on the device that you're using. If that doesn't work, you might want to try checking out the Redmi Note 8 sub-forums since others might have the same issue. Try drivers and/or cable changes and share the results