Database Develop

VZW Moto X DE Phone Update?

After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?

There's a bunch of ota threads my friend. Read up. Some are stickies...like the complete Moto x guide thread.
Sent from my Moto X cellular telephone...

SwiftLeeO said:
After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?
Click to expand...
Click to collapse
If you downloaded the update it's in the cache folder.

Ryno77 said:
If you downloaded the update it's in the cache folder.
Click to expand...
Click to collapse
Well, it just says install. I don't want to install it because I'm rooted with custom recovery and it might brick my phone. I checked the cache folder and there are 3 folders: backup, lost+found, and recovery

SwiftLeeO said:
After installing TWRP and SuperSU (not sure if they are relevant, but I'd figure I'd include all the steps), I notice that my phone has a firmware update. Now, first of all, I thought dev phones don't get updates? Also, if this is a legitimate update, how can I pull the ota to post?
Also, I'm already on 4.4, so could this be 4.4.2?
Click to expand...
Click to collapse
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted but you already know that.
What root explorer/browser are you using?

Cozume said:
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted.
What root explorer/browser are you using?
Click to expand...
Click to collapse
Root Browser by JRummy. I normally use ES, but i stopped after it wouldnt let me edit permissions.

Its just a glitch. In your cache it'd have its own folder named after the current os. Wipe cache and dalvic and you should be free of the glitch.

SwiftLeeO said:
Root Browser by JRummy. I normally use ES, but i stopped after it wouldnt let me edit permissions.
Click to expand...
Click to collapse
that is what I am using and I see the exact same subfolders you are seeing in the cache. I take it you don't see the OTA file in any of the subfolders?

Cozume said:
that is what I am using and I see the exact same subfolders you are seeing in the cache. I take it you don't see the OTA file in any of the subfolders?
Click to expand...
Click to collapse
No ota file. Might be a glitch as shane suggested.
False alarm. Went into Software Update to check and I'm up-to-date .-.

Cozume said:
Developer Editions get OTAs the same as any other Moto X. But that is odd as there have been no reports of the soak test even being started for the Verizon Moto X. Sounds like the OTA got pushed to you by mistake.
Anyhow, what is clear is that you can't take an OTA when you are rooted but you already know that.
What root explorer/browser are you using?
Click to expand...
Click to collapse
If you are rooted and want to take the OTA, you can flash the stock recovery and the system.img file with mfastboot.exe, and the OTA should install. i.e. if you are on 4.2.2, rooted with a custom recovery, then you should download the factory 4.2.2 image FOR YOUR DEVICE. Then extract it and use mfastboot to flash recovery.img and system. img. When you reboot, the phone will download the 4.4 OTA and it should install no problem. After it installs, just use mfastboot to flash TWRP and let TWRP root your device and you should be good as new with 4.4.
The stock recovery and an unaltered system folder are the key ingredients to a successful upgrade.

Mr. Orange 645 said:
You can absolutely take an OTA while rooted. The only thing that would prevent you from taking an OTA is if you have altered any system files (such as deleting system apps), or if you have messed and around and flashed a bootloader that doesn't match.
If you flash the factory recovery, you can take the OTA no problem even if rooted. You will of course lose root, but that's easily solved with an unlocked bootloader.
Click to expand...
Click to collapse
Ok, this is the kind of stuff that makes it so hard on noobs. On the thread about the OTA it says you have to get rid of root:
[NOOBS][WARNING][OTA]how to accept an ota
I know if the Moto X were a Nexus you could take the OTA while rooted but would lose root. But with the Moto X, it seems like you can't do that.

