I was having some issues with my phone, so I followed the instructions to unroot and re-lock my bootloader. Everything seemed to work fine. I restored from 4.4.2 to 4.4 and then took an OTA back to 4.4.2. Now when I try to flash anything in fastboot or mfastboot, I get the following error:
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load ' ': No error
The phone reports:
getvar max-sparse-size
getvar max-download-size
My phone reports the bootloader is unlocked. Status Code: 3
The phone works fine and I've had no issues installing or configuring.
I've searched through the posts and googled the hell out of the error, but I haven't found an explanation or a fix. Can anyone tell me how to fix this issue?
Morrolan said:
I was having some issues with my phone, so I followed the instructions to unroot and re-lock my bootloader. Everything seemed to work fine. I restored from 4.4.2 to 4.4 and then took an OTA back to 4.4.2. Now when I try to flash anything in fastboot or mfastboot, I get the following error:
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load ' ': No error
The phone reports:
getvar max-sparse-size
getvar max-download-size
My phone reports the bootloader is unlocked. Status Code: 3
The phone works fine and I've had no issues installing or configuring.
I've searched through the posts and googled the hell out of the error, but I haven't found an explanation or a fix. Can anyone tell me how to fix this issue?
Click to expand...
Click to collapse
Too bad you didn't read the many many warnings here that you will BRICK your phone if you downgrade once on 4.4.2....
It is literally everywhere on this forum.
Hope you are able to find a solution.
Good luck
samwathegreat said:
Too bad you didn't read the many many warnings here that you will BRICK your phone if you downgrade once on 4.4.2....
It is literally everywhere on this forum.
Hope you are able to find a solution.
Good luck
Click to expand...
Click to collapse
It's funny that you say that, because there are just as many posts with guides on how to do it. Luckily, my phone is not bricked. But I would love one of the geniuses here to explain why it's happening and if and how I can fix it.
Morrolan said:
It's funny that you say that, because there are just as many posts with guides on how to do it. Luckily, my phone is not bricked. But I would love one of the geniuses here to explain why it's happening and if and how I can fix it.
Click to expand...
Click to collapse
Could you please link the guide that told you how to do this?
The only version you can downgrade is from 4.4 to the 4.2.2 POST-Camera-Fix update.
See here:
http://forum.xda-developers.com/moto-x/general/4-4-2-update-t2625303/page26
and here:
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
and here:
http://forum.xda-developers.com/moto-x/moto-x-qa/4-4-2-unlocked-downgrade-t2682613
and here:
http://forum.xda-developers.com/moto-x/moto-x-qa/warning-4-4-2-downgraded-t2658742
and there are many, many, many more. Just for the sake of not linking dozens of posts, I feel that those will suffice...
Some have been semi-successful on downgrading by flashing everything except GPT.bin, but this means you will have mismatched versions on your phone, which will result in a hard-brick once a new OTA comes out.
Even if you are fine now, the next OTA you accept will brick your phone.
samwathegreat said:
Could you please link the guide that told you how to do this?
The only version you can downgrade is from 4.4 to the 4.2.2 POST-Camera-Fix update.
See here:
http://forum.xda-developers.com/moto-x/general/4-4-2-update-t2625303/page26
and here:
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
and here:
http://forum.xda-developers.com/moto-x/moto-x-qa/4-4-2-unlocked-downgrade-t2682613
and here:
http://forum.xda-developers.com/moto-x/moto-x-qa/warning-4-4-2-downgraded-t2658742
and there are many, many, many more. Just for the sake of not linking dozens of posts, I feel that those will suffice...
Some have been semi-successful on downgrading by flashing everything except GPT.bin, but this means you will have mismatched versions on your phone, which will result in a hard-brick once a new OTA comes out.
Even if you are fine now, the next OTA you accept will brick your phone.
Click to expand...
Click to collapse
I linked to them via Google search, so it's a hassle. I did see the warnings after this downgrade, which was unintentional. Mislabeled file that I didn't check.
Kinda weird it didn't brick when I did the OTA for 4.4.2.
I appreciate you telling what the issue is. Is there no way to fix the mismatch?
You can probably use RSD Lite and the correct firmware to fix your phone. RSD the proper 4.4.2 and you'll be fine. After i took the 4.4.2 OTA when it first came out I tried to RSD back to 4.4 just to see if it would work and of course it didn't. I just rebooted the bootloader, fastbooted TWRP in, wiped everything. Cache's, data, system, internal storage and RSD'd the proper 4.4.2.
Phone will be restored and no issues.
Since you have a developer edition it will be hard to brick your phone. You can always use Team Blackhats factory cable adapter to get your phone into bootloader also.
Morrolan said:
I linked to them via Google search, so it's a hassle. I did see the warnings after this downgrade, which was unintentional. Mislabeled file that I didn't check.
Kinda weird it didn't brick when I did the OTA for 4.4.2.
I appreciate you telling what the issue is. Is there no way to fix the mismatch?
Click to expand...
Click to collapse
There is one possibility to get you back on track.
Find the "Return to Stock" thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
We are going to use the "manual method"
Do NOT use RSD Lite, and follow MY instructions:
FIRST, before you follow the return to stock thread, boot the device into bootloader.
You will need the entire stock 4.4.2 SBF File for your carrier from here: http://sbf.droid-developers.org/phone.php?device=0
Now unzip the file into the same folder that fastboot and mfastboot are located.
FIRST, execute these commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
now reboot into bootloader:
mfastboot reboot-bootloader
now run these commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
(Yes, we just did these again - it is intentional)
NOW, execute all the commands listed in the "Return to Stock" thread.
If you don't get errors, then you are in good shape.
EXPLAINATION:
gpt.bin is "GUID Partition Table"
what we are doing is JUST flashing the partition table, and bootloader, then allowing the phone to reboot into bootloader to LOAD the new partition table BEFORE we write the rest of the partitions. It has worked for some.
Please let us know if it works for you....
samwathegreat said:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
C:\Android-SDK>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'gpt.bin': No error
C:\Android-SDK>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'motoboot.img': No error
Phone
getvar max-sparse-size
getvar max-download-size
getvar max-sparse-size
getvar max-download-size
samwathegreat said:
now reboot into bootloader:
mfastboot reboot-bootloader
Click to expand...
Click to collapse
Works
samwathegreat said:
now run these commands:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
(Yes, we just did these again - it is intentional)
Click to expand...
Click to collapse
C:\Android-SDK>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'gpt.bin': No error
C:\Android-SDK>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'motoboot.img': No error
now reboot into bootloader:
Phone
getvar max-sparse-size
getvar max-download-size
getvar max-sparse-size
getvar max-download-size
I'm assuming this means I'm most likely screwed? When does the Moto X+1 come out?
Morrolan said:
C:\Android-SDK>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'gpt.bin': No error
C:\Android-SDK>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'motoboot.img': No error
Phone
getvar max-sparse-size
getvar max-download-size
getvar max-sparse-size
getvar max-download-size
Works
C:\Android-SDK>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'gpt.bin': No error
C:\Android-SDK>mfastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'motoboot.img': No error
now reboot into bootloader:
Phone
getvar max-sparse-size
getvar max-download-size
getvar max-sparse-size
getvar max-download-size
I'm assuming this means I'm most likely screwed? When does the Moto X+1 come out?
Click to expand...
Click to collapse
error: cannot load XXX
usually means that the files are not in the same folder as fastboot/mfastboot.
Make sure that all of the files are in the same folder as fastboot/mfastbot, and not inside another folder.
please show me a directory listing of the files inside C:\Android-SDK\
it should have fastboot, mfastboot, gpt.bin, motoboot.img, system.img, etc. etc. all inside the same folder....
(Sorry if this is redundant, just trying to cover all bases...)
samwathegreat said:
error: cannot load XXX
usually means that the files are not in the same folder as fastboot/mfastboot.
Make sure that all of the files are in the same folder as fastboot/mfastbot, and not inside another folder.
please show me a directory listing of the files inside C:\Android-SDK\
it should have fastboot, mfastboot, gpt.bin, motoboot.img, system.img, etc. etc. all inside the same folder....
(Sorry if this is redundant, just trying to cover all bases...)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've deleted and created a new folder. Maybe it's picking up old files. Here is the new folder.
Morrolan said:
View attachment 2838765
I've deleted and created a new folder. Maybe it's picking up old files. Here is the new folder.
Click to expand...
Click to collapse
OK, great. According to that image, everything is in C:\Android-SDK\Platform-Tools\
now if you open a command prompt:
C:\
cd Android-SDK
C:\Android-SDK\
cd Platform-Tools
C:\Android-SDK\Platform-Tools\
mfastboot flash............etc.
Any success now?
samwathegreat said:
OK, great. According to that image, everything is in C:\Android-SDK\Platform-Tools\
now if you open a command prompt:
C:\
cd Android-SDK
C:\Android-SDK\
cd Platform-Tools
C:\Android-SDK\Platform-Tools\
mfastboot flash............etc.
Any success now?
Click to expand...
Click to collapse
SUCCESS! Thank you for your perseverance! I think I had a couple of additional files in the previous folder. I'm showing 4.4.2 and no ill effects that I can see. I suppose it's ok to root now and be on my way.:good:
Morrolan said:
SUCCESS! Thank you for your perseverance! I think I had a couple of additional files in the previous folder. I'm showing 4.4.2 and no ill effects that I can see. I suppose it's ok to root now and be on my way.:good:
Click to expand...
Click to collapse
Fantastic! Congrats, glad it all worked out for you.
Now that you no longer have a mismatched gpt.bin / bootloader you should be safe for future updates.
You are all set to root and have fun.
My only suggestion is in the future, please don't use google search or youtube for flashing tutorials - these get alot of people in trouble, and we spend a great deal of time fixing these issues. Please always come to XDA for tutorials and instructions to make sure you aren't at risk of bricking. This could have been much worse (good thing the 4.4.3 / 4.4.4 OTA hasn't been released yet...)
samwathegreat said:
Fantastic! Congrats, glad it all worked out for you.
Now that you no longer have a mismatched gpt.bin / bootloader you should be safe for future updates.
You are all set to root and have fun.
My only suggestion is in the future, please don't use google search or youtube for flashing tutorials - these get alot of people in trouble, and we spend a great deal of time fixing these issues. Please always come to XDA for tutorials and instructions to make sure you aren't at risk of bricking. This could have been much worse (good thing the 4.4.3 / 4.4.4 OTA hasn't been released yet...)
Click to expand...
Click to collapse
Yes, sir! I made a huge mistake downloading a file from outside XDA that caused the problem. That and my dumb self not checking the file first. Hopefully, 4.4.4 will be an easy upgrade and then on to L. I really appreciate it!
rebretz000 said:
...Since you have a developer edition it will be hard to brick your phone. You can always use Team Blackhats factory cable adapter to get your phone into bootloader also.
Click to expand...
Click to collapse
Bricking a DEV Edition is just as easy as bricking a Moto Maker or Retail X.
But Yes, the Team Blackhat Moto factory adapter is a good thing to have.
Related
I have a vzw moto x and I'm looking to unroot. Unfortunately, I have a mac, so the RSDlite that works only with Windows will not install. I don't have access to any vmware or a windows disc, so my question is, is there any way to fully unroot using only mac software? Thanks!
You can use fastboot to flash the files instead of rsdlite.
Sent from my XT1058 using Tapatalk 4
jhnl33 said:
I have a vzw moto x and I'm looking to unroot. Unfortunately, I have a mac, so the RSDlite that works only with Windows will not install. I don't have access to any vmware or a windows disc, so my question is, is there any way to fully unroot using only mac software? Thanks!
Click to expand...
Click to collapse
I just tried that and could do everything except for `system.img`. Worked fine with the same files and everything using RSDLite. I am not sure why, but that was my experience.
jhnl33 said:
I have a vzw moto x and I'm looking to unroot. Unfortunately, I have a mac, so the RSDlite that works only with Windows will not install. I don't have access to any vmware or a windows disc, so my question is, is there any way to fully unroot using only mac software? Thanks!
Click to expand...
Click to collapse
Download the FXZ for whichever version you have (ATT, VZW, etc.) then just extract the recovery.img and system.img. fastboot flash the recovery.img and system.img. reboot and you should be able to then just do a standard factory reset and you'll be back to stock. worked for me at least. I did the factory reset for good measure but flashing the system may suffice.
SnowKing25 said:
Download the FXZ for whichever version you have (ATT, VZW, etc.) then just extract the recovery.img and system.img. fastboot flash the recovery.img and system.img. reboot and you should be able to then just do a standard factory reset and you'll be back to stock. worked for me at least. I did the factory reset for good measure but flashing the system may suffice.
Click to expand...
Click to collapse
I'm having trouble flashing system.img. Terminal tells me that "bootloader variable not supported", "invalid sparse file format at header magi" and then "bootloader prefllash validation failed" and then "FAILED (remote failure)."
What do I do? I don't want to risk getting stuck in boot loop so I just have it sitting in fastboot mode...
Well, I'm not terribly adept at this myself, but I would say make sure that you downloaded the proper version of the FXZ. Extract the files, and I would flash the boot.img first, then the system.img. Mine worked flawlessly. Make sure you have the most updated fastboot and and stuff?
Sent from my XT1058 using xda app-developers app
jhnl33 said:
I'm having trouble flashing system.img. Terminal tells me that "bootloader variable not supported", "invalid sparse file format at header magi" and then "bootloader prefllash validation failed" and then "FAILED (remote failure)."
What do I do? I don't want to risk getting stuck in boot loop so I just have it sitting in fastboot mode...
Click to expand...
Click to collapse
Sounds like you have the wrong FXZ or the files may be corrupt. Try downloading again.
Tried again, still get the same error. Have the latest fastboot and got the right vzw firmware...idk what's wrong
Sent from my XT1060 using Tapatalk
In the same boat as the OP.
jhnl33, did you get the FXZ from here: sbf.droid-developers(dot)org/ghost_rcica/list.php
A lot of people have suggested using mfastboot.exe instead of regular fastboot. The file is too big to flash the system.img. mfastboot breaks the file down for flashing. I'm on the phone otherwise I would add the link. This is what I used and it worked flawlessly.
Sent via my MOTO X Press
buyayo said:
In the same boat as the OP.
jhnl33, did you get the FXZ from here: sbf.droid-developers(dot)org/ghost_rcica/list.php
Click to expand...
Click to collapse
Yeah, that's were I got it. I'm fine now; I just borrowed a friends Windows computer and used RSDLite.
lilcdroid said:
A lot of people have suggested using mfastboot.exe instead of regular fastboot. The file is too big to flash the system.img. mfastboot breaks the file down for flashing. I'm on the phone otherwise I would add the link. This is what I used and it worked flawlessly.
Sent via my MOTO X Press
Click to expand...
Click to collapse
Yeah, unfortunately, mfastboot.exe is a windows only thing, as far as I know...
jhnl33 said:
Yeah, that's were I got it. I'm fine now; I just borrowed a friends Windows computer and used RSDLite.
Click to expand...
Click to collapse
Yeah, I've been in the same boat. Typically I wind up using my work computer which is running XP. Fortunately, I have install privileges and a good boss =)
FYI: I've used Linux scripts on my previous phone (Atrix 2) but I don't code much. So if you find, or someone develops, a Linux option it'll work on Mac.
Sent from my XT1058 using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=33228220
I believe the third post is the one for Linux.
Sent via my MOTO X Press
lilcdroid said:
http://forum.xda-developers.com/showthread.php?p=33228220
I believe the third post is the one for Linux.
Sent via my MOTO X Press
Click to expand...
Click to collapse
I'm in the same boat here- I only have a mac at home AND at work... No access to a windows machine without bothering a friend. I found the motofastboot osx32 and 64bit files but am kind of stumped as to how to execute those mfastboot over the usual fastboot I've been using this whole time. I've been able to flash everything back to stock but system.img because the file is too large, so if anyone can somehow explain to me how I can execute motofastboot commands using these files I'd really appreciate it, as it's really my only option to have the .img broken up and successfully installed.
Thanks!!!
Any update on this?
Same boat as OP.
---------- Post added at 08:49 AM ---------- Previous post was at 08:41 AM ----------
I tried using BHUNDVEN's [TOO] found in OG Android Dev but keep getting
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Traceback (most recent call last):
File "/usr/local/bin/moto-x-flash", line 24, in <module>
tree = ET.parse(firmware_xml)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 656, in parse
parser.feed(data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 1, column 2
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
Thanks for the help!
---------- Post added at 09:18 AM ---------- Previous post was at 08:49 AM ----------
Ok so I needed to rename the .xml file to a .zip file ... extract it. I put the contents into the "moto-x-tools" folder and then run the command and keep getting "command not found".
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Running: fastboot oem fb_mode_set
/bin/sh: fastboot: command not found
Running: fastboot flash partition gpt.bin
/bin/sh: fastboot: command not found
Running: fastboot flash motoboot motoboot.img
/bin/sh: fastboot: command not found
Running: fastboot flash logo logo.bin
/bin/sh: fastboot: command not found
Running: fastboot flash boot boot.img
/bin/sh: fastboot: command not found
Running: fastboot flash recovery recovery.img
/bin/sh: fastboot: command not found
Running: fastboot flash system system.img
/bin/sh: fastboot: command not found
Running: fastboot flash modem NON-HLOS.bin
/bin/sh: fastboot: command not found
Running: fastboot erase modemst1
/bin/sh: fastboot: command not found
Running: fastboot erase modemst2
/bin/sh: fastboot: command not found
Running: fastboot flash fsg fsg.mbn
/bin/sh: fastboot: command not found
Running: fastboot erase cache
/bin/sh: fastboot: command not found
Running: fastboot erase userdata
/bin/sh: fastboot: command not found
Running: fastboot erase customize
/bin/sh: fastboot: command not found
Running: fastboot erase clogo
/bin/sh: fastboot: command not found
Running: fastboot oem config carrier vzw
/bin/sh: fastboot: command not found
Running: fastboot oem fb_mode_clear
/bin/sh: fastboot: command not found
Flashing was successful!
Running: fastboot reboot
/bin/sh: fastboot: command not found
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
cscohammers7 said:
I'm in the same boat here- I only have a mac at home AND at work... No access to a windows machine without bothering a friend. I found the motofastboot osx32 and 64bit files but am kind of stumped as to how to execute those mfastboot over the usual fastboot I've been using this whole time. I've been able to flash everything back to stock but system.img because the file is too large, so if anyone can somehow explain to me how I can execute motofastboot commands using these files I'd really appreciate it, as it's really my only option to have the .img broken up and successfully installed.
Thanks!!!
Click to expand...
Click to collapse
I just got mine to flash system with the 64 bit on my MacBook Pro just renamed the moto-fastboot-osx64 to mfastboot and did the command: mfastboot flash system system.img and it worked like a charm! Unrooted and took the OTA no issues! Then I unlocked the bootloader since it no longer voids the warranty on the Dev Ed.
lilcdroid said:
http://forum.xda-developers.com/showthread.php?p=33228220
I believe the third post is the one for Linux.
Sent via my MOTO X Press
Click to expand...
Click to collapse
Tried to use the Linux one, but got an error, any help with how to get this to work?
Try snapdragon-fastboots
Try snapdragon-fastboots, from skeevydude post 21, but I was able to flash twrp-2.6.3.1-ghost-4.4.img in Linux Mint 13 on my Moto X dev using ... fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img and it gave me the option to flash root. I saw for Mac/Darwin also.
For anybody still wondering, here is a link to download the mfastboot files for mac 32 and 64bit
https://gist.github.com/crazed/7670423
Hey guys I'm mostly a lurker not too much of a poster I would respond to "BHUNDVEN"'s thread ([TOOL] Moto X FXZ Flashing Script (100% back to stock) [10/03/2013]) over on the OG Android development sections but alas my "Post count" is too low.
I keep getting this when trying to run the final command "moto-x-flash [insert .xml file]"
Any help? Thanks!
Last login: Thu Nov 7 00:31:17 on ttys001
jeffreys-mbp:~ jeffreymarshall$ cd desktop/moto-x-tools-0.2.0
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ sudo python setup.py install
running install
running build
running build_py
running build_scripts
running install_lib
running install_scripts
changing mode of /usr/local/bin/moto-x-flash to 755
running install_egg_info
Removing /Library/Python/2.7/site-packages/moto_x_tools-0.2.0-py2.7.egg-info
Writing /Library/Python/2.7/site-packages/moto_x_tools-0.2.0-py2.7.egg-info
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Traceback (most recent call last):
File "/usr/local/bin/moto-x-flash", line 24, in <module>
tree = ET.parse(firmware_xml)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 656, in parse
parser.feed(data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 1, column 2
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
I'm not to sure I have the python pkg installed correctly. Had to use the "sudo" command to get it to take.
AceBoonKoon said:
I'm not to sure I have the python pkg installed correctly. Had to use the "sudo" command to get it to take.
Click to expand...
Click to collapse
i cant help you with that toolkit as i don't use it. But if you are merely trying to flash your phone to stock then find the rsd back to 100% stock thread and do that. Just as simple as any other tool you can find.
But honestly, if you spent say 4 hours reading and installing things for adb/fastboot stuff, you won't ever need one of those tools and you won't ever again spend countless hours trying to figure out how to get some tool someone created to work correctly for your phone. The simple sometimes becomes the most time consuming.
Once you figure out a few commands and realize whats going on, you will understand how simple all of that stuff is, and then will be confused as to why anyone ever created a tool for that simple task. Not bashing on the people that created the toolkit, that helps hundreds of people out I'm sure that dont feel like reading a little bit.
memapp can
I would but this [TOOL] is for mac.
No windows machine ala no rsdlite. I did however see that I needed to rename the .xml file to a .zip file ... Then extract the contents and move them over to the moto-x-tools folder and tried flashing it that way but got a "Command not found" error.
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Running: fastboot oem fb_mode_set
/bin/sh: fastboot: command not found
Running: fastboot flash partition gpt.bin
/bin/sh: fastboot: command not found
Running: fastboot flash motoboot motoboot.img
/bin/sh: fastboot: command not found
Running: fastboot flash logo logo.bin
/bin/sh: fastboot: command not found
Running: fastboot flash boot boot.img
/bin/sh: fastboot: command not found
Running: fastboot flash recovery recovery.img
/bin/sh: fastboot: command not found
Running: fastboot flash system system.img
/bin/sh: fastboot: command not found
Running: fastboot flash modem NON-HLOS.bin
/bin/sh: fastboot: command not found
Running: fastboot erase modemst1
/bin/sh: fastboot: command not found
Running: fastboot erase modemst2
/bin/sh: fastboot: command not found
Running: fastboot flash fsg fsg.mbn
/bin/sh: fastboot: command not found
Running: fastboot erase cache
/bin/sh: fastboot: command not found
Running: fastboot erase userdata
/bin/sh: fastboot: command not found
Running: fastboot erase customize
/bin/sh: fastboot: command not found
Running: fastboot erase clogo
/bin/sh: fastboot: command not found
Running: fastboot oem config carrier vzw
/bin/sh: fastboot: command not found
Running: fastboot oem fb_mode_clear
/bin/sh: fastboot: command not found
Flashing was successful!
Running: fastboot reboot
/bin/sh: fastboot: command not found
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
jayboyyyy said:
i cant help you with that toolkit as i don't use it. But if you are merely trying to flash your phone to stock then find the rsd back to 100% stock thread and do that. Just as simple as any other tool you can find.
But honestly, if you spent say 4 hours reading and installing things for adb/fastboot stuff, you won't ever need one of those tools and you won't ever again spend countless hours trying to figure out how to get some tool someone created to work correctly for your phone. The simple sometimes becomes the most time consuming.
Once you figure out a few commands and realize whats going on, you will understand how simple all of that stuff is, and then will be confused as to why anyone ever created a tool for that simple task. Not bashing on the people that created the toolkit, that helps hundreds of people out I'm sure that dont feel like reading a little bit.
Click to expand...
Click to collapse
In response to the fastboot commands suggestion - I have already tried using the adb/fastboot methods didn't work. Did a search for people with similar issues and found that it has something about it being on a mac or some other nonsense. That's the reason for the [TOOL] I think. It's a workaround.
AceBoonKoon said:
In response to the fastboot commands suggestion - I have already tried using the adb/fastboot methods didn't work. Did a search for people with similar issues and found that it has something about it being on a mac or some other nonsense. That's the reason for the [TOOL] I think. It's a workaround.
Click to expand...
Click to collapse
don't know where you fastboot is but i believe its trying to call it and its not in the directory that the cmd is pointed to.
Ok I've went down the list and manually flashed each command.
When I get to ./fastboot flash system system.img
I keep getting this error
"Mismatched PIV partition name for system
Invalid PIV image: system"
I can successfully flash all other commands except this one. I went into the .xml file and deleted the "getvar" portion already. Any help?
AceBoonKoon said:
Ok I've went down the list and manually flashed each command.
When I get to ./fastboot flash system system.img
I keep getting this error
"Mismatched PIV partition name for system
Invalid PIV image: system"
I can successfully flash all other commands except this one. I went into the .xml file and deleted the "getvar" portion already. Any help?
Click to expand...
Click to collapse
not sure about the error sorry. also you might want to click on the reply button so it appears as a notification for me or i might not ever look at the thread again if i forget, jsut fyi.
are you sure you are using the right fxz for your phone? also when you run manual commands in fastboot, the xml file doesn't matter. that file is just there for rsd and other programs to use (it is basically just a script of commands that gets called on by programs to run). i don't know if you are typing "./fastboot" instead of just "fastboot" in cmd prompt but you only need to type "fastboot flash system system.img"
jayboyyyy said:
not sure about the error sorry. also you might want to click on the reply button so it appears as a notification for me or i might not ever look at the thread again if i forget, jsut fyi.
are you sure you are using the right fxz for your phone? also when you run manual commands in fastboot, the xml file doesn't matter. that file is just there for rsd and other programs to use (it is basically just a script of commands that gets called on by programs to run). i don't know if you are typing "./fastboot" instead of just "fastboot" in cmd prompt but you only need to type "fastboot flash system system.img"
Click to expand...
Click to collapse
Thanks for the fyi didn't know. I've tried flashing both fxz's for my phone and nothing both keep saying the same error Mismatched PIV. Thanks for the schooling on the xml file didn't know that. Going to keep searching.
AceBoonKoon said:
Thanks for the fyi didn't know. I've tried flashing both fxz's for my phone and nothing both keep saying the same error Mismatched PIV. Thanks for the schooling on the xml file didn't know that. Going to keep searching.
Click to expand...
Click to collapse
both? you can't just flash both like that. are you sure you are doing all of this right? one for your phone is a different FW version than the other one. This could be why you are getting this mismatch. Also, you would need to unzip and move all of the files to the directory that your fastboot is in. Then if you were trying to flash a different fxz, you would need to remove the old files from that directory and replace them with the new fxz files.
Finally, the commands to run manually will be found at this link. http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
jayboyyyy said:
both? you can't just flash both like that. are you sure you are doing all of this right? one for your phone is a different FW version than the other one. This could be why you are getting this mismatch. Also, you would need to unzip and move all of the files to the directory that your fastboot is in. Then if you were trying to flash a different fxz, you would need to remove the old files from that directory and replace them with the new fxz files.
Finally, the commands to run manually will be found at this link. http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
Click to expand...
Click to collapse
Now it's saying that can't downgrade when trying to flash the bootloader and it still won't flash the system.img same error.
I think I messed up when I tried to flash the "newer" FXZ. To see if I could get it to go through.
AceBoonKoon said:
I think I messed up when I tried to flash the "newer" FXZ. To see if I could get it to go through.
Click to expand...
Click to collapse
ya you can't flash the old one anymore. it will fail. you should be able to flash the new system img though. just make sure you are using the right one for your device. couldn't find anything on the internet for that particular error. So not many people run into it. It has to be something you are doing. try redownloading the fxz (the correct new fxz for your phone) and then start over from the beginning of the code and flash all the new stuff.
jayboyyyy said:
ya you can't flash the old one anymore. it will fail. you should be able to flash the new system img though. just make sure you are using the right one for your device. couldn't find anything on the internet for that particular error. So not many people run into it. It has to be something you are doing. try redownloading the fxz (the correct new fxz for your phone) and then start over from the beginning of the code and flash all the new stuff.
Click to expand...
Click to collapse
The fastboot flashes through every command flawlessly all EXCEPT the system.img. Keeps saying the bootloader preauthorization failed. I've flashed it every which way, straight through, at random, only the recovery, bootloader, and system.img. Can't get it to play nice.
I did read somewhere that mac fastboot had an issue with how large the system file was for VZW's moto x and couldn't flash it. Someone said that rsd lite breaks it up into smaller pieces in order to get it to flash. I wonder if there is a manual way to do this?
AceBoonKoon said:
The fastboot flashes through every command flawlessly all EXCEPT the system.img. Keeps saying the bootloader preauthorization failed. I've flashed it every which way, straight through, at random, only the recovery, bootloader, and system.img. Can't get it to play nice.
I did read somewhere that mac fastboot had an issue with how large the system file was for VZW's moto x and couldn't flash it. Someone said that rsd lite breaks it up into smaller pieces in order to get it to flash. I wonder if there is a manual way to do this?
Click to expand...
Click to collapse
forgot you were using a mac. just throw that thing away and get a big boy computer. lol. jk. don't need to start hearing a bunch of people chime in but here is a link to a fastboot file that splits it up for you. don't know if it will help or not.
http://forum.xda-developers.com/showthread.php?t=2489249
jayboyyyy said:
forgot you were using a mac. just throw that thing away and get a big boy computer. lol. jk. don't need to start hearing a bunch of people chime in but here is a link to a fastboot file that splits it up for you. don't know if it will help or not.
http://forum.xda-developers.com/showthread.php?t=2489249
Click to expand...
Click to collapse
I went and downloaded the "motofastboot-olympus" file and extracted the Linux fastboot file and placed in my folder replacing the current fastboot and now when I try to run a fastboot command I get "./fastboot: cannot execute binary file" I've tried the "Darwin" fastboot as well same thing.
AceBoonKoon said:
I went and downloaded the "motofastboot-olympus" file and extracted the Linux fastboot file and placed in my folder replacing the current fastboot and now when I try to run a fastboot command I get "./fastboot: cannot execute binary file" I've tried the "Darwin" fastboot as well same thing.
Click to expand...
Click to collapse
i see that you actually searched for this answer because i went to that mac thread i remembered seeing to see if there was a solution there. so you can just factory reset the device right? you don't need the system.img there to factory reset i don't think. just try a factory reset.
just found this. try downloading the nexus for stuff. pull the fastboot-mac file or whatever it is out of it. run all your commands with the "./fastboot-mac" and see if it works now.
jayboyyyy said:
i see that you actually searched for this answer because i went to that mac thread i remembered seeing to see if there was a solution there. so you can just factory reset the device right? you don't need the system.img there to factory reset i don't think. just try a factory reset.
Click to expand...
Click to collapse
I've been searching all day for all of these answers. Just thought it would help to ask as well.
I found the solution to my problem. For any of those who are having trouble flashing back to stock ON A MAC It will not flash because the system.img file is TOO BIG you need the CORRECT version of Moto-Fastboot. Here's the link that you can download and place it in your "Fastboot" folder. http://forum.xda-developers.com/showthread.php?t=1138092
I suggest you hold on to that fastboot for future flashes/return to stock. Thank you for your help jayboyyyy!
AceBoonKoon said:
I've been searching all day for all of these answers. Just thought it would help to ask as well.
I found the solution to my problem. For any of those who are having trouble flashing back to stock ON A MAC It will not flash because the system.img file is TOO BIG you need the CORRECT version of Moto-Fastboot. Here's the link that you can download and place it in your "Fastboot" folder. http://forum.xda-developers.com/showthread.php?t=1138092
I suggest you hold on to that fastboot for future flashes/return to stock. Thank you for your help jayboyyyy!
Click to expand...
Click to collapse
nice find. im going to update that thread i made with this link instead of the link i had because it seems to have fastboot for everyone.
I tried to manually flash back to stock 4.4.2 (so I can upgrade to 4.4.3) on my moto x but whenever I type the command "mfastboot flash system system.img" I get "invalid sparse image chunk count. The rest of the commands worked. Now my phone is stuck in the unlocked bootloader screen and I don't know what else to do. Help please?
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
serophia said:
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Where would I get the latest version?
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
KidJoe said:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
Click to expand...
Click to collapse
Thanks for the link. I used it and I still got the same error.
Make sure you are using the system.img from the correct firmware. Below is a link to the Moto model firmwares. Download the right one, unzip the files until you get to the .img files and use that system.img.
Motorola Firmwares
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
n0obpr0 said:
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
Click to expand...
Click to collapse
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
samwathegreat said:
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
Click to expand...
Click to collapse
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
n0obpr0 said:
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
Click to expand...
Click to collapse
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
samwathegreat said:
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
n0obpr0 said:
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
Click to expand...
Click to collapse
That's what were here for to help others xD
Sent from my XT1053 using XDA Free mobile app
I have requested the stock 5.1 file from motorola and it comes with everything to flash it on the phone via fastboot which also comes in the file. I know what im doing but for some reason everytime i get to flashing the system file it says this?
$ fastboot flash system system.img
sending 'system' (1404896 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Does anybody have a clue i cant get a system img on my phone and I kinda need my phone
Shafty6 said:
I have requested the stock 5.1 file from motorola and it comes with everything to flash it on the phone via fastboot which also comes in the file. I know what im doing but for some reason everytime i get to flashing the system file it says this?
$ fastboot flash system system.img
sending 'system' (1404896 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Does anybody have a clue i cant get a system img on my phone and I kinda need my phone
Click to expand...
Click to collapse
have you tried mfastboot, its modified version of fastboot for larger files
Download mfastboot-v2.zip
hugh a said:
have you tried mfastboot, its modified version of fastboot for larger files
Download mfastboot-v2.zip
Click to expand...
Click to collapse
When I requested the system image for 5.1 it came with fastboot in it everything is from motorola. Why would they not include a fastboot that can load a file that large?
Also i got the mfastboot v2 and it would not work as a fastboot, then i renamed it as fastboot and still will not load the system.img
Shafty6 said:
When I requested the system image for 5.1 it came with fastboot in it everything is from motorola. Why would they not include a fastboot that can load a file that large?
Also i got the mfastboot v2 and it would not work as a fastboot, then i renamed it as fastboot and still will not load the system.img
Click to expand...
Click to collapse
Make sure that the fastboot which is running is the one included with the moto download, and not the one from the Android SDK...
In other words, for Windows PC's, if the Android SDK Platform Tools folder is in the path, often its fastboot will be used instead of the one included in the moto download.
Try renaming the one which came in the moto download as mfastboot.exe, and running it that way, by typing mfastboot.....
KidJoe said:
Make sure that the fastboot which is running is the one included with the moto download, and not the one from the Android SDK...
In other words, for Windows PC's, if the Android SDK Platform Tools folder is in the path, often its fastboot will be used instead of the one included in the moto download.
Try renaming the one which came in the moto download as mfastboot.exe, and running it that way, by typing mfastboot.....
Click to expand...
Click to collapse
Im using mac because its much easier than windows, and ive used the fastboot that comes with everything to fast and everything works perfect till I try system.img
I've have read that it is possible to downgrade from MM to LP without bricking the device using the easy installer.bat file. I have also read that the bat file must be edited removing 2 lines of code ie: "mfastboot.exe flash motoboot motoboot.img" (Which appears twice ) . Is there anything else that needs to be removed ? Also does the whole section need to be removed ie: "echo FLASHING BOOT LOADER..
mfastboot.exe flash motoboot motoboot.img
echo". or just the "mfastboot.exe flash motoboot motoboot.img" line. I would appreciate a clarification . Thank you !!
You're also gonna want to remove the line of code responsible for flashing the partition table (gpt.bin) which also appears twice.
I modified this script for that very purpose....see the attachment.
Just place it in the same folder and flash.
MobileHD said:
You're also gonna want to remove the line of code responsible for flashing the partition table (gpt.bin) which also appears twice.
I modified this script for that very purpose....see the attachment.
Just place it in the same folder and flash.
Click to expand...
Click to collapse
.. Wow thanks! So let me get this straight. I extract the attached zip file to the easy installer folder and use it to flash back to to 5.0.2. I assume all 4 lines of code have been removed?
garyben60 said:
.. Wow thanks! So let me get this straight. I extract the attached zip file to the easy installer folder and use it to flash back to to 5.0.2. I assume all 4 lines of code have been removed?
Click to expand...
Click to collapse
Just make sure the following files are in the folder where you extracted the flash script:
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
flashfile.xml
fsg.mbn
logo.bin
mfastboot.exe
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
TITAN_RETUGLB_5.0.2_LXB22.99-24.12_cid9_CFC.info.txt (NOTE: name will differ based on variant)
gpt.bin & motoboot.img aren't required for the downgrade and shouldn't be downgraded as if may brick your device.
As an additional precaution you can rename those two files to something like '_gpt.bin' & '_motoboot.img'
And yes all unnecessary lines have been removed.
Run the script and choose option '1' to downgrade.
Good Luck and safe downgrade!!
MobileHD said:
Just make sure the following files are in the folder while you extracted the flash script:
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
flashfile.xml
fsg.mbn
logo.bin
mfastboot.exe
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
TITAN_RETUGLB_5.0.2_LXB22.99-24.12_cid9_CFC.info.txt (NOTE: name will differ based on variant)
gpt.bin & motoboot.img aren't required for the downgrade and shouldn't be downgraded as if may brick your device.
As an additional precaution you can rename those two files to something like '_gpt.bin' & '_motoboot.img'
And yes all unnecessary lines have been removed.
Run the script and choose option '1' to downgrade.
Good Luck and safe downgrade!!
Click to expand...
Click to collapse
Thanks again!! really appreciate your help..
One last question. My specific device model is xt1068 (Titan). I see that the flash script say it's for the xt1063. Will it still work with my device?
garyben60 said:
I've have read that it is possible to downgrade from MM to LP without bricking the device using the easy installer.bat file. I have also read that the bat file must be edited removing 2 lines of code ie: "mfastboot.exe flash motoboot motoboot.img" (Which appears twice ) . Is there anything else that needs to be removed ? Also does the whole section need to be removed ie: "echo FLASHING BOOT LOADER..
mfastboot.exe flash motoboot motoboot.img
echo". or just the "mfastboot.exe flash motoboot motoboot.img" line. I would appreciate a clarification . Thank you !!
Click to expand...
Click to collapse
I Recently made a video on this. If you want you can follow this https://youtu.be/OP_AGnwJF4Q tutorial. Hope you like it.
Manav08 said:
I Recently made a video on this. If you want you can follow this https://youtu.be/OP_AGnwJF4Q tutorial. Hope you like it.
Click to expand...
Click to collapse
. Thank you. I saw your video. Well done! I do have a question.. Did you modify the easy installer bat file in any way? The reason I'm asking this because if you read the previous replies certain modifications to the code within the bat file have to be made so that the bootloader doesn't get downgraded thus hardbricking the device.
garyben60 said:
One last question. My specific device model is xt1068 (Titan). I see that the flash script say it's for the xt1063. Will it still work with my device?
Click to expand...
Click to collapse
This is important:
It will work, just make sure that all the system.img_sparsechunk files are accounted for. You may have to edit the script in accordance, for example:
The Lollipop stock ROM for my device XT1063 has 5 system.img_sparsechunk files from 0-4 as the file extension thus the lines of code in the script...
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 system system.img_sparsechunk.4
However if your stock ROM has more or less system.img_sparsechunk files, simple edit the script adding or removing the addition files so that the system partition is properly flashed to your device.
--Update--
I just watched the video that @Manav08 posted, and yes the flash script will work with your device (XT1068), you have nothing to worry about.
MobileHD said:
This is important:
It will work, just make sure that all the system.img_sparsechunk files are accounted for. You may have to edit the script in accordance, for example:
The Lollipop stock ROM for my device XT1063 has 5 system.img_sparsechunk files from 0-4 as the file extension thus the lines of code in the script...
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 system system.img_sparsechunk.4
However if your stock ROM has more or less system.img_sparsechunk files, simple edit the script adding or removing the addition files so that the system partition is properly flashed to your device.
--Update--
I just watched the video that @Manav08 posted, and yes the flash script will work with your device (XT1068), you have nothing to worry about.
Click to expand...
Click to collapse
. Thanks a million for your input.. What are your views about the video?
garyben60 said:
. Thanks a million for your input.. What are your views about the video?
Click to expand...
Click to collapse
I can see in the video that the easyinstaller script used, attempted to flash 'motoboot.img' which you sure avoid doing. What I suggest is to follow the instructions from the video but use my flash script instead.
My thoughts exactly. ..
If anyone uses this method to downgrade don't do what I did and after downgrade allow your device to take any official updates or your device will hard brick. It happened to me and my moto g is now a paperweight.
Sent from my XT1068 using XDA-Developers mobile app