Develop Bugs

[Q] Installing OTA - Red Triangle

Hi All,
I am currently S-Off and on an Unlocked Bootloader. I have the Harmon Kardon sound mod applied.
I used to have TWRP recovery and last night flashed on a stock recovery to my device.
When I click on the OTA download install my phone reboots to recovery with the Triangle and a Green Line. This progresses to around 30-40% completion and then stops and shows the Red Triangle which means I have to Vol Up + Power to restart.
Settings>About>Software Info> Software Number>
Mine is 1.54.61.5
CID is: ORANG001
Anyone have any idea where I am going wrong?

Firstly, you're not searching as this question has been asked and answered a lot.
Secondly, your ROM is detected as not stock and the patch is failing.
You'll need to return to stock, thus process is described in lots of threads.

BenPope said:
Firstly, you're not searching as this question has been asked and answered a lot.
Secondly, your ROM is detected as not stock and the patch is failing.
You'll need to return to stock, thus process is described in lots of threads.
Click to expand...
Click to collapse
I searched and found some conflicting comments with some stating that the bootloader needed to be re-locked, and some saying my CID needed to be changed to 1111.
I don't have a stock backup so I'm stuck for what I need to do, I'm presuming I need some stock apps that may be got removed?
I'll keep searching, thanks for taking the time to reply.

KinetiClutch said:
I searched and found some conflicting comments with some stating that the bootloader needed to be re-locked, and some saying my CID needed to be changed to 1111.
I don't have a stock backup so I'm stuck for what I need to do, I'm presuming I need some stock apps that may be got removed?
I'll keep searching, thanks for taking the time to reply.
Click to expand...
Click to collapse
Check this : http://forum.xda-developers.com/showpost.php?p=54571670&postcount=1482

Hi
I've ensured I have the correct recovery.
When the installation fails it is because of this error: Verifying Current System...
/system/customize/ACC/default.xml has unexpected contents. Installation Aborted.
I've made sure my MID and CID are correct and I have a stock recovery
Is this because I have the HK Sound Mod?

KinetiClutch said:
Hi
I've ensured I have the correct recovery.
When the installation fails it is because of this error: Verifying Current System...
/system/customize/ACC/default.xml has unexpected contents. Installation Aborted.
I've made sure my MID and CID are correct and I have a stock recovery
Is this because I have the HK Sound Mod?
Click to expand...
Click to collapse
Yep .... HK mod modified the default.xml
That's why I gave you that link so you can revert to real Stock.

Is there away to copy the default.xml from the stock backup links and paste it into phone?
Or is this likely to cause an issue.

KinetiClutch said:
Is there away to copy the default.xml from the stock backup links and paste it into phone?
Or is this likely to cause an issue.
Click to expand...
Click to collapse
Sure, with a root explorer, or adb, or lots of other ways, assuming you have the kernel mod for writing system. You might get bored of that though, I suspect more than one file is altered or missing.

[Q] Will OTA updates work after flashing back and forth?

Hi all,
so I got my M8 like three weeks ago and made the ultimate mistake of not backing up MY factory ROM before flashing stuff. I went ahead and, following a guide from 'teh internets', turned my phone into a Google Play Edition after a successful S-Off with SunShine. About a week later, I started missing some Sense features and tried to revert back to stock which proved difficult at first due to partition size issues. Finally, I was successfully following a mixture of several guides in this very forum, flashing different combinations and versions of stock ROMs, firmwares and recoveries. I'm on Sense again. Last thing I can't get rid of is a message in HTC Tell that's talking about a testing device and how I could not turn off HTC Tell for that reason.
Long story short, I do now have a phone that reads:
Code:
*** Software status: Official ***
*** UNLOCKED ***
M8_UL PVT SHIP S-OFF
CID-HTC__102
HBOOT-3.19.0.0000
RADIO-XXX
OpenDSP-XXX
OS-3.28.401.7
eMMC-boot 2048MB
Oct 10 2014,00:20:35.0
Unfortunately, I do not exactly remember which Recovery I flashed last. I'm pretty sure it was one from the Stock Backup & OTA Collection thread. If I go into recovery, I get a red triangle and nothing happens.
Now for my question, I want some features of Lollipop really bad and I know HTC is going to come out with their Lollipop-Sense in about two weeks. I would gladly wait and go for it instead of starting over and turn my phone into a GPE again. Question is, will I get the Sense OTA or is there anything that will keep me from it?
Thanks a lot for reading and any information I got (and hopefully will get in the future) from the folks on this awesome forum!

