Database Develop

Gingerbread 2.3.3 Q&A

I think we need to sticky/pin this for us who just flash the stock/leaked GB 2.3.3 along with the optional root from this thread since we can't post there http://forum.xda-developers.com/showthread.php?t=1127249
Since this is the route that I went I would be able to help answer questions for others. I see cognition, mosaic.... but how about us who like to keep it stock?

Brickster
Just want to say that I have learned so much on here and I have a lot of fun trying out different ROMs. Thanks to all the DEVs, when I get a job I'll buy you guys some beers lol.
So... This has soft bricked my phone every single time. The first 4 attempts were from stock eclair. My last attempt I was successfully running Stock I9000 2.3.3 NEE so I thought I would try it from there. Odin gets to boot.bin and then says FAIL! I got into download mode using VOL DWN and PWR which is the key combination from Stock I9000 2.3.3 NEE. I have been running I897UCJF6-final-OCD-REV0 to flash back to stock after brickness.
So i'm sure i'm missing something pretty simple, but any help is appreciated.

Woah dude, that was very very very close to being a hard brick. Boot.bin is the primitive bootloader. so you had a kf1 pbl, and since you had the combos for I9k boots you obviously had an I9000 sbl, (secondary bootloader that's where the combos are contained.)
Make sure the usb chord is on a port attached to the motherboard (in the back of the pc), if it is already switch to another. Reboot the computer and try again.
But with such a close call like that, and the fact that you said it fails every time I would avoid it altogether I mean its a stock rom, is it worth bricking over??

Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?

ttr187 said:
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
Click to expand...
Click to collapse
Use admin mode for Odin and change the compatiblity to Xp service pack 2. This is the best way to run Odin for Windows 7 x 64. Since I use Cog 5 v2, I strongly recommend following the instructions 100%. Please remember when you need to loading stock UCKF1 and when you load UCKF1, you are loading bootloaders, so any disconnection can brick you hard. Thank goodness for the simplified instructions there.

GB stock? I thougth captivate stock were eclair or froyo.

KF1 is the leaked gingerbread firmware for the captivate...

popfan said:
Use admin mode for Odin and change the compatiblity to Xp service pack 2.
Click to expand...
Click to collapse
After changing the compatibility mode to XP pack 2 everything worked like a charm. Then I was able to successfully flash Cognition 5 v2. Sweet!
Thanks.

Hello. I use Darky's rom 10.2. And I have problem with Dialer. It sometimes crushes and exits. Problem will be solved with reboot. how can I fix it? thanks.

I would try to flash again and make sure you do a data/cache wipe. I've had random issues with other ROMs when I did not wipe, and all was fixed once I flashed properly.

I know I'm not wiping everything while flashing, but I flash it as told as in FAQ. But my memory will stay unwiped after I run newly installed ROM.

When you say "memory" what exactly do you mean?
If you mean the /sdcard storage partition, that is normal.

yes, /sdcard storage partition.
Before flashing, I get warning message about wiping all data in my internal storage... what does it mean then?

The /data and /cache partitions. And the dalvik cache.
The first 2 are in the cwm main menu. Wipe data/factory reset and wipe cache. Dalvik is in the advanced sub menu.

When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.

Griff1220 said:
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Click to expand...
Click to collapse
It appears to be asking for some encryption password according to one of these guys that posted in the following thread. But there is a way to get past it by the method in this thread...http://forum.xda-developers.com/show...02&postcount=7
Remove ur external sd and copy over/back up anything u want to save from ur internal sd before u do this, just in case.

data/chache wipe i should do right after flashing right?

[Q] Need help with ROM Manager

Hi Everyone,
I bought ROM Manager Premium v4.5.0.1, in order to do a Nandroid backup on my I896 running stock I896UXJL1.
I ran "Flash ClockworkMod Recovery", and it said my Current Recovery 2.5.1.2 was the same as the Latest Recovery. So far so good.
Then I ran "Backup Current ROM." Instead of doing a backup, it rebooted my phone into Recovery "3e" every time. I tried it many times and got the same result.
This is so confusing. For whatever reason the app decides to boot my phone into recovery instead of doing the backup, I would expect it to at least go into CWM Recovery instead of the stock 3e.
Questions:
1. Has any of you gotten rebooted when you try to do a Nandroid backup?
2. Has any of you gotten rebooted into stock recovery even when CWM is installed?
Thanks.
KK

In general ROM manager is trash for SGS. Don't bother with them. I would say find a kernel with CWM cooked in it but JL1 is a rogers only and I don't know any for that.

prbassplayer said:
In general ROM manager is trash for SGS. Don't bother with them. I would say find a kernel with CWM cooked in it but JL1 is a rogers only and I don't know any for that.
Click to expand...
Click to collapse
froyo wasnt so damn kenel picky. any froyo kernel will work.

Doesn't work with any ROM
I've tried ROM manager after flashing KH3 and KJ3, and the "Reboot into Recovery" still doesn't work. I get the triangle-exclaimation-droid screen with nothing else, and it stays that way until I use the 3-button reboot.
Since the app can't even perform one of the more basic functions, I am afraid to let it do anything else. I wish I hadn't paid for the premium version.

ROM manager doesn't work on Gingerbread..... Rom manager isn't very good for Samsung phones

KarateKick said:
I've tried ROM manager after flashing KH3 and KJ3, and the "Reboot into Recovery" still doesn't work. I get the triangle-exclaimation-droid screen with nothing else, and it stays that way until I use the 3-button reboot.
Since the app can't even perform one of the more basic functions, I am afraid to let it do anything else. I wish I hadn't paid for the premium version.
Click to expand...
Click to collapse
Stop what you are doing and read. ROM Manager sucks basically. Very few people on here actually use it. If you keep just throwing things at your phone though without knowing what you are doing you are going to end up with a shiny, expensive, paperweight. Then you get to spend upwards of 50$ getting that fixed. So please, for me, the forum, and your phone just read. Or at very least ask a directed, detailed question. As in: my phone is here, im trying to get to there, this is what im doing and this is where and how its failing.

Flashing using an app
I actually did weeks of reading before flashing my phone for the first time. I got scared by potential problems such as USB interruptions.
This is where I am at: I've been using mostly Odin to flash. I have successfully flashed KH3 and then KJ3 (with KF1 bootloaders and Boog's kernel); however, I am still nervous each time I do anything.
This is where I hope (or used to hope) to get to: I keep looking for a way to minimize the probability of human errors and technical hiccups. (It's a habit I've picked up while working as a software manager.)
I went for ROM Manager because the same developer wrote CWM. I do appreciate you guys sharing your opinion of the app's effectiveness with the SGS. I only wish I had been warned sooner (ideally by the app's developer).

