[Motorola Atrix HD] mattlgroff:
Researching length of code: http://pastebin.com/zHh76h60

After researching, I can conclude the code is going to be between 1-20 digits (assuming I am reading syntax correct)

Looks like we need the code for it for work, normally fastboot tells you the code for use and explains how to do it...but this is much better than success story than Razr, I believe the unlocking bootloader tool from Motorola WILL support this device! [UPDATE: NOPE! Motorola at this time is not supporting this device, but this method is the proper way anyway. ]

C:\Users\matt>fastboot devices
(My device ID) fastboot

C:\Users\matt>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.104s]
finished. total time: 0.107s

C:\Users\matt>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.104s]
finished. total time: 0.107s

This is not a special Atrix HD, it still says "Device is LOCKED. Status Code: 0" on the AP Fastoot Flash Mode (S) screen.

C:\Users\matt>fastboot oem get_identifier_token
...
(bootloader) Restricted oem command
FAILED (remote failure)
finished. total time: 0.100s

EDIT: (August 14th 2012)

C:\Users\matt>fastboot oem get_unlock_data
...
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
OKAY [ 0.351s]
finished. total time: 0.353s

Put this into your own device and find out your unlock data :)

Below is an excerpt from a strings.exe of the abootBackup partition:

Device already unlocked!
%s: START
%s: value = %s
fastboot oem unlock [ unlock code ]
OEM unlock failure!
Could not get unlock data!

Above you can see... we HAVE the unlock data now. We just have to figure out how to use it.

Status codes shown in AP Fastboot:

Device is LOCKED. Status Code: 0
Device is UNLOCKED. Status Code: 1
Device is LOCKED. Status Code: 2
Device is UNLOCKED. Status Code: 3

More strings.exe:

Error while unlocking device
mot_sst_validate_token: Token header incorrect
mot_sst_validate_token: Format version incorrect
mot_sst_validate_token: Length incorrect
mot_sst_validate_token: Binding information incorrect
mot_sst_validate_token: Unable to validate token integrity
mot_sst_validate_token: Token integrity invalid
unlock failed in sst oem unlock handler %02x
unlock data invalid!
Password incorrect
Password incorrect!
Cannot provide unlock data
Cannot provide unlock data!
general failure in sst oem unlock handler %02x
General system failure! %02x
Unlock completed! Wait to reboot
General Unlock failure!
unlock failed in sst oem unlock handler
Set MOT SST values
Done Setup my special MOT SST values
mot_sst_create_token: Unable to retrieve PUID
mot_sst_create_token: Unable to retrieve FUID
mot_sst_create_token: Getting PSV
mot_sst_create_token: Unable to retrieve PSV
mot_sst_create_token: Generate token code
mot_sst_create_token: token code generated!
mot_sst_create_token: Writing token
mot_sst_create_token: Unable to generate token code
create_token status: %d
mot_sst_create_token: Creating token
mot_sst_create_token: Getting flash uid
%s START
mot_sst_oem_lock_handler: invalid state
mot_sst_oem_lock_handler: load and validate failed
Re-lock failure
lock complete
%s failure to delete or create token
mot_sst_oem_lock_handler

From what it seems like... the device itself must create the same token that I believe a webkit will give us. [UPDATE: Proven right lol ]