Cozume said:
Ok, this is the kind of stuff that makes it so hard on noobs. On the thread about the OTA it says you have to get rid of root:
[NOOBS][WARNING][OTA]how to accept an ota
I know if the Moto X were a Nexus you could take the OTA while rooted but would lose root. But with the Moto X, it seems like you can't do that.
Click to expand...
Click to collapse
Ok, so I just downgraded to 4.2.2, rooted, and tried to take the OTA and it failed. So, I stand corrected. You are right, you can not take the OTA if you are rooted. Well, you CAN take it, but it will fail to install. It sees the su app as an alteration to the system folder (which it is).
Easiest fix is to to use mfastboot to flash the stock recovery and flash the system.img file so it is back to stock. Reboot then let the OTA install and you should be good to go.
Sorry for the misinformation, and I will correct my earlier post so as not to confuse the "noobs." LOL.
Thank you, Cozume

OK ,its simple. 1 moto is no nexus device
2 where does the su binary flash to?xbin folder, is that not part of the system? The only reason why some folks on T-Mobile have root afterwards is, the 4.4.2 is a partial update for them as they received 4.4 , it only replaces some files,If you have a carrier such as Rogers that's going from 4.2.2 directly to 4.4.2 then all the system folders are replaced and you need to remove root along with the binary file, there are other carriers as well that are going from 4.2.2 to 4.4.2 directly
Sent on my Gummy running Lenoto X

flashallthetime said:
OK ,its simple. 1 moto is no nexus device
2 where does the su binary flash to?xbin folder, is that not part of the system? The only reason why some folks on T-Mobile have root afterwards is, the 4.4.2 is a partial update for them as they received 4.4 , it only replaces some files,If you have a carrier such as Rogers that's going from 4.2.2 directly to 4.4.2 then all the system folders are replaced and you need to remove root along with the binary file, there are other carriers as well that are going from 4.2.2 to 4.4.2 directly
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Yup, sorry for the misinformation. I was mistaken and corrected it. Likely while you were typing up your response.

[Q] Back-ups When Rooting

So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Save my custom wallpaper using these instructions:
How to Pull Custom Wallpaper
2) Root using Slap My Moto method
- here it the 4.4 OTA if 4.4.2 has already come out by the time I do this
Verizon 4.4 OTA
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the 4.4.2 OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Then after I root, I can selectively flash the 4.4.2 update:
Slap My Moto Page 150
Important Warning Before Flashing 4.4.2 Page 15
System.img, boot.img, non-hlos.bin and fsg.mbn

Cozume said:
So I am planning on rooting my Verizon Moto Maker locked bootloader Moto X running 4.4 before the 4.4.2 OTA gets pushed and I want to safely stay rooted. Here is what I am planning on doing and please correct me if I am wrong or doing things unnecessarily:
1) Flash TWRP and boot into it to make a pre-root nandroid b/u
- I know the custom recovery won't stick when I reboot, just doing it to make a pre-root b/u
- is this necessary as long as the sbf firmware is available?
2) Root using Slap My Moto method
3) Make an EFS b/u
4) Install Titanium b/u and make a post-root b/u
5) Use Titanium b/u to freeze MotorolaOTA so that the OTA won't be pushed to my device
- will freezing MotorolaOTA stop the OTA from being downloaded or will it just stop the notification popup?
6) Uninstall Motorola Device Manager from my PC so that it won't try to upgrade my phone's OS every time I connect my phone to my PC
- is there any way to stop MDM from checking for updates without uninstalling it?
- will I lose the Motorola drivers for my Moto X if I uninstall MDM?
Also when am I supposed to wipe my dalvik cache wrt back ups and rooting? Am I supposed to clear any other cache or data anywhere along the way?
Also, I can't hit the thanks button anymore today but if you help me I will come back tomorrow and hit it, I promise!
Click to expand...
Click to collapse
Flashing twrp while having a locked boot loader? Idk
Sent on my Gummy running Lenoto X

flashallthetime said:
Flashing twrp while having a locked boot loader? Idk
Click to expand...
Click to collapse
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.

Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
well good! you're on the right track. 3 best pieces of advice here:
1. Search first
2. Read alot (yes even some long threads with several pages)
3. Then Q & A is here for you.
Glad you're being safe with your exepnsive device, some noobs usually shoot first ask questions later.

