yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] Schaweet:
If you have the Dev edition from VZW, it's simple to install the OTA.

This is what I did as I had root and xposed installed.

1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard

2. Flash stock 4.4 recovery image via fastboot.

3. Flash 4.4 system image using mfastboot (must use mfastboot)

4. Boot into recovery

5. Apply update and selected the OTA zip.

6. Reboot

7. Power down and boot back into fastboot.

8. Flash TWRP, allow it to root, reboot.

9. Reinstall Xposed framework.

All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.

Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.

Sent from my Dev Edition Moto X
[Moto X Q&A] _slam:
If I was you I would wait to see what the community is doing, see how they are approaching this. But my method returned the phone back to stock, but I keep the bootloader unlocked and no root access and yes this delete all my settings and apps. I did this because I wanted learn the manual way of flashing to stock.

You can try what; Senior Member, tcrews said:

Which if I didnt flash back to stock I would have tried. Big ups tcrews :good:
[Moto X Q&A] _slam:
Definitely trying this method on next OTA :good:
[Moto X Q&A] _slam:
Update

Update; this method workd for me just got vzw OTA 4.4.2 this morning, after download the update/install took under 7 minutes.
[Moto X Q&A] _slam:
After this AM MotoX DEV 4.4.2 OTA update I'm back to unlocked bootloader (never relocked), TWRP (twrp-2.6.3.1-ghost-4.4), SuperSU, and VzwEntitlementService.apk hack. AND phone still works... WooHoo! :D
[Moto X Q&A] Roland Stone:
If I wait long enough do you think I can expect to find a flashable 4.4.2 zip for rooted Dev Edition so that I wouldn't have to go through restoring back to stock with fastboot and could just do the whole thing on my phone without being hooked up to a computer?
[Moto X Q&A] shadowmonk36:
Just want to make the note that if you have a stock kernel you must flash boot.img as well, otherwise it will error out because something isn't right. Took me way too long to realize this was my issue, but now i'm running 4.4.2.
[Moto X Q&A] edthesped:
This may be what you're looking for...

http://xdaforums.com/moto-x/development/xt1060-164-55-2-unofficial-fxz-unlocked-t2659682
[Moto X Q&A] Coop9:
Maybe... but why?

The process isn't hard, and if you want to be super safe, you can follow the official instructions from Moto, keep your data and in about 20 minutes be running the official 4.4.2 with root.

Download the system image from Moto's site

unzip it, and open the .xml file

Grab the motorola fastboot.exe for your OS, put in the same place you unzipped the system image.

Boot into fastboot

