Develop Bugs

Confirm this?? If S-off, I can flash recovery with bootloader locked?

It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....

syntropic said:
It is so hard to re-locate threads between this general HTC One M8 and the variant for the carriers....so I hate adding to repetitive questions in threads....
BUT... I was certain that I read countless times that you could flash recoveries from ADB with bootloader locked provided you had S-off.
And now I am getting this error:
FAILED (remote: not allowed)
I had two updates and wanted to flash stock recovery then reflash TWRP.... I thought it would take 20 minutes tops....
Click to expand...
Click to collapse
SO I said f*ck it... no big deal, and I unlocked the bootloader and flashed the stock recovery (btw, I flashed a stock recovery I found in the TMO forums that had a version number identical to the software version I had installed, this is correct right????). I had no problems flashing the stock recovery....so apparently, you need to unlock the bootloader whenever you are flashing recoveries irrespective of whether you have S-off.
But then, I tried to run the OTA, and got the red triangle error.... — Is this because my bootloader is now unlocked?
This seems to be going against everything I have read numerous times (namely that if you are S-off, the bootloader is not that big of an issue). I am assuming this is because my bootloader is now unlocked... so I will unlock it.

IGNORE

Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: ★★★★★★★★★★★★★
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s

syntropic said:
Just adding my experiences as I don't want to start another thread with new information...
I have unlocked bootloader
flashed stock recovery
relocked bootloader
went into setting==>apps and enabled the 10 or so apps that I had previously disabled...
I even deleted all downloaded OTA updates and had the phone re-download them again.
However, I still cannot install OTA updates. I know that the standard instructions are to flash a stock rom or restore a nandroid that is stock, but my phone is stock!!! Nothing has touched any of the original software on it other than the stock recovery, which I flashed back on it...
I think my phone is techincally still rooted because it has the SuperSu binary installed... But (again) from everything I read, the way I understood it was that in order to get OTA updates you needed to have stock (or pretty close with no uninstalled/frozen/disabled system apps), and the stock recovery.... AND that is it....
Anyway, I did a fastboot getvar all if that is helpful.... I have pasted it below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44VWM00543
(bootloader) imei: DO NOT POST IMEI NUMBER
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
Click to expand...
Click to collapse
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.

BerndM14 said:
What OTA update are you trying to install?
version-bootloader: 3.18.0.0000 - latest
version-main: 2.22.531.5 - latest
Remove your IMEI from your post.
Click to expand...
Click to collapse
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But as of now, I have re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number of the recovery matched exactly the version number of the software that is showing on my hboot screen. I thought that was a educated guess that wouldn't be too risky.
I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused....because aside from the recovery, I didn't touch any of the firmware.
NB: I do have a nandroid that I made that is entitled: 2014-09-24-14-06{whatever) release keys I don't know what release keys means.... I have made a lot of nandroids in my time... 95% of them on HTC devices using TWRP (at least since its inception), and I have never seen a "release keys" appended to the name of an nandroid like that.
I could restore this nandroid... but then I would have to unlock the BL, fastboot flash TWRP, flash SuperSU (although I know TWRP now prompts you which is very cool), then restore the nandroid, fastboot flash the stock recovery, then (apparently) re-lock the bootloader, and get the OTAs.... if the OTAs even work...

syntropic said:
I removed it just before I saw your post... but thanks! And thanks for replying.
I am trying to install the 2.22.531.6 OTA software.
I don't know if the bootloader/hboot version has any correlation to the software, but I have not touched anything... I did two updates, then a three days later did HTCDev unlock of bootloader, I flashed TWRP, flashed SuperSU, got Sunshine S-Off, then relocked bootloader. As mentioned I also disabled a bunch of apps. But I have no re-enabled them.
The only variable that wasn't precisely in my control was the stock recovery. I didn't know which one to flash, but made the common sense decision to flash the 2.22.531.5-TMO-Recovery.img since the version number matched exactly the version number of the software as shown in the hboot screen. So I assumed it was the right one. I haven't flashed or changed the hboot, or flashed any RUUs....nothing else.
really confused.
Click to expand...
Click to collapse
Ok stock recovery flashed back is good then, you need to be completely stock to do OTA's i.e If you made changes to the system even removed pre-installed apps like Facebook, Twitter etc you need to restore those back as well. As the OTA will do a verification check to see that all those things are intact before it continues the update. If it's not stock then you're not getting OTA. Bootloader status won't make a difference, you can keep it unlocked.
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.

BerndM14 said:
{...}
When you do the OTA and it fails what error does it give? When an OTA gets applied it reboots the system to the stock recovery and proceeds to apply the update, if it fails you can view the error. You can press Volume Up and then TAP the power button and it'll show you the recovery log details at the bottom, there it should tell you what errors you have during the OTA installation.
/system/app/blahblahblah has unexpected contents, or cannot find /system/app/blahblah etc
If it requires missing files etc just get them and add them back on the device. Like I said above, you need to be stock.
Click to expand...
Click to collapse
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.

