A user on the forums at Tortuga posted this in response to formatting a corrupt hard drive while on this Rogero 4.30 CFW.
I Fixed the bug for my Slim 2504-B, datacode 0C. Let me explain, what it does seem to me. I think it's very important.
All NOR consoles are affected, and are vulnerable. This is a serious thing. It's just a time bomb, a matter of time you get a semibrick if your HDD gets damaged on a NOR console (al PS3 Slim and some FAT consoles seem to be affected). There's many people affected. You won't be able to reflash or replace the HDD by a new one.
The problem with this firmware, once you look inside, is that the LV0, LV1 and LV2 chains, seem to have been taken from the E3 firmware, which I don't understand. And the LV0 chain is broken because of the coolboot and the logo of Rogero's 4.30.
This means, that if you flash this firmware on a NOR console and then format the HDD because the data is corrupted or because you want to do it(or simply you try to put a new one), you get in a loop, a semibrick. The brick is because the format is not being done correctly, cause of the bad lv0 string.
The way I fixed it is taking the HDD of the console, putting it on a PC, and destroying all the format. Then managed to get into a recovery that detects the HDD without format and flashed the 4.25to3.55. The console asked to reformat about 2 times more, but it came to alive with the semi-downgrade done.
The NAND consoles are not affected, but the broken chain is there and who knows.
Can anyone confirm if this is the case and there is a possibility of a future semi-brick if updating to this 4.30 CFW and then needing to format a corrupt hard drive? I have read all 62 pages and the user guide and this is not addressed that I can remember (changing a hard drive because it was corrupted.) I want to thank Rogero for his work and by no means want to start up any rumours if not true...just want clarification before I jump in and install this over my KMEAW 3.55 CFW .
Update: For anyone wanting to read about this on Tortuga forums here is a link to the thread