[Motorola Atrix HD] skeevydude:
What you described is the bootmenu. From there, select recovery (might have to press both volumes here, I don't really use stock recovery at all), then install update. If nothing happens or it doesn't flash anything (what I suspect) you're gonna then have to select factory reset THEN you're gonna have to flash a stock fastboot.

Sorry. I know you don't wanna hear that, but if you didn't make /system fully stock before taking the upgrade that's what ya gotta do to fix it.

That said, you can always try manually flashing a fastboot and skip the last three erase commands...or at least the fastboot erase userdata command. Make a backup of you're current AT&T fastboot XML, replace it this this one, then flash it with RSD. It has all the regular fixes in place only it won't format your app data. You may or maynot get lucky and get to keep your data.

<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="DINARAJB_CFC" />
<software_version version="MB886_att-user 4.1.1 9.8.0Q-97_MB886_FFW-20 27 release-keysMB886_BP_100740.071.65.04P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="3F91C106A878810B0AE8132F3FB8EACC" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="6A4BF8E8480F3A14EB22A932314B430F" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="AC66902C8721200A2FC08E485D4510D2" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="919D0B340CFDD5FC7C541803DB65C2D6" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="ED1C505E36E769CCF0BB3C10E46DD62B" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="15F98BAFB7C4853C2582465EEB7A3522" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="D03DEDA491CDB39D81B213269FB1E586" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="A517AE513A5CDF7327AD2FF45646336B" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="boot" filename="boot.img" MD5="20BA5D0988DE0AAAC2C447E1E066FE56" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="63DEEABFB8FCD48F3F91681281657D9D" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="3A1C235E4B54E00A09D7C7A53B83AD9E" />
<step operation="flash" partition="system" filename="system.img" MD5="C5C30794293A8951E5599FA7A24820DE" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="C55107A3131A226459A09195B6E48E57" />
</steps>
</flashing>

Also, the above isn't something you normally want to flash and is just for this time only. Normally there are 3 more erase commands and the command to flash the gpt. Tack on the 3 below to make this a normal, fixed fastboot xml (between the bottom cdrom line and /steps)

<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />

I don't like being that guy, but let this be a lesson for you about finding a decent app backup solution and setting it up to run nightly. I use Titanium Backup Pro (my first app purchased, btw) and every night at 2am I have it scheduled to backup any updated app data, any updated apk's, call logs, wifi passwords, browser bookmarks...Regardless of what rom I'm on, if anything happens I can be back to where I was within an hour with all my apps, their correct settings, etc...might take a little longer if I flash a rom like PAC and get sucked into tweaking settings.

//And if it doesn't quit raining I'm gonna go insane. I have welding to do, only where I have to weld it becomes 6 inches deep in water within 30 minutes of decent rain....I really don't like being electrocuted by a 110v welder because I'm standing in a puddle....Makes me wonder if welding with my phone in my pocket the other day is what might have fried it since I did have a few currents pass through me (they didn't hurt).