yashsingh1/xdaforums huggingface dataset:
[Moto X General] dogyears:
I have a VZW DE Moto X with an unlocked bootloader and TWRP recovery installed. When trying to flash the 4.4.2 update it fails with the error this update is for a "ghost" device. Then it says something like your device is a ..... Has anyone else come across this is and if so is there a way around it? i have searched and haven't seen anyone post on this error for the 4.4.2 update.

Thanks!
[Moto X General] tcrews:
You need to flash using the stock recovery, not twrp recovery.

Sent from my Nexus 10
[Moto X General] whatnow275:
Moto is sending me a code for a new moto x because the front facing camera is starting to be blocked. Does anyone know a way to use this to get a Dev edition?
[Moto X General] dogyears:
Thanks!
[Moto X General] kbluhm:
Not gonna happen.
[Moto X General] dkoon1987:
Can anyone who has flashed 4.4.2 confirm if OTG support has returned? I'm taking natively (for recovery purposes). I'm still holding out for the OTA, I was just curious. Thanks!
[Moto X General] hyatari:
No its because you can't change the physics of the batteries capacity.
[Moto X General] slappydj1:
I apologize in advance if this is too much to ask, but can someone with a rooted non dev moto x runnung 4.4.2 with busy box installed do a dd of the recovery.img? It would be more than helpful to us bricked users.
[Moto X General] sfetaz:
I forgot if/what the . 2 update brings to kit kat that is a big change or addition. I have a nexus 7 2013 and don't remember anything major. I have a locked vzw edition so I don't want to upgrade unless I can keep root.

If I start getting the OTA notifications is there anyway to stop it on stock rooted wp off 4.4?
[Moto X General] bb1981:
I have a locked X with 4.4 on Safestrap and freezing Motorola OTA with Titanium Backup took care of the automatic updates. I don't want to lose root or end up with the wp turned back on.
[Moto X General] KidJoe:
ANYONE can sign in with a moto account, or gmail account and request the images from Moto. You don't have to have purchased a device. (as a test, I signed in using my backup gmail account).

Also, the Verizon Developer Edition ROM is exactly the same as the ROM for Verizon Retail and Moto Maker phones. So anyone with a Verizon X (XT1060) needing the SBF/FXZ can request and use this rom from Moto's web site.

Oh, and once they approve you, they send you a link to the file hosted on Google Drive. Once you are granted access to it, you retain access to it. So hang onto the link in case you might ever want to download the file again in the future.

---------- Post added at 07:03 AM ---------- Previous post was at 06:56 AM ----------

The OTA ZIP file is signed by Moto. Once you edit/change it, its not signed so you can't use it on a locked bootloader phone.

In other words, by editing the manifest file and saving it back into the OTA ZIP, you break the Moto Signature on the OTA ZIP so you can't flash it if you have a locked bootloader.
[Moto X General] Talguy:
I can't wait till this gets pushed to my phone. I really hope it brings so better battery life and more stable radios with it. I got a VZW DE X which I haven't taken the time to unlock it yet and frankly don't feel like doing it until Motorola drops support for this device like HTC did to my rezound.
[Moto X General] kbluhm:
If you have any intentions of unlocking the bootloader, just do it and get it over with so down the road you won't lose any data. An unlocked bootloader doesn't affect your system, updates, etc, in any way.
[Moto X General] _litz:
what version of safestrap, and how did you go about installing it on 4.4?
[Moto X General] KidJoe:
Why wait? Unlocking the bootloader on a Developer Edition does NOT void the warranty. Its an easier root process (if you want/need root).

Keep in mind, the process is destructive, i.e. will wipe your data, so you'll have to back up your data before hand, and re-install all your apps, settings, etc after wards. That in itself might make it more desirable to do it sooner, rather than later when you have more stuff and customization on your device that you'd need to redo.
[Moto X General] nathansnyder:
Right, but software enhancements can improve battery life by decreasing battery drain from certain apps. It's also software which reads the current capacity of the battery. That said, I have no way of knowing if draining it all the way will help it to read it properly, but it may be worth a shot.
[Moto X General] Legacystar:
If you have moto assist turned on then that's your battery problem right there. Moto x has great battery life
[Moto X General] sonic1675:
Im on 4.4.2 though
[Moto X General] Legacystar:
Won't matter of you still have moto assist on
[Moto X General] sonic1675:
its been off but battery just still isnt quite the same as 4.2.2
[Moto X General] meant2live218:
Other Soak?

