yashsingh1/xdaforums huggingface dataset:
[Moto X General] KidJoe:
I think what jimmydafish is saying is that clearing the cache isn't really needed. Sure it will remove the OTA download file which will stop the reboots (until the update downloads and tries to install again).

The main fix is to "unroot" by flashing the stock recovery. I had to also flash boot and system.

So rather that wasting time going into fastboot menu, erasing the cache and rebooting, then powering of, going back into fastboot to flash the 3 files... just fastboot flash the 3 files, and reboot. The installer will be able re-run without boot loop as the OTA Update file is still in the cache, and the stock files have been put back where they belong.
[Moto X General] jonnythan:
Seems identical to the previous version.
[Moto X General] 640k:
While I can't confirm what actually comes on the ROM, anything I've previously uninstalled didn't come back and everything else stayed frozen.
[Moto X General] lowvolt1:
Wait until phone boots. Go to cache and delete the update. No more constant reboots.
[Moto X General] travishamockery:
When I fastboot flash recovery I keep getting this error. Anyone know why?

(bootloader) Preflash validation failed
[Moto X General] whitlecj:
Tesla unread count doesn't seem to. Be working for me after the upgrade. Running beta 3 of nova. Is it working for anyone else?
[Moto X General] jmill75:
Mine is screwed up. Bought the phone off someone tonight. Got home connected to WIFI, update downloaded. It went to Android recovery. I clicked reboot and now the phone will not boot. Sits at Moto screen. I can get into FastBoot but thats it. No recovery at all. Can anyone assist me in fixing this??

Thanks
[Moto X General] Verttex:
I also have this problem.
[Moto X General] jonnythan:
If you can get into Fastboot, you can use RSD to flash the full system image. Get the image here:

http://sbf.droid-developers.org/ghost_rcica/list.php
[Moto X General] jmill75:
I have downloaded both of the versions from that site. It gets to 7/17 flash system and says error. Any ideas?

Edit: I tried a 3rd time and it went through! Yay
[Moto X General] a1exus:
Did you did anything else other then trying again?
[Moto X General] jmill75:
I tried the 2 from the site then tried the KitKat download (link on Droid-Life) then tried the newest version from the site again and it worked.
[Moto X General] gueszman:
Hey what about performance? Is it fast? Better than jelly bean? is it Worse? Worth it? ....

Sent from muy Moto X
[Moto X General] jonnythan:
Performance seems about the same to me, and I'm very conscious of interface lag.

Definitely worth it, if just for the dialer and drag-to-focus-and-set-exposure camera.
[Moto X General] gueszman:
Could you post an image of the new camera interface?

Sent from muy Moto X
[Moto X General] racer83l:
I had a nexus 5 for a bit.. With it, when you were in the dialer and searched something, it searched Google for the results.. The moto x doesn't seem to be doing this for me. Can someone confirm if their phone is the same way??
[Moto X General] k3ff0:
How is working the phone with this update? It is faster and smoother? And the battery life?
[Moto X General] jonnythan:
You can drag the focus box around. It will set focus and exposure based on what's in the box.

Moto X on Verizon
[Moto X General] jonnythan:
Same way. Some people are complaining about it.

Moto X on Verizon
[Moto X General] ClippinWings:
I don't have Verizon... But some experience...

Others have said performance is about the same.

We won't get any realistic battery assessments for a couple days.

Sent from my MotoX, using TapaTypo
[Moto X General] gueszman:
Seems to be useful. I'll wait for the update. Thank you jonnythan.

Sent from muy Moto X
[Moto X General] colinj22:
Please help

I have tried fastboot flashing recovery and it will not work. It just keeps on repeating preflash failed. Please help me!!!
[Moto X General] droe411:
Weird, that was the way the camera looked like in the first At&t leak. When they sent an OTA after that, the drag to focus feature went away.
[Moto X General] I Am Marino:
This is pretty shocking, Verizon doing anything first.
[Moto X General] a1exus:
I'm sure I'm saying on behalf of a lot of folks out there:

