Go Back   Android Forums > Android Phones > Samsung Captivate > Captivate - All Things Root
Captivate - All Things Root Rooting, ROMS, Overclocking, etc.

Find everything you need for the Galaxy S5 and discuss it in our S5 forum!
Have you seen that OnePlus One's awesome camera?? The forum is over here!

test: Reply
 
LinkBack Thread Tools
Old July 29th, 2010, 12:26 PM   #1 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jul 2010
Location: Seattle, WA
Posts: 14
 
Device(s): Samsung Galaxy S (Captivate)
Carrier: Not Provided

Thanks: 4
Thanked 0 Times in 0 Posts
Question adb shell - error: device not found

I've seen different posts about this, but none for the captivate, and none in the past month, so...

Last night I rooted my captivate using the stickied thread in this forum. Worked great! Simple, and not much to it. I have the Superuser Permissions app in my app list.

This morning I installed the android sdk and the drivers from the samsung website, enabled usb debugging on my phone, connected the phone, and did the following in my cmd prompt:

C:\android-sdk-windows\tools>adb shell

(yes, that is the correct location of the android sdk folder)

...but all i'm getting is 'error: device not found'.

I tried uninstalling my drivers and doing it again, this time connected to a different USB port, and still the same thing.

Anyone have any insights? I'm able to successfully connect my phone to my machine and view it like a storage device (drag folders around, etc).

ChapelJuice is offline  
Reply With Quote
sponsored links
Old July 29th, 2010, 12:43 PM   #2 (permalink)
Junior Member
 
rrrrramos's Avatar
 
Join Date: Jul 2010
Location: Flower Mound, TX
Posts: 89
 
Device(s): Samsung Captivate
Carrier: Not Provided

Thanks: 0
Thanked 11 Times in 9 Posts
Default

Try going to the install directory, then doing

cd tools
adb shell
su
rrrrramos is offline  
Reply With Quote
Old July 29th, 2010, 12:50 PM   #3 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jul 2010
Location: Seattle, WA
Posts: 14
 
Device(s): Samsung Galaxy S (Captivate)
Carrier: Not Provided

Thanks: 4
Thanked 0 Times in 0 Posts
Default

Thanks for your quick reply!

But, I got the same thing. I did notice when I plug it in I get a notification (windows xp) that says:

"A problem occurred during hardware installation. Your new hardware might not work properly."

And I only get that message when I plug my phone in while USB debugging is on.

I've also read that people say to plug the phone in with USB debugging off, then once it's plugged in turn it on, however I'm unable to do this (I get a pop up on my phone that says "Attention USB is connected. Remove the cable").
ChapelJuice is offline  
Reply With Quote
Old July 29th, 2010, 02:18 PM   #4 (permalink)
Junior Member
 
Join Date: Jul 2010
Posts: 19
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by ChapelJuice View Post
Thanks for your quick reply!

But, I got the same thing. I did notice when I plug it in I get a notification (windows xp) that says:

"A problem occurred during hardware installation. Your new hardware might not work properly."

And I only get that message when I plug my phone in while USB debugging is on.

I've also read that people say to plug the phone in with USB debugging off, then once it's plugged in turn it on, however I'm unable to do this (I get a pop up on my phone that says "Attention USB is connected. Remove the cable").
Did you install both drivers from the stickied USB thread? That's what fixed everything for me.
biocalves is offline  
Reply With Quote
Old July 29th, 2010, 02:20 PM   #5 (permalink)
Member
 
Join Date: Jun 2010
Location: Indiana
Posts: 134
 
Device(s): Skyrocket
Carrier: Not Provided

Thanks: 4
Thanked 7 Times in 5 Posts
Default

Whenever you get an error in the command prompt, try typing this out and then retrying your command:

Code:
adb kill-server
__________________
Samsung Galaxy S2 Skyrocket
Darkeligos is offline  
Reply With Quote
Old July 29th, 2010, 11:05 PM   #6 (permalink)
Junior Member
 
shocker's Avatar
 
Join Date: Nov 2009
Location: Michigan
Posts: 82
 
Device(s): Droid X Gingerbread LexLite Ginger
Carrier: Not Provided

Thanks: 0
Thanked 7 Times in 6 Posts
Send a message via AIM to shocker
Default

is busybox installed and running on your phone?
shocker is offline  
Reply With Quote
Old July 30th, 2010, 01:17 PM   #7 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jul 2010
Location: Seattle, WA
Posts: 14
 
Device(s): Samsung Galaxy S (Captivate)
Carrier: Not Provided

Thanks: 4
Thanked 0 Times in 0 Posts
Default

