Go Back   Android Forums > Android Phones > Samsung Galaxy S2 (T-Mobile)

Like Tree1Likes
  • 1 Post By MikePhoenix

test: Reply
 
LinkBack Thread Tools
Old October 10th, 2012, 09:56 PM   #1 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default Samsung Galaxy S2 will not work with ADB

I have tried everything suggested in the tutorial in this forum. I followed all the instructions and ADB simply will not recognize this device that I purchased through T-Mobile. I have attempted it on 3 different systems. PDANet doesn't recognize the device when I try to install it. Samsung technical support was absolutely useless.

If you want a device for development, I would suggest staying away from Samsung.

Advertisements
MikePhoenix is offline  
Reply With Quote
sponsored links
Old October 11th, 2012, 05:38 AM   #2 (permalink)
Senior Member
 
Atma's Avatar
 
Join Date: Dec 2011
Location: North Carolina
Gender: Male
Posts: 6,070
 
Device(s): Samsung Galaxy S4, Samsung Galaxy S2; Nexus 10
Carrier: T-Mobile

Thanks: 3,427
Thanked 2,906 Times in 1,852 Posts
Default

Hi Mike. Have you tried installing Samsung Kies? Do you have USB Debugging checked in settings developer options? Does your computer recognize your phone when you plug it in?
__________________
Helpful FAQ's, Site Rules/Guidelines
Atma is offline  
Reply With Quote
Old October 11th, 2012, 02:50 PM   #3 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Yes, I have tried Kies, I have USB debugging turned on, and my computer recognizes the phone. I can transfer files between the device and computer with no problem.
MikePhoenix is offline  
Reply With Quote
Old October 11th, 2012, 02:55 PM   #4 (permalink)
Senior Member
 
Atma's Avatar
 
Join Date: Dec 2011
Location: North Carolina
Gender: Male
Posts: 6,070
 
Device(s): Samsung Galaxy S4, Samsung Galaxy S2; Nexus 10
Carrier: T-Mobile

Thanks: 3,427
Thanked 2,906 Times in 1,852 Posts
Default

Ok, are you using Win 7? If so, try going to the adb platform tools folder. Hold down shift and click right mouse button, choose open command window here. Type in adb devices. Anything?
Atma is offline  
Reply With Quote
Old October 11th, 2012, 03:27 PM   #5 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

That is EXACTLY what I did. It didn't work.
MikePhoenix is offline  
Reply With Quote
Old October 11th, 2012, 05:44 PM   #6 (permalink)
Senior Member
 
Atma's Avatar
 
Join Date: Dec 2011
Location: North Carolina
Gender: Male
Posts: 6,070
 
Device(s): Samsung Galaxy S4, Samsung Galaxy S2; Nexus 10
Carrier: T-Mobile

Thanks: 3,427
Thanked 2,906 Times in 1,852 Posts
Default

I'm not sure what to suggest next. Do you have another device you can try it with? Do you have another computer you could try it on?
Atma is offline  
Reply With Quote
Old October 11th, 2012, 07:15 PM   #7 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

I have tried it on three different computers. I'm about to try a different device.
MikePhoenix is offline  
Reply With Quote
Old October 11th, 2012, 08:22 PM   #8 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Just tried it with my old Nexus One and it worked without a hitch. So it is not a problem with the way I have the SDK setup, it is a problem with the Samsung device.
MikePhoenix is offline  
Reply With Quote
Old October 11th, 2012, 08:40 PM   #9 (permalink)
Senior Member
 
Atma's Avatar
 
Join Date: Dec 2011
Location: North Carolina
Gender: Male
Posts: 6,070
 
Device(s): Samsung Galaxy S4, Samsung Galaxy S2; Nexus 10
Carrier: T-Mobile

Thanks: 3,427
Thanked 2,906 Times in 1,852 Posts
Default

Quote:
Originally Posted by MikePhoenix View Post
Just tried it with my old Nexus One and it worked without a hitch. So it is not a problem with the way I have the SDK setup, it is a problem with the Samsung device.
Well that's strange. Did you use the same cable with both phones? Are you using the usb cable that came with the GS2?

Try these drivers and see if it makes any difference. They are older drivers and I'm not sure it would help.
Atma is offline  
Reply With Quote
Old October 15th, 2012, 10:43 PM   #10 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Those drivers took forever to install and still didn't work. I have used the same cable that came with the Samsung and the cable that came with the Nexus to attempt to connect the Samsung.

Like I said, I would think twice about buying a Samsung as a development phone.
MikePhoenix is offline  
Reply With Quote
sponsored links
Old November 23rd, 2012, 07:59 PM   #11 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

This problem was corrected when my phone was upgraded to Android version 4.0.4. Was running version 2.3.3 when I reported this last month.
Atma likes this.
MikePhoenix is offline  
Reply With Quote
The Following User Says Thank You to MikePhoenix For This Useful Post:
Atma (November 24th, 2012)
Old November 24th, 2012, 08:32 AM   #12 (permalink)
Senior Member
 
Atma's Avatar
 
Join Date: Dec 2011
Location: North Carolina
Gender: Male
Posts: 6,070
 
Device(s): Samsung Galaxy S4, Samsung Galaxy S2; Nexus 10
Carrier: T-Mobile

Thanks: 3,427
Thanked 2,906 Times in 1,852 Posts
Default

Glad you got it working Mike and thanks for letting everyone know how you did it.
Atma is offline  
Reply With Quote
Old November 24th, 2012, 11:34 PM   #13 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Feb 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Sure thing, but I can't take any credit. It was the automatic update that had the added benefit of updating to Android 4.0.4. Not sure if there was a problem with the 2.3.3 version that was originally installed on the T-Mobile release of the Galaxy SII or if Samsung and/or T-Mobile put in a fix with the update. I find it hard to believe that I'm the only one who ever had this problem.
MikePhoenix is offline  
Reply With Quote
Reply

Buy the Samsung Galaxy S II 4G
Sign up for instant notification when the Samsung Galaxy S II 4G goes on sale!
Samsung Galaxy S II 4G

The Galaxy S2 (sometimes known as the Galaxy S II) is the follow up to Samsung's widely successful Galaxy S lineup. This time, the Galaxy S2 raises all the stakes and Samsung has found a way to double almost every spec in a true, one of a kind ... Read More

Tags
adb device, samsung galaxy s2 t-mobile


Go Back   Android Forums > Android Phones > Samsung Galaxy S2 (T-Mobile)
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 05:48 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.