Database Users

[Q] Accidentally OTA update on clockwork recovery, now no USB.

Nexus 7 is rooted and unlocked.
stupidly hit OK to OTA update, even though clockwork recovery was flashed. Didn't work out so well.
So now there no USB support. Doesn't show up in device manager, doesn't work with fastboot/adb.
Not sure how I can fix this. It seems like the best solution would be to flash a factory image, but I can't without fastboot.
I think maybe its an issue with the kernel, but I don't really know.
Tried searching for the last 3 hours, can't find anything.
Any ideas?
Thanks

After researching more, and trying all sorts of things, I'm starting to think its a problem with the boot loader.
Still same problem, with no usb being recognized anywhere, not sure how to proceed.
Any suggestions greatly appreciated.

Same problem here, did you find a solution?

mine shows in Fastboot mode but not ADB mode....same kinda problem maybe??

have you tried a different usb cable? or if it works with another computer?

Think I might have solved my problem... have you checked USB Debugging is enabled on the tablet?
Mine wasn't and therefore ADB didn't see the device....

I know there are those who advocate manual steps but I just used one of the tool kits to solve this. But my tab was still being recognized by my computer so it was pretty easy. Just flashed root and Recovery in one step.
Sent from my Nexus 7 using xda premium

I cant´t get any USB Connection, even not reinstall the driver, because the Nexus is not shown in the Device Manager.
I tested different Cables on different PCs with no luck.
But OTG with stickmount still works, so i think it can´t be the USB-Port that´s damaged und must be some Software error.
I just flashed the Paranoiddroid in hope that it changes anything, but it did not.
ADB not working, no connection too.

TVeil said:
I cant´t get any USB Connection, even not reinstall the driver, because the Nexus is not shown in the Device Manager.
I tested different Cables on different PCs with no luck.
But OTG with stickmount still works, so i think it can´t be the USB-Port that´s damaged und must be some Software error.
I just flashed the Paranoiddroid in hope that it changes anything, but it did not.
ADB not working, no connection too.
Click to expand...
Click to collapse
Try going into Settings > Developer Options
Make sure USB Debugging is ticked.
Worked for me....

I think your misunderstanding the ops situation.
USB debugging will not help because when he is plugging in, its not been recognized as a device has been plugged in
Even with debugging disabled your PC will detect when you plug it in
Sent from my Nexus 7 using xda app-developers app

taffypride said:
Try going into Settings > Developer Options
Make sure USB Debugging is ticked.
Worked for me....
Click to expand...
Click to collapse
Thank you, but i tried that several times, in different USB-modes too...
bagofcrap24 is right, no recognition at all.
I think i will flash the device back to stock, remove CWM, unroot, lock the bootloader etc., hope that this will change the situation.
The problem is, that there is no USB-Connection at all even in fastboot mode.
Does anyone know if it´s possible to Is it possible to flash a Factory Image with fastboot with ADB over TCP/WIFI ?

bagofcrap24 said:
I think your misunderstanding the ops situation.
USB debugging will not help because when he is plugging in, its not been recognized as a device has been plugged in
Even with debugging disabled your PC will detect when you plug it in
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Just speaking from my own experience....
With USB Debugging set to on, ADB recognises the device as does the Device Manager.
With USB Debugging set to Off, ADB doesn't see the device and neither does the Device Manager.
Only other thing I can think to do is to try a different USB lead and failing that, reinstall the Android SDK/Drivers

taffypride said:
Just speaking from my own experience....
With USB Debugging set to on, ADB recognises the device as does the Device Manager.
With USB Debugging set to Off, ADB doesn't see the device and neither does the Device Manager.
Only other thing I can think to do is to try a different USB lead and failing that, reinstall the Android SDK/Drivers
Click to expand...
Click to collapse
Device Managed Should See your device regardless of weather it has debugging on or not.
please see the attached images to verify
With USB-Debugging On
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With USB Debugging OFF
As you can see the Nexus 7 is still listed as a portable device regardless of weather debuggin is on or off
the only difference is that with USB debugging off the ADB interface will not work
The only thing i can suggest to the OP is to try a Live Linux CD and pray that you can get it to recognize it in there, if you can then it is possible that you can reflash a completely stock image & bootloader

My Nexus is not recognized by Linux too.
So the problem is not the driver, it´s the tablet´s system.
Does anybody know if it´s possible to flash a factory-image with adb via wifi?

TVeil said:
Thank you, but i tried that several times, in different USB-modes too...
bagofcrap24 is right, no recognition at all.
I think i will flash the device back to stock, remove CWM, unroot, lock the bootloader etc., hope that this will change the situation.
The problem is, that there is no USB-Connection at all even in fastboot mode.
Does anyone know if it´s possible to Is it possible to flash a Factory Image with fastboot with ADB over TCP/WIFI ?
Click to expand...
Click to collapse
Fastboot and adb are two different things and the device is identifying itself with different ids when connected to the PC. Adb over TCP/WIFI is possible (see http://anddisa.blogspot.de/2012/10/remote-debugging-over-tcpip.html, fastboot not.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
TVeil said:
My Nexus is not recognized by Linux too.
So the problem is not the driver, it´s the tablet´s system.
Does anybody know if it´s possible to flash a factory-image with adb via wifi?
Click to expand...
Click to collapse
You need to add the correct dbus-rules. Have a look at http://anddisa.blogspot.de/2012/10/nexus-7-mtp-automount-on-opensuse-114.html where you can extract the rule-devs you need.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Fastboot and adb are two different things and the device is identifying itself with different ids when connected to the PC. Adb over TCP/WIFI is possible (see http://anddisa.blogspot.de/2012/10/remote-debugging-over-tcpip.html, fastboot not.
Click to expand...
Click to collapse
Got it, thank you. So it´s not possible to flash the Stock image via WIFI - it´s necessary to be in fastboot-mode to do that? Or is there a way to activate the adb-WIFI-Connection in the fastboot-mode?
Is it possible to flash the Factory Image with the Clockwork-Recovery from SD-Card?
Or is there any other way to get back to stock without the need of an USB-Connection?

What version is our boot loader, did ota update also update this? If not you could try to flash this. You can download it from a thread in android dev section of the forum.
Sent from my Nexus 7 using xda app-developers app

My Bootloader Version Number is 3.34, is there a version you can recommend?
-and is it a simple zip-install with clockwork recovery?

The newest boot loader that goes with android 4.1.2 is version 3.41. It is a cwm flash able zip called JZ054K boot loader which you can find in the android (not original) development section of the nexus 7 xda forum. The thread is called [boot loader] JZ054K, or something. Sorry can't post links yet.
Good luck, hope this solves your USB issue.
Sent from my Nexus 7 using xda app-developers app

Thank you very much! I´ll give that a try after work.

[Q] LG Optimus L3 usb not connecting but charging

Hello
My phone: LG E400
rom: SDmerge+ miniCM (not sure if the problem is connected with that as everything was fine at the beginning)
All of a sudden my phone didn't show usb connection any more. No connection is shown in the phone or PC, but the phone is charging.
I tried all usb connection options, usb debugging on/off, no result.
Uninstalled all phone drivers in my PC and reinstalled LG driver, nothing.
Tried another usb cable and another PC, the same problem.
Also tried turning off my phone while connected, no help.
Please help me.
Don't know if it helps but I once saw a strange message in Titanium backup while usb was connected (this was after the problem started, so no usb connection was shown, usb debugging was on). It only happened once, so I'm not 100% sure what it said but it was sth about that I should turn on usb debugging.

Bosskardo said:
Hello
My phone: LG E400
rom: SDmerge+ miniCM (not sure if the problem is connected with that as everything was fine at the beginning)
All of a sudden my phone didn't show usb connection any more. No connection is shown in the phone or PC, but the phone is charging.
I tried all usb connection options, usb debugging on/off, no result.
Uninstalled all phone drivers in my PC and reinstalled LG driver, nothing.
Tried another usb cable and another PC, the same problem.
Also tried turning off my phone while connected, no help.
Please help me.
Don't know if it helps but I once saw a strange message in Titanium backup while usb was connected (this was after the problem started, so no usb connection was shown, usb debugging was on). It only happened once, so I'm not 100% sure what it said but it was sth about that I should turn on usb debugging.
Click to expand...
Click to collapse
message is fine thats mode for special apps to control phone from pc or when using adb
there is a program to see if phone fully not detected "Advanced USB Port Monitor" it will show all the requests to usb
seems like you need a flash because usbmanager is part of system and i'm not sure if possible to reinstall
wait a little if not in rush maybe someone else can help @slipsystem @AwesomeSMS

IGGYVIP said:
message is fine thats mode for special apps to control phone from pc or when using adb
there is a program to see if phone fully not detected "Advanced USB Port Monitor" it will show all the requests to usb
seems like you need a flash because usbmanager is part of system and i'm not sure if possible to reinstall
wait a little if not in rush maybe someone else can help @slipsystem @AwesomeSMS
Click to expand...
Click to collapse
I did format and flashed rom again but it didn't solve it. Does this mean its a hardware issue for sure?

Bosskardo said:
I did format and flashed rom again but it didn't solve it. Does this mean its a hardware issue for sure?
Click to expand...
Click to collapse
can you access phone using adb ?
how did you flash ?

IGGYVIP said:
can you access phone using adb ?
how did you flash ?
Click to expand...
Click to collapse
No, phone doesn't show up as adb device
I copied rom files to sd card and flashed from recovery.

Bosskardo said:
No, phone doesn't show up as adb device
I copied rom files to sd card and flashed from recovery.
Click to expand...
Click to collapse
TRY THIS http://forum.xda-developers.com/showthread.php?t=2660144
did you try to access phone using adb in recovery mode ? (not cwm !) does it recognise phone in lgmobile support tool whire in recovery mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
?
if you can then try to recovery mode flash new stock firmware
if not leave it because if anything happens to your cwm you will be stuck until you get usb port/controller (i think controller) repaired (yes its most likely hardware damage)
you could also ask if anyone will provide you with .img partition dumps and then adb wifi sideload them (HARD AND DANGEROUS)

IGGYVIP said:
TRY THIS http://forum.xda-developers.com/showthread.php?t=2660144
did you try to access phone using adb in recovery mode ? (not cwm !) does it recognise phone in lgmobile support tool whire in recovery mode
?
if you can then try to recovery mode flash new stock firmware
if not leave it because if anything happens to your cwm you will be stuck until you get usb port/controller (i think controller) repaired (yes its most likely hardware damage)
you could also ask if anyone will provide you with .img partition dumps and then adb wifi sideload them (HARD AND DANGEROUS)
Click to expand...
Click to collapse
No, LG support tool doesn't recognize it. I gave up on usb, just been using bt and wifi transfer (not the best solutions but at least I can transfer data).
But sth happened a few days ago. I plugged it in to my laptop for charging and suddenly it connected. It showed as device in the computer. But then I looked at my phone, it was connected as media device. I don't know why but I changed the connection to usb storage straigth away and lost the connection. Changing back to media device and replugging doesn't connect any more, it still charges.
What could that be about?

Bosskardo said:
No, LG support tool doesn't recognize it. I gave up on usb, just been using bt and wifi transfer (not the best solutions but at least I can transfer data).
But sth happened a few days ago. I plugged it in to my laptop for charging and suddenly it connected. It showed as device in the computer. But then I looked at my phone, it was connected as media device. I don't know why but I changed the connection to usb storage straigth away and lost the connection. Changing back to media device and replugging doesn't connect any more, it still charges.
What could that be about?
Click to expand...
Click to collapse
Actually the problem is on your windows not on your phone.

george brown said:
Actally the problem is on your windows not on your phone.
Click to expand...
Click to collapse
I've tried it on another computer (Vista, mine is win7).

Bosskardo said:
I've tried it on another computer (Vista, mine is win7).
Click to expand...
Click to collapse
If the problem is not from your windows then try to reinstall your cusrom. Or try another cusrom.

No Drivers

So, I'm trying to unlock the bootloader. I can't get it to show up on my laptop running Windows 8.1. Just can't figure out how to get my pc to find the device even after typing adb devices or fast boot devices.

try this to put device in fastboot, press and hold button that is located on the bottom of the player, plug in the power cord and hold until led light flashes repeatedly.

eko3484 said:
So, I'm trying to unlock the bootloader. I can't get it to show up on my laptop running Windows 8.1. Just can't figure out how to get my pc to find the device even after typing adb devices or fast boot devices.
Click to expand...
Click to collapse
i had same issue see here
http://forum.xda-developers.com/showpost.php?p=56870580&postcount=6

Still trying. No luck yet.

eko3484 said:
Still trying. No luck yet.
Click to expand...
Click to collapse
Have you unlocked the developer options in the About menu? Then did you enable USB debugging in the developer options? Those two steps are required before your PC will recognize the NP in adb. Also make sure you are on the latest SDK to get the newest platform tools (and drivers).

Elrondolio said:
Have you unlocked the developer options in the About menu? Then did you enable USB debugging in the developer options? Those two steps are required before your PC will recognize the NP in adb. Also make sure you are on the latest SDK to get the newest platform tools (and drivers).
Click to expand...
Click to collapse
Yes I have done all of that. I have the latest sdk but maybe I set it up wrong? It detects my phone, I can run commands through the terminal and everything. It just won't detect the nexus player. My guess was maybe drivers but I'm no expert here lol.

eko3484 said:
Yes I have done all of that. I have the latest sdk but maybe I set it up wrong? It detects my phone, I can run commands through the terminal and everything. It just won't detect the nexus player. My guess was maybe drivers but I'm no expert here lol.
Click to expand...
Click to collapse
Try holding down the button on the bottom of the NP until the white light starts quickly flashing, then let go. This'll put you directly in fastmount mode. Then try "fastmount devices" from your pc to see if it's recognized (assuming you have a normal usb cable between the two, no OTG cable between them of course).

Elrondolio said:
Try holding down the button on the bottom of the NP until the white light starts quickly flashing, then let go. This'll put you directly in fastmount mode. Then try "fastmount devices" from your pc to see if it's recognized (assuming you have a normal usb cable between the two, no OTG cable between them of course).
Click to expand...
Click to collapse
Okay. Do you mean, hold the button as I plug in the power cord? I can get it to fastboot mode just fine.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have USB Debugging enabled.
The sdk works with my phone.
My pc will not detect when I plug in the nexus player, whether it is fastboot mode or running normally.
Anything else I can try?

eko3484 said:
I have USB Debugging enabled.
The sdk works with my phone.
My pc will not detect when I plug in the nexus player, whether it is fastboot mode or running normally.
Anything else I can try?
Click to expand...
Click to collapse
Sorry, I was typing quickly and mistyped. You can't use adb in fastboot mode (which is what you're in when you manually reboot with the button held down), only fastboot works.
Type "fastboot devices" and see if yours shows up. Its the "fastboot oem unlock" command you'll need to type twice to unlock the bootloader, but "fastboot devices" will tell you if its seeing your NP in the first place. Again, adb won't work in fastboot mode.

