Develop Bugs

corrupt bootloader s-off

hi
i just downgraded my desire hd and then did a radio s-off but then i wanted to do a S-OFF.
i used the easyS-off but then it said bootloader corrupt do not reboot.
i already tried without "I Have Radio S-OFF" then it just says connection problem
i have charged only and debugging turned on
what now?
thnx

hmm what about Easy Radio Tools?

i used that for radio s-off

it worked now!! thnx to this guy
http://forum.xda-developers.com/showthread.php?t=999219
second post!!

I would be hesitamt to reboot though, haven't used the easytool as I personally prefer to know what steps are being carried out, but if it warns that the bootloader is corrupt I wouldn't reboot until I knew the situation is corrected.

Hello guys (I suppose most of the visitors are in fact guys ),
I downgraded my DHD to 1.32 this week and managed to get root-access and did a successful Radio S-OFF using the One click Radio S-OFF.
However; this morning I tried the One click ENG S-OFF but the first time I tried to run the tool I got an error stating "Connection error (SD)". Rebooted my phone and tried again.
This time I got the error "Bootloader corrupt, contact XDA".
After I almost crapped myself I started to search for a solution; someone on this forum stated to go to application settings - superuser - and clear data. Did it and then I got a bunch of applications which did a forced close.
Tried the One click tool again and got the same error (Bootloader corrupt).
In the meanwhile I got all this popups regarding android.process.acore needed to close which finally resulted in an unusable phone so I rebooted...
Thank god this went alright and my phone is up and running again but...
I think the last failure was probably caused by the One click app that doesn't have root access (didn' t get a popup though), but I'm a little afraid to try it again.
Does anyone know if it's save to try it again?

enz0123 said:
Does anyone know if it's save to try it again?
Click to expand...
Click to collapse
Why not do it longhand? Concise instructions are available here, I realise you already have root but even if you follow the instructions from the begining they aren't gonna do any harm.

Thanks, that could be a solution however I found out that I didn't check the box "I have Radio S-OFF
Tried again with the checkbox checked but got the same error again.
The files that were copied to my SD-card at the first attempt are still there.
Is it safe to remove these files?
Maybe that solves it...

It is very important, that you agree the super user request while the tool does its job.
I had the same problems some weeks ago (bootloader corrupt), because during the flash my display timeout was reached and the super user request failed (black locked screen).
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.

KaseDesire said:
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.
Click to expand...
Click to collapse
Which is one reason I favour doing it long hand at least then youd know it's failed to flash the bootloader

Hmm, strange.
When I boot into the bootmenu (vol. down + power) it states the I'm already ENG s-OFF and hav CID 111111...
Something must have gone right....
However I can't find the line anymore that states that I have Radio S-OFF, is this normal behaviour?

KaseDesire said:
It is very important, that you agree the super user request while the tool does its job.
Click to expand...
Click to collapse
Exactly! The instructions don't mention it, but when you run the easy s-off exe, it goes through a few steps and then your phone will ask you to allow superuser access. So have your screen on and be ready, and THEN run the easy s-off utility. That's all it was for me. I hit "OK" on the error message, tried it again but this time watched my phone and allowed SU access, and it worked fine.

Hi,
I'm posting here because i had the same problem ( Bootloader corrupt etc ... ).
First I rooted my DHD, and made it Eng s-off and installed a rom a few month ago.
Today I wanted to install another rom, and flash the radio.
But I did not remenbered if I already had the radio s-off, so i installed the 1.32 stokified rom, used the easy radio tool ( v2.2 ) and when i wanted to use the easy s-off tool ( v05 ), the program gave me the error message concerning the bootloader corrupt and stuff. I tried it with "I have radio s-off" ticked, and when I try it with unticked, I have a connection error message.
I tried to delete the data from SU, but it didn't help, and then I noticied ( remenbered ) that SU did not asked me the authorizations when I used easy radio tool ans easy s-off.
Anyone have an idea how I can fix that ? Maybe unistall/reinstall SU ?

HTC Desire HD radio S-OFF steps
http://www.youtube.com/watch?v=dTFphGbgqbQ&feature=player_embedded

Yes I did that after reinstalling the 1.32 rom, excepted the Visionary steps.
The root is permanent no ? I did it on my previous rom, so I don't have to root it again when I install another rom ?
Anyway, my DHD rebooted when I tried to secure the battery compartment, the bootloader wasn't corrupted, it's fine.
So I checked the bootload, I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?

HornAdama said:
I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?
Click to expand...
Click to collapse
Yes, you can install custom roms and flash radios now.

Quick RUU Question, need to bring my phone back to TMO

I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?

Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.

There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.

jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.

ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.

Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?

ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.

Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????

So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!

ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.

jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?

ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.

jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!

n00b stuck on old CM because too dumb to be able to upgrade bootloader

