Related
Foremost, I apologize if this has been asked and answered before. I've been searching for weeks...maybe I'm a bad searcher.
My issue is that I have been experiencing random force closings on random apps, including random partial reboots when unlocking the Unlock screen (screen freeze then goes to Rom intialization screen). Sometimes Dolphin HD closes when loading pages, same with stock browser and Opera Mini, though sometimes the same page will load fine (both with JS on and off and with Flash turned off in Froyo ROMs). Swype (v.2.15) will sometimes close when typing in the search widget or an SMS message in both ChompSMS and stock messaging app. Titanium Backup and Astro sometimes close when scrolling down the app list. The only consistant factor that I can think of is available RAM or the processor overheating.
I have installed multiple ROMs thinking its ROM-specific, but the same behavior manifests in each one. I've tried Assonance 5.2, Cognition 3.04, Phoenix 4.5 and Serendipity 5-1.4.
With each new flashing I first use Odin to get back to stock, then use Odin to Master Clear, then root the phone, then install Clockwork, flash it's recovery app and then use Clockwork to flash the new ROM.
I did fresh installs of any apps I installed from the Market as I know user data from 2.1 will cause issues with 2.2.
Because I thought it was a RAM issue I installed Autokiller Memory and used the 'Optimum' preset.
After all this I still have the same issues with random apps closing and the phone doing ROM reboots when at random times I unlock the phone. Can anyone give me some guidance?
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
diablo009 said:
1. When restoring apps with TiBu, are u restoring system data too?
2. Do not restore data of non-system apps if moving between android 2.1 and 2.2.
3. Last ditch attempt, try flashing 5.5 version of the rom in my signature, and if the issue still persists.
4. Processor overheating can be reduced to some extent by turning 3G off, and getting on EDGE. This would reduce ur download speed though.
Click to expand...
Click to collapse
I'll give your ROM a shot.
Stupid question - Do all ROMs have kernels and modems cooked into them? I was just thinking that I've been flashing tons of ROMs lately and I'm not sure of the most stable kernels to have.
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
avgjoegeek said:
Yup they come all "pre-cooked" with kernels and modems... otherwise they wouldn't run
But you can flash different modems and even kernels (at your own peril). You can find them in the dev forum.. usually "update.zip" that you can use to flash under recovery.
But.. this sounds like maybe your internal RAM is corrupt?
Do these things persist if you were to stay at stock 2.1? I would run it "barebones" with just the restore and use the phone for a day or two to see if it continues to happen.
If the issues stop - your all good - just need to figure out what your doing or what your installing that is horking your phone. For me in the past its been due to overclocking without even knowing it (yay for Voltage Control) or it's been an application or bad flash causing the issue.
If the issues persist under the stock ROM - probably hardware related and you would need to warranty it for a different one.
Click to expand...
Click to collapse
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
DRoc740 said:
diablo009 - I ended up not using Tibu to restore anything because I feared that a backup was the cause of my force closings. I had done a clean flash of stock, rooted and then flashed a new ROM. The only apps I installed were dolphin, pandora, clockwork and Lookout.
Thanks avgjoegeek, I did kind of fear that it was bad RAM as this behavior mimics performance on a PC with bad RAM installed.
I did run it on stock for half a day because I wanted to verify and there were no force closings. I am going to run it on stock for the weekend and see what happens. If everything is all good then I will flash di11i's 5.5 and see what happens.
Could it be possible that some features of 2.2 just are not compatible with my captivate build?
Click to expand...
Click to collapse
When u restore to stock, format the internal SD from within windows. (Ok, I won't contest anyone's arguments on this, but I personally find it easier than doing a master clear and to wipe off even the basic folders android os format creates.)
And, I would recommend u download a fresh copy of 5.5, with a kernel that does not have any OC in it, to play safe. 5.5 is available in two versions - one with OC kernel, and one with non-OC kernel.
It could be a case of kernel too. Try swapping kernel and see if that helps. Not all kernels go well with all hardware. That's the reason I swapped to xcalibur kernel as soon as I loaded 5.5.
I think, personal opinion here, u could do away with clockwork recovery too. U cud download the cwm console update.zip and put it on ur sdcard root. And apply the update.zip with in console in stock to load up CWM console. This is the most non-intrusive way of going to CWM console as far as I know.
I've been running stock since yesterday with zero issues. My force closing issue usually appears within an hour of flashing a new ROM so this is a very good sign that its a flashing and not a hardware issue.
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Maybe its a kernel issue as I think i've exhausted all other options. I'll try xcaliburinhand's v2.3.2 01.31.2011 and see if it works.
Any other suggestions?
DRoc740 said:
diablo009, you mention using the CWM console instead of clockwork recovery. Isn't this what the clockwork manager installs? Are you saying to install through the consol startup app instead of using the clockwork app when fully booted up? If so, this is what I have been doing.
Click to expand...
Click to collapse
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
diablo009 said:
Yes. But instead of updating the system boot with this, it leaves the system as it is, and uses is as a standalone program.
Click to expand...
Click to collapse
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
DRoc740 said:
I searched around and couldn't find any download links for this. Do you happen to know where I can find it?
Click to expand...
Click to collapse
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not now be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
diablo009 said:
Here you go.
1. Copy this to the root of ur sd card.
2. Go to recovery
3. Select "apply update.zip"
4. If u r doing this for the first time, u would need to step 3 again.
You would not be in a green screen recovery console.
I would recommend storing this file in a safe place so u can copy it to sdcard root whenever u want to revert to stock before flashing a new rom.
Click to expand...
Click to collapse
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
DRoc740 said:
Awesome! Thanks!
From your description I think this is the update.zip I have but I'll try anything
Click to expand...
Click to collapse
welcome to the world of flashing. let me (us) know if u need any more help
diablo009 said:
welcome to the world of flashing. let me (us) know if u need any more help
Click to expand...
Click to collapse
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
DRoc740 said:
Update:
I ran on stock ROM for 2 days without any force closings, no issues.
I just flashed di11i's 5.5 (no OC) ROM and within 10 minutes had numerous force closings and a ROM reboot.
I then flashed the I9000 reoriented ROM (from diablo009's signature link) and the issues persisted.
Is there something I'm doing wrong? Or any more ideas on what could be causing my issue?
Click to expand...
Click to collapse
did you restore anything with titanium backup?
Pirateghost said:
did you restore anything with titanium backup?
Click to expand...
Click to collapse
No, didn't restore anything.
I flashed the update and had the force closings within a few minutes while I was typing an SMS using Swype.
Bumping
I have the same problem
Anyone done an 'absolute' clean install...? A bit of help needed...
After flashing about 9 different roms over the past 12 months, I would like to achieve a TOTAL wipe of my phone and an install of stock or custom - I have a feeling something is not right in the system image part of the phone... I have used Darky 9.5, 10.2 F, EE, RE, Cericko lite, F1, Ficeko JVH base, Galaxian, dark core, etc etc.
But still i cant get the perfect situation - either bluetooth in car goes (touch handset for nissan) or process.phone FC's.Flashed stock JVR today and still phone FC's after using bluetooth.
I have flashed previously both by CWM and Odin, and you may just say that re-partition in Odin does what i want (wipes system image) but I am not sure - what about the bootloader files etc? Can the internal system image become corrupted? (especially if done ext4/rfs conversions on and off?)
To be fair, the only time it was 'perfect' was on froyo 2.2 BEFORE the .1 update - ever since there has been these niggling issues...
If anyone has got any great ideas please pass them on!! Thanks!!
grab yourself a stock froyo ROM, flash it with all 3 files and 512 pit
boot onto recovery and do a factory reset, wipe cache / dalvick cache then go into mounts and storage (CWM needed) and format cache again, data, and datadata.
format internal and external sd card.
completely clean !!
i'd have to have froyo bootloaders no? And then,flash chainfire cfroot to get cwm? Cann i then upgrade to gb 2.3.4 and believe my system is clean? Thanks so much for the,tips!
dwgalaxys said:
i'd have to have froyo bootloaders no? And then,flash chainfire cfroot to get cwm? Cann i then upgrade to gb 2.3.4 and believe my system is clean? Thanks so much for the,tips!
Click to expand...
Click to collapse
What ROM are you on now ? if you are already on a GB ROM then do the whole procedure with a 2.3.4 firmware, Save the hassle of all that flashing.
If you are on froyo now, you dont need to mess with bootloaders unless you upgrade to GB which states you need them..
hope that makes sense
yes sorry, should have stated am on XXJVQ already and changed yesterday to sensation 2.1 as i was getting probs with all others. This is at least stable after 36 hours so hopefully a working solution - but,if ihave to do superclean i wanted to know how to do. THANKS!!
EDIT - whoops - spoke to soon. Also loss of touch in car Bluetooth with this rom! Have now frozen with TB all BT settings - print/share/opp/bluetooth services etc etc... recovered in car BT touch for the time being - even without any BT entries running!??? shall monitor and see. This is what the issue has been with ALL 2.3.4, 2.3.3 gb versions/roms. I'm stumped if i know what is causing it!
see edit post, thanks!!
Please note that Sam (author of SURFACE ROM) gives a good guide about how to achieve that in this post:
http://forum.xda-developers.com/showpost.php?p=15382251&postcount=2
thats a great post too - i've also downloaded this surface rom in order to try next if the sensation one screws up! Thanks very much!
Hello guys.
Official Gingerbread is finally available on Portugal.
I have currently Stock Froyo + Speedmod installed on my Galaxy S, so how can i update to Gingerbread?
Can i just update and Speedmod will still work?
Or should i install a stock kernel, then update, then install the Speedmod (Gingerbread version)?
Or i shouldn't update at all?
i'm interested in this too,i'm in the same situation (froyo+speedmod) and i'm quite a noob
is there someone who can patiently give us an hint about that? also about a good battery life gingerbread rom?
This is what I did.
1. Disable any lagfix - convert back to rfs (very important).
2. Back up all apps, contacts, data, photos etc from internal memory. Use something like Titanium backup or Mybackup pro.
3. Update through Kies for an official update.
4. Install latest Speedmod kernel for gingerbread (not Froyo version). Use odin.
5. Install superuser from clockwork mod recovery.
6. From recovery, do a factory data reset (make sure you have everything backed up first!)
7. Restore previously backed up apps, data etc, sync with google calendar.
8. Redo lagfix from recovery (convert to ext4).
Battery life at first seemed all over the place but has now settled down and is similar to Froyo/speedmod.
The phone is smoother and faster to use.
Thank you a lot!
That's exactly what i'm going to do!
thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?
skeletonboy said:
thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?
Click to expand...
Click to collapse
If Kies is showing that there is an update available then I think you should be ok.
If not then it is a case of flashing the whole firmware with odin. Open phone dialer and enter *#1234# and you will see the firmware details you are on now. It is worth making a note of these so you can reflash your current firmware if there is a problem.
okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?
Everything is working better than ever, except for one little thing: The GPS.
Today i turned on GPS and tried to use my navigation software (CoPilot) and the GPS signal just didn't fix at all!
I ended by not using it, but i don't know why it doesn't work. It always worked wonderfully well before this update...
skeletonboy said:
okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?
Click to expand...
Click to collapse
Still try kies first. If no luck there is a lot of info in this thread.
http://forum.xda-developers.com/showthread.php?t=723596
Make sure you can get into recovery mode first. Power button, volume up and home pressed all at once. Let go home button when Samsung logo appears.
ok thanks for the infos! i'll do it all when i can have a bit of relax,i am relocating so i need a working phone during these days
so i did it then!
flashed darky's resurrection 10.2 and then updated to doctorz rom jvt leaving ext4 enabled with no probs: another phone
just needs a good theme now..
Hi,
I have bought a Samsung Galaxy GT-I9000 six months ago. It always restarts by himself or crashes. And I've still couldn't find the problem. I have already tested with: Gingerbread 2.3.5, 2.3.6 and Cyanogen 7.1 and 7.2 RC1. What happens is that with Gingerbread it restarts autmatically while on the Cyanogen it only crashes and I need to remove the battery and reinsert it.
I've taken my phone to a Samsung technician. He said that my battery was with 90% of its capacity, the memory and processor were tested and they are ok. He said that it wasn't any hardware problem.
His conclusion was that Android wasn't a good OS, and that is happens with all phones. But if the hardware is OK, and I've hard resetted many times, installed a lot of differents OS, why does the problem still persists? It just doesn't make any sense.
The interesting part is that when the phone has few application, the phone works fine. It only start restarting when I install 10 applications from market, for instance.If I have 3 apps installed, it may reboot but much less frequently.
In your opinion, was the conclusion of the technician correct?
I've encountered similar problem a long time ago. At that time I deleted the apps , and then rebooted the phone, one by one and finally the SGS works fine again without a certain app. So try to find out which app crashed your phone.
App is not responsable for the reboot
Well, I don't think this issue is related to a specific application. Because the technician also noticed the problem when he installed a lot of applications that he has chosen without knowing my apps.
Besides that I am using the common ones like: Facebook, WhatsApp, YouTube, Gmail, Google Maps, Skype, and BBC News. They are all updated. I don't think any of them has a bug that resets the phone.
My Phone will reboot by itself sometimes when i enable wifi
This has only started since Darky's 10.2 (JVQ kernel) has been installed on my phone. I have since installed ICSSGS 4.2 with semaphore 0.91 (no reboots) and are now back on stock (factory/carrier) gingerbread ROM and rebooting occurs when wifi is enabled sometimes.
Try cm9. I used to get random reboots on gingerbread roms but since being on cm9 I haven't had one. Current using the latest nightly with stock kernel and have been running since build 7. Battery life is great and is stable. I highly recommend :thumbup:
Sent from my I9000 running CM9
Something is dodgy, imho, backup all apps using Titanium, wipe phone, wipe caches, factory reset, then install stock gb, say jw4 using odin with pit file and repartition, hard reset again, then root using latest semaphore kernel. Remove usual bloatware, then Restore apps 1 by 1 to see what's causing the problem. Think its always best to start from scratch. Backup efs folder, and sms etc first.
Sent using TCP/IP
More info
Wait guys, you are using the terms I don't know.
About the comment: "then install stock gb, say jw4 using odin with pit file and repartition, hard reset again, then root using latest semaphore kernel. ", I have some questions:
What's stock gb? What is jw4? Can you send me a link about how to do so or where I can download jw4? There is semaphore kernel and stock kernel? What is the difference between them? The original kernel is not good? Why do I need to install it?
The other commend was: "Current using the latest nightly with stock kernel". I will try that. But how can I install cm9 with stock kernel? Could you send me a link with the steps?
About the comment: "I have since installed ICSSGS 4.2 with semaphore 0.91 (no reboots) and are now back on stock (factory/carrier)". Never used Ice Cream Sandwich for Samsung Galaxy S. How can I install it with semaphore 0.91? Is this OS better than Gingerbread and Cyanogen?
Sorry about the stupid questions,
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5. I have rooted my phone with Odin3 v 1.85, but it's been running slow even before the root. (In fact, I rooted the phone so I could install a lagfix, but I can't find one for Captivate I897 running on 2.3.5).
Anyway, I don't see the reason for games and apps to be running slow because I've heard that the Captivate has a pretty good GPU. Also, it's not like I've overstocked my phone's storage; I only have a few apps.
I've also made a short video explaining my problem further. Just search "slow captivate" on youtube. I should be the first video: "Really Slow Samsung Galaxy S Captivate - Fix?"
I've searched everywhere for a fix, but I can't find anything, so I came here. Does anyone have an idea on how to fix this, or at least reduce the lag?
Thanks in advance,
-xxTDGPainxx
I was seeing my phone work slower and slower on 2.3.6, I suspected that the developers of the apps I used were starting to develop for ICS and that maybe it was different enough that the updates were causing the apps to misbehave on older versions. I flashed to ICS just to see... and it was a great move, ICS on the captivate flies!!! I used SlimICS, I think it is the right way to go for Galaxy S phones...
xxTDGPainxx said:
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5.
Click to expand...
Click to collapse
Have you run any tools to see what is sucking up your phone's resources?
[email protected] said:
Have you run any tools to see what is sucking up your phone's resources?
Click to expand...
Click to collapse
No, I don't think I've checked that. What app do you recommend on checking that?
xxTDGPainxx said:
No, I don't think I've checked that. What app do you recommend on checking that?
Click to expand...
Click to collapse
I would say cpu spy
Sent from my SGH-I897 using xda premium
First of all, lagfix isn't really used anymore. Also, I would say to get rid of those task killing apps. They don't help and only add to your problems. A lot of the symptoms you encountered are pretty common, and I was expecting something much worse. You seem to be running a different kernel that allows overclock; which is it?
If all else fails, try ICS
Sent from my ICS Samsung Captivate
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
xxTDGPainxx said:
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
Click to expand...
Click to collapse
You flashed it twice, correct? Try wiping your data.
korockinout13 said:
You flashed it twice, correct? Try wiping your data.
Click to expand...
Click to collapse
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
xxTDGPainxx said:
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
Click to expand...
Click to collapse
This is the stable ics in my opinion, but i use aokp by sixstrings.... http://forum.xda-developers.com/showthread.php?t=1362092
Sent from my SGH-I897 using xda premium
Maybe don't wipe dalvik cache. That can sometimes result in that happening
Sent from my ICS Samsung Captivate
I gave up on ICS... I could not get it to work for the life of me and it was getting me extremely frustrated. I almost bricked my phone (I think).
Maybe I'll try it again if someone could link me to a detailed step-by-step tutorial to upgrading to ICS. I'm very new to the way android works and a lot of the tutorials are just plain confusing to me...
I ended up reverting back to GB 2.3.4.
Thanks for helping me out though.
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
korockinout13 said:
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
Click to expand...
Click to collapse
The one in your sig is about the best I've seen. Great job!
GUIDE TO INSTALL ICS, my way at least
Hey if you're looking for a good guide to putting ICS on your captivate I can help, The first time i tried ICS i messed things up and angrily decided that i wouldn't try it again and reverted back to 2.3.5, after carefully trying ICS again i love it so much. I won't ever go back to android 2.whatever.
I used CM9 ICS and have no issues or bugs. It's possible there are other better ICS roms but i prefer this one since i know for a fact that it works great.
http://forum.xda-developers.com/showthread.php?t=1363760
You'll need to download CM9 v17 and a gapps package on your SD card.
trust me, ICS is worth it, it's much better than 2.3
if you have titanium backup backup your user apps (NOT SYSTEM APPS/SYSTEM DATA)
Rom installation:
First things first always do a nandroid backup so you can go back easier, if necessary.
once thats done go to CWM recovery and do a wipe data/factory reset, wipe cache partition. once that's done install the CM9 .zip package for the rom.
IT WILL STOP HALFWAY THROUGH AND REBOOT ITSELF, as this is the new kernel being installed. while it's still rebooting pull the battery and let it turn off, reboot straight into CWM recovery.
once this happens go back to install you CM9 .zip file again. it will finish all the installation after that. once it finishes the install you should definitely install the Gapps.zip. it will load up your google apps (market,gmail,youtube,etc and your google account sync) if you don't load the Gapps you will not have very much functionality to your captivate.
once you have your google apps installed you should be ready to fly with a fast responsive captivate. Hope this helps, it took a few trial and error runs before i figured it out.
If you used titanium backup to backup your apps you can restore APPS ONLY!!! don't restore any system data/system apps!!!! it's very important that you don't do that.
that should be it. enjoy your ICS, it's much better than android 2.blah
Fastness: CM7
Sexyness: CM9
That's the answer to everything.
I have run aokp (my current) and doc's master. Both have been great!
I'm far from an Android guru but if you follow the directions, you will be ok. Both also have relatively supportive forums if you get in a jam.
Sent from my SGH-I897 using Tapatalk