Bah, I tried all of your suggestions above, and still get device not found. I uninstalled the drivers and installed the ones at the top of the stickied thread, but noticed something a bit strange. I downloaded USBDeview and saw my devices (listed below), but only one of them says it's connected (again, USB Debugging is checked):

SAMSUNG_Android
SAMSUNG SGH-I897 Card USB Device
Communication
Connected = Yes

SAMSUNG_Android
CDC Abstract Control Model (ACM)
Communication
Connected = No

SAMSUNG_Android
USB Mass Storage Device
Mass Storage
Connected = No

SAMSUNG_Android
S3C6410 Android ADB
Vendor Specific
Connected = No

Also, I installed BusyBox and have the latest version...but how do you 'run' it? You mean just have the application open when I connect the phone to the machine? I did see that there's a green dot in the superuser permissions app next to it, so does that mean it's running?

Again, thanks for your help.
ChapelJuice is offline  
Reply With Quote
Old August 2nd, 2010, 04:06 PM   #8 (permalink)
Junior Member
 
Join Date: Jul 2010
Location: STL
Posts: 88
 
Device(s): Samsung Captivate w/ JM2 I9000 ROM, SamSet 1.7
Carrier: Not Provided

Thanks: 1
Thanked 16 Times in 10 Posts
Default

Make sure you have USB Debugging turned on in Settings > Applications > Development. A few times after rooting / flashing I forgot to turn it back on and ADB won't connect until it is.
keredini is offline  
Reply With Quote
Old August 5th, 2010, 01:41 PM   #9 (permalink)
Junior Member
 
Join Date: Jul 2010
Location: NY
Posts: 26
 
Device(s): Samsung Captivate
Carrier: Not Provided

Thanks: 0
Thanked 6 Times in 3 Posts
Default

I've gotten that error before while trying to use the SDK. Even though the computer saw the phone using Mass Storage setting without a problem.

Wasn't until I plugged it into a different usb port that it worked. Go figure.
iMouseOne is offline  
Reply With Quote
Old August 5th, 2010, 08:43 PM   #10 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jul 2010
Location: Seattle, WA
Posts: 14
 
Device(s): Samsung Galaxy S (Captivate)
Carrier: Not Provided

Thanks: 4
Thanked 0 Times in 0 Posts
Default

Yeah, thanks all. I tried it on a different computer and it worked right away, so not sure why my work machine can't get it to run still. Kind of annoying.
ChapelJuice is offline  
Reply With Quote
sponsored links
Old August 26th, 2010, 11:18 AM   #11 (permalink)
New Member
Thread Author (OP)
 
Join Date: Jul 2010
Location: Seattle, WA
Posts: 14
 
Device(s): Samsung Galaxy S (Captivate)
Carrier: Not Provided

Thanks: 4
Thanked 0 Times in 0 Posts
Default

Okay, so just to kind of close this thread and to hopefully make other peoples lives easier if they're having the same troubles, I finally got this working. How, you may ask? Well, I've read it before on these forums, but I didn't want to believe it. All I did was just kept uninstalling and re-installing the Samsung drivers, and eventually it worked. Didn't do anything else.

So...if you're having the same troubles as me...keep un/re-installing the drivers, and it should work eventually.
ChapelJuice is offline  
Reply With Quote
Old August 28th, 2010, 01:37 PM   #12 (permalink)
Member
 
Join Date: Jul 2010
Posts: 298
 
Device(s):
Carrier: Not Provided

Thanks: 8
Thanked 11 Times in 10 Posts
Default

Try KIES. Go on and click something like Driver Reinstallation. Does the trick.
yahoowizard is offline  
Reply With Quote
Old May 22nd, 2011, 10:36 PM   #13 (permalink)
New Member
 
Join Date: May 2011
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I am in the process of rooting and Im getting the same thing. Wh I turn my phone on it shows google with a lock at the bottom. Loads up in the storage setting, I have not mounted it and while typing adb shell i get the same error. I have not been able to complete the rooting process and now my phone is locked at this screen
vwdoc2000 is offline  
Reply With Quote
Old June 15th, 2011, 09:00 PM   #14 (permalink)
New Member
 
Join Date: Jun 2011
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I have a captivate and an intel iMac. What worked for me was to plug the USB cable into the back of the computer instead of the keyboard. It didn't like the keyboard port for some reason. At the same time I removed my Flip Mino (so maybe a conflict, but I think it was the Keyboard port, not everything likes being plugged in there).

Eric
viking79 is offline  
Reply With Quote
Reply
Tags
drivers adb device android sdk


Go Back   Android Forums > Android Phones > Samsung Captivate > Captivate - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 11:02 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.