Find ODIN packages that don't inlcude bootloaders. That will only minimize your risk to soft bricks wich can be recovered with a jig that are easy to make and only cost ~ $10 if you choose to buy them. I personally use KH3 as my "stock" setting when I need to flash to stock. I use Cezar's KH3 .tar that doesn't include them but there are atleast 1 1 click around.

CWM for Captivate Gingerbread UCKJ2
Sorry in advance for the noob question. I have read many posts but can't find my answer. I've installed the leaked gingerbread rom from Samsung called uckj2. I was trying to change the modem by flashing a zip file using clockworkmod recovery. I've heard the way to do it is by using a kernel that already has cockworkmod already baked in. Which kernel should I use?
Thanks in advance

KJ2 have 3 kernels that should work. Corn kernek, Samurai and Boog's kernel.

[Q] Rooting my captivate, can't copy root file to phone

Hey folks. I'm bailing on Gingerbread because it was causing me too many problems. I'm trying to get back on Firefly 3.0 and I'm stuck at getting the phone rooted.
Whenever I try to copy the Root.zip from the AIO folder over to the phone's root folder, I get an error about the parameter being incorrect. I'm not sure what to do at this point.

Use Fugu root? Easier.... Also depending on what Gingerbread you are on there are kernels that have the root scrip baked in them.

^ you misread he's not on gingerbread, he wants to flash firefly.
You don't need root to flash a ROM. Odin a kernel that has cwm baked in. boot into recovery and flash the ROM.

Thought he was on GB trying to get on... you know what ya I missread. @OP do what Studa said xD. Wonder why people think they need root to flash roms..... I blame Rom Manager.

I know I don't need to root the phone, but in order to get certain things done on the phone, it's necessary.
I'm actually at a wall right now. I used SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click which successfully booted my phone to ATT 2.2 firmware, but I can't get any Odin to pick up on it now. I've tried five different Odins.
At this point, I think once I get the phone up and running on Firefly, I'll be walking away from flashing until I get another phone. Then I can use this for testing, etc.
On a side note, before I started this project yesterday, my modem was messed up. Now it would seem I have a successful connection to wifi, which I couldn't get.
As great as that is, I still can't get Odin to pick up my phone. Any thoughts?

