[Q] Motorola Atrix HD help. - Motorola Atrix HD

I am hoping someone out there will be able to help me with my Motorola Atrix HD which I have soft bricked. Previously I was running it with Jellybean and safestrap installed. I flashed a ROM using safestrap, but apparently it was still pointing to the stock location. I got an error for the ROM installation and when I tried to reboot, it went to a screen with a android lying down with a red triangle. I was able to get it into Android System Recovery Utility, but haven't been able to get anything to install. I also tried RSD lite with the appropriate files and have received 1/24 partition errors, 1/23 partition errors, and several other errors. I have tried to flash CWM and install other roms, but nothing works. I would appreciate any help on this. Thank You.

Safestrap is a dead and extinct method. Use Mythtools and read about the edited xml files so you can properly flash via RSD.
Sent from my MB886 using xda app-developers app

See post #2 for the short answer.
Now for the cause:
You flashed an unlocked bootloader rom on a locked bootloader phone. The stock recovery you have access to will only flash signed roms from Motorola and you can't replace it with CWM until you've unlocked the phone. Like post 2 said, download MythTools and have it get you back to stock, say yes to using stock recovery, then either root it and do what you were doing or unlock it, install Philz CWM, and start using the custom roms. For RSD to work for you right now, extract the fastboot, open up the xml file, and delete the two lines with -- <step operation="oem" -- in them.
FWIW, we should have an actual KitKat update sometime eventually soon and that will contain a fix to prevent the bootloader from being unlocked. If you don't unlock the bootloader before that update you probably never will.
This is for Bell ICS stock. You have to use ATT JB fastboot's xml, don't copy/paste this -- the md5sums are different but the changes are the same. The lines to remove are in bold.
BEFORE
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="DINARA_CFC_FFW" />
<software_version version="qinara_bell-user 4.0.4 7.7.1Q-115_MB886_BELL_FFW-12 18 release-keysQINARA_BP_1045.703.41.09P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="7DDA3A0C79737F7980373E25C028F26D" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="497EADC7B6A9C37CE7E828E9CDCB2383" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="E892D0369C886C4D8C4C4772A3035739" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="D60717471D584B8FAD41365730512256" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="F44809F0BE9CDF883D007DB2041DCEDA" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="F41F0F575D52B390D576A89BC773DDB0" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="DA04D26F5C34F2A2F7FCF14003E65BF7" />
<step operation="reboot-bootloader" />
[B]<step operation="oem" var="fb_mode_set" />[/B]
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="ABBD3EE4CB254F620DEDF9A1DB337FF1" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="35F8FBF53B46410B495357EA5CC4225D" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="boot" filename="boot.img" MD5="E7A95F72340F2F3E03EC2E1A4050FCAC" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="FF8CDD711906306D3F876FC69AE0D192" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="C5D0968CC8E8A2003CCDAE4D19F29031" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="FFD273DED204C4388F6907AE0ECDE130" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="14FDDA83BD7AC9DD5B829962A9F4C6BA" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
[B]<step operation="oem" var="fb_mode_clear" />[/B]
</steps>
</flashing>
AFTER
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="DINARA_CFC_FFW" />
<software_version version="qinara_bell-user 4.0.4 7.7.1Q-115_MB886_BELL_FFW-12 18 release-keysQINARA_BP_1045.703.41.09P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="7DDA3A0C79737F7980373E25C028F26D" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="497EADC7B6A9C37CE7E828E9CDCB2383" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="E892D0369C886C4D8C4C4772A3035739" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="D60717471D584B8FAD41365730512256" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="F44809F0BE9CDF883D007DB2041DCEDA" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="F41F0F575D52B390D576A89BC773DDB0" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="DA04D26F5C34F2A2F7FCF14003E65BF7" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="ABBD3EE4CB254F620DEDF9A1DB337FF1" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="35F8FBF53B46410B495357EA5CC4225D" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="boot" filename="boot.img" MD5="E7A95F72340F2F3E03EC2E1A4050FCAC" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="FF8CDD711906306D3F876FC69AE0D192" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="C5D0968CC8E8A2003CCDAE4D19F29031" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="FFD273DED204C4388F6907AE0ECDE130" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="14FDDA83BD7AC9DD5B829962A9F4C6BA" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
</steps>
</flashing>

