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

[GUIDE] Update XT1095 Pure Edition to Latest Android Lollipop *DISCONTINUED* - X 2014 General

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

Related

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?

[updated] THE ULTIMATE GUIDE TO FLASH GPE LOLLIPOP 5.1 on XT1032/33/34 WITH ROOT

Okay, so there has been a lot of confusion an ambiguity on how to successfully install the GPE lollipop update on the Moto G. The reason I am starting this guide is because I faced a lot of trouble myself trying to get this update and get stuff working.
DIFFICULTY LEVEL: EASY (NOOB FREINDLY )
WARNING:
I HAVE TESTED THIS FULL PROCEDURE MYSELF. BUT I SHALL NOT BE HELD RESPONSIBLE FOR ANY PROBLEMS THAT MIGHT OCCUR BY USING THIS PROCEDURE, THOUGH I SHALL TRY MY BEST TO SOLVE THEM IF YOU FACE ANY. DUAL SIM USERS, ONLY SINGLE SIM WORKS BECAUSE IT IS A GPE FIRMWARE AND THERE IS NO WORKAROUND FOR IT. THIS PROCEDURE DOES NOT WORK WITH XT1031 (confirmed by @goldeneagle1972 )
THIS PROCEDURE WILL WIPE ALL YOUR DATA ON THE PHONE. SO TAKE A BACKUP.
EXISTING GPE 5.0.1/2 USERS, FLASH THE ORIGINAL GPE MODEMS FIRST AND MAKE SURE YOUR SYSTEM ISN'T MODIFIED. (eg: rooted ). THEN DIRECTLY GO TO STEP 5.
THE REST OF YOU, FLASH THE 5.1 GPE FIRMWARE [HERE] FOLLOWING INSTRUCTIONS IN STEP 2.2 AND THEN GO DIRECTLY TO STEP 6
PREREQUISITES:
You will need an unlocked boot loader. If you have not already unlocked it, refer to [this]
STEP 1:
Download the 4.4.4 GPE XT1032 FIRMWARE from [here] [mirror]
Download mfastbootv2 from [here]
Download the minimal sdk from [here]
Download and install adb drivers from [here]
Download the batch files for all the commands from [here]. (OBSOLETE)
Download the batch files for flashing 5.1 firmware and fixing network from [here]
Download Motorola drivers from [here]
Reboot system after installing drivers.
Download THE 5.1 GPE FIRMWARE [HERE] FOLLOWING INSTRUCTIONS IN STEP 2.2 AND THEN GO DIRECTLY TO STEP 6
Extract the GPE firmware archive, batchfiles archive and mFastbootv2 archive to the Minimal ADB and Fastboot folder (or your folder containing the platform-tools)
Download OTA update from [here]. Rename it to "ota".
Copy this archive to the same folder mention above (do not extract this archive).
STEP 2:
Boot into fastboot (POWER+VOLUME DOWN) and connect phone to PC
If you are starting from scratch, skip 2.1 ) and go to 2.2 )
2.1 ) If you have already made a failed attempt to OTA, or have previously flashed the Brazilian OTA, then flash the GPE 4.4.4 firmware follow this step. SHIFT + RIGHT click in the folder where you have extracted everything and choose open command window here. Then double-click on "Step 2_1.bat" or type the following commands one by one.
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
You will not get network now but do not flash the modems of the firmware you use now because you will get a status 7 error when flashing the OTA. You will now be dumped at the welcome screen. Do not enter any details, just power off and boot into recovery via fastboot. Skip step 2.2)
YOU WILL GET SOME ERRORS LIKE HAB CHECK FAILED. JUST IGNORE AND PROCEED.
2.2 ) For those who haven't attempted the OTA or are not on the Brazilian Firmware, use the following method to flash the 4.4.4 GPE firmware. SHIFT + RIGHT click in the folder where you have extracted everything and choose open command window here. Then double-click on "Step 2_2.bat" or type the following commands one by one. (Thank you @jmonster141 for pointing out my silly error).
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
You will not get network now but do not flash the modems of the firmware you use now because you will get a status 7 error when flashing the OTA. You will now be dumped at the welcome screen. Do not enter any details, just power off and boot into recovery via fastboot.
IT SEEMS THAT SOME 4.4.4 FIRMWARE HAVE NEWER PARTITION TABLES THAN GPE 4.4.4, SO THE GPT.BIN WILL FAIL TO FLASH. JUST SKIP IT AND YOU'L BE FINE (confirmed by @SickBeast ) or TAKE A LOOK AT [THIS] (thank you @t4n017 ).
AFTER ERASING USERDATA AND REBOOTING, YOUR PHONE MIGHT BOOT DIRECTLY INTO FASTBOOT AND IT WILL SAY "UTAG FLASHFAIL CONFIGURED AS FASTBOOT. JUST REFLASH THE BOOTLOADER TO FIX
Code:
mfastboot flash motoboot motoboot.img
(thank you @t4n017 again )
YOU WILL GET SOME ERRORS LIKE HAB CHECK FAILED. JUST IGNORE AND PROCEED.
STEP 3:
Now we shall flash the OTA. Boot into recovery. You shall see a weird android logo with an exclamation mark. AFTER THAT HOLD VOL+ FOR 15 SECONDS, THEN TAP POWER BUTTON (KEEP HOLDING THE VOL+ BUTTON) (thank you @thestory101) and choose apply update from adb in the recovery. Then double-click on "Step 3.bat" or type the following command:
Code:
adb sideload ota.zip
OR just OTA from Settings>About phone>System updates (confirmed by @t4n017) though i would yet recommend using the former procedure.
STEP 4:
Once it has finished, select reboot system now from the recovery. DO NOT WIPE YOUR CACHE. YOU WILL BE STUCK AT THE GOOGLE BOOT LOGO SCREEN FOR AROUND 10-20 SECONDS. JUST BE PATIENT. If you are stuck for more than 20 seconds, just flash [this].
STEP 5:
Now check your phone for and update and you shall get an update notification for 5.1 lollipop. Follow onscreen procedures and complete the update.
STEP 6:
SKIP THIS if you have EUROPEAN XT1032.
Download XT1033 modems [here] if you have the Asian Moto G. THESE MODEMS APPARENTLY DON'T WORK. LOOK AT POST NO. 593 FOR FIX.
Download XT1034 modems [here] if you have the Canadian Moto G
Download XT1032 US GSM modems [here] if you have the us version (thank you @jmonster141)
I HAVE GIVEN LINKS TO ALL THE MODEMS OF THE COMMON VARIANTS OF THE MOTO G. IF YOU HAVE A DIFFERENT VARIANT, DOWNLOAD YOUR RESPECTIVE FIRMWARE, COPY THE "NON-HLOS.bin" and "fsg.bin" FROM YOUR ORIGINAL FIRMWARE TO THE FOLDER WHERE YOU HAVE THE SDK, mFastboot, GPE FIRMWARE AND OTA AFTER STEP 3 AND FOLLOW STEP 5 TO GET NETWORK. IT IS EXTREMELY TIME CONSUMING FOR ME TO HUNT DOWN MODEMS FOR ALL THE NUMEROUS VARIANTS AND LINK THEM IN THE OP (IM KINDA BUSY WITH MY STUDIES RIGHT NOW) SO PLEASE TAKE THE PAIN TO DO SO YOURSELF. ALSO, LINK THE MODEMS YOU USED,TO GET NETWORK, IN THE THREAD SO I CAN ADD IT TO THE OP AND HELP THE REST. (That's how the amazing XDA community works right ?! )
BryanByteZ said:
Link for Stock Roms to extract modem files:
[here]
(All Moto G Variants)
Click to expand...
Click to collapse
hacorn96 said:
I'll just drop this here:
http://forum.xda-developers.com/showthread.php?t=2649763
All variants/regions kernel/recovery/radio files...
Click to expand...
Click to collapse
We shall now flash the modems. You will be put at the welcome screen after a few minutes. Power off, boot into fastboot. Then double-click on "Step 5.bat" or type the following command:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
You shall now be running 5.1 GPE !
voilamos said:
For anyone having difficulties with their network on an XT1033 , try using network fix.bat from here :
http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472
Click to expand...
Click to collapse
ROOT: (OPTIONAL)
Download the latest superSU flashable zip from [here] and copy-paste it into to your phone.
Download the latest TWRP recovery image from [here]. Copy the image to the folder where you have adb and fastboot. Rename the image to "recovery". Open a command prompt in the folder containing this recovery (press shift + right-click, choose open command window here). Boot your phone into fastboot mode and execute the following code:
Code:
fastboot flash recovery recovery.img
Ignore the partition mismatch error.
Use your volume rockers to boot into the recovery. Go to install zip, and choose the SuperSU zip and flash it.
Reboot into rooted 5.1 GPE.
TO FIX THE LAGGY ANIMATIONS IN GOOGLE NOW LAUNCHER, SEE [THIS] POST.
nishantjian4u said:
- MOST IMPORTANT: please read and follow the steps as if your life depends on it. If you have any doubts, read the whole thread. I confirmed the steps with some other google searches wherever I thought I am confused. Luckily for me, if worked like a breeze for me the first time. Read all the messages on the command prompt / terminal on your computer and the information displayed on your phone while you are flashing all sorts of stuff. There are certain important information that you will on this displays. BE PATIENT
Click to expand...
Click to collapse
CREDITS TO ALL PEOPLE WHO HAVE CONTRIBUTED TO THE AMAZING MOTO G XDA COMMUNITY.

pfufle said:
Okay, so there has been a lot of confusion an ambiguity on how to successfully install the GPE lollipop update on the XT1033. The reason i am starting this guide is because I faced a lot of trouble myself trying to get this update and had to scavenge through multiple threads to get stuff working. I had flashed the update on my Moto G XT1033 converted to GPE using the mixed firmware by @deej_roamer [using this tutorial], OTAed to 4.4.4 and flashed the OTA manually using ADB. I was stuck at the bootlogo following this. This was because of the firmware being modified this interfering with the OTA. Since i was now stuck with the new 41.18 bootloader and the partition table (gpt.bin) of the OTA, i could not flash the XT1033 firmware. So this is what I did:
Click to expand...
Click to collapse
That's a nice way to convert I didn't think it could be done this way.... Cool bro

dual sim will work with this method right?
can you give feedback, is it stable enough to be used daily? have you encountered any bugs or features that doest work? force close?
im thinking jumping to 5.01 but need some idea of how stable it is as i dont have a spare phone at the moment if it fail or got bricked

thankyou !!!

No Network
Hey
I still don't see any network on my phone.
This is after I flashed the modem files
Any fix ? Thanks

For me GPE 4.4.4 doesn't boot anymore, because of the new bootloader I assume. GPE 5.0.1 also didn't boot. Only Motorola Firmware booted successfully. Do you know what I can do about that?

This works whit the xt1034 ?

aben.dc said:
dual sim will work with this method right?
can you give feedback, is it stable enough to be used daily? have you encountered any bugs or features that doest work? force close?
im thinking jumping to 5.01 but need some idea of how stable it is as i dont have a spare phone at the moment if it fail or got bricked
Click to expand...
Click to collapse
The build is epic! Flash it right away if you dont need dual sim.
voilamos said:
Hey
I still don't see any network on my phone.
This is after I flashed the modem files
Any fix ? Thanks
Click to expand...
Click to collapse
I am really sorry but i missed an important step in the OP (i realised it right away but my mom wouldnt allow me to touch my PC before i finished my homework :| )
Once you flash GPE 4.4.4 with the original modems, flash the OTA and after that reboot to bootloader and AFTER that flash the modems of the phone model you have. When you boot into lollipop it will say that it will take around 5 minutes to find network and wait patiently until it is done.
k-kuchen said:
For me GPE 4.4.4 doesn't boot anymore, because of the new bootloader I assume. GPE 5.0.1 also didn't boot. Only Motorola Firmware booted successfully. Do you know what I can do about that?
Click to expand...
Click to collapse
Make sure you follow step 2.1. And make sure you used thw links i provided in the OP. GPE 4.4.4 boots just fine for the rest of us. (Sans the screen flickering which is fixed after a screen unlock)

Hi,
I'm stuck on step 3 (can't adb sideload the ota). I can't boot to recovery - just a picture of android with the ! (red) sign.
GPE 4.4.4 is working just fine (with network too).
Thank you!

