Develop Bugs

[Q] Did some searches, spent more than four hours looking..

Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone

Valkalkas said:
Hello,
My adb devices is not showing my device.
I'm pretty sure I forgot to activate developer mode and turn on USB debugging. I can not flash any room and I'm stuck in a boot loop or just using TWRP. I'm completely lost in a way to get beyond this. I've been searching XDA for 4.5 hours straight and it seems some people have 80% of my problem but not 100%. I decided initially to follow a Youtube video that didn't mention anything about USB debugging so I'm wondering if that's the main issue in all of this. I've tried going back to stock RUU, through Hasoon2000's allinone but I keep getting failures. Just at a loss and would appreciate any help. I'm trying to go to the Skydragon Rom, but I'm willing to go back to stock to work my way back up. I've initially rooted this type of phone before, but I didn't follow the same method as last time(which was Hasoon's) as I thought it would work the same, I used this Youtube video, youtube/watch?v=_yo4eoCfxmE. (sorry link is weird cause I can't post links yet, add a .com after youtube!) I do not have S-Off. I just wanna know what I can do to get back to Skydragon or at least back to stock before my girlfriend beats my ass for messing up her phone
Click to expand...
Click to collapse
haha... Love :victory:
Now back to issue.
If you're in the bootloader you don't need USB Debugging enabled, you can still use the fastboot command regardless of USB debugging mode. Check
Code:
fastboot devices
not
Code:
adb devices
.
Make sure all the drivers are still fine on the PC, reinstall if you must.
On a side note, try not to use all-in-one toolkits as you really don't get to learn from using something like that. If you did it manually you'd already have a pretty good understanding on which command gets used in which instance i.e bootloader vs in-system.

I actually didn't use a all-in-one this time around but as soon as I unlocked boot loader and rooted I had issues installing the custom rom. I've used both phil z and twrp but it still gets stuck when I install the sky dragon, or viper for that matter to test and make sure it wasn't just a bad download. Earlier when I did fast boot devices it did show something but now it's just a blank space. I'm in bed now I would double check again to make sure but like I said it's been a few hours and now it's 4:38 am and I'm tired. I'll double check in the morning but I appreciate your response and I'll double check. Drivers should be good from last time but I will double check and make sure. Again thanks for responding!

Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.

Valkalkas said:
Alright, now after some rest I've checked the fastboot devices and it does show up.
Tried flashing to latest SkyDragon again and it just sits on the HTC screen before boot looping.
The device is S-On, unlocked and says tampered. I've tried flashing the boot.img in bootloader after flashing the rom but still no dice.
Click to expand...
Click to collapse
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device

ckpv5 said:
Latest skydragon, ARHD, InsertCoin and many more are meant for hboot 3.18 and above. If you boot to bootloader and see your hboot is 3.16, these ROMs won't work properly for you.
So check your hboot no.
Next ... check your CID and MID
If possible the OS version no. on bootloader too
You may need to revert to your stock ROM ... then check any OTA for your device
Click to expand...
Click to collapse
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.

Valkalkas said:
Alright yeah, my hboot is 3.16. Tried looking up ways to update the fastboot but all I've seen is requiring S-Off.
CID is CWS____001
MID is 0P6B12000
The OS is blank, just says OS- (blank space)
Gonna try flashing stock recovery again.
Click to expand...
Click to collapse
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423

ckpv5 said:
Yours is At&T (if I'm not wrong as I'm not familiar with this Sprint, Verizon and AT&T)
And there are RUU for both 4.4.2 and 4.4.3 (hboot 3.16 and 3.18) ... it's best for you to head over AT&T forum for better guidance.
http://forum.xda-developers.com/showthread.php?t=2757462
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Alright, thank you for your help. I relocked and I tried the second link you posted, but the ruu messes up after I accept the EULA and just keeps popping up boxes. Downloading the RUU from the first link now and gonna try that. I just run the RUU in fastboot usb right?
Again thanks, I had no idea to check for hboot versions when rooting/flashing in the time I've rooted some devices so guess I'm learning something the hard way.
Edit: Same thing with the first link. I feel like I'm in the wrong place trying to run the RUU in fastboot usb?

Alright, tried running the RUU's again on the black screen with the silver HTC letters as suggested by someone else and the program still acts up after the EULA.

Alright, I was able to find a nandroid backup and restore it through there, so now I'm back in business. Thanks for the help!

Returning to stock issues.

I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!

Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.

I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?

Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.

Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?

Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...

Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.

Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?

Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?

Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!

Bricked HTC One M8

Hi
Please can anyone help please?
Got a HTC One M8 on o2. I installed a custom rom (Viper One) and used it fine for over a year.
I've since changed to a S6 edge and wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Can anyone help?
Thank you

This section is absolutely filled with the same question.
Have a GOOD read here
http://forum.xda-developers.com/showthread.php?t=3086860

Ah right sorry, thanks... Will check it out

bah77 said:
I'm now stuck with a handset, everything wiped (including the operating system and backups)
Click to expand...
Click to collapse
If I'm understanding you correctly, you wiped the OS, not realizing it would cause your phone to be without . . . an operating system?

NO, the operating was wiped by accident

bah77 said:
NO, the operating was wiped by accident
Click to expand...
Click to collapse
Well the easiest way without going through any hassle to fix your phone and make it Stock/Like Brand New is to run a RUU.
I will explain how to do this process with a PC and you should be good to go :good:
1. Download HTC drivers for your PC if you haven't already Here, install and uninstall HTC Sync Manager while KEEPING "HTC Driver Installer".
2. Download the RUU that best matches your phone Here, you can possibly find a O2 RUU on xda but I did not find one my self for you unfortunately, otherwise if your phone is a GSM variant phone you can flash the international RUU from Here (Instructions would be different in this case)
3. Get your phone into bootloader by TWRP or if your phone is off then hold down VOL DOWN and POWER BUTTON at the same time until HBOOT shows up.
4. Plug your device via USB into the computer and verify that you see "Fastboot USB" on your phone's screen.
5. Run the RUU .exe file, I recommend you "Run as Administrator".
6. Follow the on screen instructions and sit back 10-20 minutes as your phone becomes brand new, do not interupt the process or you could have a permanent phone brick.

bah77 said:
Ah right sorry, thanks... Will check it out
Click to expand...
Click to collapse
Is your problem fixed ? Do you still need a RUU for this ? Or the TWRP backup that you found in that link is good enough ?

Sorry not had time to try yet but hoping to in the next day or two
Thanks for the help guys, will let you know how i get on

bah77 said:
wanted to revert my old phone back to stock rom unrooted.
In doing so I messed up!!!
I'm now stuck with a handset, everything wiped (including the operating system and backups)
I have TWRP recovery and need to re-install stock rom.
Click to expand...
Click to collapse
Seems (from the vague description) that a few things went wrong:
1) You may have been proceeding without the proper knowledge of how to return to stock, and at least somewhat, "making it up" as you went along or "experimenting". This is not the proper way to go about things when modding (or in this case "unmodding") a phone. Stick to specific instructions and guides, as already pointed out the process to return to stock is well documented.
2) No degree of wiping or factory resets is going to restore a stock ROM, if you have a custom ROM installed (if that is what you were trying to do); which is a somewhat common misconception. Also, wiping things without understanding the result is a bad idea. The Wipe options are called "Advanced" for a reason. If you don't understand what it is (or the results of wiping it) than don't do it.
The process to return to working stock has been outlined by others. But if you want more specific help, you will need to do a getvar all and post the output (being sure to delete your IMEI and serial number, as those are personal info) so we can better determine the way forward. But in summary, you have 2 choices:
a) Relock the bootloader and run the proper RUU, of one exists for your CID version.
b) Restore the stock nandroid that corresponds to your CID and main version (firmware), then flash the correct corresponding stock recovery.

