Develop Bugs

[Q] HTC One m8 unrooting

hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance

hassaan08 said:
hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance
Click to expand...
Click to collapse
Click this link. It will tell you how to convert your phone to GPE.

xunholyx said:
Click this link. It will tell you how to convert your phone to GPE.
Click to expand...
Click to collapse
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....

hassaan08 said:
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....
Click to expand...
Click to collapse
Okay. The instructions are in the link. Where are you getting stuck?

Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?

EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
yes i do.. i tried a few things but got stuck in between cos i dont know this stuff in depth..
I tried to unroot by downloading the stock firmware for my phone..
the method i was following was to match my cid number etc which i got through getvar with the firmwares on xda.. that bit i did well but the method i was following said that now i had to copy and paste this firmware in my phone in the backups folder of clockwordmod.. now i couldnt find that folder.. even though the backup i made is occupying space on my phone but i cannot locate it when i try to copy paste the downloaded firmware..
can you tell me where i can find that or tell an alternate way to do this thing?

OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)

EddyOS said:
OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA13G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__002
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
is this what you were asking for?

Indeed! OK, if you want go back to 100% stock, running on Sense as if you just got it out the box you can do the following:
First, download these files to the same location as fastboot:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249 (doesn't need renaming)
1. Relock your bootloader - fastboot oem lock
2. Once done, reboot the bootloader to confirm it says 'RELOCKED' - fastboot reboot-bootloader
3. Once relocked, reboot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the RUU ZIP using the HTC fastboot app - htc_fastboot flash zip ruu.zip
5. It will go through a few passes but once complete reboot the phone to the bootloader - fastboot reboot-bootloader
6. Once back at the bootloader, go into recovery and you should get the stock recovery not CWM. Hold volume up and press power to get the recovery menu and do a factory reset
7. Once the reset has finished, reboot the phone
You should now be working again on 100% stock Lollipop

help needed, new to rooting stuff
Hi forum members. This is my first post and and i am an infant in unlocking and rooting stuff. The reason I am researching these things is because of my HTC one m8. I got this phone used from a seller 6 months ago. I was expecting OTA updates but did not receive any till date. I am still running on 4.4.2 . So, after a bit of searching on forums, I learned about a thing called boot loader. And checked mine. To my surprise it was TAMPERED , UNLOCKED AND S-ON. Now I really don't know what that means. Some suggested to check if it's rooted, installed root checker and it said "device is not rooted" .
Can anyone pLease help me And explain me what all this means as it will be greatly appreciated.I only want to have OTA updates And need stock android. Thanks in advance

Best to start your own thread, and post up the same details as the OP in post #8, rather than confusing things in someone else's thread

EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.

xunholyx said:
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.
Click to expand...
Click to collapse
That was the second request, the first being to get it back to stock. I was just saying that if they're not familiar with rooting HTC devices then converting to GPe could potentially brick the device

It worked... thank you so much..
i hope liverpool get into the top 4 this season

hassaan08 said:
It worked... thank you so much..
i hope liverpool get into the top 4 this season
Click to expand...
Click to collapse
I'm an Arsenal fan but thank you anyway!

hey again
i unrooted my device and it seemed fine then but since day one the device is highly unstable.. I did the hard reset several times but have not been able to fix the problem.. suddenly all the data vanishes from the device and some features get locked ( brightness, power saver and others too). Please suggest what i should do?

Is there a way I can re-flash the stock lollipop with a different RUU file?

Nope, if you still have issues when stock you have a faulty phone

these are definitely sofware issues.. for example one in ten times when i format my device it starts working totally fine... but after a few days the same problem re-appears... the problem is that htc zoe add keeps popping up again and again.. and when it starts i cant adjust the brightness or the power saver options.. the rest of the phone works fine....
can you please suggest if i should convert my phone to GPE? or will it be too difficult a process for a rookie like me?

Sounds like a faulty phone, get it replaced

Android won't start and need help flashing

Hi,
I have bought a used HTC M9 on Kijiji (I'm in Québec, Canada)
It must be faulty because it kept randomly restarting (sometimes once, sometimes for periods of 20 minutes, which made it hardly usable)
After clearing the cache partition and factory resetting it a couple times, I decided to flash it.
What I did:
- enabled the developer mode and USB debugging
- unlocked the bootloader
- flashed TWRP
- flashed SuperSU v2.74-2
Now, Android won't boot. When I start the phone, I see the green HTC logo on a white background with a red text saying it's a development build, then after about 10 seconds it restarts to the same screen. Over and over again.
In download mode, I am able to see the device with fastboot, but adb does not show anything.
In recovery mode, it's the opposite.
The phone is still S-ON so I have tried S-OFF methods (moonshine and firewater), but the fact of not having fastboot AND adb working at the same time made them fail.
Here's my phone info:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.38.666.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
Any help would be greatly appreciated...
Thanks in advance!

youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine

Roobwz said:
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Click to expand...
Click to collapse
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?

zzzer51 said:
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
Click to expand...
Click to collapse
You shouldnt use toolkits imo, no offence squabbi. You should just download the 2.64 file from chainfires thread and flash it in twrp. It isnt harder than that. Btw 2.64 was the only superSu that worked for me

Ok, I have been able to find a zip for 2.64 and will install it with TWRP when my phone's battery is drained out (it tried to boot on the OS and is currently stuck on the HTC logo...)
I have also tried installing files directly from the microSD
downloaded from:
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://androidruu.com/index.php?developer=M9
using fastboot flash zip zipfile.zip
but I get errors like
9 RU_SECURITY_FAIL
android-version information is missing
I'm not sure I'm trying to flash the right file anymore...
EDIT:
I have tried to flash both 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.30 and 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6 files by going to TWRP -> Install but I get the error message 'zip file is corrupt!' every time...
And when I try to flash with fastboot, I get "Invalid sparse file format at header magi"
EDIT2:
Ok, I have made some progress!
What I did:
1/ Downloaded the image from this page http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
2/ Formated my 8GB microSD card to exFAT (because the system image file is over 4GB)
3/ Extracted the system.emmc.win and boot.emmc.win files to the microSD card in path: E:\TWRP\BACKUPS\<myPhoneIDThatFastbootCanGiveYouIfYouTypeFastbootDevices>\Stock Bell
4/ Started the phone in recovery mode (TWRP)
5/ Tapped on Restore
6/ Selected the two files and hit Restore
7/ Performed a Factory reset (through TWRP, by tapping Wipe)
8/ Rebooted the phone in System mode
And Android started!
I'm not 100% sure it fully works as I haven't been able to finish the configuration yet (I don't have access to a wifi network where I am) so I will do that when I get home tonight.
But it looks a lot better than these past few days.
In the meantime, a quick question:
My bootloader is still unlocked. Can I leave it like that or should I re-lock it?
Thanks

No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.

shivadow said:
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
Click to expand...
Click to collapse
You can OTA with an unlocked bootloader but you need to be 100 % stock. It's always best to not relock bootloaders as if you get into problems, you'll not be able to flash stuff. The only time a locked bootloader is needed is when running RUU.exe while S-On. The SD card method works with an unlocked bootloader. I'd recommend to leave it unlocked

Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time

zzzer51 said:
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
Click to expand...
Click to collapse
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.

Roobwz said:
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Click to expand...
Click to collapse
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?

zzzer51 said:
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
Click to expand...
Click to collapse
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Skickat från min HTC One M9 via Tapatalk

Roobwz said:
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Click to expand...
Click to collapse
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?

zzzer51 said:
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
Click to expand...
Click to collapse
The service is remotely done over the computer, so you'll see everything that happens.
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free. Either that or s off (25$ as well), and you'll be able to convert your phone into a world wide edition model or dev edition. S off opens up a whole new world for you. Ex - you can flash exactly what you want (no need for Canadian firmware) and you're able to downgrade etc. The rest is up to you.

Roobwz said:
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free.
Click to expand...
Click to collapse
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code

zzzer51 said:
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
Click to expand...
Click to collapse
That's kernel source I believe. Your only luck would be flippys thread in the general section
Skickat från min HTC One M9 via Tapatalk

The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!

zzzer51 said:
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
Click to expand...
Click to collapse
I would recommend upgrading to 3.xx for several reasons like doze, custom ROMs that are up to date etc. If you did the OTA from 1.x to 2.x, you shouldn't have any problems with the OTA to 3.x. in the worst case, just re flash the RUU or just convert the device to an European version.

Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks

zzzer51 said:
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
Click to expand...
Click to collapse
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.

Roobwz said:
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Click to expand...
Click to collapse
A looooot of stuff!
But even after flashing the original HTC recovery again, I get the same message.
And I can't access the recovery menu either.
Thanks

[SOLVED] Bricked device, please help! (HTC ONE M9 himauhl)

Hello,
As mentioned in the title, I have a HTC one m9 which I have somehow bricked by attempting to install supersu. I flashed a rom that was horribly slow, so I wanted to flash my stock rom after I have flashed the other rom. It was a RUU so I relocked my bootloader, but the update failed because I am S-ON. Whenever I try to unlock my bootloader again it asks me if I want to unlock and that would void my warranty everything as normal but would then restart and still be relocked. Also, whenever I try to boot normally it takes me to bootloader. Any help would be appreciated! (No SD card I have.)
fastboot getvar all:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__J15
Thank you!

MikeTheGamer said:
Hello,
As mentioned in the title, I have a HTC one m9 which I have somehow bricked by attempting to install supersu. I flashed a rom that was horribly slow, so I wanted to flash my stock rom after I have flashed the other rom. It was a RUU so I relocked my bootloader, but the update failed because I am S-ON. Whenever I try to unlock my bootloader again it asks me if I want to unlock and that would void my warranty everything as normal but would then restart and still be relocked. Also, whenever I try to boot normally it takes me to bootloader. Any help would be appreciated! (No SD card I have.)
fastboot getvar all:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__J15
Thank you!
Click to expand...
Click to collapse
Have you tried to download from
http://www.htc.com/us/support/rom-downloads.html
And reinstall the stock 6.01 using download mode through your bootloader?

mcarden2006 said:
Have you tried to download from
And reinstall the stock 6.01 using download mode through your bootloader?
Click to expand...
Click to collapse
I have, but will try redownloading and attempting again. Got the unknown error I think it was code 105
I'm trying to get this: http:././dl3.htcdotcomslashapplication/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe?_ga=1.172299883.913399690.1483411382
also I noticed this is hima UL not UHL, will it still work?

MikeTheGamer said:
I have, but will try redownloading and attempting again. Got the unknown error I think it was code 105
I'm trying to get this: http:././dl3.htcdotcomslashapplication/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe?_ga=1.172299883.913399690.1483411382
also I noticed this is hima UL not UHL, will it still work?
Click to expand...
Click to collapse
Do you have s-off? I had the same error code when I tried to install the wrong one. I have an at&t HTC so I downloaded from the top. You have to make sure oem unlock and debug mode are check on the developer option from your phone. Reboot into download mode and should work like a charm. When I installed supersu I had to go back to 2.65 version or use magisk root.

mcarden2006 said:
Do you have s-off? I had the same error code when I tried to install the wrong one. I have an at&t HTC so I downloaded from the top. You have to make sure oem unlock and debug mode are check on the developer option from your phone. Reboot into download mode and should work like a charm. When I installed supersu I had to go back to 2.65 version or use magisk root.
Click to expand...
Click to collapse
As I mentioned I have S-ON. If there's any way I can make it S-OFF with fastboot or something I'd be glad to, and bootloader is stuck at relocked.

MikeTheGamer said:
As I mentioned I have S-ON. If there's any way I can make it S-OFF with fastboot or something I'd be glad to, and bootloader is stuck at relocked.
Click to expand...
Click to collapse
I know a lot of people complain but I paid 25$ and used sunshine. It worked like a charm and I have s-off. Now I'm finally free ?

mcarden2006 said:
I know a lot of people complain but I paid 25$ and used sunshine. It worked like a charm and I have s-off. Now I'm finally free
Click to expand...
Click to collapse
I would have tried, but I have no access to android. Please read the whole thread

MikeTheGamer said:
I would have tried, but I have no access to android. Please read the whole thread
Click to expand...
Click to collapse
What I was saying is after you get your phone up and running you can do it.

mcarden2006 said:
What I was saying is after you get your phone up and running you can do it.
Click to expand...
Click to collapse
Oh, yeah, no problem Until then though, I have S-ON and at 52% of the RUU download. Will right back soon!

MikeTheGamer said:
Oh, yeah, no problem Until then though, I have S-ON and at 52% of the RUU download. Will right back soon!
Click to expand...
Click to collapse
Just remember magisk root is really easy but supersu install the 2.65 and not the 2.78 or 2.79. They will just keep bootlooping the phone.

mcarden2006 said:
Just remember magisk root is really easy but supersu install the 2.65 and not the 2.78 or 2.79. They will just keep bootlooping the phone.
Click to expand...
Click to collapse
Thank you! Guess I should have looked better before flashing supersu...
Anyway, do you have any other solutions if this doesn't work? I'm really paranoid and afraid that I cannot fix my phone this time. I usually go through this stuff a lot but I usually fix it easily too, but this time it's been a few days and I'm really frustrated.

MikeTheGamer said:
Thank you! Guess I should have looked better before flashing supersu...
Anyway, do you have any other solutions if this doesn't work? I'm really paranoid and afraid that I cannot fix my phone this time. I usually go through this stuff a lot but I usually fix it easily too, but this time it's been a few days and I'm really frustrated.
Click to expand...
Click to collapse
Well, It failed. Error code 155 UNKNOWN. I believe the reason is S-ON and probably locked bootloader. Any help please?

MikeTheGamer said:
Thank you! Guess I should have looked better before flashing supersu...
Anyway, do you have any other solutions if this doesn't work? I'm really paranoid and afraid that I cannot fix my phone this time. I usually go through this stuff a lot but I usually fix it easily too, but this time it's been a few days and I'm really frustrated.
Click to expand...
Click to collapse
Do you have twrp installed? One time I formatted everything by accident including the boot loader. It took me awhile to fix everything but I did. One time I had to install a custom rom and then I was able to go to stock. Its usually just trial and error. That's what I love android so much because of the freedom.
---------- Post added at 06:29 PM ---------- Previous post was at 06:29 PM ----------
mcarden2006 said:
Do you have twrp installed? One time I formatted everything by accident including the boot loader. It took me awhile to fix everything but I did. One time I had to install a custom rom and then I was able to go to stock. Its usually just trial and error. That's what I love android so much because of the freedom.
Click to expand...
Click to collapse
Sorry it took me awhile but I had to walk the dog.

mcarden2006 said:
Do you have twrp installed? One time I formatted everything by accident including the boot loader. It took me awhile to fix everything but I did. One time I had to install a custom rom and then I was able to go to stock. Its usually just trial and error. That's what I love android so much because of the freedom.
---------- Post added at 06:29 PM ---------- Previous post was at 06:29 PM ----------
Sorry it took me awhile but I had to walk the dog.
Click to expand...
Click to collapse
My bootloader is relocked, and won't unlock again. As I said before, goes through all the normal stuff and then reboots to bootloader and stays relocked. Therefore, I cannot access recovery.

You haven't unlocked the bootloader yet? Its free and helps you step by step using this site.
http://www.htcdev.com/bootloader/
That's usually the first thing I do. The key it provides you in the terminal is very picky so make sure there are no spaces.

mcarden2006 said:
You haven't unlocked the bootloader yet? Its free and helps you step by step using this site.
http://www.htcdev.com/bootloader/
That's usually the first thing I do. They key it provides you in the terminal is very picky so make sure there are no spaces.
Click to expand...
Click to collapse
I have unlocked it before, I said it's "relocked" I have the unlock bin, but it's just stuck there.

MikeTheGamer said:
I have unlocked it before, I said it's "relocked" I have the unlock bin, but it's just stuck there.
Click to expand...
Click to collapse
Do you have the drivers installed and using the terminal under administrator mode? I installed mine using 15 second adb fastboot installer.

I'll try reinstalling adb, and I have HTC sync manager, so I'm sure I have the right HTC drivers. one second.

MikeTheGamer said:
I'll try reinstalling adb, and I have HTC sync manager, so I'm sure I have the right HTC drivers. one second.
Click to expand...
Click to collapse
Usually I use the power shell terminal when you press shift and right click on the folder. It never failed me that way.

mcarden2006 said:
Do you have the drivers installed and using the terminal under administrator mode? I installed mine using 15 second adb fastboot installer.
Click to expand...
Click to collapse
The problem he is likely to run into is that the HTC fast boot checks the os to see if unlocking is allowed. I made the same mistake myself trying to get back to stock to install nougat. I have hima_ul w s-on and the uhl version didn't take on my phone. I imagine Mike will need the uhl version ruu. Put the phone in fastboot, then run the ruu. Make sure that you have a .doc viewer installed (open office will suffice). I found the ruu will bomb out silently it you don't. It's some error thrown by the ARWizard contained in the ruu.
You can also teach out to HTC support. They can reset the device for you.

My htc 10 is dead ?

Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!

ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.

yldlj said:
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15

ubadafatta said:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
Click to expand...
Click to collapse
Since there Is no RUU and you re locked your Bootloader there's not much I can help you with sorry.

ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).

Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on

Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.011s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.080s]
finished. total time: 1.094s
this what i get when i try to flash unlocktoken or oem unlock bootloader or even when i try get_token_identifier

You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
ubadafatta said:
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Click to expand...
Click to collapse

Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.

Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The threory of the OTA is fine but not in this case.
Cheers.
Click to expand...
Click to collapse
Yeah thanks. I deleted all my post because there's no point in arguing. Your correct I totally forgot what the OP problem was after all this. Thanks for the clarification.

Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Click to expand...
Click to collapse

It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
ayyu3m said:
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Click to expand...
Click to collapse

Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Mr Hofs said:
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
Click to expand...
Click to collapse

ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I will have a look at it when i have more time, and let's not bash but learn ?
:highfive:
Cheers guys.

ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:

Yeah i got your PM. Thanks for that. After reading your PM i also knew how stupid i was being. And when i came to delete the post, they were already deleted by the thread administrators.
Sorry once more man. Wont happen again
yldlj said:
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Click to expand...
Click to collapse

ayyu3m said:
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
Click to expand...
Click to collapse
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on

[email protected] said:
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
Click to expand...
Click to collapse
Flash ruu
https://androidfilehost.com/?fid=673956719939830809

yldlj said:
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
Click to expand...
Click to collapse
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%

[email protected] said:
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
Click to expand...
Click to collapse
Yeah everyone I flash RUU it does bypass some things. Relocking bootloader usually causes problems and I don't know people still keep doing it. I would say flash twrp followed by leedroid but pretty sure you need an unlocked bootloader to flash twrp. Sorry but I'm out of ideas.

Htc bootloader issue

So, okay, I'd like to start off by saying I messed up. I couldn't read what the thing said, so I clicked the wrong thing, and I'm pretty sure I somehow bricked my htc m8.
So, I was using Hasoon2000's Htc one all in one tool kit, and I was trying to root an m8 I just got. I wnt through all the steps to unlock the bootloader and whatnot, and everything somewhat worked, I couldn't flash TWRP on the phone for whatever reason. So, I put it on an sd card, and was gonna flash it myself. I clicked on "Relock bootloader" Meaning to click on "Boot into Bootloader"(Bad eyesight), and now I have no clue what the hell is going on with the phone.
I restarted the phone, and when it loaded into the os, I couldn't access settings, I couldn't uninstall apps(App not installed even though it was), so, I tried to install the factory os via the all in one tool kit, but now all my phone says is
*** Software status: Modified ***
*** RELOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.25.21331147a1.06g
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-
eMMC-boot 2048MB
Jan 12 2015,21:43:09.9093
RUU
And thats it... I have no clue what the hell even happened, and whats going on.
Edit:
I was able to restart the phone and get into some more of the back end stuff, but not much...
It now has
Fastboot, recovery,factory reset,simlock,check smartsd,image crc,show barcode, however, clicking the first 3 takes me to ther fastboot menu(or fastboot usb with it plugged into my win pc), and if I try and factory reset it, it says *** Security Warning ***
Sigh... No clue how to fix it

The good news, is that your can't really brick this device while s-on (which it is), especially with the stuff you've done. It's simply stuck in a state that is not usable to you, that is very likely recoverable.
First off, I highly recommend you ditch the toolkit. This is for a couple reasons: one reason being, the toolkit only acts as a middle man for something you can (and should) know how to do yourself: simple one-line fastboot commands. And as you've seen, the toolkit makes it a little too easy to do something on accident, such as lock the bootloader. Which not only will typically render the phone unable to boot to OS (I'm surprised yours still did at first) as well as wipes all personal data on the phone. This would never happen, if you were doing the fastboot commands by yourself.
Another big reason to avoid the toolkit, it stopped being supported a long time ago, in 2014. Well before HTC stopped supporting this device (2016?). Since the toolkit is so old, it contains outdated versions of TWRP and SuperSU, which will cause a lot of problems for most folks. This includes you, and most likely the reason TWRP (outdated version) did no work for you.
My recommendation:
1) Your firmware is outdated (Lollipop). Since the bootloader is presently locked (relocked, basically the same thing) it is a good time to flash official firmware/RUU and bring your firmware up to Marshmallow. In order to figure out what firmware or RUU is right for your M8 version, we need more info. Do fastboot getvar all, and post the results (delete IMEI and serial number). If you don't know how to use fastboot, it's time to learn. Use xda seach function, and/or Google (although being a bit careful when following random websites outside xda) and learn the basics of fastboot. If you have specific questions, come back and ask. I'll be happy to help with those. But don't intend to give you a step-by-step instructions, for info that is posted in countless places already.
2) Once firmware is updated, unlock the bootloader again. You should be able to use the same unlock bin code as you originally did, to unlock the bootloader. Otherwise, just go through the process at HTCDev.com and get another unlock bin code. Flash the code with fastboot.
3) Once the bootloader is unlocked, flash latest TWRP 3.2.3-1 using fastboot. You can get TWRP from here: https://dl.twrp.me/m8/
4) Make a backup in TWRP of your stock ROM. This way, if you run into any problems rooting (or otherwise, want to reverse the process), you can still revert to stock. To backup the stock ROM, select BACKUP in TWRP, and select system and boot.img to backup. This is a very important step, that many folks (and guides) skip. But to me, it is not only best practice, but just common sense to make a backup and give yourself an "escape plan". I simply never root or make other mods to these devices, without having a backup of the stock ROM.
5) In TWRP, flash current version SuperSU 2.82 from here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
But to be honest, I would suggest Magisk at this point. It is a newer root method than SuperSU. And SuperSU appears to be dead, anyways. Not only is Magisk still being updated and supported, but it seems to work a little more reliably. Plus, Magisk has a ton of cool and useful features, that SuperSU does not. Suggested Magisk version is 18.0: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6) After flashing your root file of choice (SuperSU vs. Magisk), reboot and you should have a usable (and rooted) operating sy system.

