Related
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
rjsmer said:
Some time the fault cud be the cable itself... I had same issue months ago my original samsung UsB cables didn't worked... It olwyz show the msg UsB not recognized... Then I tried with a different UsB cable (i had a Nokia UsB cable) and it worked...
Try it...
Cheers!!!
Sent from battery killer Jellybean GT-I9100 :-\
Click to expand...
Click to collapse
As stated, I have tried to use two other USB cables aside from just the one that came in the package.
Since all cables work on the laptop, but not this computer, I have pretty much singled it out to be a windows or a driver issue. :\
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
scott14719 said:
What are the specs of your desktop and the specs of your laptop? You claim it is a windows issue so I assume your laptop (that recognizes the phone) is not windows? Do you have Kies on the PC? If so, try to uninstall it completely and then install the individual drivers. Also, maybe just try updating Kies. You wouldn't need to install it, just download to your PC should work. As far as that goes, does Kies recognize the phone when plugged in at all? Does ODIN recognize the phone when plugged in? Maybe some of this will help you to find out if it is a driver issue or not. Good luck.
Click to expand...
Click to collapse
PC is i7 920, 12GB DDR3, Intel x58
Laptop is i5 2430M, 6GB DDR3, Sandy Bridge
Both are Win7 Pro, neither have Kies (I always just downloaded the drivers themselves) but I'm downloading it now to give it a try. As of now, nothing recognizes the phone on PC.
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Shuurei said:
Kies method didn't work either
I did "Troubleshoot connection error", which I guess reinstalled the driver, but it still didn't work.
Getting ready to dig out that Win7 Pro CD at this point... :\
Click to expand...
Click to collapse
Samsung Kies isn't yet compatible with the sgh-m919. Samsung rep told me soon last night
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
SBERG117 said:
Have you unlocked developer options yet and checked usb debugging? That might be your problem....
Click to expand...
Click to collapse
Enabling dev options and USB debugging was the first thing I did once I turned on the phone. Tried it both with and without, still not recognized either way. Still recognized on laptop.
I've also reinstalled windows altogether, since that fixed my issue last time around, but it's no good this time still. Clean install, formatted. No good. Previous steps from first post also taken, still no good. Tried the PDAnet method as well, no good.
At this point I am wondering if it might be an x58 issue, which would really suck, but it's the only thing I can think of given all the steps I have taken.
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
x58 issue
luckyduck69 said:
Okay... so what's the trick on getting Windows 7 x64 to recognize this device in Download Mode?
I have enabled USB Debugging. Tried several different ports on my Maximus V Extreme motherboard. I have tried using the PDANet drivers. Nothing works.Windows will prompt me with the "Device Driver software was not successfully installed" message. Anyone know a trick?
EDIT: FIGURED IT OUT. The last Android device I owned was the Galaxy S2. Now, back then it was understood that one should avoid Kies like the plague. However, in this case, it solved my problem. It installed all necessary drivers and I was able to communicate with ODIN. Cheers.
Click to expand...
Click to collapse
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Confirmed x58 and S4/general USB connectivity issues
Shuurei said:
I might have pinpointed the issue!
I tried Kies again, uninstalled, reinstalled, updated. No go. I did Kies by air and got a connection! So It's gotta be something with the USB.
Although I thought it was weird, I think it might be an x58 issue, I decided to pursue that anyways.
I found out that USB issues are common with x58 (per this forum: http://www.evga.com/forums/tm.aspx?m=159610 ) and will be trying a fix located here: http://www.evga.com/forums/tm.aspx?m=442244&mpage=1
I'll report back once I try this out. Hopefully it fixes it.
If not, I just ordered another USB 3.0 controller (completely unrelated, it doesn't need to be USB 3.0, just a different controller altogether, but USB 3.0 is backwards compatible anyways. I just needed one for blackmagic) which was PCI-e x1 (still dependent on x58, so it wouldn't have mattered, check diagram on fix link), which I WAS going to install in my PCI-e x1 slot, but that would have not worked! Going to install in a PCI-e x16 and hope for the best.
I'll reply back once I test that out too.
Click to expand...
Click to collapse
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Shuurei said:
In case anyone was wondering or stumbles upon this later, I have a few updates.
I got the USB controller today and plugged it into the PCI-e x16 slot, plugged in the S4 and it worked completely fine.
I also contacted EVGA about the issue and will get an RMA, so perhaps it's just a faulty unit. However, this seems rather common (refer to previous linked threads) in x58 chips.
I imagine it has something to do with power distribution with the controller, which is why upping the ICH voltage fixes it for some people. The USB controller is powered via 4pin, not dependent on Southbridge. I guess the S4 has higher voltage(?) requirements for it to be recognized. It seems rather strange since my other devices are still recognized, but well, that's what I managed to come up with.
Cheers.
Click to expand...
Click to collapse
Here's my craziness.
USB connection was working yesterday. Today, it is not.
I have uninstalled/reinstalled the Samsung Windows drivers/Kies
I have even adjusted my southbridge voltage to 1.2V in my BIOS
Still, no joy.
Curiously, when I boot the phone into download/ODIN mode and connect it, ODIN recognizes the connection. Reboot back into normal mode, and no USB connection is recognized. It is not showing up in my Device Manager as an unrecognized device. It just doesn't know it is there (unless phone is in download mode).
UPDATE: Solved. I had installed this ROM (http://forum.xda-developers.com/showthread.php?t=2261013). Reading back over the thread, it provided instructions for re-enabling the USB recognition of the phone. Had to re-enable the developer options and reset USB debugging. Makes sense now.
HI
I'm facing this issue today, I've tried two different laptops, both have Windows 7 x64 installed. I've tried every USB port on the two machines, I've tried with three different cables, I've downloaded and installed every USB driver there is. no use!
I'm out of options here and I can't think where to look further.
any help please?
shuurei said:
the device acts as if it is being charged.
Steps i have taken so far:
-uninstalled t-mo samsung mobile drivers and reinstalled
-deleted (uninstalled) all recognized usb devices via usb deview
-tried to connect without samsung drivers installed and all usb devices uninstalled
-tried to connect with samsung drivers installed and all usb devices uninstalled
-tried to connect without samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on samsung's site (1.5.14.0) and with the one found here on xda from 25apr2013 (1.5.23.0)
-tried to connect using different usb ports
-tried to connect using a different usb port on a different usb controller altogether
the kicker:
Device is recognized instantly... On my laptop.
This means:
-it is not the usb cable i am using (even though i have tried 3 different cables altogether regardless, including the one that came with the phone)
-it is not the device itself
possible: Windows issue? Last time this happened was long ago when i had gotten a mytouch 3g slide. I eventually just reinstalled windows since i had been meaning to then. I don't want to do it now though because i have too many things installed on here to start a fresh install... But i suppose if nothing else works, that's what i'll have to do.
Before that though, i would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
很想帮你啊 可是英文水平比较拙计
ok so now I'm guessing it is not windows, I tried on another machine with Windows Vista and got the same error.
any thoughts, anyone?
Did a factory reset for the phone
no it works!
don't know why
I just picked up this phone a couple days ago and last night tried to get the USB to work with no luck. I've tried everything I can think of. It does work in PTP mode but not MTP mode. I was able to use odin to on it though, so I was able to root it.
I've tried both in linux and on windows xp. I've never had an issue with any phone on linux and have installed/removed drivers numerous times on XP.
Tried 3 different cables, Factory reset with and without USB installed, tried pretty much everything I could find while googling similar problems (removing old registry entries, installed media player, etc)
I have adb installed on my linux box and even with debugging enabled I can't even get adb to connect to the phone.
Definitely something strange going on. Maybe I'll switch to cm10.1 to see if that makes a difference
I cant get my computer (windows 7) to connect with the phone when the phone is on, and was hoping some one might have found a fix.
This might fix it...
Shuurei said:
The device acts as if it is being charged.
Steps I have taken so far:
-uninstalled T-mo Samsung mobile drivers and reinstalled
-deleted (uninstalled) ALL recognized USB devices via USB deview
-tried to connect without Samsung drivers installed and all USB devices uninstalled
-tried to connect with Samsung drivers installed and all USB devices uninstalled
-tried to connect without Samsung drivers and other devices installed
-tried to connect using safe mode, both with drivers installed and not
---**these are both trying with the current one provided on Samsung's site (1.5.14.0) and with the one found here on XDA from 25apr2013 (1.5.23.0)
-tried to connect using different USB ports
-tried to connect using a different USB port on a different USB controller altogether
The kicker:
Device is recognized instantly... on my laptop.
This means:
-It is not the USB cable I am using (even though I have tried 3 different cables altogether regardless, including the one that came with the phone)
-It is not the device itself
Possible: Windows issue? Last time this happened was long ago when I had gotten a MyTouch 3G Slide. I eventually just reinstalled Windows since I had been meaning to then. I don't want to do it now though because I have too many things installed on here to start a fresh install... but I suppose if nothing else works, that's what I'll have to do.
Before that though, I would love to hear any other suggestions from anyone here.
Click to expand...
Click to collapse
Here's a link with a list of things to try what you may not have tried to fix your problems.
A small number of devices I have worked on have a weird thing, that the first time I plug the cable into the computer, it connects but won't show up on the screen. unplugging the USB cable from the machine for maybe 3 seconds, and reinserting makes the connection work... go figure! :>)
Aloha and Good Luck!
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335
Hello all!
First: I promise I searched the forums and google as hard as I could!
I'm running AOKP JB with CWM, although the problem was present on stock ICS from T-Mobile.
Symptoms: Computer and phone will refuse to acknowledge any connection (nothing shows up in Device Manager), except the phone will still charge. If I do the "remove the battery with USB plugged in" trick, the first time I do it, it will recognize an unknown device, but kies and adb won't recognize it. If I unplug it and plug it back in, it'll go back to not acknowledging any connection.
I previously programmed it (when I was still running stock ROM) via ADB via WiFi, but I need to be able to use ADB via USB. Besides, I can't seem to get ADB over WiFi anymore.
When I plug it into a different computer (Win7), it will, however, recognize my phone.
Earlier this year, before I ever tried programming via WiFi, it connected to my Win8 machine with no problem. I don't think it's a problem with the wifi setup though because the ROM was reinstalled and of course I've restarted ADB in USB mode in the months since...
What I've tried:
Reinstalling Kies
Reinstalling Samsung USB drivers
[^]Restarting the ADB server
Updating ADB
Trying different USB cables
Trying different USB ports
Toggling USB debugging
Toggling MTP mode
The UART thing from the dialer
Restarting the phone and the computer (of course)
Checking to see if my computer's USB drivers need to be updated
The android terminal command "setprop persist.sys.usb.config mass_storage,adb"
Pulling and replacing the battery while connected via USB
Crying in a corner
If anyone can help me, it'd be greatly appreciated! I'm all out of ideas and Google is no longer helpful =/
try to uninstall the drivers that are present anything samsung related to your drivers ... then connect the phone and let the process do its thing if you have the samsung drivers saved on your PC and the drivers still aint working update the drivers and then manually click where the drivers are to install them and hopefully it will work and when you tried MTP is it the only option it gives you no storage or anything ??... and is usb debugging on when you are trying all this ??
krazierokz said:
try to uninstall the drivers that are present anything samsung related to your drivers ... then connect the phone and let the process do its thing if you have the samsung drivers saved on your PC and the drivers still aint working update the drivers and then manually click where the drivers are to install them and hopefully it will work and when you tried MTP is it the only option it gives you no storage or anything ??... and is usb debugging on when you are trying all this ??
Click to expand...
Click to collapse
I tried on my work computer that didn't have any samsung drivers and when the "unknown device" dialog popped up it didn't do anything or install anything, nor did it show up in Device Manager. Unplugging and replugging it back in did not reproduce the dialog box. Togged USB Debugging and still no dialog box saying it recognized it.
The thing with the samsung drivers is that they're self installing so even if it popped up in Device Manager, I wouldn't be able to manually update the drivers =/
I tried MTP both with and without USB Debugging, although it also gives the option for PTP.
At this point do you think I should unroot and go back to stock? It's not been recognized on three computers now! =[
Are you using the stock cable? My computer wouldn't recognize mine without it.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
foltz61 said:
Are you using the stock cable? My computer wouldn't recognize mine without it.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Both the stock cable and a generic cable.
Similar problem
Similar problem as the OP. And hi guys, it's nice to be on these forums.
My device, when I plug it in using the stock cable, doesn't even charge. It doesn't show up in device manager, nor does it give me a notification, or say it's unsupported and bear that yellow icon. I have tried using different USB ports, I have tried the toggling USB debugging, I have tried restarting phone, computer, and taking out battery. I have tried that PDA/MODEM dialer trick. I am using 4.1.2 Jellybean, not rooted. (that WAS my goal,, until I hit this roadblock) I have not connected it to the computer in the past, it's relatively new. I'm thinking the cable is bust.
Any suggestions would be appreciated. It charges fine through a wall outlet plug, be it generic or stock.
so guys ive come to a conclusion i think its something in the samsung usb cables try getting yourself a blackberry usb cable , TRUST ME !!! ever since i got my phoness etc... tablet and yadi yadi samsung usb cables have always seemed to give me problems i think its because they are multi data/charging cables and when using the blackberry usb cable i have never ever once encountered a problem with any of my phones sd/storage problems do yourself a favor and pick up one of those cables and you will be golden !! if not then i guess im the only lucky one :LOL here you go http://www.amazon.com/Blackberry-Travel-Adapter-Micro-Cable/dp/B004VMVSYK/ref=pd_sim_cps_2 5 bucks!
Edit also one more test boot into recovery and click in the advanced menu and see if mount usb works for you in recovery mode ??
FIX (try using a generic cable)
I actually solved it on my own! After borrowing a generic cable from a friend it booted up! The Samsung cable was just not doing its thing.
yeah im telling you those cables they provide are JUNK!!! i only use my samsung to charge because they do that well but data they are str8 CRAP!! glad you got it up and going
OP
Hope OP will have the same luck as me...pray to the Android gods...
Lol:thumbup:
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I've been running CyanogenMod 10.2 on my rooted HTC One for a good long while now. Since the ROM worked so well, I never had the need to connect the phone to a computer via USB in quite some time. A few months ago, when I attempted to transfer some photos, I ran into a weird and frustrating road block; my phone is simply not being recognized by any computer <see here>
I have updated all drivers
I have enabled debugging in Developer Options
I have tried rebooting Fastboot in bootloader
I have tried using the toolkits
I have tried everything I think I know
The weird part is that the phone charges via USB connected to the computer.
Since it didn't effect much, I just figured it was a glitch and I never ran into a problem again--that is, until today. I hadn't used my MHL adapter with the HTC One (only my GNexus), but after reviewing an intended installation of a Pioneer Appradio, I wanted to ensure that my One would work with the MHL. Hooking up my One to the Samsung MHL adapter (and power supply of course), I get no display on my television.
I am now beginning to wonder if the USB port is damaged. Visual inspection doesn't reveal anything, but I am curious if anyone has had this problem and would appreciate any help. Is there any way to test if I've fouled up the port?
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
cmlusco said:
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
Click to expand...
Click to collapse
No and no
I installed Flashify and did install CWM 6.0.4.7 to see if it would help, but to no avail
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
cmlusco said:
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
Click to expand...
Click to collapse
I have tried adb, but the device never is recognized.
I'm currenty transferring my TWRP backup via WiFi.
I planned on switching to CM11 and see if I can't get it to work after that.
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Subscribed
I'm having the same issue. Stock non rooted and it will not connect. I have tried it on other computers cables ports everything.
Art2Fly said:
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Click to expand...
Click to collapse
You might try a different cord.
Open Device Manager in Windows and then plug the phone in. Do you see it in the list with a little yellow triangle? Do you see Android USB Devices listed?
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
beamer1341 said:
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
Click to expand...
Click to collapse
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Art2Fly said:
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Click to expand...
Click to collapse
Uninstall all HTC drivers and HTC Sync. Then connect the phone. DO NOT choose the option to automatically install any drivers.
Open Device Manager, find the phone. Select the option to manually pick the driver, and select the generic MTP device driver.
This is what worked for me, after countless attempts at re-installing various HTC drivers, different cables and ports, etc.
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Art2Fly said:
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Click to expand...
Click to collapse
Have you tried revoking the USB debugging authorization and then accepting the RSA fingerprint key again when connecting to PC?
Obviously it can't be an USB cable problem if you can connect to it in bootloader mode and use fastboot commands.
To clarify, the phone just charges when connected, it does not detect that it is connected to PC so debugging doesn't even trigger, neither does mtp. I don't even get the slow charging notification
Does it do the same when you plug it in and reboot the computer to "pick up" during boot up process? Or if you run a live CD? I never had an issue like that with my phone but I did have a similar problem with the USB external blu ray drive I bought some time ago. The pc just didn't detect it at all not on any of the ports until I rebooted my PC with the drive already plugged it and for some reason it picked it up. <Not a solution as I don't know what caused it to not be detected in the first place but still...
Not sure if it's an issue with the device(Phone for you, blu ray drive for me) or if it's a problem with the PC even though other things might still work for you as it definitely did for me(phone, headset, mouse, keyboard, usb extender + all the external hard-drives connected to it)...
Problem exists in all computers, Mac, pc, linux
Did you try what I suggest in Post #6 above?
This worked for me when I had the same issue. adb and fastboot would work, but it would not mount MTP.
And just in the last day or 2 I helped someone else with the same issue and fix.
The phone doesn't show up in device manager.
Have you modify the Kernel? (Applying some settings for example)
I browsed over the web for this issue and found some people with the same problems. They solved by removing the settings applied on the kernel or flashing a new one.
I've flashed various kernels and ruu, still same result
Still looking for help
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.