[Galaxy S Plus I9001 Android Development] skywalker01:
This is a fixed version of manveru0's FeaMod recovery V1.4 (aka CWM recovery v 5.5.0.4) so all credits go to him.

Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this piece of software and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !

Terms of use: Remember the power of reading ! If you can't find some particular information on the first page use the search function, it is your best friend.

Besides there are even guides and tutorials all over the forum and in most cases your question was already answered.

If you take a moment and read through the WHOLE post below and a few more moments to read some of all the stuff in other device related threads of this forum, you will find ALL you need just there.

It's not invisible so you CAN find it. And forum rules and good manners tell you to do it exactly like this. And I WILL ignore every question that is already answered here.

Obey the rules !

Recovery feature list

- the internally used kernel to boot CWM recovery is not overclocked and not undervolted and uses Samsung's stock kernel settings so it should work on any i9001 phone (it's different from manveru0's release and I already released this fix in January in the original FeaMod thread)

- reworked the integrated script in recovery startup sequence that takes care about the recovery reboot issue automatically so no more rebooting into recovery again and again once and for all (reported to work finally by wintel_mac, thanks for testing all releases) ;)

- the CWM 5.5.0.4 recovery itself remains totally untouched and is the very same as in FeaMod V1.4; for any more information on that please refer to the original FeaMod thread here:

http://xdaforums.com/showthread.php?t=1331164

- the package includes only the recovery image so anything else on your phone remains untouched including your boot kernel; the recovery partition has its own kernel integrated which is only used for booting CWM recovery, in all other cases your original kernel in the boot partition is used - primarily for booting android that is

​

This version is meant for use with ANY i9001 ROM including stock ROMs, custom ROMs and even AOSP ROMs as well (as soon as the latter are actually available) ;)

Install instructions:

1. If you don't have already any CWM version (FeaMod Recovery) install V1.2 via Odin first. If you never heard of that learn all about it here:

http://xdaforums.com/showthread.php?t=1331164

2. Now make a complete nandroid backup of your phone with CWM

3. Download the attached CWM zip package

4. Copy it to your internal sdcard

5. In CWM choose "install zip from sdcard", then "choose zip from internal sdcard"

6. Select the downloaded file "FeaModV1.4_Fixed_NoBootLoop_NonOC_NonUV.zip"

7. Confirm install with "Yes"

8. Wait till you see the message "Reboot to use Fixed FeaMod V1.4 !"

9. Do so like the message says.

10. On first reboot the fix to cure the recovery reboot wasn't yet executed so you will end up in recovery once again (if your phone is affected with that issue) !

11. So you have to reboot into system once again and from now on everything will be fine, promised :D That is if you installed it properly and exactly like described above.

​

If anything went wrong during install just try again.

If you can't boot into recovery anymore just install FeaMod 1.2 via Odin again.

If you want to install Fixed FeaMod V1.4 directly via odin just extract the recovery.img only from the zip file and tar it. Then flash it via Odin in one package mode. If you don't know how to do that refer to the flash guides in this i9001 subforum or use the above described method only. If you still can't handle anything of that don't use FeaMod/CWM at all, you will most probably brick your phone with it.

The experienced users (ONLY !!!) can also use dd of course to flash the recovery.img directly to the appropriate partition ;)

If you got severe errors AND didn't make a backup because you knew better than the developer don't even dare to beg for help.

If you encounter any other errors report them here but be sure that this is no feature or problem that was already described above.