Develop Bugs

(Q) Firmware

Alright... ive spent several hours trying to figure this out .... i'm getting very annoyed by it.. i've visited several firmware posts on here and it still isn't working. My htc one m8 is from at&t and i do believe that my firmware version is 3.28.401.7 (not 100%) but i also tried 401.9 and that also didn't work. I am currently s-on. I'm trying to push this over through fastboot since i'm SON and i did relock my bootloader... im throwing my hands up on this and now i'm seeking help

401 is Euro firmware, and there is now way you flashed that if you are S-on.
What radio and hboot number? What ROM did you flash?

redpoint73 said:
401 is Euro firmware, and there is now way you flashed that if you are S-on.
What radio and hboot number? What ROM did you flash?
Click to expand...
Click to collapse
i went back to stock rom. i assumed that was my version. my bootloader is 3.16.0.0000 radio is 1.16.21331931.la11g
i want to install viper but it borks my wifi

PureLife90 said:
i went back to stock rom. i assumed that was my version. my bootloader is 3.16.0.0000 radio is 1.16.21331931.la11g
i want to install viper but it borks my wifi
Click to expand...
Click to collapse
I assume you were previously on a Euro based custom ROM, and that is why the phone is telling you the main version is 3.28.401.
"Firmware" is a confusing term. But when folks here talk about it in terms of the latest custom Sense ROMs, broken WiFi, long boot times, etc. it refers to certain modules that are included with the OTA, but not a part of the ROM. These include hboot, radio, WiFi, Bluetooth, and some others.
Firmware itself does not have a specific "number" per se. Folks here will usually refer to the software number that the firmware deployed with, for lack of any other point of reference. But this can be deceiving, as if you look at your own software number or main version, it is just telling you the number of the ROM, which will change whenever you flash a ROM. To know what firmware you are on, your best bet is to look at the hboot and radio numbers.
Your hboot and radio version indicate you are still on 1.x firmware, and therefore flashing any 2.x or 3.x custom ROMs will result in some serious bugs like you are experiencing (broken WiFi, also long boot time is common).
You need s-off to manually update the firmware. If you do decide to s-off and update the firmware, there are various guides for doing so. But for AT&T, I recommend the following thread, as Wonders_Never_Cease deals with the AT&T variant exclusively, and has the most experience with making the phone work seamlessly on AT&T's network.
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Your other alternative is to return to stock ROM and recovery, and update when the 3.x OTA rolls out (should be soon), which will also update your firmware to the latest.

Help with SIM unlock & more help.

