Database Info

[Q] Help with Boot/Recovery Problems?

Hello, I have a T-Mobile HTC Sensation 4G, and I've ran into some problems recently. I'm a basic-intermediate user when it comes to Android, but I can't find a solution specifically for this. It started with a small problem but got worse and worse until I couldn't even boot correctly.
I started out installing a small custom battery mod, but that led to a few problems with the notification bar (not a big deal).
Then I tried to revert to the stock battery to fix the problem, format cache and dalvik cache in recovery, and reset. Then I was put into an infinite boot loop with the HTC splash, but going into cwm recovery was still possible.
Then, in recovery, I could not access my sd card for some reason, so I shut off, reinserted the sd card, and remounted it, then I reset again.
Now, it's impossible to boot to android at all, and I am completely stuck at HBOOT/FASTBOOT, and cannot access recovery OR perform a hard reset.
If I try to reinstall cwm recovery, I get a partition update fail as well...
I have full root, s-off, etc.
ROM- InsertCoin 3.3.1
Kernel- Stock
Hboot- 1.17.1011
Clockwork version- 5.0.0.8
Any suggestions? Am I bricked? I can give more details if needed.

I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium

neoissuperman said:
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Alright, thanks, I'll try that soon and see if it works.
Update: Unfortunately, I don't think I can flash anything, it just comes up with a partition update fail...

Anyone else know what I could try? I also tried to flash the 1.45 RUU, but it can't continue past the search for the bootloader.

If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device

joshndroid said:
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
Click to expand...
Click to collapse
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...

have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas

joshndroid said:
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
Click to expand...
Click to collapse
Nope, still nothing, I even tried different sd cards and usb cables, with no difference...
So has my phone been reduced to a paperweight?

APmoss13 said:
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
Click to expand...
Click to collapse
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.

Divine flaw said:
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Click to expand...
Click to collapse
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.

APmoss13 said:
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
Click to expand...
Click to collapse
ok.... i was just askin cause did the exact same thing (well almost, i tried to change the notification icons which resulted in my notification bar completely gone) you did and got into that infinite boot loop. and couldnt boot into android. and couldnt figure it out. the only thing i did was just install the ruu while i was in the fastboot screen and it worked. i wasnt aware that there was a 1.45 ruu for tmous but i dont think that should matter since you are scid anyways. now im just wonderin if you tried any other ruu's besides that one. for me i flashed the 1.29 ruu for tmous and that got me up and running...... sorry i couldnt help

one x soft bricked stuck on htc logo and reboots

hey guys i have asked this in other threads with no answer
a customer hard reseted the device using the opyion inside the rom
not the devies gets to htc logo then reboots then htc logo and green logo like updating then red triangle
thas it after a while reboots and on and on
i wanted to install oem
i went to hboot
then to fastboot
run the oem ruu
goes to bootloader
and erases the user data and then starts sending
and thats it nothjing elses happens for hours
no instalation
what can i do?

Does the phone has unlocked bootloader? If yes it could be why. You can't go back to stock ruu unless you have locked bootloader. Try relock it before you flash ruu.

phidung3721 said:
Does the phone has unlocked bootloader? If yes it could be why. You can't go back to stock ruu unless you have locked bootloader. Try relock it before you flash ruu.
Click to expand...
Click to collapse
it says tampered locked
it was new when sold
customer dont know how to do the
bootloader unlocking

The carrier ID (CID) of the phone needs to match the CID for the RUU, or you need the phone to have SuperCID. That may be your problem also.
Need more details on what version (carrier) of the phone you have, and which RUU you are trying to run.

If it was having an issue, you would get an error telking you why it failed. If it gets as far as to start the process it recognizes the phone and is worjing properly. On slower pc's the process can take up to an hour ive seen. Start the procesz and do not touch it unless it finishes the process, or gives u an error of some sort. As long as it says sending, its sending and let her do her thing.
---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------
You can also select the recovery option when your in bootloader. Once in recovery select the factory reset option, then reboot.

all night long and nothing
D:\Elman Ortega\Desktop\android>f
cid: CWS__001
finished. total time: 0.003s
D:\Elman Ortega\Desktop\android>
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
mine is a quadcore 3.6ghz desktop pc
1.09.0000
radio 0.16.32.09.01

Your in fastboot right there. From right there you can type
fastboot erase cache
Then
fastboot reboot
Or
Fastboot erase cache
Then
Fastboot reboot recovery
Then do a factory reset

18th.abn said:
Your in fastboot right there. From right there you can type
fastboot erase cache
Then
fastboot reboot
Or
Fastboot erase cache
Then
Fastboot reboot recovery
Then do a factory reset
Click to expand...
Click to collapse
Can you do a factory reset with a stock recovery?
Sent from my HTC One XL using Forum Runner