acid032 said:
This works whit the xt1034 ?
Click to expand...
Click to collapse
Assuming that it is the brazilian version, yes it should work.

Metalingus903 said:
Hi,
I'm stuck on step 3 (can't adb sideload the ota). I can't boot to recovery - just a picture of android with the ! (red) sign.
GPE 4.4.4 is working just fine (with network too).
Thank you!
Click to expand...
Click to collapse
I for got to mention in the OP, you are supposed to press volume up and power button simultaneously when that logo comes for 7 seconds and then release it.

It just reboots the system when I press volume up and power button when that logo shows up.
Thanks
EDIT: Got it to work! Just have to precise!

pfufle said:
Make sure you follow step 2.1. And make sure you used thw links i provided in the OP. GPE 4.4.4 boots just fine for the rest of us. (Sans the screen flickering which is fixed after a screen unlock)
Click to expand...
Click to collapse
Thanks.
As far as I can tell the difference is leaving bootloader (which fails to flash anyway) and GPT from the retail Firmware. I flashed the whole GPE before which resulted in being stuck at bootlogo

k-kuchen said:
Thanks.
As far as I can tell the difference is leaving bootloader (which fails to flash anyway) and GPT from the retail Firmware. I flashed the whole GPE before which resulted in being stuck at bootlogo
Click to expand...
Click to collapse
Yep. The old partirion tables are incompatible with the new bootloader apparantly.

