Develop Bugs

Need help with returning to stock or S-OFF root (issues caused by latest OTA)

When I tried the new OTA with a new Incredible I got off of eBay (not rooted or tampered with) it kept messing up half way through and causing my phone to constantly reboot. I restored my phone but when I leave it plugged in with 3G on the OTA messes up my phone again.
I don't have root access so ES Explorer can't delete the .zip in the security folder to stop the OTA.
I've been trying to downgrade the HBOOT and get it to 2.3.3 but it won't work.
I either want it to be full stock or gain S-OFF so I can put CM9 on there. I have HBOOT .98 and can't get it to downgrade.
So, I tried following the following:
http://forum.xda-developers.com/showthread.php?t=1298990
Everything worked fine up until near the end. It says "remote: 99 unknown fail". (SEE 1ST IMAGE)
*NOTE, ERASING CACHE WILL WORK. JUST DIDN'T THIS TIME. I'VE TRIED THIS SUCCESSFULLY UP UNTIL THE REMOTE 99 FAIL*
http://www.youtube.com/watch?featur...v=CgIYFGcVimU&annotation_id=annotation_395071
It's still 2.3.4, Sense 2.1.
My phone is Unlocked but still S-ON. I can't get rid of S-ON no matter what I try and do.
See 2nd image for what my HBOOT looks like.
Can anyone tell me what I'm doing wrong and what steps I need to follow at this point?
Also, can I flash CM9 and delete bloatware even with S-ON?
Thanks!

Someone correct me if I'm wrong, but it seems like the phone was unlocked through the HTC Dev Unlock tool. Have you tried relocking using that?
Sent from my Incredible 2 using xda app-developers app

To my knowledge I didn't use that. Just what is listed on these links.
Where can iI find this program and try to relock?

You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.

I cant boot back into the phone.
---------- Post added at 03:10 AM ---------- Previous post was at 02:43 AM ----------
I locked the bootloader and now it just will not boot into the phone. I tried to go into recovery but it just reboots.
Did I just mess up my phone?

sjpritch25 said:
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
Click to expand...
Click to collapse
Thank you! I actually decided to stick with stock. The new OTA actually worked this time around so I have no issues. IF ICS ends up never coming out, I'll eventually root. I really enjoy Cyanogenmod but for now stock feels safe for me.
You have no idea how much I truly appreciate this. I've been frustrated for a week. Searching all over the internet and doing everything in my power to fix it. All it took.. was that! THANK YOU!

Your welcome...

Now I have no stock recovery. It's a phone image and a red exclamation point. It then boots e3 and says something like "E: can't open cache/recovery/command"
How can I regain stock recovery?
Sent from my ADR6350 using xda app-developers app

Download the gingerbread RUU located http://minus.com/mvivow#1
I recommend renaming before downloading it.
rename it PG32IMG
Be careful with windows because it might rename it as PG32IMG.zip.zip. It won't work.
Move it to the sdcard
reboot into bootloader and allow the update. Its a signed RUU, so it should work.

It says "Main Version is older! Update fail"
Is there a RUU yet for the latest 6.xxxx OTA version?

I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked again and could use recovery, which is what I'm doing right now.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!

It would be less confusing if you used the same user name on all the forums you post on.
undergone said:
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked the phone again and can now use Recovery. I will stay like this I suppose.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
Click to expand...
Click to collapse

Sorry dude.
Here's what is happening now... let me re-clarify.
So I had several issues caused by the latest INC 2 OTA. After the OTA messed up my phone I followed several threads online to downgrade to 2.3.3. After I did this, I updated back to 2.3.4 and then did the new OTA. It worked.
When I did this, "recovery" disappeared in the bootloader.
I eventually unlocked my phone again and was able to flash a custom recovery.img to get clockwork mod recovery back on. Everything was going smoothly!
I then entered recovery and accidentally restored a previous backup (version 5.xxxxx which would power off due to the OTA messing it up). So I immediately did a factory reset.
After this, the Radio is 1.09.01.0312. Every time I boot up it gets stuck on the white HTC screen. I've tried clearing cache, formatting system and then doing a factory reset. It still is the same.
To my knowledge this current radio is the radio for the new OTA (6.xxxxxx). My phone thinks it's software is still 5.xxxxxx due to the accidental restore.
I guess the radio I need ends in .1111. Would not having this radio cause this issue? I downloaded the radio but it says I have to be S-OFF to install it.
I am currently unlocked and S-ON.
Am I screwed or is there anything I can do to fix this?
I can only Fastboot and use CMD prompts. I don't even care if it's a custom rom at this point. Anything I can do to restore the phone.
Please and thank you.
EDIT: Also, PG32IMG files will not work. If I go to manually install it says E: Can't open sdcard/PG32IMG.zip (BAD)
Nor will it go through when I boot it up in the bootloader. I tried this for the version 5.xxxxxx. Do I need to wait for a 6.xxxxxx officiall RUU PG32IMG to come out? I haven't seen one yet.

when you see the red exclamation point press power button and volume up at same time, will put you in stock recovery

Is there ANYONE that can possibly help be fix my phone? I'm still stuck in the white HTC boot screen.
I can only load up in the bootloader.
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
RADIO-01.09.01.0312
eMMC-boot
I need to install the latest software. Is there a RUU yet for the latest 6.xxxx software yet as a PG32IMG?
Any steps to successfully do this would be appreciated.
Could someone with the stock software do a backup, zip the file and send it to me? that way I could put it in the sd/clockworkrecovery/backup and try to make it work.
Thank you.
EDIT: ***HERE IS THE FIX THAT WORKED FOR ME***
Here is how I fixed it: I suggest all others with my issue try this...
Flash the boot.img from this rom: http://forum.xda-developers.com/showthread.php?t=1737494
THEN went into recovery > factory reset > clear cache > wipe dalvik > install zip from SD > install
If you need addition details, how to flash, etc. they can be found here (http://forum.xda-developers.com/showthread.php?p=28262673#post28262673) where I was also given help.
I'm user "telecastertunes" on there.
Good luck!

[Q] Reroot and Reunlock after ruu

I have a Wildfire S CDMA from Virgin, USA which I unlocked, s-off and rooted, and installed cyanogenmod recovery.
Fastboot shows MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
I am looking to unlock from 'RL', and reroot, but after no small amount of wading through forums, I'm here asking you all for assistance. I'm new to messing with my phone, but feel like I'm about ready for an 'Ah HA!' breakthrough.
Initially, I had deleted all system/data through Recovery, and finally found an RUU that would run and reinstalled the stock ROM.
Rerooting has been a challenge. When I follow the instructions at htcdev, I fail to execute run get_identifier_token, with "command error"
Fastboot running on my desktop does recognize the device, but have not been able to flash anything.
When I boot into recovery, the phone loads the HTC spash, but lands on a screen with a red triangle and exclamation point.
PG76IMG.zip isn't recognized by FASTBOOT on the phone, regardless of the modelid or cid in the android-info.txt
I would appreciate any suggestions to get back to root.... hard to imagine that some people use their phone with out it.

Lhooqtoo said:
I have a Wildfire S CDMA from Virgin, USA which I unlocked, s-off and rooted, and installed cyanogenmod recovery.
Fastboot shows MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.0000
I am looking to unlock from 'RL', and reroot, but after no small amount of wading through forums, I'm here asking you all for assistance. I'm new to messing with my phone, but feel like I'm about ready for an 'Ah HA!' breakthrough.
Initially, I had deleted all system/data through Recovery, and finally found an RUU that would run and reinstalled the stock ROM.
Rerooting has been a challenge. When I follow the instructions at htcdev, I fail to execute run get_identifier_token, with "command error"
Fastboot running on my desktop does recognize the device, but have not been able to flash anything.
When I boot into recovery, the phone loads the HTC spash, but lands on a screen with a red triangle and exclamation point.
PG76IMG.zip isn't recognized by FASTBOOT on the phone, regardless of the modelid or cid in the android-info.txt
I would appreciate any suggestions to get back to root.... hard to imagine that some people use their phone with out it.
Click to expand...
Click to collapse
It's because your bootloader doesn't support being unlocked.............Any bootloader that has *LOCKED*(or *RELOCKED*) written can be unlocked via HTCdev
Look over for the RUUs provided before the steps and see which one's for the CDMA WFS, run it and you will be able to unlock the phone

csoulr666 said:
It's because your bootloader doesn't support being unlocked.............Any bootloader that has *LOCKED*(or *RELOCKED*) written can be unlocked via HTCdev
Look over for the RUUs provided before the steps and see which one's for the CDMA WFS, run it and you will be able to unlock the phone
Click to expand...
Click to collapse
Downloaded the WFS SprintVM RUU from htcdev. It fails with error130 model ID error.
Identical situation as shown here:
http://forum.xda-developers.com/showthread.php?t=2027649
Walkthrough for downgrade exists here: but links are missing..
http://forum.xda-developers.com/showthread.php?t=1942991

Lhooqtoo said:
Downloaded the WFS SprintVM RUU from htcdev. It fails with error130 model ID error.
Identical situation as shown here:
http://forum.xda-developers.com/showthread.php?t=2027649
Walkthrough for downgrade exists here: but links are missing..
http://forum.xda-developers.com/showthread.php?t=1942991
Click to expand...
Click to collapse
If it doesn't work look for updates on your phone, maybe your carrier released an OTA with an unlockable bootloader

csoulr666 said:
If it doesn't work look for updates on your phone, maybe your carrier released an OTA with an unlockable bootloader
Click to expand...
Click to collapse
There is an OTA system update (through Settings/About phone/Software updates), however, the update fails with a red question mark over device. Doesn't custom recovery (CWM) and a changed CID (111..1) prohibit OTA update?

Lhooqtoo said:
There is an OTA system update (through Settings/About phone/Software updates), however, the update fails with a red question mark over device. Doesn't custom recovery (CWM) and a changed CID (111..1) prohibit OTA update?
Click to expand...
Click to collapse
The custom recovery does, but the CID doesn't....... Try doing it with a custom recovery installed

csoulr666 said:
The custom recovery does, but the CID doesn't....... Try doing it with a custom recovery installed
Click to expand...
Click to collapse
I currently have CWM installed (though currently if I run recovery from the bootloader, it fails).
If the custom recovery prohibits the OTA update, shouldn't I remove CWM to allow the OTA?

Try doing it with a stock recovery installed

csoulr666 said:
Try doing it with a stock recovery installed
Click to expand...
Click to collapse
followed this:
http://forum.xda-developers.com/showthread.php?t=2025121
sending 'recovery' <3146 KB>...
OKAY [ 1.522s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 1.526s

No joy?
Is there any chance that flashing the recovery would succeed if the recovery were different? (instead of a permissions issue).

[Q] Stuck in bootloader mode. No wifi. Adb can't find devices

Okay so, I had a problem of having no OS and had my htc m8 on soft brick for a while but i finally got that resolved by flashing a new rom on it. ( Here it is if you want to read: http://forum.xda-developers.com/htc-one-m8/help/os-installed-transfer-files-t3018626)
Unfortunately, I wasn't getting wifi on it. I tried 2 other roms and still no dice. I read online that i needed to update my firmware to do that. To do that, I needed to relock my bootloader so I did and the firmware flashed successfully.
Now my hboot is 3.19 instead of 3.16 and my bootloader says RELOCKED.However, when i go into recovery mode, my phone shows a picture of the dead android. I can't get past the bootscreen either so my phone is stuck on bootloader mode.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2497712 to help me get my phone unlocked again cause the unlock code at htc dev wont work again.
However, when i write adb devices, no serial number shows up now. adb shell says no devices connected.
I tried pushing and flashing a new recovery and rom in cmd and it said it failed.
I'm really grasping at straws at this moment since I can't really do anything.

Are you sure you are updated? In the bootloader, what does it say for "os"?
And what roms are you trying to flash? 4.4.4 or Lollipop?

And to unlock bootloader, start over at HTC Dev. See what happens. Instead of trying old code.
You can't flash a recovery with a locked bootloader.

I'm pretty sure it updated because everything looks different. Bootloader's background is black instead of white now too. When I flashed the firmware, everything seemed to be okay as well. . .
my OS says 3.11.1700.5
and i tried it at dev and generated a code, but it gave me an error and didn't give me a file. I tried to use my old file but that didnt work.

Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.

Darth said:
Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.
Click to expand...
Click to collapse
Which RUU do I download from here? I'm confused.

Shiverfire said:
Which RUU do I download from here? I'm confused.
Click to expand...
Click to collapse
Read the whole first post. It tells you how to determine that.
Any help needed after trying, you can ask there. ?

I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001

Shiverfire said:
I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery

SaHiLzZ said:
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery
Click to expand...
Click to collapse
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/

Shiverfire said:
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/
Click to expand...
Click to collapse
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app

mikem2273 said:
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said, recoveries wont flash cause its stuck on Relocked mode. I cant fix that because adb devices wont see my phone.
All the other commands on the All-in-One root kit gives me this:" 'C:\Users\Admin' is not an internal or external command, operable program or batch file " regardless of where i do it. I don't understand what I'm doing wrong here.
I tried to put the 0p6bimg.zip file but it wont copy on to my sd card cause of some error saying not responding or disconnected.
I tried flashing it instead but it said the file was too large
I tried the latest firmware but it said Failed! verification error.
I tried using the RUU to update and it stopped on the 1/7 process saying Error 155: Unknown Error.
I think what i need to do and how to fix it but I just need adb devices to find my phone.
If i can do that I can unlock my bootloader, install a recovery, install a rom and be home free but I can't do that until it detects my phone. I've tried everything now including reinstalling my drivers three times now.
Please help :'(

You don't need adb devices to see the device. You need to put the phone in the bootloader and type fastboot devices.
Open the command prompt inside the folder where also the fastboot.exe file is located.

Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...

BerndM14 said:
Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...
Click to expand...
Click to collapse
No, you guys. I already said this. I already used the htc dev the first time to get my phone unlocked. I had to relock it to flash a firmware. Now I can't unlock it again.The token isn't working. I already used the token once and its not working for the second time. I need adb devices to use adb shell. That way I can adb push revone and unlock my bootloader, but im not sure if that would work either.
Edit: I tried htc dev by generating a code 3 times. It generated different ones, the last one worked.

Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?

Shiverfire said:
Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?
Click to expand...
Click to collapse
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.

Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?

BerndM14 said:
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.
Click to expand...
Click to collapse
just flashed the boot.img and recovery.
cleared cashe and reinstalled super su.
same thing.

ckpv5 said:
Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?
Click to expand...
Click to collapse
wait, how do i know if its GPE? (I didnt buy a GPE phone)
I was able to download skydragon and android revolution before, the former was stock lollipop.
So what do I do? how do i install sense roms??

[SOLVED] Stuck on boot after OTA update!

I used a .exe RUU to get my phone 100% stock!
If you have a locked bootloader, use the command "fastboot oem lock" via Fastboot.
If you have "stuck on sending 1/8" issues, try to use the .exe on another computer! It worked for me.
Big thanks to ckpv5 and Mr Hofs for the help !
Hi guys..
So a long time ago I rooted my phone, installed a custom recovery and a custom ROM on my HTC. But then I came back to a stock ROM, stock recovery but still rooted.
Today I had an OTA official update (security fix). I installed it, but then my phone is stuck on the HTC One logo! I don't have any backups..
I don't know if I can use ADB or everything since i don't know if I can power off.
I don't know if I'm really rooted. When I wanted to unroot the phone it didn't worked, so I desactivated supersu, and automatically set supersu to "reject requests" (to root access)
S-ON
Stock recovery
Stock rom (this one: http://www.forum-generationmobiles....lection-de-roms-officielles-en-zip-htc-one-m8 )
CID= HTC_203
Unlocked bootloader
Rooter-or not
I don't know what to do, help :'( I don't want to waste 500€...

Flash a custom recovery and flash a custom rom. Then start looking for a backup with at least a working phone. There is a dedicated firmware/backup thread in the general section. Have a read there .... it's stickied so can't mis it !

That's what I wanted to do too! Okay. But thats kinda strange, I mean I installed a stock rom with a stock recovery but I can't install OTA update

LowPoly said:
That's what I wanted to do too! Okay. But thats kinda strange, I mean I installed a stock rom with a stock recovery but I can't install OTA update
Click to expand...
Click to collapse
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.

ckpv5 said:
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.
Click to expand...
Click to collapse
Okay, thats good to know.
Before I do anything, can I also re-lock the bootloader and install a RUU (exe) instead ? Will it work ? I'm probably wrong, but I think it's better since its a pure stock new ROM and not a backup..

LowPoly said:
Okay, thats good to know.
Before I do anything, can I also re-lock the bootloader and install a RUU (exe) instead ? Will it work ? I'm probably wrong, but I think it's better since its a pure stock new ROM and not a backup..
Click to expand...
Click to collapse
Yeah .. you can use RUU.exe (relock bootloader because S-On and make backup of your internal storage important data as this will wipe everything)
Some prefer to use pure stock TWRP backup because of the hassle to relock and later to re-unlock as these process will wipe data. Some prefer to keep their data intact and there is no need to relock bootloader when using a backup

ckpv5 said:
[...] because of the hassle to relock and later to re-unlock
Click to expand...
Click to collapse
By the way, if I want to re-unlock my bootloader, will I have to do this method again
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
with HTCdev etc ? Or is there a "fastboot" method as fastboot oem lock ?

LowPoly said:
By the way, if I want to re-unlock my bootloader, will I have to do this method again
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
with HTCdev etc ? Or is there a "fastboot" method as fastboot oem lock ?
Click to expand...
Click to collapse
Yes ... you can use the unlock_code.bin that you already have. If that doesn't work, you need to reapply to HTCDev as there is no fastboot command to unlock bootloader unless your device is S-Off.

ckpv5 said:
Yes ... you can use the unlock_code.bin that you already have. If that doesn't work, you need to reapply to HTCDev as there is no fastboot command to unlock bootloader unless your device is S-Off.
Click to expand...
Click to collapse
Okay! Thank you very much

Hi again,
I thought of something. A long time ago, white installing an Aroma-install stock ROM (link in first post), I had this problem: http://forum.xda-developers.com/htc-one-m8/help/problem-write-internal-storage-5-0-1-t3085187 . But to solve it, I need root, and for an unknown reason I couldn't uninstall root.
So since i'm not very comfortable with english, and IN CASE i have the same problem with a RUU:
if Aroma stock rom:
-> Stock rom
-> Stock recovery
-> Rooted (i can choose if i root it or not)
-> SD card problem
-> Need root to solve (terminal emulator)
-> Solve
-> No OTA update because can't uninstall root
If RUU
-> Stock rom
-> Stock recovery
-> Not rooted
-> SD Card problem
-> Need root to solve
-> Install root and solve
-> No OTA update because can't uninstall root
What will I have to do ?

Since now your current firmware is a lollipop and you need to do another OTA, don't think that problem will happen again.
But if that still happen, you only need to reunlock the bootloader and install TWRP (the latest) and reflash SuperSU.zip then follow that instructions to correct that SD problem.
(assuming you're using RUU to get back to stock)
If you want to use a backup ... read my thread on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and all the files needed are there.

ckpv5 said:
Since now your current firmware is a lollipop and you need to do another OTA, don't think that problem will happen again.
But if that still happen, you only need to reunlock the bootloader and install TWRP (the latest) and reflash SuperSU.zip then follow that instructions to correct that SD problem.
(assuming you're using RUU to get back to stock)
If you want to use a backup ... read my thread on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and all the files needed are there.
Click to expand...
Click to collapse
Thank you very much for all your quick answers. I did the fastboot oem lock command to lock the bootloader, but it appeared it failed:
C:\Fastboot>fastboot oem lock
... INFO[PGFS] partition_update_pgfs: pg1fs_securi
ty
INFOTZ_HTC_SVC_ENC ret = 0
INFO[PGFS] partition_update_pgfs: pg2fs_sec_recovery
INFOLock successfully...
INFOdeinit_lcd
INFOmipi display off
INFOmdp_clock_off
INFOturn off fd8c2308 failed 1 times. Try again...
INFOdisable_mmss_clk done
INFOpll1_disable done
INFOTZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
INFO[CRITICAL] SPMI write command failure: cmd_id = 0, erro
r
INFO= 4
INFO[CRITICAL] SPMI write command failure: cmd_id = 0, erro
r
INFO= 4
INFO[ERR] Cannot halt SPMI arbiter!!
INFO[INFO] Rebooting device
FAILED (status read failed (Unknown error))
finished. total time: 1.190s
but the bootloader is showing "RELOCKED" anyway. So I launched the RUU, but for more than 30min it was stuck on "1/8". The program said it was supposed to take only 10min, so I unplugged the phone and powered-it off.
For now my bootloader says "RELOCKED" and OS "4.16.401.13 (4.16.401.10)".
So I don't really know on which os version I am.
What I want to do now is:
Unlock my bootloader again;
Flash a 4.16.401.10 firmware
Install latest twrp recovery
Install a backup
Is it correct, or is there another way to fix all this ?

I hope no partition is corrupted when unplugged phone while RUU still running.
OS "4.16.401.13 (4.16.401.10) means incomplete process.
You can try those steps.

ckpv5 said:
I hope no partition is corrupted when unplugged phone while RUU still running.
OS "4.16.401.13 (4.16.401.10) means incomplete process.
You can try those steps.
Click to expand...
Click to collapse
Or I still can try another ruu exe, and wait longer, like 1 hour ?

LowPoly said:
Or I still can try another ruu exe, and wait longer, like 1 hour ?
Click to expand...
Click to collapse
You can try again to run the RUU but it should not take more than 20 mins.
You need to use USB 2.0 to avoid problem and if possible to run it on Win7 pc as some reported problem on Win8 and Win10 (personally I don't have problem on any windows version but USB 2.0)

ckpv5 said:
You can try again to run the RUU but it should not take more than 20 mins.
You need to use USB 2.0 to avoid problem and if possible to run it on Win7 pc as some reported problem on Win8 and Win10 (personally I don't have problem on any windows version but USB 2.0)
Click to expand...
Click to collapse
Some people said that they solved the problem by re-running the RUU.. Btw it was stuck on "sending". Anyway I'm gonna re-run the same RUU. If it's still stuck i'm gonna try to re-run the ruu by using a usb 2.0. And if it's still stuck I'm gonna try to flash the .10 firmware, twrp etc...
I'll keep you up to date
EDIT: or maybe the RUU isn't working because fastboot oem lock said FAILED ?

LowPoly said:
Some people said that they solved the problem by re-running the RUU.. Btw it was stuck on "sending". Anyway I'm gonna re-run the same RUU. If it's still stuck i'm gonna try to re-run the ruu by using a usb 2.0. And if it's still stuck I'm gonna try to flash the .10 firmware, twrp etc...
I'll keep you up to date
EDIT: or maybe the RUU isn't working because fastboot oem lock said FAILED ?
Click to expand...
Click to collapse
No .. not that. It's the USB connection usually.
You also can try fastboot flash RUU.zip - http://forum.xda-developers.com/showthread.php?t=2735235
but you need to use htc_fastboot.exe instead of normal google fastboot.exe
You can have all the needed files RUU.zip and htc_fastboot.exe there

Okay here's what I'm gonna do.
- Trying the exe RUU on another computer (with windows 8, but there I'm sure there's no usb problem).
- If not working, trying flashing the zip RUU you gave me on this same computer
- If not working, trying again the exe RUU but waiting a longer time (~3hours, it worked for someone).
- If not working, trying flashing a new firmware, twrp, and using a backup.
If all these steps don't work I'm gonna be sure that there's no more solution and that my phone is officialy dead uhh
EDIT: I'm definitely sure that this is an USB problem. On my first computer (with windows 7), I can't read some USB keys for no reason. They're not detected.

LowPoly said:
If all these steps don't work I'm gonna be sure that there's no more solution and that my phone is officialy dead uhh
Click to expand...
Click to collapse
There are many ways to update the phone... don't give up.
Try all the steps that you mentioned. They should work. If still not working, I'll tell you the other way that I have in mind i.e. flashing firmware and ROM without a need of PC.

Okay! I finish to install all the drivers and start to try the steps. I'll keep you updated. Thank you again by the way. Right now you're my last and only hope

HELP!

Hello, I am using a rooted htc one m8. I wanted to unroot it and reverted my device to android KitKat. I flashed stock recovery from the official OTA of 5.1.1. after that I tried to lock the bootloader using the command "fastboot oem lock" command using adb. then I tried to update the phone to Android lollipop. It installed and the phone shut down. now when I try to switch on the phone, It boots to stock recovery. even I cant get unlock code for bootloader to unlock it again. Please help me to solve this issue...

can you boot to bootloader ??
if yes then post the result of fastboot getvar all ( remove serialno and imei before posting )

Affanthegreat said:
Hello, I am using a rooted htc one m8. I wanted to unroot it and reverted my device to android KitKat. I flashed stock recovery from the official OTA of 5.1.1. after that I tried to lock the bootloader using the command "fastboot oem lock" command using adb. then I tried to update the phone to Android lollipop. It installed and the phone shut down. now when I try to switch on the phone, It boots to stock recovery.
Click to expand...
Click to collapse
This is really confusing. In addition to the getvar data previously requested, you should outline step by step, what exactly you did (in detail, with file names, etc.). In particular, I'm very confused about:
1) What version number you started on (when you were rooted)?
2) How did you "revert to Kitkat", what files did you use, etc.
3) What stock recovery number you flashed
4) How/where you obtained the file to update after you flashed stock recovery and locked bootloader. Did it download automatically after you flashed stock recovery, or did you put it on the phone manually (if the latter, what version number and/or file name).
Also, the following should be kept in mind:
- You need a stock never rooted ROM/TWRP backup (unrooting won't work) and stock recovery in order to properly update by OTA.
- You do not need to lock the bootloader to install an OTA update, but you do need a locked bootloader to flash an RUU or firmware.zip. So depending on what exactly you used to try to update, locking the bootloader may not have been necessary; and may be causing you more trouble than good.