Database Users

[GUIDE] Noob's Guide to setting up ADB

How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!

I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.

Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?

Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!

I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.

ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES

Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked

Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.

bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.

+1 for sticky

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.

Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.

I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App

allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.

Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App

bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.

sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.

bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse

Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App

[Q]PC cannot detect my Nexus4

I use the Stock ROM, Kernel, when I plug in the USB, there are nothing happen in my PC.
I've tried differen USB port, different cable and different PC. i can charge, but PC cannot read my Nexus
Also, I've tried to enable and dsiable the USB debug, the MTP/ also useless.....:crying:

I know this issue. Sometimes my PC also wont recognized my Nexus. I switch between mtp and ptp a few times while connected to the pc and and plug the cable in and out and after some times it works again.
But to be sure, all necessary driver are installed and there is this sound, when you connect the nexus to your pc?

CCody said:
I know this issue. Sometimes my PC also wont recognized my Nexus. I switch between mtp and ptp a few times while connected to the pc and and plug the cable in and out and after some times it works again.
But to be sure, all necessary driver are installed and there is this sound, when you connect the nexus to your pc?
Click to expand...
Click to collapse
Yes, I had install the driver.
no song when I plug in the USB. It's my Nexus dead?

ryo2456 said:
Yes, I had install the driver.
no song when I plug in the USB. It's my Nexus dead?
Click to expand...
Click to collapse
You still can use your nexus, right? It isnt dead.

CCody said:
You still can use your nexus, right? It isnt dead.
Click to expand...
Click to collapse
Yes, But I cannot update it if my USB port is dead.....-.-

Try this:
Plug your phone in. Find it in the device manager (look for the yellow triangle). Right click, and choose "Update Driver Software ...". Choose "Browse my computer for driver software". Choose "Let me pick from a list of device drivers on my computer". Scroll down and pick "portable devices", click Next. Choose Standard MTP Device > MTP USB Device. When it warns you that things may go tits up, click yes anyway.

CCody said:
Try this:
Plug your phone in. Find it in the device manager (look for the yellow triangle). Right click, and choose "Update Driver Software ...". Choose "Browse my computer for driver software". Choose "Let me pick from a list of device drivers on my computer". Scroll down and pick "portable devices", click Next. Choose Standard MTP Device > MTP USB Device. When it warns you that things may go tits up, click yes anyway.
Click to expand...
Click to collapse
Computer cannot read My Nexus......

ryo2456 said:
Computer cannot read My Nexus......
Click to expand...
Click to collapse
Yeah,i understand but did you do, what I suggested above?

CCody said:
Yeah,i understand but did you do, what I suggested above?
Click to expand...
Click to collapse
There are no yellow triangle if my PC cannot read my Nexus.
I don't think it's driver problem....:crying:

Reinstall your driver and thats it. That is surely a driver issue, cause your phone still operates.
Watch this video:
http://youtu.be/LirXNHRsGJE
Its batman, hope he could help you

CCody said:
Reinstall your driver and thats it. That is surely a driver issue, cause your phone still operates.
Watch this video:
http://youtu.be/LirXNHRsGJE
Its batman, hope he could help you
Click to expand...
Click to collapse
No Android Device for me.....

To be sure: it is a Windows PC, right?
Have you pluged it to another computer? Same happens there?

thebuga said:
To be sure: it is a Windows PC, right?
Have you pluged it to another computer? Same happens there?
Click to expand...
Click to collapse
As I sad in the first post, I have tried different USB port and different computer.
Yes, I've tried on Windows 7 and Windows 8.1, same result.

ryo2456 said:
As I sad in the first post, I have tried different USB port and different computer.
Yes, I've tried on Windows 7 and Windows 8.1, same result.
Click to expand...
Click to collapse
Have you tried to do a factory reset? If not make a backup and go for a try.
Backup without a USB connection can be done through bluetooth (sloooow) or Wifi (much faster than bluetooth). I like to copy large files to/from my N4 with ES File Explorer.

thebuga said:
Have you tried to do a factory reset? If not make a backup and go for a try.
Backup without a USB connection can be done through bluetooth (sloooow) or Wifi (much faster than bluetooth). I like to copy large files to/from my N4 with ES File Explorer.
Click to expand...
Click to collapse
use wifi still slow and I cannot transfer file to my PC :crying:

