Database Users

Booting into clockwork recovery

I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!

Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?

Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.

kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?

To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed

Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem

Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!

enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!

No recovery mode/Phone with Explanation mark

Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks

Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™

You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.

ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...

So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good

Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.

copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.

copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?

brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App

ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different

brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.

chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove

Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App

I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.

danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian

I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App

[SOLVED] Bricked?

SOLVED I have done something very very stupid. I tried flashing a galaxy nexus kernel to my kindle fire. I've been flashing roms/kernals all day to my G-nex and for some reason i was thinking i was on my gnex and i just flashed it in rom manager on my kindle fire (DUMB). Now my KF will only boot into TWRP. I have adb working on my computer if someone could just help me figure this whole shinanigans out.

I was on cm7 when i flashed it. then i tried flashing cm9. it looks like it flashed it right but it wont boot up. it just goes straight to twrp.

bb-gun said:
I was on cm7 when i flashed it. then i tried flashing cm9. it looks like it flashed it right but it wont boot up. it just goes straight to twrp.
Click to expand...
Click to collapse
Did you select reboot into recovery at any point? From reading other threads, it seems like people get stuck in TWRP due to bootmode settings after choosing that option.
*EDIT* I'm guessing if you used ROM Manager the app defaulted to booting into recovery in order to install the kernel.

ghost_og said:
Did you select reboot into recovery at any point? From reading other threads, it seems like people get stuck in TWRP due to bootmode settings after choosing that option.
*EDIT* I'm guessing if you used ROM Manager the app defaulted to booting into recovery in order to install the kernel.
Click to expand...
Click to collapse
Yeah. I even knew i wasn't supposed to do that. I was half awake when i did it. Is there any way to recover it?

bb-gun said:
Yeah. I even knew i wasn't supposed to do that. I was half awake when i did it. Is there any way to recover it?
Click to expand...
Click to collapse
Pretty sure. Search the dev forum for how to switch boot modes. I think the Kindle Fire Utility thread would be a good place to start.

if you allready have twrp it should be no problem:
http://forum.xda-developers.com/showthread.php?p=20714780#post20714780
do from the status where you are - means you don't need the twrp installation

Thank you soooooooo much. It worked. It took forever to boot up but it finally did.

glad to help ...

Should change the subject of the topic (edit first post) to [Solved]

They really need to take that reboot to recovery option out lol.

bb-gun said:
Thank you soooooooo much. It worked. It took forever to boot up but it finally did.
Click to expand...
Click to collapse
How much is forever? Mine is 10+ minutes.

[Q] Razr M Root and RSD fail constantly.

Hey all, im new to the forum. I have been a spectator for a while and decided to see if you could help me. I have a Razr M (Verizon) and i used to have it rooted and running eclipse. I wanted to switch roms to PACman but it wouldn't stop failing. So after much anger i decided to reflash firmwear to stock 4.1.2 and it worked. I tried to root again using motochopper but it fails every time. I have tried to reflash with RSDlite but it also fails every time on step 1/19. Nothing i try is working and im loosing faith haha. Ive looked threw a lot of the other boards but all solutions never work for me. The goal is to have a Razr M running PACman but for right now its still on the ugly stock rom Any help or insight at all is greatly appreciated.

Willybrown said:
Hey all, im new to the forum. I have been a spectator for a while and decided to see if you could help me. I have a Razr M (Verizon) and i used to have it rooted and running eclipse. I wanted to switch roms to PACman but it wouldn't stop failing. So after much anger i decided to reflash firmwear to stock 4.1.2 and it worked. I tried to root again using motochopper but it fails every time. I have tried to reflash with RSDlite but it also fails every time on step 1/19. Nothing i try is working and im loosing faith haha. Ive looked threw a lot of the other boards but all solutions never work for me. The goal is to have a Razr M running PACman but for right now its still on the ugly stock rom Any help or insight at all is greatly appreciated.
Click to expand...
Click to collapse
what recovery are you running? if TWRP (any version other than 2.4), then you should be able to place the ROM on the external SD card and flash it (after wiping system/factory reset) - and then install the GApps.

jco23 said:
what recovery are you running? if TWRP (any version other than 2.4), then you should be able to place the ROM on the external SD card and flash it (after wiping system/factory reset) - and then install the GApps.
Click to expand...
Click to collapse
I was running safestrap but now im not running anything, the device has been Firmwear flashed and factory reset. Safestrap would also fail, made it basically useless. It wouldn't even correctly activate the stock rom slot.

Willybrown said:
I was running safestrap but now im not running anything, the device has been Firmwear flashed and factory reset. Safestrap would also fail, made it basically useless. It wouldn't even correctly activate the stock rom slot.
Click to expand...
Click to collapse
UPDATE: i got to step 6/19 in RSD, Here is a screenshop of it, i hope it helps.

Willybrown said:
UPDATE: i got to step 6/19 in RSD, Here is a screenshop of it, i hope it helps.
Click to expand...
Click to collapse
Post about phone info. Unlock status. Hold all 3 keys til black then let off pwr pause 2 sec. Let go vols. V down to fast boot v up.

Willybrown said:
I was running safestrap but now im not running anything, the device has been Firmwear flashed and factory reset. Safestrap would also fail, made it basically useless. It wouldn't even correctly activate the stock rom slot.
Click to expand...
Click to collapse
PAC and all other 4.2.2 ROMs can only be installed via TWRP/CWN, not SS.

aviwdoowks said:
Post about phone info. Unlock status. Hold all 3 keys til black then let off pwr pause 2 sec. Let go vols. V down to fast boot v up.
Click to expand...
Click to collapse
Not combination of key presses has any result, the only thing i get is fastboot, and its a razr m with an unlocked bootloader...

Willybrown said:
Not combination of key presses has any result, the only thing i get is fastboot, and its a razr m with an unlocked bootloader...
Click to expand...
Click to collapse
I DO not know. Bad XML Redownload?

aviwdoowks said:
I DO not know. Bad XML Redownload?
Click to expand...
Click to collapse
No go, ive tried redownloading everything and no luck. Im also getting errors of fastboot is not a recognized command from RSD. Ive tried matts tool with same result. The phone rejects everything i try to do to it.

Willybrown said:
No go, ive tried redownloading everything and no luck. Im also getting errors of fastboot is not a recognized command from RSD. Ive tried matts tool with same result. The phone rejects everything i try to do to it.
Click to expand...
Click to collapse
How much battery do you have? Also, which version of RSD are you using? I can barely read the version in your screenshot, it looks like 6.1.5, but I can't tell.

just got the phone to boot using SDK. I am using RSD 6.1.5 im going to try rooting and installing PACman. What recovery should i use?

SDK worked! the phone is now operating on the stock rom. problem is motochopper (by itself or in Matt's utility) fails every time. here is a screenshot. anyone have any ideas because i am lost.

Softish Brick Recovery i9505 int

Hi,
My i9505 Intl (Australian Telstra LTE) SGS4 has been rooted for a year at least now, and recently (a few months) had TWRP recovery and CM13 installed and everything was going great. I loved CM!
Anyway I had done a few nightly patches of CM and all seemed good and then a week ago I installed the most recent nightly (possibly this one cm-13.0-20160819-NIGHTLY-jfltexx-recovery.img ). Well the subsequent reboot put the phone into a boot loop. So I thought no problem just boot to recovery and install my recent Nandroid back up. So did that but in my haste didn't clear cache or data. The nandroid reinstall seemed to go ok but a subsequent boot hung at the CM logo (I think it was a while ago now) and I couldn't boot to recovery, just hung with the blue text.
So I fired up Odin and booted to download and reflashed with TWRP. Boot to recovery still didn't work however I could still boot to download.
Tried different USB ports, different versions of Odin, re installed drivers to no avail. Also tried CWM, TWRP and Philz recovery and once I did get it to boot to recovery with Philz. THIS TIME cleared cache and data and loaded a good copy of CM that I had on my SD card. Again stuck in boot. Couldn't get back to recovery.
Tried loading the orginal samsung firmware and they I was stuck with a Samsung logo boot looping. Ditto recovery just hung at the logo and the blue text "recovery booting".
Rinse and repeat a few times and now the phone has started to become difficult to get into download or recovery. If I leave it with the battery out for a while it seems to come good again.
Odin when flashing a new recovery either hangs half way though or completes and says everything is OK. Full blue bar on the phone.
Rebooting however still leaves me in the boot loop.
There is no mention on Odin of any issues with the partition however I have d/l a PIT file from one of samersh72's posts but am not sure if it is the correct one for my Int phone or indeed if I need to use it as Odin doesn't seem to report any partition errors.
If any one has any suggestions I am very receptive to ideas right now.....
Thanks

Did you perform a factory wipe after flashing stock before booting the rom for the first time?

audit13 said:
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
Click to expand...
Click to collapse
I did a factory wipe and then installed CM from my SD card but that is the only time I have able to get into recovery since the first time when I reloaded my nandroid backup

Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.

audit13 said:
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
Click to expand...
Click to collapse
Yup tried that, as I realised that the auto boot might be overwriting the custom recovery...........however as a new development I haven't been able to boot to download or even the stuck recovery since yesterday.
I think it has now moved to a full hard brick

Is still turns on? You have a USB jig to try?

audit13 said:
Is still turns on? You have a USB jig to try?
Click to expand...
Click to collapse
No I don't have one but I have all the makings of one so i'll put one together and give it a go. Though I have to say that I am not that hopeful as I can't even get a peep out of it now.

A jig may be the last solution before sending it for repair or replacing the motherboard.

audit13 said:
A jig may be the last solution before sending it for repair or replacing the motherboard.
Click to expand...
Click to collapse
Thanks Audit, Ill let you know how I get on. Just looked at some replacement motherboards and they don't seem too common for the LTE version used here in Australia AND USD60......pretty much get a working phone locally here on ebay for that and I get the rest of the parts too.

Have you tried already flashing a stock rom as a tar file from sammobile?

justgamer01 said:
Have you tried already flashing a stock rom as a tar file from sammobile?
Click to expand...
Click to collapse
Yup did that as well!

Ghostdog1 said:
Yup did that as well!
Click to expand...
Click to collapse
I'm not sure if it will work! But try emergency recovery with Smart Switch!

justgamer01 said:
I'm not sure if it will work! But try emergency recovery with Smart Switch!
Click to expand...
Click to collapse
With Smartswitch I get the same outcome as with Kires
"GT-I9505 does not support initialising. Please contact our service centre."
But on the plus side it is actually responding to button presses today. I will pick up some 100K resistors tomorrow and finish off my USB jig. See how that goes.

Well it appears to have finally died fully. No response to any button or combination of button presses. Made up a USB jig but without some response to a boot that won't work either.
Thanks to Audit and Justgamer for your advice. Think it is time to draw a line under this one and move on. Maybe a new Nexus when they drop?