Database Info

[GUIDE] How to fix "Failed image LNX 0x0002 / RSD mode 2

I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!

mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?

I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded

You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.

yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...

Droid RAZR HD @ No Valid PIV block in Sp for system

Hi guys. First, trust me that I have looked at every post I could find regarding this issue and the reason I am starting a new thread it because the fixes are not working for me. First, my phone:
Droid Razr HD Dev Edition, I believe it's the T926, though it doesn't boot now so.....
I had rooted this phone with the Droid Razr HD Utility 1.1. I had it running on T-Mobile fine for quite some time (only HSA speed or whatever they call it, but that's fine I'm out of range for anything better anyway). I had Superuser installed and something like root keeper I think it was called. Anyway my point is everything worked great.
I started getting this popup that seemed to say Motorola wanted to do an update. Now I had ignored the update on my phone for a while as I didn't want to go through the process just yet. Finally I gave in and I let the Motorola from my Windows PC try to push an update. That was the last my phone has booted.
So now all I get is Fastboot. Now if I do the buttons and manually go to fastboot it looks normal and I connect USB and it looks fine. But if I try to run the HD Utility 1.10, 1.20 both fail, RSDLite 5.6 and 6.0 both fail. All I can come up with is No valid PIV block in sp for system. The phone does seem to respond when I try the utility but all I get is failures and it clearly says the phone is locked. RSDLite has no such luck and immediately fails.
I still have the original XT926 xml I used and I also downloaded a VZW_XT926. I'm really SOL here guys and I would so appreciate any help.
I guess the last bit of info I can think to add is that when I plug USB in fresh what looks like Motorola software (what messed me up to begin with) pops up and tells me it wants to repair the phone. Of course like an idiot I've tried that as well.

My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com

coolloser said:
My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com
Click to expand...
Click to collapse
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.

Dagroth said:
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.
Click to expand...
Click to collapse
After Jellybean there needed to be new Fastboot files because of some security change in Android, the newest utility most likely has it. I found this file
http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
in this thread:
http://www.droidrzr.com/index.php/topic/15828-rsd-lite-stock-412-firmware-restore-not-working/
If you are still stuck after that I suggest signing up on DroidRzr.com and joining the chatroom, those guys know far more than I!

Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.

Dagroth said:
Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.
Click to expand...
Click to collapse
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!

Unbricked
Dagroth said:
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!
Click to expand...
Click to collapse
I was trying to load a different ROM (running 4.4.2) so I could unlock the bootloader and root and hard bricked my phone with the same error message as a result of a failed flash. Using the fastboot command (fastboot flash system system.img) I was able to load the system.img from VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml and now am booting successfully once again.
Dagroth, you pulled my fat outta the fire! Many thanks. I hope this message helps others.

Razr HD Update Screen Flashing and Recovery Not Working

Hi,
So I've taken the time to create some videos showing exactly what my problems are, and I'll start with the first one.
Ever since the last update for KK was released, I have been unable to update (due to a second issue we'll get to in a bit) so I've just been delaying the update until I've had the time to troubleshoot the other issue. However, I believe not updating is causing the update screen to randomly attempt to appear and then disappear really quick, you'll see it in the video. It mostly happens when I'm watching videos, or using the browser at all. It's super annoying as it stops videos and just generally interrupts anything I'm doing.
Non-the-less, here is the video.
http://quickvid.org/watch.php?v=3SLcUguDAyT
In addition to this, I cannot currently update as my recovery is either corrupt or just not working right.
Here is a video of what happens when I try to boot into recovery...
http://quickvid.org/watch.php?v=RvnxD-fXrUu
Since the recovery is not working, when I try to do the update, it reboots the phone, attempts to go into recover (sits at the moto logo for 2 mins then boots the phone like normal). It does this about 5 times then it just fails the update.
I've tried to flash multiple recoveries, and this all started when I flashed Clockwork mod recover (which obviously did not work). I've even tried flashing back to stock recovery, but with no luck.
Any help is appreciated!
-------------
Oh and as a side note, in case anyone is wondering where these videos are uploaded to, it's a website that I own called QuickVid. It's essentially Imgur, for videos. So if you ever need to upload a video to post on the forums or something, feel free to use the service

masters1222 said:
Hi,
So I've taken the time to create some videos showing exactly what my problems are, and I'll start with the first one.
Ever since the last update for KK was released, I have been unable to update (due to a second issue we'll get to in a bit) so I've just been delaying the update until I've had the time to troubleshoot the other issue. However, I believe not updating is causing the update screen to randomly attempt to appear and then disappear really quick, you'll see it in the video. It mostly happens when I'm watching videos, or using the browser at all. It's super annoying as it stops videos and just generally interrupts anything I'm doing.
Non-the-less, here is the video.
http://quickvid.org/watch.php?v=3SLcUguDAyT
In addition to this, I cannot currently update as my recovery is either corrupt or just not working right.
Here is a video of what happens when I try to boot into recovery...
http://quickvid.org/watch.php?v=RvnxD-fXrUu
Since the recovery is not working, when I try to do the update, it reboots the phone, attempts to go into recover (sits at the moto logo for 2 mins then boots the phone like normal). It does this about 5 times then it just fails the update.
I've tried to flash multiple recoveries, and this all started when I flashed Clockwork mod recover (which obviously did not work). I've even tried flashing back to stock recovery, but with no luck.
Any help is appreciated!
-------------
Oh and as a side note, in case anyone is wondering where these videos are uploaded to, it's a website that I own called QuickVid. It's essentially Imgur, for videos. So if you ever need to upload a video to post on the forums or something, feel free to use the service
Click to expand...
Click to collapse
If your bootloader is locked, you won't be able to flash a custom recovery. Depending on what version you are on, you want to get the correct FXZ to retrieve the recovery.img file and flash that. Flashing anything else could result in issues.
First things first, please let us know the answer to the following questions:
What version of Android is your system on?
Is your bootloader unlocked?

Hi thanks for taking the time to reply.
1. Kitkat 4.4.2 183.46.10.XT926
2. Yes my bootloader is unlocked.

masters1222 said:
Hi thanks for taking the time to reply.
1. Kitkat 4.4.2 183.46.10.XT926
2. Yes my bootloader is unlocked.
Click to expand...
Click to collapse
Then you just need to get the correct FXZ, extract the recovery.img file from it and then reflash it to your phone from your PC with the following command:
fastboot flash recovery recovery.img
You can get the FXZ from here -> http://sbf.droid-developers.org/download.php?device=5&file=902

I will try this, I believe I have done this in the past, but I'll try again and post results.

Okay so I just flashed that recovery, and now I have an android guy laying down with a red ! triangle coming out of the chest. Doesn't sound good.
Maybe I am flashing wrong?
I am booting into the bootloader, with USB connected, then using fastboot with the following command flash recovery recovery.img and it is finishing.

masters1222 said:
Okay so I just flashed that recovery, and now I have an android guy laying down with a red ! triangle coming out of the chest. Doesn't sound good.
Maybe I am flashing wrong?
I am booting into the bootloader, with USB connected, then using fastboot with the following command flash recovery recovery.img and it is finishing.
Click to expand...
Click to collapse
OH wow come to find out this is the stock recovery. I just need to hit up + power button to get the menu. Okay great this might have fixed the issue then.
I'll try and do the update now and see how it goes.
Edit: The update took! Seems that I was just flashing the wrong thing the whole time.
Now to just find out how to restore root via flashing.

iBolski said:
Then you just need to get the correct FXZ, extract the recovery.img file from it and then reflash it to your phone from your PC with the following command:
fastboot flash recovery recovery.img
You can get the FXZ from here -> http://sbf.droid-developers.org/download.php?device=5&file=902
Click to expand...
Click to collapse
Oh and I don't think I ever said thanks, so thank you! this worked and the update took!

Bootloader gone?

I downloaded the "Retail Canada (1GB)" firmware as listed in this post:
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
I went to install it via the guide linked at the beginning of the first post. The command mfastboot flash motoboot motoboot.img didn't complete because no such file (motoboot.img) existed in that archive. The guide said nothing of this, so I continued with the other steps until the end (every other one said 'okay'), finally issuing the reboot command.
Now the phone won't boot up because, I assume, I no longer have a bootloader. I just get a black screen. If I plug in the USB cable to my computer, I can hear the sound of a device being connected, but it just shows as a Qualcomm device in Device Manager. Pressing and holding the power and volume-down keys seems to reboot the device (I hear Windows chime that a USB device was disconnected, then reconnected) but nothing ever comes on the screen. ADB/Fastboot commands just say "waiting for device".
Is the phone done? If so, then that's pretty lousy that the archive for the stock ROM doesn't contain the bootloader file that I apparently need.
Yes, my bootloader was unlocked because I had installed TWRP to try out the CM ROM before deciding to return to the stock ROM.

You didn't flash the bootloader, but didn't erased either. That guide is for older phones and some files are missing or with a different name. I did that flashing and it went well even without flashing motoboot.
Sent from my MotoG3 using Tapatalk
---------- Post added at 11:48 AM ---------- Previous post was at 11:42 AM ----------
Adb will always says waiting for device bc Adb loads only with system. Try typing "mfastboot devices" to see if you can still access fastboot
Sent from my MotoG3 using Tapatalk

@Sevael - Thanks for pointing this out. The motoboot.img is now known as bootloader.img in Osprey firmware images. The motoboot partition is also different, now known as 'bootloader.'
The new command to flash Bootloader file is therefore:
mfastboot flash bootloader bootloader.img​

lost101 said:
@Sevael - Thanks for pointing this out. The motoboot.img is now known as bootloader.img in Osprey firmware images. The motoboot partition is also different, now known as 'bootloader.'
The new command to flash Bootloader file is therefore:
mfastboot flash bootloader bootloader.img​
Click to expand...
Click to collapse
Will be great to add (if isn't there already) this on the OP of osprey FW post. Thanks!
Sent from my MotoG3 using Tapatalk

nelsonw said:
Will be great to add (if isn't there already) this on the OP of osprey FW post. Thanks!
Click to expand...
Click to collapse
Working on it now.

nelsonw said:
Adb will always says waiting for device bc Adb loads only with system. Try typing "mfastboot devices" to see if you can still access fastboot
Click to expand...
Click to collapse
I tried ADB, fastboot and mfastboot, they all return empty lists. I even tried the qboot solution for older Moto Gs. It doesn't respond to anything. I was on the internet for four hours looking up solutions and trying everything and nothing worked. Best I can tell, the bootloader is corrupted or missing. Since I can't get into the bootloader, I can't reflash anything to fix it.
According to the later pages of this thread, there are software tools out there which would fix this exact problem, but no one on XDA has been able to get their hands on them for the 3rd gen Moto G. Seems that only Motorola and perhaps some authorized repair places have access to the tools.
It wouldn't be such a big deal if this wasn't my only phone. I've previously had Samsungs and LGs and modded the hell out of them and it was always easy to recover from any type of issue via Odin or LG FlashTool. This is my first Motorola and I'm quickly learning that it's a much more fragile beast. I'm thinking that this might be my last Motorola for that very reason. I like to mod but I don't like this kind of fragility. I technically made no mistakes (just followed the guide I was directed to) and now my phone is hardbricked.
I have to go out and buy another phone this morning. The Moto G is an amazing phone for the price, but I'm not sure I want to risk it again.

@Sevael - Are you using Fastboot in Windows or Linux?
Edit: From what you have described, the bootloader hasn't even been touched.

Sevael said:
I tried ADB, fastboot and mfastboot, they all return empty lists. I even tried the qboot solution for older Moto Gs. It doesn't respond to anything. I was on the internet for four hours looking up solutions and trying everything and nothing worked. Best I can tell, the bootloader is corrupted or missing. Since I can't get into the bootloader, I can't reflash anything to fix it.
According to the later pages of this thread, there are software tools out there which would fix this exact problem, but no one on XDA has been able to get their hands on them for the 3rd gen Moto G. Seems that only Motorola and perhaps some authorized repair places have access to the tools.
It wouldn't be such a big deal if this wasn't my only phone. I've previously had Samsungs and LGs and modded the hell out of them and it was always easy to recover from any type of issue via Odin or LG FlashTool. This is my first Motorola and I'm quickly learning that it's a much more fragile beast. I'm thinking that this might be my last Motorola for that very reason. I like to mod but I don't like this kind of fragility. I technically made no mistakes (just followed the guide I was directed to) and now my phone is hardbricked.
I have to go out and buy another phone this morning. The Moto G is an amazing phone for the price, but I'm not sure I want to risk it again.
Click to expand...
Click to collapse
I'll look into that thread and see how i can help you. But some command must be wrong to achieve that king of brick. For sure isn't Motorola issue... Give me some time and look into that.
Sent from my MotoG3 using Tapatalk

lost101 said:
@Sevael - Are you using Fastboot in Windows or Linux?
Click to expand...
Click to collapse
Windows.
I followed all instructions. The files were all in the same folder, I copy/pasted the commands to ensure no typos, I carefully went through line by line. But something is different about the 3rd gen that the tutorial from the first gen just doesn't seem to work.
I know that I had things setup right because I was able to get TWRP flashed no problem. Installed CM, gave it a whirl, decided to go back to stock. Went back into the bootloader (didn't re-lock it at any point, that might have been my mistake), then tried to follow the linked guide to restoring the stock firmware. I even downloaded the firmware archive twice to ensure that it was correct. I extracted it all into the folder with the ADB and mfastboot files.
lost101 said:
Edit: From what you have described, the bootloader hasn't even been touched.
Click to expand...
Click to collapse
That's what I thought, but the phone does not boot into the bootloader under any circumstances. I tried things like holding the power and volume down buttons for two minutes (tried both when plugged into PC and unplugged). I tried just the power button for two minutes. I tried every software solution I could find online (four hours of searching and trying). Nothing worked.
Fortunately, the store rep bought my story when I told him that the phone was like that right out of the box and he gave me a full refund. So I grabbed a different phone.
Thanks for trying to help out guys, I really appreciate it. XDA is always an awesome place. I'm not done with Motorola, but I've picked up a Moto X Play to try for now. Fingers crossed!
Thanks again.

@Sevael - I'm glad you got out of the situation easily.
I've added a new guide for flashing Firmware Images in 'General.'
The only significant difference is the change of name for the 'Bootloader' partition and bin file. Some people have previously posted in the Firmware Images thread that they had successfully restore Stock Firmware - following the old Moto G Tutorial. Maybe all of them skipped the 'fastboot flash motoboot motoboot.img' command.
Since the command failed for you, it doesn't make any sense that it would hard-brick the phone - unless simply by using that command a new partition was created on the phone called 'motoboot' - which conflicted with the existing 'bootloader' partition.

Sevael said:
Windows.
I followed all instructions. The files were all in the same folder, I copy/pasted the commands to ensure no typos, I carefully went through line by line. But something is different about the 3rd gen that the tutorial from the first gen just doesn't seem to work.
I know that I had things setup right because I was able to get TWRP flashed no problem. Installed CM, gave it a whirl, decided to go back to stock. Went back into the bootloader (didn't re-lock it at any point, that might have been my mistake), then tried to follow the linked guide to restoring the stock firmware. I even downloaded the firmware archive twice to ensure that it was correct. I extracted it all into the folder with the ADB and mfastboot files.
That's what I thought, but the phone does not boot into the bootloader under any circumstances. I tried things like holding the power and volume down buttons for two minutes (tried both when plugged into PC and unplugged). I tried just the power button for two minutes. I tried every software solution I could find online (four hours of searching and trying). Nothing worked.
Fortunately, the store rep bought my story when I told him that the phone was like that right out of the box and he gave me a full refund. So I grabbed a different phone.
Thanks for trying to help out guys, I really appreciate it. XDA is always an awesome place. I'm not done with Motorola, but I've picked up a Moto X Play to try for now. Fingers crossed!
Thanks again.
Click to expand...
Click to collapse
It won't help you now, but technically all you needed to do to get back to stock was flash the system image files (and maybe the kernel if CM comes with its own kernel). You didn't even need to attempt to flash anything else. Its OK following guides but be aware that they aren't fool proof.

scott_doyland said:
It won't help you now, but technically all you needed to do to get back to stock was flash the system image files (and maybe the kernel if CM comes with its own kernel). You didn't even need to attempt to flash anything else. Its OK following guides but be aware that they aren't fool proof.
Click to expand...
Click to collapse
I did try reflashing. As I said, the bootloader was gone. No devices detected by ADB, fastboot, mfastboot, qboot, or any other tool I tried. I put in commands and it just sat at "Waiting for device".

I'm glad that you get a Moto X. I can't understand what you did. But that is the past. Good luck and enjoy your phone! Thanks @lost101 for the new guide.
Sent from my MotoG3 using Tapatalk

Sevael said:
I did try reflashing. As I said, the bootloader was gone. No devices detected by ADB, fastboot, mfastboot, qboot, or any other tool I tried. I put in commands and it just sat at "Waiting for device".
Click to expand...
Click to collapse
Hi,I meant for your first attempt at flashing back stock when your bootloader was OK. CM is just a new system image, you didn't need to even attempt to reflash a bootloader.
Even just using twrp to restore the system image alone would have got you back to stock.

scott_doyland said:
Hi,I meant for your first attempt at flashing back stock when your bootloader was OK. CM is just a new system image, you didn't need to even attempt to reflash a bootloader.
Click to expand...
Click to collapse
Yes, that's true. But at the time I didn't know that. There was a thread with links to the stock firmware and a guide how to flash it, so I followed it. Oh well, at least the issues I had have allowed for better information to become available for everyone.
scott_doyland said:
Even just using twrp to restore the system image alone would have got you back to stock.
Click to expand...
Click to collapse
Also true. I didn't take the time to create a backup of stock after first installing TWRP because I am used to Samsung and LG phones where you just download a single file and can restore the stock firmware image under any circumstances with no problems. It didn't dawn on me that a Motorola phone (this was my first) would be more complicated. I had (wrongfully) assumed that all Android phones were as foolproof as those two brands.
Especially Samsung. Odin plus the SamMobile website is like having an unlimited amount of get-out-of-jail-free cards. Why can't all Android phones work like that?

Sevael said:
Yes, that's true. But at the time I didn't know that. There was a thread with links to the stock firmware and a guide how to flash it, so I followed it. Oh well, at least the issues I had have allowed for better information to become available for everyone.
Also true. I didn't take the time to create a backup of stock after first installing TWRP because I am used to Samsung and LG phones where you just download a single file and can restore the stock firmware image under any circumstances with no problems. It didn't dawn on me that a Motorola phone (this was my first) would be more complicated. I had (wrongfully) assumed that all Android phones were as foolproof as those two brands.
Especially Samsung. Odin plus the SamMobile website is like having an unlimited amount of get-out-of-jail-free cards. Why can't all Android phones work like that?
Click to expand...
Click to collapse
I didn't know that about Samsung and LG as I have never had one. So I have also learnt something

Anyone ever figure this out?
I just did basically the same thing as the OP, because I'm an idiot. If there's a way to recover (there's a fix for the 2nd gen model involving qboot, but I'm guessing the images are different) without having to hope Motorola will replace it without noticing the unlocked bootloader that would be awesome. Qboot.exe will recognize it, so if I had the right blank-flash images that would work in principle.
I still don't understand what happened. I skipped the motoboot step because I didn't want to replace the bootloader and now I can't even get the screen to turn on.

@mcrammerdocdoc - It would be helpful if you can provide as much detail about what you did, fastboot commands used etc. It's important to get a clear understanding as to why this is happening.
If you are not touching the Bootloader at all, then it can only be gpt.bin (Partition Table) - creating this situation - as all other fastboot files are benign. The other possibility is that it's not really hard-bricked; perhaps there is a bug suddenly dropping battery life to zero (this occurred with Moto G (1st Gen)) and letting the phone charge will resolve this.

lost101 said:
@mcrammerdocdoc - It would be helpful if you can provide as much detail about what you did, fastboot commands used etc. It's important to get a clear understanding as to why this is happening.
If you are not touching the Bootloader at all, then it can only be gpt.bin (Partition Table) - creating this situation - as all other fastboot files are benign. The other possibility is that it's not really hard-bricked; perhaps there is a bug suddenly dropping battery life to zero (this occurred with Moto G (1st Gen)) and letting the phone charge will resolve this.
Click to expand...
Click to collapse
Yeah, sorry about that. Here's what I tried, ripped directly from Gammerson's stock-restore guide (new user, can't post the actual link apparently):
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img # skipped; no motoboot.img in the zip
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
The only variations besides skipping the bootloader were the system.img chunks (there were 5 for my device) and the fact that I used plain old fastboot from the Android SDK vs. mfastboot. Right after that "fastboot reboot" command the screen went dead and hasn't done a thing since. Plugging it into a PC will get it listed as "Qualcomm HS-USB QDLoader 9008 (COM8)", which I'm guessing is some kind of emergency serial interface. I guess that means the battery isn't dead? Unless it's just pulling power out of the USB port. I'll try charging it for a bit and see if that helps.
Thanks! Hope some of that is useful. Seems like the thing to do would be dump a bootloader image over that serial link, but I've got no idea how to begin doing that.

@mcrammerdocdoc that's exactly what happened with me.
It wasn't battery-related because it was nearly full when I did the final reboot command and it was dead immediately. I left it plugged in overnight and it didn't change anything.
The qboot thing would be the solution if we had the applicable software for the 3rd gen. There is a thread on XDA (I didn't bookmark it) where they were discussing the black-screen brick and the Qualcomm device showing up in Windows for all three gens of Moto G. The last few pages made it clear that 3rd gen owners with this issue don't yet have a solution.
I think it might have been in the 1st gen Moto G forum. The thread was over 100 pages long and involved all three gens.

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!