OPT is not connected to Win10: Unknown USB Device (Device Descriptor Request Failed) - OnePlus 2 Q&A, Help & Troubleshooting

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.

Related

[Q] Half-bricked phone (USB isn't working)

Hi all
my USB doesn't seem to work anymore. However I don't believe it is a HW failure.
In Linux, when I connect my I9000 to usb, I see the following in the syslog:
Oct 14 17:17:29 xsdnied kernel: [ 1222.601065] usb 3-1: new low speed USB device using uhci_hcd and address 3
Oct 14 17:17:29 xsdnied kernel: [ 1222.670996] hub 3-0:1.0: unable to enumerate USB device on port 1
This happens both in "Download mode" and if I boot in OS and choose "Mass storage for USB", also in Debug Dev Mode ON.
Also in Windows Odin can't see the device via USB. Windows at least told me under certain condition that a new USB device detected but it failed to recognize it (albeit all needed drivers have been already installed)
The phone is working, but I can't even install CM7.1 on it because of signature verification error that seems to be unavoidable under <3e>.
Any idea how to fix this situation?
have u tried a different pc?
hezibanda said:
have u tried a different pc?
Click to expand...
Click to collapse
I've tried two. at least one of them was already working via usb with this I9000 both in windows and linux
Have you reinstalled the drivers, or tried another cable?
Talon26 said:
Have you reinstalled the drivers, or tried another cable?
Click to expand...
Click to collapse
I've tried another cable. I connect/disconnect several times and once of 20 attempts Windows makes its usual USB-discovery sound, but then says something like: USB-device is either broken or device is not recognized.
Well, just took another SGS1 that we have in our family and tested -- both cables are 100% OK.
Hm, maybe USB is indeed broken and that's it :-/
But how? why? Charging after all works.
Got the same problem bro...
One contact broke on the USB port, bricked my Phone too. I wasnt able to use odin to flash my Phone. The crazy thing is that my phone was able to charge but no connection to the PC.
I sent the bricked phone to an thrid partner from samsung, they flashed my phone and repaired the USB port. No is everything okay.
I tried several things to get the USB to work, nothing helped.

[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.

[Q] Nexus 4 gone stealth

... and is no longer recognized when connected to a computer via USB, meaning I can't return to stock to get ready for the Lollipop OTA.
Got a rooted Nexus 4 running the latest PA beta.
What happens when connecting to PC:
- On two different Windows machines: systray popup saying "USB device not recognized. The last USB device you connected to this computer malfunctioned etc.". In device manager it says "Unknown USB device (device descriptor request failed)"
- On elementary OS, based on Ubuntu 12.04: nothing, besides charging.
No USB debugging connection notification on the Nexus 4 either when plugging in.
What I've tried (USB debugging enabled, all relevant drivers installed):
- Settings > Storage > USB computer connection > check Camera PTP (used to be required in order to get an RSA key prompt when connecting to a computer, now it does nothing)
- Flashing latest stable CM to see if PA was to blame. Made no difference.
- Uninstalling device through device manager in Windows and reconnecting. No effect. Driver update doesn't work either, finds nothing.
- Using Wugfresh's Nexus toolkit to see if that worked, but that obviously doesn't work either when the device isn't recognized, same with the Universal Nexus Linux Toolkit on Linux.
- Scouring the net for solutions and coming up with nothing
I have flashed factory images before on this phone without problems. Should I consider it a hardware failure by now, or is this a known issue with a fix?
Try a new wire, different usb port on computer, finally look into cleaning your charging port on the phone/replacing it.
DrFredPhD said:
Try a new wire, different usb port on computer, finally look into cleaning your charging port on the phone/replacing it.
Click to expand...
Click to collapse
Tried three different cables, every port on two laptops, no joy - my girlfriend's phone connects normally.
Wouldn't replace the charging port, then I'd just get a new phone since it's a 2 years old Nexus 4. If only there was a way to flash the factory image using only TWRP.
bimsebasse said:
Tried three different cables, every port on two laptops, no joy - my girlfriend's phone connects normally.
Wouldn't replace the charging port, then I'd just get a new phone since it's a 2 years old Nexus 4. If only there was a way to flash the factory image using only TWRP.
Click to expand...
Click to collapse
Flash this in twrp http://forum.xda-developers.com/showthread.php?p=47476426
Sent from my Nexus 5 using XDA Free mobile app
Thanks jd1639, that seemed to be exactly what I was looking for -
- but then I had an extremely blonde moment and formatted everything in TWRP, wiping the ROM I was gonna flash in the process, on a device where USB file transfer doesn't work anymore
My phone is now a paper weight.
Have you tried the file manager in twrp yet? I've found it connects when nothing else will...

N7 lost abilty to use ADB

I've had it working for a long time, then my PC quit recognizing my N7 2012 intermittently. I thought it was a buggy ROM so I tried another. Same problem, so I wiped it and flashed stock 5.0. Same problem
It doesn't recognize it at all anymore, but I can plug in my N5 and N9 and they work great. Has this happened to anyone?
liquidsuspension said:
I've had it working for a long time, then my PC quit recognizing my N7 2012 intermittently. I thought it was a buggy ROM so I tried another. Same problem, so I wiped it and flashed stock 5.0. Same problem
It doesn't recognize it at all anymore, but I can plug in my N5 and N9 and they work great. Has this happened to anyone?
Click to expand...
Click to collapse
Did you try reinstalling the drivers? Download official Google ADB/USB drivers and install them through Device Manager.
Yep, did all that. The same driver runs my other nexus devices fine. I wish I could remember what the Windows error message says...something like 'unplug and plug it in again, if that doesn't work then replace the device'.
Make sure you enable USB debugging on your tablet. And first time you do that and connect it to PC, it should ask you for sth like RSA fingerprint. Accept that and it should work.
stuck in boot loop
Fobos531 said:
Make sure you enable USB debugging on your tablet. And first time you do that and connect it to PC, it should ask you for sth like RSA fingerprint. Accept that and it should work.
Click to expand...
Click to collapse
I see where on a lot of replies that the tablet needs to be in USB debugging. If it's in boot loop, how can you do that? My Vista won't even recognize the tablet any more!
Ok it started working again, so I quickly downloaded the 5.1 image to flash. I got through it but now it just shows the google logo forever. I can get into the bootloader via the hardware keys, but the n7 isn't recognized as a fastboot device, so I can do nothing else with it....
What Windows tells me when I plug it in is this: "The last USB device you plugged in to this computer malfunctioned, and Windows does not recognize it"
In device manager it says this: "Unknown USB Device (Device Descriptor Request Failed)"
I can get it into recovery, but it just shows our little android friend laying on his back with a red triangle.
billycrashed said:
I see where on a lot of replies that the tablet needs to be in USB debugging. If it's in boot loop, how can you do that? My Vista won't even recognize the tablet any more!
Click to expand...
Click to collapse
Try getting into Fastboot. Hold Power button to turn it off. Hold Power + Volume Down button to get to bootloader. Try using Nexus Root Toolkit when you get there or try getting into recovery and flashing something.
---------- Post added at 05:37 AM ---------- Previous post was at 05:35 AM ----------
liquidsuspension said:
Ok it started working again, so I quickly downloaded the 5.1 image to flash. I got through it but now it just shows the google logo forever. I can get into the bootloader via the hardware keys, but the n7 isn't recognized as a fastboot device, so I can do nothing else with it....
What Windows tells me when I plug it in is this: "The last USB device you plugged in to this computer malfunctioned, and Windows does not recognize it"
In device manager it says this: "Unknown USB Device (Device Descriptor Request Failed)"
I can get it into recovery, but it just shows our little android friend laying on his back with a red triangle.
Click to expand...
Click to collapse
Why can't you get into the bootloader with the hardware keys? To get into recovery in your situation, Hold Power Button + Volume Up(for one second only) and the recovery should pop up.
I can get into the bootloader. Just can't get the device to be recognized bu the pc, so O never succeed at flashing anything.
liquidsuspension said:
I can get into the bootloader. Just can't get the device to be recognized bu the pc, so O never succeed at flashing anything.
Click to expand...
Click to collapse
Try using a different USB cable or port, or even try doing all this on an alternative PC.
Its the same on my laptop and desktop, all usb ports, 3 different cables...
I'm starting to think the n7's usb port is going bad perhaps.
liquidsuspension said:
Its the same on my laptop and desktop, all usb ports, 3 different cables...
I'm starting to think the n7's usb port is going bad perhaps.
Click to expand...
Click to collapse
It could be, try taking it to the local service.

PC won't detect S7, all conventional fixes exhausted!!

I've got 5 S7s on my desk, all Canadian variant, all from the same manufacturer all the same model. - SM-G930W8
All are recognised by my PC but one and I can't work out why not!
Plugging the phone into the PC makes no noise from the PC but the phone seems to detect a regular charger not a PC.
I have plugged it in using different cables including the one in its box and the ones used on other devices that were recognised and only this phone doesn't work with any of them.
I have plugged in, unplugged and rebooted many times.
I have set the USB configuration to MTP (Media Transfer Protocol)/Transferring files.
USB Debugging is ON and OEM unlocking is ON.
I have tried booting into stock recovery and wiping cache AND factory resetting.
When phone is turned on "adb devices" returns nothing.
I have installed Samsung Kies and Samsung Smart Switch to reinstall the drivers.
NOTHING IS WORKING!
All threads I find tell me to do the things I have listed above and have people saying these have worked but all of them I had already tried and double tried and nothing is working.
The cables are correct and working with other S7s of the same model.
All the correct drivers are installed and have been uninstalled and reinstalled.
All the correct setting are selected and OEM unlock and USB debugging enabled.
Phone was fresh out the box as were the other four and all cables.
Samsungs apps installed on PC to ensure best drivers installed.
Would really appreciate some guidance or consolation that its not something stupid I'm doing! I work with these phones everyday and this has never happened! Just banging my head against a brick wall trying to resolve it
maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.
yaro666 said:
maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.
Click to expand...
Click to collapse
Thanks but unfortunately Odin doesn't recognise in download mode.
Could it be a USB port problem if I used the same port for the other 4 devices and have no issue?
I'm considering sending the phone back to manufacturer to be honest I think it may just be a faulty device or something!
I bet its microusb port fault
Had a similar issue on Windows 10 , if that's what your running let the phone be connected, uninstall the driver from device manager, and then install driver select have disk and select the basic mtp , if this doesn't help connect to Microsoft support and they'll guide you through it , worked for me , my phone used to detect on other laptops but mine , also I could connect other phones on mine but not my phone, hope this helps
same issue here

Categories

Resources