Develop Bugs

[Q] [BootLdr] Computer not seeing Phone.

I am new to android, HTC One VX being my first phone ((Got it like Last year as a gift iirc)).
Using Stock rom and my os is 8.1 pro x64
I am trying to unlock the bootloader.. I went to HTCdev, followed the directions for unlocking the bootlader.
1. Got the Android SDK and installed
2. Got the HTC SYnc Manager for the drivers.
3. Got Fastboot and moved it to where the ADB .dll file is.
I get my phone into bootloader after making sure USB Debugging is enabled, then I plug it into my computer. After a few moments, Windows pops up with USB Device is not recognized. I check Device Manager, it shows "My HTC" under unknown devices. I manually point the thing to where the W8 x64 driver is , and it says the driver is up to date. Bring up the Property info of the device, this is what is showing int he text box,
Code:
A request for USB BOS descriptor failed
Just to make sure, I navigate back to the ADB folder, bring up CMD there and type in
Code:
adb devices
. No device was listed despite my phone being connected to my computer. Tried it with 3 different cords, front and back of my computer. ((USB 3.0 ports.))
I put it in one of my USB 2.0 ports and the issue persists, the device status shows
Code:
A device which does not exist was specified
.
Is there anyway to fix this, its quiet annoying, Apparently doing clean reinstalls of everything isn't going to fix it for me.

Cracked Zenfone 2 Screen, Want to Wipe NO ADB

I cracked the screen on my Zenfone 2 and before I send for RMA, I would like to wipe passwords and sensitive content. I've installed the Intel Android driver as explained in this forum, and attempted to connect via ABD to no avail. I'm not sure if I enabled USB debugging before the drop.
It still shows as a MTP in the device manager, whereas my rooted HTC M7vzw lists as an android device and is able to be seen by ABD. So, I'm trying to tshoot if it's an issue with the driver, or simply that I didn't enable the USB debugging.
I've searched the forum and found similar threads, but haven't found anything the directly addresses this problem. If there has been a link would be appreciated or any suggestions.
I'm running win8.1 and have the latest stock firmware installed on the phone. I've also tried multiple USB ports and cables.
Please help me not to buy another phone,
- Thanks

If the screen is still visible, I would use a USB mouse (using the OTG adapter) to enable USB debugging just in case it wasn't enabled. And if a popups appears when plugging in debugging mode, I guess your only choice is to use a bluetooth mouse to be able to check whatever dialog may appear at the same time you use the USB port to plug it to your PC

rambn said:
I cracked the screen on my Zenfone 2 and before I send for RMA, I would like to wipe passwords and sensitive content. I've installed the Intel Android driver as explained in this forum, and attempted to connect via ABD to no avail. I'm not sure if I enabled USB debugging before the drop.
It still shows as a MTP in the device manager, whereas my rooted HTC M7vzw lists as an android device and is able to be seen by ABD. So, I'm trying to tshoot if it's an issue with the driver, or simply that I didn't enable the USB debugging.
I've searched the forum and found similar threads, but haven't found anything the directly addresses this problem. If there has been a link would be appreciated or any suggestions.
I'm running win8.1 and have the latest stock firmware installed on the phone. I've also tried multiple USB ports and cables.
Please help me not to buy another phone,
- Thanks
Click to expand...
Click to collapse
there are lot of ways,[if u get the 1st way below]
1. get an usb or wireless mouse,connect and do a factory reset
2. directly goto droidboot and use recovery,factory reset
3. connect to PC with fastboot mode and open cmd ,type
Code:
fastboot erase userdata
think these 3 ways are easiest

Unknown USB device (failed request for device descriptor)

I have a problem.
My screen is broken. Now I want to send him to OnePlus.
But before that I want unroot it. Or at least reset to factory defaults. But both things fails.
I have the latest FreedomOS Rom. Since then I can no longer use TWRP. When I start my phone to the recovery the screen goes black and nothing happens anymore.
The same happens when I put it back to factory settings through the settings menu .
I've read there is a modified version of TWRP.
From here begins the real problem. Windows doesn't recognizes my phone.
In Device Manager it appear as "unknown USB device (failed request for device descriptor)"
What I've tried:
Boot in to Bootloader
Original (Dash) USB cable
Other USB cable
WIndows 10
Windows 7
USB debugging on
USB debugging off
OEM unlocking on
OEM unlocking off
USB configuration: File transfer
USB configuration: MTP
USB Configuration: Charge
Anyone have an idea?
Maybe it's the ROM. But I cannot flash another ROM because I can not get into TWRP.
Maybe it's an option to flash the modified TWRP without a computer. So right from the bootloader. But I do not know if this is possible. And how it should be done

