Ok i made a post and it was moved to trash and it says i dont have permission to post there so ill just move it here.....
Ok well i have been trying for like 2 hours now to get ADB to work. I followed all the guides, installed the 1.5 SDK and everything even did the Enviroment Variable thing as well. When i plug in my G1 i dont get any popup of a new device or anything. In device manager there is not ADB as well just Android Phone and when i uninstall it, it installs again on its own when i plug the phone in again. I went to cmd and typed in adb shell but i get "device not found".
Anyone know whats wrong? Btw im using Windows Vista SP1
I went into fastboot and that gave me the new driver notification so i have fastboot working but when i go to ADB i get device not found and device manager finds my phone as a universal usb device or w/e. Why wont this work?!?!?!?
It sounds like you didn't install the drivers.
Read this (I wrote it). You should have adb working in no time.
http://androidcommunity.com/forums/f28/what-is-adb-made-easy-17732/
Did you update the driver for the phone (should currently be showing as one of the USB Composite Device, IIRC) with the ADB driver included in the SDK (android_usb.inf in <sdk root directory>\usb_driver\)?
If you are using a 64-bit edition of Vista, alternatively, you can try the 64-bit signed driver found here. Also, you can try the updated driver I have attached.
Well, if you used your phone as a card reader at any point before you enabled USB debugging, then you'll have to uninstall the USB Mass Storage Device associated with your phone first. After that, unplug and plug the USB cord back in and it'll install the USB Mass Storage Device and then it'll ask about the ADB interface. That's your chance to install the driver that everyone is talking about but didn't spend the time to explain how to get there if you were in this situation...
never mind i got it. I used a program to uninstall all the Android USB drivers then i plugged it back in and it worked. Thanks for the help guys!
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Uninstall the usb drivers. Not sure what there called when kies installs it
fivebraids said:
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Click to expand...
Click to collapse
I had a similar problem and it turn out that Kies hosed up all my drivers...The only way I got it fix was by totally removing any trace of Kies and then uninstalled all my samsung drivers and usb drivers and then rebooted my pc. Then I reinstalled the samsung drivers and win 7 did the rest...
Well, I haven't uninstalled Kies yet. Although I have uninstalled and reinstalled the drivers from the ODIN thread. No difference.
I even uninstalled the ODIN referred drivers and tried the drivers directly from the Samsung site. Still no difference.
I'll go ahead and try uninstalling Kies and then the ODIN drivers, reinstall the ODIN drivers and see if that helps.
I've also ordered a new cable, since I've read a few threads on other forums where the problem was bad cables. I was going to go to AT&T and get a new cable, but they want $24.99. I just ordered a pair from Amazon at $3.99 each, with free shipping!!
Thanks...off to try ridding myself of Kies...
Well, deleting Kies (and associated drivers) didn't help!
After deleting Kies, I tried both the ODIN referenced drivers, as well as those from the Samsung site. Still not working!
I guess I'll wait on a new cable and see if that helps...
Okay, I think I'm in BIG TROUBLE here!!!
New cables arrived today, but they made no difference at all! Still getting the USB Device Not Recognized message. Doesn't matter if I plug the cable in while the phone is on and select any of the connection options (Kies, Mass Storage, etc.). It gives me the same message when I have Odin running and plug the phone in while holding the volume keys.
To further add to the problem, I tried installing the Odin referenced USB drivers on my wife's laptop which has never seen this phone or Kies. SAME PROBLEM!
I'm thinking there might actually be something wrong with the physical port on the phone. But this highlights my actual problem...
How can I return the phone (for the second time) when this phone has been rooted and is running SRE 1.2.1a ?!?!?
Apparently, there's no way for me to restore this thing to stock without USB.
Any ideas/suggestions?
Relax dude--I just got a captivate a few weeks ago, and have it working on tmobile.
For the drivers, when you plug your phone in, you're getting some errors. I know you uninstalled the drivers, but to double-check, open up device manager and see if there are any ! marks for the phone. Right-click and uninstall the entries. Also, you might try using a different USB port. I can only get my phone to connect using one of the 6 usb ports i've tried. Finally, and I don't know if these are the drivers for Odin, but I downloaded these drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
When the phone connects, you might want to go to device manager, find the device(s), righ-click and and select 'update driver'. then, in the driver update window, pick 'manual' or 'let me specify location' and navigate to the unzipped SGH-i897_Captivate_USB_Drivers_5_02_0_2 file. Then, it should work.
Like I said, I have no idea if those are the drivers for odin...but I'm about to find out
I'd like to relax, but I think I'm dealing with a phone with a bad usb port...and since I've rooted, SRE'ed, etc., I won't be able to return it.
Anyway...
The driver you're using is the 'direct from Samsung' version, not the one for Odin.
Regardless, I've been through the exercise you propose...both with the Samsung and Odin drivers. When you attempt to manually install drivers, you need to point the installer to the ".inf" setup information file to use. The Samsung driver has three: SSADADB2.inf, SSADBUS.inf, and SSADMDM2.inf.
I get the following message when trying to use any of these three setup files:
The specified location does not contain information about your hardware.
Oh, and I've tried several different USB ports on the computer...both on my external hub and directly into the back of the machine.
Thanks for the suggestions, but still not working...
I'm really thinking I have a bad port on the phone...especially since trying the connection on my wife's laptop produces the exact same error.
Dam...
Still trying to find a way to restore the phone to stock without a USB connection...
i also have this "DEVICE NOT RECOGNIZED" on my sony x1.
Drivers
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
superdog404 said:
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
Click to expand...
Click to collapse
Not sure different USB drivers would help, but I went to the thread you show and tried to download the 32bit drivers. This is what I get:
{"error": "Invalid access attempt for this token"}
Oh well, thanks anyway.
I'm still thinking that the problem is hardware on the phone. I've tried four different cables, and three different computers. All show same problem of DEVICE NOT RECOGNIZED.
Still trying to figure out how to restore to stock without USB connection for ODIN so I can exchange for a new phone...
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
No modifications, same error
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
mukherji said:
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
Click to expand...
Click to collapse
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Rhiannon224 said:
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
JayPhill89 said:
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
Click to expand...
Click to collapse
USB is set to Ask on connection
Debug off or on makes no difference
All tests have been done on XP machines (3 different ones)
I'm all but positive this is hardware...
Thanks for trying to help!
Rhiannon224 said:
<snip>
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
I haven't tried ADB, but I'm not understanding how ADB would be able to connect when the connection to the computer is failing at the driver level. I guess I can give it a try tomorrow.
Thanks for trying to help!
What would REALLY help me is for someone to post a backup taken of a completely stock (ODIN'ed) phone using ROM manager. I'm thinking I could load that on the phone and then be able to return it for a new phone!
Any volunteers...please?
techmik67 said:
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
Click to expand...
Click to collapse
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
jaxf250 said:
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
Click to expand...
Click to collapse
Great!! Glad it all worked for you. My next advice is, before adding anything READ A LOT!!! =) Decide what you want from the descriptions and issues you will see in the threads....
Happy modding!!
I didn't see, I just skimmed through bit did you try to put the phone in download mode and see if windows sees that (different drivers come in to play in download mode and none of the touch wiz stuff is running)? it would test the idea of a bad port.
then you can still always install linux and use adw from there, linux and macs don't need drivers. if that doesn't work, put insurance on the phone if you haven't already then drop it in the sink and get another one.
also I think although I don't know but I think adw may have something to do with it. and incorrectly uninstalling it. first put the phone in download mode then you can work from there on ways to fix that.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ok, I've given up trying to get this to work. I'm 100% convinced this is a hardware problem with the phone!
I had another thread going, looking for a way to restore this phone (remove SRE, SU, etc.) without usb/ODIN so I could return it to AT&T. I've figured out how to restore it to stock and will be heading to AT&T in the morning.
Thanks to everyone for their patience and assistance!
Once i got my new nook color i rooted it with auto nooter, and im running 1.0.1, on my previous nook i rooted it and adb worked right then, now i cant get adb access, im using the same computer and everything, all thats diferent is its a new nook. I have full root access and can install apps and everything. Any help?
Seems to be a common problem. You can launch NookColorTools and fix it temporarily. Go to "Development" and then unchecked and then recheck the USB Debugging box.
Ok I've been doing that for a while and finnaly got the message that USB debugging is only for development. It works now......
Sent from my LogicPD Zoom2 using XDA App
Get ADB wireless, it works great.
I've had zero luck using usb adb, but adb wireless works great!
I was having similar issues so after many many attempts I just decided to go with adb wireless and would definitely recommend going that route if you can't get it working over usb.
Yeah, getting ADB to work requires a lot of uninstalling/reinstalling drivers and unplugging/replugging the device, it's very temperamental.
can someone link me to a link on how to use/setup adb wireless
beezy69 said:
can someone link me to a link on how to use/setup adb wireless
Click to expand...
Click to collapse
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
chemical1der said:
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
Click to expand...
Click to collapse
is there any tutorials on how to use it and what commands i need to install apps?
beezy69 said:
is there any tutorials on how to use it and what commands i need to install apps?
Click to expand...
Click to collapse
once you've installed adb on your computer type "adb" at your terminal prompt and you should list of commands there.
here's the link to Android Developer's ADB website (this also lists commands):
http://developer.android.com/guide/developing/tools/adb.html
files and installation directions can be found here:
http://developer.android.com/sdk/index.html
Good luck!
Ok so me being my dumb self forgot to install the adb drivers for the nook....... im dumb haha, but i cant get them to install, every time i uninstall the mass storage driver so i can install the proper driver it automatically re-installs it....... HELPPPPPPP
Is there any way to download this to the SD and install it from there? I've upgraded to a version of froyo, which doesn't have the market, and my command line won't work after swapping nooks.
I can't seem to get mine to work with either adbwireless or via usb.
Using USB I get this:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
But it doesn't show a serial number like all the HowTo's says it should. What am I missing?
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.
This thing really needs to be pinned somewhere, preferably with IOMonster's first post. There's so many of us starting on this from scratch not able to get adb to see the device. har02's crosspost of hacku's post is what finally got it to work for me. there's a ton of junk out there that just doesn't make sense, and the installing the second driver on the "android interface" is a step that is completely missing from just about every post on this topic.
Aside from that, this forum is what got me buying a nook and happily learning all sorts of cool new things!
THANK you so much har02052, this marks the end of a 6 hour nook-fixing marathong....ahhhhh