Database Info

USB unknown device

I've tried the drivers from Samsung, Keis, ODIN one click. None of them worked on 4 different machines, Windows 7 both x64 and x86(which was a fresh install), and two Windows XP machines. I tried it on Ubuntu(10.04 LTS) and that recognized the captivate.
Anyone know how to get one of those to correctly recognize my Captivate so I don't stuck on Samsung's/AT&T's 2.2

uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers

What is it that you're trying to do?
Sent from my SAMSUNG-SGH-I897 using XDA App

If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.

Samsung really failed at the USB drivers for the Captivate. I would expect to be able to install the drivers from their website. Plug in my phone, and have it working.
trell959 said:
uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers
Click to expand...
Click to collapse
I tried that before, didn't work.
bornjamerican said:
What is it that you're trying to do?
Click to expand...
Click to collapse
I'm trying to:
1) connect as a mass storage devices. Yes I know turn on USB debugging and to mount the drive.
2) flash back to stock 2.1 or root my phone so I can install a custom ROM on it. Might go with CM7/MiUi or something from Team Phoenix. So use Odin3
shinji257 said:
If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Click to expand...
Click to collapse
Tried all of the ports on the computers. I don't have another microusb cable to test to see if that's the problem, but I'll check that tomorrow.
Johnnie5000 said:
I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.
Click to expand...
Click to collapse
I'm going to try a fresh install of windows 7 32-bit with aio toolbox see if that works.
Tried my friends brand new microUSB cable. It worked.

I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.

rmriggin said:
I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.
Click to expand...
Click to collapse
If you're just trying to transfer apk files to it for sideloading, you can use a wifi transfer app. I use Wifi File Explorer and it's great. You can connect to your phone via web browser and upload/download anything on the SD card.
Another option is to use an external SD card that you can remove and plug into your computer, transfer the files to it, then insert it back into the phone.
This won't work for connecting to PC apps like Odin, Heimdall, or Kies, but for simple file transfers it works like a charm.
Additionally, regarding other usb cables, you didn't mention what types of cables you used, so I'll throw in another thought. The cables that come with the Captivate don't work on some PCs (like my new iMac). Third-party, generic usb cables might not work, either (I tried some and got a whole lot of fail). The only cable that works for me is the one that came with my wife's Motorola phone. If you haven't tried one yet, I would recommend getting your hands on a Motorola cable and testing it out. You'll immediately notice the cable is much thicker. I don't know if that has anything to do with why it works when others don't, but there's something about that cable that others don't have.

Bad Phone?
Could it be the phone port is having issues?
I've had the same problem and it seems that the port on the Captivate is shot which may be your issue. it will always charge; but tends to cause a lot of profanity when trying to get a PC connection to transfer files or flash it. It will be seen, then immediately play the 'unplugged' sound from windows. I've sat there and had it play the tones of plugged in and un plugged over and over again just by tilting the phone from side to side. No matter what cables I use (tried several but they are all samsung due to the recessed port). If it establishes the connection; I have to be very still with it or it'll lose it. If it loses it; I get unknown device messages or not functioning messages on that port until I reboot the PC.
Trying to flash anything via ODIN takes a lot of patience.
Those same cables / USB ports are used on my wife's Focus without ever having a problem. I wrote it off as too much flashing / overclocking of my phone but am not sure.

hi i was having this issue as well. i solved it by:
1. download a good & stable miui rom, rename it to update.zip and place it into your sd card. i took the sd card out of the phone and used a adapter to connect the sd card to my PC since i can't access my sd card through the usb port.
2. put the sd card back into my phone, turn off my phone. press and hold volume up and down buttons, then press n hold the power button till the screen shows something.
3. select install from sd. wait until the installation finishes and select reboot the phone.
4. when you're in your new miui rom, try to connect your phone to the pc via usb port again.
this worked like charm for me.
about the miui rom, i suggest you to use the one from miuiandroid.com (the UK version)
after flashing the rom im able to connect via usb and use mass storage.
hope this helps

Also, when you uninstall drivers, don't forget to look in the program files for anything that may have been left behind and delete it.

From the description it sounds strongly like you are actually experiencing a port failure which is common on the Galaxy S devices. PM me if you need this repaired...