I'm having the exact same problem. Did you find a solution?
In windows 10 -> i get Device Descriptor Request Failed
In windows 7 -> Unknown Usb Device (Installed Correctly)
whenever i try to update device driver with ANY driver (oneplus... or generic sdk driver) I get a message saying "doesn't contain a suitable driver for your device.....)

I went to device manager > right click mtp (unknown device) > update driver software > browse my computer > let me pick > mtp USB device > happy me

Windows it's the problem. I reinstalled drivers, adb, nothing. At work i try it & it works. I reinstalled windows. Now works.
I'm on windows 10 x64.

Damn it, I don't think windows is my problem.. i tried Windows 10 / Windows 7(2 diff computers)
i can't even see the phone as MTP..

Found any solution to this? Having a similar issue

THREAD CLOSED! If interestend in this subject, please continue here: https://forum.xda-developers.com/oneplus-3/help/usb-device-recognized-t3722279

Pixel XL Fastboot Works to Flash Stock ROM+TWRP. Unseen as USB in TWRP or OS

I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???

Pay_It_Forward_Pete said:
I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???
Click to expand...
Click to collapse
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?

TheBobMiller said:
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?
Click to expand...
Click to collapse
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.

Pay_It_Forward_Pete said:
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.
Click to expand...
Click to collapse
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?

TheBobMiller said:
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?
Click to expand...
Click to collapse
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.

Pay_It_Forward_Pete said:
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.
Click to expand...
Click to collapse
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.

TheBobMiller said:
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.
Click to expand...
Click to collapse
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)

Pay_It_Forward_Pete said:
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)
Click to expand...
Click to collapse
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...

TheBobMiller said:
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...
Click to expand...
Click to collapse
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.

Pay_It_Forward_Pete said:
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.
Click to expand...
Click to collapse
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!

TheBobMiller said:
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!
Click to expand...
Click to collapse
@TheBobMiller I appreciate all your thoughtful suggestions and well wishes. Have an awesome weekend!

Need a help flashing stock ROM

Hi, I got this bugger for way too big price (40 bucks for non-working piece of garbage), but I needed it because nobody helped me with reflashing original Nexus 7 I botched up while flashing (can't even get to fastboot mode).
I need to resurrect it from death. Apparently, somebody was tinkering inside, one antenne lead is broken, USB port seems replaced with very wrong one (it fits, it sits, but clearly it is not original) and the main, biggest problem is that the OS is corrupted.
All I keep getting is Google logo, can't boot into normal mode, can't boot into recovery mode. Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)". When I try to manually install Universal Naked Driver, it keeps *****ing about wrong driver version or not compatible hardware. What I have to do to get it working except sending it to Asus and pay 5 times the tablet's price to get it fixed?
It was going to be replacement for that botched Nexus 7, but now it seems that it will cost way more...

Have you not tried the Nexus Root Toolkit by Wugfresh? I reckon you should give it a try good luck.

Yeah, that came around my mind too, but there is one problem. USB debugging was never turned on and now when I plug in the tablet, it shows in device manager as Unknown USB device (device descriptor request failed). And because there is no working communication (it doesn't show up as tablet), I cannot ADB DEVICES it, returns me empty list.

krivulak said:
Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)"
Click to expand...
Click to collapse
USB debugging on/off is relevant only in ADB mode and has no impact whatsoever in fastboot mode. Please boot it in fastboot mode, connect to PC and quote USB device descriptor number from device manager.
If it is 18D1:4EE0 then you have to resolve driver issues on your PC
If it is 0000:000x then you have to fix hardware problem in your Nexus
I posted more info in this and this thread.

USB Device Tree Viewer shows it as vid_0000&pid_0002, so there is hardware problem with the tablet.
So, if I understand it correctly, it can be caused either by badly seated cable or bad USB port. Sice the one that is there is clearly changed for the wrong one, I will try to order proper one and see what will it do.
By the way, I already tried to reseat the ribbon cable, no luck there.