ryo2456 said:
use wifi still slow and I cannot transfer file to my PC :crying:
Click to expand...
Click to collapse
A thought just came to me: have you tried to look for the device while it is at the bootloader screen or at recovery mode?
If not, give it a try:
note: while at the bootloader screen the touchscreen does not respond, this is by design – or lack thereof. to manipulate you can swith options with volume up or volume down and choose an option with the power button. to quit this screen use the volume rockers to choose "Start" or "Power off". The former will resume the normal boot sequence while the later will, as you should expect, turn off the device.
1. turn off and unplug the device, if it is pluged.
2. hold down volume down and power. keep holding until it vibrates or you se the big open android with lots of text information. this is the bootloader screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You should be seen something like this - Nexus 4 bootloader screen​
3. now plug the device to the computer. it should recognize the device and eventually install/apply some drivers.
If that happened and the device got recognized by the PC you can do the next step: go to the recovery mode. To do this follow on.
4. using the volume rockers choose the "Recovery mode" option and with the power button choose it.
You will see something like this - Nexus 4 stock recovery mode​
If that happened you should get the device recognized again and new drivers installed.
If this happens we will be very close to be able to use the USB to copy the backup to the PC. Let us know if all goes as planned.
To quit the recovery mode just press and hold the power button until the device turns off, 5 to 10 seconds.

thebuga said:
A thought just came to me: have you tried to look for the device while it is at the bootloader screen or at recovery mode?
If not, give it a try:
note: while at the bootloader screen the touchscreen does not respond, this is by design – or lack thereof. to manipulate you can swith options with volume up or volume down and choose an option with the power button. to quit this screen use the volume rockers to choose "Start" or "Power off". The former will resume the normal boot sequence while the later will, as you should expect, turn off the device.
1. turn off and unplug the device, if it is pluged.
2. hold down volume down and power. keep holding until it vibrates or you se the big open android with lots of text information. this is the bootloader screen.
You should be seen something like this - Nexus 4 bootloader screen​
3. now plug the device to the computer. it should recognize the device and eventually install/apply some drivers.
If that happened and the device got recognized by the PC you can do the next step: go to the recovery mode. To do this follow on.
4. using the volume rockers choose the "Recovery mode" option and with the power button choose it.
You will see something like this - Nexus 4 stock recovery mode​
If that happened you should get the device recognized again and new drivers installed.
If this happens we will be very close to be able to use the USB to copy the backup to the PC. Let us know if all goes as planned.
To quit the recovery mode just press and hold the power button until the device turns off, 5 to 10 seconds.
Click to expand...
Click to collapse
I've tried before. no response......
So I'm pretty sure that the USB function is gone....

got to admit it sounds like there are some good ideas here but you seem to be sure that your phone usb port is done. Ok if this is the issue you can always use ES File Explorer and share the folder you want on your pc and use the LAN function on ES explorer to transfer files over wifi.
Secondly I had a similar issue and download minimal adb and fastboot which found drivers for me to use adb on my phone which again will help you transfer files. Hopefully you dont respond to me like others with I tried that already.... LOL

playya said:
got to admit it sounds like there are some good ideas here but you seem to be sure that your phone usb port is done. Ok if this is the issue you can always use ES File Explorer and share the folder you want on your pc and use the LAN function on ES explorer to transfer files over wifi.
Secondly I had a similar issue and download minimal adb and fastboot which found drivers for me to use adb on my phone which again will help you transfer files. Hopefully you dont respond to me like others with I tried that already.... LOL
Click to expand...
Click to collapse
yes I think my USB PORT is done too. so I decide to repair it by myself because the fee is about HKD $200...:crying:

In case you want to give it one last shot i had a similar problem when i first purchased my nexus 4.
The first time I connected it to the PC (Windows 7) I had USB debugging enabled and it recognized it (I.E made the sound when connecting it and started charging it) but could not access the storage via MTP or Camera. When turning off USB debugging I could access it as a camera but not as Media storage. I kept installing and uninstalling the USB drivers in windows. Eventually after many attempts causing frustration to build up, I clicked on cancel on the installing drivers and to my amazement the PC recognized it as MTP and I could transfer files. To this day I continue to use the same configuration and have not touched the drivers.
I don't know how or why this worked, I just know that it did.
Good Luck.
---------- Post added at 04:07 PM ---------- Previous post was at 03:50 PM ----------
You can also check this thread out. Try the solutions mentioned here.
http://forum.xda-developers.com/nexus-4/help/nexus-4-recognized-windows-7-help-t2232471

