Develop Bugs

How to back in Stock Rom

Hi , I installed the Revolution Android rom , i will to return in stock rom , How ?

Flash the RUU that fits your device......

Did it work???

No Details,Why?
First,you didn't say anything about your device:
-Is it s-off ?
-Is the bootloader Unlocked ?
-What's Your Hboot version ?
-What's your Current rom version ?
After all,if you think your device is ready for flashing,Here is All official roms for you:http://hipfile.com/users/kasra1/37448/One%20X
<<<FEEL FREE TO PRESS MY THX>>>

a.) Grab the stock recovery (in dev forum) and RUU for your device (google it). The RUU is the official HTC recovery file. Its an exe.
b.) Connect your phone in fastboot and flash the stock recovery. Reload into fastboot.
c.) in fastboot issue 'fastboot oem lock' , might be relock or similar going from memory
d.) Reload fastboot, run the RUU
back to stock

wintermute000 said:
a.) Grab the stock recovery (in dev forum) and RUU for your device (google it). The RUU is the official HTC recovery file. Its an exe.
b.) Connect your phone in fastboot and flash the stock recovery. Reload into fastboot.
c.) in fastboot issue 'fastboot oem lock' , might be relock or similar going from memory
d.) Reload fastboot, run the RUU
back to stock
Click to expand...
Click to collapse
Hello, can you please mention the command to run RUU? eg: to relock bootloader "fastboot oem lock" or is it just to double click the RUU exe file?

No commands for RUU. RUU is and exe file click on it once you have flash stock recovery and re-locked bootloader.
May I ask why you want to go back to stock?

vallandil said:
Flash the RUU that fits your device......
Click to expand...
Click to collapse
FLash this RUU but you need tou RELOCK your bootloader.

wolfraim said:
FLash this RUU but you need tou RELOCK your bootloader.
Click to expand...
Click to collapse
Don't forget to mention he needs stock recovery as well.

Returning to Stock from JB Maximus

Hi, I'm heading back to stock JB Sense from the original JB Maximus rom (which worked very well). I relocked in fastboot and went to flash original RUU (3.14.401.31) and I got the error message to use the correct RUU. My cid is HTC__001, it's from Clove UK. Do I need to change the HBOOT? It's from the first Maximus JB rom. It's just booting to the bootloader now. Thanks for any help!

Do this:
fastboot getvar version-main
and post the result here...

vin4yak said:
Do this:
fastboot getvar version-main
and post the result here...
Click to expand...
Click to collapse
3.09.401.100
Thanks very much!

Firs you need to update your firmware to 3.14.401.31 with Hboot 1.39..
Download (firmware): http://www.androidrevolution.nl/downloader/download.php?file=3.14.401.31.zip
And then run this RUU:
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/

Hi, thanks very much, that was the RUU I used but I'll try with that firmware and report back. Cheers for the prompt help!!

Hi, I've downloaded the firmware a few times but when I try to flash it I'm getting "cannot determine image filename for 'firmware.zip'
I moved the firmware download to my fastboot folder and renamed it firmware.zip. Then I did "fastboot flash firmware.zip" < EDIT YEP THAT was the problem
Thanks again!

Honestly at this point I'd just even go back to Maximus 4.1 at this point, but those threads all disappeared.
EDIT: I got the firmware updated, now going for the RUU

Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.

Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger

Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Click to expand...
Click to collapse
That's what I got the first time I tried to run the RUU, before flashing the new firmware. You may need firmware with a higher HBOOT to use this JB RUU. Once I flashed the firmware above, the RUU in this thread worked fine. I'm having some flashing now but heck, I had that when my phone was stock when I first got it, heh. I remember that issue now!

