[RAZR HD Android Development] pcarenza:
I'll sum it up in a three-word phrase: it's not possible.

First of all, when you flash a rom, it's usually comprised of 3 parts: a kernel, a system partition, and the scripts that insert it into your phone.

For the most part, the boot.img (kernel) is the one that could cause problems like the one you see... with the exception of some errant propmods in build.prop or something in the device-specific files.

So let's say something wreaks havoc on your system.... it's likely something to do with corrupt memory.. that's essentially what it boils down to.

When you have a problem where it doesn't get past the logo... you've got a serious malfunction, likely something overwrote your boot partition with some corrupt data. In my years of devving and flashing, the only thing that's brought my phone to its knees like that was experimenting with some low-level injection of code into my kernel at boot-time (kexec). So, it's not outside the realm of possibility that it could happen with a ROM... not likely, since 99% of the hundreds of CM-10 users on this device have not had it.

What I find increasingly hard to believe... because I intentionally think analytically.. have to in order to troubleshoot.. is that you would be encountering problems with your backups - if they were done on a clean system (caveat). Here's why:

When you do a restore, you essentially overwrite the boot, system, and data partitions you had when you backed up.. sometimes more, sometimes less, depending on what you chose. I'm happy to see you choose to wipe before you restore, though it's really not necessary because in the big 2 recoveries, these partitions are automatically wiped before they're restored by the recovery script. So, you wouldn't see any trace of that corrupt kernel that was causing the issue... or the system drivers which you just overwrote. They're gone. That last rom that caused problems for you won't be hiding in some unknown sector, waiting to jump out... if your backup files are good. If boot, system, and data are replaced, the problem should be fixed. And it's not a memory corruption thing because your RAM was wiped on reboot. Get me so far?

Now, here's what you should look at more closely:

1) your recovery. Are you using TWRP or CWM? How do you perform your wipes? If your data partition is completely wiped (not factory reset, I mean actual complete wipe of data from the advanced menu), you may find that your phone is not going to boot.

2) your mounts in recovery. Are you a safestrap refugee - have you been mounting /system in recovery? No need to bother with that, it's not necessary.

3) your actual restore files. Have you created them from clean working ROMs? Have you made them with MD5s to make sure they're intact and complete?

Look - I'm not here to maliciously contradict what you're saying. I'm just saying that if you've taken the plunge to unlock your bootloader (you have done that, right? otherwise this whole post is moot and you've definitely been doing things wrong the whole time), you should take time to do the research before you tinker with the low-level stuff. Figure out why things happen... figure out the things to do to troubleshoot... and most of all, if you come up with a serious issue, document it the best you possibly can for the dev, including logcats and kernel logs. If the developer hasn't seen the issue or documentation, it might as well not exist.

This isn't a Galaxy Nexus, or a Nexus of any kind - these ROMS are the product of hard work, extensive troubleshooting and understanding of all kinds of unique kinks that come with our particular device - I think dhacker, epinter, nadlabak and crew deserve more than a little respect and space.. it's new and relatively undiscovered territory. If you're scared of mountain lions (apple pun was intentional), perhaps the bars and confinement of a zoo would better suit your curiosity.

Oh one more thing... in the past month I've flashed over 150 times, not all of them successful, some requiring a little more attention and debugging than others. I know what I'm talking about too.

Thanks :)