Related
Can I just erase from settings to restore to default?
Sent from my XT1058 using XDA Premium 4 mobile app
our best bet is probably to follow this guide here...
http://forum.xda-developers.com/showthread.php?t=2446515
Or maybe easier would be just to...
fastboot flash system <nameofsystemfilehere>.img
I would have to double check my last bit of advice though.
Newbie help
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
MarcusSi1516 said:
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
Click to expand...
Click to collapse
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
i think so
thepolishguy said:
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
Click to expand...
Click to collapse
yah i do. but i origginaly downloaded root app as apk
MarcusSi1516 said:
yah i do. but i origginaly downloaded root app as apk
Click to expand...
Click to collapse
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
####EDIT####
If fastboot will not flash the system.img use a different fastboot.exe created to flash the larger .img
arigi said:
The solution is to use the mfastboot.exe linked from here:
http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
And if you leave it named "mfastboot" then you must issue the commands with the "m"...
"mfastboot flash system system.img"
without the parenthesis of course
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it should. Just got to make sure you grab the correct images for your carrier.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
should.
But I have a VZW MotoX and I dont want to jack anyone up.
As long as you are using the proper system and recovery. If you flash the ATT system to a VZW device you are going to have problems.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Worked perfect on my ATT Moto x
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
This man deserves some props. Thanks for posting that.
Sent from my HTC One mini
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks for this! It cleared up a whole bunch of things about rooting and locked/unlocked bootloaders for me that just hadn't "clicked" before.
Sent from my Moto X
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
arigi said:
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
^^^^THIS^^^^
Thanks @arigi I added this to my original instructions.
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
edited my build.prop, pasted back my original build.prop,tried reboot ,wouldnt reboot flash moto globe then vibrate then black screen,
booted to bootloader to flash stock firmware, every other file flashed except system .img.
formatted sytem but stil a no go.
this is what i get in command prompt.
when restoring my moto x to stock 4.4.4. retail-gb firmware everything else flashes except the system.img file i get this error : c:\android>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 968495348 bytes
error: cannot load 'system.img': Not enough space
i dont know what to do.
You typed sysytem instead of system, but that's probably just a typo in your post. I can't help you with why mfastboot won't flash the system.img when that's what it was created to do.
nhizzat said:
You typed sysytem instead of system, but that's probably just a typo in your post. I can't help you with why mfastboot won't flash the system.img when that's what it was created to do.
Click to expand...
Click to collapse
in command prompt i typed system
i dont get it,its like the system partition doesnt have enough space to load it on, but ive had 4.4.4 running on it but i messed up my build.prop, well believe it or not i pasted my original build.prop back into system and then my phone wouldnt boot.
If you have the proper 4.4.4 sbf, try rsdlite . Your phone will be wiped though.
I solved it , in the unzipped file there was an XML file with a max download limit line and I erased it from the file in notepad and saved it ,then reflashed all parts again.