My ATT HTC One M8 was rooted using the 'official HTC' method soon after purchase and I was able to get CyanogenMod installed via their windows install tool back in the day so I didn't have to really understand what I was doing. It still runs CM11 quite well, but I'd really like to upgrade to CM12 if for no other reasons then the security updates. When I try to upgrade to CM12 though I get this error:
This package supports bootloader(s): 3.18.0.0000, 3.19.0.00000; this device has bootloader 3.16.0.00000, Installation aborted.
My recovery is ClockworkMod Recovery v6.0.4.8
Here's my bootloader screen:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.58.502.1
eMMC-boot 2048MB
Apr 18 2014,16:06:33.0
I don't know what I'm doing.
After six months of occasionally messing with this I still haven't figured out how to upload the boatloader. I only barely understand the stuff I read on this site. Most things have pointed me to do this:
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
But I'm not s-off, there is a ton of downloads and steps and 150 pages of comments (!) so if there is something burried in there that will help me I can't find it. I tried blindly applying one of the firmware downloads but it didn't work. and it was probably the wrong one anyway.
Everything else pointed me to return to stock and accept the OTA update with this thread:
http://forum.xda-developers.com/showthread.php?t=2696282
But I again got lost, and never got this working. Once I got brave and spent the better part of a day trying to return everything to stock, but I couldn't figure out how to do it in the end and was super-happy to get back where I started and have a working phone again. I don't recall the exact problem I had, but I remember trying several RUUs - not being sure which one was the right one - and they wouldn't apply and that was after changing recovery versions and types several times and following random forum advice and thinking I bricked the thing a dozen times.
My question is: Is there a simple way to upgrade my bootloader ? Simple meaning exact steps to follow to just upgrade the bootloader without doing a bunch of other stuff that could brick me and I don't understand? I'm not really sure where to begin, even though I've tried a bunch of stuff, this stuff is so confusing.
Is there any help for noob like me?

You have AT&T - those threads are not for you.
You need to see this - http://forum.xda-developers.com/showthread.php?t=2751432
1. Download RUU 4.28.502.2 RUU
2. Boot your device to bootloader/fastboot and connect to PC
2. relock bootloader - command fastboot oem lock
3. Install RUU
4. re-unlock your bootloader with the unlock_code.bin that you got from HTCDev
5. reinstall custom recovery
6. install your preferred custom ROM
To run a RUU .. you need USB2.0 and latest HTC USB driver installed. If not sure, download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
install it as it will install the latest HTC USB driver then uninstall the HTC Sync Manager but leave the driver.
This will wipe everything on internal storage - backup your photos, musics & etc to PC first.

Wow, thanks for taking the time with specific steps and links! I'll try again this weekend and let you know!

thanks!
This worked perfect! I think the key was the ATT RUU, which I definitly wasn't using it before. Once done getting back to CM was a snap and I'm now in great shape! Thanks so much!

You're welcome.
Correct RUU for correct device always fix things

How to root my HTC One M8 (Android 6.0)?

I would like to root my M8, it has the latest OTA update from HTC which is Android 6.0. I have the developer edition, from what I've heard, the bootloader is already unlocked right?
I've seen some guides but most of them are outdated or they are meant to be used with Android 4.4.4.
I must say I'm not an expert when talking about phones, so is there a step by step guide to root an M8 with marshmallow? I would really appreciate any help.

The bootloader screen will indicate the bootloader status (LOCKED, UNLOCKED or RELOCKED) near the top of the screen.
In general, the process is:
1) Unlock the bootloader by HTCDev.com (if its not already unlocked).
2) Fastboot flash TWRP 3.0 custom recovery: https://twrp.me/devices/htconem8gsm.html
3) Backup your stock ROM in TWRP - lots of folks have been running into bootloop or no boot after trying to root (but probably usually when trying to use an obsolete version TWRP and/or SuperSU - but it never hurts to be safe and have a backup).
4) In TWRP, flash SuperSU v2.76 to root: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip

redpoint73 said:
The bootloader screen will indicate the bootloader status (LOCKED, UNLOCKED or RELOCKED) near the top of the screen.
In general, the process is:
1) Unlock the bootloader by HTCDev.com (if its not already unlocked).
2) Fastboot flash TWRP 3.0 custom recovery: https://twrp.me/devices/htconem8gsm.html
3) Backup your stock ROM in TWRP - lots of folks have been running into bootloop or no boot after trying to root (but probably usually when trying to use an obsolete version TWRP and/or SuperSU - but it never hurts to be safe and have a backup).
4) In TWRP, flash SuperSU v2.76 to root: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Click to expand...
Click to collapse
Thanks for the answer. Just one more question. My bootloader is already unlocked, but it says "S-ON" under "UNLOCKED", will that be a problem?

