yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] flashallthetime:
If you have any other question I started a thread http://xdaforums.com/showthread.php?t=2639102

Sent on my Gummy running Lenoto X
[Moto X Android Development] kpetrie77:
Nice thread, going to save a lot of headaches. Once point that differs particular to only this OTA is that it does not tamper with the su apk or binary or symlinks and you do retain root. I updated the OP with my results of testing the OTA with both Superuser and SuperSU.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] paranoid365:
That made me lol, thanx for 1st real laugh of the day :highfive:
[Moto X Android Development] flashallthetime:
This has been modified, the real ota does

Sent on my Gummy running Lenoto X
[Moto X Android Development] Jayrod1980:
With this patch you are incorrect. This patches files. It's not a full stand alone ota. You can keep root if you already have it.

---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------

This times 1000 which is why it's perfect for those who have locked bit and root on 4.4
[Moto X Android Development] flashallthetime:
It is patched this version, on the ota from motorola you can not keep root nor can you even flash the ota as it will fail

Sent on my Gummy running Lenoto X
[Moto X Android Development] Jayrod1980:
Serious, there are multiple people reporting it works. I flashed it with root, just not custom recovery, in fact it worked even with the GB 4.4.2 boot loader.
[Moto X Android Development] flashallthetime:
I understand in regards to this threads version, it works .but you cant flash the ota that your phone downloads from moto with root

Sent on my Lenoto A2109 tablet :) :)
[Moto X Android Development] Gus194:
Can I flash this if I'm on the GB 4.4.2?
[Moto X Android Development] Jayrod1980:
Well its crazy anyway. Anyone with an xt1053 should just unlock boot loader if they want root. At this point in the game, your phone either works or it doesn't.
[Moto X Android Development] kpetrie77:
Bone stock only. Edit: Retail.en.US
[Moto X Android Development] SymbioticGenius:
This is only a flashable zip? Are the fastboot files in there?

MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
[Moto X Android Development] kpetrie77:
This is the OTA downloaded from Motorola. Root was installed when it downloaded and still working after.
[Moto X Android Development] kpetrie77:
No, just patches and an updater-script unless you count the recovery.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] flashallthetime:
This is why people are screwing up there frigging phones, miss information, its only 147 mb its a patch that you use to flash the ota that allows you to maintain root, its not the actual ota. So what I said is you can not accept the ota untouched directly from Motorola and have it flash while having root stays as a fact

Sent on my Lenoto A2109 tablet :) :)
[Moto X Android Development] kpetrie77:
We may have a misunderstanding of terminology here. The OTA, from Motorola, consists of system file patches. If there is another OTA file, it would be beneficial to all for me to examine it.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] flashallthetime:
I just downloaded it, an people are going to assume they can flash the ota while having root, you can't. Unless you patch the files like you did, you touched the ota, yes. Understand. The ota directly from moto has no patches

Some folks aren't to bright and I'm tired of explaining to them why there frigging phones are boot looping after accepting the ota. Basically your version is an altered ota

Sent on my Lenoto A2109 tablet :) :)
[Moto X Android Development] kpetrie77:
Can you PM me a link to the file please?

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] SymbioticGenius:
Any T-Mobile fastboot flash files? I'm probably keeping Britain and just want the updated modem. Or more importantly I'm not updating unnecessary stuff.

MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
[Moto X Android Development] munchy_cool:
how is it altered ? I mean he downloaded the OTA, uploaded it to mega and then applied it on his phone. how was the OTA altered?
[Moto X Android Development] vikramkhalsa:
I'm on an unlocked bootloader and had root on 4.4. I went back to stock recovery, got the OTA directly from motorola on my phone and was able to take it. ( after I reflashed my system to get rid of xposed and other mods).

I should have checked if i still had root but I was eager to get back to TWRP which I flashed again, and it said i don't have root and asked if i wanted to root. I said yes and booted up, everything was back the way it was, still had super SU installed ( the same as before) and it still remembered all the various apps root privileges and all.. So not sure if it stuck or what but was easy enough to "keep" root after updating.

