Unlocking bootloader on S-off - HTC Sensation

Hey guys,
Been using my htc sensation for years (rooted, s-off) but bootloader is still locked and I'd need to unlock it.
I'm CM 13 Ivanich's custom rom.
I tried using official HTCDev procedure and I do get to the last last step where I should simply select by pressing volume button up "YES" and confirm by pressing power button to proceed with unlocking the bootloader: the issue is that I select Yes by pressing volume up but when I press power button to confirm that option nothing happens (like it doesn't get the power button confirmation...). However, I press volume down selecting NO option and press the power button for confirmation (thus "aborting" the unlocking procedure and making the phone rebooting), in this case it does get confirmation and phone reboots...
Any ideas how this can be solved?
(HBOOT 1.29
Kernel 3.4.113)

murchz said:
Hey guys,
Been using my htc sensation for years (rooted, s-off) but bootloader is still locked and I'd need to unlock it.
I'm CM 13 Ivanich's custom rom.
I tried using official HTCDev procedure and I do get to the last last step where I should simply select by pressing volume button up "YES" and confirm by pressing power button to proceed with unlocking the bootloader: the issue is that I select Yes by pressing volume up but when I press power button to confirm that option nothing happens (like it doesn't get the power button confirmation...). However, I press volume down selecting NO option and press the power button for confirmation (thus "aborting" the unlocking procedure and making the phone rebooting), in this case it does get confirmation and phone reboots...
Any ideas how this can be solved?
(HBOOT 1.29
Kernel 3.4.113)
Click to expand...
Click to collapse
you don't need htcdev since you are on S-OFF
use 3.33 universal firmware from this thread
https://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions carefully
and before flashing check md5 sums( important)

rzr86 said:
you don't need htcdev since you are on S-OFF
use 3.33 universal firmware from this thread
https://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions carefully
and before flashing check md5 sums( important)
Click to expand...
Click to collapse
Thanks! It worked!

Related

[Solved] Damaged bootloader. please help!

Try to unlock. Lots of things went wrong.
First the usb driver installed via installation of HTC Sync.
Open revolutionary and work on it, it stopped at "waiting for fastload".
So that I flushed a file - PG58IMG.zip, according to the noobproof post "method 2" here http://forum.xda-developers.com/showthread.php?t=1232107
It went wrong because I did not delete the file before rebooting. message: file error CRC.
While I use revolutionary to get into the bootloader again, I see this:
PYRAMID PVT SHIP S-OFF RL
Hboot - 1.17.0011
RADIO-10.11.9007.27_M3
eMMC-boot
Jun 2 2011,22:31:39
Then I can not use any key combination to enter bootloader.
If I use the revolutionary to get the the bootloader screen, it does not respond to the vol. keys and power key. Have to pull off the battery.
The phone can still boot normally.
Whay should I do to get the clockwork recovery flushed in?
Appreciated!
soma900 said:
Try to unlock. Lots of things went wrong.
First the usb driver installed via installation of HTC Sync.
Open revolutionary and work on it, it stopped at "waiting for fastload".
So that I flushed a file - PG58IMG.zip, according to the noobproof post "method 2" here http://forum.xda-developers.com/showthread.php?t=1232107
It went wrong because I did not delete the file before rebooting. message: file error CRC.
While I use revolutionary to get into the bootloader again, I see this:
PYRAMID PVT SHIP S-OFF RL
Hboot - 1.17.0011
RADIO-10.11.9007.27_M3
eMMC-boot
Jun 2 2011,22:31:39
Then I can not use any key combination to enter bootloader.
If I use the revolutionary to get the the bootloader screen, it does not respond to the vol. keys and power key. Have to pull off the battery.
The phone can still boot normally.
Whay should I do to get the clockwork recovery flushed in?
Appreciated!
Click to expand...
Click to collapse
First thing first, run RUU, then try revolutionary again, but READ THEIR HOW TO's!!!!! Again, read their HOW TO's!!!!!
If you have no RUU available you'll have to mess about with ADB, which is not that easy for a newbee.
Google on how to install ADB and stuff, once it's running and working properly, you have to type
adb reboot bootloader
fastboot flash recovery recovery_name.img
fastboot reboot-bootloader
But if your buttons still don't work, you won't be able to get into recovery.
Anyway, there are a lot of things you can do, i can sit here all night trying to write up different scenarios, but best thing for you to do is to start from scratch (RUU->REVO etc) AND READ HOW TO and don't rush when you do it.
P.S. Have you tried booting into bootloader by holding -vol button while pressing power button (after battery pull, as if you just shut it down, you might still have fast boot enabled)? Should really start from that.
tinky1 said:
P.S. Have you tried booting into bootloader by holding -vol button while pressing power button (after battery pull, as if you just shut it down, you might still have fast boot enabled)? Should really start from that.
Click to expand...
Click to collapse
Already tried many times. Either vol-down + power, or vol-up + power, the phone will start to sense. I can get into bootloader screen via revolutionary, but it does respond to menu change by holding the vol-up, or down and run by power button.
Unlocking the first time. Also new to android. used to be stick with win for years. Thanks Tinky1! I will try revolutionary again. Please stay with me.
New developemnt.
Try the revolutionary again. This time I put the cwm rocovery tools 5010 as a zip on the card beforehand. This time the Rev screen still shows "Communication with the phone interrupted unexpectedlly ......". But on the phone it now shows "Hboot - 1.17.1111". Then I unplug the USB, boot in rocovery. This time it responsed. Wait untill it says update completed, then restart phone into sense home screen.
I guess this time it is alright.
Yes. Now I can goto blue CWM recovery menu. The next figure out which rom to flush my phone. Thanks, Tinky1!
soma900 said:
Yes. Now I can goto blue CWM recovery menu. The next figure out which rom to flush my phone. Thanks, Tinky1!
Click to expand...
Click to collapse
You should change title since u found solution
Sent by my feau gee

Phone won't power on -- HELP

HTC Sensation -- Completed last step to get s-on for warranty purposes. Phone will not power on, have tried everything. Battery turns on a different Sensation. What can I do?!
Sounds like you are the proud owner of a brand new ... brick!
But seriously will it do anything? Did you try booting into the bootloader like step 10 says?
10. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
11. Run RUU_Pyramid_***.exe to reflash stock rom. (the one u just downloaded in step 1) and then reboot. It should work now
Click to expand...
Click to collapse

relocked bootloader

Cannot unlock bootloader anymore after RUU update , tried 10 times without succes.
thx in advace for the help
What's the steps are you doing in trying to lock the bootloader?
Information like that help to see what's right or wrong.
What do you get when typing in command
Code:
fastboot devices
does the PC see your device?
This is a second thread today with same issue refer to the other for solution!
CLUE:Cannot Unlock Bootloader
yes i use one AIO toolkit for the first 8 times it appear the choice YES or NO if you want to unlock..but i haven't uncked the fastboot in the power setting. Now i'm trying again but seems that the unlocking choice doesn't appear , i'm stuck on the bootloader screen.
mastercut said:
yes i use one AIO toolkit for the first 8 times it appear the choice YES or NO if you want to unlock..but i haven't uncked the fastboot in the power setting. Now i'm trying again but seems that the unlocking choice doesn't appear , i'm stuck on the bootloader screen.
Click to expand...
Click to collapse
recheck your typed commands, probably a typo error! follow the steps properly!
Ok to re unlock your bootloader after flashing the token let the phone boot up then enable usb debugging and disable fastboot in the power menu
Then completely power off the phone wait a minute then reboot once you are back on the home screen push power and restart holding volume down when you reboot to bootloader it should now say unlocked again
Sent from my HTC One S using xda premium
Code:
:cd %:h
adb kill-server
adb reboot bootloader
fastboot flash unlocktoken Unlock_code.bin
pause
exit
I had the same issue. I took all the steps again from start. Meaning I requested the the token ID (which differs from the first for me) and this token ID registered this again at htcdev.com. It worked the first time with the new unlock.bin.
Hope this helps.
I had a similar problem, the author of the other thread, I havent worked out the exact problem yet but I think the key here is to not rush the steps and also disconnect the usb cable one you are on the YES/NO choice screen (before you select and phone reboots).
craig1965 said:
Ok to re unlock your bootloader after flashing the token let the phone boot up then enable usb debugging and disable fastboot in the power menu
Then completely power off the phone wait a minute then reboot once you are back on the home screen push power and restart holding volume down when you reboot to bootloader it should now say unlocked again
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
SOLVED thx a lot

[Q] Phone is bricked after install MaximusHD 10.0.0

Hi,
I just got the phone, and I managed to unlock, root it using the guide in here http://forum.xda-developers.com/showthread.php?t=1583427
I then install MaximusHD 10.0.0
I went thru the Aroma, and I need to go to fastboot for s-off. But the screen is off now. When pressing the power button 3 virtual buttons are blinking, so I guess it's not really bricked.
How could I get into fastboot mode?
Thanks
You should have s-off before installing maximus. Anyway press and hold power button about 10-15 seconds to force close the phone, then press again power button(but don't hold this time) while holding down the "volum down" button. That will let you enter the bootloader and you can access fastboot mod from there. By the way if you see that you have hboot 2.16 in your bootloader you can just flash the boot.img from maximus zip and start using your phone
Sent from my HTC One S

My Nexus 5 is bricked or dead ?

In short:
Scenario:
Bootloop or logo Google freeze
bootloader is unlocked
I tried to:
Flash original stock with normal method and with Nexus Root Toolkit (menĂ¹ bootloop).
I can't access recovery from bootloader menu (after click Recovery it bootloop)
I can access recovery by adb commands
I can't power off with power button (it reboot), I must go to bootloader menu and select power off.
What can I do?
thanks
derekz2 said:
In short:
Scenario:
Bootloop or logo Google freeze
bootloader is unlocked
I tried to:
Flash original stock with normal method and with Nexus Root Toolkit (menĂ¹ bootloop).
I can't access recovery from bootloader menu (after click Recovery it bootloop)
I can access recovery by adb commands
I can't power off with power button (it reboot), I must go to bootloader menu and select power off.
What can I do?
thanks
Click to expand...
Click to collapse
Try flash a custom recovery image like twrp with fastboot (connect phone to pc, go into bootloader)
How to do that:
http://en.miui.com/thread-58623-1-1.html
(Skip step 6 and 7)
Hope that helped
I had this problem:
https://www.youtube.com/watch?v=doPuXkQTGbc
its the power button.
try clicking it a lot of times while booting or smash it (the power button facing down) on a table a few times. This fixes it for most of us
Power button is ok.
I installed twrp with Nexus root toolkit, do you think with this method can change something?
are there advanced controls I can use on the Nexus toolkit?
.
The problem was the defective battery.
.

Categories

Resources