Database Users

[GUIDE] Update XT1095 Pure Edition to Latest Android Lollipop *DISCONTINUED*

Well, there's been a lot of confusion about over in the 5.0 OTA thread about how to get onto the latest build of Lollipop.
**********UPDATE********
Sorry guys, I no longer have a Moto X and as such have to discontinue support for the downloads in this thread; I can no longer keep up with a device I don't have
If you can get the files I mention elsewhere, most of these instructions should remain applicable.
Thanks
*****************************
So how does one get onto the latest OFFICIAL build of Android 5.0 on their Moto X 2014 Pure Edition (XT1095)? Here's how (and it most likely involves a data wipe)
Have an XT1092 or XT1097? Well fear not! It's easy to convert.
Follow this guide later in the thread (thanks to@steff999 for this!):
http://forum.xda-developers.com/showthread.php?p=56700701
And if you have cellular problems on your 1092 or 1097, follow this post by @sbtm1337:
http://forum.xda-developers.com/showthread.php?p=56778275
****If you damage anything in the process, it's no one's fault but yours (it's hard to mess this up, though )****
Step 0:
Make sure you have basic fastboot and adb knowledge; have Motorola drivers on your computer.
Enable USB debugging on your phone if you haven't yet.
Then, go to the home screen. Plug in the USB cable into your computer, and then into your phone.
If you haven't done anything like this before, it should prompt you for RSA authorization. Check always allow, and then yes.
Step 1:
Determine where you are in the process.
You can be in one of 5 places:
A: On 4.4.4 KitKat, un-tampered
B: On 4.4.4 KitKat, tampered (root, /system mods, etc.)
C: On 5.0 Lollipop LXE22.39-6 un-tampered
D: On 5.0 Lollipop LXE22.39-6 tampered
E: On ANY other version
If option A, go to step 4 (no wipe!)
If option C, go to step Q (keep your data )
If option B, D, or E, go to step 2 (gonna have to wipe...)
******Unless you're on option A or C, you NEED an unlocked bootloader!******
Step 2:
Download the stock 4.4.4 firmware.
It's on Motorola's site, but you have to request access and wait a while. I've mirrored it in .zip form for easy access:
https://onedrive.live.com/redir?resid=227F163CB35629DA!20267&authkey=!AMWPTB3ICDtezYs&ithint=folder,
Extract the .zip on your PC. On OneDrive, open the Moto Fastboot folder and download the fastboot corresponding to your OS (Windows or Linux, no Moto Fastboot exists for Mac unfortunately).
***Take the fastboot file here and replace the one in whatever directory you have your current one***
***Move the files from the 4.4.4 Firmware to the same place you have the new fastboot.***
***There may be a file called fastboot in the 4.4.4 Firmware folder. Delete that, you only need the one from OneDrive***
Step 3:
Reboot your device to fastboot.
Enter these commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
Don't sign into any accounts, and skip all the setup.
Step 4:
Now, download the 4.4.4 to 5.0 OTA zip from here:
https://onedrive.live.com/redir?resid=227F163CB35629DA!20267&authkey=!AMWPTB3ICDtezYs&ithint=folder,
Put it in the download folder of your Moto X.
Step 5:
Reboot to stock recovery. Once you see the Android and a red triangle above it, press volume up for 3 sec and then lock right afterwards. Then let go immediately.
Select "apply update from sdcard".
Navigate to your download directory, and select the update zip.
Let it flash.
Reboot.
Step 6 **IMPORTANT**:
Now you've got L! But... Not so fast.
Skip through the setup, and go to factory reset in settings (enjoying the beauty along the way).
Here's why: Android L has 256-bit encryption (up from 128-bit on KitKat), however it only takes effect if you factory reset within L.
It's ultimately up to you whether you reset or not, but coming from a clean KitKat install like most this is a great benefit for little effort.
If you've made it this far without a wipe and don't want to re-set up your phone, it will work without it, but to ensure smooth operation and for security purposes I'd highly recommend the reset (many who haven't done this reset have reported numerous FCs and other issues as well).
Step Q:
All you have to do now is download the 5.0-6 to 5.0-11 OTA from my OneDrive and flash it in stock recovery. Not much to it!
*If you have an alternate modem, you'll be ineligible for this .6-.11 OTA. It's likely that you'll have to wipe, flash 4.4.4, and redo the steps it took to get you to -6 but with the -11 OTA file.*
And...
BAM!
LOLLIPOP!
YEAHHH BUDDY
Enjoy
Hope this helps some folks! Hit the thanks button if it does!
Sent from my Moto X Pure Edition using Tapatalk

