The developer edition is pretty clean from the get-go, but its primary advantage does come from the unlockable bootloader. It wasn’t nearly as smooth of a process as my Galaxy Nexus, but no Nexus 5 on Verizon means options are far and few between. Farewell old friend
The Usual Toys + mfastboot & RSD Lite
Grab the usual platform-tools from the Android SDK. Add the binaries to your PATH if you’d like etc.
Motorola devices also may (in this case assuredly) need to use mfastboot which helps avoid some flash recovery size issues with this purpose-built Motorola variant of fastboot.
I’ve uploaded a copy here — http://www.mediafire.com/download/1resnckuzeehy3m/mfastboot.exe — but, you’re free to find a copy for yourself if you’re wary.
KitKate 4.4 OTA or Manual Update
Before anything, I patched the system up to KitKat 4.4 through OTA
EDIT: Also, you can find the firmware here – http://sbf.droid-developers.org/phone.php?device=0
If you’re going to use RSD Lite:
- Install Motorola Device Manager (for drivers) – https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
- Extract the correct firmware (e.g. )
- Find the .XML file in the extracted directory and remove the line:
PowerShell1<step var="max-download-size" operation="getvar"/>
- Save the file.
- On the phone, enter the bootloader
- Open up RDS Lite and ensure the program sees your phone.
- Navigate to the XML file and begin the process. (This will cause a wipe)
Unlock the Bootloader
If you’re not on VZW or ATT (or have the “Developer Version” on those carriers) you can unlock your bootloader by following the instructions on this website: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/action/auth
You will need fastboot/mfastboot to recovery necessary GUIDs/IDs and perform the unlock.
Essentially it involves pulling and formatting data from the device, submitting that to Motorola, and they provide you with an unlock code to which you can unlock your device in the bootloader using:
mfastboot oem unlock UNLOCKCODE
This may void your warranty.
TWRP 184.108.40.206 patched for Moto X
At the time of this article, 220.127.116.11 only had initial support for f2fs which Moto X uses (KitKat 4.4)
I should also note that ADB sideload did not seem to be functional, so you’ll have to load the ZIP files on to the /sdcard
- Boot into the bootloader (Power+VolDwn)
- Use the command to flash the recovery
PowerShell1mfastboot flash recovery twrp-18.104.22.168-ghost-4.4.img
- After a successful flash, use VolDown to select RECOVERY and use VolUp to boot into it (Power will simply boot into system). If you do not do this after initially flashing the recovery, you will encounter issues like “No Command” the next time you try to boot into Recovery
Once you’ve verified TWRP is working you can either flash the SuperSU ZIP yourself or use the play store app to download/flash it for you.