Develop Bugs

Figuring out CID/getting OTA Updates to work again

Hello!
I recently bought a HTC One m8 used. Sadly i did not check up on the Software and it was pre-rooted and had some older version of Viper Rom on it (2.7 i think). It was also s-on and had that bug (i believe it was a TWRP one) so it would not show me the CID nor the current version it was on. So my thought was that id like to initially get to the point where i would recieve OTA Updates again so i could update the base system to install any ROM id like. After doing research for hours and trying various stuff it seemed i could not get back to stock without the CID. So what i initially did then was use Method 2 described in this thread to Upgrade the Firmware which is now 3.28.401.9. I then change the CID to the google OTA Update one and installed the Google Play Edition Rom. The ROM was kinda buggy and did not work properly tho (i assume its still an issue that the underlying Firmware is not up-to-date enough) so i went back, changed the CID to HTC__001 and installed the stock 3.28.401.9 Rom + Recovery hoping the OTA Updates would come. It has not yet happened and i am not sure it will.
So here is my question: Will OTA Updates come if my initial CID does not match the CID i currently have even if i set it with fastboot? Is there a way for me to figure out my initial CID at this point? All i really want are working OTA Updates, after that i can install any ROM anyway, but this seems to elude me.
Thanks you!
Best Regards
ly

lyeeth said:
Hello!
I recently bought a HTC One m8 used. Sadly i did not check up on the Software and it was pre-rooted and had some older version of Viper Rom on it (2.7 i think). It was also s-on and had that bug (i believe it was a TWRP one) so it would not show me the CID nor the current version it was on. So my thought was that id like to initially get to the point where i would recieve OTA Updates again so i could update the base system to install any ROM id like. After doing research for hours and trying various stuff it seemed i could not get back to stock without the CID. So what i initially did then was use Method 2 described in this thread to Upgrade the Firmware which is now 3.28.401.9. I then change the CID to the google OTA Update one and installed the Google Play Edition Rom. The ROM was kinda buggy and did not work properly tho (i assume its still an issue that the underlying Firmware is not up-to-date enough) so i went back, changed the CID to HTC__001 and installed the stock 3.28.401.9 Rom + Recovery hoping the OTA Updates would come. It has not yet happened and i am not sure it will.
So here is my question: Will OTA Updates come if my initial CID does not match the CID i currently have even if i set it with fastboot? Is there a way for me to figure out my initial CID at this point? All i really want are working OTA Updates, after that i can install any ROM anyway, but this seems to elude me.
Thanks you!
Best Regards
ly
Click to expand...
Click to collapse
as far as I know the stock 3.28.401.9 Rom + Recovery is the newest version. Your not getting updates because their are none

clsA said:
as far as I know the stock 3.28.401.9 Rom + Recovery is the newest version. Your not getting updates because their are none
Click to expand...
Click to collapse
That makes me happy to hear. I'll just wait and hope for an early Lollipop then. Thank you!

lyeeth said:
That makes me happy to hear. I'll just wait and hope for an early Lollipop then. Thank you!
Click to expand...
Click to collapse
I do see a 3.29.401.9 firmware but I think it was a small OTA fix
try pushing your date ahead and trying to find it

[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.

[Q] Stuck with a pretty much unusable phone abroad

hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks

Run the ruu for your cid and revert to stock

rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
Click to expand...
Click to collapse
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.

rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
You flashed firmware for your specific device in the firmware/RUU thread before clean flashing to the update on viper? Like iElvis said you are describing what some users have posted in a few threads where users checked the 1.40 kernel and 1.40 in base(I think, I haven't flashed viper), but didn't properly flash the firmware for their device via fastboot or RUU back to stock to get official OTA(if OTA was released from HTC for users specific device.). Hope you get it sorted out
Do you have a back up of your system before viper update? (1.90 or below) or back up ROM ?
---------- Post added at 11:05 PM ---------- Previous post was at 10:46 PM ----------
iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
Correct me if I'm wrong, but I thought viper allowed user (sprint for example) to run their "1.40 base" on old firmware, they just had to select 1.32 kernel in aroma and would lose out on newer features

that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..

iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
im pretty sure, yes. Because It shows so in Download mode and in the about section of settings of my phone. I came across pre update error 1.90 and it fixed itself when the phone rebooted in downlaod mode.

Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it

rpimentel1 said:
that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..
Click to expand...
Click to collapse
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243

rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
EDIT:Are you on tmobile?Because than you need to flash back 1.32 firmware, as our installer will install older tmobile kernel in order for wifi calling to work, or you need to manual flash international boot.img if you want to keep 1.40 firmware.

BUBBA DUB'S said:
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
ivicask said:
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
Click to expand...
Click to collapse
kash20 said:
Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it
Click to expand...
Click to collapse
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?

rpimentel1 said:
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?
Click to expand...
Click to collapse
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545

BUBBA DUB'S said:
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Click to expand...
Click to collapse
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.

rpimentel1 said:
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.
Click to expand...
Click to collapse
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:

BUBBA DUB'S said:
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:
Click to expand...
Click to collapse
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???

rpimentel1 said:
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???
Click to expand...
Click to collapse
Check out this link it might help , also in the first link I posted I think I saw someone reference what you are asking but I'm not 100% sure.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698

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 !

Downgrade from official 6.0 MM to 4.4.4 official KK backup

Hey, as the OP says i'd like to downgrade my phone to KK, i feel battery life was so much better back then and lasted lonnger in daily use, was less heat in my phone as well. My CID is htc_332 (latin america), but i've couldn't found any stock backup for my phone in the sticky thread. Can anyone Guide me? if i passed over my bad guys. thank you.

Thepho3nix said:
... My CID is htc_332 (latin america), but i've couldn't found any stock backup for my phone in the sticky thread....
Click to expand...
Click to collapse
You can't find it because you don't really read the stickied threads ...

ckpv5 said:
You can't find it because you don't really read the stickied threads ...
Click to expand...
Click to collapse
Hey I've just found your thread and I'm actually downloading the 1.57.599.1_ckpv5.zip (I guess is 4.4.4kk)
I'm actually on leedroid r60. I'd like also to flash the stock recovery and relock my bootloader. So in 4th post there's your recovery collection. What recovery should I download? And flash after downgrading from MM to KK? Is there a problem if I downgrade? My Hboot is 3.19. Thank you.

Frankly speaking I have no idea what will happen when you restore a KitKat ROM on a Marshmallow firmware. It may work and it may not. I never try that because my device is S-Off (I can properly downgrade with S-Off).
Also I don't know whether x.xx.599.x is correct for your device as for HTC__332 there are 3 different versions x.xx.598.x , x.xx.599.x and x.xx.600.x - only you should know better which is yours (but I don't have any x.xx.598.x in my collection)
You can always use a stock recovery that one version higher, for example for this backup you can use 2.25.599.1 stock recovery.
Lastly ... don't relock bootloader until you satisfied with your test. I don't advise to relock bootloader in any situation unless you're flashing firmware or install RUU (while on S-On)
Gotta go now ... good luck.

ckpv5 said:
Frankly speaking I have no idea what will happen when you restore a KitKat ROM on a Marshmallow firmware. It may work and it may not. I never try that because my device is S-Off (I can properly downgrade with S-Off).
Also I don't know whether x.xx.599.x is correct for your device as for HTC__332 there are 3 different versions x.xx.598.x , x.xx.599.x and x.xx.600.x - only you should know better which is yours (but I don't have any x.xx.598.x in my collection)
You can always use a stock recovery that one version higher, for example for this backup you can use 2.25.599.1 stock recovery.
Lastly ... don't relock bootloader until you satisfied with your test. I don't advise to relock bootloader in any situation unless you're flashing firmware or install RUU (while on S-On)
Gotta go now ... good luck.
Click to expand...
Click to collapse
My downgrade went fine on the first time, but things went bad after i flashed stock recovery 2.25.599.1 for 1.75XXX nandroid backup. it popped up an 4.4.3 update and was about 560mb, the ota installed correctly, but for my surprise wifi wasn't working, and the phone got really really slow, then i don't know what went wrong, i was happy because KK was stunning, blazing fast and solid. But at the end i was forced to upgrade to my own nandroid backup of MM and then flash leedroid r60 again. So the wifi is up and running again. I feel bad now, i thought i could stand with KK in my phone again.

That's true ... you're not supposed to install OTA.
OTA will breaks thing because some firmware parts cannot be replaced when on S-On

ckpv5 said:
That's true ... you're not supposed to install OTA.
OTA will breaks thing because some firmware parts cannot be replaced when on S-On
Click to expand...
Click to collapse
What do you suggest? I'd like to install kk on my M8 and put everything back to stock. If possible stay with 4.4.4 on my phone. I saw some files named as signed RUU's , what's the difference with normal RUU files?