Ok so I am trying to plug my phone into pc using usb cable so i can use odin. But my computer doesn't recognize my device. I've tried everything from uninstalling the drivers and reinstalling them restarted pc and phone. nothing works i did get it to read one time and was able to access my sd storage and then i tried to go into download mode and i plugged in usb cable and it didn't recognize so i got out of download mode and it didn't recognize the phone again. Then i plugged in my girls evo and it reads the phone all the time. Is there something wrong with my epic then? how can i fix that problem. seriously getting frustrated!!
Try not to double post. We will get to your issue eventually. Refer to the other case, as it has potential solutions available for your issue.
(I've dealt with this as well.)
When I plug my handset to ANY computer (with, without kies or drivers, it doesn't matter) the phone charges, but, nothing appears on the computer (no unknown device or recognizing the two drives of the phone, but not mounting them (as it did before)) on the phone.
The "USB" icon doesn't prompt and if I go to settings/wireless and network/ USB utilities, when I touch the USB mass storage button, it prompts me to connect cable, which is already connected.
-USB debug isn't activated (I've tried both)
When my phone is powered off and I start to charge it, the charging screen doesn't prompts, It just start booting.
I've tried different USB Cables.
The Phone is Official Stock Never Rooted (I discovered this trying to root it today)
Am I SOL if I want to root it without a working USB Data port?
Any ideas?
i would say make sure there's no dust/ buildup in the port. I had connection issues once to find a pocket lint cramed in there. next do all the other stuff. uninstall/reinstall drivers, diff usb port, diff pc, reboot. My symptoms were similar to yours but i was able to reboot into recovery/bootloader and use adb/fastboot no prob, so not sure. and I was already rooted/twrp recovery. might be worth it to try fastboot in bootloader just to be sure and get a recovery on it asap. If that works you should be able to recover stock or flash whatever, then test usb again in diff pc with fresh kies install. good luck.
Sounds like bad/improper USB cables to me, not all USB cables support data and charging, make sure you're using an official Samsung USB cable.
If you have a friend with a Samsung smart phone ask to try their cable.
Hi,
I have an Xperia Arc with PolygonKK 1.4 custom ROM.
I had a problem similar to what has been reported many times of Xperia S where the phone becomes soft brick if the battery was completely drained, and the phone was not starting or allowing me to recharge the battery. This problem was fixed by charging the battery outside the phone and then plugging it in and starting the phone.
The problem now is that neither my phone or my PC can detect that they are connected via a data cable.
I checked the cable with another phone, it works fine, and I am using the same PC that I have always used to handle my phone (on windows and linux).
When I try to access fastboot mode I see the blue LED but the PC detects nothing
Flash tool does not detect any mode connected (fastboot, ADB, Flash)
I tried cleaning the USB port with no result.
I think now that the port is damaged, but I still have a little hope that this is a software issue, is there a way to know what has happened to the phone?
I have the d2spr with OctOS 7.1.1 installed (from April 2017 I think). This rom has been awesome and I have been able to connect via USB and transfer files in the past but now I cannot. When I plug in USB I always get a charging indication on the phone but no evidence of a data connection either at the phone or the PC. I have the USB mode set to MTP but when I plug in the phone it acts as though I have Charging Only selected. Windows device manager shows no activity. There are no UNKOWN devices listed and the PC shows no sign of hardrive or processor activity when I connect the phone. I have tested with 5 different USB cables and three different PC's. They all behave identically. Additionally I have plugged the phone in while in DOWNLOAD MODE and still the behavior is identical. I have fresh samsung phone drivers installed. One of these PC's have seen this phone before the other two have not. I'm beginning to think my micro usb port on the phone has taken a biff but it has always and still does charged perfectly.
I could try a factory reset but that doesn't seem to jive with getting nothing in DOWNLOAD MODE. I haven't loaded ODIN to see if it sees the phone but even without odin loaded it should still load a bunch of devices in device manager.
EDIT: I have also booted into recovery and it also behaves identically when plugged into the PC - no response but it charges
Any ideas? I have searched the forums but no one I could find has this exact issue of absolutely no response from the PC.
Thanks in advance!
I have had this for quite awhile. USB port is done. It's also a very difficult repair. Now I use flashfire instead of Odin because of this. But flashfire doesn't do bootloader and modems are iffy. So only flashfire a version you are already on (nd8, ndc, etc.)
UPDATE: I was able to adjust the usb cable to just the right position for Odin to see it and was able to flash via Odin. The weird thing is no amount of wiggle gets windows to recognized it. Thanks for your response.
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.