otarinz said:
Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.
Click to expand...
Click to collapse
Glad you sorted it out mate!
if you had just gone to stock to update... Then I will recommend you to use a custom sense rom if your attached to sense that much!
Use ViperX... It needs Hboot 1.31 at least..
Steps for flashing are the same as any other rom...
1. Wipe Data..Wipe Cache...Wipe Dalvic Cache... Or use Super Wipe Script(Recommended) : https://www.dropbox.com/s/0y31poo1kiaif4y/Super wipe script.zip
2. Flash rom. Flash Patch. (Check ViperX Thread)
3. Reboot.
Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger
Click to expand...
Click to collapse
You first have to update your firmware... Download this : http://goo.gl/M0hLq
and then run the ruu...

Hey there,
it sounds as if the HBOOT is in fact my problem. Quick question: How exactly did you flash the firmware, especially the HBOOT? I flashed the boot.img and recovery.img via command since I have no SD card access, but this doesn't seem to have changed the HBOOT.
Thanks again
Froschfinger

Relock the bootloader:
"fastboot oem lock"
Reboot RUU:
"fastboot oem rebootRUU"
Flash the firmware:
fastboot flash zip firmware.zip
You might get an error the first time you do it... try again until you get a successful message.
After successful flashing...
Go to fastboot again,,,
Now if you want to install a custom rom, you need to flash custom recovery by unlocking the bootloader... or if you want to go full stock then run the RUU...

Hey vin4yak,
that was the missing piece in the puzzle. Flashing the whole .zip file. Finally I got it working - thank you so much!!!!
All the best
Froscher

HTC One M8 Canadian RUU

I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated

marawan31 said:
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
Click to expand...
Click to collapse
Go back to stock, and take the OTAs. Then re-root and enjoy your new firmware.
Visit this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
or this thread:
http://forum.xda-developers.com/showthread.php?t=2710735

I cant do that because i am not s-off

marawan31 said:
I cant do that because i am not s-off
Click to expand...
Click to collapse
Incorrect. This is the method that you use if you are not S-Off.
If you were S-Off, you would just update firmware manually, with no need to go back to stock.

thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?

marawan31 said:
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
Click to expand...
Click to collapse
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.

xunholyx said:
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
Click to expand...
Click to collapse
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh

marawan31 said:
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
Click to expand...
Click to collapse
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2

ckpv5 said:
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
Click to expand...
Click to collapse
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys

marawan31 said:
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
Click to expand...
Click to collapse
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. relock bootloader - fastboot oem lock
4. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
5. check software update
6. accept, download, install
7. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM

ckpv5 said:
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip hbootMOD3.zip
fastboot flash zip hbootMOD3.zip <---- again for the 2nd time
fastboot reboot
4. check software update
5. accept, download, install
6. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
Click to expand...
Click to collapse
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused

marawan31 said:
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
Click to expand...
Click to collapse
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot

ckpv5 said:
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
Click to expand...
Click to collapse
oh ok thanks man!!
ill post back with the result

marawan31 said:
oh ok thanks man!!
ill post back with the result
Click to expand...
Click to collapse
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock

ckpv5 said:
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
Click to expand...
Click to collapse
yea i was going to do it and also for the sake of completeness flashing the stock recovery(3.34.661.4) after the restore, just in case someone else has the same problem

You can do that but not really needed because the signed firmware.zip will restore stock recovery.

ckpv5 said:
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
Click to expand...
Click to collapse
oh didnt know that, i guess i wont then

I just wanted to thank you guys for helping me out!
I did everything and now i am on android 5.0.1 (although i ran into a small problem: process com.android.phone is not responding, factory reset from recovery fixed it)
Hope this thread helps someone else with similar problems

https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it, I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it. There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.