Was that kb2 package heimdall?
If so you have to uninstall the heimdall driver and reinstall the Samsung driver.
Either way I would reinstall the Samsung drivers but it is a must if you used heimdall add the drivers conflict.

Alright. That's done, but I'm on I896UXJL1-stock now, and I'm pretty sure in doing that through Odin 1.85 I unrooted the phone. Correct me if I'm wrong. That's why I used the ATT stuff, because it auto-rooted the phone.
So it would seem I have some issues to work through. I can either root my phone and be stuck with ATT firmware that I don't want, or I can unroot the phone and use Rogers stock and hope for the best with Firefly.
This is by far the most confusing computer-related issue I've ever worked with. There's too many options to play with and they all work differently.

Why would you be stuck on at&t firmware? Why do you need to root before flashing firefly? Why don't you root Rogers stock?
you're confusing everyone involved lol

Okay, so maybe I'm a little in the dark on the rooting issue. Basically, I'm going back to Firefly because I thought it was amazing. Fast, responsive, and no issues I can think of on my phone.
I'm rooting the phone because it's my understanding that in order to spoof my location in order to get certain apps (Google Music), I'd need to be rooted.
I'm having a hell of a time trying to get this done, and my biggest problem, to reiterate, is that I have about fifteen different Roms, all either ATT or Rogers, three different Pit files, and so, so many Odin programs.
I'm now on 2.1 with that Toronto stock firmware, in order to work around the 3e error in recovery mode when trying to put on Clockwork. Unfortunately, now I'm getting some other error in regards to the Update.Zip file, Status 7.
I apologize for confusing people, but I promise I've read as much as I can about the tools I'm using, but I'm running in circles, flashing back and forth trying to find solutions.

you do not need to root before flashing the rom. it will be rooted after and then you can do what you need to do to get your apps working if you need to (firefly contains canadian locale cause its based off of rogers froyo firmware) changing stuff before you flash so apps can work is a waste of time as the flash will overwrite the firmware you just tweaked.
now, since your on eclair i'm attaching an update.zip that contains cwm, put it in the root folder of your sdcard boot into recovery select reinstall packages twice and it should boot into cwm where you can then flash firefly.

You're a frickin' genius, Studa. Don't let anyone tell you otherwise. I've got Firefly on thanks to that Update file, and I'm getting the ball rolling on everything else. If I wasn't so broke, I'd donate, but I hope my thanks is good enough. I really appreciate the help. It cut through twelve hours of stupid.

[Q] Accidentally flashed to 2.1

Okay first of all, I would like to apologize if this is being posted in the wrong forum, or if I am upsetting anybody by posting this. I have searched all over for a couple days trying to figure this out. This is my last resort, and I'm hoping you guys can help. All of your time and understanding is much appreciated!
So a little background. About a week ago, I rooted my AT&T Captivate 2.2(build number 1012 if that helps) using Superoneclick, and then flashed CM7.1 using clockworkmod. I was not satisfied with CM7.1(terrible battery for me, other various reasons). I then downloaded MIUI (not sure which version, the one available on the premium version of clockworkmod) and flashed it using clockworkmod. This started with the cm bootscreen, and then went to an MIUI bootscreen that played a little tune. The miui screen looped, and it would not go past this.
After rebooting and running into the same thing, I went to f\attempt to find a solution. I thought I backed up my rom, but it had been erased (issue with the external sd I think). I used an odin one click I found on here, but this odin one click brought me back to eclair 2.1, instead of 2.2. Up until now, I could get into both download and recovery mode using the three button method, and now I can't. I am not sure what to do exactly. I have read about getting it into download mode using adb, but I'm not sure if that would work in my situation, and I'm not too educated on adb or android sdk. I stayed up almost all night last night, and now have researched most of today, not making much progress.
Thanks again for your time!