Cozume said:
Thanks for pointing that out. I read that on a site about backing up that I could do that if I wasn't rooted, but it didn't specify I had to have an unlocked bootloader to do it.
Seriously I am thanking you but I hope you see it from the point of noobs like me, too. I really am reading and trying but that very basic point went over my head. There is so much to try to absorb when you are learning that sometimes the very basic stuff gets missed.
And I am trying to learn both unlocked and locked bootloader methods and not always keeping it straight in my head.
Click to expand...
Click to collapse
Flashing a custom recovery always requires a unlocked boot loader, On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Sent on my Gummy running Lenoto X

flashallthetime said:
On a more serious note, I would wait for the Verizon ota to arrive and see how folks manage to root their phones, if its possible?
Click to expand...
Click to collapse
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?

Cozume said:
I want to do it now in case the exploit is closed forever in 4.4.2. Then if someone comes up with a new way to root 4.4.2, I can unroot, revert to stock and take the update then, right?
Click to expand...
Click to collapse
No, wait and see what happens, it makes sense flash 4.4.2 now, it won't make any difference now or later, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware. Read please. I have 6 months of moto x experience behind me, been here from day 1
Sent on my Gummy running Lenoto X

My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!

SymbioticGenius said:
My advice. Root it now, wait it out. If they can't come up with an exploit for 4.4.2, sell your phone, get a developer edition then you can do whatever you want.
Click to expand...
Click to collapse
yeah, but it will cause me great sadness to sell my beautiful wood backed baby!!!

flashallthetime said:
it won't make any difference now or later
Click to expand...
Click to collapse
well, yes it would because if I take the OTA then I won't be rooted unless someone finds an exploit for 4.4.2 and I will never be rooted if someone doesn't.
flashallthetime said:
i
, second point is, you can not flash the 4.4.2 sbf firmware as Verizon's version is not available why?,your boot loader is locked, you not flash any sbf with a locked. boot loader, you can ONLY flash your specific carriers sbf firmware.
Click to expand...
Click to collapse
I am getting confused now. If I stay on 4.4 rooted and something happens to my device, can I or can't I flash the sbf for Verizon 4.4 with a locked bootloader to restore my device?
Maybe I wasn't clear but my plan is to root on 4.4 and stay there by freezing MotorolaOTA, which is the app that installs the updates and sends the annoying message. I was going to stay on 4.4 rooted and not upgrade to 4.4.2 unless someone can come up with a way to root it with a locked bootloader.

Cozume said:
yeah, that is my plan. But it will cause me great sadness to sell my beautiful wood backed baby!!!
Click to expand...
Click to collapse
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Sent on my Gummy running Lenoto X

flashallthetime said:
Go for it root it now, I have no idea which sbf firmware you can flash that won't brick your device and I guess we'll see you back with the developer edition. Did you read my previous post? Is Verizon's or at&t 4.4.2 firmware available? Not last time I checked. Locked bootloaders can not flash any sbf firmware only your specific carriers sbf firmware can be flashed
Click to expand...
Click to collapse
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?

Cozume said:
Did you read my previous post:
My Previous Post
My plan is to NEVER flash 4.4.2 unless someone can root 4.4.2. Then I would unroot and take the OTA, not flash anything. Can't I unroot on 4.4 and take the OTA?
Click to expand...
Click to collapse
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Sent on my Gummy running Lenoto X

flashallthetime said:
No one knows yet for sure what and will not work for the 4.4.2 ota, you'll just have to wait. Probably the only way is keep the 4.4 boot loader while running the 4.4.2 system only but its all speculation until the ota comes out
Click to expand...
Click to collapse
I am not planning on taking the 4.4.2 OTA. The whole point of freezing MotorolaOTA is to block the OTA.