Thank you to Verizon Wireless for finally getting and Motorola (Google) for such a super fast delivery of Android Kit Kat 4.4 to my Moto X!

I personally didn't update my phone just yet (but really want too) is due to root, so i now between switching phone to kit kat or keeping root? so far root won, but for how long?) I paid full price for my phone and I do not have warranty through Verizon Wireless, so why can't I have root? Why is my bootloader is locked?! I thought Moto X is a "Global Phone"! What is "Global Phone" anyway?

I guess it's possible to downgrade if I can't live w/out root) (at least try it out)).
[Moto X General] skatewiz722:
dialer problems?!?!

is anyone having trouble with the dialer? I know with the nexus 5 you can look up businesses and such from the dialer. With the moto x you cant. anyone know why??
[Moto X General] Ianxcom:
Anyone else find the new touch tones quite annoying? Its like a woman walking in heels on a hardwood floor.
[Moto X General] Zackcez:
The easiest way to accept the update would be to download the 57 fxz file and flash it through rsdlite. That will for sure work.
[Moto X General] tgerbracht:
This is the first time I haven't felt compelled to root or modify my phone at all. Bravo Motorola, Bravo Android!
[Moto X General] MustWarnothers:
Has anyone tried sideloading the Nexus 5 Wallet to confirm if the emulated secure element allows tap to pay?

