[Moto X General] KidJoe:
If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.

With the Verizon Kit Kat roll out, and now that there is an ATT Kit Kat soak starting soon, so undoubtedly they and the other carriers will start getting it, I wanted to summarize some of the information found in these two main threads ->

http://xdaforums.com/showthread.php?t=2534060

http://xdaforums.com/showthread.php?t=2525495 (start at the back and work your way front because of some of the fluff from before the OTA hit)

This might make it easier for those Verizon users who haven't received Kit Kat yet, or those of you on other carriers as Kit Kat starts rolling out. These are the most common issues and questions I've seen asked....

You will lose root when you take the KitKat OTA.

There is no way to retain root while upgrading to Kit Kat Updated Root for KitKat released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)

If your phone has a LOCKED BootLoader, you will not be able to root KitKit at this time. UPDATED Root for KitKat 4.4 has been released see -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)

Note: If you have an unlocked boot loader, or developer edition, root is obtainable. (see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP )

You must be unrooted, reverse the impacts of PwnMyMoto and/or RockMyMoto or you will be stuck in a boot loop when the OTA. (how to fix posted later)

Once on Kit Kat, you can't flash back to past firmware, unless you have an unlocked boot loader. (see the updates section below, and the SlapMyMoto threads)

You must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update.

there are several options to get back to "stock" without loosing your data. (posted later in this thread), some are more techincal, some are more noob friendly.

If you want to thether "for free", FoxFi doesn't work. Any past hacks that require root wont work, unless your phone has been Rooted update:see the EDITS & UPDATES section at the bottom of this post)

Kit Kat brings some style and status bar changes to be aware of. Like everything being WHITE, no more blue, no data traffic arrows, etc For more info please see -> http://www.androidpolice.com/2013/1...nd-only-shows-connectivity-in-quick-settings/

Note: If you have flashed your phone with another carrier's ROM, or have tried the previously leaked T-Mobile or ATT pre-release roms, these steps may not work!!

Motorola Fastboot, mFastboot, and android SDK fastboot... what's the difference?

When you install the ADB and Platform Tools from the AndroidSDK, you will also get a fastboot.exe. This standard fastboot.exe is compatible with most, if not all, Android devices to flash parts or partitions with. Unfortunately, that standard fastboot is limited on how big of files it can properly flash. In recent android devices, Motorola has surpassed the limits of fastboot, as such they have an "upgraded" or "tweaked" fastboot.

Having two fastboot.exe files, one that comes with the AndroidSDK install, and one from Moto, can get confusing, and presents a challenge. You can't put the Moto one into your PlatoformTools folder with the AndroidSDK one due to the same name. If you overwrite the AndroidSDK one with the Moto one (keeping the same file name of fastboot.exe) it could be overwritten with a future update of the Android SDK. Because of this, some have renamed the Moto fasboot.exe to mfastboot.exe. So if when you see reference to mfastboot.exe, they are talking about the Moto tweaked version of fastboot.exe that has been renamed so as to not overwrite the one included with AndroidSDK. Simple, right?? :p

So, where can you get the Moto Fastboot.exe, or mfastboot.exe?

You can grab the Moto Fastboot.EXE from -> https://www.dropbox.com/s/kyqjzpjgamrepf1/fastboot.exe (Thanks to Cell Zealot) Note: you will want to rename this one before putting in your PlatformTools folder so future updates to the Android SDK doesn't overwrite it. Alternate download -> http://xdaforums.com/showpost.php?p=47191012&postcount=115 Another way to get it is to request the GSM Developer Edition recovery image directly from Motorola (HERE) as they recently added the updated fastboot.exe along with minimal ADB support.

I take no responsibility for any issues, errors, problems, etc. you encounter while attempting to unroot, get back to stock, etc or using these instructions. Please backup your data BEFORE you attempt anything below!!

How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8 users have had issues.

You will need...

To know what version ROM is on your phone before you touch anything. On Phone... App Drawer -> Settings -> About... Make note of the build number.

Motorola Device Drivers -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Adb Drivers, Android Platform Tools from the Android SDK, some good tutorials -> http://xdaforums.com/showthread.php?t=1830108 or see -> http://www.xda-developers.com/android/lightweight-adb-and-fastboot-installer/

Updated Moto fastboot if you will be doing things manually See above!

MicroUSB Cable.

NOTE: the GSM Moto X Developer Edition recovery image available by request from Motorola (HERE) has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need for the Adb Drivers and Android Platform Tools from the Android SDK.

NOTE2: The T-Mobile XT1053 Retail and Moto Maker versions use the same Rom/Recovery Image as the GSM Developer Edition X. The Verizon XT1060 Retail and MotoMaker versions use the same Rom/Recovery Images as the Verizon Developer Edition phones. The the recovery images are available by request directly from Motorola (HERE). Unlockibility of the bootloader is NOT part of the ROM or Recovery Images that we can flash, so flashing the Developer Edition ROM/Recovery images will NOT have an impact on unlocking your bootloader. This tip is just in case you would feel more comfortable downloading the ROM files directly from Motorola, or if sbf.droid-developers.org has problems again.

Then select from one of the following options...

Option 1 The "Moto X Tool Kit"

See -> http://xdaforums.com/showthread.php?t=2477132

It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for yor phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.

Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).