Absolutely

18th.abn said:
Absolutely
Click to expand...
Click to collapse
Hi I actually haVE THE SAME PROBLEM.
THis is how it happened
MIUI
CM10
MIUI
Stock
MIUI
Clear Cache
SD card not recognised in TWRP
Tried Factory reset, system cache etc
RUU failed
Unplugged
Not recognised by Windows but can by mac
Flashed hBoot from the RUU
Now bricked
Still have lights, TWRP, HBOOT
Please help!!!

PM me or hit me up on gtalk. Ill help you out

XsMagical said:
PM me or hit me up on gtalk. Ill help you out
Click to expand...
Click to collapse
Sorry but i'm very new, how to pm you

cw99, having twrp and hboot is very very very far away from a brick.
odds are you made the mistake of factory reset inside the phone or bootloader instead of in twrp only. only time i made that mistake i just ran the ruu and never plan on making the mistake again. others might have done it for testing purposes to find ways to properly revive it without needing to run ruu.
with newest twrp 2.3 you might be able to get away with adb sideload flashing of a rom if that works. then format internal storage once you boot into rom.

DvineLord said:
cw99, having twrp and hboot is very very very far away from a brick.
odds are you made the mistake of factory reset inside the phone or bootloader instead of in twrp only. only time i made that mistake i just ran the ruu and never plan on making the mistake again. others might have done it for testing purposes to find ways to properly revive it without needing to run ruu.
with newest twrp 2.3 you might be able to get away with adb sideload flashing of a rom if that works. then format internal storage once you boot into rom.
Click to expand...
Click to collapse
Hi I tried it but it did not work. When I clicked ADB SIDELOAD, they said mounting of storage failed and hence I cannot enter it.

XsMagical said:
PM me or hit me up on gtalk. Ill help you out
Click to expand...
Click to collapse
Thanks XsMagical for the help! You really saved my life!

Awesome, what was the issue?

Im in big trouble.

Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?

wonkizzle said:
Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
Click to expand...
Click to collapse
You are not bricked. Try flashing the stock recovery which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=2708291

droidkevlar said:
You are not bricked. Try flashing the stock recovery which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=2708291
Click to expand...
Click to collapse
How can I flash it if it wont even boot? The screen wont come on and it just rumbles.

wonkizzle said:
How can I flash it if it wont even boot? The screen wont come on and it just rumbles.
Click to expand...
Click to collapse
You cant get into fastboot?
Mode: press and hold Volume Down and Power simultaneously. You will soon see the LOCKED text and then you can release the keys.

droidkevlar said:
You cant get into fastboot?
Mode: press and hold Volume Down and Power simultaneously. You will soon see the LOCKED text and then you can release the keys.
Click to expand...
Click to collapse
No, the screen (barely) lights up for a split second, then shuts off, and vibrates. This repeats over and over. Ive tried holding all the buttons for 90 seconds, still just vibrates. Ive tried all button combinations for as long as I thought it was needed, and nothing is bringing any picture back to the screen. Just vibrations.

wonkizzle said:
No, the screen (barely) lights up for a split second, then shuts off, and vibrates. This repeats over and over. Ive tried holding all the buttons for 90 seconds, still just vibrates. Ive tried all button combinations for as long as I thought it was needed, and nothing is bringing any picture back to the screen. Just vibrations.
Click to expand...
Click to collapse
Not sure what else to try, but I know you're not hard bricked. You are just softbricked. I would go into the M8 channel on irc. andirc.net and channel is #m8
jcase and others hang out there and can be able to help you.

wonkizzle said:
Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
Click to expand...
Click to collapse
What did you type into terminal emulator?
This thread might be of help to you: http://forum.xda-developers.com/showthread.php?t=2718562

sparky_005 said:
What did you type into terminal emulator?
This thread might be of help to you: http://forum.xda-developers.com/showthread.php?t=2718562
Click to expand...
Click to collapse
In my haste, before anyone figured out that the TWRP team listed the wrong partition to flash to, I decided to try and flash it again once more, using the same command I did before:
"su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43"
Only this time I did it within the terminal emulator in TWRP, thinking maybe I hit a typo the first time or something, and also since adb didnt list my device on my computer. And THATS when it all went to ****.
Firstly, it only vibrates every 10-15 seconds, stuck in a bootloop and crashing. Only when I hold Volume Down in between vibrates does the phone go into the bootloader. But theres the next problem.
Screen does not illuminate anymore, and I can only see whats going on when I shine a flashlight onto the screen. It will only go to the bootloader, will not load recovery, will not factory reset, fastboot getvar all returns a garbled mess of text that does not resemble the S/N or IMEI, and it seems anything I try to load through fastboot is fruitless. I need some real pros to see this thread, or im ****ed. And I didn't get insurance on the phone when I ordered it, so a replacement is out of the question. Im real upset that I ****ed myself here. I dont hold anyone responsible but myself, but I really wish the proper command would have been included in the instructions instead of flashing it to the wrong partition, twice.