syntropic said:
Cool... NEAT trick I didn't know about that...!!! thank you for the tip. They should put that in the documentation with the f*ckin phone.
The recovery/installation log says (in relevant part):
Verifying current sytem. . .
"/system/build.prop" has unexpected contents
Installation aborted.
I thought about why the build.prop would have changes, and remembered that I have an app called Android Tweaker Pro (but it is being renamed since Google now prohibits apks with 'Android' in the name). It requires root to make its tweaks. Its a good app, but it does make a lot of changes to build.prop. But... am pretty sure it has a reset/restore to default option on it... I am going to check and try that.
Will let you know...
Sh*t.... still can't believe I didn't know about the installation log screen... very impressed.
Click to expand...
Click to collapse
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
---------- Post added at 01:22 AM ---------- Previous post was at 01:20 AM ----------
BerndM14 said:
And so we all learn new things everyday It's great!
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 2.22.531.6]
There's a stock backup for 2.22.531.5 in there that you can restore to go back to stock for the OTA. Changes to build.prop usually is changes to system. Perhaps you could also try and pull the build.prop from there and restore that and see if it works
Click to expand...
Click to collapse
They also have the 2.22.531.6 stuff there so just make sure you select the correct versions, it's under the "clickable" buttons so...

OK.... I used a app called Nandroid Manager (very helpful app) which extracts anything you want from a nandroid. Since I had already disabled the Android Tweaker 2 App, and realized I had an original build.prop in that nandroid, I just extracted that and renamed the old one, and used the extracted one. I did a chmod 644, and then attempted OTA install.. And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
EDIT: Actually.... I would really like to avoid the htc unlock token as that erases the data partition as some kind of existential pennace ordained by HTC for unlocking your bootloader.

syntropic said:
[...] And it went fine! Very nice... A bigger headache then I had anticipated... but it serves me right for forgetting that I had root apps modifying sh*t that I had not considered.
Very big thanks for the tips.
Click to expand...
Click to collapse
Glad it worked out :good:
Also...lastly, since I stupidly relocked the bootloader, I am now no longer root but cannot flash TWRP because the BL is locked. I cannot use Scotty1223's method (I don't think) because it requires su permissions in adb shell.
I could probably just use the htc .bin file.... but out of curiousity, is there any easy way to get temp root in this case?
Click to expand...
Click to collapse
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
Click to expand...
Click to collapse
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.

BerndM14 said:
Glad it worked out :good:
Yeah you can use the unlock binary you had if you went through htc unlock method, or you can just do it again if you want(another headache).
You'll have to read up on temp root methods, I haven't used any at all, so I'm not entirely sure, sorry.
---------- Post added at 02:01 AM ---------- Previous post was at 01:58 AM ----------
Just saw your edit...you're right it'll probably wipe everything again.
Did you get S-OFF with Sunshine? I don't know if maybe there's a way to unlock the bootloader again even if you're already S-OFF If you didn't then it probably won't be feasible to pAy $25 just to unlock the bootloader, I'd rather then just back up everything and let the data get wiped doing it the HTC way.
Check the Sunshine Thread maybe, they had some discussions in there about temp roots if I recall correctly.
Click to expand...
Click to collapse
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!

syntropic said:
I have been spending the past 2+ hours researching this. Even worse, the HTC token no longer unlocks the bootloader.... So I have this great phone with S-Off, but no way to get root. In my first attempt with chatting with HTC, they said that they "were very sorry but [they] do not support 'unlocking the bootloader' as it is against the warranty". WTF????? I am trying to get though to HTCDev... luckily I didn't change my CID. But I hate waiting for this.... I do a lot of stuff on that phone with root privileges..
I tried adb root, adb root shell, adb shell su, and a whole bunch of combination.... no dice...
There is just no way to hack a way to get temporary root at this point. I have looked... Weaksauce has long been deprecated/useless once you are past 4.4.2.
My planned 20+ minute task today is now going into its sixth hour....!!
Click to expand...
Click to collapse
how did you get S-OFF? Firewater?

BerndM14 said:
how did you get S-OFF? Firewater?
Click to expand...
Click to collapse
He said SunShine on OP.
OP - try towelroot to gain root then use scotty's guide to unlock bootloader

If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.

jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
Really ?
Read his problem again... His device has no root so can't do what you suggested

ckpv5 said:
Really ?
Read his problem again... His device has no root so can't do what you suggested
Click to expand...
Click to collapse
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.

jshamlet said:
If you are still S-off, just use adb to unlock the bootloader again.
http://forum.xda-developers.com/showthread.php?t=2475914
No muss, no fuss, and no lost files.
Click to expand...
Click to collapse
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.