Samsung Windows drivers problem

Looking for some help please, with my new-to-me S5. I want to root it, mostly so that I can restore Titanium backup from my S4, but probably to install CM12 too. I have installed (and uninstalled, rebooted, installed, rebooted, many times) the latest Samsung drivers e.g. Samsung_USB_Driver_v1.5.51.exe, I have tried installing Kies3, I have tried different USB cables, I have tried my Win7x64 laptop, my wife's Winx64 PC; none of them will show the phone in Windows Explorer.
I did try it on a very old laptop (Core solo) that happens to have a play copy of Win8.1, and it worked! I then tried to use Odin v1.85 and Odin v3.09 to push CF-Auto-Root, and it always ended with Odin "Not responding" - presumably because the laptop doesn't have the guts.
I did put Win10 preview on a spare hard drive in my laptop, but no joy after installing Samsung_USB_Driver_v1.5.51.exe. Under Win7 I had tried older versions of the drivers too.
Ant bright ideas please??
TIA

fjuniper said:
Ant bright ideas please??
TIA
Click to expand...
Click to collapse
Kies will install the correct drivers so uninstall Kies completely, reboot your PC then install it again, check for updates and if any update kies then run it.
When it is running plug in your phone to a USB port that is directly on the PC not via any hubs and you must use the cable that came with the S5, other cables will not work correctly, make sure it installs the drivers at this set up.
Windows does not necessarily install the correct drivers, you need to go to My Computer > properties >. device manager and find your device in the list it should be shown as Android Mobile Phone if that is there then make sure the installed drivers are Samsung Android ADB Interface, if it isn't showing this driver them change it.
The other option if you have the Samsung drivers installed is to plug in the phone check in Device Manager on your PC and find your phone then check and change the drivers.
Turn off any firwall whilst you do this as that can block the device as well

Thanks for the suggestions. Yes, I had tried the original Samsung cable as well as others. Plugged straight into a ThinkPad, no USB hub.
Uninstalled Kies and the Samsung driver package, rebooted, installed Kies, checked for updates (none), and - Nothing. Nothing in Device Manager, nothing in the Safely Remove Hardware tray applet. Nothing in the notification area of the phone. The firewall was disabled for all of that post-reboot.
It's driving me mad...
I do eventually get a USB Device Not Recognised popup with Unknown Device shown in the window. By now, there is also an Unknown Device showing in Device Manager under Universal Serial Bus Controllers. I could Update Driver, but unsurprisingly Windows can't find one. My only other option would be to use the Have Disc option, but only if I had the right .inf file... :crying:

"None of them will show the phone in windows explorer"
You know you need to put the phone into download mode to use ODIN?
It won't show in explorer when you do that, but ODIN should say it is connected
And use the latest version of ODIN you can find, 3.09 should work, 3.10.6 is latest

*Detection* said:
"None of them will show the phone in windows explorer"
You know you need to put the phone into download mode to use ODIN?
It won't show in explorer when you do that, but ODIN should say it is connected
And use the latest version of ODIN you can find, 3.09 should work, 3.10.6 is latest
Click to expand...
Click to collapse
Thanks for replying. Yes, I have tried plugging in with it in download mode and using Odin, but it wasn't showing the COM port, so it wasn't recognised using that either. I even tried pushing CF Auto Root, but of course it failed.

It sounds like the cables you've tried are faulty, so long as the phone USB port is not
Multiple PCs say to me it's not a PC issue
The samsung drivers just need installing with the installer, don't worry about manually installing them, once you have working USB cables/port it will install them automatically so long as you ran the installer

Have you attempted to use different USB ports on the computer you are using? Contrary to what Detection has said, the fact that you can get it working on another computer with all of your cables does point to this being a PC problem and not a cable problem. My suggestion would be to completely uninstall Kies, keep it uninstalled, use different USB ports and allow windows to install the drivers itself.
On various occasions, removing Kies has worked, and on another it was the USB port that I was using that was the problem.