Only try another usb cable, i bricked my cappy with a bad contact cable on odin, unknown device too, new cable=i897 device on windows notifications
try and feedback!

strange, this only happened to my when i soft bricked my phone. try connecting it to your computer in download mode

I had this issue once before. Here is what I did which resolved the problem. I was using a windows 7 PC
1. Download the ADB kit and extract it to C drive.
2. Connect your mobile to the PC on USB port
3. Wait for the drivers to be installed automatically (it might give you a failed to install message)
4. Never mind that message. Open Device Manager
5. In Device Manager, if you expand the "Universal Serial Bus Controllers", you'll see a device that has yellow question mark against it. This is your phone and since drivers are not installed properly, it has the question mark.
6. Right click that device, and select "Update Driver".
7. IN the window that comes up, select "I'll select a driver".
8. Browse to the folder where you have extracted the ADB kit on C drive
9. Check include subfolders and click Next.
10. The drivers should be be installed and your device should be identified by the computer.
Let me know if it works for you.

Found the Samsung Infuse 4G Drivers

For those of you who have had trouble with getting the drivers for the Infuse, download this:
[Im new so cant post a link, but goto softpedia.com and search kies. The only kies program available will appear, and download and install that]
It wont recognize your phone, but after you install the program, the appropriate drivers will be present, and the root with SuperOneClick will work immediately.
*remember, the program wont recognize your phone if its plugged in, but that doesn't matter. It will just install the appropriate Samsung_Android drivers your PC needs to recognize the phone in SuperOneClick.
Hope this helps!

Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?

pvillasuso said:
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
Click to expand...
Click to collapse
404 Page Not Found
The page you requested was not found.

http://forum.xda-developers.com/showpost.php?p=13895587&postcount=7
posted here.

Phone doesn't exist on my PC.
Nope. Bought the infuse on day one. Installed Kies 2.0.0.11044_11_3. Phone not recognized, installed drivers, learned the truth about Kies. Phone would not be recognized but at least installing Kies made the phone visible to the PC, so I knew I could root if I so desired, read up about rooting and thought I was ready. The phone had other plans.
Decided the other day that I was ready to root. Plugged in the phone but it no longer showed up in Windows. Something about the phones compatibility with my system changed. Tried to install this Kies 2.2.1.11053_99_3 yesterday, reinstalled drivers, activated USB debugging, plugged the phone in started up SuperOneClick and . . . still nothing happened. So I deactivated USB debugging and started over. Followed all the directions in the root posts and and SuperOneClick threads . . .
But somehow between day one and today my Windows 7 64 bit system does not know that the phone is plugged into it.
When I plug the phone into USB the phone asks me how I want to interact with the computer, Kies (Firmware Update); Media player: Mass storage. But the computer shows nothing. Device Manager doesn't list the phone, Windows Explorer doesn't show the phone, Devices and Printers window shows everything that's connected but NOT the phone, it's as if I plugged nothing into the computer. The phone is charging so I know that it's plugged in, but it doesn't seem to be communicating with the PC. I've re-booted, re-installed, reviewed, rewired and re-alized that I have no clue what happened. (Tried different cables, different USB ports different times of the day)
It worked once upon a time, I tried rolling back restore points and disabling my kaspersky 2011, I've followed all rooting instructions in these threads to no avail.
I am now ready to hurl my phone out into traffic to see if that will help, but before I do I'm hoping someone here may have the answer I need.
. . . please . . .

Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?

For me, one of the SuperOneClick packages included Windows drivers.
Which is great since SOC is the only reason I needed Windows drivers. (SOC never works in Linux for me for whatever reason...)

All android phones are supported in linux natively.......jus t saying

Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Well yeah - I've never had to install any drivers for ADB or anything else.
However, for whatever reason, superoneclick and Linux don't get along for me. So the only time I ever have to install drivers is when SOC rooting from Windows.

superweapons said:
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
Click to expand...
Click to collapse
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.

menzoom said:
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
Click to expand...
Click to collapse
I've tried just about everything too, and nothing works to get my 64 bit Windows 7 PC to recognize the Infuse. Finally resorted to AndroidSync for file transfers, which worked fine, but it just makes me angry that I can't make the darn thing connect via USB.

http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT
And select SOFTWARE

