Database Info

[Q] Bricked? By trying to get s-on

Dear xda-community,
as said in the title i dont know if i bricked my device by trying to get s-on again.
At first i read some threads here about getting s-on again and revert to stock.
I was s-off by revelutionary and flashed the ENG-hboot a few days ago (0.98.2000). After that i flashed the stock 1.47 rom and was trying to get s-on and stock again with the 1.47 RUU. I read that if i have the ENG-hboot i can run the RUU and then i get back to stock and s-on. But after i was running the RUU, i get to the bootloader again (on the phone). In the header stands now "*** Security Warning ***" and i'm s-on again like i want it with hboot 0.98.0002.
But the problem is that i cant get out of the bootloader, i can only acsses fastboot and the bootloader. If i click 'recovery', 'reboot' or anything else it only restarts the bootloader. I cant even turn the phone off, only with pulling the battery :/
So i'm stucked in the hboot 0.98.0002 with s-on and i dont know what i can do now or if i bricked my desire s permanently
Can anyone help me please?

are you sure that you have used the right RUU?

amidabuddha said:
are you sure that you have used the right RUU?
Click to expand...
Click to collapse
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?

Jahai said:
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Click to expand...
Click to collapse
It should be if you bought it in Europe. What happens when you try the RUU again? You should do this when "FASTBOOT USB" is written on your phone screen.

amidabuddha said:
It should be if you bought it in Europe. What happens when you try the RUU again?
Click to expand...
Click to collapse
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S

Jahai said:
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Click to expand...
Click to collapse
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit

amidabuddha said:
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
Click to expand...
Click to collapse
thank you for your help!
i will try that and report back in a few minutes

hm
i cant get it to work in this way :/
if i write fastboot flash system C:\android-tools\system.img
it tells me:
"sending 'system' (571388 KB)...
OKAY [93.130s]
writing 'system'...
(bootloader) signature cheking...
FAILED (remote: signature verify fail)
finished. total time: 166.095s"
its the same with boot_signed.img and recovery_signed.img

if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?

So you problem maybe sounds the same, but it is not.
Try
Code:
fastboot oem rebootRUU
Your phone will reboot to a black screen with silver HTC logo. Then run the RUU.
Other options is to go to the repair centre and tell them that this happened during OTA update.
Sent from my HTC Desire S using Tapatalk

Jahai said:
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
Click to expand...
Click to collapse
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk

amidabuddha said:
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
will try it with that. since now i tried it until 2.10.401.4
Edit: it took me ages to download that ruu from filefacrtory :/

i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever

Jahai said:
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Click to expand...
Click to collapse
Go to repair center and say that the OTA update did this (it is the same as RUU) They should repair it for free
Sent from my HTC Desire S using Tapatalk

maybe there is any way to get s-off from fastboot or bootloader?

got to new hboot with this instruction: http://forum.xda-developers.com/showpost.php?p=20850548&postcount=22
managed to get the unlocktoken from htcdev but if i flash it everything themes fine, but i cant choose the option yes (unlock bootloader).
if i choose "no" and press the power button it reboots like it should but if i choose "yes" and press the power button nothing happens. i can still choose between the options but nothing happens :/
anyone know how i can get it working to unlock this bootloader and flash a custom recovery?

[Q] RUU error 155, can't get into recovery, HALP

Okay so I have been running CM10 fine for months. But I got a notification about an OTA update to CM10.1 and decided to let it install... bad idea.
the install process failed somehow and then my phone was stuck at the HTC screen when booting. Booting into recovery wouldn't work because it would try to install the ROM but always fail. So I figured I could just flash my recovery and restore. So I download the newest TWRP and flasht he recovery. Once I get into TWRP I couldn't read the SDCARD or find any of my files. But if I use an adb shell I can see CM10.1 and Gapps for 4.2.2 So I tried restarting recovery a couple times but I could never get the recovery to see the files. I figured I would just relock the bootloader, run RUU, then start the rooting/unlocking process fresh as I have done in the past when I got into trouble. Only problem now is that I get error 155 when trying to run the RUU utility, and can't boot into recovery since I re-locked my bootloader. I can still use fastboot but that's it, HALP!

What ruu are you using? Error 155 usually means its the wrong ruu.

iElvis said:
What ruu are you using? Error 155 usually means its the wrong ruu.
Click to expand...
Click to collapse
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217

SkuzeeII said:
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217
Click to expand...
Click to collapse
Do you have an AT&T phone? Or something else?

I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?

SkuzeeII said:
I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?
Click to expand...
Click to collapse
unlock yourself using "fastboot flash unlocktoken Unlock_code.bin"

Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.