palmbeach05 said:
Safestrap is a dead and extinct method. Use Mythtools and read about the edited xml files so you can properly flash via RSD.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
You are right. I've tried mythtools, but need to read about the edited xml files to flash via RSD.
Thanks for you help.

skeevydude said:
See post #2 for the short answer.
Now for the cause:
You flashed an unlocked bootloader rom on a locked bootloader phone. The stock recovery you have access to will only flash signed roms from Motorola and you can't replace it with CWM until you've unlocked the phone. Like post 2 said, download MythTools and have it get you back to stock, say yes to using stock recovery, then either root it and do what you were doing or unlock it, install Philz CWM, and start using the custom roms. For RSD to work for you right now, extract the fastboot, open up the xml file, and delete the two lines with -- <step operation="oem" -- in them.
FWIW, we should have an actual KitKat update sometime eventually soon and that will contain a fix to prevent the bootloader from being unlocked. If you don't unlock the bootloader before that update you probably never will.
This is for Bell ICS stock. You have to use ATT JB fastboot's xml, don't copy/paste this -- the md5sums are different but the changes are the same. The lines to remove are in bold.
BEFORE
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="DINARA_CFC_FFW" />
<software_version version="qinara_bell-user 4.0.4 7.7.1Q-115_MB886_BELL_FFW-12 18 release-keysQINARA_BP_1045.703.41.09P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="7DDA3A0C79737F7980373E25C028F26D" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="497EADC7B6A9C37CE7E828E9CDCB2383" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="E892D0369C886C4D8C4C4772A3035739" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="D60717471D584B8FAD41365730512256" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="F44809F0BE9CDF883D007DB2041DCEDA" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="F41F0F575D52B390D576A89BC773DDB0" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="DA04D26F5C34F2A2F7FCF14003E65BF7" />
<step operation="reboot-bootloader" />
[B]<step operation="oem" var="fb_mode_set" />[/B]
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="ABBD3EE4CB254F620DEDF9A1DB337FF1" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="35F8FBF53B46410B495357EA5CC4225D" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="boot" filename="boot.img" MD5="E7A95F72340F2F3E03EC2E1A4050FCAC" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="FF8CDD711906306D3F876FC69AE0D192" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="C5D0968CC8E8A2003CCDAE4D19F29031" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="FFD273DED204C4388F6907AE0ECDE130" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="14FDDA83BD7AC9DD5B829962A9F4C6BA" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
[B]<step operation="oem" var="fb_mode_clear" />[/B]
</steps>
</flashing>
AFTER
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="DINARA_CFC_FFW" />
<software_version version="qinara_bell-user 4.0.4 7.7.1Q-115_MB886_BELL_FFW-12 18 release-keysQINARA_BP_1045.703.41.09P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="7DDA3A0C79737F7980373E25C028F26D" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="497EADC7B6A9C37CE7E828E9CDCB2383" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="E892D0369C886C4D8C4C4772A3035739" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="D60717471D584B8FAD41365730512256" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="F44809F0BE9CDF883D007DB2041DCEDA" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="F41F0F575D52B390D576A89BC773DDB0" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="DA04D26F5C34F2A2F7FCF14003E65BF7" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="ABBD3EE4CB254F620DEDF9A1DB337FF1" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="35F8FBF53B46410B495357EA5CC4225D" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="boot" filename="boot.img" MD5="E7A95F72340F2F3E03EC2E1A4050FCAC" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="FF8CDD711906306D3F876FC69AE0D192" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="C5D0968CC8E8A2003CCDAE4D19F29031" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="FFD273DED204C4388F6907AE0ECDE130" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="14FDDA83BD7AC9DD5B829962A9F4C6BA" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
</steps>
</flashing>
Click to expand...
Click to collapse
Thanks for the help. Do I need to enter the code listed in your post? Also what would I need to do to unlock the bootloader. I am a little new at this. Thanks again.

bigjds said:
Thanks for the help. Do I need to enter the code listed in your post? Also what would I need to do to unlock the bootloader. I am a little new at this. Thanks again.
Click to expand...
Click to collapse
After reading your post again, I realized I just need to remove the 2 lines from the xml file.
Thanks.

