yashsingh1/xdaforums huggingface dataset:
[Moto X General] jcrss13:
I ran the command got the appropriate response back, took the update, installed superuser (superSU will not work because it cannot update binaries) and installed Xposed, which is NOT working. I'm assuming this is because you lose write permissions with the update?
[Moto X General] liveMike:
My bootloader is unlocked. The reason I have the hack for wifi tether is that the xposed wifi tether was not available at the time. I do have xposed though for gravity box. when i get 4.4.2 i will just used xposed for it.
[Moto X General] KidJoe:
UGH.. we do need to split Locked vs Unlocked into seprate threads.. I forgot you had unlocked/dev edition!!

---------- Post added at 03:22 PM ---------- Previous post was at 03:18 PM ----------

It comes down to personal choice. :D Me, I don't want or need to install Xposed, Gravitybox, etc.. I don't feel like having to mess with changing the entitlement APK... I use Wifi Tether For Root on my older phones, and that is what I still use on my X :D

Yeah, I got a Dev Edition X because I knew I always wanted root. So some of this locked booloader stuff is getting confusing. Especially with the initial reports early in this thread about looked bootloaders keeping WP Enabled after taking the update, which were later proven wrong.
[Moto X General] evandena:
Non-DE, does 4.4.2 update replace hosts file? Or, can R/W be turned on for /sys so I can update hosts between reboots? All I really care about root for is ad blocking.
[Moto X General] Bionic75:
Rooted 4.4 back to stock then OTA

I've been reading through this thread and several others, so forgive me if this was mentioned before and I missed it.

I have a Non-Dev VZW running 4.4 rooted, if I RSDlite back to 4.4 stock recovery and system then take the OTA should everything work fine?

I used MotoWPnomo to root along with Jcase's awesome help and I heard that MotoWPnomo was a permanent "hack/step," is this true?

I just want to go back Stock everything and I want to be as careful as possible. I'm done rooting, it's becoming such a pain anymore..ugh.
[Moto X General] evandena:
I haven't tried it yet either, but that's my understanding as well.
[Moto X General] KidJoe:
Yes, RSD will work to get back to where you can take the OTA. BUT if you want to flash just stock recovery and system, use mfastboot instead. But yes that will get you back to a state where you can take the OTA.

To repeat...

If you have a locked bootloader and take the 4.4.2 update, you might retain root, but no, MotoWpNoMo is not permanent when you take the 4.4.2 OTA. You will lose the Write Protect Disable that MotoWPNoMO gave you (i.e. WP becomes re-enabled), meaning you can no longer permanently write to /system and the like the way you could before.

And once on 4.4.2, do NOT attempt to downgrade your rom!
[Moto X General] Teksu:
If you like root and being able to write to system, stay on 4.4

4.4.2 turns back on WriteProtect

Root can be retained, however you will not be able to write to the protected system, thus the binary cannot be updated for SU.

Xposed will work after "soft reboots", but if you do a full power cycle, the modules will become disabled.
[Moto X General] KidJoe:
Teksu, you have a locked bootloader, or unlocked? Just asking because i have an unlocked and so the stuff about Xposed after 4.4.2 on locked bootloader is turning to mush inside my head.
[Moto X General] cveez11:
Dev edition. Unlocked. I used rsd lite to go back to stock 4.4. Took the ota. Installed twrp and root. Took about 5 to 10 minutes. Hard for me to understand why anyone would buy non dev edition.
[Moto X General] kbluhm:
Huzzah! The headaches that could be avoided for an extra 50 bucks.
[Moto X General] KidJoe:
For those of you joining late....

In order for an OTA to successfully install you need to undo the tethering hack, any other modifications you've made (including Xposed) and get back to as close to stock as possible. This is because the OTA includes a manifest file which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail.

You must also have the stock recovery on your phone. Again this is needed and the update will fail if you don't have it. If you don't have stock recovery installed, you could get stuck in a boot loop.

Now that is common for all Moto X phones.

Here come the somewhat confusing part for this thread...

If you have a developer edition X for Verizon you have the ability to unlock its bootloader.

If you have a retail or Moto Maker X for Verizon you have a LOCKED bootloader.

This is important. The information about root and write protection for locked vs unlocked is different! and therefore so is the information about taking the OTA

Because it is getting confusing in this thread, IF YOU HAVE A LOCKED BOOTLOADER PLEASE SEE THE THREAD started by tekhna -> Verizon 4.4.2 OTA discussion for LOCKED bootloaders Its initial post contains some valuable information.
[Moto X General] kwyrt:
A lot of the people on non-dev edition phones (like myself) likely are on contract and used their carrier subsidy to purchase their phone. However, I am strongly considering selling my non-dev and putting the proceeds toward a dev edition. :D
[Moto X General] kbluhm:
Fair point. :P
[Moto X General] KidJoe:
I completely understand why some have the non-Dev edition. When I got mine, the Dev Edition was $649. Way more than the "with contract" price at the time. I know quite a few who couldn't justify that price difference. My wife was one of them. she thought I was crazy!!

I knew this day would come, and I wanted root, so it was worth it to me. Thankfully I was in a position to get the Dev Edition.
[Moto X General] Mike7143:
So... all this talk about not being able to downgrade from 4.4.2 back to 4.4 and how it'll brick you if you do. This applies to non-unlocked devices only right? I mean, if I update to 4.4.2 on my dev edition and for some reason wanna go back, I would just fastboot the images or SBF and be good to go right?

EDIT** Also, pleasantly surprised to see an almost 50/50 split on dev and non-dev Moto X users, however, then I remembered I'm on a developers forum, the sample is all wrong lol. carry on!
[Moto X General] Cozume:
Got it!
[Moto X General] kbluhm:
You should be able to adb sideload the update.

I am wondering if it's a similar procedure to the steps in this article:

http://www.androidpolice.com/2013/1...16s-ota-manually-root-or-unlock-not-required/
[Moto X General] rda990:
Oh ok. No problem.

Perfect thanks!!!!

---------- Post added at 03:33 PM ---------- Previous post was at 03:30 PM ----------

https://www.dropbox.com/s/o4abwshkxf25kcp/Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip Mirror
[Moto X General] aFancyTickler:
(NON DEV) Guys i can confirm root survived the ota to 4.4.2

https://drive.google.com/file/d/0B6FCm9ji-ZuET1RpR053WmNxUlk/edit?usp=sharing

https://drive.google.com/file/d/0B6FCm9ji-ZuEUXNFVjdfbjg0M3c/edit?usp=sharing

Awesome for us :D
[Moto X General] ballisticn8:
Have any non dev edition phones with 4.4.2 been able to keep root access? Just wondering since someone or someones seem to have pissed off jcase, not sure if he'll be putting any time into finding a root exploit for moto x users anymore...
[Moto X General] tcrews:
Cool...didn't lose root updating either (Dev Edition).
[Moto X General] rda990:
Can't you just put it in the root of storage, boot into stock recovery and update from there? That's how I did it back on my Droid Razr

You flashed stock recovery right? & updated from recovery or the OS?
[Moto X General] KidJoe:
JCASE has already said he doesn't have time and wont be looking at 4.4.2 (in another thread).

I have a DE X, so I can only say I've read in some of the threads from the carriers that received the OTA, those with locked bootloader have reported keeping root, but losing write protection disable... meaning they have root, but can't write to /system thus making root pretty worthless. Unlocked bootloaders have reported keeping root and R/W system access
[Moto X General] aFancyTickler:
uh i always had my stock recovery. so didnt have to reflash it. just installed the update from the OS . make sure you unfreeze any apps and turn off xposed framework if you have it
[Moto X General] Cozume:
Does Dev Host have a download limitation on it?
[Moto X General] aFancyTickler:
I kept my R/W system access . ;P
[Moto X General] whatnow275:
Noob question but I'm rooted and using xposed. How do I return to stock root so I can install?
[Moto X General] KidJoe:
Locked or Unlocked bootloader? If locked that is very cool and first report I've seen. If Unlocked, that is what should happen.
[Moto X General] aFancyTickler:
locked bootloader.
[Moto X General] Cozume:
Does Dev Host have a download limitation on it? Because I just signed up for Drop Box and can post a link to it.
[Moto X General] aFancyTickler:
just go into xposed and unistall it then take update. root will last thru update
[Moto X General] KidJoe:
Very nice. You are the first I've seen say it stayed with a locked bootloader.
[Moto X General] krazie1:
No devhost does not have a limit, also thanks for the link guys.
[Moto X General] balleron24z:
Thanks to those who were fortunate enough to get the update and provide it for those of us who are too lazy to fight Moto's block on rooting. That's the only thing I miss about my Gnex, and I wish I would've gotten a Dev edition, but oh well. Thanks to you all!
[Moto X General] Restola:
For those with unlocked bootloaders flashing twrp-2.6.3.1-ghost-4.4.img worked great to restore root.
[Moto X General] Reserved Name:
Wifi Tether without Write Protection