Sporting123 said:
Thanks for the answer. Just one more question. My bootloader is already unlocked, but it says "S-ON" under "UNLOCKED", will that be a problem?
Click to expand...
Click to collapse
Nope, that is just fine. S-on is perfectly okay for most mods, such as root, and flashing ROMs.
You only need s-off to do some very specific things, such as flashing modified hboots, manually flashing radio, changing CID&MID, downgrading by RUU, etc.

I have a simple doubt regarding flashing twrp. Does this means I can flash twrp through adb without getting root access to get root access.I usually root my devices using kingroot,works perfect for my old phone micromax.It also works for my htc one m8 when it was kitkat.But after I update to marshmallow Kingroot doesn't work for it,tried many times.If you could answer my question I would be very thankfull

hriatahriatpuia said:
I have a simple doubt regarding flashing twrp. Does this means I can flash twrp through adb without getting root access to get root access.
Click to expand...
Click to collapse
You don't need root to install TWRP, if that is what you mean. You just need an unlocked bootloader.

Thanks a lot,have already unlocked the bootloader.

redpoint73 said:
You don't need root to install TWRP, if that is what you mean. You just need an unlocked bootloader.
Click to expand...
Click to collapse
I've unlocked the bootloader but apparently I need to know which ver of twrp to use for my carrier ....no idea what to do there so I can't just flash the latest SuperSU from here? and how do I back up my stuff in case I mess up? Please help me i'm lost here