syntropic said:
When ckpv5 referred to Scotty's method in the post above yours, he is talking about the thread you linked. I am aware of that method and think it is great, but you need to get a shell... and you need root privileges in that shell in order to run the dd= command. That is just the way it works. It doesn't matter if you are S-off (this is why I have been frustrated). Until HTC replies to me, I am stuck with an unrooted phone with S-off.
I am going to try the towelroot method though... I forgot about that (thank you ckpv5).
If I can get temporary root long enough to unlock the bootloader.... then I can flash TWRP and I am good to go. We'll see.
Click to expand...
Click to collapse
Yeah, I had a bit of a brain fart on that one. I forgot you have to be able to su to execute that dd command, even s-off. However, I do know for a fact that you don't actually have to flash TWRP to re-root. When I did the same thing you are doing, I simply booted TWRP instead of installing it to preserve the stock recovery.
TWRP did have an issue booting for a while when using the firmware that came along with 4.4.3, but they appear to have fixed it in the last two versions. I ended up using CWM instead, but the effect is the same.

jshamlet said:
I realized that shortly after posting.
However, there is still a solution. Use Sunshine to temp-root, then use a local terminal instead of adb.
Click to expand...
Click to collapse
That is another good potential solution...and I know it works.... I will try and let you know!

[Solved] Cannot install CM12 due to outdated bootloader

Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
Model: HTC ONE M8 16GB Unlocked (purchased on amazon; network free)
CID: HTC_001
Bootloader: Unlocked
Recovery: Clockworkmod Touch v6.0.4.8
S status: S-ON
Click to expand...
Click to collapse
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Edit: SOLVED!
See http://forum.xda-developers.com/showpost.php?p=58859881&postcount=13 for solution.

