ive been in a cwm bootloop for over a month on the boost version, and the mibib does nothing for me...even if i extract the one for boost from the nandroid backup...what i need is someone who knows about .ops files so i can figure out what .pit file matches it(512 is most common) and force odin to repartition the phone this way, start over from stock gb, and work way back up again...be careful guys, i dunno what happened, but apparently the internal partitions are very easy to screw up with this phone. once ive un-bricked this monster i will write a how-to...i figured out the problem by researching bricked samsungs on xda, used parted via adb to investigate the partitions on my device, and discovered missing labels, and a revert of ext4 filesystems back to rfs which confuses the **** out of me cuz my nandroids were from phoenix0.2 which has a script to reformat the phone in ext4, not rfs....so not sure wtf happened but i feel the fix is close...CWM boot loops require you to flash the MIBIB file that the others in this thread used to the phone in Odin, but you need to get into download mode to do that.
You can get into download mode when you're stuck in this situation, I was in the same position after installing the FA19 modem on my Replenish. If you cannot get into DL mode by using the key combo on the phone: Plug the phone into your computer (while the phone is in CWM), open a command terminal window, change directory to where you have the Android SDK installed (if you don't have the SDK already, get it, its a necessity for modding your phone), and type ADB devices to see if the phone shows as a connected device.
If the phone shows as a connected device, type in "ADB reboot download" to boot into download mode.