wonkizzle said:
In my haste, before anyone figured out that the TWRP team listed the wrong partition to flash to, I decided to try and flash it again once more, using the same command I did before:
"su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43"
Only this time I did it within the terminal emulator in TWRP, thinking maybe I hit a typo the first time or something, and also since adb didnt list my device on my computer. And THATS when it all went to ****.
Firstly, it only vibrates every 10-15 seconds, stuck in a bootloop and crashing. Only when I hold Volume Down in between vibrates does the phone go into the bootloader. But theres the next problem.
Screen does not illuminate anymore, and I can only see whats going on when I shine a flashlight onto the screen. It will only go to the bootloader, will not load recovery, will not factory reset, fastboot getvar all returns a garbled mess of text that does not resemble the S/N or IMEI, and it seems anything I try to load through fastboot is fruitless. I need some real pros to see this thread, or im ****ed. And I didn't get insurance on the phone when I ordered it, so a replacement is out of the question. Im real upset that I ****ed myself here. I dont hold anyone responsible but myself, but I really wish the proper command would have been included in the instructions instead of flashing it to the wrong partition, twice.
Click to expand...
Click to collapse
As a side note, when you use fastboot getvar all or fastboot getvar serialno this is what happens "F:\Android-adb>fastboot getvar serialno
serialno: ≤º┴╛ ╤■ù╩■ù╚■u♀ "
Another side note, any type of attempt to flash with fastboot ends up with this: "target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.500s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.508s "

atirx7man said:
As a side note, when you use fastboot getvar all or fastboot getvar serialno this is what happens "F:\Android-adb>fastboot getvar serialno
serialno: ≤º┴╛ ╤■ù╩■ù╚■u♀ "
Another side note, any type of attempt to flash with fastboot ends up with this: "target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.500s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.508s "
Click to expand...
Click to collapse
This. He's been helping me figure this out. Anyone help?

wonkizzle said:
This. He's been helping me figure this out. Anyone help?
Click to expand...
Click to collapse
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down

dsEVOlve said:
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
Click to expand...
Click to collapse
I will report back with results as soon as I can.

dsEVOlve said:
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
Click to expand...
Click to collapse
Followed your directions exactly dsEVOlve. While the flash does complete successfully, it still did not fix the problem. Now, does flashing this way only flash recovery? I had another member who wrote some zip files trying to fix the serial number issue by replacing the mfg and misc folders. Both failed flashing through fastboot so I'm wondering if this method might have some way of working.
As I said, everything that we attempt to flash through fastboot returns the error FAILED (remote: not allowed)
Your help is greatly appreciated.

If you're a Verizon customer, take the phone back and tell them it won't turn on at all. They'll get you a new one.
Sent from my #6F6E71 M8

atirx7man said:
Followed your directions exactly dsEVOlve. While the flash does complete successfully, it still did not fix the problem. Now, does flashing this way only flash recovery? I had another member who wrote some zip files trying to fix the serial number issue by replacing the mfg and misc folders. Both failed flashing through fastboot so I'm wondering if this method might have some way of working.
As I said, everything that we attempt to flash through fastboot returns the error FAILED (remote: not allowed)
Your help is greatly appreciated.
Click to expand...
Click to collapse
Yes, it only had a recovery image in the ZIP. The ZIP you got from someone else wasn't bootloader flashable and now we've established that nothing can be flashed at this point except through the bootloader.
So you weren't able to boot to recovery through the bootloader after it updated?
I suppose the next thing I would try is reflashing the hboot through bootloader. You would follow the same process but with one of the bootloader flashable ZIPS from here: http://forum.xda-developers.com/showthread.php?t=2709976

dsEVOlve said:
Yes, it only had a recovery image in the ZIP. The ZIP you got from someone else wasn't bootloader flashable and now we've established that nothing can be flashed at this point except through the bootloader.
So you weren't able to boot to recovery through the bootloader after it updated?
I suppose the next thing I would try is reflashing the hboot through bootloader. You would follow the same process but with one of the bootloader flashable ZIPS from here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Alright, just finished trying the hboot flash through bootloader. Same results. Flashes, says to press power to reboot, remove the sdcard and take file off, reboot into a bootloop with no screen illumination.
The only other change I notice is that the flag at the top that used to say "Unlocked" now says "Relocked"

atirx7man said:
Alright, just finished trying the hboot flash through bootloader. Same results. Flashes, says to press power to reboot, remove the sdcard and take file off, reboot into a bootloop with no screen illumination.
The only other change I notice is that the flag at the top that used to say "Unlocked" now says "Relocked"
Click to expand...
Click to collapse
I'll think on it some more but I'm out of ideas. The fact that it is relocked means you probably flashed the stock hboot which might hamper any future efforts. Might want to flash the no red text version to see if it unlocks but it won't fix any of the bigger problems.

