so i installed cwrecovery, rooted my NS and renamed install-recovery.sh. then I installed a few root-only apps (ROM manager, ROM toolbox, titanium, file expert, etc) and tried oxygen2.2.2 and devnull1-1. now i want to restore the stock recovery image so I renamed install-recovery.sh back. but when i reboot into recovery, cwm5.0.1 is still there. isn't the install-recovery.sh supposed to restore the stock recovery image when i reboot the phone?
I rooted a friend's NS earlier today, this time just unlocking the bootloader, flashing cwm5.0.1, and installing su (did not rename install-recovery.sh). when that phone rebooted, it no longer had the cwm5.0.1 image.
whats up with my install-recovery.sh? why doesn't it restore my recovery?
My guess is the install-recovery.sh has to be called by some startup script, which *I think* does not exist in those custom ROMs.
In your friend's case, because his NS is still on stock ROM it makes sense that the install-recovery.sh was called properly.
suksit said:
My guess is the install-recovery.sh has to be called by some startup script, which *I think* does not exist in those custom ROMs.
In your friend's case, because his NS is still on stock ROM it makes sense that the install-recovery.sh was called properly.
Click to expand...
Click to collapse
sorry. forgot to say this: i have reverted to the stock rooted Gingerbread ROM (restored via cwm backup). so i'm no longer running devnull or oxygen.
Install recovery.sh is a stock binary. You don't rename anything to make this file. It is patched in with OTA updates.
So......put intall-recovery.sh in /etc and put recovery-from-boot in /system
http://db.tt/hLKJDY0
http://db.tt/M2fKfC3
^^^both files above^^^
snandlal said:
Install recovery.sh is a stock binary. You don't rename anything to make this file. It is patched in with OTA updates.
So......put intall-recovery.sh in /etc and put recovery-from-boot in /system
http://db.tt/hLKJDY0
http://db.tt/M2fKfC3
^^^both files above^^^
Click to expand...
Click to collapse
thanks. i'll check those files out. i didnt "make" the install-recovery.sh file from anything. I took the original file and renamed it to install-recovery.sh.old to prevent it from overwriting the cwm recovery image with the stock image.
now that I WANT it to overwrite the CWM image, i renamed it back to install-recovery.sh but its not working.
i didnt touch recovery-from-root.p, just install-recovery.sh
flyfingersfly said:
sorry. forgot to say this: i have reverted to the stock rooted Gingerbread ROM (restored via cwm backup). so i'm no longer running devnull or oxygen.
Click to expand...
Click to collapse
In that case I think you should check the file permissions -- it should be something like rwxr-x-r-x.
suksit said:
In that case I think you should check the file permissions -- it should be something like rwxr-x-r-x.
Click to expand...
Click to collapse
oh wow. can't believe i missed that. LOL.
That was it. Thanks!
Related
Now that the recovery has been made sticky on the later versions of the One-click-root, how would I go about restoring the original stock Recovery if I ever wanted to?
I'd rather prefer it not to be sticky, or at least the script for restoring it to be renamed rather than deleted, so I can run it manually later to restore the original recovery if needed.
I haven't run the run.bat script yet, and would appreciate help in the process to backup the recovery and be in a good situation for allowing full roll back before I do the rooting.
ggggg1 said:
Now that the recovery has been made sticky on the later versions of the One-click-root, how would I go about restoring the original stock Recovery if I ever wanted to?
I'd rather prefer it not to be sticky, or at least the script for restoring it to be renamed rather than deleted, so I can run it manually later to restore the original recovery if needed.
I haven't run the run.bat script yet, and would appreciate help in the process to backup the recovery and be in a good situation for allowing full roll back before I do the rooting.
Click to expand...
Click to collapse
Assuming you're using this: http://forum.xda-developers.com/showthread.php?t=1138755
Just extract root.zip, go into the updater-script and remove the line:
delete("/system/etc/install-recovery.sh");
Save the file, repack the zip and continue (you can turn off signature verification in CWM)
You can easily rename it using adb, remounting /system manually, or via root explorer or a similar app once rooted.
Excellent, thanks; I'd seen that delete of the .sh , but wasn't sure if removing it would allow the rest of the bat or it would break further down expecting it to have been removed and a reboot to go back to CW.
Thanks!
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
sounds like you're totally lost. I don't know what a recovery.img is, well I guess most android phones have a recovery partition and a boot partition and you would flash a recovery.img to those but the galaxy s series doesn't work anything like that.
lets start with you sharing some information. open settings>about phone and tell me the baseband and android version. because if I have to guess you are trying to use a froyo proceedure that was only needed before custom kernels existed and you're trying it on stock gingerbread firmware, either a Rogers phone or a phone that has been flashed with a gingerbread leak.
also do you mean miui??? auto correct is a *****. and if you flash miui then why an old build? wouldn't you want 2.3.7???
singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
huh .....
oh and this should be in the [email protected]
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
singhtjay said:
I am trying to install mini 2.3.5 on my infuse 4g. It is rooted and everything. When I tried to instal the recovery.img, it wasn't in the system/bin folder. I used terminal and busy box to put it there. Then i used clockworks mod to flash it. Then when i reboot into CWM it says
Signature Verification Failed
I did notice a recovery file in /system. not in the bin folder.
Click to expand...
Click to collapse
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
singhtjay said:
Yes it's a Rogers phone. I'm sorry if I'm making this difficult it is my first time doing this so I'm kinda nervous anyways. Basically its asking me to replace the recovery.img with the 3e modded one. The recovery.img is not in system/bin (where it should be), its in the root folder however. May kernel version os 2.6.35.7-1997. My firmware is 2.3.3 and my baseband is i997RUXKG3
Click to expand...
Click to collapse
well first off its not a .img its a binary file with no extension a .img is something you get when you dump a partition or drive on a low level so all the Metadata and everything is copied exactly and it would be used for reproducing a drive as a backup or on another device, well it could be any extension really but .img is common.
other androids have a different partition layout and may have a recovery partition.
now what is going.g on is you are trying to do a proceedure for froyo on a gingerbread rom. Samsung changed the boot scripts making it impossible to use cwm without a custom kernel. the boot scripts are in the initramfs which Samsung uses in place of the boot partition which means cwm and init.d support can't be added without replacing the whole kernel.
good news is Samsung has a flash tool called Odin. and there is an open source substitute called heimdall and if you are rooted there is a phone based program called sgs kernel flasher that will flash the kernel. look into the Rogers infuse root thread. the root kernel will also give you cwm. you could also use the hellraiser kernel, entropy's dd kernel, or the infusion gb kernel.
I cant go to recovery through Rom Manager for some reason. It works manualy( power+volume) but when I click it from the app it freezes, and shows an exclamation point triangle
have you tried to reinstall the app?
Wich CWM do you have?
thy the above post; if that doesn't work, go into recovery manually and fix permissions
that must be why
I was following this video http://www.youtube.com/watch?v=PVyGw6vycFo
and it said I had to wipe my data which I did, and maybe CWM was removed?
Ill try to flash CWM and see what happens.
Worked! thanks
In wich way?
Have you reinstall Rom manager App or reflah CWM Recovery?
actually, theres been a trend going on here....
I went on recovery to check if its working after I flashed it and it worked, after turning it off and removing the usb out of my computer I tried again and it didnt work.
Any ideas why?
Edit: when I had ROM manager I already tried to Flash CWM there if you're wondering.
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Harbb said:
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Click to expand...
Click to collapse
where can I find /etc/install-recovery.sh and what do you mean by file explorer with root capability?
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Harbb said:
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Click to expand...
Click to collapse
fairly new to android so I have no clue what you are talking about sorry... can you give me some steps on how to do that. again I apologize, Im still new
Download this from the market, i'm sure you'll figure it out
quick unrelated question: I tried to apply the ROM and it didnt continue, it said it was aborted or something
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 have looked for hours for the final stock recovery for Stingray. I have found 4.1.1 and updates, but not what I need to flash my Xoom back to root. Can someone point me to a copy please?
TWRP won't work? Download goomanager and have it download and install it.
rastaguy said:
I have looked for hours for the final stock recovery for Stingray. I have found 4.1.1 and updates, but not what I need to flash my Xoom back to root. Can someone point me to a copy please?
Click to expand...
Click to collapse
Are you using the stock kernel and stock ROM right now? If you are, just download the JZO54M OTA file from Google. Open the ZIP file, and go under the "recovery" folder. Put recovery-from-boot.p in /system and put install-recovery.sh in /system/etc. Set the permissions on install-recovery.sh to 544 and set ownership to root:root. Reboot and it'll flash stock recovery for you on the next bootup. :good: