USB not detected bad port? - Nexus 6P Q&A, Help & Troubleshooting

I know what your thinking another newb not installing drivers properly or hasn't changed to file transfer mode.... This is not the case. I been installing adb and USB drivers since the og droid.
I have a real problem here....
I been on custom ROMs and wanted to fastboot back to stock however none of my computers are detecting my phone... Tried on 2 windows 10 x64 and one windows 7 x64 with same result. None even pop up a notification or ding a sound that the phone has been plugged into it. Nothing in device manager either. The phone charges at least I have also tried 4 different cables granted 3 came in a bundle pack that I do not trust but reviews state although not full speed they should do data....
Now here is the kicker:
If I turn off my phone and boot to the bootloader my 3 computers detect a device has been connected but the drivers fail and say something about the device signature can't be recognized. I have tried disabling the device signature validation in windows 10 with no luck and also windows 7....
Tried manually installing the drivers but says not compatible with device hardware
At this point I'm baffled luckily I'm rooted twrp and can download files to install directly but I rely heavily on fastboot as my goto if something goes wrong I'll be hosed!
I did factory reset and even flashed another custom rom to see if it was the ROM I was using.
Please help if you have any ideas to try. I have yet another cord coming Friday just in case the offchanse the main went bad and the other three from the bundle pack are ****

Sending back to google I hope they don't mind the custom rom, unlocked bootloader and twrp recovery lol

Related

Semi-Bricked....can you help?

Hi, been lurking around here for a good while now....fantastic website website and I've learned so much but now I have an issue.
For what ever reason my nexus 7 will not boot, I can get into fastboot and have been following the guides to do a full factory restore through fastboot. Everything goes fine until is comes to "Sending System" then just.....stops. I have used the nexus toolkit and also the official sdk drivers and fastboot contained there. I only have an old laptop as my main pc for some reason does not recognise the nexus.
I have tried alternative USB cable too.
Does anyone have any other advice.
Also the device is complete stock no custom rom has been installed so no custom recovery available.
I really appreciate any help.
Cheers!
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Try a search, shouldn't be hard to find what others have done with Windows 8 difficulties...
singlemanriot said:
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Click to expand...
Click to collapse
Go to Device Manager, show hidden devices and uninstall any Android or ADB related devices that you have. Disable USB debugging on your Nexus, then plug it into your PC and see if it's recognized. If it is, then re- enable USB debugging, then go to Device Manager and reinstall the Google USB drivers to get ADB support back.
Thanks for the advice, first thing I did was try searching....I have tried countless methods suggested but nothing works its like windows cant find the drivers. In the device manger its recognised but no diver installs no matter what I do. If I force the manual driver install it fails!? I have tried the Naked drivers, the SDK even making sure the media components of windows are installed properly

[Q] Device Manager Error 43 + No ROM installed

I'm having one heck of a problem here. So I've got my Nexus 7, on stock Android, but rooted and unlocked.
I wanted to try Paranoid Android, so I installed the TeamWin Recovery using the Nexus Root Toolkit, then flashed the ROM and wiped cache/dalvik. I tried to boot into the new ROM, but it just stayed on the boot animation. So I looked up the issue, and the solution seemed to be return to stock Android, then flash Paranoid Android again.
So I tried to use the 'Flash Stock and unroot functionality' of the Nexus Root Toolkit, which proceeded fine until the copying of 'system' onto the device... This lasted for about an hour without progress, so I decided to try again with a different version of stock Android. This too didn't work.
So then I (foolishly) rebooted the tablet. But when I got back to fast boot, it didn't show up in Windows (on either of the two machines I have here, and with two cables that have both worked previously, in multiple USB ports). The specific error is that it shows up as an unknown device (which is fine) but also in the device manager there is error 43, which states that the USB has malfunctioned so it has stopped.
For that reason, it's impossible for me to connect it to a computer or even re(install) the proper drivers for it. And as it doesn't have a working OS, i can't get to ADB either. So right now I can't think of anything that will work - no fast boot, no recovery, no connection to a PC.
Any ideas?
Really, no ideas? Come on XDA Developers, you're my only hope <3
Hi there!
ive got the same issue and i can tell what is NOT working to fix this problem:
deleting ALL usb drivers from pc and installing adb drivers, windows troubleshoot and nrt
i'm just like confused but i think it's all windows fault, if i could i would trie on linux or any other pc os

