it took me a couple days to figure it out, but finally i got my macbook to communicate successfully with my oneplus one via fastboot! adb worked fine, and even after "adb reboot bootloader" and "fastboot devices" it would list my device. however, as soon as i tried another command from fastboot, like "fastboot boot recovery.img" it would get stuck on the fastboot screen, while in terminal it would only show "<waiting for device>" indefinitely until it timed out on an error.
i haven't found a solution to this yet, but i DID find a work-around. none of the advice on other forums worked, like: unplug all other devices, try USB 2.0, change USB ports, etc. but apparently, the latest version of fastboot isn't compatible with OSX (or at least, OSX 10.8+ mountain lion or mavericks, i tried both). so just unzip and copy this to your android directory, then use ./fastboot-mac to run it.
hopefully if anyone's having similar problems with OSX and fastboot, this saves you some time and frustration.
Related
So i just got my first android device about 4 hours ago. Been reading a lot and got the sdk all setup. ADB is working fine i can see the device by typing "adb devices". I've added Fastboot to the .bash_profile and "fastboot --help" shows the help file so its working but i'm trying to flash a recovery.img and after i put in "fastboot flash recovery recovery.img" i just get "<waiting for device>
Its a Dell Streak and i know the id is -i 0x413c I've been searching google like a mad man and every instance i find is either for ubuntu or XP and solved by updating the drivers yet there is no need for the drivers on Mac.
Any help?
figured it out.. i had so many tabs open and so much going on i overlooked the simplest thing!
the device wasn't in bootloader mode! haha (power on device while holding the camera button to get into fast boot...) i feel like a fool... oh well, we all have our days right?
waiting for device
Hi fone_fanatic, I got similar problem. I've been trying to search for solution but I just found your post. I hope you can help me out.
I was trying to install recovery to my LG P350, got errors and when it reboots it self, it just says:
fastboot mode started
udc_start()
and when I plugged it in to my pc it says:
fastboot mode started
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
and so on and so forth...
I have tried downloading sdk and all drivers needed for my lg phone.
Tried using cmd promt and typed in "cd (directory where skd located)"
Then typed in "fastboot erase recovery" It says waiting for device. Tried "fastboot devices" but no list for devices.
I am not familliar with bootloader mode. I really hope you can give me some hints or fix for my problem. Thanks in advance..
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...)
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...!
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.
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.
bob3rt said:
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
Click to expand...
Click to collapse
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
dzidexx said:
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
Click to expand...
Click to collapse
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.
I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?
Thank you for your time so far helping me.
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
I had the same issue and lasted untill I tried different usb cable
Shield K1 connectivity is very sensible to cable quality
try others
dzidexx said:
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
Click to expand...
Click to collapse
Hey Sorry again for a late response! However the good news is that I got it working!
What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
0mad said:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
Click to expand...
Click to collapse
Worked like a charm! Thanks.