Just download MythTools. It'll do everything for you.
See the MythTools thread for links and getting it set up.
First use it to flash the stock att jb fastboot, the Android 4.1.1 one -- assuming you were using stock att jb here
All our fastboots are located here.
And when it gets to the recovery flash, select stock because you're locked
Let it boot up, and you can skip all setup and restoration crap, you'll be doing a factory reset real soon
Once booted to the homescreen, use MythTools to root it.
Once rooted and rebooted, use MythTools again to unlock the bootloader.
After that flash Philz CWM....Myth does that too.
When you unlock it does a factory reset so you can either setup the stock ATT
Or flash a different stock fastboot (use Myth....) or one of the many custom roms we have here.

skeevydude said:
Just download MythTools. It'll do everything for you.
See the MythTools thread for links and getting it set up.
First use it to flash the stock att jb fastboot, the Android 4.1.1 one -- assuming you were using stock att jb here
All our fastboots are located here.
And when it gets to the recovery flash, select stock because you're locked
Let it boot up, and you can skip all setup and restoration crap, you'll be doing a factory reset real soon
Once booted to the homescreen, use MythTools to root it.
Once rooted and rebooted, use MythTools again to unlock the bootloader.
After that flash Philz CWM....Myth does that too.
When you unlock it does a factory reset so you can either setup the stock ATT
Or flash a different stock fastboot (use Myth....) or one of the many custom roms we have here.
Click to expand...
Click to collapse
Thank You!! It worked and my phone is back. I guess I just wasn't following directions. I do appreciate your help.
Thanks again.

Related

Editing FXZ .XML Files for Fun & Profit

While trying to find a better way to get a friend on .886 to update to 5.9.905 I decided to poke around an FXZ file to see if I could get RSD Lite to essentially only update system, webtop, and radios while leaving everything else intact. I found this portion of the XML to be interesting.
<step operation="reboot-bootloader" />
<step operation="flash" partition="cdt.bin" filename="cdt.bin" MD5="fd8c44b060415dfd963fa870ae7a4f35" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="emstorage" />
<step operation="flash" partition="lbl" filename="lbl" MD5="239bbc49a9cdb329577074ba60bbf1e5" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="06c07c2970460a4e656a3206859a3617" />
<step operation="flash" partition="ebr" filename="ebr" MD5="4c6df9afcd64661036a982e03eb1aa1a" />
<step operation="flash" partition="mbr" filename="mbr" MD5="712e3e3757219ecfd925eb43be14f944" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="2404a4f245f1da389d3422d0d59be24a" />
<step operation="flash" partition="system" filename="system.img" MD5="8e306ac58dd4fcf01566c517eabc098d" />
Click to expand...
Click to collapse
It looks like all I'd have to do is remove the lines containing "userdata" and "emstorage" and that means that /data and /sdcard will be untouched during the flash process, while everything around it gets updated. Can someone confirm/deny if my thoughts are correct?

[Q] How to flash a new FW and keep radio/modem untouched?

Which lines should be removed from .xml file when flashing with RSD Lite in order to keep radio/modem untouched?
I saw different answers in different topics.
Option 1:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="e93541730af3b17d5d447acb813f4a49" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
Option 2:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="e93541730af3b17d5d447acb813f4a49" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="a4d7cb43a587b60a73c4aba929e6b93e" />
Which one is correct?
I took the 1. One to flash without touch the modem.
Gesendet von meinem XT1052 mit Tapatalk
amarguli said:
Which lines should be removed from .xml file when flashing with RSD Lite in order to keep radio/modem untouched?
I saw different answers in different topics.
Option 1:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="e93541730af3b17d5d447acb813f4a49" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
Option 2:
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="e93541730af3b17d5d447acb813f4a49" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="a4d7cb43a587b60a73c4aba929e6b93e" />
Which one is correct?
Click to expand...
Click to collapse
option 2 are the lines you want to delete if you dont want to flash the radio and modem's

RSDLite and Moto X 2014