Thanks but it's still a no go. Maybe I could try using another pc. Makes no sense because it all works for my note 3.

if windows does not see it in any way ( nothing coming up in "devices" ) , assume you have a bad cable , bad port , or a security block . ( or worse case, a defective usb port on your NP )

bkdg100 said:
if windows does not see it in any way ( nothing coming up in "devices" ) , assume you have a bad cable , bad port , or a security block . ( or worse case, a defective usb port on your NP )
Click to expand...
Click to collapse
Okay. I've tried different cables. USB otg works on it. I've tried all USB ports on my pc. I'll keep trying though. Thanks for helping me try to figure this out.

is the NP showing up under devices ?

eko3484 said:
Okay. I've tried different cables. USB otg works on it. I've tried all USB ports on my pc. I'll keep trying though. Thanks for helping me try to figure this out.
Click to expand...
Click to collapse
If your cables work with your phone on the same usb port, it's probably just misconfigured drivers (very likely) or a bad NP (unlikely).
Go in to your control panel/device manager with the NP plugged in and see if you can find it. If it is under unknown, right click and install driver. If it is there, double click it and select the driver tab then "update driver" button. You can get the correct drivers here:
http://developer.android.com/sdk/win-usb.html
Select "browse my computer" and find wherever you extracted the above drivers, then let it install. Hopefully that'll fix things up for you... if not, you'll have to uninstall the existing drivers and reinstall them. Good luck.

