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...

[Q] Nexus S 4G bootlooping

Hello XDA. First post here. I need the pros.
I may have seriously messed up my Nexus S 4G. The "Google" logo appears when I turn it on but there is no lock on the bottom (there was before) and after that, boot animation of the X keeps restarting. Pull the battery. Hold up and power on. Go into Recovery and I end up with the white triangle and yellow exclamation point inside it.
Did I just brick my phone? Any way to get out of this? I have an upgrade available, but I'd rather check out the Nexus4 before buying the Galaxy Nexus. (Nonreplaceable battery in the Nexus4 might be a killer for me.)
I searched around but no other situations were like mine. Sorry if I missed something. Help me XDA. You're my only hope.

mjnouri said:
Hello XDA. First post here. I need the pros.
I may have seriously messed up my Nexus S 4G. The "Google" logo appears when I turn it on but there is no lock on the bottom (there was before) and after that, boot animation of the X keeps restarting. Pull the battery. Hold up and power on. Go into Recovery and I end up with the white triangle and yellow exclamation point inside it.
Did I just brick my phone? Any way to get out of this? I have an upgrade available, but I'd rather check out the Nexus4 before buying the Galaxy Nexus. (Nonreplaceable battery in the Nexus4 might be a killer for me.)
I searched around but no other situations were like mine. Sorry if I missed something. Help me XDA. You're my only hope.
Click to expand...
Click to collapse
What have you done before this happened?
You have relocked your bootloader?
Fix is easy, you'll lose your data doing so.
Unlock the bootloader using fastboot
Install a custom recovery such as Clockworkmod
From within recovery wipe data
Try to boot like this. If it doesn't boot, go back to recovery, wipe everything and re-install your ROM/stock ROM depending on which you have. You can transfer the flashable zip from within Clockworkmod recovery by mounting your USB storage when connected to your computer.

polobunny said:
What have you done before this happened?
You have relocked your bootloader?
Fix is easy, you'll lose your data doing so.
Unlock the bootloader using fastboot
Install a custom recovery such as Clockworkmod
From within recovery wipe data
Try to boot like this. If it doesn't boot, go back to recovery, wipe everything and re-install your ROM/stock ROM depending on which you have. You can transfer the flashable zip from within Clockworkmod recovery by mounting your USB storage when connected to your computer.
Click to expand...
Click to collapse
First of all, thank you polo for helping me out!!!
At first, I was flashing nandroid backups between AOKP, CM10 M2, and CM7. Then it got stuck in a boot loop of a different sort (don't remember the details) and before I remembered to come over to XDA, I formatted some partitions under Mounts and Storage in CWM like an idiot. However I did wipe data/factory reset, wipe cache, wipe dalvik cache and still nothing.
I just googled some directions on unlocking from fastboot, flashing CWM, and from there let's see how it goes. Wish I brought a cable with me to work, but it'll have to wait a few hours. Thanks polo!

mjnouri said:
First of all, thank you polo for helping me out!!!
At first, I was flashing nandroid backups between AOKP, CM10 M2, and CM7. Then it got stuck in a boot loop of a different sort (don't remember the details) and before I remembered to come over to XDA, I formatted some partitions under Mounts and Storage in CWM like an idiot. However I did wipe data/factory reset, wipe cache, wipe dalvik cache and still nothing.
I just googled some directions on unlocking from fastboot, flashing CWM, and from there let's see how it goes. Wish I brought a cable with me to work, but it'll have to wait a few hours. Thanks polo!
Click to expand...
Click to collapse
Well if you formatted system and the like, you pretty much wiped your ROM. If you installed a stock ROM, it's possible your recovery was replaced by the stock recovery, otherwise there should be no reason for your recovery to get wiped.
Rooting again with the whole unlocking process and re-installing a ROM will get you back online in no time.

Welp, it looks like I need a little more help if you don't mind polo. For someone who was rooted, I guess I didn't know much, but learned a lot from this so far.
I flashed CWM from my desktop via fastboot and can now get into CWM. I then mounted the phone as a USB drive and loaded CM7.2 and then installed it. "Install from sdcard complete." after that. Rebooted and now it's looping at the boot animation for CM7.2. Wiped data/factory reset and same thing happens.
What am I missing here?
After I'm in CM, I plan on going back to stock + root.

Make sure you also wipe cache and dalvik cache. If this doesn't seem to work, in mounts and storage format cache, data, sdcard and system then reinstall your rom. Be sure you have the correct rom for your phone and not the crespo4g version or vice versa.

I just followed those exact instructions and it still loops at the boot animation. Damn.
The world needs more people like you polo. Thanks for trying to help me through this!! I have a genuine gratitude for you my friend.

OK, run a log cat with Adb. First night I had mine had serious issues, nothing worked same problem.
If you don't know how to do log cat
Is
Adb logcat > log.txt
Same as if fastboot. Upload that and we can find your prob instantly.
Sent from my A100 using Tapatalk 2

das_webos_transformer, I just PMed you the dropbox link since I can't post links here, but I don't see it in my sent. Did you get it?

I would try the factory images from Google. Make sure the phone is working as per usual and then take it from there.
There are guides on how to do so on the forums. It is very easy.

albundy2010 said:
I would try the factory images from Google. Make sure the phone is working as per usual and then take it from there.
There are guides on how to do so on the forums. It is very easy.
Click to expand...
Click to collapse
Hey Al. Thanks for replying. My problem is I'm seeing too many guides. I know it's a mortal sin to ask, but can you link me to one that you think is done correctly? Unfortunately I need a little more hand holding if that ok with you guys.
UPDATE - SOMEhow, I got CM10 installed and gapps. Just flashed it it worked. I did nothing differently than before. I installed a bunch of apps and that went well. I had a feeling I wasn't in the clear and now I can't restore a nandroid backup, a fancy widgets transparent background goes missing but the text remains, and Swype won't install. It's just weird. I'm more than willing to go back to stock now. If you can provide a link for how to flash the stock images, I'll definitely give it a shot. Thank you!!!

You're all over place so here are some general FYI.
Depending on which recovery was used to make the nandroid you may not be able to restore it with a different recovery.
When you say you can't restore a nandroid and a widget or swype won't restore I am lost. What are trying to restore it from and with what.
Anyways. Stock images are here https://developers.google.com/android/nexus/images
Make sure you download the ones for your device. The sprint d720.
Once the download is finished extract the file. You should have a few .img files and a update zip in there. Take those files and move them to the directory you have fastboot in.
With the phone in the bootloader enter the commands.
Fastboot flash bootloader bootloader file name.IMG
Fastboot reboot bootloader
Fastboot flash radio radio image name.IMG
Fastboot reboot boot loader
Fastboot -w update image name.zip
You can most likely skip the reboot 2nd and third reboot bootlaoders . People seem to do it for some reason. If your device already has versions of the bootloader and radio installed you can skip those flashes as well.
Make sure you change the commands to the actual file names you're going to flash. Can manually type/ paste the names or just hit tab after you typed the first letter. Example. Fastboot flash radio r tab. It should auto fill it in. Check anyways.
If you're not comfortable with this dont do it. Read some more or find a video on YouTube if you're unsure. I am not responsible if you screw something up . End result will give you factory up to date bootloader radio and rom. It also wipes the phone but not the internal storage. The bootloader will still be unlocked so you can relfash a custom recovery later and do what you want.
Guides are all over. Just make sure you're flashing the correct files for your device. The commands and procedure is the same for all nexus devices.
And last if the factory images give you issues then there most likely is something actually wrong with the device. Or you managed to screw up flashing.

Thanks Al! I did all that and am pretty comfortable with this stuff, but when time came to flash the image...
C:\Users\Nouri\Desktop\Fastboot>fastboot -w update image image-sojus-jro03r.zip
error: failed to load 'image'
Same issue without the -w. I'm starting to think something is wrong with the phone. But how can it. It's functioning. is it possible that a hardware problem can cause these inconsistent issues?
Issues
- When I had CM10 installed, it ran choppy. It ran fine when I flashed it a few days ago. I didn't do much and flashed another ROM, but I know the S 4G is capable of running CM10 smoothly. Swipes between homescreens were choppy and so was bringing up the app drawer.
-I couldn't take a screenshot. "Screenshot not saved" or something to that effect
-Swype would get to 100% download and then halt for a few minutes. I'd hit Install and it would just stay there for a few minutes and nothing would happen.
-I couldn't restore from a CWM nandroid that I just made.
Internal sdcard faulty maybe?
THANK YOU FOR YOUR HELP!!!!!

Nevermind! Back to stock! Thank you so much Al!!!! Holy crap you have made me a happy man before I sleep tonight dude!
The last step was actually fastboot -w update image.zip, but it's all good!!!!! Thank you ALL!!! XDA is a pretty special place where you guys help someone to the best of your knowledge. I'm going to pass this forward.
Polo, das, Al, I can't thank you guys enough. Know that you guys helped someone out big time here. Hopefully this makes your day better too!

Hey all. I just wanted to send a quick update your way. I successfully went back to 100% stock thanks to Al's awesome directions. Still couldn't install swype and there were some files on the internal storage that had all sorts of strange symbols and were .01 to 5 GB in size! Clearly there is something wrong here. I rebooted and that all went away actually. This morning I rebooted and I see a notification saying "Damaged USB storage - USB storage is damaged. Try reformating" I tapped it and successfully formatted the storage, but that's my issue all along. Wish I left the notification up there, but I'll get it back and take it to Sprint. Hopefully get a replacement.
You guys freakin rule. You helped me until we all, especially I, were blue in the face. Thanks again!!!

If you're going to take it sprint you should probably re lock the bootloader. They may not check or care but eh
Fastboot oem lock.
That doesn't wipe anything
Fastboot oem unlock does and that would be needed if you wanted to root and flash your device again .

Thanks and yup! I got pretty good at this whole thing now. I feel very good now learning fastboot. I flashed completely stock like you said. It worked. Problems arose. Locked the bootloader and tucked the phone away. If it wasn't for Google Voice, my life would suck right now! Hopefully my trip to Sprint turns out well. A few short hours.

Need some quick help

So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?

Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium

Any ideas?
Sent from my LG-LS970 using xda premium

Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.

No one can help?
Sent from my LG-LS970 using xda premium

Well that sucks...
Sent from my LG-LS970 using xda premium

Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.

I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.

[HOW TO] [NO JTAG] unbrick / debrick hardbricked Samsung Galaxy S3

This should work on all Qualcomm Snapdragon based Samsung galaxy SIII's, if it doesn't, PM me the model and I'll try and find a solution.
WHILE THIS IS VERY LIKELY TO WORK FOR ANY BOOTLOADER/MODEM/FIRMWARE BRICKED PHONE, THERE IS NO UNCONDITIONAL GUARANTEE THAT THIS WILL WORK FOR YOUR PARTICULAR SITUATION, THERE IS A POSSIBILITY THAT THERE ARE SOME BRICK STATES THAT THIS WILL NOT WORK FOR, but in my experience, almost all cases can be resolved by rewriting the sdcard with correct partitioning.
Disclaimer out of the way, let us begin.
Needed Materials and Files:
EDIT: if you have another phone or know someone else with the same phone have them run this and the output will be a debrick image you can use: busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=200 if it does not work then change the last number (count=) to something larger and try it. If you create an image please upload it so I can put it into a repository I'm creating
16GB or 32GB class10 microSD card
A hard bricked Samsung galaxy S3 US Cellular
The debrick image for your device:
[[Here is the drive image for a folder containing all the debrick images that I currently have uploaded, more will be coming: https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing ]]
If you have any images that I missed, please send me a link or, better yet, upload them to drive, make them publicly shared, and share them with me at [email protected], I will put them in this folder for all to use
US Cellular R530: ftp://sdbruington.us/d2usc/SCH-R530_ALIVE_MJA_200MB_16GB.bin
Sprint L710: http://www.mediafire.com/download/23...ph_l710.img.xz
AT&T I747: http://d-h.st/iEy
T-mobile T999: http://www.mediafire.com/download/gr...k_SGH-T999.img
---I did not upload these images, I have simply collected the links over time, please thank Cnexus for his help in finding these and
---helping me to originally unbrick my S3
Your computer
A card reader that will accept the card (another phone will not work as this is an image, and it needs to repartition the SD card)
Either a partition editor (I've heard that you can use dd or something on linux, but I haven't tried) or this: View attachment win32diskimager-v0.9-binary.zip
A wall charger (computer charging isn't as reliable)
Procedure:
1. Take the sdcard and insert it into your computer
2. Download the mentioned image and the software to put it onto the sdcard
3. Use your computer to pull the data already on the card onto your computer hard drive, as the sdcard will be wiped when the image is put onto it
4. use the software that you downloaded earlier to burn the image to the sdcard
5. Remove the battery from the SGS3
6. insert the sdcard into the S3
7. Put the battery into the S3
8. The S3 may boot automatically, or you may have to manually boot it by holding down the power button for 5< seconds
9. If the update that bricked your phone also messed up /system, then you'll have to coerce Odin mode to shove a stock firmware image to your phone, though I've had more than just SOME trouble with that in the past (in other words I haven't been able to get back to stock yet...), if you simply had a radio update or something go wrong, then proceed to the next step.
10. Do a victory dance with your phone in your pocket not the repair bench, or on second thought, make sure you don't drop it, don't create another problem.
11. After that, you can just use your device normally with the sdcard in it without worry of bricking it, though it will not be able to boot if you remove the sdcard;
the only known method of getting it to boot without the sdcard is reflashing stock firmware, which completely wipes the phone and resets everything back to complete stock. Also, Odin mode has, at least for me, objected when I've tried to flash the stock image back onto it, and even if Odin mode was sure of working, backing up ~16GB of data isn't a fast process, especially with the most reliable means being ADB. If you try to flash a stock image and it fails, your device will almost definitely come up with a version of dmode when you try to turn it on with the sdcard (still bricked otherwise) that says something about Kies update failure, the only way of correcting this that I've had success with is flashing an image that won't do much, such as the same recovery that you already had, over odin mode from that special dmode, as while that won't correct the actual brick, it will at least make you able to boot from the sdcard again. I will provide links to the stock images in a little while, once someone gets that far, as I will have to find all but the one from the US Cellular version.
I am currently looking for firmware images that will only flash the bootloader/modem, if anyone knows of an odin file that could do that, please let me know as soon as possible, in the meantime, I will try and create an update.zip that will flash the necessary files; as most bricks are likely cause by an update.zip that was meant for a different device, I am very confident that it can be fixed with another .zip file.---Stay tuned!
---Don't forget, that thanks button won't bite your finger off if you push it:fingers-crossed:
If any of the links are not fully functional, PM me to let me know, and if you have the link to another debrick image for another device, send me the link so I can include it here!
Please note: While there is a similar procedure for Xynos based S3's, they apparently require a physical modification that requires an amount of soldering, so it is most likely best for them to simply take them in for Jtagging and then just not brick them after that.
EDIT: here is the link to a full youtube tutorial that I made, just for those of you who like watching a video instead of getting lost in a written guide https://www.youtube.com/watch?v=-RTAbLBVfMI
EDIT AGAIN: I'm sorry about both of the mediafire links being down, I will try and find some more and upload them to my google drive, along with the others just to make sure they exist somewhere safe.I'm downloading the images now and uploading some that I already have, they will be available in this folder (https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing) on google drive and will be available by email upon request
here is a sprint image that should work, sorry I haven't tested it http://www.mediafire.com/download/231uhy6l80jx74n/debrick_sph_l710.img.xz
for the t999 4.1: https://www.copy.com/s/xSAswQZbhQX8/t999_debrick.zip for the t999 4.3: https://www.copy.com/s/7ICfKXMC3ccr/T999_4.3_debrick.zip
I know this is becoming a mess of links but here is a link to an xda post that has t999 variant images http://forum.xda-developers.com/showthread.php?t=2439367
here is a sprint 4.4 debrick image: http://www.androidfilehost.com/?fid=23329332407591176
If you want to get your phone to operate without an sd card in there for every boot, stay tuned, I'll have a guide to return to stock soon, though a quick google search shouldn't be that hard if you're desperate
I will clean up this guide in a little bit but currently I have school and such to attend to so it may not be immediate
I know this is getting unwieldy but (big thanks to youdoofus) I have a way to completely debrick and fix it so it doesn't require even the sd to boot.
"Restoring stock bootloader
1) You were able to boot into the ROM
2) Plug your phone into a computer and use MTP mode
3) Move the debrick file onto your internal sdcard (/sdcard/debrick.bin)
4) Disconnect your phone
5) Open up a Terminal Emulator on your phone and input this code
Code:
su
dd if=/sdcard/debrick.bin of=/dev/block/mmcblk0
6) Reboot"
Of course this should be modified for the different versions and types of debrick image as some are img, some are bin, I think there might even be an ISO hanging around somewhere
EDIT: As of October 10th I'm working on a tool that will get an image directly from a stock rom/tar and put it on the SDcard. This is pretty complex so it will probably take a little while, but it should make it easier to get images if all that's required is a stock tar.