Tried that last week. Didn't work for me. The PC does see the device, but never finds any files on it.

Drivers in that link
I was having the same issue mentioned yesterday after loading the Samsung Infuse drivers, where my PC still couldn't see the data on my phone. (I'm also running 64-bit Windows 7 OS.)
Once I loaded the drivers and plugged in my phone, I got the happy little "device drivers installed properly" message and thought I was good to go. Nope. No drives mounted and visible in Explorer.
Under Devices and Printers, I could see SAMSUNG_Android with the unhappy yellow exclamation point. The troubleshooting report just says "Problems with PnP devices."
So I dug into into Device Manager. Under Portable Devices, there were 2 new WPD FileSystem Volume Drivers. Both had the same yellow exclamation points and showed a Device Status of "This device cannot start. (Code 10)."
It turns out Windows 7 wasn't assigning drive letters to the new Android volumes. It creates two disk drives (one with pictures, videos, and ringtones and the other with music, external SD, and media). If you right-click on the drives and choose "Change Drive Letter and Paths," click Add, and assign it an unused drive mapping, it will then appear in Explorer.
Incidentally, the SAMSUNG_Android still shows up with its unhappy yellow exclamation point in Devices and Printers. So I imagine there's supposed to be a more user-friendly way that doesn't expose the true internal file structure when it's all working properly. But in the meantime, I can at least access my phone data via USB.

Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.

neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Dude look at the date

neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Hey there..
View attachment 876861

thanks

Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Yep...
Ubuntu / Linux FTW!

Hmmm, native on Linux you say? Don't have to battle with windows composite USB hub bullcrap you say? I shall try this.
Sent from my SAMSUNG-SGH-I997 using xda premium

[Q] SK4G not being recognized on PC

I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.

What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.

Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA

Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.

I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.

I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.

More info request.
Can you provide us with the names and links to the drivers you have tried?

DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.

Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.

DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.

Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.

Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?

Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...

Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?

DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.

No MTP or PTP for Rooted Nexus 5?

I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.

aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.

ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online

aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4

Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go

ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.

ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.

By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.

The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!

Question Phone not detected by PC

A couple days ago my mobile data just stopped working. I had a couple updates I had been ignoring because it would remove the root. I finally gave in and ran the updates. Data returned. Root gone. I connected to my home computer to begin the root process, but my phone would not be recognized by the PC and would not show anything related except that it was charging. It's a new cable, barely used. I tried on my work computer with a different cable and still nothing except "charging". To the best of my knowledge, it connected to my computer just fine prior to the updates.
I've checked Developer Options for anything that says "USB". Toggled USB debugging, revoked authorizations, etc. "Select USB Configuration" is a weird one, all I have are: "Charging", "MTP", "PTP", RNDIS (USB Eathernet)", and "MIDI". But in "Default USB Configuration" I have: "No data transfer", "File transfer / Android Auto", "MIDI", "PTP", "USB tethering". I've selected every option, but (again) no reaction from my phone or PC.
My final options are wipe and reset, or take it to a store; I'm wanting to avoid both of these if possible. Does anyone have an idea of what else I can try?

Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?

IamTheBRAVE said:
Maybe try this?
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com
It's a Usb bootable LiveISO linux distro with all android drivers supported. Might help get your phone detected. Haven't used it so don't know if it'll work for you.
Is your phone booting? Why do you need a connection to PC?
Click to expand...
Click to collapse
I'll take a look at that tonight.
To answer your questions, phone boots and everything else seems to operate just fine. Just checked and boot screen says "Orange State Your device has been unlocked and can no longer be trusted", then like 30 seconds later it boots. It no longer has root after the updates and the only way I know to do it is through adb and fastboot commands. But also I backup my photos to my home PC when it gets pretty full. Also, also I occasionally do mobile development at home and test things on my phone.

The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.

IamTheBRAVE said:
The orange state is when it's bootloader unlocked. So that's normal. To root, you would indeed need an adb connection even when using the patching boot method.
I just remembered something. Go to your pc, look for a file in Users> your username > .android (hidden folder) > adb.key.
Even when you revoke authorisation from the phone, if that file still exists, the pc still sees 2 different keys so it won't allow it. So see if you can delete it.
Are you on win10 or sbove? It sometimes won't let you connect "untrusted" devices. Hope it helps.
Click to expand...
Click to collapse
Ya, I wasn't too worried about the bootloader message, just being thorough. I'll try the android folder at home also, but for what it's worth I don't have anything android-related on my work computer and it doesn't connect either.
Both are Win10