for each step execute 'fastboot <operation> <partition> <filename>' (if one of the options doesn't exist omit it) i.e. 'fastboot reboot-bootloader'

Reboot into recover to verify it's the stock recovery (you'll see an android lying on his back with a red triangle above him, this is the stock recovery not an error, hold volume up for a couple secs, then press power, you'll see)

Reboot as normal.

Go into settings, check for updates, download OTA, and install it.

Reboot back into fastboot, flash TWRP, reboot into recovery.

Reboot from within TWRP and it will prompt you to root

Enjoy your rooted 4.4.2 device

This will not wipe your data, and while more steps than you technically have to do, is 'by-the-book' and should be completely safe. You'll be running the latest bootloader, custom recovery, and your device will be rooted.
[Moto X Q&A] edthesped:
First the image has to be available on Moto's site....

Moto X, VZW Dev Edition:

KK 4.4-13.11.1Q2.X-69-3 (VZW)

Is the latest available download.
[Moto X Q&A] Coop9:
You use the 4.4 image to revert to the stock recovery and system... Then you download the 4.4.2 OTA and install it as normal.
[Moto X Q&A] wmarcin:
I've read through the thread and it's been very helpful, but I'm still a tad confused.

1. When I flash recovery.img and system.img, it won't affect any of my installed user apps or their settings or anything in the /data folder, will it?

2. I don't need to worry about disabling xposed, reverting entitlement hack, or restoring deleted/frozen system apps if I go the above route, correct?

Please advise, and thanks in advance.

... Moto X VZW DE ...
[Moto X Q&A] Coop9:
1. Nope, your apps and data will be untouched.

2. I had no issues accepting the OTA after flashing the stock 4.4 system image. Frozen apps remain frozen... The only thing I had to do was reinstall SuperSU after completing the 4.4.2 OTA.
[Moto X Q&A] edthesped:
I guess I'm fixating on not "upgrading" my bootloader as I'll not flash a newer bootloader unless there is no other choice. However, in doing so I also know to not take an OTA again. The method in the link I posted can be done while allowing the opportunity to still downgrade, though I'm not really sure why anyone would want to do that.
[Moto X Q&A] Coop9:
Why? That makes sense if you have a device where the bootloader gets updated to prevent an exploit, but if you're running the Moto X Dev edition, you don't have to worry about that. I guess if you do want to downgrade, there's that, but I can't see a reason at this point to go down to 4.4

We aren't oppressed Samsung users, where it should be avoid the OTA at all costs. We have officially unlocked bootloaders, so prepping for an OTA to hit actually can mean getting ready to accept it rather than prevent it. But, because you have an unlocked bootloader, you can do whatever you like I guess!
[Moto X Q&A] wmarcin:
I can confirm, it worked like a charm. All apps and data were untouched. System.img took care of reverting the framework changes xposed caused, as well as the system apps previously uninstalled. Only had to reflash TWRP + SU, then SU binary, then restored xposed (rebooted from within -- it wasn't uninstalled during the whole process). As some pointed out earlier, the xposed mods were already enabled after it was restored.

I am typing on a wi-fi tethered laptop.

For total noobs like myself, here is the order (again) and the commands (I had to look that up, since I do these things so rarely) you'll need (assuming all files are in the same folder, and that folder is your path in command line):

1. ---connect the phone to the computer, while the phone is on type the following---

adb reboot bootloader (to boot into fastboot mode)

2. ---when in fastboot mode---

fastboot flash recovery recovery.img (to flash recovery.img)

mfastboot flash system system.img (to flash system.img)

You can get both files when you extract the contents of this zip:

http://sbfdownload.droid-developers...W_XT1060_4.4-13.11.1Q2.X-69-3_CFC_1FF.xml.zip

3. ---reboot your phone---

4. ---accept OTA update (in System - About - System Update)---

5. ---after your phone installs the OTA and reboots---

adb reboot bootloader (to boot into fastboot mode)

6. ---when bootloader shows up---

fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img (to flash custom recovery)

7. ---select Boot into Recovery--- (volume Down to move down, volume Up to select)

8. ---swipe to install SU when leaving TWRP---

9.---when phone reboots, open SU, select to update binary using TWRP/CWM---

OPTIONAL

10. ---if you have xposed, open the app, in Framework, chose Install/Update and Reboot---

You should be good to go. :)

EDIT: Added link.
[Moto X Q&A] edthesped:
call me cynical but one never knows if or when moto/vz might try to change the game and I like options.
[Moto X Q&A] Coop9:
Well, rest assured, you're A-OK with the 4.4.2 bootloader. It's still unlocked... Verizon would be looking at one ugly lawsuit (in terms of precedent it would set) if they suddenly decided Developer edition phones weren't unlockable.
[Moto X Q&A] Mickoou:
Continue Reading ....

I can confirm, it worked like a charm. All apps and data were untouched. System.img took care of reverting the framework changes xposed caused, as well as the system apps previously uninstalled. Only had to reflash TWRP + SU, then SU binary, then restored xposed (rebooted from within -- it wasn't uninstalled during the whole process). As some pointed out earlier, the xposed mods were already enabled after it was restored.

I am typing on a wi-fi tethered laptop.

For total noobs like myself, here is the order (again) and the commands (I had to look that up, since I do these things so rarely) you'll need (assuming all files are in the same folder, and that folder is your path in command line):

1. ---connect the phone to the computer, while the phone is on type the following---

adb reboot bootloader (to boot into fastboot mode)

2. ---when in fastboot mode---

fastboot flash recovery recovery.img (to flash recovery.img)

mfastboot flash system system.img (to flash system.img)

3. ---reboot your phone---

4. ---accept OTA update (in System - About - System Update)---

5. ---after your phone installs the OTA and reboots---

adb reboot bootloader (to boot into fastboot mode)

6. ---when bootloader shows up---

fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img (to flash custom recovery)

7. ---select Boot into Recovery--- (volume Down to move down, volume Up to select)

8. ---swipe to install SU when leaving TWRP---

9.---when phone reboots, open SU, select to update binary using TWRP/CWM---

OPTIONAL

10. ---if you have xposed, open the app, in Framework, chose Install/Update and Reboot---

You should be good to go. ￼

If these files could be put in a zip file in there modified state for flashing it would help a Noon like me a lot

Thanks
[Moto X Q&A] wmarcin:
Nothing needs to be modified, you just need to download the big zip file from the link posted earlier in this thread (I'll add it to my previous post), and extract recovery.img and system.img. And have the TWRP recovery image ready. I assume you should have it, as well as adb, fastboot, and mfastboot setup, along with appropriate drivers, since you're in this thread.

... Moto X VZW DE ...
[Moto X Q&A] kevdog:
Hey guys I followed the above steps, however when I get to this step:

6. ---when bootloader shows up---

fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img (to flash custom recovery

I can flash the recovery but it never sticks. The stock recovery is always present. What do I do? (VZM MotoX Dev Edition flashed with OTA 4.2.2)
[Moto X Q&A] wmarcin:
Are you on 4.4.2 or 4.2.2? I think this recovery is for the 4.4 and up.

You MUST boot into recovery from within bootloader first thing after flashing it. Otherwise, it won't stick.

Edited.

... Moto X VZW DE ...

---------- Post added at 11:34 AM ---------- Previous post was at 11:23 AM ----------

8 and 9 seem like a longer way to accomplish the same thing I suggested: boot into recovery directly after flashing custom recovery.

8 is really unnecessary, since you should be inside the bootloader already after flashing TWRP. Once you're there, pressing volume Down and then volume Up. Takes you to recovery (reboots phone to do that).

... Moto X VZW DE ...
[Moto X Q&A] kevdog:
Made such a dumb green mistake -- Oh I hate when I do such things!!!!

You are right, you need to flash the recovery partition and then withing the bootloader menu, immediately boot to recovery, rather than normal boot -- since the recovery partition would just be overwritten. That was exactly the mistake.

To summarize --

Reflashed system and recovery partitions from images found on this page; http://sbf.droid-developers.org/phone.php?device=0. Specifically it was the 4.4 image: Blur_Version.140.45.5.ghost_verizon.Verizon.en.US

I used the fastboot executable for linux found in this download.

I then rebooted and accepted the OTA update.

I then rebooted into the bootloader and flashed (with fastboot utility) the twrp-2.6.3.1-ghost-4.4.img and from the bootloader screen rebooted into recovery. Upon exiting TWRP you are prompted to root.

Rebooted.

Opened SU app and updated -- rebooted into twrp to allow for root, rebooted

I then had to open the Xposed Installer to reinstall the installer -- reboot -- and then activate all the xposed modules -- reboot. All changes from xposed were reverted without having to set them up again.

I then finally flashed within the bootloader using the fastboot utility the logo.bin file to get rid of the Unlocked bootloader warning.

That was it.

And just for reference -- fastboot works within linux for all these activities -- I did not need mfastboot. The only issue was that I had to run the fastboot executable as root: ie sudo fastboot flash ........... I'm not sure why the root requirement is in place, however that made it work. I could not run fastboot as a regular user although the executable had global ugo +x privileges.
[Moto X Q&A] shanshor:
Could someone post a link to the stock recovery?
[Moto X Q&A] kevdog:
Not knowing what carrier you are using, you can find the 4.4 links here:

Reflashed system and recovery partitions from images found on this page; http://sbf.droid-developers.org/phone.php?device=0. Specifically it was the 4.4 image:

For verizon it would be: Blur_Version.140.45.5.ghost_verizon.Verizon.en.US

The recovery image is in the zip file that you download from the site. I guessing likely all the stock recovery images are the same for the carriers, but I really don't know this for a fact.
[Moto X Q&A] Ryno77:
Sent it to you in a PM.
[Moto X Q&A] shanshor:
Thanks guys, got t!
[Moto X Q&A] jjustice31012:
4.4.2 OTA Update

I woke up this morning to find I had the 4.4.2 OTA update. Currently I have stock 4.4 on my unlocked, rooted Moto X. I have TWRP installed and superuser installed. When I tried to install the update it boots into TWRP. I tried to install the update but it is asking for me to locate the zip file and I have been unable to do so. Is there a way around this as if I shut down my phone it will boot back up but shortly after doing so it would reboot on it's own and go back into TWRP recovery options. The only way I was able to stop this was booting into recovery and clearing DAVlik cache and system cache. I also notice that there is 3 4.4.2 version listed on the above website so how do you know which one to choose. They are listed below.

Android 4.2.2

Blur_Version.139.10.53.ghost_verizon.Verizon.en.US Verizon US 527.5 MiB E1BEA8E9AA84F6F9FEAE12DBB83C8252

Android 4.2.2

Blur_Version.139.15.1.ghost_verizon.Verizon.en.US Verizon US 562.1 MiB B349F480216CAD3BCE9E32A32C20304B

Android 4.4.2

Blur_Version.164.55.2.ghost_verizon.Verizon.en.US Verizon US 692.7 MiB 7981527816CE0637531B953C65D43C8F
[Moto X Q&A] pkomarnicki:
If you look closer at the version numbers, the top two you have listed are different from the bottom one. The bottom one is the one you want - two 4's followed by one 2, vs one 4 followed by two 2's.

Sent from my XT1060 Dev Edition
[Moto X Q&A] jjustice31012:
Thanks

That is the one I downloaded. My phone will download the update but when I tell it to install it boots to the Teamwin recovery screen. I currently already have 4.4 stock on my phone with no other mods. Do I have to disable the TWRP recovery software or install it through the computer. It will not install via normal update to the phone unless there is something I am missing.
[Moto X Q&A] pkomarnicki:
You have to have the stock recovery installed in order to install the update.

Sent from my XT1060 Dev Edition
[Moto X Q&A] DragoonBrethren:
You need to install the stock recovery in order to take the OTA. Look back a few pages in this thread. There are several posts with step-by-step instructions that will help you.
[Moto X Q&A] jjustice31012:
Thanks again.

Will do.
[Moto X Q&A] Roland Stone:
Finally got my Dev Ed updated using the Flashify method. It took a few failed attempts that kept crashing from the desktop and rebooting into recovery before I remembered to uninstall Xposed first!

After uninstalling Xposed, using the free Flashify app from the Play Store to flash the Stock Recovery (which I downloaded from Motorola) (thereby removing TWRP recovery), accepting and installing the OTA, using Flashify again to re-install TWRP, and finally reinstalling Xposed - I'm back in business!
[Moto X Q&A] smt0222:
Thanks!

Thanks to everyone here. Reiterating what worked in a slightly different way.

Staus: VZN, XT1060, MotoX, 4.4, DEV unlocked bootloader, TWRP, SuperSU, No Xposed, Free tether, Ad blocking, disabled apps, LED modified for charging light:

1. Re-enabled any bloat (e.g., VZ Navigator). Went to settings, apps, and then went to right tab "disabled".

2. Undid free tether. Deleted /system/priv-app/VzwEntitlementService.apk, renamed VzwEntitlementService.apk.bak and VzwEntitlementService.odex.bak back to original filename by removing .bak to each

3. LED charging. This is probably not necessary since it's not in the /system folder (it's in the /sys folder) but I disabled (normal where LED only turns on if not enough battery to turn on screen) it anyway. Also did not worry about Ad blocking app. Did not do anything with SuperSU app.

4. Downloaded flashable zip of Stock Recovery (found here) so I didn't have to worry about getting Motorola 4.4 sbf or doing stuff with mfastboot.

5. Booted into TWRP recovery.

6. Installed Stock Recovery zip file.

7. Rebooted. (actually first rebooted into bootloader, then recovery to make sure I was on stock recovery (if you do do this, when you see the lying down android, hold Volume Up for about five seconds. Then while still holding Volume Up, press and release the Power button)).

8. Installed OTA 4.4.2.

9. Rebooted, still had root. So far so good!

I still haven't put back TWRP recovery yet since I retained root. And I don't know why i went so long without Xposed framework and GravityBox and Moto Tether modules. So awesome.
[Moto X Q&A] jdellingson7:
Downgrade to 4.4 from 4.4.2

Has anyone been able to successfully downgrade to 4.4 after updating to 4.4.2. I have heard that downgrading from 4.4 to 4.2.2 caused bricked phones. I have updated to 4.4.2 and have noticed issues with bluetooth drops and other small bugs and I'm considering downgrading but want to make sure its safe.
[Moto X Q&A] NWKENT:
Go here to the OP..assuming you have a DEV model..if you are still unsure..PM and I have a custom FXZ from 4.4.2 back to 4.2.2 with TWRP 2.6.3.1 install included >> http://xdaforums.com/showthread.php?t=2659682

sent by my 4.2.2_139.15.1

Jelly Bean TWRP 2.6.3.1

XT1060 Moto XDEV

Please donate to: jcase & Hashcode (if you can)
[Moto X Q&A] _slam:
I was able to downgrade to 4.4 after the 4.4.2 update; my setup was: TWRP, SuperSU, on 4.4.2 on my MotoX Dev. Ed. I just did the flash back to stock using the manual method and was able to flash back to 4.4; after the flash to 4.4 stock I booted up the phone I got the 4.4.2 update again. I did a flash back to 4.4 because I was testing Xposed framework (it didn't take) so I uninstalled and flashed back back to 4.4 to get a clean image. And I was have radio issue after the update and the install of Xposed framework; for example with the with the FCC Speed Test I was getting download number like 6.72 Mbps vs 25.65 Mbps; main reason I wanted a clean image and for the downgrade to 4.4 for a clean 4.4.2 image

btw getting a clean image did not help my network radio issues; but clean cache data in storage did, who knew!
[Moto X Q&A] GandalfTehGray:
Where you find a stock recovery zip? Been looking all over and gave up to just pull what I needed from the complete SBF file
[HTC Desire X] K-NineHD:
My HTC Desire X (4.1.1) has been playing music weirdly, when i plug in headphones it plays warped (I dont know the exact word) ive tried with other headphones and they dont work, does anyone know a fix and/or am i the only one with this problem
[General Questions and Answers] kapidanialmir:
Hello there , I don't know how but when I turn on my phone (HAIER w910) I can't charge it, when he is powered off I can charge him without any problem. Someone help me please, any ideas?
[Moto G Q&A, Help & Troubleshooting] tplnoor:
i want to buy moto g but its hard for me to find which model is better?

single sim or dual?

google play version or not?

i mean which one have better xperiance?

normally we love google play versions . but here we have a motorola.i had not any motorola cellphons before

which one is better? motorola roms and suport? or the google ones?

which one have better roms and support and development?

single sim? dual sim?

tanx alot.and exm for my english.
[Moto G Q&A, Help & Troubleshooting] Durteedee:
I depends on your needs and your network. Do you need dual Sim?

sent from the kitty kat Atrix HD Maxx
[Moto G Q&A, Help & Troubleshooting] tplnoor:
if the dual sim is like sigle sim in all things( roms-performance-development)-you know for example galasy s and galaxy s dual arent like together-

i wana get dual sim

but if not.no problem.i will use single sim

imean aim asking you about the performance-roms- support -development

tnx again
[Moto G Q&A, Help & Troubleshooting] digitalmahdi:
It's like the single sim. It's not like Samsung which Dou's versions are different.
[Moto G Q&A, Help & Troubleshooting] tplnoor:
tnx bro

what about roms? which one is better? motorola or google play version?

generally nexsus are more better.cuse better support .but i dont know motorola

which one have better support for updates and what difference did you seen in motorola rom and google ?
[Moto G Q&A, Help & Troubleshooting] debaj:
Currently most ROMs only support single SIM variants with very limited support to dual sim devices or none at all, but this can change later.
[Moto G Q&A, Help & Troubleshooting] TotesMyGoats:
The moto g runs stock android. Its not a custom skinned rom like HTC and Samsung like to do. So really, the only difference is the GPE doesn't have the 3 Motorola apps (migrate, help, and the better moto camera app). Also, the GPE will get updates a couple months before.

My suggestion is get the normal moto g because of the camera app is better. Though, really in day to day use, you'll never notice if its the normal one or the play edition.
[Moto G Q&A, Help & Troubleshooting] jaspreet997:
3 actually usefull apps and also Regular Moto G has an F2fs file system which was first used in moto x and promises faster random data reads ( faster read performances )

And about the updates....You can be sure that as soon as Moto G gpe would get any s/w update...it will be ported soon enough to regular one too

Sent from Samsung Chat
[Moto G Q&A, Help & Troubleshooting] ashut0sh:
Dual SIM Google Play Edition

>Dual vs Single: Dual SIM

Why?:confused:

Because you will have space for one extra SIM if some day you need it:), no harm in having two slots while if you have only one you might need to buy a new phone just for an extra SIM.:p

>Google Play vs Moto Version: Google Play

Why?:confused:

You will get unlocked Boot loader:D with warranty which you loose out in Moto Version:( in case you unlock your Boot loader.

Its like they unlock the boot loader for you with the warranty intact.

This will allow you to play with different ROMs without loosing out your warranty.:laugh:

For software support, Google ROM support will always be better than Motorola any day.:)

Further, in case of Hardware issues you shall be contacting Motorola in both cases so you aren't loosing out nothing :)

by buying a Google play edition.

Verdict: Dual SIM Google Play Edition :good:

Edit: as mentioned by [MENTION=5351279]jaspreet997[/MENTION]

Such phone is not available and also I have checked up the same.

So then opt for Simple SIM GPE untill and unless a dual SIM is very very important to you.
[Moto G Q&A, Help & Troubleshooting] jaspreet997:
Are there any dual sim gpe being sold anywhere? I think not
[Moto G Q&A, Help & Troubleshooting] tplnoor:
tanx again

generally single sims have better development(i dont know about motorola).if its true on motorola.its more important than one sim more

in my country motorola havent eny office and the waranty isnt meaning here!

i think moto version will get updates as soon as the GPE got

so the motorola one sim looks better

thank you all