iElvis said:
Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.
Click to expand...
Click to collapse
I've been at the same issue myself.
Have tried using the toolkit and pushing manually. I can get to the screen where you choose yes/no to unlock, which I choose yes. Then the phone just shuts off. When I turn it back on, the factory reset is done but I'm still stuck at "RELOCKED". I've probably tried this 20 times tonight and do not know what I'm missing. My CID is still all 1s.
FYI, using 2.20 RUU (had a similar issue... CM10 nightly bricked phone completely so used 2.20 RUU to restore phone)

i sometimes have alot of problems getting token to stick. try booting into bootloader without phone plugged up to computer, once booted into bootloader plug in phone, then push the token.

I've found that you need to unplug and reboot your phone before pushing the token. When I do this, it always takes the first time.
Sent from my HTC One X using Tapatalk 2

So I found that I was rebooting the phone myself when I shouldn't have during the unlock process. So I've got it unlocked now, and I can install recovery like TWRP or CWM but now I'm trying to get a ROM to load. I'm using the last Evita CM10 build but it always gets stuck on the booting screen. I think maybe I need an update.zip or need to use adb to get root from fastboot or recovery but I can't remember how and searching hasn't helped me yet...

I'm going to try to do a fastboot flash boot boot.img with the boot.img file from my CM10 zip file. Maybe that's what I was missing

I really should just be more patient before creating a thread. I got into CM10 then got S-OFF so now I'm on CM10.1

Question on 3.18 Firmware

I know that the new roms use a new kernel now.
I'm on 1.14 Hboot
S-ON
*UNLOCKED
*TAMPERED
I am rooted (Not sure if supercid but I assume so)
Since you have to be on 3.18 now, and be S-OFF, Do I have to go back to stock, do official 3.18 OTA and then unlock bootloader and root again?
I'm kind of confused.
(At&t One X)

The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita

timmaaa said:
The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita
Click to expand...
Click to collapse
I'm trying to get back to stock.
Just sick of this phone.
I didn't know about the 2.20 to 3.18 bricking problem with s-on. so I bricked my phone. warranty replacement on it. got the new on, did the ota update to 3.18. used hasoon's tool to root and unlock the bootloader. got soff, downgraded my touch to use the cm10.1 nightly. and just have had a TON of problems since.
phone turning off, getting stuck in boot loops. tried going to cm10.0 and had the same issues, was able to load a backup from the htc sense rom before I put CM on and even that will reboot and get stuck in a boot loop.
I wish I hadn't touched the damn thing.
Now I'm scared to run the RUU 3.18 because last time it bricked my phone.
I do have my boot loader unlocked, on hboot 2.14 and have s-off.
Should I be okay to run that RUU you listed?

Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita

timmaaa said:
Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much! I followed everything you said and it worked, only problem is the TWRP, it freezes for a sec when I click to reboot and then goes unresponsive until it restarts.

[Q] Help with returning to stock/Stuck at bootloader

I'm having a problem with my One X and returning it to stock. I've been rooted with S-ON for quite some time now and had the Viper ROM installed. Now it's time to trade it in to Amazon and I wanted to return it to stock and hopefully remove the tampered text. I seem to have gotten myself in to a pickle though and I'm stuck at the bootloader.
I've been using the WinDroid Universal HTC Toolkit to install stuff, I have the unlock.bin file from HTC, and I've been able to communicate with the phone through my Windows 7 computer no problem. But after the last attempt I relocked the phone and not I'm stuck. Here's what it says on the bootloader screen:
*** TAMPERED
*** RELOCKED
*** Security Warning
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
Using the WinDroid kit it shows that it successfully unlocked the bootloader and loaded TWRP, but since it's in fastboot, WinDroid doesn't recognize the phone model and won't let me send any files to it though. When I reboot the phone in to recovery, it returns me to the bootloader.
Anyone have any advice?

First piece of advice: ditch the toolkit, you don't need it. The best way for you to go about this is to follow these steps:
1) Unlock the bootloader again.
2) Flash TWRP again.
3) Flash a ROM.
4) Get s-off (this is the most important step, and all the previous steps were all leading to this).
5) Run an at&t RUU (to return the phone to stock, I'm assuming it's the at&t model?).
6) Return the CID to the original CID.
Code:
fastboot oem writecid CWS__001
7) Relock the bootloader.
Code:
fastboot oem lock
8) Return the phone to s-on.
Code:
fastboot oem writesecureflag 3
Voila.
Sent from my Evita

Wow. Nice Tim !!!
Sent from my Inspire 4G using Tapatalk