Option 2 Fastboot flashing individual parts of your phone's firmware.

This will not erase your data and apps. It is a good option if you are stuck in a boot loop.

If you already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept the KitKat OTA without losing data/apps.

You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.

You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.) See above.

Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)

steps would be... (mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)

Unplug phone

Power down phone.

Hold Volume Down and Power

After a few seconds release Power, you should be in fastboot menu on phone.

Connect to PC.

open command prompt file and change to the folder you unziped the ROM file to.

type the following, pressing enter after each command, and wait for it to finish before going onto the next...

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img

mfastboot reboot

phone should reboot and and be ready for the update.

NOTE: to combat a 401 ERROR while doing the update, some users have also had to flash do the following

fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn

See -> http://xdaforums.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)

Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings

NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.

Follow this guide -> http://xdaforums.com/showthread.php?t=2446515 using the latest ROM from your carrier. HOWEVER, before as part of STEP 4, while editing the XML file, also remove the line that says...

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

Failure to remove this line will result in your data/apps/settings being erased from your phone.

Option 4... Fully flash your phone using RSDLite

Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.

Follow this guide -> http://xdaforums.com/showthread.php?t=2446515 using the latest ROM from your carrier.

Option 5 Using mFastboot to manually flash your phone's firmware (without wiping data).

This is the same as using option 3, but usese Moto fastboot instead of RSD. This will not erase your data and apps.

You must already have ADB drivers and Platform tools from the Android SDK installed and in your path, along with the Motorola drivers already installed and working.

You must also have the updated Moto Fastboot.exe, renamed to mfastboot.exe, and in your path (it can be in your SDK/PlatformTools folder next to the standard fastboot.exe.)

Download the ROM image that your phone currently has from here -> http://sbf.droid-developers.org/ghost/list.php and unzip it to a folder your PC using WinRAR, 7Zip, etc. (unzip location does not matter, as long as you know where it is)

steps would be... (note: mFastboot command in these steps assumes you are using the updated moto fastboot.exe and have renamed it to mfastboot.exe, or downloaded the one already named MFASTBOOT.EXE)

Unplug phone

Power down phone.

Hold Volume Down button and Power button.

After a few seconds release Power, you should be in fastboot menu on phone.

Connect phone to PC.

open command prompt and change to the folder you unziped the ROM file to.

type the following, pressing enter after each command, and wait for it to finish before going onto the next...

mfastboot getvar max-download-size

mfastboot flash partition gpt.bin

mfastboot flash motoboot motoboot.img

mfastboot reboot-bootloader

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 reboot

The phone should reboot and and be ready for the update.

Main issues encountered during the Kit Kit upgrade install...

Boot loop while trying to install the update. This is usually caused by having used PwnMyMoto or RockMyMoto to root. Those tools replace the stock recovery which is needed to install the OTA. You must re-install the stock recovery with one of the above options.

Error 252 reported by the "update". Again this is related to having been rooted but not restoring to Stock

Error 401. One of your files still isn't stock. See the NOTE in option 2 above, or see -> http://xdaforums.com/showpost.php?p=47639731&postcount=315

Some apps haven't been upgraded to be Kit Kat Compatible... Foxfi, HBOGo, and others. You have to wait for the app vendor to update.

Some apps partially work.. WellsFargo app, I can't deposit a check via camera, but rest of app works. Again, we have to wait for the vendor to update it.

Hope this helps!!

EDITs & Updates: Here are a few more things found since the initial posting...

For those running the T-Mobile Pre-Release leak, I just wanted to link to this thread here -> Oficial tmobile KK over tmobile leak It pretty much summarizes the ability of using Option 3 and/or 4 above to flash TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_CFC.xml.zip over the leaked T-Mobile pre-release rom. (Thanks beelzebu)

There are reports of Verizon Moto X (non-developer) users who took the KK 4.4 update yet were able to flash back to the previous 4.2.2 w/camera fix rom. Please see -> [Q] Return to JB from kitkat on Verizon Moto X (locked) for more details.

Be sure to keep up on the [BOUNTY/PLEDGE/NON-DEV VARIANTS] ROOT 4.4 for MOTO X ($325) as there is some rumblings that a root for Non-Developer Edition KitKat 4.4 might be being worked on.

Tethering options for ROOTED KitKat 4.4 (currently limited to unlocked bootloader)... so far there are two....

On my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/

change device profile to galaxy nexus (cdma/lte)

check box: wifi-driver reload

check box: enabled routing fix

If you have troubles, its also suggested to...

check box: wifi-driver reload 2

(per -> http://xdaforums.com/showthread.php?t=2449534 )

See -> Native tether for VZW DE 4.4 <- This works for rooted with locked boot loader too!!

Root for KitKit users who have a locked bootloader has been released. See -> SlapMyMoto 0.5c Beta (4.4 root, RW to system) (thanks Jcase!!)

When I re-downloaded the GSM Moto X Developer Edition KitKat recovery image recently, available by request from Motorola (HERE) I noticed it has been updated to include the required files for ADB and the customized Moto Fastboot.exe. This could negate the need to download the Adb Drivers and Android Platform Tools from the Android SDK.

If you have a locked bootloader and/or rooted via SlapMyMoto, ModMyMoto, etc.... PLEASE WAIT ON ACCEPTING ANY NEW OTA Updates as they may break root.