Can somebody confirm if this works for XT1034 (Retail Canada/US AWS)?

Well it Works but i dont have any network I flashed my modems from the original firmware of the xt1034.
Any Help ?

acid032 said:
Well it Works but i dont have any network I flashed my modems from the original firmware of the xt1034.
Any Help ?
Click to expand...
Click to collapse
In the very last step can you try and flash these? Should work, they are XT1034.
https://drive.google.com/file/d/0ByPjgNaqEEYBU0lGenNxTmxwR0k/view?usp=sharing

Anyone of you who has flashed the ota, could you please upload an nandroid backup of the rom
Sent from my XT1031 using Tapatalk

If it is fully functional with moto g XT 1033
If it is fully functional with moto g XT 1033

ali4ek said:
In the very last step can you try and flash these? Should work, they are XT1034.
https://drive.google.com/file/d/0ByPjgNaqEEYBU0lGenNxTmxwR0k/view?usp=sharing
Click to expand...
Click to collapse
MAN I FCK LOVE YOU THANKS, IT WORKS IN THE XT1034
sorry for the caps but Im really happy

[FAQ] How to prepare for and take an OTA update (All Carriers)

This is a reserection of -> http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735 and -> http://mark.cdmaforums.com/MotoX-OTA.html
With Verizon pushing a maintenance release for their Stock 4.4.4 (which doesn't change the Android version number), I wanted to post this sooner rather than later because questions are coming up....
Whenever a new OTA comes up, there are always questions like "what do I need to do to take the OTA?" or "I got prompted to take the OTA, but xxx is happening." This thread is intended to provide that information in once place.
This information is based on the past OTA updates for the Verizon, T-Mobile, and ATT Moto X phones, and threads on various forums. It should apply to all OTA updates.
Please note: If you have tried downgrading by flashing only parts of a rom, or have mismatched files on your phone for any reason, DO NOT TAKE AN OTA or you will likely brick your phone!! First flash your phone with a full SBF of the latest ROM for your carrier before attempting to take future OTA's. For more on Downgrading and the risks associated with it, see -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
These are the most common Questions and Issues we've seen in the past...
If you could NOT get your bootloader unlock code directly from Motorola and rooted by some other process, you should *WAIT* on taking an OTA update as it may patch any vulnerability being exploited to root your phone. And you may not be able to ROOT on this new version!!
If you used Sunshine, or got your Bootloader Unlock code from the China Seller or Middleman... You should BE CAUTIOUS and *WAIT* on upgrading past 4.4.4. Please see -> [LOLLIPOP WARNING]Those Who Unlocked Via Sunshine or Purchasing a Code from China
You should expect to lose root when you take an OTA.
For the Motorola X, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... To take the 4.4.4 OTA, your phone needs to be on 4.4.2 (or 4.4.3 depending on your model/carrier). To take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
Inside the OTA is a "Pre-flash Validation Check" to ensure your phone is on the correct version BEFORE it will flash. It includes a manifest file that contains a list of files and their check sums the OTA expects to be on your phone. If the files are missing from your phone, or the check sum for a particular file doesn't match (because you've replaced or altered the file), the OTA will fall. NOTE: The more files patched by the update, the more strict the pre-flash validation will be. So an update from 4.4.4 -> 5.1 will be more strict than the recent Verizon 4.4.4 maintenance patch.
Because of #5, you must be "stock." Any bloat you deleted, needs to be put back. Any apps you froze with Titanium Backup or the like, may need to be unfrozen. Apps disabled via the phone's Settings -> Applications -> [select app] -> [disable] can remain disabled and should not impact the update. NOTE: Back in the "early days" of the 2013 X, all apps frozen with TiBu had to be unfrozen. Later updates that hasn't been much of a problem. I don't use it, so I can't say for sure.
If you have XPosed installed on your phone, it often does make changes that will cause the Pre-Flash Validation to fail. You may be able to just disable it, rather than fully removing it, and then take the OTA. (To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) NOTE: There is a newer version of Xposed needed for Lollipop!!
The OTA Updates will only install via Stock Recovery. If your Root method has replaced stock recovery with something else, you will need to use mfastboot to flash stock recovery on your phone BEFORE you attempt to take the update. Not having Stock Recovery on your phone when you take the OTA can result in your phone doing a boot loop. NOTE: You can use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop.
There are several options to get back to "stock" without loosing your data. (I will add them to Post #2 of this thread at a later date), some are more technical, some are more noob friendly. The one you use, depends on how much, or how little, you have modified your phone away from stock.
In some cases, using mfastboot to reflash stock Recovery.IMG and System.IMG can be enough to get you back to "Stock" and take the OTA update.
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 Please be sure to use the latest TWRP fastboot IMG file (Alternate Link) and Installable ZIP of SuperSU
Any tethering hacks you have done will likely need to be undone in order to take the OTA (see #5 above), and may not work after the OTA is installed.
Some FAQ's...
I've tried taking the OTA, but I'm stuck in a loop. It wants to keep rebooting. - This is usually caused by having a 3rd party recovery, like TWRP/CWM, on the phone. Re-flash the stock recovery to install the OTA update, or use fastboot erase cache to delete the update zip file from your phone which will stop the boot loop. (instructions will be added to Post #2 of this thread in the future)
I've tried putting back my bloat, and taking the OTA, but it fails. - You likely missed something the Pre-flash Validation check is looking for. If you are able to capture the OTA ZIP and use the SIDE LOAD AN OTA instructions (which will be added to post #2 of this thread in the future), you can watch progress of the OTA install. It will tell you the error, and/or what file doesn't match.
In the past we've seen error codes 252 and 410. These have been related to files on the phone not matching the OTA's pre-flash validation checks.

[NOT YET SPELL CHECKED!!!]
How to return to stock & Unrooted... (Windows options only, as I don't have a Mac) Note: Some Windows 8/8.1 users have had issues, so when possible, please use Windows 7.
The following are listed in the order I originally posted them HERE and HERE
Requirements: These are the same no matter which option you use.
To repeat what I said in the OP, Do NOT attempt to downgrade your phone!! Please be aware of the risks -> [INFO/WARNING]The Risks of Downgrading, and the impacts of GPT.BIN and MOTOBOOT.IMG
Know what version ROM is on your phone before you touch anything. Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites that host leaked ROMS until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, and you'll find... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools can NOT flash the SYSTEM.IMG on Moto phones!!
Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The Options...
NOTE: I most often recommend option 5.
Option 1... The "Moto X Tool Kit"
This is the most newbie friendly.. But it can be a little complex to prepare and put your SBF in the right place, etc.
See -> [TOOL] Moto X Toolkit v1.4.4 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
It is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. The only thing it does not appear to include would be Roms for your particular phone, so, you'll likely need to download the ROM for your phone separately. As noted in the ToolKit thread, if they are available, you can get them from here -> http://sbf.droid-developers.org/ghost/list.php your "build number" or part of it, should be in the file name you are downloading.
Again, I haven't used this tool, so for install, setup and usage, I'll have to point you to that thread to ask. Two main options you'll be interested in... UNROOT (which keeps your data and apps) or FLASH BACK TO STOCK (which will likely also completely reset your phone and wipe any/all data, settings, applications, etc).
Option 2... mFastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.
NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements as listed above, the steps would be as follows...
Start the phone in Fastboot AP/Bootloader mode.
Connect phone to PC via USB cable.
open command prompt file and change to the folder you unzipped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and be back to stock and ready for the update.
NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
Option 3... Fully flash your phone using RSDLite while attempting to keep your data and settings
NOTE: this has the potential to erase your data if you don't edit the XML properly before flashing.
Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using SBF of the ROM currently on your phone, or newer for your carrier and model. HOWEVER, before doing it, as part of STEP 4 while editing the XML file, also remove the line that says...
<step operation="erase" partition="userdata" />
Failure to remove this line will result in your data/apps/settings being erased from your phone!!
Option 4... Fully flash your phone using RSDLite
Note: this WILL ERASE YOUR USER DATA AND APPS, and put you back to a "fresh" phone.
Follow this guide -> [GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash) using the ROM from your carrier.
Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).
This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.
As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements near the top of this page, the steps would be as follows...
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready. (it could take a little longer than a normal reboot)
NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata
Option 6... Flash only stock recovery.
This option is useful if all you did was unlock your bootloader, flash TWRP recovery, and rooted. It can be used if you've haven't installed Xposed, or modified any stock apps, and only run rooted for apps like BigTinCan's Adaway, Root Explorer, Wifi Tether for Root, etc.
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
The device will start in Stock Recovery display additional menu options (Text will appear in BLUE)
While in Stock Recovery, use the VOL DOWN Key to scroll and the POWER Key to select the option you wish to use.
You may now use the option to reboot the phone.

{reserved}

KidJoe,
Thanks so much for this. Even though I manually returned all changes to stock, the ota still kept quitting with an error.
It was really annoying because after each error, I would have to redownload the entire ota, 696MB, which was downloading rather slowly.
Anyway, I followed option number 2 from the original post to flash boot, recovery and system and it was smooth sailing after that
Thanks again

KidJoe said:
[NOT YET SPELL CHECKED!!!]
Option 2... mFastboot flashing individual parts of your phone's firmware.
This will not erase your data and apps. It is a good option if you are stuck in a boot loop.
If you have made very few changes to your phone and already have ADB drivers and fastboot from the Android SDK installed and in your path, along with the Motorola drivers already installed and working, this is the quickest and easiest way to return to a state that is ready to accept an OTA without losing data/apps.
NOTE: you may need to disable and/or uninstall Xposed before doing this.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements as listed above, the steps would be as follows...
Start the phone in Fastboot AP/Bootloader mode.
Connect phone to PC via USB cable.
open command prompt file and change to the folder you unzipped the ROM file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot reboot
phone should reboot and be back to stock and ready for the update.
NOTE: to combat a 410 ERROR while doing the update, some users have also had to also do the following
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
See -> http://forum.xda-developers.com/showpost.php?p=47639731&postcount=315 (thanks jimmydafish)
[/list]
Click to expand...
Click to collapse
KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.
The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.
Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.
Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?
Again, thanks for your help here!

summit15 said:
KidJoe, thanks for the help. I have an XT1095. All I am pretty sure I did was root. I've never installed TWRP or even used root apps other than Greenify. In that state I was not able to accept the recent 5.1 OTA. I used the option in Supersu to full unroot (which also uninstalled Supersu). That did not fix the problem. I am now just finding your guide but other searching has led me to your conclusion that Option 2 should be all I need to do plus it won't wipe my phone.
The confusion I have now involves the system.img file. I requested the 5.0 download from Moto, but they never responded. I found the proper zip file elsewhere (TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip). When I unzip it, I see all the files. The recovery.img file is there but the system.img file is broken up into eight different files all named system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2, etc.
Do I have the right files? Do I flash all of them individually? I'm not very experienced in this and don't want to screw this up. Any information you could provide would be greatly appreciated. Thanks.
Edit: After posting this, I found this site: http://www.usoftsmartphone.com/t279221.html that showd me how to extract the system file from all the sparse files. Step one creates a system.img file from all of them. Step two seems to unzip them. I am guessing that the file created after step 1 is the file I would need to flash?
Again, thanks for your help here!
Click to expand...
Click to collapse
Keep in mind that the XT1095 is NOT a 2013 X, so its files may be different.

So I'm using a cm12 based rom and I've wanted to return to stock lately, let me see if I got this straight. Using rsd lite and erasing the line:
<step operation="erase" partition="userdata" />
Won't erase internal memory like music, photos, etc?
It's safe? I'm wondering if I'm going to have problems with the apps since they're running on ART on lollipop or if the system settings will have issues when I return to stock KitKat

OTA Accepted
For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:
Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.
NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.
Thanks again to KidJoe for this guide.

summit15 said:
For anyone who finds themselves in my same situation (all I really did to my phone was root it and install Supersu, no custom recovery or big time changes and I wanted to apply the OTA without wiping my device), I got my OTA update applied by doing the following:
Did a "Full Unroot" from within the Supersu app which then uninstalled itself.
I found the proper Moto ZIP file that contained Lollipop 5.0.
I then used mfastboot to flash the boot.img and the recovery.img
I then boot the phone up and told it to check for system updates.
It found the update, downloaded it, and then applied it.
It worked and I can move on with my life now.
NOTE: Most of my confusion in this process centered around my being told I needed to flash the system.img file. My problem was that inside the Moto ZIP file were eight different system_sparse files. I didn't know what to do with all them. I found a site in the previous link that showed me how to essentially combine all them into one system.img file. I followed those directions and it created the file. However, when I tried to flash it, I got an error that seemed to suggest that the file was corrupt.SO, this was after I had already flashed the boot and recovery files. I gave the OTA a shot just hoping it would work. Turned out it did.
Thanks again to KidJoe for this guide.
Click to expand...
Click to collapse
Again.. you have an XT1095... which is NOT a 2013 X... this guide is in the 2013 X section, so things can/will be different for a 2014 X...
But thanks for sharing.

Awsome Tutorial!!
I'm really a noob, so I still have some questions...
After that you should get the OTA update by going to setting -> about phone -> update??
because if so, I'm not.
Another thing i may done something wrong. On this step:
4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.
Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.

Malba14 said:
I'm really a noob, so I still have some questions...
After that you should get the OTA update by going to setting -> about phone -> update??
because if so, I'm not.
Click to expand...
Click to collapse
The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet.
Malba14 said:
Another thing i may done something wrong. On this step:
4. Download ROM/SBF files for the ROM currently on your phone!!!! from one of the sites listed HERE. Failure to use the EXACT SAME ROM/SBF that is on your phone now can cause problems!!
I needed to move the ROM/SBF to the phone right? At any folder? Because I didnt do that and I opened the command prompt in the pc folder that the ROM/SBF was unziped. Nothing wrong happened to my phone, apparently.
Should I remake the tutorial moving the unziped file to the sdcard folder of my phone?
sorry for so many doubts.
Click to expand...
Click to collapse
No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.
The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.
In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.

KidJoe said:
The OTA update hasn't rolled out for all phone models and carrier variants yet. So there is a VERY GOOD chance it wont be available for you yet..
Click to expand...
Click to collapse
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.
KidJoe said:
No, you do NOT move the SBF, or parts of it, to your phone. Leave it on your PC.
The tools to flash (RSDLite and mFastboot) are tools ON YOUR PC... they need the file to be on your pc.
In the post I talk about figuring out what file to download and use the example of the Rogers XT1058, and the correct file being XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip so sticking with that example.. you visit one of the sites (from your PC), download XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip ... and unzip it on your PC to a folder... If you are following option 2, 5 or 6 and using mFastboot, then you need to open a command prompt and change drive and directories to where you unzipped XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip to BEFORE you start entering the mfastboot commands. NOTE: you could just SHIFT-RightClick on the folder and "open command window here" as that will open a command prompt in that path/folder.
Click to expand...
Click to collapse
This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.

Malba14 said:
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button and then every time I turned my phone on, after 30 seconds it rebooted to TeamWin. This kept going until I clicked on recovery or system (I dont remember - under the reboot page) and the cycle went off saying that has been some kind of problem with the update.
Click to expand...
Click to collapse
Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)
Malba14 said:
This part I did it right, i think. I fount the one that describe my phone better.
XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml
Actually I just reallized it is .xml. Is that ok? On my PC it opened with winrar just like any zip.
Click to expand...
Click to collapse
There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.

KidJoe said:
Rebooted to TeamWin and said there was a problem with the update?? Yeah, because you need STOCK recovery on the phone. (as stated in the OP)
There maybe an XML inside the ZIP... you need to uncompress the entire file (extract all) BEFORE you can flash it, other wise RSDlite or mFastboot wont find the files you are trying to flash.
Click to expand...
Click to collapse
Thanks for the help man. I'm sorry for the noob questions.
I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.
Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?
And how can I know that I did it right?
Your are awsome man!

Malba14 said:
The thing is that the update was rolled out for me before. But kept regecting it until one day that I clicked on "stop bothering me, I'll do it when I want" button....
Click to expand...
Click to collapse
I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.
Malba14 said:
Thanks for the help man. I'm sorry for the noob questions.
I actually did the hole tutorial before. I extracted this hole file and opened the command prompt in it and did the tutorial number 5.
Sorry if I wasnt clear before but the problem with the update was just a backgroud history to what I was aiming to know. That is: after I do the tutorial, what I have to do to get the OTA update now?
And how can I know that I did it right?
Your are awsome man!
Click to expand...
Click to collapse
As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...
OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...
OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079

KidJoe said:
I forgot to mention... for the models IT has started pushing for, they were sending it out in waves... IF you missed your turn (which you eventually did by not installing), you usually need to wait until the end, when the waves are done.. Because of when the BR Xt1058 push was started, I'd say that might be in the next week, or two.
As long as you flashed the latest 4.4.4 rom, your bootloader is consistent with the ROM you flashed, are you 100% completely stock, you just sit and wait until the OTA becomes available to your phone again. You can manually keep checking...
OR you can see if the 5.1 SBF is available for your carrier/model in this thread -> http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628 download and flash it instead, which will take you right to 5.1...
OR you can see if the official OTA zip has been posted, download the zip to the /SDCard of your phone, and follow the SIDE LOAD section of -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
Click to expand...
Click to collapse
Thanks a lot!!!

KidJoe said:
Option 5... Using mFastboot to manually flash your phone's firmware (without wiping data).
This is very similar to using option 3, but uses Moto fastboot instead of RSD, however it adds a few steps which aid in flashing when your GPT.BIN and MOTOBOOT.IMG are mismatched from the rest of your rom, and refuse to flash.
As written, these steps will NOT erase your data and apps. Because of this you may need to disable and/or uninstall Xposed before doing performing these steps.(To disable Xposed, boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip ) Keep in mind there is a newer version of Xposed needed for Lollipop!!
After you have the requirements near the top of this page, the steps would be as follows...
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you unzipped the ROM/SBF file to.
type the following, pressing enter after each command, and wait for it to finish before going onto the next... NOTE: yes, there are a few commands being repeated, but this is intentional!!!
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
The phone should reboot and and be ready. (it could take a little longer than a normal reboot)
NOTE: if you wish to erase your data and apps during this process, just before the final reboot command, issue... mfastboot erase userdata
Click to expand...
Click to collapse
Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:
Code:
mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.534s]
finished. total time: 0.819s
I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.
Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7
I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.

RohanAditya said:
Hey.
I wanted to return to stock by flashing the parts manually.
I followed your steps but when i executed the command a message popped out saying 'Variable not supported' and it continued the execution.
I did not find any change in the system when I checked after the whole process was completed.
The message I mentioned earlier was shown for every step.
Example Code:
Code:
mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.280s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.534s]
finished. total time: 0.819s
I also flashed boot, logo, system and the others parts.
But the same message was shown every time.
And after the process was complete I restarted the phone but the 'Bootloader Unlocked Warning' screen appeared.
I hadn't removed this after I rooted the phone.
I thought it would be removed when I flashed motoboot, boot and logo.
Phone Details:
Current Android Version: 4.4.4
System Version: 212.44.26.ghost_row.AsiaRetail.en.03
Build Number: KXA21.12-L1.26
Kernel Version: 3.4.42-g50861a7
I used this image:
Drive Link:
https://docs.google.com/file/d/0B5XNxZ2OcfKtdDROTk5kb21ObU0/edit?pli=1
File Factory Link:
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
I desperately need your help.
What should I so to flash the stock image properly?
Thanks in advance.
Click to expand...
Click to collapse
Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.
Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.

