Database Info

Constant Loss of Single/Odin 1 Click Boot Loop

Background. Was using 2.2 for the longest time, loved Firefly. Went ahead and bit the bullet and decided to go to 2.3 and use Gingerbread. Solid week of great success. However I started notcing my antenna saying no signal. Several Reboots and still nothing worked. Decided I would One-Click Back to 2.1 and start fresh. Well I never had issues with Odin 1 Click before, but now I get in a boot loop (ATT SPlash Screen) I have noticed when its unloading the package after , the last thing i see is CSC and that it boots into the loop. Would love to get my phone back to stock so i can see if its a hardware or software issue with my antenna. I have looked at this link, http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but was afraid I possibly might still have GB bootloaders on my phone. I would think not if Odin finished, but I just want to double check with the community so I dont brick.
Thanks guys.

Can you get into DL mode? IF so, i would try and Odin again. ALthough I looked at the link in your OP, unless your heart is set on 2.1JH7, i would use the Odin3 one click downloader. That will restore your phone to 2.1JF6 as well as flash the correct bootloaders. I have gone back and forth from continuum to cm7 a few times now using that method.

Thanks for the quick reply. however this is the 3rd time trying Odin-1 Click tonight and I still end up in a boot loop. I have redownloaded the file just to make sure I didnt have a corrupt one. I just want a stock system and see if the constant antenna issues continue. (Trust me Ive tried different modems and all those possibilities.) Is it safe with that link? I noticed when i do Odin they flash a sbin and bootloader. I am assuming that puts it back on 2.1

which Odin are you using? Are you using the one click program that gives you stock firmware... JF6 firmware?
It is here:
http://www.megaupload.com/?d=SBSMALFJ

Yup thats what I have. It looks like it doesn't load the android system. Soon as it says installing Multi-CSC its done and rebooting. It would seem like its not unpacking the files. I have no status bar at the bottom. I have no idea why its doing this. Here is the crazy part. If i go back to the ginberbread stock, its not a problem to get to boot.

while I'm no expert.. seems like a bootloader thing. Try downloading it again from the link i put up and see if it was maybe a corrupted download.

The bootloaders are the first thing flashed in odin. It stopped after that then you have stock bootloaders. Also if all you see is the white AT&T screen and then it reboots, that indicates stock bootloaders as well. The gb bootloaders have a black galaxy s I9000 screen as the param.lfs image.
I would bet money you have stock bootloaders, use that link you posted that work be perfect. If you go back to gingerbread and want to return to stock bootloaders you'll have to use one click again even though you got a problem from it this time, if you get the same problem you know this worked to fix it.
And lastly usually problems with cell signal are modem related ... Which one were you using, did you even try another one? That would've been my first move instead of going all the way back to stock.

Hey studacris,
I have been using Mosaic (Love the work you guys do over there). I did try and use the other method to get back to Stock Last night and it did the same thing. Just a bootloop. If its plugged into the USB cable it goes directly to the Battery Symbol, if its not the Att 3G bars loop. I can flash to Gingerbread stock and then apply Other Roms. I tried GR-2 and Mosaic again, but still nothing with the signals. I just dont like the fact I cant get back to Stock with those 2 different methods. What I think is odd is when I load Gingerbread, it seems like items are being unpacked and loaded. When i try to go to Stock, everything happens super quick, making me believe nothing ever gets installed on the Internal Card during the unpacking sequence. I am no pro, but thats just something i noticed. Here was my original post on the Mosaic board. http://forum.xda-developers.com/showthread.php?p=14043766&highlight=Rizz67#post14043766

Help! boot loop

ok so i rooted a few weeks ago and downloaded the usual apps. super user titanium back up and clock work mod. tried to flash a rom with clock work mod and got the e:signature verification failure message. found a post for a kernal that made clock work mod actually work so i tried to flash a rom. zSimplyAOKPV5_Dark to be exact. now it sticks on boot screen. i have searched for hours and cannot find a way to fix my problem. its my first rooted android and first attempted rom flash and i botched it right off the rip. please help?

