Database Develop

[Q] Captivate Boot Loop after Odin one click

Hello all and thx in advance.
ATT Captivate batch 1010
I had Cognition 2.3 I think on my phone and it worked great however I wanted to try a different ROM so I attempted to restore my phone to stock using ODIN one click. I realized after that that I never disabled the voodoo lag fix or deleted my user data.
Now I am stuck in a boot loop that either shows the white ATT logo screen flashing every couple seconds or the phone off charge screen re starting every couple seconds.
I bought a USB Jig and it works great so I can get into D/L mode easily but I have tried flashing the stock firmware at least 6 times now using different machines, different ports, different versions of ODIN and I've searched around these forums and others for several hours trying to find a solution. It seems that I needed to erase my user data in recovery mode and removed the lag fix before I did this but it is what it is. I have tried to get to recovery mode to no avail. All I can get to is download mode.
Any ideas on what I should/can do?
any help will be greatly appreciated.
Rob

Aircraft123 said:
I realized after that that I never disabled the voodoo lag fix or deleted my user data.
Click to expand...
Click to collapse
Neither are necessary for Odin use.
ATT Captivate batch 1010
Click to expand...
Click to collapse
I think that you may need to use the Froyo Odin (JI6).

http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
CM7

please help, i have the same problem, was flashing back to stock from a serendipit 5.12 so that i could get the 6.0 version... all went as planned until odin said "reset" which was my cue to unplug and that the process was complete.... i unplugged the phone and tried to reboot and now it does exactly as the first post described, at&t logo then black screen, then back to the at&t logo then black screen again... my computer doesnt recognize my phone none of the methods of getting to download screen will work... no matter how many times i pull the sd, sim, and batt, no matter the button combination i use or which order i use them in.... same result... i cant afford a new phone i need help, i will donate also... i knew this stuff was over my head, but "curiosity killed the cat" i guess...

