Has anyone figured out a solution to this issue? I can't get my computer to recognize my device any longer.
I've tried:
Uninstalling the driver
Manually doing a generic USB hub driver
Trying to forcefully install the google driver (gives the warning it's not compatible)
Different USB cables
Different USB slots
Unrooting
OEM re-lock
Enabling/disabling developer options
No idea what else the issue could be.
ADB, fastboot, or both?
Try a different pc or roll back Windows update. I've had this issue and it turned out to be a Windows update that screwed up the communication between my phone and pc.
Related
Hi,
I have a hobby to develop phone application.
I have no problem with connecting my HTC phone to my laptop for "USB Debugging connection" but my Verizon Samsung Galaxy s3 SCH-I535 could not get the "USB Debugging mode".
I DID CHECK the "USB Debugging mode in the system menu" however, my development environment could not get the debug mode.
Actually, when I plug in the USB with Galaxy s3, it shows the folder of the phone as usb data storage but not for debugging connection
Is there any way to get debug mode on my phone? Do I need to return this phone and wait for developer version of phone when Samsung launch in the developer site?
Thank you
I had the same issue where the galaxy only wanted to identity itself as a mtp or a camera device even though the usb debugging was enabled. adb devices command return nothing aswell. Found somewhere on stack overflow that installing the samsung kies suite would install the debug driver needed for adb to pick it up and it worked for me in my case, so hopefully that'll solve your issue as well.
I had that problem too, and I found it to be a driver issue. Grab the USB drivers from http://forum.xda-developers.com/showthread.php?t=1756885 (links direct to Samsung's site) and Win7 should detect everything.
I am having the same exact issues on my Sprint S3. I have installed all the drivers. Turned on USB debugging, and nothing! I am about fed up with this. I can transfer music over to the SD card without issue. When i try to put on anything other then media it tells me my device has stopped working or was unplugged. If i wasn't past my 14 days I'd return this thing and go back my Evo.
When I plug my Infuse into the computer running Windows 8.1, it is not properly recognized. I have tried different USB ports with different cables and I still have the same issue. The battery will charge, but in the Device Manager, the phone reads "Unknown USB Device (Device Descriptor Request Failed)".
Updating the Windows driver with the Samsung driver files does not work, and installing Kies mini doesn't help either.
Any suggestions or help with this would be greatly appreciated.
A friend of mine gave me today his OnePlus One. He had problems to connect it to his PC and then he wiped the whole device (TWRP) ...
So ... now there isnt a os on the phone and i cannot get it to work with USB.
i tried several drivers:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
- PdaNetA4180
- adb-setup-1.4.2
- UniversalAdbDriverSetup
- latest_usb_driver_windows
But no change. Tried 3 different PCs, but it doesnt work. It seems, that the Smartphone is broken and cannot establish a connection over USB.
adb sideload does also not work, it stucks at "Starting ADB sideload feature". fastboot mode is also not working.
USB cable is also not the problem, tried 2 different (both original).
Windows just saying "USB device not recognized" and its listed as unknown device and no driver works with the device.
Does anybody have an idea?
DerKiLLa said:
A friend of mine gave me today his OnePlus One. He had problems to connect it to his PC and then he wiped the whole device (TWRP) ...
So ... now there isnt a os on the phone and i cannot get it to work with USB.
i tried several drivers:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.33.0
- PdaNetA4180
- adb-setup-1.4.2
- UniversalAdbDriverSetup
- latest_usb_driver_windows
But no change. Tried 3 different PCs, but it doesnt work. It seems, that the Smartphone is broken and cannot establish a connection over USB.
adb sideload does also not work, it stucks at "Starting ADB sideload feature". fastboot mode is also not working.
USB cable is also not the problem, tried 2 different (both original).
Windows just saying "USB device not recognized" and its listed as unknown device and no driver works with the device.
Does anybody have an idea?
Click to expand...
Click to collapse
Did you try using OTG-USB?
TWRP supports OS installation via OTG-USB
http://m.youtube.com/watch?v=Vkcqhw0dvyo
I ordered yesterday an OTG Adapter, will try that.
Any other ideas?
So I just replaced the battery in my Pixel. It died during an update (thought I'd bricked the thing at first!), so it's currently bootlooping. No ROM or recovery installed. I'm able to access the bootloader though.
However, when I plug it into my computer (tested with two different computers and two different USB cables), it doesn't show up. Not at all. Doesn't just show up as "USB device" or "Mass Storage Device" or any of that - it doesn't show up at all. It's like I'm not plugging anything in at all.
Now, the thing does charge (when powered off and plugged in, it displays a battery icon), so I'm pretty sure I didn't damage the USB C port while replacing the battery. But it doens't show up in device manager, can't get it through the fastboot devices command, nothing.
Any ideas?
Thanks!
i've had issues on my Windows 10 laptop.. it shows up as pixel but wont' let me see it as a mass drive or transfer files... tried to update drives but fails...
1. Update USB device driver, generic USB hub or motherboard’s chipset drivers.
2. Disable USB selective suspend setting.
3. Use Windows USB Troubleshooter to troubleshoot for problems.
Hi,
I have issue after final update of Pixel 1 sailfish device, my device not recognized in pc/laptops, i unable to unlock bootloader of my phone for rooting. Anyone have solutions for this error, i have try many solutions from internet but none of these works for me.
---------- Post added at 09:12 AM ---------- Previous post was at 09:12 AM ----------
Hi,
I have issue after final update of Pixel 1 sailfish device, my device not recognized in pc/laptops, i unable to unlock bootloader of my phone for rooting. Anyone have solutions for this error, i have try many solutions from internet but none of these works for me.
If all the solutions above don't work yet, try to download & install the Google USB Driver at first.
Hey guys,
I am Currently attempting to unlock the bootloader on my Pixel 6a, but when I attempt to connect via fastboot in the bootloader my PC shows nothing connected? I can push commands through ADB while the device is booted and have full functionality, but as soon as I reboot the device into the bootloader I lose connection to my PC. OEM Unlocking is enabled in the settings and I have toyed with updating it to the latest update and factory resetting the device. It shows correctly in device manager as 'Pixel 6a' while USB Debugging is disabled and as 'android composite ADB interface' while it is enabled.
To clarify as I am sure many have seen this issue before I do not believe it do be a driver issue as the device will not show up at all in device manager, not even showing with the incorrect driver (No ding to indicate a device has been connected). I have tried using 2 different USB C -> A cables in all slots of two entirely seperate PC's (Both running Windows 10). When I enter fastboot with OEM Unlocking disabled it acts no different to when it is enabled.
I appreciate any help or insight any of you folks can give me.
Device is currently running Android 13 Build number TQ2A.230505.002 if you need anymore info please let me know.
The OEM Unlocking toggle does not affect whether USB function works. It is only a "safety" that allows unlocking the bootloader.
Have you ensured you've installed the correct drivers? Google USB Drivers
I have spent a long time looking at drivers, but I have no device to install the drivers to as the connection drops out once I eneter the bootloader. I have used Zadig in the past to install the correct drivers for devices but when I reconnect the device while I have it open it cannot even detect a new device being connected to the PC. (Also no audible tone which would be heard even with incorrect drivers) I actually only recently used Zadig to install the correct WinUSB drivers for my S10e in which I connected it to my PC in download mode (Queue audible ding) and used Zadig to overwrite the incorrect driver with the correct one. It's almost as if the device will not communicate while it is in Bootloader mode?
I assume you have checked with the 'fastboot devices' command to see if your device is connected when in fastboot mode?