I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?

derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.

polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.

Thanks for sharing this

derget1212 said:
how do i find out the correct bootloader? i was using this rom http://forum.xda-developers.com/showthread.php?t=2518998 for a couple months and randomly got hard bricked yesterday. any help is greatly appreciated.
Click to expand...
Click to collapse
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.

polobunny said:
Explain your situation. Randomly bricked is very vague. Did you flash anything? Do you remember doing anything? It's important. Phones don't go and "randomly brick" unless of a HW problem, and to either confirm or eliminate that possibility we need more details.
Click to expand...
Click to collapse
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.

derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.

polobunny said:
Whoa whoa there, if your phone still boots in either recovery or download mode, then you don't need to use a debrick.img.
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM using ODIN in download mode.
Click to expand...
Click to collapse
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.

derget1212 said:
Like i said, it was totally random. My phone froze and rebooted yesterday. It got to the Samsung logo so i thought everything was okay. I fell asleep and woke up to a bricked phone. After all of my attempts, I got one debrick.img to show something on my screen and it shows "BOOT RECOVERY MODE". Odin sees my phone and tries to fix the PIT and the Bootloader but it always fails. From what i gather, it seems to be a hardware issue.
Click to expand...
Click to collapse
It really sounds a lot like the BRICKBUG to me, anyone know how to tell if a chip is insane without it working? And did you have the 4.3 bootloader? If you got that you should have been safe, but if you didn't then the kernel may have burned out the chips from the "bug" (it really doesn't seem too much like a "bug", more like an issue worthy of recall)
Sorry I don't know exactly what's wrong off the top of my head

derget1212 said:
It is hard bricked. Without the sd with a debrick.img installed, I get no response at all. And I've tried all the i747 debrick.img files I could find here with no success.
I can get to boot recovery mode with one .img I could find but boot recovery os different than recovery mode. It's essentially useless and Odin doesn't like it.
Click to expand...
Click to collapse
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.

polobunny said:
You don't need a debrick.img of a 4.4 to get it working, you need a debrick.img of the correct bootloader. If you bricked your phone by flashing an older bootloader after upgrading to the 4.3 bootloader, then you need a debrick.img with the 4.3 bootloader.
Click to expand...
Click to collapse
Exactly

This image gets you in the clear if the ONLY thing screwed up is the boot partition, meaning modem/firmware/bootloader, it does NOT get you fixed if you got your rom F***ed up, and do not expect it to, this will get you into dmode so you can use odin or something like fastboot to flash a /system image or a FULL stock rom if you want to get your bootloader fixed without the SD card being in all the time.

dreamwave said:
If you get ANY response at all, then the debrick image is doing its job; what you need is a stock image, I'll try to find a link for you to use. Try using Kies or something, alternatively, as if you have the serial number you can apparently flash it quite cleanly, all data on the phone will be lost though, as it effectively wipes the eMMC.
Click to expand...
Click to collapse
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.