SolarTrans said:
Well, there's been a lot of confusion about over in the 5.0 OTA thread about how to get onto the latest build of Lollipop.
In case you haven't followed it all, here's the story:
On the 8th or 9th of November 2014, Motorola started a very limited soak test with L build LXE22.39-5. That OTA got leaked, and many of us tried to get back to stock 4.4.4 to take the OTA. On 11/11/14, they started another, more widespread soak test. The build in that one is LXE22.39-6. In order to get from the first soak test build to the next, a "delta" OTA was required, and it was only sent to those officially enrolled in the first wave. That was never leaked, so in order to get onto the -6 firmware, a downgrade to stock 4.4.4 was necessary.
So how does one get onto the latest (as of now) build of Android 5.0 on their Moto X 2014 Pure Edition (XT1095)? Here's how (and it most likely involves a data wipe):
****If you damage anything in the process, it's no one's fault but yours****
Step 0:
Make sure you have basic fastboot and adb knowledge; have Motorola drivers on your computer.
Step 1:
Determine where you are in the process.
You can be in one of 5 places:
A: On 4.4.4 KitKat, boot loader locked, untampered whatsoever
B: On 4.4.4 KitKat, boot loader unlocked, tampered
C: On 4.4.4 KitKat, boot loader unlocked, untampered whatsoever (not even root) (extremely unlikely)
D: On 5.0 Lollipop build LXE22.39-5 boot loader unlocked
E: On 5.0 Lollipop build LXE22.39-5 boot loader locked
If option A or C, skip to step 4 (phew, no data wipe needed )
If option B or D, go to step 2 (you're getting wiped, sorry)
If option E, unlock your bootloader through Motorola's website (yup. Wipe too) and go to step 2
Step 2:
Download the stock 4.4.4 firmware.
It's on Motorola's site, but you have to request access and wait a while. I've mirrored it in .zip form for easy access:
https://onedrive.live.com/redir?res...0263&authkey=!AM8xPNkiWBzJ3iY&ithint=file,zip
Extract the .zip, and open the folder corresponding to your OS (Windows, Linux, etc).
Take the fastboot file here and replace the one in whatever directory you have your current one.
Move the rest of the files not in the OS folders to the same place you have the new fastboot.
Reboot your device to fastboot.
Enter these commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
Don't sign into any accounts, and skip all the setup.
Step 4:
Now, download the OTA zip from here:
https://onedrive.live.com/redir?res...0264&authkey=!APWqFt6yzNh4mSU&ithint=file,zip
And put it in the download folder of your Moto X.
Step 5:
Reboot to stock recovery. Once you see the Android and a red triangle above it, press the volume up and lock buttons simultaneously for 3 seconds and let go.
Select "apply update from sdcard".
Navigate to your download directory, and select 5.0OTA.zip.
Let it flash.
Reboot.
Step 6 **IMPORTANT**:
Now you've got L! But... Not so fast.
Skip through the setup, and go to factory reset in settings (enjoying the beauty along the way).
Here's why: Android L has 256-bit encryption (up from 128-bit on KitKat), however it only takes effect if you factory reset within L. It's ultimately up to you whether you reset or not, but if you're coming from a clean KitKat install like most this is a great benefit for little effort.
If you've made it this far without a wipe and don't want to re-set up your phone, it will work without it, but to ensure smooth operation and for security purposes I'd highly recommend the reset (many who haven't done this reset have reported numerous FCs and other issues as well).
And...
BAM!
LOLLIPOP!
YEAHHH BUDDY
Enjoy
Hope this helps some folks! Hit the like button if it does!
Sent from my Moto X Pure Edition using Tapatalk
Click to expand...
Click to collapse
A lot of people including myself have had troubles with the motoboot command. It comes up with a downgrade from TZ ( or something like that)
Have you had any problems?
Currently I'm on 4.4.4
I was on the first soak and tried to get back to 4.4.4 but my phone bootloops and then goes to recovery when I try to update to the newest L.
I have to flash the system from 4.4.4 And the boot to get my phone back.

matt99017d said:
A lot of people including myself have had troubles with the motoboot command. It comes up with a downgrade from TZ ( or something like that)
Have you had any problems?
Currently I'm on 4.4.4
I was on the first soak and tried to get back to 4.4.4 but my phone bootloops and then goes to recovery when I try to update to the newest L.
I have to flash the system from 4.4.4 And the boot to get my phone back.
Click to expand...
Click to collapse
No, I haven't had any problems. I've heard of some people saying that you don't have to flash motoboot (it's the boot loader) to successfully downgrade.
Have you tried flashing everything else from this firmware?
Sent from my Moto X Pure Edition using Tapatalk

