I'm having issues with my laptop detecting attached adb devices (Thunderbolt specifically). I can get my main computer to recognize/detect an adb device. I will then disconnect my phone from my main computer and plug it into my labtop, and yet my laptop will not recognized there's an adb device attached. Regardless of the following, i still can not get it to work on my laptop: Closing CDM, disconnecting the phone from the computer, plugin the phone back then pull up cmd (or pull up cmd and then plug in phone -ive tried every common sense trick there is).
Whats going on with my laptop that will not allow it/android sdk to recognize the device? How do I fix this?
PS in case it needs to be mentioned, yes i have USB Debugging selected (thats why i am able to get the one computer to recognize it).
never mind i'm an idiot, since i manually add the script in for the USB drivers i forgot to select where to pull the drivers from in device manager. Sorry about this post, please delete it.
Hi
Wondering how to set my new z5 in ptp mode, so i can use helium to transfer my userdata from games to new phone.
Im looking for that answer too, just bought z5c.
Hi, I just did a Helium Backup yesterday, you don't actually need the ptp connection. Go into the device manager and right click on "ADB device" (it has a yellow triangle icon on it) and reinstall driver from your pc, choosing "ADB interface". Then disconnect the device from the computer, close helium on the computer and reopen, then reconnect. The connection will establish. That was my experience, YMMV but fiddling a bit can help. I hope you succeed
The steps I did to enable PTP mode so I can use adb:
- plug the phone into the PC USD and install normal drivers
- install Helium backup app on the phone. Run Enable PTP from Helium. It will not work, but will pop an ADB unknown driver in your computers Device Manager
- Download Sony ADB drivers: http://developer.sonymobile.com/downloads/drivers/xperia-z5-compact-e5803-and-e5823-driver/ and then unzip
- in device manager, right click on ADB Device, Select update driver, select Search Location and point to the drivers unzipped in the step above. Make sure you include Search Subfolders. The driver will be detected and you can install it.
- In helium app, enable PTP
After this I could use ADB!
After doing this, my phone rebooted and then could not be seen by Windows. So there are no recognizable drivers for windows? Sony PC Companion re-install did not reinstate the drivers.
Anyone know how to fix?
Trying to save on battery and not use the hotspot I thought I'd try USB tethering. I am able to USB tether and connect to the internet via USB tethering. However, there are two devices in Device Manager with yellow exclamation triangles: CDC Serial and LGE Android Phone. I've searched and searched but am unable to find the drivers for these devices.
CDC Serial
Hardware Ids
USB\VID_1004&PID_62C4&REV_0310&MI_02
USB\VID_1004&PID_62C4&MI_02
Install Error
E0000203
LGE Android Phone
Hardware Ids
USB\VID_1004&PID_62C4&REV_0310&MI_04
USB\VID_1004&PID_62C4&MI_04
Does anyone know where I can download the drivers for these? I've tried the LGMobileDriver_WHQL_Ver_4.0.4 with no luck.
Thanks!
I finally found the drivers on the CD partition that came up when I plugged my phone into the computer. I quickly copied the files to the hard drive from the CD partition to the hard drive. Then I installed the drivers through Device Manager. I don't know if it really matters or not but I can't stand having any yellow triangles in Device Manager.
When i turn on USB Debugging then what happens to android data files ( ex: /data/data/com.android.providers.settings , /system/build.prop &/or any others?)
Nothing.
USB debugging basically enables the Android OS itself to communicate with a Windows, Linux, or Mac computer. It acts as a connection bridge that allows software tools and drivers for Android as ADB & Fastboot to recognize your device when connected via USB.
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
That's strange, either your port is damaged or you don't have drivers installed. I've heard if this happening on Windows 11, never had a problem on Linux
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
Do you have the latest USB drivers installed?
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
The drivers are installed. My home pc is what I used to unlock/root the phone.
When I look at Show Hidden Icons -> Safely Remove Hardware and Eject Media, there is an option to remove Pixel 6. Yet it doesn't display under File Explorer or XYplorer.
If I start up my Arch (linux) vm with VMware Workstation Pro under Removeable Devices there is an entry for Google Pixel 6 with the option to Connect (Disconnect from Host). The contents can be under Arch.
Have you tried different cables & different ports? Sometimes the cable is the problem for me.
Different cables/ports had no effect.
I've got the same issue, what's weird is I can move files with ADB but can't in Windows.
If you figure anything out please hit this back up?
First make sure you have a good usb cable.
Some cables are only made for charging.
Second install the USB drivers from Google.
If you can transfer files, but can not use ADB/Fastboot, then it is a driver issue.
vandyman said:
First make sure you have a good usb cable.
Some cables are only made for charging.
Second install the USB drivers from Google.
If you can transfer files, but can not use ADB/Fastboot, then it is a driver issue.
Click to expand...
Click to collapse
Cables/drivers are good. ADB/fastboot work fine it's the transferring of file/recognision of device in windows explorer that is the issue.
thecdn said:
it's the transferring of file/recognision of device in windows explorer that is the issue.
Click to expand...
Click to collapse
Switching from charging mode to file transfer mode in the Connected devices/USB menu should give you access to Android's internal storage from Windows. USB debugging or other Dev options aren't necessary.
I had this same problem. Connecting to pc would show connection options but they were all greyed out and the phone would only charge. I couldn't find any option in the standard settings to change this.
Eventually I found 'default usb configuration' in dev options. Default was set to 'charge only'. You can sort it from there.
edit to add: although re-reading op you may have tried this already.
I solved mine by setting to PTP mode then the PC started to recognize the phone connected
thecdn said:
My phone is not recognized by either my home or work pcs. I've googled and did the basics - enabled usb debugging, preferences set to file transfer. I've never had this problem with a phone before.
It will connect to a usb stick via adaptor so I can transfer files with a multi-step process. This is a pain.
Click to expand...
Click to collapse
It's the stupid Windows drivers. There is an .inf file you need to either edit or delete but I forgot which. Might be wpdmtp.inf in the windows directory, right click and install. You might have to uninstall the driver in device manager first, the one with the exclamation mark if it's there. Sorry it's been about 3 or 4 years since I have done this but it's most likely a driver issue.
Mike Tanner said:
I solved mine by setting to PTP mode then the PC started to recognize the phone connected
Click to expand...
Click to collapse
I'm checking this on my work pc. It gives me access to DCIM and Pictures folders only. Which give me something to work with at least.
thecdn said:
I'm checking this on my work pc. It gives me access to DCIM and Pictures folders only. Which give me something to work with at least.
Click to expand...
Click to collapse
I agree about drivers, that they're either corrupted or incomplete. What's going on in Windows Device Manager when the phone is in a certain state?
During normal operation I assume the general purpose driver is always visible.
Device Manager > Portable Devices > Pixel 6
In fastboot mode with USB debugging enabled, is this driver showing up?
Device Manager > Android Device > Android Bootloader Interface
While Android is running with USB debugging enabled, do you see an ADB driver (the daemon may need to be started)?
Device Manager > Android Device > Android Composite ADB Interface