derget1212 said:
if anyone can find the correct debrick.img i need to use, i would greatly appreciate it. I have tried Kies and Odin without success. They can see the phone but seem not to be able to access it. I can't flash anything via odin or get to the CWM recovery or download mode. this is a really weird screen i haven't seen before.
Click to expand...
Click to collapse
Is there any way at all to get into dmode? What is windows recognizing it as?

Thanks for sharing.

EvangelineX said:
Thanks for sharing.
Click to expand...
Click to collapse
no problem, I hope it helped!

derget1212 said:
I've followed all these guides and haven't had any luck. I did use a CM 4.4 rom and some people are saying i need a debrick.img of a 4.4 to get it working again. i'm on an i-747. can you help?
Click to expand...
Click to collapse
If you bricked the /system partition AND the boot partition you will need a stock rom as well, just use Odin or something if possible after using a 4.3 image, a 4.4 image is more or less the same as a 4.3 as far as I know, I mean I bricked mine after using cm11 by flashing the wrong rom, it's just that the rom you tried tried to flash a 4.1 bootloader, and thus tripped the eFUSE or something in the Knox bootloader, what you need is a 4.3 unbrick image, as 4.4 didn't really change the modems/bootloader from 4.3, and the unbrick image isn't really that much more than a collection of pieces from the boot partition that are used as an autoboot by the phone when the eMMC fails to load properly.

This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.

halfdead1993 said:
This is pretty neat..
does it always work?
It's nice to have such a recover method whenever something like this happens to you.
Click to expand...
Click to collapse
I believe it will work on basically anything, as in I haven't seen a case that can't be cured at least somewhat by this, I think it works like an alternative boot, as if the bootloader on the eMMC is corrupted, it seems to remove the boot flag, thus making it so that the phone does not detect a bootable partition, the unbrick image has a partition layout mirroring the one that is supposed to be on the phone, so it is used as the boot partition but then redirects control back to whatever is on the eMMC after the bootloader, think of it as a liveCD on windows, just one that hands control back to the system after it has gotten past booting the BIOS.

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!