I though I would describe something that I have developed to aid in getting out of recovery flag bootloops.
I have also discovered what sometimes causes them in the first place. First, the user uses ROM Manager or some other software to set the recovery flag to boot into CWM. The older versions of CWM (3.2.0.1 and older) have an option in the mounts menu to format /boot. Not knowing any better, some users do that. Then they flash their ROM and hard power off to exit. They hard power off either because they did not know they should choose "reboot" from the menu or by CWM locking up when they try. When the user does that, CWM does not clear the recovery flag. So next time it boots, it tries to go to recovery as we have discussed here before. If they formatted /boot, there is no CWM there so we have our bootloop. Fortunately, that option to format /boot is missing in the newest CWM.
What I have done is create a new CWM bootable SD with fattire's/Racks' new version (5.5.0.4) and Cyanoboot. What I have done differently is to not only include CWM as uImage/uRamdisk, but also to include it as uRecImg/uRecRam. In a recovery bootloop, those are the files the system is looking for. Therefore it will boot to them. Then the user can flash the new CWM to emmc to fix the problem. This has worked for at least one user in a recovery bootloop. The new CWM image file is attached to my tips thread linked in my signature.
The reason I am posting this in this thread is, I still think it is a very good idea for the option of clearing the recovery flag to be in Cyanoboot. Mateorod, I hope you are making progress in adding that. It is as important as ever.