hi all. for some reason, my adb is glitching.
nothing is hooked up, but it says
"list of devices attached 0123456789abcdef offline"
sooo, i cannot connect anything. i have files from where i was running virtualbox, could that be causing the problems?
Does this persist even after a reboot? I had some funky problems with my drivers... What OS is your desktop on?
Related
ive used adb before on a friends computer and on my computer (a macbook pro) in the past and know the works but recently on my computer when i connect any device including my skyrocket with usb debugging on and i try to run adb using the command ./adb shell it starts to run, then says error- no device recognized. any ideas?
Check device USB driver
I have a new laptop running Windows 8.1. So I had to reinstall adb and fastboot on it. I used the quick installer described in:
http://forum.xda-developers.com/showthread.php?t=2588979
It installed in seconds.
I now need to issue some adb commands to my rooted nexus 5 running stock 4.4.4. So I
1. opened a command prompt in Windows
2. Connected the nexus 5 to the laptop with its usb cable.
The nexus appeared in Windows as a drive named "internal storage".
3. Typed adb devices and got as a response
"list of devices attached"
But nothing else shown under it.
It's been a while since I used adb. What am I doing wrong?
My nexus 5 is rooted.
Usb debugging is selected.
Should I change something else on it?
Appreciate any help.
Search and download minimal adb for windows on google ..run the program and put whatever file it is your trying to push in the same folder as adb in program files tab ..work like a charmed sideloading ota ..I'm pure stock
I have used the same adb installer in windows 7 and it works.
Are you opening cmd as an administrator? That is the only miss I can find.
It was my fault. When I installed the correct driver, everything went well.
Sorry to have bothered you guys and thanks for helping.
hey,
a couple of months ago I dropped my phone, damaging the touchscreen (unresponsive & dark since then). However, the rest of the device seems to work. A couple of weeks ago, I plugged the device into my PC and saved my stuff from the SD card. In the meantime, I updated my PC from win7 (x64) to windows 10 and now the device does not show up any more in the windows explorer.
I tried to connect it to my girlfriends PC (win7 x64) and here, the device shows up but is "empty" (no files & folders visible).
I downloaded Android SDK on both machines and tried to run ADB commands like "adb devices", but it won't show the device on either of the two machines.
Next, I tried to do it on my macbook. After downloading Java and Android SDK, I navigated to the folder in the terminal and tried to run "adb devices", but all I get is the response "-bash: adb: command not found"
the phone is connected to the machines and USB debugging on the phone should be enabled (otherwise I would not have been able to save my stuff from the SD card previously, right?)
what am I doing wrong?
thanks for any advice
I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.