Just to clarify have you used all button methods in order to try to get into download mode. Seems as though flashing bootloaders may have f'ed up you combos. I have a couple suggestions. I'll edit my post as I find the urls to post for you
Stock GB ROM you should be using -- http://www.mediafire.com/?05nemq5yyn5fuqf, this one has bootloaders, but preferably you should use stock odin roms that don't mess with the BL's (after this of course, since yours are messed up right now).
Now of course this depends upon you getting into download mode. If you can use ROMmanager (btw, I don't recommend you download your roms from rommanager, as that will not always be the most up to date and may not be the one for you) to get into recovery mode, then from there go to advanced then reboot download. However some kernels do not support this. Try the cable methods before trying this method.

First of all, I appreciate your help Mikel.canovas. I have used all the button methods. I can no longer get into recovery or download. (Romtoolbox enables me to get into recovery(2E), but not download). I now have root access, but am not able to sideload apps, and apparently rommanager free isn't available on the market. I did buy rommanager premium, but unfortunately now that I basically reset my phone, it doesn't show up as bought (known issue, apparently not resolved?), and even after I bought it again, it says I need the free version to even use the premium version.
Should I go through the process to be able to sideload apps? Or will romtoolbox do the trick? Rom toolbox gives me the option to install a rom from my sd card. Should I use that, and select the GB ROM you provided? I'm not sure I understood exactly how you want me to get that GB ROM onto my phone.
What I want to eventually have is either MIUI or rom fasty on my phone. If possible, could you give me some steps on how to reach that goal?
Thanks again for your time. Eclair on the captivate is not pleasant, especially since I had a taste of CM.

Well first off I highly recommend Mosaic over CM or Fasty, solely because of performance and battery life. However that is all subjective.
Ah since you're rom is sending to 2E recovery, you're not rooted with cwm. You need to flash another kernel that supports this. Afterwards, If you can get into CWM, I recommend putting CM onto your sdcard and flashing from there. After booting into CM hold down the power button, press reboot, choose reboot download. See if that works. If not, does adb reboot download work for you? If not again, I recommend trying another USB port, reinstalling drivers, trying different button combos. I've had issues getting into download mode in the past and, trust me, it is VERY frustrating.

Well first of all, before you back into flashing stuff, don't flash to stock unless you have done everything possible with the tools on your phone. I'm assuming you gave it at least 5 minutes to boot up, as the first boot can variably take longer. You could go into recovery and wipe stuff, or you could have gone back to CM7. A flash to stock is probably never necessary in the situation you reported.
Anyway, if you can get into recovery, maybe try getting a kernel that allows you to reboot into download from recovery. Although that will depends on what kernel you are on right now, as I know speedmod kernel has that option, but you would need to get to download to flash that.
And as another poster wrote, have you tried all button combinations?

korockinout13 said:
Well first of all, before you back into flashing stuff, don't flash to stock unless you have done everything possible with the tools on your phone. I'm assuming you gave it at least 5 minutes to boot up, as the first boot can variably take longer. You could go into recovery and wipe stuff, or you could have gone back to CM7. A flash to stock is probably never necessary in the situation you reported.
Anyway, if you can get into recovery, maybe try getting a kernel that allows you to reboot into download from recovery. Although that will depends on what kernel you are on right now, as I know speedmod kernel has that option, but you would need to get to download to flash that.
And as another poster wrote, have you tried all button combinations?
Click to expand...
Click to collapse
Or download SGS Kernel Flasher from the market. You can then flash kernels with the app. without having to go into download mode. Very handy.

Once again guys, thank you for your time. A little more information:
Kernel:
2.6.29
[email protected]#12
Baseband:
I897UCJF6
Let me know if you need any other information.
I am able to get into download mode using the terminal emulator in rom tool box. (The free version of rom manager is no longer on the market)
I was hoping one of you could give me a step by step of what I need to do, with links to downloads.
And yes, I have tried all off the three button methods. Also, I probably should have researched more before I flashed back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App

wwcjr91 said:
Once again guys, thank you for your time. A little more information:
Kernel:
2.6.29
[email protected]#12
Baseband:
I897UCJF6
Let me know if you need any other information.
I am able to get into download mode using the terminal emulator in rom tool box. (The free version of rom manager is no longer on the market)
I was hoping one of you could give me a step by step of what I need to do, with links to downloads.
And yes, I have tried all off the three button methods. Also, I probably should have researched more before I flashed back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If nobody beats me to it, I will post you some links tomorrow when I'm on my laptop.
Oh, and miui won't really give you better battery life than CM7. It basically is CM7 with a different UI. I loved CM7 a ton, so if you are having issues with it, let me know! With the right kernel and other settings, battery life is pretty decent, as long as you charge nightly.
Sent from my ICS i897 Captivate

wwcjr91 said:
Once again guys, thank you for your time. A little more information:
Kernel:
2.6.29
[email protected]#12
Baseband:
I897UCJF6
Let me know if you need any other information.
I am able to get into download mode using the terminal emulator in rom tool box. (The free version of rom manager is no longer on the market)
I was hoping one of you could give me a step by step of what I need to do, with links to downloads.
And yes, I have tried all off the three button methods. Also, I probably should have researched more before I flashed back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
What is the build number of your phone? It's located under your battery, looks something like 10.06,10.07, 10.08 and so on

Alright, thank you, I will be checking back tomorrow.

Eventually what I want is to have the working 3 button combos again for both download and recovery mode, and either the miui, mosaic or rom fasty on my phone.

Easy flash GB BL's and you won't have to worry about 3 button problems!

If you didnt do a Master Clear, now would be the time. Make sure you back up anything you want to keep. MC will erase EVERYTHING on your internal SD
Remove your Micro SD, and your SIM
Download:
OneClick Root
SideLoadWonderMachine This also has CWM, 3ButtonFix and ROM Manager in the zip
Make sure you have Debugging enabled
Connect to your PC
Run One Click Root, and follow the instructions, reboot
Run Sideload Wonder Machine and direct it to install ROM Manager
Copy the update.zip(CWM) and 3Button Fix to your phone
Open ROM manager and "reboot to recovery"
You'll go thru the boot twice to get to CWM
In CWM install the 3 Button Fix
I usually pop out the battery and check it before I put the ROM in.
VERY IMPORTANT!!!!! DO NOT TRY TO USE THE 3ButtonFix while you have a GB ROM installed you WILL brick your phone. It only works on 2.1, and 2.2 ROM's

using this one click package I now am able to manually enter download and recovery :
http://forum.xda-developers.com/showthread.php?t=1129821
However, The recovery is still 2e..

kangi26 said:
What is the build number of your phone? It's located under your battery, looks something like 10.06,10.07, 10.08 and so on
Click to expand...
Click to collapse
1012, do you think any of my problems would have to do with the build number? WHen I got it, it had froyo with the working button combinations.
Sorry, I didn't see that until now.
I now have clockwork recovery, and I'm about to try out fasty. Thanks again guys.
So can I delete this thread? And if so, should I? I've found plenty of threads that seem outdated, and fill up the search engine.

wwcjr91 said:
1012, do you think any of my problems would have to do with the build number? WHen I got it, it had froyo with the working button combinations.
Sorry, I didn't see that until now.
I now have clockwork recovery, and I'm about to try out fasty. Thanks again guys.
So can I delete this thread? And if so, should I? I've found plenty of threads that seem outdated, and fill up the search engine.
Click to expand...
Click to collapse
The only reason I asked about the build # is because the 10.08's were pretty commonly known to have 3 button issues. Also, anything above 1012 and using Odin1 Click could soft brick. I was just checking as I was offering info

kangi26 said:
The only reason I asked about the build # is because the 10.08's were pretty commonly known to have 3 button issues. Also, anything above 1012 and using Odin1 Click could soft brick. I was just checking as I was offering info
Click to expand...
Click to collapse
Trying to fix my buddys cappy. Its rooted on T-Mobile and running stock 2.1 rom. I'm not a Samsung guy so how do I get cwm and a 2.3 rom? The build number is ECLAIR.UCJH7
Sent from my Incredible 2 using xda premium

Go to this Stickied Thread in the Development Forum... http://forum.xda-developers.com/showpost.php?p=18370235&postcount=1
And u will have to use one with the Bootloaders included, because to run a gingerbread firmware u gotta have the gb bootloaders.
Post #3 has the "leaked" KK4 (Been confirmed to be the same as official).

4-2ndtwin said:
Go to this Stickied Thread in the Development Forum... http://forum.xda-developers.com/showpost.php?p=18370235&postcount=1
And u will have to use one with the Bootloaders included, because to run a gingerbread firmware u gotta have the gb bootloaders.
Click to expand...
Click to collapse
Since its already rooted do I need a computer?
Sent from my Incredible 2 using xda premium

Yep. Because these are Odin or Heimdall One Clicks.
You can't just flash to a GB firmware/rom from Eclair/Froyo without using Odin or Heimdall to at least get the Gb Bootloaders. You cannot just go through CWM recovery unless u already have the GB Bootloaders.
Of course u can get it all through mini Kies, the official GB 2.3.5 KK4 update that is.

[Q] FASTY III problem/question

HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.

When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.

HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK

studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again

Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.

I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.

If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?

No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS

studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^

All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.

studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....

the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.

Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!

another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...

Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.

oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!