Related
I was trying to put the hum/hiss sound fix on my sd card and I cannot get my pc to connect via USB...
My wife has a TP2 and it connects fine...
I have tried with/without the sd card in, rebooted the pc and phone, rebooted the phone while connected to the pc.... nothing...
wtf...
anyone else with this problem?
PS... NRGZ28 had posted a very basic rom for booting to android back in Feb and it is now gone from hotfile. Anyone know of a quick boot into android?
- Try a different computer
- Try a hard reset
That are the first thing you should do.
Tried hard reset...
Dif PC is not an option at the moment... I have rebooted...
Just flashed the ROM (NRGZ newest, thank goodness I had it on my SD card) and I still cant get it to sync...
I have attached the USB error I am getting... (Win7, new install)
The phone is not asking if I want to active sync or use as storage???? wtf...
FarBeyond said:
Just flashed the ROM (NRGZ newest, thank goodness I had it on my SD card) and I still cant get it to sync...
I have attached the USB error I am getting... (Win7, new install)
The phone is not asking if I want to active sync or use as storage???? wtf...
Click to expand...
Click to collapse
Reboot your PC? lol bet your tried that already...
Try this:
settings > connections > usb to pc > and disable Faster Data Sync then try. This way uses the generic usb drivers and maybe it will connect.
That did not work...
How do I get my Win7 laptop to see the phone with Android on it?
FarBeyond said:
That did not work...
How do I get my Win7 laptop to see the phone with Android on it?
Click to expand...
Click to collapse
dont think thats working yet
Ya I don't think that works yet, it's tied to Android software drivers and the use of the USB port, since there is no drivers to control the port only to charge battery. Windows thinks there is something there, but the phones USB can't communicate back....I think this is the issue or at lease after playing around with it on my phone anyway
Not that it's a huge amount of help but might troubleshoot down to the hardware level...if you go into bootloader mode on the phone and connect to USB does it connect?
I don't think you should go that deep and dirty. My touch pro 2 works only with only 1 (non-HTC) cable of the 10 i have at home, all are the "standard" mini-USB but only one works flawlessly for communicating/flashing/syncing, the other cables either do the same error - device not recognized - or windows says that the device could communicate faster - and only copies files slowly.
All in all: you should simply check with another USB cable or if you have the factory HTC cable try it with that. I noticed that the cable i am using other than the HTC one is a very good quality thick (low-resistance and double-shielded) USB cable and it never failed on me.
One other thing you should definitely watch for: plug the USB cable into the motherboard USB port directly (on the back of the PC where you plug the keyboard, mouse etc.), sometimes PC cases with front panel USB outputs simply die, or are wrongly attached to the motherboard USB header and it can cause the aforementioned problems too, not to mention if it is wrongly attached it could harm your phone too.
Last night I was getting ready to do my first root. Was watching the syndicate video, following along.
One thing I noticed last night, is when I plugged the phone in for mass storage, to copy the files to the sd card, I kept getting these two errors.
First, when installing the drivers after plugging the phone in, I was getting this cdc failed. You can see it in this picture...
http://i11.photobucket.com/albums/a183/lardo5150/cdcabstract.jpg
I also kept getting this "scan to fix" pop up for the M drive (my phone).
When I turned on USB debugging on the phone and plugged it in, it seemed fine, except I could not access the M drive on my computer, I would get this error...
http://i11.photobucket.com/albums/a183/lardo5150/insertdisk.jpg
I did some search and decided to try what another user tried, I formatted the sd card.
I then plugged the phone back in, and did not receive the "scan to fix" errors anymore and could access the SD card with no issues, but I could not access it still while in debugging mode.
Is this by design?
Samsung drivers are installed. Got them straight from the samsung site.
No yiu should be able to play with your sd card wgile in debugging
Did you turn on mass storage after usb debugging?
Sent from my SPH-D710 using xda premium
I couldn't access the mass storage in USB debugging for a little while. It turned out my drivers got slightly corrupted. I could do everything else but that. Went into Control Panel with USB Debugging on and found the driver listed as samsung android in USB in Device Manager and hit update driver and let it get it from Windows Update.
kennyglass123 said:
I couldn't access the mass storage in USB debugging for a little while. It turned out my drivers got slightly corrupted. I could do everything else but that. Went into Control Panel with USB Debugging on and found the driver listed as samsung android in USB in Device Manager and hit update driver and let it get it from Windows Update.
Click to expand...
Click to collapse
I will try that this afternoon.
How about that cdc? Any reason why that is failing?
Same thing.
Says the latest driver is installed.
It never gives me the option of choosing charging, mass storage, tethering like it does when debugging is off.
Any ideas?
Ok, so I found this some other forums.
Seems stupid, but I had no clue.
With my phone, with debugging off, when you connect the USB, it asks you what you want to do.
With debugging turned on, it does not, you have to tell it. Below is what I found....I feel dumb..
"Okay, so if you are freaking out, or can't figure out why your new Epic isn't being recognized by your computer, calm down. Some of you are probably already searching for drivers. Ya I already went through that freak out when I got my Vibrant. Okay, to mount your phone, and have your computer recognize the internal/external memory, do this:
Connect your phone to your computer via USB. Give it a few seconds.
Next, PULL DOWN your notification bar.
Next, tap your finger on "USB CONNECTED"
You then get a message asking if you would like to mount. Tap "mount" confirming you would like to do so.
Enjoy, your computer should now recognize the internal/external memory."
lardo5150 said:
Last night I was getting ready to do my first root. Was watching the syndicate video, following along.
One thing I noticed last night, is when I plugged the phone in for mass storage, to copy the files to the sd card, I kept getting these two errors.
First, when installing the drivers after plugging the phone in, I was getting this cdc failed. You can see it in this picture...
http://i11.photobucket.com/albums/a183/lardo5150/cdcabstract.jpg
I also kept getting this "scan to fix" pop up for the M drive (my phone).
When I turned on USB debugging on the phone and plugged it in, it seemed fine, except I could not access the M drive on my computer, I would get this error...
http://i11.photobucket.com/albums/a183/lardo5150/insertdisk.jpg
I did some search and decided to try what another user tried, I formatted the sd card.
I then plugged the phone back in, and did not receive the "scan to fix" errors anymore and could access the SD card with no issues, but I could not access it still while in debugging mode.
Is this by design?
Samsung drivers are installed. Got them straight from the samsung site.
Click to expand...
Click to collapse
I had the same issue with my epic, try using a different usb cable, the one for the motorola photon resolved all the issues I had with connecting to the computer, I found out thru experience that the stock cable when using windows 7 kept giving me the same error..
Sent from my MB855 using XDA App
Also, I've had success with rebooting both the phone but especially rebooting the computer and plugging the phone back in. Try a different USB port, some folks have 2 SLOW USB ports for mouse and keyboard (mine are in the back lower left...the fast ones are on the right and in front). Most folks have better luck trying rear USB ports (although I don't know why). First, try the computer reboot though...
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
Since I updated my phone to RR-N-v5.8.3 I am now unable to transfer files to and from a PC. When I connect the USB cable to the PC and choose USB file transfer on my phone nothing happens. It works with the PTP option but the Transfer files option isn't working. Can someone please help out?
USB File transfer was always broken on CM and now LOS. There's an easy workaround though
1. Connect the phone to pc via usb cable
2. Choose "tranfer photos(PTP)"
3. Now change it to "transfer files"
Cheers mate! Been banging my head against the wall about this
Also works if you turn on debugging. For some reason that's the only way mine gets detected.
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.