Database Develop

Using the command line for flashing original ROMs (What to do when RSD Lite Fails)

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

[4.4.2][183.46.10.XT907]RSD Flashable Firmware

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" />

[Q] stuck on black screen moto g (xt1032)

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

XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

fastboot rom for pie update.
XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

​
tys0n said:
fastboot rom for pie update.
XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
thanks , normal flash with fastboot? my bootloader its locked

is root avaliable with magisk? thanks

jonytestXD said:
​
thanks , normal flash with fastboot? my bootloader its locked
Click to expand...
Click to collapse
No idea if it works with locked bl. I don't have "nash" myself.
This it the flashfile.xml:
Code:
<flashing>
<header>
<phone_model model="nash"/>
<software_version version="nash-user 9 PPX29.159-19 02844 release-keysM8998_50.71.02.95R"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png"/>
<sparsing enabled="true" max-sparse-size="536870912"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="68f8436d0070cf51b239eb3578fb6f87" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="5ef82cf4f04fe4938b1dd0d37eb5a4ea" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="ea0836957b8d3806853722b9fcef3fd1" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step MD5="326104734b872732a74ff9f0ebf13929" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="9d6dd2834c7232367c9b5d6e75b37937" filename="BTFM.bin" operation="flash" partition="bluetooth"/>
<step MD5="db44ea4140b226b4eae3fd38a87a806e" filename="adspso.bin" operation="flash" partition="dsp"/>
<step MD5="51db0539a31730ef1275243f74ca1bd8" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="dafa8846563cc09a001e64fbfcfe03d9" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="97ac33bcdd819983bb53291253fe8d1a" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="14df3e851b691e07b4268c04514b47ed" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="75e40d7edf6e062f3cb3a0fdc1ee454b" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="5f63d47068e37a6223f98c6308e41b3f" filename="system.img_sparsechunk.3" operation="flash" partition="system"/>
<step MD5="86e277fc41f596a4e5174f001d4afde6" filename="system.img_sparsechunk.4" operation="flash" partition="system"/>
<step MD5="4196ed99d82ad7fc87f55a30c1d5582e" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
<step MD5="1f2e3b4fa31f466d03b87471249d0896" filename="system.img_sparsechunk.6" operation="flash" partition="system"/>
<step MD5="58200dc48b70e990a0a15f2c537f8942" filename="system_other.img" operation="flash" partition="system_b"/>
<step MD5="55aad038227bd2cd4cdc1b03547c2814" filename="oem.img" operation="flash" partition="oem"/>
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
So I guess the .bat file should be something like this:
Code:
fastboot oem fb_mode_set
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot reboot-bootloader
Correct me if I'm wrong. As I said, I don't own nash myself. I got other motos tho and the .bat's I've made for them works fine so I think this should be correct .
I took an existing flashall.bat for nash and only did some changes to get the file names right for pie update, but I guess you can remove the "fastboot -w" if you wanna try update without wiping data.