KidJoe said:
Based on what you posted, I'm not completely sure of your question. I mean if you think you are not stock because you still have the unlocked bootloader warning message after flashing, that is normal if you've ever unlocked your bootloader.
Out of box LOCKED bootloader shows Locked Status 0... After unlocking, it shows Unlocked Status 3. If you attempt to relock it, it will show as Locked Status 2. We don't have a way to get back to Locked Status 0. That being said... If the status is NOT 0, you'll always get the Unlocked Bootloader Warning when using the stock/standard LOGO.BIN.
Click to expand...
Click to collapse
Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance

RohanAditya said:
Okay I unlocked it. The code is 3.
Thanks
But how do I know if I'm ready to receive the OTA?
Is there a way to find out if I can receive it without it resulting in a brick?
And is the Variable not supported message normal?
Or have I done something wrong?
Thanks in advance
Click to expand...
Click to collapse
Variable not supported is normal and nothing to worry about.
Because each OTA is different and looks at different aspects of the phone (based on what it will upgrade, or not), there is no way to tell you exactly what should be checked.
If you returned to stock by flashing the COMPLETE STOCK ROM (all parts of SBF) for your carrier/model with mFastboot, and received no errors (other than variable not supported), and your bootloader version is consistent with the ROM on your phone (i.e. you didn't attempt to downgrade), then you should be ready for the OTA...

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.

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

Database Users

welcome