Database Info

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

[Q] Lost 3 Button Combo

When I got my Captivate, it had 3 button combo. I flashed back to stock with Odin One Click many times, and it still worked. Even after MIUI and CM7. I just flashed Torch 2.03, and I don't have it anymore... it doesn't work no matter what I do. I flashed the special stock ROM with working 3 button for now... but how did Torch kill my 3 button combo and how do I permanently get it back if I had it?

Haloruler64 said:
When I got my Captivate, it had 3 button combo. I flashed back to stock with Odin One Click many times, and it still worked. Even after MIUI and CM7. I just flashed Torch 2.03, and I don't have it anymore... it doesn't work no matter what I do. I flashed the special stock ROM with working 3 button for now... but how did Torch kill my 3 button combo and how do I permanently get it back if I had it?
Click to expand...
Click to collapse
Look in the zip package and see if there is a sbl.bin, I think that is what overwrites the 3 button combo on some model versions.

jhernand1102 said:
Look in the zip package and see if there is a sbl.bin, I think that is what overwrites the 3 button combo on some model versions.
Click to expand...
Click to collapse
No sbl, ROMs usually don't flash that. I just don't get it, it worked perfectly, through MIUI, CM7, and KB1, but after Torch it doesn't work.

Is torch based on GB? If so using odin can cause problems.
Sent from my SAMSUNG-SGH-I897 using XDA App

megatronisabeast said:
Is torch based on GB? If so using odin can cause problems.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I897UCKB1 ROM, 2.2 official Froyo for Captivates.
Also I tried, standard 3 button, and the ones for Gingerbread (even though it isn't) just in case, I tried every possible combo. I've always done it easily, since July.

When you flashed the 3 button Odin package you got your 3 button combo back right? Then you flashed torch again and you lost it? I think you will need to pull the fixed sbl.bin out of a working ROM and place it in the torch package to get it back.

jhernand1102 said:
When you flashed the 3 button Odin package you got your 3 button combo back right? Then you flashed torch again and you lost it? I think you will need to pull the fixed sbl.bin out of a working ROM and place it in the torch package to get it back.
Click to expand...
Click to collapse
I had it, flashed Torch and lost it, and got it back with the 3 button stock package. I refuse to flash Torch again... I don't want to lose it. Anyway most ROMs don't flash sbl.bin.

Haloruler64 said:
I had it, flashed Torch and lost it, and got it back with the 3 button stock package. I refuse to flash Torch again... I don't want to lose it. Anyway most ROMs don't flash sbl.bin.
Click to expand...
Click to collapse
Well DG's uses a fixed sbl.bin with his ROM's so people won't loose it. You can pull it out of his and put it in torch and it should work.

jhernand1102 said:
Well DG's uses a fixed sbl.bin with his ROM's so people won't loose it. You can pull it out of his and put it in torch and it should work.
Click to expand...
Click to collapse
Oh, really? Cool.
I didn't want Torch to begin with, I just wanted to play around with it. I just posted here because it's scary having a ROM kill your combo.

Try flashing Cog 4.3. If I remember correctly, all the cog roms include an sbl.bin with a working 3 button combo. Once you have a working sbl, don't flash roms that include their own sbl and you should be fine.
Also, be aware that flashing sbl can brick your phone.. like, permanently. So, once you have a working sbl in place, I'd keep bootloader flashing to an absolute minimum.

modest_mandroid said:
Try flashing Cog 4.3. If I remember correctly, all the cog roms include an sbl.bin with a working 3 button combo. Once you have a working sbl, don't flash roms that include their own sbl and you should be fine.
Also, be aware that flashing sbl can brick your phone.. like, permanently. So, once you have a working sbl in place, I'd keep bootloader flashing to an absolute minimum.
Click to expand...
Click to collapse
Thanks for the advice. I have a working one using the 3 button stock package at the moment. sbl is in the updates folder in the zip?
I'm just upset that I had a permanent 3 button combo and it's somehow gone. I really enjoyed being one of those people with a permanently working combo, being able to flash to stock and stuff.

Haloruler64 said:
Thanks for the advice. I have a working one using the 3 button stock package at the moment. sbl is in the updates folder in the zip?
I'm just upset that I had a permanent 3 button combo and it's somehow gone. I really enjoyed being one of those people with a permanently working combo, being able to flash to stock and stuff.
Click to expand...
Click to collapse
My Cappuccino has had problems with the 3 button combo since I flashed a Gingerbread ROM.
CM7 Inspire 4G

So there are only three reasons that the button combo can go away:
1 - You inadvertently flashed either sbl.bin and/or boot.bin at some point, or if you use Odin 1-click, your copy is corrupted, as all of the 1-click's will flash both sbl.bin and boot.bin.
2 - Something horrible has gone wrong from a software standpoint. Nothing in Android SHOULD ever be able to touch the SBL or BOOT partitions, but it doesn't mean it's not possible. A "bad program" of some sort, running around with root access, may have accidentally corrupted something, which is causing your problems. More likely, you had an incompatible version of Clockworkmod running at some point, and that screwed with one of those boot partitions.
3 - Your device is developing slash has developed, a hardware problem. Either causing some corrupt sectors in the boot or sbl partitions, or perhaps even at a lower level. Could be something as simple as a few bits got corrupted, and it will never happen again, or it could be indicative of more problems to come.
~~~~~~~~~~~~~~~
To fix it, I would simply flash the "3 button combo fix" that is floating around these forums, and see if that helps you. If you have a pre version 1010 Captivate, and were lucky enough to always have the 3-button combo working, simply flash back to the stock 1-click JF6 and that should fix all your problems.
If neither of those work, then perhaps there is a more serious hardware problem developing, in which case, I would replace your Captivate while it's still under warranty.
And PS, I would refrain from flashing boot.bin and sbl.bin updates from CWM. Yes, I know everyone seems to think it's safer, (though errors in file copy can happen just as easily and as undetected as in an ODIN flash), but I've quite literally re-flashed my boot.bin and sbl.bin via 1-click hundreds of times without bricking. Just make sure your cable is securely attached to both phone and computer, and that your girlfriend, cat, roommate, pet dinosaur, etc are kept far away from you and your computer while flashing. I say this because if something has already going wrong, CWM style flashes may not completely fix the problem. Whereas ODIN style flashes (either from the standalone ODIN, or via 1-click) tend to have more power to "overwrite" whatever has gone wrong. I'm sure many people will disagree with that, but hey, I've been flashing and screwing with my Captivate for some 7 months now, "soft bricked" it more times then I can remember, but have never had a single problem that couldn't be fixed with a nice stock 1-click flash.
~~~~~~~~~~~~~~~
Hope that helps!

Shammyh said:
So there are only three reasons that the button combo can go away:
1 - You inadvertently flashed either sbl.bin and/or boot.bin at some point, or if you use Odin 1-click, your copy is corrupted, as all of the 1-click's will flash both sbl.bin and boot.bin.
2 - Something horrible has gone wrong from a software standpoint. Nothing in Android SHOULD ever be able to touch the SBL or BOOT partitions, but it doesn't mean it's not possible. A "bad program" of some sort, running around with root access, may have accidentally corrupted something, which is causing your problems. More likely, you had an incompatible version of Clockworkmod running at some point, and that screwed with one of those boot partitions.
3 - Your device is developing slash has developed, a hardware problem. Either causing some corrupt sectors in the boot or sbl partitions, or perhaps even at a lower level. Could be something as simple as a few bits got corrupted, and it will never happen again, or it could be indicative of more problems to come.
~~~~~~~~~~~~~~~
To fix it, I would simply flash the "3 button combo fix" that is floating around these forums, and see if that helps you. If you have a pre version 1010 Captivate, and were lucky enough to always have the 3-button combo working, simply flash back to the stock 1-click JF6 and that should fix all your problems.
If neither of those work, then perhaps there is a more serious hardware problem developing, in which case, I would replace your Captivate while it's still under warranty.
And PS, I would refrain from flashing boot.bin and sbl.bin updates from CWM. Yes, I know everyone seems to think it's safer, (though errors in file copy can happen just as easily and as undetected as in an ODIN flash), but I've quite literally re-flashed my boot.bin and sbl.bin via 1-click hundreds of times without bricking. Just make sure your cable is securely attached to both phone and computer, and that your girlfriend, cat, roommate, pet dinosaur, etc are kept far away from you and your computer while flashing. I say this because if something has already going wrong, CWM style flashes may not completely fix the problem. Whereas ODIN style flashes (either from the standalone ODIN, or via 1-click) tend to have more power to "overwrite" whatever has gone wrong. I'm sure many people will disagree with that, but hey, I've been flashing and screwing with my Captivate for some 7 months now, "soft bricked" it more times then I can remember, but have never had a single problem that couldn't be fixed with a nice stock 1-click flash.
~~~~~~~~~~~~~~~
Hope that helps!
Click to expand...
Click to collapse
I haven't actually, Torch killed it and it doesn't have an sbl in it. Flashing back to stock always kept 3 button combo, even though it flashes an sbl that people without the combo need to avoid.
Nothing new on my phone really. CWM is for i897, also used CM7's CWM 3.0.0.5.
Very possible.. hope not.
I did get it back with the proper sbl, it worked. Nothing serious.
I didn't know you can flash an sbl from CWM before today, scary. I know how dangerous it is.
I've used One Click since July or so, it's always worked perfectly.
Well I really appreciate the help man. I am ordering a JIG already, just in case. Never thought I'd need one. I mean, I guess it isn't a big deal, not having a permanent 3 button combo.

Torch doesn't flash any bootloaders, it can't possibly kill 3-button recovery.

Haloruler64 said:
Thanks for the advice. I have a working one using the 3 button stock package at the moment. sbl is in the updates folder in the zip?
Click to expand...
Click to collapse
Usually, yes. If you're going to remove it from roms that have it, make sure you also remove the line that flashes it in the update script (META-INF/com/.../update-script)

ryude said:
Torch doesn't flash any bootloaders, it can't possibly kill 3-button recovery.
Click to expand...
Click to collapse
I know it doesn't, I checked for it. But I got into recovery to flash Torch, and after flashing it I couldn't gt into recovery anymore....

Haloruler64 said:
I know it doesn't, I checked for it. But I got into recovery to flash Torch, and after flashing it I couldn't gt into recovery anymore....
Click to expand...
Click to collapse
There are other ways your bootloader can get corrupted. I understand you're upset, but you shouldn't immediately place blame on my ROM.

ryude said:
There are other ways your bootloader can get corrupted. I understand you're upset, but you shouldn't immediately place blame on my ROM.
Click to expand...
Click to collapse
No, Torch wouldn't have done it. At least it's an easy fix.
CM7 Inspire 4G

ryude said:
There are other ways your bootloader can get corrupted. I understand you're upset, but you shouldn't immediately place blame on my ROM.
Click to expand...
Click to collapse
I didn't blame it, I simply provided info on the situation. I never said "don't use Torch."

flashing back & forth between gb & froyo

i just wanted this all in one place.i wanted my daily driver to be torch or fusion cause of call quality but also want to play around on gb roms.i found a safe way to go back and forth.if something happens to your phone i'm not responsible this is what works for me.
1.flash gb stock just like it says here:http://forum.xda-developers.com/showthread.php?t=1045734
2.i wanted mosaic on to play around with so i flashed mosaic.now from mosaic( I have only tried mosaic so far) you can flash back to 2.2 or 2.1 rom that has NO secondary bootloaders(this is very important).and you have to be on http://forum.xda-developers.com/showthread.php?t=1042543 the kernel from here in order for this to work cause it uses cwm 2.5 still.
3.make sure you wipe data/factory reset and also wipe cache partition and dalvik cache in between flashing roms.
4.if on talon kernel you cant flash from 2.3 to 2.2 cause it uses cwm 3.0.so you need to get kernel flasher from market and the this file http://etc.muteheadlight.net/android/I9000_reoriented_vG.1.1_novoo.tar and flash it from kernel flasher it will put you back on cwm 2.5 and you can go back to 2.2 from there.
this has worked for me several times today i wanted to make sure it worked go and thank all the devs on there respected paged.they work hard on all this development show some appreciation.
again dont mix boot loaders make sure the rom you are flashing does not flash boot loaders.just stay on gb boot loaders.as it is stated you will brick your phone mixing boot loaders.
I hope this helps some people out and explains it good enough.

I just use odin one click to flash back to stock then flash by froyo rom of choice.

To Gingerbread from 2.1 bootloaders:
odin flash bootloader and reorient kernel package HERE (7mb)
odin flash talon or other kernel with CWM3 built in
boot into CWM3
CWM3 flash GB wipe rom!
Back to Eclair/Froyo: (keeping GB booties)
Odin flash a Kernel with CWM2.5 built in (onix)
boot into CWM2
CWM2 flash 2.1 or 2.2 wipe rom.
------AVOID ROMS WITH SBL (secondary boot loader) LIKE A PLAGUE!!! or built-in 3 button fix!----- YOU WILL BRICK!!
****To not worry about mixing Bootloaders or the SBL on Eclair/Froyo roms flash odin-one-click to get stock booties before Odin flashing a Cwm2.5 kernel.
Easy Peasy Lemon Squeezy

i also use odin one-click to get back to stock

Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897

Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.

studacris said:
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
Click to expand...
Click to collapse
I'm on a mac I have a pc around but I swear if you saw it you'd be a little nervous to it's a cheap old lap top running xp it doesn't even have a battery, I'd be fine with odin if I had faith in my pc. That being said don't mention heimdall it doesn't recognize 2.1 bootloaders so in order to move up I still need odin.
Sent from my SAMSUNG-SGH-I897

heimdall doesnt recognize 2.1 bootloaders? really?
how was it created with 2.1 bootloaders before the 2.3 ones ever existed??
thats news to me.... learn somethin new every day...
*sarcasm*

This an interesting post from the guys that wrote heimdall the first is a list of confirmed devices that work with heimdall the eighth post is a list of confirmed working bootloaders and osx compatability i9000 this should give you an idea of what I'm talking about. Out of ten only two support osx. As far as the i897 is concerned if you ever flashed your phone with odin 1click and I have the boot loaders included do not support osx. THAT'D be a fact . *touchee*
Sent from my SAMSUNG-SGH-I897

Here's the linkhttp://forum.xda-developers.com/showthread.php?t=891518
Sent from my SAMSUNG-SGH-I897

1tontomato said:
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
no problems so far.just wipe everything and factory reset clear data in recovery the key there is to be in cwm2.5 and not 3.0. and to never flash anything with secondary bootloaders.

Hey if Im currently on a JVH ROM, and want to try out the Galaxy Sense i9000, but the whole deal about the bootloaders is a little irrating. And its even trickier for me to go back to stock considering I have a build 1010, thus One Click soft bricks my phone (*I have a jig*). But it really isnt a big deal because I use the JH2 method and iCezars method for flashing back without risk, without replacing the bootloaders. Those are the two methods I have had to flash back to stock while on a Gingerbread ROM.
But my question lies in whether I can flash back to stock using one of the two methods I stated above which DO NOT FLASH BOOTLOADERS and follow the instructions in the Sense i9000 thread (This isnt a how to, to flash, because from December--February all I did was flash MIUI and CM7), but rather do you know if I could flash with GB bootloaders or would it be too big of a mess?
And if I cant can someone point me into a direction of a .tar file that contains BOTH BOOTLOADERS such as Odin One Click but I have to use Odin 3 and manually put it in and flash.
Thanks!

Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.

studacris said:
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
Click to expand...
Click to collapse
Hmm.. I was seriously thinking that but I was worried that it would completely brick the phone because it does flash both bootloaders thus completely bricking the phone.
If I knew I could just Jig it back like ive had to do twice when I used Odin One Click Id use the JH2 package or Cezars and be good.
But since im playing with bootloaders Im worried that it will completely brick cause One Click doesnt even work on my phone.

it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders

studacris said:
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
Click to expand...
Click to collapse
yes I know that im not trying to argue you with you... hahah
Im just saying that I dont know Im just a little hesitant as I havent used Odin One Click in a while, plus the fact that it'll be twice the nerve racking coming from Gingerbread Bootloaders.
That is the one thing that is a little scary, but I know if anything flashes on to the screen im good to go, but just a little nervous, but am seriously considering just using the Odin One Click, and just praying that it at least flashes the AT&T screen then off like it normally does.
But I dont know if it'll work the same with GB, I know its mostly in my head but hahahaha
EDIT: I havent used One Click in a while should I wipe my phone before? And secondly I assume disabling lagfix?

FLASHED ONE CLICK.... Going now I will keep it posted when I get back to stock.
the bootloaders though flash went well so I think im in the clear. Lets hope : D
UPDATE: It soft bricked, Jig--> now on Stock.
THANKS SO MUCH!

No problem man.
TRUST THE ZOMBIE!!

Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?

Soccer_Dad said:
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Click to expand...
Click to collapse
please read post 3
i wrote it. i know its there..

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!

[Q] Something Wrong With New Captivates?

I just got a Samsung Captivate two days ago, and while trying to root it, I seem to have bricked it. When trying to flash initial root zip in stock recovery, the install always failed because it failed to verify the signature. Then I got the bright idea of ODIN one clicking back to stock, thinking maybe that'd help. Now, if the phone is unplugged, I get a boot loop with the white at&t screen, and if I try to plug it in to get into download mode, it just blinks the battery status screen, showing an empty battery. I tried replacing the battery with a fresh one, but no change. Any help would be greatly appreciated.

should have just ran a search for " captivate signature verification ".. million threads... and fix in my signature...
so you odin flashed to stock then flashed the root kernel?
or just flashed to stock? What stock? there are many. theres 3 odin packages and 4 one clicks just for ROGERS.. there are even more for att. some even ACTUALLY BRICK YOUR PHONE.
having the WRONG kernel for wrong rom causes bootloops.
you are not bricked. bricked your screen doesnt come on.
you really need to research.

Sounds like you flashed jf6 on a froyo shipped phone, losing your 3 button ability in the process.

shagdaddy said:
I just got a Samsung Captivate two days ago, and while trying to root it, I seem to have bricked it. When trying to flash initial root zip in stock recovery, the install always failed because it failed to verify the signature. Then I got the bright idea of ODIN one clicking back to stock, thinking maybe that'd help. Now, if the phone is unplugged, I get a boot loop with the white at&t screen, and if I try to plug it in to get into download mode, it just blinks the battery status screen, showing an empty battery. I tried replacing the battery with a fresh one, but no change. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Please, you have gotto give us a step-by-step on what you did.......especially on what you did !!!!

mrhaley30705 said:
Sounds like you flashed jf6 on a froyo shipped phone, losing your 3 button ability in the process.
Click to expand...
Click to collapse
we have a winner!!
op search usb download mode jig...easy to amke cheap to buy. it eill force dl mode and from there you can flash ANY other stock firmware than JF6...

One click root is much easier than whatever you tried doing
Sent from my SAMSUNG-SGH-I897 using XDA App

I did the same thing. You will have to get the USB jig to reflash it. Get the stock 2.2 ROM and use super one click. Odin can get you back the clock work mod.
Sent from my SGH-I897 using Tapatalk

studacris said:
we have a winner!!
op search usb download mode jig...easy to amke cheap to buy. it eill force dl mode and from there you can flash ANY other stock firmware than JF6...
Click to expand...
Click to collapse
I won! Ok, where's the bacon for winner?