[Moto X Q&A] titanshadow:
Sounds like whoever had to before you flashed something strange to it. You should take a look at the link provided in an above post about resurrecting a bricked device. Looks complicated to me but it might be what you've got to do. The problem you're looking at seems to be that the bootloader is locked.

I did notice that there are two firmwares for your brand of device on this URL:

http://sbf.droid-developers.org/phone.php?device=0

One is version Blur_Version.139.12.35.ghost_row.AmericaMovil.en.PR and the other is Blur_Version.139.7.26.ghost_row.AmericaMovil.en.PR, I've bolded the version numbers. I would download and try to flash them both. Also from my own experience don't change the file name either (you probably didn't, but it should be said anyway) since they are likely signed and I've had serious problems with trying to flash firmwares where I changed the file name.

If you can't get RDS to work, try this method here, http://xdaforums.com/showthread.php?t=2446515 which covers both RDS and my favorite the mfastboot method. Now you'll have to do a little work yourself since this guide is for Verizon but there is an XML file inside the zipped update file that you should be able to pull the information you need out of. Inside the XML file you'll see a series of "Steps" (they look like this:

<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="4C9F15C80FED62BAB7A042FDBA4D7A2F" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="34B3A02418240C805CCB2998B2343261" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="1F8DBC99E41DFB7596DBC78687AC5E7B" />
<step operation="flash" partition="boot" filename="boot.img" MD5="49C02FCD26133923B1B4F2CFE862C422" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="62DCB8F941BEC9D824146453834CD3FE" />
<step operation="flash" partition="system" filename="system.img" MD5="1D5214E5171BE9894D0413322D2DD211" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="57B83F54B07922B9CBAF3C4125CBA8A1" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="BAB00624486527FE415D8BACFF875C99" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="config carrier vzw" />
<step operation="oem" var="fb_mode_clear" />

Your XML will look similar, but different. The main difference is going to be the "config carrier vzw" line, I don't have the XML file from your update but to give you an idea on how this translates, here is the sequence of commands to manually flash the Verizon update (derrived from the XML file contents above):

mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem non-hlos.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
mfastboot reboot

If you take these two sections (the commands and the XML) you should be able to see how to get the commands from the XML and turn them into mfastboot commands. My little bit of research (please understand I did like 2 minutes of quick looking around) suggests that the only real difference is going to be the line containing "oem config carrier vzw" and the sequence is important so you'll notice the XML has the same sequence as the list of commands, you should find what to replace the config carrier command by looking right after erase clogo and right before fb_mode_clear in your own XML file. If you need any help doing this, let me know and I'll do my best.

If that fails, however, you may need to look into unlocking your bootloader, which I haven't personally done, but I have read a number of people who have done it. The best way is, if your device is supported, to use this method here (the official Motorola method):

https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth

Anyway, that is the best I've got. I hope something works for you, you may also want to see if you can get ahold of who sold you the device and find out if they did anything strange to the device - like flashing a non-standard firmware or some such.