OP said he tried two different Win 7 PCs before trying the 8.1 laptop on which he had partial success
My guess is if he is constantly moving the cables from PC to PC, if they are faulty, bending them around is possibly making the connection by the time it ended up on the laptop it recognised the phone from, like when your charger cable breaks inside and you have to wiggle it around to make a connection
But as he also said, it failed to work even on that - so that's 3 machines, one partially recognised the phone - Id say the chances of it being a bad USB port over 3 machines, or even bad machines are very slim
Bad phone USB port or bad cables is my guess
Either that, or Win 7 isn't playing nice with the phone/drivers

I remember reading somewhere that with windows 7, you have to run odin as an administrator......also remember reading that it's not just the firewall you have to disable, but the anti virus as well......It may not help to uninstall kies as this *may* remove the Samsung drivers. Probably be better to leave it installed, but to use windows task manager to kill any running kies processes before you start odin up, as (from what I've read ) kies will interfere with odin.......
And for info.......odin 3.09 is the version I have successfully used on my phone.
Sent from my rooted kn0x0 stocKK SM-G900F S5

Thanks for all your replies while I was asleep.
I have used multiple USB ports on the 2 Win7 machines, multiple cables including the one that came with the phone. When I dropped the firewall, it was f/w and AV as it's one program (Symantec) (corporate laptop, not locked down). I have tried running Odin as administrator. If it wasn't for the fact that it did work on the ancient Win8.1 laptop, I would have thought the problem was with the phone port, but I could see it in Windows AND Odin displayed the COM port - it was just that Odin then went "Not responding"... which I assume was a system performance issue...
I will have another try tonight with yet more cables and I must have some USB ports I haven't tried yet... None of it makes sense and I am not a noob.
Edit: This is all having a negative effect on my laptop too - I used to be able to see internal and ext SD on my S4 in windows explorer - at the bottom of the right pane it had i9505 then you saw a folder for each SD. Now I just see ext SD as a drive letter.

Try this:
Install or just use the portable version of "Ghostbuster"
http://ghostbuster.codeplex.com/
Unplug all USB devices from the machine other than K&M
Run Ghostbuster as Admin
On the first device listed of each section, right click and choose "Add Class"
That should highlight the entries in that class and flag the ghost entries
Do that for every section until you have them all highlighted
Now click "Remove Ghosts" at the bottom and let it do it's thing
That will remove all non connected USB devices and their drivers
Once it's done - reinstall Samsung drivers just using the normal installer
Plug phone in and see if you get any better luck with it being detected
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks Detection, I hadn't come across that before. It deleted LOADS of ghosts... ...but unfortunately it hasn't moved me on at all. Still nothing in WinExplore, no COM ports in Odin. I am somehow jinxed, or rather this S5 is.
Edit: Just did it all again with a couple of reboots for luck - no better.

fjuniper said:
Edit: Just did it all again with a couple of reboots for luck - no better.
Click to expand...
Click to collapse
Open up the Device Manager on your PC then plug in your phone and look for any new connections to appear in the USB controllers list there may be Unknown device or another named device if you see a new connection unplug the phone and check the list again to see if it has disappear from the USB list, if you see a USB device appear and disappear from the list as you unplug and plug in the phone this is the one you want.
Right click on this and select Update Driver Software, click Browse My Computer then click Let me pick from a list, if you have the Samsung drivers installed on your PC you should see one or more called Samsung Mobile USB Composite Device, select the most up to date version if you have more than one listed and install that.
If you don't see the Samsung USB drivers un-tick the box that says Show compatible hardware, scroll down the list to the left and find Samsung Electronics Co Ltd, there will be more than one, click on each one until you see Samsung Mobile USB Composite Device in the right window, then click on that and install it.
You will get a warning saying that changing the driver may cause the device to not work properly just click OK and install the driver, if it works the USB device in the list should change to Samsung Mobile USB Composite Device.
Try this and see if it gets you sorted manually but don't forget to make sure you have installed the Samsung drivers on your PC first

ag4751 said:
Open up the Device Manager on your PC ...
Click to expand...
Click to collapse
Thanks, I will give that a go, though it will not be until Saturday as I don't have the phone with me. I am pretty sure that it does appear / disappear in Device Manager, and I did look at manually updating from there, so your suggestions should be helpful.

ag4751 said:
Open up the Device Manager on your PC then plug in your phone and look for any new connections to appear in the USB controllers list there may be Unknown device or another named device if you see a new connection unplug the phone and check the list again to see if it has disappear from the USB list, if you see a USB device appear and disappear from the list as you unplug and plug in the phone this is the one you want.
Right click on this and select Update Driver Software, click Browse My Computer then click Let me pick from a list, if you have the Samsung drivers installed on your PC you should see one or more called Samsung Mobile USB Composite Device, select the most up to date version if you have more than one listed and install that.
If you don't see the Samsung USB drivers un-tick the box that says Show compatible hardware, scroll down the list to the left and find Samsung Electronics Co Ltd, there will be more than one, click on each one until you see Samsung Mobile USB Composite Device in the right window, then click on that and install it.
You will get a warning saying that changing the driver may cause the device to not work properly just click OK and install the driver, if it works the USB device in the list should change to Samsung Mobile USB Composite Device.
Try this and see if it gets you sorted manually but don't forget to make sure you have installed the Samsung drivers on your PC first
Click to expand...
Click to collapse
When I manually select the Samsung Mobile USB Composite Device, I always get "Windows encountered a problem installing the driver software for your device. This device cannot start. (Code 10)", so I am still stuck...

fjuniper said:
When I manually select the Samsung Mobile USB Composite Device, I always get "Windows encountered a problem installing the driver software for your device. This device cannot start. (Code 10)", so I am still stuck...
Click to expand...
Click to collapse
There are a couple of things you can try as Windows is preventing the installation.
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
I had this error message last year with something I was trying to install but I can't remember just how I sorted it out.

[Q] SGS5 Not recognized by PC!

Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
My phone connects to my PC via Bluetooth fine, but the USB just wont work! I've searched the web but most things are outdated or just don't work...
I think this is due to using an OTG cable, making my phone act as the host device whenever I plug it in?
Extra detail:
-PC is running Windows 7 ultimate x64
-Samsung Galaxy S5 is on Android 5.0, but didn't work on previous versions either
-I use the samsung cable, but have also tried one other cable.
-Tried plugging it into another computer, does the exact same thing.

Install Samsung drivers / KIES3

*Detection* said:
Install Samsung drivers / KIES3
Click to expand...
Click to collapse
Already tried those, made no difference unfortunately

CheeseJuggernaut said:
Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
.
Click to expand...
Click to collapse
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post

ag4751 said:
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post
Click to expand...
Click to collapse
Thank you for the great help, I think that this is what needs to be done to fix it. There is still one problem though.
I have tried this before, but I ran into a problem where it would do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect

CheeseJuggernaut said:
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect
Click to expand...
Click to collapse
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install

ag4751 said:
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install
Click to expand...
Click to collapse
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.

CheeseJuggernaut said:
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.
Click to expand...
Click to collapse
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone

ag4751 said:
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone
Click to expand...
Click to collapse
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised

CheeseJuggernaut said:
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised
Click to expand...
Click to collapse
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18

ag4751 said:
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18
Click to expand...
Click to collapse
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Are you using the OEM cable?

Rapunzl said:
Are you using the OEM cable?
Click to expand...
Click to collapse
Yes, and ive tried other cables. Its a problem that is most probably hardware though

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Take the original USB cable as well so they can try another one against yours just in case it a faulty cable

problem with the adb interface driver (install/uninstall drivers)

