【Guide】How To flash ANY Captivate ROM from Stock (including ICS)

[TRusselo]

or just follow instructions in OP.... adams heimdall method

 

[GaryOkie]

OK, got it. It flashed perfectly and reboots GB 2.3.4 KH3 just fine. I can also now go into CWM recovery mode, and was just about to flash Illuminate 2.1.1 but caught myself.

I think it would be a mistake to install a 2.3.5 KK2-based ROM onto KH3, so will hold off.

I guess what I will need to do now is use Odin to get KK2, and maybe Corn kernel as well, before Illuminating.

Thanks very much for your help!

Thanks very much for your help!

---------- Post added at 01:30 PM ---------- Previous post was at 01:22 PM ----------

or just follow instructions in OP.... adams heimdall method

Yep, that's exactly what I did. Followed the instructions very carefully, and repeated the process twice to make sure. The GB bootloaders installed fine with Adam's heimdall 1-click. It appears that the Talon kernel was the issue, but the boog kernel w/CWM in jmtheiss KH3 heimdall worked just fine.

 

[jmtheiss]

OK, got it. It flashed perfectly and reboots GB 2.3.4 KH3 just fine. I can also now go into CWM recovery mode, and was just about to flash Illuminate 2.1.1 but caught myself.

I think it would be a mistake to install a 2.3.5 KK2-based ROM onto KH3, so will hold off.

I guess what I will need to do now is use Odin to get KK2, and maybe Corn kernel as well, before Illuminating.

Thanks very much for your help!

Thanks very much for your help!

---------- Post added at 01:30 PM ---------- Previous post was at 01:22 PM ----------


Yep, that's exactly what I did. Followed the instructions very carefully, and repeated the process twice to make sure. The GB bootloaders installed fine with Adam's heimdall 1-click. It appears that the Talon kernel was the issue, but the boog kernel w/CWM in jmtheiss KH3 heimdall worked just fine.

Unless I'm mistaken, the Illuminance rom, when flashed, should set you up to be on the Illuminance setup you'll need. No need to Odin anything.

 

[GaryOkie]

Unless I'm mistaken, the Illuminance rom, when flashed, should set you up to be on the Illuminance setup you'll need. No need to Odin anything.

I realize that flashing Illuminance_v2.1.zip is done with CWM, not Odin. However, I thought Illuminance required KK2 before flashing. I figured I was asking for trouble flashing it over KH3. This ROM doesn't upgrade to KK2 as well, does it?

 

[TRusselo]

the only reason to use odin is if you don't have c w m, or need to upgrade bootloaders.

when you flash a rom they are usually "wipe roms". the wipe whatever is on your phone.

there is no need to flash to stock if the rom is going to be "wipe it" away...

I said that in the instructions. if you have c w m you don't need to odin anymore

 

[GaryOkie]

Please ignore this question - "This ROM doesn't upgrade to KK2 as well, does it?" I know that can't be true. So my apologies for not understanding your comment that flashing the Illuminance setup is all I will need when it is clear from the installation information that GB 2.3.5 is a prerequisite.

There does not appear to be an Odin KK2 1-click available anywhere, nor a Heimdall KK2 other than Adam's (which has a Talon kernel that does not work for me).

---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------

the only reason to use odin is if you don't have c w m, or need to upgrade bootloaders.

when you flash a rom they are usually "wipe roms". the wipe whatever is on your phone.

there is no need to flash to stock if the rom is going to be "wipe it" away...

I said that in the instructions. if you have c w m you don't need to odin anymore

Thanks very much for your patience explaining this to me. I did not understand that CWM could do so much - including fully replacing Odin except for BL's.

 

[jmtheiss]

In looking at Illuminance's webpage, it appears that 2.1.1 is based on KK2. So, all you should have to do is backup your stuff, download the rom, put it on your internal SD card, boot to CWM, do the wipes (wipe dalvik, wipe cache, format user data), and then install the zip file. Once you're there, download the Corn Kernel CWM version, put that on your internal SD, and flash it from CWM. That should give you the setup you're hunting for.

 

[TRusselo]

the manual wipe of those partitions in cwm is totally optional. (as in I NEVER have)


the edify install script of any correctly made cwm rom has:

delete_recursive("/system");
delete_recursive("/dbdata");
delete_recursive("/cache");
delete_recursive("/data");



and delvik is in one of those partitions, so that would just be redundantly redundant.


download rom to sdcard/anywhere
boot to cwm
flash from cwm
done

and again to clearify earlier, odin would only be needed to go back to a 2.2 cwm2 rom/kernel combo, or upgrade bootloaders

 

[jmtheiss]

the manual wipe in cwm is totally optional.as in I NEVER have.


the edify install script of any correctly made cwm rom has:

delete_recursive("/system");
delete_recursive("/dbdata");
delete_recursive("/cache");
delete_recursive("/data");



and delvik is in one of those partitions, so that would just be redundantly redundant.


download rom to sdcard/anywhere
boot to cwm
flash from cwm
done

and again to clearify earlier, odin would only be needed to go back to a 2.2 cwm2 rom/kernel combo, or upgrade bootloaders

Good point - hadn't considered that. I'm a little paranoid/overcautious, so I do the manual wipe each time, but as TRusselo pointed out, it's not really necessary.

 

[GaryOkie]

