well i did try interfering with the launcher to try force it to trigger, I.e editing some odd bytes of the launcher to break the checksums, modifying the files "created date" etc, some devs said that the code looks pretty much impossible to trigger when using a official launcher.
as i understand it, the old brick code loaded by default so any bugs in the loading process or corruption of the SD card "could" lead to the brick code being accidentally triggered....even if the launcher was absolutely un-modified, running diagnostics caused some loaded data to be corrupted meaning the brick code could inadvertently be reached as it was still loaded in to memory
if I'm understanding correctly, the revised brick code does not get loaded in to memory unless the initial payload has been specifically hacked. so any bugs in the memory will not cause the brick code to be reached for legitimate users as the code is not loaded and can't trigger by accident.
this is my interpretation the info from the dev's....but i ain't no dev so i'm not 100% on the details, but its something like that