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.

Cant flash RUU

Hi Guys, since monday im the owner of a htc one s. I unlocked the booloader and flashed the team win recovery. Then I flashed the TrickDroid Custom Rom, because I thought i would have a nice battery life like it was told in the title. But the fact is that my One S looses extremly much battery in standby-mode and i dont know why. So i would flash a RUU. But I couldnt do this. Like in some Threads i flashed the Stock-Recovery and the I relocked the bootloader. Now I tried to start my phone to flash the RUU but i coulndt, the One S wasnt booting. Then I tried to flash the Recovery over the Bootloader and ive got the failure-code 171 (ruu cant find a fastboot device -> usb). But i realy want to go back to stock. Can you help me?
iZodiac

never done an ruu, so can't help much there other than what is already posted
assuming you are up on your adb/fastboot stuff, try reinstalling the htc drivers. then open command window, cd to fastboot.exe folder, usually in something like tools or platform-tools and at command prompt type fastboot devices and see if phone is recognized.

And thats the Point, if I install Android SDK my CMD Console says me, that I cant open this and then my cmd isnt available anymore on my pc. i tried this 2 times and every time I needed to restore my pc to a earlier time..

not sure
can you reinstall htc sync or try new usb or different pc port
you need the fastboot.exe and adb.exe and 2 windll files in your tools folder. If they are missing--might be issue
did you check and see on phone if usb debugging is checked under Settings/Development and fastboot is unchecked under Settings/Power
oh, if you haven't and get to a point you can, get a nandroid. i know you can't bu sdcard to pc--but, first chance you get, do it

Thanks first for your Support, 2nd
Can you give me a link of the (if available) latest RUU-Nandroid? Would be great if you'll find something

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

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?

I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up

Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.

I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen

carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.

a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here

carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.

your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here

carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers

Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated

my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?

Sony Xperia 5 II XQ-AS62 root

Happy new year! I was hoping to bring in the new year with root, but strangely with this version when ever I boot into "bootloader" from the recovery menu, the device screen is blank, and adb does not detect anything.
Would someone be gracious enough to provide a step by step root for this particular US variant? I can send you a gift card if you get me running with just root!
Thank You!

It's a $100 USD Gift card btw. I would send it to you via a direct message, or I can send you some crypto if you provide me your wallet should the root prove successful (for same amount). Thank you and have a happy new year!

BurnsMotorCycle said:
It's a $100 USD Gift card btw. I would send it to you via a direct message, or I can send you some crypto if you provide me your wallet should the root prove successful (for same amount). Thank you and have a happy new year!
Click to expand...
Click to collapse
On other thread you mentioned that `fastboot devices` gives nothing. I suspect that you are missing drivers for your device so try installing drivers first. Try these: Xperia 5 II driver - Sony Developer World ?

I saw that link before, but my device was not specifically listed. I'll try it anyway and hope that it works.

I boot into the "Fastbootd" menu on the phone, and then plug the device into my machine. when I run the "fastboot device" command I get:
fastboot: usage: unknown command device
When I then try the second method of connecting to fastboot (by holding down the volume up button while at the same time plugging the device in as per the instructions here: https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-2), the phone screen is blank.
I then try running the command "fastboot device" and I just get a "waiting for any device". Thanks for taking a look and let me know what else needs to be done!
Also I tried installing the drivers, and that did not work either. I still get the error "fastboot: usage: unknown command device"

BurnsMotorCycle said:
I boot into the "Fastbootd" menu on the phone, and then plug the device into my machine. when I run the "fastboot device" command I get:
fastboot: usage: unknown command device
When I then try the second method of connecting to fastboot (by holding down the volume up button while at the same time plugging the device in as per the instructions here: https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-2), the phone screen is blank.
I then try running the command "fastboot device" and I just get a "waiting for any device". Thanks for taking a look and let me know what else needs to be done!
Also I tried installing the drivers, and that did not work either. I still get the error "fastboot: usage: unknown command device"
Click to expand...
Click to collapse
Did you follow: Install OEM USB drivers | Android Developers ?
If so Can you see if device is detected properly in Device Manager?

