Database Users

[OFFICIAL STOCK.IMG] WIFI ONLY MZ604_HWI69 - Official Motorola software

The files were posted today. Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

You noticed this too I see. Glad you posted this as a new thread. I was just randomly posting that link in threads where stock images may have helped.
I'm not home to try it yet but I'm guessing that's a US image?

Ahhhhh finally.

i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!

vista64 said:
i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!
Click to expand...
Click to collapse
If you want to be extra safe, start over from the beginning. You're probably still unlocked (but not rooted) if you managed to flash boot and system.

i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??

DinarQ8 said:
i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??
Click to expand...
Click to collapse
Only if you can get into fastboot mode AND your computer can see it. But if I recall, neither ADB, Fastboot nor RSD Lite will see your Xoom?

maybe solution i wait SBF file

Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody

what he said ^

Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...

If i remember correctly, scourge said that both devices are exactly the same hardware. Therefore flashing either version's set of images is irrelevant as long as you do WIFI for that model and 3G for that one.

odyseus said:
Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody
Click to expand...
Click to collapse
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.

Scourge1024 said:
Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...
Click to expand...
Click to collapse
FYI,
$ md5sum MZ604_HWI69.zip
ae9b9f5693c4b49c745cb017afe1a4b5 MZ604_HWI69.zip
$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip
You might be OK if you can get something that'll handle errors better.

In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Code:
mac-mini:mz604_img Howard$ md5 MZ604_HWI69.zip
MD5 (MZ604_HWI69.zip) = ae9b9f5693c4b49c745cb017afe1a4b5
mac-mini:mz604_img Howard$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip.
mac-mini:mz604_img Howard$

Scourge1024 said:
In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Click to expand...
Click to collapse
Yep, IIRC, ext maintains a mount count. One'd need some file system tools to properly verify.

Can someone post a walk through on how to do this?

pricej636 said:
Can someone post a walk through on how to do this?
Click to expand...
Click to collapse
from the op:
Instructions to return it to stock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

Scourge1024 said:
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.
Click to expand...
Click to collapse
Fair do's - I don't blame you! You've done enough As you say why re-lock on WiFi?
What I would really like to do is flash all the images to my UK WiFi Xoom and then try to install Bignadad's BigDX Xoom|Zoom Theme..
Previously flashing this theme soft-bricked my UK xoom - got loads of Force Closures. Installing the extracted images from you, still caused the same problem. Maybe it only works on the US WiFi Xoom, but I might re-flash with 'stock' ROM to see if that makes any difference? (I do have CWM nandroid backups in case of another soft brick!)
Cheers
Ody

Is there a risk with using these cause of zip extra bytes warning?