Thanks for the help so far. Under your advice I'm using fastboot commands manually to try and get this to work. So now I'm unlocked again, but I'm having a problem flashing TWRP. I downloaded the latest TWRP for the Evita and ran fastboot flash recovery evita.img (that's what I renamed the file to). It tells me that sending and writing was OKAY, so it should work. Then I try to reboot to recovery from the bootloader menu, and it fails after this. It appears to boot something up, I get a blank screen, then it reboots again on it's own without showing the TWRP menus.
What am I doing wrong?

You can't reboot to the recovery, you can only reboot to the bootloader and then manually select recovery using the hardware buttons (volume = scroll, power = select). The whole process should go like this:
Code:
fastboot flash recovery evita.img
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can manually select recovery and it should hopefully boot into it.
Sent from my Evita

That's what I did, although I just tried these steps again. When I used the volume/power buttons and chose recovery, it reboots as it should, then it tries to load the recovery, fails, then reboots and starts up the phone. I should note, and this might be the problem, is that phone boots up totally in to the full blown OS. It's Android 4.1.1 with the 3.18 kernel.
I have SuperCID, and the phone says it is unlocked with S-ON.
Does it make sense and try to flash the 2.15 firmware at this point since my HBOOT is older?

I tried another thing since I can actually use the phone and I'm rooted, I installed GooManager from the store and let that install the recovery then rebooted. It did the same thing. At the very least, if I could only get TWRP working I could recover a TWRP backup I made.
And ultimately, the phone works at this point, I just want to remove the tampered text and keep it at stock. Since I have a working ROM, should I just follow your steps 6, 7 and 8? Do I still need to achieve S-Off and worry about the recovery?

You need s-off, otherwise running the RUU will brick your phone. Just try getting s-off without the recovery. Which ROM is currently installed?
Sent from my Evita

I have an AT&T stock deodexed ROM version 3.18.502.6.

Ok, scratch that, without root you cannot get s-off. What's the exact filename of the recovery you've tried to flash?
Sent from my Evita

Bricked htc u11 please help!!!

Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.

kunalrokz said:
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
Click to expand...
Click to collapse
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!

OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
Thanks I'll try it out shortly!!

kunalrokz said:
Thanks I'll try it out shortly!!
Click to expand...
Click to collapse
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp

I'm on the same boat as you... Any news?

wranglerray said:
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
Click to expand...
Click to collapse
The unlock token wont flash gives me a permission error. I will post the exact error in a while.

OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
I tried your recommendation but to no avail. when I boot into the bootloader and send the fastboot command it gives me error "FAILED (remote: GetVar Variable Not found)" and when I do it in download mode it says okay and gets stuck on booting... the phone itself downloads the recovery and displays flash images success (1/1) but nothing else happens.
HOWEVER after sending that command I tried the unlock bootloader command and miraculously it WORKED! I got access to recovery!! I think that being in the download mode explicitly helped the bootloader recognize the unlock token.

zopostyle said:
I'm on the same boat as you... Any news?
Click to expand...
Click to collapse
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
 @wranglerray and @OMJ thank you so much for your help

kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...

kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
Good to hear!
Cheers
Your neighbor to the south

kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
sweet!
zopostyle said:
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
Click to expand...
Click to collapse
stock recovery or twrp? you'll need to give more specifics...

OMJ said:
sweet!
stock recovery or twrp? you'll need to give more specifics...
Click to expand...
Click to collapse
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
​(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
​
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from ​ 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)

zopostyle said:
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
​(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
​
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from ​ 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
Click to expand...
Click to collapse
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.

kunalrokz said:
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
Click to expand...
Click to collapse
Hum, OK, thanks.
Yes, my bootloader is unlocked and I can flash recovery and boot.img successfully.
I'm at work right now at night I'm gonna try that fastboot -w option.
About the custom rom I've already tried leeDroid and MaximusHD but none of then booted.

What is this?
Failed to mount '/cota' (invalid argument)

AndrzejQ said:
What is this?
Failed to mount '/cota' (invalid argument)
Click to expand...
Click to collapse
An error that I received.
I got it working already.

i have the same problem. had you worked this out ? what's the solution ?

Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...

Void tracer said:
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Click to expand...
Click to collapse
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.

MSMC said:
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
Click to expand...
Click to collapse
I can't guarantee this will work, but try the following:
Use the spreadsheet here to find the latest RUU for your phone's CID and MID.
Rename the downloaded RUU to 2PZCIMG.zip
Move 2PZCIMG.zip to the root of your external SD card. If you don't have an external SD card you'll need to get one. If using a PC make sure to format the card as exFAT.
Follow the instructions at 'https://www.the custom droid.com/how-to-restore-htc-u11-stock-firmware/#Method-1-Flashing-RUU-in-Download-Mode' to flash the RUU to your phone.
Good luck!
EDIT: I don't why but XDA forums are filtering the string c u s t o m d r o i d (w/o the spaces)