Database Info

Flashing To 2.1(stock) from Cognition w/vodoo WILL CAUSE BRICK!

Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)

Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
thats funny. i have run every froyo rom available to us, i9000 w/voodo, ulf, cognition with voodoo, and i have yet to brick my phone. i flash to stock between EVERY new rom.
there is something you are not doing right. did you disable voodoo before attempting to flash stock?

Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I always flash back to JF6 via Odin 1 click before going to any new rom. It does not matter for whether voodoo is disabled or not because Odin 1 click repartitions everything to RFS. Also, the orange screen is not that big a deal. Reflashing JF6 via Odin once more is the solution.
If you continually have these problems when flashing to JF6:
1. Try re-downloading Odin 1 click.
2. Follow correct procedure for Odin flashing (Read OP's)
3. Try other USB ports
4. Uninstall and install fresh drivers that match your operating system (eg. 32bit/64bit)
Further, this post is not for the development section, but belongs in General or Q&A.

I think even without voodoo disabled, flashing back to stock will break voodoo and it wont be functional anymore. I personally never disable voodoo when flashing back to stock. You need to Master Clear after flashing back to stock.
Never bricked my phone flashing all the time.

I do it all the time! Never bricked my phone... EVER! The closest I came was when I tried flashing to another rom with CVM with voodoo still enabled. got stuck in loop, but to rectify the situation I "flashed back to stock with one click ODIN" and all was well.

i9000 is not the captivate argh different kernel

Odin gave me Blue, Light Blue, Orange, White and Black Screens of Death, no matters if i had Voodoo or not..
I think it sometimes hangs without any reason, but the drivers/program itself..
Thanks God my phone doesn't have the Bootloader's 3 Button issue..

Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
I believe he was referring to i9000 roms. I have never had any issues flashing back to stock from any rom. It has to be something you are doing. Might be the answer you want but probably going to be the most common answer you will get. Check your steps.

Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
i never said i am running an i9000 HARDWARE, i said ROMS
like everyone else has said. its something YOU are doing wrong. please dont spread FUD

This thread needs to be deleted. It's patently false.
Sent from my Captivate.

Sometimes its not the arrow....
its the Indian. The majority of the people who flash follow the same procedure with no issues. While its nice of you to try to caution folks, maybe you need to look at what you're doing instead of jumping to conclusions.

MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
Agreed 10char

MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
AGREED!
one person has problems with multiple devices=look for the common denominator.

if not deleted then at least OP change the title because its misleading.

i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?

Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I have flashed i9000 roms, kernels, modems, themes, and anyting else imaginable, with and without voodoo, with and without master clear, and have NEVER gotten the orange death screen before, during, or after Odin flashing back to stock. I've flashed just about every iteration of the Cognition FroYo roms and have never had an issue.
Re-download odin, maybe? But it's not an issue with Cognition.

Belaflek said:
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Click to expand...
Click to collapse
Yo only need to disable voodoo when you are upgrading from one version to another but when you are flashing back to stock it will repartition everything for you back to RFS.

I've run all the Froyo kernels, ROMs, even i9000 Froyo ROMs on the Froyo reoriented kernel, with or without voodoo, it doesn't matter, and I flash back to stock all the time. Odin wipes everything out, it doesn't matter what you are running.

the "factoryfs.rfs" screen-o-death is a well known problem. fortunately, factoryfs.rfs doesn't really matter (it's only the /system partition), your phone just won't boot. Likely you'll hit the phone--!--PC screen, but as long as you have 3 button recovery working, you're safe.
this issue crops up when you have a bad USB connection to your phone. I'm willing to bet 90% of the people with this problem are running outdated hardware (made before 2006 or so) that can't keep up with ODIN's pace or are using a desktop and not plugging the USB into a port connected to the motherboard (you should be using one on the back of the tower)

MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
posts like this... littering the dev forum

[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."

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...

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..

Back to stock UCLB3..now what?

So, I decided to root my Infuse..and load 4.x.x . Rooting was no problem. Following the order I next went to ICS...got the boot logo freeze, but also got the Froyo boot loader rainbow crap... So, I used Heimdall One-click and went back to UCLB3 stock...with out Root..wth?
I also lost USB connection when booted...in download mode the device is discovered....but it recently dawned on me Debugging was turned off. oops. hope that is the ONLY problem.
So, how do I flash the UCLB3 with CW and Root (ENTROPY512's 4.4.2012 kernel?)...use the Odin Tool or can I use the Heimdall One-Click tool? I'm thinking the Heimdall is a No.
Thanks. my other Android devices were so much easier to root and flash custom to. LOL

Just ignore this dribble....I see that Heimdall has a front end for flashing....will be back if I F it up a bit later.

ok then, a complete wiping of all Samsung drivers reboot and re-install of the non-kies (http://forum.xda-developers.com/showthread.php?t=1655286 and Odin was able to connect to my phone in Download mode.
Flashed the new rom (I997UCLB3-CWM-root-deodex-extras.rar), already had GB boot loader so I "should" be good to go for ICS and then JB and beyond.

OK, Now I'm not finding any more information. I've installed ICS via Entropy's CM9 and have ICS running. When I go to install a JB rom I get 'An incompatible partition layout' error. forcing the issue leaves me stuck at the splash screen. End up having to go all the way back to stock UCLB3 because I end up with a ton of mount errors.
Am I missing a step...the same step 3 times??
Thanks.
Edit.....never mind...tried a different 4.3 rom...got same partition error..did it anyway, installed correct gapps...up and running. *whew*

gtFlue said:
OK, Now I'm not finding any more information. I've installed ICS via Entropy's CM9 and have ICS running. When I go to install a JB rom I get 'An incompatible partition layout' error. forcing the issue leaves me stuck at the splash screen. End up having to go all the way back to stock UCLB3 because I end up with a ton of mount errors.
Am I missing a step...the same step 3 times??
Thanks.
Edit.....never mind...tried a different 4.3 rom...got same partition error..did it anyway, installed correct gapps...up and running. *whew*
Click to expand...
Click to collapse
discovery..
btw..re: heimdall one click...the insecure kernel is on the second post of the thread. if you read the OP..the original intent is to return to complete stock

Thanks qkster...i knew there was a Heimdall one-click that already had cwm and root, but in my haste (in between functions at work) I couldn't find it. I'll have to look again, although I have 4.3 running now, so prob will never (never say never, right?) need to go all the way back the the stock stone age.

gtFlue said:
Thanks qkster...i knew there was a Heimdall one-click that already had cwm and root, but in my haste (in between functions at work) I couldn't find it. I'll have to look again, although I have 4.3 running now, so prob will never (never say never, right?) need to go all the way back the the stock stone age.
Click to expand...
Click to collapse
Odin or Heimdall...Either works. I think it depends on personal preference.
Here is the rooted 1 click
http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
Gl

ah yes, I remember that post in my headless chicken state.
Is it my imagination, or did 4.3 drop the audio (music player) from both front and back speakers to just back speaker? Could have sworn pandora in ICS (and 2.3.6) had sound coming from both speakers....

gtFlue said:
ah yes, I remember that post in my headless chicken state.
Is it my imagination, or did 4.3 drop the audio (music player) from both front and back speakers to just back speaker? Could have sworn pandora in ICS (and 2.3.6) had sound coming from both speakers....
Click to expand...
Click to collapse
You prolly have to check with 4.3 thread. On the infuse, I prefer gb.