Database Develop

ADB Device Not Found

ADB was working perfectly fine until this morning. Now it says Device Not Found. Any suggestions on how I can get it working again? Thanks in advance.

Bump. Anyone know?

Does fastboot work then?
Are you on windows? window 7?
Try every USB port on your computer, my win7 machine will only recognise my device through one usb port.

liam.lah said:
Does fastboot work then?
Are you on windows? window 7?
Try every USB port on your computer, my win7 machine will only recognise my device through one usb port.
Click to expand...
Click to collapse
Windows 7. Fastboot works just fine. Never had this problem before. My Nexus shows up as connected and working in Windows Device Manager. WTF is going on? Frustrating.
Tried all USB ports. All of them recognize the device, but "adb remount" returns: "error: device not found."

Part Four said:
Windows 7. Fastboot works just fine. Never had this problem before. My Nexus shows up as connected and working in Windows Device Manager. WTF is going on? Frustrating.
Tried all USB ports. All of them recognize the device, but "adb remount" returns: "error: device not found."
Click to expand...
Click to collapse
Do you have the Allow USB Debugging option checked? Maybe it got unchecked on accident.

Diceman4 said:
Do you have the Allow USB Debugging option checked? Maybe it got unchecked on accident.
Click to expand...
Click to collapse
Yeah, thanks. I've had it checked. I've tried to adb remount on all 4 of my computers tonight and none of them are finding my device anymore. Might be time for a wipe and reflash. Anyone else have a suggestion before I commit to a wipe?

I guess I'm going to wipe and reflash.

1)make sure usb tethering is off.
2)maybe reinstall the latest driver from http://developer.android.com/sdk/win-usb.html ?

I just wiped and reflashed and still no dice. Might as well just go back to my nandroid backup and keep searching for answers.

I know this might be a little late, but I would like to post how I solved my problem. I too was experiencing this problem, no matter what USB Port I plugged my phone into, it just would not work. It kept saying "error: device not found." After searching on Google for a quite a while, I decided to again play around in device manager. I remember a long time ago, a client of mine had a problem with certain USB Devices not working, the solution was to go into Device Manager expand "Universal Serial Bus controllers" and right click each "USB Root Hub" and click "Uninstall."
This did the trick for me. After I hit the right USB Root Hub, my computer detected three new Android controllers that needed drivers: CDC, CDC Abstract, and Android Composite. I installed the downloaded Android drivers for the Android Composite and guess what, IT WORKS!
Hope this helps someone.
Mike Lierman
Founder and Owner of
Invise Solutions
invisesolutions.com

0vermind said:
I know this might be a little late, but I would like to post how I solved my problem. I too was experiencing this problem, no matter what USB Port I plugged my phone into, it just would not work. It kept saying "error: device not found." After searching on Google for a quite a while, I decided to again play around in device manager. I remember a long time ago, a client of mine had a problem with certain USB Devices not working, the solution was to go into Device Manager expand "Universal Serial Bus controllers" and right click each "USB Root Hub" and click "Uninstall."
This did the trick for me. After I hit the right USB Root Hub, my computer detected three new Android controllers that needed drivers: CDC, CDC Abstract, and Android Composite. I installed the downloaded Android drivers for the Android Composite and guess what, IT WORKS!
Hope this helps someone.
Mike Lierman
Founder and Owner of
Invise Solutions
invisesolutions.com
Click to expand...
Click to collapse
Unfortunately this didn't work for me. I tried uninstalling every single USB device/port/hub on two of my systems, then rebooting and letting it do its thing, then plugging in my Nexus and installing the ADB drivers. Still can't connect via ADB. This is a complete mess. No clue how/why this happened or what I can do to get it back.

0vermind said:
I know this might be a little late, but I would like to post how I solved my problem. I too was experiencing this problem, no matter what USB Port I plugged my phone into, it just would not work. It kept saying "error: device not found." After searching on Google for a quite a while, I decided to again play around in device manager. I remember a long time ago, a client of mine had a problem with certain USB Devices not working, the solution was to go into Device Manager expand "Universal Serial Bus controllers" and right click each "USB Root Hub" and click "Uninstall."
This did the trick for me. After I hit the right USB Root Hub, my computer detected three new Android controllers that needed drivers: CDC, CDC Abstract, and Android Composite. I installed the downloaded Android drivers for the Android Composite and guess what, IT WORKS!
Hope this helps someone.
Mike Lierman
Founder and Owner of
Invise Solutions
invisesolutions.com
Click to expand...
Click to collapse
Thanks it helped me