redpoint73 said:
The good news, is that your can't really brick this device while s-on (which it is), especially with the stuff you've done. It's simply stuck in a state that is not usable to you, that is very likely recoverable.
First off, I highly recommend you ditch the toolkit. This is for a couple reasons: one reason being, the toolkit only acts as a middle man for something you can (and should) know how to do yourself: simple one-line fastboot commands. And as you've seen, the toolkit makes it a little too easy to do something on accident, such as lock the bootloader. Which not only will typically render the phone unable to boot to OS (I'm surprised yours still did at first) as well as wipes all personal data on the phone. This would never happen, if you were doing the fastboot commands by yourself.
Another big reason to avoid the toolkit, it stopped being supported a long time ago, in 2014. Well before HTC stopped supporting this device (2016?). Since the toolkit is so old, it contains outdated versions of TWRP and SuperSU, which will cause a lot of problems for most folks. This includes you, and most likely the reason TWRP (outdated version) did no work for you.
My recommendation:
1) Your firmware is outdated (Lollipop). Since the bootloader is presently locked (relocked, basically the same thing) it is a good time to flash official firmware/RUU and bring your firmware up to Marshmallow. In order to figure out what firmware or RUU is right for your M8 version, we need more info. Do fastboot getvar all, and post the results (delete IMEI and serial number). If you don't know how to use fastboot, it's time to learn. Use xda seach function, and/or Google (although being a bit careful when following random websites outside xda) and learn the basics of fastboot. If you have specific questions, come back and ask. I'll be happy to help with those. But don't intend to give you a step-by-step instructions, for info that is posted in countless places already.
2) Once firmware is updated, unlock the bootloader again. You should be able to use the same unlock bin code as you originally did, to unlock the bootloader. Otherwise, just go through the process at HTCDev.com and get another unlock bin code. Flash the code with fastboot.
3) Once the bootloader is unlocked, flash latest TWRP 3.2.3-1 using fastboot. You can get TWRP from here: https://dl.twrp.me/m8/
4) Make a backup in TWRP of your stock ROM. This way, if you run into any problems rooting (or otherwise, want to reverse the process), you can still revert to stock. To backup the stock ROM, select BACKUP in TWRP, and select system and boot.img to backup. This is a very important step, that many folks (and guides) skip. But to me, it is not only best practice, but just common sense to make a backup and give yourself an "escape plan". I simply never root or make other mods to these devices, without having a backup of the stock ROM.
5) In TWRP, flash current version SuperSU 2.82 from here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
But to be honest, I would suggest Magisk at this point. It is a newer root method than SuperSU. And SuperSU appears to be dead, anyways. Not only is Magisk still being updated and supported, but it seems to work a little more reliably. Plus, Magisk has a ton of cool and useful features, that SuperSU does not. Suggested Magisk version is 18.0: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6) After flashing your root file of choice (SuperSU vs. Magisk), reboot and you should have a usable (and rooted) operating sy system.
Click to expand...
Click to collapse
First of all, I'd love to just say thanks for not calling me an idiot or anything, and taking the time to do this! I've rooted htcs before, but nothing this complex. This community seems to be better than most others, and less toxic, or so it seems.
Anyways:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.21331147A1.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B16000
cidnum: SASKT001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dcdaa6e0
hbootpreupdate: 11
gencheckpt: 0
Still working on flashing a rom, I have no clue where to find them, or what a secure, proper download of one looks like, however, I did find one on the forums from here:
https://forum.xda-developers.com/showthread.php?t=2696282
I also got this in cmd as I tried to flash
target reported max download size of 1826418688 bytes
sending 'zip' (1559644 KB)...
OKAY [ 51.325s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)