Depending on what you did beforehand, you have some options.
If you have backed everything up previously, just flash back to stock with one of the one-click stock roms in the Development section (they're in a sticky).
If you haven't backed everything up, try holding V+/V-/power until it reboots. If it doesn't take you to recovery, you can try to flash a kernel (most likely one that would match the version of android/rom you were running prior to this flash) and see if it lets you into recovery. You'll have to flash it with either Odin or Heimdall, after rebooting into download mode (power off, hold V+/V-, insert USB).
If that doesn't work, though, the stock flashing would probably be your best and/or only bet.

it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.

phoenixfriend said:
it wont allow me into recovery though i can get to download mode by pulling the battery and pressing just the volume +- and plugging in the usb. i was trying to flash an ics slim rom. thanks for your very speedy response.
i have now tried to flash a stock rom however it is not working from there even with the stock kernal. now it is hanging on the at&t screen.
ok i got it. seems the kernal i flashed to help cwd work properly was the culprit. now i dont know how im going to flash this ics rom im looking at without it.
Click to expand...
Click to collapse
Flash corn kernel if you have stock gingerbread
Sent from my SGH-I897

The utility in my signature can help you flash the Corn Kernel so that you will have CWM.

I have corn kernal and odin 3 on the computer at home. Ill do that tonight. Any suggestions on a good stable rom for a noob? Preferably ics. I hated posting for fear of being flamed as a noob. My wife keeps making fun of me for it so I kinda have to get it done. I want to fix hers also. Its a great little phone it just seem a bit buggy to me. Very laggy. Thanks for all the help.
Sent from my SAMSUNG-SGH-I897 using XDA

Maybe start with a KK4 based rom such as Legend and then move up to ICS after that. I only say that because there is a bug in ICS that could render your internal SD unusable. It's rare, but when it happens you will not be happy.

Still unable to get corn kernal to flash. I've tried a few of your guys fixes but I'm gonna have to get some other updates to my computer first.
Sent from my SAMSUNG-SGH-I897 using XDA

Soft brick/boot loop

I was running the latest tweaked ROM yesterday when it rebooted itself into a boot loop. Iets stuck at "Samsung"
I attempted to restore using Odin following the instructions in the how to fix your phone thread. Though i've been successful with that in the past, this time it didn't fix the phone. Its still stuck on Samsung, but will randomly display the stock boot ani with sound, or even get to the lock screen, but then immediately go back to displaying Samsung.
Any ideas would be greatly appreciated, and yes, i've followed all instructions correctly with wipes and loading things in Odin, etc.
Thanks!

Hmm... was there anything going on at the time of reboot? Very curious.
Beyond that - assuming all went as it should with ODIN, if you are still having issues then the problem is a bit beyond the rom. It seems a scapegoat but perhaps a hardware error is underlying things...?
Anyhoo - what file (or files) have you tried to ODIN? There are a few to choose from, and they all can be found here (just be sure to only DL and use the charge-specific ones of course). I would try each one and hope at some point something sticks to where the phone is usable again. Sorry for the troubles!

Thanks for your reply! Phone was just sitting on my desk, I was text messaging...it may have been plugged into a non Samsung charger. I doubt its the fault of your ROM tho, as it had been running great since I installed 2.1 a few weeks ago. Its always run hot so that might have just caught up with it.
I'll try all those files this time on fresh downloads, might have been something corrupted.
thanks again!
UPDATE: Successfully loaded ED1 on, and it boots. I can unlock the phone, begin the setup process, but then it reboots. I'm so confused...

Find the most current OTA file and flash it instead of working your way all the way from Froyo to Gingerbread.
Sent from my SCH-I510 using xda premium

I had something similar happen to me just a week ago. I was on stock debloated deodexed and odined to tweeked and it bootlooped, Odin said successful but nothing was happening just Samsung logo. I knew there was no problem with tweeked cause I used the same file b4 and it worked fine. Tried to Odin back to stock ep4 same Samsung logo Odin still said it was successful. So I changed cable and made shure I was not moving phone or cable while it was doing its thing. It worked. Then updated to fp1, cwm superuser then Odin to tweeked. Everything ok. I figured the only problem of my was that the cable was a bit loose when I plugged it in the phone, the connections in the phone I guess were not getting the full contact as they should have. So try making shure you connect/plug in cable all the way and don't touch it while Odin is doing its job. You might also need to flash the stock ep4 file. Sorry could not help more. This worked for me, now on tweeked 2.2 n no problems.
Sent from my SCH-I510 using xda app-developers app

[Q] Would Samsung fix my bricked phone?

I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy

If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?

If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham

Yeah, you can still fix it. No need it to bring to samsung

Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?

random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.

cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!

Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!

random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!

[HELP] Splash Screen Bootloop, Heimdall One-Click doesn't work

A few more things you should know before I get into it. First off, this is my mother's phone, and about two days ago, she went to unplug and use her SGS4G after it had been charging overnight, and it wouldn't respond to the Power/Lock Button (It appeared simply stuck). So, naturally, she did a battery pull on it, and tried to turn it back on. After she hit the Power Button though, the Splash came up like it normally does, except instead of progressing with booting, the screen went black for a second and then went back to the Splash and it did/does this indefinitely (An obvious sign of a Bootloop).
Now. What doesn't make sense to me is that this was running the Stock ROM (I don't know if it was Froyo or Gingerbread), yet this still happened. I haven't tampered with the Phone at all, and my mother isn't too fond of the idea of Rooting, so unless the previous owner (Yes, it is a used phone) tampered with it and then restored it to Stock, then I have no idea.
Things I have tried:
Heimdall One-Click For Dummies (With and Without flashing Bootloaders)
Juls317's Noob Guide's "Potential Problems" section (With both Heimdall and ODIN)
A few Kernels (bhundven's Kernel, drhonk's KG4 Kernel)
sygee's ODIN/Heimdall Flashable ROM
hailthetheif's Step by Step Rooting Thread
Also, after I flash anything, whether it be with ODIN or Hiemdall Suite, or Hiemdall's One-Click, if I leave the phone plugged into the computer afterward, it will go to the Splash Screen and then to the Battery Screen (Which doesn't work, it just freezes with the Loading Wheel) and it'll Bootloop with the Battery Screen. If I unplug it after Flashing, it goes back to the classic Splash Bootloop that has been happening since Day 1. It doesn't even get past the Kernel.
I know that at least the Kernel and the Bootloaders can be Flashed however, by how they act on the Device. For example, if I flash certain Gingerbread Bootloaders, I can only get into Download Mode with PWR + VOL-, whereas on the Froyo Bootloader (Includes Stock), you use VOL+ + VOL-. With the Kernel, for example, if I flash a TeamAcid Kernel, their Logo comes up on the Splash Screen, but it still does the Splash Bootloop no matter what.
One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.

