Hi Everyone,
First of all, you are welcome to bash my noobness to the moon and back.
I have a VZW DE Moto X, Unlocked Bootloader. I accepted the 4.4.2 OTA update today and it broke Rootcloak for this app that I use, so I decided that I was going to SBF back to 4.4 (I know, mistake #1). So I followed the reference guide to a T to "return device back to stock" and once I was done running the commands, I booted up the phone and now it is in funky colors and I cannot read the display.
So here's where I'm at: I do have two TWRP recoveries on my PC, one from 4.4 and one from 4.4.2. I do have TWRP recovery on the phone, but since I did a device wipe I don't have the recoveries on my phone. Lastly, I can't get ADB to recognize my device now when it is in fastboot mode. so I don't know how to get the recoveries back on my phone. Can anyone save me? I would forever be grateful! :crying:
CartlandSmith said:
adb doesn't work in fastboot mode.
Can you boot into TWRP?
Click to expand...
Click to collapse
yes I can boot into TWRP
No it is gone... there is nothing there
CartlandSmith said:
While in TWRP, connect your phone to your PC via USB cable and open a command prompt in windows and then navigate to where you have adb.exe on your PC. Then type adb devices. Do you see your phone's serial number?
Click to expand...
Click to collapse
No.. it says list of devices attached and there is nothing.
I guess my only question is; how can I flash this if I can't send ADB commands to my phone?
dkoon1987 said:
I guess my only question is; how can I flash this if I can't send ADB commands to my phone?
Click to expand...
Click to collapse
download RSD Lite.
Unzip the file and use the XML file in RSD Lite. The unofficial one I used was pre-rooted.
CartlandSmith said:
you flash in fastboot mode using motorola's fastboot. You said you could get into fastboot mode, right?
The motorola fastboot is in the zip from what he said. I am downloading it now I will check.
Click to expand...
Click to collapse
There seems to be no mfastboot in his zip... I've got it downloaded and I'm reviewing the XML file for the fastboot commands... here is what is contains:
<step operation="flash" partition="partition" filename="gpt.bin" MD5="DA86065451752C9FAA4EE3AE41E91EE5" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="9C2172736B46F2B15CAC2E2A3B3A8974" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="144CEB8AB2DD962B5D304434383E8D5A" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="40CF68C879ADDC29671D9E7834BACCC7" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="A4E0ED1376D8468C7C353795D3D91D5F" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="D955C418C4F1C2F2D126575BF52CC9AF" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="933F1588597DD5D9A3D3E26F59957D38" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="5C8C2A8BA7F9E6F77DF5BEC5481A31A9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="B813274A74FF1278A41C19905E76768B" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="9A3EA0D90080200826EE7B50164012BF" />
<step operation="flash" partition="system" filename="system.img" MD5="C4579F834CB69D40E93DEDEBE95ABDBB" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="B98C55D09B5650EE93E49A6252AD7B41" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="EC92255E54062C65AE72A4926361429B" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
Should I flash these all?
Yes you can flash them, you could remove this command if you don't want it to wipe all your installed apps and files:
<step operation="erase" partition="userdata" />
rebretz000 said:
download RSD Lite.
Unzip the file and use the XML file in RSD Lite. The unofficial one I used was pre-rooted.
Click to expand...
Click to collapse
I downloaded RSD lite but I couldn't get my device to show in the list... any ideas?
dkoon1987 said:
I downloaded RSD lite but I couldn't get my device to show in the list... any ideas?
Click to expand...
Click to collapse
You should be able to recover from this as I believe I had the same or similar issue. I had horizontal lines through the boot operation then the screen would go black and I would have to hold the power button down for several seconds before I could get into recovery. I used fastboot to reinstall the fxz linked above and am back up and running. I actually did it twice while trying to push the tether hack. the only difference is that I never installed the new bootloader or GPT.
Sent from my SM-P600 using Tapatalk
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
dkoon1987 said:
I downloaded RSD lite but I couldn't get my device to show in the list... any ideas?
Click to expand...
Click to collapse
Extract the files and use fast boot to install its actually easier than RSD Lite.
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
If you have to flash manually:
fastboot flash partition gpt.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
etc.
Just do them in order.
Click to expand...
Click to collapse
don't forget mfastboot for system.img.ext4 but I'm not sure it's necessary
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
well it looked to me like Q9Nap included motorola's fastboot but he just called it fastboot. I can tell by the size of the file (210kB) that is it not Google's standard fastboot (157kB). He said he included it for windows, linux and darwin.
Click to expand...
Click to collapse
I made a rescue folder on my server with all images and files before I got the phone so I use my own fastboot files. In any event I'm 99% certain he'll recover just fine from this.
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
got it. I am sure that fastboot.exe in the windows subdirectory is motorola's fastboot for windows.
ITA and if he does, he should send a few dollars Q9Naps way since he would have had to wait for the sbf firmware or factory images otherwise.
Click to expand...
Click to collapse
Ahhhh!!! The X is alive! You guys are the bomb! I don't think you know how much I appreciate this! Thank you so much! And thank you for pointing me to Q9Naps thread as well!
edthesped said:
I made a rescue folder on my server with all images and files before I got the phone so I use my own fastboot files. In any event I'm 99% certain he'll recover just fine from this.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
So guys... now that I am back to factory... should I be able to restore my backup from 4.4? And then eventually take the OTA? Or should I just stop playing with fire.
CartlandSmith said:
got it. I am sure that fastboot.exe in the windows subdirectory is motorola's fastboot for windows.
ITA and if he does, he should send a few dollars Q9Naps way since he would have had to wait for the sbf firmware or factory images otherwise.
Click to expand...
Click to collapse
And I will be sending some dough his way :good:
dkoon1987 said:
So guys... now that I am back to factory... should I be able to restore my backup from 4.4? And then eventually take the OTA? Or should I just stop playing with fire.
Click to expand...
Click to collapse
I don't believe you can go back because of the bootloader, you can always try but you may end up redo ing the fastboot thing. The fxz is true 4.4.2 so there really is no reason to go back
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
I would be careful with the 4.4 nandroid and no, don't take the 4.4.2 OTA if you are on the 4.4. system but the 4.4.2 bootloader. If you restore to the 4.4 system but are on the 4.4.2 bootloader, you will brick your device if you take the 4.4.2 OTA from what I have read. This is because the 4.4.2 OTA will be trying to patch the 4.4 bootloader and partition table but you are already on the 4.4.2 bootloader and partition table.
http://forum.xda-developers.com/moto-x/moto-x-qa/running-4-4-4-4-2-unlocked-bootloader-t2665531
Anyhow, if you restore to 4.4, but freeze the OTA app and don't take the 4.4.2 OTA unless you are back on 4.4.2 stock.
Click to expand...
Click to collapse
Can he restore it? Also do you still have twrp installed? If so you should be protected. If you just want your data back you can restore then push 4.4.2 with fastboot without any of the erase commands and be upgraded.
Sent from my SM-P600 using Tapatalk
dkoon1987 said:
And I will be sending some dough his way :good:
Click to expand...
Click to collapse
so where's my money? haha just kidding
edthesped said:
I don't believe you can go back because of the bootloader, you can always try but you may end up redo ing the fastboot thing. The fxz is true 4.4.2 so there really is no reason to go back
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
unlocked devices ARE able to downgrade to 4.4, probably 4.2.2 as well; read the updated op and the rest of the thread for details. it's not that much reading.
CartlandSmith said:
I would be careful with the 4.4 nandroid and no, don't take the 4.4.2 OTA if you are on the 4.4. system but the 4.4.2 bootloader. If you restore to the 4.4 system but are on the 4.4.2 bootloader, you will brick your device if you take the 4.4.2 OTA from what I have read. This is because the 4.4.2 OTA will be trying to patch the 4.4 bootloader and partition table but you are already on the 4.4.2 bootloader and partition table.
http://forum.xda-developers.com/moto-x/moto-x-qa/running-4-4-4-4-2-unlocked-bootloader-t2665531
Anyhow, if you restore to 4.4, but freeze the OTA app and don't take the 4.4.2 OTA unless you are back on 4.4.2 stock.
Click to expand...
Click to collapse
you CAN reapply the ota after flashing back to 4.4. the updater script sees that the motoboot parts and gpt are already upgraded and just skips them; you will not brick.
Q9Nap said:
unlocked devices ARE able to downgrade to 4.4, probably 4.2.2 as well; read the updated op and the rest of the thread for details. it's not that much reading.
Click to expand...
Click to collapse
Going to do that now.
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
Ok, good to know. Everyone is scaring me so much on these forums that I will brick my device that I am afraid to even take the OTA myself, lol! I froze the OTA app for now until I am sure I understand the fire I am playing with.
Click to expand...
Click to collapse
Yes this forum is full of conjecture. And at this point I may be adding to it. The whole bootloader thing is a nightmare.
Sent from my SM-P600 using Tapatalk
Related
I have an AT&T Moto X, and was happily running the 4.2.2 OTA camera update rooted. I unwittingly pressed install update to upgrade to KitKat, and now am stuck in a bootloop. Whenever the phone turns on, it immediately reboots, and keeps going in this cycle. I've tried to do factory resets from settings, but it reboots again and does the same thing. I can't even boot to recovery from power off, it just goes through the same cycle. Can anyone help me?
kuz142 said:
I have an AT&T Moto X, and was happily running the 4.2.2 OTA camera update rooted. I unwittingly pressed install update to upgrade to KitKat, and now am stuck in a bootloop. Whenever the phone turns on, it immediately reboots, and keeps going in this cycle. I've tried to do factory resets from settings, but it reboots again and does the same thing. I can't even boot to recovery from power off, it just goes through the same cycle. Can anyone help me?
Click to expand...
Click to collapse
Fastboot erase cache
Sent on my Moto X
flashallthetime said:
Fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
I am having the reverse issue. I can't flash 4.2.2 (Tmobile) without bootloop. I did Fastboot erase cache and tried again but still no success. I have to flash back to 4.4 to have a functioning device.
ohmimpotence said:
I am having the reverse issue. I can't flash 4.2.2 (Tmobile) without bootloop. I did Fastboot erase cache and tried again but still no success. I have to flash back to 4.4 to have a functioning device.
Click to expand...
Click to collapse
Is your boot loader unlocked?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Is your boot loader unlocked?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
No, I'm trying to avoid unlocking my bootloader so I don't void the warranty. I'd prefer to root using SlapMyMoto.
ohmimpotence said:
No, I'm trying to avoid unlocking my bootloader so I don't void the warranty. I'd prefer to root using SlapMyMoto.
Click to expand...
Click to collapse
OK in the XML file is therens a line that erases use data and cache?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
OK in the XML file is therens a line that erases use data and cache?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
There's actually no line that erases user data, the only erase sections are
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
I edited the xml to remove the <step operation="getvar" var="max-download-size" /> line
It worked fine for when I edited the 4.4 OTA, I got them both from Motorola at https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images for 4.2.2 I'm using JB 4.2.2-13.9.0Q2.X-116-17-57-6 which is the camera fix update
ohmimpotence said:
There's actually no line that erases user data, the only erase sections are
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
I edited the xml to remove the <step operation="getvar" var="max-download-size" /> line
It worked fine for when I edited the 4.4 OTA, I got them both from Motorola at https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images for 4.2.2 I'm using JB 4.2.2-13.9.0Q2.X-116-17-57-6 which is the camera fix update
Click to expand...
Click to collapse
You need to delete userdata and cache, that's probably why you're having boot problems
Sent from my A2109A using Tapatalk 4
flashallthetime said:
You need to delete userdata and cache, that's probably why you're having boot problems
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
I'm going by Option 3 in this thread
I guess if I just fastboot erase cache and add "<step operation="erase" partition="userdata" />" to the xml perhaps it will be successful. Any idea where in the xml I need to add it? where they other erase lines are I would imagine? those are right before it does <step operation="flash" partition="fsg" filename="fsg.mbn" MD5="6C15610C6579346B34991186673F3125" />
Update: Yup, I needed to add that line, THANKS!
ohmimpotence said:
I'm going by Option 3 in this thread
I guess if I just fastboot erase cache and add "<step operation="erase" partition="userdata" />" to the xml perhaps it will be successful. Any idea where in the xml I need to add it? where they other erase lines are I would imagine? those are right before it does <step operation="flash" partition="fsg" filename="fsg.mbn" MD5="6C15610C6579346B34991186673F3125" />
It's not a big deal if I lose userdata, I was just hoping I wouldn't have to but at this point to get 4.2.2 to boot properly I'd be fine with it, just wish there were some certainty it would work for sure.
Click to expand...
Click to collapse
I believe the lines are the last instructions for rsdlite?
It sounds like it worked fine but the only thing that wasn't attempted was erasing the cache and data, so I'm assuming that's why it won't boot. The last time I rsdlite I went from the at&t kitkat firmware to the T-Mobile version, I did not erase userdata and I had all kinds of FC's , reboots and warnings
Sent from my A2109A using Tapatalk 4
flashallthetime said:
I believe the lines are the last instructions for rsdlite?
It sounds like it worked fine but the only thing that wasn't attempted was erasing the cache and data, so I'm assuming that's why it won't boot. The last time I rsdlite I went from the at&t kitkat firmware to the T-Mobile version, I did not erase userdata and I had all kinds of FC's , reboots and warnings
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
It worked now, you were definitely right. Unfortunately I gave out my limit of 8 Thanks a day so I'll be sure to check back tomorrow to hit you up. Appreciate it!
Just glad it worked:beer::thumbup:
Sent from my A2109A using Tapatalk 4
Any way to force or restart the update?
OR...since I have a dev edition and am unlocked. Can I just go through the following procedure with the latest stock files from motorola to get on 4.4 (I downloaded MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml from their google drive).
adb flash partition gpt.bin
...etc etc one step at a time in the below order?
Sorry I'm new to this
"flash" partition="partition" filename="gpt.bin"
"flash" partition="motoboot" filename="motoboot.img"
"reboot-bootloader"
"flash" partition="logo" filename="logo.bin"
"flash" partition="boot" filename="boot.img"
"flash" partition="recovery" filename="recovery.img"
"flash" partition="system" filename="system.img"
"flash" partition="modem" filename="NON-HLOS.bin"
"erase" partition="modemst1"
"erase" partition="modemst2"
"flash" partition="fsg" filename="fsg.mbn"
Click to expand...
Click to collapse
You could just reboot the phone.
Sent from my XT1060 using Tapatalk
Restola said:
OR...since I have a dev edition and am unlocked. Can I just go through the following procedure with the latest stock files from motorola to get on 4.4 (I downloaded MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml from their google drive).
adb flash partition gpt.bin
...etc etc one step at a time in the below order?
Sorry I'm new to this
Click to expand...
Click to collapse
you can do it that way if you want and it will install with no problem i have had a couple people who just could not get the 4.4 OTA to install so i know it works
I purchased a new XT1058 from pre-owner who flash a unknown firmware to original Claro Puerto Rico ROM.
System cannot boot now.
I try to flash original ( CLARO-PR_XT1058_4.2.2-13.9.0Q2.X-116-LCX-35_cid12_CFC_1FF_svc.xml ) ROM with RSD but get error:
Failes flash partition gpt.bin
Details on phone screen:
AP Fastboot Flash mode (S)
Device is Locked.Status code:0
Errors:
Downgraded security version
update gpt_main version failed
Prefalsh validation failed for gpt
Any idea for first step to unbrick?
Kind regards
zsebob said:
I purchased a new XT1058 from pre-owner who flash a unknown firmware to original Claro Puerto Rico ROM.
System cannot boot now.
I try to flash original ( CLARO-PR_XT1058_4.2.2-13.9.0Q2.X-116-LCX-35_cid12_CFC_1FF_svc.xml ) ROM with RSD but get error:
Failes flash partition gpt.bin
Details on phone screen:
AP Fastboot Flash mode (S)
Device is Locked.Status code:0
Errors:
Downgraded security version
update gpt_main version failed
Prefalsh validation failed for gpt
Any idea for first step to unbrick?
Kind regards
Click to expand...
Click to collapse
EDIT: I can unlock bootloader and can flash the new UK retail firmware but no network here ( Hungary EU )
How can I flash the right ROM for mobile network?
zsebob said:
EDIT: I can unlock bootloader and can flash the new UK retail firmware but no network here ( Hungary EU )
How can I flash the right ROM for mobile network?
Click to expand...
Click to collapse
Is the phone branded for a specific carrier? Usually you'll have to flash the carrier ROM to match the branded phone. Does the phone boot at all?
titanshadow said:
Is the phone branded for a specific carrier? Usually you'll have to flash the carrier ROM to match the branded phone. Does the phone boot at all?
Click to expand...
Click to collapse
Yes, can boot as well to UK retail now, but cannot networking, no radio. Original Latin Claro Puerto Rico device XT1058.
I try to flash original ROM but get error in RSD on phone screen:
Downgraded security version
update gpt_main version failed
Prefalsh validation failed for gpt
zsebob said:
Yes, can boot as well to UK retail now, but cannot networking, no radio. Original Latin Claro Puerto Rico device XT1058.
I try to flash original ROM but get error in RSD on phone screen:
Downgraded security version
update gpt_main version failed
Prefalsh validation failed for gpt
Click to expand...
Click to collapse
Looks like it was flashed to 4.4 by that error and you're trying to flash 4.2.2? If you're unlocked try just flashing the boot, system and recovery images or get a 4.4 image
Here just in time http://forum.xda-developers.com/showthread.php?t=2629057
Sent on my Moto X
BladeRunner said:
Looks like it was flashed to 4.4 by that error and you're trying to flash 4.2.2? If you're unlocked try just flashing the boot, system and recovery images or get a 4.4 image
Click to expand...
Click to collapse
I dont find the Latin ROM with 4.4 just 4.2.2.
How can I start the working radio?
zsebob said:
I dont find the Latin ROM with 4.4 just 4.2.2.
How can I start the working radio?
Click to expand...
Click to collapse
try flashing the modem: fastboot flash modem NON-HLOS.bin
zsebob said:
I dont find the Latin ROM with 4.4 just 4.2.2.
How can I start the working radio?
Click to expand...
Click to collapse
Sounds like whoever had to before you flashed something strange to it. You should take a look at the link provided in an above post about resurrecting a bricked device. Looks complicated to me but it might be what you've got to do. The problem you're looking at seems to be that the bootloader is locked.
I did notice that there are two firmwares for your brand of device on this URL:
http://sbf.droid-developers.org/phone.php?device=0
One is version Blur_Version.139.12.35.ghost_row.AmericaMovil.en.PR and the other is Blur_Version.139.7.26.ghost_row.AmericaMovil.en.PR, I've bolded the version numbers. I would download and try to flash them both. Also from my own experience don't change the file name either (you probably didn't, but it should be said anyway) since they are likely signed and I've had serious problems with trying to flash firmwares where I changed the file name.
If you can't get RDS to work, try this method here, http://forum.xda-developers.com/showthread.php?t=2446515 which covers both RDS and my favorite the mfastboot method. Now you'll have to do a little work yourself since this guide is for Verizon but there is an XML file inside the zipped update file that you should be able to pull the information you need out of. Inside the XML file you'll see a series of "Steps" (they look like this:
Code:
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="4C9F15C80FED62BAB7A042FDBA4D7A2F" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="34B3A02418240C805CCB2998B2343261" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="1F8DBC99E41DFB7596DBC78687AC5E7B" />
<step operation="flash" partition="boot" filename="boot.img" MD5="49C02FCD26133923B1B4F2CFE862C422" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="62DCB8F941BEC9D824146453834CD3FE" />
<step operation="flash" partition="system" filename="system.img" MD5="1D5214E5171BE9894D0413322D2DD211" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="57B83F54B07922B9CBAF3C4125CBA8A1" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="BAB00624486527FE415D8BACFF875C99" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="config carrier vzw" />
<step operation="oem" var="fb_mode_clear" />
Your XML will look similar, but different. The main difference is going to be the "config carrier vzw" line, I don't have the XML file from your update but to give you an idea on how this translates, here is the sequence of commands to manually flash the Verizon update (derrived from the XML file contents above):
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem non-hlos.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem config carrier vzw
mfastboot oem fb_mode_clear
mfastboot reboot
If you take these two sections (the commands and the XML) you should be able to see how to get the commands from the XML and turn them into mfastboot commands. My little bit of research (please understand I did like 2 minutes of quick looking around) suggests that the only real difference is going to be the line containing "oem config carrier vzw" and the sequence is important so you'll notice the XML has the same sequence as the list of commands, you should find what to replace the config carrier command by looking right after erase clogo and right before fb_mode_clear in your own XML file. If you need any help doing this, let me know and I'll do my best.
If that fails, however, you may need to look into unlocking your bootloader, which I haven't personally done, but I have read a number of people who have done it. The best way is, if your device is supported, to use this method here (the official Motorola method):
https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth
Anyway, that is the best I've got. I hope something works for you, you may also want to see if you can get ahold of who sold you the device and find out if they did anything strange to the device - like flashing a non-standard firmware or some such.
BladeRunner said:
try flashing the modem: fastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
i agree with this guys sounds like previous owner flashed a 4.4 or 4.4.2 rom so now that you have the UK rom up and running all you need to do is download the 4.2.2 rom for your phone and just flash the modem file and reboot your device and you should have youe data and other stuff back.
Dear ALL: Problem solved! I can flash the modem files with RSD from different version of original ROM.
THANKS FOR YOUR ALL HELP!!!!!!!!
Hi everyone!!
I was wondering if you could help me. I am a bit of a noob in this flashing phones, so here it goes:
I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked . I am getting very similar errors like this similar thread and it now appears to be Device LOCKED: http://forum.xda-developers.com/moto-x/moto-x-qa/bootloader-bricked-recovered-fail-t2634982/page8
I saw they did something like flashing separate partitions to get it at some point that you could unlock it again or something.
Could you please help me? I am very desperate
Thanks!
I think your phone is full bricked.
I'm from Mexico too
Enviado desde mi XT1053 mediante Tapatalk
motox1983 said:
Hi everyone!!
I was wondering if you could help me. I am a bit of a noob in this flashing phones, so here it goes:
I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked . I am getting very similar errors like this similar thread and it now appears to be Device LOCKED: http://forum.xda-developers.com/moto-x/moto-x-qa/bootloader-bricked-recovered-fail-t2634982/page8
I saw they did something like flashing separate partitions to get it at some point that you could unlock it again or something.
Could you please help me? I am very desperate
Thanks!
Click to expand...
Click to collapse
Assuming you can get to the bootloader screen, you can TRY using RSD Lite or manual method to flash the 4.4.2 SBF:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Just make sure you use the 4.4.2 SBF File for your carrier from here: sbf.droid-developers.org/phone.php?device=0
Good Luck
EDIT: Reading through the thread you linked, it looks like the key was to FIRST, JUST flash the gpt & motoboot.
So using manual method,
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
NEXT, Reboot BEFORE continuing (mfastboot reboot-bootloader)
THEN, you can use the RSD Lite method, or the manual method in the thread I linked.
Let us know if this helps.
motox1983 said:
I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked .
Click to expand...
Click to collapse
So you had 4.4.2, downgraded to 4.4, and taking the OTA caused you to brick?
That is why there are warnings to NOT downgrade (to 4.4 or below) once you have 4.4.2 on your phone...
What @samwathegreat suggested (using mfastboot to flash gpt.bin and motoboot.img first, then RSDLite to flash full 4.4.2 SBF for your carrier) should hopefully work.
Try and charge your phone to above 80% if at all possible before you start.
It lives now!!!
samwathegreat said:
Assuming you can get to the bootloader screen, you can TRY using RSD Lite or manual method to flash the 4.4.2 SBF:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Just make sure you use the 4.4.2 SBF File for your carrier from here: sbf.droid-developers.org/phone.php?device=0
Good Luck
EDIT: Reading through the thread you linked, it looks like the key was to FIRST, JUST flash the gpt & motoboot.
So using manual method,
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
NEXT, Reboot BEFORE continuing (adb reboot bootloader)
THEN, you can use the RSD Lite method, or the manual method in the thread I linked.
Let us know if this helps.
Click to expand...
Click to collapse
Thanks a lot samwathegreat. It helped me change the DEVICE Status to UNLOCKED again, but now I am in a bootloop. It boots every couple of minutes or so. I am going to try a full 4.4.2 flash with RSD Lite to see if it solves. What other reason would you think it would be?
The key is the reboot to boot loader after flashing the gpt.bin and Moto boot.img. That will allow the new boot loader to continue flashing the rest of the images.
You have a mismatched aboot image and it is incompatible with the new images and reports as locked and cannot flash any images until the proper aboot is flashed and the device reboots into the new boot loader.
Edit: I see you have gotten past the boot loader issue already.
Just flash the full XML.zip with RSD Lite and you will be fine.
Bad news
cellzealot said:
The key is the reboot to boot loader after flashing the gpt.bin and Moto boot.img. That will allow the new boot loader to continue flashing the rest of the images.
You have a mismatched aboot image and it is incompatible with the new images and reports as locked and cannot flash any images until the proper aboot is flashed and the device reboots into the new boot loader.
Edit: I see you have gotten past the boot loader issue already.
Just flash the full XML.zip with RSD Lite and you will be fine.
Click to expand...
Click to collapse
Hey guys, bad news. I flashed what it supposed to be the full XML.zip from the sbf droid-developers web page (I am not allowed to post URL links yet) and it all seemed well, but when I turned it off and then back on, it got again into a bootloop, rebooting every couple of minutes . What do you think it would be the reason? I am from Mexico, so I used the Telcel Mexico 4.4.2 firmware, so I don't use any firmware below 4.4 (the other two options are 4.2.2). I noticed that the Telcel 4.2.2 has more files than the Telcel 4.4.2. Any suggestions? Should I try to flash other firmwares?
motox1983 said:
Hey guys, bad news. I flashed what it supposed to be the full XML.zip from the sbf droid-developers web page (I am not allowed to post URL links yet) and it all seemed well, but when I turned it off and then back on, it got again into a bootloop, rebooting every couple of minutes . What do you think it would be the reason? I am from Mexico, so I used the Telcel Mexico 4.4.2 firmware, so I don't use any firmware below 4.4 (the other two options are 4.2.2). I noticed that the Telcel 4.2.2 has more files than the Telcel 4.4.2. Any suggestions? Should I try to flash other firmwares?
Click to expand...
Click to collapse
Is the Telcel Mexico 4.4.2 what you were running when you first got the phone and it was on 4.4.2?
Based on what cellzealot said.. try this...
First, make sure you are using the latest mFastboot.EXE -> download mFastboot, and unzip it. It has folders containing the Windows, Linux and Mac versions of Moto's fastboot.exe. After unzipping, find the windows version of the moto fastboot.exe, rename it to mfastboot.exe (so you don't mix it up with the one that comes with the Android SDK) and move it in your Android SDK Platform Tools folder.. usually C:\Android-Sdk\platform-tools.
Open a command prompt and change to the folder where you unziped the SBF to, and run the following...
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
EDIT the XML from the SBF. and look for the following lines...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxx" />
and right after it, add...
<step operation="reboot">
save it.
Then use RSDLite to flash the entire XML.
KidJoe said:
Is the Telcel Mexico 4.4.2 what you were running when you first got the phone and it was on 4.4.2?
Based on what cellzealot said.. try this...
First, make sure you are using the latest mFastboot.EXE -> download ..., and unzip it. It has folders containing the Windows, Linux and Mac versions of Moto's fastboot.exe. After unzipping, find the windows version of the moto fastboot.exe, rename it to mfastboot.exe (so you don't mix it up with the one that comes with the Android SDK) and move it in your Android SDK Platform Tools folder.. usually C:\Android-Sdk\platform-tools.
Open a command prompt and change to the folder where you unziped the SBF to, and run the following...
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
EDIT the XML from the SBF. and look for the following lines...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxx" />
and right after it, add...
<step operation="reboot">
save it.
Then use RSDLite to flash the entire XML.
Click to expand...
Click to collapse
I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).
Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?
I flashed separately. First edited the XML to flash only gpt and motoboot and rebooted to fastboot. Then modified again XML so it would flash the rest of the SBF. I will see how it works.
motox1983 said:
I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).
Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?
Click to expand...
Click to collapse
I ask about the version because, to play it safer, we want to make sure you are flashing the SBF of what was on your phone... No matter what way the phone got to 4.4.2, the SBF you are using should be of the same 4.4.2 that was on your phone. i.e. don't flash a T-Mobile 4.4.2 if you started out with a Telcel 4.4.2 rom on your phone. And don't flash a Telcel 4.4.2 if you had a Movistar 4.4.2 rom on there.
Post the contents of the XML, its easier to see what might be wrong with it. Or post the original, un-edited XML, and I will make the edits for you.
motox1983 said:
I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).
Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?
Click to expand...
Click to collapse
Do this instead:
Once you have flashed the gpt.bin and motoboot.img, type "mfastboot reboot-bootloader"
Phone will reboot back into bootloader.
Now, assuming you have extracted the contents of the SBF file to the same folder where fastboot and mfastboot reside, run these commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Now reboot. Is everything back to normal?
KidJoe said:
I ask about the version because, to play it safer, we want to make sure you are flashing the SBF of what was on your phone... No matter what way the phone got to 4.4.2, the SBF you are using should be of the same 4.4.2 that was on your phone. i.e. don't flash a T-Mobile 4.4.2 if you started out with a Telcel 4.4.2 rom on your phone. And don't flash a Telcel 4.4.2 if you had a Movistar 4.4.2 rom on there.
Post the contents of the XML, its easier to see what might be wrong with it. Or post the original, un-edited XML, and I will make the edits for you.
Click to expand...
Click to collapse
This is the XML: When I open it as it comes when I downloaded, It does not get the error, but when I add the line you told me, it gets the error:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_amxmx-user 4.4.2 KXA20.16-1.26 23 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="7ed24e75a2bfb3f8c02be2a269e9881b" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="167bd75bf0414558616f2a5343f7d1f4" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="96acde1a2233244bbf9828cfa041cb75" />
<step operation="flash" partition="system" filename="system.img" MD5="cf6d51b5ae957d150a693cbf3eef4432" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="f247fbd71d9a80821ecdc952c9116893" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="e50401645391cc7acfb96163748d966f" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Click to expand...
Click to collapse
samwathegreat said:
Do this instead:
Once you have flashed the gpt.bin and motoboot.img, type "mfastboot reboot-bootloader"
Phone will reboot back into bootloader.
Now, assuming you have extracted the contents of the SBF file to the same folder where fastboot and mfastboot reside, run these commands:....
Click to expand...
Click to collapse
@motox1983 yup, that is the other way.
Because if issues people had flashing logo.bin and recovery using the stock fastboot, I usually recommend using mfastboot instead of fastboot with the moto phones.
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
motox1983 said:
This is the XML: When I open it as it comes when I downloaded, It does not get the error, but when I add the line you told me, it gets the error:
Click to expand...
Click to collapse
Edited version..
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_amxmx-user 4.4.2 KXA20.16-1.26 23 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="7ed24e75a2bfb3f8c02be2a269e9881b" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation="reboot">
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="167bd75bf0414558616f2a5343f7d1f4" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="96acde1a2233244bbf9828cfa041cb75" />
<step operation="flash" partition="system" filename="system.img" MD5="cf6d51b5ae957d150a693cbf3eef4432" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="f247fbd71d9a80821ecdc952c9116893" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="e50401645391cc7acfb96163748d966f" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
or use fastboot/mfastboot to do it manually as samwathegreat has just suggested.
KidJoe said:
@motox1983 yup, that is the other way.
Because if issues people had flashing logo.bin and recovery using the stock fastboot, I usually recommend using mfastboot instead of fastboot with the moto phones.
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Edited version..
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_amxmx-user 4.4.2 KXA20.16-1.26 23 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="7ed24e75a2bfb3f8c02be2a269e9881b" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation="reboot">
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="167bd75bf0414558616f2a5343f7d1f4" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="96acde1a2233244bbf9828cfa041cb75" />
<step operation="flash" partition="system" filename="system.img" MD5="cf6d51b5ae957d150a693cbf3eef4432" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="f247fbd71d9a80821ecdc952c9116893" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="e50401645391cc7acfb96163748d966f" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
or use fastboot/mfastboot to do it manually as samwathegreat has just suggested.
Click to expand...
Click to collapse
Still getting the error message . Will try the manual process and let you know. Thanks!
KidJoe said:
@motox1983 yup, that is the other way.
Because if issues people had flashing logo.bin and recovery using the stock fastboot, I usually recommend using mfastboot instead of fastboot with the moto phones.
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Edited version..
Click to expand...
Click to collapse
It looks like the proper syntax for the reboot is this:
<step operation="reboot-bootloader" />
Perhaps this is why he is getting the error from RSD Lite?
motox1983 said:
Still getting the error message . Will try the manual process and let you know. Thanks!
Click to expand...
Click to collapse
Once you have finished the manual method and reboot, it is normal for the first boot to take longer than usual.
samwathegreat said:
It looks like the proper syntax for the reboot is this:
<step operation="reboot-bootloader" />
Perhaps this is why he is getting the error from RSD Lite?
Click to expand...
Click to collapse
Could be. But I copied it directly from the XML of the Dev Edition 4.4.2 rom (which has it, where as the others up on SBF Dev.org, and the 4.4 and below SBF's are missing it)
samwathegreat said:
It looks like the proper syntax for the reboot is this:
<step operation="reboot-bootloader" />
Perhaps this is why he is getting the error from RSD Lite?
Once you have finished the manual method and reboot, it is normal for the first boot to take longer than usual.
Click to expand...
Click to collapse
Ok, so I finished the manual method and rebooted. I realised that if it is updating or downloading applications it wont reboot, so I stopped them all and after a couple of minutes it rebooted again. Now it has been about 10 min and it has not rebooted anymore. I am not sure if it is alright or is normal or what would be the reason for it to reboot again.
motox1983 said:
Ok, so I finished the manual method and rebooted. I realised that if it is updating or downloading applications it wont reboot, so I stopped them all and after a couple of minutes it rebooted again. Now it has been about 10 min and it has not rebooted anymore. I am not sure if it is alright or is normal or what would be the reason for it to reboot again.
Click to expand...
Click to collapse
So the phone is just randomly rebooting itself? Like it has crashed or something?
All I can say is give it a while and see if it continues to happen. Since we have returned your software to 100% stock, if your phone continues to randomly reboot, I would suspect a hardware issue...but it is difficult to tell.
If it doesn't happen again I wouldn't worry about it, but definitely post back and update us.
samwathegreat said:
So the phone is just randomly rebooting itself? Like it has crashed or something?
All I can say is give it a while and see if it continues to happen. Since we have returned your software to 100% stock, if your phone continues to randomly reboot, I would suspect a hardware issue...but it is difficult to tell.
If it doesn't happen again I wouldn't worry about it, but definitely post back and update us.
Click to expand...
Click to collapse
Ok it is rebooting again now, every couple of minutes I guess it would be a hardware problem. And obviously I lost the warranty when I unlocked. So no last ideas before I give up? hehe
motox1983 said:
Ok it is rebooting again now, every couple of minutes I guess it would be a hardware problem. And obviously I lost the warranty when I unlocked. So no last ideas before I give up? hehe
Click to expand...
Click to collapse
boot into recovery and wipe cache and dalvik
I recieved 5.1 OTA but want to go back to 4.4.4.
As I found out, Moto says, that we cant donwngrade to 4.4.4 with RSDlite. So I want to install TRWP and use a backup to install 4.4.4
In best case there is a backup of the Stock-Rom. Is there one? If not, which one is the one nearest to the stock (moto x features, ....)
if you want to use the motorola features than you need stock rom. ask someone to make twrp backup of system and boot running 4.4.4 and flash it in your device
T-1311 said:
I recieved 5.1 OTA but want to go back to 4.4.4.
As I found out, Moto says, that we cant donwngrade to 4.4.4 with RSDlite. So I want to install TRWP and use a backup to install 4.4.4
In best case there is a backup of the Stock-Rom. Is there one? If not, which one is the one nearest to the stock (moto x features, ....)
Click to expand...
Click to collapse
You can use this ROM or just delete few lines from XML in FW for RSD.
If You delete this lines
Code:
<step operation="getvar" var="max-download-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="e059929f2668935282b8248b028d015d" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="2b664024c8a421245b814e3b7c4c5077" filename="motoboot.img" operation="flash" partition="motoboot"/>
You can flash stock 4.4.4 ROM with RSD.
Really? I'm already on STOCK 5.1_OTA. As I wrote I can't flash 4.4.4 through RSDlite.
T-1311 said:
Really? I'm already on STOCK 5.1_OTA. As I wrote I can't flash 4.4.4 through RSDlite.
Click to expand...
Click to collapse
Is your phone bootloader locked? Hardware model, installed system version? More details, pls.
You could flash via fastboot then. Or I can give you 4.4.4 TWRP, but it's for unlocked only.
Sorry, here are the missing infos
XT1052
Bootloader locked (but will be unlocked soon)
Stock 5.1 recieved automaticaly OTA
Baseband MSM8960PRO_BP_23255.138.89.00R
System: 222.21.15.ghost_row_Retail.en.DE
LPA23.12-15
T-1311 said:
Sorry, here are the missing infos
Click to expand...
Click to collapse
Good. Now I get why can't you install via RSD. Unlock it as soon as possible, but don't flash anything (especially including bootloader). I'll give you TWRP flashable 4.4.4 today evening.
P.S. And I also need your byke and clothes modem dump ) Instructions will follow.
. . .
UPDATE. Well, it isn't ready yet (( But after unlock you can flash any system+boot easily by fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
But DON'T flash bootloader!!! It can brick the phone
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
Or similar in RSD:
<step operation="flash" partition="partition" filename="gpt.bin" MD5="e83806da807e62fd6ffa08e330abe582" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="2b664024c8a421245b814e3b7c4c5077" />