Database Info

Need help with Odin one click master clear steps

Here is what I have I can not get Odin to find the phone to do a master clear. My phone has a charging issue in that it thinks it is charging all the time even with the charging cable unhooked from the phone and that stays whether I am running 2.1 or 2.2. All of my computers are Windows 7 and will only find the phone if it is download mode?????
I am hoping against hope it is a software issue but I am thinking it is a hardware issue. But want to try everything possible to fix it before I buy replacement parts or a new phone.
I have tried the instructions from other threads without any success.
Could someone give me a step by step process that goes from starting fresh by deleting current drivers and reinstalling everything. I may be missing something from the instructions I have followed so far.
Also if you know something else to try I am all ears.

After you one click odin to reinstal Jf6 you have to set the phone to mass storage and USB debugging again ( found in settings-aplications ). Then plug the phone back into your comp while Odin is up and running ahead of time and the phone booted and running. It should recognise it ( you'll hear that dreaded sound ), click master clear and wait for the phone to do it's thing.

Well I finally got odin to find the phone and done the master clear and it did not help.
So unless anyone has any suggestions I will assume it is a hardware issue.

bigcountry said:
Well I finally got odin to find the phone and done the master clear and it did not help.
So unless anyone has any suggestions I will assume it is a hardware issue.
Click to expand...
Click to collapse
Since you're having problems with the phone being recognized maybe it's hardware. But, my phone is recognized just fine and I have an extremely hard time getting it to master clear.
I would guess I've only gotten it to master clear twice out of probably 40 or so attempts. About 10 of those times was in download mode, but after I found out it had to be booted up it still only master cleared twice. What I do to increase the odds is manually clearing everything I can, after backing up. Factory data reset, then I go into Clockwork and clear everything I can in there by digging into the menus - cache, data, Dalvik, etc. Then I go back to stock, then just hope it'll master clear on that flash attempt.
When it takes, it goes fast, but I've let it try for 15 to 20 minutes before and had nothing happen. No progress showing, just the start announced in Odin and then the disconnection announced when I get bored of nothing happening and pull it.
So my point is, maybe try it a few more times before you write it off as hardware. I don't recall the exact conditions when I got it to work, since it takes so many tries. But I believe it's been flash to stock Eclair, rooted, USB debugging on, and sd card mounted. Maybe not mounted. I reboot the phone after every time I try.
Edit: I did another update today and master clear worked fine. Un-rooted Eclair booted normally, usb debugging enabled, and usb mounted.

Have you had the phone not turn on while it wasn't plugged in?

[Q] Corrupt Bootloader

I have the HTC Inspire 4G. I have a rooted stock rom from Bubby 323. My screen turned black when entering Clockwork recovery mode so I tried the Engineering S-Off method and when I flashed it said "Corrupt bootloader, do not turn off phone. Contact XDA" Does anyone have a suggestion on a fix? I have not turned off my phone since then. I used the one click S-Off method found here.

I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
You would think that if the program displayed a message telling you not to turn off your phone and check. XDA for a solution that he could have included the instructions you just gave.
Sent from my HTC Inspire 1G

RE-Corrupt Bootloader
Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
Thanks so much for the info. I did just as you said and it worked like as charm. I was worried for a while.

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
Thanks so much for this, I nearly had a heart attack when the message came up saying my boot loader was corrupt.

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
Sweet Mary.... I just bought my phone today, and about died when I got the DO NOT REBOOT message.... Thank you thank you thank you!!!!

Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
thanx so mush i almost died when it say DO NOT REBOOT YOUR PHONE

habanosrus said:
You would think that if the program displayed a message telling you not to turn off your phone and check. XDA for a solution that he could have included the instructions you just gave.
Sent from my HTC Inspire 1G
Click to expand...
Click to collapse
The instructions are in the thread for the UI........

HELP! Corrupt Bootloader, Do Not Reboot!
I have an Inspire 4G and i was trying to put ENG-OFF following this steps: http://forum.xda-developers.com/showthread.php?t=855403 to run "Desire HD s easy-off.exe" gave me "Bootloader is Corrupt. DO NOT REBOOT!" (He went out alone) and I could not take him with anything, you connect to the charger and nothing, the PC and nothing, as 20 minutes after i had pressed the power button turned on the cel with the white screen and vibrating continuously approx 8min, the problem is that in the beginning it takes too ... Now every time I reboot so, and if I discharge the battery will be useless because I do not grab power when connected to the charger or the pc .....
- I can not enter the bootloader, I managed to do with the "Super Tool V3" and the recovery reinstall the ROM, I thought it would end the problem but stayed the same, takes too long to start and does not grasp the power of the charger ... .
What can i do? What is it?
If I noticed that the bootloader says "ENG-OFF" and if you step back to ENG-ON?
I greatly appreciate (and have no idea how) that can help me please .....
(sorry about my english)

rikrdoVe said:
I have an Inspire 4G and i was trying to put ENG-OFF following this steps: http://forum.xda-developers.com/showthread.php?t=855403 to run "Desire HD s easy-off.exe" gave me "Bootloader is Corrupt. DO NOT REBOOT!" (He went out alone) and I could not take him with anything, you connect to the charger and nothing, the PC and nothing, as 20 minutes after i had pressed the power button turned on the cel with the white screen and vibrating continuously approx 8min, the problem is that in the beginning it takes too ... Now every time I reboot so, and if I discharge the battery will be useless because I do not grab power when connected to the charger or the pc .....
- I can not enter the bootloader, I managed to do with the "Super Tool V3" and the recovery reinstall the ROM, I thought it would end the problem but stayed the same, takes too long to start and does not grasp the power of the charger ... .
What can i do? What is it?
If I noticed that the bootloader says "ENG-OFF" and if you step back to ENG-ON?
I greatly appreciate (and have no idea how) that can help me please .....
(sorry about my english)
Click to expand...
Click to collapse
You messed up your bootloaders by not paying attention to the big bold red letters in that thread. Go to the Ace Hack Kit thread and grab the link to the IRC room. Then tell them what you did and they should be able to help you out.

"Communications with phone unexpectedly interrupted" error: Revolutionary

I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.

It's normal. Remove the phone, reboot it and run Revo again. It'll fail each time it tries to reboot but running it again does the stages one at a time. It'll eventually say you have root and do you want to install CWM

It happened with me many time....(NOTE: Do "DISABLE Fastboot" & "ENABLE Debuggin").
Try it again. When it boots into bootloader, you will eventually see on top "S-OFF" and the name "Revolutionary" as well. My Hboot version was totally different from the one mentioned on the "Guide to S-Off,Root,Flash CWM Recovery", But I did Root and flashed few ROM's till now. As soon as you instal CWM, install ROM Manager, Update the CWM and reboot into recovery and make a BACKUP(To be on safeside,as it was useful for me)
Good Luck.

Thanks. Ill keep trying and hopefully itll work eventually like you guys said.

First upgrade to Windows 7 But yeah, like the other 2 two guys said, just keep trying
Sent from my HTC Sensation Z710e using Tapatalk

ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both

icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
HTC sync was the only way it worked for me, on the the third loss of communication it worked, s off. As others stated, keep trying, it works.
Sent from my HTC Sensation 4G using Tapatalk

Please Make Sure you have HTC Sync uninstalled and Droid Explorer uninstalled.
Did you check the Post #2 of http://forum.xda-developers.com/showthread.php?t=1192300

icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
Try putting it to charge only, fastboot off and debugging on.
Try it 2-3 times.. eventually it gives s-off. Then you can install recovery by booting the phone & putting PGxx.zip on your sdcard. Then turn off the phone and boot to bootloader (Vol - and power) press vol + when it asks for update.

I had the same problem on the 3VO. When I disabled the fastboot option it worked!!

I was having this problem, USB debug on and fast boot off. No number of resets would cure it.
This is how I solved it, in case anyone is having the same problem:
The application reset the phone a second time, at which point it would get the error, I was left in the boot menu with S-On and a sad expression on my face.
During the first reboot into the boot menu, I quickly selected 'FASTBOOT USB' (I think it was vol down once, then power button). It then started processing the ZIP file before the application could reboot it a second time.
The application will still get the same error, however on your phone, you will now have S-Off.
Disclaimer: I have no idea what I'm doing, as evidenced by my post count of 1. It seems to work fine, but my phone may explode in 30 minutes time, I have no idea.

press power key
when it asks for the fastboot second time, just press the power key once and u will get the s-off

after s-off...how can we push recovery and flash su zip...for root...

sorry guys, but I just can't get this to work. I'm having the exact same issue
as, well a lot of people. "Communications with phone unexpectedly interrupted"
I got a brand spanking new Sensation. (if that could be part of the problem)
I've scowered the internet for a solution and tried just about anything I can find.
- Phone is set to USB debugging.
- fastboot is off
- set to charge only
- sync is uninstalled
- all drivers are installed
I've tried every possible combination of the above as well.
I've tried "when it asks for the fastboot second time, just press the power key once and u will get the s-off"
for the "Try it 2-3 times.. eventually it gives s-off" I just completed my 25th try,
and still no luck.
What the f**k is going on here? I'm no noble prize winner, but I've done
way trickier stuff than this.
any ideas?
Thanks guys,

I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!

Hello Guys,
I solved this issue when I rooted my HTC desire using Unrevoked..
every time the desire rebooted, then the unrevoked said that " Communications with phone unexpectedly interrupted "
What I did is that,
- Phone is set to USB debugging.
- I couldn't find (fastboot) in my mobile, I just forgot about it.
- set the mobile to sync only when connected with usb cable.
- HTC sync is uninstalled from my computer.
- my computer recognize the device when it connected with usb cable otherwise you need to download some drivers (google it).
- then I connected my desire to the computer using the usb cable and start the unrevoked software.
- the unrevoked works and download some files then said that waiting for device to reboot. my device is rebooted.. when the logo of HTC started to appear in my mobile and just before the mobile completely works after rebooting, I have unplugged the usb cable from the desire..
- the unrevoked software still saying that "waiting for the device to reboot and it may take few mintues" !!
- when the desire is completely works and ready to use I have plugged it again to the computer and choose sync mode in very fast way before the unrevoked software detect it.
- then the unrevoked software start to download some files on the deasire and reboot it again for the second time and said that " waiting for device to reboot" .. in same way in have unplugged the usb cable after the HTC logo appears before it completely start and plug it again when the desire is completely working and ready to use and to respond.
- then the unrevoked software downloaded more files and said that " Done successfully" .
When I used this method, I have rooted and flashed my htc desire mobile and It is working fine. I just installed some custom roms on my mobile from the sd card using ClockworkMod Recovery v2.5.0.7 and it is working great..
I hope this will help somebody getting same problem.
Greeting from Saudi Arabia.
Mkman

AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
Thanks alot.I was same problem and done that way....

AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
It applies to Hboot 1:18.0000 as well. However in my case, no amount of plugging and unplugging will fix the problem...
Edit: Solved by running on Win 7, outside of the VM where I usually do my phone stuff with adb installed ect... So not sure if adb was the issue or that the VM is WinXP. Anyway, seems clean install of drivers without adb installed fixed it.

try to install adb, it works
When I was rooting and s-off an htc desire on linux using revolution. It fails every time on "waiting for fastboot...", then exit with "communication with phone unexpe...".
I have adb installed with android sdk. however, i haven't started the daemon. The last time I use "adb devices" to check the connected device, this also enables the adb daemon. Then everything just goes well and i get s-off.
Remember to install adb and start it by executing "adb devices"

icepikk said:
I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.
Click to expand...
Click to collapse
i had same issue when i was using a VM windows machine, once i tried with a physical win machine it worked like a charm.

[Q] volume down wont recognize phone. am i SOL?

Hello and thanks in advance, FIRST THINGS FIRST I have searched and have spent close to 48 hours reading and attempting to resolve this through KDZ_UPD and Reflashing CM7. Im having trouble with my phone trying to reflash the V21E baseband using KDZ. When i launch KDZ software update it only looks on port 1 and 2 then I get the "Phone Was Not Found" error. I powered off one day and pulled the battery then reset to find the "No Service" and ? for my battery. I was using CM7 for about Two months prior without any problems when this happened. Now i am currently back to stock 2.3.3 with stock recovery. From what i understand when i hold both volume buttons i should see three items pop up in my device manager however i only see nvidia usb boot recovery yada yada yada.... and that is only when i hold both volume buttons. While holding the volume down button it goes into S/W update but nothing in device manager ...... does this mean its bricked (I know some people say its not possible but not possible bad luck runs in the family) and if not how would i go about getting it to connect?
P.S. I have tried several different machines some xp pro(and a vm) and some win 7 ultimate, and several different cables on each...
Please help and offer some advise before i loose my marbles!
Thanks in advance

Also if this is in the wrong place i apologize i didn't want to resurrect an obsolete thread.

for ****s and giggles, click on the "show hidden hardware" checkmark within the device manager. Maybe there are borked and need to be removed / reinstalled on the XP install?

New2my8125 said:
for ****s and giggles, click on the "show hidden hardware" checkmark within the device manager. Maybe there are borked and need to be removed / reinstalled on the XP install?
Click to expand...
Click to collapse
Nothing there out of the usual... thanks for the quick reply. do you think I'm bricked?

Ok so i had somewhat of a breakthrough... i connected my phone and it found the lg port 4 under device manager.
So i started KDZ then about half way through it disconnected...... sending a bunch of authentication errors and corrupting my V21E_00.kdz file...
now it wont connect through any cables i try.... any thoughts?

For readers with input I am in a similar situation but am getting the bootloader up and LG logo but am also unable to enter recovery... so advice pertaining to the OP prior to the device going link dead is also valuable and sought after.
Sent from my SGH-T959V using xda premium

Ok for reasons unknown i had a brilliant idea which worked..
I had an mp3 player years ago that for some reason i would not connect to the computer unless (dont ask me why) I would put it in the fridge or freezer for a few minutes.
Anyways i figured id try this and it worked. all 3 devices in device manager popped up, set the cpu priority for KDZ to high and flashed the baseband!
Booted up, just fine however, i reboot the device and now i am in the same boat with the no service. going to try to flash cm7 and see if anythings different...

Ok so i flashed cm7 and the baseband worked on first boot up but after restart it was unknown again..
Can anyone confirm this is probably hardware?
Thanks!

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