[Q] Updating DIRECTLY from 4.2.2 to 4.4.3 (Unlocked+Rooted)

So here's the deal, I unlocked my T-Mobile Moto X bootloader through Motorola's website about a year ago or so. I also rooted and didn't bother updating afterwards to anything since I had everything working perfectly for me. Now I need to update my 4.2.2 Moto X to 4.4.3 (or really anything >=4.3 just so I can use my Moto 360 that'll be arriving soon).
My question is, with an unlocked bootloader, rooted, TWRP 2.6.3.1, Xposed-installed Moto X, can I go ahead and flash a stock 4.4.3 ROM (for example from here: http://forum.xda-developers.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675) and just call it a day?
I've been reading past threads and stuff to get back into the loop, but I just can'f find anything to answer me the simple question of updating an unlocked+rooted 4.2.2->4.4+ while keeping root. Just the simple question of, if I get a stock 4.4 image and flash it on my phone, will everything be okay?
I no longer have the passion and interest to constantly be fiddling with kernels, ROMs, and little hacks with my phone like I used to with my OG Droid and, to a lesser extent, with my Galaxy Nexus (plus I feel like it's gotten significantly less easy since those OG days).
I know (i.e. 90% sure) that one way to do what I want (kinda) is RSDLite/manually go back to stock without root on 4.2.2 and then accept the OTA, but certainly it has to be easier than that right? What happened to the days where I can just find a new Gingerbread ROM for my Froyo Droid and just flash it right then and there? Now everything is "go back to stock and do these convoluted steps."
(I'm sorry I'm ranting, I'm just really tired at the moment haha)
Thank you all, hopefully, for the help!

If you don't care about retaining your data, grab the 4.4.3 fxz and unzip it. Follow the directions for returning back to stock here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358 but replace the files to be flashed with the files from the 4.4.3 fxz. Not sure where you got the idea that you need to go back to stock. Word of caution, once on 4.4.3 there's no going back to an older version.

I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?

RGNDI said:
I have the same question as the OP, on unlocked rooted 4.2.2 ATT Moto X, can i flash a custom 4.4.4 and keep root?
Click to expand...
Click to collapse
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate version recovery again and then flashing supersu.

1ad_m12 said:
You can take the ota but you need the stock recovery. Since you are unlocked you will not lose your unlocked-ness(lol) if you take an ota. But you do need to be completely stock: no su, no custom recovery, etc etc. But once you upgrade to 4.4.3 getting root back is as simple as flashing the appropriate vision recovery again and then flashing supersu.
Click to expand...
Click to collapse
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question

RGNDI said:
OK thanks, but cant I just Flash a Rooted Stock 4.4.4 over 4.2.2? Thats a more to the point question
Click to expand...
Click to collapse
Yeah that would work as long as your radio is compatible with the rom. The rom you shared earlier should be fine. Just don't downgrade to anything pre 4.4 as that can cause issues because of partition sizes (or so I've heard). But after that I wouldn't take any OTA's cause your bootloader would be incompatible with the OTA and possibly cause a brick. If I were you I'd revert to stock and take the long way to 4.4.3 just so I can get the OTA for when Android L comes out. In fact thats what I plan on doing if the Sunshine bootloader unlock is successful. But if you don't care about that then everything should be fine.

[Q] Best Way to get to 4.4.4

Hello all,
I am on a stock rooted 4.4 rom (verizon). I just used the Sunshine bootloader unlock and I'm curious about the best way to get to 4.4.4.
Should I:
a. Revert back to JB and just take all the OTAs?
b. Or is there a way to just flash 4.4.4 with a custom recovery?
Another question is that once I get to 4.4.4, the unlocked bootloader will still be there and I can put a custom recovery and just flash SuperSU right?
The final question is do I even want to update from 4.4 to 4.4.4, nothing really changed right? Would you do it or just wait for Android L?
Thanks!

streetlightman said:
I am on a stock rooted 4.4 rom (verizon). I just used the Sunshine bootloader unlock and I'm curious about the best way to get to 4.4.4.
Should I:
a. Revert back to JB and just take all the OTAs?
Click to expand...
Click to collapse
No. First I would make a nandroid of your stock rooted 4.4.
Then, if you want to keep your data, flash the 4.4 stock recovery and unroot. You said you are on a stock system, but make sure you disable the Xposed installer (not just install it but disable it) if you installed it and revert any changes to your system that you made including unfreezing any apps before you take any OTAs.
Once you have done all of that, I would just let the OTAs do the rest.
If you don't want to keep your data, you can flash the 4.4.4 sbf using RSDLite.
streetlightman said:
The final question is do I even want to update from 4.4 to 4.4.4, nothing really changed right?
Click to expand...
Click to collapse
A lot changed including the camera improvements.

Wansanta said:
No. First I would make a nandroid of your stock rooted 4.4.
Then, if you want to keep your data, flash the 4.4 stock recovery and unroot. You said you are on a stock system, but make sure you disable the Xposed installer (not just install it but disable it) if you installed it and revert any changes to your system that you made including unfreezing any apps before you take any OTAs.
Once you have done all of that, I would just let the OTAs do the rest.
If you don't want to keep your data, you can flash the 4.4.4 sbf using RSDLite.
A lot changed including the camera improvements.
Click to expand...
Click to collapse
Thanks for the reply. I don't care too much about my data so I wouldn't mind SBfing back to JB. The reason I'd rather do that is because i can't remember what apps I froze (deleted) and I removed the updater APK so it wouldn't annoy me. Would reverting back to JB affect the unlocked bootloader? It shouldn't right?

streetlightman said:
Thanks for the reply. I don't care too much about my data so I wouldn't mind SBfing back to JB. The reason I'd rather do that is because i can't remember what apps I froze (deleted) and I removed the updater APK so it wouldn't annoy me. Would reverting back to JB affect the unlocked bootloader? It shouldn't right?
Click to expand...
Click to collapse
What is the point of downgrading to jelly bean?
If you froze apps, they will show up in titanium backup as frozen. If you deleted system apps, you are not stock. So what you are running is a rooted 4.4 that is not stock b/c you deleted system apps. You can flash 4.4.4 without having to remember the changes you made. Then you can flash TWRP and reroot using SuperSU.

You can't downgrade anyways. Unless you want a paperweight. Not even sbfing will do it. Sorry brother. I'm only telling you this for your own good. Please listen.

Download the 4.4.4 sbf, unzip it, flash the contents in bootloader. You can find a guide in the General subforum.

ryanzurlo88 said:
You can't downgrade anyways. Unless you want a paperweight. Not even sbfing will do it. Sorry brother. I'm only telling you this for your own good. Please listen.
Click to expand...
Click to collapse
Depends on what you are trying to downgrade.

Wansanta said:
Depends on what you are trying to downgrade.
Click to expand...
Click to collapse
So your saying... That I have a vzw Dev ed moto x. 4.4.4. I can take it and downgrade it to 4.4.2 and then flash the gsm 4.4.2? I just use it on WiFi only anyways. Cause I'm trying to get the stock moto x firmware with no carrier bloatware. Right now the vzw has 9 bloatware apps. I have the att 4.4.4 ROM right now with only 4 bloatware apps. I want no bloatware WITHOUT using tb and others

ryanzurlo88 said:
So your saying... That I have a vzw Dev ed moto x. 4.4.4. I can take it and downgrade it to 4.4.2
Click to expand...
Click to collapse
Yes, you can downgrade to the 4.4.2 system. If you try to flash the 4.4.2 bootloader or partition table, it will fail. But you can downgrade to the 4.4.2 system. Once upgraded the bootloader and partition table are not downgradeable but if you try to flash them you will get a failure, not a brick. As long as you have an unlocked bootloader and can get to bootloader mode, you don't have a brick.
ryanzurlo88 said:
and then flash the gsm 4.4.2?
Click to expand...
Click to collapse
I don't know anything about trying to flash the XT1053 system to a XT1060 device.
ryanzurlo88 said:
Cause I'm trying to get the stock moto x firmware with no carrier bloatware. Right now the vzw has 9 bloatware apps.
Click to expand...
Click to collapse
I just remove those via Titanium Backup. Which ones do you want removed and I can tell you if I have removed them and what happened when I did.
You only need the TiBU PRO key if you are freezing apps, not removing apps.

Well like I said I have att moto x rom on a vzw moto x. I just want the straight plain ROM with no tinkering

ryanzurlo88 said:
Well like I said I have att moto x rom on a vzw moto x. I just want the straight plain ROM with no tinkering
Click to expand...
Click to collapse
The att system has carrier bloat, too. Do you mean the XT1053 - Tmobile/unlocked GSM system?

Yeah. I'm waiting on an sbf/fxz for it. Unless you've found it?

ryanzurlo88 said:
Yeah. I'm waiting on an sbf/fxz for it. Unless you've found it?
Click to expand...
Click to collapse
The latest official sbf for the XT1053 is 4.4.3 unless someone made an unofficial fxz for it.
http://sbf.droid-developers.org/phone.php?device=0

ryanzurlo88 said:
Yeah. I'm waiting on an sbf/fxz for it. Unless you've found it?
Click to expand...
Click to collapse
A lot of talk lately about downgrading being ok on 4.4.2 or higher.....and well there can be a very particular way to do it, without downgrading the bootloader....there are many ways to make a mistake and end up with a brick. This warning seems to be missing from some of the downgrade talk I've been seeing around.
The veterans of this device and XDA will always flat out say no....You can't downgrade. Why? Because if we try to guide anyone through downgrading, or advise them they can.....mistakes happen, and we don't want to be partially responsible for anyone destroying their device.
So, best (aka safest) advice, is to wait for the files you need. Then flash them fairly risk free.
Or try to downgrade.....but know the risks. ?
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
If anyone disagrees.....ask these people how downgrading went for them...
https://www.google.ca/search?redir_...ed+xda+site:forum.xda-developers.com&hl=en-US
?

[Q] Go from 4.2.2 to 4.4.2 Unlocked, rooted, twrp

I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks

dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
If all you want to do is update, you could install Custom ROM although you will lose Motorola's Active Display, Always Listening etc...
If you want complete stock and have to reflash TWRP and root your phone, you will need to flash the stock firmware using fastboot or a utility.

Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.

Alecegonce101 said:
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
Click to expand...
Click to collapse
Um, all VZW Moto Xs are SIM-unlocked.

dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
I hope it wasn't the pre-camera 4.2.2....or you might be in a tough spot now.... Risking a brick. ?
---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------
Unless the first firmware was also pre camera... Then you're OK.

dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
Taking OTA's is incremental, so if you are the initial shipping 4.2.2 you need to take the first 4.2.2 w/camera OTA, then the 4.4 OTA, then the 4.4.2 OTA... a real time waster and pain in the rear.
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
Since you have a Dev Edition, why not just go to 4.4.4? it has a few bug fixes, and is stable. For me and many others its no worse than 4.4.2 as far as performance and battery.
Once you arrive on the ROM you want, you can flash TWRP and root.

KidJoe said:
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
t.
Click to expand...
Click to collapse
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??

dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
Yup! ?
As long as it's not a lower version.

dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
OTA = Incremental. Only patches the changed/updated parts.
SBF/FXZ = "all inclusive" or "image files".. and overwrites entire partitions/parts.
So yes. You can just flash the newer SBF file. (As @Darth said... as long as the SBF you are flashing is NEWER than the version on your phone... i.e. NEVER DOWNGRADE)