I had the exact same problem. Try this method, it's the one that worked for me when all others failed... But remember to follow it EXACTLY.
1. Pull out the battery.
2. Hold Volume UP+DOWN (Don't let go of them until you see the download screen).
3. Stick in the USB (which is connected to the computer).
4. Put the battery back in.
If not, you might need to get a USB Jig.

That Froyo Odin link worked!
Thanks guys I flashed to Froyo and it worked!
I've since flashed clockwork recovery and gotten Serendipity 6.1
As far as getting into download mode I had to use one of the USB jigs.
I ordered one from the guy who does the rom reviews but you could make one as well.
On another note the new ROM seems to be discharging my battery really fast
Before I start investigating it as a problem I am going to charge it completely then let it discharge completely to calibrate it.
Thanks again guys
Rob

I just fixed mine last night, I had the exact same problem because of the exact same upgrade. What you need to do is get or make a usb jig. There's a couple resources around here for how to do it.
Here's a video showing how to make one:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
Once I got my phone into download mode, I used Darky's ROM Resurrection Edition ( http://forum.xda-developers.com/showthread.php?t=940671 ) to restore my phone. Just scroll down to where it says "Files Needed" and download the Captivate version. Once you have that downloaded, use the jig to put your phone into download mode and follow the directions in the Darky's video (jump to about 2:30 into the video). Once I had my phone booting, I used clockwork to install Serendipity 6.
Hope that helps you as much as it helped me!!

went to radio shack, got all the stuff to make a jig and i was able to get my phone into download mode! now to try darko...... thanks everyone!

odin doesnt reconize phone

which odin3 are you using? 1.7? or the one click to stock?
you mentioned you had the bootloop problem before, so you should be using odin 1.7 with 2.2 stock.
open odin
get phone into download mode with your nice jig
unplug jig and plug in computer
box in odin should turn yellow.

And make sure you have the correct drivers installed. CRUCIAL.

Multiupload links not working
I'm stuck in the same situation as the OP.
I've been trying to use the method mentioned in the quote below, but the multiupload links are not working for me. I've been trying for 2 days to get to these files.
Breakin' Ranh said:
**Another thing, read the whole thing before doing it! If you're not confident whatsoever about this process, don't do it**
1. Download the following:
I897UCJH2 Firmware
password: samsung-firmwares.com
http://www.multiupload.com/B5OFPPOJFZ
512 PIT
http://www.multiupload.com/I5WICSBFJ1
ODIN3
http://www.multiupload.com/DLS7TWUVPY
Click to expand...
Click to collapse
Here's a link to the thread for more clarification:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36I've
Would anyone happen to have these files and be willing to share them?

^
Have u tried the Odin or Heimdall One Clicks in the development stickied thread ??
Sent by XDA Premium App

Yep, tried the Odin one click - caught in a boot loop with the AT&T Logo. I have yet to try the Heimdall one.
UPDATE
Tried Odin and Heimdall One-Clicks - unsuccessful. I'm think I will need the stock Eclair firmware file with Odin and the pit file.

lllll Nova lllll said:
Yep, tried the Odin one click - caught in a boot loop with the AT&T Logo. I have yet to try the Heimdall one.
UPDATE
Tried Odin and Heimdall One-Clicks - unsuccessful. I'm think I will need the stock Eclair firmware file with Odin and the pit file.
Click to expand...
Click to collapse
You ever get this to work? - I'm in a similar situation. all flashes 'work' but get stuck at ATT on boot. Not sure Eclair is an option or not since mine is a refurbished phone that started on 2.2

ScruffMcG said:
You ever get this to work? - I'm in a similar situation. all flashes 'work' but get stuck at ATT on boot. Not sure Eclair is an option or not since mine is a refurbished phone that started on 2.2
Click to expand...
Click to collapse
If one-clicks aren't working, you might need to grab the full version of Heimdall or Odin and flash a full package. Some of the newer phone builds don't like one-clicks.

^ +1
See this thread...the original Stock i897ucKK4 thread... http://forum.xda-developers.com/showthread.php?p=19587108
Then see post #57 for the regular Odin to use and instructions on what to do with the firmware.
Sent from my SAMSUNG-SGH-I777 using xda premium

[Q] Captivate Soft Brick - Need a rooted Odin solution.

Hi
My brother (a no-geek) has a captivate, and lives in a different city (I donot have physical access to the phone). He visited me few weeks ago and I installed CM-7 on his phone, i know my bad. Some of his videos were not working, so i asked him to update to the latest CM-7 build. He download the build, saved it on int sd_card and used ClockWork Recovery to install the selected ROM. Upon reboot it entered in never-ending splash screen. I found couple of odin ROMs, and posted him link, we tried to flash them, but no good.
Status --
The COM ports are detected, but the process at times halts at <SET PARTITION> at times at <SET UP>... at times all thread completed successful would show up as soon as hitting START.
I dont have a captivate, can someone please suggest a sure shot solution and post me a link for ODIN, with a root rom. I am using Team Whiskey on my Vibrant, and I prefer stable modified ROM because of its features and power.
I can explain him the process on skype using desktop sharing, but the ROM should be good. Thankyou very much in advance.

if he can access recovery, try wiping everything thru recovery then start again

Phone is in Soft Brick state.
Phone is in Soft Brick state. So i cannot boot into the phone and go to CW recovery.

What he needs is just a stable usb connection that's how he got to this point, bad communication between the phone and computer. On cm7 I beleive you need the nexus s drivers installed. Also make sure it's plugged into a usb port that's attached directly to the motherboard (back of pc, port 1 on laptop)

@studacris
I think the drivers are already installed good. The connection is also good, as i can the COM port detection in the ODIN, with one of the boxes changing its colour from NO-COLOUR to YELLOW-COLOUR.
I think the ROM builds are not good. They go action-less during flashing, actually nothing (progress bar) comes on phone, it keeps showing the Downloading screen, endlessly. Odin usually is stuck at at <SET PARTITION> at times at <SET UP>...
Can someone post a link for a test one click odin. Well i would prefer one click.

You did try DG's JF6 one click, thats the only one I use, how are you establishing dowload mode on the phone or are you even doing this.

REMY4223 said:
I would suggest to Odin back to stock then update to Froyo via Kies.
Click to expand...
Click to collapse
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament

Ragin Caucasian said:
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Click to expand...
Click to collapse
+1 If you read the OP the problem is he can't flash back to stock he is having problems flashing anything period, @ the OP correct me if I'm wrong but I have a strong hunch that you are leaving out some pretty crucial steps, I have a feeling that you are not putting the phone into download mode, I also believe that you are gonna need to make a jig and pay a visit to your brother to help him out especially if its bricked the same way mine just was flashing with cm7 roms. But if you are getting a com port to show without having to put in download mode then you are farther along in the boot process. If this is the case you may be able to adb into recovery do a full wipe excluding /boot and reflash. Will the PC recognize the phone with it in its current boot locked state? If so then recovering should be somewhat of a breeze.
http://forum.xda-developers.com/showthread.php?t=829392 read this post it may help otherwise there are tons others

- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.

viveksharma2108 said:
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
Click to expand...
Click to collapse
Try putting the phone into download mode after you open Odin. Which version of Odin is this? Also, installing the nightly build of CM7 again often fixes the boot loop on the newer builds. I would try that if you can get to recovery.
Sent from my SGH-I897 using XDA Premium App

[Q] OH NO! Another noob bootloop thread :p

Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus

I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.

ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...

Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again

I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.

For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App

cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...

Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA

TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business

*removed double post

studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.

You have to hit enter at the Right moment, it takes practice

Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA

Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA

If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.

Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )

How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.

Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA

Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.

When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium

Please help i will donate/ pay u

I have a Samsung Captivate which has been rooted and unlocked...it was running 2.3.5 uckk4
I believe I got a virus from downloading some app that was not on the market well long story short I tried to flash it back to a different version
I believe I put something in odin bootload that I wasnt suppose to it was an accident as you see I am a total noob at this then I use the 1 click unbrick now my phone keeps rebooting itself but i looked at the about phone which i get to for a few seconds before it reboots itself again and this is what it says
Firmware
2.3.3
Baseband
1879UCKF1
Kernel Version
1897UCKK414489
BUILD
gingerbreadUCKF1
I have tried a master reset since I could get it into debug just that it keeps looping and it worked in odin but not on my phone and this is what it generated
<?xml version="1.0" encoding="UTF-8" ?>
- <REFLASH>
- <UNIT>
<ESN>00000000000000 /0</ESN>
<TIMESTAMP>20120424002823</TIMESTAMP>
<RESULT>_20120424002823</RESULT>
<SOFTWARE_NAME>Downloader</SOFTWARE_NAME>
<SOFTWARE_VER>3.00</SOFTWARE_VER>
<OEM_NAME>SAMSUNG</OEM_NAME>
</UNIT>
</REFLASH>
PLEASE HELP ME....if you can get my phone operational again I WILL DONATE MONEY TO YOU!
I have tried EVERYTHING and searched FAR AND WIDE!!!! I almost forgot Odin does not display my device anymore...ie such as com4...I really have tried everything that's why I am willing to donate/ pay you if you can solve my problem....if odin recognizes my device then it gets stuck halfway through. As of today my computer recognizes my device but Odin does not!
I have read and tried everything here
http://forum.xda-developers.com/showthread.php?t=858765
and here
http://forum.xda-developers.com/showthread.php?t=731989
and alot of other things listed and not listed on this site
NEW IFO: now I'm stuck at ATT logo and can not get into download mode

This thread will selfdestruct in 5...4...3...2...1....

DANG IT wrong section? SORRY MODERATORS!!!! SORRY

Please dont delete please just move it please!!!!

