I can not get my device to show up in almost every mode via usb. The ONLY thing that works, is, from recovery, choosing apply update from adb. Then, I can see the device as sideload with adb devices, but every command results in "error: closed"
When just in recover, download mode, or powered on, the device will not be recognized. I have tried Windows and Linux mint on my computer, as well as another mac computer, all with 3 different high quality cables that work fine for other devices.
In windows, device manager shows the error "Device descriptor request failed". This all started out of nowhere the other day.. I had it connected via mtp, it disconnected and reconnected itself a few times, then quit working all together.
I've tried HTC sync manager, as well as standalone drivers, but I doubt it is any computer issue since i have tried multiple OSs annd computers....
Any ideas? I'm trying to backup some files and finally get this thing running something other than stock.
Related
Does anyone know why a win xp computer would recognize the debugging mode, I'm rooted and the one click root worked fine, but not recognize my phone when in download mode? I have the drivers installed and java sdk installed. Every time I go to download mode and plug in I get a pop up (on computer) that my device is malfunctioning and the device manager says unknown device.
I know it's not the cables because I used my brothers laptop to flash eb13 from the froyo install tool before installing syndicate. But three computers including mine have failed with this same message.
I'm confused why this one lowly laptop that is nothing special worked fine and my computer along with the other 2 give me this "usb device malfunction try connecting device again, if fails replace device". Not an exact quote.
It's a long drive to my brothers, and I would like to use odin with out having to wait a couple days til I can drive out their. It's been putting a cramp in my rom flashing mojo. Any help would be greatly appreciated. I have done a bit of searching and haven't found a solution yet, among,
Trying different usb cables
Every usb port tried
Have it in download mode and plugged in while booting computer, (doesn't
Give message just doesn't connect. Then unplug replug gives message.)
Every combo of debug, unknown source on/off
Java sdk installed
Try downloading the XP drivers from Samsung and installing them fresh. I had a similiar problem. My computer took almost 10 minutes to connect all drivers the first time with new drivers. Then Odin worked fine after that.
BONSAI 4 and loving it!
I've searched google/xda and no one seems to address this very clearly.
I was having problems connecting my SGSIII via USB to my computer(s). Yes, I was using the cable that came with the phone. When trying to simply transfer files via USB (MTP or PTP) windows would not recognize the phone and a message saying "usb device has malfunctioned" popped up from the notification area of the taskbar. I had all of the drivers installed. I tried connecting the phone to my laptop (thinkpad) and desktop (homebuilt) computers, which were both win7 64bit. I tried every single USB port of each computer. Sometimes the device would show up in my computer, but I couldn't access any of the files. I was able to get odin to recognize my phone, however, and (foolishly) tried to flash a rom to my phone. Odin would fail every time at a different point in the process. I was stuck with a phone that would not bootup.
Then, I tried a computer (old dell, win XP) at work. I tried to flash the rom with Odin again. On the third attempt it worked! (after changing to a back (instead of the front) USB port) It was a big relief that I didn't brick my phone. Also, with this computer I could connect to my phone via MTP or PTP. I thought, therefore, that the problem was win7. So, I went back, installed win XP on my computer at home. This computer would still not play nice with the phone. (USB device malfunctioned error appeared again.) So, if you're having problems try a different computer. I had to try 3 before I found one that worked.
TL;DR: Try a different computer and different USB ports on that computer before you give up on connecting your phone to a computer via USB.
Finally, I NEVER had these problems with my HTC Hero, or HTC Evo. The phone would connect to ANY computer or ANY USB port. This was true for transferring files and for ADB also. With my S3 I'm transferring files by removing the SD card and connecting that to my computer. Kind of a pain in the ass. Thanks samsung.
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
I'm having trouble connecting my phone to my PC to transfer files. The phone never seems to register on windows, there are no "device inserted" sound at all and the phone is not listed in the device manager. On the phone, it is not even showing the little notification to change USB mode from Charging to File Transfert. Even in the settings directly, the option does nothing. Latest Google USB drivers are installed.
When the phone is in the bootloader, it shows up in the windows device manager with "Unknown usb device (device descriptor failed)".
I've tried multiple PC and cables, rebooting in safe mode, same thing!
I'm running TWRP recovery with stock ROM and ElementalX kernel, might that be an issue ? Thanks