Develop Bugs

ADB only recognizes phone when it's in recovery. Why?

I used to be able to
1. Plug my phone in via USB (unmounted - meaning "charge only")
2. Open up a command prompt and navigate to the correct folder.
3. Type "adb devices"
4. Receive a long string of characters that indicated that adb recognized the device.
Now this only happens for me if the phone is in recovery already. For example:
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT05SHL05247 recovery
Things I've tried:
* Re-installed SDK
* Re-installed HTC Sync
* Manually re-installed drivers for phone
It is interesting to note that when the phone is on and plugged in, Device Manager sees it as a disk drive no matter if the phone is mounted as a disk drive or not. Strange.
Everything worked fine until I went on vacation. Now it's messed up!
The question is: how do I get adb to recognize my phone again?

is usb debugging still on?

when you plug in the USB cable do you get the screen to select
charge only, HTC Sync Disk drive etc..
if not go to "Settings" -> "Connect to PC"
and turn on "Ask Me"
I had a bad USB port, would only charge could not get any PC connection to work until phone was replaced, works now
Bill

Thanks for the responses.
mdwoods said:
is usb debugging still on?
Click to expand...
Click to collapse
Yes, I checked and USB Debugging is selected.
btedeski said:
when you plug in the USB cable do you get the screen to select
charge only, HTC Sync Disk drive etc..
if not go to "Settings" -> "Connect to PC"
and turn on "Ask Me"
I had a bad USB port, would only charge could not get any PC connection to work until phone was replaced, works now
Bill
Click to expand...
Click to collapse
Yup, when I plug it in I get the pop-up asking me what kind of connection I want.
Any other ideas?

Still nothing! I'm going to be selfish and bump in case a fresh pair of eyes can help me solve this.

Something similar happened to me. I tried many things over and over again. I changed kernals, roms, reinstalled drivers, etc. Eventually, I just reformatted my computer and it worked. I don't know why reinstalling the drivers wouldn't work when reformatting did. I honestly have no idea, but that reformat did the trick for me.

ADB not working when booted is a somewhat commonly-reported problem with King's kernels. Try flashing the stock kernel and see if it starts working again. Also, wipe your caches in the future before flashing a new kernel. This seems to prevent a lot of issues.

I has this same problem. I believe I wrote a thread about it. When I toggled USB debugging off and then back on, that is what solved the problem. Believe me, I went through hours of reinstalls of multiple androidusb.inf drivers plus HTC Sync among others. It wasn't until a "what the hell, let's give it a try" moment that I toggled USB debugging off/on. Like you, I had it on the whole time. Still don't know what caused the mishap but this is what fixed it for me.
Sent from my PC36100 using XDA App

Thanks for the last two ideas. I love Fresh ROM, but have been having major issues with it lately, and this must have been tied into it. I installed Baked Snack with the custom baked snack "speed" kernel and the issue went away (along with all my other issues). Yay.
I don't doubt that toggling the USB Tethering check box would have fixed it, though. And that's just funny. Sad and funny.

Sprockethead said:
I don't doubt that toggling the USB Tethering check box would have fixed it, though. And that's just funny. Sad and funny.
Click to expand...
Click to collapse
Actually, I found an answer to that question. I am experimenting with Andromadus CM10 on a HTC Desire Z and this is what happens:
The mobile phone declares what USB device it is. You can look at this on the linux computer you have connected it with:
Code:
lsusb -v -d 0bb4:0c91
The string after "-d" is what you get from a plain lsusb command. The important part of the output of that command is
Code:
bInterfaceClass 255 Vendor Specific Class
"adb devices" only shows the phone if this 255 is present.
With the phone in fastboot and recovery, I always could see the 255 on my linux box. Normally booted, I sometimes had it, sometimes not.
If I had it the device was called "HTC Vision", if I didn't have it, it was a "HTC Desire / Desire HD / Hero (Charge Mode)"
Toggling "USB Debugging" actually helped me to make it a "HTC Desire" and get adb over USB working.

[Q] Drive Mode Windows 7

Hello,
I just got my Evo. Love it.
My question is, I enter drive mode on Windows Vista, but when I try to enter drive mode on Windows 7, the drive does not show up. In the device manager, it shows up as an unknown device. In devices and printers, it shows up as an Android phone. ????
Any help would be great!!!

did you install htc sync on the windows 7?

Mine did the same thing on Windows 7. Actually I'm on my third Evo & all of them were like that. I never got the option to choose in the notification bar & HTC Sync never helped, the phone wasn't recognized.
Make sure you're using the cable that came with the phone or at least one shorter than two-feetish. Long 3rd party cables won't work. Download widgetsoid 2.x from the market, it's a power control widget & it's great. Make a 1x1 switcher widget & only select "usb storage" under the first category. Ignore all of the other options because you'll be removing it after anyway. On the bottom panel, scroll all the way to the right & click apply. Sorry for the lengthy description, I'm not sure how well you know how to work your phone. Okay, turn on USB debugging in settings > applications > development. If you feel the need you can reboot your phone. Be sure to not kill anything.
Connect the cable to the computer. You should get a notice that usb debugging is on, don't touch it. Find the widget you made & touch it. You should connect after a couple seconds. If it tells you to connect your phone first, then it isn't working & this advice was pointless.