Please see my comments in red font below:
350Rocket said:
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Photo link is coming up with 404 error for me. Better to do fastboot getvar all, then post the results (cut and paste from command prompt), so we can see all the info on the phone (delete IMEI and serial number before posting).
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it,
If you can be more specific about which ROMs you tried (plus info about your device from getvar as noted above), then we might be able to advise why they did not flash. Did you get error messages, and if so, what exactly were they?
I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it.
What exactly did you do (step by step, with any relevant file names, etc. - more detail is better).
I presume you intentionally relocked the bootloader in attempt to run some RUU. But would like clarification on this (and where that happened in the sequence of events)
There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
Far as I know, Canadian versions don't have RUU.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
One option (maybe the best one) is to restore a stock TWRP back from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You will need to unlock the bootloader to do this. You can either reuse the unlock bin code you used originally (if you still have it). Otherwise, you should be able to request a new bin code from HTCDev.com. Far as I know, that still works for this phone.
Click to expand...
Click to collapse

Need help with S-On HTC One M9...

I have an international stock HTC One M9. CID is: HTC__621 and firmware version: 210.709.1 - I've already found the stock recovery for 210.709.1 - I'm looking to install a custom ROM, but I may want to go back to stock later on. I found a TWRP stock backup for 210.709.1, but because I am S-ON, will I not have to manually flash the boot.img? I used winrar to look into the TWRP backup, and I could not find a boot.img. So, my question is: if I flash the TWRP backup using TWRP, will the boot.img automatically get flashed?

You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .

mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?

mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
There's no "boot.emmc.win" within the archive? I can't find it...

arif9m9 said:
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
Click to expand...
Click to collapse
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON. (I wasn't able to verify that since my phone is S-OFF.) So there should be no need to rename and manually flash the boot image if it's already inside the backup.
arif9m9 said:
There's no "boot.emmc.win" within the archive? I can't find it...
Click to expand...
Click to collapse
You can find the needed boot image in my signature.

Flippy498 said:
You can find the needed boot image in my signature.
Click to expand...
Click to collapse
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?

arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
If you use the backup from my signature you only need to follow the instructions on the first page of my google sheet to get back to stock.
Be warned: Since Android 5.1 you should only relock the bootloader if you are completely sure that your phone is able to boot to system and that you ticked the new option that allows a bootloader unlock (can be found in the developers options). Many users already got stuck with a non-booting phone that cannot be re-unlocked because they didn't fulfill these requirements. (Sidenote: If you only want to get back to stock to install new OTAs you don't need to relock your bootloader.)
Besides I read that some people stated that the AOSP roms of the M9 messed up their LTE reception (so that LTE was even unusable on other custom roms or stock rom). I don't know whether this problem is already fixed. Some weeks passed since I read about that problem so I suggest you to read the corresponding threads before you start flashing.

arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.

iElvis said:
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
Click to expand...
Click to collapse
My phone is S-ON, won't I have to flash the boot.img via fastboot?

arif9m9 said:
My phone is S-ON, won't I have to flash the boot.img via fastboot?
Click to expand...
Click to collapse
Flippy498 said:
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON.
Click to expand...
Click to collapse
iElvis said:
There is no need to flash the boot.img separately on this phone.
Click to expand...
Click to collapse
No, it's not needed. The only exceptions are backups that don't contain a boot image (like mine for example). That's why I created the google sheet with the instructions.

Flippy498 said:
No, it's not needed.
Click to expand...
Click to collapse
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?

arif9m9 said:
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
Click to expand...
Click to collapse
No.

Flippy498 said:
No.
Click to expand...
Click to collapse
But, I'm S-ON....

arif9m9 said:
But, I'm S-ON....
Click to expand...
Click to collapse
It hasn't been an S-on restriction since the M7.

iElvis said:
It hasn't been an S-on restriction since the M7.
Click to expand...
Click to collapse
Does that mean I can flash RUUs even if I'm S-ON?

arif9m9 said:
Does that mean I can flash RUUs even if I'm S-ON?
Click to expand...
Click to collapse
For your CID/MID, yes.

iElvis said:
For your CID/MID, yes.
Click to expand...
Click to collapse
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?

arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.

iElvis said:
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
Click to expand...
Click to collapse
When going back to stock, at which stage should I relock my bootloader?

arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
Because if you follow these guides your phone will state "locked" instead of "relocked" at the end. And that is only possible with S-OFF. Besides with S-ON you can only use RUUs with the same firmware version as your phone (or newer RUUs)*.
*Actually downgrades seem to be possible, too, but as far as I know only if the two first numbers of the firmware versions before and after the downgrade are the same. Like from 1.32.xxx.15 to 1.32.xxx.8 but not from 1.40 versions to 1.32 versions or from 2.xx versions to lower versions.
Edit: Looks like I didn't type fast enough.

HTC M8(TMOB101) Revert to Stock Issue

Sorry..if it's an already solved issue.
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
The device information are :
version-main: 6.12.111.4
version-misc: PVT SHIP S-ON
modelid: 0P6B10000
cidnum: T-MOB101
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Please help.

If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU

ckpv5 said:
If you can't find 6.12.111.4, restore fully stock backup
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You don't need to relock bootloader to restore nandroid
Edit : here is RUU.zip - https://www.androidfilehost.com/?fid=24399965296001026
You need to relock bootloader to install RUU
Click to expand...
Click to collapse
OK..will try the RUU zip after relocking bootloader.
Hope it works.
Will update about the same after.

Downloading...

So I relocked my bootloader.. downloaded the RUU zip.. renamed it to 0P6BIMG and put in my SD card.
Booted into bootloader and voila.. it flashed right away and now am back to pure stock.
Thank you..ckpv5 for all the help.
You saved my day.

[email protected] said:
I'm using an unlocked HTC M8 which I rooted, unlocked bootloader and installed the latest Lineage OS (Android 7.1.2).
I got a good offer for the device and would like to sell it. So I want to revert it back to stock.
Click to expand...
Click to collapse
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
[email protected] said:
The device information are :
version-main: 6.12.111.4
I could only find a Lollipop firmware for my CID which I copied into my SD card as OP6BIMG.zip
But the bootloader gives error as "Large Image Update Failed..Press power to reboot"
This goes on until I remove my SD card.
The RUU I used is "0P6BIMG_M8_UL_L50_SENSE60_MR_TMO_DE_4.19.111.3_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_449335_combined_signed.zip"
Is this because I'm trying to downgrade Android version?
Click to expand...
Click to collapse
Correct. You cannot "downgrade" by RUU with s-on.
[email protected] said:
Also should I try after re-locking the bootloader (which is something I'm a bit worried to do because I think I will end up in an even worse condition if it doesn't work...because in my experience with an M9 it never unlocks again after relocking in a custom rom.)
Click to expand...
Click to collapse
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.

redpoint73 said:
Just good practice: Always make a TWRP backup before flashing a custom ROM, root, etc.
I personally never start messing with these phones, without beforehand having some strategy to get back to stock.
Correct. You cannot "downgrade" by RUU with s-on.
Typically, no problem unlocking the bootloader on the M8 again, after relocking it.
Locked or Relocked bootloader is required to RUU with s-on.
Click to expand...
Click to collapse
Thanks for all the information.
Will definitely keep these in mind the next time I try to mess with software;

Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.

Babakkardan said:
Hello a quick question, instead of reverting to stock by RUU, can I flash a Sense-based rom via TWRP? I am presently on Lineage 15.1 with latest TWRP and S on. Thank you.
Click to expand...
Click to collapse
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.

[email protected] said:
If you are looking to go back to stock..you can use Stock RUU zip of your model to flash via recovery.
Click to expand...
Click to collapse
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader). Another alternative is to flash the RUU executable (.exe).

redpoint73 said:
You can't flash RUU.zip with recovery. It will fail if you try to do so. You need to flash RUU.zip with htc_fastboot in RUUmode. Otherwise use the SD card method (auto install in bootloader).
Click to expand...
Click to collapse
Oops my bad...I actually meant the sd card method renaming the rom to OP6BIMG.
:angel:
(Thanks for correcting)