yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] jferg5:
For everybody out there asking why. I flashed my wifes phone to gb recently, but I put these boot loaders on her phone first. I only flashed the kernel and then the rom, no wiping or back to stock, and she has had no problems and I believe it is because of the universal boot loaders. She was on andromeda 3. it made the process so much easier with something "made for this phone."
[Captivate Android Development] smali26:
FLASHED THIS COMING FROM STOCK AND IT GAVE ME THE PHONE + COMPUTER ICON AND WILL NOT GO INTO DOWNLOAD MODE.

I HAVE TRIED ALL POSSIBLE BUTTON COMBO.

1. TRIED STARTING ODIN, REMOVE BATTERY, AND UNPLUG USB. HELD UP+DOWN AND POWER AND PLUG IN USB WAITED FOR THE SCREEN TO GO BLANK AND RELEASE POWER DID NOT WORK

2. TRIED HOLDING DOWN VOL UP+DOWN AND PLUG IN USB NO LUCK

3. TREID HOLDING DOWN VOL DOWN AND POWER AND PLUG IN USB NO LUCK.

4. I HAVE TRIED ALL THE DIFFERENT COMBOS I FOUND FOR ABOUT A HUNDRED TIMES AND STILL NO LUCK.

5. SO I JUST BOUGHT A JIG AND I HOPE IT WILL WORK.

:confused:
[Captivate Android Development] mrhaley30705:
with odin opened, plug your phone in from the computer-!-screen. Don't worry if it didn't show a com port. Hit start. See if it flashes from there.

Some people have said that they have had successful odin flashes from that screen.
[Captivate Android Development] bigbadwolf311:
I had the phone comp screen on my phone awhile ago. I odin one click back to stock from it. It may take a few times but it works. I just hooked up my phone to my comp and saw that odin read my phone and flashed back to stock
[Captivate Android Development] bigblue95z:
Flashed over Serendipity7, on reboot it went into clockwork. I thought.... oh, this must be normal. Hit reboot system and bootloop city. Did a battery pull and was back to normal. Just a heads up for anyone who runs into this.
[Captivate Android Development] dc5ftw:
mine went to clockworkmod and i just hit reboot and it got like 5 secs of boot loop then it was normal lol.
[Captivate Android Development] johan8:
Bootloader does not contain boot splash!

It is in param.lfs

They are seperate things.

In fact there are two Boot splash.

The first one from param.lfs

The second one from the kernel.

But none of these related to the bootloader.
[Captivate Android Development] mrhaley30705:
Boot splash> kernel splash> boot animation. Thats the start up order. Yes, the boot splash is in the param.lfs file, not boot.bin (primary bootloader) or sbl.bin (secondary bootloader). But using this 1 click flashes all 3 files. As for relation to loaders, it is better to flash with it. Odin sometimes over writes the param.lfs file even when not flashing that file, causing a boot loop.

Yes, the kernel splash is cooked into the kernel (but its not called boot splash, simply got clarity).
[Captivate Android Development] evrionis:
I am on mosaic/talon, with the i9000 bootloaders. There are some folkd saying having these bootloaders give you some better responses.

Do I use this iclick odin download on top of mosaic? or do I have to go back to the stock GB, etc...
[Captivate Android Development] -Perp-:
You can run it on top of any rom. No need to go back to stock
[Captivate Android Development] TomMelee:
Trying to update over most recent Continuum before 6, so maybe 5.6? Odin saw the phone, I pressed start, I've been at "Setup Connection" now for ~12 minutes. Afraid to unplug or do anything. Suggestions?

EDIT: Holy crap I'm an idiot. I forgot I just reinstalled windows a couple weeks ago after dropping an SSD into this sytem...I've never setup the drivers again! I pulled the cable and restarted, all is well. Going to try again. Freaking noob.
[Captivate Android Development] rkkaranrk:
Just flashed this over Serendipity VII without any problem :)
[Captivate Android Development] Shammyh:
Just to confirm, there is still not a single actual verified/replicated report of ANY difference at all in using these bootloaders?

Call me old-fashioned, but this seems like a whole lot of people flashing something under the assumption that "because it says AT&T and came with a leaked non-official Gingerbread ROM it must be better for my device".