minics04 said:
Hello,
I just got my Evo. Love it.
My question is, I enter drive mode on Windows Vista, but when I try to enter drive mode on Windows 7, the drive does not show up. In the device manager, it shows up as an unknown device. In devices and printers, it shows up as an Android phone. ????
Any help would be great!!!
Click to expand...
Click to collapse
The device it's seeing is the adb interface from the phone (Unknown Device). If you enter storage mode (ie Cable plugged in -> Notifications > USB Connected > Turn on USB Storage), it is a different device that should be recognized by Win7 native drivers. If not, you could try installing HTC Sync and then rebooting, then plugging in your phone and try that.
Worst case, get a microSD-SD adapter that will let you put your SD card direct in the PC (not the best solution, but it works).

USB charges but no data

Hi, my phone stopped being able to get a USB data connection. The port is physically intact and does not wiggle. I've tried two different Macs and one PC, different USB-A to -C cables (all verified by Benson Leung). Also toggled USB debug, MTP and PTP modes from Developer Options, rebooted phone and computer. When I plug the phone in, it only goes to Charging mode. Android File Transfer doesn't see it and 'adb devices' comes back empty. There is no notification offering me to select connection type. Did I miss anything or is it time to send it in? Thanks, Tony

What OS are you running on your Windows - checking your Device Manager under Control Panels - are all the Google / N5X drivers installed and working correctly before this ? Try uninstalling, reboot PC and re-install them - and, use different USB port to connect the cable (what kind of connections are you using ??)
Can you run ADB ?

Thanks I'm primarily using a Mac (10.10.5) but the PC was running Vista. It was a borrowed PC so I didn't install the drivers. I don't think it's a driver issue though since nothing shows up in device manager and the phone doesn't offer to switch out of charge-only mode. Also the same Mac worked previously.

Cant transfer files from my phone to my pc via usb

so im using a pixel 2 xl, and i cant seem to transfer files between my phone and any pc whatsoever, i used to do this easily before, ive tried everything, turned on usb debugging, use the notification drawer changed the cable, but nothing seems to be working, what coudl be the problem and how do i solve it ??????????????????

USB mode now always defaults to "charging". You have to change it manually to "MTP" each time. At least in my experience.

I had the same problem. With my Nexus 5x and USB-C to USB cable it works, but with my Pixel 2 XL it works not, so i had to buy a new USB-C to USB cable and now it works.

Not sure what cable you are using but do not use a USB C to USB C cable, make sure its a USB c to USB a.
Sent from my Pixel 2 XL using XDA Labs

Ive been having issues lately too. Doesnt matter which cable i use. It will connect then disconnect over and over again. IT may be my computer but not sure how to check why it would be doing that.

Are you doing gigabytes of data? If it's just in the hundreds of megabytes transfer to Google Drive. I do that when I have files on my computer I want over to my phone and vice versa.
Sent from my Pixel 2 XL using Tapatalk

Engineer
nasfayde said:
so im using a pixel 2 xl, and i cant seem to transfer files between my phone and any pc whatsoever, i used to do this easily before, ive tried everything, turned on usb debugging, use the notification drawer changed the cable, but nothing seems to be working, what coudl be the problem and how do i solve it ??????????????????
Click to expand...
Click to collapse
I had the same issue with my Pixel 2 as well and after reading through numerous forums, I figured out how to fix it. its been two days now and I am still able to transfer files via USB.
Here is what you need to do:
1) Enable developer mode by going into Settings > System About Phone > Build number and tapping a few times (5 I think!)
2) Click back and then select Advanced > Developer Options
3) Scoll down the menu until you see "Default USB configuration". Tap and then select the option you require (ie: File Transfer)
4) Click back, then scroll up the menu till you see "USB Debugging". Enable USB Debugging.
5) Connect your Pixel 2 to you laptop/PC. The phone should appear in the Devices list in 'Control Panel\Hardware and Sound\Devices and Printers. Leave it connected for another 5 or 10 minutes and it should become available in "This PC"
6) Disconnect the Pixel2 from your laptop/PC
7) Disable "USB Debugging" and disable "Developer Mode" on the phone.
8) Reconnect the Pixel2 to your PC/Laptop. It should now appear under "This PC" every time you connect and you should now be able to view and transfer files between you PC and Pixel2.
Let me know if it works for you or not.

equlizer said:
Ive been having issues lately too. Doesnt matter which cable i use. It will connect then disconnect over and over again. IT may be my computer but not sure how to check why it would be doing that.
Click to expand...
Click to collapse
I had the same issue on my notebook yesterday - the phone would connect, but once I transmitted a larger file the transmission was terminated after a few seconds.
In my case it wasn't the cable, it was the USB port on my notebook! I simply used a different one and then it worked flawlessly
Thank god my notebook has 4 USB ports, I pity people with notebooks with a single USB port :laugh:

IsaacFC said:
I had the same issue with my Pixel 2 as well and after reading through numerous forums, I figured out how to fix it. its been two days now and I am still able to transfer files via USB.
Here is what you need to do:
1) Enable developer mode by going into Settings > System About Phone > Build number and tapping a few times (5 I think!)
2) Click back and then select Advanced > Developer Options
3) Scoll down the menu until you see "Default USB configuration". Tap and then select the option you require (ie: File Transfer)
4) Click back, then scroll up the menu till you see "USB Debugging". Enable USB Debugging.
5) Connect your Pixel 2 to you laptop/PC. The phone should appear in the Devices list in 'Control Panel\Hardware and Sound\Devices and Printers. Leave it connected for another 5 or 10 minutes and it should become available in "This PC"
6) Disconnect the Pixel2 from your laptop/PC
7) Disable "USB Debugging" and disable "Developer Mode" on the phone.
8) Reconnect the Pixel2 to your PC/Laptop. It should now appear under "This PC" every time you connect and you should now be able to view and transfer files between you PC and Pixel2.
Let me know if it works for you or not.
Click to expand...
Click to collapse
Got the same problem. Since a few days device isn't recognized on any computer. Tried serveral usb cables (they were all working before) - no success. As soon as i am connecting device to a windows computer it says "device couldn't get regonized properly". So it isn't recognized as android phone. So your method didn't work (tried all the steps before). I also remarked before, thad my device sometimes restarts as i plug in an usb cable. Mainly when connected to a pc but also serveral times only when charging. So i resetted my device back to all stock (even formated data), flashed original boot whitout twrp, no root. It's starting nice but i even can't install the update (january patch) through device. Alway gives me install error. So it isn't recognized in adb... So i can't use fastboot mode to reinstall twrp.... Any advice? Think gonna claim for replacement.... Seems a hardware problem.

Had something similar a couple of months back.
Just do a quick check with usb dac and otg. If they are not working, the component is fried. RMA.
Else, faulty cable or friend port in laptop.

USB error PLEASE HELP!

USB will not function with my OnePlus 3, I've loaded drivers and still no avail.

templarsniper said:
USB will not function with my OnePlus 3, I've loaded drivers and still no avail.
Click to expand...
Click to collapse
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.

There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?

kenboyles72 said:
There could be several reasons for this, but lets start with the basics.
Have you tried a different cable?
Have you selected File Transfer (MTP) from usb options?
Click to expand...
Click to collapse
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.

TNSMANI said:
As regards the attaching of files, you have to have a minimum number of posts to be able to do that.
As regards the USB, be a little more specific like what you are trying to do, which ROM you are running, whether you are rooted, what happens when you connect the phone to PC etc which will enable the members to help you.
Click to expand...
Click to collapse
I cant even root for the life of me now, Im on 8.0, I'm trying to just root the phone and to start the computer has to recognize it I understand but it won't, with my Oneplus 2 was fine,(I'm thinking maybe phone doesnt have the drivers built in to the file system, you know when you plug in and turn on MTP it shows the drivers app for Windows?) the only thing it errors plugging in.
I get a windows sound like its connecting then in the bottom right where the time is next to that is a root sign then I get a pop up saying exactly.....The last USB device you connected to this computer malfunctioned and Windows does not recognize it. Recommendation.. Try reconnecting the device. If Windows still does not recognize it, your device may not be working properly. When I go to the Device Manager/Control Panel it doesnt do anything. I've tried to add adb to the path but maybe added it to wrong path now it won't come on. If there is a work around maybe to re-add to right path. Device Manager was fine before I added adb and added path as per internet search. Device Manager before would say something like error 39. I've tried MTP that doesn't get it to open up either.

On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80

Fixed USB problem
kenboyles72 said:
On my son's pc running windows 10, I didn't have any issues connecting my OP3 to it and viewing files, nor did I have to install any drivers, same for Windows 7.
Hook phone to pc via usb cable.
Pull down notification bar and select "File Transfer" from usb options or go to Settings and search USB and select USB Preferences > File Transfer.
Browse phone from Window's file manager.
If still having issues, you can try and install Oneplus USB drivers, reboot pc and see if the phone can be recognized.
Oneplus USB drivers:
https://app.box.com/s/u47rur40qm5efly6pz41rbhagu5qvc80
Click to expand...
Click to collapse
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.

templarsniper said:
For some reason it's working now don't know what the problem was or even if it was something I did. Either way it's fixed.
Click to expand...
Click to collapse
If you are running Win 10, you will have to disable driver signing before the correct drivers are installed. May be that was your issue.