Database Develop

Lost ADB Access...

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

Getting Nexus One ADB/USB Mount working (Driver)

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.

[Q][FIXED] ADB won't connect under linux

I have the android sdk installed, my phone shows up under lsusb, and mounts properly with the mass storage option. However, adb won't properly recognize my phone, reporting it to have a question mark serial number. Additionally, I can't deploy apps from eclipse. Any help?

TheEscapist said:
I have the android sdk installed, my phone shows up under lsusb, and mounts properly with the mass storage option. However, adb won't properly recognize my phone, reporting it to have a question mark serial number. Additionally, I can't deploy apps from eclipse. Any help?
Click to expand...
Click to collapse
If you are running ubuntu, you need to run sudo adb
Sent from my SAMSUNG-SGH-I897

Pirateghost said:
If you are running ubuntu, you need to run sudo adb
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
Tried that, no difference.
Sent from my SAMSUNG-SGH-I896 using XDA App

Stupid question, but do you have the USB cable plugged into the back of the desktop, direct motherboard plug? There are issues with ADB if you are using a USB plug that isn't direct, there is a voltage problem.

TheEscapist said:
Tried that, no difference.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
if you tried sudo after you tried normal, you have to kill server before you run as sudo
sudo adb kill-server
sudo adb devices

trekie86 said:
Stupid question, but do you have the USB cable plugged into the back of the desktop, direct motherboard plug? There are issues with ADB if you are using a USB plug that isn't direct, there is a voltage problem.
Click to expand...
Click to collapse
On a laptop, so there isn't much choice. Besides, I never had issues like that on my custom desktop. Plugging into front panel, my Das keyboard usb hub, and rear ports all worked.
Pirateghost said:
if you tried sudo after you tried normal, you have to kill server before you run as sudo
sudo adb kill-server
sudo adb devices
Click to expand...
Click to collapse
Ahh, makes sense, I'll try that.
Edit: It worked, thank you.

Good call Pirateghost. Totally forgot about the killserver function first. Glad to hear it works Escapist

also, have a look at this so you dont have to run as sudo
http://www.google.com/support/forum/p/android/thread?tid=08945730bbd7b22b

ADB Errors

so, stupid question time.
i've used ADB in the past and its worked great so not sure whats going on this time around.
I get the following errors when trying to start adb:
"daemon still not runningerror: cannot connect to daemon"
I have installed moto drivers for droid 3 (32bit), im on win7 32bit. I have my phone on dev mode, and charge only. I have run CMD with admin rights. and still ADB wont turn on.
I have also tried using the new one click method:
http://rootzwiki.com/showthread.php?t=3714&p=75934
anyone have some direction? I did kill adb from my running processes (all instances) and tried all over, no go, same error.
help?

Did you put the phone is PC Mode as opposed to USB Mass Storage?

its supposed to be done in Charing only mode, the issue isn't on my phone setup, it got to do with my darn computer, I can even do an adb devices command... may have to remove the sdk completely and start over.

Put in charge only, use one click method
Sent from my DROID3 using xda premium

did you change directory in cmd to the folder that adb is in?
...I had to change to the folder like this cd\program files (x86)\android\android-sdk\platform-tools

The one-click root method is bundled with adb.exe. Except for the driver and a USB cable, it contains everything needed to root.

ADB Not Working

MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR

John98Zakaria said:
MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR
Click to expand...
Click to collapse
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.

ayushag96 said:
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.
Click to expand...
Click to collapse
Thanks for the reply I can't use ADB anywere ..
The phone doesn't even appear in the PC with ADB debuging enabled not even a connected sound or anything ..
I tried Wifi Kontect on the playstore as I didnt find "ADB over Network" But ADB wont connect....
Any Other solutions ... I dont mind if i have ADB over wifi the important thing is to have any ADB connection
www .mediafire .com/convkey/fb15/db3ykaaldgkqsd66g.jpg?size_id=5
www .mediafire .com/convkey/93e0/49f47ps6s9nbeyj6g.jpg
Remove spaces so you can see the images I cant post links yet

Fixed
I have fixed my probem thanks to @sijav !
Installing
http://forum.xda-developers.com/showthread.php?t=1687590
Fixed everything ! even after un-installing the app