[Q] N4 won't boot, isn't recognized by any computer (adb, fastboot, etc.)

A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.

KitKat on Nexus 7 Failes

My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
In my win8 64bit the nexus 7(2012) does show up as a portable device, but MTP works and there's no issue with sending or pulling files. currently it's running stock kitkat 4.4 (KRT16S).
like you I suspect it's a driver issue with windows. If you could locate the device on device manager (try View\Devices by connection and look under PCI Express Root Complex and comb for USB Host Controller\USB Root Hub\Generic USB Hub), delete the entry for Nexus7 and scan for hardware changes again. This forces the system to look for correct driver(s) for your nexus.
Some guides on updating drivers are in fact concerned with the ADB interface, which is needed for USB debugging. In your case, if it's just accessing the internal storage of your Nexus you want to solve, those info may not be relevant.
krrasmuss said:
My problem is basically getting my nexus 7 to connect to the pc... This is what I've done. and what happends...
When I first connected it, I got no message at all, and nothing happened, then I changed the cables around, I changed the USB Pports... and by some mysterious wounder I found a combo of pad, port and cable that made my nexus go your connected as MEdia Device... BUT my computer wont see it.. hmm.. changed it to camera mode, and still nothing. Then I turned off USB Debug. Still nothing, but wen I turned it back on, I got the message that I was connected, and I got to install some drivers, and NExus popped up as a camera in windows 8... Started up the nexus toolkit thingy (I love simplicity) And there it popped up.. rebooted to fastboot, and no luck... windows wont recognize the damn driver. And I have done everything I can think of except install linux and try it there... IT wont connect in Fastboot mode, Not a chance... I've tried to unindatll all the drivers, and their files. everything I can think of... I've followed like 20 diffrendt howto s on the same problem, and no luck...
So how would a guy like me go about doing this in linux... is there a tool made for it? Do I need to do it all by commands? Is there a howto?
Click to expand...
Click to collapse
Installing fresh SDK won't hurt.
holynoob said:
Installing fresh SDK won't hurt.
Click to expand...
Click to collapse
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Update
peterk-1 said:
The USB drivers are available in a zip file here: http://developer.android.com/sdk/win-usb.html
and instructions are here:http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
For drivers and devices on your system browse http://www.nirsoft.net/ for the free utilities
DriverView
USBLogView
DevManView
USBDeView
Click to expand...
Click to collapse
Basically I would like to have ¤.¤ installed on my Tablet. Right now I have 4.2.2 SmoothROM installed, and whilst this works for me, I'd like to get the update.
In the past, I used the Toolkit to root and install stuffies... Until the last update to SmoothROM wheres I used GooManager thingy...
When I started this I got the Tablets to connect using PTP whilest in Android, but not in Fastboot mode. So I downloaded the 4.4.kitkat Offisial ROM and tried to install that in recovery, after a full wipe, BUT that ended in me having to install SmoothROM again. And now the Tablet wont connect at all... I have deleted all drives, and reinstalled them... I've tried 3 diffrent Wondows USB driver, but no luck there... I've tried like 5 diffrent USB data cables, in all 4 of my USB ports, on 2 diffrent machines, both win 7 and win 8... AND still no luck... now all the machine says that it cannot identfy the device...
Tomorrow, I will end up installing linux, and try there... At the moment I loathe all things called windows drivers...!!!!
EDIT:
Great news... I found a cable, I havent used in a long time. THis is the original cable that came with the Nexus, and I havent used it in a long time because it had some bad connections. Felt like the plug was loose, but now it made the whole thing work without any problems at all...
So I found the cable, used USBDeView to delete all drivers assossiated with the nexus. plugged it in while in fastboot, and BANG installed. rebooted it, and BANG installed.

[Q] Bricked Updating to CM11

Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?
I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?
Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..
Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!

Categories

Resources