Hey everyone,
Just got my Xoom an hour ago. Been preparing to unlock it as soon as I got it. I am running Linux Mint 10, and have installed the sdk and adb/fastboot.
However, when I type in the command to boot my Xoom into the bootloader it works and takes me into the "Starting Fastboot protocol support" screen. Then when I type the "./fastboot oem unlock" command, it just says "<waiting for device> in the Terminal. Any ideas how to proceed? I've tried taking the usb in and out, I've tried using a different usb port.
Thanks
Nerver mind. I figured it out
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..
Hello together,
first I wanna say sorry for my bad english...i'm still learning
I've got three days before the A510 from my cousin, with the note that it always hangs during the Acer logo. He said he wanted to make an update and after that it would no longer boot.
When I type "fastboot devices" in cmd, no model appears.
Drivers are installed,'ve tried different USB ports. Used as the operating system Windows 8 64bit.
USB debugging is probably not been turned on (according to statement of my cousins).
Does anyone know this problem and can anyone help me with this?
Is the first time that I have to do with an Acer device, so am really encouraging hose...
I just tried the whole on a Windows 7 64bit computer times. Now there stands the following things in cmd after typing "fastboot devices": "fastboot devices" a "?" then some space and "fastboot".
If I type "fastboot oem unlock" there are two pictures on the tablet and the message that I should confirm with Vol- and Vol+ to select ... but when I do, it says:
"SetUnlockMode: Error occured while unlock the device ..."
"Fastboot: Failed to set unlock mode"
Now I am even more confused than before ...
Thanks for the help!!!
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.
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!!!
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.