Database Develop

[Q] When is Lollipop going to be pushed?

So I just bought my Moto G 2014 (unlocked) and I have it all activated and set up. I was wondering though when Lollipop will be pushed so I can update to it? All I see articles are saying "It will get it" and "you should be able to update to it now" but I can't and I really don't want to void my warranty a day after I bought the phone. I want to try vanilla* Lollipop. Does anybody know when exactly?
( * = without having to manually install it via unlocking bootloader and using fastboot)

Motorola knows.

If it is the XT1063/4 ones, you can already install it via OTA.
Sent from my XT1064 using XDA Free mobile app

I have an Xt1064 and I still havent received the update. Is the update available here the same as the OTA? Im tempted to just install that one.
PerrottiX said:
If it is the XT1063/4 ones, you can already install it via OTA.
Sent from my XT1064 using XDA Free mobile app
Click to expand...
Click to collapse

I have XT1063 and I still didn't get the update through OTA as well. Is this normal?

i was trying
Hello, im from Perú. I got an XT1063 so when i am flashing i got two problems
1. hab check failed for boot
2. hab check failed for recovery
so anyone can help me?
I tried with Fastboot and with mfastboot, but same result.
I found this updates in other web which you can update to lollipop. Can anybody try them? I want to try but i can open the recovery...
getmovil dot com / motorola / root-moto-g-2014-android-lollipop /comment-page-1 /#comment-83348

Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.

Lokke9191 said:
Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.
Click to expand...
Click to collapse
...from where can i download the proper ota zip????
mine is MOTO G2 (2nd GEN) XT1068 dual sim europe

You can't. Lollipop isn't released for the XT1068 yet. But be patient. I suspect it to be there in the first or the second quarter of 2015! (And with a little luck maybe even this year...).

i understood we will take directly :angel:Android 6.0 (M) Milky Bar.......:good:

htcgr said:
i understood we will take directly :angel:Android 6.0 (M) Milky Bar.......:good:
Click to expand...
Click to collapse
Honestly, it should be there anytime now. But people keep asking the question over and over again: when is it coming? This is annoying, because no one really knows!

Lokke9191 said:
Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.
Click to expand...
Click to collapse
any idea how to re-lock the bootloader? :good:

kevin_arthur said:
any idea how to re-lock the bootloader? :good:
Click to expand...
Click to collapse
Follow the guide at ( http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/ ). However there's a couple of things you have to do differently.
Your first command after you enter fastboot mode is gonna have to be "mfastboot.exe oem lock begin".
Theres also gonna be four system.img that you have to flash so after the command "mfastboot.exe flash system system.img_sparsechunk.2" you have to enter the command "mfastboot.exe flash system system.img_sparsechunk.3". Follow the rest of the guide, including the "mfastboot.exe oem lock" command at the end.
So basically the commands would be...
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
My phone automatically rebooted after that last command and my boot loader was locked even though it still displays the "Bootloader Unlocked" screen, I was able to flash the zip in the OP through the stock recovery after that.
COPIED AND PASTED FROM ANOTHER THREAD.
Courtesy of captivatingtab
---------- Post added at 11:29 AM ---------- Previous post was at 11:13 AM ----------
htcgr said:
...from where can i download the proper ota zip????
mine is MOTO G2 (2nd GEN) XT1068 dual sim europe
Click to expand...
Click to collapse
The xt1068 ota isnt available yet. There is a process to install another versions firmware on the xt1068 then upgrade to lollipop. But it looks buggy and super risky. I wouldn't recommend trying it. Id wait a little for the 1068 ota to be released. I know the other poster said it wont be available until 2015. But nobody knows for sure when itll be out. If i where to guess, id say itll be out fairly soon, sometime in the next 30 days. If I where you Id play it safe and wait it out.
---------- Post added at 11:32 AM ---------- Previous post was at 11:29 AM ----------
The only otas out so far are for the 1064 & 1063.

wish me luck!
Lokke9191 said:
Follow the guide at ( ). However there's a couple of things you have to do differently.
Your first command after you enter fastboot mode is gonna have to be "mfastboot.exe oem lock begin".
Theres also gonna be four system.img that you have to flash so after the command "mfastboot.exe flash system system.img_sparsechunk.2" you have to enter the command "mfastboot.exe flash system system.img_sparsechunk.3". Follow the rest of the guide, including the "mfastboot.exe oem lock" command at the end.
So basically the commands would be...
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
My phone automatically rebooted after that last command and my boot loader was locked even though it still displays the "Bootloader Unlocked" screen, I was able to flash the zip in the OP through the stock recovery after that.
COPIED AND PASTED FROM ANOTHER THREAD.
Courtesy of captivatingtab
Click to expand...
Click to collapse
okey, i will try.
thank you my friend!

smitharro said:
You can't. Lollipop isn't released for the XT1068 yet. But be patient. I suspect it to be there in the first or the second quarter of 2015! (And with a little luck maybe even this year...).
Click to expand...
Click to collapse
It'll be sooner than that. Within the next 6 weeks.
Sent from my XT1068 using XDA Free mobile app

Lokke9191 said:
Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.
Click to expand...
Click to collapse
i have the international unlocked xt1063. where can i get the zip?

Is there any official source on the release date?

Kobro said:
i have the international unlocked xt1063. where can i get the zip?
Click to expand...
Click to collapse
Its in the general section under a thread titled ota-index 1063-1064 update to lollipop.

I have a complete stock, nothing flashed or rooted or anything xt1064 and it says the zip needs a fingerprint when I try to install it from this thread...
http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361/page11

htcgr said:
i understood we will take directly :angel:Android 6.0 (M) Milky Bar.......:good:
Click to expand...
Click to collapse
its a Marshmallow 6.0

[Q] lollipop to kit kat?

Is it possible to downgrade from lollipop to KitKat? Is there any guide out there?
I have a simfree uk motox 2014 from Motorola, currently unrooted
Please let me know!
Thanks and happy holidays

If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Edit: You can't just flash factory image to downgrade. See my post below.

_MetalHead_ said:
If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Click to expand...
Click to collapse
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L

varignet said:
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L
Click to expand...
Click to collapse
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.

_MetalHead_ said:
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.
Click to expand...
Click to collapse
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks

fbiryujin said:
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks
Click to expand...
Click to collapse
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.

_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Edit: Also I take it that I should use mfastboot?

fbiryujin said:
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Click to expand...
Click to collapse
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.

Huh, I had never heard of RSD Lite before... I have just been using mfastboot.

_MetalHead_ said:
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.
Click to expand...
Click to collapse
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it

fbiryujin said:
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it
Click to expand...
Click to collapse
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.

_MetalHead_ said:
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.
Click to expand...
Click to collapse
Thanks. I'll use mfastboot just to be sure (If I even need to downgrade). Now to wait for that Walnut Finish to come back in stock :/

mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04

NWKENT said:
mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04
Click to expand...
Click to collapse
I wonder why they stopped including XML files...

_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.

divergens said:
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.
Click to expand...
Click to collapse
So you skipped "fastboot flash boot boot.img"?

No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img

divergens said:
No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.

fbiryujin said:
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.
Click to expand...
Click to collapse
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.

divergens said:
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.
Click to expand...
Click to collapse
Haha my main device is sadly an iPhone 6 right now, and that's too big. I prefer the size of the iPhone 5S or the first gen Moto X. I want to be able to use the entire device with one hand while being secure in the fact that a movement or gesture won't loosen my grip on it. Sadly the world is just making bigger phones now, and the few smaller ones out there are "cheap" low budget/power options.

My XT1072 stuck on fastboot flash screen - Help needed

Hi,
I have an XT1072 which was rooted and running CM. Since I wanted to install stock ROM, I used the Windows Tool from this forum to restore stock Android. By doing so, I was stuck with Bootloader locked screen.
Since then I am stuck on Fastboot Flash Mode screen (see pic attached).
When I try to connect my device to the same PC or any other PC and try mfastboot or fastboot or any command, it just says Waiting for device. I have all the required drivers installed in all the PCs I tested.
Using the volume buttoms, I am able to select any option, but it wont open any option (such as Normal Powerup or Recovery)
Can someone help?
Thanks

anyone?

ram11 said:
anyone?
Click to expand...
Click to collapse
Your system image is signed using incorrect key. Reflash system partition with factory image.

LuK1337 said:
Your system image is signed using incorrect key. Reflash system partition with factory image.
Click to expand...
Click to collapse
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?

ram11 said:
Hi, I am unable to do anything as the phone is not even identified by the PC, and although I am able to select any option using the volume buttons, it doesn't do anything.
Any other suggestions on how to re-flash as you said?
Click to expand...
Click to collapse
You need to get fastboot drivers...

LuK1337 said:
You need to get fastboot drivers...
Click to expand...
Click to collapse
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.

ram11 said:
Hi, like I said above, I have tried fastboot and mfastboot commands but when I try that it says "waiting for device" and it does nothing.
I have ADB and fastboot drivers on my pc, and they used to work just before I encountered the above mentioned error.
Not sure how to proceed here.
Thanks if you could provide a workable solution.
Click to expand...
Click to collapse
Join #titandev at freenode in 20 mins, I'll try to help you out.
Sent from my Moto G 2014 LTE using Tapatalk

Any luck?
Hi Guys,
I know this is a long shot as this is an old thread but did you get anywhere with a resolution to this?
I'm in the exact same position.
Tried flashing with different factory roms and "fastboot boot" to try force it to boot a twrp image

I'm also stuck here, anyone has had any luck?

Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
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
Click to expand...
Click to collapse
This will flash the fw, factory reset and reboot the phone.

I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it
dr.nic said:
Guys i think you just need to flash over the entire fw.
Just get fastboot+mfastbootv2, motoroladevicemanager (for phone drivers) and then flash over the original stock fw, you can get the right one for you phone/region here -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
This will flash the fw, factory reset and reboot the phone.
Click to expand...
Click to collapse
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!

Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot reboot
Click to expand...
Click to collapse
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks

dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
Bootloader should check if boot and system images are correct otherwise it should send user back to bootloader.