Neku DHack said:
Still working on flashing a rom, I have no clue where to find them, or what a secure, proper download of one looks like
Click to expand...
Click to collapse
Yeah, my intent was to get the fastboot getvar info about your device version (which you have now given), so we can further direct you from there. Figuring it out yourself is not that easy, for a number of reasons. You probably got signature verify fail, since the firmware must be the specific to your device version's CID (carrier ID) or else it will fail by design.
My suggestion would be:
a) Flash firmware fw_6.13.666.7 from here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Using instruction near the bottom of the post.
b) Restore stock TWRP backup (stock ROM) from here: https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Using the instruction in Post #1 of that same thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to Steps 1-9 of that guide (and skip step 3 of that guide).
c) Then you can do steps 4-6 of what I posted in my earlier reply above: https://forum.xda-developers.com/showpost.php?p=78750946&postcount=2
Keep in mind that the TWRP backup (stock ROM) in step "b" above, is not the same as the "firmware" in step "a" above. The firmware in this case, is not a full ROM, but a small file which contains radio, hboot, and some other small partitions, needed to make the ROM work, but does not contain the ROM itself. This is a little confusing I know, but moral of the story, is that you should update both the firmware and the ROM to get the phone working again, than backup and root.
---------- Post added at 09:57 AM ---------- Previous post was at 09:47 AM ----------
Neku DHack said:
First of all, I'd love to just say thanks for not calling me an idiot or anything,
This community seems to be better than most others, and less toxic, or so it seems.
Click to expand...
Click to collapse
Yeah, name calling and belittling folks is not my style. And also against xda's rules of conduct. There are a lot of toxic forums on the internet, and I agree xda is a cut above that; at least most of the time.
We all had to start somewhere with this stuff. And for a device this old, there is a lot of outdated and contradictory info out there. The only reason I understand all this the way I do, is that I've been here on the M8 forum section, since practically the start. And I've learned a lot from other folks in the community; and have benefitted from great resources like ckpv5's thread I linked above.