Also as a sidenote to you Moto X users (I'm debating between this and the Nexus 5 off contract), how is the GPS performance on this phone? I've heard bad things about the LG G2's GPS, but Motorola tends to use good quality sensors and radios.
[Moto X General] 640k:
see here:

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

short answer: yes, it works.

---------- Post added at 09:05 AM ---------- Previous post was at 09:05 AM ----------

except for ads (and possibly lack of tethering), i agree.
[Moto X General] phositadc:
Can you set exposure and focus on two separate points?

Sent from my XT1053
[Moto X General] jonnythan:
Not that I can figure. Nor can you adjust exposure up or down, or manually set ISO. Both of which annoy me greatly.

---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------

I rooted mine an hour after I got it. I unrooted to take part in the soak test.... and noticed that there was nothing at all I missed. The stock experience is fast and functional.
[Moto X General] phositadc:
I couldn't figure it out either, but the release notes made me think it should be possible.

Oh well, release notes were probably poorly written.

Sent from my XT1053
[Moto X General] halfsquatch:
update fails on unlocked Moto X (officially unlocked)

I have a Verizon Moto X unlocked phone with TWRP. Attempting to upgrade to Kit Kat failed with the following errors:

Installing '/cache//Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip'...

Checking for MD5 file...

I:Cannot find file /cache//Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip.md5

Skipping MD5 check: no MD5 file found.

I:Zip does not contain SELinux file_contexts file in its root.

installing gptupgrade updater extensions

installing BL updater extensions

script aborted: This package is for "ghost" devices; this is a "xt1058".

This package is for "ghost" devices; this is a "xt1058".

E:Error executing updater binary in zip '/cache//Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip'

E:Error installing zip file '/cache//Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip'

Done processing script file

It went into a boot loop until I moved the zip file to /sdcard/.

Uggg.... I guess Moto changed the device string when I unlocked the boot loader. Is there any way to change it?
[Moto X General] a1exus:
how do I downgrade to 4.2.2 using adb/fastboot. I already downloaded 4.2.2 firmware.
[Moto X General] KidJoe:
are you trying to install via TWRP? I think you can only do it via stock recovery.
[Moto X General] tgerbracht:
Couple bugs pure stock never modified X:

-Google music unavailable (on device). Had to reboot.

- Notifications not disappearing from the status bar when they were deleted or dismissed. Causing a soft reboot

I might have to do a factory reset after all after this update.
[Moto X General] aooga:
Does the device string change using moto's official bootloader unlock, or just the verizon hack? I plan to unlock my tmobile one, but if that screws up OTA's forever, then I might have to find a different way.
[Moto X General] jayboyyyy:
can't downgrade if you already took the 4.4 ota on a locked bootloader.

---------- Post added at 12:52 PM ---------- Previous post was at 12:51 PM ----------

not possible to downgrade after you take 4.4 on a locked bootloader.
[Moto X General] a1exus:
I didn't install 4.4 just yet, I'd like to make sure I can go back to 4.2.2 (root->tethering) if I have too.
[Moto X General] jayboyyyy:
im not certain, but i think that you can't take otas on a rooted device even though you have a dev edition. i could be wrong but i don't think so. I think you may just need to make all your backups or whatever. go back to stock 4.2.2. take the ota. then unlock,install twrp, reroot, etc. then go back and restore all your backed up info. This might be wrong but I don't think it is. With some unlocked phones like the nexus i don't think it matters, but unless verizon released a dev ota as well that doesn't do security checks, then you will have to unroot and install 4.2.2 fw back to stock before taking ota.

---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------

well know need to make sure, because you can't on a locked bootloader. it puts security checks in the bootloader that you can't remove to make sure you can't downgrade. if you have an unlocked bootloader, then you are good to go and can do what you want.
[Moto X General] chaoslimits:
I thought Vzw model was XT1060?

Do you know of anyone with an unlocked bootloader being able to accept the OTA? My Vzw X is a Dev Ed but the bootloader was not unlocked.
[Moto X General] KidJoe:
It is, but at one point during the root process last night (On my VZW Dev Edition with unlocked boot loader), the windows saw my XT1060 as an XT1058 and failed to install drivers (I needed to manually pick Motorola Moto ADB Composite Interface to finish the steps).

unlocked boot loader shouldn't prevent OTA from coming down. However, the other caveats will apply.. (need to be "stock", have stock/factory recovery, all bloat restored, etc).
[Moto X General] jayboyyyy:
and once you get stock, you can just put the OTA file on the phone and go into recovery and update it yourself manually. takes less than time then trying to figure out how to get the "check for updates" button to actually find the update.
[Moto X General] yopete525:
Apologies if this has been asked before, but I looked through the entire thread and couldn't find anything. I'm running a rooted 4.2.2 VZW Moto X (not the dev version), and froze a bunch of the system apps. I haven't taken the first camera OTA because I didn't want to lose my apps/data (previously I thought the only way to preserve my apps/data was to restore them with Titanium), but it seems like this "fastboot" flashing stuff can work around this (I haven't had an Android phone in 2 years, and don't remember this method from before with my Droid Incredible).

A few questions:

1. Can someone explain the fastboot flashing method to me, or forward me to a link with more information on it? (Bearing in mind I hadn't even heard of it until this thread. My computer is also a Macbook Pro)

2. Will I have to restore the frozen system apps first, and then do the fastboot recovery, get the camera OTA, and then get the 4.4 OTA? Or can I just do the flashing, get the camera OTA, and then update to 4.4?

I'm aware I'll lose root by updating to 4.4, but the only reason I wanted to retain it in the first place was to be able to restore my apps/data. Thanks for any help you all can give me.
[Moto X General] KidJoe:
#1. fastboot flashing allows you to flash one partition or data area of the phone at a time... manually. Its instead of using RSDLite and an FXZ (rom) file to flash everything, clear all settings and data. Someone described RSDLite as a "gui" interface to Fastboot, since the XML file in the FXZ/ROM file contains all the fastboot commands.

How to do it on a Mac, I don't know. If there are instructions for using RSD you could just edit the XML line to remove the like that erases the USERDATA area, and flash the FXZ.

2. Depends on how you froze them. If you did it the "built in" way... Settings -> App Manager, and hit the apps and selected DISABLE, they can stay disabled. If you used Titanium Backup to freeze, then you need to unfreeze them first, or the update will fail.

I do not know if the OTA will update the pre-camera ROM, or if you must already have the camera update ROM installed.
[Moto X General] emaculant29:
Vz moto x w tmobile cant send sms

I want to see if anyone else is getting this bug. I have a deve version of the vz moto x, and upon updating to kitkat I know have access to LTE but seems I can send SMS or MMS unless I'm on either hspa 3g or edge. I can force it on either by trying to make a call and after it fails I can send a SMS. I rec SMS and calls fine, and vz has disabled the option to add a manual APN the #*#* is disabled and even a app I use to use to toggle Gsm LTE CDMA etc once toggled Gsm only it still in areas of LTE gives me just LTE. Is anyone else getting this, and if so is there a workaround before trying to wait for a root and flash a another ROM ?
[Moto X General] yopete525:
WELL, it turns out I really ****ed up my Moto X because I backed up and then uninstalled the system apps I didn't want using Titanium Backup, rather than just freezing them:

Backup Assistant Plus 4.2.2-5

Backup Assistant+ Contacts Client 1.0

com.android.browser.provider

Email 4.1

Mobile Hotspot 1.0

NFL Mobile 6.5.1.1

Verizon Tones 5.1.4

Voicemail 2.0

VZ Navigator 9.0.2.36

Through the research I've done, it seems like the only way I'll be able to get these back (and hence be able to install the camera OTA, and then the 4.4 update) will be to flash the stock images on the phone, wiping all of the storage. Is there any way for me to retain backups for my apps doing this (e.g. by transferring them to my computer)? Also, how exactly do I go about flashing the stock images? I'm on a mac.

Thanks again for the help.
[Moto X General] natezire71:
If you wish for root, please post pledges here: http://xdaforums.com/showthread.php?t=2536089
[Moto X General] jayboyyyy:
flash system and recovery images in fastboot
[Moto X General] a1exus:
system wont flash

mbp:VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml alexus$ fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 48.784s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 49.184s
mbp:VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml alexus$
[Moto X General] jayboyyyy:
try different fastboot

http://xdaforums.com/showthread.php?t=2489249
[Moto X General] alex94kumar:
do this:

fastboot oem fb_mode_clear

fastboot reboot-bootloader

then using the motorola fastboot binary install the sbf files
[Moto X General] Jaime88:
you still need help

mine did the same would power on then about 30 seconds reboot. the way i got it working was a full factory reset. i had to use a tool kit to return back to a working state. the only way i found of fixing that problem
[Moto X General] halfsquatch:
I willl the stock recovery, flash it, and try this again. I can always put TWRP back. I will post back to this thread with the results. Cross your fingers!

---------- Post added at 09:57 AM ---------- Previous post was at 09:47 AM ----------

You shoulldn't have to factory reset. I had the same issue. If you have TWRP, you can use the file browser in the Adbvanced menu to move to Blur*zip update file from /cache to /sdcard. When it trys the update again, it will throw an error and stop trying to update the ROM.

I hope that helps. Factory resets are time consuming....
[Moto X General] KidJoe:
You need to be completely stock and unrooted to take the update.

If you don't have the Developer Edition with unlocked boot loader, you can't put TWRP back on after taking KitKat
[Moto X General] KidJoe:
Did you try flashing boot, system and recovery... then doing the OTA?
[Moto X General] halfsquatch:
This could be the issue. I only flashed the recovery manager and not the system. Do I need to reflash boot too? Apart from unlocking hte bootloader, which wiped my phone, I haven't messed with the bootloader.

Finally, sorry if this is a dumb quesiton, but is flashing the system distructive to my settings or is it like an update--preserving my settings. I assume it's the latter.

I got used to CyanogeMod on my Galaxy Nexus where I didn't have to jump through so many hoops :-/
[Moto X General] yopete525:
Can you point me in the right direction for doing this on a mac?
[Moto X General] halfsquatch:
I put back TWRP and got the errors from /cache/recovery/last_log.1. I am posting them here for posterity:

Finding update package...
I:Update location: /cache/Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
installing gptupgrade updater extensions
installing BL updater extensions
failed to stat "/system/recovery_update.txt": No such file or directory
file "/system/recovery_update.txt" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
Updating new recoveryfailed to stat "/system/recovery_update.txt": No such file or directory
file "/system/recovery_update.txt" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file

I am travelling now, so I will have to get back to this when I have time. For now, I will put SuperSU back on and get on with my life

:-|
[Moto X General] jayboyyyy:
search how to fastboot on a mac. there are many threads on the topic plenty of places. also you may want to try and get the motofastboot for the mac (which probably wont be addressed in whatever thread you find because it applies to motorola phones only). Here is a link to motofastboot stuff.

http://xdaforums.com/showthread.php?t=2489249
[Moto X General] SQFreak:
I tried that on my unlocked VZW dev ed; no luck:

I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/T0620054QY'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
installing gptupgrade updater extensions
installing BL updater extensions
script aborted: This package is for "ghost" devices; this is a "xt1060".
This package is for "ghost" devices; this is a "xt1060".
E:Error executing updater binary in zip '/sdcard/Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip'
Error flashing zip '/sdcard/Blur_Version.139.15.1.ghost_verizon.Verizon.en.US.zip'
Updating partition details...
I:Data backup size is 750MB, size: 26957MB, used: 1166MB, free: 24348MB, in data/media: 416MB.
I:Set page: 'flash_done'
I:Set page: 'rebootcheck'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Rebooting...

I ended up downloading the full system image from http://xdaforums.com/showthread.php?t=2535707 and flashing that in TWRP, which worked fine. This was after I had already flashed stock bootloader, system, and boot, then tried the OTA (failed; error 450), then tried the manual download of the OTA zip and flashing that in TWRP (failed, above error). There's no modem in the full system flashable package yet, so I'll just wait on that.
[Moto X General] KidJoe:
Please take a look at -> http://xdaforums.com/showthread.php?t=2536735 Start at the top, then scroll to Option 2.

---------- Post added at 09:26 PM ---------- Previous post was at 09:22 PM ----------

What ROM do you have on your phone now? Is it System Version: 139.15.1.ghost_verizon Build: 13.9.0Q2.x-116-MX-17-57-x-1 (the camera update ota). Or the older, pre-camera update OTA?

If its 13.9.0Q2.x-116-MX-17-57-x-1, then also hit http://xdaforums.com/showthread.php?t=2536735 and use option 2... then take the OTA Update.

Another option might be (which I haven't tried).... Hit http://sbf.droid-developers.org/ghost/list.php.... Grab VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip unzip it, edit the XML to remove line saying... <step operation="erase" partition="userdata" /> and flash using RSD...
[Moto X General] lowvolt1:
If your on vzw you can
[Moto X General] SQFreak:
I had the camera update OTA. Actually, what I did was download the camera update OTA FXZ and flash that system in fastboot, then try to take the OTA.

The method I described was giving me crashes when I tried to go into Settings * Security, so I gave up and decided to FXZ using the 4.4 FXZ. Oy. At least I'm starting clean... The system was in a super messy state because I rooted pre-camera update, then somehow installed the camera update (I don't remember how) keeping root, the unlocked the bootloader. It's probably for the best, though I do wish it hadn't wiped userdata.
[Moto X General] jayboyyyy:
you cant just go into twrp and then flash a zip that was made for stock recovery on the phone. that is why it didn't work. you would have to flash the zip with stock recovery.
[Moto X General] skatewiz722:
google now hotword problems???

Is anyone having problems with the google now hotword? whenever im in the google now app and when I say "okay google" the voice search doesn't pop up like it did in the past. anyone having this problem?

in the settings it says "google" is the hot word but that doesn't work either.
[Moto X General] jonnythan:
It's OK Google now.

Moto X on Verizon
[Moto X General] skatewiz722:
yes, i know that. That opens touchless control though. when your in the GOOGLE NOW APP you cant say "okay google" anymore to make the regular voice search pop up.
[Moto X General] kolomanschaft:
Flash system

I had exactly the same problem. Flashing the system image solved everything without harming any apps/data/settings. After that I sideloaded the 5.0.1. OTA using stock recovery and everything was fine.
[Moto X General] monkeypaws:
Just to show some similarities. With then HTC one the Dev edition was not the first to get their 4.2 updates nor their 4.3 . I think we have a wrong idea of what a Dev edition means. Seems a few carriers don't consider them first come first serve.
[Moto X General] strictlyphat:
Mines coming in now. 13℅ lmfao!
[Moto X General] 640k:
SON OF A BISCUIT here comes mine too!!!!