Database Info

[Q] Error 155 Such a case has not yet gone.

I have RUU which I used a few times, this time one pops me "error 155" and check the CID still gives me H3G-UK H3G__001 but as I check the version does not show any information. Already changed the cables, I have uploaded the drivers, I downloaded the new files from the RUU.
TEMPERED
RELOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.08es 50.02.16
PpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
If anyone can solve this riddle?

Ironic this happened to you because I was just trying to go back to ( which I have successfully have done several times before ) my stock RUU file. I am also getting the ERROR 155. Maybe our issues are the same.
I have :
- Gone back to a stock rom
- Relocked Bootloader
- tried to run RUU from within Fastboot ( and every other way I could imagine )
Still get the ERROR 155! The only difference now is that I am coming back off a Jelly Bean ROM ( every other time I was on a Sense 4.04 based ROM)
Could that be the issue? Did it update my HBOOT to one that my stock RUU won't recognize? That seems to be were the RUU fails everytime. It blinks fast but I do beleive the RUU installer says something about HBOOT before it craps out.
Any suggestions or help would be appreciated by us both I presume!
Thanks! :fingers-crossed:

Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Sent from rooted awesomeness using xda premium

TheArtiszan said:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Click to expand...
Click to collapse
Thanks for the reply! I didn't even think to look for a log file for the RUU. Sure enough it was right on the root of my hard drive! The log confirms my suspicion :
<T230213><DEBUG><OUT>INFOchecking hboot version...</OUT>
</DEBUG></T230213>
<T230213><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Somehow my HBOOT has been updated from the last time I have went back to stock. I don't remember doing an update last time I was STOCK and RELOCKED ( i might of though, can't remember! ). Is it possible that the Jelly Bean ROM I had installed after my last RELOCK, updated the HBOOT?
Sooooo.....I went ahead and I have extracted the HBOOT NB0 file from the ROM.ZIP that the RUU creates in a temp folder. Is there a way to push that onto my phone, then run the RUU?

