Related
Are you still able to connect your phone via usb with no problems? With drivers and odin still working?
Thanks!
Yes yes and yes it works fine
Sent from my ........
Odin'd my phone and my sisters vibrant yesterday. All is well.
Sent from my SPH-D700 using xda premium
Odin won't see my epic since I went to Windows 8 :/
Any thoughts?
Please?
xfilemanx said:
Odin won't see my epic since I went to Windows 8 :/
Any thoughts?
Please?
Click to expand...
Click to collapse
The only way I could get the drivers to install right on windows 8 was to boot into download mode and plug in to usb on computer... let it search and find them in download mode... worked for me when nothing else was...
___________________________________
My muffin is blueberry, what flavor is yours?
——————————————————
I actually came across a link to samsungs web site for some USB drivers.......I thought what the hell, I've tried everything else LOL, I installed them on my 8 box...and it actually worked, Odin sees my Epic now
did anyone get this to work? ive tried repeatedly to get my epic 4g (with keyboard) to be recognized by my new windows 8 computer and I cant for the life of me. The above does not work for me. Along with other suggestions ive read online.
i downloaded these drivers and even tried compatibility mode.
what i noticed is windows 8 isnt listed in the list of compatibility mode
http://www.samsung.com/us/support/owners/product/SPH-D700ZKASPR
My win 8 machine did just fine when I connected my Epic. Able to transfer files between them both and Odin worked with no issues.
I did find, however, if you download the new drivers - win 8 has a hard time seeing the Epic. I also have Zentimo Storage Manger installed and it actually reads the Epic as a Linux Card Reader.
niteNarmor said:
My win 8 machine did just fine when I connected my Epic. Able to transfer files between them both and Odin worked with no issues.
I did find, however, if you download the new drivers - win 8 has a hard time seeing the Epic. I also have Zentimo Storage Manger installed and it actually reads the Epic as a Linux Card Reader.
Click to expand...
Click to collapse
which drivers do you have? can you post them so i can try to install your version instead and hopefully have better luck. The computer recognizes my evo lte right away without installing any type of drivers. but wont recognize the epic.
AL_CAPONE_X3 said:
which drivers do you have? can you post them so i can try to install your version instead and hopefully have better luck. The computer recognizes my evo lte right away without installing any type of drivers. but wont recognize the epic.
Click to expand...
Click to collapse
Not a problem. Give me a couple of minutes to find them plus I am currently doing maintenance to my media server.
As soon as I'm done I will post the drivers and links.
---------- Post added at 05:28 PM ---------- Previous post was at 04:45 PM ----------
AL_CAPONE_X3 said:
which drivers do you have? can you post them so i can try to install your version instead and hopefully have better luck. The computer recognizes my evo lte right away without installing any type of drivers. but wont recognize the epic.
Click to expand...
Click to collapse
Took the liberty to find the driver download that I have on my laptop. ----> Samsung Driver <----
Let me know if this helped.
Just in case you don't know (which I am sure you do), open with winrar or 7-zip and click on setup.exe.
niteNarmor said:
Not a problem. Give me a couple of minutes to find them plus I am currently doing maintenance9 to my media server.
As soon as I'm done I will post the drivers and links.
---------- Post added at 05:28 PM ---------- Previous post was at 04:45 PM ----------
Took the liberty to find the driver download that I have on my laptop. ----> Samsung Driver <----
Let me know if this helped.
Just in case you don't know (which I am sure you do), open with winrar or 7-zip and click on setup.exe.
Click to expand...
Click to collapse
i extracted and ran the exe and I get "the samsung android driver was not successful(9)" or something like that. Guessing the "9" is a error code?
one thing i might add is device manager doesnt even recognize the device when i plug it in. no sound notification like you would usually here.
Are you running 32 or 64? Those drivers are 64.
Also try a different port. I know if I don't use the sane point I have issues too.
One other thing might be your connecting wire. If you have another USB wire, I would try that too.
niteNarmor said:
Are you running 32 or 64? Those drivers are 64.
Also try a different port. I know if I don't use the sane point I have issues too.
One other thing might be your connecting wire. If you have another USB wire, I would try that too.
Click to expand...
Click to collapse
im running x64
ive tried the only other usb 2.0 port i have and tried even the 3.0 for the heck of it as well as another cable. But ill look for another cable and see again.
you think since the computer is still new enough where i can get away with a system restore to when i first got it without losing anything if that would be any help? maybe I messed up some how. maybe plugging in the phone before installing drivers messed it up?
also funny thing is i connected the phone to the computer in download mode as well and still was recognized not even as if it was charging.
forgot to add I was able to install your drivers once i did compatibility mode but my phone still wasnt being recognized.
I'm sure you know this as well, but is USB debugging checked?
You can try a system restore but my experience with that and windows 8 hasn't been good.
You stated when you connect your device the computer does nothing? Not even chime?
If that is true, it is your USB ports on computer not your phone.
Have you connected another device with the same cable? If so, what if anything happens?
niteNarmor said:
I'm sure you know this as well, but is USB debugging checked?
You can try a system restore but my experience with that and windows 8 hasn't been good.
You stated when you connect your device the computer does nothing? Not even chime?
If that is true, it is your USB ports on computer not your phone.
Have you connected another device with the same cable? If so, what if anything happens?
Click to expand...
Click to collapse
Yes tried usb debugging. Switched back and forth between pda and modem on diag uart menu thing. Tried different cables as well as different ports and yes other phones it sees and chimes the epic 4g charging light lights up but won't chime with computer.
I've also installed kies to see if that would help.
One last thing to try.
Go to settings/wireless - mobile networks/ scroll down till you find USB connection.
You may accidentally have check charging only. Check ask on connection.
niteNarmor said:
One last thing to try.
Go to settings/wireless - mobile networks/ scroll down till you find USB connection.
You may accidentally have check charging only. Check ask on connection.
Click to expand...
Click to collapse
I've been through usb debugging and the charge only the tether option as well as mass storage
Could the version have anything to do with it or that's its been flashed already from another computer.
Flashed from another computer should have nothing to do with it. I can take my device from desktop (where my device was flashed) to my laptop without any issues.
The only thing I can think of is, it has to your USB port on your device. For some reason, it is only letting you charge from a computer. That's why I thinking of the charge only feature. That would prevent your computer from seeing your device.
Even if it was the wrong driver it still would say "unrecognized device".
I would say go into control panel and uninstall driver but with it not seeing the device you can't do that.
Sorry. Right now I'm at a loss. I will keep thinking about it.
niteNarmor said:
Flashed from another computer should have nothing to do with it. I can take my device from desktop (where my device was flashed) to my laptop without any issues.
The only thing I can think of is, it has to your USB port on your device. For some reason, it is only letting you charge from a computer. That's why I thinking of the charge only feature. That would prevent your computer from seeing your device.
Even if it was the wrong driver it still would say "unrecognized device".
I would say go into control panel and uninstall driver but with it not seeing the device you can't do that.
Sorry. Right now I'm at a loss. I will keep thinking about it.
Click to expand...
Click to collapse
Ya Im lost too. I usually search and search and only post if I'm stummped and ny ideas are ran out of lol
That's what I do too. Are you able to connect to another computer with the same rom you are currently running?
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
@Istvan_86,
We should move the discussion for your problem here.
cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.
Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?
Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.
cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.
Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.
What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.
Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html
@clockcycle,
This solution works 100% too. https://www.ubuntu.com/
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!
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!
USB cable only charges the phone when connected to computer. Tried the following
1. Using 2 different cables which previously worked for data but phone only shows charging.
2. Using pc and Mac and both does not see phone. Looked in device manager of windows but it nothing shows up. Both computer previously used for data transfer on this phone
3. Looking inside usb-c port but no lint or dirt. Although just before update to September security patch my phone has some water on the screen which I wiped off. And the phone does not show sign of problem other than no data transfer to computer
4. Factory reset phone and same thing
5. No notification shown for changing charging only to file transfer
6. Computer doesn't Bing when connected.
What else can I try? Anyone can help or confirm if their usb-c works after September update so I can narrow down to hard ware problem.
Anyone diagnosed this hardware problem before?
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
jd1639 said:
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
Click to expand...
Click to collapse
I tried changing the options to MTP, PTP, midi, charge only, etc but non of them make any difference to the computer, nothing pops up and does not show as new item connected in device manager
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
jd1639 said:
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
Click to expand...
Click to collapse
Tried changing when USB connected and when not. Doesn't seem to make a difference.
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
jd1639 said:
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
Click to expand...
Click to collapse
I don't know how I can flash a previous firmware if I don't have USB access.. it's really frustrating. Looking from ifixit. It does not seem there is any chip near usb-c other than voltage control.
Can't seem to find how I can look at logs to know if USB has been engaged or if there is any error message. It's all dead end and my phone seem to be the unique case.
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
jd1639 said:
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Click to expand...
Click to collapse
USB worked fine, I am using it for Android studio, and transfered music across as well. Looked at the post and it seemed that has to do with device manager. Problem is mine does not show up any changes to device manager. I.e . No ADB or other device. Seemed like no data is exchanged and windows treating it like a battery or something
Any fix for this?
I've hit the same issue and wondering if anybody has a fix for this yet?
I'm using linux and seeing no usb activity at all from my nexus 5x after sep 17 update.
I've tried multiple cables. Cleaned the usb port on the phone. Multiple PCs.
I've connected to the phone using adb over tcpip and seeing nothing in logcat except battery logs when the usb cable is plugged in and out.
Turned usb debugging off and on.
I've set usb mode in developer options to mtp (it was on 'charging') and restarted the phone. Then find the option is forced back to 'charging.'
Logcat entries during boot show no failures in regards to usb connectivity.
Charging works fine but no data connectivity via usb at all.
Anyone got any other ideas?
Hello world.
I had the same issue.
To solve the problem :
- unlock developer mode
- switch on debug usb
regards
J.
I had this problem too- did not have to enable USB debugging though, just enabling the developer options fixed it for me. Which is odd because I definitely had them enabled previously... I guess a recent update reset that and for some reason all the USB data options are tied to developer mode now.
I've got 790 (american, as i know). The same issue, no response from service, guarantee, doesn't help, pc shows it as unknown device. some other bugs, mobile data fails, no sim detected after a few seconds, violet camera with no focus, but nice when the distance ia ok, so matrix works ok, but no stabilisation.
Then, bad battery, it seems that the bank ia ok, but controller works bad. it charges enough time to think that the capacity is not degraded. I suppose that usb controller (pc connection and fsat discharging) are nearby problems.
None of the above posts worked for me on my N5x (8.1.0 March), but searched some more and found this to work for me:
https://productforums.google.com/forum/#!topic/phone-by-google/DfpqXN1UfWY
Hello everyone. I'm just resurrecting this old thread so I can provide the solutions I have found to this problem. It appears this symptom has multiple causes, and there are different solutions depending on the cause. I have seen this problem twice now on my Nexus 5x (stock, no custom ROM) and solved it both times.
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
2. SOLUTION #2 - ClockworldMod USB Driver was installed. Replace with Google driver
The second time I encountered this issue, the Solution #1 above did not work. Surprisingly, the adb devices command successfully detected the Nexus 5x. It's just that the phone wasn't showing up in the Windows 10 File Explorer interface.
The root cause of this problem was that I had installed the ClockWorldMod USB Driver because I was playing around with their Vysor App (on a different phone.)
BTW, I think the Vysor tool is really nifty for screen mirroring purposes!
To resolve the problem, I replaced the ClockWorldMod driver with the regular Google USB Driver.
(Sorry, XDA is not letting me post links because of my low post count. The link is:
h++ps://developer.android.com/studio/run/oem-usb.html )
The procedure is:
- Download the Google USB Driver from the link above and extract the ZIP.
- Enter the Windows Device manager
- Find 'Android ADB Composite Interface'
- Open the properties of 'Android ADB Composite Interface' and you will see it is from ClockWorldMod.
- Right click on this Interface and Select 'Update Driver'
- Click on 'Browse My Computer for Driver Software'
- Click on 'Let me pick from a list of available drivers on my computer'
- Click on 'Have Disk'
- Browse to the Google USB Driver you downloaded.
- Select that driver and load it on top of the ClockWorldMod driver. (Windows may claim that you've got the best driver already installed, but ignore that.)
After re-installing the Google driver, the Nexus 5x appeared immediately in the Windows 10 interface for file transfers.
Cheers, I hope this helps someone out!
I have the same problem with LineageOS 15.1, I am not sure since when, because I don't use USB that often, but I it must have been after the second update for 15.1. ADB and FASTBOOT don't work.
None of the suggested methods work. I am on Linux, but I also tested the USB driver solution on a windows PC.
The problem is, my phone does not trigger any response from the system I connect it to.
On Linux an lsusb/dmesg shows nothing, and on windows it doesn't make the classic "ding" when I connect something to the USB port.
It is like my phone isn't even there.
In the developer options under networking and USB, USB was set to charging only. I changed that to MTP, but it didn't help.
Now I can't change it back (not that I want to, but just saying). No matter what I press on this menu, it always stays on MTP.
I am here because of adb not connecting tho, MTP is not my concern anyways.
I am not sure what to do, format data, and wipe system etc. and go for a clean install? The problem is, when I boot into recovery, ADB and FASTBOOT don't work either, i.e. my computers don't see an USB connection. So will a wipe even help? I am scared I wipe my phone, and then I can't connect via ADB in TWRP.
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
tantalfr said:
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
Click to expand...
Click to collapse
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
ufopaper said:
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
Click to expand...
Click to collapse
Never underestimate the power of a toothbrush
Bamboo-Toolkit said:
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
Click to expand...
Click to collapse
Amazing, this solved my problem. Thanks!
UPDATE:
I ended up just returning the phone and getting a new one (it was an Ebay seller so they didn't try to repair it).
New one connected instantly and I can use ADB and Fastboot perfectly.
Definitely something wrong with the first one, weird how the headphone adapter and OTG worked though.
Original post:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in device manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?
megaman1574 said:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in task manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?
Click to expand...
Click to collapse
Which version of Windows are you trying it on? Can you try it on a Win 7 machine? It's not the phone but the drivers. There are various threads around that will guide you thru it but you have to search some. Some are a little old but they should work. Keep at it, you'll figure it out. There is something in device manager that you need to tinker with if I recall correctly. Happened to me on my Pixel OG and it took me a few days to finally figure it out. Total pain but relief once you get it.
If you have a relatively new computer (Win 7 or newer) then it *should* recognize the Pixel. But sometimes Windows can be a pain in the ass. Download & install Android SDK which will install the latest Android USB driver, reboot the computer, then connect the Pixel again.
sublimaze said:
If you have a relatively new computer (Win 7 or newer) then it *should* recognize the Pixel. But sometimes Windows can be a pain in the ass. Download & install Android SDK which will install the latest Android USB driver, reboot the computer, then connect the Pixel again.
Click to expand...
Click to collapse
I don't think I can install any drivers unless the phone shows up as something in device manager, which mine doesn't
megaman1574 said:
I don't think I can install any drivers unless the phone shows up as something in device manager, which mine doesn't
Click to expand...
Click to collapse
Your computer must have Android USB driver installed before it will recognize the phone.
sublimaze said:
Your computer must have Android USB driver installed before it will recognize the phone.
Click to expand...
Click to collapse
I'll search this in the morning. He needs to uninstall something.. dang it I forget. I'll figure it out tomorrow. Or search my posts from a year ago I'm sure it's there somewhere.
Sent from my Pixel 2 using XDA-Developers Legacy app
sublimaze said:
Your computer must have Android USB driver installed before it will recognize the phone.
Click to expand...
Click to collapse
What I mean is it doesn't show up at all. When I plug the phone in device manager doesn't change.
bobby janow said:
I'll search this in the morning. He needs to uninstall something.. dang it I forget. I'll figure it out tomorrow. Or search my posts from a year ago I'm sure it's there somewhere.
Sent from my Pixel 2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I had a look through your post history but I'm not sure what I'm looking for... And I can't figure out how to search a post history
megaman1574 said:
I had a look through your post history but I'm not sure what I'm looking for... And I can't figure out how to search a post history
Click to expand...
Click to collapse
Yeah I know, only goes back for like a year or so. This is the guide I followed and it worked. Some still had problems but check out the OP and give it a shot.
https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625
This may be silly but when my phone was new I had the same issue. I had to go into the USB settings on my phone and change them from charging to file transfer.
I'm having similar issues to the OP, but I've had my phone since it was released. I have done everything known to man to try and get this working--updated Android Studio/drivers, both fixes listed HERE, tried numerous cables, rebooting phone and multiple PCs, still not getting my phone to get recognized at all.
My exact issue is this: I'm still on the August 2018 Security patch, so I wanted to update to October. Downloaded my files then went into Magisk and uninstalled (un-root) restoring stock boot. I waited a few hours before I could try to flash the OTA, but once I did, I connected the phone (USB-C to USB-C OEM cable) to my PC and it successfully connected in Debug mode. Ran "adb devices" and phone was seen. "adb reboot bootloader" successfully rebooted phone, but it did not go into bootloader mode for some reason, it just restarted in normal mode. The only problem is now the phone doesn't talk to my PC no matter what.... the USB-C to USB-C OEM cable doesn't even charge the phone let alone connect to give me file transfer options. If I try a USB-C to USB-A cable, the phone charges but the PC doesn't recognize my phone is connected. Debugging never works. Even my Car Charger (which is USB PD capable) doesn't charge the phone, I have to go back to my regular USB-C QuickCharge car adapter to get it to take a charger. I've disabled Debugging, changed default USB connection type to File Transfer, PTP, etc.
So, is there a way I can try to flash the OTA without connecting to a PC? Maybe even just flash the August Boot.img? I want to try updating the phone to see if that fixes my issues first. I am currently with an unlocked bootloader, no root and stock recovery, so I don't believe Flashify will work without getting root back... I think when I restored my stock Boot via Magisk, it FUBARed something. The only thing I can try is to use my USB-C to USB-A cable and see if fastboot recognizes the phone with that cable... the USB-C to USB-C cable is no dice in Fastboot.
Do you have another Android device? If so, (and it is rooted), you can run adb and fastboot from there. The binaries are available via the Magisk repository. Just grab a terminal emulator and a usb-otg cable and go to town. No driver issues, no fuss, no mess.
I was occasionally successful with a usb-c to usb-c cable, but sometimes the devices would get confused. The otg cable works every time, with the host end facing the adb/fastboot running device.
@hawkjm73 To whom are you talking to? If me, I don't have an OTG cable nor another rooted phone.
I did try the USB-A to USB-C cable and booted into Fastboot, which worked. I was able to at least boot into TWRP and get Magisk re-installed so I'm rooted. I booted the phone back up and still no USB recognition or Debugging. I'm going to wait to try a third PC to see if that will work in getting Debugging/ADB commands to work. All else fails, I'll just do a full Factory October flash without the wipe.
What's puzzling to me is why this all happened and why even my USB-C PD car charger won't work. Something strange is going on.
---------- Post added at 03:01 PM ---------- Previous post was at 02:25 PM ----------
Update: I grew impatient and decided that since my PC was seeing the phone in fastboot, I flashed the full October Firmware manually in fastboot (ran each command in the flash-all.bat one by one). As soon as it booted into the OS, Debugging and USB connectivity (both cables) turned back on. I haven't tested my Car USB PD charger, but I suspect that will work too.
I'm guessing when I uninstalled Magisk and tried restoring the stock Boot.img, something went awry and it was causing the connectivity issues.
So, if you can get your phone into Fastboot and your PC recognizes it, I would suggest a full system image flash, don't forget to remove the -w if you don't want to wipe.
megaman1574 said:
I know there are other threads on this but I really need some help on this.
I just got a Pixel 2 XL, but it won't connect to the PC. At all. No connection noise, nothing in task manager. The only change between plugged and unplugged is that the phone starts charging. No notification appears when I plug it in, it doesn't even try to connect.
I've tried three different cables, three different PCs, I've fiddled with USB debugging. I can't do anything with drivers on Windows because nothing changes in device manager when I plug it in.
I don't have any computers with USB C ports so I can't test that but I've tried all different ports on my PC (USB 2 and USB 3).
The headphone adapter works and when I plug in my old HTC U11's earbuds it says "accessory not supported" (which it's supposed to say, those earbuds only work on specific phones) so the port can't be completely broken.
I also tried plugging a USB drive into the full size to C adapter that comes with it and it reads it perfectly. I copied my music library onto the Pixel by putting it on a flash drive first.
I realise it may just be defective but it would be a huge pain if I got a new one only to discover that it was something that I'm doing or my PC causing it. And is it even possible to be defective when it can output music and even transfer files from a flash drive through that same port?
What else can I try?
Click to expand...
Click to collapse
Time for an RMA...just happened to me a month ago
WoJ... good follow-up update.
I ended up just returning the phone and getting a new one (it was an Ebay seller so they didn't try to repair it).
New one connected instantly and I can use ADB and Fastboot perfectly.
Definitely something wrong with the first one, weird how the headphone adapter and OTG worked though.