Database Users

[GUIDE] Restore Moto Firmware for American Moto G

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys, this guide is to help you to go back to Stock Firmware from any custom ROM or from Google Play edition firmware.
First, all credits go to the original owners of this guide, firs of all thanks to @Semseddin and his previous guide !!!
Click to expand...
Click to collapse
I started this thread because I have an Argentinian Retail Moto G, and downloaded the retail 4.4.2 firmware for Argentina, it comes in *.tar.gz format, but the guide stated above was for *.xml.zip firmware, so here it comes some differences.
DISCLAIMER: If your Moto G dies, explodes, turn into a zombie, goes berserk and tries to kill you, I'm not the one to blame. I've tested this tutorial and worked for me, if this does not work for you, keep googling about your problem. I can help you but its not my fault! Try this at your own risk.
THIS SHOULD WORK ON LOCKED AND UNLOCKED BOOTLOADERS​
LETS BEGIN...
-1 - Make a backup of all the apps and media in your SD card because all of this erases and formats everything inside! So backup everything!
0 - DOWNLOAD and install Motorola drivers.
1 - Go to THIS PAGE and download a 4.4.2 firmware suitable for your device. In my case I searched and downloaded Retail Argentina 4.4.2 firmware. There aren't a lot of 4.4.4 specific firmware, so download a 4.4.2 firmware. After installing it, you can OTA to 4.4.4.
2 - On Windows, create a temporary folder in drive c:\ called "restore" so it would be like this: c:\restore ; and there using 7zip or similar, extract everithing inside the firmware file into this "retail" folder. (The firmware I needed was in *.tar.gz format but this can work if the firmware you get is in *.XML.zip format)
3 - Now, download the attachment I provide you (those three files are from 4.4.4 OTA ZIP). Extract and place them inside the "restore" folder and replace the files inside.
4 - Download "mfastboot-adb.rar" in the attachments. After that, extract everything inside the RAR in the "restore" folder.
Important: Everything has to be inside the "restore" folder, don't leave files inside extraxted folders. It has to look like this:
5 - Turn off the phone and turn it on in FASTBOOT MODE (When turned off tap and hold ON BUTTON and VOLYME DOWN BUTTON for 5 seconds and release them, you should see the FASTBOOT MENU) and plug the phone to PC via USB.
6 - Start CMD (Windows console) with Administrator rights (in Windows 7 click on Start and in the search bar write CMD and above right click on CMD and start it as Administrator) and type:
cd c:\restore
Click to expand...
Click to collapse
This will place the console inside the "restore" folder.
7 - Here starts the COPY-PASTE action. Don't miss ANY LINE here!!! Copy and paste this lines one by one, waiting to the flashing to finish and giving an OKAY as a result!!! If some of this commands gives a (bootloader) FAILED answer, try to repeat that command.
If you upgraded to Lollipop, you can go back to KitKat, but DONT FLASH THE COMMANDS I GIVE HERE THAT ARE IN RED COLOR. Use the RED commands only if you NEVER upgraded to Lollipop before:
mfastboot flash aboot emmc_appsboot.mbn
mfastboot flash partition gpt.bin
mfastboot reboot-bootloader
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img -- (this one gives trouble on some devices, if that is your case, click below)
If mfastboot flash system system.img gives an error, you can try this commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
If yoy have a Moto G LTE version, you can use this commands: (Correct me if these are not the right ones for LTE)
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata -- THIS ERASES ALL YOUR DATA AND FORMATS SD! You should have done a backup by this point! (If this command gives a (bootloader) FAILED error, immediately run this command again, that should work.)
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
Please, I say this again! Do this one line at a time, waiting for every line to flash and perform actions and to return an OKAY as an answer...
If every step on the copy-paste steps give OKAY as an answer, you will see your Moto G return to life with the original Moto firmware!!!! The first boot will take like 7 or 8 minutes, so be patient!
So this is it. If you need help let me know below... :fingers-crossed:

