Database Info

[Q] Problem booting into Recovery (ClockworkMod)

Please help this newbie out!... I recently rooted my Inspire 4G with attn1's hack kit. That went smooth without issue and I have tried a variety of custom ROMs thanks to this great community, but I have noticed a random issue with booting into ClockworkMod Recovery since... I installed Rom Manager and ClockworkMod Recovery 3.0.0.6 and the problem is that sometimes I can boot into recovery and sometimes not. It only seems to work is the first time I reboot immediately after flashing ClockworkMod, then subsequent reboots the phone just boots normally. (I hold volumn down and press power.) I have also tried installing Amon's Recovery (supersonic 2.3) manually using Fastboot - it seems to install without error but when I try holding the down volume button and hitting power - phone just boots normally. So it seems I am stuck with a ClockworkMod install that does not really work with reliability.... I am lost now trying to figure out why this is happening.
Can someone that has seen similar issues provide some tips/suggestions?
TIA
-Reebo

I had the same problem... quit using version 3.0.0.6 and go back to the earliest version, 2.5.1.3 through All ClockworkMod Recoveries. Worked for me.

reeboblue said:
Please help this newbie out!... I recently rooted my Inspire 4G with attn1's hack kit. That went smooth without issue and I have tried a variety of custom ROMs thanks to this great community, but I have noticed a random issue with booting into ClockworkMod Recovery since... I installed Rom Manager and ClockworkMod Recovery 3.0.0.6 and the problem is that sometimes I can boot into recovery and sometimes not. It only seems to work is the first time I reboot immediately after flashing ClockworkMod, then subsequent reboots the phone just boots normally. (I hold volumn down and press power.) I have also tried installing Amon's Recovery (supersonic 2.3) manually using Fastboot - it seems to install without error but when I try holding the down volume button and hitting power - phone just boots normally. So it seems I am stuck with a ClockworkMod install that does not really work with reliability.... I am lost now trying to figure out why this is happening.
Can someone that has seen similar issues provide some tips/suggestions?
TIA
-Reebo
Click to expand...
Click to collapse
You don't have 'fast boot' enabled in settings/application? If so it will not really shut off completely and when you power it up with VOL- it will not work.

i'm also having issues getting cwm to work outside the black screen. i have tried sense/ no sense roms and none have been able to bring up cwm outside the blank screen. i am also running 3.0.0.6 or whatever it is but that has not helped my issue

nyamoV2 said:
i'm also having issues getting cwm to work outside the black screen. i have tried sense/ no sense roms and none have been able to bring up cwm outside the blank screen. i am also running 3.0.0.6 or whatever it is but that has not helped my issue
Click to expand...
Click to collapse
did you use the Simple Root method to root your phone?
can you confirm if you have s-off and root?
Read post #2400 in the thread http://forum.xda-developers.com/showthread.php?t=961406&page=240

reeboblue said:
Please help this newbie out!... I recently rooted my Inspire 4G with attn1's hack kit. That went smooth without issue and I have tried a variety of custom ROMs thanks to this great community, but I have noticed a random issue with booting into ClockworkMod Recovery since... I installed Rom Manager and ClockworkMod Recovery 3.0.0.6 and the problem is that sometimes I can boot into recovery and sometimes not. It only seems to work is the first time I reboot immediately after flashing ClockworkMod, then subsequent reboots the phone just boots normally. (I hold volumn down and press power.) I have also tried installing Amon's Recovery (supersonic 2.3) manually using Fastboot - it seems to install without error but when I try holding the down volume button and hitting power - phone just boots normally. So it seems I am stuck with a ClockworkMod install that does not really work with reliability.... I am lost now trying to figure out why this is happening.
Can someone that has seen similar issues provide some tips/suggestions?
TIA
-Reebo
Click to expand...
Click to collapse
Sounds like fastboot is enabled. If you turn it off you will be able to boot into recovery.

i used the simple one click. yes i have root and s-off. but i'm stuck now. can not see cwm by manually booting into hboot. or through the app and clicking boot into recovery

[Q] Clockworkmod recovery not booting up
I have my phone rooted and ready to flash a custom ROM. I want to install android revolution 4g 4.0. I read that I need to ahve CWM version 3.0.0.6 to flash a 2.3 ROM. Anyways, when i select reboot into recovery in ROM Manager, my phone reboots and shows the HTC logo but then it fades to black screen and does nothing. If i press the power button, the phone reboots normally into the OS. Does anyone know how to fix this so i can install a custom ROM?