Hmz27 said:
I've unlocked the bootloader but apparently I need to know which ver of twrp to use for my carrier ....no idea what to do there so I can't just flash the latest SuperSU from here? and how do I back up my stuff in case I mess up? Please help me i'm lost here
Click to expand...
Click to collapse
what carrier ? if you are on gsm just flash TWRP 3.0.2-0 from official website
https://twrp.me/devices/htconem8gsm.html
after you flash TWRP recovery you will find option to backup it's too easy to understand how it works ( just check the partitions you want to backup and confirm your choices by sweep to proceed the process )
after you make a backup flash the latest supersu.zip from here ( choose TWRP installable.zip )
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Hmz27 said:
I've unlocked the bootloader but apparently I need to know which ver of twrp to use for my carrier ...
Click to expand...
Click to collapse
I think you're looking at some really outdated info or guide. TWRP hasn't been carrier specific for about 2 years; with Verizon and Sprint being the only ones you had to look out for. But TWRP was unified long ago (so Sprint/Verizon no longer requires a different TWRP version). You'll see from ahmed's link, that it specifies "All variants" of the M8. The exception would be if you have an M8s; and maybe another oddball variant or two (which are really different hardware). But as long as its a true "M8" the TWRP version linked by ahmed will work.
If you have any doubts or concerns about the M8 version, connect the phone to your computer, reboot to fastboot mode and do command fastboot getvar all and post the results so we can take a look (delete IMEI and serial number before posting).
Hmz27 said:
no idea what to do there so I can't just flash the latest SuperSU from here?
Click to expand...
Click to collapse
No, you can't flash SuperSU without first flashing TWRP. Why would threads/guides tell you to do something that isn't necessary, if you can just skip it?
Simply put, you can only flash official "signed" files from the stock recovery. You need a custom recovery like TWRP to flash SuperSU.
Hmz27 said:
and how do I back up my stuff in case I mess up?
Click to expand...
Click to collapse
Once you install TWRP, you can use it to create a backup of your stock unrooted ROM and user data. And its highly recommended to do so, before you flash SuperSU. Not only will this give you an easy way to revert/recover if something goes wrong with the root attempt; but you will also have a backup of your stock, unrooted ROM if you ever want it.
There are other ways to backup your data, but that depends on what "stuff" you are talking about (as that vague description doesn't tell us what you actually want to backup). For instance, for files, photos, etc. you can just copy and paste them to your computer as a backup.

Hello , I'm new to the whole thing guy and I want to unlock my bootloader in order to install custom rom , I looked in the fourm and I'v found an old method with all in one tool kit but I don't think it will work on my android version 6.0 would someone kindly guide me and tell me what do I need to do ? thanks .

Monzer_ said:
Hello , I'm new to the whole thing guy and I want to unlock my bootloader in order to install custom rom , I looked in the fourm and I'v found an old method with all in one tool kit but I don't think it will work on my android version 6.0 would someone kindly guide me and tell me what do I need to do ? thanks .
Click to expand...
Click to collapse
If the method is firewater, it no longer works.

fireguy85 said:
If the method is firewater, it no longer works.
Click to expand...
Click to collapse
I'm not sure what are you talking about since I'm new to the whole thing I believe that firewater has something to do with S-off which is something I couldn't do because all the guides says download firewater and the links takes me to sunshine which i believe cost me money to do ? sorry correct me if I'm wrong but I'm just a newbie beside I don't need s-off right ? what does that have to do with my problem ?

Monzer_ said:
I'm not sure what are you talking about since I'm new to the whole thing I believe that firewater has something to do with S-off which is something I couldn't do because all the guides says download firewater and the links takes me to sunshine which i believe cost me money to do ? sorry correct me if I'm wrong but I'm just a newbie beside I don't need s-off right ? what does that have to do with my problem ?
Click to expand...
Click to collapse
Firewater was an all-in-one kit used to unlock bootloader and achieve s-off. The guys that created this went on to create Sunshine, leaving firewater project behind, so any guides from 2014 are likely obsolete. Unlocking the bootloader is as simple as going to htcdev.com, making an account and following the instructions there-it's super easy. S-off isn't necessary for most.

fireguy85 said:
If the method is firewater, it no longer works.
Click to expand...
Click to collapse
fireguy85 said:
Firewater was an all-in-one kit used to unlock bootloader and achieve s-off. The guys that created this went on to create Sunshine, leaving firewater project behind, so any guides from 2014 are likely obsolete. Unlocking the bootloader is as simple as going to htcdev.com, making an account and following the instructions there-it's super easy. S-off isn't necessary for most.
Click to expand...
Click to collapse
yes that what I have done exactly I'v unlocked the bootloader this way then used the all in one kit to root but then couldn't s-off as the guide I was following said download firewater and the links take me to sunshine . I don't know much further have not tried sunshine yet and now my rom seems ok after I re-flashed it awesome rom btw still little curious about s-rom but this one will do just fine I'v been using stock for ages .

Monzer_ said:
yes that what I have done exactly I'v unlocked the bootloader this way then used the all in one kit to root but then couldn't s-off as the guide I was following said download firewater and the links take me to sunshine . I don't know much further have not tried sunshine yet and now my rom seems ok after I re-flashed it awesome rom btw still little curious about s-rom but this one will do just fine I'v been using stock for ages .
Click to expand...
Click to collapse
Firewater and the AIO (all-in-one) toolkit are 2 different things. Firewater is an (obsolete) s-off method. May have also contained a temp root, and some other things (can't remember exactly, it's been 2 years - and doesn't matter anyway - see more below). But firewater is not typically referred to as a "toolkit" or "all-in-one" (never seen it referred to that way, actually).
All-in-one toolkit (there are a couple) is a PC for unlocking the bootloader, root, and several other things (may have had a link for firewater, don't remember - again it's irrelevant for reasons below).
The toolkits are not recommended. They haven't been updated in a long time, and therefore use very obsolete files for TWRP and SuperSU (when applicable). You will have issues flashing many ROMs with old TWRP (and I'm surprised you haven't yet). Plus, you will probably find in bootloader and fastboot getvar, that the OS number is now blank (known bug in old versions of TWRP). I would suggest flashing the current version TWRP 3.1.1 using fastboot, to prevent issues moving forward. Current TWRP is fully compatible with current ROMs - but will not fix the bug of OS number being blank (need to flash firmware or RUU to fix that - but it's just a minor thing).
Firewater doesn't work, no matter what you do. It required an online server component, which the devs took offline over 2 years ago. Sunshine ($25 US) is the only current s-off method. But be aware, that most folks don't need s-off. S-off isn't needed to root, flash custom ROMs, and most other mods. s-off is only needed for very specific things, such as manually flashing radios, changing CID/MID, and some other things.

redpoint73 thank you so much for such a help truly gentleman much appreciate it .

It appears you can no longer use the usual method to unlock the bootloader. I just got this phone the other day in fantastic condition as a gift.
HTCDev told me there was an error or try again later. I'll upload screenshots later.

Not true... I used www.htcdev.com to unlock the bootloader of my HTC One M8 today.

I have this phone, with Android 6.0 and bootloader locked. However it has become practically unusable as it regularly powers off by itself, most likely due to lack of storage (there's only 0.6 GB left...). I've already uninstalled all of my few (useful) apps, I have no media on it whatsoever, but it is just filled up with bloatware that is pre-installed and gets re-installed automatically and that I thus cannot get rid of. I don't want to buy a new phone (it's in good condition) but from reading on the internet I understand that the only option is to unlock and root it, and put an oem on it exempt of all of these useless apps.
So my questions are, is this really the only option and if so is it still possible on this old machine to unlock the bootloader, and to get the right - clean - software for it somewhere?
I registered at HtC dev. There's a page that walks you through the unlocking process. So I should be able to do that part, if what FlexMcMurphy said in July last year still is true... For the rest, I'm quite new to this process but there are pages here on XDA that describe rooting and flashing. I'm ready to give it a try, but could use help if stuck.
Any reply/help would be wonderful !
Thank you in advance.
Judith

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.