Develop Bugs

HTC One M8 - Stuck at Boot Screen after SkyDragon Flash.

Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.

Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.

redpoint73 said:
Is your firmware up to date? Not sure about Skydragon specifically, but long boot times (along with broken WiFi) is often a symptom of outdated firmware.
Let the phone alone for 10 minutes or so, and see if it eventually boots, and isn't actually "stuck" (but rather just takes a REALLY long time).
To flash a different ROM, adb push it to internal storage, or put in on your SD with a USB card reader connected to your computer. Then boot into recovery and flash.
Click to expand...
Click to collapse
Hello,
I've actually tried flashing another ROM "Android HD Revolution" I believe. The phone shows the HTC Screen along with some red text at the bottoms saying "this build is for developer purposes only....". The phone then stays on the HTC screen for ~3mins then reboots and continues to boot loop.

You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app

OLEO34 said:
You just need to flash the new firmware that is found in the sky dragon OP.
Easiest way is to use fastboot. Google fastboot firmware m8. Lots of guides out there. It's only a few commands.
Edit: Should have asked if you are s-off. That will make a difference in your ability to flash new firmware.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Hello Thanks for the reply.
However, I am currently S-ON, I have searched ways to achieve S-OFF but they all require installing a ROM. However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.

Default-G8way said:
... However, I cannot flash any rom, I will just get the bootloop. If you could advise on a method that would work for my situation, I would be very grateful.
Click to expand...
Click to collapse
Start with fastboot getvar all command in fastboot/bootloader, put the result here (delete serialno and imei no.) .. then we'll see whether is there any stock ROM available for your device.