Hope this helps!
So first off, to the OP Kobi71, sorry if I hijacked your thread! I was going to post about my issue and came across yours first which sounded pretty much identical! So hopefully my experience can help you!
So I got it to work! I have successfully flashed my RUU. What I found out from reading other threads and poking around was that my HBOOT was to new for the RUU file I had. There isn't an update RUU for my phone out there so I decided to give the HBOOT downgrade to 1.06 a shot.
[TUT] Downgrade/Unbrick Ville S4
http://forum.xda-developers.com/showthread.php?t=1990043&page=16
I followed the instructions and it all worked out just fine. READ through the instructions twice if you have too!
Understand them if you decide to try this because your essentially bricking your phone (at first). All being said, worked like a charm. Downgraded to HBOOT 1.06 from 1.13. The only "troubles" I had during the process, was that when I did step 9 and 12 the phone would hang on Sending Reset randomly throughout the process. Probably about ten times. So I did this each time :
absolutelygrim said:
" If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed "
Click to expand...
Click to collapse
It also hung at the very end of the process too, so again hold the power button down if that happens to you.
After all that was done, I flashed the stock recovery from the ROM.ZIP that i got from the RUU ( don't know if I needed to do this ). Wiped everything/Factory reset. Then i relocked the bootloader. I then ran the RUU file, and it worked perfectly. Just like before. HBOOT was also "upgraded" to 1.08
Hope this helps your situation!

[Q] [ Help! ] One S - soft bricked, S-ON, can't manage to get S-OFF, wont load ROM

Hello guys, this is the 5th day since im messing my mind on this particular device, im out of ideas now, and thats why im creating this thread hoping someone will solve this puzzle out.
I was reading a lot of tutorials, tryed many diffrend ways to get S-off, or trying to get back to stock..
GOAL: make this One S work, being rooted and have s-off, and have custom rom with sense 5 on it.
Story: i bought this HTC ONE S as a used device on cheap price, it was looking terrible, damaged case, cracked glass, outdated rom.
but i got idea i have to buy this one, because i think HTC ONE S IS MOST PRETTY DEVICE I HAVE SEEN , i will do restoration and make this baby beautiful as new! I polished glass, put glass protection on, repainted whole case with new white car paint. (it was black color version) now i have beautiful WHITE edition of HTC ONE S. its not for resell or anything, just personal use. ( i will do photos later on, when i will finish this project).
I noticed this phone have custom rom on it, but it was kinda buggy and slow, and outdated, it was some modded ICS rom. i was thinking like: no problem, i just read some tutorials here and flash new fancy rom, it will take just a hour or so at most,
i though this will be easy cake... since i have samsung galaxy s3 and i flashed it many times without problems.
ohhh how wrong i was... i almost bricked this phone...
THE STAGE THIS PHONE IS NOW AT:
ITS AN S4 DEVICE,
it can boot in to HBOOT with no problems and it can be controlled from windows 7 with fastboot commands.
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
(date and clock)
Recovery also works
TWRP v2.6.3.0
it have sweet feature to mount internal sdcard as usb flash for windows, also file browser and so on.. really like this recovery.
last installed rom: cm-10-2.0.-ville.zip
(but it wont load of course)
but after it hangs on HTC logo, red lines about developer rom, ADB DEVICES command shows this device serial number and phone listens to ADB commands with windows cmd from SDK platform tools.
This device original CID was: ORANG001
i was trying to get supercid, and somehow i managed to make it 11111111, but i cant managed to install any original RUU, so later i tryed to change cid to O2___001, and install O2 RUU, but it still wont install.
now i cant change CID to 11111111, just wont work, i have no idea how i changed in first place. but i edited hex and now i cant push this file with supercid againt to phone, gives error. also fastboot write cid wont work to, ends up in error and flastboot frozes, need to reset by holding power key.
so now im stuck with CID: O2___001
soo... can somebody give me some instructions how to get out of this crazyness and make this sweet phone work again by having Maximus HD on it? thank you

Saiyaru said:
Hello guys, this is the 5th day since im messing my mind on this particular device, im out of ideas now, and thats why im creating this thread hoping someone will solve this puzzle out.
I was reading a lot of tutorials, tryed many diffrend ways to get S-off, or trying to get back to stock..
GOAL: make this One S work, being rooted and have s-off, and have custom rom with sense 5 on it.
Story: i bought this HTC ONE S as a used device on cheap price, it was looking terrible, damaged case, cracked glass, outdated rom.
but i got idea i have to buy this one, because i think HTC ONE S IS MOST PRETTY DEVICE I HAVE SEEN , i will do restoration and make this baby beautiful as new! I polished glass, put glass protection on, repainted whole case with new white car paint. (it was black color version) now i have beautiful WHITE edition of HTC ONE S. its not for resell or anything, just personal use. ( i will do photos later on, when i will finish this project).
I noticed this phone have custom rom on it, but it was kinda buggy and slow, and outdated, it was some modded ICS rom. i was thinking like: no problem, i just read some tutorials here and flash new fancy rom, it will take just a hour or so at most,
i though this will be easy cake... since i have samsung galaxy s3 and i flashed it many times without problems.
ohhh how wrong i was... i almost bricked this phone...
THE STAGE THIS PHONE IS NOW AT:
ITS AN S4 DEVICE,
it can boot in to HBOOT with no problems and it can be controlled from windows 7 with fastboot commands.
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
(date and clock)
Recovery also works
TWRP v2.6.3.0
it have sweet feature to mount internal sdcard as usb flash for windows, also file browser and so on.. really like this recovery.
last installed rom: cm-10-2.0.-ville.zip
(but it wont load of course)
but after it hangs on HTC logo, red lines about developer rom, ADB DEVICES command shows this device serial number and phone listens to ADB commands with windows cmd from SDK platform tools.
This device original CID was: ORANG001
i was trying to get supercid, and somehow i managed to make it 11111111, but i cant managed to install any original RUU, so later i tryed to change cid to O2___001, and install O2 RUU, but it still wont install.
now i cant change CID to 11111111, just wont work, i have no idea how i changed in first place. but i edited hex and now i cant push this file with supercid againt to phone, gives error. also fastboot write cid wont work to, ends up in error and flastboot frozes, need to reset by holding power key.
so now im stuck with CID: O2___001
i would like to get step instructions what i should try do now, like guiding me trough steps on actions, and i will report how phone responds, and making this phone alive again ?
Click to expand...
Click to collapse

Saiyaru said:
Hello guys, this is the 5th day since im messing my mind on this particular device, im out of ideas now, and thats why im creating this thread hoping someone will solve this puzzle out.
I was reading a lot of tutorials, tryed many diffrend ways to get S-off, or trying to get back to stock..
GOAL: make this One S work, being rooted and have s-off, and have custom rom with sense 5 on it.
Story: i bought this HTC ONE S as a used device on cheap price, it was looking terrible, damaged case, cracked glass, outdated rom.
but i got idea i have to buy this one, because i think HTC ONE S IS MOST PRETTY DEVICE I HAVE SEEN , i will do restoration and make this baby beautiful as new! I polished glass, put glass protection on, repainted whole case with new white car paint. (it was black color version) now i have beautiful WHITE edition of HTC ONE S. its not for resell or anything, just personal use. ( i will do photos later on, when i will finish this project).
I noticed this phone have custom rom on it, but it was kinda buggy and slow, and outdated, it was some modded ICS rom. i was thinking like: no problem, i just read some tutorials here and flash new fancy rom, it will take just a hour or so at most,
i though this will be easy cake... since i have samsung galaxy s3 and i flashed it many times without problems.
ohhh how wrong i was... i almost bricked this phone...
THE STAGE THIS PHONE IS NOW AT:
ITS AN S4 DEVICE,
it can boot in to HBOOT with no problems and it can be controlled from windows 7 with fastboot commands.
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
(date and clock)
Recovery also works
TWRP v2.6.3.0
it have sweet feature to mount internal sdcard as usb flash for windows, also file browser and so on.. really like this recovery.
last installed rom: cm-10-2.0.-ville.zip
(but it wont load of course)
but after it hangs on HTC logo, red lines about developer rom, ADB DEVICES command shows this device serial number and phone listens to ADB commands with windows cmd from SDK platform tools.
This device original CID was: ORANG001
i was trying to get supercid, and somehow i managed to make it 11111111, but i cant managed to install any original RUU, so later i tryed to change cid to O2___001, and install O2 RUU, but it still wont install.
now i cant change CID to 11111111, just wont work, i have no idea how i changed in first place. but i edited hex and now i cant push this file with supercid againt to phone, gives error. also fastboot write cid wont work to, ends up in error and flastboot frozes, need to reset by holding power key.
so now im stuck with CID: O2___001
soo... can somebody give me some instructions how to get out of this crazyness and make this sweet phone work again by having Maximus HD on it? thank you
Click to expand...
Click to collapse
Well lest start shall we...
First find stock or close to stock ROM like sourcE
Then find the tool rumrunner and s-off
once your s-off your going to flash the ROM first then update firmware in maximus But before that back up your SD your going to have to wipe it
Now if you get a bootloop your going to have to adb push the ROM to your phone I hope this helps you
Sent from my Nexus 7 using Xparent Red Tapatalk 2

Flashalot said:
Well lest start shall we...
First find stock or close to stock ROM like sourcE
Then find the tool rumrunner and s-off
once your s-off your going to flash the ROM first then update firmware in maximus But before that back up your SD your going to have to wipe it
Now if you get a bootloop your going to have to adb push the ROM to your phone I hope this helps you
Sent from my Nexus 7 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
ty for helping ;D
ok, i installed SourcE 1.4 zip trough recovery, and did cache, dalvic wipe, but after system reboot, i got boot loop. also ADB wont show device number, so its even less wants to boot as with Cyanogen mod roms. they also get boot loop but atleast ADB shows device number after sending command adb devices.
ok, i will simply try now do s-off like i would do by tutorial, and tell u where i get stuck.

completely stock (never tampered) Mini won't boot past hboot into OS

Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.

iceterminal said:
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
Click to expand...
Click to collapse
I gotchu my friend ;D http://www.htc.com/us/support/htc-one-mini-att/news/ That is the ruu for the htc one mini

abzboi said:
I gotchu my friend ;D That is the ruu for the htc one mini
Click to expand...
Click to collapse
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!

iceterminal said:
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
Click to expand...
Click to collapse
Ah I read that it will work too if it is fastboot which is why you were suggesting it. I'm wrestling with fastboot drivers and windows 8.1 so it is recognized so I dualbooted into ubuntu which can communicate via fastboot so I'm hoping WINE will run and flash the RUU .exe

So I ended up rebuilding an older laptop to Windows 7 and ran the RUU executable and it looked promising at first with the updater recognizing the device and displaying what software version and stuff.... but then when it rebooted into hboot with it's process, the update failed.. not sure if it matters but it was "updating" from the same version as the current version. I was hoping this would be a fresh install. So now I'm looking into maybe doing a fastboot oem unlock and flashing a rom myself. Not sure if this will help me get the phone back from the dead, but going to do some more reading and exploring. If anyone has some shots-in-the-dark they would like to offer, I'm up for trying them.

I hope you would be able to fix it.

Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.

iceterminal said:
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
Click to expand...
Click to collapse
Have sent you a PM re your issue.....
Re flashing recovery without fastboot (locked bootloader), it can be done, but only, as far as I know, via the phone os using CWM manager or Flashify (which is a cool app!)

wanted to close the loop on this thread that nelvinchi and I literally tried everything we could think of to bring the phone back to life with no avail. Much respect out to nelvinchi for taking his time to help me out! We've determined that the device has a faulty memory chip and cannot be recovered...

Mine just did the same thing and I can't get through to anything I need help also if you have found a solution

Help my
provided you solve a problem with one htv mini.my I have the same problem, please help me

[Q] Ask a Stupid (Firmware) Question

Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.

Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita

So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.

Did you check the md5 of the recovery download?
Sent from my Evita

timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.

Stuck on Verizon screen, can't open bootloader or recovery

Hello,
I bought an unlocked HTC One M8 off Amazon two years ago and I rooted it a year ago and everything was fine. Today I got the notification that SuperSU needed to update its binaries, I thought it was weird since it just updated binaries a few days ago but I went on ahead and did it. It asked to reboot my phone and now I'm stuck on the Verizon screen. I'm way out of my field here, I don't even remember how I rooted it exactly and going through the threads here is making my head hurt. I was following advice from this thread but I feel like I hit a brick wall. I hit "fastboot" on bootloader and it takes me to the screen with the "hboot, ramdump, reboot, reboot fastboot, power down" options but I don't know what I'm supposed to do here. Recovery takes me to TWRP but idk what to do there either. I tried the suggestion to run the RUU but it always says that my phone is not connected and won't let me do anything, I updated my drivers but it still won't recognize my phone. As a last resort I tried doing a factory reset but that doesn't work either. I don't know what else to do and I'm starting to think I just got a new shiny brick. Can anyone help? Thanks in advance.
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5
eMMc-boot 2048MB
Feb 3 2015,21:50:28

guilisafreak said:
Hello,
I bought an unlocked HTC One M8 off Amazon two years ago and I rooted it a year ago and everything was fine. Today I got the notification that SuperSU needed to update its binaries, I thought it was weird since it just updated binaries a few days ago but I went on ahead and did it. It asked to reboot my phone and now I'm stuck on the Verizon screen. I'm way out of my field here, I don't even remember how I rooted it exactly and going through the threads here is making my head hurt. I was following advice from this thread but I feel like I hit a brick wall. I hit "fastboot" on bootloader and it takes me to the screen with the "hboot, ramdump, reboot, reboot fastboot, power down" options but I don't know what I'm supposed to do here. Recovery takes me to TWRP but idk what to do there either. I tried the suggestion to run the RUU but it always says that my phone is not connected and won't let me do anything, I updated my drivers but it still won't recognize my phone. As a last resort I tried doing a factory reset but that doesn't work either. I don't know what else to do and I'm starting to think I just got a new shiny brick. Can anyone help? Thanks in advance.
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.12.20.1211
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-4.17.605.5
eMMc-boot 2048MB
Feb 3 2015,21:50:28
Click to expand...
Click to collapse
I think the easiest solution to try is to flash the most recent SuperSU.zip in TWRP.
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
The process may of had issues if your TWRP is out of date, I think.. not sure.
But you have options, for sure
Flash a custom rom. If you prefer stock, then flash RUU, using sd-card method.
I don't think you need to worry about a brick as long as you're still nothing into hboot and recovery.
Once it won't turn on, then you have yourself a brick.
Or the state of some HTC 10 owners who are stuck in aboot and can't enter recovery.
You are stuck in a bootloop, or soft brick, if you will.