hi,
im having issues installing drivers for my oneplus 2 device.
here's what i've tried doing:
iv'e tried connecting the device with usb debugging and without. without usb debugging it finds the name of the device normally.
the first thing i've done is uninstall every driver that was resembled any phone, google or usb storage driver.
and tried to install the drivers from this tool: (which i think is the source of my problem i dont know how to remove this.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it went ok with no problems, but it didn't find my device. (when i typed adb devices)
i've uninstalled the drivers again via programs and features and usbdeview tool (this time i've found older samsung device driver from regedit and removed it also).
rebooted (as every step of driver removal and install).
i've tried again with no luck.
so i've decided to install those drivers from the android sdk but when i've tried to install it from the device manager it shows up this:
i also tried downloading samsung drivers to see if it works. i saw in one of the threads that said it's ok to use them because they were universal too. (i removed it again from the regedit when i couldn't find the drivers)
i tried to use the oneplus one toolkit's for it's universal driver i thought maybe it will work
how can i fix this? i want to start over again clean. i can't find it in USBdeview or programs and features or regedit. what am i missing?
the photos are after trying to install the drivers from the sdk tool and uninstall it back with reboots several times now
+as im seeing in other threads, it supposed to be an android device and not adb interface.
+there is nothing else in the driver selection list that resembles any device
thanks to everyone who helps!
EDIT:
whatever i did i couldn't remove this marshall driver and i really don't know how i got it there. so i decided to format my pc. start over clean.
i've downloaded the sdk tools this time and before connecting my phone to the pc (maybe the windows 10 has to do anything with installing these marshall drivers.) i have installed these drivers from the sdk, rebooted the pc and connected the device. now everything works! the cmd find my device i type "adb reboot" to make sure everything works BUT when i go into fastboot mode (in order to unlock the bootloader)
the pc doesn't recognize the device. it says "android" with an question mark icon near it, ok so i just need to install the driver like in image #1 right? so i did, and it didn't show up this android adb interface driver. instead i've found this marshall driver AGAIN! i went inside it and i'm seeing marshall drivers and google inc drivers INSIDE this marshall driver selection (like image#2)
i really don't know from where this marshall london device is coming from
although setting it up as the marshall device, it works... but it's a marshall device not my oneplus 2
this doesn't make any sense to me. i never owned marshall product, beforehand i guessed it came from the toolkits i installed but this time i went clean and there's no way it came from those toolkits.
if im unclear about anytning im willing to share my teamviewer or screenshots.
this how it looks like:
EDIT2:
Q: what if i decide to ignore that marshall device? because it seems to find the device and im able to reboot from the commands. is it ok? should i ignore the name?

Hi, I used Universal ADB drivers.
I had to manually chose the .inf file with the have disk feature to make it work.

I used the Oneplus two toolbox to install my drivers.
forums.oneplus.net/threads/oneplus-2-how-to-unlock-bootloader-install-custom-recovery-root-efs-backup-more.345478
I didn't even bother with the 15 second ADB installer.

've found the problem.
apparently the drivers name was "marshall london device". i accidently clicked on it and there was an option to choose adb interface driver (like the image #2)
EDIT:
well it worked for the first try and it stopped working.
what is marshall london device? it seems to have a bunch of drivers like clockworkmod and marshall composite adb interface

Noahsoskha said:
i've found the problem.
apparently the drivers name was "marshall london device". i accidently clicked on it and there was an option to choose adb interface driver (like the image #2)
it works now
EDIT:
well it worked for 1 try and it stopped working.
what is marshall london device? it seems to have a bunch of drivers like clockworkmod and marshall composite adb interface
Click to expand...
Click to collapse
It's an Android phone design for Marshall (the music / sound gear company).

Theberge43 said:
It's an Android phone design for Marshall (the music / sound gear company).
Click to expand...
Click to collapse
i still don't get what that driver is doing in my pc
i can't install the inf file it tells me it's not supported.

for some retarded reason the usb drivers that i downloaded from google are being installed into marshall device. i don't know why but it's the second time my pc thinks my phone is a marshall device. it works if i type adb reboot, but only once. now i have to delete this marshall thingy that i don't even know how the hell it got there...

anything?
i really need help, i think i've made this problem as clear as possible.

Bump! same problem. This all happened as soon as i installed the latest version of OS. Oxygen 2.1 . Adb worked perfectly before i flashed this new OS. now windows wont read the devices with adb drivers. it keeps saying Marshall London Device.. sigh.. anybody? i tried all the same things in this thread to fix it. I also wiped all drivers using USBDeview and reinstalled to no avail.
Noahsoskha said:
anything?
i really need help, i think i've made this problem as clear as possible.
Click to expand...
Click to collapse

azenus said:
Bump! same problem. This all happened as soon as i installed the latest version of OS. Oxygen 2.1 . Adb worked perfectly before i flashed this new OS. now windows wont read the devices with adb drivers. it keeps saying Marshall London Device.. sigh.. anybody? i tried all the same things in this thread to fix it. I also wiped all drivers using USBDeview and reinstalled to no avail.
Click to expand...
Click to collapse
before that what did it detect? the device name? or adb interface?
are you running windows 10?
i managed to ignore the name of the driver because like the third image i posted says that inside the marshall driver there is "google inc" and then that the adb driver...
so i think it's windows 10 that's causing this. but i've tried ignoring it and adb commands are working for me. i don't know whether it's safe to unlock and such but i managed to make it reboot into recovery...

I am running windows 10. I tried another computer of mine with windows 7 which worked perfectly before the new OS update. That computer as well cannot detect any ADB devices. I managed to get windows to install the proper ADB Android drivers in windows 10 and 7 now. However, whenever I load One plus 2 into Fastboot Mode windows DOES detect the device but ADB wont connect to it.
I have made sure that i am in debugging mode and that I authorized the connection when prompted. any ideas?
Thank you
Noahsoskha said:
before that what did it detect? the device name? or adb interface?
are you running windows 10?
i managed to ignore the name of the driver because like the third image i posted says that inside the marshall driver there is "google inc" and then that the adb driver...
so i think it's windows 10 that's causing this. but i've tried ignoring it and adb commands are working for me. i don't know whether it's safe to unlock and such but i managed to make it reboot into recovery...
Click to expand...
Click to collapse
---------- Post added at 04:25 PM ---------- Previous post was at 04:12 PM ----------
Figured out why adb wouldnt connect. Even though usb debugging was on and permissions granted for some reason the Developer Mode toggle was hidden again. I enabled the toggle again, turned off usb debugging mode. Turned it back on 10 seconds later and it all works now. *sigh*

useranonymous said:
I used the Oneplus two toolbox to install my drivers.
forums.oneplus.net/threads/oneplus-2-how-to-unlock-bootloader-install-custom-recovery-root-efs-backup-more.345478
I didn't even bother with the 15 second ADB installer.
Click to expand...
Click to collapse
Thanks! Worked for me too!

Hi there,
my problem is very similar to this.
Suddenly all my android devices (OPO and OP2) are recognized as marshall london devices.
adb devices finds them but I am not able to get the authorization of my PC showing up on my phones.
adb tells me the device is not authorized.
I tried resetting the usb authorization from the development options, changing usb ports, changing cables, disabling and enabling of usb debugging, mtp mode and such.
Nothing works so far. The google adb drivers show up under the marshall london category like in the first post. It all startet after I rebooted the OP2 in fastboot once.
Any ideas?
Thanks
-howgie
Update:
I was able to get rid of the marshall london entry by removing it from the registry manually. But the problem of the unauthorized device remains...

I am also getting this error, I was able to select google devices before and had adb working but after it unlocked the bootloader and rebooted the phone it wasn't detecting anything correctly, just the marshal london device and adb doesn't detect anything, also on windows 10. Will try tomorrow on my windows 7 work machine.

Same Problem! Please Help!
For some reason "Marshall London Device>Marshall London Bootloader Interface" keeps installing itself every-time I hit Scan for hardware changes, after trying to uninstall it. ADB doesn't recognize my OPT even when my phone is in fastboot mode. Running Windows10

In windows 10 use manual choose driver from list, then choose proper driver.... If you can't find it I'll post screens tomorrow
Sent from my ONE A2005 using Tapatalk

cosmicsquid said:
Same Problem! Please Help!
For some reason "Marshall London Device>Marshall London Bootloader Interface" keeps installing itself every-time I hit Scan for hardware changes, after trying to uninstall it. ADB doesn't recognize my OPT even when my phone is in fastboot mode. Running Windows10
Click to expand...
Click to collapse
I have same problems. Have someone found a solution for this?

I deleted all drivers and it says unknown USB device (Device Descriptor Request Failed). I can't get it to install Oneplus2 drivers, Android ADB or Samsung drivers and be recognised.
Again I concur and think this is a Windows 10 issue, I am not using the official cable, are others using it and having the same issue??

I used a different cable and it worked, strange as I tried one unofficial and one official and in the end my new Anker one I just purchased worked okay.

howgie said:
Hi there,
my problem is very similar to this.
Suddenly all my android devices (OPO and OP2) are recognized as marshall london devices.
adb devices finds them but I am not able to get the authorization of my PC showing up on my phones.
adb tells me the device is not authorized.
I tried resetting the usb authorization from the development options, changing usb ports, changing cables, disabling and enabling of usb debugging, mtp mode and such.
Nothing works so far. The google adb drivers show up under the marshall london category like in the first post. It all startet after I rebooted the OP2 in fastboot once.
Any ideas?
Thanks
-howgie
Update:
I was able to get rid of the marshall london entry by removing it from the registry manually. But the problem of the unauthorized device remains...
Click to expand...
Click to collapse
where is it in the registry pls? (marshall london device)