[One (M7) Q&A, Help & Troubleshooting] LibertyMarine:
! Once this section was constantly growing !

​

Basic issues and troubleshooting? Here it goes​

Q: I can't start up my device, not even the soft buttons are lighting up!

A: I know, it sound strange, but you have to do the following thing:

Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
​

Q: I still can't boot up my device!

A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
​

Q: I tried flashing the RUU and I got an error while flashing hboot, what can I do?

A: JUST DON'T REBOOT try reflashing, try a different hboot... use a different computer/usb cable, just don't reboot, rebooting will lead into a hard-bricked device!

The following Errors are save to reboot(Thanks [MENTION=1102297]Sneakyghost[/MENTION], http://xdaforums.com/showthread.php?t=2316726):

- 12 signature fail (unknown yet but safe to reboot)

- 23 parsing image fail (means something wrong with the image in the zip)

- 32 header error (means the zip couldn’t be read and unzipped properly)

- 41 Wrong Model ID (means its not the right device)

- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)

- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).

- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)

- 155 seems to indicate different things, always relating to your phone not being eligible for a certain update. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match - there is no conclusive evidence yet, only hints. I can for now not see the commands being run by a RUU and determine which check exactly fails, so i am left guessing for now.​

Q: What do I have to pay attention to using Windows 8.1 ?

A: Actually, there are no more driver issues with Windows 8 or Windows 8.1. But if your HTC One is on hboot 1.44 or even below hboot 1.44 you can't get a fastboot connection to your HTC One. This means if you're using one of the older RUU's that downgrade to hboot 1.44 you'll be stuck after the first hboot preupdate:

FAILED (remote: 90 hboot pre-update! please flush image again immediately)

And you won't be able to reflash the RUU to complete the RUU process.. This means that you have to find a Windows 7 Computer to complete the RUU process. What does this exactly mean?

Never flash a 1.44 firmeware or RUU package to your device using Windows 8+ or you'll be stuck!

​

Q: What do I have to check when choosing an RUU?

A: That's pretty easy. But the best thing is to explane it with an example.. Ok, I downloaded this file here from HTC1Guru and it's called like this:

Now, the red marked text has to be the same as your device was on stock.

x.xx.401.x stands for your location. It's also written before... like above "Europe"

And the blue text is also important
​

Q: What issues might come with newer hboots?

A: Ok, new hboots give you more performance and better stability. But the downside of one of these hboots is the newly introduced Tamper detected on hboot 1.55. This basically means that when going back to stock with a RUU Locking and Untampering and taking all OTAs up to hboot 1.55+ and then going back S ON(Highly NOT recommanded) will lead into a tamper dectected and you'll see this tampered flag again. What means, a lot of work: Unlocking, S offing, RUUing and Locking going S ON the right time again.. The particular right time is:

After hboot 1.44 but before hboot 1.55... this means the best hboot to use is 1.54.. you did an OTA and this means that the bootloader is more than stock and so most likely safe to go back s on and you are on a version before hboot 1.55 what means you won't get a tamper detected!

Also: Going back S ON with a altered bootloader is inevitably going to lead into a hard bricked device !

Summary:

NEVER GO S-ON WITH A MODIFIED HBOOT AND A HBOOT VERSION HIGHER THAN 1.54
​