So I just got the email to a soak test this morning, and the patch notes they released on the private forums was actually the same link that was used before: http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf

However, notice that this now says 139.15.1.ghost_verizon.Verizon.en.US instead of something like 164......, and it says absolutely nothing about 4.4.2.

I know I'm not the only one involved in this other soak; the forums in there have a number of enthusiastic people who are waiting for it to be pushed, and all the topics are fresh (none of the usual complaining about it not working or being pushed that would have accompanied the 4.4.2 soak test).
[Moto X General] ericsdeadinside:
Yeah that pdf has appeared and disappeared in the last couple of days.
[Moto X General] meant2live218:
Thanks; it was really weirding me out. The forum is the Verizon (B) Software Update section, so I assume (A) might've been the group to soak test 4.4.2.

Also weird is that it's 139, which is... less than 140. Is that supposed to happen? Ever?
[Moto X General] ericsdeadinside:
Idk. I just got this phone on Saturday, I can wait for ota. I'm just enjoying everything working.
[Moto X General] KidJoe:
What says 139? (i'm guessing you didn't type out.. 139.15.1) If your talking about the PDF VZW has posted, then you might just be seeing an older copy of the PDF, meant to go with a past update. Remember, VZW hasn't officially started pushing to all users yet, so you can't go by what their support site or pdf says yet.
[Moto X General] meant2live218:
Yeah, you were right about what number I was looking at. That was the link that the Moto people put up in the Soak forum, so I was assuming it was up-to-date. To compound the weirdness, it's the exact same link that was used for the 4.4.2 VZW soak...
[Moto X General] gsk3rd:
Not part of the Soak test and the OTA is currently downloading. Not Rooted, locked bootloader. Says its 155.7 mb. Will update once its installed.

Yep it's 4.4.2.

164.55.2.en.US
[Moto X General] snoking:
Same here. It is installing now. Chris

---------- Post added at 09:52 AM ---------- Previous post was at 09:43 AM ----------

Mine has completed the update. Wife's has not received it and when I check for update, it says it is up to date.

Both completely stock. I have been checking a lot for the update. Maybe they threw a carrot.

Chris
[Moto X General] snoking:
Screen shot.

WiFi did not want to turn on, so I rebooted it again and now that is working.

Chris
[Moto X General] natezire71:
Someone should do a write-up of how to retain root if they are on a non-dev, locked bootloader VZW MotoX.

I have Xposed, so I know I need to disable that... But what about bloatware that's been deleted from the system partition?
[Moto X General] AndKacz:
I have DE Moto X unlocked and rooted. Xposed installed and running Gravity Box. I have the OTA downloaded that pushed is there anything I need to do to keep root before I install the update?
[Moto X General] Theron113:
Thated the normal way, by pulling the update wirelessly. (Not DE, never rooted) I'm sorry to report that my App Ops no longer works. That's really lame... I know that it was never supposed to be a public facing feature, but it was well received. Not to mention a huge boon for the fine-grain customization of security in Android.

In conclusion:

Moto X on 4.4.2 = broken App Ops
[Moto X General] syde1020:
Doesn't work for me. When I run the ota I get an error around 25 percent of the installation process. And when I do it manually I it stops around the same percent says the plus one.apk is to blame. Even after a factory reset then redownloading the ota, its still a no go :(
[Moto X General] kbluhm:
No need to worry about keeping or losing root if you have an unlocked DE:

- disable Xposed

- boot into bootloader/fastboot

- flash stock recovery

- 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

- flash custom recovery

- boot to recovery

- flash SuperSU

- reboot

- re-enable Xposed

- reboot

- BAM

It looks more tedious than it really is. Outside of waiting for the OTA to install it's like fiive minutes of your time, and much of that is waiting out the ~600MB system flash.
[Moto X General] KidJoe:
the "plus one.apk" on your phone doesn't match the check sum in the OTA's manifest file. You need to fix that for the OTA to work. It should show you the folder it resides in too.