ProTofik said:
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Click to expand...
Click to collapse
Since you are S-On, you can't just flash the firmware, which is the easiest way. But you can use this method.
I'll give you an RUU to flash. But before you flash it, backup everything that is important to you, because this will wipe your phone.
Download this.
Rename it to 0P6BIMG.zip (that's a zero not the letter)
Put it onto the root of your extSD (By root of I mean just on the card and not a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power button to reboot when done)
Congratulations! You now have the latest lollipop firmware.
Make sure you delete the renamed zip from your extSD when you are done. If you don't delete it, it will try to update again every time you go back to hboot.

Since you are S-On, you can't just flash the firmware
Click to expand...
Click to collapse
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.

ProTofik said:
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
Click to expand...
Click to collapse
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.

xunholyx said:
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
Click to expand...
Click to collapse
Sorry, doesn't work either. I'm getting this error on 3rd command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1830711296 bytes
error: cannot load 'ROM.zip'
Click to expand...
Click to collapse

ProTofik said:
Sorry, doesn't work either. I'm getting this error on 3rd command:
Click to expand...
Click to collapse
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.

xunholyx said:
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
Click to expand...
Click to collapse
There you go:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: TOP SECRET
(bootloader) imei: TOP SECRET
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Click to expand...
Click to collapse

ProTofik said:
There you go:
Click to expand...
Click to collapse
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.

xunholyx said:
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
Click to expand...
Click to collapse
Didn't work but I got a different error this time
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM
.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1536838 KB)...
OKAY [ 43.198s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 43.510s
Click to expand...
Click to collapse
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?

ProTofik said:
Didn't work but I got a different error this time
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
Click to expand...
Click to collapse
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.

xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to lollipop. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?

ProTofik said:
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to kitkat. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
Click to expand...
Click to collapse
Yes. Sorry for the confusion I have caused.

xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5. Using this info, I downloaded matching nandroid backup of that ROM from here and restored it using my custom recovery.
Then, downloading from the same thread, I flashed back stock recovery image using HTC One 2014 (M8) All-In-One Toolkit V2.0.
I was back on my original ROM with original recovery, so I started doing OTA updates until I got to the official android 5.0.1. These updates updated my bootloader to version 3.19.
Having the bootloader that I needed, I flashed custom recovery and installed CM12 without any problem.
Thanks for help!

Hey, I just found this as I am having the same problem. I am trying to follow your solution, but hit a road block and was wondering if you could help. I ran the command "fastboot getvar all" in fastboot and got output similar to yours. Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway? I'm getting so close! I want cm12!!

I did it over like 6 months ago. I can't remember any more. Sorry.
Anyway, CM12 has way too many problem on HTC ONE M8 to be used as a daily driver. I am using GPE Rom now, which I can recommend.

I just need to find some way to update my bootloader so I can get lollipop up and running. Thanks tho

noo_too_droid said:
Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway?
Click to expand...
Click to collapse
The number needs to match exactly to restore to stock and OTA update the software/firmware (and therefore update hboot).
You can try to post on the following thread, and ask if someone can post the stock nandroid for 1.55.605.2 :http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Otherwise (if you can't get a stock nandroid) you may need to resort to getting s-off in order to update hboot (actually I recommend updating all firmware, not just hboot).

ProTofik said:
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5.
Click to expand...
Click to collapse
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?

raghuchary said:
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
Click to expand...
Click to collapse
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.

xunholyx said:
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
Click to expand...
Click to collapse
Apologies, newbie here. I was looking for the correct place to place my request for help, when I found this thread and asked. I will put it up in the Q&A section.

(solved)Help with update To android M

Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????

What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

HTCNerdYoda said:
What did you use TWRP for, or better asked what did you change on your system? Has your system been rooted or the system.img been manipulated in any kind?
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully

OTA failure
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.

ecmelg said:
My device is not rooted and today I tried to upgrade to marshmallow (ota) but it failed to do so after 80% it aborted the installation and now I'm stuck with a dump phone please help I'm not familiar with this kind of situation. I tried to wipe cache partition and wipe data/factory reset but nothing works. IT says on the screen:
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power.
-----------------------------------------
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
-----------------------------------------
Supported API: 3
handle_cota_install: install cwpkg to/c
ache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop to /
cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip c
w installation.
Click to expand...
Click to collapse
Try flashing RUU for ur model id.

Alxens said:
I used TWRP for root access and yes my system Is rooted but and boot loader unlocked for reinstalling stock recovery was working before and the updates were installed successfully
Click to expand...
Click to collapse
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

HTCNerdYoda said:
If it is rooted the OTA won't be installed as the system partition and thus it's md5 has been changed by mounting it r/w and flashing SuperSU. This is as google and HTC following this guidelines changed the OTA delivery to a block based system where the routine checks if the system has been untouched prior to installing it. You got to restore the untouched image of the system partition for your device. After this you could flash the stock recovery and install the OTA.
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
Click to expand...
Click to collapse
I have twrp backup system
would this work??

Alxens said:
Today I received the android m update I download it and install stock recovery so I can install the update But every Time I do it gets to the half of the bar and then says install aborted I have tried factory reset and wipe cache nothing worked
I had twrp recovery before And every time I get any update I replace the twrp with stock recovery and it always worked for me until today
Any solution please?????
Click to expand...
Click to collapse
Esta solución me sirvió a mi. www . htc.com/us/support/rom- downloads . html (saca los espacios) en tú caso descarga la versión desbloqueada

Yes would work
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?

sonoman87 said:
I'm having the same problem. I don't have a ROOT and already talked to the HTC help desk and didn't find any solution. With this TWRP can I fix this problem?
Click to expand...
Click to collapse
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.

redpoint73 said:
Most likely NO.
The above user(s) used TWRP backups to remove changes that were done by root.
Since you never rooted (from the sounds of it) you don't have the same problem.
Click to expand...
Click to collapse
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Thanks again!

sonoman87 said:
Thanks redpoint73. So, what do you recommend me to do now? Because, the problem started with the android notification of the update and then the system crashed. Search for a ROM and try to install it?
Click to expand...
Click to collapse
If there is a MM RUU for your version, download and run it.

redpoint73 said:
If there is a MM RUU for your version, download and run it.
Click to expand...
Click to collapse
I've fixed it! Thanks so much again!

sonoman87 said:
I've fixed it! Thanks so much again!
Click to expand...
Click to collapse
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country

oscar1355 said:
Which country are you from? And which ROM did you use? I'm from Spain and I'm afraid if I install the ROM it wouldn't work again in my country
Click to expand...
Click to collapse
First of all, you need to understand that ROM and RUU are two very different things.
Also, nobody can advise you the proper RUU is, without knowing some basic information. Namely, do fastboot getvar all, and post the output (delete IMEI and serial number before posting).

Hey everyone,
I am trying to get my M8 to stock (been stuck at this for about 10 days now, tried everything). I am from India. There was some problem and I accidentally have a phone now with no OS and TWRP. I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device:
Software status: Modified
Unlocked S-ON
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <serial number>
(bootloader) imei: <imei number>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would really appreciate it if you could guide me how to get my phone to stock OS. The ROM that I should prefer etc. I have been going through a lot of forums and ended up being utterly confused.
Thanks in advance for the help!

skull_143 said:
been stuck at this for about 10 days now, tried everything
There was some problem and I accidentally have a phone now with no OS and TWRP.
Click to expand...
Click to collapse
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
skull_143 said:
I have installed stock recovery and plan to flash the ROM/RUU. Some details of my device
Click to expand...
Click to collapse
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).

redpoint73 said:
Sorry, this is a pet peeve of mine, but I really wish folks would stop posting they "tried everything". This literally tells us nothing, and you should list specifically one-by-one (and in detail) what things you tried, and the results (again in detail) of each.
"Accidentally" appears to mean you unlocked the bootloader, then flashed an very old, obsolete version TWRP (which causes the main version to be blank) then decided it was a good idea to wipe the OS (system)? Again, you need to tell us exactly what steps you took to get to this point.
My next advice to you, is to only do things that are specifically instructed for you to do in your situation. Don't guess or do things without fully understanding them. As your present situation seems to indicate you don't have a very good understanding of what you are doing, and only making matter worse by proceeding with insufficient knowledge.
RUU will only work if its version 6.15.720.2
Your version (CID and MID) is rather obscure, so I'm not sure whether such RUU exists or not. If not, your best bet is to get TWRP back on the phone, and restore the stock nandroid 6.15.720.2 using the files and instructions on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Also, flashing stock recovery is not needed to RUU; and not helpful in your current situation (you'll probably need to go back to custom recovery TWRP).
Click to expand...
Click to collapse
Sorry about the shortened version, just though it might be too big and unnecessary. Okay here goes what happened. I moved the whatsapp media to my laptop (at this time the device was unrooted and running stock android M updated over OTA). After the move, the device was stuck at the splash screen with HTC logo. After this I gave the phone to a service centre (not official HTC) and asked them to NOT root and put stock OS and get the phone working. What they did was, rooted it and installed a custom ROM with TWRM recovery (which was very screwed up, as in the camera kept crashing and I couldn't even use that). So, I decided to get it back to stock ROM and sense UI.
So what I did was looked up some thread (not sure which one) and went ahead to do a wipe through recovery. Here I did the mistake of wiping everything and so the device doesn't have any OS at the moment. The phone is still getting stuck in HTC logo now (obviously as it doesn't have an OS). I have tried to do the following:
1. To flash the boot only using fastboot flash boot and fastboot flash zip commands. The version I tried was stock 3.35.720.1_recovery.img. This didnt seem to work.
2. Next tried to go to usb fastboot mode and tried to run the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe official one from the laptop. But it showed some mismatch of versions and aborted.
3. Then I read that stock could only be flashed on S-ON devices if we relock the bootloader. So used the fastboot oem relock command to relock bootloader and then tried both the above but didn't work.
4. Next saw somewhere that it is pretty impossible to flash on a locked S-ON device. So went to htcdev and got the bootloader unlocked again.
5. Downloaded a stock image 3.35.720.1 Stock Unrooted. Read that we need lower or same stock recovery to flash the same and so flashed the stock recovery of the same version. Next extracted the .win001 and .win002 files using the tar command and finally put them along with META_INF folder and boot.img files into a zip file. The image had the contents of the system folder and tried to flash this using fastboot and also through the stock option "Update from SD card". Got error "E: footer is wrong. E: update signature verification failed".
This is the status so far. I am not sure what I should be doing anymore. Hope this helps in understanding the situation. Sorry it's so long.
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.

