Database Develop

Stuck rebooting to TWRP after OTA Download?

I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?

reno55 said:
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
Click to expand...
Click to collapse
Try using Titanium Backup to freeze MotorolaOTA

samwathegreat said:
Try using Titanium Backup to freeze MotorolaOTA
Click to expand...
Click to collapse
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?

reno55 said:
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
Click to expand...
Click to collapse
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck

samwathegreat said:
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
Click to expand...
Click to collapse
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?

reno55 said:
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
Click to expand...
Click to collapse
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850

samwathegreat said:
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Click to expand...
Click to collapse
Can I flash philz?

reno55 said:
Can I flash philz?
Click to expand...
Click to collapse
Don't see why not. Just substitute the filename for philz recovery instead.
Get Philz here: http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
I have not used Philz personally...I prefer TWRP, but it looks like (unlike TWRP), that there is a different img for each variant of the Moto X. You will need to be careful to download the correct one.

I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup, TWRP and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is there no way to complete the OTA without flashing a stock recovery? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.

frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?

frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
YES, that is the best way to do it. You can -try- disabling xposed, and un-doing any major modifications you have done (like freezing or removing any system apps). You want it to be as close to stock as possible before you try to accept the OTA, which includes flashing back the stock recovery.
SBFing back to stock 4.4.2 FIRST, and accepting the update, THEN flashing TWRP and rooting, then re-configuring everything and installing your apps is MUCH safer and pretty much guarantees that your filesystem will be 100% intact.
If it were ME, I would SBF first -- for whatever that's worth...
Good Luck
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
reno55 said:
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
Click to expand...
Click to collapse
Sure. It's just slightly more complicated. You'll need the entire 4.4.2 SBF for your carrier.
Do this: Reboot to bootloader
FIRST, JUST flash gpt.bin and motoboot.img:
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Now you need to REBOOT back into bootloader (to prevent gpt.bin mis-match -- if you don't reboot here, you will get errors). Do this by typing:
mfastboot reboot-bootloader
Now flash the rest of the files:
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
Reboot, and you should be back to stock 4.4.2
And finally the disclaimer: DO NOT TRY TO DOWNGRADE TO ANY VERSION PRIOR TO 4.4.2 .....if you don't want a brick.
It's ok to downgrade 4.4.3 to 4.4.2 because the bootloader version did not change. It is NOT safe to downgrade to anything prior (4.4 or 4.2.2).

[Q] Looking for the SBF files for Moto X ( any firmware +4.4)

Now that I have an unlocked bootloader I was trying to update to the newest stock version. I had modded by /system so I was unable to do an easy OTA update. I was trying to flash a system.img from here for 4.4 since that is what I was running but then fastboot threw me an error. I think it was an issue with the file since I got this error
Anyone know where I can the sbf file for our phone? I need +4.4 since that is what I was running last.
Side Question: When using TWRP to back up what format does the usb drive need to be so I can put back ups on it? FAT32?
Thanks in advance for all help

Are you using motos custom fastboot to flash the system image? The image is too large for regular fastboot, moto fastboot breaks it up into chunks to flash properly
Sent from my XT1060

rocketsaucev2 said:
Are you using motos custom fastboot to flash the system image? The image is too large for regular fastboot, moto fastboot breaks it up into chunks to flash properly
Sent from my XT1060
Click to expand...
Click to collapse
So I was using the fastboot that comes with the sdk. Where can I download motos custom fastboot? Are there any important differences from regular fastboot?

Nitro made a zip that has everything you need including the mfasboot.exe
You will need to flash the system.img with the mfastboot command instead of fastboot.
https://www.elementalxdesigns.com/e...-Edition-install-TWRP-and-how-to-flash-images

Icon000 said:
So I was using the fastboot that comes with the sdk. Where can I download motos custom fastboot? Are there any important differences from regular fastboot?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B28ubovBBGskTnBlUl9reGFzQ1E/view?usp=sharing
heres a copy of mine. Make sure you put it in the same folder as your adb or regular fastboot and use the command 'mfastboot' when flashing

rocketsaucev2 said:
https://drive.google.com/file/d/0B28ubovBBGskTnBlUl9reGFzQ1E/view?usp=sharing
heres a copy of mine. Make sure you put it in the same folder as your adb or regular fastboot and use the command 'mfastboot' when flashing
Click to expand...
Click to collapse
I tried using that it seems to have worked but now I have an issue with my system.img. It will not turn wifi on and it will not update to 4.4.4. Where can I find a good copy of 4.4.2 sbf

Icon000 said:
I tried using that it seems to have worked but now I have an issue with my system.img. It will not turn wifi on and it will not update to 4.4.4. Where can I find a good copy of 4.4.2 sbf
Click to expand...
Click to collapse
Did you flash back the original boot.img so it matches your system.img?

adm1jtg said:
Did you flash back the original boot.img so it matches your system.img?
Click to expand...
Click to collapse
I tired a whole bunch of things ended up finding 4.4.4 and using rsdlite to put it on my phone.
Thanks anyway.

[IMG] LXE22.46-11 Pure Edition Stock Boot, Recovery and System.img [Lollipop 5.0]

Here is the fully stock Boot.img, Recovery.img and System.img. There are no modifications to any of these. This is all we have until Motorola releases full factory images for Lollipop 5.0.
For the XT1095 Pure Edition ONLY
BUILD: LXE22.46-11 (22.21.11)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.21.11_BOOT_RECOVERY_SYS.zip
md5: 43888F4EAB74600E6D6DF41FF202C9BA
here's a mirror
https://mega.co.nz/#!a9hymLCD!ek2VVQNPGmUpNHFl6WIQe8znsFtUBjbsvTu0-TyORnM
Previous builds
BUILD: LXE22.39-6 (22.11.6)
http://apollyon-dev.com/motox/XT1095_Lollipop5_22.11.6_BOOT_RECOVERY_SYS.zip
md5: 6A527AFB1DEED2248AE2D3B4ACCF04ED
here's a mirror
https://mega.co.nz/#!H0wn2LoT!hHqhasTUnLjxMxACvODWcRIrtm3jTGjg1MEqxZfP5lo
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, catches on fire or it starts WWIII. Use at your own risk.

how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5

godutch said:
how do you flash these, I tried both fastboot and mfastboot but both fail, they crash even
also build prop says this is 4.4.4 not 5
Click to expand...
Click to collapse
you are doing it wrong...

mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
ok, how can we do it?
thx

overon37 said:
ok, how can we do it?
thx
Click to expand...
Click to collapse
by using mfastboot. this is for advanced users...

yes, i got it, but, can i flash it over XT1092 with Kitkat?

^^I have a conversion guide, that'd help you for sure

mrvirginia said:
you are doing it wrong...
Click to expand...
Click to collapse
so how i am supposed to flash this then?

After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:

Can someone provide the bootanimation file in system/bin?

Links dead?

Devans32 said:
Links dead?
Click to expand...
Click to collapse
Nope. they both seem to work here.

updated
for the official 22.21.11 Build.
mirror up shortly

Ok now I am getting a parse invalid file error when I try to flash the system image.
Edit; fixed. Found right files and up and running.
Sent from my Nexus 6 using XDA Free mobile app

Chronzy said:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Click to expand...
Click to collapse
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?

Kallb123 said:
I get the error:
Code:
Invalid sparse file format at header magi
when trying to flash system.img
I've verified MD5 of file, but I'm redownloading it. Do I need to manually split it into chunks or something?
Click to expand...
Click to collapse
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?

Chronzy said:
Are you using mfastboot v2?
The files in this OP worked great for me on .6, but .11's so widespread I'm not sure why one wouldn't downgrade to KK and accept the OTA? Then use chainfire's root?
Click to expand...
Click to collapse
Yes, got the new mfastboot, but I've tried with old as well as mfastboot v1. I was trying to flash .11 but I got this error, so I came here to use these files but also got this error :/
EDIT: Flashed KK and upgraded .11 from there. Can't get a signal though, even after flashing my modem back..
EDIT2: erase modemst1 and modemst2 and then flashing my fsg and modem worked

Chronzy said:
After some experimentation I cleaned up these instructions a little bit and confirmed this method works for me for rooted (.6):
Here's what I did, real easy:
- Download mfastboot v2 from graffixnyc's thread.
- unzip boot, recovery, system imgs that you downloaded from the OP into the mfastboot folder where the mfastboot.exe is located. Open a cmd prompt on that folder.
- Put phone in fastboot, plug it in:
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
For the new radio, download it from graffixnyc's site, put in mfastboot folder and flash :
Code:
mfastboot flash modem radio.img
After you get a successful boot, put the phone back in fastboot and download CF-Auto-root from graffixnyc's post in "General". Put the CF-Auto-Root.... img (inside the zip in the /image folder) in the mfastboot folder with everything else and flash according to his instrucions :
Code:
mfastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
That's it. Nothing hard about it. Any questions let me know.
Big thanks to both mrvirginia and graffixnyc for their work on this. And of course Chainfire.
*Note- you have to be upgrading from KK for this to work. If you run into issues already on a version of 5.0 and attempt this method to "fresh install", you will get stuck at boot ani. Downgrade and then try this method again. :good:
Click to expand...
Click to collapse
You did this from -6 rooted? With stock recovery or TWRP?

zgroten said:
You did this from -6 rooted? With stock recovery or TWRP?
Click to expand...
Click to collapse
That was the method I used to upgrade from KK to .6. I don't understand your recovery question. All this is done in bootloader.
I think you guys would benefit from SolarTrans' guide in the "general" section... http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074

Anyone else have issues
I'm on 22.39-6 and I am having issues when the phone. Anyone else have the issue where the home and menu buttons randomly disappear? Or text messages don't appear? The only fix was to reboot the phone. I also have unresponsive issues randomly when the phone is plugged to AC power and charging. Just wondering if I'm the only one with these issues. I'm going to flash the new build, but just wondering.

Please help..Cannot flash system.img manually OR with script.

i have been trying to flash the system.img manually and with the script. all i get is cant find the system.img and i get the wrong size reported back when trying to flash it. i am at a loss.. and my system has been erased so all i can do is boot into the bootloader....any help would be GREATLY appreciated...im so pissed i did this and have no phone right now..
thank you
FYI, Verizon N6 on 5.1 , unlocked, and rooted

dvigue said:
i have been trying to flash the system.img manually and with the script. all i get is cant find the system.img and i get the wrong size reported back when trying to flash it. i am at a loss.. and my system has been erased so all i can do is boot into the bootloader....any help would be GREATLY appreciated...im so pissed i did this and have no phone right now..
thank you
FYI, Verizon N6 on 5.1 , unlocked, and rooted
Click to expand...
Click to collapse
Flash all bat doesn't work. Did you unzip the second folder and find actual system.img. Then fastboot flash system system.img.

dvigue said:
i have been trying to flash the system.img manually and with the script. all i get is cant find the system.img and i get the wrong size reported back when trying to flash it. i am at a loss.. and my system has been erased so all i can do is boot into the bootloader....any help would be GREATLY appreciated...im so pissed i did this and have no phone right now..
thank you
FYI, Verizon N6 on 5.1 , unlocked, and rooted
Click to expand...
Click to collapse
dont use the flash-all script. flash each partition separately.

yes...i have tried it manaully..i keep getting "cannot find system.img" and my fastboot, adb and the .img files are all in the same folder... what the heck am i doing wrong...it also shows and i always get an "target allowed MAX download size of 536870912 when ever i try to flash system.img

dvigue said:
yes...i have tried it manaully..i keep getting "cannot find system.img" and my fastboot, adb and the .img files are all in the same folder... what the heck am i doing wrong...it also shows and i always get an "target allowed MAX download size of 536870912 when ever i try to flash system.img
Click to expand...
Click to collapse
Open command prompt. type fastboot flash system (drag and drop system img here)

I had this happen on my n5 with the first preview, honestly what worked for me(and really hate even recommending using toolkits) but NRT with force flash enable fixed it a flashed all files.
Again don't even know if n6 can use NRT but if it helps it helps lol
Sent from my Nexus 5 using XDA Free mobile app

todorcim said:
I had this happen on my n5 with the first preview, honestly what worked for me(and really hate even recommending using toolkits) but NRT with force flash enable fixed it a flashed all files.
Again don't even know if n6 can use NRT but if it helps it helps lol
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Shouldn't use toolkit till understand how it should work manually. Can get into trouble and not know how to fix.

ok..NRT worked!!!! yes...thank god...thanks for all your help

Here are all the manual commands.
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
fastboot flash radio {radio.img}
Step #2
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot format vendor {don't need for phone}
fastboot format cache
fastboot format userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot flash userdata {userdata.img}
fastboot reboot

prdog1 said:
Shouldn't use toolkit till understand how it should work manually. Can get into trouble and not know how to fix.
Click to expand...
Click to collapse
Yep totally agree, notice my brackets?
Good I'm glad it worked!!
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 08:23 AM ---------- Previous post was at 08:18 AM ----------
dvigue said:
ok..NRT worked!!!! yes...thank god...thanks for all your help
Click to expand...
Click to collapse
Don't rely on the toolkits tho, I personally think you need to know and understand the manual flash and Woking with adb/fastboot, I only used it because I spent a good hour trying every other possible fix to flash system (on both windows & Ubuntu).
But again I'm glad it work
Sent from my Nexus 5 using XDA Free mobile app

Turbo firmware?

Hello need help tracking down stock turbo firmware. The Motofirmware website (http://motofirmware.center/files/category/23-droid-turbo/downloads) are corrupted. The links in this thread are all dead: http://forum.xda-developers.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470. Does anyone know of another source for stock 5.1?

http://motofirmware.center/

Stanleywinthrop said:
Hello need help tracking down stock turbo firmware. Does anyone know of another source for stock 5.1?
Click to expand...
Click to collapse
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637

Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.

jalal-jap said:
http://motofirmware.center/
Click to expand...
Click to collapse
Thanks, classic, i'll give this a try.
classic757 said:
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Click to expand...
Click to collapse

Stanleywinthrop said:
Thanks, classic, i'll give this a try.
Click to expand...
Click to collapse
No problem. Please let me know how it turns out.

Stanleywinthrop said:
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
Click to expand...
Click to collapse
i have same problem. extract it whit "7ZIP" and no corrupted for me.

http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1

TheSt33v said:
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
Click to expand...
Click to collapse
I get this error:
http://i.imgur.com/EOPsxnB.png

dmginc said:
I get this error:
http://i.imgur.com/EOPsxnB.png
Click to expand...
Click to collapse
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.

Oh thanks. Good info. Is there a write up on using fastboot anywhere? These forums are pretty poorly maintained and no good stickies anywhere
Edit: Oh, you edited your post. Awesome. Thanks.

The root junky fxz is that for rsd lite when I look at the contents the system image is in several sections and says system.img sparsechunk and has 10 sections. I have never seen this in an fxz. Is this a new way of flashing the system image.

TheSt33v said:
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Click to expand...
Click to collapse
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.

When in fastboot, type "fastboot oem lock" (without the quotations"

Btrusa said:
When in fastboot, type "fastboot oem lock" (without the quotations"
Click to expand...
Click to collapse
Wouldn't that lock the bootloader?
Is it even possible to re-lock?
From what I understand he wants to avoid locking the bootloader...
Edit: nevermind I looked it up... Should have just done that the first time... ("I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.")

dmginc said:
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
Click to expand...
Click to collapse
Nope

So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Sent from my XT1254 using Tapatalk

dmginc said:
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Click to expand...
Click to collapse
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin

unhappybirthday said:
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?

dmginc said:
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
Click to expand...
Click to collapse
I can only speak from my experience. I was on the KitKat bootloader and used mofo to flash lollipop. I unlocked with sunshine and installed twrp. Then I flashed the lollipop bootloader with the fastboot command . Still unlocked.
Sent from my DROID Turbo using Tapatalk.