I've tried to flash the system, but it tells me something about needing to use a new fastboot. Multi....+++++? Not used anymore.
I've tried to flash the gpt but it won't work either. I've done boot, fsg, modem, that is it.
System, gpt, motoboot are all a no go.
Kinda lost.
I'm at work now, so I can't do much for about 7 more hours.

Thanks for this - so this is the official 5.0 OTA? Not the Soak test?

SolarTrans said:
Extract the .zip, and open the folder corresponding to your OS (Windows, Linux, etc). Take the fastboot file here and replace the one in whatever directory you have your current one.
Click to expand...
Click to collapse
There are no folders in the archive with stock 4.4.4 firmware and there is no fastboot.exe for Windows inside. Where I can get fasboot for Windows to flash so big system.img ?

It's in the os folders - that fastboot did not work for me however. I just used sdk fastboot.

Quick question
Sorry for a noob question, but am I correct in assuming this will function fine on a Mac using the Linux fastboot? And does it need to be placed in the same directory as the files associated with the Android SDK? Or can it be in its own folder?
Thanks for any help!

Sdobron said:
It's in the os folders - that fastboot did not work for me however. I just used sdk fastboot.
Click to expand...
Click to collapse
I have downloaded both archives (1st link in OP, 2nd in another tread) and both do not have any folders inside. There is "fastboot" file in the archives and looks like it is for Mac and not for Windows.
So does it means that sdk fastboot flashed sustem.img successfully ?

Thanks to @SolarTrans and everyone else, both here and on MFN, I was able to reflash back to 4.4.4, update OTA to the Lollipop soak test, and restore the logo file to get rid of the ugly bootloader unlocked warning screen
This has been a great resource, and first time doing all of this. Definitely a little confusing at first, but I figured it out. Thanks everyone.

matt99017d said:
I've tried to flash the system, but it tells me something about needing to use a new fastboot. Multi....+++++? Not used anymore.
I've tried to flash the gpt but it won't work either. I've done boot, fsg, modem, that is it.
System, gpt, motoboot are all a no go.
Kinda lost.
I'm at work now, so I can't do much for about 7 more hours.
Click to expand...
Click to collapse
That's because you need the motorola fastboot file in the 4.4.4 zip
Sent from my Moto X Pure Edition using Tapatalk

Sdobron said:
Thanks for this - so this is the official 5.0 OTA? Not the Soak test?
Click to expand...
Click to collapse
It's the 2nd soak test, which some believe is the final OTA.
If it isn't, however, I'm registered as part of that soak test so I'll be able to post the update
Sent from my Moto X Pure Edition using Tapatalk

greggov said:
Thanks to @SolarTrans and everyone else, both here and on MFN, I was able to reflash back to 4.4.4, update OTA to the Lollipop soak test, and restore the logo file to get rid of the ugly bootloader unlocked warning screen
This has been a great resource, and first time doing all of this. Definitely a little confusing at first, but I figured it out. Thanks everyone.
Click to expand...
Click to collapse
How did you restore the logo? Just fastboot flash the logo.bin from the factory image?