Not at the house right now but I'll try all of this when I can. Thanks.

OPT is not connected to Win10: Unknown USB Device (Device Descriptor Request Failed)

Anyone knows why my USB device descriptor is failing?
OnePlus Two is not getting connected to my Win10 machine. Look, at the screenshot, I'm getting USB device not recognized popup every time I plug OPT with my cable.
In system's Device Manager it shows Unknown USB Device (Device Descriptor Request Failed) and there, in Properties of the device, it says:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.​
I've tried to reinstall driver (ADB & Fastboot) and add 0x2A70 into adb_usb.ini, etc., but nothing helped. Maybe you know how this could be fixed?
Tech details:
OnePlus Two; Android 5.1.1; OxygenOS v2.2.1
Original red OnePlus' USB Type-C cable
Windows 10 Home; 64-bit;
Laptop is msi 2pc gs70
Phone charges from my laptop;

Is your device bricked? Last time I had this my device was bricked

it's not bricked
zFramed said:
Is your device bricked? Last time I had this my device was bricked
Click to expand...
Click to collapse
Well, it's not bricked. I guess. I'm using it without any other problems.
Also, worth mentioning:
When I go to Settings->Storage->[menu]->"USB computer connection" I get toast message saying: Connect your device to a computer to access USB connection settings
I was always updating it via OTA software updates. Did not try flashing it yet.
I upgraded windows from Win8.1 to Win10.
I also can't connect my OPT via cable on Linux (Ubuntu) as well
I was always connecting my OPT for debugging via WiFi, AFAIR, but now, I want to do some VR development and it's too slow to install apps there.
Connecting old Huawei works fine both on Windows and Ubuntu.
Any thoughts, what should I do more?