Two ways to fix.. find the correct file and put it in place (hopefuly you made a backup before you messed with it), or fastboot flash system from the SBF of the rom on your phone.

EDIT: looking at my phone... there is a /System/App/PlusOne.APK which appears to be part of Google Plus. You can try uninstalling any updates via App Manager. But that shouldn't be a problem
[Moto X General] a1exus:
if anyone have `164.55.2.en.US` to share let me know
[Moto X General] a1exus:
can you share that file?)
[Moto X General] KidJoe:
what exactly are you looking for? the OTA Update? or a real SBF of 4.4.2?

The OTA update which brings you to 164.55.2 (4.4.2) has some mirrors in the OP. Yes, the file name may contain "140.45.5" in it, but that is only because the OTA's have been named with the version the update applies to, not the version that the phone will be updated too..

---------- Post added at 03:29 PM ---------- Previous post was at 03:29 PM ----------

Are the links in OP not working?
[Moto X General] a1exus:
all links are working (as far as I know), i thought maybe there is a different file for OTA vs soak test.
[Moto X General] donslade:
This is exactly what I did this weekend. All my settings were retained. After I re-enable Xposed those settings were retained also. So far so good.

FYI - I have an unlocked and rooted VZW Dev Edition
[Moto X General] syde1020:
Yeah I tried that but stopped myself. Im thinking this is a blessing in disguise.

Not sure i want to lose root yet...

One positive about a failed flash is that it get rid of the ota notification lol
[Moto X General] KidJoe:
No. Not as far as I know.

The links in the OP will update a Verizon X on 140.45.5 (4.4), to 164.55.2 (4.4.2) which matches what the few soak testers have said they received, and the PDF that Verizon had on their web site has in it.

---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------

You wont loose root, but you will loose the Write Protect disable, which is a big deal if you have a locked bootloader. (Dev Edition wont loose WP Disable because of its unlocked bootloader)
[Moto X General] AndKacz:
Thanks!

One last question, how do i disable Xposed exactly? Do I just uninstall it?
[Moto X General] FSXv13:
I'm on an unlocked, rooted, xposed, TWRP, Verizon DE.

I've read 17 pages of this thread.

I believe I did my homework but just want to confirm...

1. Go into Xposed, click on uninstall.

This leaves the previous modules I downloaded on the phone but it is not an issue so long as Xposed is not active.

2. Download the update and place on my phone

(I've downloaded it from OTA but I will use the one from here anyway cause I don't know where to find the OTA one)

3. Flash the stock recovery which was kindly uploaded around page 13.

4. Flash the update

5. Understand I can never go backwards from here without bricking my phone.

6. Use my newly updated phone.

Is this correct?
[Moto X General] chucky7910:
Doesn't flashing stock image completely wipe your data as well.

I have an unlocked rooted dev edition with the vzwentitlement hack. I was thinking all i had to do was remove the hack flash stock and then I could take the OTA (not flash it via recovery).
[Moto X General] KidJoe:
I don't use Xposed, but for the rest yes you are correct.

---------- Post added at 04:36 PM ---------- Previous post was at 04:34 PM ----------

Using RSDLite to flash, without modifying the XML, yes. Using mfastboot to flash system.img does not touch your data, but if you are rooted, you will lose root. (if you have an unlocked bootloader can re-root later)

If the vzwentitlement hack is the only system file you modified, then you should be fine to take the OTA after undoing it and flashing stock recovery.
[Moto X General] LastSilmaril:
VZW Dev Edition - probalos

After the phone initially attempted to install the update while TWRP was still installed, I tried again with the stock recovery. This failed to take (it kept saying update failed) so I decided to wipe, reinstall 4.4 (didn't realize there were mirrors for 4.4.2), and then upgrade to 4.4.2 via OTA.

That worked, except that after reflashing TWRP, when I try to enter recovery, the screen simply says "No command". Anybody know what the story is there?

The only system mod I can remember doing is VZWEntitlement and setting default runtime to ART.
[Moto X General] KidJoe:
If you run the install from inside the stock recovery it should tell you why if failed.

If you get the android laying on its back with "no command" hold vol and hit power. Does that take you to the stock reocvery? if so, you didn't install TWRP correctly.
[Moto X General] LastSilmaril:
Thanks for the quick reply!

Yeah I'm not concerned with why it failed the first time, I'm just trying the get the recovery to work :) I wasn't watching the screen too closely during the installation but I noticed that it finished very quickly (a minute or two) and while the phone reported that it updated successfully at first, under About Phone it still said 4.4 and had the old FW version, and under system updates reported failure and began downloading the OTA update again.

