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.

Phone wont connect

Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.

InV15iblefrog said:
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
Click to expand...
Click to collapse
your phone must be in FASTBOOT bootloader mode..not in the HOME of your ROM..
if you don't wan to turn off your phone first and pressing volume down + power to go to bootloader..then you can using a adb command on cmd while your phone is still in the HOME of your ROM.. type "adb reboot bootloader" then select "FASTBOOT" now you can type "fastboot oem get_identifier_token"
don't forget to disabled Fast boot mode and enable USB Debuging first from the system settings and just connect your phone to pc as charge mode..
hope this help..

Sorry mate. Tried that before your post though.
However the person for whom I was doing this no longer needs it doing, and plans for a newer device, so I no longer have this device available. Thus, i thanked you, since it was a cue for me to mention that.
Cheers.

This model of HTC is died

[Q] Pull data with a smashed screen

Just after updating to lollipop I completly smashed my screen. It doesn't show any usefull information and touch is not working.
Since I'm not in the mood to buy a new screen because I already bought a Note 4, I wanted to pull the data from the phone. It's pin protected but fastboot is still working, adb however is not.
After reading up a bit I found that going into cwm recovery I would still be able to acces adb.
So I with fastboot I booted cwm recovery (fastboot boot recovery.img) only to find that adb still won't find my devices.
Is there any way left to pull the data from my phone? I also have acces to a external keyboard/mouse with a otg cable but that won't seem to work either.

Boot into recovery and with your device plugged into your pc go to device manager. Do you see your device there?
Sent from my Nexus 9 using XDA Free mobile app

In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.

Wiisper said:
In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.
Click to expand...
Click to collapse
Google 15 second adb install xda. It has drivers as well as sets up adb and fastboot on your pc which you'll need if you can get your device detected
Edit, also download the twrp image from here and boot into it fastboot boot twrp.img (use the full name of the twrp image file) cwm sucks. http://techerrata.com/browse/twrp2/hammerhead
Sent from my Nexus 9 using XDA Free mobile app

I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.

Wiisper said:
I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.
Click to expand...
Click to collapse
Np, glad it seems to be working
Sent from my Nexus 9 using XDA Free mobile app

Okay got all the files from the phone!
Thanks for helping.

Can i do this without rooting , how ?

I am new and noob , i hope i am asking at the right place
So i have a galaxy note 4 verizon model , i am using a different carrier and the problem is that i cant add apn's because verizon is restricting that, i searched the web for a solution but only found solutions involving rooting which i will not risk at any cost
Until i found this post of someone explaining how to overcome this using a flashable mod and recovey mode ,
Is this possible without rooting for some claimed so ? I have uploaded his post can someone pleeeeease explain this for me and direct me to what to do
Sent from my SM-N910V using XDA Free mobile app

maqqam said:
I am new and noob , i hope i am asking at the right place
So i have a galaxy note 4 verizon model , i am using a different carrier and the problem is that i cant add apn's because verizon is restricting that, i searched the web for a solution but only found solutions involving rooting which i will not risk at any cost
Until i found this post of someone explaining how to overcome this using a flashable mod and recovey mode ,
Is this possible without rooting for some claimed so ? I have uploaded his post can someone pleeeeease explain this for me and direct me to what to do
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
The method 1 in the image says you to use a custom recovery. To use a custom recovery also your phone must be rooted and bootloader unlocked. So, you can't do this without rooting your phone.

Yeah, 4shreyas is right.
Sent from my SPH-L300 using XDA Free mobile app

maqqam said:
I am new and noob , i hope i am asking at the right place
So i have a galaxy note 4 verizon model , i am using a different carrier and the problem is that i cant add apn's because verizon is restricting that, i searched the web for a solution but only found solutions involving rooting which i will not risk at any cost
Until i found this post of someone explaining how to overcome this using a flashable mod and recovey mode ,
Is this possible without rooting for some claimed so ? I have uploaded his post can someone pleeeeease explain this for me and direct me to what to do
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Actually, your shud have asked it here: http://forum.xda-developers.com/note-4-verizon
Okay, install Minimal ADB and Fastboot in PC. (Google it)
Then install your phone drivers and ADB drivers (Google it).
Download this: http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.5.0-trltevzw.img
Rename it to recovery.img and place in C:/ drive
Enable USB debugging in phone and connect to PC. (Google it)
Then open 'Minimal ADB and Fastboot' shortcut in Desktop as Admin and type the following:
Code:
adb reboot bootloader
fastboot boot recovery C:\recovery.img
Now install the mod zip file which you saw from there.
That's all. Your phone won't be rooted.