dr.nic said:
Sorry guys tought that could help, i fixed mine like that, flashing latest reteu fw on my reteeu phone, mine was unlocked tought ^^ when this happened to me, but doing some more investigation reveal more and more posts whit the same problem and unlocked bootloader.
if you had it unlocked previusly may be worth checking, if the "get unlock code" work or not and check the old mails for the unlock code sent by motorola (luckly i have a backup of mine xD).
Anyway Luk1137 was talking about /system partition only, worh trying
@LuK1337 can you explain a bit more pls ? I had the same problem but fixed it in a few secs by flashing the whole fw and got no errors, also i tought flashing correct region/model stock fw on the phone don't require to unlock the bottloader, thanks
Click to expand...
Click to collapse
I gave this a shot as suggested and I'm getting this error:
C:\Users\Nick\Downloads\New folder>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259279 KB)...
OKAY [ 9.742s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.131s
Also getting the error:
version downgraded for system
Invalid PIV signed system image

Out of tricks stock flash + factory reset always worked for me sorry.
I noted my phone model/region before doing anything (xt1072-thea-reteu) got the right fw and it worked fine, maybe was another problem giving the same error "failed to validate system image" unable to boot and stuck in bootloader, weird.... :\

Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?

nickkk93 said:
Well thanks for trying.
I've been giving it another shot again and I still can't get past these errors.
Anyone any more ideas or shall we admit defeat?
Click to expand...
Click to collapse
My phone is in a drawer I'd love to be able to fix it because I really miss Android now but it there doesn't seem to be a solution... I am no giving up hope entirely though!

I tink that I have similar problem with my X1072.
After unroot with Kingroot and install AdAway and TWRP from Google Play I even noticed that I hadn't unlock bootolader.
Now I can't reboot my phone without entering in Bootloader and reseting to factory defaults. After some reboots no data has been deleted.
I have tried to reflash the entire phone but In bootloader mode the phone is not detected by the computer, so I can't flash. I'm stucked. by now

josepmanel said:
I tried doing this but as soon as I enter "mfastboot flash partition gpt.bin" it gives me the error "Preflash validation failed". I always get the same error when trying to flash ANYHTING. I suppose it is because i relocked the bootloader out of ignorance. I' a bit desperate actually, I think I might have a brick... but I won't give up!
Click to expand...
Click to collapse
Have you had any luck at all? My phone has been in a drawer for a couple of months now...

Guys try flashing the latest MM stock i discovered an error too in my old update script /sniff.
Run the *.bat as admin .
Stock zip for XT1072:
MEGA Mirror 1
MEGA Mirror 2
Fastboot+mfastbootv2
BAT File
MM Flash BAT said:
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 system system.img_sparsechunk.4
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
Click to expand...
Click to collapse
Also remember if you are on another model and not XT1072 you should dl the correct image for your phone from HERE Look if Android 6 is available for your country, if you have gb-de-fr-es you can use the EU stock image.
Unpack everything in the same folder and launch the *.BAT as admin

Installation error rom XT1078

hello all right with you, I hope so, I am Brazilian, and I would take a doubt on the bike variant g2 xt1078 of my region (Brazil).
Accidentally I Flashed the ROM xt1068 on my mobile xt1078, and now the first command "mfastboot.exe flash partition gpt.bin" shows the error "GPT Version Downgrade". And then camndo "mfastboot.exe flash system system.img_sparsechunk.0" It also shows the error "Image is too large" with this system partition has been reduced or changed, I wonder if this has repair, and that any suggestion and welcome.
@lost101 
 @Kamin4ri
 @VitaTaf
 @parrotgeek1
l.rochas

Is your Bootloader unlocked?

lost101 said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
yes unlocked.

What is the exact name of the XT1078 firmware image your are currently trying to flash?

lost101 said:
What is the exact name of the XT1078 firmware image your are currently trying to flash?
Click to expand...
Click to collapse
this and the image of factory with august patch
XT1078_THEA_RETBR_DS_6.0_MPBS24.65-34-5_cid12_subsidy-DEFAULT_CFC.xml
mfastboot flash partition gpt.bin
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 system system.img_sparsechunk.4
And the rest of the commands operates normally

@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
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 system system.img_sparsechunk.4
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​
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493

lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
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 system system.img_sparsechunk.4
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​
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said

lost101 said:
@l.rochas - Do commands in this order:
mfastboot flash motoboot motoboot.img
mfastboot flash partition gpt.bin
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 system system.img_sparsechunk.4
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​
Use this version of mFastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
@lost101
does not work, same mistakes previously said

l.rochas said:
@lost101
does not work, same mistakes previously said
Click to expand...
Click to collapse
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052​
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.

lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052​
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
It seems to be a very risky method, but not hurt to try.

l.rochas said:
It seems to be a very risky method, but not hurt to try.
Click to expand...
Click to collapse
You already almost completely destroyed your handset by flashing the wrong bootloader. You don't exactly have many options here.

lost101 said:
The issue appears to be that you have flashed the XT1068 Bootloader and this cannot be simply undone by flashing the motoboot.img via mfastboot.
This thread describes the process for unbricking an XT1068, but may also be applicable for your handset. You will need another user with an XT1078 to provide you with the partition backups:
http://forum.xda-developers.com/moto-g-lte/help/moto-g-xt1068-aka-moto-g-2nd-generation-t3435052​
There is a risk that this won't work and your phone will never turn on again.
If you prefer, you could just flash a custom Stock MM ROM (if available) or CM/AOSP ROM via TWRP.
Click to expand...
Click to collapse
I've tried this method.
After a backup of all partitions on another default XT1078, the restore process on my phone finished with error only on /system or /data (I don't remember well).
Then I've tried to boot, but it had boot loop, just blinking very fast the Warning screen of unlocked bootloader.
It didn't work. :/
The only working method was merging XT1068 and XT1078 ROMs. Now Wifi and Mobile Data are working.
Now I can't change this ROM. Lineage or the whole XT1078 stock can't be installed.
The problem was that I didn't realize I was applying a XT1068 ROM on a XT1078 phone.
As all partitions were changed by flashing gpt.bin, the correct gpt.bin of XT1078 can't be applied.

Any solution????

I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.

benjausen said:
I am afraid that there is no solution right now. You already permanently ****ed up your machine by flashing a wrong motoboot.img and GPT, that is, by not using a correct ROM file. You were careless, because mfastboot is a DANGEROUS tool that requires CARE and a wrong use of this tool can turn your Moto device into a fancy black paperweight. It has no security measures that prevent you from flashing a stock ROM for a wrong device, which is what you did by not making sure that you were using a correct (or at least compatible) firmware.
I am afraid that your device is now crippled for life unless you somehow can force the correct motoboot and GPT in your phone (impossible AFAIK) or you get a new Thea motherboard and replace the current one. You are very lucky that you can still boot it, because most people in your situation are left with a permanent hard brick. Can you get into fastboot and is your bad bootloader unlocked? If so, you can try installing TWRP and LineageOS for Titan (then the worst you risk is a soft brick) or leave the "stock" franken-ROM that "works".
IMO you should get a spare XT1078 motherboard, unlock it's bootloader (AND NEVER TOUCH IT AGAIN UNLESS OTHERWISE SPECIFIED), flash TWRP and IMMEDIATELY flash LineageOS+GApps so you never have to deal with stock ROMs and the dangers they carry when handled carelessly. With custom AOSP based ROMs and recoveries the worst thing you risk is a soft brick, which you can fix by reflashing a proper custom ROM in TWRP and/or wiping partitions. No recovery? You still have a working fastboot to flash another TWRP. Messing with /system is MUCH SAFER than messing with your bootloader.
I hope you have learned a lesson about the real risk of flashing smartphone firmwares without doing enough research first. It's no game, a wrong step and no more phone for you.
Click to expand...
Click to collapse
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?

peacehope said:
Nice answer, benjausen.
I've done a lot of things on more than 10 different mobile phone models, but for the first time I think there is no complete solution.
My only solution was using a mix of XT1068 and XT1078 Stock ROMs, flashing one component per time. The only bug is on screen rotation that is rotating to the wrong side. The rest is fine.
I'd like to install LineageOS, but flashing isn't being possible. It is giving error.
Only the way I mentioned was successful. Is there any manual way to flash components separated instead of using a .zip file?
Click to expand...
Click to collapse
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.

benjausen said:
I don't have a lot of advice for you, as a previous post states your options are pretty much limited. Try flashing individual .img files from a LineageOS ROM. Try downloading one for Titan and patching the images inside it.
Click to expand...
Click to collapse
I don't have now a LineageOS ROM to check, but if I'm not wrong, it doesn't have each separated file as Stock ROM. Am I wrong?
I've flashed many Stock ROMs manually file by file, but never with custom ROMs.
Can you please provide any link teaching this with custom ROMs? I really want to try this.
Maybe this can be a solution, and if it works we will help many people here.

Factory Image Moto Z2 Force (NASH) RETAIL

Here in Germany the latest patchlevel is august 2017.
BUILD: NPX26.122-68
Here ist the Factory Image for retail devices (reteu ist also flashable) --> THANK YOU "Rickk182440":
BUILD: NPXS26.122-68-1 - Patchlevel 09/2017
(File was removed on androidfilehost)
Update:
BUILD: NPXS26.122-68-2 - Patchlevel 10/2017
https://androidfilehost.com/?fid=673791459329059776
Update:
BUILD: NPXS26.122-68-4 - Patchlevel 11/2017
https://androidfilehost.com/?w=files&flid=227116

Great!!
Have you tried to root and/or install twrp?

No, my device ist not rooted and bootloader is closed. Fully stock.

Passerati said:
No, my device ist not rooted and bootloader is closed. Fully stock.
Click to expand...
Click to collapse
Thanx a lot! Downloaded!
I'm going to install TWRP+root+Xposed instead, I need them for my needs...
Could you post the exact flashing sequence you used and what flashing command executable?
Keep in touch, I think we are the only European with a Z2 here...
(Mine is a dual SIM -06 version from Germany too)

enetec said:
Thanx a lot! Downloaded!
I'm going to install TWRP+root+Xposed instead, I need them for my needs...
Could you post the exact flashing sequence you used and what flashing command executable?
Keep in touch, I think we are the only European with a Z2 here...
(Mine is a dual SIM -06 version from Germany too)
Click to expand...
Click to collapse
Here is the sequence, a little bit different because seamless updates functionality and two system partitions:
I flashed no gpt.bin!
*(fastboot flash bootloader bootloader.img) -> only when needed!
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
I hope, this helps.

Passerati said:
Here is the sequence, a little bit different because seamless updates functionality and two system partitions:
I flashed no gpt.bin!
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash system_b system_b.img_sparsechunk.3
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
I hope, this helps.
Click to expand...
Click to collapse
Thank you, it helps A LOT!
I agree about not flashing gpt...
I would have some doubt about bootloader too... did you see if it upgrades bootloader version?
(On old Griffin it was a problem...)
So, you used normal fastboot and not mfastboot as many hint to... interesting..!

enetec said:
Thank you, it helps A LOT!
I agree about not flashing gpt...
I would have some doubt about bootloader too... did you see if it upgrades bootloader version?
(On old Griffin it was a problem...)
So, you used normal fastboot and not mfastboot as many hint to... interesting..!
Click to expand...
Click to collapse
Sorry, I don´t noticed the version before...You can try without the bootloader.bin and start with HLOS.bin.
And YES, i used fastboot from actual plattform-tools and no mfastboot without errors.

either AFH is down or i just cant access the file. ------ works now
Should this also work for U.S.?
Edit: It does flash to the TMO U.S. version but no radio.

ac1dx said:
either AFH is down or i just cant access the file. ------ works now
Should this also work for U.S.?
Edit: It does flash to the TMO U.S. version but no radio.
Click to expand...
Click to collapse
What does software channel say under settings > about phone ?

themustached said:
What does software channel say under settings > about phone ?
Click to expand...
Click to collapse
I didnt check that however, i did have the correct APN's automatically loaded.
Right now im back on TMO software.

ac1dx said:
I didnt check that however, i did have the correct APN's automatically loaded.
Right now im back on TMO software.
Click to expand...
Click to collapse
Oh, okay. Well since you were able to go to that and flash back I'll try that.

themustached said:
Oh, okay. Well since you were able to go to that and flash back I'll try that.
Click to expand...
Click to collapse
I'd like to see it work because its nice having a true aosp feel. none of the tmo crap even if you remove oem.img from tmo, it doesnt feel right.

ac1dx said:
I'd like to see it work because its nice having a true aosp feel. none of the tmo crap even if you remove oem.img from tmo, it doesnt feel right.
Click to expand...
Click to collapse
Not exactly sure, but I wonder if you flash that and then take and flash the modem from tmo if it'll work. I'll try and let you know.

themustached said:
Not exactly sure, but I wonder if you flash that and then take and flash the modem from tmo if it'll work. I'll try and let you know.
Click to expand...
Click to collapse
I would imagine swapping out the NON_HLOS file would work....??

ac1dx said:
I would imagine swapping out the NON_HLOS file would work....??
Click to expand...
Click to collapse
possibly, not 100% for sure

themustached said:
possibly, not 100% for sure
Click to expand...
Click to collapse
It worked. Just replace that file

ac1dx said:
I would imagine swapping out the NON_HLOS file would work....??
Click to expand...
Click to collapse
Where did you get the TMO radio from? Did you just pull it from the stock flash.bat file?

Amd4life said:
Where did you get the TMO radio from? Did you just pull it from the stock flash.bat file?
Click to expand...
Click to collapse
yes

For those wondering, this will not work with sprint model unless you keep the oem.img from the sprint bat zip. Their provisioning apk is in the oem partition.

ac1dx said:
Should this also work for U.S.?
Edit: It does flash to the TMO U.S. version but no radio.
Click to expand...
Click to collapse
Have you tried to flash it without baseband?
Can someone report what baseband version is reported after update?