yashsingh1/xdaforums huggingface dataset:
[Moto X General] Travisdroidx2:
That's what I thought. I would suggest flashing the most recent 4.4.4 from Verizon and make sure your bootloader and gpt.bin are the correct version before doing so. You guys having this issue looks like it is due to the state of your device and what ever you have done with it in the past. Remember if the bootloader or gpt.bin are downgraded you at a high risk for a brick.

---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------

Buy your device new or from somewhere like Ebay? Have seen people selling moto x on Ebay with miss matched partitions.
[Moto X General] rskyline:
I already flashed the latest image from the official Motorola page and still get that.

Enviado desde mi XT1060 mediante Tapatalk
[Moto X General] bigshotproducer:
Bought from Moto. BL unlocked via middlemen.
[Moto X General] Travisdroidx2:
Not sure what to say then. I never flashed any non Verizon firmware to my phone and had no issues at all. I have flashed CM 5.1 before and returned to stock with no issues. But another carriers firmware is too risky for me. Hopefully someone that knows more than me can help you out.
[Moto X General] billycar11:
i think the problem is you are flashing bootloader unlocked consumer devices with dev imgs they have different build numbers
[Moto X General] rskyline:
Tell me something. Do you got an ota on KK like a month ago?

Enviado desde mi XT1060 mediante Tapatalk
[Moto X General] Travisdroidx2:
Hmm that is weird then. In theory you should be fine if your device is stock with just a unlocked bootloader. I have a dev edition and have flashed tons of builds. I just flash it back to complete stock and never had any issues.

---------- Post added at 01:13 AM ---------- Previous post was at 01:12 AM ----------

Yes.
[Moto X General] bigshotproducer:
I guess I should just flash 4.4.4 stock and try from there.
[Moto X General] rskyline:
I have a Dev edition image and a Dev edition factory image. Do you mean the ota zips?

Enviado desde mi XT1060 mediante Tapatalk

---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------

Well I never get that ota and I think that's the issue. But I can't find that ota to flash it manually either.

Enviado desde mi XT1060 mediante Tapatalk
[Moto X General] billycar11:
the ota is for the non developer edition and you flashed a dev img on your non dev device that works fine but they have different build numbers there will be an ota for dev edition too so wait for that or flash the consumer img and do the otas
[Moto X General] rskyline:
I have a dev edition..

Nobody here got the update on Dev edition??

Enviado desde mi XT1060 mediante Tapatalk
[Moto X General] bigshotproducer:
Here's what I have going on right now... Best option just back to 4.4.4 stock and start from there? Thoughts? Thanks!
[Moto X General] rskyline:
Is your device a Dev ed?

Enviado desde mi XT1060 mediante Tapatalk
[Moto X General] bigshotproducer:
No. Retail. Bought from Moto. BL unlocked via middleman. Rooted.
[Moto X General] gakirby:
For what's it's worth, I updated to this http://www.apkmirror.com/apk/google...ices-8-1-15-2250156-236-android-apk-download/ and now I'm no longer getting a Google Play Services issue. I had manually updated to the -036 version the other day to get Android Pay to work, so I am likely partially to blame for the issue.
[Moto X General] Travisdroidx2:
I have a Dev edition and the OTA pushed and flashed just fine.
[Moto X General] rskyline:
You got the ota by itself or you did flash manually? Also, you know which version u have before updating?
[Moto X General] Njrani6:
:thumbup::thumbup::thumbup:
[Moto X General] Travisdroidx2:
I went into settings and hit the system update and received it. I am at work so don't remember the latest build number from my previous version of 4.4.4 kit kat. I never modify my device without having the stock images first. I did flash back to stock and took the OTA a couple of months ago. So that was the most recent build I was on.
[Moto X General] rskyline:
Well if you can, tell me the stock image you have on your computer, maybe i can start from it.
[Moto X General] Njrani6:
:thumbup::D:thumbup::thumbup:
[Moto X General] Meticode:
I never rooted or unlocked my phone I had a regular Moto X (not Dev Edition). After the update I was getting the Google Services sign-in bug. My phone ran fine after I got past that, battery seemed okay. I just turned it off/on with no problem at all. So far, so good.
[Moto X General] imnuts:
There is absolutely no difference in the firmware on devices of the same model. The XT1060 developer image from Motorola is the same as what retail models received over the air, as are all updates.

