Database Info

[Q] Cannot Flash Back To Stock, Boot, or Mount

First of all I apologize if this has been covered, I have been trying to find a solution for 3 days straight. I have a Rogers Wireless HTC One X I managed to unlock bootloader and root as well as having access to TWRP 2.1.8. recovery.
My problem is when I tried to apply the 3 dot removal mod my phone suddenly would not boot past the first screen, and a message would appear for developers use do not distribute but just stay on that screen. I have tried numerous things to no avail. I can boot in recovery and mount sd card from there (but have not found a successful way to restore from within recovery mode) otherwise in fastboot etc. the computer does mount the phone at all. it will not mount as a device properly so I cannot run the RUU and flash to stock.
So I am left with a unmountable and unbootable phone (brick) and have no other ideas on how to fix it if possible. BTW the device does show in device mgr and the computer gives the connect and disconnect alert, but it will not mount. Also, I have read the bootloader has to be relocked to flash back to stock if I relock the phone I cannot access recovery therefore an endless nightmare. Also, within TWRP recovery I try to reboot and it gives an error saying no Android OS found, install a rom or restore from backup (which I have neither) so I have to hold the power and dwn volume button to reboot each time to switch from recovery to fastboot. I think its toast.
Thank you in advance for any responses, I have been up almost 36 hours straight trying to figure this out and the phone is not even a week old. :crying:

There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.

Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.

gunnyman said:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Click to expand...
Click to collapse
Thank you very much I will look into that today. Fingers crossed!

i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.

stnguyen09 said:
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
Click to expand...
Click to collapse
Yes, thank you I have HTC Sync installed and it does not recognize the phone when it is connected either. I will keep searching. Thanks.

ethantarheels123 said:
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
Click to expand...
Click to collapse
Yes, I have tried relocking bootloader, it did not help with the phone being recognized by the computer also when I oem lock I cannot access recovery and such. I will have some more time to poke around with it, I have downloaded the RUU utility although it sends back error with device not found. Thanks for your reply, I will keep at it I know the phone can not be bricked, well I am hoping not!

[Q] One S Brick? HELP!

Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\

I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium

beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.

nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?

Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .

As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know

Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk

Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.

Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.

nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.

I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).

nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.

Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.

Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!

nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.

Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2

HTC One X in boot loop after unlocking

Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.

mrwizard65 said:
Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.
Click to expand...
Click to collapse
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.

HTC_Phone said:
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.
Click to expand...
Click to collapse
I don't believe the computer is recognizing it at all. I'm not hearing the normal "ding" I get when it reboots.

first turn the phone off by holding power button for a longer time, then turn it on by holding both power and volume down buttons for a couple of seconds to enter bootloader

Did you install the Rom? Or just the boot.img?
Sent from my VENOMized HoxL

Alright, so holding down the volume button did get me into the bootloader. I tried the recovery and was able to recover using TWRP, but when I reboot it brings me back to the same HTC screen. So again, now I am able to do things via the bootloader so hopefully there is a next step to fix this.
To answer your question, I did not get to install the ROM, only the boot.img
Thanks for everyones help so far.

So go to twrp and install the Rom
Sent from my VENOMized HoxL

area51avenger said:
So go to twrp and install the Rom
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Ok, went ahead and loaded up Viper 3.2.2 and it seemed to go fine. Rebooted and am at the same HTC logo screen with the "this build is for development....." It will keep rebooting into this screen several times and will hang.
I did get the tampered/unlocked notice on the bootloader before doing all this. Not sure if that makes a difference or not.
Thanks for any additional help.

Did the ROM install correctly? Flash the boot img in adb again.

pOLLYpOCKET said:
Did the ROM install correctly? Flash the boot img in adb again.
Click to expand...
Click to collapse
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.

mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
I thought you wouldn't be able to install RUU if your bootloader is unlocked. But anyway, try this thread instead http://forum.xda-developers.com/showthread.php?t=1732980

I'm glad to report that I was finally able to flash the 3.2.2 Viper ROM. I was having problems unlocking the phone again, but just did it via fastboot command line. Once that was done it was smooth sailing.
I do have a couple of issues with the Viper ROM, but all in all it's fine and I'll post those questions in the Viper thread.
Thanks again for everyones help!

mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
Re-unlocking is a *****. Took me about 80 tries. Reboot phone, reboot pc, keep trying. Eventually it will work. You didn't need to run the ruu.. You may just want to keep the phone in stock state if this seems complex to you.
Sent from my One X using xda app-developers app

go into bootloader manually then plug phone to pc. works first time to unlock.

RUU Error 171 Stuck on waiting for boot loader

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/showthread.php?p=39046436#post39046436

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

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
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.

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.

iElvis said:
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.
Click to expand...
Click to collapse
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.

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

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
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.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
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.

redpoint73 said:
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.
Click to expand...
Click to collapse
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.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

Please Help !. HTC One Mini stuck in BOOTLOADER Menu

My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP

Hi guys n gals
it appears ive inadvertantly deleted my rom i successfully unlocked bootloader installed recovery but over killed me wiping. Sso ive got an unlocked bootloader, have access to fasboot and recovery but fone is stuck at bootlader screen. How do I flash a rom now? as when hooked to a pc its no longer recognised. any help much appreciated!!!

moh19814 said:
My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP
Click to expand...
Click to collapse
I seem to be in the same situations... although I got to it in a different way. Where did you download the RUU from? is it version-main: 4.14.401.2 or higher?
Try: rootwiki dot net and search for htc one mini bootlocker unlock....this helped me to UNLOCK and put TWRP recovery on it... maybe it gets you a step closer.