skull_143 said:
Please advice what I should do now. Currently, I have stock recovery installed and no OS. I just want to have the stock sense OS on the device.
Thanks for all your time.
Click to expand...
Click to collapse
1. Download the 6.15.720.2 RUU.zip : http://forum.xda-developers.com/showpost.php?p=66309774&postcount=20
2. relock the bootloader with command - fastboot oem lock
option 1 - if you have a microsd
1. rename the downloaded RUU.zip as to 0P6BIMG.zip
2. put it on root of your microsd not in any folder
3. on bootloader select hboot - it will scan the zip and ask you to update.
4. select volume up to update
5. once completed, delete the zip from microsd
option 2
1. Download htc_fastboot.exe : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
2. put both htc_fastboot.exe and the 0P6BIMG.zip in your fastboot folder
3. run below commands :
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip 0P6BIMG.zip (to install RUU - read it is htc_fastboot not fastboot)
Once complete - fastboot reboot
run setup .. done

Can't revert HTC One M8 to stock

I received an unlocked HTC One M8 (US, works on AT&T, not Harmon Kardon), factory reset, never been modded. Because it ran Android 6.x, I was concerned that it wasn't as secure as it could be, so I researched how to install the newest Android possible. I found many articles on these forums, guides from 2014 all the way to 2016. I didn't (and still don't) know enough to tell the difference between a good tutorial and a bad/outdated one. I saw that some tutorials were edited to reflect new mods, but now that I have read even more, I suspect that even those updated ones are now obsolete.
My problem is that I installed Resurrection Remix with v7.1.2, along with pico Open Gapps, and it won't let me install several apps like Chrome or even YouTube. I have decided that I don't want a newer ROM and I would rather just revert to stock. I have been attempting to revert to stock for the last three or four days, and I have spent many hours researching and reading (mostly this site...go figure), but so far I have not accomplished anything.
Current information about the phone: I did not make a backup (I've had little success doing this over the years on Android phones), I unlocked the bootloader with the HTC unlock code.bin file, the phone has S-ON and has not been rooted. In fact, I've tried SuperSU and Sunshine and neither worked. I have TWRP 2.7.1.0 installed. I have drivers from HTC Sync, but I also installed the Android Studio, along with some utilities that come with it. I have attempted the RUU from HTC (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4) and it always says that there was an error.
I have attempted several times to change the CID, but only because a tutorial told me to. I assume that it was changed when I installed the Remix mod. I have no idea what it should be. I have attempted to install firmware as well, both with the adb method and by copying it to the SD card and renaming it for bootloader, but both options fail. The adb method fails with...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
...and the SD card method thinks for a bit, then says "press power to reboot" in the same type of text as the bootloader text.
I am only a little familiar with adb and fastboot, so please, be gentle. If you list commands, I will use them without even thinking, like how Ron Burgandy reads everything on the teleprompter.
Please help.
Here's the getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!

speedee39 said:
Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Hi,
no you did not post in the wrong forum. This section is not that active but there are still a handful of people visiting and trying to help.
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.

maultasche said:
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Click to expand...
Click to collapse
The guide I found for reverting to stock said to change to the super CID (fastboot oem writecid 11111111). I only did that because I thought that it was the "right way" to do this. But if the CID can't be changed unless the phone is s-off, then it must still be stock, because I doubt that I've ever achieved s-off while flashing a different ROM.
maultasche said:
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Click to expand...
Click to collapse
Yes, I attempted the Sense stock because the tutorial told me to and also because that's what is listed on HTC's website. I don't want to go to Sense, just thought that I was supposed to. So you're saying that the phone is a Google Play Edition? I'll need to look that up.
maultasche said:
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Click to expand...
Click to collapse
Thank you for that, I didn't know. I'll get it. One question that I've never found the answer to is, if I installed TWRP to change the ROM, what is the stock recovery image? Or, is it bad to simply leave TWRP installed? I have no plans to sell the phone.
maultasche said:
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.
Click to expand...
Click to collapse
I think I did this correctly. Here's what I found through the shell:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p45 1032088 853196 178892 83% /system
Once I started looking this up, I found a post on XDA about GPe and different partition sizes. I'll check for GPe ROMs now. Do I need any other files besides that and the updated TWRP? Is the order to install a newer TWRP, then flash the GPe ROM, and then relock the bootloader?
I noticed that the bootloader has a persistent message about it being relocked and **WARNING**. Is there a way to clear the warning flag? One of the tutorials that I was following listed several shell commands to do this. I'm going to list them, so let me know if that is the way to clear the flag.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot-bootloader
Thanks for your help.

You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Since your device is a GPe device there is no need to change cid, mid etc. - with s-on you can't change them anyways. Just grab the latest GPe ruu and follow flashing instructions.
Stock recovery is only needed for ota-updates. On sense the updates would fail as this particular recovery is missing. I assume on GPe that would happen as well. It's up to you if you use twrp or stock recovery. GPe won't get updates anymore, same as sense.
I recommend not to mess with this stuff in bootloader. Once you go back to stock (ruu etc), it should fix itself. Besides that to temper with it you need to be s-off anyway.

maultasche said:
You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Yes, I had found that exact thread earlier today, thanks to you, and I was just replying to tell you that I have successfully reverted my phone back to stock.
In the spirit of contribution to the site that has helped a novice such as me, I want to share the steps I took so that others might be helped.
The phone, as mentioned earlier, is an HTC One M8 Google Play Edition (Gpe), was s-on, not rooted, bootloader unlocked. I had an old version of TWRP and Resurrection Remix ROM using Android 7.1.2.
Prerequisites
1. Stock GPe ROM: https://androidfilehost.com/?fid=817550096634750828
2. TWRP 3.1.1-0-m8: https://dl.twrp.me/m8/twrp-3.1.1-0-m8.img.html
3. Backup account fix (linked in aforementioned thread): https://www.androidfilehost.com/?fid=24686680535467942
4. ADB and fastboot
5. Unlocked bootloader
**This assumes that you have a Windows computer. I used Windows 10 v1709**
Steps
1. Copy the ROM and TWRP files to the same folder in which fastboot and ADB are located. This makes it easier to run commands.
2. (There might be another way to do this one, but I don't know it) Copy the backup account fix file "MRA58K.H15_backup-account-fix.zip" to a micro SD card and put it in the phone.
3. Open a command prompt or PowerShell window in the folder that contains ADB and fastboot by right-clicking + Shift in an open area and selecting "Open PowerShell/Command Prompt window here."
4. In the PowerShell/Command Prompt window, type "fastboot flash recovery twrp-3.1.1-0-m8.img" and press Enter to install TWRP
5. Reboot into the bootloader and choose "fastboot," then choose "recovery"
6. In TWRP, browse to ADB sideload and then "swipe to start sideload."
7. In your PowerShell/Command Prompt window, type "adb sideload HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H15_AROMA-Installer-v6-020817.zip" and press Enter to start the installation
8. On the phone's screen, choose the top option, which should be the unrooted, completely stock installation.
9. On my machine, the PowerShell/Command Prompt window showed progress up to 41% and then it finished successfully.
10. After that, do not reboot, but go back into the main TWRP menu and go to Install. Browse to the MRA58K.H15_backup-account-fix.zip file that you previously saved on your SD card and install it.
11. Once that is installed, reboot the phone. My phone took between 5 and 10 minutes to boot the first time.
12. (Optional) I wanted to have a completely reverted phone, so I locked the bootloader again by rebooting the phone into the bootlader and typing "fastboot oem lock" in the PowerShell/Command Prompt window. It then said "relocked" but no warnings or errors.
I hope this helps somebody. All credit goes to maultasche for pointing me in the right direction and to graffixnyc for the other thread.

Unable to install/enter twrp recovery

I purchased a HTC M8 dual sim phone. I unlocked the bootloader and flashed the latest twrp on it, all seemed fine. However when rebooting to recovery it's stuck at "entering recovery...". There's tons of threads about that suggesting various version of twrp, so far I have tried (erasing cache in between):
twrp-2.7.1.0-m8.img
twrp-2.8.0.0-m8.img
twrp-2.8.1.0-m8.img
twrp-2.8.3.0-m8.img
twrp-2.8.7.0-m8.img
twrp-3.0.0-1-m8.img
twrp-3.1.1-0-m8.img
twrp-3.2.3-1-m8.img
twrp-3.3.0-0-m8.img
twrp-3.3.1-0-m8.img
However I always get either stuck at entering recovery or go directly back to bootloader.
So I wanted to do OTA updates first, but HTC doesn't allow me to anymore. So I installed stock recovery from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 Still couldn't install the OTA. So i (probably stupidly followed these instructions to get S-ON: https://forum.xda-developers.com/ve...w-to-to-stock-unroot-lock-bootloader-t3505783
The getvar all reports:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.22.30306251.27G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) version-misc: PVT SHIP S-ON
[...]
(bootloader) meid: A1000037D21505
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B41000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
In some old threads about dual sim "special" twrp imgs like TWRP_Recovery_2.8.0.5_M8_CPTB.img are recommended, but the download links are broken.
So in the end I'd just like to get twrp installed, from there I know my way around (I'd have tried lineage first). Any pointers/ideas what to try next to achieve that?

imsodin said:
Still couldn't install the OTA. So i (probably stupidly followed these instructions to get S-ON: https://forum.xda-developers.com/ve...w-to-to-stock-unroot-lock-bootloader-t3505783
Click to expand...
Click to collapse
S-off does not limit OTA. So maybe not the best idea to make it s-on again. On the other hand, s-on will not limit installation of TWRP, custom ROMs, etc.
Also, if the device was made s-off by sunshine, you should be able to install the sunshine app, and just s-off it again with no fee. The sunshine license is forever associated with the device, and if it was purchased once, you can s-off that device again and again.
imsodin said:
In some old threads about dual sim "special" twrp imgs like TWRP_Recovery_2.8.0.5_M8_CPTB.img are recommended, but the download links are broken.
Click to expand...
Click to collapse
Far as I can recall, the dual SIM M8 did require it's own version of TWRP. Keep trying to find a working link, is all you can do.

redpoint73 said:
S-off does not limit OTA. So maybe not the best idea to make it s-on again. On the other hand, s-on will not limit installation of TWRP, custom ROMs, etc.
Also, if the device was made s-off by sunshine, you should be able to install the sunshine app, and just s-off it again with no fee. The sunshine license is forever associated with the device, and if it was purchased once, you can s-off that device again and again.
Far as I can recall, the dual SIM M8 did require it's own version of TWRP. Keep trying to find a working link, is all you can do.
Click to expand...
Click to collapse
Good to know about s-on, then it won't bother me.
As to a working link: They all go to yandex/mega/..., i.e. no luck with any archives. I scoured xda and google, and all broken links or pointers to the "normal" m8 twrp (often explicitly stating that it's the same for dual sim, e.g. https://forum.xda-developers.com/htc-one-m8/help/twrp-recovert-htc-one-m8-dual-sim-t3384609). I really don't want to write this phone off, well mostly I don't want to look for an alternative, but I am at my wits end and wasting too much time

imsodin said:
I scoured xda and google, and all broken links or pointers to the "normal" m8 twrp (often explicitly stating that it's the same for dual sim, e.g. https://forum.xda-developers.com/htc-one-m8/help/twrp-recovert-htc-one-m8-dual-sim-t3384609).
Click to expand...
Click to collapse
It is confusing to determine whether the dual SIM requires its own recovery or not, as I looked at some threads myself. But the thread you linked in particular, the guy that says it is the same recovery (as the single SIM M8) ckpv5, I don't think I've ever seen him wrong about anything. So I would take his word for it.
Based on his thread here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
the proper TWRP version for OS version 3.xx should be TWRP 2.8.3.0, so you should focus there. I know you tried it already, but it doesn't hurt to try it again.

TLDR:
This device isn't unproblematic to handle - don't just assume anything from previous experience as I did. I manages to create a paperweight (technically maybe recoverable, but I don't have the patience anymore to try).
Thanks for keeping me on the right track, I managed to get twrp 2.8.1.0 (sic!) to work. I doubt the following will be helpful to anyone, but who knows:
fastboot getvar all showed the above output, i.e. version 3.33.401.6. However when I tried to get the downloaded OTA (for the firmware) I noticed it says it will upgrade to 3.33.401.6. So checking the settings in Android I find that my actual version is 1.45.401.12. Which according to https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 means you should use twrp 2.8.1.0.
I was pretty sure I already tried that, but I probably didn't. I did find a dubious claim that you need to flash the recovery twice immediately and then erase cache and did that for good measure (I know I am not supposed to, but when it comes to all things android/phone I do believe in "weird s**t").
Now after that I installed LOS 16 - well I tried. TWRP fails to report the model which aborts the installation. So I removed the asserts from LOS' install script. Stupid move: It doesn't only check the model but also the bootlocker - and that was actually incompatible. Obviously as I have no reason to go back to some ancient HTC OS I didn't do a backup. So now I can't boot a system to get to s-off and can't install an RUU - which for all I read is the only way to get back on track to update the firmware. Just for funsies I also tried to flash a newer boot.img in hopes to get to bootloader 0.19, but that didn't have any effect.
The only way out would be to install some ROM that runs on bootloader 0.18 - I didn't find any. Then get to s-off using sunshine, then go through the entire back-to-stock dance and finally use OTAs to update firmware and once done go back to custom. Well, actually that would have been the intuitive and logical thing to do in the first place: Exhaust all official upgrades, backup, go custom. But inpatient me wanted to take the shortcut to custom and now I spent hours for nothing.
Sorry for the lengthy rant

See my comments below in red font:
imsodin said:
TLDR:
fastboot getvar all showed the above output, i.e. version 3.33.401.6. However when I tried to get the downloaded OTA (for the firmware) I noticed it says it will upgrade to 3.33.401.6. So checking the settings in Android I find that my actual version is 1.45.401.12. Which according to https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 means you should use twrp 2.8.1.0.
The OS number reported by getvar is the correct (current) firmware. The OS number shown in settings is not to be trusted. At some point, it looks like somebody flashed a 1.45.xxx based ROM, but the phone still has 3.33.xx firmware. You want the ROM to correspond with the firmware.
Now after that I installed LOS 16 - well I tried. TWRP fails to report the model which aborts the installation. So I removed the asserts from LOS' install script. Stupid move: It doesn't only check the model but also the bootlocker - and that was actually incompatible. Obviously as I have no reason to go back to some ancient HTC OS I didn't do a backup. So now I can't boot a system to get to s-off and can't install an RUU - which for all I read is the only way to get back on track to update the firmware.
You don't need s-off to flash an RUU intended for your version M8 (dual SIM). If the RUU is not for the dual SIM, it will probably brick your phone if you flashed it. So those safeguards exist for a reason.
If you can find RUUs for your dual SIM M8, that would be an easy way out. But I don't think I've seen such an animal.
Other options might be:
- (if you can find them) flash 3.33.401.6 stock backup and stock recovery. Then OTA update.
- (if you can find it) flash 4.30.401.16 signed firmware, and restore stock TWRP backup 4.30.401.16 that ckpv5 posted in his collection.
- (if you can find it) flash 4.30.401.16 signed firmware and flash LOS16, as that firmware might put you on the right bootloader and firmware to work with that ROM.
I know these unfortunately are all high bars to meet, as the dual SIM doesn't have a lot of resources posted.
Just for funsies I also tried to flash a newer boot.img in hopes to get to bootloader 0.19, but that didn't have any effect.
boot.img is a completely separate partition from bootloader. They sound the same, but not the same. boot.img is essentially the kernel. You can't flash bootloader by itself with s-on. But you can flash bootloader with the correct RUU or signed firmware for your version M8 (CID, MID).
Click to expand...
Click to collapse

The problem is my CID has been changed to 111111 (which I read is some kind of magical super-power CID, don't know why though ), thus I can't flash any RUUs. I tried flashing a few x.x.401.x firmwares without success.
Anyway thanks again for helping me - in the meantime I lost the phone I wanted to replace, which was the final trigger to abandon this project and just get a cheap new phone that I'll hopefully not butcher (for now (still gets security updates) it'll get Magisk Root only - after upgrading and backing up).