Database Develop

How to flash the FXZ file via fastboot?

Hello everyone, I have a favor to ask for.
I want o flash rogers rom on my PR Moto X but the crappy moto software can't recognize my phone.
I can't use rsd at all so I want to do it via fastboot.
Can you tell me how to do this with commands? Which parts do I need to flash?
like: fastboot flash system system.img and so on
But I need a full script of this, please help! Deadly need the update for the camera!
Thanks in advance!

chrisjenho said:
Hello everyone, I have a favor to ask for.
I want o flash rogers rom on my PR Moto X but the crappy moto software can't recognize my phone.
I can't use rsd at all so I want to do it via fastboot.
Can you tell me how to do this with commands? Which parts do I need to flash?
like: fastboot flash system system.img and so on
But I need a full script of this, please help! Deadly need the update for the camera!
Thanks in advance!
Click to expand...
Click to collapse
if your phone is not recognized for rsd purposes then you probably should be trying to flash anything through fastboot. Rsd uses fastboot to flash your system so if RSD is not recognizing the device then fastboot won't recognize the device either. If you don't have the most up to date drivers then you most likely will run into problems when trying to flash any images using fastboot.
Download moto device manager. plug the phone into the computer with the cable you got when buying the phone. Make sure it is on MTP (the mass media option). To do this after you plug the phone in you can pull down the notification bar and it will have what type of usb connection you are using right there. To change just click on it and select mtp. Nopen up moto device manager and it should download some stuff for your phone. Next time you plug your phone in you should see a webpage pop up and a little moto icon in the bottom right tool bar on your computer.

jayboyyyy said:
if your phone is not recognized for rsd purposes then you probably should be trying to flash anything through fastboot. Rsd uses fastboot to flash your system so if RSD is not recognizing the device then fastboot won't recognize the device either. If you don't have the most up to date drivers then you most likely will run into problems when trying to flash any images using fastboot.
Download moto device manager. plug the phone into the computer with the cable you got when buying the phone. Make sure it is on MTP (the mass media option). To do this after you plug the phone in you can pull down the notification bar and it will have what type of usb connection you are using right there. To change just click on it and select mtp. Nopen up moto device manager and it should download some stuff for your phone. Next time you plug your phone in you should see a webpage pop up and a little moto icon in the bottom right tool bar on your computer.
Click to expand...
Click to collapse
Thanks buddy. Actually fastboot works but RSD doesn't. I made it on fastboot.
For these guys have the same problem with me.
Script use in command,
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
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

chrisjenho said:
Thanks buddy. Actually fastboot works but RSD doesn't. I made it on fastboot.
For these guys have the same problem with me.
Script use in command,
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
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
Click to expand...
Click to collapse
I tried this on my VZW dev edition but it wouldn't let me flash system.img

alex94kumar said:
I tried this on my VZW dev edition but it wouldn't let me flash system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2489249

[Q] Clarification on OTA bug fix update for Pure Edition

I have read the threads on the latest OTA update for the Pure Edition and I am confused on how to proceed. I am running System Version 22.11.6 Build Number LXE22.39.-6 and have got an OTA for 22.21.11.en.US, but it has failed of course. I am rooted with CF-Auto Root, the version from the middle of November, and have stock recovery.
What I am seeking to do is update to 22.21.11.en.US and not lose my apps or data.
What is the correct procedure for updating? Thanks Guys!!

I was on the first soak test build for lollipop and when the .6 build came out (the one that your on) I couldn't update unless I downgraded to 4.4.4 then re upgraded to lollipop OTA but it took a day for the OTA to show on my phone .....im pretty sure you have to do the same from .6 to .11 so https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images follow the steps on Motorola's website here really simple process just a few commands, but it will wipe your device

Since you're rooted, just run Titanium backup, return to 4.4.4, then apply .6 update and .11 update. (The .11 we have so far is only a delta from .6 -- not the full OTA)
edit: Apparently the full kitkat->lollipop .11 OTA is out there... hooray!