paul_jones said:
Sorry for a noob question, but am I correct in assuming this will function fine on a Mac using the Linux fastboot? And does it need to be placed in the same directory as the files associated with the Android SDK? Or can it be in its own folder?
Thanks for any help!
Click to expand...
Click to collapse
As I said in the guide, it needs to replace your current fastboot file in your Android SDK (it works for other manufacturers too, it just has some added functionality for Motorola so it's safe to do this).
But yeah you should be fine with the Linux one, although I don't have a Mac so I can't test it
Sent from my Moto X Pure Edition using Tapatalk

Moto Fastboot files are back up guys! They're in my OneDrive, just follow the folders from either link up there
Sent from my Moto X Pure Edition using Tapatalk

Sdobron said:
How did you restore the logo? Just fastboot flash the logo.bin from the factory image?
Click to expand...
Click to collapse
I actually googled around trying to replace it, and it linked me back to a thread here. Downloaded the logo.bin file and flashed it. It's the stock M logo with "powered by Android" or whatever that says

greggov said:
I actually googled around trying to replace it, and it linked me back to a thread here. Downloaded the logo.bin file and flashed it. It's the stock M logo with "powered by Android" or whatever that says
Click to expand...
Click to collapse
Care to link that thread? Thanks

Sdobron said:
Care to link that thread? Thanks
Click to expand...
Click to collapse
here you go!

Anyone did try on XT1097 (Brazilian model)?

Updated OP with Moto Fastboot files! There should be no problems now
Sent from my Moto X Pure Edition using Tapatalk

How I upgraded my Consumer Cellular Moto G 2014 X1064 to Lollipop

Since I've been lurking all day looking for solutions, I thought I'd share my success story and instructions. I'm a new poster so I can't make links, so I'll do my best to give you an idea if you've got the right link. The fastboot instructions may be a little truncated, so look around if they seem unclear. These are the commands you need to enter, though. I wasn't able to relock my bootloader.
This is for the Consumer Cellular Moto G 2014 X1064. Starting from retail (where you have the Consumer Cellular app):
Unlock the bootloader on Moto's site at motorola-global-portal.custhelp dot com
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder (I was using a Mac with the quick fastboot/ADB tools and just typed them in Terminal):
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader. No Consumer Cellular app.
Grab the torrent file from the thread titled "[OTA] Moto G 2014 XT1064 v22.11.6" on this subforum. It's on page 8, post #73
Rename that file to something simple like update.zip
Use Android File Transfer or similar (I had a Mac) to put that on the root of your device. It was at the same level as the Downloads folder. If you can see that, you're in the right place.
Reboot into fastboot mode
Select recovery mode (press volume down to highlight it, then volume up to select)
You'll now see an Android guy with a red triangle. Press volume up and power at the same time, let go, and you should be in another text menu.
Select boot from SD card (use volume down to highlight it, then power to select)
Select your update.zip
Wait 20 minutes or so while it works
Select reboot when you're finished
That was enough to get me to Android 5. Good luck everyone!

Janus Kirin said:
Since I've been lurking all day looking for solutions, I thought I'd share my success story and instructions. I'm a new poster so I can't make links, so I'll do my best to give you an idea if you've got the right link. The fastboot instructions may be a little truncated, so look around if they seem unclear. These are the commands you need to enter, though. I wasn't able to relock my bootloader.
This is for the Consumer Cellular Moto G 2014 X1064. Starting from retail (where you have the Consumer Cellular app):
Unlock the bootloader on Moto's site at motorola-global-portal.custhelp dot com
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder (I was using a Mac with the quick fastboot/ADB tools and just typed them in Terminal):
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
You should now be at stock Android 4.4.4 with an unlocked bootloader. No Consumer Cellular app.
Grab the torrent file from the thread titled "[OTA] Moto G 2014 XT1064 v22.11.6" on this subforum. It's on page 8, post #73
Rename that file to something simple like update.zip
Use Android File Transfer or similar (I had a Mac) to put that on the root of your device. It was at the same level as the Downloads folder. If you can see that, you're in the right place.
Reboot into fastboot mode
Select recovery mode (press volume down to highlight it, then volume up to select)
You'll now see an Android guy with a red triangle. Press volume up and power at the same time, let go, and you should be in another text menu.
Select boot from SD card (use volume down to highlight it, then power to select)
Select your update.zip
Wait 20 minutes or so while it works
Select reboot when you're finished
That was enough to get me to Android 5. Good luck everyone!
Click to expand...
Click to collapse
During the first flash, did you not get System Downgrade errors? And after reboot i could still see same Consumer Cellular system version. Did you verify your system version before you updated Lollipop?
I still cant believe it worked for you as i have seen other people still having issues like me where they cannot flash 21.11.17 version because of system not permitting downgrading.
Please add any more insights or if you downloaded the ROM from somewhere else.
Thanks.

zoomingrocket said:
During the first flash, did you not get System Downgrade errors? And after reboot i could still see same Consumer Cellular system version. Did you verify your system version before you updated Lollipop?
I still cant believe it worked for you as i have seen other people still having issues like me where they cannot flash 21.11.17 version because of system not permitting downgrading.
Please add any more insights or if you downloaded the ROM from somewhere else.
Thanks.
Click to expand...
Click to collapse
I didn't get system downgrade errors, no. I unlocked first. Maybe that was it?
My system version was 21.11.23.titan_ccaws.AWSCC.en.US cc

Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?

Janus Kirin said:
I didn't get system downgrade errors, no. I unlocked first. Maybe that was it?
My system version was 21.11.23.titan_ccaws.AWSCC.en.US cc
Click to expand...
Click to collapse
That's the same version I had, and I got the same error as the person above.

chibichn said:
Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?
Click to expand...
Click to collapse
I was not able to lock the bootloader. It shows that warning for five seconds and then starts the boot animation. I'd also like to lock it, but I've decided not to press my luck.

Janus Kirin said:
I was not able to lock the bootloader. It shows that warning for five seconds and then starts the boot animation. I'd also like to lock it, but I've decided not to press my luck.
Click to expand...
Click to collapse
chibichn said:
Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?
Click to expand...
Click to collapse
Thanks a ton Janus & Chibichn, it works and i was able to downgrade and flash Lollipop via recovery!

See this post:
http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Seems to work for me. Happily running Lollipop on my Consumer Cellular G (2014).

Other than the void warranty, any other disadvantage in unlocking the bootloader? Will we get future OTA updates or well have to flash every time?

Thanks, worked for me, for those who aren't able to downgrade, are you sure you got your bootloader unlocked?

Great tutorial, worked exactly as described. Thanks A LOT! Now to root and start restoring my TitaniumBackup.

Thanks for the tutorial, I am having issues on step 14 the installation aborts in recovery. I did rename the zip to update.zip. If some one can point me in the right direction that would be appreciated. Thanks.
Sent from my A0001 using XDA Free mobile app

Thanks a ton for this. Got my less than 24 hour old Moto G upgraded last night. Youre a lifesaver.

root??
work was actually really really perfect! however I noticed that when starting this root and lost without recovery. is normal in this version? because at the end she asked me to reinstall it would root.

I got the xt1064 from consumer cellular and have been trying to replicate the process but with a locked bootloader.
My cc x1064 originally came with 21.11.23.titan_ccaws.AWSCC.en.US cc. I couldn't flash an older US retail build (21.11.17.titan_retuaws.retuaws.en.US - the latest available for download at the time) because of downgrade issues. Locked bootloader wont let you downgrade, image verification issue.
As of today I was able to located the latest US retails aws rom for 21.11.23. I ended up getting it from a different faster mirror than the ones posted in another xda thread.
http://motofirmware.com/files/file/951-retuaws-xt1064-444-kxb2185-23-cid9-cfcxmlzip/
Fastboot flash of this rom was successful. No bootloader/image issues. My consumer cellular rom was removed, cc app was gone, and now my system version reads 21.11.23.titan_retuaws.retuaws.en.US cc ( build # kxb21.85-23). Don't know why the "cc" is still appended to the end of the system version. Baseband version also had CCAWS_CUST in it. Is this an indication that consumer cellular components like the baseband modem files were untouched during the US retail flash?
Anyway, tried all the tutorials on getting OTA to update via stock recovery thru "update form sd" but the update keeps failing. I keep getting message " package expect build finger print of motorola/titan_retuaws/titan_umts:4.4.4/kxb21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan_retuaws/titan_umts:4.4.4KXB21.85-23/30:u Installation aborted."
So the phone is complaining that the package currently installed either had to be 21.85-17 (4.4.4) or lollipop 5.0, in order to flash , but found 21.85-23(4.4.4) on my phone instead, hence it fails because of version mismatch. So in order to update OTA lollipop with a locked bootloader only a currently installed build of 21.11.17 will allow you to do it? If that is the case, I can't downgrade and thus can update the OTA.

diamondjoker5 said:
I got the xt1064 from consumer cellular and have been trying to replicate the process but with a locked bootloader.
My cc x1064 originally came with 21.11.23.titan_ccaws.AWSCC.en.US cc. I couldn't flash an older US retail build (21.11.17.titan_retuaws.retuaws.en.US - the latest available for download at the time) because of downgrade issues. Locked bootloader wont let you downgrade, image verification issue.
As of today I was able to located the latest US retails aws rom for 21.11.23. I ended up getting it from a different faster mirror than the ones posted in another xda thread.
http://motofirmware.com/files/file/951-retuaws-xt1064-444-kxb2185-23-cid9-cfcxmlzip/
Fastboot flash of this rom was successful. No bootloader/image issues. My consumer cellular rom was removed, cc app was gone, and now my system version reads 21.11.23.titan_retuaws.retuaws.en.US cc ( build # kxb21.85-23). Don't know why the "cc" is still appended to the end of the system version. Baseband version also had CCAWS_CUST in it. Is this an indication that consumer cellular components like the baseband modem files were untouched during the US retail flash?
Anyway, tried all the tutorials on getting OTA to update via stock recovery thru "update form sd" but the update keeps failing. I keep getting message " package expect build finger print of motorola/titan_retuaws/titan_umts:4.4.4/kxb21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan_retuaws/titan_umts:4.4.4KXB21.85-23/30:u Installation aborted."
So the phone is complaining that the package currently installed either had to be 21.85-17 (4.4.4) or lollipop 5.0, in order to flash , but found 21.85-23(4.4.4) on my phone instead, hence it fails because of version mismatch. So in order to update OTA lollipop with a locked bootloader only a currently installed build of 21.11.17 will allow you to do it? If that is the case, I can't downgrade and thus can update the OTA.
Click to expand...
Click to collapse
I also noticed that Base Band version stays from Consumer Cellular. Any idea if we should or can flash the Base Band to US Retail? Also as far i read, yes the lollipop update is based on top of 21.11.17 not 21.11.23. There may be a lollipop image on top of 21.11.23 but i am not sure.

^^ personally I didn't care to void the warranty since I picked it up for 75 (gift card for another 75), also the consumer cellular model. Updated it to 5.0 and using it as my spare phone for browsing and web on my secondary line, it works fine. Immediately after the update, getting back into recovery is an issue, haven't tried since but it's been working fine so I'm not complaining.

zoomingrocket said:
I also noticed that Base Band version stays from Consumer Cellular. Any idea if we should or can flash the Base Band to US Retail? Also as far i read, yes the lollipop update is based on top of 21.11.17 not 21.11.23. There may be a lollipop image on top of 21.11.23 but i am not sure.
Click to expand...
Click to collapse
I was successful with the Consumer Cellular XT1064, but I unlocked the bootloader first and left it that way. It is my understanding that this is required to downgrade, but I'm no expert.
The Lollipop *does* update the Baseband, though the CCAWS_CUST was/is appended throughout. Unsure what that is all about (or if it even relates to Consumer Cellular), but it works just fine. I'll paste the various Baseband, System, and Build numbers reported as I progressed below. Perhaps this will shed some light?
___________________________________
Consumer Cellular XT1064 - As found:
Baseband: MSM8626BP_1032.394.88.00R, CCAWS_CUST
System: 21.11.23.titan_ccaws.AWSCC.en.US.cc
Build: KXB21.85-23
___________________________________
After factory retail flash:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
Baseband: MSM8626BP_1032.394.88.00R, CCAWS_CUST
System: 21.11.17.titan_retuaws.retuaws.en.US na
Build: KXB21.85-17
___________________________________
After Lollipop update via adb sideload:
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip
Baseband: MSM8626BP_1032.3105.93.00R, CCAWS_CUST
System: 22.11.6.titan_retuaws.retuaws.en.US cc
Build: LBX22.39-6
___________________________________
Kinda strange that the System went from US cc, to US na, then back to US cc. ???
If someone can provide this information from another carrier or carrier-less, it would be interesting to compare. I have 2 more of these ordered and due to arrive Wednesday. I'll check back here before I alter them in case someone wants additional info. - Regards
---------- Post added at 02:48 AM ---------- Previous post was at 02:07 AM ----------
chibichn said:
Zoomingrocket, check out my post here: http://forum.xda-developers.com/showpost.php?p=56707918&postcount=26
Thanks for the guide, helped me to update to Lollipop after flashing the retail image. Are you able to lock your bootloader, or will I just have to live with it being unlocked?
Click to expand...
Click to collapse
Oh my, that bat file looks eerily familiar to me. Could be a coincidence, but I *know* Jack - very well

Recovery issue
Anyone else have issues getting back into recovery after flashing lollipop? Before I wipe mine and redownload the file, is anyone else's recovery an issue? I get stuck at the dead android logo and it won't show the recovery menu text/options.

By chance will this by default carrier unlock the device as well?

XT1053 222.27.5 Stagefright OTA Update Guide

It seems like there needed to be a thread dedicated to the issues that users have been seeing with this recent OTA, as it seems like there has been a few problems with updating if you ever used Motorola's Stock 5.1 Image, I'll begin by listing the steps necessary to successfully apply the OTA update regardless of what software version you are currently running, there is also a TWRP System Image for those of you who don't want to go through the fastboot process or return to stock
Official OTA Update Procedure
1) Use TWRP and make a full backup, then connect your phone to your computer and transfer the backup files to your computer
2) Reboot your phone into the bootloader, either by doing adb reboot-bootloader or the physical key combination (power off then press and hold the power and volume down key for ~4 seconds)
3) Download the Stock 5.1.0-LPA23.12-15.0 Image from here, do NOT use Motorola's Recovery Image to do this procedure, it will fail, as the hashes are not what the OTA is expecting for the system.img, and extract the contents to a folder on your computer
4) Download the OS relevant attached mfastboot zip and unzip the contents to the same folder on your computer (if you are having issues with mfastboot try reefuge's version and see if it helps!)
5) Open up a command prompt in the directory and use the following commands to flash the 5.1 Stock Image, erasing the userdata partition is not required but it is highly recommended, as you can easily restore the TWRP data partition after doing these steps if you want your personal data back
Code:
[B]not required, but recommended![/B]
mfastboot erase userdata
[B]required[/B]
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot -P flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
6) Reboot your phone and do your initial 5.1 phone setup, and then immediately check for System Updates
7) Download the OTA and select to install the OTA
8) Rejoice in your completed OTA update, if the update fails to install, upload the recovery logs (or tell us the problem) and we will try to help!
9) You can now install TWRP and root if desired, and restore your TWRP data backup if you erased it beforehand
TWRP System Image
The TWRP System Image can be used instead of trying to apply the OTA update, this is a backup of my own phone's system partition after doing the OTA update, so it's already on 222.27.5...
Alright, after quite a bit of time uploading...
Here is the TWRP System Image
1) Download the Stagefright System 222.27.5 TWRP backup from the above link
2) Unzip the Stagefright System 222.27.5 folder to your computer
3) Copy the Stagefright System 222.27.5 folder to your phones internal storage, to the TWRP/BACKUPS/TA0000008VJ/ directory
4) Reboot your phone into recovery (TWRP)
5) Click Restore and select the Stagefright System 222.27.5 folder
6) Verify that the System partition is selected and then Swipe to Restore
7) Clear your cache
8) Boot into system and enjoy the new patch
_