As for the recovery, after initially selecting 'Recovery' from the 'hboot' menu, I get the Android lying on its back/no command. Pressing and holding power and either of the volume buttons doesn't do anything. I tried flashing it again, nothing. Very weird.
[Moto X General] FSXv13:
I hit uninstall on xposed inside the app, flashed stock recovery, did the OTA through the phone. Never lost root, just re-enabled xposed. Phone back to normal. Just need to reflash TWRP if I care to.
[Moto X General] LastSilmaril:
What ended up working was, I flashed the original recovery, and then flashed the twrp recovery again, one after the other with nothing else happening in between. I hope this helps somebody.
[Moto X General] Mr. Orange 645:
When you boot into recovery and see the android on his back press and hold Volume Up for about five seconds. Then while still holding Volume Up, press and release the Power button. Profit.
[Moto X General] bb1981:
I think hashcode said on his thread on rootz that it doesn't work on 4.4 with SELinux...but it does work to run a 4.4.x ROM as long as you flash to the stock slot and have matching kernel/baseband (I think it was 640k's script here that I used to flash both).

On my locked X, I have the latest SS (3.65 AFAIK and linked on rootz) installed while I had root/write protection disabled on the JB camera update (instead of taking the KK update on the last step of SlapMyMoto, I proceeded to run the four commands while on JB then installed SuperSU and safestrap) then downloaded Nitro's eclipse ROM and flashed it to the stock slot. From there I rebooted to bootloader and flashed the 4.4 baseband and kernel. Everything is working so far. Just didn't want to risk an update attempt that would remove the write protection mod and root because that line is used as a hotspot and I use adaway so I froze moto ota just to be on the safe side.

I did however rsd back to stock on my dev edition to take the update then afterwards, flashed TWRP then CyanogenMod.
[Moto X General] LastSilmaril:
It appears the old entitlement hack doesn't work anymore, and moreover that the VzwEntitlementService.apk isn't even part of the distribution. This happening to anybody else?

ED: Apparently there is a new hack here:

http://xdaforums.com/moto-x/themes-apps/mod-native-android-tether-t2657265
[Moto X General] donslade:
Flashing the stock image did not wipe out my data. I checked and everything was still as before flashing. Xposed the modules were still there just not active.
[Moto X General] Max725:
I am trying go through the SlapMyMoto process now - I attached a screenshot of the update message. It says "Android 4.4, KitKat" and doesn't seem to mention any of the 4.4.2 features, but the update number (14045.5.en.US) is the same as the 4.4.2 update, so I just wanted to make sure it's safe to take the update.

Thanks.
[Moto X General] kbluhm:
Install Xposed Framework, then grab a module called Moto Tether and you're all set. Nice and clean, no moving around or editing system files.
[Moto X General] Flexia32:
Your safe. The new 4.4.2 is 164.55.2
[Moto X General] tu3218:
So just to be clear here, I'm still on 4.4 Verizon, locked, and non rooted. Is it still possible to root and than get the OTA to be on 4.4.2? I've been so good on not tinkering with my phones lately, but I hate not having any options anymore to tether. That's the only reason I'd want root. It seems once I have 4.4.2, it's "over" for gaining any root access.
[Moto X General] Flexia32:
As of right now there is no way to get root once on 4.4.2. If you are rooted on 4.4 and take the 4.4.2 you will keep root but Write Protection becomes enabled again. So with write protection enabled again anything you do to the system files (xposed frameworks) will not stick after a hard reboot. You will just need to get used to doing soft reboots and if a hard reboot is done you will have to apply your xposed modules again. I believe that is correct.
[Moto X General] Max725:
You can root by the SlapMyMoto procedure (Downgrade to 4.2.2 -> RockMyMoto -> MotoWPNoMo -> reflash 4.2.2 -> SlapMyMoto); however, based on what others have said, if you take the 4.4.2 OTA after that, you'll most likely maintain root but regain system write protection.

