I've been trying to unlock the bootloader on my Legend using the HTCDev unlock guide, however I can't get past the initial update. It says "wait for bootloader..." before giving error 170 or 171 (USB connection) yet the cable is still connected. I have USB debugging on, and "adb devices" shows the phone connected and not offline, however "fastboot devices" lists nothing when in the fastboot screen on the bootloader. I can't see where I've gone wrong here as I have all the requirements listed by HTCDev, I have the correct ROM (3.14.161.1) and HBOOT v1.00, and I've checked again and again that I have downloaded the correct RUU.
What can I do?
Edit: Never mind, I was being stupid and didn't try other USB ports.
Related
Okay, so i'm using this guide to relock my bootloader and i've gotten to the part where I must enter in the command "fastboot oem lock." My phone just sits at "waiting for device." I read somewhere that the USB connection might not be 100% in the phone, so when I adjusted the plug, the computer unrecognized the device and I cannot do anything. The connection comes and goes as it pleases.
I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.
HosstaLaVista said:
I'm trying to relock my bootloader and unroot because I cracked my screen and wish to use my insurance to get a new DNA. My computer recognizes my phone when the phone is on, but when i boot into bootloader, the computer does the two beeps like a connection has been found but then is followed by 3 low pitched beeps like it failed. I'm S-ON. I can't do any work on my phone when in bootloader. When I try to enter the command "fastboot oem lock," it just says <waiting for device> I've installed the latest version of HTC Sync Manager so i'm sure the drivers are up to date.
Click to expand...
Click to collapse
Try a different usb port. Uninstall HTC Sync, as I have seen sync cause problems before. Also try using a different cable if you have one. I have an old T-Bolt cable that will let you charge and transfer, but will not recognize phone in bootloader.
when in bootloader make sure that you are in fastboot and it says "fastboot usb"
Hello,
I'm (finally) trying to root my Rezound, but I'm unable to get the identifier token to get the bootloader unlock code from HTC. fastboot oem get_identifier_token gets stuck at < waiting for device >. I've ensured that:
USB Debugging is on.
USB connection type is "Charge Only".
The Fastboot option is Disabled in the phone's Settings.
HTC Sync is disabled.
There's only one copy of abd.exe and fastboot.exe (in C:\Android).
I'm running Windows 8.1, but I managed to find drivers that (apparently) worked online. When I connect the phone when it's NOT in Fastboot mode, it appears as "My HTC" under Android USB Devices. When connecting in Fastboot mode, it's in the same place, but there's a yellow exclamation with an error:
"This device cannot start. (Code 10)
A request for the USB BOS descriptor failed."
Additionally, a notification appears in the System Tray when connecting in Fastboot mode regarding the USB device malfunctioning.
It seems like I'm all set when outside Fastboot mode; the device has no errors in Device Manager and is visible when I run abd devices. It does not appear when I run fastboot devices in Fastboot Mode.
Any tips?
There are no working Windows 8 drivers for the Rezound in Fastboot... Sorry, you need Linux or Windows XP/Vista/7, wish I had a better answer for you.
Sent from my Nexus 4 using Tapatalk
Ah, I was afraid of that! Well, thanks for the quick response. I'll go dig up that Linux machine I have somewhere around here
Hey there! I'm currently going through the process of unlocking the bootloader on an old Desire 610 I had lying around, and was stuck following the HTCDev website instructions. It tells me to execute the command "fastboot oem get_identifier_token" but it won't go through, even though the phone is in the fastboot menu, connected via USB and displays "FASTBOOT USB" on the screen. Can anyone help?
ShinyMagikarp99 said:
Hey there! I'm currently going through the process of unlocking the bootloader on an old Desire 610 I had lying around, and was stuck following the HTCDev website instructions. It tells me to execute the command "fastboot oem get_identifier_token" but it won't go through, even though the phone is in the fastboot menu, connected via USB and displays "FASTBOOT USB" on the screen. Can anyone help?
Click to expand...
Click to collapse
Not sure this is your issue but with Mac you need to start all commands with ./
So I just purchased this phone and am trying to follow the instructions on the Sony site. The rooting status in my service menu says my devices should be able to be unlocked.
Device is on android 13 on latest update, OEM unlock and USB debugging are both enabled.
I downloaded the usb drivers and the platform tools from the Sony site.
I opened a command prompt in the platform tools folder and when I run fastboot devices I get a response
When I run the command with my unlock code, I get the error
FAILED (remote: Command not supported in default implementation)
I tried to go to device manager to update the drivers, however when I do that it says the best driver is already installed.
I read in another thread to try to boot into the bootloader rather than fastboot. When I select reboot to bootloader the device seemingly shuts off.
EDIT: OK, I'm dumb and was in fastbootd mode rather than fastboot. I've now entered fastboot correctly (holding volume up while I plug it in, getting a black screen and a blue LED), updated the drivers correctly, and am now getting the error that the device is already unlocked. Now I guess I just need to verify that it is indeed unlocked, anyone have some advice on that?
EDIT 2: OK it seems to be going through the unlock process despite that error rather than the expected confirmation. After a few reboots it is now giving me the setup process again so I hope it worked. Leaving thread up for others who have the same issue to stumble accross.