Im having some trouble with ADB / Fastboot commands. No matter if i try "fastboot devices" or "adb devices" they both show nothing / no device. I've tried the commands to the TWRP recovery, a booted os and the bootloader in fastboot mode. Nothing seems to be working. Im using the well known adb/fastboot 15 sec installer from here. I've tried two win10 computers and now a win7 computer although all 64 bit, which have not been a problem before.
In the bootloader on the phone with the cable plugged in, the red fastboot text doesn't show "FASTBOOT USB" unless i move the cursor (like it doesnt update before i move the cursor). Im running the command prompts with administrative rights. I've also tried different cables, but im beginning to think that its the phones micro usb connector that is faulty, although MPT is working fine in windows, and transfers files without problems. Its a HTC One S im trying to do this on. All i want is to update my recovery!
Is there something very obvious im missing?
I found a solution however a wierd one. I already had debugging enabled on the phone, but thought that i should try and disable it, and then re-enable it right after. This seemed to trigger something, as my computer now started to install some drivers, that it had been missing before. After this fastboot commands and adb commands ran without any trouble.
Da9L said:
I found a solution however a wierd one. I already had debugging enabled on the phone, but thought that i should try and disable it, and then re-enable it right after. This seemed to trigger something, as my computer now started to install some drivers, that it had been missing before. After this fastboot commands and adb commands ran without any trouble.
Click to expand...
Click to collapse
I just tried that and it absolutely worked for me too. Thanks. Very bright person you are.
Related
Went back to stock for a while due to CM7 issues and I now want to try the nightlies. I installed the android sdk on my xp machine along with the revision 4 usb drivers and platform tools. I have the phone in fastboot and when I try "adb devices" I get nothing. I've tried reinstalling everything again and I get the same result.
I have no idea what is going on. On the fastboot screen at the bottom it says
USB Control Init
USB Control End
I've never seen that before...
HALP!
adb will never see the phone while in fastboot mode
use "fastboot devices" instead
Fastboot is not recognized as an internal or external command...
WTF
I never had problems in the past, I don't get what's going on. GRR
thejron said:
Fastboot is not recognized as an internal or external command...
WTF
I never had problems in the past, I don't get what's going on. GRR
Click to expand...
Click to collapse
Are you attempting to run fastboot from the correct location?
i.e if fastboot is in C:\android\tools and you're in C:\android it won't work (unless you've setup a system variable for fastboot...)
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
Hey guys, my computer won't pick up my phone at hboot anymore even though i deleted 0 files whatsoever and changed nothing, I need the computer to pick up my phone at hboot so that i can flash the boot.img files otherwise roms dont work for me, when i press fastboot, it doesnt say fastboot usb, but when i press down with the volume key it says fastboot usb but no commands work in the command prompt , it just gets stuck at waiting for device. I know it's not the cable, I tried it with my friends, any solutions?
I'm having the "< waiting for device >" hanging problem when trying to run the fastboot command from the Android SDK. I've searched around and seen many with this problem, but no single fix. I've reinstalled the SDK and drivers, made sure HTC Sync and other syncing processes are not running, and made sure USB debugging is on. "adb devices" and "adb shell" work fine. I've also tried rebooting the phone while "waiting." All to no avail.
What could be causing this? What can I do to successfully run fastboot?
This is on an HTC Sensation running SuperSensation v.1.0.5 (Android 2.3.5), connected to a Windows 7 PC.
Thanks for helping with a noobie question.
mturk
sensation lover said:
Hey guys, my computer won't pick up my phone at hboot anymore even though i deleted 0 files whatsoever and changed nothing, I need the computer to pick up my phone at hboot so that i can flash the boot.img files otherwise roms dont work for me, when i press fastboot, it doesnt say fastboot usb, but when i press down with the volume key it says fastboot usb but no commands work in the command prompt , it just gets stuck at waiting for device. I know it's not the cable, I tried it with my friends, any solutions?
Click to expand...
Click to collapse
So "adb devices" when booted, and "fastboot devices" when in bootloader returns nothing, or "waiting for device"?
You have both adb and fastboot drivers in the same location you are issuing these commands from?
Sent from my Pyramid-T
Oh......
I didn't realize that "fastboot" was to be run while in the bootloader. I think I tried that without success earlier, but am not sure - in any case, it worked this time.
Many thanks...!
I'm running into an odd issue with using fastboot. For some reason it's not detecting any devices.
I installed, and reinstalled all the drivers (and everything installs and displays correctly in Device Manager)
ADB works properly and displays my device
I have USB Debugging enabled in developer mode
I tried different USB-microusb cables (same thing)
I tried installing PDAnet --> no difference
I also tried downloading the SDK and running the platform tools from there. Once again ADB works fine, but fastboot is just <waiting for any device>
Any thoughts?
As a side note, have a SM-G930T phone. I was able to get TWRP on my phone before, and I'm trying to get it again and I can't seem to recall how I have done it. I do remember I unlocked the bootloader through a website, but I can't remember the steps. Perhaps someone can point me to the right direction. Of course, in order to unlock the bootloader I would need to get fastboot to work, so this is what I'm trying to take care of first.
I previously unlocked my bootloader, installed oxygen 11 (am on beta 4) . I want to install PA but I can't get fastboot on my machine. Shouldnt it be as simple as instilling adb and fastboot as well as the oneplus drivers? I've done everything I can think of and the majority of times ,I ended with an exclamation point in device manager and couldn't get the correct driver installed. I tried SDK etc.. more so... Android composite adb isn't showing in device manager. I might just use my laptop.
Any quick ideas on how to fix though? Thanks
There are lots of guides and links to the minimal adb/fastboot packages here on XDA. I will say it's a heck of a lot easier on Linux or even Mac, but typically the issue is that you want to have your device drivers installed first, then connect your phone (switch it between charging, file transfer, and MTP modes and let it install each of them fully to the device manager while it's plugged in), then install adb, enable debugging, plug in, run "adb devices" and trust the RSA fingerprint, and let it install that side of things to device manager as well.
I'd start by uninstalling all of the instances of the device in your system first to start over. You might even try plugging it in with no drivers installed first to see if it loads working generic drivers.
Man, I do not miss Windows.
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Make sure you have the latest Android Platform Tools installed...
https://developer.android.com/studio/releases/platform-tools
satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Try revoking all adb authorizations and then try to plug it in and run "adb devices" to regenerate an authorization maybe? Is the problem only with fastboot or is adb also broken? You are running fastboot commands in the bootloader instead of adb commands, right?
satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Any luck? I'm having the same issue. Just managed to get my phone unlocked from tmo, and for the life of me can't get windows to recognize my device in fastboot. After an uninstall of the device in device manager, and plugging it back in fastboot. It appears under other devices as simply android with a question mark icon top left, and a yellow triangle bottom right. Manually pointing to either the drivers from 15 sec minimal adb & fastboot google drivers, or selecting all devices>have disk>and pointing too the inf of the driver downloaded straight from google results in the yellow triangle going away, but the question mark still remains, and it's still listed under other>Android. So I suspect for some reason or another the drivers aren't installing properly. Usually (having to have to do this with other devices) has worked in the past. I've had win 10 mess up loads of things most notably my dl speed once. Some bug had it capped at like 24 kb/sec (shudders). Just for comparison what Windows version are you on?
Tried dl ubuntu to boot from usb and try that. Then I ran into issues dl the iso. Couldn't catch a break yesterday I guess. I'll try again after work today, and report back. Don't like the idea of having to boot linux just for fastboot. Might a vm, but I'm not sure that would work considering windows doesn't recognize the device to pass it through, but we shall see. I will say this just about over win10.
Also Idk if it matters, but I had Android studio installed before this as well. Might be time for a fresh install it's been a while.
Sent from my OnePlus8TMO using XDA Labs