Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

RUU Error 171 Stuck on waiting for boot loader

OP Okkoto

12th March 2013, 04:59 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
17 posts
Join Date:Joined: Jul 2012
More
As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.

EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??


More background information: http://forum.xda-developers.com/show...6#post39046436
Last edited by Okkoto; 14th March 2013 at 03:48 AM.
12th March 2013, 06:09 PM   |  #2  
Senior Member
Flag san fran california
Thanks Meter: 448
 
1,146 posts
Join Date:Joined: Jan 2013
More
What we're your steps exactly? Did you relock your bootloader
12th March 2013, 06:21 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
17 posts
Join Date:Joined: Jul 2012
More
Quote:
Originally Posted by a box of kittens

What we're your steps exactly? Did you relock your bootloader

Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.
12th March 2013, 07:07 PM   |  #4  
iElvis's Avatar
Recognized Contributor
Flag Modville
Thanks Meter: 1,902
 
3,767 posts
Join Date:Joined: May 2012
More
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.

Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
12th March 2013, 08:40 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
17 posts
Join Date:Joined: Jul 2012
More
Quote:
Originally Posted by iElvis

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.

Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.
12th March 2013, 08:42 PM   |  #6  
iElvis's Avatar
Recognized Contributor
Flag Modville
Thanks Meter: 1,902
 
3,767 posts
Join Date:Joined: May 2012
More
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
13th March 2013, 05:07 AM   |  #7  
OP Junior Member
Thanks Meter: 0
 
17 posts
Join Date:Joined: Jul 2012
More
Quote:
Originally Posted by iElvis

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
13th March 2013, 11:04 AM   |  #8  
OP Junior Member
Thanks Meter: 0
 
17 posts
Join Date:Joined: Jul 2012
More
Does anybody else have some more ideas?
13th March 2013, 06:37 PM   |  #9  
redpoint73's Avatar
Recognized Contributor
Thanks Meter: 3,360
 
7,739 posts
Join Date:Joined: Oct 2007
Quote:
Originally Posted by Okkoto

And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?

It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
The Following User Says Thank You to redpoint73 For This Useful Post: [ View ]
13th March 2013, 09:26 PM   |  #10  
OP Junior Member
Thanks Meter: 0
 
17 posts
Join Date:Joined: Jul 2012
More
Quote:
Originally Posted by redpoint73

No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?

It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes