I've just recently flashed CM7.03 onto my nexus one.
As part of that procedure I had to install the android SDK and adb drivers to enable me to use fastboot.
Now when I plug my phone into my PC, it recognises an Android adb device, but I am unable to access mass storage. In device manager it sees a new android adb device instead of mass storage.
How to I get around this?!?! Is it a case of one or the other i.e. do I have to uninstall adb just to get mass storage back. It seems quite idiotic.
OK fixed it..
I had to go into device manager and change the driver of the android device back to USB driver instead of ADB driver.
I am amazed at how poorly documented some of this stuff is. e.g. how you have to manually add the sdk tools directory to your path. I realise its aimed at developers but really how hard is it to make these quirks clear up front, also that path issue is totally ridiculous, MS-DOS 5.0 called and its 1992 again lol. They give you a nice GUI repo system (I'm used to using yum and apt get in conventional linux) but fail to warn you that if you install the adb drivers you bork your mass storage capability. How hard would it have been to have a few lines of explanation in the GUI.
Related
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!
Hello all,
I have been following the guide posted by Nephron http://forum.xda-developers.com/showthread.php?t=532719 but am having a few problems with my computer recognising my G1 as an ADB device...
My computer's OS is Vista. I have followed the guide to the letter, have downloaded the SDK and unzipped it to C:\ root. I have checked my phone and ensured that 'USB Debugging' is checked. My computer doesn't try to install the Android 1.0 driver (as the original drivers are already installed) and my device is ready to use as a storage device - HOWEVER it is not acknowledging it is an ADB device.
I have tried using USBDeview but it won't let me uninstall the 3 already installed Android drivers. I have even tried manually uninstalling them through the taskbar USB device manager. Even when I uninstall them and re-connect my phone, it automatically installs the standard drivers and doesn't give me an option to select the SDK drivers.
Hope that makes sense to someone. How can I install these damn SDK/ADB drivers on my G1?! Thanks.
Try this...
Remove every mass storage device except your phone (Any usb memory sticks, external HDD's, other phones, etc)
Open the start menu, right click on 'Computer', click 'Manage', and you may need to click continue here.
On the next page, click on 'Device Manager' on the left hand side. In the list on the right, open up the tree for 'Universal Serial Bus Controllers'
Find 'USB Mass Storage device' in the list. Right click it, click 'Uninstall'
Click 'Action' at the top, then 'Scan for hardware changes'.
If it all goes well, you should now be asked to locate a driver, point the the Android USB driver. Good luck.
PS, this is all from memory of the issues I had, so if you get stuck, post back .
Worked a charm, thanks!
(Mods...can this be merged to the NEWBIE Q&A thread for ADB/Fastboot etc...more useful place for it than here!)
Glad I could help .
OK...
New problem...
I am using command prompt on vista, entered the following:
cd C:\android-sdk-windows-1.5_r2\tools
adb devices (shows my device listed as HT845KV02724)
adb shell (shows a # on the following line)
However....when I enter adb it returns with /sbin/sh: adb: not found .....what have I done wrong? I have checked that the SDK is in C:\ and have downloaded the SDK again just to be sure. What do I need to change???
Once you type adb shell, you're in a terminal on your phone, you can type shell commands there, you need to type exit before typing adb again.
Basically, it's working as intended .
so i had ADB (sdk 1.5 r3) set up on this laptop (in xp) it was working fine on my htc dream 32b, went to update the sdk to 1.6r1 and now neither my dream that worked before or the magic will be recognized as adb devices.
tried following the instructions in the adb thread utilizing usb deview, now i have 3 "drivers" listed per phone, usb composite, usb mass storage and adb, but mass storage and adb always show not connected (even when mass storage is enabled) on both phones, windows asks me if i want to "eject" the adb interface or the mass storage controller...
any insight would be appreciated, on a side note i have never gotten the mt3g (magic) to interface with adb but the dream has been used MANY times before and still functions on my personal laptop but this is the one at work
Make sure you uninstall the drivers from device manager, not just remove them.
the drivers install immeadeatly again after hitting uninstall in device manager when re plugging in the magic, doing that worked with the dream when i installed it the first time
Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!
Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.
WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.
the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues
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