New: XDA launches forum for app developers. Discuss coding, tools, marketing, and more.
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
jkpair
Old
(Last edited by jkpair; 11th October 2010 at 01:35 AM.) Reason: wrong board
#1  
jkpair's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 15
Join Date: Dec 2009
Location: Gloster
Default [Q] Rebooting to Bootstrap

I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!


just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!
 
citanes-26
Old
#2  
citanes-26's Avatar
Senior Member
Thanks Meter 0
Posts: 110
Join Date: May 2010
Location: Tazewell,TN
That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.

Sent from my DROIDX using XDA App
 
matrix2004
Old
#3  
Senior Member
Thanks Meter 5
Posts: 154
Join Date: Mar 2008
Wait. I have a normal reboot. Maybe mine is messed up?
 
jkpair
Old
#4  
jkpair's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 15
Join Date: Dec 2009
Location: Gloster
Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.

Sent from my DROIDX using XDA App
Droid X OTA 2.2
Rooted and Deodex'd
APEX Rom (life is so much clearer without all the blur)
 
Zaphod-Beeblebrox
Old
#5  
Zaphod-Beeblebrox's Avatar
Senior Member
Thanks Meter 131
Posts: 673
Join Date: Dec 2009
Location: Virginia
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
 
kcrang
Old
#6  
Junior Member
Thanks Meter 0
Posts: 9
Join Date: Aug 2010
If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.
 
jkpair
Old
(Last edited by jkpair; 11th October 2010 at 04:48 PM.)
#7  
jkpair's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 15
Join Date: Dec 2009
Location: Gloster
Quote:
Originally Posted by Zaphod-Beeblebrox View Post
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?

Oh and thanks for the help by the way.

UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer
Droid X OTA 2.2
Rooted and Deodex'd
APEX Rom (life is so much clearer without all the blur)
 
Zaphod-Beeblebrox
Old
#8  
Zaphod-Beeblebrox's Avatar
Senior Member
Thanks Meter 131
Posts: 673
Join Date: Dec 2009
Location: Virginia
Quote:
Originally Posted by jkpair View Post
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
 
jkpair
Old
(Last edited by jkpair; 11th October 2010 at 05:28 PM.)
#9  
jkpair's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 15
Join Date: Dec 2009
Location: Gloster
Quote:
Originally Posted by Zaphod-Beeblebrox View Post
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
so for adb shell it would be something like:

Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?

So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.


Once again thanks for the help. Seems the answer is always 42.
Droid X OTA 2.2
Rooted and Deodex'd
APEX Rom (life is so much clearer without all the blur)
 
Zaphod-Beeblebrox
Old
(Last edited by Zaphod-Beeblebrox; 11th October 2010 at 06:36 PM.)
#10  
Zaphod-Beeblebrox's Avatar
Senior Member
Thanks Meter 131
Posts: 673
Join Date: Dec 2009
Location: Virginia
Quote:
Originally Posted by jkpair View Post
so for adb shell it would be something like:

Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?

So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.


Once again thanks for the help. Seems the answer is always 42.
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.

If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.


XDA PORTAL POSTS

Dos and Don’ts of Android Design

As long as you’re coming from some type of programming background, the unseen part of app … more

Expand Your Choice of Icons with Icon Themer

Icons are some of the most commonly themed elements of the Android UI, and there is certainly no … more

MicrowaveTimePicker Brings 4.2 TimePicker to 2.1+ Devices

It’s frustrating to see slick new features that you can’t use when … more

What’s Possible with CASUAL & How to Make Your Own CASUAL – XDA Developer TV

XDA Elite Recognized Developer AdamOutler is known … more