PPGX5II said:
Did you follow: Install OEM USB drivers | Android Developers ?
If so Can you see if device is detected properly in Device Manager?
Click to expand...
Click to collapse
I see the issue now, I've been typing "Fastboot device" instead of "fastboot devices". I managed to successfully unlock the bootloader! Now how do I go about achieving root access?
btw the screen is still blank when I plug in the phone via the "Volume Up + USB connect" way of getting access to fastboot, if that makes a difference.
Also as A WARNING for anyone following this thread, unlocking the bootloader immediately initiates a wipe of the device. I had no problem with that since this is a brand new phone that I just got and am trying to unlock. Also, I am on:
Android 10
Build #: 58.0.A.22.21

BurnsMotorCycle said:
I see the issue now, I've been typing "Fastboot device" instead of "fastboot devices". I managed to successfully unlock the bootloader! Now how do I go about achieving root access?
btw the screen is still blank when I plug in the phone via the "Volume Up + USB connect" way of getting access to fastboot, if that makes a difference.
Also as A WARNING for anyone following this thread, unlocking the bootloader immediately initiates a wipe of the device. I had no problem with that since this is a brand new phone that I just got and am trying to unlock. Also, I am on:
Android 10
Build #: 58.0.A.22.21
Click to expand...
Click to collapse
Follow this guide to get root access: [GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares | XDA Developers Forums (xda-developers.com)
As you have unlocked bootloader I believe you only need steps 25-27 to get root access.
Note: Read thread completely so that you can take backup if needed and also make sure you install all required things.

PPGX5II said:
Follow this guide to get root access: [GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares | XDA Developers Forums (xda-developers.com)
As you have unlocked bootloader I believe you only need steps 25-27 to get root access.
Note: Read thread completely so that you can take backup if needed and also make sure you install all required things.
Click to expand...
Click to collapse
I'll try this out when I get back to my house. If it works, ill send you the gift card information. Please note that the gift card that I have works only in the US, so if you want to make some other arrangement, let me know.

BurnsMotorCycle said:
I'll try this out when I get back to my house. If it works, ill send you the gift card information. Please note that the gift card that I have works only in the US, so if you want to make some other arrangement, let me know.
Click to expand...
Click to collapse
Thanks! But I just wanted to help you out. I won't be taking any gift cards in return!
If you want you can donate it to some of these developers so that they can work on supporting more!
Cheers and Happy New Year!

It Worked! I appreciate your help, but I mostly just followed the link you provided from
Miustone. Thank you to him and you both! That Thread should definitely be pinned in the
"Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe" section too!
Ill donate to Miustone, and have a happy new year!
EDIT: Darn looks like Miustone only takes paypal, which I don't have (I have crypto). Thanks again for the help everyone!

Quick Question, how do you tell which region firmware is on your phone?

Do *#*#7378423#*#* go to Service Info >> Software Info and you will get Firmware details

PPGX5II said:
Do *#*#7378423#*#* go to Service Info >> Software Info and you will get Firmware details
Click to expand...
Click to collapse
you are so kindful!

Hi to participants of this thread,
can you tell me how you backed up the DRM keys before rooting?

klausstoertebeker said:
Hi to participants of this thread,
can you tell me how you backed up the DRM keys before rooting?
Click to expand...
Click to collapse
No because you can't

I also have Sony Xperia 5 II XQ-AS62 and I've found myself in a similar situation as burnsmotorcycle but I think it's because I have TWRP installed. More specifically, I see my device when I run "adb devices", I get nothing when I run "fastboot devices", and I get TWRP when I run "adb reboot recovery".
Does anyone know how I can uninstall TWRP? Please note, my device still has the bootloader unlocked, fastboot commands are unresponsive now that TWRP is present, and ADB and Magisk seems to be the only tools available to me right now.