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!
Related
I was following the guide over at cyanogen's wiki to install the sdk and I haven't been able to get it working.
I added the tools directory to the environmental variable, ran the setup, tried to install the usb driver, and turned on usb debugging but it wont install. Windows gives me a failed to install driver notice and when I type adb devices in the console it says "List of devices attached".
I've uninstalled the drivers with USBDeview and plugged my phone back in several times, but it still wont work.
Using Win7 and a Nexus One, anyone know what I'm doing wrong?
Nevermind, got it working. Went too far into the usb_drivers directory when I was trying to install it..
Hello all,
I have installed android sdk, google usb drivers etc. I am using windows Xp. My phone is upto date as per the Sony PC companion installed in windows. When I try to connect my phone in usb debugging mode to adb, its not showing up. when I give adb devices it doesn't list any devices.
when I give adb shell, it says device not found. I tried all methods like kill-server, start-server and killing adb.exe etc. after I went thru the existing threads in this forum. Nothing works !!
And the interesting thing that I could not figure out is about the device manager. After I try all methods it says drivers not installed. I try to install google usb drivers as well by browsing the folder in my android sdk . It was displaying like 'nothing found to install'
Any ideas please ??
One update.
Google usb drivers were not being installed correctly. When I update driver and browse to the Android SDK folder where the Google USB drivers present (My case .... Android SDK-> Extras-> Google -> usb_driver) it says 'nothing to update'
Then I edited android_winusb.inf file there and included my device ID (as showing up in Device manager). And it installed the drivers.
Then I opened adb again. And gave 'adb devices' and finally I could see my device listed !!!!
But still one major problem exists. That the device is getting disconnected continuously from adb and each time I would have to restart the adb and this makes it useless....
Not able to figure out why ...
Try using this: adbdriver . c o m
If it does not work try flashtool's drivers
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
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.
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Chrisp3 said:
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
Click to expand...
Click to collapse
On Windows, make sure your phone is connected and you can run ADB commands. Enter Device Manager in Windows and verify that there is a listing for Android ADB Interface.
I just connected to a new computer and I could do ADB but not Fastboot. Discovered that instead of ADB Interface in Device Manager, it just said "Pixel 3a."
If this is the same for you, go install the Android USB drivers.
KaptinBoxxi said:
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Click to expand...
Click to collapse
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Chrisp3 said:
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Click to expand...
Click to collapse
The issue with the fastboot method (realized this when I upgraded to Win11 Beta) is the ADB Quick Installs are missing some stuff, and cause certain flash methods to not work via flash-all.bat's from Google or Graphene or others.
When I install ADB System Wide, I also download the platform-tools from Google, and over-write everything in the c:\adb folder, also adding the stuff missing. Idk why the adb quick installers don't just download from google directly, would save a lot of headaches