Default-G8way said:
Hello Everyone,
I am having an issue with my M8.
I decided to try out SkyDragon, give it a shot.
I downloaded the ROM, put it on my SDcard. Flashed Philz 6.25 recovery, did NOT make a nandroid backup (I know i'm an idiot),then proceeded to flash the rom via Philz.
I flashed the Rom, and followed all the instructions, I then rebooted the phone. Still stuck at the bootscreen. I read the Q&A and tried to flash the rom multiples times. Still stuck on the boot screen. I have an unlocked bootloader with S-ON.
I just got this phone a few months ago and I am unable to take it out of this state. Could use some help. Thank you.
Click to expand...
Click to collapse
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.

lilbigdude1 said:
You needed to make sure you have the latest GPE software, s-off and supper cid... Also you need to know and have ADB/FASTBOOT installed on your PC.. All which can be found throughout all of the various threads.... Right now you soft bricked your device and needed to return to stock... And stay the process over.
Click to expand...
Click to collapse
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.

Mr Hofs said:
You don't "need" the latest gpe software. The rom runs fine on the latest sense firmware.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=53838669

So ? Just like i said.....no need for gpe

Issue Resolved!
Hello Everyone.
The issue is resolved. Through many flashes, wipes and commands. Its done. I was able to flash the rom, let the rom sit for ~20mins, and it finally booted up into Lollipop. I now have no wifi. However, I should be able to follow the FAQ to get S-OFF and fix my wifi!. Thanks team. I really appreciate it.

HC One (M8) Hanging loading TWRP recovery

I have an M8 that I unlocked, rooted and installed a custom rom on. It was my brothers phone and have not touched it in quite a while but I tried to enter recovery on it and it just hangs at loading recover. I am able to get in to the bootloader, so I used fastboot to install the latest TWRP recovery image. No change, it just sits there loading recovery and then reboots and loads the rom.
My next step was to try updating the bootloader as it is on 3.16 and I need to get atleast to 3.19 for the latest CM12.1 roms. It is a CWS__001 device and with all the RUU's out there, I am totally confused and cannot find the one that I should be using.
I would appreciate anyone that can get my past the hanging recovery and pointing me to the proper RUU would be awesome!!!
Thanks!!!!

Flash an older twrp like the 2.7 series. The newer ones don't work on old hboots.

Thanks Mr Hofs!!!! That did it. I installed 2.7.1.0 and it works now. I appreciate the help.
Now to find the latest ruu for this phone and I will be all set!

bluecobras09 said:
Thanks Mr Hofs!!!! That did it. I installed 2.7.1.0 and it works now. I appreciate the help.
Now to find the latest ruu for this phone and I will be all set!
Click to expand...
Click to collapse
Here is the latest AT&T RUU direct from HTC's US website. Read the Manual System Update instructions (if you need them). The RUU download is at the end of the instructions.

Well, I finally found the RUU I used to update the bootloader on my original M8. It was the same model and a CWS__001, I followed the instructions I used before and first install failed as it said was usual and ran it a second time and it said it was successful. But after the fastboot reboot, it makes it to the white HTC screen and no further. Can't get it to go in to the bootloader or nothing so I think it may be bricked.
But thanks for the pointer.

bluecobras09 said:
Well, I finally found the RUU I used to update the bootloader on my original M8. It was the same model and a CWS__001, I followed the instructions I used before and first install failed as it said was usual and ran it a second time and it said it was successful. But after the fastboot reboot, it makes it to the white HTC screen and no further. Can't get it to go in to the bootloader or nothing so I think it may be bricked.
But thanks for the pointer.
Click to expand...
Click to collapse
Found the RUU that you used on your old phone? Did the RUU you ran contain the same or newer firmware than what was already on your new phone? If you aren't S-Off you can not flash an older firmware.
Your phone turns on, so it isn't bricked. Hold power + vol up to force a reboot (it could take up to 20 seconds). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down and hold it till it boots. That'll take you to bootloader.
Click the link I provided and download the newest RUU available for the AT&T M8 directly from HTC. Run that and hopefully your issues will be solved.
Good luck.
EDIT: I now see from your original post that you are still on the older bootloader, so the RUU you used should be newer that what you have (3.16 bootloader)
Still, give it another go. I'm not sure what RUU you have now, but downloading it again can't hurt.
Don't give up. You can fix this. Even if the RUU doesn't work (it should) there is always a way.

Thanks xunholyx, I will give it another try. The RUU I have gives me 3.19. It is the one I used on my personal M8 and it went without a hitch. I will follow you directions and report back.
Thanks!!
xunholyx said:
Found the RUU that you used on your old phone? Did the RUU you ran contain the same or newer firmware than what was already on your new phone? If you aren't S-Off you can not flash an older firmware.
Your phone turns on, so it isn't bricked. Hold power + vol up to force a reboot (it could take up to 20 seconds). AS SOON AS THE SCREEN GOES BLACK slide your finger from vol up to vol down and hold it till it boots. That'll take you to bootloader.
Click the link I provided and download the newest RUU available for the AT&T M8 directly from HTC. Run that and hopefully your issues will be solved.
Good luck.
EDIT: I now see from your original post that you are still on the older bootloader, so the RUU you used should be newer that what you have (3.16 bootloader)
Still, give it another go. I'm not sure what RUU you have now, but downloading it again can't hurt.
Don't give up. You can fix this. Even if the RUU doesn't work (it should) there is always a way.
Click to expand...
Click to collapse

bluecobras09 said:
Thanks xunholyx, I will give it another try. The RUU I have gives me 3.19. It is the one I used on my personal M8 and it went without a hitch. I will follow you directions and report back.
Thanks!!
Click to expand...
Click to collapse
And you will have to run it twice. The first time will update your bootloader. After you get a fail, don't disconnect or reboot, run the RUU a second time. (you'll get a message saying "flush" it again) This is normal with the older hboot.

Awesome, it is back online. Turns out the reason it would not boot was the complete lack of software on it. I do not remember that from my phone last year when I did it. The RUU update actually completed fine. I didn't know about the volume-up+power, slide to volume-down at black screen. That got me back into fastboot, unlocked bootloader, installed latest TWRP and rom and now all is well with the world again!!!.
I thank you for your time and knowledge xunholyx!!!
xunholyx said:
And you will have to run it twice. The first time will update your bootloader. After you get a fail, don't disconnect or reboot, run the RUU a second time. (you'll get a message saying "flush" it again) This is normal with the older hboot.
Click to expand...
Click to collapse

