• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Bricked X--HELP

ninefall

Newbie
was trying to go back to 2.1 from 2.2. RSD flash failed, had to unplug phone. Now the bootloader screen says CODE CORRUPT and Cannot Program. I can only get this message when plugged into the wall charger. If i plug into USB to PC i get just a green light where the power light is.....any help or suggestions would be appreciated
 
can you get into recovery? (power + home, then hit search when the droid guy pops up). if you can, try that and try to do another wipe, then try to boot into bootloader again (without the phone plugged in to anything)
 
yeah, i figured. i've been googling it and i am beginning to understand the problem. when you plug it into usb, does RSD even recognize that there is a phone plugged in?
 
Sounds like you X has become a paper weight. You might be able to take it into a verizon store and see if they can replace it....just dont tell them what you did, they replaced my orig Droid when my phone wouldnt turn on...it was rooted and overclocked...
 
RSD wont recognize it whatsoever. Cant do a warranty on it because im an employee of vzw. thank god for insurance

So since you work at VZW you dont get a warranty? that sucks, when i worked for a local phone company I got free phones....and if one broke i got another free one, but I worked in IT.
 
i get a warranty but as an employee its not worth dealing with the hassle of explaining why my phone is stuck in a corrupt bootloader mode
 
Yikes! :( This is the reason I'm avoiding downgrading to 2.1... I've never had to use the .sbf (yet... I guess i'm lucky) but I'd rather avoid it while I can. I'm sure I'll have to use it eventually, given how much I like to tinker with my phone.

Have you tried this? (from droidforums.net-- Unbricking Your Droid X - Droid Forum - Verizon Droid & the Motorola Droid Forum)
"Code Corrupt" Error
Some Info
Chances are that if you are getting this error, you probably tried to reflash the .sbf and something went awry (for me it was that I only waited to charge the battery for 10% ).
Symptoms
You'll know your at this screen because, well, you'll be scared to death for your phone. This screen looks like the bootloader screen but it says "Code Corrupt" on it. If the screen says that your battery is okay and RSD Lite can still see it when you connect it to your computer, scroll up to The Infinite Boot Loop and go to the section How to Fix in order to fix the error.
How to Fix
One thing that you may notice is that when you have this error, your phone will not charge the battery and you'll only be able to see the screen turn on if its plugged into the wall. Somewhere on the screen it will say "Your Battery is Low" and "Cannot Reprogram" or something like that. The easiest way to get through this is to find a friend with a charged battery or go to your local Verizon store and see if they have a demo phone they can use to charge your battery. If you're like me though you will not be lucky in any sense like this so you will have to find the MacGyver inside of you and get a little creative. What you need for this is an old USB cord. One end must be a standard USB cable head and the other can pretty much be anything. Once you have that, follow these steps:

NOTE: I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO ANY PHONE, BATTERY, ETC. FOLLOW THESE STEPS WITH CAUTION TO AVOID RISK OF DAMAGE.

1. Take your cable and cut off one of the ends, leaving a standard USB plug at the opposite end to plug into your computer.

2. Now you need to strip about and inch of the wire off until you get to the core where you should see 4 colored wires (red, black, white, and green). The colors don't really matter and they may vary, just as long as you can see a red wire and a black wire.

3. Strip off about a quarter inch of the rubber sleeving on the red and black cables, exposing the actual metal wire.

4. Twist the metal strands of each of the wires a couple of times so that all of the wires from the black cable are together and all of the wires from the red cable are together. This is just to make sure that you don't create a short circuit.

5. Here's where it gets a little tricky. You are going to use this cable to make the phone think the battery is fully charged, when in fact you will just be powering the phone using the power from the USB port. Pull out the battery on your phone and find the 4 exposed metal slots (the battery terminals).

6. Each of the far terminals should be labeled with a plus (+) or a minus (-). What you need to do is put exposed leads on the red wire up to the positive terminal and the leads of the black wire up to the negative terminal.

7. While still holding the leads on their respective terminals, slide the battery back into place in the phone. MAKE SURE THE WIRES ARE NOT TOUCHING WHEN YOU PUT THE BATTERY INTO THE PHONE! BAD THINGS COULD HAPPEN ONCE YOU PLUG THE CORD INTO THE COMPUTER!

Note: As tested by parm289, you can skip step 7 and just use the cable to charge the battery if you'd like. He recommends allowing it to charge for 6-7 minutes before placing it back into the phone. Thanks parm!

8. Once the battery is in place and the wires are on the correct terminals but not touching each other, plug the USB cord into the computer. If all has gone as it should, the screen on your phone should come on (may have to press the power button) and the phone should be telling you that the battery charge is okay and that it is okay to program. YAY! Your phone is almost back to normal!

9. Go back up to the previous section in this post that tells you how to reflash the .sbf and follow all of the instructions there. Once that has finished flashing the .sbf to your phone, your phone should be back to working order! You will most likely have to redo the entire setup on your phone but at least your phone is no longer a fancy paperweight
 
that.....sounds stupid hard

Yeah well there's more to the article. Thats only if your battery is dead while you get the code corrupt error. If its not, then maybe the rest of the article may be helpful. IDK if the OP had tried the first steps or not.
 
i came across it about an half hour ago.....by far the most ghetto thing i have ever done. i was a little nervous about doing it. but all be damned it worked. stripped a usb cable down, connected the pos and neg to the 2 terminals on the droid, threw the battery in and she fired right up. phone is back to flashing in rsd which is good. think everything is gonna be good. appreciate the help from everyone by the way.
 
i came across it about an half hour ago.....by far the most ghetto thing i have ever done. i was a little nervous about doing it. but all be damned it worked. stripped a usb cable down, connected the pos and neg to the 2 terminals on the droid, threw the battery in and she fired right up. phone is back to flashing in rsd which is good. think everything is gonna be good. appreciate the help from everyone by the way.

wow lmao I hope I never have to do that hahahahaha
 
i came across it about an half hour ago.....by far the most ghetto thing i have ever done. i was a little nervous about doing it. but all be damned it worked. stripped a usb cable down, connected the pos and neg to the 2 terminals on the droid, threw the battery in and she fired right up. phone is back to flashing in rsd which is good. think everything is gonna be good. appreciate the help from everyone by the way.

Reading what you had to do frightened me a little bit. Glad everything seems to have worked out. That thread saved you some money for sure. Gotta love these forums.
 
i came across it about an half hour ago.....by far the most ghetto thing i have ever done. i was a little nervous about doing it. but all be damned it worked. stripped a usb cable down, connected the pos and neg to the 2 terminals on the droid, threw the battery in and she fired right up. phone is back to flashing in rsd which is good. think everything is gonna be good. appreciate the help from everyone by the way.

As an electrical engineering student, I love stories about almost destroying expensive electronic devices and then doing something incredibly ghetto to fix them.

I once accidentally broke two pins off my desktop's AMD processor. After freaking out appropriately ("Oh, f&#* me! Oooooh f&#* ME!"), I went and yanked out the Pentium 4 from my old Gateway, cut off a couple of its pins, dropped them into the respective mobo pin holes, replaced the processor, took a deep breath, and turned the computer on. That was 4 years ago. Desktop still runs great.

Jason
 
As an electrical engineering student, I love stories about almost destroying expensive electronic devices and then doing something incredibly ghetto to fix them.

I once accidentally broke two pins off my desktop's AMD processor. After freaking out appropriately ("Oh, f&#* me! Oooooh f&#* ME!"), I went and yanked out the Pentium 4 from my old Gateway, cut off a couple of its pins, dropped them into the respective mobo pin holes, replaced the processor, took a deep breath, and turned the computer on. That was 4 years ago. Desktop still runs great.

Jason


LOL FOUR years and STILL running! Cool story.


@OP glad things worked out for you.
:)
 
what an incredible story!!! The saving of an X! I am teary eyed!!! escaped into the wild, brought back to safety!!!
 
glad to hear it worked but couldnt you just leave the phone plugged in until it charged OR charge the battery on one of the battery chargers sold on ebay? just a thought
 
Dude.. did you read my guide..

Go look for it on the main page. It has a video to walk you through step by step.



All the best,
Eric
 
Sounds like you X has become a paper weight. You might be able to take it into a verizon store and see if they can replace it....just dont tell them what you did, they replaced my orig Droid when my phone wouldnt turn on...it was rooted and overclocked...

Please don't encourage fraud. If a user is messing around with leaked roms and stuff like this, they should know very well what the risks are and that they are not covered under warranty. Abuse of the return system is the reason these phones are so expensive in the first place.
 
Great story ninefall!

Had a similar experience over the weekend -- pretty much bricked my Droid X too, but I was fortunate that I didn't have a corrupt bootloader on top of it! I think I would have @$%! my pants. :mad:

RSDLite DID NOT work for me. It was all about Linux and the command line that saved my phone from the land of the brick! ;)

My little story is that I tried to update Friday night, put SU command into xbin folder instead of copying it, tried the update that wouldn't work since I rooted and deleted City ID.apk and resulted in a Moto symbol staring me in the face for an hour. I was so pissed -- so I took it out on my fianc
 
Dear God I hope I don't have to do anything like this when the official Froyo comes out. My phone is running great but I admit it will suck if I have to downgrade to 2.1 in order to do the official 2.2 update.
 
glad to hear it worked but couldnt you just leave the phone plugged in until it charged OR charge the battery on one of the battery chargers sold on ebay? just a thought

Apparently when it's corrupt like that the battery doesn't charge when plugged in. Op could have gotten a battery charger but he would've had to wait for it to come before evem knowing if his X could be saved.
 
As an electrical engineering student, I love stories about almost destroying expensive electronic devices and then doing something incredibly ghetto to fix them.

I once accidentally broke two pins off my desktop's AMD processor. After freaking out appropriately ("Oh, f&#* me! Oooooh f&#* ME!"), I went and yanked out the Pentium 4 from my old Gateway, cut off a couple of its pins, dropped them into the respective mobo pin holes, replaced the processor, took a deep breath, and turned the computer on. That was 4 years ago. Desktop still runs great.

Jason

Being a network engineer, that gave me hot flashes all over..LOL..
:p
 
Back
Top Bottom