I have adb installed on a Windows XP computer, and when I do "adb devices", my NC is listed with no problem. But, when I try to an "adb shell", it just hangs at the prompt with no response. I'm stumped. Any ideas? Thanks.
I figured it out.
What did you do? How did you fix this issue? I can't get adb working for 3 weeks now. I have exactly the same symptoms. ADB over WiFi works, but I'd rather use USB.
Thanks.
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
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
When I try to run ./adb devices or ./adb shell it always says device not found. Yes USB debugging is turned on too. I'm on a mac also.
chron12 said:
When I try to run ./adb devices or ./adb shell it always says device not found. Yes USB debugging is turned on too. I'm on a mac also.
Click to expand...
Click to collapse
Mac might be your problem. Have you made sure your drivers are installed correctly?
If you just let it auto-install drivers, try finding a manual download online.
Tivo7 said:
Mac might be your problem. Have you made sure your drivers are installed correctly?
If you just let it auto-install drivers, try finding a manual download online.
Click to expand...
Click to collapse
no need to install drivers on a mac. what mode is you phone in. Try both PC Mode and Charge only...I had a few dab problems myself...so much that I restored it back to stock..which fixed all of them. I am set up on a mac and use a little batch file to show and hide hidden folders, then I dropped adb into /bin folder so I didn't have to keep putting the ./ in front of dab.
-Try killing adb in activity monitor, then retyping adb devices...if that doesn't work,
- have you tried resetting your computer too? Mine weirds out every now and again and a restart fixes dab
Good suggestions, however,you can stop the adb service with adb kill-server
Try typing just adb by itself to get a list of options
Sent from my DROID BIONIC using xda premium
Any help with my problem would be greatly appreciated!
Recently I managed to soft brick my Kindle Fire HD 7", and hoped to use the "KFHD System.img Restore Tool" to fix. I bought a factory cable and was able to put my Kindle into fastboot mode. Prior to this I had ADB installed so I could root my KFHD (which I did).
Now obviously when I rooted my KFHD, ADB recognized my device then. Unfortunately, now I have no such luck. While in fastboot I tried to use the command ---> adb shell su -c "reboot bootloader" <--- but I kept getting error messages that stated there was no recognized device.
I re-installed the AndroidSDK file to ensure there were no errors there and tested ADB with successful results. I also re-installed the Device Drivers and made sure that in my device manager under Kindle Fire it said "Android ADB composite interface" (or similar, I don't remember off of the top of my head). I went back and tested again, and ADB still does not recognize my device while in fastboot. I then left my Kindle on until it ran out of battery to test to see if ADB would recognize when out of fastboot.
After turning on my Kindle when not in fastboot, I typed in the command prompt "adb devices" and no device showed up. Also, now under my device manager "Android ADB composite interface" or whatever doesn't even show up. I have searched over and over again on many forums with no luck. Does anyone know what I am doing wrong? Or what I should try doing?
Sorry for that ^huge story^ but thanks in advance for any feedback!
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
"That's a special kind of stupid. The kind that makes me laugh."
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
bryanchapman9999 said:
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
Click to expand...
Click to collapse
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ive been using the android drivers on windows 8 without an issue. They have to be manually installed and driver signing needs to be turned off.
Sent from my KFOT using Tapatalk 2
soupmagnet said:
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
Click to expand...
Click to collapse
I see, well the program seemed to work fine without it apparently (the line of code). My Kindle is working perfectly again! Thank you for the reply.
Hello all, I think this is going to be easily answered here as I can't find the answer anywhere else.
I am trying to use ADB to pull the entire contents of /sdcard/
Ive been typing the following commands
adb root
adb shell
adb pull -p /sdcard/ C:\Users\
after typing the pull command I just end up at a '>' prompt and nothing happens.
I'm using a Win 10 machine, CMD running as admin. My phone is I9305, rooted running CM 12.1, debugging is enabled and I have even installed ADBD insecure.
I have been doing all this with the device booted.
What obvious mistake am I making?
Is your device getting detected in command prompt by typing "adb devices"?
My issue was fixed after EFS repaired and ADB starts detecting my phone