Develop Bugs

Need some help with my M8 after flashing ROM

SO, let me start off by mentioning that I am not a noob, but I JUST got this HTC M8 ( moved from M7 ) , I unlocked the bootloader and flashed a custom recovery and rooted it, but I am having a problem every time I flash a custom ROM.... Any time after installing a custom ROM , the boot time on the phone becomes RIDICULOUS, I mean 5-10 mins EVERY time, not just initial boot ... The phone sits at the " this builld is for developers only blah blah blah" warning with the HTC logo in the back for a solid 5 mins usually, then the screen will turn off, and when I turn it on, it will be fine, but while it's in that state ( "loading?" ) if I receive a text message, I will still get both haptic and audio feedback, any ideas? I was trying to flash ARHD!
FLASHING STOCK ROM GETS RID OF THIS! ( but I want a custom ROM )

What custom rom and did you update your firmware already ?

I had the same issue. It's the firmware mismatch. The ROM is built on a different firmware than the one you are currently on.
Most of the time flashing the correct firmware will require S-off... (Sunshine was the only one that worked for me)
I've never run into this before on other phones or ROMs so it was definitely a learning experience for me.

Mr Hofs said:
What custom rom and did you update your firmware already ?
Click to expand...
Click to collapse
ROM is Android Revolution HD and, no, I haven't updated my firmware yet. Is there a way to do it without S-OFF? Firewater doesn't work, and I realllllly can't afford to pay $25 for software to do it for me, after all , as a programmer, I know it's probably one line of code that changes it from firewater lol, in the end, they need to do the exact same thing, it's not like there's many different ways to achieve S-OFF, they all essentially follow the same process. Someone is just being greedy ( they probably designed SunShine for themselves, then thought " heyyyyyy profit", not cool in my books )
Liskrig said:
I had the same issue. It's the firmware mismatch. The ROM is built on a different firmware than the one you are currently on.
Most of the time flashing the correct firmware will require S-off... (Sunshine was the only one that worked for me)
I've never run into this before on other phones or ROMs so it was definitely a learning experience for me.
Click to expand...
Click to collapse
Know of anyway to do it without S-OFF? I can't afford $25 for a S-OFF atm... Especially to fix such a stupid little issue...... ughhh... I already wanna switch back to my M7 lol....

OR a way to achieve S-OFF without Firewater or SunShine

tutchthesky7 said:
OR a way to achieve S-OFF without Firewater or SunShine
Click to expand...
Click to collapse
No way to S-Off and fimware update without one of the two.

HTCNerdYoda said:
No way to S-Off and fimware update without one of the two.
Click to expand...
Click to collapse
Thanks for the help, managed to find a way around!
I didn't S-OFF yet, but I reverted to stock, and did the 4.4.3 OTA which bumped my FIrmware version past the ARHD 10.2 version, and now it works flawlessly!

