[Captivate Android Development] bobbylx:
Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.

Terminology, the differences in my opinion.

Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.

Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.

Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.

1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.

3 Methods.

Method 1: (ADB - from recovery or normally booted with usb debugging on)

Open a cmd prompt/console/shell

adb shell

adb reboot download

Method 2: (KEY COMBO)

Remove the battery, sim card, sdcard if you have one

Insert the battery

Hold Volume Up + Volume Down + Power

Method 3: (KEY COMBO)

Remove the battery, sim card, sdcard if you have one

Insert the battery

Hold both Volume buttons (from i9000 just down, don't touch the power button)

Plug in the USB cable and continue holding both Volume buttons

If not, use designgears fix. http://xdaforums.com/showthread.php?t=812434

2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.

Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:

Then open a command prompt and type,

C:

CD tools

Then issue adb commands.

adb reboot, adb reboot download or whatever command you need.

Of course make sure your phone is connected via USB and debugging is enabled.

Here's another method for using adb.

1) start-> run-> sysdm.cpl

this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.

2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.

http://wtfokc.com/sef****/sysdm-1.gif

3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:

http://wtfokc.com/sef****/sysdm-2.gif

4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.

http://wtfokc.com/sef****/sysdm-3.gif

5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.

3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.

Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.

NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.

http://xdaforums.com/showthread.php?t=841512

Here's another thread about the USB Jig method.

http://xdaforums.com/showthread.php?t=819551&highlight=USB+jig

If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.

****Disclaimer****

This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.

I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.

This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.

Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.

Just my 2 cents, take it or leave it.

Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.