Been stuck like this for 40 minutes

bah77 said:
Been stuck like this for 40 minutes
Click to expand...
Click to collapse
What did you do ?
Do you have right RUU ? Can you give the RUU name that you are using ?
I saw you use a ROM.zip .. AFAIK your O2 RUU is an exe file.
You also need USB 2.0 and latest HTC USB Drivers installed.

Do i need to re lock the bootloader first?

Discussion has resumes here:
http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-brick-t3243115
Thread closed.

Updater Bug: Unable to restart to recovery

Hello,
I wanted to install the newest nightly update. But when I tap "Install" it says "Unable to restart to recovery". Ive got a few questions here:
What causes this and why doesnt the errormessage explain itself?
Can I apply the update myself somehow (Where is it located and how can I apply it)?
Greetings,
Ravior

Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.

shivadow said:
Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.
Click to expand...
Click to collapse
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?

can you boot in Recovery via adb (adb reboot recovery)

Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something

RaviorMetal said:
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?
Click to expand...
Click to collapse
If had read anything to do with installing ANY rom it will have detailed instructions on how to install it, usually it will tell you how to get to recovery too. Even if it doesn't tell you how to get to recovery it is a google search away.
Spoon feeding is a no-no. You must try to solve issues yourself before asking and refer to the forum for "obtuse" issues.
As for the detailed output of why it failed, usually you get some sort of error code or phrase as to why. If not then you have to start looking into logcat. You will notice that it failed to boot to recovery so manually doing it will resolve that, then you just follow whatever guide you were using after that step..
I understand that things can get overwhelming when flashing devices but it is all part of the learning curve and knowing how to navigate your device is essential before even considering changing anything.
Further more, I didn't insult you. I didn't intend to. It was an honest opinion because if you don't do the basics you WILL "become a cropper", you'll probably brick your device.
Back to basics is my advice before you proceed to mess with ANY device.
bigjailerman said:
Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something
Click to expand...
Click to collapse
Yup, missing the cid is supercid. No longer valid. Cid and mid must match the firmware you're trying to install.
The bigger issue is not being able to get to recovery at all... Will it go to download mode?.
Obviously you've read flippy's thread and sneakyghosts thread?
Beamed in by telepathy.

Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw

bigjailerman said:
Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw
Click to expand...
Click to collapse
Yes there is, it's done via a command in fastboot but I can't remember if you can do it with just root or if you need s-off too..
Beamed in by telepathy.

So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Aint nobody got time fo dat!. It's confusing for idiots like me.. My attention span is... Oo ice cream!..
Beamed in by telepathy.

Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
No honestly, I re read everything and t is right there, no question and it is appreciated. I was just concentrating on how to get back to a version of TWRP. Finally I was able to do that and still unlocked, S Off and have a TWRP 2.7 but every time I try to go higher I get the cannot boot recovery in the red letters. My bottom line was to install a 7.1.x rom. That is what caused all my original issue, tried to update into 7.1.1 RR Rom and everything crashed. I used a RUU you have in that thread (THANK YOU) and was able to get out of bootloop on RR bootanimation. I am running on stock 5.x, rooted as well.
Is there anyway to still move forward? Do I need to change the CID to match the firmware I choose within the device choices?
Thanks for all your earlier posts and it has become invaluable and thanks for any advice going forward.: good:

TWRP versions above 3.x require your M9 to be at least using firmware 3.x. The same applies to android 6/7 based roms. Either restore the correct CID for your SKU, flash the latest available 3.x RUU for that SKU and then install all missing updates via the software update function of the stock rom or restore the correct CID and look for a full-wipe firmware pack in Sneakyghost's firmware thread (located in the development section). Be aware that his packs don't contain a rom but that shouldn't be a problem at all if you want to install RR, anyway.

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.