Just sharing my experience in case it helps someone.
[Moto X Android Development] Gundabolu SC:
You cant alter an ota and flash it unless it is signed again using motorola's keys!
[Moto X Android Development] inittowinit:
Sorry for the NOOB question, but how do I flash back to the stock recovery. I'm currently using twrp and I am rooted.

Thanks for the help.
[Moto X Android Development] geekabilly:
Get it from the sbf for the version you are on

tapped out via XT1053 DE

---------- Post added at 12:33 PM ---------- Previous post was at 12:32 PM ----------

Then flash it just like you flashed TWRP

tapped out via XT1053 DE
[Moto X Android Development] varxx:
I got a copy of stock recovery for TMobile's 4.4 by downloading the corresponding stock firmware from this link (one of the most useful pages on the internet, I might add):

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

Then I unzipped that file and simply copied and pasted the recovery.img it contained to the same directory where I had fastboot located on my computer. Then I did as geekabilly says and flashed the recovery.img file the same way I had previously flashed the twrp recovery ing file.

EDIT: If you've forgotten how you flashed twrp, you can look here:

http://www.theandroidsoul.com/new-t...orks-cool-with-android-4-4-kitkat-ota-update/

Elsewhere on this forum flashallthetime has posted a link to the stock recovery img file from Rogers. Check the initial post in this thread:

http://xdaforums.com/showthread.php?t=2639102
[Moto X Android Development] vikramkhalsa:
Thats what I did as well.
[Moto X Android Development] DanRyb:
Same here. Worked fine for me! Then used the OTA and then flashed back a custom recovery. :)
[Moto X Android Development] vikramkhalsa:
Yup! Pretty simple process overall :)
[Moto X Android Development] Cash Machine:
So I'm a little confused by the comments about how this is perfect for users with locked bootloaders and root. I am guessing that means only those that have used MotoWpNoMo?

I rooted following this guide, which avoids MotoWpNoMo in favor of the tweaked recovery that disables WP on reboot recovery. However, since that has replaced the stock recovery, I am unclear on how to move forward with the OTA as per the instructions linked in the OP.

Perhaps I can't? I'm assuming there is some way I can go back to stock recovery, but then I fail to see how I'll be able to disable WP when I need it.
[Moto X Android Development] kpetrie77:
Going to recommend you avoid this. I see where that root method changes some things around that seem kind of important. (One of the comments is write boot to recovery partition?)

Personally, I would unlock my bootloader and go from there to restore everything with stock 4.4 images. We took ownership of anything that could go wrong and kissing warranty good-bye by modifying the firmware anyway. Might as get the benefit of it and have a way to fix anything short of a screwed bootloader.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] Cash Machine:
I am coming around more to this way of thinking. At first I took comfort from the fact that my phone was still under warranty and could easily be restored to original stock if need be. Then I got increasingly more confused by the intricacies of all of these workarounds and tricks. Plus I was reminded that the beloved warranty won't cover any dings or drops, just defects which appear naturally. I guess there's a chance that the wood back will start peeling away someday or something like that, but I'm willing to roll those dice for ease of flashing.

So the steps as I see them are:

Create a full set of backups with Titanium, copy to a safe place [PC].

Follow "Returning to Stock" instructions listed here.

Unlock bootloader through Moto's website.

Take 4.4.2 OTA.

Install TWRP recovery per instructions.

Root via TWRP.

Restore backups with Titanium.

Do I have that right? And in the returning to stock step, I don't need to worry about first removing root apps or modified system files?
[Moto X Android Development] kpetrie77:
That is almost right. You'll need to unlock the bootloader first in order to return to 100% stock. Once you fastboot the boot.img, system.img and recovery.img onto your device, you are over-writing any changes made. For your purpose, that is back to stock. Having an unlocked bootloader lets you fastboot any recovery which is the golden ticket to root.
[Moto X Android Development] Cash Machine:
Thanks a million. I will definitely follow your guidance to the letter when I do this tomorrow after work.