Yeah, it's firmware, I also had this issue until i fixed it few days ago. I'm s-on (can't go s-off) and I've made it to upgrade my firmware to the newest one.
I just downgraded to 1.54.401.10 (or something similar) and then did official OTA. Now I don't have problems with signal, wifi or long boot times.
Sent from HTC One m8, or maybe not anymore

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.

HTC One M8s OTA not working

Hi,
I recently managed to root my HTC One M8s with TWRP recovery and everything works perfectly, except that I can't install the new OTA (1.16.401.1).
After searching I have flashed my recovery back to the stock for my version (which is 1.11.401.1) and tried applying the OTA again, but it still fails.
I downloaded the recovery from this website: ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/HTC%20Recovery/ (I can't post URLs yet).
Below is the error I receive when trying to update on stock recovery, TWRP recovery also gave the same error when I tried updating there.
(Code -1)
E:Find no match PARTITION: for package path @/cache/recover/block.map
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.105.019
Verifying current sytem...
Package expects build fingerprint of htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/531284.2:user/release-keys or htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/555949.10:user/release-keys;
This device has htc/m8qlul_htc_europe/htc_m8qlul:5.0.2/LRX22G/53128
E:Error in @/cache/recovery/block.map
(Status 7)
From what I can see my build fingerprint is incorrect, but I have no idea how to fix it...

Seems to me it's likely that you've altered some system files while rooted and the Ota doesn't like it.
Now, I don't own an M8s...i have an M8, but I'd say the easiest route would be to flash your stock ruu again. After that the OTA should work.
It's that or figure out what system changes have been made and correct it. Xposed can mess you up, Uninstalled system apps can stop the Ota... MODS that changed system files... Etc. The Ota us looking for a stock system, then it updates it.
Good luck!

Thanks for the answer, I will see if I can try this solution tomorrow. I just have 2 questions:
What does the RUU do exactly? Should I see it as a complete stock reset of my phone?
And can I simply flash it using fastboot or is there a special method for a RUU?
My previous phone had an automated root and I always updated with OTA afterwards so I never flashed before now.

Im on the same boat. Tried to sim unlock by rooting and playing with CID but didnt work, now ive a rooted m8s and no ota. Tried to ruu but kept getting an error something like not enough space although i had 10gb free, cleared cache rebooted. Cant even factory reset. If anyone know how to unroot it and bring it back to stock that would be fantastic. Kind of want to delete the "flag" too make it "LOCKED" and "OFFICIAL" incase for warranty. Any ideas?

You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?

voidzero said:
You guys have flashed 1.16 before, haven't you...?
See here: http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8s-to-stock-howto-t3190238
Err, oops, posted too soon. You said you have flashed to 1.11. What is the full filename of the RUU you flashed?
Click to expand...
Click to collapse
When I got my phone I updated with OTA to version 1.11, after that I flashed TWRP recovery and rooted my phone. Now that OTA 1.16 is out I tried to update but couldn't, so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
Manual OTA flash worked on my previous phone with root which was an ASUS Padfone Infinity A80 as ASUS would release them on their own website for you.
Apparently HTC does not do this, or I am not looking in the right place.
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash original recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.

Codyksp said:
(...) so I tried to flash back to stock recovery but it still wouldn't work because of the error above. Now it would seem that I am doing this the wrong way, and you cannot use OTA on a rooted/unlocked/custom recovery M8s.
(..)
I have never flashed a RUU before, and I don't know how to lock my bootloader again. From what I understand, every time there is a new OTA I will have to lock my bootloader, flash custom recovery, flash RUU and then update. That sounds like a lot of trouble every time a new OTA comes out.
(...)
Is there no way to manually flash the new OTA without losing root, custom recovery and locking the bootloader? Will I have to follow these steps every time? Also I use the built in back-up to Google as well as HTC back-up but I don't know if all my data is in those back-ups or if I will lose something.
Click to expand...
Click to collapse
If you restore a RUU, and afterwards don't flash your recovery and boot partitions, You will see "Software status: official" in fastboot.
Now here's the trick: if you just boot a custom recovery with "fastboot boot my_recovery.img" (TWRP for example) then it will boot TWRP, but you can make the modifications to your system partition without losing "Software status: official" in fastboot.
So: If you just boot your recovery with 'fastboot boot' and don't flash anything, you can make all the modifications you want and still be able to install OTAs later, I think. I've rooted my phone, even installed XPosed, done all kinds of funky things to it but Fastboot still shows me that I'm on official software.
How does that sound?

So since there is no decent guide at all about flashing RUU for a HTC One M8s (the s makes a difference!). I have assumed that I need to have the bootloader locked first, as I unlocked it. According to all the M8 guides I have to gain S-OFF before I can lock the bootloader again. So I followed a guide to wipe with TWRP and flash a ROM called InsertCoin so that I can S-OFF my phone.
Now after going through the ROM's setup my phone is stuck in a bootloop, constantly trying to boot up. There is NO way at all for me to get it to stop, it just keeps booting the entire time. Not a single combination of buttons is working. Good thing the battery is non removable. How am I supposed to fix this? I've tried every volume up/down/power combination possible. The phone just boots to the HTC - Power by Android screen, shuts off after about 5 seconds and then repeats the same thing over and over. I can't turn it off and I can't get to the bootloader either.
What I need is a guide that tells me all the steps required to get an HTC One M8s (NOT M8!) back to 100% stock. This means, stock ROM, stock recovery, locked bootloader and S-ON. I am getting extremely frustrated by the lack of information and the amount of redicilous things I need to do just so I can root my phone and have OTA as well.
All I want is root on my phone for 1 app that I use with my car radio and I want to be able to update to the newest OTA afterwards, is that really so much to ask?
I am fine with installing a custom ROM with root and easy updates too, as long as the damn phone will boot after installing it and it's actually made for the M8s.

Deleted......

Well I finally managed to get the damn thing to the bootloader, and I've used "fastboot oem lock" to relock my bootloader. It now shows ***Software status: Modified ***, *** RELOCKED *** and ***Security Warning ***.
I will now have to go to my parents where my laptop is to be able to copy the RUU to my SD card, from what I understand it has to be named 0PKVIMG.zip and then it should automatically install.

Now the phone says it can't find the image or the image is incorrect.... It searches for, 0PKVDIAG.zip, 0PKVDIAG.nbh, 0PKVIMG.zip or 0PKVIMG.img. and it seems to find 0PKVIMG.zip and loads it but it cannot find the .img file and does absolutely nothing. Am I supposed to have both?

So it turns out that the RUU zip from http://ruu.lalleman.net/HTC_M8S%28QL_UL%29/RUU/ is actually not correct and I had to use rom.zip which was inside the folder. The phone is now running the "update" as it calls it. Fingers crossed...

Yes, possible you need to use rom.zip inside the zip, depending on the version, but I think this applies to 1.16 which I advice against using for reasons previously specified.
---------- Post added at 07:47 PM ---------- Previous post was at 07:47 PM ----------
By the way, I did write an RUU restoration thread specifically for this subject. Did you not find it?

Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.

Codyksp said:
Apparently I also needed to use the rom.zip for the 1.11 version, in the meantime I have also updated with OTA to 1.16. Afterwards I also unlocked my bootloader, restored my settings and installed SuperSU by booting TWRP. Let's hope the next OTA still works...
I did read your thread but I got stuck at first on relocking the bootloader, as I couldn't find the exact instructions for a while. Afterwards I got stuck on flashing the RUU because I didn't know that I needed to use the rom.zip file to get it to work.
After all that I got quite frustrated and I just wished there was 1 thread with instructions for everything (unlocking, relocking, flashing, compatible ROMs, booting to keep OTA, etc.) which is why I was angry at the time and couldn't properly read everything or find solutions. In the end it all worked out so far though.
I would ask you to create a compilation thread though if you wanted to improve the available information. Either way, thanks for the information that you've already provided.
Click to expand...
Click to collapse
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.

Mr Hofs said:
The next ota won't work because you rooted it. Root changes binaries which lead to a fail on ota.
You need a non rooted (read : never rooted before) stock rom.
Click to expand...
Click to collapse
So in that case I just unroot it before updating then?

Codyksp said:
So in that case I just unroot it before updating then?
Click to expand...
Click to collapse
Read my post again...... "a never rooted rom" so that means you need a stock rom before its ever been rooted. NOT an unrooted one because it leaves traces which will cause the ota to fail !
People should learn to create a nandroid backup before flashing ANY mods/superuser.zip/roms etc......etc

Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
I would say that M8 roms wouldn't be compatible, and could even mess up your device badly. Sorry!

Codyksp said:
Well developers shouldn't make this such a hassle... My previous phone was an ASUS Padfone Infinity (A80) and it didn't receive any OTAs after being rooted but ASUS simple lets you download the firmware updates on their website and then you can manually update it without any problems. If HTC provides a bootloader unlock, why can't they allow OTA or at least provide manual firmware updates?
I wouldn't mind using a custom ROM either but I have no idea which ROMs work for the HTC One M8s. Would any M8 ROM be compatible? The phones aren't identical, the "s" is there for a reason...
Click to expand...
Click to collapse
Your point of view is a bit off if you ask me. Developers (in this case HTC) do not have to support custom modding of your phone. They support the device in the state you buy it !
If you want to mod it that's YOUR call not theirs. Do some homework before modding it. Getting a phone back to stock for future updates is relatively easy but many people don't read first how to as they think it's not important.
HTC has no obligation at all towards you regarding custom software !
And indeed M8 roms do NOT work on your M8s !

M8 Update gone wrong...!

It been a long time.. Well maybe 3years since i been on xda. I still remember how to root and flash this n that n etc... But yesterday i wanted to get started on flashing my verizon m8 onto a rom. Yeah little complicated. I tried everything to unlock my bootloader i keep getting the 172 error. Still considered S-on, So i just left that alone and tried to go #oldschool. I tried to update using htc sync manager. But I had to leave and go to the store. Left this on the computer to finish updating. came back 20-30mins later its on a black htc screen with the green line across. So i thought it was just finished But my computer had been frozed for 10mins. (ive checked the time) but Now it gotten bricked. i can only boot into hboot... Fastboot... And ruu.. But not recovery... I Already downloaded the rom, and the latest twrp recovery on my pc. But im still s-on.. I really don't got time to start from scratch and just factory reset this.. And im no longer worried about my data and shxt because i know im eventually going to losed them anyway. So right now its on fastboot. My win7 detects it in fastboot usb. So where do i go from here? Anybody? No worries though :fingers-crossed: :angel:

You can't unlock the bootloader on the VZN version by HTCDev.com, you need to s-off by sunshine, then use sunshine to unlock the bootloader.
Unfortunately, sunshine requires a working OS. So first you'll need to RUU back to working stock. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
After that, you will need to root (think kingroot is the mot common method) then you can load the sunshine app ($25 license) to s-off and unlock the bootloader: http://theroot.ninja/
Once the bootloader is unlocked, you can load custom recovery TWRP and flash a custom ROM.
But keep in mind, there are kernel differences between the VZN version and most other M8 versions. Meaning, you will need to either flash a ROM that explicitly states it supports the VZN M8; or you can flash other ROMs, but you will need the proper kernel.
You'll want to read up in the Verizon M8 forum section, as this version has some peculiarities, as I've mentioned: http://forum.xda-developers.com/verizon-htc-one-m8

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.