In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?

IamTheBRAVE said:
In device manager in win10, do you have any yellow triangle next to android drivers? What are the drivers you installed for your phone?
Click to expand...
Click to collapse
Phone doesn't show anywhere in Device Manager, and no yellow triangles. IIRC, drivers were installed by my phone when I plugged it in at home. I actually don't remember the last time I plugged into my pc at work before now.

Then look for your brand's android drivers and install them. I think that's the issue. Plugging the phone alone would install generic android drivers not your specific ones.

Short version: Nothing worked.
I had already tried searching for "oneplus 9 drivers". The main site doesn't offer anything, so there are a couple search results that really feel like scam sites. But they're the top results, so maybe I'm wrong. I installed the results from the search, and also searched xda and the one result I found.
I downloaded the ISO for mAid. Ran it in a VM. I couldn't really figure out what to do in it to troubleshoot. I was also discouraged because if my computer won't recognize the device, then why would the device show up in a VM?
I found and removed adbkey and adbkey.pub from "Users\<me>\.android\".
I had a brief bit of hope. I doubt the drivers caused it, so I'll probably remove those again. I got the device to appear in Device Manager but with a yellow triangle. It only seemed to happen when switching between "No data transfer" and "File transfer / Android Auto". The device was displayed as "Unknown USB Device (Device Descriptor Request Failed)". I doubt that provides much help though.

Have you tried clearing out the dust bunny's in the usb port on phone?

Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com

MrSteelX said:
Have you tried clearing out the dust bunny's in the usb port on phone?
Click to expand...
Click to collapse
Yup. Folded some paper after the previous stuff. A little bit came out, but not so much that I'd think it's the issue. I have a floss stick thing, but it was a bit thicker and was moving the piece inside the slot.

IamTheBRAVE said:
Keep the device in file transfer mode and with a yellow triangle. That's better than nothing.
I found this. Try and install it. (Also, doesn't this forum have a sticky thread for drivers? I have the 9pro btw)
Download Official OnePlus USB Drivers - GSM USB Drivers
Looking for official OnePlus USB Drivers? Then you can download Official OnePlus USB Driver for your Android Smartphone and tablet here.
gsmusbdrivers.com
Click to expand...
Click to collapse
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds

tconn said:
I'm new to XDA, but from what I've seen there's only a sticky for OS Builds
Click to expand...
Click to collapse
Took a look on OP9 forum, doesn't look like there is one. We have that on OP9Pro. Here's a link to the drivers, should work for you i think.
10.26 MB file on MEGA
mega.nz
You can use this thread as tutorial for root (you don't need all parts of it)
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com

"Device Descriptor request failed" tells you that the very first step of USB enumeration failed.
So you're talking about flakey cable, bad connection, interference OR the device was not initialized properly.
So try different ports, different computers, something different.
The first step is getting it to the point where it connects solidly (even if it can't/won't find a driver).
Unfortunately you can't tell Windows to use common sense and install a WinUSB driver. That's why we have Zadig: https://zadig.akeo.ie/
Unfortunately (again), adb.exe expects the correct DeviceInterfaceGUID. Ok, you can patch adb.exe or you can use Zadig with a custom .cfg file to specify the DIGUID.
Here is an example .cfg file. You'll have to fill in the VID/PID/MI if you ever get your phone to connect solidly and you can see that info in the DeviceManager.
So, go to Zadig, select Device > Load Preset File, select Options > List all devices, find your device and hit install.
Code:
[device]
Description="Standard Google Device"
VID=0x18d1
PID=0x4ee7
MI=0x00
GUID="{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}"
Good luck.

Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!

tconn said:
Dang... I think it's the dust bunnies. I have to push the cord in pretty hard, but it'll connect. So either bunnies or I don't know if the port itself gets displaced over time. Used an air compressor to blow out a bit, might try a bit more tomorrow. Thanks for everyone's help!
Click to expand...
Click to collapse
Try using a toothpick. Just try not to bend port too much.