redpoint73 said:
Yeah, my intent was to get the fastboot getvar info about your device version (which you have now given), so we can further direct you from there. Figuring it out yourself is not that easy, for a number of reasons. You probably got signature verify fail, since the firmware must be the specific to your device version's CID (carrier ID) or else it will fail by design.
My suggestion would be:
a) Flash firmware fw_6.13.666.7 from here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Using instruction near the bottom of the post.
b) Restore stock TWRP backup (stock ROM) from here: https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Using the instruction in Post #1 of that same thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to Steps 1-9 of that guide (and skip step 3 of that guide).
c) Then you can do steps 4-6 of what I posted in my earlier reply above: https://forum.xda-developers.com/showpost.php?p=78750946&postcount=2
Keep in mind that the TWRP backup (stock ROM) in step "b" above, is not the same as the "firmware" in step "a" above. The firmware in this case, is not a full ROM, but a small file which contains radio, hboot, and some other small partitions, needed to make the ROM work, but does not contain the ROM itself. This is a little confusing I know, but moral of the story, is that you should update both the firmware and the ROM to get the phone working again, than backup and root.
---------- Post added at 09:57 AM ---------- Previous post was at 09:47 AM ----------
Yeah, name calling and belittling folks is not my style. And also against xda's rules of conduct. There are a lot of toxic forums on the internet, and I agree xda is a cut above that; at least most of the time.
We all had to start somewhere with this stuff. And for a device this old, there is a lot of outdated and contradictory info out there. The only reason I understand all this the way I do, is that I've been here on the M8 forum section, since practically the start. And I've learned a lot from other folks in the community; and have benefitted from great resources like ckpv5's thread I linked above.
Click to expand...
Click to collapse
So, I did the first step, and flashed the OS twice because it gave me an error, now its stuck on the white boot screen with the htc o1ne logo in the middle, and its been like that for hours now. gonna wait for the battery to die, and see what happends. Can't hold the power to shut it down.
Edit:So, It died, and now it won't charge, and red/orange light at the top is blinking... the battery logo pops up and says its charging, but it isnt.
Edit 2:Fixed the charging issue