In looking at Illuminance's webpage, it appears that 2.1.1 is based on KK2. So, all you should have to do is backup your stuff, download the rom, put it on your internal SD card, boot to CWM, do the wipes (wipe dalvik, wipe cache, format user data), and then install the zip file. Once you're there, download the Corn Kernel CWM version, put that on your internal SD, and flash it from CWM. That should give you the setup you're hunting for.

Fantistic! I've now reached the goal of having KK2/Corn/Illuminance running along with an ICS/Illuminance theme. Quite a big jump for me coming from stock - and a lot to comprehend.

Thanks so much jmtheiss & TRusselo for all your advice!

 

[jmtheiss]

Fantistic! I've now reached the goal of having KK2/Corn/Illuminance running along with an ICS/Illuminance theme. Quite a big jump for me coming from stock - and a lot to comprehend.

Thanks so much jmtheiss & TRusselo for all your advice!

Great to hear that you got where you were going.

 

[askpcguy]

I been searching around for anything that explains if it is possible to Clockwork Mod flash Gingerbread boot loaders on the Captivate. Reason is, I am at work and want to try out Gingerbread bootloaders. I'll keep searching.

Also, can nandroid backup restore Froyo bootloaders over the gingerbread bootloaders? Or is that only asking for a hard brick?

 

[TRusselo]

no it must be done with odin.

 

[Snow.Goose]

Hey, I've got a question.... I used to be running cm7 but yesterday, I tried out some other roms. I flashed back to stock, and installed some roms, but now I have the at&t splash at boot.

How would I go back to the black sgh-i896? Should I go back to Rogers 2.3 stock w/o BL and get root+cwm?

If I get cwm, I can just restore back to my backup before I started flashing other roms
Sent from my SGH-I897 using XDA App

 

[TRusselo]

are you seeing i896 then ATT or just ATT? ( actually ATT twice, but you can't tell)


the first screen is fixed or customized with the link in my sig. Captivate Bootscreen Replacementand if this is the case you didnt flash to stock with MY ROGERS STOCK flashes. because my stock flashes specifically fix that issue except the 2.3.3 ONEclick odin the other NONoneclick method works fine. and other 6 flash packages work fine too

the second ATT splash screen is built into the kernel, and you are probably on a custom rom built on At&t and we dont have the kernel source code to fix that. you would have to find a custom rom built on ATT 2.3.3 and flash a Rogers 2.3.3 kernel to fix that issue (not worth it). or almost any custom 2.2 kernel and rom (we had the source back then). the second screen you are just going to have to live with if you want new custom roms. Rogers wont update past 2.3.3 (doubt they will)

 

[Snow.Goose]

are you seeing i896 then ATT or just ATT? ( actually ATT twice, but you can't tell)


the first screen is fixed or customized with the link in my sig. Captivate Bootscreen Replacementand if this is the case you didnt flash to stock with MY ROGERS STOCK flashes. because my stock flashes specifically fix that issue except the 2.3.3 ONEclick odin the other NONoneclick method works fine. and other 6 flash packages work fine too

the second ATT splash screen is built into the kernel, and you are probably on a custom rom built on At&t and we dont have the kernel source code to fix that. you would have to find a custom rom built on ATT 2.3.3 and flash a Rogers 2.3.3 kernel to fix that issue (not worth it). or almost any custom 2.2 kernel and rom (we had the source back then). the second screen you are just going to have to live with if you want new custom roms. Rogers wont update past 2.3.3 (doubt they will)

it's the first screen. Running glitch kernel, so it's not the second screen... I haven't flashed your stock yet, just wondering how I should go about it. The first time I ever put cwm on my phone, I followed cyanogenmod's wiki (heimdall and speedmod kernel). It's almost bricked way to many times, so i'm looking for a different method. Sorry if I wasn't clear on what I meant.

I'm on cm7 with at&t boot screen, I want to be on cm7 with the black boot screen.
Edit: So it's just bootloader that is different right now? Reading your link right now
Sent from my SGH-I897 using XDA App

 

[TRusselo]

the bootloader points to a file in the params.lfsparams.lfs can only be flashed by odin.


you must have at some point flashed an Att one click...
either way the bootscreen replacer will work.
go for the i897 bootloader version. logo_ATNT.jpg youll find out...

 

[Snow.Goose]

Okay. Thanks for your help!

Sent from my SGH-I897 using XDA App

 

[Kayen]

Hey, so i've been meaning to upgrade to GB for awhile, been running Fasty 2.5 for awhile, but decided it was time to move up into the GB world.
I did steps 1-10, with Odin 1.7, first i put the phone into download mode, and then placed PDA.tar.md5 into PDA, pressed start.
Closed ODIN, and reopened it.
Then after phone rebooted, i put it in download mode again - placed "Samurai-1.3.tar" into PDA, pressed start. Phone went into AT&T boot screen after uttering a random voice for abit. I waited till it finally rebooted. The phone seems to be stuck in a bootloop now.

Any solutions?

EDIT: 593048 bootloops later, I somehow ended up in recovery mode, and flashed my rom...
And now it works.

Thanks man, GREAT guide!

 

[TRusselo]

yes you must boot STRAIGHT into recovery at that point. that kernel wont work with the rom that you WERE on, that kernel is only used to cwm flash your next rom.