[Moto X Q&A] KidJoe:
Sorry for the long answer, but I think you're going to need this info....

The Moto Maker and Retail Moto X from ATT and Verizon have locked bootloaders and can't have their bootloaders unlocked. Moto doesn't give out the bootloader unlock codes for them. There was a Chinese site selling the codes but it got shut down.

Since you couldn't downgrade successfully, I'm going to guess that you have 4.4.2 on your phone?

Due to changes in the bootloader, GPT.BIN and other parts included with 4.4.2, under certain circumstances when trying to downgrade from 4.4.2 to 4.4 or lower, you could either brick your phone, or set it up to brick in the future when you take an upgrade. So it is suggested you just stick with what is on your phone once you get on 4.4.2!! i.e. do NOT attempt to downgrade from 4.4.2 to anything lower.

I don't know what state your phone is in now, but if you had 4.4.2 on your phone, and you tried to downgrade, but didn't brick, do NOT take any OTA's!!! That will definitely brick your phone. For now, you'll likely get HAB Check errors, and other things if you try to reboot into bootloader or recovery. If you try to go under Settings -> Security you likely be "kicked back" to the settings screen instead. If you are experiencing these or similar issues, when the ATT 4.4.2 SBF gets leaked and posted to -> http://sbf.droid-developers.org/phone.php?device=0 you'll want to download it and flash your phone with it to get back to a stable/consistent foundation.

As for rooting the X with a locked bootloader... (like the ATT Moto X, or non-Developer Verizon X)

If you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection.

When Write Protection is enabled (the phone's default state with locked bootloader, or the state you are in after you take the 4.4.2 OTA), any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on.

Even if you have root, but lost Write Protection, any apps you've installed that need to write to system can't permanently save their changes (you have to re-do every time your phone powers off/on), and any Root type app, or app that gets installed to /system after WP is enabled will be lost at power off/on.

MotoWpNoMo was used on 4.4. and below to Disable Write Protection. Part of the 4.4.2 update patches the exploit that MotoWpNoMo used, so it wont work on 4.4.2.

SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower to Root, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone, so you can't use these anymore.

JCASE has already posted he has an exploit to use to gain root on 4.4.2, but due to job and family, wont release it or a process making use of it until the fall. Who knows what ROM Moto will push out by then, and if they will have patched the exploit already. BUT before you get mad at JCASE for waiting so long, that doesn't address a Write Protection dis-abler. I've not seen any talk about work on that for locked bootloaders (when you unlock the bootloader, like on Dev Editions, the write protection is disabled). So JCASE could release his Root exploit, he or someone could develop that process, but it would be kind of useless without the ability to disable write protection since all your changes would be lost as soon as you power off/on.

Trust me, *IF* or when a Root and Write Protection bypass is out for 4.4.2, you will see threads on it. Until then, you have to sit tight.

Now, if you have 4.4 on your phone, you can root and disable write protection by using SlapMyMoto and MotoWpNoMo, but then you must NOT take the 4.4.2 OTA update, as you will keep root, but write protection will become enabled again. You can use a root capable file explorer (like Root Explorer) to navigate to /system/priv-app and rename the 3C_OTA.APK to 3C_OTA.APK.BAK to prevent the OTA update prompts.

If you are on 4.4 rooted with write protection disabled, you might want to check out the SafeStrap discussions over at Rootzwiki.com. That might at least afford you a way to run 4.4.2.