Neku DHack said:
So, I did the first step, and flashed the OS twice because it gave me an error, now its stuck on the white boot screen with the htc o1ne logo in the middle, and its been like that for hours now. gonna wait for the battery to die, and see what happends. Can't hold the power to shut it down.
Edit:So, It died, and now it won't charge, and red/orange light at the top is blinking... the battery logo pops up and says its charging, but it isnt.
Edit 2:Fixed the charging issue
Click to expand...
Click to collapse
Power + vol up will force a reboot, in cases where holding power alone doesn't do it. Or you possibly didn't hold power long enough. In some "stuck" situations, you may have to hold the button(s) for about a minute, before it reboots.
The button combos are hardwired into the device, so they will always work unless the phone is truly bricked.
Also, flashing the firmware twice is normal, as is the error message. So you did the right thing in flashing it again.

redpoint73 said:
Power + vol up will force a reboot, in cases where holding power alone doesn't do it. Or you possibly didn't hold power long enough. In some "stuck" situations, you may have to hold the button(s) for about a minute, before it reboots.
The button combos are hardwired into the device, so they will always work unless the phone is truly bricked.
Also, flashing the firmware twice is normal, as is the error message. So you did the right thing in flashing it again.
Click to expand...
Click to collapse
So, after leaving it for a few days, and trying to reboot it, it got stuck in the boot screen again, so I did the power+vol up, and now its black screened and wont charge... Is it bricked?
Edit:Not bricked, if I hold down every button it flashes the htc boot screen, then it goes to black again