We don't have the bootloader sources, we don't know how/when/what/why Samsung designed this stuff. We don't even know if there's any difference from the i9000 loaders except for the splash screen and button combos. Occam's Razor. Why assume there are more changes than we can see? Especially without any evidence suggesting that to be the case?

Personally, I prefer the i9000 button-combo, and the i9000 splash. Since I'm running an i9000 ROM, i9000 Kernel, and an i9000 modem, I might as well stick with my i9000 bootloader and call it a day. No?
[Captivate Android Development] tkjeeper:
No, that is inaccurate. Check out my comments on page 18 of the continuum v6 thread. I explain the"night and day" difference I noticed using the i897 bootloaders as compared to the i9000. I just thought.my phone didn't like talon or ext4/lagfix, not so.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] Shammyh:
Just read your comments. The problems you were having were not normal, and indicated either a bad flash, or a filesystem corruption. And since I have not seen any other users comment on having the same problem, and finding a bootloader flash to be the solution, I'm going to have to assume it was something else going on.

I've used hundreds of ROM revisions, and every one of the major filesystems (including JFS and EXT 2), and whenever there was a problem with "applications taking 7-8 seconds to open" it was a bad flash, or filesystem problem. Without digging through your logs, or replicating the problem, it's really hard to chalk the difference up to the bootloaders. Especially when from a technical standpoint, they have very little to do with the filesystem/rom you are running.

Further, not all phones play nicely with custom kernels and EXT4. Many folks have found at various points in time that "X Kernel just doesn't work well for me". I have a Revision 1007 Captivate, and personally never had a problem with anything, but that's just my phone. Luck of the draw I guess. Still doesn't mean that a having a different bootloader fixed your problems. Perhaps even simply the act of putting your phone into download mode and flashing anything could have helped. Who knows. But again, the bootloader is a VERY low level piece of software, and it's dangerous to assume that it's responsible for things it's not.
[Captivate Android Development] Cezar`:
You must remember the main reason why bootloaders were upgraded in the first place, because of the graphical issues between GB drivers/kernels and the old bootloaders. I tend to believe that the bootloaders are not JUST bootloaders but a form of a Basic Input/Output System which matter not only when you start up the device but when you operate it as well.

To be honest, the first reason why I made this package is because I flashed these bootloaders and my phone stopped turning 50-60 degrees Celsius (122-140 F) while charging or playing a game.

The dev community is trying to eliminate all sources of troubles so is only logical that we will turn to original i897 software, bootloaders, in this case.
[Captivate Android Development] cbasse:
So, in the last couple of days I've successfully tried out a couple of ROMs (Continuum 6 RC1 and Apex 7.2). I've made backups through Recovery of each, so I could switch from one to the other without too much difficulty if I found I didn't like one for some reason...

Anyhow, today I decided to load the i897 bootloaders, followed iCezar's instructions and successfully (i think) loaded the bootloaders. After that, I decided I wanted to restore one of my ROM backups through Recovery. Well, when I go to CWM recovery and try to restore my file, it gives me a "No Files Found" message and just reverts to the main menu. I know I'm using the correct version of CWM (I'm using the same version as the one I created the backup in), and I've never had a problem doing this before (probably done it twice now with no issues). So, the only difference I can point to is the i897 bootloaders.

I've made sure the file hasn't somehow been erased, and tried installing a zip from the sd card just to be sure that CWM was functioning properly in that respect - no issues.

Any ideas on how to fix this so I can restore my backup? Anyone else experienced this?

Thanks for any help!

EDIT: Never mind...silly me didn't realize that I couldn't move my clockwork mod backup files to the external sd card. Had to move them back to their original folder on the sd card and...good to go! Sorry for crying wolf!
[Captivate Android Development] Shammyh:
It's just that I see so many threads around here full of snakeoil fixes and patches, that it scares me a bit what n00bs might do to their phones without being full informed. To be clear, I have no problem with people doing whatever they want to their phones. Lord knows, I bought mine with the express purpose of tinkering with it. But informed risky decisions aren't the same as uninformed risky decisions. Heck, even the "one-click maker" app is relatively untested, and I doubt is as stable as using ODIN yourself.

And yes, it certainly follows that a PBL/SBL package designed for the Captivate should function better than one designed for the i9000. However, as we've seen in every "official" release of software for our Captivates, "official" isn't necessarily better than modified i9000. Take for example "official" 2.2 vs i9000 2.2.1. It appears that the dev team for our phones lags behind the international dev team. Or as with Gingerbread, the release of "official" 2.3.3 vs already working 2.3.4 builds for the i9000.

My only point in playing devil's advocate here is to try to get some more hard evidence of what's different/improved in running this SBL/PBL pair over the i9000 PBL/SBL pair. While I imagine the PBL is identical, or nearly so, it does stand to reason the SBL (responsible for download mode, and ODIN support) might have some sort of impact in the functioning of the phone. Your right that there were some glitches running Gingerbread on top of 2.2 loaders, but that's not to say it didn't work. In fact, it DID work, but with garbage output at boot, and some other "quirks".

Normally, I'd say "flash it and find out". But since this is one of the few and only operations that can actually brick a Captivate, I'm just advocating for a little extra caution.
[Captivate Android Development] tkjeeper:
I can appreciate your concerns, I just assumed 2+2=4. The change for me was immediate and drastic. I can't explain anything other than that. I had lag with apex, and continuum on ext4, then I didn't. I'm on mosaic V now with ext4 and no lag here either, although on the i9000 bootloaders. Every phone is different I guess.
[Captivate Android Development] Endoran:
Now this is the first post with actual benefits listed to using the at&t boatloaders. I'm still not convinced tho, mainly because not even you, cezar, can say *why* the bootloaders have added those benefits (and since you're the op your opinion is biased). I just don't see the bootloaders doing all that behind the scenes. Maybe other ppl confirm?

Sent from my SGH-I897
[Captivate Android Development] Ben74:
the third time was literally the charm for me. i flashed these bootloaders the first time, got the phone to PC screen, used my jig to get to download mode, flashed back to stock with odin one click, and repeated three times. i was finally able to flash them successfully and install continuum 6. just had to be persistent :)
[Captivate Android Development] devoured321:
Ok...how can you tell if they flashed besides the boot screen...i flashed then twice..both times odin said completed...and succeeded....but I still have the gti9000 screen and not the i897

Btw I'm running mosaic iv with xcals 1.2 noovoo and no bln...with montage theme...not sure if any of that matters
[Captivate Android Development] VFO:
If you have the at&t initial boot screen then you have the KF1 bootloaders. The next screen you get is the Kernel boot screen. I am not sure if Existz uses the I9000 screen for his 1.2 kernel. The next screen you get is your boot animation. So If the first thing you see is the at&t world phone screen then the bootloaders flashed ok.
[Captivate Android Development] devoured321:
Thank you for the quick response....thats how mine is so sure enough it flashed ok
[Captivate Android Development] smali26:
thanks. Mr.Haley.

i gave that try no luck

i received the Jig and got it into Download Mode now Windows 7 does not recognize the USB device (captivate). i reinstalled the captivate drivers and no luck.

Weird.....

anyone have any suggestions. i am willing to try anything at this point.

PS. i am not new to this and i have been flashing on the vibrant, the Galaxy tab, the epic and the captivate regularly.
[Captivate Android Development] mrhaley30705:
Have you tried installing the drivers that come with KIES?
[Captivate Android Development] smali26:
yes i did that and used the one from the AIO captivate. no luck

i have also tried different versions of Odin
[Captivate Android Development] sorata98:
Stock bootloaders

Does the Odin One-click downgrader restore the original/stock bootloaders? Just a question I have. Thanks in advance!!
[Captivate Android Development] nybmx:
Yes it restores everything.
[Captivate Android Development] smali26:
no i tried that. does not work
[Captivate Android Development] mrhaley30705:
Did you use mine or designgears? Mine doesn't have bootloaders, dg's does, and should flash you back to stock JF6
[Captivate Android Development] Kyuta Syuko:
I have a suggestion that might be a bit out there for most people, but for those having issues getting Windows to recognize their phone so they can flash via Odin I might suggest going to http://www.ubuntu.com/download/ubuntu/windows-installer and using that to install Ubuntu or Kubuntu or which ever you desire along side your Windows installation then booting into whichever you installed and downloading Heimdall from http://www.glassechidna.com.au/products/heimdall/ and flash your phone from Ubuntu using Heimdall. I always use my laptop running Kubuntu and Heimdall to flash my phone with no problems granted I have the DVD version installed on my laptop so I'm not sure how different the Wubi version will be. Also the thing about Heimdall is that it's not as easy as Odin since you have to pull the files out of the RAR file and put them in the proper locations for a flash with Heimdall, but it's pretty straight forward.

The Recovery slot isn't used as far as I know.
[Captivate Android Development] iphaded:
Hello All,

Forgive me for my noobishness but I last installed Firefly 3.0(Froyo) on my Captivate. I've tried to follow the threads on how to upgrade to one of the Gingerbread custom ROMs but somehow have lost the trail. From what I understand, I am able to use this package to have updated GB bootloaders that will then allow me to flash GB kernels and roms? Thanks ahead for your responses.
[Captivate Android Development] mrhaley30705:
Yes, flashing this package will allow you to flash GB kernels and roms.
[Captivate Android Development] Kyuta Syuko:
You will also have to make sure you're flashing the correct kernel for the ROM you want to flash. Some require CWR 3.0+ and some require CWR 2.X.
[Captivate Android Development] iphaded:
Meaning that I'd just have to flash the prepared packages for that specific custom rom, correct?

So I'd like to verify one more time, from Firefly 3.0 my steps will be:

1. disable lagfix and convert to RFS

2. clear dalvik, clear cache, factory reset

3. use this package to flash GB bootloaders directly without going back to 2.1/2.2 stock

4. flash GB kernel+rom of my choice

and if I chose to use this http://xdaforums.com/showthread.php?t=1145149 for example it would be the same method? I'd like to stick to a Captivate based rom thus my hestitation in using the I9000 GB. Thank you in advance.
[Captivate Android Development] Kyuta Syuko:
The best thing you could do to make sure you have it flashed right is after step 3 flash the ROM of your choice, reboot into recovery clear cache, falvik, data/factory reset and flash it again. Flashing the ROM the first time will make sure you have the right CWR version (ROM may or may not be messed up due to wrong version at this point) and flashing the second time will make sure the ROM itself gets flashed correctly.
[Captivate Android Development] iphaded:
Awesome thanks, I'm confident enough to give it a go now.
[Captivate Android Development] iphaded:
Thanks everyone, I'm now on Captivate GB stock successfully!
[Captivate Android Development] rkkaranrk:
I did flashed these over serendipity VII some days back but I have a question in mind after flashing these bootloaders can we flash any GB Rom over it. Like im on S7 right now can I flash other rom over it or I have to flash the whole kf1 rom (without the bootloaders) to go back to stock GB.
[Captivate Android Development] KayvinM:
You should be able to flash any Rom over it. No need to go back to stock. I just do a factory reset, clear cache and dalvik cache. Just make sure you read the OP of whatever Rom you choose to flash to make sure you don't miss any important Rom related step.
[Captivate Android Development] malbolgias:
Can someone post the bootloaders for use with heimdall. Thanks.
[Captivate Android Development] mrhaley30705:
Just download UCKF1 from samfirmware. They are in the file labeled "CODE_I897UCKF1........". You can use 7zip to extract everything (password is samfirmware.com). Just move them from the folder you extracted them in to Heimdall.
[Captivate Android Development] mrhaley30705:
nice mind.
[Captivate Android Development] malbolgias:
Thanks a lot.
[Captivate Android Development] malbolgias:
Ok quick question, boot.bin => primary, sbl.bin => secondary?

Thanks
[Captivate Android Development] mrhaley30705:
Yes. And I would recommend using the param.lfs.
[Captivate Android Development] Kyuta Syuko:
Yeah if you're going from I9000 bootloaders (which you probably are why else would you be flashing these) then you'll want to use the param.lfs. Otherwise you'll end up with garbage as your initial boot screen.
[Captivate Android Development] malbolgias:
Ok thanks guys. Will it a try in a while
[Captivate Android Development] mrhaley30705:
Im not sure, but i think one of the new(actually old) button combos is power+vol up = reboot.
[Captivate Android Development] nybmx:
Yeah it's been that way since at least froyo (maybe eclair but it's been way too long since I've used it). I use that combo instead of battery pulls if it locks up. Makes things easy.
[Captivate Android Development] golfslicer:
Something weird going on with this package, it won't install, just hangs, everything else works fine, to flash the bootloaders I had to download the one click package for KF1 by Designgears and then flash Continuum after that. Just the bootloaders won't flash on either of my computers running windows 7 64 bit with the correct drivers. I even reinstalled windows 7 on one machine. The phone connects fine and odin works fine, doesn't make sense?
[Captivate Android Development] mrhaley30705:
Did you run it as Administrator? If you look a couple posts up, I uploaded a package with the individual files for use Heimdall

.

Edit

Removed link
[Captivate Android Development] golfslicer:
I am the administrator account, and yes I used the run as administrator option also. How do I use the three files in zip package that you posted in Odin as the full odin works fine. ie: boot.bin sbl.bin and param.lfs. What do I check and which slot do I put them in?

Also I just looked at the tar package to flash just the i9000 gingerbread bootloaders and it had a file zimage in it instead of param.lfs file. What is it for. I guessing I just create a tar file from these 3 files and then put it in the pda slot in odin. I just want to get it right.
[Captivate Android Development] djinferno806:
I'm experiencing something strange. with these bootloaders, and an i9000 rom if I'm playing music and I turn the screen off or it times out. the music skips endlessly repeating itself and the OS crashes. u need to hard reboot. I've reproduced it 100% of the time.

ie: i897 bootloaders + apex 7/continuum 6

=crashing

but if I use i9000 bootloaders its all good. not one problem at all.

and also with cog 5 and these bootloaders I don't get this problem. Only with an i9000 rom.

really Strange. I'm sticking to i9000 bootloaders....
[Captivate Android Development] mrhaley30705:
Actually, I made that for a Heimdall user. To use it in odin, I would have to create a tar file with all 3 files in it, then add a md5 sum to it before odin would recognize it. Just stick to the one click until I am able to put up an odin file for it.
[Captivate Android Development] mrhaley30705:
For those not wanting to use the one click, here you go.

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.

Sorry for any confusion I may have caused anyone.

Updated 2/11/12 due to technical issues with multiupload
[Captivate Android Development] golfslicer:
Thank you that one click file must be too small because it won't run on my pc's.
[Captivate Android Development] mrhaley30705:
No problem. Glad I could help.

You might want to check your antivirus software. Until I made an exception for Odin, it kept removing it automatically, thinking it was a security risk.
[Captivate Android Development] Fate-Silver:
Sorry, I want to ask some stupid questions here. :o

Thanks.
[Captivate Android Development] xpakage:
Correct

10 char
[Captivate Android Development] mrhaley30705:
Check the 2.1 & 2.2 roms for boot loaders. Some roms use a secondary bootloader, which could cause a hard brick. I wouldn't flash the gb loaders until you are ready to run a gb rom.

It actually flashes 3 files. The primary bootloader (boot.bin), secondary bootloader (Sbl.bin), and boot splash image (param.lfs).

The phone-!-computer is not a new dl screen, just an alternative one.
[EVO 4G General] r2tincan:
I can't text more than one message to any person at one time. This includes both mass texting and sending large compound messages.

Searched google and the forums but see no fix. What do I do?

Thanks
[EVO 4G General] DarkManX4lf:
I ran into this problem when I merged with Google voice.....it was the only reason I un-merged.....

Google voice does not support sending messages to mutiple people at the same time. You could use your stock message app to send messages to mutiple people but the responses will come back into Google voice. The other option is to un-merge.
[EVO 4G General] r2tincan:
I am using my stock app... Google voice is integrated to my account with sprint
[EVO 4G General] Fazulka:
I send messages to groups all the time. Yes, to send them I have to use the stock app but its not hard. Before the integration replies came in another thread, now it comes in a different app, not a big difference to me, it all pops in the notification bar anyway. The only thing I miss is the pop up message from handcent they you could reply directly from.
[HTC Sensation] ilgrande:
Bear in mind that I come from a Desire HD running Cordedroid V6.8...;-))

On the plus, the screen and resolution look great....

But:

- it's somehow less responsive, I feel that on occassion it feels like I really have to bang the screen

- sense 3.0 is laggy

- the keyboard is laggy

- scrolling, whether through sreens or in widgets, isn't smooth...

In honesty, it reminds me of my first stock Galaxy S...

Am I the only one ?
[HTC Sensation] xnifex:
if the 8348235923497834 other threads that rehash these issues are any indication, then no.
[HTC Sensation] redbullcat:
Don't worry. It's HTC's rubbish stock ROM. I made a thread about it: Clicky!

Once we get optimized ROMs on here, this thing is gonna fly :)