oh goodness... No need for donation but all you need to do is download a stock package odin like kk4 which is the most recent. Flash in download mode. There a sticky at the top of the thread list with all the packages.
In the future post in the questions/help section.

diskjockee said:
DANG IT wrong section? SORRY MODERATORS!!!! SORRY
Click to expand...
Click to collapse
Ok I gave you the only warning in the PM. I have moved this thread. A word from the wise. Learn what you are doing before you do it. This is not something to be taken lightly. You could very easily mess something up beyond repair. Take a few hours to spend reading and researching.

ThisWasATriumph said:
oh goodness... No need for donation but all you need to do is download a stock package odin like kk4 which is the most recent. Flash in download mode. There a sticky at the top of the thread list with all the packages.
In the future post in the questions/help section.
Click to expand...
Click to collapse
I have tried that it doesnt work. thats was one of the 1st things I tried

try this
http://forum.xda-developers.com/showthread.php?t=1266172

Make sure you're using a usb port that is on the motherboard (back of computer). Before you plug in your phone to flash, set up Odin first. Put all the files you are going to flash in the right places. After Odin is fully set up, plug in the usb to the back of your computer, then to you phone. Make sure you are in download mode. If the usb still isn't working, try a different USB port that is on the back of the computer. Connecting the usb to the back of the pc is very important. Odin doesn't recognize my phone when it's plugged in the front, when the phone is in download mode. Only the back usb ports.
If Odin still doesn't recognize the phone, try a different USB cable. But do everything else the exact same way as I described.
Also make sure you fully setup Odin before you plug your phone in to the usb.
Sent from my Serendipity VII flashed Captivate using xda premium

Limitz Cash said:
Make sure you're using a usb port that is on the motherboard (back of computer). Before you plug in your phone to flash, set up Odin first. Put all the files you are going to flash in the right places. After Odin is fully set up, plug in the usb to the back of your computer, then to you phone. Make sure you are in download mode. If the usb still isn't working, try a different USB port that is on the back of the computer. Connecting the usb to the back of the pc is very important. Odin doesn't recognize my phone when it's plugged in the front, when the phone is in download mode. Only the back usb ports.
If Odin still doesn't recognize the phone, try a different USB cable. But do everything else the exact same way as I described.
Also make sure you fully setup Odin before you plug your phone in to the usb.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
I just tried that....it worked but now I'm stuck at the ATT logo

You probably have mismatch kernel and bootloader loader. Maybe you can try to wipe data / factory reset in recovery.
Sent from my Serendipity VII flashed Captivate using xda premium

If you continue to go into a bootloop then I recommend a USB jig for the galaxy s series. I had had that happen before, Nothing worked, couldnt get it into download mode, couldnt get into recovery, Until I got the USB jig, Fixed my problem right away, and I flashed back to stock. The USB jig is only 6 bucks on ebay. Ill link you if you are interested.

Limitz Cash said:
You probably have mismatch kernel and bootloader loader. Maybe you can try to wipe data / factory reset in recovery.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
I know you're trying to be helpful, but there is no such thing as a kernel/bootloader mismatch...

b-eock said:
I know you're trying to be helpful, but there is no such thing as a kernel/bootloader mismatch...
Click to expand...
Click to collapse
Are you sure? Becuz I tried to flash an overclock kernel on my rom, and kept getting a bootloop. Then after flashing a few different kernels, the kernel that came with my rom didn't even work. I had to go back to stock and reflash my rom.
Idk, maybe it was just me then. I apologize. thank you for correcting me, that's how we learn what's right, and what's wrong.
Sent from my Serendipity VII flashed Captivate using xda premium

noob advice
I'm a noob, so this comment might just serve to show how little I know, but whenever I find myself in a bootloop situation, I've noticed that the problem starts with the initial attempt of installing a rom via a kernel with an older version of CWM. During the post-install boot sequence, I'll see the AT&T splash screen, a CWM screen with script running, and then a reboot. Usually, accessing the CWM (now on a higher version) and reinstalling the rom will get it working. Not quite kernel / bootloader mismatch, but close.