Just for the sake of educating myself, however, what is the reason I should unlock the bootloader first, exactly? The guide that I linked above that originally gave me root had me do the same return to stock process to downgrade to 4.2.2 post-camera, and it worked fine without an unlocked bootloader. Again, just trying to understand what I'm doing a little better here.
[Moto X Android Development] kpetrie77:
Should work but a lot of extra steps. If you unlock the boot loader first then it is just a matter of using fastboot to flash everything without all the exploits.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] Cash Machine:
Great, that's actually a relief that I didn't completely misunderstand what I was doing! Your point about efficiency is well-taken, though.

One last thought: would there be any real benefit to unlocking, returning to 4.4, and then just installing a 4.4.2 stock rom instead of going the OTA route? My understanding is this would preserve my bootloader at still-downgradable 4.4, but since I'm crossing the bootloader unlock bridge anyway there is not a lot of benefit in that anymore; it's not as if I'll ever be in a situation where I want to apply the 4.2.2 root exploit when I could just do it with TWRP instead.
[Moto X Android Development] kpetrie77:
If you're talking about a "stock" aka someone made a flashable zip then you will not get the modem update that comes in this OTA. ROM's are typically system and boot only and assume the base firmware/modem is current. There is a lot more that goes into an update than just the ROM. Yes, this update includes a new bootloader that cannot be downgraded, but once the bootloader is unlocked that is not really an issue.

Not part of this conversation but if you want to learn...

You can modify the updater-script to do what you want, including leaving the bootloader as is, and even make the OTA flashable in TWRP. It will be under META-INF/com/google/android/updater-script. Bear in mind that changing the OTA needs a custom recovery to flash since it will not have the Motorola sigs.
[Moto X Android Development] Cash Machine:
Right on, I am definitely learning. Your modification of the updater-script is compelling, and I think I'll sleep on it. One way or another, I'll follow the steps laid out above tomorrow and report back [for posterity, if nothing else].

Thanks again. Conversations like this are what grow this community and make the sometimes daunting world of Android modification a little more palatable to somebody like me.
[Moto X Android Development] kpetrie77:
This should help: http://xdaforums.com/showthread.php?t=1931585

If you are going to make your own script, reuse the appropriate parts of the original script. PM if you need assistance.
[Moto X Android Development] kpetrie77:
Video added to OP.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] flashallthetime:
This will not work for any moto x phone , Rogers never received the 4.4 ota from moto. This is a small update that patches only certain folders within the existing 4.4 stock ROM.

Please to avoid issues we all need to put every once of info for the noobs to read in our op's. We have so many different variants of moto x's and this is causing a lot of miss information within the moto x threads

So anyone with a moto x on 4.2.2 can not flash this update, nor would I flash it if I was a European moto owner as the T-Mobile boot loader is 30.B4 and all European boot loaders are 30.B3

I appreciate the video, good job

Sent on my Lenoto A2109 tablet :) :)
[Moto X Android Development] Cash Machine:
Well, I followed the process as outlined earlier, and everything went according to plan. I now have an unlocked bootloader, TWRP, and root on 4.4.2 with all of my apps restored via Titanium.

I decided to hold off on modifying the updater-script for now. Maybe I'll play with that feature for a future OTA, depending on the circumstances.

The only odd part of the process was when I used fastboot to return to stock 4.4, the system no longer detected that the 4.4.2 OTA was available for download, insisting that 4.4 was the latest version. However, I simply flashed 4.4.2 via stock recovery as outlined in the OP and I was on my way.

Big thanks for everybody's contribution to this thread, and especially to kpetrie77 for the dedicated help.
[Moto X Android Development] kpetrie77:
Mirror added.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] kpetrie77:
Updated OP with very specific information although it was clear already from the title this is for the US XT1053 and it is an OTA not sbf.

We can't fix stupid, someone

will

try to flash this on another Moto X than intended, but hopefully that will lighten your workload in General and Q&A.

Thanks for the help.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] flashallthetime:
I appreciate that, my intension was never to piss you off, get you upset or start a war, just wanted to hopefully make evryones life easier:thumbup:

Sent on my Gummy running Lenoto X
[Moto X Android Development] crusher1908:
Force