Good Morning. I tried to run the Moto X 2014 with many versions of RSDLite but the program does not find the phone. Some users of the forum is successful ???
Mine isn't connecting either not sure what the issue is you have any luck yet??
jmcdonald58 said:
Mine isn't connecting either not sure what the issue is you have any luck yet??
Click to expand...
Click to collapse
Hello. I tried again but RSDLite does not see it. Windows detects the phone correctly but RSDLite not. Patience will use the adb commands to install the firmware.
solocchi said:
Hello. I tried again but RSDLite does not see it. Windows detects the phone correctly but RSDLite not. Patience will use the adb commands to install the firmware.
Click to expand...
Click to collapse
hey, could you please tell me how to install stock firmware using adb commands? Or is it the same as here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Hope u can help me.
Thanks
nerotix said:
hey, could you please tell me how to install stock firmware using adb commands? Or is it the same as here:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Hope u can help me.
Thanks
Click to expand...
Click to collapse
Hello. If you have the Moto X 2013, and want to install a firmware you must use RSDLite and download your firmware from here:
http://sbf.droid-developers.org/phone.php?device=0
However, if you have the Moto X 2014 RSDLite does not work and then you have to use adb commands and install it manually. To date, however, the Moto X 2014 is only a firmware that you can download from here:
http://sbf.droid-developers.org/phone.php?device=37
Hope of signing helped.
I too would like to know what the commands are to flash the phone back to stock via ADB.
I have tried RSD Lite with no success (device is not recognized)
I have tried the tool found here in the Android Development Forum with no success. The phone is back to stock ie. firmware, recovery, boot logo, etc. but SuperSU is still installed and does not respond to the full unroot command. In addition in Fastboot my software status is modified and the bootloader is still unlocked.
If you open the xml file all the commands for fastboot should be listed. They need to be run while in fastboot mode
shane1 said:
If you open the xml file all the commands for fastboot should be listed. They need to be run while in fastboot mode
Click to expand...
Click to collapse
This is what I see in the XML file. Is there an easy to decipher what I would type at the CMD prompt? It looks like I type what is in "quotations" with a preceding fastboot.
What command do I start at? Is it the line "flash" partition="partition" filename="gpt.bin" or do I need to enter the lines above too?
Where do I stop? Is the last line I enter "erase" partition="clogo"
<phone_model model="victara"/>
<software_version version="victara_retbr-user 4.4.4 KXE21.187-30.3 3 release-keysMSM8974BP_2147.127.04.55R"/>
<sparsing max-sparse-size="268435456" enabled="true"/>
-<interfaces>
<interface name="AP"/>
</interfaces>
</header>
-<steps interface="AP">
<step var="max-sparse-size" operation="getvar"/>
<step var="fb_mode_set" operation="oem"/>
<step operation="flash" partition="partition" filename="gpt.bin" MD5="425fd971c01f06a55748351c9736632c"/>
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="5789a83488d5b48665b57a8e2871d76c"/>
<step operation="flash" partition="logo" filename="logo.bin" MD5="95483d7b99d80cbe95bf85dbfb6615a8"/>
<step operation="flash" partition="boot" filename="boot.img" MD5="5d4d32ef9e9bba969b65d435a30dca55"/>
<step operation="flash" partition="recovery" filename="recovery.img" MD5="2c51aaa9b338526a9ff7a051f8d72075"/>
<step operation="flash" partition="system" filename="system.img_sparsechunk.0" MD5="6bb83c5068477c90955593c9932bc0bf"/>
<step operation="flash" partition="system" filename="system.img_sparsechunk.1" MD5="410bc6efa9d44f4e5ea27cf77fbef8f7"/>
<step operation="flash" partition="system" filename="system.img_sparsechunk.2" MD5="57e32da8507b1dfb51f701790680760d"/>
<step operation="flash" partition="system" filename="system.img_sparsechunk.3" MD5="efc731e070fe8f21a29eac9f9fdb391b"/>
<step operation="flash" partition="system" filename="system.img_sparsechunk.4" MD5="e0fb68a662ea1c7224f71584685b981e"/>
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="800dc7d555e23394c0c34519d922a028"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="70a133521d5a135bfd8af614173f3827"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="customize"/>
<step operation="erase" partition="clogo"/>
<step var="fb_mode_clear" operation="oem"/>
Example : " <step operation="flash" partition="partition" filename="gpt.bin" MD5="425fd971c01f06a55748351c9736632c"/>".
Fastboot flash partition gpt.bin
Theyve changed the wording a bit but should be the same. If you want to flash you run the fastboot commands for all the ones that day "flash" and you also run the ones that say "erase" unless you want to keep your data. Good luck and if you flash theres probably no turning back.
in order for rsd to see you phone you need to update to rsd6.2.4 and usbdrivers6.4

