Database Info

[STOCK FLASH][ODIN]DK05 Filesystem + DK17 Kernel + Clockwork Flash Included

Well since I got bored and wanted a PoC what we have here is....
**Neglected to include thanks...
- noobnl and Firon for the CW zImage from the 1click
- noobnl for the dk17 kernel and odin
- monopolykiller for the dk05 leak
- skeetslint,firon and bubby323 for the chats about it.
A Jump start for new users:
DK17 Kernel
DK05 File-system
DK05 Modem
Latest Clockwork installed as 3button Recovery.
It is not zip aligned, not pre-rooted, not deodexed and not compressed.
Included in the zip is Odin 1.3 with the Original Pit, because Odin 1.61 Hates this md5.
**FLASH AT OWN RISK**
It has been tested on my phone but it WILL overwrite everything(except SDcard of course so make a Nand)
Notable Fixes from the dk17 kernel are that the camera doesn't FC, lock-screen lag is gone and that Barcode Reader will work again!
Download: SPH-D700-DK05-Extended
Step 1. Boot into download by powering off your phone holding 1 on the keyboard and holding power til you see the little Yellow digger.
Step 2. On your computer launch odin.exe and select the pit and under PDA select the SPH-D700-DK05-Extended.tar
Step 3. Plug in the usb cable.(if it's done right you should see a yellow Com device.)
Step 4. Click Start and wait.
That's it. You've got DK05 files ystem and modem with a dk17 kernel and clockwork preinstalled so all you'd need to do is run z4root to root it OR hold down Vol Down, Camera and Power to get into clockwork to flash your own rom.
Enjoy!.

What are the benifits of this over just flashin in cwr?
Thanx in advance.

Its stock.
Sent from my Android using Tapatalk and Wifi/CDMA

Thank you... I was about to create my own, lol

It means instead of having to do all the boring stuff and flashing back to an older version you can odin flash this to as dangdang said "stock" and essentially start yer phone from a happy place without needing to screw with the 1click to get a rom loaded.

After doing this, how do we get a system dump?

same way as normal i'd guess. cept the modem isnt gonna flash because it's not properly signed like the di18 is(thats why it has to be odin flashed)
Essentially i just made this for simplistic fun, it lets you odin to "stock" and have CW again at first boot to flash whatever yer hearts content just by copying it to the SD .

art3mis-nyc said:
same way as normal i'd guess. cept the modem isnt gonna flash because it's not properly signed like the di18 is(thats why it has to be odin flashed)
Click to expand...
Click to collapse
I used to know how to do this, but could you refresh my memory?

Well seeing as how i keep forgetting to do so for myself(and have never done one).
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
Actually this post/thread is better: http://forum.xda-developers.com/showpost.php?p=8819675&postcount=26
Something along those lines i'd guess...

Does the gps work out of the box? I'm not having any luck with the dk05 rom and modem. Was going to try the flash di18, get gps lock, don't wipe, flash dk05 trick.
This would be a faster way for sure.

Well it works for me, your mileage may vary, but if you're already planning on flashing, i'm fairly sure the "give it a try and see" approach would be a good choice..

Odin is stuck at <ID:0/004> boot.bin
There is no progress bar, no indication anything happening. Should I battery pull and start over?

aestil said:
Odin is stuck at <ID:0/004> boot.bin
There is no progress bar, no indication anything happening. Should I battery pull and start over?
Click to expand...
Click to collapse
Same issue here. Pull the battery and use another file.
Every now and then I like to flash back to stock and start all over, so this is no big deal.

If you use the new odin 1.6 it does that which is why i included the 1.3, which shouldn't (or rather didnt for me)

Did it with Odin 1.3 and old .pit and it hung up.
Pulled the battery, tried again and got the same thing.
Switched to Odin 1.61 and new .pit and it went through. Strange, but who cares, it worked

By the way, thanks art3mis-nyc for putting this together as it makes starting all over absolutely painless!

I did get this flashed and it looks great thus far! But I do have the question, and I am sorry for asking this stupid one, what is 'z4root'? Or rather where do I find it?
Sent from my SPH-D700 using XDA App

mphillippi said:
I did get this flashed and it looks great thus far! But I do have the question, and I am sorry for asking this stupid one, what is 'z4root'? Or rather where do I find it?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This is the easiest way to go about it.
http://forum.xda-developers.com/showthread.php?t=770388

z4root is an app in the market that lets you jailbreak your phone without using the one clicks or even having it hooked to a computer.
the 1click is rather pointless with this ass CW is already there, i didnt really make it as a rom to use, it's more a starting point to play with that has Clockwork already there to flash back one of the other roms(or a previous rom you used)
was the simplest way to get peoples feet wet with the idea of odin and saved a step
(that being flash with odin THEN 1click to get CW back to flash.) this way it's just 1 odin flash back to stock and CW is there ready to flash you to the newest rom.

Can this be used for a first flash of cwm on a stock epic or is it only for flashing back?

What exactly bricks a Captivate?

Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App

rufex2001 said:
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you test the phone to make sure it can accept the button combinations to go into download mode (almost all do, except for a batch of faulty ones), there is almost nothing you can do that will truly "brick" the phone. A bad or interrupted flash will result in a boot loop, which you can recover from by forcing download mode, and using Odin to reflash back to stock.

Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.

Basically what causes a brick in any electronic equipment is from an interruption/error in any boot critical files. The item does not have the proper/complete instruction to turn on. You could say it is like starting a car being told to first put the key in
Sent from my SAMSUNG-SGH-I897 using XDA App

If you can use the 3 button combos to get into download or recovery mode, you are good to go. The only danger would be a bad Odin flash, but even so you'll have a chance to recover it by making a cheap USB jig (3 100k Ohm resistors into pins 3 and 4, I think, of the usb port) or buying one. This will boot the phone straight into Download mode.
When using Odin, there is only one stage where you can brick your phone for good, during the bootloader copy process, which probably takes less than a second.

Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App

rufex2001 said:
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
Click to expand...
Click to collapse
My Cappy is a 1007 build, too. I've soft bricked my phone more times than I can count, but Odin hasn't had anything to do with it. It can do it, though.
At one time in my life I flashed a new ROM every day, and I used Odin every time before I flashed.
On a side note, back when I flashed my first ROM, I pulled the battery during the first boot, dropped it, and then flashed another ROM without using Odin, and it never bricked it, so that should give you a good idea of how hard it is to brick these phones. Lol

Stupidity.
Sent from my Captivate.

opcow said:
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Click to expand...
Click to collapse
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?

No odin really is not that bad just don't unplug it while it is running. You would not want to unplug your computer when flashing a new bios
Sent from my SAMSUNG-SGH-I897 using XDA App

Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Sorry for any dumb or repeated question I may be asking.
Sent from my SAMSUNG-SGH-I897 using XDA App

Pierce533 said:
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
Click to expand...
Click to collapse
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.

rufex2001 said:
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Click to expand...
Click to collapse
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.

opcow said:
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
Click to expand...
Click to collapse
Thanks for the info. Is there a stock I897UCJF6 ROM that can be flashed with CWM? I haven't been able to find one and if there is one I would like to have one around to use. Thanks for taking the time to answer my questions.

opcow said:
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
Click to expand...
Click to collapse
That is exactly the sort of thing I had in mind! So I guess I could keep a CWM update.zip and a stock rom update.zip and some custom roms and just do everything directly from the phone and without Odin, right? Or am I missing something?
Sent from my SAMSUNG-SGH-I897 using XDA App

Guns don't kill people

opcow said:
Odin isn't bad so much as an unnecessary risk. Then there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build.
Click to expand...
Click to collapse
Yep. I have build 1008 that has always had the 3-button combo and lost it after using ODIN 1-click (I restored the combo with a later flash).
I believe opcow and others when they say that flashing back to stock is unnecessary. I just don't understand why the authors of some of these ROMs leave this as part of their installation guide.
Sent using XDA App

Pay close attention to the options in recovery when you are using a custom rom. It's part of the custom kernal, and of used properly can help you avoid odin. I avoid it because I have a mac and odin won't run on anything but windows. Custom recovery will allow you to format every part of the OS but the sbl.bin. Also in some custom recoveries there is an option to mount usb. This will allow you to format the internal sd then copy a new rom.zip and flash if you really want a clean flash. If your doing this make sure you are able to mount your sd before you format anything. Avoid stock 2.2 kernals because they have 3e recovery. There are ways around that but they have to be in play before you end up in a bootloop.
3e recovery + bootloop= odin recovery "only option".
Make sure lag fix for rom kernal A understands lag fix for rom kernal B. Also usually only a concern for stock 2.2 kernal. Other than that really hard to brick this phone.
Sent from my SAMSUNG-SGH-I897 using XDA App

As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.

ryude said:
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
Click to expand...
Click to collapse
Could you please explain what a wipe ROM is? Thanks

How I hard bricked my Captivate (FYI)

Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.

bigbyte.me said:
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
Click to expand...
Click to collapse
U got a jig?
Sent from my Captivate using XDA Premium

Zig won't help as nothing is helps only in case of Soft brick.
BTW i figured out where I went wrong, The cognition ROM contains seconday bootloader. So when I flashed it I ended up with Gingerbread primary and Froyo secondary bootloader and hence the Brick. I request all the rom dev to mention at the start of their post if their ROm contains bootloaders.

bigbyte.me said:
Flashed Cognition 4.3.2, flashed successfully.
Click to expand...
Click to collapse
^ That's where you went wrong. Cog flashes sbl. You ended up with one bootloader from 2.3, and one bootloader from 2.2.
There are videos of how to unbrick a perma-bricked phone with a riff box jtag unit on youtube. It'll require you to remove the motherboard and blow $150 or so on a riff box, though.

or you send it to someone with the equiptment, like mobiletechvideos.com and not learn about riff/boxing and spend less money... and and and...
or because it doesnt boot and they cant prove you voided your warranty send it back!

So, this could be avoided doing what?
-Going back to GB stock and from there going back to froyo stock (without 3 button fix)?

I don't think moviletech does crappys something about the solder points too close together.
Edit: but could be wrong.
Sent from my GT-I9000 using XDA Premium App

i was in a similar situation, no 3 button nothing worked my phone wouldn't even power on
but the one method that saved me was this,
Remove battery, SIM card, SD card (if present)
Connect USB cable from computer
While holding down up & down volume, re-insert battery
may be this could help you too.

mobile tech does and has been for over a month, and the first few people are free!
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
for me if i touched any buttons the jig would not work.
other methods wouldnt work either.
worth a shot.

You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897

You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin

1tontomato said:
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.

studacris said:
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
Click to expand...
Click to collapse
Yea your right it is the sbl.bin. It was a good idea before gingerbread, but I think it's time has passed especially since it's really easy to get past not having a button combo with a jig. A bad combination of bootloaders is a "brick" for sure.
Sent from my SAMSUNG-SGH-I897

amtrakcn said:
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
Click to expand...
Click to collapse
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.

bigbyte.me said:
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
Click to expand...
Click to collapse
I say none. ANYTIME you touch bootloaders there is a chance of hard bricking. If they don't have any, worst case is a "clay" (soft brick)

TRusselo said:
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
....
Click to expand...
Click to collapse
Perhaps I;m not out of the woods yet but a wrong action in ODIN had HB'd my Cappy. Your steps got me back to DL mode. Perhaps it is the 5 count. Patience not being my strong pt I had "not waited" until your recommendation.
I was trying from Continuum5.3 to get back to eclair so to carrier unlock when I made an ODIN error. Still need do that but for now I'll just be thankful that it lives, and move only forward..

its the not touching buttons that makes this trick work
if you replace the battery, what is your normal instinct?
try the power button! or try the button methods...
you are the first to confirm my trick!
congrats!
http://forum.xda-developers.com/showthread.php?t=731989

Use this to get back to stock safely!
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE
use the thanks button!

Hmm very interesting...
I thought your trick worked because it was a screw up in the param.lfs not a bootloader brick, guess not.

im surprised too...

Odin one click question

Can I use odin one click to revert to stock even though I have 1101 build cappy? It seems oc only works for 1010 and below. Should I use odin 3 and flash stock jf6 instead? Currently on cog 4.4.
Sent from my SAMSUNG-SGH-I897 using XDA App

some people have trouble with odin one click with newer models. some dont.
you can flash anything with the odin 3 flasher.
avoid stocks with bootloaders. or "3 button fix" versions.
if you dont flash bootloaders you should never hard brick.

Once back to stock, do you know if I can use kies to flash official froyo upgrade, or will that be a prob after flashing custom rom? Is there an odin flash that will get me stock 2.2 without using any bootloaders? I've searched, but seems like everything takes you back to eclair.
Sent from my SAMSUNG-SGH-I897 using XDA App

Cdub3 said:
Once back to stock, do you know if I can use kies to flash official froyo upgrade, or will that be a prob after flashing custom rom? Is there an odin flash that will get me stock 2.2 without using any bootloaders? I've searched, but seems like everything takes you back to eclair.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You could use the one Trusselo made.. In his sig right above your post

thats for rogers... is he rogers...?

I'm at&t. same thing right? I got one completely dead, bricked, cappy in the hands of samsung right now. Hoping they'll replace or fix me. Got one cappy in my hand that's being "borrowed" for the 30 day window till I find out what's up with the one samsung has. Hoping I can get functioning cappy back from samsung, and talk the wife into letting me keep the "borrowed" one. That way I have a stable one, and one to mess around with. Planning on taking on gingerbread, only once I've covered all my bases.....I think. Just wanted to know best way back to stock, just in case I needed to bring back the phone. Like I said, it's a 1101 build, and I'm currently running Cog4.4, so I didn't want to brick it with one click. Dumb noob question, but are boot animations same/diff from bootloaders. I opened archive on cog 4 and in system/bin their are boot animations. I flashed cog via rom manager. Did i just get lucky or are these not bootloaders, just animations? Is there a thread that shows which roms come with bootloaders and which don't?

read this it explains the boot process and what a bootloader is
http://forum.xda-developers.com/showthread.php?t=1049294
bootloaders are not the same as a boot animation.
animations are found in /system/media/bootanimation.zip
you didnt get lucky with cognition flashing a bootloader that will only **** **** up if you have gingerbread bootloaders which you didnt, so flashing a froyo secondary bootloader was fine (thats why its in there)
The bootloaders would be in the updates folder of the zip.

Thanks studacris. Seems the more I learn about all this, the more ii find stuff I didn't know. Constantly on forum trying to learn so I don't have to bother guys like you. Since I got ur attention, flashing to i9000 rom would require bootloaders correct? Looking to do that next. Currently im US, att, i896. Sorry to bother ya.
Sent from my SAMSUNG-SGH-I897 using XDA App

Sorry I meant i897
Sent from my SAMSUNG-SGH-I897 using XDA App

nope new bootloaders are only needed if you are jumping to gingerbread

only flashing the i9000 2.3.3 roms requires bootloaders. all the 2.2.1 roms will work without danger of bricking.
if all you did on the borrowed cappy is root and flash a kernel you can flash the backed up kernel and then unroot. (did you use sgs kernel flasher to flash the kernel like when we talked about it? did you back up the kernel?)
you might want to look at getting a jig just to have one around. samsung keeps releasing new builds of the phone and there are unknowns. there are mixed reports from the 1010 build and up. you should be able to use odin 1.7 and flash the jf6 from icezar1 and you still have stock bootloaders so there "should" be no need for odin one click.
all the problems last time must have been do to the gingerbread bootloaders in combination with your 1010 build phone, i should have told you to use odin one click, infact you should have had a jig before i encouraged you to try gingerbread, my fault, but i didnt have problems when i did the same thing.

Should I flash a i9000 kernel before a i9000 rom? Then after all is said and done, find a compatible modem? Only reason I want to go to i9000 rom is because there seems to be more available. Can I do all this via sgs kernel flasher and rom manager/cwm or does it have to be done odin for the first switch to i9000? I'm assuming I can go back between sgh I897 and i9000 no prob since no ginger boots are involved? Just to be clear, even if I flash a rom with bootloaders, it shouldn't be a prob as long as it's 2.2 rom? Are 2.2 boots backwards compatible if i want to flash back to stock? I ask cuz prob can't use oneclick cuz my build is to new. again, don't mean to be a pest. cut me off whenever you feel like it.

Roms are all in one package kernel and modems are included.

I was able to flash from the "phone ! pc" screen (kinda) May be useful for bricks?

I was able to flash from the "phone ! pc" screen (kinda) May be useful for bricks?
If this post proves to be useful and would serve better in another section then please move it.
Yesterday (June.09.2011) I got a refurb replacement for my Captivate, it was actually a new phone though and as far as I can read it's an 1105 build.
It came with Froyo 2.2 and no software updates from AT$T were available when I checked from the phone.
GPS didn't seem to do so well according to My Tracks recording a 22 mile motorcycle trip home.
I was going to try Cognition (Froyo based)
I was able to use the buttons on the phone to get into recovery 3e but it checks for signatures and I couldn't figure out how to root the phone and replace recovery.
I would have used one click root from my pc but I didn't have the proper windows drivers (net framework?)
I decided to flash Odin one click to stock (Eclair 2.1)
I also have the Odin stock 2.1 with 3 button fix that I had used on my other refurb captivate successfully.
This is where things went bad for me.
I used the 3 button fix version of Odin (I don't know if my result would have been different if I had used One click Odin instead and I'd like to know for later)
After the flash the phone would only boot to the phone ! pc screen no matter how many different button, battery, power button, usb cable, jig combinations I tried (Yes I have a jig)
Anyways, I had Odin one click (not the three button fix version) open and even though I only ever saw the ! screen on the phone I noticed that Odin was showing the device connecting and disconnecting when I pulled the usb cable.
What the hell, I thought I was bricked anyways so I hit Start. The phone showed a progress bar that mirrored what Odin was showing me, right below the ! icons on the phone.
After that I was able to use the jig to enter download mode, I tried both Odin (stock 2.1) versions I had and they ran the flash but the phone boot looped when I tried to start it up.
I then tried the method to update the bootloaders and move onto Gingerbread and I was successful, Running Serendipity VII now (Thanks MikeyMike01, ChanceM)
It was a nerve racking experience and I'm nervous if I decide to try to go back to Froyo again.
Maybe this info isn't new, maybe it's helpful. I may summarize later.
Any thoughts or tips to get back to Froyo if I want to later?

not weird at all.
here's what happened:the phone...!...pc screen just signifies that a flash was incomplete, the first flash with the 3 button fixed failed before it ever loaded any firmware, therefor the image for when download mode is initiated was missing, all that is is a .png. since it was missing the incomplete flash screen was the only thing there for it to call upon when DL mode was started.
odin one click bootlooped you cause it just does that to new phones...to get back to stock bootloaders use odin one click then use this http://forum.xda-developers.com/showthread.php?t=995143... or just use that and go back to stock eclair with the GB bootloaders. DO NOT FLASH THE 3 BUTTON FIX PACKAGE WITH GB BOOTLOADERS THAT WILL BRICK YOUR PHONE.

Thanks for the explanation!

studacris said:
not weird at all.
here's what happened:the phone...!...pc screen just signifies that a flash was incomplete, the first flash with the 3 button fixed failed before it ever loaded any firmware, therefor the image for when download mode is initiated was missing, all that is is a .png. since it was missing the incomplete flash screen was the only thing there for it to call upon when DL mode was started.
odin one click bootlooped you cause it just does that to new phones...to get back to stock bootloaders use odin one click then use this http://forum.xda-developers.com/showthread.php?t=995143...or just use that and go back to stock eclair with the GB bootloaders. DO NOT FLASH THE 3 BUTTON FIX PACKAGE WITH GB BOOTLOADERS THAT WILL BRICK YOUR PHONE.
Click to expand...
Click to collapse
Is there a reason they don't just include the intended PBL with that SBL for the 3 button fix? it would solve all the problems... I'll go figure this one out.

AdamOutler said:
Is there a reason they don't just include the intended PBL with that SBL for the 3 button fix? it would solve all the problems... I'll go figure this one out.
Click to expand...
Click to collapse
they dont have the PBL file. all they have had is the SBL

A similar thing happened to me on my replacement. It came with stock 2.2 and when I tried to use Odin one click it failed. I pulled the plug and after that nothing was getting me into download mode. No button combinations or jig worked. When I was trying more combinations I had left odin open and realized it was showing as connected even though I was only getting the phone ! pc screen. So just like you I figured what the hell and went for it. 2 minutes later I was at stock 2.1.

nybmx said:
A similar thing happened to me on my replacement. It came with stock 2.2 and when I tried to use Odin one click it failed. I pulled the plug and after that nothing was getting me into download mode. No button combinations or jig worked. When I was trying more combinations I had left odin open and realized it was showing as connected even though I was only getting the phone ! pc screen. So just like you I figured what the hell and went for it. 2 minutes later I was at stock 2.1.
Click to expand...
Click to collapse
What build number on yours?
I'm still having problems, post to follow...

I just tried to go back to Froyo from Gingerbread.
I followed the instructions linked to in this thread (thanks) http://forum.xda-developers.com/showthread.php?t=995143...
The following 4 flashes just left me in a boot loop but I was able to use my jig to get into d/l mode each time.
I did get a random Odin 3 v1.3 from the net that had GT-P1000 instead of i897 or i9000 on it's title when run. I don't think it was the issue though since OneClickDownloader also failed the same way for me.
Odin 3 v1.3 JF6 Secure
Odin 3 v1.0 OneClickDownloader
Odin 3 v1.3 JF6 Secure
Odin 3 v1.7 JF6 Secure (This Odin came with the Gingerbread installation package I got from Cezar/icezar1 (I think)
Now I am running a fever and I'm generally slow but I think I'm following your suggestions.
edit; I wrote 1.2, I meant 1.3

Pirateghost said:
they dont have the PBL file. all they have had is the SBL
Click to expand...
Click to collapse
God damnit.... NEVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER flash a PBL without a matching SBL.... This is the cause of bricking for 90% of captivates.

AdamOutler said:
God damnit.... NEVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER flash a PBL without a matching SBL.... This is the cause of bricking for 90% of captivates.
Click to expand...
Click to collapse
yep. but the sbl was all that was needed when that package was created months and months ago. we didnt have any need to worry about pbls at that time...then 2.3 came along

DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)

daveyian said:
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
Click to expand...
Click to collapse
Well I know 4.5 and above for cognition doesn't have boatloaders in it. You might want to unzip roms and check for bootloaders just to be safe.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

daveyian said:
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
Click to expand...
Click to collapse
It will work. I am running firefly 3.0 at the moment, on GB bootloaders. I have not tried cyanogen yet. I'm sure eventually all the little bugs will get worked out of gingerbread, and I'll be back on it.

wow i posted about this MONTHS ago....
heres the link.....
http://forum.xda-developers.com/showthread.php?t=988927&highlight=flash+from+soft+brick

I got that phone ! pc last night while trying to odin back to 2.1 from stock. Odin didnt make any progress for 10 mins and I removed battery. Thought I was screwed. Removed the usb and pulled the bat. Opened odin and plugged it back in and the same screen came right up. Just held down the volume keys and power button till the screen flashed once and noticed odin recognized the com port. Then tried odin again and it worked fine... even displayed the little blue progress bar on that screen lol.

daveyian said:
What build number on yours?
I'm still having problems, post to follow...
Click to expand...
Click to collapse
A refurb 1008

true story!
happened to me 2!