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...)
Related
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...!
This seems very much to be a driver problem. Everything I find says Mac needs no driver for this device though.
dab works fine. android file transfer seems the device file structure fine. only thing not working, is when the device goes into fastboot mode, "fast boot devices" returns nothing. "fastboot oem unlock" sits and 'waiting for device' and never goes any further.
What's going wrong?
Blario said:
This seems very much to be a driver problem. Everything I find says Mac needs no driver for this device though.
dab works fine. android file transfer seems the device file structure fine. only thing not working, is when the device goes into fastboot mode, "fast boot devices" returns nothing. "fastboot oem unlock" sits and 'waiting for device' and never goes any further.
What's going wrong?
Click to expand...
Click to collapse
no driver's necessary, maybe your sdk installation is an old version and needs to be updated for kitkat?
fastboot is 1 word, not 2 as you have listed
you would execute this in the terminal:
./fastboot devices
( might be ./fastboot-mac devices )
ilanzo82 said:
no driver's necessary, maybe your sdk installation is an old version and needs to be updated for kitkat?
Click to expand...
Click to collapse
Yeah… not working at all. adb can see the device. I've never seen the mac fastboot see it. Also, it's fully updated to API 19.
Zepius said:
fastboot is 1 word, not 2 as you have listed
you would execute this in the terminal:
./fastboot devices
( might be ./fastboot-mac devices )
Click to expand...
Click to collapse
autocorrect keeps changing to two words in text boxes other than terminal. It's not finding anything. Others have seen different? That'd be shocking to me. With no drivers installed?
Blario said:
Yeah… not working at all. adb can see the device. I've never seen the mac fastboot see it. Also, it's fully updated to API 19.
autocorrect keeps changing to two words in text boxes other than terminal. It's not finding anything. Others have seen different? That'd be shocking to me. With no drivers installed?
Click to expand...
Click to collapse
I've used both adb and fastboot on a Mac for my Nexus 5, Nexus 4 and Nexus 7.
No drivers needed.
If you have adb and fastboot in the same directory and you can use adb without issues then fastboot should work as long as you've rebooted into the bootloader.
If it's still not working maybe take a look at this writeup about setting up adb and fastboot on a Mac... http://forum.xda-developers.com/showthread.php?t=1917237
Good luck!
Sent from my Nexus 5 using xda app-developers app
chef_christoph said:
I've used both adb and fastboot on a Mac for my Nexus 5, Nexus 4 and Nexus 7.
No drivers needed.
If you have adb and fastboot in the same directory and you can use adb without issues then fastboot should work as long as you've rebooted into the bootloader.
If it's still not working maybe take a look at this writeup about setting up adb and fastboot on a Mac... http://forum.xda-developers.com/showthread.php?t=1917237
Good luck!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Because I'm on API 19, that means I've already updated the SDK as far as is possible. ADB works. fastboot doesn't. What nexus 5 fastboot driver actually works?
So this is a bit weird but here goes. I already knew it was damned easy to unlock the bootloaders for Nexus 5s( usually), so I figured why not give it a go. Downloaded the sdk, enabled usb debugging, opened cmd, typed adb devices and yada yada. I get to the point where I reboot the device into fastboot via the cmd, type in fastboot oem unlock andddd........nada. Literally nothing happens, it just says waiting for devices in the cmd, but changes nothing on the Nexus 5. Anyone keen on what the problem might be?
boomvausstat said:
So this is a bit weird but here goes. I already knew it was damned easy to unlock the bootloaders for Nexus 5s( usually), so I figured why not give it a go. Downloaded the sdk, enabled usb debugging, opened cmd, typed adb devices and yada yada. I get to the point where I reboot the device into fastboot via the cmd, type in fastboot oem unlock andddd........nada. Literally nothing happens, it just says waiting for devices in the cmd, but changes nothing on the Nexus 5. Anyone keen on what the problem might be?
Click to expand...
Click to collapse
If it says "waiting for devices", it means it cant see the device. When you boot into bootloader, the first command you trype should be "fastboot devices".
I would recommend ditching the SDK and uninstalling the drivers then setting your computer up the way I satet in my "Adb and fastboot. What is it?" thread, which you can get to via my signature link
rootSU said:
If it says "waiting for devices", it means it cant see the device. When you boot into bootloader, the first command you trype should be "fastboot devices".
I would recommend ditching the SDK and uninstalling the drivers then setting your computer up the way I satet in my "Adb and fastboot. What is it?" thread, which you can get to via my signature link
Click to expand...
Click to collapse
I'll try your method and see what happens
Update: It worked, thanks!!!
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.