Here's some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Other than right clicking and uninstalling that driver I have nothing else to propose. I'm pretty sure you have already done that though so I'm sry. Just try another PC would be last resort

Try to go to drivers manager then right click on the unknown device then do update driver then choose from the computer then select the OnePlus driver (may be the OnePlus Drivers won't be in the list and you will have to select with File Manager )

I was Googling for that OnePlus Two driver, but all links would lead to some generic drivers. So you know where should I get it?

viliusk said:
I was Googling for that OnePlus Two driver, but all links would lead to some generic drivers. So you know where should I get it?
Click to expand...
Click to collapse
Naman Bhallas thread on oneplus.net for bricked devices. The driver should be there

Try advance reboot, disable signature verification, install drivers again.
Try different cable and computer
Sent from my ONE A2005 using Tapatalk

Oh crap! Apparently it's cable issue! Original red flat OnePlus Two's cable charges my phone perfectly, has no visual defects BUT does not support *ADB Interface* connection! How weird is that! Was always giving me *USB device not recognized* error message.
Just now I tried this other http://www.ebay.com/itm/151671008605 cable which I was using in my car just for charging.
Thanks everyone for the support in this journey finding the problem.
PS.: that other cable I tried and also did not work was this cheap item from ebay:
http://www.ebay.com/itm/USB-C-3-1-T...obile-Phone-/401006950019?hash=item5d5de07683

viliusk said:
Oh crap! Apparently it's cable issue! Original red flat OnePlus Two's cable charges my phone perfectly, has no visual defects BUT does not support *ADB Interface* connection! How weird is that! Was always giving me *USB device not recognized* error message.
Just now I tried this other http://www.ebay.com/itm/151671008605 cable which I was using in my car just for charging.
Thanks everyone for the support in this journey finding the problem.
PS.: that other cable I tried and also did not work was this cheap item from ebay:
http://www.ebay.com/itm/USB-C-3-1-T...obile-Phone-/401006950019?hash=item5d5de07683
Click to expand...
Click to collapse
I've been struggling with a similar thing recently. I can get fastboot, charging and the software for factory flashing a bricked OP2 to work 90% of the time. But once I get into Oxygen, or CM13 (tried on many versions from different devs), my W10 doesn't recognize the MTP device. It's just charging the phone but I can't transfer any files.
What is more odd though is that I don't even have to have the original OP2 usb-c cable plugged in the phone to get error messages in W10. I plug one end of the cable into my computer's USB slot and get DEVICE NOT RECOGNIZED...plugging it into the phone doesn't do anything then.
I ordered a new cable, that hopefully helps but it's a weird thing, since fastboot and factory flashing work (mostly). I hope it's not something with the hardware, I'm selling it in two weeks and getting a OP3.

viliusk said:
Anyone knows why my USB device descriptor is failing?
OnePlus Two is not getting connected to my Win10 machine. Look, at the screenshot, I'm getting USB device not recognized popup every time I plug OPT with my cable.
In system's Device Manager it shows Unknown USB Device (Device Descriptor Request Failed) and there, in Properties of the device, it says:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.​
I've tried to reinstall driver (ADB & Fastboot) and add 0x2A70 into adb_usb.ini, etc., but nothing helped. Maybe you know how this could be fixed?
Tech details:
OnePlus Two; Android 5.1.1; OxygenOS v2.2.1
Original red OnePlus' USB Type-C cable
Windows 10 Home; 64-bit;
Laptop is msi 2pc gs70
Phone charges from my laptop;
Click to expand...
Click to collapse
I am having the SAME problems! With an old cable and NEW!
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
This is crazy cause I have used the same cables without problems.

I'm waiting on the new cable and hoping it will solve the issue. I even factory reset my W10 desktop to have a fresh driver install, but no drivers help, not Google drivers, not Oneplus drivers or Samsung drivers.

What cables are working? I NEED to connect my device daily.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
viliusk said:
Anyone knows why my USB device descriptor is failing?
OnePlus Two is not getting connected to my Win10 machine. Look, at the screenshot, I'm getting USB device not recognized popup every time I plug OPT with my cable.
In system's Device Manager it shows Unknown USB Device (Device Descriptor Request Failed) and there, in Properties of the device, it says:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.​
I've tried to reinstall driver (ADB & Fastboot) and add 0x2A70 into adb_usb.ini, etc., but nothing helped. Maybe you know how this could be fixed?
Tech details:
OnePlus Two; Android 5.1.1; OxygenOS v2.2.1
Original red OnePlus' USB Type-C cable
Windows 10 Home; 64-bit;
Laptop is msi 2pc gs70
Phone charges from my laptop;
Click to expand...
Click to collapse
DonJuan89 said:
I'm waiting on the new cable and hoping it will solve the issue. I even factory reset my W10 desktop to have a fresh driver install, but no drivers help, not Google drivers, not Oneplus drivers or Samsung drivers.
Click to expand...
Click to collapse
Am I crazy..lol these cables worked before but I'm having these issues above to the T! Plug a cable in and get a malfunction pop up!! Didn't happen before!!

I didn't use to have the problems either. When it first started happening, I though it was because I was flashing back an forth between roms, factory restoring to stock OOS many times. I thought the drivers got a bit messed up. But I've been on fresh CM for a week and now on stock OOS 3.0.2, a fresh W10 system and I still have the problems. Phone works without a hitch, but it just won't connect to MTP. It's either the cable (I hope) or something happened with hardware or partition with all that flashing...(i guess unlikely)
And yeah, getting the device not recognized error when I simply plug in the cable in a USB port is really weird...it's like the cable became it's own device without a driver... I'm pretty sure it wasn't like that before. I didn't get the USB connected sound notification on Windows when I plugged in the cable into a USB slot. Got the sound notification when I plugged in the phone as well. Don't know, I've been looking for weeks for solutions.

DonJuan89 said:
I didn't use to have the problems either. When it first started happening, I though it was because I was flashing back an forth between roms, factory restoring to stock OOS many times. I thought the drivers got a bit messed up. But I've been on fresh CM for a week and now on stock OOS 3.0.2, a fresh W10 system and I still have the problems. Phone works without a hitch, but it just won't connect to MTP. It's either the cable (I hope) or something happened with hardware or partition with all that flashing...(i guess unlikely)
And yeah, getting the device not recognized error when I simply plug in the cable in a USB port is really weird...it's like the cable became it's own device without a driver... I'm pretty sure it wasn't like that before. I didn't get the USB connected sound notification on Windows when I plugged in the cable into a USB slot. Got the sound notification when I plugged in the phone as well. Don't know, I've been looking for weeks for solutions.
Click to expand...
Click to collapse
Yeah, same here. I didn't have this problem till I updated to 3.0.2 now that I think about it.. and like you I thought I messed something up flashing back and forth but that's not the case. As I'm always transfering pic ands what not and all was fine till the update which gave me a bootloop and after I got that fixed had this issue.

Umm, did you eliminate the USB port as the problem? Try connecting to a different port, preferably on a different computer?

karthikrr said:
Umm, did you eliminate the USB port as the problem? Try connecting to a different port, preferably on a different computer?
Click to expand...
Click to collapse
Yeah, I tried a different computer, I tried all 6 USB ports on my desktop, I even reset my W10, wiping everything and installing fresh drivers. Nothing helped. As soon as I connected my OPT cable to the USB slot, I got DESCRIPTOR FAILURE. On every USB port.
EDIT:
new cable arriving shortly, will post update as soon as I have it

DonJuan89 said:
Yeah, I tried a different computer, I tried all 6 USB ports on my desktop, I even reset my W10, wiping everything and installing fresh drivers. Nothing helped. As soon as I connected my OPT cable to the USB slot, I got DESCRIPTOR FAILURE. On every USB port.
EDIT:
new cable arriving shortly, will post update as soon as I have it
Click to expand...
Click to collapse
karthikrr said:
Umm, did you eliminate the USB port as the problem? Try connecting to a different port, preferably on a different computer?
Click to expand...
Click to collapse
evertking said:
Yeah, same here. I didn't have this problem till I updated to 3.0.2 now that I think about it.. and like you I thought I messed something up flashing back and forth but that's not the case. As I'm always transfering pic ands what not and all was fine till the update which gave me a bootloop and after I got that fixed had this issue.
Click to expand...
Click to collapse
Ladies and gentlemen, at least for me, the cable was the culprit. I got the new one, went to my university's library and plugged my OP2 into a public computer without any prior installation of any drivers. The device got recognized immediately, set up it's own drivers and MTP works like a charm...all on first try.
Below a link for the cable I bought. There's different brands that would work as well. Cheers and I hope that this simple thing helps more people.
https://www.amazon.de/gp/product/B01A6F3WHG/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

For those who can't fix this issue (even with working cable),
Disable Driver Signature Enforcement (Windows 8 and above) before installing Oneplus Drivers ---> https://www.youtube.com/watch?v=71YAIw7_-kg
Drivers won't install properly without disabling it.

q about current root method on shield tv

the current method to root the shield tv requires that you need to use a micro sd card in twrp to install root, the only problem with that is the new 16gb models do not have a micro sd card slot will it make these new models unrootable?
it seems only the new pro 500gb models will only have root at this point unless the devs can think of a work around to avoid this issue with the micro sd cards.
using a memory card reader and putting the micro sd card in there won't work either because i tried this when i attempted to root the mad catz mojo and it didn't work.
should i hold out and wait and see what the root situation is going to be for the new models first before i order the 16gb model? just incase i need to get the 500gb model instead, it would be a pain to return and refund to do that.

Shouldn't be an issue, you should be able to use a thumbdrive. I guess we'll find out when someone tries it. Later today I'll put supersu on a thumbdrive and see if twrp will mount it. Now that I think about it, you can prob just copy it locally & flash it. I'm just curious if the old root will work on the 5.0 update.

The slim doesn't have a micro usb port anymore either. Can adb be run through the regular usb with a male to male cable?

You don´t need a micro sd-card. Only need twrp to flash su.zip. In twrp you can use usb-drive, adb push file to internal flash oder adb sideload.

Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv

unsatgoua said:
Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv
Click to expand...
Click to collapse
Thanks for that. I am picking mine up in a few minutes and going to try and root it with a USB M/M.

unsatgoua said:
Shouldn't be an issue, you should be able to use a thumbdrive. I guess we'll find out when someone tries it. Later today I'll put supersu on a thumbdrive and see if twrp will mount it. Now that I think about it, you can prob just copy it locally & flash it. I'm just curious if the old root will work on the 5.0 update.
Click to expand...
Click to collapse
i'm assuming the nougat android update will have a new bootloader so all the root methods out there right now do not work with the new 2017 model.
please try and report back the results, i'm holding off buying this till we get more info on the root status.
unsatgoua said:
Hmmmm, no micro usb... got me on that one, not sure how you would push twrp via adb. You might be right on the usb m2m, not sure. I'll Google it and see if anyone has rooted it yet, I have 2 1st gen 16gb so I'll just be pushing everything via micro usb. You have me curious now, how do you charge your controller?
---------- Post added at 09:16 AM ---------- Previous post was at 09:06 AM ----------
Got this blurb off the web:
"You'll also notice the Micro-USB port is gone, but don't worry — NVIDIA has an option to let you use one of the USB-A ports as an input port for a PC connection if you need it."
Got it from:
http://m.androidcentral.com/nvidia-shield-android-tv
Click to expand...
Click to collapse
i've googled for 2 days straight to see if any new root methods have popped up but nothing so far.
will the usb a be good enough for root i wonder?

Usually nvidia has developer images available that are already rooted so maybe just flash that on the new shield when it becomes available.

Forgot what I read a while back but the rooted images don't actually give you root but only allow you to run adb in an elevated mode. Nothing I needed. So I just fastbooted twrp and flashed supersu. Also remember reading something about those images not able to update ota which means fresh install every update. Don't quote me though but there was enough I read to say [email protected] no to the "rooted images" and just root the standard ones. As far as root I would definitely agree that waiting for a verified root will prevent a possible brick and major headache.

So I have yet to get my Shield to show up on my pc under device manager when I connect with the cable. I am hoping I just have a bad cable so I have ordered one that will come in about 2 days.

You installed the drivers? Don't forget, they said one port, so try both.

unsatgoua said:
You installed the drivers? Don't forget, they said one port, so try both.
Click to expand...
Click to collapse
When you put it into ADB mode it tells you what port to use. And when I plug it into my pc it never comes up under device manager so I can't install the drivers.
Edit: That is why i'm trying a new cable since I know the port work with my mouse.

I'm surprised they didn't provide a cable to flash images.
Sent from my SM-G935T using XDA-Developers Legacy app

unsatgoua said:
Forgot what I read a while back but the rooted images don't actually give you root but only allow you to run adb in an elevated mode. Nothing I needed. So I just fastbooted twrp and flashed supersu. Also remember reading something about those images not able to update ota which means fresh install every update. Don't quote me though but there was enough I read to say [email protected] no to the "rooted images" and just root the standard ones. As far as root I would definitely agree that waiting for a verified root will prevent a possible brick and major headache.
Click to expand...
Click to collapse
excatly, this is why I'm holding out for now.
yojoe600 said:
So I have yet to get my Shield to show up on my pc under device manager when I connect with the cable. I am hoping I just have a bad cable so I have ordered one that will come in about 2 days.
Click to expand...
Click to collapse
not a good start but let us know how it goes anyway.

I have the old 16gb version and I wont be upgrading until there is a root method.

Slayerkodi said:
I have the old 16gb version and I wont be upgrading until there is a root method.
Click to expand...
Click to collapse
I wish I would have found the old version for the price I paid for this one ($175 + tax). I am sure there will be a way to root it I hope since there is an option to connect through ADB. I am just hoping it's my cable.

yojoe600 said:
I wish I would have found the old version for the price I paid for this one ($175 + tax). I am sure there will be a way to root it I hope since there is an option to connect through ADB. I am just hoping it's my cable.
Click to expand...
Click to collapse
It can only be our cable, because i was able to install the official fastboot drivers from NVIDIA and connect via ADB
Win10 Prof. x64
SHIELD TV Gen. 2017
SHIELD TV bootloader version:
Code:
24....
enabled developer options
enabled adb debugging
rsa fingerprint acceptance
installed fastboot driver :good:
adb connection via SHIELD USB port 1 USB A <=> A :good:
Code:
adb devices
listed the shield :good:
reboot into fastboot
Code:
adb reboot bootloader
:good:
unlocked bootloader
Code:
fastboot oem unlock
after unlocking i sometimes got a flickering on my screen
could not
Code:
fastboot boot TWRP
boot TWRP, The SHIELD would reboot, show the "unlocked bootloader message" and would reboot to system
could flash recovery (success message)
Code:
fastboot flash recovery twrp-3.0.2-0-foster.img
but after reboot to system i saw the "unlocked bootloader message" and then i guess the SHIELD reflashed to stock recovery.

aVlkaFenryka said:
It can only be our cable, because i was able to install the official fastboot drivers from NVIDIA and connect via ADB
Win10 Prof. x64
SHIELD TV Gen. 2017
SHIELD TV bootloader version:
Code:
24....
enabled developer options
enabled adb debugging
rsa fingerprint acceptance
installed fastboot driver :good:
adb connection via SHIELD USB port 1 USB A <=> A :good:
Code:
adb devices
listed the shield :good:
reboot into fastboot
Code:
adb reboot bootloader
:good:
unlocked bootloader
Code:
fastboot oem unlock
after unlocking i sometimes got a flickering on my screen
could not
Code:
fastboot boot TWRP
boot TWRP, The SHIELD would reboot, show the "unlocked bootloader message" and would reboot to system
could flash recovery (success message)
Code:
fastboot flash recovery twrp-3.0.2-0-foster.img
but after reboot to system i saw the "unlocked bootloader message" and then i guess the SHIELD reflashed to stock recovery.
Click to expand...
Click to collapse
Hey did you try this bit?
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
https://twrp.me/devices/nvidiahshieldandroidtv.html

If you have a usb or 2.4ghz keyboard, theres the non root/adb method of, ALT+PRINT SCREEN+i to boot into recovery folks could test, confirmed working on first gen shield.
More details here
https://forum.xda-developers.com/shield-tv/help/accessing-satv-stock-recovery-t3300211
I believe its an android feature, rather then a shield specific one, as i believe the method was first found on the ouya console, and found to also work on other android consoles, like the ouya, nexus player, shield....... i wouldnt be surprised to find out that it works on phone/tablet
Edit
I just retested this again, pressing the combination once, and letting the shield bootup, instead of pressing again, on boot logo image, to go to recovery, and it looks like it removed root for some reason, so bare that in mind, just incase thats normal behaviour. Ive just used the method again to boot to recovery this time to flash supersu zip in twrp, everything seems back to normal

banderos101 said:
If you have a usb or 2.4ghz keyboard, theres the non root/adb method of, ALT+PRINT SCREEN+i to boot into recovery folks could test, confirmed working on first gen shield.
More details here
https://forum.xda-developers.com/shield-tv/help/accessing-satv-stock-recovery-t3300211
I believe its an android feature, rather then a shield specific one, as i believe the method was first found on the ouya console, and found to also work on other android consoles, like the ouya, nexus player, shield....... i wouldnt be surprised to find out that it works on phone/tablet
Click to expand...
Click to collapse
theirs no power button on the 2017 shield.