One final thing, if I flash a Kernel/ROM that includes a Recovery Mode, I can't access it at all (PWR + VOL+). I couldn't/can't access the Stock Recovery at all either.
Pull the battery, hold power& both volumes, drop the battery back in. Should bring you to recovery (gb, not sure, can't remember froyo same or not). Wipe data & cache etc.
On the heimdell, awesome threads that you quoted. Follow directions and it should get you there. Kj6.. you may have to flash it twice to get the bootloaders for gb(it's setup that way so you can't fubar it without trying really hard). You would have to check the load boot loader box on second flash.

I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot

LiangChi said:
I just had this same exact issue. No matter what I flashed, it wouldn't work. Just kept with the boot loop. Now the difference with my issue was, I was still able to get into CWM and/or Download mode. (I was running custom rom). Heimdall wouldn't work for me because it was a driver issue. Odin, well, all the links I found for Odin were dead..
Anyway, when you're working with Heimdall, does it recognize your phone and flash? I had to flash it over twice for it to get to work. It is possible she was on Froyo and you're trying to flash it over with a GB stock rom could be causing an issue. Someone correct me if I'm wrong.
I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there.
This thread helped me out the most:
http://forum.xda-developers.com/showthread.php?t=2042927&highlight=frozen+at+boot
Click to expand...
Click to collapse
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.

Able to get in to recovery and wipe? Wipe data & caches. Got cwm? Which one click? Eilleo(sorry for the spelling) put out a one click that was to be used as stepping stone to ics only.

WinterPhoenix96 said:
It does recognize the phone, and it does Flash (As far as I know). I used Zadig, so there shouldn't be an Driver problems. I flashed it several times with a lot of different things, however, I just now flashed it twice with the Heimdall One-Click again to see if that made any difference. It did not. I'm still stuck in that Splash Bootloop.
Also, what did you mean by, "I'd say try sourcing a Heimdall to Stock Froyo ROM and see what happens from there."? I haven't ever seen that suggested anywhere, and I have no idea where I would find a Stock Froyo ROM that is flashable via Heimdall.
Click to expand...
Click to collapse
I'm honestly not to sure if a Froyo ROM for Heimdall exists. I do believe seeing one for Odin, though. Not sure if that link is still alive. I'll see if I can find it again.

We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.

lumin30 said:
We do have a Froyo One-Click but if KJ6 One-Click is not working for him I do not know why you think the Froyo One-Click will.
Click to expand...
Click to collapse
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.

Stuck on Froyo
LiangChi said:
I figured if the phone was still running on the Stock Froyo when this happened, that it may work as opposed to forcing the phone to accept a new ROM while it's still clashing with itself.
It's worth a shot at this point.
Click to expand...
Click to collapse
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!

You have so much info here... let's see what we can figure out.
grovernyc said:
I hate to hijack this thread but it describes my current situation and symptoms perfectly and I never saw a conclusion / fix.....
I just got a used phone from ebay (verified SGH-T959V in battery compartment) and have run into the same exact problems described in the start of this posting. Phone was running Froyo and I attempted to upgrade to Gingerbread with Heimdall One-Clicks. I was actually successful at one point but then it crashed when I tried to install boot loaders to get rid of rainbow screen at startup.
Now all I ever get is a splash screen bootloop whenever I try any of the Heimdall One-Click gingerbread variants. I have also tried Odin and the Gremlin remover with same results of splash screen bootloop (Linda always completes). I was however able to access the new kernel CWM recovery and try to flash other gingerbread ROMs - splash screen bootloops on all attempts.
Ok... when you flash the "stock" rom... have you tried to wipe cache, data etc???
Are you letting it boot up before appling any of the kernels??
So I gave up on Gingerbread and tried using CWM recovery from gingerbread ROMS to install CM9 / CM10 / Slim Bean. I was able to upgrade almost perfectly but had same problem for each one of these. Not the bootloop thankfully but instead the headphone speaker (if that is the right description) doesn't work. No sound for phone touchpad, screen selections, and when receiving a phone call (have to switch to speaker phone as back/big speaker works or plugin headset to hear whoever was calling).
All of the other features were great but I really needed to be able to use my phone as a phone! The Heimdall One-Click worked to return me to Gingerbread with same problem of splash screen bootloop (gets to pink welcome letters every once in a while). Then I used the Heimdall One-Click for Froyo (as suggested by LiangChi) and got a perfectly working version of Froyo.
Try wiping data and such, still bootlooping??
Used Froyo CWM recovery to switch to ICBINB ROM which works fairly decently.... Am I doomed to stay at Froyo though? I tried to follow all of the guides to a T but not sure what I might be doing wrong or if I might have purchased a damaged phone - can't recall ever testing camera and it still doesn't work on current stable Froyo. At various points I tried different cables, SD cards, USB ports, removing/reinstalling drivers, etc... Even tried Kies when I got back to stock Froyo to upgrade - went to Splash Screen Bootloop!
Click to expand...
Click to collapse
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.

Dirty Flashing
Champ - I think you might be on to something...haven't read about dirty flashing but it sounds right. I have been wiping data and caches (even tired reformatting system with a few roms). I do remember running into problems trying to following a few instructions sets that asked to disable the voodoo lagfix - hit option it just doesn't disable. After hitting disable see below Voodoo lagfix is actually: enabled next boot: disabled but even if I reboot back to CWM it is still enabled.
I might try the Odin Gremlin remover again. I was just getting frustrated after several days of failed upgrades. Second opinion on if it might be hardware/memory vs user error. I really didn't understand why even Kies (which everyone disparages) upgrade from stock Froyo also caused same loop.
champ1919 said:
You have so much info here... let's see what we can figure out.
nope, it sounds like dirty flashes to me...
I would start with entering cwm and disabling lagfix & wiping data & caches.... linda needs to do her thing after the first boot up...
Then, I would reflash the germlin remover, If I remember correctly, you will have to do this twice (second time will allow you to check the add bootloaders)...
After the phone hits the think-pink, then you can battery dump, reenter download and flash the kernel.
Click to expand...
Click to collapse

Retry the gremlim remover. Redownload it incase of a bad download.
Lumin30 has a good guide in his signature for the heimdall one clicks.
I use Odin, I have used his one clicks without problems though.
http://forum.xda-developers.com/showthread.php?t=1470716
Sent from my SGH-T959V using xda app-developers app