If you are on the appropriate stock ROM for your CID, and corresponding stock recovery, you will get the OTA.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
jndvid said:
Unfortunately, I do not exactly remember which Recovery I flashed last. I'm pretty sure it was one from the Stock Backup & OTA Collection thread. If I go into recovery, I get a red triangle and nothing happens.
Click to expand...
Click to collapse
Red triangle is stock recovery. However, its not clear whether its the right stock recovery. You need to be on the stock ROM for your CID, and the recovery needs to be the one that matches that software number. Just find the stock ROM (and corresponding recovery) for your CID on the following thread.
http://forum.xda-developers.com/showthread.php?t=2701376
There is no harm in restoring the correct stock ROM and recovery over whatever you have now (whether the current state is correct for your CID or not). But being on the correct stock ROM and recovery will put you in the right place for OTA.

Thanks for the explanation.
So it is safe to assume that if I flash TWRP now and restore the 3.28.401.6 nandroid and recovery from this thread, I should A) get the OTA from .6 to .9 and later on B) the Sense-Lollipop OTA?
Sorry for the redundancy of my question but without a speedy internet connection, downloading ROMs is a time-consuming project, so I want to get it right the first time now.

jndvid said:
So it is safe to assume that if I flash TWRP now and restore the 3.28.401.6 nandroid and recovery from this thread, I should A) get the OTA from .6 to .9 and later on B) the Sense-Lollipop OTA?
Click to expand...
Click to collapse
If you restore to .6, it won't install the .6 OTA since its already on that version. But yes, it should install any "more up-to-date" OTAs (and then any future OTAs as they are released) in sequence once you return to stock and check for updates.

Thanks again. I will report back after flashing.

Well, it worked - I think. However, a little more research showed that the red text in HTC Tell is present because I unlocked my phone, particularly the bootloader, via HTCDev. I will consider to revert that change in the future.
I restored (via TWRP) the stock 3.28.401.6 and flashed the corresponding stock recovery. Unfortunately, no update is to be found yet (according to the OTA collection, there should be an update from .6 to .9 which I hoped to get automagically or on manual query in phone settings).
For the time being, I can download the OTA myself from the awesome collection and then update manually through stock recovery, I suppose.

jndvid said:
Well, it worked - I think. However, a little more research showed that the red text in HTC Tell is present because I unlocked my phone, particularly the bootloader, via HTCDev. I will consider to revert that change in the future.
Click to expand...
Click to collapse
The device will come up as a "test device" since its s-off.
jndvid said:
I restored (via TWRP) the stock 3.28.401.6 and flashed the corresponding stock recovery. Unfortunately, no update is to be found yet (according to the OTA collection, there should be an update from .6 to .9 which I hoped to get automagically or on manual query in phone settings).
Click to expand...
Click to collapse
I'm not that familiar with the WWE updates, as its not my version. So I don't know of the .7 and .9 updates deployed to all folks in all regions that have the WWE version, etc. You might check with folks that know more about the WWE updates.

OTA Update 5.1 Help

So right now my phone says it's getting the 5.1 update OTA. I am using TWRP. When I try to install the update it goes to the TWRP everytime. I dont use custom roms, just what came with the phone. How do I update the phone?

Found out I need to return it to stock recovery before I can install an OTA update. So I tried using instructions found on the web made for the noob I am. But when I use the CDM console it tells me that it can't open the recovery file.
\
What do?
Edit: I just need step by step help on what to do. I just rooted it so I could have BB10-like gestures and stock android navigation buttons. I didnt know it would screw me over for OTA updates
Edit 2: I got it work, now the update fails and goes to bootloader and tell me this, i am using the carrier supplied OTA update.
"this package of fir"htc_himaulatt" devices; this is a "htc_himauhl""

BriniaSona said:
Found out I need to return it to stock recovery before I can install an OTA update. So I tried using instructions found on the web made for the noob I am. But when I use the CDM console it tells me that it can't open the recovery file.
\
What do?
Edit: I just need step by step help on what to do. I just rooted it so I could have BB10-like gestures and stock android navigation buttons. I didnt know it would screw me over for OTA updates
Edit 2: I got it work, now the update fails and goes to bootloader and tell me this, i am using the carrier supplied OTA update.
"this package of fir"htc_himaulatt" devices; this is a "htc_himauhl""
Click to expand...
Click to collapse
This phone is a real hassle to update.
You won't be able to do OTAs until you return it to stock, and to do that, you'll have to run an RUU so that it removes TWRP and root. Make sure to re-lock the bootloader. So run the RUU of the latest version if it exists if you can then you won't have to OTA, or run the RUU that matches your phone's OS version and then take the OTA.

TWRP is removed using a stuck recovery image
the bootloader is relocked using commands from a video I watched on how to do it, it displays relocked when open.
however, now instead of getting the yellow error from before, I now get sent to the bootloader screen and nothing happens.
Edit: when I try to boot into recovery through the boatloads it gives me an error message saying it can't and takes me back to the white screen.

BriniaSona said:
TWRP is removed using a stuck recovery image
the bootloader is relocked using commands from a video I watched on how to do it, it displays relocked when open.
however, now instead of getting the yellow error from before, I now get sent to the bootloader screen and nothing happens.
Edit: when I try to boot into recovery through the boatloads it gives me an error message saying it can't and takes me back to the white screen.
Click to expand...
Click to collapse
I guess you missed the whole part about restoring your system partition to stock
From the backup you made after installing TWRP .
You need an untouched system partition and Stock recovery.
At this point you should look for the RUU for your phone
Sent from my HTC One M9 using Tapatalk

GG didnt make a backup.
Can you link me to one at all, and all the instructions needed to make things work. Sorry for the hassle, I really don't want to do this without help now, incase I mess things up more than they already are.
EDIT: this it it right? http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Except there's now Canada option.
EDIT 2: I wish it was as easy as BlackBerry which everyone seems to think it out of date, http://crackberry.com/install-leaked-os-autoloader

BriniaSona said:
GG didnt make a backup.
Can you link me to one at all, and all the instructions needed to make things work. Sorry for the hassle, I really don't want to do this without help now, incase I mess things up more than they already are.
EDIT: this it it right? http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Except there's now Canada option.
EDIT 2: I wish it was as easy as BlackBerry which everyone seems to think it out of date, http://crackberry.com/install-leaked-os-autoloader
Click to expand...
Click to collapse
Theirs a thread in the general forums for Canadian files
Sent from my HTC One M9 using Tapatalk

So I'm downloading the bell one and using download mode and adb to input the show commands?
''Fastboot output
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) version-main: 1.32.666.30
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001''
Edit: Didnt work, so I am using these commands, but now I need to s-off, so I'm going to do that now. http://forum.xda-developers.com/showthread.php?t=1907796
if you read this and I havent added and Edit: 2, then answer this.
what command erases everything and put it back to default, like how it was when i bought the phone.
Edit 2: re-unlocked the bootloader.
Device is giving me the same error as when I started. "this package of fir"htc_himaulatt" devices; this is a "htc_himauhl"

I downloaded a stock bell RUU. Went into adb and used
"fastboot update "filename""
I got an error saying there wasnt enough space.
EDIT: failed to load '0PJAIMG.zip': Not enough space
and when i try to sideload it it says the file can not be read.
Can someone just tell me what to do from the beginning, instead of telling me to look myself. Looking myself has only gotten me more lost and confused.
I need step by step instructions with links and files.
Please.
I just want my phone to be the way i bought it, No root, no bootloader changes, no twrp, just stuck everything.

MY phones current status.
Rooted, Bootloader Unlocked, Stock Recovery installed.
What do I do from there, where do I find the correct Bell RUU, how do I flash it, where does it go so it can be flashed.

BriniaSona said:
MY phones current status.
Rooted, Bootloader Unlocked, Stock Recovery installed.
What do I do from there, where do I find the correct Bell RUU, how do I flash it, where does it go so it can be flashed.
Click to expand...
Click to collapse
I think I found the correct RUU for your firmware version. The problem is you will have to pay if you want it since the website isn't for free. Sorry that I wasn't able to find a cheaper source. (Link)
Edit: Forget what I said. I just saw that there is a TWRP backup in this thread. Using it should be much cheaper than the RUU.

HTC One M8s OTA not working