[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

[IMG] 5.0 Lollipop RETEUALL XT1092 LXE22.46-19

Haven't seen it around here, so I thought sharing is caring:
Image of Lollipop 5.0 RETEUALL for XT1092 version LXE22.46-19
DOWNLOAD http://motofirmware.com/files/file/1055-reteuall-xt1092-50-lxe2246-19-cid7-cfcxmlzip/
Enjoy!
How to flash (taken from https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and modified)
After downloading the image for your device:
Unzip the image.
Put your device in fastboot mode. [e.g. by using "$ fastboot reboot"]
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility [better known as "mfastboot.exe" - so you probably change the command "fastboot" to "mfastboot"]
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ 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_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 modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot erase customize [leave that out if you have special customization from motomaker]
$ fastboot erase clogo [leave that out if you have special customization from motomaker]
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Click to expand...
Click to collapse
If you don't know how to flash it - don't! I am not responsible if anything goes wrong!

Whats the method to flash this ?

willy_907 said:
Whats the method to flash this ?
Click to expand...
Click to collapse
added a quick tutorial from motorola with a few modifications and notes.

Hi good afternoon , I Flashed with RSD LITE , and perfect. thank you very much
regards

Is there anyone who would be able to get hold of Motorola signed images? That would be aweosme.
Many thanks for this too

subhramani said:
Is there anyone who would be able to get hold of Motorola signed images? That would be aweosme.
Many thanks for this too
Click to expand...
Click to collapse
What would be the use for this? For devices without an unlockable bootloader? Just curious why this wouldn't suffice.

It will be useful when you want to lock the bootloader back again.
I'm sure you'll want it if you were from a country like mine.

subhramani said:
It will be useful when you want to lock the bootloader back again.
I'm sure you'll want it if you were from a country like mine.
Click to expand...
Click to collapse
Once you request for the unlock code and unlock the bootloader of your device its done, relocking won't help you to claim warranty if the service center guy looks it up.

nithin1992 said:
Once you request for the unlock code and unlock the bootloader of your device its done, relocking won't help you to claim warranty if the service center guy looks it up.
Click to expand...
Click to collapse
Worth keeping it justin case right?

I think it's time to finally unlock the bootloader of my phone, now I have the factory firmware for my model and variant
Thanks for this.

How to know if mine is RETEUALL or other?
Thanks
Edit: solved thanks

Hi, thanks for the upload.
I have a question, as my device is XT1092, the european version. But my carrier, Orange Spain, sells the Moto X unlocked, or they say so, and my phone version goes by 21.21.45.victara_oraeu.oraeuall.en.EU oraes. Should I be able to flash the ROM? I have experience doing so, so my question is just this one.
Thanks.

Yes, you can flash this image.
I myself flashed it on my French Orange Moto X (orafr).

-iNSiGhT- said:
Yes, you can flash this image.
I myself flashed it on my French Orange Moto X (orafr).
Click to expand...
Click to collapse
Good to know, thanks!
I'm pretty sure I flashed this file on my Orange Moto X but I still have "orafr" after "22.21.19.victara_reteu.reteuall.en.eu".
Is it the same for you ?

ichi go said:
Good to know, thanks!
I'm pretty sure I flashed this file on my Orange Moto X but I still have "orafr" after "22.21.19.victara_reteu.reteuall.en.eu".
Is it the same for you ?
Click to expand...
Click to collapse
I have that too, but since i flashed the retail modem (modem and fsg files) i think the "orafr" is related to the efs partition (something we don't "touch" during the flash process.

-iNSiGhT- said:
I have that too, but since i flashed the retail modem (modem and fsg files) i think the "orafr" is related to the efs partition (something we dont "touch" during the flash process.
Click to expand...
Click to collapse
OK, you're probably right.
Thanks for your answer.

NVM Posted in the wrong thread.

Hello to All
Can someone give me a good link to the mg file, the link is broken...
Thank you

cesarium said:
Hello to All
Can someone give me a good link to the mg file, the link is broken...
Thank you
Click to expand...
Click to collapse
http://www.androidgb.com/download-moto-x-2nd-gen-2014-android-5-0-lollipop-factory-image-784/

Nicolae-Daniel said:
http://www.androidgb.com/download-moto-x-2nd-gen-2014-android-5-0-lollipop-factory-image-784/
Click to expand...
Click to collapse
was searching for the 5.0 stock cause each time i've downgraded to stock 4.4.4 and OTA'd to the latest.. and it was timeboggling!
Thank you!

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

[HELP] Return to stock before selling G5 Plus!

Hi! I could really need some help over here!
I have a G5 Plus that i bought in Sweden, Europe. I unlocked bootloader, and flashed a ROM.
But now i´m going to sell it, so i need to reflash the stock image (ROM). Also i need to relock bootloader.
Can someone help me find the latest, working firmware, and also with the right commands to use with fastboot to do this?
Modell is: X1685.

Why would you need to relock the bootloader? I guess you will sell the device warning the person that it doesn't have warranty, right?

I was going to type this but then found this post....
lvvine said:
NPN25.137-35
https://drive.google.com/file/d/0B3G...ew?usp=sharing
Watch the Video which will help you to flash the firmware.
https://www.youtube.com/watch?v=blYQ28DZJQk
Use FastBoot Command to flash the firmware (Backup you data as it would erase the internal Memory)
Fastboot command:
fastboot oem fb_mode_set
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 dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse

eemgee said:
I was going to type this but then found this post....
Click to expand...
Click to collapse
Be careful, it will flash the bootloader. If you have a newer version of the bootloader than th one you sumbitted, you will harfbrick your device.

M1810 said:
Be careful, it will flash the bootloader. If you have a newer version of the bootloader than th one you sumbitted, you will harfbrick your device.
Click to expand...
Click to collapse
If the stock ROM is older than what you have on your device, then the bootloaders usually prevent you from downgrading.
Hard bricks usually do not happen when you downgrade, they happen if you've downgraded and then take OTA updates (mismatches between the bootloader patch level and system patch level are a culprit). Best way to avoid this is to not downgrade.
At any rate, you cannot lock a bootloader with a build older than your existing stock firmware, regardless of custom ROMs flashed. You need a firmware of the same or newer build than your device stock firmware to relock. To the best of my knowledge, NPNS25.137-33-11 appears to be the newest or nearly newest firmware for EU devices. You can download from here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ please confirm that this firmware is suitable before flashing.
You could try re-locking with other firmware, however NPN25.137-35 is for US devices, so would not likely receive OTA updates if flashed onto EU devices. As for warranty, the warranty isn't transferable as far as I know and as Motorola's got a record of the device being unlocked, the warranty is void. However, under EU consumer laws, you or the buyer could still get repairs if you're both resident in the territory. Would be wise to check this and let the buyer know.

Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.

syl0n said:
Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.
Click to expand...
Click to collapse
Original current gb version is as screenshot, anything else may screw up you phone.

syl0n said:
Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.
Click to expand...
Click to collapse
hi, i have similar issue. can you tell me how you fixed it?

Smeagal192 said:
Original current gb version is as screenshot, anything else may screw up you phone.
Click to expand...
Click to collapse
There appears to be no fastboot flashable file for this version available anywhere on the internet. I've searched for days and had absolutely no luck!
Looks like both the OP and I are stuck on custom ROMs. Why Lenovo don't make these available I don't know...
If anyone knows of anywhere to get this please help us.
EDIT: Oh, also mine is XT1684 which I've seen virtually nothing about on XDA.

darkglobe87 said:
There appears to be no fastboot flashable file for this version available anywhere on the internet. I've searched for days and had absolutely no luck!
Looks like both the OP and I are stuck on custom ROMs. Why Lenovo don't make these available I don't know...
If anyone knows of anywhere to get this please help us.
EDIT: Oh, also mine is XT1684 which I've seen virtually nothing about on XDA.
Click to expand...
Click to collapse
Mines a 1684, seems moto made 2 models for UK with same specs.
Regarding fastboot did you extract download zipped archive into fastboots folder.
When I say download follow the link above to firmware centre, if using phone to browse you need phone in landscape otherwise you cannot get name.

Smeagal192 said:
Mines a 1684, seems moto made 2 models for UK with same specs.
Regarding fastboot did you extract download zipped archive into fastboots folder.
When I say download follow the link above to firmware centre, if using phone to browse you need phone in landscape otherwise you cannot get name.
Click to expand...
Click to collapse
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it. Thanks though.