[Q] Flashing Moto Maxx Back to Stock using RSDLite

Hey guys,
I'm preparing to flash my Moto Maxx (from Puerto Rico) back to stock, and have been getting the required components. I've been advised to flash the stock firmware using RSDLite, which I've downloaded.
I've also downloaded the firmware file (AMXPR_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-CLALASL_CFC) from MotoFirmware. I got curious and unpacked the file, and poked around. I received further advice to edit the .xml file, just so I'm only flashing /system/ /recovery/ and /boot/ and remove a few lines from the .xml file.
Here's what I've got after editing the .xml file; and would love to get a-OK if I've done this right:
Code:
<?xml version="1.0" ?>
<flashing>
<header>
<phone_model model="quark"/>
<software_version version="quark_amxpr-user 4.4.4 KXG21.50-9 6 release-keysMDM9625_104335.118.02.54R"/>
<sparsing enabled="true" max-sparse-size="268435456"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step MD5="8e8422957d0511fb8a19d7c9cfcfd110" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="b5958a2059d39bffeff47e3613a97721" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="a3b58864f06052cc6ac36d86191d6a56" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="74a638ceb30e684df058e9abe0345dfe" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="dfb7f2c6d9523d99dce6efcdaf0927a9" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="c59674f83509363a6233174d96620532" filename="system.img_sparsechunk.3" operation="flash" partition="system"/>
<step MD5="6445ccbc56edbea2c53d94388d88bb49" filename="system.img_sparsechunk.4" operation="flash" partition="system"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="clogo"/>
</steps>
</flashing>
Cheers!
Code:
<?xml version="1.0"?>
-<flashing>
-<header>
<phone_model model="quark"/>
<software_version version="quark_amxpr-user 4.4.4 KXG21.50-9 6 release-keysMDM9625_104335.118.02.54R"/>
<subsidy_lock_config name="slcf_rev_a_clalasl_v1.0.nvm" MD5="70a839740b65a133bea545607829c1cd"/>
<sparsing max-sparse-size="268435456" enabled="true"/>
-<interfaces>
<interface name="AP"/>
</interfaces>
</header>
-<steps interface="AP">
<step var="max-sparse-size" operation="getvar"/>
<step var="fb_mode_set" operation="oem"/>
<step MD5="62980e8cf3e6638a9f6fb09454abb428" operation="flash" partition="partition" filename="gpt.bin"/>
<step MD5="c53a4172ee6706406291ae0e74c768ad" operation="flash" partition="motoboot" filename="bootloader.img"/>
<step MD5="d4ae0c76d0c32f7211bd8ed435c228da" operation="flash" partition="radio" filename="radio.img"/>
<step MD5="dccbc0c11265f98336602f1bb5e755cb" operation="flash" partition="logo" filename="logo.bin"/>
<step MD5="8e8422957d0511fb8a19d7c9cfcfd110" operation="flash" partition="boot" filename="boot.img"/>
<step MD5="b5958a2059d39bffeff47e3613a97721" operation="flash" partition="recovery" filename="recovery.img"/>
<step MD5="a3b58864f06052cc6ac36d86191d6a56" operation="flash" partition="system" filename="system.img_sparsechunk.0"/>
<step MD5="74a638ceb30e684df058e9abe0345dfe" operation="flash" partition="system" filename="system.img_sparsechunk.1"/>
<step MD5="dfb7f2c6d9523d99dce6efcdaf0927a9" operation="flash" partition="system" filename="system.img_sparsechunk.2"/>
<step MD5="c59674f83509363a6233174d96620532" operation="flash" partition="system" filename="system.img_sparsechunk.3"/>
<step MD5="6445ccbc56edbea2c53d94388d88bb49" operation="flash" partition="system" filename="system.img_sparsechunk.4"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="clogo"/>
<step var="fb_mode_clear" operation="oem"/>
</steps>
</flashing>
something missing

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>

Categories

Resources