Everything looks good and worked for me except for 2 things:
-Flashing motoboot.img will error if you're trying to downgrade from 4.4.4 gpe or 4.4.3 moto but you can just skip it
-You need to add a .img at the end of this "mfastboot flash system system (this one gives trouble on non european models but is the one that works on american (and argentinian) Moto G!)" (not a big deal but it errors if you don't and people can get scared)

anerik said:
Everything looks good and worked for me except for 2 things:
-Flashing motoboot.img will error if you're trying to downgrade from 4.4.4 gpe or 4.4.3 moto but you can just skip it
-You need to add a .img at the end of this "mfastboot flash system system (this one gives trouble on non european models but is the one that works on american (and argentinian) Moto G!)" (not a big deal but it errors if you don't and people can get scared)
Click to expand...
Click to collapse
You're damn right man, correcting right now! :good:

Hey man thanks for the guide. No the question is, why flash back? GPE is much better for me! or it is because we will have problems when trying to update to Android L?

I plan to do this when 5.0 comes out. Currently I'm on CM11. However, on the official downloads page I only see 4.4.2 for my retail firmware. Would this be fine if I'm on 4.4.4?
Thanks for the guide.

there is one thing, if you upgrade to 4.4.3/4.4.4, you will not be able to downgrade yourself to 4.3.
I have tried. it just wont boot.

SloppyBeef said:
I plan to do this when 5.0 comes out. Currently I'm on CM11. However, on the official downloads page I only see 4.4.2 for my retail firmware. Would this be fine if I'm on 4.4.4?
Thanks for the guide.
Click to expand...
Click to collapse
Yes, I was on GPe 4.4.4 firmware, then I flashed 4.4.2 Moto firmware, then OTAed to 4.4.4 Moto firmware.. So this will work..

AgentChaos said:
there is one thing, if you upgrade to 4.4.3/4.4.4, you will not be able to downgrade yourself to 4.3.
I have tried. it just wont boot.
Click to expand...
Click to collapse
Yes, that is true, so 4.3 is no more an option.. I wonder if this will happen in the future, I mean, maybe when 5.0 comes out, will it be impossible to downgrade to 4.4.2 firmware also?... I hope I'm wrong..

titotito1983 said:
Hey man thanks for the guide. No the question is, why flash back? GPE is much better for me! or it is because we will have problems when trying to update to Android L?
Click to expand...
Click to collapse
This is just in case you miss Stock firmware... If you like GPe firmware just stay there, but if you have trouble you can use this guide. Also this should work to revert from CM11 or another custom ROM. :good: But, when Lollipop arrives, there will be no problems with OTAs on GPe firmware, but Motorola gives some extra features..
I returned to stock because of some options and features Stock firmware has... (FM radio, Sounds Effects, Assist, Moto Camera, OTG options on Settings > Storage, etc...)

Hi, i bougth the Moto G in Argentina with 4.4.2 and unlocked the bootloader, updated OTA to 4.4.4 and rooted the device , if i do this procedure will i lost the CMW recovery and/or root? the bootloader will remain unlocked?
i just tried the Factory Reset option but it ends un a bootloop... is there another option to have the stock rom clean or i have to do all this?
THANKS !

sublowBASS said:
Hi, i bougth the Moto G in Argentina with 4.4.2 and unlocked the bootloader, updated OTA to 4.4.4 and rooted the device , if i do this procedure will i lost the CMW recovery and/or root? the bootloader will remain unlocked?
i just tried the Factory Reset option but it ends un a bootloop... is there another option to have the stock rom clean or i have to do all this?
THANKS !
Click to expand...
Click to collapse
If you do all of this, you will loose root and CWM... but you can root it again when you do this procedure-- and the bootloader will remain unlocked. :good:

If you download the firmware in .xml.zip format enter :
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
Instead of mfastboot flash system system.img

Cyber. said:
If you download the firmware in .xml.zip format enter :
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
Instead of mfastboot flash system system.img
Click to expand...
Click to collapse
When I tried to flash my specific firmware, those commands didnt work, and somewhere else I read those commands you say are for some european devices. I use the system.img command and it worked every time I do it on my retail Arg moto g. That is a little difference between some devices.
Edit: sorry I forgot that the firmware I used was in tar.gz format, so that's why those commands didn't work for me.. If the firmware you download is xml.zip you have to use the other guide that is on sticky posts.

Thanks for your guide! It was very usefull.
I've been trying CM rom and the Decepticon kernel, and because of that I've reinstalled the stock rom quite a few times now.
Because of that, every time I restored the 4.4.2 rom (Retail Argentina) and then OTA to 4.4.4. It's very annoying to download that update every time and I couldn't find it online so I've made a backup of the update zip. That way I only need to enter into the recovery and flash the update.
Anyone else wants it?

I was worried about the sparsechunk.xx files as well, but flashing them worked no problem for me (I'm using the Bell 4.4.2 Canada firmware).
Got my Moto G back to Moto stock 4.4.2 from GPe 4.4.4 just fine! Thanks Marckozz <3 Can confirm this works for XT1032 in Canada (although this is probably the same model as an American one to be honest).

MarckozZ said:
Hello guys, this guide is to help you to go back to Stock Firmware from any custom ROM or from Google Play edition firmware.
I started this thread because I have an Argentinian Retail Moto G, and downloaded the retail 4.4.2 firmware for Argentina, it comes in *.tar.gz format, but the guide stated above was for *.xml.zip firmware, so here it comes some differences.
DISCLAIMER: If your Moto G dies, explodes, turn into a zombie, goes berserk and tries to kill you, I'm not the one to blame. I've tested this tutorial and worked for me, if this does not work for you, keep googling about your problem. I can help you but its not my fault! Try this at your own risk.
THIS SHOULD WORK ON LOCKED AND UNLOCKED BOOTLOADERS​
LETS BEGIN...
-1 - Make a backup of all the apps and media in your SD card because all of this erases and formats everything inside! So backup everything!
0 - DOWNLOAD and install Motorola drivers.
1 - Go to THIS PAGE and download a 4.4.2 firmware suitable for your device. In my case I searched and downloaded Retail Argentina 4.4.2 firmware. There aren't a lot of 4.4.4 specific firmware, so download a 4.4.2 firmware. After installing it, you can OTA to 4.4.4.
2 - On Windows, create a temporary folder in drive c:\ called "restore" so it would be like this: c:\restore ; and there using 7zip or similar, extract everithing inside the firmware file into this "retail" folder. (The firmware I needed was in *.tar.gz format but this can work if the firmware you get is in *.XML.zip format)
3 - Now, download the attachment I provide you (those three files are from 4.4.4 OTA ZIP). Extract and place them inside the "restore" folder and replace the files inside.
4 - Download "mfastboot-adb.rar" in the attachments. After that, extract everything inside the RAR in the "restore" folder.
Important: Everything has to be inside the "restore" folder, don't leave files inside extraxted folders. It has to look like this:
5 - Turn off the phone and turn it on in FASTBOOT MODE (When turned off tap and hold ON BUTTON and VOLYME DOWN BUTTON for 5 seconds and release them, you should see the FASTBOOT MENU) and plug the phone to PC via USB.
6 - Start CMD (Windows console) with Administrator rights (in Windows 7 click on Start and in the search bar write CMD and above right click on CMD and start it as Administrator) and type:
This will place the console inside the "restore" folder.
7 - Here starts the COPY-PASTE action. Don't miss ANY LINE here!!! Copy and paste this lines one by one, waiting to the flashing to finish and giving an OKAY as a result!!! If some of this commands gives a (bootloader) FAILED answer, try to repeat that command.
Please, I say this again! Do this one line at a time, waiting for every line to flash and perform actions and to return an OKAY as an answer...
If every step on the copy-paste steps give OKAY as an answer, you will see your Moto G return to life with the original Moto firmware!!!! The first boot will take like 7 or 8 minutes, so be patient!
So this is it. If you need help let me know below... :fingers-crossed:
Click to expand...
Click to collapse
i was on stock 4.4.4(no root no unlocked boot loader indian moto g)
then i installed Asian stock soak 5.0.2 from here
http://forum.xda-developers.com/moto-g/general/moto-g-xt1033-asia-retail-android-t3001206
but i want to install it from ota update( it has some other features also)
i have tried every damn method including yours but it shows invalid piv system signature file...
can you help?

gpe lollipop 5.0.1 to stock retail
hey man, thnks for ur guide, I have a question what if i have gpe. Lollipop 5.0.1 but i want the 5.0.2 lollipop retail firmware from motorola? How do i proceed? I want the argentinian retail stockand my bootloader is unlocked. Thks!

Maxxgavin said:
hey man, thnks for ur guide, I have a question what if i have gpe. Lollipop 5.0.1 but i want the 5.0.2 lollipop retail firmware from motorola? How do i proceed? I want the argentinian retail stockand my bootloader is unlocked. Thks!
Click to expand...
Click to collapse
Try this:
*Flash ENTIRE firmware image from Brazil Retail Lollipop 5.0.2... So your bootloader will be updated to Moto bootloader... (search in this forum that firmware image and steps to flash it, and yes, flash motoboot.img and gpt.bin also, I've done that and it can be flashed on top of the old Google bootloader from GPE)
*Then, flash Retail KK 4.4.4 using this guide, but dont flash motoboot or gpt.bin from 4.4.4....
*And last, update via OTA to Retail AR Lollipop...
:fingers-crossed:

Thks, but why do i have to flash the brazilian firmware first? Flashing directly the argentinian retail 5.0.2 wont work?

Maxxgavin said:
Thks, but why do i have to flash the brazilian firmware first? Flashing directly the argentinian retail 5.0.2 wont work?
Click to expand...
Click to collapse
there is no AR 5.0.2 firmware yet, you can either wait or do what @MarckozZ suggested

[GUIDE] Lollipop for XT1064 (CANADA ONLY)

This is a guide that is strictly for those who are as impatient as I am to get Lollipop on their Moto G (2014). I know there are several guides for folks in the US, and other countries as well, but currently there is no OTA for Canada yet. We are literally left out in the cold. So, I thought I would put a collaborative guide together so the Canadians can enjoy some 5.0, too!
First and foremost, if you F up your phone, that's on you. This will void your warranty, and I am in no way responsible for any stupidity you conjure up during the process.
I have only tested this on the XT1064, which is the single SIM US/Canada model.
The issue when trying to simply follow the upgrade guide for the XT1064 is that the OTA file looks for a 4.4.4 variant of Android that needs to be the same region as where the OTA came from. If you try to install it on the Canadian versions, you will get an error. So, here goes:
1. Unlock your bootloader. Follow this wonderful guide: http://forum.xda-developers.com/mot...wip-unlock-bootloader-moto-g-2nd-gen-t2875728
2. Download the US version of 4.4.4, it can be found here: http://www.filefactory.com/file/2ygnt0x45vcr/RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
3. Extract the above file to the same location you installed Minimal ADB in the first step (C:\Program Files(x86)\Minimal ADB and Fastboot)
4. Turn your phone off and disconnect it from the computer. Press and hold the volume down (-) button and power button to get into Fastboot mode. Connect your phone to the computer.
5. Run Minimal ADB and run these commands:
PHP:
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 erase cache
fastboot erase userdata
fastboot reboot
I removed the modem commands on purpose, and I will explain why later.
6. Once the phone has rebooted, plug it in to the computer and follow this guide: http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361
You should now have Lollipop on your Canadian XT1064!
If you have issues with the WiFi or cellular, you may have to flash the modem commands again from the old file. I had to download the original Canadian ROM (http://www.filefactory.com/file/78znv8hx0tvt/RETCA_XT1064_4.4.4_KXB21.85-16_cid14_CFC.xml.zip) and using Fastboot flash the following:
PHP:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
After that I had no issues and everything seems to be working as it should. You can relock your bootloader afterwards if you like as well.
Thanks to the other contributors above, I was simply trying to put a quick guide together for us Canadian folks who wish to get Lollipop, too!
Cheers!

This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?

This worked for me! Thanks for the awesome tutorial!

brianshayne said:
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
Click to expand...
Click to collapse
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?

NexusChrist said:
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
Click to expand...
Click to collapse
Yeah - I'm not sure what the problem was - originally it wouldn't take the US ROM due to a downgrade error. Tried it again, after a factory reset and for some reason it went through. Flashing Lollipop and the modem after was no issue at all - so good to go now. It's beautiful.
Thanks for the follow-up.
AKA: I should have just ignored downgrade error + HAB fail on phone, the first time around

I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help

ramzilla136 said:
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
Click to expand...
Click to collapse
Disregard the error and move on to the next command. You are going to get a few errors. Don't worry.

installing update
verifying current system
/system/app/3c_main.apl has unexpected contents
installation aborted
this is after i run the commands and upload from sd card...
followed your commands and tried few fresh zips
can you please help, it won't let me install the lollipop file

Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
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 system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot

TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
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 system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Is this procedure better? Any enhancement? Thanks.

Botsok said:
Is this procedure better? Any enhancement? Thanks.
Click to expand...
Click to collapse
This one just avoid you to flash USA KitKat and then Lollipop. This one goes directly to Lollipop.
Doesn't flash Modem/Radio from USA Lollipop because doesn't work on Canadian models, at least didn't work with WIND Mobile model.

WIND canada moto G XT1064 lollipop
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
https://mega.co.nz/#!dk430ZBZ!diHa6V-rcidHFc3niGjshk-2A9ELbqZtCnb63pFK010
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
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 system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse

Just a super-dooper-uber Thanks To NexusChrist!
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post

UnderAppreciatedDev said:
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
Click to expand...
Click to collapse
That happened because you flash the modem from Lollipop... Just flash the modem in OP and you will be ok.

spiritflare said:
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
Click to expand...
Click to collapse
Just a tad bit curious I also have a Wind Mobile Moto G2 and i'm just wondering how you unlocked the bootloader in the first place. If you could please share the process on how you did it that would be great.

Anyone know how we can get the LP bootloader on the Canadian version?
I'd like to be able to update my CM12.
Thanks!

Awesome
I'm on Bell &
everything is working 100% radio/wifi/bluetooth all good
Thanks

This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.

Kewjoe said:
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Click to expand...
Click to collapse
Your carrier is most likely the reason since they have the final say on updates.

Tel864 said:
Your carrier is most likely the reason since they have the final say on updates.
Click to expand...
Click to collapse
But what about the people that bought their phones from Staples. It's unlocked and not associated to any carrier. They are directly under Motorola and still no update at all. Phone are getting 5.1 update already, but we're still at 4.4.4
What's so different in the Canadian market from the US one that the update can't come fast? Specially if the phone is not associated to a carrier and the update should come directly from Motorola

[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

[How To] [XT1032] Koodo/Telus - Downgrade and/or Upgrade - LP -> KK -> LP

Scenario
So back in December of 2014 I upgraded to Lollipop by converting to GPE 4.4.4 and upgraded to LP via OTA. Now Telus/Koodo has upgraded to LP, I wanted to return to stock then back to LP on stock. Also I've missed my Radio sooo much...
Warning
So as you may have read in the forums do not, I say again, do not downgrade to 4.4.2 then upgrade to 4.4.4 because it will brick your phone! Something to do with the boot-loader, just saying. So please use the STOCK FIRMWARE linked below.
Required Files
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.2 - [LINK]
[TOOL] [WINDOWS] mFastboot-v2.zip - [LINK]
[STOCK FILE] XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml.zip - [LINK]
Instructions
Download required files above.
Install the ADB/FASTBOOT Tool.
Extract stock file and mFastboot-v2 into a directory that you can get to easily via command prompt.
Connect phone to computer and boot into bootloader. You may have to install drivers manually in the device manager for your phone "ADB Bootloader driver" or something like that. I'm not going into that detail here if you don't know how but you can use the forum search tools and/or Google.
Open Command Prompt with Administration Right and navigate to the folder you extracted the files to.
Run the following mFastboot commands below.
Now your phone will reboot and boot into KK 4.4.4 for Telus/Koodo subscribers.
Optional: OTA to LP 5.0 via system updates.
mFastboot Commands
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
Thanks & Sources
Snoop05 - ADB, Fastboot and Drivers - 15 seconds ADB Installer
Unknown - XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml.zip
Forum Guides Everywhere - Method to flash stock via mFastboot
Anything missing let me know in regards to thanks/sources.

akasaka said:
Scenario
So back in December of 2014 I upgraded to Lollipop by converting to GPE 4.4.4 and upgraded to LP via OTA. Now Telus/Koodo has upgraded to LP, I wanted to return to stock then back to LP on stock. Also I've missed my Radio sooo much...
Warning
So as you may have read in the forums do not, I say again, do not downgrade to 4.4.2 then upgrade to 4.4.4 because it will brick your phone! Something to do with the boot-loader, just saying. So please use the STOCK FIRMWARE linked below.
Required Files
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.2 - [LINK]
[TOOL] [WINDOWS] mFastboot-v2.zip - [LINK]
[STOCK FILE] XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml.zip - [LINK]
Instructions
Download required files above.
Install the ADB/FASTBOOT Tool.
Extract stock file and mFastboot-v2 into a directory that you can get to easily via command prompt.
Connect phone to computer and boot into bootloader. You may have to install drivers manually in the device manager for your phone "ADB Bootloader driver" or something like that. I'm not going into that detail here if you don't know how but you can use the forum search tools and/or Google.
Open Command Prompt with Administration Right and navigate to the folder you extracted the files to.
Run the following mFastboot commands below.
Now your phone will reboot and boot into KK 4.4.4 for Telus/Koodo subscribers.
Optional: OTA to LP 5.0 via system updates.
mFastboot Commands
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_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
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
Thanks & Sources
Snoop05 - ADB, Fastboot and Drivers - 15 seconds ADB Installer
Unknown - XT1032_TELUS-CA_4.4.4_KXB21.14-L1.50_52_cid14_CFC_1FF.xml.zip
Forum Guides Everywhere - Method to flash stock via mFastboot
Anything missing let me know in regards to thanks/sources.
Click to expand...
Click to collapse
Do NOT flash 4.4.4's motoboot if you had already upgraded to Lollipop via OTA or system image

I had upgraded via OTA originally and downgraded and upgraded via my method above. Everything went well.

Thanks, I was using a custom recovery and was having no luck downloading the OTA (repeated hung at 353.2mb of 358.2mb).
What I did

Your welcome let me know how it turned out for you.

DustArma said:
Do NOT flash 4.4.4's motoboot if you had already upgraded to Lollipop via OTA or system image
Click to expand...
Click to collapse
If I don't flash motoboot from 4.4.4, the phone don't boot at all (error: UTAG "flashfail" configured as fastboot)
If I flash it later, again: the phone don't boot. (same error: UTAG "flashfail" configured as fastboot)
It was necessary to flash it using @akasaka's sequence of commands in order to boot my phone (when flashing motoboot will appear a message about „bootloader downgrade tz”)
I installed 4.4.4 retail.DE on my 5.0.1 GPE. I have a XT1032 Moto G.
Later I installed the DE OTA zip for 5.0.2 Lollipop from Recovery>SDcard (It took some time, about 15 min). Everything was alright
So, tested on my own phone XT1032: GPE 5.0.1 > KK 4.4.4 (DE) > Lollipop 5.0.2 Moto (DE).
Method successful confirmed. Thank you @akasaka.

OTA update to LP
Hi all, I was hoping someone might know how to fix my problem. I tried this method , returned my xt1032 back to stock as per the procedure above. I booted into the rom updated the Motorola updater and downloaded the ota VIA the system update in settings, when it updates if fails with this message
Package expects build fingerprint of motorola/falcon_tkpca/falcon_umts:4.4.4/KXB21.14-L1.50/52:user/release-keys or motorola/falcon_tkpca/falcon_umts:5.0.2/LXB22.46-32/31:user/release-keys this device has motorola/falcon_tkpca/falcon_umts:4.4.4/KXB21.14-
I must have some corruption in the fingerprint, I tried backdating via my original back up from back last June JB I think, then updated via system update to KK 4.4.4 and then tried the OTA again, and got same message

frgmelester said:
Hi all, I was hoping someone might know how to fix my problem. I tried this method , returned my xt1032 back to stock as per the procedure above. I booted into the rom updated the Motorola updater and downloaded the ota VIA the system update in settings, when it updates if fails with this message
Package expects build fingerprint of motorola/falcon_tkpca/falcon_umts:4.4.4/KXB21.14-L1.50/52:user/release-keys or motorola/falcon_tkpca/falcon_umts:5.0.2/LXB22.46-32/31:user/release-keys this device has motorola/falcon_tkpca/falcon_umts:4.4.4/KXB21.14-
I must have some corruption in the fingerprint, I tried backdating via my original back up from back last June JB I think, then updated via system update to KK 4.4.4 and then tried the OTA again, and got same message
Click to expand...
Click to collapse
I have had the exact same problem. I've been working on this all day.

Ya over a week for me . i've flashed every back up I had! including my original from unlocking my bootloader . my first ota to KK went through but not the LP ota . I'm at a loss .I used the same ota to update my wife's untouched moto g an it worked fine . I'm looking into modifing the updater script but I m over my head with what I need to change to force the updade . cm 12 is
running not to bad but I wanted to try original
Sent from my Moto G using XDA Free mobile app

LeopardSurd said:
If I don't flash motoboot from 4.4.4, the phone don't boot at all (error: UTAG "flashfail" configured as fastboot)
If I flash it later, again: the phone don't boot. (same error: UTAG "flashfail" configured as fastboot)
It was necessary to flash it using @akasaka's sequence of commands in order to boot my phone (when flashing motoboot will appear a message about „bootloader downgrade tz”)
I installed 4.4.4 retail.DE on my 5.0.1 GPE. I have a XT1032 Moto G.
Later I installed the DE OTA zip for 5.0.2 Lollipop from Recovery>SDcard (It took some time, about 15 min). Everything was alright
So, tested on my own phone XT1032: GPE 5.0.1 > KK 4.4.4 (DE) > Lollipop 5.0.2 Moto (DE).
Method successful confirmed. Thank you @akasaka.
Click to expand...
Click to collapse
For the Movistar Chilean system image I didn't flash motoboot coming from brazil 5.0.2 and had no problems booting the ROM

May I ask what ROM's are you installing? Should be installing the STOCK firmware linked above.

akasaka said:
May I ask what ROM's are you installing? Should be installing the STOCK firmware linked above.
Click to expand...
Click to collapse
yes step by step as provided in this thread
---------- Post added at 06:02 PM ---------- Previous post was at 05:03 PM ----------
david77123 said:
I have had the exact same problem. I've been working on this all day.
Click to expand...
Click to collapse
Did you try Fastboot or Mfastboot ?? or both? just wondering if i should try with both

@frgmelester & @david77123
Please ensure you use mFastboot, that's how I restore. Also are you booting the Phone into 4.4.4 and updating via OTA? Not side-loading.

I have tried fastboot, mfastboot, restoring to 4.4.4 and using both adb sideload and the ota.

david77123 said:
I have tried fastboot, mfastboot, restoring to 4.4.4 and using both adb sideload and the ota.
Click to expand...
Click to collapse
mfastboot workded for me , i also installed the ADB posted in this thread. just finished patching the OTA booting into LP now

frgmelester said:
mfastboot workded for me , i also installed the ADB posted in this thread. just finished patching the OTA booting into LP now
Click to expand...
Click to collapse
I'm glad to hear that.

frgmelester said:
mfastboot workded for me , i also installed the ADB posted in this thread. just finished patching the OTA booting into LP now
Click to expand...
Click to collapse
No such luck for me

I used the Minimal ADB and Fastboot by shimp208 linked in step "D" of this post
I also cut and paste, line by line, the the code from "Step 3B" of the same post. Just remove the "m" from "mfastboot" and don't forget to add a decimal between sparsechunk and the numeric (ie. sparsechunk.0 not sparsechunk0).
Running a couple of days now on 5.02, all good. Around 500 available memory, less than some folks are reporting and that could be some of my apps, GPS appears a bit faster to fix though that may just appear that way.

LeopardSurd said:
If I don't flash motoboot from 4.4.4, the phone don't boot at all (error: UTAG "flashfail" configured as fastboot)
If I flash it later, again: the phone don't boot. (same error: UTAG "flashfail" configured as fastboot)
It was necessary to flash it using @akasaka's sequence of commands in order to boot my phone (when flashing motoboot will appear a message about „bootloader downgrade tz”)
I installed 4.4.4 retail.DE on my 5.0.1 GPE. I have a XT1032 Moto G.
Later I installed the DE OTA zip for 5.0.2 Lollipop from Recovery>SDcard (It took some time, about 15 min). Everything was alright
So, tested on my own phone XT1032: GPE 5.0.1 > KK 4.4.4 (DE) > Lollipop 5.0.2 Moto (DE).
Method successful confirmed. Thank you @akasaka.
Click to expand...
Click to collapse
I know that this may seem redundant, but I would like to clarify the situation.
In order to go to Motorola 5.0.2 (EU or DE) from GPE 5.0.1 you have to downgrade to KK 4.4.4(EU or DE).
When downgrading the command sequence should be:
Code:
mfastboot flash partition gpt.bin
[B]mfastboot flash motoboot motoboot.img[/B]
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
And in order to upgrade, the (Motorola) 5.0.2 OTA zip can be flashed through recovery.
So my questions are
motoboot must be flashed and does not lead to a brick? (I believe that you answered this question, but I'm confused because some people say that you can brick your device this way)
Do you have to update the Motorola OTA app before upgrading or you can flash 5.0.2 directly from recovery?

Reply to sigma95
@sigma95
Just take in account that I am restoring stock firmware to a stock device. I don't care if you converted it to GPE on any device. If you are restoring stock firmware via Fastboot to the device and carrier it was intended for then you should not have any issues.
My instructions where for the Telus Moto G 2013 (1st Gen) XT1032 devices. All I've done has returned the phone to it's original state. (Minus the boot being locked which I don't think it can be undone.)
Question One: motoboto
That all being said, use mFastboot and flash the motoboot image and you should be fine. Mine has worked and so have others.
A lot of the boot issue with the motoboot is downgrading to 4.4.2 then upgrading to 4.4.4 (that causes the boot failure). By downgrading to 4.4.4 the change to the bootloader where implemented in prep for the Lollipop update. Thats what I understand from the talk back in the days of the 4.4.4 update.
Question Two: Update to LP
As for the update to Lollipop. You could update via recovery but if I understand correctly Moto had to update some of their software via the Play Store before updating to Lollipop via OTA. This is due to device support issues and ensuing the device is supported. You will likely get a recover error if you try via recovery for updating from a hash issue for a app in the code saying that the files are not the same.
I recommend you let it bootup and download and update via OTA.
I have a question
Why do you want to upgrade via recovery? Particularly when your returning to stock and not custom roms or stock firmware for other devices. This question isn't in spite, I really don't understand.

Unable to update OTA since repair - alternatives?

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

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

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

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

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

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

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

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

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

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

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

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