Read BEFORE flashing!!

[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://forum.xda-developers.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.

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

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.

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://forum.xda-developers.com/showthread.php?t=841512

Here's another thread about the USB Jig method.
http://forum.xda-developers.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.

 

[sublimaze]

+sticky

excellent write up. a must-read for anyone even thinking about flashing

 

[malfuncion]

Original Post updated to add my information

 

[sparker366]

ADB reboot download is nice, but if you are stuck at ATT logo

Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.

If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.

Steps

1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.

Mileage may vary but should work.

This has saved me a few times.

 

[bulletproof1013]

STICKY

Sent from my SAMSUNG-SGH-I897 using XDA App

 

[bobbylx]

Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.

I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.

 

[creepyncrawly]

STICKY

+1

This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.


Sent from my SAMSUNG-SGH-I897 using XDA App

 

[Pirateghost]

This thing is getting buried in the BS posts....BACK TO THE TOP!

definitely sticky

 

[tweek1020]

Bump Bump Bump

Great Info

 

[bobbylx]

Updated original post with extra info.

 

[bobbylx]

Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.

 

[HBeezy]

Thanks, great info.

 

[Scottbg1]

FWIW........

I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.

One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.

Thanks for the post, my vote for sticky as well.

 

[spartan07]

+1 sticky

Sent from my SAMSUNG-SGH-I897 using XDA App

 

[bobbylx]

Moving this to the top. More questions in QA that can be helped by reading these tips first.

 

[othermark]

I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.

The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.

Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).

This will ensure your USB connection is stable enough for long, error free transfers to the phone.

Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.

 

[bobbylx]

Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.

 

[ootz0rz]

Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!

 

[balishared]

thanks for the reminder

there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!

another good reason flashing stock with odin before flashing new rom

 

[mattbeau]

I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.