Phone has a "failed to boot 0x1000" on the screen.

[thekooliest]

So..first of all, my mind is tripping right now because all of the posts (except the last 3) say they were posted 9/11/11 or 9/16/11...and, well this definitely isn't true because I remember asking post #21 a couple days ago. Anyone else seeing this?

Anyways, AtrixBomb. I do not think unlocking bootloader affected unlocking SIM. What I do think happened is the custom ROM Alien 4, may have had an unknown glitch that broke functionality of unlocking the SIM (although I do not know how this works). Anyways, I would've instructed you to flash the 4.5.91 SBF like you did so maybe the functionality would be restored. Now, just like when installing a new ROM when you are instructed (or advised) to wipe data and cache to avoid crazy glitches, you should do the same after (or before) flashing a sbf (especially going from modded software to stock software). This is why your phone is glitchy when you bypass SIM unlocking and continue to the OS. So, your current task would be to factory wipe so maybe you can at least use the phone, and hopefully troubleshoot the SIM unlocking more.

CWM (or Android Recovery) are part of the system files so they were replaced with the SBF flash. I'm going to guess that your are seeing a caution symbol and android robot when selecting Android Recovery from the boot options. If so, then this is stock ATRIX Android Recovery. You can factory reset through the Android Recovery following this simple guide:
https://motorola-global-portal.custh...nal-hard-reset

Anyways..bonus questions!
- If my theory is correct about Alien 4 messing up SIM unlocking, then the software probably never even attempted to unlock therefore not registering as an attempt and not locking up after X number of tries.
- Yes, like I said it will get wiped with the SBF and replaced with stock Android Recovery. To be reinstalled, you will have to reflash the pudding file, which will automatically unlock the bootloader (not having to redo the fastboot oem unlock commands), and then reinstall CWM.
- Stumped me! I am trying to think about this...but can't figure it out. I'll reply back when/if I have an epiphany.

-Sam