Read BEFORE flashing!!

[yahooserious]

On the bricked note, last night I was flashing back to JF6 with Odin one click. About a quarter way into it windows decided that my samsung usb drivers should quit and disable my my flash. The phone screen went a real dim red and that was that. Waited for 10 min+ but Odin saw no device nor Windows, Win 7Pro 64 bit, for that matter. Pulled the battery and nothing, no battery charging graphic, no home button lights, vibration, NOTHING! So I fiddled with it, rebooted the comp to no avail.

My sim and sd were already removed before flashing so I resurrected my Tilt just in case and went to the forums.

I found a post somewhere (can't remember where, sorry) about just barely making battery contact with the contacts on the phone while holding vol +- and power down with the USB plugged in and Odin running to get some sign of life.

I did this for about 5 min after letting the phone sit for 30 secs or so with no battery or usb card and got 6 lines of red text to come up then disappear.

Kept doing the "trick" and after about 10 mins the phone suddenly came on in download mode! Yes! , flashed to stock then put Perception 8 non oc/uv on with no problems.

This happened to me last night and i had never been bricked before. This was a serious problem but the solution was close to what you tried.
What I was told to do worked each time i needed to bring it back into download mode cause of multiple stalled re-flashes.
the method should make it to the top of this thread too as I have been successful every time.
remove sim, memory card and battery. Hold Power button to drain any residual power. Start odin on your computer. Press the volume rocker ONLY. Plug USB into computer. Put Battery into the phone. DONE!
I was hard bricked with black screen and 6 red lines of text.
The above methood worked EVERY time (i couldnt get a complete flash on my desktop..so i tried on my notebook and flash went 1 time smooth as silk.)
Cheers and thanks to all the helping hands in this community XDA rocks!

 

[tazman171]

Glad it worked for you too yahooserious. It took a while for me to get it to work as it was DEAD, but the hour of constanlty trying seemed better than the $300 or $400 option that was on the table.

The method you used for DL mode is what I always used when a flash "stalled" but mine was beyond that, it was lifeless as in no charge indicator, lights, buzzes, anything for a good 4 or 5 hrs. Never had that before but also never had windows dump my usb drivers while in the first stage of flashing to stock.

Just wish I could find the post where the guy was talking about lightly contacting the battery to the contacts repeatedly. I know that's what shocked the phone back to life as I had tried everything I could find in many different forums, but that was what got the red text briefly, 6 lines. I knew then that it wasn't hopeless.

 

[1tontomato]

I had this exact problem over thanksgiving weekend. My phone was was was hard bricked I was getting the "phone + computer" it took some effort to get it into download but I got it there and when I was recovering with odin the connection got lost the screen went blue and then nothing. It was dead totally unresponsive no charging or boot screen nothing but once I got a black screen with redlines. After a lot of attempts to revive it I gave up called ATT warranty for a replacement. Luckily I opted for the slow mail service and kept reading. Yesterday I saw the above post and now I can say "yes even now your phone is not bricked even though it does NOTHING"

step 1) first thing I did was charge the battery with my replacement phone as the bricked phone was no longer able to charge the battery

step 2) open odin1 click and hooked up the usb to the phone and computer no battery

step 3) inserted the battery holding only volume up+down

step 4) "BOOM" download mode and a happy dance

 

[xdeslitx]

nevermind...took a gamble and it worked

 

[tazman171]

Right on 1tontomato and xdeslitx! Glad it worked for you guys, great feeling when that download screen finally came up huh! Really glad to see this working for other people!

 

[DroidAsk]

Hi all,

Please help me. I feel like an idiot. I did not set usb debugging mode before attempting to flash a voodoo kernel. Now I get the phone-!-pc screen all the time. I can still get into download mode though, but no luck getting into recovery. Is there anything I can do to save my situation?

 

[silverslotcar]

Download odin one click jf6 then open it on your pc (assuming u have the right drivers installed) then put your device into download mode then plug it in via usb and flash.

