Database Info

[Q] COMPLETE Noob Bricked Samsung Vibrant While Flashing New Rom (Please Help! :( )

Hey Guys,
So I am definitely new to this and may have made a huge noob mistake...
I rooted my phone successfully using 1click root.
Then I tried installing the Bionix zip file as well as the DoW 1.4ghz overclock zip file...and my phone kept getting stuck on the boot screen that says "Team Whiskey" for like over 30-45mins. Even when I turn my phone on now, it stays stuck there. Is my phone bricked? I had my entire internal memory of 16gb full of music so at first I assumed it was b/c of that, but I think I might be bricked.
I ultimately just wanted to be able to use Bionix (or Fusion) with all the goodies like lag fix, and if possible, to flash the overclock zip as well.
What is going on here? How can I fix my phone? I would sincerely appreciate your expert advice!

What you say is one kind of brick, but this is the easiest to solve. All you have to do is reflashing the device using Odin. If you search a bit you'll find tutorials about it (samdroid.net has a tutorial for Spica, but I think the method is the same just the files are different). Good luck!
Sent from my GT-I5700 using XDA App

What you say is one kind of brick, but this is the easiest to solve. All you have to do is reflashing the device using Odin. If you search a bit you'll find tutorials about it (samdroid.net has a tutorial for Spica, but I think the method is the same just the files are different). Good luck!
Sent from my GT-I5700 using XDA App
__________________

Thinking about unrooting Read this first!!!! ALL MODELS

**********Please Sticky**********
(MOTOROLA HAS RELEASED ALL THE IMAGES FOR ALL COUNTRY VERSIONS OF THE XOOM RECENTLY MAKING THIS A UNIVERSAL TUTORIAL AT THIS POINT)
Listen I notice recently there is a flood of issues with the xoom using different unrooting methods. I personally will say to unroot your device just bring it back to stock images. Its the safest method with the other methods if you do not know what you are doing you will find yourself sending your device to motorola for warranty repairs.
Here is a short and sweet way to unroot your xoom. by doing this you will lose your data and information so start by backing up your stuff to a computer if you have any important things on there.
if starting fastboot is on your xoom screen open up a command prompt:
0. For those who've modified their boot splash graphic with Team Eos' Splash Screen Logo Maker make sure to restore the stock Motorola boot splash FIRST as this process doesn't touch that part of the system. (Posted by Bait-Fish *Thanks for the update*)
1. Goto: http://forum.xda-developers.com/showthread.php?t=1049485 for stock USA 3G and Wifi Images
2. download the files you need
3. extract all the img's into the tools folder
4. with the command prompt open type: cd "replace with tools directory location"
5. disconnect your xoom from your computer and shut off the xoom
6. at the prompt type: fastboot oem unlock
7. it will say waiting for device
8. now plug it into your computer and reboot into fastboot by holding the down volume button and power on
9. follow the on screen instructions and agree to everything
10. your device will reboot you will get the motorola dual core window
11. force restart device by holding volume up and pressing the power button right after the device shuts off hold the down volume button and press power button
12 you should now be in fastboot mode
13. then copy each line one by one into the command window. This will allow you to go back to factory settings like you bought it from the store
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata

Good write up. +1 for sticky if there's not something already.
Sent from my SPH-D700 using XDA Premium App

whats good about this post is that it has been fully tested by me with wifi and 3G versions of the xoom with no problems reported. This method has also fixed some RSD issues. I say some because some people have flashed wrong boot images and ruined fastboot on their xooms from seeing the desktop.

wow you would think with all the issues happening with oneclick root etc you would think this would be a highly read thread. lol.

Nice guide man.

Good to have a thread like this as I was one of those one-click rooters. Unrooted, semi-bricked and learned ADB. If you're going to play with your Xoom, at least have a general idea of ADB.

Please add that this instruction (original post) is only appliable to US Xooms. Not EUs

Thanks!
Thank you so much!
I was also a clueless one-click rooter. I'd tried everything to get rooted again. This was by far the clearest and saved my hanging around waiting for a one-click unroot solution.
Cheers

your welcome enjoy your xoom.

I already upgraded to 3.1, and I unlocked it, but I can't get CWM to work, so I can't root. Can I use this method to go back to the older HC and relock, then go back to 3.1? I bricked mine before, trying to unroot and relock (I know...I know...) I've been adb'ing like crazy trying to get CWM to work, but I feel like giving up and going back to lock, stock, no barrel.

you can if you want it wont hurt the xoom which xoom do you have wifi or 3g?

I have the wifi, running 3.1, build HMJ37

if you go back to 3.0.1 you can root it, install clockwork, then upgrade to 3.1 using clockwork method. its pretty simple. within 25-30 minutes you can be running with clockwork and 3.1 rooted.

I learned my lesson! And the forum saved me.
I did the one-click root back when I got my Xoom a couple months ago, and then when I tried un-rooting and relocking to get the 3.1 update, I bricked it (you're welcome, angel) and sent it back to Motorola. When I got it back, I tried rooting the long way, but couldn't push CWM onto it. I got lots of help and tireless support from a forum member, and finally got it unlocked, rooted, CWM'd with SD support....re-lovin' the Xoom now. And I'm glad the guy that helped me out made me re-check re-download, and redo everything just to make sure we weren't missing any steps.
I love the Xoom NOW, but when I got it back from getting fixed, I was so not happy with it being unrooted! I love to toy with stuff, and this was a real learning experience. Doing all the commands, getting the stock images, re-flashing....it was very rewarding, even though it took so long to figure out how I screwed up. (can you believe it was a usb cable that wasn't working that made it so difficult! Pushed some things, but not others....changed cables, and everything worked fine.)

Nice walk through. I don't think I'll be unrooting anytime soon but its good fyi.
Sent from my Xoom using XDA Premium App

this tutorial should be more helpful now.

dirtymindedx said:
this tutorial should be more helpful now.
Click to expand...
Click to collapse
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom

bwcorvus said:
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom
Click to expand...
Click to collapse
how do i go about doing that.

dirtymindedx said:
how do i go about doing that.
Click to expand...
Click to collapse
I would just edit line 1 to say you can get from moto at blah blah or download from blah blah so you don't have to log in.
http://forum.xda-developers.com/showthread.php?t=1049485
Sent from my Xoom

nice set of links definitely treasure in my book. Can you post a link on there to this thread since they still haven't stickied this yet?

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

[Q] Bricked MZ602 seeking 1.35-everest.reflash.sbf

Hello,
I love my Xoom MZ602 but right now it's bricked while trying to repartition. I've faithfully executed everyone's solution, but nothing's working. Several posts say I need:
1.35-everest.reflash.sbf
which has links all round but they're all dead!! Does anyone have it? HELP
Thanks very much!!

donriner said:
Hello,
I love my Xoom MZ602 but right now it's bricked while trying to repartition. I've faithfully executed everyone's solution, but nothing's working. Several posts say I need:
1.35-everest.reflash.sbf
which has links all round but they're all dead!! Does anyone have it? HELP
Thanks very much!!
Click to expand...
Click to collapse
Thought i would try and help you out since i have some old xoom files laying around. However, i am confused about while files you need.
MZ600: 3g xoom for Verizon US called stingrayCDMA(maybe?)
MZ601: 3g xoom for GSM called everest
MZ602: 4g lte xoom for Verizon US called stingray
MZ603: WiFI only xoom called wingray
MZ603: WiFi only xoom called wingray
So the everest file you need will not work on an MZ602.
Test question is, do you have an MZ602(Stingray) or an MZ601(everest)?
Let me know, and I will see if I can find the right file.
PS: Also, what is your region/language?

urushiol said:
Thought i would try and help you out since i have some old xoom files laying around. However, i am confused about while files you need.
MZ600: 3g xoom for Verizon US called stingrayCDMA(maybe?)
MZ601: 3g xoom for GSM called everest
MZ602: 4g lte xoom for Verizon US called stingray
MZ603: WiFI only xoom called wingray
MZ603: WiFi only xoom called wingray
So the everest file you need will not work on an MZ602.
Test question is, do you have an MZ602(Stingray) or an MZ601(everest)?
Let me know, and I will see if I can find the right file.
PS: Also, what is your region/language?
Click to expand...
Click to collapse
Thanks for helping... It's definitely an MZ602 - Verizon 4GLTE. The device accepts flashing through Fastboot or RSD, but will not save anything. I think the partition table must be gone. There is NO Recovery. Someone else suggested this file would help even on the "wrong" device. Desperate at this point will try anything.
Region - USA
Hope you have something or an idea.

donriner said:
Thanks for helping... It's definitely an MZ602 - Verizon 4GLTE. The device accepts flashing through Fastboot or RSD, but will not save anything. I think the partition table must be gone. There is NO Recovery. Someone else suggested this file would help even on the "wrong" device. Desperate at this point will try anything.
Region - USA
Hope you have something or an idea.
Click to expand...
Click to collapse
METHOD 1:
If you haven't tried it already, download this http://www.mediafire.com/download/klylgjtuy42y625/HRI39.zip, extract and flash using the following fastboot method.
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
METHOD 2:
Can you flash a custom recover in fastboot or does it fail? If it fails, what exactly is the error?
If you can successfully flash a custom recovery image, try following this guide. I know it is intended for removing a "BigPart", it should be able to recreate your partition tables if you can flash recovery.
http://forum.xda-developers.com/showthread.php?t=2635282
METHOD 3:
You can also try this SBF file which is an SBF of the newest stock rom for the MZ602
http://sbf.droid-developers.org/download.php?device=24&file=710
IF NONE OF THIS WORKS
I have searched high and low and can't find a copy of the 1.35-everest.reflash.sbf, however i understand what you were thinking, i found many people talking about this file as a method for recovery. If non of my methods above work, maybe someone still has the everest sbf in question laying around.

Please help to restore old xoom
Please help restore old Xoom mz600. It stuck in moto logo.
Recovery doesn't work too, stuck in "Reading ODM fuse: 1".
After long investigation I get it is problem with bootloader.
Maybe somebody still have this magic file 1.35-everest.reflash !!!

1.35-everest.reflash.sbf
Finally I found these files, thank you KidJoe:
1.35-everest.reflash.sbf
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
My xoom comeback to live!!!
If somebody need it, send the message I will share it.

kleralexi said:
Finally I found these files, thank you KidJoe:
1.35-everest.reflash.sbf
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
My xoom comeback to live!!!
If somebody need it, send the message I will share it.
Click to expand...
Click to collapse
please send 1.35-everest.reflash.sbf to me,thank you very mach!
emil:[email protected]

kleralexi said:
Finally I found these files, thank you KidJoe:
1.35-everest.reflash.sbf
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.sbf
My xoom comeback to live!!!
If somebody need it, send the message I will share it.
Click to expand...
Click to collapse
Why not share it in the public thread? lets be honest you won't be here to respond to stuff forever so you might as well drop a link in the thread for future collectors everywhere. And PLEASE use Android File Host, it seems to keep files forever and i don't see it going down anytime soon.

links to files
1.35-everest.reflash.zip
HRI39.zip
VZW_MZ600_Signed_HRI39_Signed_MDM600BP_C_02.0F.00R_SW.combo.zip

thank you very much !
thank you very much !