Neku DHack said:
So, after leaving it for a few days, and trying to reboot it, it got stuck in the boot screen again, so I did the power+vol up, and now its black screened and wont charge... Is it bricked?
Edit:Not bricked, if I hold down every button it flashes the htc boot screen, then it goes to black again
Click to expand...
Click to collapse
Try power+vol down.
The phone isn't bricked. I already said, you can't brick this phone doing what you did (trying to flash recovery, root file). Those partitions are separate from the bootloader, which is also protected by s-on (you couldn't overwrite it, even if you wanted to).The fact that the HTC logo screen comes on, also means bootloader is still working properly (no bootloader = dead screen) and that you just need to execute the proper button combo to get to the bootloader screen. As long as bootloader works, the phone is recoverable.
Also, have you been charging the device? Since you let the battery die, you should charge it fully again (overnight on wall charger, not connected to PC).

redpoint73 said:
Try power+vol down.
The phone isn't bricked. I already said, you can't brick this phone doing what you did (trying to flash recovery, root file). Those partitions are separate from the bootloader, which is also protected by s-on (you couldn't overwrite it, even if you wanted to).The fact that the HTC logo screen comes on, also means bootloader is still working properly (no bootloader = dead screen) and that you just need to execute the proper button combo to get to the bootloader screen. As long as bootloader works, the phone is recoverable.
Also, have you been charging the device? Since you let the battery die, you should charge it fully again (overnight on wall charger, not connected to PC).
Click to expand...
Click to collapse
in my case bootloader is working even i cn can access recovery( but to access recovery it takes 20 minutes) /data is not mounting
tried every solution to flash even ran RUU , but no luck
I did nothing to device as such , device rebooted and i think EMMC blown itself!