sent from my cappy running Di11igafs Rom 2.5 overclocked at 1280 with JK4 modem!!!

 

[DroidAsk]

Hi silverslotcar, my phone is the international version of galaxy s and not the captivate. I had my problem reposted in the correct phone model forum now but will this work for the international version of galaxy s too?

 

[silverslotcar]

Nooooooo sorry. Its captivate specific.

 

[DroidAsk]

Oh well.. thanks anyway silverslotcar. I should have been more careful and made sure I set to usb debugging before attempting to flash voodoo.

 

[tazman171]

Hi all,

Please help me. I feel like an idiot. I did not set usb debugging mode before attempting to flash a voodoo kernel. Now I get the phone-!-pc screen all the time. I can still get into download mode though, but no luck getting into recovery. Is there anything I can do to save my situation?

If you can get to download mode you're in great shape! Odin is what you need for your phone now. Odin is Samsung's flashing software and there are version for your divice. Now that your post is moved to the correct thread I'm sure you can find an Odin version that will work for you.

Read this page from the I-9000 thread;

http://forum.xda-developers.com/showthread.php?t=810682

AND DEFINITLY THIS ONE;

http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Recovery_Mode

Save that page and understand it and refer to it. Understanding the ins and outs will save you a lot of grief, like your current sitrep.

 

[malicenfz]

Thank you for this thread, I'm about to attempt to learn some basic commands on the SDK

 

[avgjoegeek]

Added to the Q&A sticky - hopefully more people will read this before posting in the Dev/Q&A forums now.

 

[bobbylx]

Nice. One of these days I'll add some images back to the original post showing how to add SDK tools to windows PATH.

 

[reinbeau]

Nice. One of these days I'll add some images back to the original post showing how to add SDK tools to windows PATH.

Please do!

 

[CatalystWon]

I suggest you add a section to say that you should get your unlock code while you're still on stock before jumping to 2.2 (which will wipe the code from your device)

I suggest SuperOneClick

Thank you CLShortFuse.

I'm looking for a pre-owned Captivate. It may have stock AT&T 2.2 on it (not sure). If so, does this mean I can't unlock it???

Any advice is appreciated!

 

[BAleR]

for some reason I cannot get adb working, when i goto cmd and type in adb shell it says it is not recognized as an internal or external command, operable program or batch file


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.


I did that, i downloaded sdk, installed samsung drivers, put the sdk in C: named it SDK, I added ;C:\sdk\tools to the system variables reboot, and it gives me that error. can anyone help me with this please? I'm on winxp net4 framwork im not sure what im missing

 

[Reynaldinho111]

for some reason I cannot get adb working, when i goto cmd and type in adb shell it says it is not recognized as an internal or external command, operable program or batch file


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.


I did that, i downloaded sdk, installed samsung drivers, put the sdk in C: named it SDK, I added ;C:\sdk\tools to the system variables reboot, and it gives me that error. can anyone help me with this please? I'm on winxp net4 framwork im not sure what im missing

Do you have the newest sdk?? If so open command prompt and do the following, hit enter after each line
cd\
cd AndroidSDK\platform-tools\

Then try your shell command.
In the recent sdk they moved adb from tools to platform tools.
sent from my beloved cappy!!

 

[BAleR]

Do you have the newest sdk?? If so open command prompt and do the following, hit enter after each line
cd\
cd AndroidSDK\platform-tools\

Then try your shell command.
In the recent sdk they moved adb from tools to platform tools.
sent from my beloved cappy!!

Thanks I just happened to read a txt that said that it moved, i updated the file and corrected it and works now. I do have a small question if you would be so kind, Im not sure what build my captivate is, how do I check for that? its on 2.2 and it says under system/about - Build Number: FROYO.UCKB1, and can I just use the superoneclick to root then go on to flash the GB BL and ROM?

 

[oxlong27]

Your build number is under your battery

Sent from my HTC Inspire™ 4G using XDA Premium App