Sent from my Nexus 6
[Moto X General] raddacle:
I'm having the same problem, but I noticed its expecting KXA21.12-L1.26 where I have KXA21.12-L1.26.1

What should I do? Should I flash KXA21.12-L1.26 first or will I have a bootloader problem if I do that?
[Moto X General] Jizzylax:
Having no issues so far. Did a factory reset though.
[Moto X General] rskyline:
Same here, that's the build present here, but OTAs expect KXA21.12-L1.26.26 or KXA21.12-L1.26.3 so that mismatch abort the update.
[Moto X General] bigshotproducer:
So, the fix is...?[emoji52]
[Moto X General] rskyline:
I have all the fukin day searching for that fix mate :(. I just trying to download the latest firmware on motofirmware but my internet sucks hard also. Try that and lemme know. Mine is a Dev Ed running the latest from the Motorola recovery images page.

Enviado desde mi XT1060 mediante Tapatalk
[Moto X General] Talguy:
Just got the update this afternoon. Lollipop definitely has a learning curve
[Moto X General] raddacle:
Well I just downloaded KXA21.12-L1.26 Do I flash it?
[Moto X General] bigshotproducer:
Yeah, gonna flash 4.4.4 from Moto in the morning. Unless Someone finds a solution overnight.
[Moto X General] BADDINOROX99:
I just took the leap since there was never going to be any boot bootloader unlock method or Root method for this device anyway..everything seems to be running smooth so far
[Moto X General] raddacle:
Alright so I think I got it. I flashed just the system.img from this file https://cloud.mail.ru/public/64a43f...Lollipop/XT1060_Verizon/Stock_RSD_before_OTA/ and now its installing the updates

EDIT: MAKE SURE YOU REBOOT BETWEEN UPDATE 1 & 2 AND LET ANDROID APPS UPGRADE
[Moto X General] AndrewNeo:
So I finally checked the recovery logs in /cache and I'm getting

Super disappointing. If I have to reflash I'll wait for Moto to release the 5.1 images, not going to bother 4.4.4 OTA'd all the way up to 5.1.

Edit: It seems that recovery has it's own build.props file? Is there a way to get a recovery image from someone that has run the first patch but not the second?

Edit 2: Flashing the RSD recovery.img bumped the error to 4.4.4 missing the -4. Looks like I need to patch recovery from the OTAs somehow?
[Moto X General] SmokeyDP:
Does anyone else notice that the 'trusted bluetooth devices' is now gone? My phone used to not lock if it was connected to my car.

EDIT: Just found out its now called 'Smart Lock' in the security settings.
[Moto X General] Liamfm:
Damn, went back to my stock 4.4.4, but it says my software is up to date. Haven't replaced my recovery yet with stock, but that shouldn't effect it saying the update is available right?
[Moto X General] Dadud:
I saw a link a few pages back (i want to say between page 36-38 that had a link containing 3 OTA zips, the one for the 911 fix back in june (which i assume is the one you're missing) and the newest 2 released today.
[Moto X General] 92slammer:
well mine got the update but now my data isnt working......on straight talk
[Moto X General] rskyline:
Tried those also, didn't match the fingerprint :(.
[Moto X General] thekendog:
What a piss poor update. Every single reboot requires apps to be optimized. Takes 15 minutes if you want to restart your phone. Motorola had over a year to get this **** out and somehow f'ed it up. No freaking way I'd buy another phone from them.
[Moto X General] rocketsaucev2:
Would this help anyone out lol. Y'all been messing with your phones too much without proper knowledge or having full fxz images in order to return to stock when tinkering. Here's a run down of the ota's for this device. I also have the fxz for the 212.55.26 version of this phone. If anyone wants I can upload a copy if it would help.

Sent from my XT1575
[Moto X General] AndrewNeo:
Personally I need the recovery partition from 4.4.4-KXA21.12-L1.26-4 (212.166.4), which isn't available as a flashable img from anywhere I can find. Last is L1.26 with no -4, which the OTA still won't flash from.
[Moto X General] rocketsaucev2:
Well here's the recovery img from the version I mentioned, which is older but can't hurt to try. https://drive.google.com/file/d/0B28ubovBBGskLVR1c1F6Qm9ULTg/view?usp=docslist_api

Sent from my XT1575

---------- Post added at 10:58 PM ---------- Previous post was at 10:52 PM ----------

Definitely not seeing that. This device is insanely responsive and quick after this update. Reboots are normal as always, save for the boot logo showing a bit longer before the animation starts. Moto x first gen still bringin it

Sent from my XT1575
[Moto X General] rskyline:
You missed the official recovery image for DEV ED xt1060 which ends on 26.1, which doesn't allow this otas as well.
[Moto X General] rocketsaucev2:
There is no version ending in 26.1. Remember this is the Verizon moto x, the XT1060, not any other version of the first gen Moto X. There is a grand total of zero differences from the 'developer edition' XT1060 and a regular XT1060 with an unlocked bootloader. The software is exactly the same. If you flashed a part of a system from another model, that isn't anyone's fault but yours and it looks like your Moto X has been flashed in such a way.

I also mentioned this recovery is older, from the first 4.4.4 update for this Verizon version

Sent from my XT1575
[Moto X General] raddacle:
Is there any way I could get the recovery.img for the 5.1 build that came out today?
[Moto X General] rskyline:
I said it was your fault or anyone's here fault? Let me introduce to you, the Motorola Moto X 1st Gen Verizon Developer Edition Model XT1060 which the latest 4.4.4 build is called KK-4.4.4-KXA21.12-L1.26.1-1 (VZW).
[Moto X General] rocketsaucev2:
Just saying you're posts indicate you've flashed firmware not for the xt1060, dev edition or not. I've never had a kitkat firmware on my XT1060 that had a build number with that 1-1 on the end. Only one with just the 26, the 26-3 and 26-4. Only what is in the screen shot I posted and my update went smooth as silk without a hitch and the phone is flying as it always has it seems.

Sent from my XT1575
[Moto X General] rskyline:
If you are so aware of my post you should know already that i just flashed system and boot partitions before, which never could get any OTAs as well, but now I'm here on the XT1060 thread what should mean that i have a XT1060 as well. Now i have the stock rom made for this device which is 26.1-1. So maybe you never got that because you don't have a DEV ED, or you don't download official recovery images.

I've found that the issue i was having, as other mate here said before, is that Dev Ed will have a different OTA that the normal xt1060.
[Moto X General] rocketsaucev2:
Alright well mine works and there's never been a difference between the dev and non dev with unlocked bootloader devices on vzw and I've never had a system version you are mentioning. *shrugs *

Sent from my XT1575
[Moto X General] rskyline:
Tell that to motorola. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
[Moto X General] Dadud:
I havent had any of those issues, seems like thats a problem that can be fixed with a cache wipe or full wipe.
[Moto X General] raddacle:
Have you experienced the bug where your navigation buttons will pop up when your screen is off and then your screen suddenly turns on and then fades back off? I've been on this update for just a few hours and its happened quite a bit already
[Moto X General] Jizzylax:
Nope. No app optimizing on reboot issue either.
[Moto X General] fopoku2k2:
Yaaaaay. I just updated my Moto x
[Moto X General] s5610:
How about flashing VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip and start applying OTA on it?

You current bootloader version, btw?
[Moto X General] imnuts:
No it won't. If all of the files on the phone are the same, why would there be a different OTA? A XT1060 is a XT1060, and all will get exactly the same OTA files, developer edition or not. The only difference besides cosmetics between a developer edition and a retail XT1060 is that one you can get a code from Motorola to unlock the bootloader, the other you can't.
[Moto X General] AndrewNeo:
Got it to work! Removed all the device checks, recovery-related files, and the GPT update lines from the OTA zip, flashed it with TWRP, then flashed the gpt.bin with fastboot. Was worried it was broken since it sat at the VZW logo at boot for ages, but I was just impatient, had to wait maybe 10 minutes (then another 30 for optimizing apps). But now I have Lollipop on my dev XT1060!
[Moto X General] jwelsch:
Could I beg you to share your zip/files?
[Moto X General] AndrewNeo:
Unfortunately since it's 730mb I don't have a place to put it, and it'd take hours to upload.

Here's the lines to take out of updater-script, though:

(use Blur_Version.212.166.4.ghost_verizon.Verizon.en.US.zip)

2,5d1
< getprop("ro.build.fingerprint") == "motorola/ghost_verizon/ghost:4.4.4/KXA21.12-L1.26-4/7:user/release-keys" ||
< getprop("ro.build.fingerprint") == "motorola/ghost_verizon/ghost:5.1/LPA23.12-39.7/7:user/release-keys" ||
< abort("Package expects build fingerprint of motorola/ghost_verizon/ghost:4.4.4/KXA21.12-L1.26-4/7:user/release-keys or motorola/ghost_verizon/ghost:5.1/LPA23.12-39.7/7:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
< getprop("ro.product.device") == "ghost" || abort("This package is for \"ghost\" devices; this is a \"" + getprop("ro.product.device") + "\".");
421d416
< apply_patch_check("/system/etc/recovery-resource.dat", "205a2f233aae3a81bc71dde0c4304363e9f127d1", "63a5abee9a593e7d42a805b52e292d1ae3e54b22") || abort("\"/system/etc/recovery-resource.dat\" has unexpected contents.");
1303,1304d1297
< sha1_check(read_file("system/bin/install-recovery.sh"), b54528cf9ebba39534b768ad9108a4732e1eff4a) ||
< apply_patch_check("/system/etc/install-recovery.sh", "b54528cf9ebba39534b768ad9108a4732e1eff4a") || abort("\"/system/etc/install-recovery.sh\" has unexpected contents.");
3863,3865d3855
< assert(apply_patch("/system/etc/recovery-resource.dat", "-",
< 205a2f233aae3a81bc71dde0c4304363e9f127d1, 313421,
< 63a5abee9a593e7d42a805b52e292d1ae3e54b22, package_extract_file("patch/system/etc/recovery-resource.dat.p")));
6899d6888
< rename("system/etc/install-recovery.sh", "system/bin/install-recovery.sh");
7201d7189
< set_metadata("/system/bin/install-recovery.sh", "uid", 0, "gid", 0, "mode", 0750, "capabilities", 0x0, "selabel", "u:object_r:install_recovery_exec:s0");
7492,7494d7479
< assert(package_extract_file("gpt.bin", "/tmp/gpt.bin"),
< motorola.update_gpt("/tmp/gpt.bin"),
< delete("/tmp/gpt.bin"));

Also you may have to delete the MANIFEST.MF file, not sure. Make sure to flash gpt.bin in the zip root with the Motorola fastboot tool, too.
[Moto X General] CallOfHonor100:
I just got a notification for the system update. I recently bought this mobile and I want to unlock the bootloader first. Should I do that right now or after the update?
[Moto X General] gangrif:
Dev edition? If so, I don't think it will matter before or after. Both should wipe all of your user data though. The system doesn't get wiped though. So whatever update level you're at will still be there after the unlock. Also, I don't believe the update will relock the boot loader. Maybe someone else can clarify there. They never did on my n7 which I unlocked the day I got it.
[Moto X General] CallOfHonor100:
I'm not sure if its dev edition. How do I check?
[Moto X General] gangrif:
I don't have one either. So I'm not certain. I believe it's printed in the back cover. Also, you can check by going thorough the unlock procedure on moto's web site. It'll tell you if it's not a dev edition before it gives you an unlock code.
[Moto X General] CallOfHonor100:
So is it advisable to unlock bootloader thru their website?
[Moto X General] gangrif:
I think that's the only way. Again. I could be wrong.
[Moto X General] mbonus:
It would say developer edition on the back. If you have a regular one and it is on 4.4.2 you can unlock for $25 via sunshine

Either way, do not take the update until you figure it out assuming you want to unlock.
[Moto X General] Reserved Name:
So it took awhile but I'm on stable 5.1 with no reboot problems and I have root and native tethering hacked through xposed and the boot loader never even locked up again. Seems fast enough and I like the aesthetics, my old battery saving app doesn't work now though and I don't think the built in battery saver does anything for it until the battery is nearly gone anyway. Hint: if you want to score some points on the lollipop easter egg game found by clicking on the android version in settings, just open developers options and turn animation up to 10x
[Moto X General] Liamfm:
I can't even get it to tell me I have an update available. Do I need to go back to stock recovery just to get that notification?
[Moto X General] bigshotproducer:
So I d/l VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml -- RSD'd w/keep data. First update went fine had to manually do 2nd part, but it worked.
[Moto X General] KidJoe:
You are correct the Retail and Dev Edition use the SAME roms, SBF's, OTAs, etc.

I wonder if some are getting confused because there was a thread about a funky versioned SBF on Moto's site for the "Developer Images". While still 4.4.4 It was slightly newer than the latest OTA that was pushed at that time. I'd have to find the thread discussing it, but the file was later fixed.

I don't recall if it was for the XT1060 or the XT1053.

EDIT: It was the XT1060 and here is a link to the thread -> http://xdaforums.com/moto-x/moto-x-qa/xt1060-weird-build-version-t3122215

That version was never pushed OTA to the phones, it was only those who downloaded the file from Moto at the time and flashed it, that got it.

HOWEVER, it does not appear to be the same version those with the failed finger print message are running, so I don't know where that one came from.
[Moto X General] King Speedy:
Has anyone compared this to CM12.1? I'm running that now on my VZW DE and could be compelled to switch over to get Moto Voice back.
[Moto X General] grhomes:
Anyone had any no sim card errors after the update to 5.1? I have a totally stock never rooted BL locked XT1060 that will not recognize the sim card. WiFi won't work either- I've cleared the cache from the storage settings and am currently formatting the /cache partition and it keeps hanging while it does that...

Edit: Cache wipe finally finished. No change. Still sim error. Decided to do a factory reset in stock recovery, now the Setup Wizard hangs and it still shows as a sim error in the top corner. Anyone with any thoughts/suggestions? I essentially have a setup wizard paperweight atm...
[Moto X General] strikeir13:
For those getting the fingerprint error (and don't want to edit the updater script), here is what I did:

1. Flash back to 4.4.2 using the images on Moto's page

2. Erase user data.

3. Boot up and let the OTAs do the job.

Not ideal, but I was planning on a data wipe after upgrading anyway. Plus, if you're flashing images, you're unlocked, so it's easy to root/backup/restore information with TiBu+Dropbox.
[Moto X General] Burkert:
Received the 5.1 update last night, and, was indeed hopeful that it would include VoLTE. Please note, I'm using the XT1060 Developer Edition on T-Mobile. Afraid that even with the 5.1 update, VoLTE appears to remain disabled / invisible.

For anyone else in a similar circumstance, it would appear that T-Mobile limits use of VoLTE to LTE Band 12 (Which the Moto X 2013 Developer Edition lacks... it includes Bands 4 & 13).

While on topic... has anyone who has accepted the 5.1 Update, and, using this phone on Verizon, been able to confirm if VoLTE (i.e. - Verizon Advanced Calling) is enabled / available?

Thank you,

Burkert
[Moto X General] _litz:
Well, so far I've been impressed and unimpressed.

As a device, this thing is buttery smooth on 5.1.

Usable? Not so much. It freezes (just like my Nexus 9 used to do), then unfreezes some minutes later.

It also fails at a basic required function : phone calls. They go through, then one of the above freezes occurs, and the call drops. Esp. when using speakerphone.

I've also cannot filter any lockscreen notifications. No matter apps are selected/unselected in the moto display config, it is showing all notifcations, no matter what.

We waited HOW LONG for this buggy mess?
[Moto X General] Vizsla_Buddy:
Moto X 2013 Verizon Lollipop Update Received

I just got the update. Heads up, it broke by Outlook.Com (O365 for free) connection for contacts and calendar. It is all wacky. Some contacts come down, some don't. Calendar entries all appear twice (they are correct on the server). I have deleted the account and cleared the cache. In rebooting the phone, it has gone into an "Optimizing" and then "Starting" process that has now taken 30 minutes.

This is very concerning.
[Moto X General] Travisdroidx2:
Weird I am not having these issues.

---------- Post added at 04:56 PM ---------- Previous post was at 04:56 PM ----------

None of these issues also.
[Moto X General] _litz:
I'm really hoping this is just teething pains. This was sent out as an upgrade.

An upgrade shouldn't require either a factory reset, or a downgrade back to the previous version.

Ran into another issue ... after the alarm clock was finished and shut off, the lock screen froze, with just a back arrow on the screen. Black screen otherwise.

Could not unlock or do anything; had to reboot.
[Moto X General] appletonpunk:
I'm just curious, are the people having issues after upgrading coming from a clean install or factory reset? Or just a regular dirty upgrade?
[Moto X General] Travisdroidx2:
Again I am not seeing any of these issues on my device. I did not do a factory reset or flash stock before taking the OTA. Not sure why you are having so many issues. I used my alarm a couple of times since yesterday with no issues or any freezing at all for that matter.
[Moto X General] bigshotproducer:
Anyone getting the "Update Gloogle Play services" constant notification? I'm on the most current version via apkmirror. Anyone else?
[Moto X General] grhomes:
So. I downloaded the large 5.1 update hoping that I could apply the update from the sdcard in stock recovery, (I am already on 5.1 but it won't recognize the sim card and wi-fi is stuck trying to turn on) and it goes through the process and comes up with an error on the modem : [IMG="Recovery Error"]https://drive.google.com/file/d/0B-bTyp8eGyCUcW1LQ3F4V0ZScTA/view?usp=sharing[/IMG]

I can boot the phone and it eventually quits the activation process as it thinks there's no sim card, then sits on trying to get wifi to turn on: [IMG="Sim Error"]https://drive.google.com/file/d/0B-bTyp8eGyCULW5ONW1Jc3FudUE/view?usp=sharing[/IMG] [IMG="Wifi Hang"]https://drive.google.com/file/d/0B-bTyp8eGyCUSXhxY2twQ2U2SEk/view?usp=sharing[/IMG] [IMG="About Phone"]https://drive.google.com/file/d/0B-bTyp8eGyCUSFZKY0JKbHFEMmc/view?usp=sharing[/IMG]

Any suggestions? I am at a loss.

Edit: I have no idea why those pictures are failing, here's an imgur album: imgur(dot)com/a/NMPCT
[Moto X General] bigshotproducer:
Which version of Xposed are you using, I'm just getting back set up with root and need some tethering this afternoon. Thanks!
[Moto X General] dcooterfrog:
i broke something badly but nowe I can finally get into recovery as well as fastboot.

something is wrong wiht boot

does any one have a complete nanadroid of verizon lolipop. i suppose I dont need data.

but the rest would be good.