I'm going to take the OTA from 4.4 to 4.4.2 as the only thing I use root for is the wifi tether. I am concerned about keeping root though, was using OTA Rootkeeper or SuperSU Pro necessary or does the root stay on its own? I don't use the tether hack, just the Wifi Tether apk but I'm not sure if it needs write protection or not.
[Moto X General] Eighthourblink:
Having trouble appling update

Tried to apply update and I'm getting an error:

basicdreams.apk has unexpected contents

Does anyone know what this means?

Is it really worth updating if I use Xposed?

Thanks
[Moto X General] whatnow275:
So will greenify and app ops work with root on 4.4.2 w/ Write Protection enabled? Those are the only two reasons I'm rooting.
[Moto X General] :
Downgrading on locked, unlocked, regular or Dev edition devices is all the same thing...playing with fire.

Not advised if you value your device.

And to all again: a dev edition is the same as any other Moto x that you can unlock. All the same rules of flashing apply.

Dev edition means you keep your warranty when you unlock.....

Nothing more.
[Moto X General] syntrix:
Non-DE.

I did do the superuser survival mode thing. You don't have to pay for it, there's an option at the bottom of the settings. I would still buy it as a "donation" later though :)

Haven't read all the responses here, but that's my story, and I kept root. Also, the first time firing up the Wifi Tether apk, it worked, but closing it and getting regular wifi data to work required a reboot. Haven't used it since, but at least I know it works with a read only /system and root now.
[Moto X General] Eighthourblink:
I have a locked bootloader
[Moto X General] seandarcy:
I'm on VZW DE 4.4. Unlocked, rooted. TWRP recovery, su installed. Also Xposed. In addition, I replaced the unlocked warning boot screen with a moto screen.

Here's what I think I need to do before I upgrade to 4.4.2:

1. uninstall Xposed

2. get the 4.4 VZW firmware: VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip

3. from my computer, adb reboot bootloader or use the hardware key combination

4. fastboot flash recovery recovery.img (which I get from the 4.4 VZW firmware in 2)

Anything else? Uninstall su? What about the boot screen?

I'm sure this is all answered somewhere in this thread, but I gave out after page 20!

Thanks for any help.
[Moto X General] liveMike:
I am having problems rooting after the update. I flash recovery and it says OK then when i boot into recovery it just boots up the phone.

I have the Dev Edition, Bootloader unlocked, and now 4.4.2 installed.
[Moto X General] :
Volume down to scroll to recovery, volume up to choose it. Not power button. ;)
[Moto X General] liveMike:
Thanks, I am an idiot:)

For those having problems, in addition to everyone here, I used this link which offered a lot of help: http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/
[Moto X General] seandarcy:
So I just did it, and it worked, sorta, kinda. I now have 4.4.2 installed and it works just fine. It replaced the moto boot screen with the "danger bootloader unlocked" screen.

But now, I can't power off! I select Power Off, and it shows the "Your phone will shut down" dialog. OK, and then it shuts down, goes black, and then reboots.

It's really odd, and it stops me from getting into fastboot mode by booting into recovery. Which means I can't install TWRP, or replace the boot screen.

---------- Post added at 09:16 PM ---------- Previous post was at 08:37 PM ----------

[Solved] As long as the phone was connected to the computer, it kept rebooting. Unplug the usb connection, and all works. Puzzling.
[Moto X General] KRUSH101:
Anybody else able to get the new cast screen button to work with chromecast?
[Moto X General] jamespark:
SystemUI.apk

Oops...