tys0n said:
No idea if it works with locked bl. I don't have "nash" myself.
This it the flashfile.xml:
Code:
<flashing>
<header>
<phone_model model="nash"/>
<software_version version="nash-user 9 PPX29.159-19 02844 release-keysM8998_50.71.02.95R"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png"/>
<sparsing enabled="true" max-sparse-size="536870912"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="68f8436d0070cf51b239eb3578fb6f87" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="5ef82cf4f04fe4938b1dd0d37eb5a4ea" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="ea0836957b8d3806853722b9fcef3fd1" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step MD5="326104734b872732a74ff9f0ebf13929" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="9d6dd2834c7232367c9b5d6e75b37937" filename="BTFM.bin" operation="flash" partition="bluetooth"/>
<step MD5="db44ea4140b226b4eae3fd38a87a806e" filename="adspso.bin" operation="flash" partition="dsp"/>
<step MD5="51db0539a31730ef1275243f74ca1bd8" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="dafa8846563cc09a001e64fbfcfe03d9" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="97ac33bcdd819983bb53291253fe8d1a" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="14df3e851b691e07b4268c04514b47ed" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="75e40d7edf6e062f3cb3a0fdc1ee454b" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="5f63d47068e37a6223f98c6308e41b3f" filename="system.img_sparsechunk.3" operation="flash" partition="system"/>
<step MD5="86e277fc41f596a4e5174f001d4afde6" filename="system.img_sparsechunk.4" operation="flash" partition="system"/>
<step MD5="4196ed99d82ad7fc87f55a30c1d5582e" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
<step MD5="1f2e3b4fa31f466d03b87471249d0896" filename="system.img_sparsechunk.6" operation="flash" partition="system"/>
<step MD5="58200dc48b70e990a0a15f2c537f8942" filename="system_other.img" operation="flash" partition="system_b"/>
<step MD5="55aad038227bd2cd4cdc1b03547c2814" filename="oem.img" operation="flash" partition="oem"/>
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>
So I guess the .bat file should be something like this:
Code:
fastboot oem fb_mode_set
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot -w
fastboot reboot-bootloader
Correct me if I'm wrong. As I said, I don't own nash myself. I got other motos tho and the .bat's I've made for them works fine so I think this should be correct .
I took an existing flashall.bat for nash and only did some changes to get the file names right for pie update, but I guess you can remove the "fastboot -w" if you wanna try update without wiping data.
Click to expand...
Click to collapse
I think its not posible with locked bootloader =( i tried and ger message system corrupt after some reboots system stared and no changes in the firmware =(

this might be a noob question but, if this was installed via flashall would it lock the bootloader on nash-02 with the bootloader already unlocked?

doombuger said:
this might be a noob question but, if this was installed via flashall would it lock the bootloader on nash-02 with the bootloader already unlocked?
Click to expand...
Click to collapse
-02 is US Cellular right? Either way, flashing for the most part won't re-lock a bootloader, but it has happened ironically. THIS is the important part though, flashing a pie firmware for a variant it isn't intended for has done nothing but create bricks and unusable phones. The firmware posted here is RETAIL INDIA (retin) and it will NOT work for US variants. Once you flash a pie modem there is no going back to an oreo modem. The only US variant to have pie is Verizon.

41rw4lk said:
-02 is US Cellular right? Either way, flashing for the most part won't re-lock a bootloader, but it has happened ironically. THIS is the important part though, flashing a pie firmware for a variant it isn't intended for has done nothing but create bricks and unusable phones. The firmware posted here is RETAIL INDIA (retin) and it will NOT work for US variants. Once you flash a pie modem there is no going back to an oreo modem. The only US variant to have pie is Verizon.
Click to expand...
Click to collapse
Ok thanks. Just browsing around for a fix for my modem ironically. Lol. Didn't flash any pie ROM but I did a tmo Oreo variant and lost baseband. I'm half tempted to try a Verizon firmware since they are my provider. I don't even have wifi

I understand all the warnings about flashing this on US varients (have the T-Mobile). My question is this: can we flash this via fastboot, without flashing the modem parts? Basically flashing everything but the modem so we keep our T-Mobile modem files. I assume that I wouldn't flash the following files: NON-HLOS.bin, fsg.mbn, modemst1, modemst2.

alfick3 said:
I understand all the warnings about flashing this on US varients. I assume that I wouldn't flash the following files: NON-HLOS.bin, fsg.mbn, modemst1, modemst2.
Click to expand...
Click to collapse
? What he said

Restoring Stock Firmware using fastboot - Guamp XT 2083-3

In case of bootloop if Lenovo Rescue and Smart Assistant (LMSA) doesn't work, to re install MOTO G9 PLAY XT2083-3 RETEU (europe) stock firmware :
1) Download stock firmware and uncompress it in adb folder
2) Put your mobile in fastboot mode (power + vol down) and connect it to your computer
3) Check if fastboot mode allright : fastboot devices
4) Launch this :
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot flash super super.img_sparsechunk.16
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
That's it. It will reboot automatically to moto stock rom.
Note: Commands can vary for different carriers snd software builds.
Refer to firmware flashfile.xml for exact commands for the firmware you are using.

Note: Commands can vary for different carriers snd software builds.
Refer to firmware flashfile.xml for exact commands for the firmware you are using.