I don't know if anyone have posted how to force this update but here's what i did.

1. Go to: Setings > About Phone > System Updates and let the system look for an update. If you get the typical meesage of "Your system is up to date" then go to the next steps, if don't, just ignore them.

2. Go to: Settings > Apps > All Apps

3. Search for "Google Services Framework"

4. Enter the app and Stop it and Clean the data

5. Turn Off your Moto X

6. Turn On your device

7. Some advices will appear as in "Please activate the Location Finder" or some stuff like that

8. Activate the services required

9. Go to: Settings > About Phone > System Updates

10. Voila!

That's what i tried and got success.

The method is just as same as the required to force updates on the Nexus devices.
[Moto X Android Development] kpetrie77:
Thank you. Yes, that does work, but there are other issues created. See Dan Morrill's comments on the subject here.

The OTA package is available, please sideload to avoid the issues Morrill discusses.
[Moto X Android Development] geekabilly:
Great reference, kp

tapped out via XT1053 DE
[Moto X Android Development] Iceman248:
I just tried this on my brand new GSM Unlocked phone that I'll be using on AT&T. I'm not ready to make the transition from my old Sprint phone and service yet, but I wanted to go ahead with the latest OTA before I go about setting up my phone, rooting, possibly unlocking bootloader, etc.

It doesn't work, even though I saw and followed everything in the list. Is this wise anyways? Will I be able to root just fine and all on the 4.4.2 even if I never had it on 4.4?
[Moto X Android Development] kpetrie77:
Once you go to Motorola's website and unlock the bootloader, root is easy as fastboot flash recovery and installing superuser.

Otherwise, you need to downgrade to 4.2.2, exploit to install a recovery, upgrade back to 4.4, then OTA. All this is while having a locked bootloader so you are in deep poop if something goes wonky.

Either way technically voids warranty. Short version, don't update if you want root and unwilling to unlock the bootloader.

Edit: Clearing data on GSF is not much of an issue if you have not setup your phone yet. Dan Morrill's post goes over the problem of doing so.
[Moto X Android Development] r_diaz13:
Is this rule of thumb? I tried and it didn't work for me. Not to worry though. I got the OTA that was captured saved in the phone already. Just waiting to Root first then upgrade.
[Moto X Android Development] kpetrie77:
Updates are provisioned by IMEI blocks. First 10K, then another 50K if there are no issues, then another 50K a while later and so on until the OEM or carrier decides to release for all handsets. This is done to prevent widespread issues. If your specific IMEI is not in one of the blocks that are released for an update, clearing GSF data does nothing.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] varxx:
Thank you for this very helpful info. I've always wondered how the OTA releases are distributed. Where did you learn this?
[Moto X Android Development] kpetrie77:
I was introduced to someone that handles device provisioning last year, came up in conversation about what we both did for a living.
[Moto X Android Development] jmcdonald58:
Thanks

Thanks for sharing went off without a hitch
[Moto X Android Development] needleyepoke:
I have a XT1053 with unlocked bootloader upgraded to 4.4.2. After regaining root I restored one of my 4.4 backups, worked fine. So my question was could I flash by fastboot just the boot.img and system.img of 4.4 boot into custom recovery, clear cache and data, reboot and be fine? I don't have any plans but I was just wondering
[Moto X Android Development] flashallthetime:
Yes and no no no no, if you flash the 4.4 IMG only, first thing is root will be gone, now here is what i was afraid of and listen closely. Your bootloader is now 30.B4, the new boot loader which can not be downgraded. If you go back to 4.4 you will receive the ota notification, you will inevitably take the ota, it will flash and when it reboots chances are you will hard brick your device

Sent on my Gummy running Lenoto X
[Moto X Android Development] needleyepoke:
Another question... I thought that motoboot.img was the bootloader and boot.img was the kernel... if not what is the difference?

sent from my XT1053 unlocked bootloader 4.4.2
[Moto X Android Development] Kenichi:
Any chance of reflashing the 4.4.2 OTA on my device already running 4.4.2 OTA update? I need to stop a force close of settings so that I can enter the permission section of my phone, beause I can't enable read/write for SMS Backup+.