Obligatory initial post
If this guide helped you at all, please show your support by either donating or telling people about how they can fix their device, pay it forward!

Please forgive me for being paranoid and not immediately running out and flashing some random OS image off the internet without first asking: what's the provenance of this OS image?

vtluu said:
Please forgive me for being paranoid and not immediately running out and flashing some random OS image off the internet without first asking: what's the provenance of this OS image?
Click to expand...
Click to collapse
The image is a Motorola signed Image, it's just not the same one that they have listed on the Recovery page, here is the details from the factory version info file inside the zip
Code:
BUILD REQUEST INFO:
SW Version: ghost_retail-user 5.1 LPA23.12-15 15 release-keysMSM8960PRO_BP_23255.138.89.00R
MBM Version: 30.BE
Modem Version: MSM8960PRO_BP_23255.138.89.00R
FSG Version: ONEBIN_BP_FSG_2.3.03_v127
Build Fingerprint: motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 222.21.15.ghost_row.Retail.en.US
Model number: Moto X
Android Version: 5.1
Baseband Version: MSM8960PRO_BP_23255.138.89.00R
Build Number: LPA23.12-15
Build Date: Sat May 9 01:44:45 PDT 2015
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.222.21.15.ghost_row.Retail.en.US
Version when read from CPV: ghost_retail-user 5.1 LPA23.12-15 15 release-keys

