Database Info

[Q] Stuck at the Fastboot protocol support

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.

[Q] Help

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"

[Q] Fastboot problem

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

How to backup data when screen is broken？Rooted，USB debugging is NOT open

How to backup data when screen is broken？Rooted，USB debugging is NOT open
My screen is totally broken. Display and Touch are both failed.
I want to back up my data , but the USB Debugging is not opened.
The phone is rooted already.
How to backup my data? Help needed.

help needed...

read this thread, it even tells ya how to do it via ADB / Fastboot
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273

Hi guys,
Firstly OP, i'm sorry I am using your thread for this but doesn't make sense to make a new thread for my own, any solution here would hopefully also help u right.
So, my phone gets the STATIC screen when powered on and then on screen timeout it goes to sleep.
Now when I press the POWER BUTTON to unlock, only the backlight goes on, display wont come on.
USB debugging is enabled but when I go to command prompt and type "adb devices" it shows me the device ID but says unauthorized.
Please help me get through to my phone and do a ADB PULL for some folders and files I need as backup from my Nexus 5.
If someone can post a link with some steps or write down some info here for me to follow, please please please help me.
PS: I have been trying to search for a solution for the same for the past 8-9 hrs......i'm really exhausted and you champs are my last resort, also i'm not well versed with ADB but google is my friend.

gaurav2912 said:
Hi guys,
Firstly OP, i'm sorry I am using your thread for this but doesn't make sense to make a new thread for my own, any solution here would hopefully also help u right.
So, my phone gets the STATIC screen when powered on and then on screen timeout it goes to sleep.
Now when I press the POWER BUTTON to unlock, only the backlight goes on, display wont come on.
USB debugging is enabled but when I go to command prompt and type "adb devices" it shows me the device ID but says unauthorized.
Please help me get through to my phone and do a ADB PULL for some folders and files I need as backup from my Nexus 5.
If someone can post a link with some steps or write down some info here for me to follow, please please please help me.
PS: I have been trying to search for a solution for the same for the past 8-9 hrs......i'm really exhausted and you champs are my last resort, also i'm not well versed with ADB but google is my friend.
Click to expand...
Click to collapse
Did you open the above link?
Another one: http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351

To handle the adb permissions : http://androiddevza.blogspot.be/2013/07/adb-whitelist-issue-and-android-422.html
You can always boot to a custom recovery to get access to the file system.

I cannot do fastboot commands. Please help, I've been doing this all day!

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