I'm comming from the Samsung vibrant so im fairly new to nexus community. However I did find a couple tut. that were very good, I followed everything exactly as the person in the video. By the way the tutorial i used was from the Unlockr. But anyways i followed everything i set up adb my device appeared in the command prompt. However the next step once your phone is recognized when setting up adb is to power off and get into "fastboot". I did that, plugged the usb in and opened another command prompt. When i type in "fastboot oem unlock" it just hangs on the "waiting for device" part forever. Can someone please help me out thankx
You should really use a more descriptive title. I had no idea what this was about until the last sentence.
If you closed your terminal, than adb probably closed as well. Open up the cmd window while the phone is in fastboot and type
adb devices
Click to expand...
Click to collapse
That should start adb back up and let you know if the phone is detected in one command. It should then be ready for
fastboot OEM unlock
Click to expand...
Click to collapse
Sent from my Nexus S 4G "Lore"
Related
I trying to unlock my XOOM WIFI from COSTCO, when I ran the command
adb reboot bootloader
The XOOM reboots show the message STARTING FaSTboot protocol support and stuck in there, I have to VOL UP & Power to reset it.
What I am doing wrong.?
I do not want to do the ONE CLICK to avoid wiping the machine completely.
Do I need to wipe it the first time?
you need to have fastboot in your machine, then you can run:
fastboot oem unlock
it will ask you to use volume up/down keys to confirm "twice" the terms of service and will unlock it for you.
please not that unlocking it will void your warranty right away, so unless you are a developer or have a very good reason to do so, I would not recommend it.
You are doing it right.
adb reboot bootloader
is supposed to bring you to "Starting Fastboot protoco"l screen. Just continue and enter the commands as the instructions entail. If this is the first time you are rooting the device though you will end up wiping everything fyi.
ubuntu and fastboot....waiting for device
I am running Ubuntu 10.10. When I do adb reboot bootloader....when I run any fastboot command it says <Waiting for Device>…do I need to install USB drivers and how would I do that on Ubuntu.
Any help would be greatly appreciated...
Type in adb devices.
Does it list your device there?
Most likely it's a driver issue when it says "waiting for device."
I know nothing about ubuntu though so i wont be any help getting those drivers installed.
Yes it does before I get into the bootloader. After I get into the bootloader I get nothing.
Sent from my PC36100 using XDA Premium App
adb not reconized
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx
wmchristian said:
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx
Click to expand...
Click to collapse
Make sure you are running the commands from the directory on your computer that the adb file is in. For example, make sure you do a CD "\Program Files\Android\android-sdk\tools" if that is where adb and all the necessary files are.
thx for reply
Thought I did ill try again this weekend to over clock my xoom never was good at dos.
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Did you follow the instructions? I've also done the HTC unlock method and it's flawless. I revolutionary'd after that but that's besides the point.
Not trying to sound like a douche, but you definately missed something. Maybe you didn't enable USB Debugging.
just do the s-off/rooted thing by this forum :
http://forum.xda-developers.com/showthread.php?t=1192300
and you will succed in 1 time oh and dont forget htc sync need to be on at phone with usb debugging
Yes, I've followed the instructions
I had a similar problem. I simply rebooted the phone (while it said "waiting for device") and all went well after that.
kaustic187 said:
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Click to expand...
Click to collapse
first Enable USB debugging on phone . Boot your phone into bootloader. Connect your phone to pc via usb cable. Phone should read FASTBOOT VIA USB.
Make sure that HTC sync is off . ( Go to task manager, if you see the HTC sync is running, kill it)
Also remove anything else that may attempt to sync when you connect device.
Eg doubletwist, isyncr etc.
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!!!
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!
You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb