I also believe that the referenced thread is about the same problem.
Freescale recommends that you program the security bits to "unsecured" as part of erasing flash. The Freescale recommended 27 step unsecuring method does this. Simple flash programming utilities do this routinely after doing a bulk erase of flash.
If this recommendation is followed, the only value that can be programmed without another erase is 00. Doing this "cumulative programming" violates Freescale recommendations, but does work.
The proper method would be to read the sector containing 0xFOFE, erase it, and program it with the modified values. As far as I can tell, many programming utilities do not consider doing sector reprogramming and don't do this.