Do not use the instructions on Motorola factory images website
That website is missing a subtle command, that will make your OTA fail. I had that problem.
This line is missing.
fastboot flash modem NON-HLOS.bin
The OTA checks for the integrity of the modem and fails otherwise.
---------- Post added at 12:40 PM ---------- Previous post was at 12:31 PM ----------
Matthewlawson3 said:
What I am seeking to do is update to 22.21.11.en.US and not lose my apps or data.
Click to expand...
Click to collapse
You can try ADB backup for backing up all your apps and restore after OTA. This way the restore process works even after unrooting.

nimper said:
Since you're rooted, just run Titanium backup, return to 4.4.4, then apply .6 update and .11 update. (The .11 we have so far is only a delta from .6 -- not the full OTA)
edit: Apparently the full kitkat->lollipop .11 OTA is out there... hooray!
Click to expand...
Click to collapse
Android.is.better94 said:
I was on the first soak test build for lollipop and when the .6 build came out (the one that your on) I couldn't update unless I downgraded to 4.4.4 then re upgraded to lollipop OTA but it took a day for the OTA to show on my phone .....im pretty sure you have to do the same from .6 to .11 so https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images follow the steps on Motorola's website here really simple process just a few commands, but it will wipe your device
Click to expand...
Click to collapse
I was rooted on .6 and had to go to 4.4.4. I received the OTA to .11. It was a 576 MB or so update. So there are 2 update OTA depending on what version you are running.

Questions and Requests
bradley26 said:
I was rooted on .6 and had to go to 4.4.4. I received the OTA to .11. It was a 576 MB or so update. So there are 2 update OTA depending on what version you are running.
Click to expand...
Click to collapse
Ok. I have a few questions and requests.
First, this would be my first downgrade I have ever done, do I have to relock the bootloader and/or unroot first?
Second, what are the exact steps and commands in order to downgrade. I know you said they are Motorola's website, but just to be safe, and with the modem command added in, I would feel much better and be appreciative if someone provided that for me.
Third, I am on the US pure edition, which version of 4.4.4. would I need to download from Motorola's website? I've forgotten which version it came with.
Fourth, I was never a soak tester and I am on .6. Why can't I do a direct upgrade to .11 such as what is discussed here?
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625

Another Approach?
And what about this approach to upgrading from .6. to .11? Could this work?
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074

Matthewlawson3 said:
Ok. I have a few questions and requests.
First, this would be my first downgrade I have ever done, do I have to relock the bootloader and/or unroot first?
Second, what are the exact steps and commands in order to downgrade. I know you said they are Motorola's website, but just to be safe, and with the modem command added in, I would feel much better and be appreciative if someone provided that for me.
Third, I am on the US pure edition, which version of 4.4.4. would I need to download from Motorola's website? I've forgotten which version it came with.
Fourth, I was never a soak tester and I am on .6. Why can't I do a direct upgrade to .11 such as what is discussed here?
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
For whatever reason you can never have been rooted to update your ROM. So i followed the steps below to get back to stock for the update.
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
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
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
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.

bradley26 said:
For whatever reason you can never have been rooted to update your ROM. So i followed the steps below to get back to stock for the update.
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
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
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
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.
Click to expand...
Click to collapse
@Matthewlawson3
you can't downgrade the bootloader so omit that step. it won't make the OTA fail.
i'd recommend erasing userdata and cache.
once you do this, you should get the official full OTA that you can check for in the settings menu and apply. good luck.

mrvirginia said:
@Matthewlawson3
you can't downgrade the bootloader so omit that step. it won't make the OTA fail.
i'd recommend erasing userdata and cache.
once you do this, you should get the official full OTA that you can check for in the settings menu and apply. good luck.
Click to expand...
Click to collapse
So motoboot.img is the bootloader? That is the command you don't want me to enter?
I need to type in all the commands in that exact sequence, correct? Where does one enter the fastboot flash modem NON-HLOS.bin in the sequence of commands?
I would prefer not to lose my apps and data if it can be avoided. I do have Titanium Backup and could if need be, but what are the downsides to not erasing usercache and cache?
Thanks for your help on this!!!