sd_shadow said:
Note: Commands can vary for different carriers snd software builds.
Refer to firmware flashfile.xml for exact commands for the firmware you are using.
Click to expand...
Click to collapse
These commands are efectively specific to XT2083-3. I have tried XT2083-1 first, it doesn't work and found out about .xml file.
flashfile.xml can be found inside stock rom archive.
XT2083-3 is something like this :
Spoiler: xml file
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="guamp_retail"/>
<software_version version="guamp_retail-user 11 RPXS31.Q2-58-17-4-1 9f01c release-keysHA10_29.11.02.88R"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="84561da925e7a878ba8806173d609e0d134ea10e" name="regulatory_info_xt2083_3_europe_sar.png"/>
<sparsing enabled="true" max-sparse-size="268435456"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="4dedfb15d07ce8a33bc4342bfeb0941c" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="8d817e3321ede68abc4e77b7310c396c" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="756fed025758674179f747a458cf98ba" filename="vbmeta.img" operation="flash" partition="vbmeta"/>
<step MD5="9746b7e6088c39fee24213acb55fbc0c" filename="radio.img" operation="flash" partition="radio"/>
<step MD5="b25e307c8c099c2233eb29a693d9bb21" filename="BTFM.bin" operation="flash" partition="bluetooth"/>
<step MD5="59d248cb50acb0e7bfab993e30bb40d2" filename="dspso.bin" operation="flash" partition="dsp"/>
<step MD5="ddadc4e48def8caba7f575ebac1cfcb6" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="032c1230d7a6e42ecda2a302f462dcb7" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="7011633204467c318a602271d37514db" filename="dtbo.img" operation="flash" partition="dtbo"/>
<step MD5="9b3a92add3e7de23020477792ee6300a" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="5a29e34698d617fcfbf60e88ef77c3ac" filename="super.img_sparsechunk.0" operation="flash" partition="super"/>
<step MD5="9d1f20724d9284fb6e4378302b8aeffb" filename="super.img_sparsechunk.1" operation="flash" partition="super"/>
<step MD5="664f3bf6d2e868018bf6af381590907e" filename="super.img_sparsechunk.2" operation="flash" partition="super"/>
<step MD5="9759a0c289ec28b514a6eaadafcf41e0" filename="super.img_sparsechunk.3" operation="flash" partition="super"/>
<step MD5="74f6d83d1a6d0640690ed80d8cf7624c" filename="super.img_sparsechunk.4" operation="flash" partition="super"/>
<step MD5="e71ec1d7285686c497c6ceb81b3e69f7" filename="super.img_sparsechunk.5" operation="flash" partition="super"/>
<step MD5="e9ec9772de45a2f5c05482d98ebd04f7" filename="super.img_sparsechunk.6" operation="flash" partition="super"/>
<step MD5="e60278dbcd17fb660609247ba7c333fe" filename="super.img_sparsechunk.7" operation="flash" partition="super"/>
<step MD5="e66d58085abacc8f10de69a745ef81ab" filename="super.img_sparsechunk.8" operation="flash" partition="super"/>
<step MD5="1d93fbd624393550832ca8f2c008c324" filename="super.img_sparsechunk.9" operation="flash" partition="super"/>
<step MD5="d05b76bb8c0543cb1dfb36ae3c227705" filename="super.img_sparsechunk.10" operation="flash" partition="super"/>
<step MD5="748f2926a72f3f6c895df539436339f5" filename="super.img_sparsechunk.11" operation="flash" partition="super"/>
<step MD5="e57069cd8533318d0e28186b702591cb" filename="super.img_sparsechunk.12" operation="flash" partition="super"/>
<step MD5="69cc2413e52c6d10c38d3caa372aa016" filename="super.img_sparsechunk.13" operation="flash" partition="super"/>
<step MD5="6ac300f5961bb031916332352e5823f3" filename="super.img_sparsechunk.14" operation="flash" partition="super"/>
<step MD5="861d968785dd9a8cd2584dc8c253d6a2" filename="super.img_sparsechunk.15" operation="flash" partition="super"/>
<step MD5="38aa0f47e20fa909b937d933ec3d6d96" filename="super.img_sparsechunk.16" operation="flash" partition="super"/>
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="metadata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>