HTC M9 won't boot after update - can't flash anything, factory reset or unlock bl..?!

Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(

At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.

fernandezhjr said:
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
Click to expand...
Click to collapse
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?

zroice said:
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
Click to expand...
Click to collapse
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.

Aldo101t said:
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Click to expand...
Click to collapse
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course

zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
lol, sorry missed that part
---------- Post added at 07:50 PM ---------- Previous post was at 07:26 PM ----------
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
I do believe if you can get to download mode you can do a factory nreset from there, if that will help you.

zroice said:
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
Click to expand...
Click to collapse
What about flashing an older RUU and trying to take the update again?

fernandezhjr said:
What about flashing an older RUU and trying to take the update again?
Click to expand...
Click to collapse
cant find any ruu for that branding - if you see/saw one please let me know.

zroice said:
cant find any ruu for that branding - if you see/saw one please let me know.
Click to expand...
Click to collapse
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.

Flippy498 said:
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Click to expand...
Click to collapse
*downloading with fingers crossed*

Failed: -2, 19 to flash via downloadzip or smth like that

Can you flash twrp recovery? If you can, maybe you can flash a stock backup from someone else.

zroice said:
Failed: -2, 19 to flash via downloadzip or smth like that
Click to expand...
Click to collapse
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.

Flippy498 said:
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Click to expand...
Click to collapse
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?

zroice said:
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
Click to expand...
Click to collapse
Yes, 2.10.206.2 is the latest version for now. If there were a RUU with your firmware version then using it would be the easiest way to solve your problems. But as far as I know the only existing ones for O2 are for 1.32.206.6 and 1.32.206.15. But with S-OFF you would be able to use the older RUUs, too.
I never used a java card so my knowledge about this topic isn't that outstanding. I know that it is a small, SIM-Card-like looking thing that allows you to S-OFF your phone. Usually they cost several hundred euros/dollars and the number of times you can use them is limited. Since verizon blocks bootloader unlocking these cards are the only option if a verizon users wants to flash anything on his/her phone. Some German phone shops offered S-OFF by java card, too, before sunshine got updated for the M9. That's why I gave you the link to Android-Hilfe. (And that's actually all I know about that topic.)

i need this rru please any one have to uplode link
thanks

Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.

theadra said:
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
Click to expand...
Click to collapse
Bootloader and s status are irrelevant. The phone will flash regardless.

HTCone M8 Not able to update firmware to 4.28.502.10

I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.

suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.

suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
You don't need to relock with s-off. Something else is going on. Post your getvar data (be sure to delete IMEI and serial number as these are personal info).

xunholyx said:
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.
Click to expand...
Click to collapse
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.

suzyq42 said:
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.
Click to expand...
Click to collapse
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.

suzyq42 said:
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.
Click to expand...
Click to collapse
As @redpoint73 said earlier, post your getvar. Hook up to your PC, get into ADB/fastboot and enter the command fastboot getvar all.
I was helping someone else with AT&T last night on the VenomROMs website, and mistakenly thought you were superCID when it was him. That won't be a problem though. It will abort with a CID mismatch.
The reason I suggested WWE firmware is that Marshmallow is coming out soon and WWE will get it way before AT&T updates.
If you want to stay on AT&T firmware, you could run the official RUU from HTC's US website.
Post your getvar, and we can go from there.

suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
OK here should be the final solution, when you are in fastboot/hboot screen you must enter "fastboot oem rebootRUU" then once you see the black screen with HTC logo then you may flash the firmware, you can not flash firmwares on PC while fastboot is actively running, but of course run the firmware flash command TWICE! first flash it will fail because HBOOT gets updated by it self, then on second flash the rest of the firmware files get updated.
If you have S-OFF then you never have to lock your bootloader again.

HTC M8 stuck in bootloop

Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.

So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup

ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.

Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.

You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.

Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).

redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.

Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).

redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.

Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.

redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?

Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.