Motorola Fastboot
I've never used the Motorola Fastboot utility. How does one acquire it and how do you set it up? I've only use the Android fastboot in the platform-tools folder.
Also, which build of 4.4.4. do I choose from on graffinxnyc's website? 4.4.4 Build: KXE21.187-42 Full Restore Images?

Matthewlawson3 said:
I've never used the Motorola Fastboot utility. How does one acquire it and how do you set it up? I've only use the Android fastboot in the platform-tools folder.
Also, which build of 4.4.4. do I choose from on graffinxnyc's website? 4.4.4 Build: KXE21.187-42 Full Restore Images?
Click to expand...
Click to collapse
fastboot flash partition gpt.bin
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
I got the images from motos site. had everything I needed.
not sure what, if any, errors you'd see due to not erasing userdata/cache

mrvirginia said:
fastboot flash partition gpt.bin
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
I got the images from motos site. had everything I needed.
not sure what, if any, errors you'd see due to not erasing userdata/cache
Click to expand...
Click to collapse
I have got the image for 4.4.4 (TMO_21.21.42.victara_tmo.tmo.en.US) from Motorola for the US Pure Edition, through the request process. Can I run these commands using regular fastboot from the android SDK platform-tools folder or must I use fastboot found in the Motorola 4.4.4 image? If I must use Motorola fastboot, what is the process for getting that setup before I go into a command prompt and enter the commands?
If I use the Motorola fastboot can I just copy the needed files into the Windows folder found in the Motorola image folder and then open a command prompt there to enter the commands? Is it that easy? I do not have a mfastboot file in the Windows folder in the image.

Matthewlawson3 said:
I have got the image for 4.4.4 (TMO_21.21.42.victara_tmo.tmo.en.US) from Motorola for the US Pure Edition, through the request process. Can I run these commands using regular fastboot from the android SDK platform-tools folder or must I use fastboot found in the Motorola 4.4.4 image? If I must use Motorola fastboot, what is the process for getting that setup before I go into a command prompt and enter the commands?
If I use the Motorola fastboot can I just copy the needed files into the Windows folder found in the Motorola image folder and then open a command prompt there to enter the commands? Is it that easy? I do not have a mfastboot file in the Windows folder in the image.
Click to expand...
Click to collapse
After doing some research, I have placed the fastboot.exe from the Motorola image in the Android-SDK platform-tools folder, but before I placed it in there, I renamed it mfastboot.exe, so as not to clash with the android fastboot.exe. When I type in the command prompt "mfastboot," I get a list of commands. Does this indicate everything is working correctly? And if so, when I type in the commands to perform the downgrade will I type in "mfastboot" instead of "fastboot" with every command?

Matthewlawson3 said:
After doing some research, I have placed the fastboot.exe from the Motorola image in the Android-SDK platform-tools folder, but before I placed it in there, I renamed it mfastboot.exe, so as not to clash with the android fastboot.exe. When I type in the command prompt "mfastboot," I get a list of commands. Does this indicate everything is working correctly? And if so, when I type in the commands to perform the downgrade will I type in "mfastboot" instead of "fastboot" with every command?
Click to expand...
Click to collapse
yes and yes

Ok. Thanks! One last question regarding the commands. After I flash partition gpt.bin, I am suppose to reboot from fastboot back to fastboot (reboot-bootloader) before continuing the commands..correct?

[HELP] Moto X bricked. How to unbrick it?

let me explain what exactly happened. l was running LiquidSmooth v3.2 on my Moto X. I have flashed few roms previously as well. I was facing no issues whatsoever but still wanted to upgrade to LiquidSmooth v4.0. So this time when I got on fastboot menu
and chose recovery, I got invalid kernel/ ramdisk size error. I was not able to enter recovery menu and this has happened to me for the first time. I chose normal reboot and then even the phone was working fine. But now, things have gone worse. I entered fastboot menu again and by mistake chose factory option instead of recovery. Phone started rebooting i think. As i had installed LiveLog app on my phone all I could see was logs on the screen. I waited for around 45 minutes but phone didnt boot up. I switched off and restarted again but same result. I think it is bricked. Is there any way I can get my phone back to working state? Any kind of help would be appreciated.
Thanks.

Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy

crazyworm said:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
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
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
Click to expand...
Click to collapse
you can def do that but if you want to try to bring it back to life without going to stock you can try this.
Flash your custom recovery again threw fastboot. then after that if you can boot into it just reinstall LS rom and try and boot your phone up if no luck then just follow the above guide from my thread and return to stock and redo everything

Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app

d1nesh said:
Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Yes Root Romoved, don't use last command "fastboot oem lock" if you want bootloader still unlocked

Sound advice above... Except there's no reason to lock your bootloader again. I'd skip that part. And remain unlocked. ?

Thanks a lot. I will try this method today and then flash LiquidSmooth v4.0. Just in case if I face any problem, I'll be back.
Sent from my GT-S5360 using xda app-developers app

I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app

d1nesh said:
I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
what carrier is your phone from i will try and find a good like for the stock firmware.
but like i said i would try to just flash the custom recovery and see if you can boot into it. if you can you might not have to go back to completely stock from the recovery you can iinstall liquid smooth rom. it has its own kernel so it should fix the kernel issue and system issues. if not then you can go back to flashing everything to stock.

It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Also, can you please guide me through the steps so that I do not make any mistakes this time. I'm really scared this time and I don't wanna hard brick my phone. I'd be really very thankful.
Sent from my GT-S5360 using xda app-developers app

Thank you for your help, guys.
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA

d1nesh said:
It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Click to expand...
Click to collapse
No. USB Debugging does not need to be on when using RSDLite or mFastboot.
d1nesh said:
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA
Click to expand...
Click to collapse
At this point, I would consider redoing the steps outlined by @dray_jr earlier in this thread.. with a few tweaks...
its important to be using the correct ROM for your phone. Is there fine print on the back of your phone, does it say XT1052? If so, the link to the Asia XT1052 4.4.4 rom should be correct.
Next... use mfastboot for ALL parts, not just system.img, and follow these steps.. Yes, the are very similar to what you did already, and yes, i know some are repeated, that is intentional.
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
OPTIONAL, but in your case might be necessary: just before the final mfastboot reboot command, issue... mfastboot erase userdata this will erase your apps and data.
If any of these commands fail, please make sure you capture it and post it. (NOTE: there is a way to select and copy on the text from the CMD Prompt window, please do that, rather than screen shot)
Once your phone boots up properly, it will be back to stock, unrooted, but as long as you don't do the "oem lock" command with mfastboot or fastboot, your bootloader will remain unlocked. You can then flash TWRP or other custom recovery and re-root.

[Q] [URGENT] Moto G 2nd Gen XT-1068 failed to validate system image

i had tried to lock boot-loader and now itz stuck in fastboot and saying failed to validate system image . Some please help me with what i have to do next

Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your specific device forum here (bookmark/subscribe this):
Moto G (2014)
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
G 2014 Q&A, Help & Troubleshooting
Good luck!

Did you UNLOCK your bootloader before?
If yes then again UNLOCK it again by connecting your phone to PC, enter into fastboot mode and type "fastboot oem unlock" in the cmd window.

what if the phone is not connecting to ur computer???
SharkcpN said:
Did you UNLOCK your bootloader before?
If yes then again UNLOCK it again by connecting your phone to PC, enter into fastboot mode and type "fastboot oem unlock" in the cmd window.
Click to expand...
Click to collapse
what if the phone is not connecting to ur comp???