Hello this is my first HTC device and I just learnt about Hboot, Firewater, S-off, and RUU terms.
These are my AT&T HTC M8 with 4.4.2 OS on it, Just had it S-off and Unlocked bootloader.
Can I know the following things...before flashing anything onto this
1-> Can I SIM unlock it using the Config.dat method as the device was not at all updated ?
2-> Changing CID to SuperCID grants me access to all RUUs but that's not needed as I will use customROMs based on Sense and AOSP right ?
3-> In order to flash and all I must be S-off I did it So now I can use ViperROM 4.4.4 but before that the viperrom page says need for an updated firmware >3 mines on 1.5, So if I flash any will the S-off goes away ?? & found this thread here for firmware updates but it says red text, can I know whats that ??
4-> How can I convert this device to a fully unlocked device like dev edition/ international version ?
5-> Most important of all what makes this device go hardbrick and S-on again (Firmware flashing, RUU etc, Like to know what will cause this since the device is S-off can I assume this device won't brick like Nexus phones).
Sorry for this lengthy post, never used a HTC device wanted to make sure all is well.
Thanks :fingers-crossed: !!

S-OFF allows you to do all sorts
I used the Sim unlock method after i S-OFF my At&t device just because and really couldn't tell you if worked cause I actually like At&t .
Supercid does allow for flashing other gsm firmware/ruu
Yes you would want to be as close in firmware to gain the best running experience when flashing Roms above your current firmware
S-OFF only changes if you do it the way you gained it
Being S-OFF you could flash the wrong ruu and hard brick your device ( CDMA device hardware I believe could brick your device along with the wrong device kernel could also brick it )
Nexus is pretty solid but can be bricked

Thanks for the quick post :good:
So I will go ahead and update the firmware w.o redtext (just noticed it's the one that says "This build blah blah" when bootup) then I'm good to go for the flashing all stuff ??
I can also flash a non sense based rom after using sense based Viper ROM / ARHD / etc without any issues, now is my device basically a Dev Edition plus the RUU & CID editing is only needed If I ever need going back to stock (though it wont happen) or flash regional firmwares or converting to GPE, DEV, WWE editions rt ?
Lastly my device ID it says M8_UL_CA will it change after I flash a ROM or Radio or Firmware ?

Ashtrix said:
Thanks for the quick post :good:
So I will go ahead and update the firmware w.o redtext (just noticed it's the one that says "This build blah blah" when bootup) then I'm good to go for the flashing all stuff ??
I can also flash a non sense based rom after using sense based Viper ROM / ARHD / etc without any issues, now is my device basically a Dev Edition plus the RUU & CID editing is only needed If I ever need going back to stock (though it wont happen) or flash regional firmwares or converting to GPE, DEV, WWE editions rt ?
Lastly my device ID it says M8_UL_CA will it change after I flash a ROM or Radio or Firmware ?
Click to expand...
Click to collapse
Yes, you can flash any ROM. If you plan on running GPE, you will need to convert back using a WWE RUU as GPE uses different sized partitions making the system partition too small to run Sense based ROMs.
Your device ID will change to M8_UL after flashing WWE firmware, but it isn't anything to worry about.

xunholyx said:
Yes, you can flash any ROM. If you plan on running GPE, you will need to convert back using a WWE RUU as GPE uses different sized partitions making the system partition too small to run Sense based ROMs.
Your device ID will change to M8_UL after flashing WWE firmware, but it isn't anything to worry about.
Click to expand...
Click to collapse
Thanks a lot !!
While GPE is a trade off for only AOSP, with DEV/WWE I can run any ROM based on Sense/AOSP i.e GPE & including the Lollipop right ?
So before proceeding I will update the Firmware first to a 2.xx or 3.xx then run an RUU based on DEV/WWE for conversion
Sorry for so many doubts, slowly learning about HTCs devices

Ashtrix said:
Thanks a lot !!
While GPE is a trade off for only AOSP, with DEV/WWE I can run any ROM correct ?
So before proceeding I will update the Firmware first then run an RUU based on DEV/WWE for conversion & for the last If I need to run Lollipop I should flash firmware again for v5 base or the WWE/DEV RUU (I think the Dev edition had got the lollipop Update) has the Firmware, Radio packed with it ?
Click to expand...
Click to collapse
The RUU contains the firmware. No need to flash it twice. You could just flash the WWE firmware if you are on Sense right now. Mostly RUUs are used to fix devices that are experiencing issues, or for converting GPE/Sense.
Running the RUU wipes EVERYTHING, so flashing the firmware is preferable. The WWE 5.0.1 firmware should be out soon, but DevEd is out now. If you wanted to convert to DevEd, there are plenty of tutorials on XDA. I'm really not up to speed on running DevEd firmware.

Found this page for all stuff & this thread for conversion.
& what's this .401 stuff in the first thread ?
I'm ok with full wipe anyways so I can use the RUU or the other recovery way for the conversion right ?

Ashtrix said:
Found this page for all stuff & this thread for conversion.
& what's this .401 stuff in the first thread ?
I'm ok with full wipe anyways so I can use the RUU or the other recovery way for the conversion right ?
Click to expand...
Click to collapse
401 is International WWE firmware. For example, my firmware version is 3.28.401.9 Verizon's latest firmware is 3.28.605.4
If you are okay with the full wipe, the RUU is probably the best way to convert, but the recovery method with stock recovery and stock nandroid would work too.

xunholyx said:
401 is International WWE firmware. For example, my firmware version is 3.28.401.9 Verizon's latest firmware is 3.28.605.4
If you are okay with the full wipe, the RUU is probably the best way to convert, but the recovery method with stock recovery and stock nandroid would work too.
Click to expand...
Click to collapse
Thank you verymuch for clarification !!!
Will do the work tmrw, its 2AM here

I've been fully converted GPE and back twice and after successfully converting back to Sense this last time I chose the Dev edition backup and stock recovery method followed by the proper CID&MID to take the OTA update witch is now lollipop
So basically I now have a lollipop firmware to run with the stock GPE lollipop ROM and you bet it runs great

Phone stock in bootloop after flashing custom rom

So I installed ViperOne M9, the latest version, everything went fine, the download didn't fail, but after rebooting the phone just boots to the bootloader. I can access recovery mode, and download mode but I can't do anything else. I'm not sure what went wrong, though I suspect it might have been that my phone wasn't updated to the latest firmware, I thought it was but I think it wasn't. I made a TWRP backup and placed it on my SD Card but it doesn't seem to be reading it since nothing shows up in there.
In summary I switched to ViperOne M9 from stock, my bootloader is unlocked and my phone is rooted. Its S-On, and it seems to be rebooting every so often. Can anyone help me, this is my first time flashing a custom ROM and everything seemed to be going well until this step.

ArgusPMC said:
[...]
ViperOne M9, the latest version
[...]
S-On
[...]
Click to expand...
Click to collapse
You need the Android M firmware for the latest Viper version. Not every SKU got that update already. What's your current firmware version (stated in Download Mode in the line with "OS" at the beginning)?
Edit: Pressing and holding the power button and both volume buttons at the same time (for a certain amount of seconds I always forget - was it something around 30?) should end the bootloop and make your phone return to Bootloader Mode.

My current firmware is 2.10.709.180. I looked into the Backup and RUU collection too, though I wasn't sure about what to do with that. I did see a TWRP backup for version 2.10.709.1, but I'm not sure if that's the same as the firmware version I have, give those two digits at the end with my phone. Otherwise I guess I could use an RUU if I understood correctly, but I got that I should look for a specific one for my phone.
My CID is also HTC__621 if that helps anything. I'm also not sure about S-ON, should I go S-OFF, I know there's an app that does it for $25, and if it is better for custom ROMs then I have no issue paying that.

If I'm not mistaking your firmware version belongs to the first of the two updates that install Android M on the Taiwanese version (SKU 709) of the M9. So you probably only installed the preparing one and not the Android M one itself. Unfortunately no one contributed a backup for that version and I don't have enough time at the moment to create one. Since you're S-ON you can't use any of the RUUs either because S-ON prevents you from downgrading or changing to a different SKU. And there is no RUU for your firmware version which is accessible for free.
I would recommend installing one of the Android L custom roms (e.g. Viper One M9 3.5). After that you have four options:
Wait and hope that someone creates and uploads a backup you could use. (Can be combined with option 2)
Wait for an Android M RUU for your SKU. (There's no guarantee that there ever will be one.)
Get S-OFF via Sunshine so that you could use one of the older RUUs for the SKU 709. (They can be found in my google sheet.)
Use this RUU service.
If I were you I would choose option three since S-OFF makes getting back to stock so much easier and you're independent from others uploading a backup that corresponds to your current firmware since you can use any RUU you want with S-OFF. But don't feel pushed by me to choose option 3 (since that's not my intention). It's completely your choice.

I'll just go S-OFF, seems like the easiest solution. I was going to do it anyway, so I might as well do it now.
EDIT: Thanks, your solution worked out for me, now I've just got to use the RUU I downloaded and with that I can go ahead and get the Android M firmware I need.

HELP need serious advice here.

Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.

kalel29 said:
Hi,good afternoon,my friend brought me his HTC one m9,because i have experience with these things, i have flashed many devices of different brands but this is my first HTC device.
Well the problem is this:
He unlocked the botloader,installed TWRP ,super SU.zip (via twrp) and a custom rom with s-on,after that he lost signal,the phone does not have imei and baseband is uknown.
I've searched trough xda ,before posting this,so i came across with a thread that said that the phone can recover signal flashing a custom rom and a kernel,did that with no success. And also i've read that returning the bootloader to locked status,will allow me to flash a RUU file in order to get back to stock.
So, i relocked the bootloader,using CMD, but now the phone just boots into bootloader ,i can enter download mode aswell,but its stucked there.
Phone is recognized by windows,via fastboot.
So,the phone status is bootloader relocked,and s-on.
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Any suggestions are very apreciated. Thanks fot your time.
Click to expand...
Click to collapse
For download mode SD card method:
Make sure you're using an external SD card, not internal storage.
Make sure SD card is formatted properly.
Make sure file is named 100% correctly and is meant for that specific carrier /model.
No reason it shouldn't work.
Sent from my HTC6545LVW using Tapatalk

kalel29 said:
i´ve tried flashing the RUU via sdcard on download mode and gives me error,also i tried using fastboot commands and the result is the same,i can not flash the RUU file.
Click to expand...
Click to collapse
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.

Flippy498 said:
Are you sure you flashed the correct one? Some basic information about firmware versions, RUUs and instructions how to flash them can be found in my sticky thread in the general section.
Concerning the reception problem: It's important whether you tried to use a sense-based custom rom or a non-sense-based one. The mono-kernel only works with non-sense roms like CM or Candysix. Moreover the reception problem has been covered in this thread some days ago. If you want to use a sense-based rom the re-flash boot.img "trick" might be working for you, too.
Sidenote: There is absolutely no need for flashing SuperSU if you are going to erase the system and to flash a custom com. It doesn't harm the device but it's a waste of time.
Click to expand...
Click to collapse
Yes I flashed the one for my operator. Can I flash another RUU?
About your links, I'll check them when I get back from work. Thanks.

Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.

Flippy498 said:
Is your phone branded by your carrier? (Can be checked by looking at the SKU of the currently installed firmware.) If not then it's the wrong RUU. Is the RUU made for the same firmware version as the one that is currently installed on the phone or does the RUU even have a newer version? If not then it's the wrong RUU.
Click to expand...
Click to collapse
Hi again, the phone is giving me this error :

im still lost ,hope this helps to point me in the right direction.
Code:
D:\Francisco\Desktop\HTC\fastboot_adb\fastboot_adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.44.600.1
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: HTC__332
all:
finished. total time: 0.033s
Thanks

You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.

Flippy498 said:
You still didn't mention the name of the RUU you wanted to flash. However a quick search for your SKU (Telcel Mexico) showed me that there is no RUU available you could use. The only one I could find is linked in my thread and that one is too old for your phone since you can't downgrade the firmware with S-ON. You either need to re-unlock the bootloader, flash a sense-based custom rom and buy the sunshine app or try to find someone who has a java card. Both solutions would set the phone S-OFF so that you would be able to use that old RUU. Alternatively you could contact Llabtoofer (a link can be found in my thread and in my google sheet). He has a RUU service with RUUs that are not available publicly*. Neither the sunshine app, nor a java nor the RUU service are for free. Llabtoofer and the sunshine app cost nearly the same. I don't know how much you need to pay for java card services. Be aware that even if it's OK if the phone is running a custom right now** and you don't want to use any of these solutions that you still lack a way back to stock if a new OTA (like the one for Android N) gets distributed and therefore you won't be able to install it.
If you use the old RUU all OTAs that got installed on your phone will need to get re-installed.
However you choose you should read the tab "make your own backup" of my sheet after the phone got recovered and all available OTAs got installed but before anyone starts flashing anything, again. This way you will learn how to create a backup that will help you out if you face such a situation, again. Instructions how to restore such a backup correctly can be found in the tab "twrp backups".You'll always need to create a new backup when a new OTA got installed on your phone and you want to re-root it. Besides if you're willing you could upload the backup (and any upcoming ones) and share it(/them) with the xda community by posting the download link(s) in my thread.
* He wants to know the hboot version of your phone of you request his help. Since the One M9 has no hboot but an aboot and that one never got updated you can enter version 1.0.0.0000. That's the current aboot version.
** Possible solutions for recovering the reception can be found in my first post in this thread. There is no need to flash a RUU since your IMEI and your baseband are still intact but the boot.img of the rom you tried to use was/is incompatible.
Click to expand...
Click to collapse
Ok,thanks, and yes,the RUU I was trying to flash I the telcel one.
I'm going to tell my fiend that he needs to pay in order to get his phone working.
Thanks again for everything. Have a nice day.

Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.

kalel29 said:
Update
I managed to unlock the bootloader again, the phone boots, but it has no signal.
Do I need sunshine and then flash any ruu?
Or what can I do? BTW my friend agreed to pay for sunshine.
Click to expand...
Click to collapse
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.

Flippy498 said:
Is it a sense-based rom? If yes, did you reflash the stock boot.img? Or is it a non-sense-based rom? In that case the mono kernel which is linked above needs to be flashed for recovering the reception.
If you're currently using a sense-based rom (which is not an HTC 10 port - e.g. Viper one m9 4.3) then you can install the sunshine app and start it. The app will explain the rest of the procedure. Just google "sunshine s-off" and you'll find it. After your phone got S-OFF you simply need to try reflashing the RUU.
Click to expand...
Click to collapse
The phone has the ICE rom,Twrp and superSU,I think it's a sense-based rom, sorry I can't give you more info, as I said I'm new in flashing HTC, but I'm learning thanks to you.

ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.

Flippy498 said:
ICE is sense-based. It's using HTCs own launcher and framework which is called Sense. Examples for non-sense-based roms are CM, CandySix or other AOSP roms.
Depending on the version of ICE that got flashed on the phone you might need to revert back to an older version*. The newest ICE rom is based on an HTC 10 port and I've read several posts of users reporting that they couldn't use sunshine with an HTC 10 port.
* I don't know which version that would be. I've never used ICE so you would need to figure that out on your own.
Click to expand...
Click to collapse
So basically, no matter what rom I flash,sense or no sense based, I will need sunshine in order to have a working baseband?

No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.

Flippy498 said:
No. Sunshine is needed for getting back to stock for installing upcoming OTAs. And in case you want to use a sense-based roms it's needed for being able to backup the stock boot.img. As explained before, you need to re-flash that one after you flashed the custom rom. The boot.img of 3.35.y (y is a placeholder for any possible number) custom roms isn't compatible with 3.x firmware if x is not equal to 35 (as in your case). At the moment your only option for not having to use sunshine would be flashing a non-sense-based rom and the kernel I linked in an earlier post. But as explained before you wouldn't be able to install upcoming updates like the one for Android N if you choose not to use sunshine.
Click to expand...
Click to collapse
Finally i have signal again,flashed slim 6 and monokernel. Thank you so much,i've learned something new about HTC now im going to return the phone to my friend,also i explained what you told me in order to have a sense based rom.

HTC M9 Dev S-Off 3.35.617.21 Needs A Upgrade! :p

Good Evening Helpful People,
I'm currently in a predicament with my M9 Dev Edition on trying to upgrade to the latest Android 7 firmware...
I forgot to make a stock backup using TWRP while S-Off to restore a factory state to use the RUU.exe from the HTC site, and I'm having troubles upgrading to 3.35.617.31 to have the "base" to take the 4.14.617.6 RUU.exe successfully.
**I'm currently on 3.35.617.21
*I understand how to change my CID and MID with S-OFF
*I can not find a stock 3.35.617.21 recovery.img to allow the RUU.exe to work
*I have no intentions to turn my S-OFF to S-ON
*I'm un-rooted "TWRP Backup Save" (No SuperSU) with TWRP as my custom recovery
*I can re-root whenever needed.
*ADB and Fastboot drivers are totally fine
I know that there is probably 3 or 4 different ways to go about my problem and I like to be resourceful on my own, but I would super appreciate it if someone here would lead me on the right track!
SeventiesPaintbox

I'm a little confused - what problem are you running into with the Android 7.0 RUU (4.19.617.1.) from the HTC website? A non-stock recovery shouldn't be an obstacle to using a RUU. Assuming you're not worried about your phone being reset to factory*, you can use the RUU executable or install it via the SD card method.
I'm still learning, so maybe I'm missing something obvious - please let me know.
* As you know, your internal memory is wiped and your phone returned to stock system & recovery - but I'm pretty sure you don't lose S-OFF from RUUs. I've used RUUs several times since getting S-OFF and still have it.