Related
Hello everyone
I have a Bell MB886 that I bought on Amazon.com. It came with ICS 4.0.4, and OTA doesn't work for me (maybe because I'm from Chile).
I saw this post and wanted to install stock Bell's 4.1.2 for my Atrix HD using RSD Lite, which gave me lots of errors, and when I finnaly could make it work, it gave me an error flashing system.img.
I thought I bricked my phone, cause even trying to flash other original ROMs, it gave the same error message.
From this point, I did some research on the internet and I want to share my experience with you guys to flash the Stock ROMs using the manual method on our Atrix HD's.
First: Get the firmwares.
http://www.filefactory.com/f/b7425536f9a2526e
http://sbf.droid-developers.org/dinara/list.php
Once you download the firmware ZIP, uncompress it to any folder you want (I recommend using the C:\ root or your desktop).
Then you need to download the file "fastboots.zip" (attached to this post).
Uncompress the files located on the Windows folder of the file fastboots.zip on the folder you decompressed the stock ROM.
If you want to replace the original recovery with CWM, you can replace the file "recovery.img" on the folder you decompressed the stock ROM with the one attached to this post (uncompress it on the same folder).
You should get something like this:
{
"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"
}
There you have the files "fastboot" (with orange, the one you will use to flash), "MB886~.xml" (the XML file that contains the instructions for flashing the system), and if you replaced it, contains the modified recovery.img (in yellow).
So, now we will analyze the MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA.xml file. There is always a XML file named as the ROM name, that contains the instructions to RSD Lite for flashing the file. We will use this instructions for manually flashing our file.
Open the XML file with Notepad and you should see this:
The lines on red are useless for us. The rest of lines are the ones we have to insert on the fastboot command line.
Let's analyze the lines.
Every line includes an operation (command), var/partition, and filename. We have to tell the command line the commands between < >. For example:
When the XML file says this:
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="66250529A6711D25A1AFB4F8D4CA4873" />
It tells to the command line:
flash partition gpt_main0.bin
So, now we will flash our device.
I assume you have installed Motorola's Drivers (link) and put your phone on fastboot mode (Turn off your phone and press both volume keys and power on. You'll enter bootmenu options. Choose AP Fastboot by scrolling with volume down and volume up to select).
This guide is intended for use under Windows 7 64-bit, as I have not tested it on other platforms. Do it at your own risk as I assume no responsability if this doesn't work for you as it worked for me.
Go to the folder on which you extracted the files, and click the adress bar and type CMD and hit enter, doing this we open the command line on the folder you are actually.
So, now we have to flash the rom, typing the commands on the XML file on the command line.
If the XML file says the following:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="66250529A6711D25A1AFB4F8D4CA4873" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="0F1D270C3083522F2726710AC1DD22F2" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="1936488F8449E652CE53D7CC8F43E52F" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="9A6D34EB8D306BE6FFCA85719F6451C6" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="919D0B340CFDD5FC7C541803DB65C2D6" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="ED1C505E36E769CCF0BB3C10E46DD62B" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="00D268AAE9924B28AEC0F5401CF73E11" />
<step operation="reboot-bootloader" />
<step operation="oem" var="fb_mode_set" />
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="68BD7F2CE348C55F3778862E47FBEE54" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="6EA5E26FCF4D5AD45569B8F864AC9F90" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="06C07C2970460A4E656A3206859A3617" />
<step operation="flash" partition="boot" filename="boot.img" MD5="66A49414AC7AC9BCCA1243D9EAFAA46A" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="3C3AF0A695CCDD57897C861AA58CC5EB" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="E0E4804A20D47C379B2F718F1C118B8A" />
<step operation="flash" partition="system" filename="system.img" MD5="D1E7B6FC549B0AE578350A1028FEEF87" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="C3A09EA2D007AC96F4BA7AA09B478ABE" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
We have to insert the following on the command line (hitting enter between lines):
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
If between every step you see the OK message, every went ok. Type fastboot reboot and you should see your new system working OK.
I hope this helps anyone that had the same problem as I had, as RSD Lite didn't work for me, and almost bricked my new Atrix HD :good:
Greetings,
I also did this before Btw, nice guide for anyone who cant use RSDLite to flash.
leanix said:
Hello everyone
I have a Bell MB886 that I bought on Amazon.com. It came with ICS 4.0.4, and OTA doesn't work for me (maybe because I'm from Chile).
I saw this post and wanted to install stock Bell's 4.1.2 for my Atrix HD using RSD Lite, which gave me lots of errors, and when I finnaly could make it work, it gave me an error flashing system.img.
I thought I bricked my phone, cause even trying to flash other original ROMs, it gave the same error message.
From this point, I did some research on the internet and I want to share my experience with you guys to flash the Stock ROMs using the manual method on our Atrix HD's.
First: Get the firmwares.
http://www.filefactory.com/f/b7425536f9a2526e
http://sbf.droid-developers.org/dinara/list.php
Once you download the firmware ZIP, uncompress it to any folder you want (I recommend using the C:\ root or your desktop).
Then you need to download the file "fastboots.zip" (attached to this post).
Uncompress the files located on the Windows folder of the file fastboots.zip on the folder you decompressed the stock ROM.
If you want to replace the original recovery with CWM, you can replace the file "recovery.img" on the folder you decompressed the stock ROM with the one attached to this post (uncompress it on the same folder).
You should get something like this:
There you have the files "fastboot" (with orange, the one you will use to flash), "MB886~.xml" (the XML file that contains the instructions for flashing the system), and if you replaced it, contains the modified recovery.img (in yellow).
So, now we will analyze the MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA.xml file. There is always a XML file named as the ROM name, that contains the instructions to RSD Lite for flashing the file. We will use this instructions for manually flashing our file.
Open the XML file with Notepad and you should see this:
The lines on red are useless for us. The rest of lines are the ones we have to insert on the fastboot command line.
Let's analyze the lines.
Every line includes an operation (command), var/partition, and filename. We have to tell the command line the commands between < >. For example:
When the XML file says this:
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="66250529A6711D25A1AFB4F8D4CA4873" />
It tells to the command line:
flash partition gpt_main0.bin
So, now we will flash our device.
I assume you have installed Motorola's Drivers (link) and put your phone on fastboot mode (Turn off your phone and press both volume keys and power on. You'll enter bootmenu options. Choose AP Fastboot by scrolling with volume down and volume up to select).
This guide is intended for use under Windows 7 64-bit, as I have not tested it on other platforms. Do it at your own risk as I assume no responsability if this doesn't work for you as it worked for me.
Go to the folder on which you extracted the files, and click the adress bar and type CMD and hit enter, doing this we open the command line on the folder you are actually.
So, now we have to flash the rom, typing the commands on the XML file on the command line.
If the XML file says the following:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="66250529A6711D25A1AFB4F8D4CA4873" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="0F1D270C3083522F2726710AC1DD22F2" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="1936488F8449E652CE53D7CC8F43E52F" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="9A6D34EB8D306BE6FFCA85719F6451C6" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="919D0B340CFDD5FC7C541803DB65C2D6" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="ED1C505E36E769CCF0BB3C10E46DD62B" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="00D268AAE9924B28AEC0F5401CF73E11" />
<step operation="reboot-bootloader" />
<step operation="oem" var="fb_mode_set" />
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="68BD7F2CE348C55F3778862E47FBEE54" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="6EA5E26FCF4D5AD45569B8F864AC9F90" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="06C07C2970460A4E656A3206859A3617" />
<step operation="flash" partition="boot" filename="boot.img" MD5="66A49414AC7AC9BCCA1243D9EAFAA46A" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="3C3AF0A695CCDD57897C861AA58CC5EB" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="E0E4804A20D47C379B2F718F1C118B8A" />
<step operation="flash" partition="system" filename="system.img" MD5="D1E7B6FC549B0AE578350A1028FEEF87" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="C3A09EA2D007AC96F4BA7AA09B478ABE" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
We have to insert the following on the command line (hitting enter between lines):
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
If between every step you see the OK message, every went ok. Type fastboot reboot and you should see your new system working OK.
I hope this helps anyone that had the same problem as I had, as RSD Lite didn't work for me, and almost bricked my new Atrix HD :good:
Greetings,
Click to expand...
Click to collapse
wow u are super awesome, i thought i surely bricked my atrix but this brought it back from the grave, thank you, thank you, thank you. lol
fixed my moto atrix hd phone!!
hey so i got it figured out by following these directions from xda ppl http://forum.xda-developers.com/show....php?t=2259661 im all good again & brought back from dead. but question do u think i can now use cwm recovery to flash a stock at&t rom onto phone cuz i flashed a stock bell rom but maybe i will stick with that because 1. its jb 4.1.2 verus at&t 4.1.1 & 2. it lets the wifi hotspot feature built into rom work where as at&t 4.1.1 rom blocked it? ty tho for all your help. ron. :highfive:
It worked 4 me, i upgraded my bell's atrix hd from 4.0.4 to 4.1.2, thanks!
Saved my phone
You are awesome! I was so afraid I'd bricked my phone. I've been lurking the forum for a while, but finally joined just to say thanks.
Hello everyone. I'm glad to hear that this worked for you too :laugh:
rubberman365 said:
hey so i got it figured out by following these directions from xda ppl http://forum.xda-developers.com/show....php?t=2259661 im all good again & brought back from dead. but question do u think i can now use cwm recovery to flash a stock at&t rom onto phone cuz i flashed a stock bell rom but maybe i will stick with that because 1. its jb 4.1.2 verus at&t 4.1.1 & 2. it lets the wifi hotspot feature built into rom work where as at&t 4.1.1 rom blocked it? ty tho for all your help. ron. :highfive:
Click to expand...
Click to collapse
Honestly I don't know, as I have not ever installed AT&T ROMs on my phone, only Bell ones. As far as I know, you can install AT&T ROMs on Bell phones, but only if they have unlocked bootloaders. As a matter of fact, there is a guide for that! http://forum.xda-developers.com/showthread.php?t=2050283
Hope this helps.
Greetings,
mega thanks, leanix ! ! !
leanix, i was SOOoo close to just giving up on my Atrix HD... (read my plight at: http://forum.xda-developers.com/showthread.php?t=2394238&page=2 ).
Very grateful for your post. It was time consuming and tedious to execute all the commands, but have just loaded epinter's rom and excited about having an AWESOME Atrix HD breathing fire!
Whew!!!!
- ricer1
leanix said:
Hello everyone
I have a Bell MB886 that I bought on Amazon.com. It came with ICS 4.0.4, and OTA doesn't work for me (maybe because I'm from Chile).
I saw this post and wanted to install stock Bell's 4.1.2 for my Atrix HD using RSD Lite, which gave me lots of errors, and when I finnaly could make it work, it gave me an error flashing system.img.
I thought I bricked my phone, cause even trying to flash other original ROMs, it gave the same error message.
From this point, I did some research on the internet and I want to share my experience with you guys to flash the Stock ROMs using the manual method on our Atrix HD's.
First: Get the firmwares.
http://www.filefactory.com/f/b7425536f9a2526e
http://sbf.droid-developers.org/dinara/list.php
Once you download the firmware ZIP, uncompress it to any folder you want (I recommend using the C:\ root or your desktop).
Then you need to download the file "fastboots.zip" (attached to this post).
Uncompress the files located on the Windows folder of the file fastboots.zip on the folder you decompressed the stock ROM.
If you want to replace the original recovery with CWM, you can replace the file "recovery.img" on the folder you decompressed the stock ROM with the one attached to this post (uncompress it on the same folder).
You should get something like this:
There you have the files "fastboot" (with orange, the one you will use to flash), "MB886~.xml" (the XML file that contains the instructions for flashing the system), and if you replaced it, contains the modified recovery.img (in yellow).
So, now we will analyze the MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA.xml file. There is always a XML file named as the ROM name, that contains the instructions to RSD Lite for flashing the file. We will use this instructions for manually flashing our file.
Open the XML file with Notepad and you should see this:
The lines on red are useless for us. The rest of lines are the ones we have to insert on the fastboot command line.
Let's analyze the lines.
Every line includes an operation (command), var/partition, and filename. We have to tell the command line the commands between < >. For example:
When the XML file says this:
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="66250529A6711D25A1AFB4F8D4CA4873" />
It tells to the command line:
flash partition gpt_main0.bin
So, now we will flash our device.
I assume you have installed Motorola's Drivers (link) and put your phone on fastboot mode (Turn off your phone and press both volume keys and power on. You'll enter bootmenu options. Choose AP Fastboot by scrolling with volume down and volume up to select).
This guide is intended for use under Windows 7 64-bit, as I have not tested it on other platforms. Do it at your own risk as I assume no responsability if this doesn't work for you as it worked for me.
Go to the folder on which you extracted the files, and click the adress bar and type CMD and hit enter, doing this we open the command line on the folder you are actually.
So, now we have to flash the rom, typing the commands on the XML file on the command line.
If the XML file says the following:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="66250529A6711D25A1AFB4F8D4CA4873" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="0F1D270C3083522F2726710AC1DD22F2" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="1936488F8449E652CE53D7CC8F43E52F" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="9A6D34EB8D306BE6FFCA85719F6451C6" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="919D0B340CFDD5FC7C541803DB65C2D6" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="ED1C505E36E769CCF0BB3C10E46DD62B" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="00D268AAE9924B28AEC0F5401CF73E11" />
<step operation="reboot-bootloader" />
<step operation="oem" var="fb_mode_set" />
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="68BD7F2CE348C55F3778862E47FBEE54" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="6EA5E26FCF4D5AD45569B8F864AC9F90" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="06C07C2970460A4E656A3206859A3617" />
<step operation="flash" partition="boot" filename="boot.img" MD5="66A49414AC7AC9BCCA1243D9EAFAA46A" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="3C3AF0A695CCDD57897C861AA58CC5EB" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="E0E4804A20D47C379B2F718F1C118B8A" />
<step operation="flash" partition="system" filename="system.img" MD5="D1E7B6FC549B0AE578350A1028FEEF87" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="C3A09EA2D007AC96F4BA7AA09B478ABE" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
We have to insert the following on the command line (hitting enter between lines):
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
If between every step you see the OK message, every went ok. Type fastboot reboot and you should see your new system working OK.
I hope this helps anyone that had the same problem as I had, as RSD Lite didn't work for me, and almost bricked my new Atrix HD :good:
Greetings,
Click to expand...
Click to collapse
hello I do not understand how it is to put the commands in the cmd you could make a video .. I when I try to flashar with lite rs I get error in "BOOT.IMG" know it can be?
well crud...
Right in the middle of flashing a new ROM (the PACMAN) my sWindows machine goes to the infamous blue-screen-of-death... Now the phone is in bootflash mode and won't accept any flashing.
After spending most of the day trying various 'tricks' to no avail, I'm resolved to send it to mobiletechvideos.com and let them revive it. I think it will take a JTAG to jump-start this guy...
I'll post a reply when it's returned and report on what they were able to do.
- ricer1
mobiletechvideos.com did good on my Atrix HD
I've had a month now to play with my revived Atrix HD! I sent my bricked phone to mobiletechvideos.com and they were able to install the PACMAN rom onto it (pac_mb866_4.3.Build-1_20130917-025321). So far, so good. I'm very happy to have a working 4.3 on the AHD. And thanks to Skeevy420 for his work to port this rom.
- ricer1
________________________________________
ricer1 said:
well crud...
Right in the middle of flashing a new ROM (the PACMAN) my sWindows machine goes to the infamous blue-screen-of-death... Now the phone is in bootflash mode and won't accept any flashing.
After spending most of the day trying various 'tricks' to no avail, I'm resolved to send it to mobiletechvideos.com and let them revive it. I think it will take a JTAG to jump-start this guy...
I'll post a reply when it's returned and report on what they were able to do.
- ricer1
Click to expand...
Click to collapse
Hey i have cuestion i have an atrix hd mb886 from at&nt and i want to go back to stock but my phone is unlocked so i want to know if is going to lock to at&nt or will continue unlocked for any sim thanks.
No Probblem
Antrax57 said:
Hey i have cuestion i have an atrix hd mb886 from at&nt and i want to go back to stock but my phone is unlocked so i want to know if is going to lock to at&nt or will continue unlocked for any sim thanks.
Click to expand...
Click to collapse
It will continue unlocked.
massterlee said:
It will continue unlocked.
Click to expand...
Click to collapse
Ok thanks bro
H get back to my stock rom thanks to u bro but i have a problem my wifi dont want to turn on it says Turning wifi on but stays like that what can be the problem??
Thank you leanix for this write up. My AHD is back from the "dead"!
Strangely enough I can flash MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX after removing the red lines, but can't get past "fastboot flash partition gpt_main0.bin" when trying MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
clockcycle said:
Strangely enough I can flash MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX after removing the red lines, but can't get past "fastboot flash partition gpt_main0.bin" when trying MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
Click to expand...
Click to collapse
So what I found out is that you can not "cross flash" without encountering errors. Find out which base your phone is currently, as the partition table my be different and you may not be able to flash gpt_main0.bin. I got the point I couldn't use RSDlite to flash any of the 4.1.x stock roms without it failing. Had to do it manually, when you find which, you're able to flash it all without errors.
clockcycle said:
So what I found out is that you can not "cross flash" without encountering errors. Find out which base your phone is currently, as the partition table my be different and you may not be able to flash gpt_main0.bin. I got the point I couldn't use RSDlite to flash any of the 4.1.x stock roms without it failing. Had to do it manually, when you find which, you're able to flash it all without errors.
Click to expand...
Click to collapse
Well I get the stock but i needed to doet manualy with fastboot and I get the stock zip from att and t but stay like that not working the wifi some one tell me that my be Ithe wifi brakes or something because I change the kernel but dont work
Antrax57 said:
Well I get the stock but i needed to doet manualy with fastboot and I get the stock zip from att and t but stay like that not working the wifi some one tell me that my be Ithe wifi brakes or something because I change the kernel but dont work
Click to expand...
Click to collapse
I just had that problem last night. I followed the OP's guide, but only ran this one command: fastboot flash modem NON-HLOS.bin. Make sure NON-HLOS.bin is in the same directory as fastboot.exe
I've read and reread jcase's guide since it was first released but it's a little too advanced for me and includes far too many steps than I could easily botch. It's my opinion that a better guide or video could be really beneficial for myself as well as all the other lost users that make the occasional failed attempt post. Is there anyone out there who's successfully completed root who could help out?
Sent from my XT1060 using Tapatalk
rockstarr001 said:
I've read and reread jcase's guide since it was first released but it's a little too advanced for me and includes far too many steps than I could easily botch. It's my opinion that a better guide or video could be really beneficial for myself as well as all the other lost users that make the occasional failed attempt post. Is there anyone out there who's successfully completed root who could help out?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Not sure if you still need help or not but here is what I did. None of this is my own work. I read through the forums over and over and tried to take notes from the 4 different forums (RSD Lite, RockMyMoto, MotoWPNoMo, and SlapMyMoto) so that I could have one place to look while rooting my phone. No video but maybe this will help you get rooted.
Edit: Telnet Thread
Before you begin, make sure to visit each forum and download the necessary files. You will need RSD Lite, Cydia Impactor, Android SDK(For ADB), the camera update file for 4.2.2., and the files from each of the 3 steps (RockMyMoto, MotoWPNoMo, and SlapMyMoto). Unzip these and save all the files in the same folder with your SDK tools. You will also need to open the 4.2.2. file using wordpad and delete the following line
<step operation="getvar" var="max-download-size" />
Save the new file with the deleted line and use this when you use RSD Lite to go back to 4.2.2.
You will need to turn off firewalls and antivirus. Telnet needs to be enabled on your computer. I used Windows 7 and you can find that option from Control Panel, Programs, Turn Windows Features On and Off. Then check the boxes for Telnet Client and Server.
You will need to turn on USB debugging on your device and hook it up to your computer and make sure you have all of the necessary drivers working. You can test by opening your ADB command window (hold shift and right click the folder where you downloaded and unzipped Android SDK) and typing adb devices. If it does not list a device, you need to check your drivers (Motorola drivers) If it does, you are ready to start.
Root directions
ADB commands in bold and telnet commands in italics. Do not type "quotes" except internal set in step 5 l.
1. Revert to 4.2.2 using RSD Lite
a. Open command prompt by holding shift and right clicking folder where ADB tools are
b. Verify adb devices connected by typing "adb devices"
c. Reboot into bootloader by typing "adb reboot bootloader"
d. Open RSD Lite and verify that device is connected (Should show up in Line 1)
e. Click three dots to Open file VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF
f. Click Start and let process run.
Phone will be working and RSD Lite will show that it is working. After phone reboots type adb reboot bootloader in adb command window. This will let it reconnect to RSD Lite and should say finished or passed where it had listed the progress. If it does, start up the phone using volume up on your phone and go back to settings and enable usb debugging. Then proceed to RockMyMoto.
2. Run RockMyMoto
a. Open adb command prompt
b. Find device ip address
i. type "adb shell getprop dhcp.wlan0.ipaddress"
ii. write this down for future use
c. Push files to sd card
i. type "adb push su /sdcard/"
ii. type "adb push RockMyMoto.jar /sdcard/"
d. Run Cydia Impactor “# start telnetd as system on port 2222” and hit start
e. Open a command window by holding shift and right clicking on the folder where you saved Cydia Imapactor.
f. Type "telnet {your phone’s ip address} 2222"
g. Type "dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto"
h. Reboot in adb command prompt by typing "adb reboot"
i. Repeat telnet process again (will have to start a new session after each reboot) (should reboot on its own this time)
i. type "dalvikvm –cp /sdcard/RockMyMoto.jar RockMyMoto"
j. Repeat telnet process for a third time (Will not reboot)
i. type "dalvikvm –cp /sdcard/RockMyMoto.jar RockMyMoto"
k. Wait ~60 seconds for su to install then install SuperSu from Google Play Store
You should now have root
3. Run MotoWpNoMo to disable write protection (Must be rooted and have disabled firewall and antivirus before running. Also set phone to "stay awake" when charging. Will need to grant root permissions during process so make sure to watch phone)
a. Run “wpbegone.exe” as administrator. File located in MotoWpNoMo folder
b. Follow on-screen prompts
c. After complete, verify in adb command prompt by typing "adb shell getprop ro.boot.write_protect"
d. Will see a “0” if write protection is disabled
I had to repeat this process 5 or 6 times before it actually worked. It will take 15 minutes or so if it runs the whole process. If not, it will cut short and tell you to hit enter to exit.
4. Use RSD Lite to go back to the 4.2.2. update. Follow the same directions from Step 1
5. Run SlapMyMoto 1.0
a. Push SlapMyMoto to sd card using adb command window
i. type "adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar"
b. Open telnet session (See 2c and 2d)
c. In telnet type "dalvikvm –cp /sdcard/SlapMyMoto.jar SlapMyMoto"
d. Reboot in adb
i. type "adb reboot"
e. Open telnet session again
i. type "dalvikvm –cp /sdcard/SlapMyMoto.jar SlapMyMoto"
f. Device should reboot
g. Take 4.4 OTA
h. Open adb command prompt
i. type "adb shell"
j. type "cp /sdcard/install.sh /data/local/tmp/install.sh"
k.type chmod 755 /data/local.tmp/install.sh
l. type "echo “/data/local/tmp/install.sh” > /sys/kernel/uevent_helper"
m. Toggle Bluetooth and when device reboots, process is complete
(Mine device did not reboot with bluetooth toggle so I rebooted using adb command and it worked fine)
Agreed with OP. I'll try the above guide, thanks. Question: Does this method cause permanent changes? I heard somewhere that either RockMyMoto or SlapMyMoto or something, 1 of the methods, caused irreversible changes even if you went back to stock. I'm really just looking to root to get tethering on an unlimited Verizon account and other basic things.
Yazzinit said:
Agreed with OP. I'll try the above guide, thanks. Question: Does this method cause permanent changes? I heard somewhere that either RockMyMoto or SlapMyMoto or something, 1 of the methods, caused irreversible changes even if you went back to stock. I'm really just looking to root to get tethering on an unlimited Verizon account and other basic things.
Click to expand...
Click to collapse
The only irreversible change comes from MotoWPNoMo. It permanently turns off write protection.
If you root and go through all of the steps you can access free wifi tethering. It can be done after following the above directions and then running the script from post #35 in this thread.
Thanks a ton. I don't think that turning off write protection is a big deal if I don't go crazy letting stuff access it or whatever. I appreciate the help. Only other problem I wondered is getting OTA updates but I guess people will make topics how to accept them while rooted later when new updates come out.
Edit: Is that above guide for non DE Moto X on Verizon? 2) That link for tethering also says for DE, does that matter? Non DE here
Not 100% sure but I think that you can still accept OTA updates if you use RSD lite to go back to 4.2.2 before you do it.
Yes, the link will work for non DE Verizon Moto X. I am running a non DE from Verizon and have so far had no problems with it. Granted, I haven't used it much yet but so far so good.
Sent from my XT1060 using Tapatalk
Yazzinit said:
Agreed with OP. I'll try the above guide, thanks. Question: Does this method cause permanent changes? I heard somewhere that either RockMyMoto or SlapMyMoto or something, 1 of the methods, caused irreversible changes even if you went back to stock. I'm really just looking to root to get tethering on an unlimited Verizon account and other basic things.
Click to expand...
Click to collapse
Correct.. If u rsd back to 4.2.2 u can still take OTA..HOWEVER u will no be able to root... Simply because there is no known root for 4.4 hince y u must go back to 4.2.2
KLRTN said:
Not 100% sure but I think that you can still accept OTA updates if you use RSD lite to go back to 4.2.2 before you do it.
Yes, the link will work for non DE Verizon Moto X. I am running a non DE from Verizon and have so far had no problems with it. Granted, I haven't used it much yet but so far so good.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Slapped my Moto
I get that. But the list above eventually says take the 4.4 OTA. So really, it's going back to 4.2.2, rooting, then since you're already exploited, you can still get 4.4, right? I was worred about getting updates beyond 4.4 in the future, but I guess people will figure that out when they come out.
Yazzinit said:
I get that. But the list above eventually says take the 4.4 OTA. So really, it's going back to 4.2.2, rooting, then since you're already exploited, you can still get 4.4, right? I was worred about getting updates beyond 4.4 in the future, but I guess people will figure that out when they come out.
Click to expand...
Click to collapse
Yes... U go back to 4.2.2 get root then use motowpnomo to kill WP then reflash back to 4.2.2 for clean push slapmymoto and then take OTA for 4.4 and finish using the adb commands listed in instructions.
Slapped my Moto
KLRTN said:
... You will also need to open the 4.2.2. file using wordpad and delete the following line
<step operation="getvar" var="max-download-size" />
Save the new file with the deleted line and use this when you use RSD Lite to go back to 4.2.2....
Click to expand...
Click to collapse
this is really great, thanks! I'll give this a try tonight. however, I need clarification on this step I extracted from your instructions. when saving the file, do I need to re-zip the package or do anything special?
this is really great, thanks! I'll give this a try tonight. however, I need clarification on this step I extracted from your instructions. when saving the file, do I need to re-zip the package or do anything special?
I did not rezip the file. I deleted the line, hit save, closed wordpad, and used the file with RSD Lite.
Sent from my XT1060 using Tapatalk
Followed the guide, had root at the beginning. Took the 4.4 OTA and finished the guide, no longer have root with SU or Titanium Backup. Can't proceed further, any help?
Edit: Seems a reboot into bootloader and then rebooting worked. Do I need to do this every time I reboot the phone? As in, must I connect it to my PC and do this? Or can I reboot from the phone directly somehow?
Yazzinit said:
Followed the guide, had root at the beginning. Took the 4.4 OTA and finished the guide, no longer have root with SU or Titanium Backup. Can't proceed further, any help?
Edit: Seems a reboot into bootloader and then rebooting worked. Do I need to do this every time I reboot the phone? As in, must I connect it to my PC and do this? Or can I reboot from the phone directly somehow?
Click to expand...
Click to collapse
OK...so u had root then u took 4.4 OTA and no more SU? Correct?
Slapped my Moto
I edited too late, sorry about that. Seems after I randomly rebooted again through the adb prompt on my computer, it now works, for now.
Yazzinit said:
Followed the guide, had root at the beginning. Took the 4.4 OTA and finished the guide, no longer have root with SU or Titanium Backup. Can't proceed further, any help?
Edit: Seems a reboot into bootloader and then rebooting worked. Do I need to do this every time I reboot the phone? As in, must I connect it to my PC and do this? Or can I reboot from the phone directly somehow?
Click to expand...
Click to collapse
Were you able to verify that write protection was turned off using adb?
c. After complete, verify in adb command prompt by typing “adb shell getprop ro.boot.write_protect”
d. Will see a “0” if write protection is disabled
i'm currently at step 2d, and cydia just reads, "testing #9950697".... how long should this process take before I try something different?
thanks!
Check your phone
jco23 said:
i'm currently at step 2d, and cydia just reads, "testing #9950697".... how long should this process take before I try something different?
thanks!
Click to expand...
Click to collapse
Check your phone because the first time you do it, you have to hit "Accept" on the screen.
jco23 said:
i'm currently at step 2d, and cydia just reads, "testing #9950697".... how long should this process take before I try something different?
thanks!
Click to expand...
Click to collapse
It generally takes less than a minute or 2 to go through the testing process and connect.
Please help!!
I have attempted to root my Moto X several times and I have had no success. I originally had 4.2.2. rooted with PwnMyMoto. i have reflashed the stock 4.2.2. firmware (or at least i think i have).Every time I have finished and opened SuperSU, I get a notification that no SU binary is installed. I have copied and pasted my cmd prompts along with the file versions and applied setting in hopes someone will be able to see where the problem is occurring.
Instructions followed: http://forum.xda-developers.com/showthread.php?t=2565762
PC: Windows 7
Phone at start of process: VZW, Moto X XT1060, current OS- 4.4 OTA, Build number- 13.11.1Q2.X-69-3
Motorola Device Manager: up to date
RSD Lite: v6.1.5.
SDK Manager: Revision 22.3, 64-bit version,
Installed Packages:
Tools--Android SDK Tools Rev, 22.3., Platform-Tools Rev. 19.0.1., Build-Tools Rev. 19.0.1.
Android Support Library Rev. 19.0.1.
Google USB Driver Rev. 8
Stock 4.2.2. Firmware: VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml
RockMyMoto-1.1.
MotoWpNoMo-0.0.4
SlapMyMoto-1.0
1. <step operation="getvar" var="max-download-size" /> deleted and file saved
2. Antivirus and firewalls shutdown
3. Telnet Client and Server turned on
4. USB debugging turned on
5. Verified proper USB data cable
CMD IS AS FOLLOWS: (ADB commands in bold and telnet commands in italics.)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
T062801ZBN device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools> adb reboot bootloader
RSD Lite opened; Device shows up in Port 2
Installed stock 4.2.2., phone restarted but RSD Lite said the install was still in progress so I logged in to phone, verified in About Phone that 4.2.2. installed, activated USB Debugging, then in cmd prompt window used adb reboot bootloader command to restart the phone. RSD Lite then indicated that the install was complete and it passed.
Script for stock 4.2.2. I used:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VZW_XT1060_CFC" />
<software_version version="ghost_verizon-user 4.2.2 13.9.0Q2.X-116-MX-17-57-X-1 1 release-keysMSM8960PRO_BP_2323.020.90.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="4C9F15C80FED62BAB7A042FDBA4D7A2F" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="34B3A02418240C805CCB2998B2343261" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="1F8DBC99E41DFB7596DBC78687AC5E7B" />
<step operation="flash" partition="boot" filename="boot.img" MD5="49C02FCD26133923B1B4F2CFE862C422" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="62DCB8F941BEC9D824146453834CD3FE" />
<step operation="flash" partition="system" filename="system.img" MD5="1D5214E5171BE9894D0413322D2DD211" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="57B83F54B07922B9CBAF3C4125CBA8A1" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="BAB00624486527FE415D8BACFF875C99" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="config carrier vzw" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Turned on Wifi and logged in
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell getprop dhcp.wlan0.ipaddress
###.###.##.## (ipaddress hidden for privacy)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\RockMyMoto-1.1>adb push su /sdcard/
3164 KB/s (100452 bytes in 0.031s)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\RockMyMoto-1.1>adb push
RockMyMoto.jar /sdcard/
1022 KB/s (3142 bytes in 0.003s)
Ran Cydia Impactor telnet as system on port 2222
Clicked “Accept” on phone screen
Opened CMD prompt from Cydia folder
telnet ###.###.##.## 2222 (ipaddress hidden for privacy)
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot
Closed telnet cmd window
Repeated Cydia Impactor telnet as system on port 2222
Opened new CMD prompt from Cydia folder
telnet ###.###.##.## 2222 (ipaddress hidden for privacy)
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
Phone did not reset on its own like instructions suggested so I executed C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot
Closed telnet cmd window
Repeated Cydia Impactor telnet as system on port 2222
Opened new CMD prompt from Cydia folder
telnet ###.###.##.## 2222 (ipaddress hidden for privacy)
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
Installed SuperSU and it said there was no SU binary installed
Any help or suggestions at this point would be greatly appreciated.
supertrav1980 said:
I have attempted to root my Moto X several times and I have had no success. I originally had 4.2.2. rooted with PwnMyMoto. i have reflashed the stock 4.2.2. firmware (or at least i think i have).Every time I have finished and opened SuperSU, I get a notification that no SU binary is installed. I have copied and pasted my cmd prompts along with the file versions and applied setting in hopes someone will be able to see where the problem is occurring.
Instructions followed: http://forum.xda-developers.com/showthread.php?t=2565762
PC: Windows 7
Phone at start of process: VZW, Moto X XT1060, current OS- 4.4 OTA, Build number- 13.11.1Q2.X-69-3
Motorola Device Manager: up to date
RSD Lite: v6.1.5.
SDK Manager: Revision 22.3, 64-bit version,
Installed Packages:
Tools--Android SDK Tools Rev, 22.3., Platform-Tools Rev. 19.0.1., Build-Tools Rev. 19.0.1.
Android Support Library Rev. 19.0.1.
Google USB Driver Rev. 8
Stock 4.2.2. Firmware: VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-57-X-1_CFC_1FF.xml
RockMyMoto-1.1.
MotoWpNoMo-0.0.4
SlapMyMoto-1.0
1. <step operation="getvar" var="max-download-size" /> deleted and file saved
2. Antivirus and firewalls shutdown
3. Telnet Client and Server turned on
4. USB debugging turned on
5. Verified proper USB data cable
CMD IS AS FOLLOWS: (ADB commands in bold and telnet commands in italics.)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
T062801ZBN device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools> adb reboot bootloader
RSD Lite opened; Device shows up in Port 2
Installed stock 4.2.2., phone restarted but RSD Lite said the install was still in progress so I logged in to phone, verified in About Phone that 4.2.2. installed, activated USB Debugging, then in cmd prompt window used adb reboot bootloader command to restart the phone. RSD Lite then indicated that the install was complete and it passed.
Script for stock 4.2.2. I used:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VZW_XT1060_CFC" />
<software_version version="ghost_verizon-user 4.2.2 13.9.0Q2.X-116-MX-17-57-X-1 1 release-keysMSM8960PRO_BP_2323.020.90.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="4C9F15C80FED62BAB7A042FDBA4D7A2F" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="34B3A02418240C805CCB2998B2343261" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="1F8DBC99E41DFB7596DBC78687AC5E7B" />
<step operation="flash" partition="boot" filename="boot.img" MD5="49C02FCD26133923B1B4F2CFE862C422" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="62DCB8F941BEC9D824146453834CD3FE" />
<step operation="flash" partition="system" filename="system.img" MD5="1D5214E5171BE9894D0413322D2DD211" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="57B83F54B07922B9CBAF3C4125CBA8A1" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="BAB00624486527FE415D8BACFF875C99" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="config carrier vzw" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Turned on Wifi and logged in
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell getprop dhcp.wlan0.ipaddress
###.###.##.## (ipaddress hidden for privacy)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\RockMyMoto-1.1>adb push su /sdcard/
3164 KB/s (100452 bytes in 0.031s)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\RockMyMoto-1.1>adb push
RockMyMoto.jar /sdcard/
1022 KB/s (3142 bytes in 0.003s)
Ran Cydia Impactor telnet as system on port 2222
Clicked “Accept” on phone screen
Opened CMD prompt from Cydia folder
telnet ###.###.##.## 2222 (ipaddress hidden for privacy)
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot
Closed telnet cmd window
Repeated Cydia Impactor telnet as system on port 2222
Opened new CMD prompt from Cydia folder
telnet ###.###.##.## 2222 (ipaddress hidden for privacy)
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
Phone did not reset on its own like instructions suggested so I executed C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot
Closed telnet cmd window
Repeated Cydia Impactor telnet as system on port 2222
Opened new CMD prompt from Cydia folder
telnet ###.###.##.## 2222 (ipaddress hidden for privacy)
~ $ dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is not write protected...
Executing step 3...
Installed SuperSU and it said there was no SU binary installed
Any help or suggestions at this point would be greatly appreciated.
Click to expand...
Click to collapse
I had some issues with SuperSu too. I unistalled SuperSu and then reinstalled and problem cleared up.
hello,first what i have to say is,my english is very bad..
I have a big problem..I wanted to wipe data and system on mine xt890 before flashing a rom.my recovery was cwm.the wipe failure.then i tried to flash a twrp flashable zip via recovery.this fail ,too...now i con only go to bootloader,but i can`t flash over rsd lite and if i try to flash over fastboot in command-line i get a error...(sending to device ok flashing failure [remoteermision denied]
can anyone help me please?
Can you flash cwm and restore a backup?
Do you have a downloaded original ROM to match this. If so you can flash the original gpt using fastboot command
Sent from my XT890 using XDA Premium 4 mobile app
Flacid Monkey said:
Can you flash cwm and restore a backup?
Do you have a downloaded original ROM to match this. If so you can flash the original gpt using fastboot command
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no i can`'t....
alex-aus-bz said:
hello,first what i have to say is,my english is very bad..
I have a big problem..I wanted to wipe data and system on mine xt890 before flashing a rom.my recovery was cwm.the wipe failure.then i tried to flash a twrp flashable zip via recovery.this fail ,too...now i con only go to bootloader,but i can`t flash over rsd lite and if i try to flash over fastboot in command-line i get a error...(sending to device ok flashing failure [remoteermision denied]
can anyone help me please?
Click to expand...
Click to collapse
You have to reformat the "disk" which is almost impossible because you have to figure out the parameters for each partition and do it manually with a linux reformatting tool. I had this happen to me once with a Nook Color and eventually just gave up and threw it away. Sorry. I hope someone else has a better answer for you.
iolinux333 said:
You have to reformat the "disk" which is almost impossible because you have to figure out the parameters for each partition and do it manually with a linux reformatting tool. I had this happen to me once with a Nook Color and eventually just gave up and threw it away. Sorry. I hope someone else has a better answer for you.
Click to expand...
Click to collapse
i hope it,to.if there is a possibility way to figure out the parameters?have anyone a script or a info about the data of the razr i partitions?
It can't boot,can't go to recovery.Only ap fastboot works.but i can't flash anything over rsd lite and fastboot command.it says sending to device... ok.flash failure (remote : permission denied ) only radio flashing is funktionable.in fastboot menü i have the following error messages :
faild to read /dev/block/mmcblk0 I/O Error
E:read intel version from mmc : faild to read OSIP Header from sector 0
E:faild to read version for bos
failt to read /dev/block/mmcblk0 I/O Error
E:faild to read partition gpt_main
E:faild to load gpt_main
failt to read /dev/block/mmcblk0 I/O Error
E:faild to read partition gpt_backup
E:faild to load gpt_backup
E:no valid GPT existed
faild to hab check gpt
no any partition found
E:no PDS Partition found
fastboot reason:invalid GPT
max download size:100mb
no any partition found
E:no PDS Partition found
the command fastboot getvar all shows :
C:\Users\win7 ultimate x64\Desktop\ADB>fastboot getvar all
(bootloader) version-bootloader: 0x200F
(bootloader) product: smi
(bootloader) secure: yes
(bootloader) rom-key: motorola-key
(bootloader) model-id: 0268
(bootloader) cid: ffff
(bootloader) version: 0.5
(bootloader) uid: 2E1424CDCA1DA18A3F7ED9B4A871
(bootloader) max-download-size: 104857600
(bootloader) emmc-size: 8GB
(bootloader) qe:
(bootloader) unlocked: no
(bootloader) is-warranty-void: Not supported
(bootloader) ifwi: 42.21
(bootloader) cpu: Intel(R) Atom(TM) CPU Z2480 @ 2.00GHz
(bootloader) kernel: droidboot
(bootloader) battery: capacity: 39, voltage: 3792500, temperature: 430
all:
finished. total time: 0.328s
flash a stock rom with rsd lite. you can also only flash gpt with rsdlite. if you only want to flash the gpt, then edit the fastboot.xml like this:
first unzip the ****.sbf.zip. then edit:
<?xml version="1.0" encoding="utf-8"?>
<flashing>
<header>
<phone_model model="Scorpion Mini I EMARA" />
<software_version version="XT890_emara-user 4.1.2 9.8.2I-50_SMI-26 1358465787 release-keysSUNRISE_SMB_REV30_V2_R3_1251.B" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="gpt" filename="gpt_signed" MD5="e507b43d78403531b9392112f66286df" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
</steps>
</flashing>
fastboot getvar says, yout bootloader is not unlocked "(bootloader) unlocked: no".
you may need to re-unlock the bootloader via the motorola website.
reflash cutom recovery.
tachno said:
flash a stock rom with rsd lite. you can also only flash gpt with rsdlite. if you only want to flash the gpt, then edit the fastboot.xml like this:
first unzip the ****.sbf.zip. then edit:
<?xml version="1.0" encoding="utf-8"?>
<flashing>
<header>
<phone_model model="Scorpion Mini I EMARA" />
<software_version version="XT890_emara-user 4.1.2 9.8.2I-50_SMI-26 1358465787 release-keysSUNRISE_SMB_REV30_V2_R3_1251.B" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="gpt" filename="gpt_signed" MD5="e507b43d78403531b9392112f66286df" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
</steps>
</flashing>
that was not succesful ...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
what error code do you get from rsd lite when you try to flash a full stock rom ?
Hello, i have exactly the same problem as alex-aus-bz,
Can sombody know how to fix this error?
luis_villarruel said:
Hello, i have exactly the same problem as alex-aus-bz,
Can sombody know how to fix this error?
Click to expand...
Click to collapse
try flashing with latest official firmware (4.1.2) from your device, so EU to Eu and BR to BR. And use latest rsd-lite 6.1.x
didn't worked for me, RSD says: "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL."
the phone was on fastboot flash mode.
Hazou said:
try flashing with latest official firmware (4.1.2) from your device, so EU to Eu and BR to BR. And use latest rsd-lite 6.1.x
Click to expand...
Click to collapse
luis_villarruel said:
didn't worked for me, RSD says: "Failed flashing process. 1/12 flash gpt "gpt_signed" -> Phone returned FAIL."
the phone was on fastboot flash mode.
Click to expand...
Click to collapse
Try this and use the JB ones from your firmware, not the ICS ones. And try rsd-lite again.
If this fails i dunno what happened. Looks like a memory failure to me.
Didn't work! i think i'm going to take the phone to Motorola's technical service...
thanks for the help!
Hazou said:
Try this and use the JB ones from your firmware, not the ICS ones. And try rsd-lite again.
If this fails i dunno what happened. Looks like a memory failure to me.
Click to expand...
Click to collapse
I take no credit for this. Do not thank me. Go thank Skrilax_CZ.
This is only for reference for those that only visit XDA
Firmware flashable using RSD Lite to backup back to 4.4.2 Kitkat
Android 4.4.2
Blur_Version.183.46.10.XT907.Verizon.en.US
Go check out the guys at http://sbf.droid-developers.org/ for more awesome firmwares
Does the CM11 can flash this package Radio?
can I, install this with RSD LITe if my phone is locked?
allen_ho said:
Does the CM11 can flash this package Radio?
Click to expand...
Click to collapse
You can flash this on CM11 for the radio, but you will need to reinstall CM afterwords
aagcnet said:
can I, install this with RSD LITe if my phone is locked?
Click to expand...
Click to collapse
Yes
Sent from my One using XDA Premium 4 mobile app
But this is in no way rooted, or rootable presently, correct??
bofis said:
But this is in no way rooted, or rootable presently, correct??
Click to expand...
Click to collapse
It is not prerooted. In order to root, you will need an unlocked bootloader and CWM/TWRP.
Sent from my One using XDA Premium 4 mobile app
just flash "NON-HLOS.bin" and "fsg.mbn" ?
I found the "sbl1.mbn"~"sbl3.mbn", is it need to flash too?
allen_ho said:
just flash "NON-HLOS.bin" and "fsg.mbn" ?
I found the "sbl1.mbn"~"sbl3.mbn", is it need to flash too?
Click to expand...
Click to collapse
sbl1-3 are you basebands. I'd reccommend you flash those as well.
Sent from my One using XDA Premium 4 mobile app
I tried to flash this file with rsd lite and I received an error.
I updated to 182.46.10.... recently, but I suppose 183 has some issues alredy fixed. What did happen here?
Please someone let me know what happened.
Leraeniesh said:
sbl1-3 are you basebands. I'd reccommend you flash those as well.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
after I flash "NON-HLOS.bin" and "fsg.mbn" "sbl1.mbn"~"sbl3.mbn", and reboot and reflash the CM11 (or carbon) the system didn't get signal, even the wifi. does something I miss?
Just so you and everyone else knows (I'll have to post this in a few threads) but the Towel Root method completely works on our phones. Locked bootloader, stock 4.4.2, and I was able to root my wife's Razr M just now:
http://towelroot.com/
i have unlocked my phone to use with other sim cards.. can i flash 4.4.3 update or will i lose my sim connectivity of other providers>>
misal6666 said:
i have unlocked my phone to use with other sim cards.. can i flash 4.4.3 update or will i lose my sim connectivity of other providers>>
Click to expand...
Click to collapse
If by flashing to 4.4.3, you mean AOSP based ROMs, then no.
Sent from my One using XDA Premium 4 mobile app
Leraeniesh said:
If by flashing to 4.4.3, you mean AOSP based ROMs, then no.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So i guess the answers also no for if i flash 4.4.2 official verizon firmware
Im rooted and unlocked now but I have 182.46.10 and I would like to install 183. How can I do it?
Enviado desde mi XT907 mediante Tapatalk
misal6666 said:
i have unlocked my phone to use with other sim cards.. can i flash 4.4.3 update or will i lose my sim connectivity of other providers>>
Click to expand...
Click to collapse
I lost it going to official Verizon (4.4.2), but got it back by doing the same hack I used to get it in the first place.
misal6666 said:
i have unlocked my phone to use with other sim cards.. can i flash 4.4.3 update or will i lose my sim connectivity of other providers>>
Click to expand...
Click to collapse
Can you use tmobile and at&t sim cards?
Enviado desde mi XT907 mediante Tapatalk
Issues with RSD Lite
Anyone having issues flashing back to Stock 98.30 with the flash files? I keep getting an "Unknown Fastboot Command", Failed Flash Error.. Not sure if RSD Lite or PC config is the problem. I downloaded the above mentioned file (4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip, Opened RSD Lite, Decompressed/Flashed, and get "FAIL". Anything I need to change in my ADB/Fastboot/SDK-Platform-tools folder??? The error I am getting says "Please check input file. Either XML format is wrong or image files associated with it are missing".
So...if I didn't want to overwrite my current system install, could I just use this:
Code:
fastboot flash partition gpt.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot erase tombstones
fastboot erase cache
MoPhoMike said:
Anyone having issues flashing back to Stock 98.30 with the flash files? I keep getting an "Unknown Fastboot Command", Failed Flash Error.. Not sure if RSD Lite or PC config is the problem. I downloaded the above mentioned file (4.4.2-KDA20.62-10.1_CFC_1FF.xml.zip, Opened RSD Lite, Decompressed/Flashed, and get "FAIL". Anything I need to change in my ADB/Fastboot/SDK-Platform-tools folder??? The error I am getting says "Please check input file. Either XML format is wrong or image files associated with it are missing".
Click to expand...
Click to collapse
the .XML is bad..it has 3 lines that should not be there and 1 missing...this is the proper code
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VZW_XT907_CFC" />
<software_version version="smq_vzw-user 4.4.2 KDA20.62-10.1 10 release-keysSM_BP_101031.042.32.86P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt.bin" MD5="5B3FD782141145E4BD1C9270D954AFF1" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="B06997B2407D87205454D47A4DE2CA77" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="9EBD6FB39A7DDBD3DD8BB0F0E7B4E612" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="B3D58C0A21BAA8DEAC238B6002ABB59E" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="6ACFA1DA4F8FF45341D7C2EC40C733F7" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="8514ED883150B7A0579F9431CD872B39" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="974770FC264C73E429B716F1832A8C38" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="56CC3781D10C94A342F5262560EFEFDB" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="42661F0BBF0DB568369F9337324F7BEC" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />
<step operation="flash" partition="boot" filename="boot.img" MD5="B59DF3268823BCE19DF80409C036645D" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="2FD6AB345BBE5B6C99DE1B5CE1D56F2C" />
<step operation="flash" partition="system" filename="system.img" MD5="1362E5D51CA3D71089F9B48A836624C9" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
</steps>
</flashing>
edit: the removed lines that cause the failed flash.
Code:
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
Code:
<step operation="oem" var="fb_mode_clear" />
Hello forum!
i need some help, i have a moto g with apparently big issues...
note:
*i have unlocked bootloader(status code 3)
* 4.4.2 ( 2014 - 06 - 16)
___________________________________
fastboot reason : volume down key pressed
USB connected
cmd: getvar:max-download-size
cmd: download: 00008000
cmd: flash: partition
cmd: getvar:max-download-size
cmd: download: 001e8600
cmd: flash: motoboot
..etc...................................................................................................
..etc...................................................................................................
..etc...................................................................................................
//xml code to flash *** i have to erase getvar references because didnt flash if i use it
<?xml version="1.0" ?>
<flashing> <header> <phone_model model="falcon_retbr"/>
<software_version version="falcon_retbr-user 5.0.2 LXB22.46-28 28 release-keysMSM8626BP_1032.3105.93.00R"/>
<sparsing enabled="true" max-sparse-size="268435456"/>
<interfaces><interface name="AP"/></interfaces>
</header>
<steps interface="AP">
<step MD5="c656f74e9666ea988d75ca4847bda443" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="10f89c00e21cb851cca3209aa27735cb" filename="motoboot.img" operation="flash" partition="motoboot"/>
<step MD5="430c86260d74d74baaba53c57ad80f18" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="bbb146a9efb61ca91e33bf691126773c" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="ff9b0a3bc4484c60a1d98e05034cbf73" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="e857dba9785009a1135f7b1c111dc649" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="d0936fee0846a1a7b599e2b2273358ec" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="57ff5e6f64c3c295fe009a03ca55b477" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="88af2c1b0b43346508cbb17b6a819d0a" filename="system.img_sparsechunk.3" operation="flash"partition="system"/>
<step MD5="60e835888ec7cbc5d6014a6dabfff606" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="1706b3415196a8a2d6d96ea1eb45b246" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
</steps>
</flashing>
_______________________________________________________________________________________________
the device start up with the logo and do all animations and when it ends... only have a blackscreen, first time appears a message box " system failed " and two options (wait ... close....)
i flashed with rsd and cmd with 5.0.2 stock brasil but when its finish.... do it the same animations and blackscreen
im stuck with this phone :/ can some one help?
davcastroruiz said:
Hello forum!
i need some help, i have a moto g with apparently big issues...
note:
*i have unlocked bootloader(status code 3)
* 4.4.2 ( 2014 - 06 - 16)
___________________________________
fastboot reason : volume down key pressed
USB connected
cmd: getvar:max-download-size
cmd: download: 00008000
cmd: flash: partition
cmd: getvar:max-download-size
cmd: download: 001e8600
cmd: flash: motoboot
..etc...................................................................................................
..etc...................................................................................................
..etc...................................................................................................
//xml code to flash *** i have to erase getvar references because didnt flash if i use it
<?xml version="1.0" ?>
<flashing> <header> <phone_model model="falcon_retbr"/>
<software_version version="falcon_retbr-user 5.0.2 LXB22.46-28 28 release-keysMSM8626BP_1032.3105.93.00R"/>
<sparsing enabled="true" max-sparse-size="268435456"/>
<interfaces><interface name="AP"/></interfaces>
</header>
<steps interface="AP">
<step MD5="c656f74e9666ea988d75ca4847bda443" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="10f89c00e21cb851cca3209aa27735cb" filename="motoboot.img" operation="flash" partition="motoboot"/>
<step MD5="430c86260d74d74baaba53c57ad80f18" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="bbb146a9efb61ca91e33bf691126773c" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="ff9b0a3bc4484c60a1d98e05034cbf73" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="e857dba9785009a1135f7b1c111dc649" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="d0936fee0846a1a7b599e2b2273358ec" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="57ff5e6f64c3c295fe009a03ca55b477" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="88af2c1b0b43346508cbb17b6a819d0a" filename="system.img_sparsechunk.3" operation="flash"partition="system"/>
<step MD5="60e835888ec7cbc5d6014a6dabfff606" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="1706b3415196a8a2d6d96ea1eb45b246" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
</steps>
</flashing>
_______________________________________________________________________________________________
the device start up with the logo and do all animations and when it ends... only have a blackscreen, first time appears a message box " system failed " and two options (wait ... close....)
i flashed with rsd and cmd with 5.0.2 stock brasil but when its finish.... do it the same animations and blackscreen
im stuck with this phone :/ can some one help?
Click to expand...
Click to collapse
have you check the XML ROM file that you unzip?
it doesn't contains system.img_sparsechunk.4?
xt1068 and 69 lollipop rom's does so you need to add one more line in the CMD just like the others 1 2 and 3 for that system.img_sparsechunk.4. :good:
baybutcher27 said:
have you check the XML ROM file that you unzip?
it doesn't contains system.img_sparsechunk.4?
xt1068 and 69 lollipop rom's does so you need to add one more line in the CMD just like the others 1 2 and 3 for that system.img_sparsechunk.4. :good:
Click to expand...
Click to collapse
no, doesnt contains that .img.... only 0, 1,2, 3.... but i try with 4.4.4 america movil and the same ( blackscreen when ends the animations )
davcastroruiz said:
no, doesnt contains that .img.... only 0, 1,2, 3.... but i try with 4.4.4 america movil and the same ( blackscreen when ends the animations )
Click to expand...
Click to collapse
the process to flash a rom via cmd is very easy if you are not successful you must be doing some wrong.
Use this program
mfastboot-v2.zip
Do this commands in bootloader screen
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot reboot
Remove mfastboot.exe the command flash system system.img_sparsechunk.4 if the xml file does not have it.
the files of the rom and mfastboot need to be in the same folder like the pic attached, hold shift and click on empty space on the folder and click ''open cmd from here''
I recommend you to re-download the xml file from here the one for your device and country.
I use this program with this commands and never have problem.
baybutcher27 said:
the process to flash a rom via cmd is very easy if you are not successful you must be doing some wrong.
Use this program
mfastboot-v2.zip
Do this commands in bootloader screen
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot reboot
Remove mfastboot.exe the command flash system system.img_sparsechunk.4 if the xml file does not have it.
the files of the rom and mfastboot need to be in the some folder like the pic attached, hold shift and click on empty space on the folder and click ''open cmd from here''
I recommend you to re-download the xml file from here the one for your device and country.
I use this program with this commands and never have problem.
Click to expand...
Click to collapse
thank you but doesnt work for me :/
im thinking maybe could be the drivers .. but i try with w7 w8 with (motorola device manager for the drivers and console and rsd lite ) when i have the phone on fastboot mode in devices appears as fasboot falcon s
I had different motorola phone and flash never was difficult, but at the time this goes up files ... on the fatsboot console of motog appears cmd: the Instruction and the name of what is coming up
in other motorolas as (xt890 motox 910) did not appear so
Thanks
Thanks for your very prompt reply
I really appreciate everyone doing this for me.
I will download the firmware now,
if i have any problems i will post back
Many thanks
Lewis Viner