Motorola G2 stuck in boot loop solution
rajdeepjadeja3 said:
Same problem..... Failed to validate system image...what to do now?? somebody please help...fast......
Click to expand...
Click to collapse
I have solution.... i had same problem... and searched it now my moto G2 is running successfully..... 1st You have to download stock firmware (official may be)...after that you have to install via fastboot with ADB codes....
follow instruction=========>>>>>
1. Extract the downloaded firmware file to a folder.
2. Download and extract mfastboot and copy its content to the same folder where the extracted firmware files.
3. Reboot your Moto G into the Bootloader Mode. To do so, turn off your phone and then press and hold the Volume (-) and Power buttons simultaneously for a few seconds.
4. Connect your phone to your PC via USB cable.
5. Now, launch a command window from inside the firmware folder (click shift key, right click and select open command window here option).
6. In the command window, issue the following commands one by one:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
NOTE: If firmware includes four system.img_sparsechunk or you do not want to erase the userdata, you can modify the command. You have now successfully installed a fresh ROM on your Moto G and the phone the phone should work as usual.
Also, depending on which version you are going to and from, you may need to try using the standard fastboot rather than mfastboot.
that's it... Enjoy...... (suggesting to download 5.0.2)

Same issue for Moto g 2nd Gen XT-1079 failed to validate system image
I also having same problem and I had done all the u have included above but still I am not able over come that plzz hlep to out

Managed to screw up phone, but bootloader still works.... what to do??

Okay, guys...
I have a big, big, big issue and If it's possible, I'd like all the help in the world.
I unlocked my bootloader, upgraded to mm 6.0 and decided to root and install TWRP because bloatware, right?
Anyways, I did a big no-no and after a series of unfortunate events, I don't have a recovery and I can only boot into the bootloader.
Don't ask HOW I got here, I couldn't tell you with a gun to my forehead.
Now, I have tried ways to get myself out of this:
Installed an earlier TWRP recovery - doesn't work
Installed CM recovery - Doesn't work
Looked on motorola.ca for stock images - doesn't work
I can boot my phone with TWRP but I can't install it. (the inapropriate partition size error in pink)
whatever. Whenever I boot into twrp, I see all my partitions and with modifications on, I cannot format my /sdcard/ partition (internal memory)
it was being detected by my pc a few times and after a few more tries to flash ANY rom compatible with my phone, I simply have no luck.
Any advice right now is more than appreciated!
Awaiting answers with impatience.
EDIT: Forgot to mention the model number is the XT1097 canadian Moto X 2014 (Telus mobility)
Thanks for the help in advance

Have you tried this? Put ROM/gapps on internal storage. Fastboot boot twrp, then flash ROM/gapps with twrp. Once booted you should be able to install twrp via playstore without the partition mismatch issue. I had to go this route to get twrp to stick on my XT1096

I cannot access the internal memory for some reason!
I hear my pc make a sound for connected but it doesn't show up in explorer

Have you tried ADB sideload? Try flashing the stock MM Rom Zip located in the Moto X 2014 XDA Thread. It might work, if it doesn't, I can send you a toolkit that might fix the phone.

I did try to sideload and I get the following:
Installation failed: unable to mount (all the partitions are listed)
E: Failed to mount
E: Can't mount
And if you're talking about RDS Lite, I am completely unable to find my phone with it.

What I really need is a tool that will fix the partition table.
I don't know how, but I messed it up REAL GOOD!

also, for some reason I Have 2 recoveries atm.
When I completely power off my phone and then power on, I boot into the CyanogenMod Recovery.
THEN, when I reboot into recovery, I go into the TWRP recovery.
And every time afterwards I Reboot to recovery, I come back to the TWRP

Install Motorola USB Drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download and keep full firmware VICTARA_RETCA_XT1097_6.0
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
If you are able to flash with fastboot, maybe you can go back to stock, then go on from there.
Try these, one by one:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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

I know you wouldn't, but hope you do. But if you could tell me how you got here, I could assist you better.

Thank you, Mate!
This restored my phone to retail!
I am in your debt!

You're welcome. We are all here to help each other.

Hi, I am in the exact same situation right now. I tried the fastboot method to flash all the files for the XT1096 VZW version. Every time I boot up after flashing everything, the dead andy with read exclamation point 'No Command' logo pops up and blinks every 5 seconds or so. Any help please? Thanks!

So I managed to get TWRP to install. Now I can't flash anything. All the partitions are somehow corrupted and I can't mount anything. Any ideas on how to fix the partitions?

OK

My apologies, Gus. I just posted a new QA thread on here. Can we discuss there? Thanks.