Kenichi

EDIT: Stupid question, 4.4.2 has disabled accessibility to the section of the app, therefore, I will have no ability to change this settings.
[Moto X Android Development] kpetrie77:
No, the updater-script will fail on assert for /system/priv-app/PlusOne.apk

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] flashallthetime:
Motoboot is the bootloader

gpt.bin is partition

Boot.img is the kernel

Sent on my Gummy running Lenoto X
[Moto X Android Development] kpetrie77:
Just did this successfully on mine after rechecking the contents of the OTA and attached updater-script to make sure. Flashing boot and system only then taking the OTA is fine this time, but that is definitely the exception and bad practice. Obviously root is lost.

Don't count on doing this with future updates. Best practice is to flash all required partitions from the sbf. You never know what all is required or not required for an OTA to successfully flash until you go through the OTA zip contents and updater-script. Most people have no idea what they are looking for anyway.

http://xdaforums.com/showthread.php?p=50165820

Edit: flashallthetime answered the boot question.
[Moto X Android Development] kpetrie77:
Ah. Try going under your main settings > more and set it as the default SMS app. Then try to backup/restore. I had to do this with Helium on my HTC One 4.4.2 update to restore messages.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] Kenichi:
I wish! SMS Backup+ cannot do that without permission. All well, :( Least I can do right now is just backup my messages. Not a big deal. Just inconvenient to a degree.

Kenichi
[Moto X Android Development] Iceman248:
Okay. So what I should do then is update to 4.4.2, then unlock bootloader and flash recovery and superuser to achieve root?
[Moto X Android Development] kpetrie77:
If you need root and are good with unlocking the bootloader, that is the easiest way to proceed.
[Moto X Android Development] Kenichi:
Found an alternative solution! Quite useful actually. App called "Apps Ops X" free on Playstore, you need root access but it will recreate an enviornment similar to native Apps OPS and function accordingly.

Kenichi
[Moto X Android Development] piccit:
As long as you're taking the OTA that installs the bootloader that you already have, there is never a problem with this. (the problem is when people take old OTAs that actually try to downgrade their bootloader)
[Moto X Android Development] mrvirginia:
uhhh so i have a question. how come no one has taken the OTA apart and repacked it so it just updates system files instead of bootloader, etc? in doing something like that, you could then pull the /system and create a stock ROM...
[Moto X Android Development] sdxda:
Can someone verify that I digested all the information in this thread correctly?

I have an unlocked bootloader on tmobile Moto x. I installed twrp so I have a custom bootrom. I then installed stock 4.4 from tmobile manually. But since I got root from twrp, this is not considered a stock rom anymore? In addition, since I installed xposed, this is even more a custom rom. So even though I flashed a stock ROM and I am getting the OTA message every 5 minutes, I really have a custom ROM which I made, and therefore I cannot upgrade OTA or manually.

So my best bet for upgrading to 4.4.2 without losing my data is to go to KANGAKAT?

My biggest confusion is that I have a stock rom flashed. But it sounds like when people say stock, they mean more than just the rom.
[Moto X Android Development] cannondale0815:
I applied this update on my dev edition and all went well. The only issue I am having is that I cannot switch to ART. When I try, the phone reboots but is still on Dalvik. Tried clearing caches and also reverting to stock recovery, but no go.
[Moto X Android Development] kpetrie77:
Flashallthetime has a great info Q&A thread here. Root is okay on this one, but avoid the OTA with Xposed. Your options are go back to stock and OTA 4.4.2, flash another ROM from TWRP, or wait for the full system and boot images for the XT1053 from Motorola and flash manually like you did with 4.4.

You should be able to disable the OTA notification until you make up your mind of course of action. One of the 3c apps, not 100% which one, but try disabling 3c_ota.apk first. In adb shell it would be pm disable com.motorola.ccc.ota or use an app to freeze it. If you still get a notification also look at 3c_notification.apk (com.motorola.ccc.notification).
[Moto X Android Development] kpetrie77:
If you want to do this, I'll link it in the OP.