Hey, thanks Dan. I was able to quickly implement that change on the way out the door, and it has indeed stabilized the size issue. Which will, I believe, make the fix functional, although not quite finished. I had tried importing some commands from the omap config file that were set up like that (specifically the rewrite to bcb after an update.zip is applied) but the way I was doing it as breaking the rest of the function.
So now I just need to winnow out whatever is writing the boot data and encrypted characters. I'll do it tonight. Thanks for the tip.
I will say it looks pretty cool, due to the framework tonsofquestions (I believe) put together. Very easy to put in.
My plan is to only change the default to recovery behavior in the event of a missing bcb file, since the other two eventualities (too small or empty, if memory serves) can be addressed by the menu option. Hopefully that lets us boot into recovery from the ROM, because as it is I can still only get to recovery through cyanoboot.