GokulNC said:
Actually, your shud have asked it here: http://forum.xda-developers.com/note-4-verizon
Okay,........
That's all. Your phone won't be rooted.
Click to expand...
Click to collapse
I think this method also changes the system status to modified which breaks the warranty. If it doesn't then this method can be used.

4shreyas said:
I think this method also changes the system status to modified which breaks the warranty. If it doesn't then this method can be used.
Click to expand...
Click to collapse
Booting doesn't break the warranty. I'm damn sure

GokulNC said:
Booting doesn't break the warranty. I'm damn sure
Click to expand...
Click to collapse
Thanks so much , i am on it
Sent from my SM-N910V using XDA Free mobile app

I think i got everything ready , before i proceed will this erase everything ?
Sent from my SM-N910V using XDA Free mobile app

GokulNC said:
Actually, your shud have asked it here: http://forum.xda-developers.com/note-4-verizon
Okay, install Minimal ADB and Fastboot in PC. (Google it)
Then install your phone drivers and ADB drivers (Google it).
Download this: http://www.techerrata.com/file/twrp2/trltevzw/openrecovery-twrp-2.8.5.0-trltevzw.img
Rename it to recovery.img and place in C:/ drive
Enable USB debugging in phone and connect to PC. (Google it)
Then open 'Minimal ADB and Fastboot' shortcut in Desktop as Admin and type the following:
Code:
adb reboot bootloader
fastboot boot recovery C:\recovery.img
Now install the mod zip file which you saw from there.
That's all. Your phone won't be rooted.
Click to expand...
Click to collapse
So i have done all these steps , after the first command the phone reboots and start with a green droid screen that shows *downloading dont turn off*
When i type the second command the adb command screen shows *waiting for phone * but nothing happens ??
Sent from my SM-N910V using XDA Free mobile app

maqqam said:
So i have done all these steps , after the first command the phone reboots and start with a green droid screen that shows *downloading dont turn off*
When i type the second command the adb command screen shows *waiting for phone * but nothing happens ??
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
After rebooting into bootloader, check if your phone is connected to fastboot mode properly by:
Code:
fastboot devices
If an unique device number is listed, then it means your phone is connected properly.
You can proceed.
You can also try manually going into fastboot by holding some button combination like power + volume up+ volume down while phone is switched off. (This is device specific, so better ask in your phone's forum if you can't figure out)
After going into fastboot mode, do the recovery booting as I gave command before

[SOLVED] confused noob - adb/fastboot : install or just run?

Hi
Noob alert here.
I'm trying to flash a custom recovery (twrp) on a very old phone which has its bootloader unlocked. (the phone currently runs android 6.0, yes, that old...)
I read on the forums here that I need to use ADB from windows (Win10 here) in order to flash twrp onto the phone (to replace the stock recovery).
I DLed the neccessary files (platform tools), but it's just a bunch of files with nothing to actually install AFAICT...
MAny tutorials mention that I should just launch a CLI from within the folder containing the tools and then run ADB to flash twrp.
However, I get stuck at < waiting for any device > which, according to other tutorials, isa sign that drivers are not installed for my device in windows.
Some tutorial mention that I should INSTALL ADB (rather than just run it from CLI), so I'm starting to wonder what I am missing here.
- Should I INSTALL ADB? how?
- Should I install drivers for my device? It seems like my device is properly detected by Win10 and I couldn't find any driver to install anywhere.
I'm confused about what's going on.
Could you please help me out here?
Thanks a lot for your advice.
Best,
-a-

OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess?
Running windows update found a driver for
Google Android Bootloader Interface
So I guess now it should work
I'll post the results
Thanks a lot
-a-

nope...
No luck
ADB still cannot see my device when in bootloader mode

asheenlevrai said:
nope...
No luck
ADB still cannot see my device when in bootloader mode
Click to expand...
Click to collapse
Actually it works!
Even though
adb devices
would not list anything when the phone wwas in bootloader mode, I was able to flash twrp
problem solved!

In the future some commands in Bootloader Mode require fastboot oppose to ADB.