try going into the device manager and removing the driver. Remove your phone from your computer then reconnect it. Upon the request to allow drivers to install, tell it you want to install from a specific location and point the driver installer to a known good copy of the ADB driver.
-------------------------------------
Sent via the XDA Tapatalk App from my Nexus One

[Q] Captivate USB problems

Hi everyone,
I have an AT&T Captivate SGH-i897 (2nd hand) and i can't mount the phone to my laptop (winXP 32bit). When i plug in the cable to the phone and then the PC i get the "device not recognized".I've donwloaded the Samsung drivers from the xda wiki page and extracted them and tried to update the driveres via Device Mng ,but didn't work.Also dl'ed the Samsung drivers 5.0.x instaled ,and still nothing.USB Debugging is on...
So to recap,my top can't recognize the phone('s internal sd card) so plz help ???????

Try this, go into usb settings and choose "mass storage"
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

install kies

I would also recommend trying to fully uninstall all the drivers that associated on your pc with your phone (samsung or otherwise), and then reinstall the drivers before you plug in your phone. Then try to reconnect.

Just covering the basics. Assuming your phone is working correctly.
You have tried multiple USB ports on your computer, particularly those on the back if it's a desktop.
You have installed correct drivers (x86 or x64)
" for the correct operating system.
You have uninstalled the drivers before trying to reinstall.
You've tried to get Windows/ Mac to find them online (assuming you're using versions of OS that support doing that)
You've first tried Kies mini before full version, uninstalling in between. (Kies full version isn't supported for US, there are workarounds, but that's a different discussion)
On the phone you tell the phone to connect 'USB storage' (from the pull down menu after connected or in the settings)

I too am having problems with USB connectivity on a notebook with Win7/64. The usual failure mode is Windows not recognizing the USB device. I have followed ZBigT's basics, step by step and still cannot connect.
FWIW, my registry is awash with Samsung entries, some of which cannot be deleted.
I've even tried the AIO Toolbox application (to install the 64 bit drivers) to no avail.
Any other tips?

Is usb debugging turned off?

