Related
Hi.
I don't know what happened, but I cant access my phone via adb anymore. I've used adb for months with no problem so far.
The Device is shown in windows xp as "Android Composite ADB Device". I uninstalled an reinstalled the drivers. But ADB and other apps like ddms don't recognize the device anymore.
I'm not sure, but perhaps the problem exists since I installed the modem-driver to use USB-tethering.
USB-Debugging is enabled too...
Does anyone have an idea?
I'm using cyan 4.3.2.1.
Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
If none of that works, try to re-root using this;
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_Versions
Make sure to backup and stuff, etc. etc.
Hope I helped!
Exodeity said:
Try unplugging your phone, turning it off, on, let it load up, connect it to your comp, wait a good minute or two for it too load up, double check USB debugging, etc. etc.
If it still doesn't work, boot into recovery, connect it, and try adb shell there. ( assuming you have cyan's recovery, or that other custom one, Idr the name xD )
Click to expand...
Click to collapse
thx a lot for the quick answer, but I tried all of this. In the Recovery (Amon Ras' I recognized the first time, that adb doesn't work)
I can't believe, that I have to re-root... Recovery and SU are still working.
Any other experience with the problem?
p.s.: I unchecked the USB-Tethering and already uninstalled the modem-driver without success...
That's weird, you sure your in the right area on your cmd prompt?
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.
Exodeity said:
That's weird, you sure your in the right area on your cmd prompt? ( Assuming your on windows, the Terminal in linux, I'm sure you know xP )
x:\xx\android\tools adb shell
You could also try adb remount and see what that gives you.
I'm just learning the real ADB commands, forgive me, I'm no master
Edit: Make sure to unplug your phone before you uninstall the USB/ADB drivers, and make sure you uninstall *everything* that has android or HTC on it from the device manager.
Click to expand...
Click to collapse
you gave the right advice...
it's weird. I set adb as variable in windows environment and it worked till today.
Now I started a command prompt in another folder with adb in it and started adb... and it works. weird. I already uninstalled the drivers with usbdeview, restarted etc. a several times and it didn't work. Just use another adb-command finally worked...
thx
Code:
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT852KV04159 device
Yeah, that happens to me sometimes, where it says the device didn't ACK, or something, but I just unplug it, plug it back it in, and wait a good minute it works flawlessly.
I guess our G1's just get moody sometimes, I know I would if someone changed my innerds and outterds on a regular basis xD
Download This file and extract.
hit Windows Key + r
Type in devmgmt.msc
right click on nexus one
click update
update from location on computer.
select that folder.
---------------Notes-------------
Be sure to enable debugging on your phone via Settings>Applications>Devlopment>USB debugging.
Confirmed working on:
Win 7 Ultimate x64/x86
Win 7 Home Edition x86?
Win Vista
XP Home x86
XP Pro x64/x86
O.S
What O.S you had this working on?
@th3fallen
143!!
I got it working on win7 Ultimate version
This works for Windows 7 Home Premium Edition as well.
In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android.rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny
I was able to access it by using dream, magic and adb testing device didnt need any specific driver.
I did this to get it working on win 7 ultimate x64
NexVision said:
I was able to access it by using dream, magic and adb testing device didnt need any specific driver.
Click to expand...
Click to collapse
You need the latest refresh of the drivers (and tools for updated fastboot, etc.) from the SDK. If you go to a Windows command prompt and run Android, assuming the tools directory is in your path, you can select the update for both. It will fail in updating tools, since you are using an app in it, but don't close the app, just reapply at that point and it will work on the second go. Then when you install the N1, you will have the drivers you need to install as before.
Not meaning to argue with you but what I was saying is I have had no issues doing anything via adb with it as a magic I have done fastboot as well hey maybe its just working for me.
kfk2 said:
In order to get ADB working on Linux (Ubuntu 9.04) I had to edit /etc/udev/rules.d/51-android-rules (I may have created this file for the G1) and add:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
What I was seeing was the device would sort of show up when I ran adb devices, but it would list ????????? as the ID and no permissions.
~Kenny
Click to expand...
Click to collapse
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.
Swervo said:
Hmm...I have that already in my /etc/udev/rules.d/51-android.rules (mine has .rules, not -rules...I'm assuming that's a typo in your post?) and I'm still coming up with ?????????? as the device and no permissions, all attempts to do anything with adb result in it telling me I don't have permission to do these things.
Click to expand...
Click to collapse
Yah that was a typo.. The no permissions error appears to me that adb doesn't have access to the /dev/ devices used. I'm not at home so I cannot lookup what device is created and used in /dev/ for you to check the permissions. I know I killed the adb server and restarted it a few times while trying to get mine to work, along with updating to the latest sdk. So you may want to try those things, you could also try running adb as root and seeing if that fixes it (if so, then it's a simple permission error with udev not creating it with correct permissions).
Alrighty, I think I got it. I'm no udev expert (in fact, I'm rather useless at it), but this worked for me.
1) Make sure USB debugging is turned on on the phone.
2) Plug the phone into the USB port on the machine.
3) Make sure /etc/udev/51-android.rules has
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click to expand...
Click to collapse
in it.
4) run
adb kill-server
Click to expand...
Click to collapse
5) As root, run
service udev restart
Click to expand...
Click to collapse
6) run
adb start-server
Click to expand...
Click to collapse
Worked for me to get the device recognized.
Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!
Confirmed on Vista
I can confirm that the instructions in the OP work on Vista. Thanks a lot, th3fallen.
Alleviate said:
Hey guys, I have the Android 1.5 SDK/ADB installed on my computer.. so I don't know what will happen when I mount my N1 (haven't tried yet). I want to be able to mount my N1 normally without ADB or anything, 'cause I'm not going to root it for a while. Thanks!
Click to expand...
Click to collapse
Nothing will happen, ADB doesn't start interacting with your phone without you explicitly telling it to. Also, if you don't have debugging turned on on your phone, then it won't even if you do explicitly tell it to. Feel free to mount the drive on it.
ADB and Root
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3
Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows devices
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?
ccunningham83 said:
Okay, so I navigated to the "1.1-nexusone-superboot" folder in the command prompt and tried
Code:
adb-windows remount
and my device showed up. Now I want to move those files to where I originally had my adb files in C:\android-sdk-windows\tools so that all I have to type is
Code:
adb devices
to have my phone listed. I tried replacing the files in my \tools folder and renaming them to what they were named before, but that didn't work. Could somebody please help me get this set up properly?
Click to expand...
Click to collapse
in your command prompt you have to be in the c:\android-sdk-windows\tools\ directory for it to work
ccunningham83 said:
Maybe I'm doing something wrong, but I can't get ADB to recognize my phone. ADB is all set up correctly, I have it updated (I believe) to the most recent version. I installed the updated USB driver and I see the "Android Phone" in my device manager. I have USB Debugging checked off in my phone settings. ADB worked fine for my G1, but it doesn't recognize my Nexus One.
I shouldn't have to root the phone to have ADB working should I? Can anybody think of something I overlooked? I am running Windows XP Professional SP3
Click to expand...
Click to collapse
I was having the same problem yesterday. But i'm on Vista. Nothing seemed to work, but ADB was working fine on my Mytouch. At any rate, I ended up going to download the most recent SDK and trying adb again from a command prompt @ the tools location of the newest SDK, and then everything worked. I don't know if that was something I should have done in the first place and I just didn't know it (duh), but that's what worked for me.
for the past 18 months I have been able to access my G1 via USB. I could mount it easily and ADB was set up correctly. for some reason this week, it stopped working. now when I plus it in, I get the "USB Not Recognized" error in XP, and my device no longer shows up as an adroid phoen in Device Mgr. It now says unknown device.
I have tried updating the driver with no luck.
Any ideas would be great,
Thanks
Something similar happened to me. After trying to mess around with Live Wallpapers and DroidExplorer, my phone doesn't show up. I get the "Error: Device not found".
I have the latest USB driver, but yet device manager keeps saying that it's up to date when I try to reinstall (however under Driver Details, Vista says the location of the drivers are on System32 and they're Microsoft drivers....)
Edit: after searching Google for answers, I stumbled on a Google Group and found that someone fixed their issue (similar to mine) by installing HTC Sync. I did, and voila! ADB works again.
http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
OUTSTANDING!! That did it. Thanks a bunch, and thanks for the link!
fixed for real now
So the above didn't do it for me, here's what I did:
download and extract USBDeview
Open it up and remove the 3 or 4 entries that say "android phone"
Unlplug (if its plugged into USB) your phone and replug it in, the "found new hardware" window should pop up and be sure to install the drivers that came with the SDK.
That took care of my USB mounting situation, but I still couldn't get adb or fastboot to see my device. Turns out I had adb.exe and fastboot.exe in my WINDOWS/System32 folder as well as in the SDK/tools folder (prolly from when I updated the SDK). Having them in 2 spots seemed to cause problems so I removed them from the SDK/Tools folder. Alternatively I could have removed the other set, but I didn't want to go to my SDK folder every time to use them, this way I can access ADB from any folder on my computer.
This is all from memory so if something's not clear, lemme know. All I know is ADB and Fastboot are working now.
trying to root 2.1 sprint hero, had the patched .6 version but redownloaded the .5 version on my phone, now says 2.27.651.5! Good right? Then I'm trying the regaw method for rooting. Downloaded the sdk, downloaded HTC Sync 2.0.33, downloaded hero-root. Renamed them to C:\android-sdk-windows\tools, went to the command prompt and typed it in. Then I type in adb devices and I get an error: adb not recognized as an internal or external command, operable program or batch file. I've checked debugging, and still get same error. Deleted files and redownloaded everything again and STILL get same error. Any help would be much appreciated
make sure you cd to that directory, or you can click-n-drag adb.exe (adb-windows.exe in some cases) into your CMD promt and type your command after... Little work around for odd computer setups
EDIT - you could also try to append the ".exe" at the end, i.e. >adb.exe devices
Thanks, I gave it a try! Still nothing,
Did you run the setup or did you just download, extract, and then run straight to CMD? try running the setup, don't download anything if you don't want to, and then try again.
I must be an idiot, the folder size is 54.2 mb. I'm at a loss. I will continue trying!!!!
Ok, total noob here! I've been at this for a while now and still can not get adb devices to recognize my phone. Device manager says everything working properly, drivers installed properly. I have searched and searched for an answer and still I can"t find one. Is there something I am doing wrong or have I not set up. All I want to do is root my phone, any answers would be a godsend.
I can't get the adb devices to recognize the device and tried everything.can someone please walk me through this so I can root?
This?
http://forum.xda-developers.com/showthread.php?t=613217
And this?
http://forum.xda-developers.com/showthread.php?t=636795
Is not enough?
tried both of those step by step to no avail. im running windows xp 64. in the device manager under android phone it says "android composite adb Interface" when i plug my phone in. installed the drivers and uninstalled the 50 times still when i open up cmd i get nothing listed when i type in adb devices. anything im missing? im in debugging mode and ive installed the drivers many times, im done it with sdk setup running and with it not running. cant get this crap to work
Some ADB help
flabinall said:
tried both of those step by step to no avail. im running windows xp 64. in the device manager under android phone it says "android composite adb Interface" when i plug my phone in. installed the drivers and uninstalled the 50 times still when i open up cmd i get nothing listed when i type in adb devices. anything im missing? im in debugging mode and ive installed the drivers many times, im done it with sdk setup running and with it not running. cant get this crap to work
Click to expand...
Click to collapse
Check the path in your CMD, the androidsdk needs to be in that path to have adb access. Unless you changed your path values, but it should go something like this(users/nameofuser/documents and settings<). If your path is like that, then your SDK folder needs to be in the folder @ the end of that path or whatever path you have set in your CMD. Also did you run the android.exe and update your SDK. Get back to me and let me know exactly where your @.