EDIT - Flexia32 beat me to it.
[Moto X General] tu3218:
Hmm thank you both for the information. Cleared it up for me. Maybe I'll research that rooting method but just from browsing around here, it's a "dirty method." Last thing I want to do now is brick my moto x lol I've rooted a lot of phones but the processes were pretty straight foward and automated.
[Moto X General] alhadee12:
Have anyone heard if 4.4.2 is out for AT&T?
[Moto X General] flacco40:
bug ??

When updated to 4.4 on verizon I noticed that the screen doesnt lock or go back to the slide setting I set it to after a missed call. This is a headache because screen stays on, it makes me accidentally open apps and make calls, and runs battery fast because screen stays on. For those who have updated already does 4.4.2 fix this...
[Moto X General] iscott:
NON DEV will loss R/W system access?
[Moto X General] aldouse:
yep. correct.
[Moto X General] KidJoe:
tu3218,

What Flexia32 and Max725 have said is accurate, but to expand on that a little further, if you already have taken the 4.4.2 upgrade, you can NOT downgrade to 4.4 or below, that is why the previous root (SlapMyMoto, RockMyMoto, etc) wont work. And the changes made by MotoWPNoMo are un-done by taking the 4.4.2 OTA update which is why write protection is re-enabled.

---------- Post added at 07:34 AM ---------- Previous post was at 07:22 AM ----------

To repeat...

Those with a locked bootloader who rooted and used MotoWPNoMo that take the 4.4.2 OTA, will likely keep root, BUT Write Protect becomes re-enabled. (i.e. MotoWPNoMo is undone). When Write Protect is enabled, any changes made to /system and the like are not retained after reboot. The 4.4.2 update prevents downgrading flash version, so none of the previous methods work, and JCASE has posted that he doesn't have time to work on 4.4.2. So unless another dev steps up, those with locked bootloaders will likely be out of luck when it comes to 4.4.2 and Root and disabling write protection.

Those with unlocked bootloader who take the OTA update, will retain Write Protection Disabled status, and likely keep root. (and if they loose it, they can always re-root via custom recovery & SuperSU anyway).
[Moto X General] AndKacz:
Is it necessary to flash stock system? Won't I lose my data?
[Moto X General] donslade:
I flashed the stock system because I had some mods and wanted to be completely stock for the OTA to work. I did not lose any of my data or settings. After the OTA I retained all my settings and installed programs including Xposed and the modules I had download and their settings. I flashed TWRP and re-rotted and was good to go.
[Moto X General] KidJoe:
The OTA has a manifest file in side which contains check sums of the files it wants to update. It compares the check sums in the manifest against those files on your phone. If there is a mismatch, the update fails. NOTE: there are some "non-system" items checked like the bootloader, recovery, and a few more things.

Files in /SYSTEM are what most users mess with once they've rooted. Flashing stock system is the "quickest" and "easiest" way to get your phone's system partition back to stock, without you having to hunt down and manually undo any changes you might have made.

"mFastboot flash system system.img" does NOT touch your data.

That being said, if you installed Xposed, just uninstall it. If you did the tether entitlement hack, just un-do it, and if that is all you've changed, you're fine and don't need to flash system.
[Moto X General] nhizzat:
Just for clarification, no changes can nor will be made without a reboot into "recovery". Once there, changes can and will be made. Those changes will survive even when booted normally.
[Moto X General] KidJoe:
So you're saying those who take the update with locked bootloader and Write Protection becomes enabled again can not change any files in /system, even temporarily?

Some recent posts of those with locked bootloaders stated they could make changes, and they survived until they did a "hard boot" ...

Since I have dev edition with unlocked bootloader, I can't test/experiment for myself right now, so I'm going by the current trend of posting. So if WP Enabled means they can't even make temporary changes, that is very important.
[Moto X General] tcollum:
Changes will survive a soft reboot. Not a hard one.
[Moto X General] AndKacz:
Yeah only changes I made was within Gravity Box. Did not do the tether hack though. Is it better to do the OTA or flash the update that uploaded in this thread? I feel if I do the OTA I should flash system.img so the likelihood of a mismatch does not occur.
[Moto X General] syntrix:
Locked bootloader, you can't mount /system rw anymore.