I have this exact same issue. Although i can load roms from choosing "Install from sd card" i cannot just boot into recovery and install it from there.
I just recently bought my inspire 4g a week ago.

Mine is 2 days old. Now i cant get it to boot up because it keeps trying to boot into CWM recovery but it cant. Its and endless loop.

Mine wont even load recovery. It reboots the phone but then just fades to a black screen. I cant get back into the OS

flrdast2 said:
Mine wont even load recovery. It reboots the phone but then just fades to a black screen. I cant get back into the OS
Click to expand...
Click to collapse
just press power button and it will reboot your phone.

still stuck doing that too. can get the phone to reboot. but stuck at htc screen or black cwm screen. also checked sd card and is corrupted. i was thinking if i could just flash a new rom over to fix boot issue. but i need some screens to blindly walk through to flash. cwm is 3.0.0.5 if that matters. thanks. on a side note. i think i have a new cm7rc2 build on a formated sd card to try and minimize the guess work on what to click

nyamoV2 said:
still stuck doing that too. can get the phone to reboot. but stuck at htc screen or black cwm screen. also checked sd card and is corrupted. i was thinking if i could just flash a new rom over to fix boot issue. but i need some screens to blindly walk through to flash. cwm is 3.0.0.5 if that matters. thanks. on a side note. i think i have a new cm7rc2 build on a formated sd card to try and minimize the guess work on what to click
Click to expand...
Click to collapse
do you know how to confirm if you have S-OFF and if your phone is rooted?

no but when in hboot it says s-off in the top of the screen

nyamoV2 said:
no but when in hboot it says s-off in the top of the screen
Click to expand...
Click to collapse
OK...I sent you a PM just follow those directions and you will be good.

habanosrus said:
OK...I sent you a PM just follow those directions and you will be good.
Click to expand...
Click to collapse
thanks for the help, but i can't get back into the os to make sure that debugging is checked.

nyamoV2 said:
thanks for the help, but i can't get back into the os to make sure that debugging is checked.
Click to expand...
Click to collapse
pull your battery and just turn you phone on without going into Fastboot menu.

downloading now. will give update in a few min
also does it matter that my phone will not go past the white htc screen?

nyamoV2 said:
downloading now. will give update in a few min
also does it matter that my phone will not go past the white htc screen?
Click to expand...
Click to collapse
Are you saying that your phone shows the white HTC screen then fades to black?
if so, no, it doesn't matter...just press the power button to reboot your phone.

Is my N8013 completely dead?

I have a sinking feeling that the same failure that killed my first tablet, an HP Touchpad (NAND Lock/Failure) has killed my Galaxy Note N8013. All was fine until a few days ago. I was running TWRP 2..8.0.1. and alternating between CM12.1 and BliisRom with no problems. I connected it to charge overnight and went to bed. The next morning it was stuck on the CM12.1 boot animation. It would never boot, just run the animation until the battery drained. I can put it in download mode and it appears to successfully flash stock/custom roms/recoveries (I've tried them all) but as soon as it reboots it goes back to the CM boot animation. If I try to put in recovery (power + Volume up) the TWRP splash screen appears but quickly disappears and is replaced by CM boot animation. Since I can't get into recovery is there another way to do a factory reset/wipe? Any ideas or suggestions?

DaElderGeek said:
I have a sinking feeling that the same failure that killed my first tablet, an HP Touchpad (NAND Lock/Failure) has killed my Galaxy Note N8013. All was fine until a few days ago. I was running TWRP 2..8.0.1. and alternating between CM12.1 and BliisRom with no problems. I connected it to charge overnight and went to bed. The next morning it was stuck on the CM12.1 boot animation. It would never boot, just run the animation until the battery drained. I can put it in download mode and it appears to successfully flash stock/custom roms/recoveries (I've tried them all) but as soon as it reboots it goes back to the CM boot animation. If I try to put in recovery (power + Volume up) the TWRP splash screen appears but quickly disappears and is replaced by CM boot animation. Since I can't get into recovery is there another way to do a factory reset/wipe? Any ideas or suggestions?
Click to expand...
Click to collapse
did you tryed with odin or abd, try to flash newest twrp from the site and flash it via odin3.

Pupskartoffel said:
did you tryed with odin or abd, try to flash newest twrp from the site and flash it via odin3.
Click to expand...
Click to collapse
Only with Odin. My understanding is that ADB isn't available if you can't boot into recovery. I haven't found anyway to make it boot into recovery.

Reflash/recovery
Have you tryed to flash twrp 2.8.7.0 or cwm or, try to reflash the boot.img.
Sorry for bad english i'm only 12

Phone is not power up?

I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:

sanrajbhar said:
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
Click to expand...
Click to collapse
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).

xMotoDA said:
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
Click to expand...
Click to collapse
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .

sanrajbhar said:
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
Click to expand...
Click to collapse
I have a similar issue, as my phone also cannot turn on and I have TWRP recovery.
I had rooted my phone with SuperSU and unlocked the bootloader via motorola's tool. But then due to SafetyNet, apps such as Snapchat wouldn't work (cant log in), and I couldn't download Netflix (totally a huge issue).
So I decided to try switching to Magisk instead, as I heard that uses systemless root that doesnt trip Safety Net. While uninstalling SuperSU (using the built in feature for full removal), I was able to uninstall SuperSU and unroot my phone, but was not able to restore the stock boot image in the process. It was at this point I made a NANdroid backup in case I stuffed anything up.
Because of this, I was unable to flash Magisk via the TWRP recovery, so I downloaded a previous version of the firmware from January to flash back to from here. After flashing this and also wiping the user data, my phone booted up fine and worked, and appeared to be in normal condition.
However, then I elected to download and install the firmware update. This all went well, and was installing, until just at the end of the process, when the phone turned off. It had over 60% battery at the time.
At this point in time I'm still unable to get it to boot up, even into recovery or fastboot mode, so I cant really do anything, or restore my NANdroid backup.
If I plug it into my laptop, and hold the power + volume button down for a period of time, I can hear the USB connected tone (Windows 10), which then switches to a disconnected tone and a "USB device malfunctioned" error message pops up.
I tried leaving it unplugged all of last night just in case it was stuck in a boot loop or something so the screen couldn't display anything, in order to flatten the battery, but obviously I couldn't tell any difference. I'm currently now trying to have it plugged into power for an extended period of time just in case it is actually just flat. The current condition is just a black screen as if there was no power at all, with no lights or anything, regardless of a charger being connected, with the buttons not doing anything (I've attempted holding down the power and volume down buttons together for at least 2 minutes to no effect)
Any help would be greatly appreciated.
My specs: Moto G Turbo (2015), model XT1557, running Android 6.0.1. Can't remember exactly, but it previously had the latest firmware available before I tried flashing the January firmware.

TWRP keeps crashing

I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.

Yippee38 said:
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Click to expand...
Click to collapse
Do you have a TWRP backup from when your phone worked on an external drive?

Can you access fastboot? Just use the fastboot ROM files to reflash the OS. Or if that doesn't work try the unbrick tool.

Yeah. I can use fastboot. However, I wasn't able to get to ROM to flash. I'm not sure if I'm using the correct parameters in the command. I googled, but all I came up with was flashing custom ROMs. Where can I find the unbrick tool?
NM. Found the unbrick tool. I may try it. I'll let you know how it works.

Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.

Yippee38 said:
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Click to expand...
Click to collapse
Glad you got it solved

Huawei Watch 2 Pro (Shawshark) stuck in horrible bootloop

My relatives have gotten this watch gifted to them a while back but it was in chinese so to get it to English I had to unlock bootloader and flash the room. But while doing so I by mistake flashed twrp instead of booting into it on the Recovery Partition right after unlocking bootloader and after rebooting, it was stuck in a horrible bootloop. Why is it horrible?
So the problem is, it keeps booting into twrp, fails to mount data cache and everything, shuts down and reboots again, shows a warning that it can't detect an operating system and continues to boot into the same twrp recovery and so on. When I try to boot into bootloader, it says to go to g.co/ABH and read instructions to proceed, but after holding down the button to continue to boot, it goes back to the same bootloop.
I cannot boot it into bootloader or get it into fastboot, I can't do anything in twrp and I can't boot into os (cause of course, there is none). Does anyone know how I can fix this? I've been struggling for 4 hours with this today. I'm really scared that I've completely bricked it and can't restore it .
I can see it in adb devices while it's in twrp and twrp is freaking out then shutting down, but I can't even side load a rom to even install something I can boot into.
Link me a thread if there is one where this problem gets fixed or help me please. Thank you!