I've flashed CWM Recovery three times, and I cannot for the life of me get it to stick. My phone constantly resorts to the stock recovery, so, I'm rooted and have SuperUser working fine, but no custom recovery. I'm on a Mac by the way.
Just delete or rename /etc/install-recovery.sh
suksit said:
Just delete or rename /etc/install-recovery.sh
Click to expand...
Click to collapse
Where do i find that?
luv2vexx said:
Where do i find that?
Click to expand...
Click to collapse
It's located in your phone. You can access it by running adb shell command. Or use Root Explorer.
Related
Won't replacing your update.zip get rid of the 'clockworkMod' recovery? What should be done if you already have clockworkmod installed?
bird333 said:
Won't replacing your update.zip get rid of the 'clockworkMod' recovery? What should be done if you already have clockworkmod installed?
Click to expand...
Click to collapse
Yes, but there is a copy of the file inside clockworkmod folder, that you can copy over afterwards, and rename. Or you can have ROM manager and let it download clockwork again, by clicking flash recovery.
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
mrnexus said:
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There is a .sh file that needs to be removed, totally forgot the location of it :/
/etc/install-recovery.sh needs to be deleted or renamed.
It's a "safety" feature in 3.3.1 and above to restore the stock recovery if it doesn't pass a check on boot each time.
This is pointed out in numerous threads...search a little for more details if you need them.
Ok thanks
Sent from my Nexus S using XDA App
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
mrnexus said:
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
distortedloop said:
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
Click to expand...
Click to collapse
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
EDIT: Nevermind, I used root explorer and was able to find "mount r/w" and rename it finally. Thanks.
godzigga said:
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
Click to expand...
Click to collapse
Because those won't allow you to modify system files. Get Root Explorer, like he said, and use that.
AllGamer said:
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
Click to expand...
Click to collapse
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
sarge363 said:
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
True, I used adb, spent like 2 hour trying to get the pc drivers to recognize the nexus. I used the PDAnet drivers eventually.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Are you on a custom ROM like CM or Bionix? They remove the script that rewrites stock recovery.
If you're on stock, what version of it are you on? 2.3.1 and higher have a file called /etc/install-recovery.sh on them, and if that's there it should be reflashing stock on every boot, whether you renamed the image you flashed to recovery or not...
Lost root after installing 9ZGgDXDi.zip.
This of course installed JB 4.1.1 but then when I go to recovery after entering fast boot menu I see a supine green robot with a red triangle with an exclamation point spilling out of its guts. (truly a horrible sight)
It also installed recovery-from-boot.p in System folder.
I know the solution is to rename recovery-from-boot.p file to recovery-from-boot.p.bak or renaming to something else or deleting, however since I lost root I don't see how I can rename or delete this file.
When I use root explorer I cannot mount r/w so cannot rename the file
Using ES File Explorer I rename the file but get the message that rename failed.
Connecting the phone via usb and turning on usb storage I can only access files from sd card and so cannot get to system folder in the parent directory.
Please can someone help destroy or rename the .p file.
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
chronophase1 said:
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Click to expand...
Click to collapse
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Kitch16 said:
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
Click to expand...
Click to collapse
Tried that site, but the links to software are broken
edited to add:
oops, yes the links to software work, just didn't see the correct download for all the advertizements.
Thanks for your help but I have solved my problem by adb flash of cwr
koyanishi said:
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Click to expand...
Click to collapse
You get this from the fastboot screen?
chronophase1 said:
You get this from the fastboot screen?
Click to expand...
Click to collapse
I think its after fastboot screen - that is when I go to apply zip from sd card
However I have since solved the problem by using adb to install cwr again so I am now back to root
thanks to both of you for trying to help
I'm trying to flash this recovery, but it does not seem to stick.
I have CM9.1, and i have tried flashing the zip and manually flashing the .img.
Both times don't work.
Any ideas?
bringonblink said:
I'm trying to flash this recovery, but it does not seem to stick.
I have CM9.1, and i have tried flashing the zip and manually flashing the .img.
Both times don't work.
Any ideas?
Click to expand...
Click to collapse
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
polobunny said:
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
Click to expand...
Click to collapse
You can get this working by flashing the recovery from rommanager. Worked for me.
Sent from my Nexus S using xda app-developers app
polobunny said:
Check with a file manager with root rights that you don't have install-recovery.sh in the /etc/ folder at the root of your phone.
If yes, delete it.
Click to expand...
Click to collapse
rather than deleting I suggest a renaming of the file to <filename>.<ext>.bak , as if he wants to return to stock , though I doubt that will ever happen
ReVo_007 said:
rather than deleting I suggest a renaming of the file to <filename>.<ext>.bak , as if he wants to return to stock , though I doubt that will ever happen
Click to expand...
Click to collapse
I'm on cm 9.1 and don't have that file
Sent from my Nexus S using Tapatalk 2
When I try, it says that its been disconnected, if I use a file manager on the phone it won't let me delete anything off, any ideas on this?
Did you push any data by adb or mtp via recovery?
I copied data via recovery, I take it that's where my problem came from?
you used
adb push backup /data/media/0
Click to expand...
Click to collapse
right?
lowsnamebrand said:
I copied data via recovery, I take it that's where my problem came from?
Click to expand...
Click to collapse
TO your device?
If so, yes that is where the problem came from. If you PUSH data TO your device via recovery (not single files but folders) It screws permissions. There is a zip to fix it which I can link to, if you can confirm that is what you did.
rootSU said:
TO your device?
If so, yes that is where the problem came from. If you PUSH data TO your device via recovery (not single files but folders) It screws permissions. There is a zip to fix it which I can link to, if you can confirm that is what you did.
Click to expand...
Click to collapse
please share the link
kamilmirza said:
please share the link
Click to expand...
Click to collapse
In this thread:
http://forum.xda-developers.com/showthread.php?t=2239421
is a sdcard fix permissions script (flashable zip)
Of course if you can't write to sdcard, you'll either need to adb push / MTP via recovery or using a root explorer, set all permissions to read, write for /data/media/0/Download
That's exactly what I did sir, so I reflashed everything, now (of course) everything is running like a champion, appreciate the info,won't be making that mistake again
lowsnamebrand said:
That's exactly what I did sir, so I reflashed everything, now (of course) everything is running like a champion, appreciate the info,won't be making that mistake again
Click to expand...
Click to collapse
Yeah, MTP and ADB via recovery are fine if you need to get a backup on there to restore or some zips to flash, but as soon as you start pushing actual folders, permissions screw up.
Choice is to go through setup wizard and then use Android MTP or push that zip too and flash every time.
Thanks for the info, won't be making that mistake again Lol, side not lollipop is snappy and responsive as all hell