Database Info

[Q] Vol. down + power dosen't enter the bootloader

After I updated my (unrooeted/locked) Nexus S (9023) to 4.0.3 I wanted to try the 4.0.4 upgrade. After the 4.0.3 the recovery mode lost the backlight, so I figured the it was a good time to root.
I tried this one-click script to unlock. It worked and I installed CWMR and flashed the 4.0.4 upgrade. After a reboot the phone had ICS 4.0.4 and got root.
But not all is working. I lost the ability to get into the bootloader by pressing 'vol down.' & 'power'. The phone just starts normally.
The only way I can get into the bootloader, is to "reboot to bootloader" from a command line. If I choose recovery, I get a picture of an android at its back with a red ! (2105.dk/temp/img_1161.jpg). After two minutes it automatically reboots. What has gone wrong? What does it mean? And how can I fix it?
I'm new at this, so i'm out of ideas

try Vol up + power

Ahhh... now i'm feeling a bit stupid
Okay, i'm able to get into the bootloader, but the problem with the recovery still remains. (what does the picture mean? - 2105.dk/temp/img_1161.jpg)
I've tried both CWRM and TWRP. They seems to flash with no errors, but i still can not get them started from the bootloader (fastboot mode?).

Not sure if it's what you are looking for since I can't see the picture you are talking about but I think it's the recovery "security" screen. When you are there press power first and maintain it to press vol up, you should now be into the recovery...
Also remember stock rom has a script that overwrites any custom recovery with stock recovery each time the rom loads.

Yes, pressing [power] + [vol. up] at the recovery "security/error" screen, starts up a recovery.
I also didn't knew that the stock ROM overwrites the recovery. I never seen it mentioned any where else.
Thanks for the hints.

Okay, after learning how the stock OS trying to reinstall stock recovery, I managed to rename /etc/install-recovery.sh to *.bak
Now the stock recovery stays away, and CWM recovery stays on permanent.
Also, the error screen doesn't show up any more. (never found out what it means)

HELP! Is my phone completely bricked ?

Ok so yesterday I installed Viper One S 3.1.2 on my phone ( HTC One S - S4 of course ), first it worked perfectly and flawless then i rebooted my phone into recovery to install the wifi fix and camera sense 5 mod v0.2. After that, i reboot my phone again, and it did had the logo of htc and viper team, but when it booted completely, it only has the status bar and a black screen and then it rebooted itself after 15-20s and then stucked into a bootloop. Sometimes it boots as normal as it did before i installed those mods, i tried to hold the power button to choose the "boot in to bootloader" option but it didnt even appeared the power option So right now i can't not boot my phone into bootloader ( even by holding volume down and power button ) and recovery, It reboots itself so fast that my computer can't recognize it to run the RUU Is my phone completely bricked ?
Recovery TWRP 2.5 ?
Hboot 1.14
Radio < 1.20
I don't remember those information much so i'm sorry :crying:

Hewvarhoo said:
Ok so yesterday I installed Viper One S 3.1.2 on my phone ( HTC One S - S4 of course ), first it worked perfectly and flawless then i rebooted my phone into recovery to install the wifi fix and camera sense 5 mod v0.2. After that, i reboot my phone again, and it did had the logo of htc and viper team, but when it booted completely, it only has the status bar and a black screen and then it rebooted itself after 15-20s and then stucked into a bootloop. Sometimes it boots as normal as it did before i installed those mods, i tried to hold the power button to choose the "boot in to bootloader" option but it didnt even appeared the power option So right now i can't not boot my phone into bootloader ( even by holding volume down and power button ) and recovery, It reboots itself so fast that my computer can't recognize it to run the RUU Is my phone completely bricked ?
Recovery TWRP 2.5 ?
Hboot 1.14
Radio < 1.20
I don't remember those information much so i'm sorry :crying:
Click to expand...
Click to collapse
Is your phone "S-OFF"?
You need HBoot 2.16 for radio 1.20. Otherwise HBoot 2.15 is recommended.
Turn your phone off by pressing Power for 10 seconds. Then press "Vol down and power" to enter bootloader.
BTW how about first READ whats required before installing a rom...