Good news is I successfully updated to 4.4.2 with everything working fine.

Bad news is I attempted to push 4G LTE icon "fix" from this thread:

http://xdaforums.com/moto-x/themes-apps/mod-statusbar-graphic-fixes-t2530954

(specifically the 4.4 version: http://j2cool.com/mirror/files/vzwdecrap44.zip )

And now, I'm getting the, "Unfortunately, the process com.android.systemui has stopped." error that has all but made my phone useless. This message keeps popping up even after I click ok. I did not back up the original systemUI.apk

Wondering if somebody could post the stock SystemUI.apk from 4.4.2 so I can push that back and get my phone working again?

Thanks in advance!
[Moto X General] kbluhm:
Let me know when you DL this so I can zap it.

https://www.dropbox.com/s/2pupqyr84rrsewi/SystemUI.apk
[Moto X General] jamespark:
Thank you so much!! Suddenly, the stock LTE icon doesn't look so bad!
[Moto X General] kbluhm:
Hahaha, nice... no problem!
[Moto X General] Mike7143:
I can't remember where I found it, but I have a TWRP 2.6.3.2 from dhacker. Just updated to 4.4.2 and flashed it, but in TWRP is says 2.6.3.0. Anyone?
[Moto X General] WhammyDroid:
When I click on this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

I do not see the 4.4.2 image for the VZW DE. Does anyone else?
[Moto X General] DonKilluminati23:
Do you get the vibration when making selections in recovery? If so, you have 2.6.3.2. Dhacker is aware of the "misprint".
[Moto X General] Legacystar:
Has anyone pulled the camera apk from 4.4.2 and tried it on 4.4

Edit: tried it myself, camera force closes after trying to take a picture
[Moto X General] KidJoe:
You are not looking for 4.4.2 from there. The Verizon 4.4.2 SBF is not out yet. Only the T-Mobile 4.4.2 sbf has shown up at -> http://sbf.droid-developers.org/phone.php?device=0

You are trying to get back to stock to apply the 4.4.2 "OTA" update, so you need to be stock 4.4. on your phone. The Moto site has the 4.4 Image for Verizon X (same rom/image/sbf/xml or whatever you want to call it works on Dev and Retail/MotoMaker X for Verizon). Inside it you will find the stock recovery.img and system.img for 4.4 that you need to flash to get back to stock 4.4 so you can take the OTA.
[Moto X General] kbluhm:
Same here, I got it from: http://batakang.com/ftp/?dir=devs/mhous33/xt1060
[Moto X General] Mike7143:
Thanks for confirming. I assume it's just the label is incorrect.
[Moto X General] liveMike:
I am just adding to this great post as I am a novice and maybe it willl help other notives as well:

- disable Xposed - I just went to the app and uninstalled it

- boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot

- flash stock recovery - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them.

- flash stock system

- reboot

- update via OTA

- reboot

You are now stock unrooted 4.4.2, so just re-apply root the same way you did the first time:

- boot into bootloader/fastboot - you should be able to follow the directions from above to do this now

- flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP.

- boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.

- flash SuperSU

- reboot

- re-enable Xposed - i just reinstalled it and all of my settings were back:)

- reboot

- BAM
[Moto X General] kbluhm:
Yup, when I said disable/re-enable Xposed, I was talking about going into the Xposed app and clicking install/update or uninstall. I have seen it cause people headaches when someone says "uninstall Xposed" and people take that as uninstalling the app itself versus uninstalling the framework from within the app. Plus I left the steps just a wee bit terse because it you have a Dev Edition and are unlocked and re-rooting you most likely already have a decent grasp on what to do. But overall some good pointers there.
[Moto X General] tco05:
Is there anywhere to get the stock images for the VZ DE Moto X other than Moto? It says I need to wait for someone to give me access to the files via google.
[Moto X General] kbluhm:
The SBF developers site. The link has been posted numerous times.
[Moto X General] tco05:
Yeah, it's weird. I went to the email I had saying that I had access, clicked the link and it brought me over to where I need to request access...even with it verifying my gmail addy.

---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------

