Hi everyone!
I'm trying to get my Nexus 7 2013 to work with Windows 10.
However, when I plug it in I get an error saying that the device is not recognized. It doesn't even show up properly at Device Manager.
I can not update or change the driver. It's driving me kind of insane. There's no OS on my tablet so I need a direct USB connection to send files.
Has anyone worked out a fix for this issue?
Nexus device drivers for windows 10
Did you download the google device drivers for Nexus devices? Just do a search for Nexus Device Drivers in your search engine.
Is your bootloader unlocked and do you have a custom rom installed? This will allow you to accomplish both tasks with a single click. http://forum.xda-developers.com/showthread.php?t=1766475
Hope this helps.
Do not forget to give thanks if it works.
gn
ev1lchris said:
Hi everyone!
I'm trying to get my Nexus 7 2013 to work with Windows 10.
However, when I plug it in I get an error saying that the device is not recognized. It doesn't even show up properly at Device Manager.
I can not update or change the driver. It's driving me kind of insane. There's no OS on my tablet so I need a direct USB connection to send files.
Has anyone worked out a fix for this issue?
Click to expand...
Click to collapse
georgenazar said:
Did you download the google device drivers for Nexus devices? Just do a search for Nexus Device Drivers in your search engine.
Is your bootloader unlocked and do you have a custom rom installed? This will allow you to accomplish both tasks with a single click. http://forum.xda-developers.com/showthread.php?t=1766475
Hope this helps.
Do not forget to give thanks if it works.
gn
Click to expand...
Click to collapse
Yes, I did. I also downloaded them from Skipsofts Toolkit. For some reason Windows does not want to use them.
Sent from my P01M using Tapatalk
If u click on the link in my first reply it will take u to a different toolkit specifically for Nexus devices.
Are you using a USB 2 or USB 3 port? I used to have problems when I used a USB 3 port.
I know this is obvious but I thought I should mention it, did u uninstall the ADB drivers and re-install the google nexus drivers?
Good luck again.
gn
ev1lchris said:
Yes, I did. I also downloaded them from Skipsofts Toolkit. For some reason Windows does not want to use them.
Sent from my P01M using Tapatalk
Click to expand...
Click to collapse
Wugs Toolkit did not work.
I'm going to try a Windows 7 USB flash drive. Hopefully it's more of a Windows 10 driver thing than USB 3.0.
Windows 7 didn't work. Going to try Ubuntu Live USB.
This is really getting on my nerves.
Is there an adapter I can get that will change USB3 to USB2?
Tried the whole Linux thing. Didn't work. My Zenfone however works like a charm.
I give up.
Rest in Peace Nexus 7 2013
ev1lchris said:
I give up.
Click to expand...
Click to collapse
Hold on, "only the white light at the bottom turns on" - is it still the case?
If no, please post VID/PID descriptor from Device Manager in Windows or 'lsusb' in Linux.
If yes, no point of struggling with USB as it will be either:
VID_05C6&PID_9008
VID_0000&PID_0000
and there is nothing you can do with it anyway.
The white light at the bottom, in this context, usually indicates a faulty battery and no recharge can fix it. I remember that you posted a few times about decreased SOT, which eventually leads to completely dead battery. You can confirm it if you disconnect the charger, take the N7's back off and measure voltage between the battery plug's pin #1 and #6. If it is below 1V, then there is no doubt the battery is faulty. Some try to 'kick start' it but it is a waste of time, just replace it.
My battery is fine. It's new and holds a charge.
The problem is neither Windows or Linux want to recognize it to push files to it.
At least I can watch the pretty Google boot sequence.
Is it possible I damaged something when replacing the battery?
ev1lchris said:
Is it possible I damaged something when replacing the battery?
Click to expand...
Click to collapse
No.
While reading about this problem on three threads already I noticed that you only try to connect to TWRP on ADB/MTP, which may be damaged for some reason. Let's try a completely different USB connection protocol:
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run: fastboot getvar all
You can run the fastboot app from Windows or Linux...
on Windows install NRT and run it from "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data" folder
or run it without installation from live Linux
If you are successful in getting normal output from "fastboot getvar all", proceed to OS reflash.
If not, post USB VID/PID while in fastboot connection.
Thanks, I'll try this. However, Windows can not detect the Nexus 7 even when in the Bootloader.
ev1lchris said:
Thanks, I'll try this. However, Windows can not detect the Nexus 7 even when in the Bootloader.
Click to expand...
Click to collapse
No worries, but I still need the USB descriptor of a failed connection in fastboot/bootloader mode...
on Windows, run UsbTreeView and post 'File - Save full report'
on Linux post the output of 'lsusb'
Well, perhaps something isn't right after the battery replacement after all
The wide silver ribbon cable which goes across the battery, connects USB data lines from the daughterboard to motherboard and it might be partially disconnected. Please try to re-seat and re-lock it on both ends.
:highfive:
k23m said:
No worries, but I still need the USB descriptor of a failed connection in fastboot/bootloader mode...
on Windows, run UsbTreeView and post 'File - Save full report'
on Linux post the output of 'lsusb'
Well, perhaps something isn't right after the battery replacement after all
The wide silver ribbon cable which goes across the battery, connects USB data lines from the daughterboard to motherboard and it might be partially disconnected. Please try to re-seat and re-lock it on both ends.
:highfive:
Click to expand...
Click to collapse
I think I may have accidentally damaged the silver ribbon when installing the battery. Some of the ends are messed up.
As for the VID and PID I took a screenshot. I can still run USB tree.
ev1lchris said:
I think I may have accidentally damaged the silver ribbon when installing the battery. Some of the ends are messed up.
As for the VID and PID I took a screenshot. I can still run USB tree.
Click to expand...
Click to collapse
No need, I see VID_0000 which indicates a hardware issue. If the cable can not be fixed, here is another one, but please check this video before replacement.
Cheers
:good:
When taking out the cable the first time I think I damaged some of the connectors.
Should be an easy fix.
k23m said:
No need, I see VID_0000 which indicates a hardware issue. If the cable can not be fixed, here is another one, but please check this video before replacement.
Cheers
:good:
Click to expand...
Click to collapse
Good news: The cable is installed, the PC can detect the Nexus 7, the Stock seems to have installed successfully.
BAD NEWS: THE TOUCHSCREEN IS NOT WORKING
What is going on? I hope this is a software issue?
ev1lchris said:
Good news: The cable is installed, the PC can detect the Nexus 7, the Stock seems to have installed successfully.
BAD NEWS: THE TOUCHSCREEN IS NOT WORKING
What is going on? I hope this is a software issue?
Click to expand...
Click to collapse
Good and bad news
Run TWRP3 and check if touchscreen works there.
If not, I think we're not done with the cable yet as it also connects touch to the motherboard.
I've watched some YouTube. I've deciphered that the wide cable is data and the narrow one touchscreen.
I've tried unplugging and plugging both. No luck there. I notice the tablet heats up sometimes too.
When installing I noticed a small plume of smoke. I hope nothing happened.
When it boots into the OS there is a crossed out square on the upper right hand corner now.
Any suggestions?
I put in the cable I kind of damaged back into the Nexus 7. Now it gets detected and the touchscreen works. I have no clue what happened here but it seems fixed.
THANK YOU ALL VERY MUCH FOR YOUR HELP. Much appreciation and love to the XDA community!
Related
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
maatsby said:
are you using the original cord that came with the phone? just any old usb cable won't work
also you can't flash a new rom without rooting and gaining S-OFF, you're unrooted and S-ON, that's why you get the "version is older" message
Click to expand...
Click to collapse
I bought the phone and it came with 1 cord (with HTC label) that can be connected to the charger, I guess there are only 1 cord for charging and connect to PC? This is the cord that I use. In addition to that I have also tried Motorola, Sony Ericsson (both also for Android phone) and Nokia cord but all can't.
The ROM is actually older version stock ROM from RUU.exe. I saw from few Desire thread they were using this method to restore the ROM to before the USB Brick condition so I thought to try it.
BUMP!
Anyone know what should I do to resolve this problem?
Are you running the very latest HTC Sync on your PC? I'm using 3.0.5606. You can get it here: http://www.htc.com/www/help/
Also, connect your phone and go into Device Manager on your PC. Check to see if you have an entry for Android USB Devices and that the phone shows up. See attached screenshot for how mine looks. This is the best place to check to see if your PC has installed the drivers correctly.
In answer to your question about the cable, yes it's the same cable that attaches to the PC or to the mains charger. I've sometimes had connection problems caused by a dodgy cable, but I've used others apart from the HTC one without issues.
Edit: Also, when you install HTC Sync it should warn you to disable Antivirus software during the installation. This can be really important! I ignored it the first time around, thinking it was just a silly precaution, and had loads of problems with the phone not being recognised. Had to uninstall, temporarily disable AV, and re-install HTC Sync. Once it has finished installing, you can turn your AV back on.
Thank you for your reply preacher6.
Yes, I'm using the latest HTC Sync, v3.0.5606, just downloaded yesterday and reinstall everything.
When my phone connected to the PC it didn't appear as Android USB Device on my Device Manager, it only appear as Unknown Device in USB Controller:
So I guess I can rule out the cable as I have tried about 4 cables already.
For the installation part, I have disable the anti virus and also running the setup program as administrator. When installing there is no problem whatsoever that crop out.
Another point is, even on Fastboot it appear as Unknown Device in the PC.
I would try to update the driver manually - right click on the Unknown device, go to "install driver" or "update driver", then browse to the "Program Files\HTC\HTC Driver" folder. See if it picks up and installs the correct driver.
I've tried manually update the driver as per your advise but it says there is no compatible driver in that folder even though androidusb.inf is in that folder.
I'm running Win 7 64bit. does the driver also work for 64bit OS?
Should do, yes, I'm on Win7 64 bit myself. There is this folder on my PC:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64
Is the unknown device present when the phone isn't connected? Just to make sure that is actually the phone - if it's still there when the phone isn't connected, it's some other device.
Otherwise try uninstalling the unknown device and then rebooting the PC, then forcing the installation of the drivers again.
The folder is same as yours.
The unknown device does not present when my DHD is not connected, so I'm certain it is the phone that appear as unknown device.
I have tried uninstalling the unknown device > reboot PC > installing the driver but it still won't install.
Another thing is, I check on the Device Manager > Unknown Device properties > Details" for it's Hardware Ids and it shows as USB\UNKNOWN. I think it should show a strings of the device id? Correct me if I'm wrong.
Yep, there should be a proper device ID string, on charge mode mine shows a hardware ID of USB\VID_0BB4&PID_0CA2&REV_0226&MI_01.
At this point the best thing I can suggest is to try on another PC. If it works, your drivers are screwed up and you'll need to strip them and reinstall. But if it doesn't work on another PC, it's possible you have a hardware problem with the phone.
xb360 said:
Good day,
I'm having problem with my DHD unable to be recognized in my Win 7 PC. I have already install HTC Sync and also tick on "Ask Me" for Connect To PC setting. I'm running on stock 3.13.707.4 ROM with S-ON and unrooted. Even restart to Fastboot my PC still unable to recognized my DHD.
From Googling it shows many Desire having USB-Brick problem, does this problem also applied to DHD? Is it my phone is hit by USB-Brick? Any guide to solve this problem? I've tried flashing older ROM via Bootloader and PD98IMG.zip but it won't allow saying something like the ROM is older version.
I just bought this used phone for about a week so I'm still not sure on how to solved this problem. any helps is much appreciated.
Click to expand...
Click to collapse
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
dmastman83 said:
Hi. This thread is pretty old but I'm wondering if you ever resolved the issue? I'm having exactly the same problem with my HTC One s and I can't seem to find a solution anywhere.
THanks
Click to expand...
Click to collapse
Yes. Holla if you still need help
marknoll said:
Yes. Holla if you still need help
Click to expand...
Click to collapse
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
FossaFX said:
I need help too (HTC Desire Z device)
Is it hardware problem? (I already purchased new system board).
For me it looks like hardware problem, because device does not accept bus address, do not show USB strings/VID/PID (Tried different cables/PCs/OSes (I have OpenSUSE linux, but phone does not connect to usb on any PC, Windows PCs even do not understand that something plugged in)).
No problems with USB-connector (checked resistance), but I do not see pull-down resistance with my tester.
But all other functions work well.
UPD. Tried to connect from FASBOOT/HBOOT/Android - the same result, device does not accept bus adress. Additionally it charges without problems, but when I connect phone to USB no pop-up/information at top bar appears.
Click to expand...
Click to collapse
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
marknoll said:
I am trying to understand what exactly are you asking me . are you asking me if the PC can recognize your device ?
Click to expand...
Click to collapse
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Install the SDK on PC and update all android versions.
Well guys it was just my PC, i made a system backup for four days and that was all the problem(the USB port of my PC)
FossaFX said:
Sorry, it looks like I explained my question wrong (I'm Russian, and English do not native to me). Let me try reformulate:
You said "Yes. Holla if you still need help" so I believe that you were able to fix "Device not recognized" problem. So I'm asking - how did you do it? Did problem was hardware or software?
For me (look at symptoms at my previous message) it looks like dead USB controller in phone. But maybe it very strange software problem (USB-controller firmware damaged)?
Did I explain it clear now?
Click to expand...
Click to collapse
After installing and updating SDK...go into platform folder and open it. Hold mouse in field and hold shift and right click mouse. Chose "open cmd here"..that will open a cmd prompt window. In regular mode on phone,type "adb devices" should return numbers (ex: hta3829g)..if in bootloader mode,type "fastboot devices" should return numbers.
This SDK helps PC see your phone when its plugged in. Especially handy when a PC won't install drivers for your phone
Sent from my ATRIX HD
Are you also stating that your device will no longer charge when plugged in?
Sent from my ATRIX HD
Just at the title says. Yes i have tried different ports and cords. All drivers are up to date. All cables and ports work as they all work with my nexus 7. What am I missing?!?!
ShadeXVII said:
Just at the title says. Yes i have tried different ports and cords. All drivers are up to date. All cables and ports work as they all work with my nexus 7. What am I missing?!?!
Click to expand...
Click to collapse
Enabled USB debugging?
Thought that may have been the issue... Enabled USB debugging still same issue.
Edit: If i change it to PTP i can see it as phone on the PC but can't view it MTP.
Try reinstalling drivers and reboot computer
ShadeXVII said:
Thought that may have been the issue... Enabled USB debugging still same issue.
Edit: If i change it to PTP i can see it as phone on the PC but can't view it MTP.
Click to expand...
Click to collapse
I think some drivers have to be installed for viewing in MTP..
I have provided a zip file of Asus Android USB drivers... There is a folder named MTP... I think you have to install those drivers.. These drivers are compatible with XP,VISTA, 7..
Please confirm the working of MPT/Drivers if successful
I have the same issue.
Windows 7 only recognises the ZF2 once out of around 10 connection attempts.
I found that deleting the USB common drivers and re-booting Windows works for one new connection, but after that the problem returns. I think the drivers that are automatically downloaded are not very reliable / stable.
I find that if I keep unplugging / re-plugging the cable, it will eventually recognise it.
It's a bit of a pain to be honest and it doesn't matter how many different cables or different USB ports I try it makes no difference.
I just spent 20 minutes with this issue ... until I realized I was using my HTC USB cable. I decided to follow the most common suggestion and plugged in the ORIGINAL ASUS cable that came with the ZF2. Worked flawlessly.
Hope you have the same luck!
Ended up being something wrong with a quick charge driver on my mother board with this. Ended up reflashing BIOS and removing that and it fixed my issue. Talked to other people as well and a lot are reporting they have to use the cable it came with as well.
ShadeXVII said:
Ended up being something wrong with a quick charge driver on my mother board with this. Ended up reflashing BIOS and removing that and it fixed my issue. Talked to other people as well and a lot are reporting they have to use the cable it came with as well.
Click to expand...
Click to collapse
That's great to hear!
I also have an Asus board, but good thing I did not install the Quick charger drivers! I would never guess that as the culprit!
lordpipa said:
Try reinstalling drivers and reboot computer
Click to expand...
Click to collapse
Please. tell me how to install Asus UDB Drivers from the Zip File on Windows 7
Did you had to reflash with adb sideload? or just going to the recovery mode and selecting hard reset?
Someone with more knowledge please help me.
I can not, for the life of me, get my computer to recognize my watch.
I've tried everything, I've tried installing the driver package another user posted.
I've enable usb debugging in dev settings.
I have adb working correctly but when I type adb devices it's blank.
The only glimmer of hope is I successfully connected my watch via bluetooth debugging and got a debugging dialog on my watch.
I've tried on two computers as well
I really need a detailed guide on how to get my computer to recognize this damn thing
Thanks - A very frustrated novice
Me too. Exact same situation. It was like i read my problem. Also i manage to unlock the device in fastboot mode. Adb in that mode is comunicating with the watch. Please help us. I dont know what to do anymore.
Sent from my SM-N910F using Tapatalk
The watch has no driver compatible with w8. I try pdanet and nO result. Please advice?
Sent from my SM-N910F using Tapatalk
Just managed to get my watch into fastboot mode but I still can't connect or recognize device in adb
Are you trying to connect while the watch is unlocked (screen on, not in ambient mode or off)?
brizey said:
Are you trying to connect while the watch is unlocked (screen on, not in ambient mode or off)?
Click to expand...
Click to collapse
No. The watch is awake
NxWorries said:
No. The watch is awake
Click to expand...
Click to collapse
Does your PC react at all when you plug in the USB cable? (Sorry if this is too basic.) Just wondering if its a bad charging cable.
brizey said:
Does your PC react at all when you plug in the USB cable? (Sorry if this is too basic.) Just wondering if its a bad charging cable.
Click to expand...
Click to collapse
Yes, my pc makes a noise and in my device manager the watch is identified as a Marshall London device. I think that's due to one of the many drivers I attempted to install. Thanks for your help by the way
NxWorries said:
Yes, my pc makes a noise and in my device manager the watch is identified as a Marshall London device. I think that's due to one of the many drivers I attempted to install. Thanks for your help by the way
Click to expand...
Click to collapse
Nevermind. It's identified as HUAWEI watch under the other devices section. I can't find a compatible driver
https://drive.google.com/open?id=0B6OEA3csBCnQU2dZSXVMTm9STDA
NxWorries said:
Nevermind. It's identified as HUAWEI watch under the other devices section. I can't find a compatible driver
https://drive.google.com/open?id=0B6OEA3csBCnQU2dZSXVMTm9STDA
Click to expand...
Click to collapse
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
I manage to install manualy usb driver from sdk directory. You have to update driver with those drivers.
https://youtu.be/RDA8PpPSFuk
https://youtu.be/FZu4GDf963M
Sent from my SM-N910F using Tapatalk
The watch was only recognize the first time.
On my case the phone are not recognized and the error message indicate:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
I must say that i´ve also that problem on pc and notebook running windows 10. usb port plugged in an nothing happen, no device recognition or something else. tried different usb ports, different machines, nothing...
Any ideas?
I have some problem how to solve??Any one have solve?
Thx
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Good luck!
edit - here is a fool proof method.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
SirRobin78 said:
I must say that i´ve also that problem on pc and notebook running windows 10. usb port plugged in an nothing happen, no device recognition or something else. tried different usb ports, different machines, nothing...
Any ideas?
Click to expand...
Click to collapse
I know it's been a long time but were you able to find a solution ? I'm having the exact same problem.
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Evnul000 said:
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Click to expand...
Click to collapse
Windows drivers 100%.
null0seven said:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Click to expand...
Click to collapse
I have tried it on both my PC and laptop with both windows 10. Does not work. My PC also has windows 7 still seems to not work. Are there any other drivers i might be missing?
i have also done some research that you should update your drivers from device manager. I dont see anything related to my device. i went to portable devices nothing and i dont have a other devices section in device manager. Any help?
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
null0seven said:
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
Click to expand...
Click to collapse
i am on the latest twrp. will blu-spark help fix it?
ive also found out theres no kedcom driver when i go to fastboot. i even reinstalled adb drivers to insure its there but it does not pop up.
You'll need to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
I once have kind of youre problem connecting to my laptop (win.10). But, at work, on that laptop, connection was ok (win.7).
I reinstal windows 10 and connection works fine, since.
I allways use latest TWRP & version of rom. I can't tell for sure what it's goin on with youre phone.
If i was in youre situation i format my phone (this will erase ALL in youre phone). And if PC still does not see the phone reinstall windows.
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
dentman said:
You'll bed to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
Click to expand...
Click to collapse
What are the driver links if you have? I already installed the OnePlus drivers.
ninjeratu said:
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
Click to expand...
Click to collapse
I used the OnePlus cable and another cable.
Driver issues win 10
Find the excellent tutorial here on drivers.
For some reason my phone didn't show up but was able to receive commands. It was frustrating because I wanted to use the all in one XDA product but couldn't.
Even if you installed drivers they can be broken!
Do drivers from scratch per xda tutorial. Don't forget reboot!
Try different cables and usb ports! My front ones never seem to work!
Don't just try fastboot commands also try adb. Like I said mine wasn't seen properly yet it took the commands.
Unless your windows is a years old install it shouldn't require reinstall.
Factory phone reset might help.
Best of luck!
So it looks like my USB C port may be fried. Had recently flashed Resurrection Remix and had used a usb thumb drive connected through usb a to c adapter that comes with phone to restore apps from titanium backup and copy files over no problem. Went to use the thumb drive again a while later and noticed that the prompt only came up to charge the device and choosing file transfer option did nothing. Rebooted to TWRP to backup and flash a different rom and noticed that my thumb drive was no longer recognized there any more either. Now when I connect to my PC with same cord I have always used, it always comes up with the windows error message saying it's not recognized and has malfunctioned. Have tried fastboot mode and booted up and always same message. Fastboot will not see the phone. I really don't think it's a driver issue at this point. I actually already have a replacement device coming for different issue and I'm wondering if I should try to flash stock June image through TWRP so at least it's on stock software when I send it in even if it's unlocked. Oh yeah and the device does currently charge still. Thanks for any help or comments as I probably only have one shot at this.
Reechings said:
So it looks like my USB C port may be fried. Had recently flashed Resurrection Remix and had used a usb thumb drive connected through usb a to c adapter that comes with phone to restore apps from titanium backup and copy files over no problem. Went to use the thumb drive again a while later and noticed that the prompt only came up to charge the device and choosing file transfer option did nothing. Rebooted to TWRP to backup and flash a different rom and noticed that my thumb drive was no longer recognized there any more either. Now when I connect to my PC with same cord I have always used, it always comes up with the windows error message saying it's not recognized and has malfunctioned. Have tried fastboot mode and booted up and always same message. Fastboot will not see the phone. I really don't think it's a driver issue at this point. I actually already have a replacement device coming for different issue and I'm wondering if I should try to flash stock June image through TWRP so at least it's on stock software when I send it in even if it's unlocked. Oh yeah and the device does currently charge still. Thanks for any help or comments as I probably only have one shot at this.
Click to expand...
Click to collapse
Just a shot in the dark, but when you plug in the cord to the phone does it snap in fully? I work in a very dusty environment and have to clean my port out with a tiny wire bent like a hook every few weeks or the plug does not stay in. It may very well not be your problem but just a thought.
CyberpodS2 said:
Just a shot in the dark, but when you plug in the cord to the phone does it snap in fully? I work in a very dusty environment and have to clean my port out with a tiny wire bent like a hook every few weeks or the plug does not stay in. It may very well not be your problem but just a thought.
Click to expand...
Click to collapse
Thanks, I wish it was that simple but no luck.
Reechings said:
Thanks, I wish it was that simple but no luck.
Click to expand...
Click to collapse
RMA that thing if you've tried everything possible. Which, it sounds like you have ?
Badger50 said:
RMA that thing if you've tried everything possible. Which, it sounds like you have ?
Click to expand...
Click to collapse
RMA is en route and my USB just randomly started working again lol
Reechings said:
RMA is en route and my USB just randomly started working again lol
Click to expand...
Click to collapse
Doesn't surprise me a bit! Damn gremlins! ?
https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post76871322