I can confirm that the stock image linked in the original post actually allows the update to succeed. I originally tried flashing the "official" firmware (TMO_Retail_XT1053_5.1_LPA23.12-15.222.21.15.ghost_row.Retail.en.US.tgz) from Motorola's site , since I had used firmware from Motorola's page to go back to stock for previous OTAs successfully, but the Stagefright OTA failed to install over that "stock" version. After flashing over to the image from motofirmware.center (GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip), the OTA installed smoothly. Looks like someone at Motorola made a mistake with the Lollipop 5.1 firmware they uploaded to their official page.

mastarifla said:
The image is a Motorola signed Image, it's just not the same one that they have listed on the Recovery page, here is the details from the factory version info file inside the zip
Click to expand...
Click to collapse
Thanks for the clarification. :good:
EDIT: false alarm about LTE functionality deleted, my bad. Happy flashing!

Sorry for posting again, but would it be possible to create a zip file for this OTA that will flash in TWRP?

vtluu said:
Thanks for the clarification. :good:
Warning: it looks like I might have lost LTE support on T-Mobile US after applying the above flash (it shows me using HSPA+). Could be a false alarm or me being clueless. Will edit this post once I've verified one way or the other.
EDIT: confirmed, after putting back the image I got from the official Motorola page, I see "LTE" once again under "Cellular network type" in "SIM status", whereas with the above image it said "HSPA+". There might be a way of mixing and matching the radio firmware to fix that, but I haven't tried. At this point I think I'll just sit tight and wait for an update to the update from Moto.
Click to expand...
Click to collapse
T-Mobile default's data to HSPA+, then once you start using data it "revs up" to LTE, this is a network topology thing
You could also use the dialer code (*#*#4636#*#*) to verify that your preferred network type is set correctly, mine is set to LTE/GSM auto (PRL)

Thanks. Will try again. (The most painful part being having to wait 15-20 minutes for ART to recompile my 109 apps after each reflash.)
UPDATE: all good. And the OTA update worked as well.

AaronCompNetSys said:
Sorry for posting again, but would it be possible to create a zip file for this OTA that will flash in TWRP?
Click to expand...
Click to collapse
I think all that has to be done for that is to remove the fingerprints from the flash script right?
If so, here you can try this version in TWRP... I didn't remove the patch hash checks, so if you used the Motorola Image you will still fail when flashing

mastarifla said:
I think all that has to be done for that is to remove the fingerprints from the flash script right?
If so, here you can try this version in TWRP... I didn't remove the patch hash checks, but theoretically they could be removed, but that seems quite risky...
Click to expand...
Click to collapse
I just tried it and it failed to install with TWRP. Bummer! Thanks for trying.

Being on Motorola Stock 5.1 image I flashed stock image linked in OP using RSD Lite. I did not erased Userdata during flash. Afer that OTA installed just fine.

sisterchick said:
I just tried it and it failed to install with TWRP. Bummer! Thanks for trying.
Click to expand...
Click to collapse
When did it fail? Was it due to the sha-1 mismatch? Or was it not even able to begin?
If it was the mismatch, then you would have gotten the same error with the stock recovery, which is resolved by flashing the 5.1 stock image that I linked to in the OP, you could also try removing the hash checks in the build-script, but that would be somewhat risky-ier
Al936 said:
Being on Motorola Stock 5.1 image I flashed stock image linked in OP using RSD Lite. I did not erased Userdata during flash. Afer that OTA installed just fine.
Click to expand...
Click to collapse
Awesome, I added to the OP that you don't need to wipe your data partition but it's still highly recommended

Do I need to unzip the pack I downloaded? For some reason system.img won't unzip. I keep getting an error that says "CRC failed in 'system.img". File is broken." I'm using 7zip to try to extract the files.

Shemlon said:
Do I need to unzip the pack I downloaded? For some reason system.img won't unzip. I keep getting an error that says "CRC failed in 'system.img". File is broken." I'm using 7zip to try to extract the files.
Click to expand...
Click to collapse
You should unzip the .zip, but you should not "unzip" the .img. The .img is a binary file that should stay as is (don't try to open it).

Alright I made a version of the update.zip without the patch checks
Edit: Unfortunately no luck as the patching cant be forced on the Motorola Image, as the places where they patch seem to be different than the other zip's system image

Will I need to reinstall TWRP and reroot my phone when I'm done? I apologize for the really basic questions guys.

Shemlon said:
Will I need to reinstall TWRP and reroot my phone when I'm done? I apologize for the really basic questions guys.
Click to expand...
Click to collapse
No problem, yes, you will need to re-install TWRP and re-root your phone if you are doing the full procedure

Thank you dude!
Looks like all problems cuz of missmatching hashes in prev firmware and OTA. I just flashed from your link following things and OTA installed fine:
mfastboot flash motoboot motoboot.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Click to expand...
Click to collapse

Success!
Thanks! You saved me a bunch of time fixing my wife's phone that failed-to-update correctly like so many others.
FWIW:
1) Do NOT use the regular android sdk 'fastboot'; use the motorola-tweaked mfastboot version attached above. I've gotten away with using the regular fastboot util for most things, but the device failed to boot past the unlocked bootloader warning screen until I reflashed system using mfastboot instead.
2) I got an error updating the gpt partition (something about downgrading security versions), but it didn't seem to matter.
3) I didn't wipe the userdata partition either, and all was fine. Had a TWRP backup just in case, though.
5.1 -> 5.1.1 == done. Secure... for now. (according to this Stagefright Detector app)
Doubt this original MotoX will get Marshmallow 6.0, so I might be switching it to CyanogenMod 13 in a couple months.