First and biggest mistake was to flash a mod that was not certified to work with Viper. In all the Viper threads (the old 2.x and the new 3.x one), it is stated NOT to flash any mod cause it might break the ROM. There are files replaced and those in Viper are tweaked by the Viper Dev team to work with Venom HUB and the themes and tweaks there. Mods usually replace framework-res.apk and if this happens you could have a non working ROM if the new framework-res file is not compatible with the rest of the ROM.
Follow the steps indicated by LS.xD to enter bootloader again. There's no reason for which you could not boot to bootloader again. Disconnect any power from phone, keep the power button hold for about 12-15 secs until you're sure phone is powered off (eventually you'll notice a faint flash on screen when it's turning off). Then hold vol-down and keep it presed while you press and hold power button for 2-3 secs. Continue to keep pressed the vol-down until the bootloader screen appears. Then go to recovery and reflash the ROM. Since you're on hboot 1.14, if you're not S-Off (you didn't mentioned anything about this), you should flash the kernel in fastboot. If you're S-Off you won't need this. Basically you should follow again the exact steps you followed first time when you flashed the ROM
And don't flash any mods again

Rapier said:
First and biggest mistake was to flash a mod that was not certified to work with Viper. In all the Viper threads (the old 2.x and the new 3.x one), it is stated NOT to flash any mod cause it might break the ROM. There are files replaced and those in Viper are tweaked by the Viper Dev team to work with Venom HUB and the themes and tweaks there. Mods usually replace framework-res.apk and if this happens you could have a non working ROM if the new framework-res file is not compatible with the rest of the ROM.
Follow the steps indicated by LS.xD to enter bootloader again. There's no reason for which you could not boot to bootloader again. Disconnect any power from phone, keep the power button hold for about 12-15 secs until you're sure phone is powered off (eventually you'll notice a faint flash on screen when it's turning off). Then hold vol-down and keep it presed while you press and hold power button for 2-3 secs. Continue to keep pressed the vol-down until the bootloader screen appears. Then go to recovery and reflash the ROM. Since you're on hboot 1.14, if you're not S-Off (you didn't mentioned anything about this), you should flash the kernel in fastboot. If you're S-Off you won't need this. Basically you should follow again the exact steps you followed first time when you flashed the ROM
And don't flash any mods again
Click to expand...
Click to collapse
Um thanks for your help guys, i wasnt aware of the requirements much, but the problem is now i cant get my phone into bootloader by holding power button and volume down :crying:

Tried Power off manually by pressing "power" for 10+ seconds? When phone turns off immediately release power and press "vol down + power"
Sent from my loved HTC One S using (most time buggy) Tapatalk

[Q] Boot looping

Please treat me as a total noob, my problem is this i installed the stock RUU Vodafone rom on my HTC One and everything went fine until i had a couple of phone updates ota first 2 installed and phone rebooted no problem on the 3rd system update the phone rebooted but this time on a boot loop where it would get as far as the HTC splash screen the continually reboot itself.
I have gone into recovery – hold power and Vol Down to go into recovery but when i do press the power button to go into recovery it just goes back to the boot loop i did have Clockworkmod installed on the phone but this seems to have stopped working.
I have tried to use fastboot and ADB but because my phone is looping it will not say on long enough to connect to the PC and run a command to wipe the cache.
My question mainly is there anything i can do to save my phone or should i just bin it.
Thanks

You're in the wrong forum, this is the HTC One XL forum.
Sent from my Evita

can boot recovery from fastboot but can't flash!

Hey guys,
My friend is having some issues with getting twrp on his new oneplus one:
the bootloader was succesfully unlocked and we tried flashing the twrp recovery on it (both the latest version and the previous version) fastboot said that it was succesfull but when we tried to boot the recovery by holding power + volume down the device hung on a black screen and needed to be restarted, and this happens everytime! However if we do fastboot boot openrecovery....img it takes a while but the recovery boots just fine!
what's going on here? can anyone tell me why it won't boot a flashed recovery?

I have the same issue as you, and yet to find an solution. Try using Philz Touch or CWM instead, both worked for me.

noahvt said:
Hey guys,
My friend is having some issues with getting twrp on his new oneplus one:
the bootloader was succesfully unlocked and we tried flashing the twrp recovery on it (both the latest version and the previous version) fastboot said that it was succesfull but when we tried to boot the recovery by holding power + volume down the device hung on a black screen and needed to be restarted, and this happens everytime! However if we do fastboot boot openrecovery....img it takes a while but the recovery boots just fine!
what's going on here? can anyone tell me why it won't boot a flashed recovery?
Click to expand...
Click to collapse
Many people don't know the correct procedure to boot into recovery using the button combination, what you need to do is first hold volume down, then hold power as well, the phone will vibrate and you'll see the OnePlus splash screen, after about a second you can let go of the power button and keep holding volume down until it boots into recovery. If you continue to good the power button after seeing the splash screen the device becomes confused and thinks you're trying a hard reset.
Transmitted via Bacon

[Q] Can't boot into recovery?

So, I got my new OnePlus One today and I tried to get CM12 onto it. I was following the [GUIDE] How to Install CM12 on the OnePlus One- Android Lollipop/5.0 on the OPO forums, and everything went well until I tried to get the TWRP on there. I flashed the recovery and rebooted the phone. I turned it off and then tried to boot it into recovery but it doesn't, it just hangs at the OPO logo until I hard-restart it.
I've tried factory resetting it and doing
fastboot oem unlock
but nothing happened. The factory reset pretty much just reset the phone. I think I might've messed up the kernel. How do I fix it?
EDIT 1: I've tried reflashing twrp recoveries and nothing. When I hold power+volume down, it powers on, shows the one plus logo, then reboots and just goes to the lockscreen.
UPDATE 1: I managed to manually flash all the CM12 files and use lollipop. I haven't tried the recovery yet but I'll keep you guys updated (if any of you even care).
UPDATE 2: Apparently flashing CM12 made the recovery work. Everything works as it should and the OTA to the most recent CM12 worked perfectly.

You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.

Heisenberg said:
You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
I was curios and enabled advanced reboot to try and boot into recovery and it worked (after I had flashed CM12). Everything's working now.

SDCore said:
UPDATE 1: I managed to manually flash all the CM12 files and use lollipop. I haven't tried the recovery yet but I'll keep you guys updated (if any of you even care).
Click to expand...
Click to collapse
How did you manually flash CM12? I think I'm having the same trouble you were having. I used the oneplus toolbox from the forum to unlock the bootloader, then flash the TWRP, but no luck in getting into recovery mode. It just boot loops with the oneplus logo until I release the volume down button at which point it then boots to the lock screen.

Heisenberg said:
You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
@Heisenberg I'm also having trouble getting into recovery. I've tried the different button combos (power + vol down; power + vol down and release power) as well as the advance reboot options to get into recovery, but they all fail. I get the 1+ logo and after I let go of the volume down button the screen goes black and boots again to the 1+ screen and then to the lockscreen. It's almost like it doesn't recognize the recovery. I tried putting the stock recovery back on using the image in the OnePlus One toolkit folder, but that one doesn't work either. In addition to unchecking the "CM Recovery Update", are there any other settings that could be causing problems?
For background info, I initially used the toolkit interface to unlock the bootloader and then flash the recovery. The bootloader unlocked with no issue...it wiped my device and I was in sync with the "How to root" video posted by alex.inthi. I got sidetracked after the (seemingly) successful flash of TWRP onto the phone I kept getting booted into the Cyanogen recovery. I realized out that I needed to uncheck the setting to keep it from overwriting TWRP and after that was not able to boot into recovery. After finding your beginners guide (thanks, by the way, very well written) I tried using fastboot from the command line as you show, but still no luck.
Thanks in advance for any help...

bellino13 said:
I used the oneplus toolbox from the forum to unlock the bootloader, then flash the TWRP, but no luck in getting into recovery mode. It just boot loops with the oneplus logo until I release the volume down button at which point it then boots to the lock screen.
Click to expand...
Click to collapse
bellino13 said:
@Heisenberg I'm also having trouble getting into recovery. I've tried the different button combos (power + vol down; power + vol down and release power) as well as the advance reboot options to get into recovery, but they all fail. I get the 1+ logo and after I let go of the volume down button the screen goes black and boots again to the 1+ screen and then to the lockscreen. It's almost like it doesn't recognize the recovery. I tried putting the stock recovery back on using the image in the OnePlus One toolkit folder, but that one doesn't work either. In addition to unchecking the "CM Recovery Update", are there any other settings that could be causing problems?
For background info, I initially used the toolkit interface to unlock the bootloader and then flash the recovery. The bootloader unlocked with no issue...it wiped my device and I was in sync with the "How to root" video posted by alex.inthi. I got sidetracked after the (seemingly) successful flash of TWRP onto the phone I kept getting booted into the Cyanogen recovery. I realized out that I needed to uncheck the setting to keep it from overwriting TWRP and after that was not able to boot into recovery. After finding your beginners guide (thanks, by the way, very well written) I tried using fastboot from the command line as you show, but still no luck.
Click to expand...
Click to collapse
Okay, I must have been having a special kind of moment - I've got TWRP 2.8.7.0 running on my handset now. I may have been holding the volume down button too long, or it may be that I was using an older version of TWRP, but I'm going to go with the former. I've also been able to successfully flash and boot into Philz 6.59.2

Having the same problem
I am having the exact same problem and cannot seem to find a solution. Recovery screen just doesn't appear, but goes to lockscreen.
Tried erasing, flashing both twrp, philz etc., but nothing works. The phone doesn't recognize the recovery status. Advanced booting does the same.
Update CM-recovery is checked off, phone is unlocked. I've followed every step of the big guide down to every detail.
Is manually flashing the 12.1 ROM the only way and in that case: is it hard for a relative newcomer?