So ive got back from work, and plugged my Motorola defy into my p.c for its usual charge and - "USB device not recognised" followed by any other usb device failing/malfuntioning.
ive just tried it connected to another p.c (XP) and that says power surge on usb hub.
the Defy is not acknowledging any usb connection at all, but will charge from its mains charger.
ive tried re-setting it, re booting both the p.c and the phone, but all i can get is device not recognised.
this is an un-rooted standard defy, running the 2.51 firmware android2.1, as it came out of the box.
help.
Does this look like a return item or is it a software bug?
up until now I havent had any problems at all.
maybe your usb cable has a problem?
Quick one for everyone,
If you're following instructions for flashboot and adb etc, and you're experiencing USB errors, or just FAILURES..... i've found that there's 2 problems i've come across which quickly resolves things:
1. You are plugged into a USB3 port - for some reason, my usb3 port gives me errors, and not my usb2, try switching different ports
2. You are using a faulty cable - i bought a longer microusb cable from ebay, and it worked fine for a while, then things started to go funny, copying and accessing the phone took a long time etc, and of course flashing didn't work... then realised the cable was stuffed, and went back to my short htc oem cable, and all is good
From a guy who finally worked out how to upgrade from ICS to JB, have fun all!
I suppose that its "fastboot"?
Anyway, have fun with jellybean
haha yes my bad, fastboot, not flashboot.
Also, one more advice that I can give that took me ages is... when flashing RUU... if you're getting battery less than 30% error (even when i was at 99%), or usb connection error.... i overcame both of these by booting the phone into fastboot mode. None of the guides out there say you have to do this...
Hey,
I have been looking on the internet for this for hours, no solution found, but found a lot of people with this problem.
My laptop (windows 8) only has USB 3.0 ports, no USB 2. Appearently it seems to be impossible to update a Sony phone via computer by connecting it to a USB 3.0 port. During the process, the phone shuts down automatically, and when it reboots, it is no longer recognized by the computer (it should reboot in flash mode, but it doesnt). I've tried both PC Companion and Sony Update Service, both give the same result.
The solution I did find on the internet was: try connecting via USB 2. I dont really have another computer available, tried it on someone else's laptop, which was a very old one, this gave me an error, probably because of other problems with the laptop.
My question is, is there ANY other way to make this update work via USB 3? And preferably a way that is understandable for someone with minor knowledge about the technical aspects involved
Thanks
My laptop has 3 USB 3.0 Ports and 1 USB 2.0 port. I've been always using my Xperia Ion with the USB 3.0 port and it works fine with flashtool as well. Try a different cable.
ARNOB said:
My laptop has 3 USB 3.0 Ports and 1 USB 2.0 port. I've been always using my Xperia Ion with the USB 3.0 port and it works fine with flashtool as well. Try a different cable.
Click to expand...
Click to collapse
Oh... thats nice (for you). However, it doesnt work for me, with neither usb port, as is the problem for a lot of other ppl appearently...
I only have 1 cable, so cant try another one, the cable is not the problem though I guess. Since in all cases the cable works fine and the phone is recognized by the computer, except at the moment it should reboot in flashmode when reconnectint it to the laptop (during updating). Googling the problem yields alot of ppl having this problem, only nowhere a clear solution...
I've been trying to go through the update process for 10 times now, just doesnt work
Today I first used an OTG adapter, after last week OTA update, but to my surprise it no longer works.
I've tried with a couple of different adpaters, with mouse and USB drive that previously worked, but neither one works now.
Can anyone confirm? I'm on stock 2.20.40.58, bootloader locked, no root.
EDIT: Now it seems that my phone isn't even recognized in my PC ( I'm at work at the moment, and I used a couple of generics microUSB cables, with the same results ), only charging works fine. Did something broke? Or it is just me
I'm on the same firmware version and I can confirm that USB OTG works. Also the phone and external memory card are detected when a USB cable is plugged. in(tried 2-3 generic cables as well as the ASUS cable). You may want to update your USB drivers for the PC to see if the phone gets recognised.
N15H4NT said:
I'm on the same firmware version and I can confirm that USB OTG works. Also the phone and external memory card are detected when a USB cable is plugged. in(tried 2-3 generic cables as well as the ASUS cable). You may want to update your USB drivers for the PC to see if the phone gets recognised.
Click to expand...
Click to collapse
Thank you, now I'll check it more thoroughly when I get home.
I've managed to replace the USB board, and now OTG USB is working back, the phone is recognized on PC, but says "Device descriptor request failed" (I've tried with W10 on two different PCs, same results). A thread in ZenTalk mentions the issue in a Zenfone 5, but did all with no resukts
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.