So the file from the SBF site (VZW_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml) will work for the dev edition?
[Moto X General] kbluhm:
Yes, the dev and non-dev use the same ROM. Make sure you grab the one you're after, they have a 4.2.2 and two 4.4's listed.
[Moto X General] jco23:
Hmm, update failed for me. I disabled xposed and re-enabled all bloat first. The only things that I can think of are that my boot loader image is different, the boot animation is different, and I installed the AOSP status bar data signals.
[Moto X General] mwalt2:
The bolded will for sure cause the check of /system to fail. It checks all of the hashes of the 4.4 files in /system (maybe elsewhere?). If it can't verify (ie you replaced SystemUI.apk and bootanimation.zip), it will fail. It does not matter if you enable or disable apps through Manage Apps and I doubt xposed will matter if it's enabled/disabled. The bootloader image does not matter.
[Moto X General] jco23:
thanks for the tips. I restored my previous system-UI.apk files and the OTA applied successfully (did not have to change the bootloader image or bootanimation).

only a soft reboot seems to keep the application of Xposed. otherwise, root still exists.
[Moto X General] ghstudio:
44 pages....and I'm now so confused.

I have a Verizon DE moto-x running android version 4.4 and I have TWRP and superSU installed. There seem to be multiple "stock recoveries" and there seem to be multiple system updates available either through OTA (It's sitting there waiting for me to get it) or through the motorola site (I've requested access).

Could someone keep it real simple for me....

How doe I get from where I am to the latest version....and I want to be sure I can continue to use Titanium Backup so I need to continue to be routed.

I'd really appreciate the help....
[Moto X General] KidJoe:
well... WHERE ARE YOU?? What have you read?

To take an OTA on either bootloader (locked or unlocked) its always the same. Get back to "stock" or as close to it as possible and take the update. This is due to manifest checks the OTA performs prior to installing.

That means flash the stock recovery.img back onto your phone. There may be multiple "stock recoveries" in this thread because there are different ROM version for the X that you can be on (the original 4.2.2 shipping rom, the first 4.4.2 OTA with the camera fix, and 4.4) and you need to flash the one which is appropriate for the version on your phone again due to the manifest checks in the OTAs.

For more see -> http://xdaforums.com/moto-x/general/4-4-2-vzw-t2656843/post50683681

Another option is you can just download the 4.4.2 Verizon SBF from http://sbf.droid-developers.org/phone.php?device=0 and use RSDLite to flash it, then root. (there are many threads about using RSDlite to flash and get to "100% stock", just follow one while using the 4.4.2 SBF)

If you have a Developer Edition and/or Unlocked bootloader, you can always root & disable write protect via -> http://xdaforums.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 whether you take an OTA or flash an SBF
[Moto X General] sonic1675:
Should I do a factory reset after I update
[Moto X General] dhoppy:
I thought you had to be rooted before upgrading to 4.4.2. Is there a root procedure after 4.4.2 is installed?
[Moto X General] piccit:
Considering KidJoe was addressing someone who has a DE, rooting is always accomplished via flashing a custom recovery and then flashing su (something TWRP will do for you).
[Moto X General] kbluhm:
No, you shouldn't have to.
[Moto X General] KidJoe:
piccit is correct. I quoted and was responding to ghstudio who stated he had a "Verizon DE moto-x." On the Developer Edition (DE), you can unlock the bootloader, install a custom recovery, and root, no matter what stock ROM is on your phone. With an unlocked bootloader, you don't need to rely on RockMyMoto, SlapMyMoto, MotoWPNoMo or the like to root and disable write protection like you do when you have a locked bootloader.

dhoppy, you are correct in thinking that for a LOCKED bootloader there is no root & write protect disable if you are already on 4.4.2.
[Moto X General] sonic1675:
eh im going to try anyway I compared my friends 4.4.2 to mine and neither of us have the dev edition but his battery is substantially better and he isn't rooted and is just as heavy a user as I am so factory might reset the battery stats.
[Moto X General] pingpong1109:
So I am not updating until I am sure that I will have root and xposed.
[Moto X General] bboz:
Porb

I Have an unlocked and rooted developer edition with philz recovery flashed. i have flashed stock recovery but keep getting the red triangle over the android when i try to enter recovery. Any ideas so I can update to 4.4.2
[Moto X General] KidJoe:
Hold volume up for a few seconds then hit power button