Hi, I'm new to the Rezound coming from an X2. I'm loving this phone. I want to unlock the bootloader but I am having issues with this phone. I am following the steps on htcdev.com exactly and when I enter fastboot oem get_identifier_token it stays at waiting for device. I unlocked a droid incredible several months ago so I have done this with a different HTC device before. Anyone know why I cant get it to work on my Rezound. I sent HTC a message about it, I'm hoping they have an answer, but I know the people on this board know alot of stuff about these phones. the software version I am on is 2.01.605.11 any sugestions? Thanks
John
When you start the phone with the volume switch down, you get taken into HBOOT. The first item on the menu is FASTBOOT. You have to put the phone into FASTBOOT (use Volume up/down to navigate to FASTBOOT and then hit the power button to select) before the PC can talk to it. Have you done this?
Assuming your phone's in FASTBOOT, there's a menu that starts with BOOTLOADER. A few lines above this menu you should see the word FASTBOOT in white on a red background. If your USB connection's okay, this should change to FASTBOOT USB a few seconds after plugging in the cable. Is this happening?
yes, It just wont go any further
jtornone said:
Hi, I'm new to the Rezound coming from an X2. I'm loving this phone. I want to unlock the bootloader but I am having issues with this phone. I am following the steps on htcdev.com exactly and when I enter fastboot oem get_identifier_token it stays at waiting for device. I unlocked a droid incredible several months ago so I have done this with a different HTC device before. Anyone know why I cant get it to work on my Rezound. I sent HTC a message about it, I'm hoping they have an answer, but I know the people on this board know alot of stuff about these phones. the software version I am on is 2.01.605.11 any sugestions? Thanks
John
Click to expand...
Click to collapse
Do you have USB Debugging enabled on your phone?
yes, as well as allow from unknown sources.
Do you have HTC Sync installed on the PC? Does the PC acknowledge the USB connection when the phone's in fastboot?
htc sync is installed and sees the phone. when in fastboot, as soon as i plug in the usb cable it says fastboot usb
I'm going to try it on another pc and see what happens.
Wish I had more to offer. It doesn't seem like you're doing anything wrong. Good luck!
jtornone said:
htc sync is installed and sees the phone. when in fastboot, as soon as i plug in the usb cable it says fastboot usb
I'm going to try it on another pc and see what happens.
Click to expand...
Click to collapse
Uninstall HTC Sync for now.
I tried it on another computer and it worked. So something is pooched on this laptop. Thank you all for your sugestions
Out of curiosity what is the OS on your laptop? I had Windows 8 for a bit and when the new firmware came out I needed to re-lock the bootloader and couldn't because windows 8 and the phone didn't play nice together. As soon as i went back to Windows 7 no issues.
I was using Windows 7 Pro.
Related
I'm attempting to root my AT&T HOX+. I have successfully unlocked the bootloader, and am trying to flash a recovery ROM. The program continues to hang at the <waiting for device> prompt. I have searched and the only solution people had was to confirm that USB debugging mode is enabled, I have checked and it is. Is there some other reason this may be happening?
Attached is the screenshot of my developer options to confirm that I'm not crazy.
chris113113 said:
I'm attempting to root my AT&T HOX+. I have successfully unlocked the bootloader, and am trying to flash a recovery ROM. The program continues to hang at the <waiting for device> prompt. I have searched and the only solution people had was to confirm that USB debugging mode is enabled, I have checked and it is. Is there some other reason this may be happening?
Attached is the screenshot of my developer options to confirm that I'm not crazy.
Click to expand...
Click to collapse
Use another USB port. Make sure you don't use a USB 3.0 port as well
hasoon2000 said:
Use another USB port. Make sure you don't use a USB 3.0 port as well
Click to expand...
Click to collapse
I have tried four different ports now, all USB 2.0, and the program still hangs at <waiting for device>. Just to confirm, the phone should be turned on when I run the flash, because I can't figure out how to boot it into charge-only mode.
Make sure you don't have HTC sync running.
Sent from my HTC One X+ using Tapatalk 2
chris113113 said:
I have tried four different ports now, all USB 2.0, and the program still hangs at <waiting for device>. Just to confirm, the phone should be turned on when I run the flash, because I can't figure out how to boot it into charge-only mode.
Click to expand...
Click to collapse
The phone must be fully turned on and you have access to the operating system.
Sent From My HTC Amaze 4G via Someone's Room
I bought my One with bootloader unlocked but the guy who sold me the phone unrooted the phone before shipping and i've tried to follow the rooting and the unlocking bootloader through fastboot methods but every time i open sdk manager it just says i have to update, i update then it says restart, and no mater what i do, cmd just keeps telling me fastboot is not a recognized command... blah blah... short question is, is there a rooting app i can purchase or if anyone can give me a helping hand?
Edit: I have followed the steps exactly, switched off fastboot in power menu, and powered off entered fastboot from bootloader, plugged in device, entered cmd and tried it but i get the aforementioned error.
Edit 2: I made the folder and placed my files and it seemed to go a little smoothly but it says waiting on device and just hangs there. The computer is still not recognizing the phone, i still get USB not recognized. try reconnecting the device....
Oh also, trying to install a recovery to this, so i can root... but just an easy way
Please help me, someone... the bootloader says unlocked btw. but fastboot does nothing when trying to flash via cmd.
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
sakumaxp said:
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
Click to expand...
Click to collapse
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
HyDRo1X said:
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
Click to expand...
Click to collapse
ok i switched to a win8 an everything seemed fine, but i get a long list of processing cmd after i type the fastboot flash recovery... and then continued as followed but nothing... still get red triangle
Ok got it... Windows 8 problems
Sent from my HTC One using xda premium
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It sounds like the waiting for device message with fastboot it because you're in bootloader (hboot) instead of fastboot maybe. You want to uninstall the HTC sync program, it's used because it installs the drivers then you get rid of the program itself or at least make sure it's not running at startup and when you connect the device. On Windows 8 did you disable the driver signature verification yet?
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same result in fastboot, I'll try uninstalling HTC sync and disabling driver signature verification now and see how it goes
edit: same result, adb devices comes up empty when in fastboot after disabling driver signature verification and uninstalling HTC sync
It should be "fastboot devices" as the command.
Does your computer have native USB 3?
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
It should be "fastboot devices"
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
that returns nothing it just starts a new command line.
and two of the ports are usb 3.0 one is 2.0, I've tried all three
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Use the snip tool in windows to grab a screenshot of the command window stretched out to show the history, that may point me in the right direction. Do a search for Windows 8 ADB and Fastboot driver installation (i prefer Google and prefix the search with "site: www.xda-developers.com" no quotes) and you should find a thread with the steps for installing the drivers properly after signature verification is disabled in Windows 8. I used it to remotely fix a user's computer with the same issue you're having but I'm mobile at the moment. I'll help you get it straightened out though that's kind of my specialty. I'm about to go get something to eat, I'm working on a migraine and when I get back I'll check back in. Feel free to PM me if you want while waiting on input from others also.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for the help, I hope this is all you need from the command window. I'm trying the adb and fastboot driver installation thread that you suggested now, hopefully this will have it resolved by the time you get back.
edit: unfortunately that didn't work, it said that the driver is already up to date. The phone shows up as "My HTC" under android USB devices already, even when in the bootloader/fastboot, but it shows the device status as "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I just have some extra things in the folder like some ROMs/recoveries but I don't think that would matter. I have adb.exe, fastboot.exe, and the two .dll's so I think I have everything I need.
And I tried fastboot reboot while in fastboot, I got waiting for device in command prompt. Also when I entered the command I got a "USB device not recognized" popup from the taskbar. Device manager shows the phone as My HTC with a yellow caution triangle on the icon and the device status "This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
CharliesTheMan said:
That's usually the result of using a USB 3.0 port, do you have a different set of ports you can try? Like back of the computer instead of front, side of notebook to back of notebook etc. Most motherboards have a USB 2.0 hub and USB 3.0 hub but the manufacturers don't make it obvious which is which in most cases. Also make sure antivirus and such is turned off while you're testing. Its one of those things that's just a tad bit off such as the ports or a driver.
Let me know how the above turns out and tomorrow if you want I can hop on teamviewer and we can try uninstalling what's there, starting fresh with the Google sdk and go from there.
PS- Sorry I haven't had a more direct answer I know it can be frustrating with so much trial and error and it being almost working. But I promise I'll stick with it until we get something figured out, or you get mad and remotely smack me over the head with a keyboard.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Finally got it working, kept trying on my old computer that I unlocked it originally with and eventually it just decided to recognize it and worked.
Thanks so much for the help getting to this point.
kalbany said:
I'm pretty sure I was using the 2.0 port but I could be wrong. I'll keep working on it and if I can't resolve it I'd love to try teamviewer wth you. Thank you so much for all the help so far.
Click to expand...
Click to collapse
I
Is there an error information, e.g: Windows code 10.
If yes, I googled it, it shows:
The error message probably occurs when you are trying to use a particular piece of hardware, such as a USB connected device or internal DVD drive. Take note of the device you are using when the error occurs in order to update the correct drivers.
error.info/windows/driver-10.html
Cheers,
Lun:
kalbany said:
I had my phone unlocked and working with a custom ROM in the past, but after some problems I gave up and just relocked it and went back to stock. Now I'm trying to unlock it again and I'm running into some problems. I'm unable to get the identifier token to use with htcdev because whenever I go into the bootloader my phone is not recognized by adb. fastboot oem get_identifier_token leaves me with a waiting for device message, and adb devices returns an empty list. If I turn the phone on normally the device shows up then. To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (including the one I originally did the unlock on, when it worked fine), and have searched all around the internet and various forums for an answer. I've tried manually updating the USB drivers through device manager, but that did nothing. I have HTC sync installed as well. When I plug the USB cable in I sometimes get a device cannot be identified/has malfunctioned message. Device manager also shows a yellow warning triangle on my phone when in the bootloader. I'm on windows 8 currently, but I've tried it on a windows 7 pc as well with the same results.
tldr: adb doesn't recognize my phone while in bootloader, so I can't unlock it.
Thanks in advance for any help, I've tried everything I can think of.
Click to expand...
Click to collapse
I have Started a thread for HTC Droid Incredible phones in the troubleshooting area. Im having the same exact problem and im running Windows
as soon as i do the command: fastboot oem get_identifier_token, it just sits there and waits. and then i get a pop up from the system tray saying that my device has malfunctioned.
CharliesTheMan said:
Adb devices worked, that's your serial number so it's definitely fixable. What does it tell you when you boot to hboot, select fastboot, and use the command "fastboot reboot"
Could you send me a screen shot of the folder contents for the mini-adb folder, just like you did the command window except inside the mini adb folder.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Regardless of how old this thread is I'm running into the same problems now!
My Xperia XZ1 Compact doesn't seem to be recognized when in the bootloader (indicated by a black screen and blue led).
I tried "adb reboot hboot" and it booted into a new black screen, but didn't last long before rebooting.
I tried other button combinations during the sequence and those didn't change anything.
Hi im fairly newthis to all this so please be patient. I have Htc 4g amaze Tmous rooted s-on unlocked. I flashed a custom rom which is stock debloated. But, the wifi and bluetooth do not work. I want to revert back to stock by using the same method which is the Htc toolkit. But, when i restart in bootloader mode the phone is no longer recognized by my laptop running win 8.1. I have been searching for a week now and have tried everything from deleting drivers, reinstalling, downloading htc sync and removing the software but leaving drivers,, different USB ports 2.0 & 3.0, nothing works. When its in bootloader about 5 seconds later my computer says USB device not recognized.
Please help.
mikeny said:
Hi im fairly newthis to all this so please be patient. I have Htc 4g amaze Tmous rooted s-on unlocked. I flashed a custom rom which is stock debloated. But, the wifi and bluetooth do not work. I want to revert back to stock by using the same method which is the Htc toolkit. But, when i restart in bootloader mode the phone is no longer recognized by my laptop running win 8.1. I have been searching for a week now and have tried everything from deleting drivers, reinstalling, downloading htc sync and removing the software but leaving drivers,, different USB ports 2.0 & 3.0, nothing works. When its in bootloader about 5 seconds later my computer says USB device not recognized.
Please help.
Click to expand...
Click to collapse
You're gonna have to be a bit more specific with how you're trying to read the device:
a) When you're in bootloader, and you have the phone plugged in, does it read HBOOT USB, or FASTBOOT USB?
i) If yes: Then just run the program. It will still recognize the system even if Windows doesn't show it. Fire off a CMD command or simply click "reboot" on the toolkit and see if the phone responds.
ii) If no: Use another cable, and make sure you're securely connected. Generic micro USB cables tend to be a bit loose even when connected, so make sure the cable itself is not "ajar" in the port
Once you're in bootloader mode, post what it says here.
darkandshadow said:
You're gonna have to be a bit more specific with how you're trying to read the device:
a) When you're in bootloader, and you have the phone plugged in, does it read HBOOT USB, or FASTBOOT USB?
i) If yes: Then just run the program. It will still recognize the system even if Windows doesn't show it. Fire off a CMD command or simply click "reboot" on the toolkit and see if the phone responds.
ii) If no: Use another cable, and make sure you're securely connected. Generic micro USB cables tend to be a bit loose even when connected, so make sure the cable itself is not "ajar" in the port
Once you're in bootloader mode, post what it says here.
Click to expand...
Click to collapse
Hi and thanks for the reply. Im using the OEM htc cable and everything else reads just fine. I'm able to read the sd card and send some commands through the toolkit. For example i can click the "boot into bootloader" command and it works fine. The problem is once it is in bootloader the command prompt window just says waiting for device and the phone says fastboot. I am able to reboot the phone back into android using the vol keys and the power button. Im trying to relock the bootloader using toolkit but on the second window (first being putting it bootloader) it won't read the phone following the computers message saying usb device not recognized. Thanks again for the help.
mikeny said:
Hi and thanks for the reply. Im using the OEM htc cable and everything else reads just fine. I'm able to read the sd card and send some commands through the toolkit. For example i can click the "boot into bootloader" command and it works fine. The problem is once it is in bootloader the command prompt window just says waiting for device and the phone says fastboot. I am able to reboot the phone back into android using the vol keys and the power button. Im trying to relock the bootloader using toolkit but on the second window (first being putting it bootloader) it won't read the phone following the computers message saying usb device not recognized. Thanks again for the help.
Click to expand...
Click to collapse
You may have to try it manually. Download a fresh copy of the Android SDK tools
and put the "Platform-Tools" folder under your C:\
Fire up Command Prompt, change directory to that platform-tools folder.
Then type in "fastboot oem lock" (without the quotations).
Your phone will reboot and upon the bootloader, it should say **RELOCKED** at the top.
If you're still having issues, I would suggest loading up on another computer, or if that isn't possible, download Ubuntu and burn it as a LiveCD and see if your phone will be recognized (properly) through Linux. Sounds like the communication protocols for your phone are fuxed. As for uninstalling and reinstalling drivers like that, you may have to use regedit to completely remove trace portions of those previous installs.
It's a driver issue, uninstall and reinstall the drivers.
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
dilyn said:
After an hour or two of wondering why I couldn't get s-off on my phone, I realized that I was using a slightly outdated guide. Used Rumrunner instead of Moonshine, s-off acquired. I was trying to get my phone to be recognized as a Developer Edition, so I had to change the MID and CID. I was using a guide for changing the MID on here, but I guess silly me misread a step or something, and now here I am: the phone is stuck in fastboot mode. If I try to get into recovery it just flashes to the white HTC screen for less than a second and back into fastboot. Rebooting the bootloader just returns me to a black screen as if my phone were off.
When I plug my phone into my PC, I can here it dinging as if a device were plugged in, and when I go into Device Manager the port it's plugged into recognizes a device is there, but it says "Device failure enumeration" and gives me Code 43 (Windows has stopped this device because it has reported problems). Any attempt to access via fastboot (I've tried reflashing a recovery and clearing cache, as well as rebooting) simply returns <waiting for device>, and when running adb devices it returns that there aren't any devices attached (explains why fastboot commands aren't working).
Any ideas? Or is my phone gone forever?
Click to expand...
Click to collapse
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
bigdaddy619 said:
Use a PC that is not Win 8.1
BTW adb devices only works in recovery and OS
fastboot devices works in fastboot
Click to expand...
Click to collapse
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
bigdaddy619 said:
I don't think there are any drivers available for 8.1 as of yet.
Some folks have got it to recognize but it's hit or miss
Click to expand...
Click to collapse
That's really strange. I had the drivers working prior to this episode. I thought that the device suddenly being unrecognizable had something more to do with it.
Oh well. Today I learned.
dilyn said:
Ah, that worked beautifully. Charged up my phone, reflashed TWRP, charging fully before I embark on any more travels and will proceed with extreme caution
Any particular reason as to why Windows 8.1 is giving me issues? I hadn't read anything about that in particular, so I'm very interested to know...
Click to expand...
Click to collapse
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
dg32 said:
So you used a PC with Windows 7 and it recognized the phone? I'm having the same issue where I can't even get the screen to turn on and win 8.1 no longer recognizes the phone being plugged in.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Windows 8.1 recognized my device in normal operation, but in any modified hboot failed miserably. (such that are used in conversions/etc)
I've long since reverted back to Win7 for anything involving Android....just so much less risky at this point.