dsEVOlve said:
I'll think on it some more but I'm out of ideas. The fact that it is relocked means you probably flashed the stock hboot which might hamper any future efforts. Might want to flash the no red text version to see if it unlocks but it won't fix any of the bigger problems.
Click to expand...
Click to collapse
I know this is for S3; but would some variant of this work? http://forum.xda-developers.com/showpost.php?p=47911843&postcount=165

OP, PM me, I've worked with a few devices like this already.

Hey drache, you already dealt with this phone you tried to help me with it on irc. We had no luck.
Sent from my HTC6435LVW using xda app-developers app

[Q] Crashed HTC One X - Hating ATT Right Now

Asking for a friend... I'll try to provide all the details. If someone knows a hardware solution, cost isn't an issue within reason.
HTC One X on ATT... the phone battery was run all the way out until the phone died. When it was plugged back in, the phone no longer will boot all the way up, it shows the HTC Logo, then the ATT Logo, then back to the HTC Logo... and it just sits there... forever. If you connect it to a computer, the device is found, but you get a message that the device could not start in device manager and there is no drive.
ATTs solution to the above problem is to Wipe and Reset the phone... but she is worried about her data, especially the pictures more than anything.
Booting to Fastboot is fine, you get the following:
***Locked***
EVITA PVT SHIP S-ON-RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
emmC-boot
Nov 26 2012​
I installed the HTC drivers and fastboot on the computer and can run some fastboot commands from the computer, so I know there is communication.
I wanted to install and boot another image, such as Clockworkmod, but... when I try to fastboot flash recovery I get:
sending 'recovery' (8642 KB)...
OKAY [ 1.046s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.938s​
Running fastboot oem unlock I get:
(bootloader) [ERR] Command error !!!
OKAY [ 0.011s]
finished. total time: 0.012s​(I was told this is the error you get when the OS is not installed properly on her device, which is the case.
I booted to the recovery partition hoping there was something there from an update or something but no dice, you just get a big "!".
I checked and was told the device needed rooted first in order to install clockworkmod or something similar... the problem is, I can go to HTCs site to unlock the bootloader with the get_identifier_token command I get an error MID not allowed... because ATT blocks it of course.
I found several guides on how to get around that... but all of them require a working phone that will boot up, which is what we're trying to fix. Does anyone have ideas for me?

timmaaa provide a guide for youre case, have you try it?

bzhmobile said:
timmaaa provide a guide for youre case, have you try it?
Click to expand...
Click to collapse
Sadly, usb debugging is not turned on and since I can't boot into the OS, I can't turn it on.

sirluke4 said:
Sadly, usb debugging is not turned on and since I can't boot into the OS, I can't turn it on.
Click to expand...
Click to collapse
You can't flash clockworkmod because the bootloader is locked. If you unlock the bootloader you will wipe data, not to mention I think unlock is blocked on that device. You could try booting android in safe mode by holding vol up, otherwise it's factory reset time.

@sirluke4
If you can get into the bootloader (which you can) you can just run an RUU, which should fix your problem without wiping any user data. I'm not sure why the title of this thread mentions hating at&t though, they have nothing to do with what's going on here.
You can use this RUU to stay on the firmware that's currently on the device:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You can use this RUU to upgrade to Android 4.2.2 and Sense 5:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
RUU tutorial:
http://forum.xda-developers.com/showthread.php?t=2593037
Transmitted via Bacon

timmaaa said:
@sirluke4
If you can get into the bootloader (which you can) you can just run an RUU, which should fix your problem without wiping any user data. I'm not sure why the title of this thread mentions hating at&t though, they have nothing to do with what's going on here.
You can use this RUU to stay on the firmware that's currently on the device:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You can use this RUU to upgrade to Android 4.2.2 and Sense 5:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
RUU tutorial:
http://forum.xda-developers.com/showthread.php?t=2593037
Transmitted via Bacon
Click to expand...
Click to collapse
Running RUU WILL wipe data....

beaups said:
Running RUU WILL wipe data....
Click to expand...
Click to collapse
Running an RUU on this device doesn't wipe user data, which is what they're worried about, I've done it countless times.
Transmitted via Bacon

timmaaa said:
Running an RUU on this device doesn't wipe user data, which is what they're worried about, I've done it countless times.
Transmitted via Bacon
Click to expand...
Click to collapse
Interesting, on an s on, locked device?

beaups said:
Interesting, on an s on, locked device?
Click to expand...
Click to collapse
Yeah, I've walked a few other people through it too.
Transmitted via Bacon

Good to know.

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)