Develop Bugs

[Q] "clean install"

I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?

Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there

unifex_ said:
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Click to expand...
Click to collapse
Do as EddyOS says, he will guide you on the best which version to downgrade to (if your looking to do that). Honestly I didnt have any issues with Lollipop, its all good.
my suggestion of the easiest way to totally wipe up your internal memory is to unlock bootloader (if you've already unlocked it, then relock and unlock again), doing that will totally wipe your internal memory, as for ext. sd card, you can just format that.
Flashing original stock rom is done by an RUU.

EddyOS said:
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
Click to expand...
Click to collapse
Thanks Eddy, I appreciate the help.
I attach an image of the fastboot output.

If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box

EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
Click to expand...
Click to collapse
Great, that sounds uncomplicated enough. My bootloader is locked, as far as I know, at least I never did anything to unlock it. So I should be good to go.
One question though. At the moment, the phone is unlocked as far as SIM is concerned. I mean that although the CID is from T-Mobile Germany, I'm using O2 as the service provider. Will that RUU keep it that way, or it will make the phone locked towards T-Mobile SIM cards?
Thanks a lot.

It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't

EddyOS said:
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
Click to expand...
Click to collapse
In case it would, what would I have to do to unlock it? I don't have any T-Mobile SIM cards around here after all.

Buy a code, like you did last time

EddyOS said:
Buy a code, like you did last time
Click to expand...
Click to collapse
I did not buy any code, I bought a phone. That's how it came from the shop - SIM-unlocked. I had no idea it had the T-Mobile anything in it until I started looking around this forum and someone asked me about my CID.

If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU

EddyOS said:
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
Click to expand...
Click to collapse
Great, thanks! I'll let you know how it went.

OK, finally got the time to do it, but unfortunately, the RUU that I downloaded
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
Click to expand...
Click to collapse
did not work, I attach the screenshot with the error. Any ideas? The error was the same regardless of whether the phone was connected to the PC.

Yeah, it appears that RUU is corrupt

EddyOS said:
Yeah, it appears that RUU is corrupt
Click to expand...
Click to collapse
That's a pity. Do you know where can one find a proper RUU? I looked at the htcdev.com download section, they list the software I need, 4.19.111.2, but the download link brings me simply to the htc.de, where nothing can be downloaded, it's just their regular advertising site.
I also found a zip file with the 4.16.111.2 firmware on a German forum (basically, from a link in the xda thread with RUU and OTA collection), but to be honest, I'm not sure what to do with the bunch of img files.

The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted

EddyOS said:
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
Click to expand...
Click to collapse
How about the files from that site (German, though). I found that link on the xda thread for RUU collection.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
They have a list of various files, for 4.19.11.2 they have nandroid backups and signed firmware, but not a RUU.
Or could you suggest a well working ROM?

You could flash the backup, then the firmware to restore stock recovery and it should work

EddyOS said:
You could flash the backup, then the firmware to restore stock recovery and it should work
Click to expand...
Click to collapse
Could you help me with mine as well
from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH445WM0----
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.177s

[Q] 5.1 OTA fails with stock recovery on unrooted GPE

Hi all-
I did my best to find all the common problems in the forums, but my HTC One M8 GPE (original, not converted) just will not take the 5.1 OTA.
I had TWRP and SuperSU 2.46 installed. I flashed the 5.0.1 stock recovery from GraffixNYC's site and did a full unroot in SuperSU. With those steps done, attempting to install the OTA results in:
Code:
file "/system/bin/app_process32" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/app_process32" has unexpected contents.
"/system/bin/app_process32" has unexpected contents.
But when I compared my app_process32 with GraffixNYC's 5.0.1 RUU version, they have the same SHA-1:
Code:
575903d0987fbadfa558fcfb9f69bdd29e519de8 app_process32 (mine)
575903d0987fbadfa558fcfb9f69bdd29e519de8 app_process32 (5.0.1 RUU)
So I pulled update.zip off my phone, extracted the updater-script, and found my SHA-1 does match the second SHA in apply_patch_check!
Code:
apply_patch_check("/system/bin/app_process32", "b6a0aef32e21dfc6a230ccf707d9b08d513dbcd3", "575903d0987fbadfa558fcfb9f69bdd29e519de8") || abort("\"/system/bin/app_process32\" has unexpected contents.");
Concerned I might have gotten a bad update.zip I grabbed the link from the OTA thread and verified it matched mine (it does).
Unfortunately I'm still S-ON, so simply flashing the system partition seems to be out.
In case I'm missing something, here is the output of fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any recommendations on how to work around this problem will be greatly appreciated.
Thanks!
Stephen

Try older stock recovery that matches your firmware..

flyera343 said:
Try older stock recovery that matches your firmware..
Click to expand...
Click to collapse
I'm confused... Are you thinking a 4.4.4 recovery or just an earlier version of the 5.0.1? In the case of 5.0.1 I'm not sure where I'd find such a thing...
Thanks,
Stephen

scbash said:
Hi all-
I did my best to find all the common problems in the forums, but my HTC One M8 GPE (original, not converted) just will not take the 5.1 OTA.
I had TWRP and SuperSU 2.46 installed. I flashed the 5.0.1 stock recovery from GraffixNYC's site and did a full unroot in SuperSU. With those steps done, attempting to install the OTA results in:
Code:
file "/system/bin/app_process32" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/app_process32" has unexpected contents.
"/system/bin/app_process32" has unexpected contents.
But when I compared my app_process32 with GraffixNYC's 5.0.1 RUU version, they have the same SHA-1:
Code:
575903d0987fbadfa558fcfb9f69bdd29e519de8 app_process32 (mine)
575903d0987fbadfa558fcfb9f69bdd29e519de8 app_process32 (5.0.1 RUU)
So I pulled update.zip off my phone, extracted the updater-script, and found my SHA-1 does match the second SHA in apply_patch_check!
Code:
apply_patch_check("/system/bin/app_process32", "b6a0aef32e21dfc6a230ccf707d9b08d513dbcd3", "575903d0987fbadfa558fcfb9f69bdd29e519de8") || abort("\"/system/bin/app_process32\" has unexpected contents.");
Concerned I might have gotten a bad update.zip I grabbed the link from the OTA thread and verified it matched mine (it does).
Unfortunately I'm still S-ON, so simply flashing the system partition seems to be out.
In case I'm missing something, here is the output of fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any recommendations on how to work around this problem will be greatly appreciated.
Thanks!
Stephen
Click to expand...
Click to collapse
Do you use Xposed?

xunholyx said:
Do you use Xposed?
Click to expand...
Click to collapse
No. Just SuperSU and Titanium Backup, and I've done the full unroot via SuperSU...
Thanks,
Stephen

Any other thoughts?
Thanks,
Stephen

I am dealing with exact same issue. GPE HTC One M8, not converted. I rooted, S-ON and installed TWRP to get CM12.1. Then flashed back pre-rooted GPE rom from GraffixNYC. I recently decided to go unrooted so that I can get OTA (and M later), but OTA gives me the same error (I have the stock recovery now) I tried to flash unrooted RUU from GraffixNYC's thread, but that fails. Firmware is flashing fine. I wonder if you have figured out a solution.
Thanks.

msgfromside3 said:
I am dealing with exact same issue. GPE HTC One M8, not converted. I rooted, S-ON and installed TWRP to get CM12.1. Then flashed back pre-rooted GPE rom from GraffixNYC. I recently decided to go unrooted so that I can get OTA (and M later), but OTA gives me the same error (I have the stock recovery now) I tried to flash unrooted RUU from GraffixNYC's thread, but that fails. Firmware is flashing fine. I wonder if you have figured out a solution.
Click to expand...
Click to collapse
Nice to know I'm not the only one who ran into this... As far as a solution, unfortunately no. I've been meaning to S-OFF the phone and then try flashing, but just haven't gotten around to it.
Let me know if you find anything...
Stephen

I did a bit more research and it seems the culprit is busybox being a part of pre-rooted ROM. /system/bin/app_process32 is actually symlinked to a new executable in /system/xbin, where busybox and su are being installed to.
With S-ON, the options are very limited (I hate HTC for this. Neither Samsung nor Nexus line never gave me this S-ON/OFF crap.). I think we need a ROM without pre-root, or somehow trick the update script (I used to do this a lot with Samsung devices). I will see if modifying the script helps.
Thanks.

msgfromside3 said:
I did a bit more research and it seems the culprit is busybox being a part of pre-rooted ROM. /system/bin/app_process32 is actually symlinked to a new executable in /system/xbin, where busybox and su are being installed to.
Click to expand...
Click to collapse
Arg, I should have thought of that! One thing that might be helpful is I found it's possible to retain superuser privileges in an adb shell if you run su while the phone is rooted and then unroot via the SuperSU app. That might allow you to fix up the symlink (assuming the original is still available). I'm a bit busy today, but if I find some time I'll experiment with that.
msgfromside3 said:
I hate HTC for this. Neither Samsung nor Nexus line never gave me this S-ON/OFF crap
Click to expand...
Click to collapse
Yeah, this is my first HTC, and being a GPE I expected a "Nexus with HTC hardware". After the ease of hacking my Galaxy Nexus and my wife's Nexus 5 the One GPE is frustrating. Really I think all my problems eventually track back to the post-5.0 OTA model of "everything must be an exact match", but I don't see Google changing direction on that anytime soon...
Thanks,
Stephen

Figured out. /system/bin/app_process32 is the culprit. The hard part was to figure out how to make a change to system partition. I first tried to remount the system partition from the shell, but that didn't stick after reboot (maybe because of s-on). So here is what I did.
1. reflash twrp, if you are back on stock recovery
2. boot into the recovery
3. mount system partition
4. go to advance -> file management (or something like that)
5. go to /system/bin
6. remove app_process32
7. rename app_process32_original to app_process32
8. restart back into the bootloader
9. reflash the stock recovery
10. go into the recovery
11. flash OTA via adb sideline (you have to press UP + POWER to see the recovery menu). You might see some error something to do with /data partition and /system partition at the end, but they seem harmless.
12. restart the phone. the OTA script will flash firmware.zip automatically
I don't know the implication of replacing the symlink to the original file, but it seems I didn't lose root yet. I just finished this process so haven't played with the phone at all other than confirming the version change.
Hope this helps!
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
scbash said:
Arg, I should have thought of that! One thing that might be helpful is I found it's possible to retain superuser privileges in an adb shell if you run su while the phone is rooted and then unroot via the SuperSU app. That might allow you to fix up the symlink (assuming the original is still available). I'm a bit busy today, but if I find some time I'll experiment with that.
Yeah, this is my first HTC, and being a GPE I expected a "Nexus with HTC hardware". After the ease of hacking my Galaxy Nexus and my wife's Nexus 5 the One GPE is frustrating. Really I think all my problems eventually track back to the post-5.0 OTA model of "everything must be an exact match", but I don't see Google changing direction on that anytime soon...
Thanks,
Stephen
Click to expand...
Click to collapse
Yeah, I tried the uninstall path first time, but no, that only deleted supersu binaries, not busybox.
That was my expectation with GPE as well. Now my rule has changed to "Only Nexus devices".

I am just curious as to why you guys are trying to "keep root" and get an OTA at the same time, you either root and never mess with OTA's again or go OTA like the rest of standard (non-xda/geek) users.
Simply dirty flash the Official pre-rooted 5.1 Stock ROM and flash any other mods you may had again like Xposed framework system files for example then wipe cache and dalvik and boom you're good to go.
A regular OTA does the same thing, flashes /System again clean and wipes cache and dalvik without touching /Data.
Then flash The Firmware and you have done everything the OTA does.
Firmware flash should work even on S-ON only if you are upgrading rather then downgrading and only if do it in fastboot on your phone by "0p6bimg.zip" to SD rather then doing it on a PC.
Now I understand dirty flashing is known to cause issues and bugs but the truth is that is only really on custom ROMs with aroma and other extra things and modifications, the zip I posted above is a Stock /System flash, nothing else besides flashing SuperSu app AFTER /System partition is written, almost all other custom ROMs I always had some kind of dirty flash issue, a missing app or something, but this method here I never ever ever had an issue, even on Nexus devices and such in the past.
Now if you wished to go OTA without root, then you must make sure you have CID "GOOGL001" and also confirm your MID is "0P6B17000" by "fastboot getvar mid" then flash This NON-Rooted Stock 5.1 RUU and afterwards do not make any modifications and lock your bootloader by "fastboot oem lock" I never tried it on my M8 but on my Nexus 4 OTA's failed on unlocked bootloaders!!
So the conclusion to all of this is in my opinion OTA and root are 2 different choices to make and mixing both are difficult and irritating, devs like enewman17 and others will always have Stock roms and RUUs posted and I am sure a rom and ruu of Marshmallow will be available 1-3 days of release if not sooner!

msgfromside3 said:
Figured out. /system/bin/app_process32 is the culprit.
Click to expand...
Click to collapse
Well son of a gun... Looks like some update to SuperSU also solved the problem, because full unrooted actually worked this time (it removed the symlink and app_process32 had the right signature afterwards). So it was probably a bug all along. So I didn't even need to jump through an hoops tonight.
Thanks,
Stephen

Viper4713 said:
I am just curious as to why you guys are trying to "keep root" and get an OTA at the same time, you either root and never mess with OTA's again or go OTA like the rest of standard (non-xda/geek) users.
Click to expand...
Click to collapse
Honestly Viper, when I started this thread back in the spring I wasn't trying to keep root. I had run a "fully unroot" and the OTA still failed to install. As I mentioned in a previous post, this seems to have been a bug which has since been corrected.
As far as messing with OTAs and root, it's a long and tortuous story that mostly revolves around a few dead phone scares that required a Titanium Backup safety net. But over the past few months I've found workarounds for everything I use root for, so going forward I won't be messing with it
Stephen

H9 to H10 Flash
HTC One ME GPE. Not converted.
I cannot get H9 to H10 either OTA or Flash. I unrooted SuperSU and returned to stock Recovery. I also have S=Off. Error says I do not have H9, but it shows H9 in Build LMYY470.H9. I could not do H9 OTA either, but I did flash it in stock recovery.
I don't really care about H10, but I do want to eventually get the phone to Android 6.0. Should I flash one of the GraffixNYC RUU's, if so which one? Or do I wait for a Android 6.0 flash?
Phil

pclewis said:
HTC One ME GPE. Not converted.
I cannot get H9 to H10 either OTA or Flash. I unrooted SuperSU and returned to stock Recovery. I also have S=Off. Error says I do not have H9, but it shows H9 in Build LMYY470.H9. I could not do H9 OTA either, but I did flash it in stock recovery.
I don't really care about H10, but I do want to eventually get the phone to Android 6.0. Should I flash one of the GraffixNYC RUU's, if so which one? Or do I wait for a Android 6.0 flash?
Phil
Click to expand...
Click to collapse
Just follow my tutorial a couple posts above, it WILL WORK, make sure you're on TWRP 2.8.7.0, no unofficial versions.

Viper4713 said:
Just follow my tutorial a couple posts above, it WILL WORK, make sure you're on TWRP 2.8.7.0, no unofficial versions.
Click to expand...
Click to collapse
Thanks Viper,
Your tutorial is right on. I have pretty much given up on OTA, as they are somewhat erratic unless you never root or unlock. I think I will leave it alone until I get my new Nexus 6p, then I don't mind using the M8 as a backup and wiping the phone. Probably in a year or so it will be on CM 13 or whatever.
Thanks, your comments are right on.
Phil

pclewis said:
Thanks Viper,
Your tutorial is right on. I have pretty much given up on OTA, as they are somewhat erratic unless you never root or unlock. I think I will leave it alone until I get my new Nexus 6p, then I don't mind using the M8 as a backup and wiping the phone. Probably in a year or so it will be on CM 13 or whatever.
Thanks, your comments are right on.
Phil
Click to expand...
Click to collapse
Alright cool, hope you enjoy the N6P! but you do not have to wipe your phone to update from H9 to H10, read the tutorial a little closer lol.

Viper4713 said:
Alright cool, hope you enjoy the N6P! but you do not have to wipe your phone to update from H9 to H10, read the tutorial a little closer lol.
Click to expand...
Click to collapse
Well, I tried that and almost always flash rather than OTA, but even though it went from H6 to H9 with flash, it will not do H9 to H10. I took it to stock recovery from TWRP and removed SuperSU root, but still no luck. Even though it shows H9 on "about phone" I get an error that it is not on H9 when doing the flash in recovery. Rather than deal with erasing some files, I think I will just leave it alone until I get the new phone. Or maybe I should just try one more time.
??
Phil

pclewis said:
Well, I tried that and almost always flash rather than OTA, but even though it went from H6 to H9 with flash, it will not do H9 to H10. I took it to stock recovery from TWRP and removed SuperSU root, but still no luck. Even though it shows H9 on "about phone" I get an error that it is not on H9 when doing the flash in recovery. Rather than deal with erasing some files, I think I will just leave it alone until I get the new phone. Or maybe I should just try one more time.
??
Phil
Click to expand...
Click to collapse
Idk that makes no sense to me, there is no reason to unroot or get stock recovery, enewman17's rom is already rooted, so in TWRP all you have to do is flash the zip file then afterwards (optional: flash your mods) then wipe cache and dalvik, and reboot, that is all it should take, you don't need to be on H6 H9, ABC123, it doesn't matter, /System gets completely replaced, remember, flash the full Rom link I sent, don't "flash" an OTA zip file in TWRP where ever you may be getting some OTA file from.
Also make sure the download wasn't bad either lol.
Also just to let you know, there is no 4.04.1700.10 firmware either, no changes were made.

S-OFF,ROOT,SUPERCID and harman kardon mod

Hey
I have a pretty new htc one m8 i have ordered
I would like to have it rooted so i can install avast rooted version plus harman kardon mode.
I am running stock rom 5.0.1 (4.16.401.10)
I know that i need to have S-OFF for my htc m8 in order to have karman kardon mode. I have just wanted to download recovery stock so i can go back and have OTA updates when i need to
after running fastboot getvar all script its seems my cid is supercid (111111) how come? it's S-ON,Locked, without root & running stock
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Moderator Removed
(bootloader) imei: Moderator Removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
thanks

efi2222 said:
I have a pretty new htc one m8 i have ordered
after running fastboot getvar all script its seems my cid is supercid (111111) how come? it's S-ON,Locked, without root & running stock
Click to expand...
Click to collapse
Was the phone purchased used or refurbished? If so, its possible someone unlocked the bootloader, SuperCID, and also S-off in order to make the bootloader LOCKED again, than s-on.
I don't think I've ever heard of an HTC device come from the factory with SuperCID. Although I suppose its in the realm of possibility; since SuperCID exists in the first place, HTC must use it at some point.

Yes, refurbished from aliexpress. As far as i know they come directly from HTC with the box and everything and they look like new.
So what do you suggest? There is anyway of backup the currect recovery ?

Moderator Information,
I have removed the Serial Number and IMEI numbers from your post. This is personal information and you should not post it online.
Many thanks,
Stephen

efi2222 said:
So what do you suggest? There is anyway of backup the currect recovery ?
Click to expand...
Click to collapse
After unlocking the bootloader (and before flashing TWRP) you should be able to boot TWRP remotely without actually flashing it with command:
fastboot boot recovery.img
(where "recovery.img" is the actual file name of the desire TWRP version).
Once booted into TWRP, you can then backup the stock recovery. After that, flash TWRP and root and apply whatever mods you like.
Alternately, you can get the .401 stock recovery from the following thread: http://forum.xda-developers.com/showthread.php?t=2701376

redpoint73 said:
Was the phone purchased used or refurbished? If so, its possible someone unlocked the bootloader, SuperCID, and also S-off in order to make the bootloader LOCKED again, than s-on.
I don't think I've ever heard of an HTC device come from the factory with SuperCID. Although I suppose its in the realm of possibility; since SuperCID exists in the first place, HTC must use it at some point.
Click to expand...
Click to collapse
redpoint73 said:
After unlocking the bootloader (and before flashing TWRP) you should be able to boot TWRP remotely without actually flashing it with command:
fastboot boot recovery.img
(where "recovery.img" is the actual file name of the desire TWRP version).
Once booted into TWRP, you can then backup the stock recovery. After that, flash TWRP and root and apply whatever mods you like.
Alternately, you can get the .401 stock recovery from the following thread: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
I don't understand. first i know that i have to unlock the bootloader throught htcDev and everything gets deleted. after that why would i flast TWRP? that would flash my recoevery before i can backup it.
Can't i just unlock bootloader and root and then use this app ? https://play.google.com/store/apps/details?id=com.gocshare.flashrecoveryboot
thanks

I have one more question - htc one m7 had an issue when people unlock their bootloader some few system apps got deleted because they were stored on /data and not on /system. they have fixed it on the m8?

efi2222 said:
I don't understand. first i know that i have to unlock the bootloader throught htcDev and everything gets deleted. after that why would i flast TWRP? that would flash my recoevery before i can backup it.
Click to expand...
Click to collapse
Nope. Read more carefully what I typed:
redpoint73 said:
After unlocking the bootloader (and before flashing TWRP) you should be able to boot TWRP remotely without actually flashing it
Click to expand...
Click to collapse
So in this instance (boot TWRP before flashing it) you are actually running TWRP on the phone remotely, where the TWRP file is still on your computer, and the stock recovery is still on the phone.
efi2222 said:
Maybe i should root and then use this app ? https://play.google.com/store/apps/details?id=com.gocshare.flashrecoveryboot
Click to expand...
Click to collapse
I'm not that familiar with that particular app, but I'm aware of others that do similar (Flashify). You can use it if you like. But I personally don't recommend such flashing apps; since they just are doing the same things you can do "manually" with fastboot/adb. Plus, such apps just add a unnecessary layer of complexity or additional point of failure. I've seen instances where folks have had issues performing a task with an app or toolkit; only to have it fun perfectly when they do it with fastboot; so pretty clear to me that the problem was the app/toolkit.
Plus, fastboot and adb are good tools to know (if you don't already) as they can be very useful when your phone doesn't boot into OS (something an app can't do).
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
efi2222 said:
I have one more question - htc one m7 had an issue when people unlock their bootloader some few system apps got deleted because they were stored on /data and not on /system. they have fixed it on the m8?
Click to expand...
Click to collapse
This issue still exists. You can get the apk's for the apps in question on this forum, and install them after you root.

redpoint73 said:
Nope. Read more carefully what I typed:
So in this instance (boot TWRP before flashing it) you are actually running TWRP on the phone remotely, where the TWRP file is still on your computer, and the stock recovery is still on the phone.
I'm not that familiar with that particular app, but I'm aware of others that do similar (Flashify). You can use it if you like. But I personally don't recommend such flashing apps; since they just are doing the same things you can do "manually" with fastboot/adb. Plus, such apps just add a unnecessary layer of complexity or additional point of failure. I've seen instances where folks have had issues performing a task with an app or toolkit; only to have it fun perfectly when they do it with fastboot; so pretty clear to me that the problem was the app/toolkit.
Plus, fastboot and adb are good tools to know (if you don't already) as they can be very useful when your phone doesn't boot into OS (something an app can't do).
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
This issue still exists. You can get the apk's for the apps in question on this forum, and install them after you root.
Click to expand...
Click to collapse
Thank you for replying
1. How can i boot TWRP remotely?
2. oh ****,which apk's get lost in the process? if i will not have the same exact apk's i would not be able to make OTA updates
3. Firewater is no longer active? the only way of doing S-OFF is by paying 25$?

efi2222 said:
Thank you for replying
1. How can i boot TWRP remotely?
2. oh ****,which apk's get lost in the process? if i will not have the same exact apk's i would not be able to make OTA updates
3. Firewater is no longer active? the only way of doing S-OFF is by paying 25$?
Click to expand...
Click to collapse
1) I already described this in Posst #5 above.
2) Only the system partition is checked during OTA install. Since (as you mentioned) the "missing" apps aren't on the system partition, it won't prevent OTA.
3) Correct. Firewater was an online service. So it doesn't work even if you have the binary (if you were wondering). Sunshine is the only way.
---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------
efi2222 said:
Thank you for replying
Click to expand...
Click to collapse
There's a button for that.

I don't see that you have mentionted which apps gets lost.... can you please give me a link?
2. you are right!
3. wow that's a shame.... i don't know if the whole process for having the harman kardon mod worth 25$
4. there is a way only rooting without changing the recovery?
thanks

efi2222 said:
I don't see that you have mentionted which apps gets lost.... can you please give me a link?
Click to expand...
Click to collapse
I don't know off hand, and may differ from one carrier version to another, anyway.
There is a thread about it, so just search. I don't have a link off hand.
efi2222 said:
4. there is a way only rooting without changing the recovery?
Click to expand...
Click to collapse
I think you can actually boot TWRP as I've described(instead of flash TWRP) then use TWRP to root.
Never done this myself and not sure it works; but I'm pretty sure another member here said it can be done this way.
Also keep in mind, its easy to swap back and forth between stock and custom recovery. You could have already done so in the time you took to ask the question and wait for an answer.

redpoint73 said:
I don't know off hand, and may differ from one carrier version to another, anyway.
There is a thread about it, so just search. I don't have a link off hand.
I think you can actually boot TWRP as I've described(instead of flash TWRP) then use TWRP to root.
Never done this myself and not sure it works; but I'm pretty sure another member here said it can be done this way.
Also keep in mind, its easy to swap back and forth between stock and custom recovery. You could have already done so in the time you took to ask the question and wait for an answer.
Click to expand...
Click to collapse
I will search for it.
I know that's an easy thing and i have done that to my friend about 6 months ago. Unlocked his m8, flashed recovery and made root then flashed original back to get OTA.
The thing is that i don't have CID so i can't download anything from the thread... Last time i have checked his cid so i knew which stock recovery i should download but now i don't know because my cid is 111111
As for the apps i am download a system dump of the rom, i hope the apks will be there.
That's really a shame that the only way to S-off is by paying 25$

efi2222 said:
The thing is that i don't have CID so i can't download anything from the thread....
Click to expand...
Click to collapse
You want the 4.16.401.10 stock recovery that corresponds with your main version.
Your MID of 0P6B10000, which corresponds to Europe, also would indicate that the .401 recovery is what you want.

Mr. Hofs Helped me before with this boot recovery so here's what I did
1. unlock bootloader
2. fastboot boot recovery.img
2.a flash supersu on recovery (now Im rooted with stock recovery intact)
3. Install flashify to back up my stock recovery (keep it very important)
4. now flash the TWRP by fastboot flash recovery recovery.img
5. go to your TWRP back up your stock rom (keep it again)
6. flash custom rom
7. enjoy

htc one m8 no sim/ network mode after Ruu install

hi all
the mother in law gave me her broken htc one m8 phone too look at as it was stuck on the htc boot screen.
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
the problem i am now having is that the phone wont let me choose a network mode as its blanked off and not able to choose, which also means when i enter a sim it just doesnt work.
i have done a fastboot getvar all and details follow
(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: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any help would be greatfully appreciated

First of all, you posted in the General M8s section. The M8s is a variant with different hardware. You have the M8 (no "s") which has it's own General forum section, but you should post questions like this in the M8 Q&A section, anyway. Don't make another post, I'll ask the mods to move this one to the right place.
s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
Click to expand...
Click to collapse
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Which TWRP backup version number did you flash? What version TWRP did you use?
---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------
s84taylo41984 said:
(bootloader) imei:
Click to expand...
Click to collapse
Is there an IMEI number listed? I know it's the right thing to leave this out, when posting online. But just want to make sure that is the case (and it is not actually missing from the getvar output as you see it). I don't want or need to know the IMEI number, just whether you can actually see it or not.

I realised i posted in the wrong section about 1 hour ago when i was looking through some other posts on here and noticed there was a differnce in the m8 and m8s.
yes IMEI is there. i just blanked it off when posting

Quote:
Originally Posted by s84taylo41984
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc...-twrp-t3086860.
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Click to expand...
Click to collapse
Oh i thought that they all worked the same, didnt realise they was so different!
Which TWRP backup version number did you flash? What version TWRP did you use?
Click to expand...
Click to collapse
I used TWRP 3.3.1-0 amd followed the whole of that guide, i thought it was RUU not stock.

s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
Click to expand...
Click to collapse
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).

redpoint73 said:
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).
Click to expand...
Click to collapse
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000

s84taylo41984 said:
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000
Click to expand...
Click to collapse
WiFi not turning on is due to restoring the wrong stock TWRP backup which does not correspond to the installed firmware. As I mentioned, this is something we could have identified much earlier, if you supplied the requested info (questions I asked days ago).

what questions did you want me to answer to answer days ago??
is there anything that can be done for me to get the phone working again???

s84taylo41984 said:
what questions did you want me to answer to answer days ago??
Click to expand...
Click to collapse
redpoint73 said:
Which TWRP backup version number did you flash?
Click to expand...
Click to collapse
s84taylo41984 said:
is there anything that can be done for me to get the phone working again???
Click to expand...
Click to collapse
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.

redpoint73 said:
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.
Click to expand...
Click to collapse
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
The TWRP backup version i flashed was 6.12.401.4

s84taylo41984 said:
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
Click to expand...
Click to collapse
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.

redpoint73 said:
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.
Click to expand...
Click to collapse
i never unlocked the bootloader just booted the phone into bootloader
the WiFi is working, just no SIM

s84taylo41984 said:
i never unlocked the bootloader just booted the phone into bootloader
Click to expand...
Click to collapse
Was the phone already bootloader unlocked when you received it? Does it say LOCKED, UNLOCKED, or RELOCKED near the top of the bootloader screen?
You can't install TWRP with a locked bootloader (while s-on).

It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember

s84taylo41984 said:
It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember
Click to expand...
Click to collapse
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.

redpoint73 said:
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.
Click to expand...
Click to collapse
I did relock it using the fastboot oem lock command.
She did have somebody look at it before me and it was the same thing.

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