Device recognized in fastboot, but not in adb - Nexus 7 (2013) Q&A

Hi All, I tried All drivers in nexus root tool kit and many other methods to uninstall all other usb drivers and then install google. But it al ways shows up as "Unknown USB Device (Device Descriptor Request Failed)". I have also tried changing the micro usb port. Charging works.Not sure whats the issue. Only fastboot mode its recognized (when i do fastoob devices, it shows with device ID ) but after i reboot into bootloader or just as MTP, its not get the above error ! . Please help !
DEVICE is : nexus 7 2013 wifi (flo) running 6.0.1

Related

Uknown USB Device (Device Descriptor Request Failed)

I am on the latest 6.0.1 and I am trying to connect my nexus 7 2013 to my windows 10. That is the error i am getting. I have factory reseted my device and I have tried to uninstall all drivers from google to samsung and to no avail it still doesn't work. Is this a bug in 6.0.1? What should I do?
I want to root my device.
Try it without 6.0.1 - boot in fastboot mode and tell us if USB registers now properly.

Watch on bootloop

Hello, I need help with my watch. USB debugging is not enabled and I cannot get pass bootloader because of it and PC does not recognize the device. I tried installing PDAdriver and sdk tools but no luck with them. Is there anyway to fix this bootloop (stuck at spinning dots)?
Edit - While in bootloader, PC recognize the watch as unknown device and i cannot update the driver.
Editx2 - Could it be because the usb charger is not oem?

usb not recognized after flash wrong kernel

------------
the problem is solved i just don't know how to delete this thread
-----------
in fact the device is still not yet recognized under twrp but does work under bootloader mode, it's just it's not adb connection but fastboot connection that i got confused
for anyone who have a similar problem, you might find it helpful in the following links that i tried before i realized my stupidness...
http://sciologness.com/download/903...-configuration-descriptor-request-failed.html
http://adbdriver.com/downloads/
http://developer.samsung.com/technical-doc/view.do?v=T000000117 // this is the samsung page, but after installation you might find in your usb driver compatibility list something like "samsung adb interface" and that might do the trick
--------------original post-----------------
hey guys,
i just followed this page to root my device
http://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
everything went fine until i flashed the xceed kernel.img for my stock rom...
and when booted into twrp and connect to pc meanwhile, the tablet it's not recognzied via usb anymore, and it says 'unknown usb device' error code 43. the tablet can either be rebooted into the system or recognized under the bootloader mode
i tried to install the google usb driver manually but it says
'This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)'
anyone please help
i don't think it's the problem of my cable or the connecting ports...
my os is win10 64
thanks all
G

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

OnePlus 3 not connecting to laptop

I bought my new OnePlus 3 and it's updated to Android N (7.0) and OOS 4.0.3 but when I connect it to my laptop (Windows 10), it only charges and my laptop doesn't recognise it. I've tried enabling and disabling USB Debugging, usb connection mode on developer options is stuck at charging and in the device manager it shows an unknown usb device (Device Descriptor Request Failed)
Please help. It's stock and with locked bootloader​
Have you installed oneplus drivers yet?
I downloaded them from the net and they're installed. I've also disabled driver signature verification in my laptop.
I cannot change usb configuration to mtp or anything else. It stays stuck at charging.
Please help ASAP or I would have to return the phone.
Thanks in advance

Categories

Resources