Hi,
I recently managed to root my HTC One M8s with TWRP recovery and everything works perfectly, except that I can't install the new OTA (1.16.401.1).
After searching I have flashed my recovery back to the stock for my version (which is 1.11.401.1) and tried applying the OTA again, but it still fails.
I downloaded the recovery from this website: ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/HTC%20Recovery/ (I can't post URLs yet).
Below is the error I receive when trying to update on stock recovery, TWRP recovery also gave the same error when I tried updating there.
(Code -1)
E:Find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.105.019
Verifying current sytem...
Package expects build fingerprint of htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/531284.2:user/release-keys or htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys;
This device has htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/53128
E:Error in @/cache/recovery/block.map
(Status 7)
From what I can see my build fingerprint is incorrect, but I have no idea how to fix it...

Seems to me it's likely that you've altered some system files while rooted and the Ota doesn't like it.
Now, I don't own an M8s...i have an M8, but I'd say the easiest route would be to flash your stock ruu again. After that the OTA should work.
It's that or figure out what system changes have been made and correct it. Xposed can mess you up, Uninstalled system apps can stop the Ota... MODS that changed system files... Etc. The Ota us looking for a stock system, then it updates it.
Good luck!

Thanks for the answer, I will see if I can try this solution tomorrow. I just have 2 questions:
What does the RUU do exactly? Should I see it as a complete stock reset of my phone?
And can I simply flash it using fastboot or is there a special method for a RUU?
My previous phone had an automated root and I always updated with OTA afterwards so I never flashed before now.

Im on the same boat. Tried to sim unlock by rooting and playing with CID but didnt work, now ive a rooted m8s and no ota. Tried to ruu but kept getting an error something like not enough space although i had 10gb free, cleared cache rebooted. Cant even factory reset. If anyone know how to unroot it and bring it back to stock that would be fantastic. Kind of want to delete the "flag" too make it "LOCKED" and "OFFICIAL" incase for warranty. Any ideas?

You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?

voidzero said:
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
Click to expand...
Click to collapse
When I got my phone I updated with OTA to version 1.11, after that I flashed TWRP recovery and rooted my phone. Now that OTA 1.16 is out I tried to update but couldn't, so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
Manual OTA flash worked on my previous phone with root which was an ASUS Padfone Infinity A80 as ASUS would release them on their own website for you.
Apparently HTC does not do this, or I am not looking in the right place.
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash original recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.

Codyksp said:
(...) so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
(..)
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash custom recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
(...)
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Click to expand...
Click to collapse
If you restore a RUU, and afterwards don't flash your recovery and boot partitions, You will see "Software status: official" in fastboot.
Now here's the trick: if you just boot a custom recovery with "fastboot boot my_recovery.img" (TWRP for example) then it will boot TWRP, but you can make the modifications to your system partition without losing "Software status: official" in fastboot.
So: If you just boot your recovery with 'fastboot boot' and don't flash anything, you can make all the modifications you want and still be able to install OTAs later, I think. I've rooted my phone, even installed XPosed, done all kinds of funky things to it but Fastboot still shows me that I'm on official software.
How does that sound?

So since there is no decent guide at all about flashing RUU for a HTC One M8s (the s makes a difference!). I have assumed that I need to have the bootloader locked first, as I unlocked it. According to all the M8 guides I have to gain S-OFF before I can lock the bootloader again. So I followed a guide to wipe with TWRP and flash a ROM called InsertCoin so that I can S-OFF my phone.
Now after going through the ROM's setup my phone is stuck in a bootloop, constantly trying to boot up. There is NO way at all for me to get it to stop, it just keeps booting the entire time. Not a single combination of buttons is working. Good thing the battery is non removable. How am I supposed to fix this? I've tried every volume up/down/power combination possible. The phone just boots to the HTC - Power by Android screen, shuts off after about 5 seconds and then repeats the same thing over and over. I can't turn it off and I can't get to the bootloader either.
What I need is a guide that tells me all the steps required to get an HTC One M8s (NOT M8!) back to 100% stock. This means, stock ROM, stock recovery, locked bootloader and S-ON. I am getting extremely frustrated by the lack of information and the amount of redicilous things I need to do just so I can root my phone and have OTA as well.
All I want is root on my phone for 1 app that I use with my car radio and I want to be able to update to the newest OTA afterwards, is that really so much to ask?
I am fine with installing a custom ROM with root and easy updates too, as long as the damn phone will boot after installing it and it's actually made for the M8s.

Deleted......

Well I finally managed to get the damn thing to the bootloader, and I've used "fastboot oem lock" to relock my bootloader. It now shows ***Software status: Modified ***, *** RELOCKED *** and ***Security Warning ***.
I will now have to go to my parents where my laptop is to be able to copy the RUU to my SD card, from what I understand it has to be named 0PKVIMG.zip and then it should automatically install.

Now the phone says it can't find the image or the image is incorrect.... It searches for, 0PKVDIAG.zip, 0PKVDIAG.nbh, 0PKVIMG.zip or 0PKVIMG.img. and it seems to find 0PKVIMG.zip and loads it but it cannot find the .img file and does absolutely nothing. Am I supposed to have both?

So it turns out that the RUU zip from http://ruu.lalleman.net/HTC_M8S%28QL_UL%29/RUU/ is actually not correct and I had to use rom.zip which was inside the folder. The phone is now running the "update" as it calls it. Fingers crossed...

Yes, possible you need to use rom.zip inside the zip, depending on the version, but I think this applies to 1.16 which I advice against using for reasons previously specified.
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
By the way, I did write an RUU restoration thread specifically for this subject. Did you not find it?

Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.

Codyksp said:
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Click to expand...
Click to collapse
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.

Mr Hofs said:
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Click to expand...
Click to collapse
So in that case I just unroot it before updating then?

Codyksp said:
So in that case I just unroot it before updating then?
Click to expand...
Click to collapse
Read my post again...... "a never rooted rom" so that means you need a stock rom before its ever been rooted. NOT an unrooted one because it leaves traces which will cause the ota to fail !
People should learn to create a nandroid backup before flashing ANY mods/superuser.zip/roms etc......etc

Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
I would say that M8 roms wouldn't be compatible, and could even mess up your device badly. Sorry!

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
Your point of view is a bit off if you ask me. Developers (in this case HTC) do not have to support custom modding of your phone. They support the device in the state you buy it !
If you want to mod it that's YOUR call not theirs. Do some homework before modding it. Getting a phone back to stock for future updates is relatively easy but many people don't read first how to as they think it's not important.
HTC has no obligation at all towards you regarding custom software !
And indeed M8 roms do NOT work on your M8s !

Unrooting, System: Official / Locked / S-ON / - how to?

Hi, it's been three hours already and I'm desperate. I'm sure that thousands of people asked this, but I always found fragmentary posts or not a step-by-step guide (and proper succession is mandatory I suppose?)
So the question is - how to unroot the phone for warranty?
1. It was rooted with Magisk, Unlocked, S-On, Modified.
2. I used my ROM that I backed up through TWRP to get it back on my phone and installed the original recovery. Then, to be sure, I installed RUU (for HTC__034, my CID)
3. The phone is now only Re-locked and everything is wiped
What can I not figure out:
How to LOCK it (not relock)
How to get it back to OFFICIAL (not modified)
If I root it again now and use Sunshine to LOCK it, it will be S-OFF - is it possible to get it back to its original state even if it's locked? What about S-OFF, can I get it back to S-ON afterwards?
Restoring the backup made when I rooted the phone also doesn't work, even the one from the local thread. It says "extractTarFork() process ended with ERROR: 255". When I put the RUU on the SD card and name it 2PS6IMG.zip and in download mode press up, it says "FAIL19 RU_MAIN_VER_FAIL"
Thank you all for anything that can help.

Matt.Murdock said:
Hi, it's been three hours already and I'm desperate. I'm sure that thousands of people asked this, but I always found fragmentary posts or not a step-by-step guide (and proper succession is mandatory I suppose?)
So the question is - how to unroot the phone for warranty?
1. It was rooted with Magisk, Unlocked, S-On, Modified.
2. I used my ROM that I backed up through TWRP to get it back on my phone and installed the original recovery. Then, to be sure, I installed RUU (for HTC__034, my CID)
3. The phone is now only Re-locked and everything is wiped
What can I not figure out:
How to LOCK it (not relock)
How to get it back to OFFICIAL (not modified)
If I root it again now and use Sunshine to LOCK it, it will be S-OFF - is it possible to get it back to its original state even if it's locked? What about S-OFF, can I get it back to S-ON afterwards?
Restoring the backup made when I rooted the phone also doesn't work, even the one from the local thread. It says "extractTarFork() process ended with ERROR: 255". When I put the RUU on the SD card and name it 2PS6IMG.zip and in download mode press up, it says "FAIL19 RU_MAIN_VER_FAIL"
Thank you all for anything that can help.
Click to expand...
Click to collapse
To get from Unlocked (or Relocked) & Modified to S-ON/Locked/Official:
1) Use Sunshine and choose S-OFF/Locked - this will give you Locked status instead of Relocked
2) Run the correct RUU for your CID/MID - this will give you Official status instead of Modified
3) From Download Mode use "fastboot oem writesecureflag 3" - this will give you S-ON
Sent from my Sprint HTC 10 using Tapatalk

The Fer-Shiz-Nizzle said:
2) Run the correct RUU for your CID/MID - this will give you Official status instead of Modified
Click to expand...
Click to collapse
Thank you for your answer. I did exactly this. Many, many times. Yet I'm getting the error mentioned in the previous post - I'm simply not able to install the official RUU...

Matt.Murdock said:
Thank you for your answer. I did exactly this. Many, many times. Yet I'm getting the error mentioned in the previous post - I'm simply not able to install the official RUU...
Click to expand...
Click to collapse
You are not mentioning your current firmware version and what ruu exactly you are trying to flash ? Main version error means the numbers ain't matching.