yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] Danh2009:
although im relatively new to the SGS scene i have already done my fair share of flashing.

I have found that there are 3 roms i regulary have been swapping between.

Simply Honey

Juwe's Smart Edition

Tweaky Rom

they are all fast and stable roms.

I have tried and tested Darky's Rom enjoyed it but I haven't re-visited it recently.

MIUI is a very very nice sleek interface, but the battery didn't seem to last very well with me.

Same with CM7 nice clean OS but the battery was an issue (and I used to swear by CM on my old G1, I will revisit when the battery is sorted).

My first SGS flashing experience was Simply Honey and I had no problems with it at all.

at the end of the day, in my opinion, every one has their favourite flavour from their favourite chef. I suggest you try them all at least once until you find your favourite.

(just flashed the latest Juwe's and so far its impressive)
[Captivate Android Development] Cezar`:
Hi guys.

I extracted the bootloaders and param.lfs from the latest AT&T Firmware, I897UCKF1 and created an OneClick ODIN package.

Flashing bootloaders is a dangerous deal but you take the same risk every single time you go back to stock using OdinOne CLick.

However, if you decide to go ahead with this method, you do it at your own risk.

I tested the package 3 times on my phone so it should be safe.

Now, you might ask why would you update the bootloaders again?

Mainly because I9000 bootloaders are not designed for I897. We've seen that there are a several differences between I897 and I9000 so is not hard to believe that having I9000 bootloaders might impact stability and even performance.

WARNING! Make sure you have a stable USB connection between your computer and your phone!

I really cant tell you how to check that, but is THE MOST IMPORTANT prerequisite.

WARNING! Key combos after flashing the bootloaders will be the same as in Froyo:

Vol UP + Vol Down + Power = Recovery

Vol UP + Vol Down + USB insert = Download

WARNING! If you have troubles connecting the phone to PC, download samsung Kies and install it to get the latest samsung drivers but make sure is not running while flashing the bootloaders.

Cyanogen MOD users, stay away!

The steps which you will need to take are as follows:

Download the package from here

Extract OneClickI897UCKF1-bootloaders.exe

Restart the phone in Download Mode

Run OneClickI897UCKF1-bootloaders.exe - with administrator permissions if on Windows 7 or Vista!

Connect the USB cable to the PC and the phone

Click "Start"

The phone will reboot by itself and you should see the ATT boot logo.

Good Luck!

Note: ANY version of Android should work with these bootloaders.

Note: Some users reported that after flashing the package, the ATT logo didnt appear but some black screen with colored points. If that happens, flash the package again.
[Captivate Android Development] Shammyh:
First off, thanks for creating the One-Click package!

Did you do it with the new tool in the most recent Gingerbread leak?

Also, has anyone noticed any appreciable differences between the Captivate and i9000 bootloaders? I think it's fair to assume there must be some difference...
[Captivate Android Development] RockRatt:
So after doing this will the roms like Apex 7 work with these bootloaders? Seems like that is what your are saying since any android version should work. Or will it not since it would be different framework or something? I have been on the i9000 gingers Continuum and the Apex along with the first gingerbread. I really liked Apex 2.3.4 and would be nice to have the ATT Captivate Gingerbread yet be able to use Apex. Then if this is the case we would then lose the advantage of having the awesome call quality of the audiance chip since we would have a i9000 based kernel and i897 modem. Just trying to clarify here. Thanks for your time and work.

PS. I am on DGs 1click gingerbread right now.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Koizuma:
Sweet awesome work
[Captivate Android Development] RockRatt:
As I stated above I have been using the i9000 gingerbread roms and now trying DGs 1click and one major noticeable difference in my opinion was how CLEAR and LOUD the calls are. I guess being on i9000 froyo and Ginger roms I never really realized how much the audience chip made call sounds so much better. The downfall is no hsupa+ speeds but it did not seem too bad as I get about 2-2.5 download but only 500-1.0 upload with it. As far as smoothness and reliability I would almost say pretty damn equal.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Shammyh:
Just FYI, this just *almost* hard bricked my phone.

One-Click packaged crashed while downloading "boot.bin" aka Primary Bootloader. Got the wonderful ol' "Phone ! PC" symbol.

Also of note, vol down + vol up + usb DID NOT bring be back to Download mode, like it would normally have down with any i9000 or i897 PBL and SBL combo. Luckily Vol Down + Power did bring me back to Download, and I'm back up and running. In fact, I believe that's the first time ever that I've recovered a soft-brick without using vol up / down + usb. Very odd. Just counting my lucky stars that I had a crash while using ODIN to flash "boot.bin" and I'm still alive to talk about it. :)

Edit: Glad to hear it's working for others, but I've NEVER had an Odin flash crash on it's own before. Makes me a little suspicious something is not right.
[Captivate Android Development] Reynaldinho111:
Just flashed over Apex 7.1 and it worked perfectly. Feels good to have the old three button combo back :P Thanks Cezar!
[Captivate Android Development] xpakage:
What ROM are you running? I just flashed over COG 5b with no problems.

DG thought the boot sound had been removed but it was still there. Now it is gone as planned by DG.
[Captivate Android Development] Shammyh:
That however is due to Modem + Kernel + ROM. Not bootloader.
[Captivate Android Development] Shammyh:
Was running Continuum 5.6 v/ Talon Test build and Voodoo Lagfix enabled.

It's possible it was just a fluke, but after hundreds of Odin flashes off of my archived One-Click copies, I just find it unlikely. Then again, we humans due have a bias to find causality in not nessecarily related events...
[Captivate Android Development] mrhaley30705:
Your flash didn't take. Thats the i9000 loader combo for dl mode. Also, I flashed this twice and had no problems. A lot people flashed this with no problem.
[Captivate Android Development] Shammyh:
I'm aware of the button combos. Yet if the "flash didn't take", why would it boot to the "Phone ! PC" screen?

Well, if it works for everyone else, it must have been a fluke. No other way around it.
[Captivate Android Development] mrhaley30705:
Cog 5 is KF1 based, right? Same bootloaders, different rom.
[Captivate Android Development] mrhaley30705:
Your data cable may be going bad.
[Captivate Android Development] Cezar`:
I am not sure why would you have this problem. Did you take in consideration the possibility of having corrupted /lfs previously? If this flash would fail, then your phone would be totally dead right now
[Captivate Android Development] Shammyh:
I was asking for practical differences between the i9000 and i897 bootloaders. The poster referenced call quality/sound and attributed it (perhaps by inference) to the different bootloaders.

I was simply pointing out that the Audience chip working or not depends on the ROM/Kernel/Modem pairing, not the bootloaders.

Boot goes vaguely like this:

iROM -> PBL "boot.bin" -> SBL "sbl.bin" -> Kernel -> Android.

The audience chip support doesn't really come into play until the kernel.
[Captivate Android Development] Shammyh:
Don't see why, considering if the params were corrupted I probably wouldn't even see the boot logo image during PBL/SBL booting. And yes, I found it odd as well, seeing as a boot.bin fail should result in a "hard" brick.

Eh, just tried it again after a fresh flash and it worked. So who knows? I'm happy to just chalk it up to gremlins and move on.
[Captivate Android Development] Cezar`:
Bootloaders have nothing to do with framework so you may run any rom after flashing this pack.

And to answer your other questions, I am not sure what you mean by having the the captivate gingerbread and being able to use a custom rom. I guess the only way to have a captivate gingerbread and the rom which you prefer is that rom to be build from a Captivate GB.

I am not sure how awesome is the call quality on captivate original roms compared to i9000 ones but i wouldn't trade some assumed better voice quality on HSUPA. This is not only a phone after all. Most of us use it less than 20% for calls and more than 70% for browsing and playing
[Captivate Android Development] xpakage:
Probably Leprechauns, Gremlins would have done a lot more damage :D:D
[Captivate Android Development] RockRatt:
I guess what I was trying to ask is kind of answered already but was trying to confirm that as long as we have these captivate TB loaders installed we CAN STILL run apex with it and not have issues with weird colors upon boot like you see when someone came from a 2.2 rom and did not flash the i9000 bootloaders. I also was not trying to say anything about the bootloaders affecting the sound quality. I know it is a trade off between the hsupa speed or call quality. I would be awesome if we could have both but I know that wont happen. Was just trying to comment on one or the other as far as pros and cons of each.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] malbolgias:
thanks mrhaley30705

Just flashed the boot loaders with heimdall, worked perfectly. Held my breath hit flash and all went well.
[Captivate Android Development] mrhaley30705:
No problem. Glad it helped you out.
[Captivate Android Development] sunfirex:
I am experiencing the same thing w/ 100% reproduction. I've also noticed my battery no longer charges what started out at 80%, went to 60%, now it's at 16%. Meaning, it will not charge past the numbers indicated above and 16% is the highest charge it will take. USB cable is fine as it registers a USB device connected and am able to transfer files back and fourth from the phone-pc.

I woke up today after my phone and I've been charging for the past 7.5 hours I pulled the plug out and the battery instantly dropped to 56% from 100% (when it was plugged in). Not sure if this is attributed to the phone not registering the charge? I've downloaded a few battery apps just to be sure, and they all register the same with the same percentages. Battery status is Good. Have never had issues with my battery.

I'm currently running Apex 7.2 on Talon Kernel 0.3.1

Will have to go back to I9000 GB BL.

Other than those issues everything seemed to run fine. No call/txt/3g issues everything was clear. The music issue is a big deal for me as well as this battery issue.

Not sure if the issue is necessarily related to these bootloaders, but it's the only change I've made to the phone in a couple weeks.

Will have to see.

It was fine the first few days I used it. Am in the process of switching back.
[Captivate Android Development] mrhaley30705:
It is recommended by Watsaa to use I9000 bootloaders on Apex 7.3.
[Captivate Android Development] mrhaley30705:
That is called the charging bug. My personal opinion is that a calibrated battery lessens the drop when unplugging.
[Captivate Android Development] Cezar`:
Pool added. Who ever used this, please vote. If you vote no, leave a comment with the result (bricked/not bricked)
[Captivate Android Development] TorqueWrench001:
Just used this on two of my four captivates. Worked perfectly on both.
[Captivate Android Development] mrhaley30705:
Poll Message

It worked for me< but the first time It left the boot splash as garbage. Reflashed and no problem since.

Also, I used Cezars 1 click.
[Captivate Android Development] RonH54:
I have been using i9000 BLs with No problem until I tried to Flash a new Captivate ROM today and got "Stuck". I have presently Flashed back to a Captivate Version of a i9000 ROM(Ficeto's JVP). If I do decide to go to Captivate a BLs I can just Flash the .tar file with Odin and should have no problem...Correct? Or do I need to be in Stock Captivate?
[Captivate Android Development] mrhaley30705:
It doesn't matter what ROM you are running when you flash the bootloaders. I was running Continuum 5.6 when I flashed them.
[Captivate Android Development] RonH54:
So Captivate GB Bootloaders will Flash over i9000 GB Bootloaders with No Problems then?

Thanks
[Captivate Android Development] mrhaley30705:
shouldn't be a problem, barring human error. Human error would include using a bad cable to flash bootloaders, unplugging your phone from the computer in process, power failure (why I use a laptop with a fully charged battery to flash loaders), anything that would interrupt the process (ie battery falling out of the phone). Please reread the the op for this, Cezar runs down the risks and preventative measures better than I do. Just remember the number one rule of flashing:

You flash at your own risk.
[Captivate Android Development] RonH54:
Thanks for the reply and I understand the risks that the reason I have a JIG...:D. Flashing ROMs and various other ROM related things don't bother me but Bootloaders scare me somewhat.
[Captivate Android Development] mrhaley30705:
As they should. But with proper precautions, its not that bad.
[Captivate Android Development] RonH54:
I have Flashed Bootloaders once when I went from the old Captivate ones to the new GB ones that came out for i9000 so it just a matter of me wanting to "roll the dice" again changing from i9000 to i897.
[Captivate Android Development] Srikar_NBK:
Sorry for my question, I'm sure it might have been answered already, but I'm unable to find it in this sea of information.I have read through lots of other threads, but they only increased my confusion.

I want to return my Captivate to AT&T as its having major GPS locking issues. I'm currently running Mosaic V on the GB boot loaders from the OP. The phone came with Froyo, so I want to go back to Froyo stock before returning to AT&T. Any ideas how I can do it ?
[Captivate Android Development] Shammyh:
Wrong thread. SEARCH for the answer to this question.
[Captivate Android Development] golfslicer:
These work great, shouldn't it be posted on the main page with the one click so it is easier to find.
[Captivate Android Development] RonH54:
"For those not wanting to use the one click, here you go.

Heimdall users should use this download.

Full Odin users should use this download.

**Odin users: Place the pda file in the pda slot. DO NOT put it in the bootloader slot."

Concerning the Odin Flash should the "Re-Partition" be left UNCHECKED when Flash these Bootloaders?
[Captivate Android Development] mrhaley30705:
Repartition should be unchecked. I didn't include a pit file.
[Captivate Android Development] Pf.ozer:
can i use these bootloaders with JVQ based roms?

read all those post and didnt understand,what do i gain if i change my bootloaders to these?
[Captivate Android Development] mrhaley30705:
So far, you can use these bootloaders with any rom that doesn't include a secondary (Sbl.bin) bootloader by itself. You should also NEVER use the 3 button fix that is floating around here after flashing these bootloaders.

As for pro's and con's, all I can tell you is read the op and decide for yourself.
[Captivate Android Development] tbong777:
The APEX ROm developer is recommending i9000 GB bootloaders for i9000 ROMS and incudes a flashing package for such...

So really two i9000 developers....... opposing views....

Maybe a detailed explanation by either developer might shine some light on why or why not certain bootloaders should or should not be used, or what about the handset makes certain bootloaders preferable. Because now if you want to flash Apex and follow the developer's instructions you need to flash i9000 bootloaders

If you prefer Continuum i897 are the chosen ones....

Is it all speculation or does it really make a difference which bootloaders reside in the Captivate.
[Captivate Android Development] Kyuta Syuko:
As far as I can tell it's all speculation. Team Phoenix also suggests I9000 bootloaders with I9000 ROMs, but so far I haven't noticed much of a difference with the exception of the already stated differences.
[Captivate Android Development] Jay_eS_Iye:
So I used this from stock JF6 and the install failed and now my phone will only go to the phone!pc logo. Unfortunately I'm deployed and don't have my jig with me, any other way I can unscrew my phone?
[Captivate Android Development] mrhaley30705:
It says firmware failure, our something like that? Treat that like dl mode and odin flash from there.
[Captivate Android Development] Jay_eS_Iye:
It doesn't say anything, it just comes to the screen with the phone logo, ! logo, and computer logo. When I try to put it into download mode it goes back to that screen.

(thanks for helping again, my download for the KF1 1-Click is still going on so I tried this method instead... friggin Iraqi satellite connection)
[Captivate Android Development] mrhaley30705:
If you have new gb bootloaders, here are the new button combos.

GB button combo

Vol up and power = recovery

Vol down and power = download

Alternate download

Pull battery, wait about 10 seconds. Reinsert battery. Hold volume down, then plug in usb. Should bring you to dl mode.
[Captivate Android Development] Jay_eS_Iye:
I've tried vol+/vol-/usb, vol-/usb, vol-/power, vol+/vol-/power, vol+/power, nothing gets me past this brick screen. It failed during the GB bootloader ODIN, I was coming from JF6 bootloaders (fresh JF6 1-Click). The only thing I can think that may screw me is that I have one of the Captivates that needs the 3 button fix, so maybe it won't go into download mode because of that
[Captivate Android Development] mrhaley30705:
Have you tried plugging into odin to see if it recognizes it? Also, have you tried adb? Its fairly easy to use. Dl the adb interface from my sig, then follow the directions in the read me file. Command for download mode is "adb reboot download"
[Captivate Android Development] Jay_eS_Iye:
Odin doesn't recognize it and ADB comes up with "error: device not found". I don't get the Windows usb chime when I plug it in so it's not recognizing it when in this brick mode. I'm thinking I may have to try and find some resistors over here and make another JIG but I'm hoping there's another solution
[Captivate Android Development] mrhaley30705:
That is what its looking like. You may have I hope. Check deeper in the Development section for 1 click UnBrick by Adam Outler. If that doesn't help you, start looking for resistors.

FWIW, I just tried dl mode form powered off (vol down+power) and it only took about 3 seconds to get dl mode. Good luck, and thanks for your service.
[Captivate Android Development] Jay_eS_Iye:
yeah I've been trying his program while doing this, hoping something will spark, but it's just not recognizing the phone. Well once I get this fixed and get the GB bootloaders back on I don't see myself going back to JF6 for any reason again. Thanks for your help

Oh and when I try putting it into download mode I get the phone<--!-->pc within about a second... blah, great way to start the morning
[Captivate Android Development] aintwaven:
I know you don't want to hear this, but keep trying different button combos and different usb cord. I had the same thing and got it back into dl mode, don't give up. Thank you for your service, we owe you.
[Captivate Android Development] stewi21:
so im not the only one..everytime i try and flash the cappy gb bootloaders from this package, or included in the stock kf1 ROM, i just end up with a soft brick, so im stuck on the i9000 bootloaders (maybe they'll work for you too if ur trying to go to gb). anyhoo as for unbricking check out this page, i find method no. 3 usually works for me :) http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode

@Cezar, any idea why this problem is occurring?
[Captivate Android Development] mrhaley30705:
Did you reboot your computer before flashing? Use usb port on back of the computer(#1 on a laptop)?
[Captivate Android Development] mrhaley30705:
Those having problems flashing the bootloaders, did you flash the one click from the op, out the packages I posted in the thread?

Also, what are the build dates on your phone?
[Captivate Android Development] Jay_eS_Iye:
I used the one from the OP, build date is 10/08

Ordered a JIG, pretty much said the heck with it, so guess I'll be back online in a week or so
[Captivate Android Development] b0uncyfr0:
Hi guys i just thought id fire up these bootloaders on MIUI hoping for more smoothness/snapyness. One guy got it working on 1.6.? , an old version.

Bootloaders were installed fine, i installed latest miui (1.7.15) and installed latest glitch kernel but it keeps taking me to recovery everytime i reboot.

Is there anything i can try to get it booting right?
[Captivate Android Development] mrhaley30705:
Not sure if that would be a loaders issue or a kernel issue. I've never used mini or cm7, but I know they have their own set of rules concerning a lot of things.
[Captivate Android Development] b0uncyfr0:
Its alrght, i got it working. I started again and installed the bootloaders first. Everything seems ok so far.
[Captivate Android Development] Palmetto_X:
Now that I have this, now what can I do?

I do not notice a difference in my boot screen, should I see something?

BTW, Thanks for you work here on XDA
[Captivate Android Development] mrhaley30705:
Unless you were using I9000 GB loaders before, you won't see a difference. The new ones use c the same att world phone boot splash. If you were using i9000 loaders and you still have the i9000 boot splash, something didn't work.
[Captivate Android Development] stewi21:
i have tried both usb ports on my lappy, rebooted tried again, still no avail. i used this package every time. my phones build is 1007. oh and its also worth mentioning that i previously had the att gb bootloaders from this thread running on my phone, before i decided to flash miui.
[Captivate Android Development] mrhaley30705:
Try flashing DGs one click to jf6 stock before flashing the gb bootloaders. Also, when you do flash the gb bootloaders, try the full odin version I posted a few pages back.
[Captivate Android Development] stewi21:
tried that too, right after i recovered my brick haha. okay hopefully it'll work! (: thanks!
[Captivate Android Development] stewi21:
okay, reporting back...and it WORKED :D thanks heaps (: dont understand why the oneclick package failed |:
[Captivate Android Development] chvybeatsford:
How would i know it worked. Stills says I900 when booting up.?
[Captivate Android Development] mrhaley30705:
Which part of boot up says it? Boot splash, kernel splash, or boot animation? Some kernels use the i9000 animation as the kernel splash. The boot splash should be the att world phone screen. You can also check your button combos.
[Captivate Android Development] chappatti:
MMMM...i dont get this. After being through 5-6 soft bricks, i dont get why this would be the new download mode. I mean with odin1.8 (NOTE VER #) it never saw the phone as connected and so would not flash anything. One clickflash GB odin alsodoes not want to see the phone. My windows 7 also refuses to acknowledge that the device is connected and adb says no device.

I AM NOT DISSING THE OP. It is that i an obssesive flasher and if the above is true I would be even more brave in the future.

My phone is running OK, but this is for future ref.

So if anyone can enlighten me will much appreciate it. :confused:
[Captivate Android Development] mrhaley30705:
I have experienced the new phone-!-computer, which also says firmware upgrade failed and something about recovery. It was recognized by odin, same as dl mode. Why? I don't know, but it did. It had been noticed that after changing bootloaders some people have had to reinstall drivers, fwiw.
[Captivate Android Development] chappatti:
Thanks, MrHaley. I'll keep on the lookout at my next soft brick, which I can feel will happen soon !!!!!!! :p:p:p