whisky23 said:
I'm a noob, so this comment might just serve to show how little I know, but whenever I find myself in a bootloop situation, I've noticed that the problem starts with the initial attempt of installing a rom via a kernel with an older version of CWM. During the post-install boot sequence, I'll see the AT&T splash screen, a CWM screen with script running, and then a reboot. Usually, accessing the CWM (now on a higher version) and reinstalling the rom will get it working. Not quite kernel / bootloader mismatch, but close.
Click to expand...
Click to collapse
Ohh ok. That might have been my problem before. Thank you.
Sent from my Serendipity VII flashed Captivate using xda premium

Try this.
Buy a jig. Either off of Ebay or mobiletechvideos.com
That week get you into download mode.
Then find the HEIMDALL flasher for a build. (my favorite was the one click for saurom Kk4)
Install heimdall drivers, and flash. Boom. Functioning phone.

Can no longer enter recovery after flashing back to stock from another ROM. Weird!

I had tried flashing the SlimBeam ROM (coming from Helly Bean, which worked great), but got the perpetual AT&T logo of death. This seemed to be an issue with several other users, as pointed out in the SlimBean thread.
To resolve this, I flashed back to stock with a Heimdall One-Click utility. Stock now boots great and the phone is functional (albeit now running a very old version of Android). I was looking to root again to go back to Helly Bean. However, I can no longer enter recovery mode with either the 3-button method or ADB. When the phone is told to enter recovery, it just hangs at the AT&T logo, just like when it was trying to boot SlimBean.
I can restart the phone into the stock ROM and I can also successfully enter download mode. Recovery just isn't happening.
Any ideas on what I can try at this point? I'm on a Mac but have access to a PC if necessary.

Have you tried flashing a stock rom with bootloaders? I hate suggesting that, but sometimes re-flashing the bootloaders makes a difference.
Just make sure you're careful to have a solid connection throughout the flash.

themilstead;30584149
To resolve this said:
Which stock did you flash back to? I've only done it (but lots of times) with Odin-one-click, not Heimdal but not all the one-click packages contain CWM.
You could try one of these:
http://forum.xda-developers.com/showthread.php?t=1300843
Click to expand...
Click to collapse

Ah, I don't remember if the Heimdall package came with a bootloader (I did this earlier today at the office, and I'm home now). When I was restoring earlier, Odin wouldn't recognize that my phone was connected in download mode...hence me using Heimdall. I'll give Odin another shot right now since I'm up and running with stock.

There are Heimdall packages with bootloaders, if you need it.
Just remember that Heimdall will write its drivers to the port you installed it to - if you plug in your phone to that port and try to fire up Odin, Odin won't see it.

I'm on a different computer than when I used Heimdall earlier, so Odin is now recognizing the phone.
New problem: The process won't get past "SetupConnection". I'm currently trying out "I897UCKJ3 Stock with BL".
Rah rah rah rah rah.

^
See this thread by jmtheiss for help with ur prob. --- Captivate Connection Issues and Download Mode Help

Well, I'll be damned: The Epilogue
Got it!
It was simply a matter of me continuing to try other USB ports (my computer has 4). I tried one that previously didn't work, and it suddenly did. Not exactly sure what changed, but persistence paid off! I suppose power tolerance is potentially different for each port? (...in the same vein of it's better to plug into the back of the computer rather than a keyboard. I digress.)
Anyway, after Odin both recognized my phone and got past the "SetupConnection" step, I proceeded to install "KI2 w/ Bootloaders & Boog's KernO". This included ClockworkMod built-in, so I thought it'd be a good option. Sure enough, I was finally able to boot into recovery without any sort of trouble, then proceeded to install the new CM10 nightly.
Everything works. Thanks for the replies and help, everyone!