o hey guys sry for keeping u waiting,
i menaged to install ginger ,
the problem was my lap....rusty old bucket!!!!
had my friend come over with his lap and it worked like a charm ,
the problem is now i need a new one ;(,
damn

mrhaley30705 said:
Is usb debugging turned off?
Click to expand...
Click to collapse
Yes. Still no love. Have tried:
usb_drivers_GalaxyS_x64
SGH-i897_Captivate_USB_Drivers_5_02_0_2
mini-KIES
Kies
AIO
uninstalling reinstalling each time
When I plug in the Captivate, any of 3 USB ports on the laptop, Windows gives the "Unrecognized Device..." message.

Go to settings/about phone. Look at the very bottom to see what rom you are running.

mrhaley30705 said:
Go to settings/about phone. Look at the very bottom to see what rom you are running.
Click to expand...
Click to collapse
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.

mabovalu said:
Paragon RC6.0
FWIW, I also have a Win7/64 desktop with the usb_drivers_GalaxyS_x64 installed and that works fine; can connect see "drives", use ODIN, adb commands etc.
It just the notebook, which I would like to be able to use to connect, especially when I travel, which has issues.
Click to expand...
Click to collapse
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.

mrhaley30705 said:
Check in program files for a Samsung folder. There may be remnants from old drivers that need to be manually deleted.
Click to expand...
Click to collapse
Thanks for sticking with this. I was able to connect. I as focused on the Registry remnants, but your advice to clear out the Samsung folder in Programs worked. Thank you.
Additional comments: I am now running the Dlev ROM, it's OK, but when I plugged in the USB cable, just to the phone, it launched the Alarm Clock app! So I deleted that.
Then on the first of my four USB ports I got a USB driver failure to install, then the Windows Unrecognized USB device on ports 2 & 3. On port 4 it worked. (This is a Lennovo/Thinkpad notebook.)
I used the usb_drivers_GalaxyS_x64 package as that also worked on my desktop.
Thank you very much.

USB Mount Issues (CM7)

Hey, everyone, I tried posting about this in the CM7 general discussion thread, but no one seemed apt to respond.
I think this was a problem that popped up in the 60s or 70s in terms of nightlies, but I'm having it again now since around the 155 mark.
I'm on 160 and when I plug my NC into the USB cable, I no longer get any options to connect for file transfers in the notification area. If anyone could help me out with this, I'd really appreciate it. It's just so perplexing and no one seems be having this issue except me. If it's user-side error, that's fine as well, I'd just like to know how to fix it.

1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?

votinh said:
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
Click to expand...
Click to collapse
1. No, nothing comes up.
2. The notification area remains blank.
3. I'm running it off eMMC.
Thanks for taking the time, by the way!

If so, unplug the usb cable then replug in a few times and see what happens.
If still nothing, try to use other usb cable.

Oh, btw, have you had Nookcolotweaks app installed?

I do have Nook Tweaks installed, yes. I'm using the cable that came with the Nook, but I'm not sure I have any other cables around.

Do make sure you check OFF the USB Host feature (reboot and reconnect)

I gave that a try, too, but still nothing. So confusing!

Don't be so hard on yourself.
Let try it on different computer if you have.
Also try difference usb cable.
Last, if nothing works, update latest nightly build

When you disconnect and reconnect the nook in testing/trying to get it recognized... unplug usb cable from computer... its made a difference at times.

I know this sounds basic but in applications-settings ensure you have usb debugging checked. Sometimes when flashing different nightlies, settings change.
Sent from my NookColor using Tapatalk

Thanks again for all the help, everyone! I made sure USB debugging was checked and tried unplugging/replugging the cable, but there's still no notification coming up.

A new development:
I tried connecting it to my Windows PC instead of my Linux and it brought up this message that said it didn't recognize the device. I also tried to get ADB to see it and it can't. Does this information help or am I in trouble here?

Next time, do clearly indicate that you are using Linux or Windows. I'm sure many members here are Linux but still far less support than Windows world.
When I provided those suggestions in previous posts, I meant in Windows.
Anyway, back to your issue.
1. "it didn't recognize the device" because of missing adb usb driver. You need to get it installed first in order to use ADB, however it has nothing to do with your usb mass storage function. For now, you don't need to worry about it just yet.
2. Back to my question before, have you seen any "removable" on the PC (Windows)
Along with USB Host uncheck, if still having problem, I would suggest you either downgrade to the earlier versions or wait until tomorrow and update with another nightly build.
Good luck

I have the ADB drivers installed in Windows, as far as I know. I've used it before.
I typed "adb devices" into the prompt and it doesn't see the NC at all. Since one of the nightlies seems to be what prompted this sudden change in connectivity, I guess I'll just hope that one of the new ones can fix it. Thanks again.
Also, Windows doesn't show anything "removable" except for my external HD.

Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.

arda99 said:
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
Click to expand...
Click to collapse
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.

junkrobot said:
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
Click to expand...
Click to collapse
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
If you've installed ADB drivers, you might want to remove it as this might mess up usb storage.

arda99 said:
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
Click to expand...
Click to collapse
Alrighty. I have those two. I've connected my NC to ADB both wirelessly and and with the cable in the past, so this should all be straightforward anyhow. It just plain refuses to cooperate.

Go to the Marketplace and download "Nook Color UMS" app. Follow instructions and it will mount properly. I had the same issue used it and it mounts proper through the app.

Why does my computer no longer recognize my phone after doing marshmallow update?

I have two Nexus 6s, one completely stock and one that I just upgraded to Marshmallow. I downloaded sdk and minimal adb and fastboot today in order to install marshmallow. I just plugged in my completely stock unmodified Nexus 6 into my computer to get my photos off my stock Nexus before I send it back to amazon and although the phone charges, nothing pops up for it being a storage device, I switched it between MTP and PTP on the phone but it does nothing, the phone does not show up, same goes for the Nexus 6 that has marshmallow on it, also switched that to MTP. My computer detects the phone because it allows me to eject it from usb but that is about it. Anything else I can try? trying to get pics off the old Nexus before I send it back.

PolishDude said:
I have two Nexus 6s, one completely stock and one that I just upgraded to Marshmallow. I downloaded sdk and minimal adb and fastboot today in order to install marshmallow. I just plugged in my completely stock unmodified Nexus 6 into my computer to get my photos off my stock Nexus before I send it back to amazon and although the phone charges, nothing pops up for it being a storage device, I switched it between MTP and PTP on the phone but it does nothing, the phone does not show up, same goes for the Nexus 6 that has marshmallow on it, also switched that to MTP. My computer detects the phone because it allows me to eject it from usb but that is about it. Anything else I can try? trying to get pics off the old Nexus before I send it back.
Click to expand...
Click to collapse
btw adb sees the phone no problem

I have the same problem. Windows seems to recognize the phone, but it displays no content when I try to browse files.
Just did a clean flash of the factory image.
EDIT:
Ok, I'm an idiot... here's the solution:
http://forum.xda-developers.com/showpost.php?p=63151023&postcount=2

Yadao said:
I have the same problem. Windows seems to recognize the phone, but it displays no content when I try to browse files.
Just did a clean flash of the factory image.
EDIT:
Ok, I'm an idiot... here's the solution:
http://forum.xda-developers.com/showpost.php?p=63151023&postcount=2
Click to expand...
Click to collapse
nope that does nothing on my phone, both are set correctly at MTP or PTP, nothing works
BTW when I eject the USB it lists it as "android adb interface" I have a feeling that is why it is not showing up?

Mine just says MTP when I eject it. Did you try toggling USB debugging on and off?

Yadao said:
Mine just says MTP when I eject it. Did you try toggling USB debugging on and off?
Click to expand...
Click to collapse
I deleted the adb driver and that fixed the issue but that can't be the correct way because I think it would be pointless to have to install and delete the adb driver each time I want to use it? I knew it was more computer related than phone related but what is the correct way to make the phone work with a adb driver installed on the computer?

PolishDude said:
I deleted the adb driver and that fixed the issue but that can't be the correct way because I think it would be pointless to have to install and delete the adb driver each time I want to use it? I knew it was more computer related than phone related but what is the correct way to make the phone work with a adb driver installed on the computer?
Click to expand...
Click to collapse
I honestly don't know. I've always had mixed results. Sometimes it would work automatically, sometimes I'd have to manually install the google drivers when the phone is in the bootloader.

Had the same "problem", to fix it and for windows to show the contents of the phone, you just need to pull down the top drawer and select mtp file transfer from the USB options. It is set for " charge only" as default. Try it out!
Sent from my Nexus 6 using Tapatalk

Pull down the status bar and set charge only to transfer files

Tek-Toyz said:
Had the same "problem", to fix it and for windows to show the contents of the phone, you just need to pull down the top drawer and select mtp file transfer from the USB options. It is set for " charge only" as default. Try it out!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yasharkhan said:
Pull down the status bar and set charge only to transfer files
Click to expand...
Click to collapse
Exactly: it is not a problem, but just a new way to manage USB connections. You just have to pull down the status bar and choose one of the USB options for your Nexus 6

lol you guys aren't understanding, I did that and it did not fix the issue. The phone was still not recognized as a storage device. I also tried a Nexus 6 that was on 5.1.1 which does not have the charging only option in the drawer and it also was not recognized but once I deleted the adb driver from my computer, my computer saw both as storage devices when I put them into MTP mode

Go into developer settings
Make sure checked Debugging on
Then Scroll down
Look for MTP CHange it to something else in the settings
then back MTP Your computer will then see it it bug in 6.0
Follow my Video
https://youtu.be/At0auL6CQeg

[Q] cant connect to pc in linux or windows

hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!

Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.

sorry double post

Same issue here. I've had no luck sorting it out.

Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.

ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.

ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?

Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?

ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.

I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.

ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!

ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!

Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?

ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?

Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.

ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.