Unable to update OTA since repair - alternatives?

Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil

clarkey586 said:
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
Click to expand...
Click to collapse
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal

DaMadOne said:
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
Click to expand...
Click to collapse
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:

clarkey586 said:
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
Click to expand...
Click to collapse
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* Here is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...

DaMadOne said:
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* .... is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
Click to expand...
Click to collapse
Haha suppose you're right! Sure I'll probably just wipe my device in the end, be nice to have a clean go at MM haha.
The bootloader status was indeed locked so I don't know what's causing the issue?
Anyway, thanks a million for the help I'll update if/when all goes well :good:

Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated

clarkey586 said:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
Click to expand...
Click to collapse
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.

DaMadOne said:
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
Click to expand...
Click to collapse
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!

clarkey586 said:
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
Click to expand...
Click to collapse
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.

DaMadOne said:
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
Click to expand...
Click to collapse
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again

clarkey586 said:
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
Click to expand...
Click to collapse
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?

DaMadOne said:
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
Click to expand...
Click to collapse
Had to use the 2nd OTA.zip but I didn't really try any of the remove sim card stuff or waiting long. No unlockable bootloader either but I'm satisfied for the moment haha.

FYI: recovered G5 XT 1676 to stock and updated. :)

Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.

where do you get the stock firmware?

Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.

We're you able to revert to a locked bootloader after this, I am looking forward to do so

We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.

astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts

ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing

TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier

downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance

distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order

Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good

thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.

distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions

Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks

astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition

I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan