Develop Bugs

Connect Desire to laptop, not recognised!

When I connect my HTC Desire through USB cable to my laptop, my laptop wait a while then pop a windows which says USB Device Not Recognised. My device just got the orange light lit up but there is no response other than that i.e. no menu pops up to choose "charge only, disk drive" whatsoever.
It worked just two days ago before I reflash a new ROM (RCMixHD 3.6.1).
During the flash, the SD card was not recognised too so I tried to get it work by using "fastboot oem enableqxdm 0" as instructed by one post named "USB brick/rickrolled/b0rked -> FIXED!" on MoDaCo.
But I did not flash the update.zip as required cos my problem was fixed before this step.
Can anyone help me fix this problem? Waiting online

USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices

FASTBOOT shows "FASTBOOT USB", Bootloader also gives me "HBOOT USB PLUG", I think the USB cable is fine.

stringer7 said:
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
Click to expand...
Click to collapse
I tried the two commands in cmd, I copy down what it gives me
E:\SDK\Tools> adb devices
List of devices attached
E:\SDK\Tools> fastboot devices
HT05HPL12963 fastboot
E:\SDK\Tools>

Ok so the fastboot result means you can connect to PC.
What happens if you connect your device whilst it's booted up with USB debugging enabled? Enable this prior to connecting in settings>applications>development.

Hi thanks for the help, I managed to unbrick the USB brick. But now even though I'm able to connect to my laptop, the adb devices still doesn't give me any device. In device manager, I got an "ADB" with yellow exclamation mark under “Other Devices”, just cannot get the right driver for it. Could it be due to the USB brick?

[Q] "adb devices" command not listing my Nexus 7 (2013) !

When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??

Tech2Yantra said:
When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??
Click to expand...
Click to collapse
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.

mdamaged said:
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.
Click to expand...
Click to collapse
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.

Tech2Yantra said:
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.
Click to expand...
Click to collapse
You're welcome, fwiw, if you follow my suggestions, you can make it so adb works in ptp and mtp, but if it's not important to you, then it's not dire.

OP3 not recognized on Win10

My oneplus 3 isn't found in com/ports on windowsill 10. It's unable to load recovery and won't boot to system. Fastbook still works and has a unlocked boot loader. Trying to install stock firmware to restore the device for se again. Any help would be greatly appreciated.

Try loading drivers, have no issues here. Also run cmd prompt by right clicking on cmd.exe and selecting "Run As Administrator"
Sent from my SM-N930T using Tapatalk

Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.

Also make sure USB debugging is enabled in the developers settings and you have the correct USB mode enabled (not charging)
Sent from my SM-N930T using Tapatalk

jaydubya24 said:
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Click to expand...
Click to collapse
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10

Will_Xda said:
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Click to expand...
Click to collapse
here is the device manager

setup driver and try in twrp

A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.

Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.

jaydubya24 said:
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
Click to expand...
Click to collapse
One more thing. Connect the phone to a USB 2.0 port and not a 3.0 port. It may not be recognised in a 3.0 port.

peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what I found on USBDeview. There are two other versions of the OP3 on this list. But they do not show as being connected while the phone is in Fastboot. Im unable to access the OS to enable anything that may help with it being seen on my computer.

http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Win7 works and i dont tryed the nice tip on site2.

i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .

You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs

update on the op3
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what shows up after the one plus boot logo appears.

I had similar problem. I was rooting my 1+3. I went to device control settings in WIN 10 and removed 1+3 drivers. Next time when i was in fastboot mode windows installed drivers. :highfive:
I used the ones that came with 1+3

jaydubya24 said:
This is what shows up after the one plus boot logo appears.
Click to expand...
Click to collapse
I think this thread will supply the solution. "your" problem is at this post https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/page-4#post-15169580

unable to unlock bootloader

Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.

I always use something called 15 Second ADB Installer when setting up ADB and Fastboot on a new computer. It installs all the correct drivers as well, so maybe that would solve your issue. Also, be sure to check Device Manager in Windows and see whether there are any devices showing with yellow caution symbols besides them.
If you find your phone displaying like this; right-click and choose 'Update driver', then 'Browse my computer for driver software' and 'Let me pick from a list of available devices on my computer'. Find Google Inc. and choose the one which says 'Android ADB Interface'. You have to do this AFTER running the 15 Second ADB Installer otherwise it won't work.

Definitely driver related, remove and reinstall etc but don't give up haha sometimes its a PITA to install the correct drivers...

satya365 said:
Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.
Click to expand...
Click to collapse
Download MIFLASH TOOL, it installs all the drivers needed for Z2

why does my bootloader driver not work?!?

I wanted to root my razer phone 2 because I rooted my old Samsung, but after unlocking my bootloader I decided against it and now ive spent about 2 days trying to lock my bootloader again with no luck.
ive tried many different usb drivers and non of them show my device under the "fastboot devices" command in adb or fastboot but I can show the device under adb devices which im aware is rather easy
ive seen many people have this issue but they don't really show/tell how its fixed! ive tried different usb sockets too!
the device name in my device manager is "SAMSUNG Android Phone" (while the phone is in fastboot mode) with the sub driver called "Android Bootloader Interface" if anyone has any kind of advice or tips to get my bootloader locked again please share!

okay, so after a lot of looking around.. I found this.
"1) - To unlock the razer phone bootloader do the following
2) - Install ADB + Fastboot and google usb drivers
3) - Enable developer mode by going to settings, about phone and hitting build number a bunch of times. then go back to settings > developer options and check USB Debugging and OEM Unlock.
4) - Open a command prompt on your PC and connect the phone's usb cable to your computer. Accept the prompt on the phone for trusting the computer when plugged in.
5) - type the following in command prompt without quotes "adb reboot bootloader"
6) - You'll be at the download mode screen with the razer logo.
7) - Make sure the driver for ADB Bootloader Interface was installed. If not you'll probably have a device called Android under "Other devices" in device manager. If this is the case, install the google usb driver.
8) - In command prompt type the following without the quotes "fastboot -i 0x1532 devices" and make sure your device comes up and not just a blank response.
9) - If it came up now just type without the quotes "fastboot -i 0x1532 flashing unlock"
10) - This will bring up a prompt on the phone itself to unlock the bootloader, use the volume button to navigate to yes and press the power button to confirm.
11) - The phone will reboot and will show a message stating "Your device is unlocked and cannot be trusted" on each boot to show that it is unlocked."
FIX - it was the "fastboot -i 0x1532 devices" I was doing wrong.. I was not putting the "-I 0x1532" i now feel stupid.. but idc i locked my phone and im back to stock finally! (ill probably end up trying to root it again some point in the future :| )