yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] anishz:
Calm down, just flash back to stock, there are one-click roms posted in stickies.

Flashing bootloaders from ICS is bad idea, flash bootloaders only from stock.
[Captivate Android Development] mrhaley30705:
Not just recommended, its the only way it will work. Difference in framework causes problems.
[Captivate Android Development] zzmomo73:
OK I managed to flash back to stock 2.3.4.. don't think ill be flashing any roms for a while
[Captivate Android Development] Dave the Knave:
Why not? As long as you do it properly you have no reason to worry. And on the off chance you muck up again, a jig is your best friend.

Sent from my Captivate
[Captivate Android Development] zzmomo73:
already got it rooted any ics installed on it.. daily life of a flashaholic
[Captivate Android Development] askpcguy:
You are not a flashaholic unless you have bricked your device at least one time.
[Captivate Android Development] zzmomo73:
Dammit
[Captivate Android Development] mrhaley30705:
You mean like "now its a paperweight:("brick or "man i got to get/make a jig:eek:
[Captivate Android Development] 4-2ndtwin:
^

Lol.

I vote for the "man i gotta make a jig, cause i don't know what this 'kernel panic' screen is...but somethin ain't right." :p
[Captivate Android Development] askpcguy:
Haha the now I need a jig brick because the paperweight brick..is just cruel.
[Captivate Android Development] mrhaley30705:
Well, I've done that a couple :rolleyes: times.

Edit

That reminds me, i need to make sure my jig still works. You know, just in case.
[Captivate Android Development] askpcguy:
Honestly I only soft bricked in 2010 when I tried an i9000 rom and didn't wait long enough for Odin to finish. Second usb cord pull soft bricked me LOL. I even called AT&T who were clueless on fixing it.
[Captivate Android Development] mrhaley30705:
I tested an Odin package i made and realized as it started to boot i forgot to put the factoryfs.rfs in the package. Definitely looped from that one.
[Captivate Android Development] LotusLTS:
help, set this boot loader, now I can not run properly, all the time this goes loader, still can not enter boot mode. how can I choose "ок" ?

please do not judge strictly. I'm noob

my device is Samsung SGH-i897 Captivate . Thanks
[Captivate Android Development] daskanda:
Use the power button to select and volume up and down to move up and down
[Captivate Android Development] LotusLTS:
I have tried does not work, and even now I can not even get into Download mode (volume down + power button)
[Captivate Android Development] melvinaury:
If you want to go to download mode just turn off the phone and pull the battery out and install it again. Then press vol up + vol down and connect the usb cable. In this way the phone will enter in download mode. Then you can use odin to install a kernell.

The combination that you mention is for enter in recovery mode. And if you have i897 bootloaders you have to press vol up, vol down +power..
[Captivate Android Development] LotusLTS:
Thank you! went to download mode.

please tell me what can I do to flash such as the latest official? For example there is only "download mode" and nothing else, that is, that as a download and fill in Odin. Thanks
[Captivate Android Development] robm1911:
Go to the link look in the third post for the kk4 one click with bootloaders by 4-2ndtwin. Be sure you have a good cable and a stable connection cause when you are flashing bootloaders if the cable gets disconnected you will hard brick your phone.

http://xdaforums.com/showthread.php?t=1300843
[Captivate Android Development] LotusLTS:
Thank you all for your quick answers, I can now through Download Mode (odin)

but again the problem, all firmware oneсlik not see my device, but simply Odin sees it. What should I do?
[Captivate Android Development] melvinaury:
First start the one click Rom and then connect the phone pressing the vol up + vol down. Then it should be recognize.
[Captivate Android Development] askpcguy:
Get the Semaphore 1.2.1c.tar and put that into Odin PDA section, then uncheck auto reboot and reset time. Flash that kernel. It should boot up as normal.
[Captivate Android Development] blackwolf13:
15th times a charm. up and going again.

thanks again ceazar
[Captivate Android Development] rivtre:
Works fine. How can I get rid of at t logo? I9000's way still works ?

Sent from my GT-I9000
[Captivate Android Development] kimchi0400:
This, I quite like having the i896 logo instead of the at&t one
[Captivate Android Development] evl2100:
After flashing this bootloader, can i use buttons to enter recovery/download mode without flashing 3 buttons fix?

Moreover, I have a friend who flash back to stock 2.1 with 3 buttons fix and he flash cognition 5 beta before. He got hard-bricked yesterday. Correct me if i'm wrong because I think hard-bricked only happens when flashing 3 buttons fix while using I9000 bootloader. So how hard brick can happen in that fact?
[Captivate Android Development] Reynaldinho111:
1. Yes you should be able to.

2. And mismatching bootloaders will always give you a hardbrick. Three button fix only has one, if he was flashing over cog 5 then yeah that would probably end up in a hard brick. Please correct me if im wrong.

Sent from my beloved Cappy!!
[Captivate Android Development] evl2100:
Got it........................
[Captivate Android Development] Cezar`:
That is very interesting. I never had that screen actually.

So what you're stating is that you had the screen and ODIN flashed the firmware as it it was in Download mode?
[Captivate Android Development] jdmusicman72:
Does it really make a difference which bootloaders we're using?

I'm only asking because it seems kind of redundant at this point or am I missing something here?

How will this affect performance for example?

Please articulate...

Nevermind..Downloaded the package, opened it up, and flashed it in literally 30 seconds. No issue whatsoever.

So it's business as usual as far as flashing GB Roms I presume???
[Captivate Android Development] mrhaley30705:
Its not a new screen, its been around for awhile. Up until now, Odin wouldn't let you flash anything from here. I still have the regular dl screen when I use my extended power menu to boot into download mode.
[Captivate Android Development] malbolgias:
The i9000 boot loaders have worked for most of us just fine. I do not really see any point in flashing. As i9000 key combos are much more straight through.
[Captivate Android Development] Time_Zone:
Well for me,on simply, the charging bug returned after flashing these bootloaders. I wonder if I am the only one though.
[Captivate Android Development] tcortinag:
Same here, had no problems with i9000 bootloaders and I can get download without USB.
[Captivate Android Development] Shammyh:
To be fair, as long as you're seeing that screen to begin with it means you aren't bricked. Only *soft* bricked as they like to say around here. As long as you see anything on the screen your PBL and SBL should be intact. And if that's the case, you should be able to get to download mode.

PS, anyone want to fry their kernel or screw up their partitions to see if they can get to DL mode from the "Phone ! PC" screen?
[Captivate Android Development] silverslotcar:
+1 on above request I'm interested to see if that the phone is recognized by Odin while having that screen.
[Captivate Android Development] erstad:
love the new boot loaders soft brick is now a dl mode
[Captivate Android Development] erstad:
no more bricks = a phone i will never get rid off

this is the best stock recovery Ive seen

does ne1 know if froyyo based roms boot off this
[Captivate Android Development] mrhaley30705:
I've not tried it, but they should.
[Captivate Android Development] Endoran:
Well besides the fact that the phone to computer soft-brick screen is now supposedly a download mode what else makes this the best stock recovery you've seen? I mean for real...getting into download mode took like 5 seconds even with that screen, is it really that awesome? So far I haven't seen any reason to flash these bootloaders, I'd like to hear some real benefits (if any) besides a slightly faster route to download mode when you've fugged your phone.
[Captivate Android Development] topiratiko:
Because theyre the bootloaders MADE for our phones? Lol ive never been a fan of bootloaders that claim your device as something it isnt....that was enough for me.

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] erstad:
Well if i used odin to flash on 2.1 bootloaders i would have abitch of a time using my jigg to get into dl mode at least when i mess up on odin its in dl mode arleady i think thats a benifit over stock 2.1 or i9000 boot loaders dont you
[Captivate Android Development] erstad:
Alsobeing able to flash other gb roms is a plus .possbly flashing other froyyo as well after cmw comes out
[Captivate Android Development] topiratiko:
In my eyes this is not optional but mandatory

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] erstad:
It may become the baskin robbins of bootloaders choose your flavor
[Captivate Android Development] mrhaley30705:
Bootloaders don't change recovery, thats in the kernel.
[Captivate Android Development] lowlymarine:
I had this same thing happen to me just now trying to flash this package, except rather than crashing Odin just spit out "FAILED" after trying to flash boot.bin, then rebooted my phone to a black screen. After my heart skipped several beats, the ol' Phone+!+Computer finally came up, and I put it back in download mode with the I9000 button combo and flashed again without incident, and it then booted back into my ROM without issue.

Still, this is my first experience with Odin 1.81 and I'm now certainly rather curious as to what it changes versus 1.3. Perhaps it's unrelated to that, of course.
[Captivate Android Development] Fate-Silver:
Can this be used in MIUI 2.3.4 Captivate ROM? :confused:
[Captivate Android Development] lownox:
Worked perfectly. Thanks
[Captivate Android Development] mrhaley30705:
I think that either 1) you cable is going bad or 2) you usb connector is going bad/needs cleaned. Thats the only thing that explains it, to my knowledge.
[Captivate Android Development] x3nhydr4lutr1sx:
Works on Serendipity 5.12 Froyo, so definitely works on Froyo.
[Captivate Android Development] kaljr1980:
After 1 clicking gb loaders it then did a reboot and went directly to recovery and I flashed cwm update.zip and installed Miui 1.6.17 for captivate and everything seems to be working fine. Seems a lil snappier. No lag that I've noticed on stock kernel. Then again it could be the thought of trying something different...lol

Sent from my SGH-I897 running MIUI 2.3.4
[Captivate Android Development] low99:
flashed without any problems. thanks man, but my phone rebooted into recovery instead... then I rebooted again from there and everything looks fine.
[Captivate Android Development] Shammyh:
So now that we're getting lots of folks to flash bootloaders...

Umm, has *anyone* found any significant or conclusive difference from using these bootloaders?

Like anything at all? I'm sort of starting to think that these are almost identical to the i9000 bootloaders minus the logo and button combo...
[Captivate Android Development] Klyentel:
doesn't the ATT bootloader screw around with the data? I thought I read they had the HSPA blocked or something like that, and I've been getting the E a lot lately since I flashed this:( Not everywhere, but in more places than usual, I always had the H with the I9000 bootloaders. Is there a fix for this?
[Captivate Android Development] s1l3nt:
worked perfectly for me on serendipity 7
[Captivate Android Development] KayvinM:
Has anyone changed the boot screen with this method yet? http://xdaforums.com/showthread.php?t=1065743

I would like to try it but not sure if it's compatible.
[Captivate Android Development] tallsilver:
Don't know why I loaded them but work perfectly on Serendipity 7. :D
[Captivate Android Development] johnwayne007:
Flashed with Continuum 5.6 no problems!
[Captivate Android Development] silverslotcar:
I just loaded these bad boys up too because two ppl on S7 said it worked and guess what, it worked flawlessly. Nice package Cezar! :cool:
[Captivate Android Development] mrhaley30705:
...bump...
[Captivate Android Development] dizx:
I am not sure if this is just a coincidence, but I just experienced a misdirected text message (intended for one person, but sent to another).

This just occurred after flashing these new bootloaders, and using Handcent.

I've always frozen the default system SMS messaging app to avoid this issue as I've had this happen on Froyo and have been using Handcent.

Anyone else have this happen? Not sure how bootloaders would affect SMS...?
[Captivate Android Development] watsa:
dont drink too much :D
[Captivate Android Development] dizx:
It's really weird. Message is shown to be sent to the right person, but when you look at the details, it shows the other persons number.

If it's the damn bootloaders, I'm going back. Not blaming Cezar. Blaming AT&T. Grrr.

Someone convince me it's not the bootloaders, please.
[Captivate Android Development] mrhaley30705:
It's not the loaders...It's not the loaders... It's not the loaders...
[Captivate Android Development] dizx:
Thanks. I needed that. Maybe Handcent just doesn't work well with 2.3.4...? Gonna try GoSMS.
[Captivate Android Development] johan8:
It is not a good idea to change the bootloader,

and it is not necessary.

I keep using i9000 bootloader,

Vol up + Power = Recovery

Vol Dn + Power = Download

And confirm work with Froyo, GB, i9000 and i897 roms.
[Captivate Android Development] KayvinM:
Boot screen Replacement

Just posting this as a FYI for anyone who is interested in changing the boot screen from the current AT&T, do not use the package that is meant for the i9000 gingerbread. You have to use the froyo package for it work. I have tested and can verify that it indeed works perfectly. Here's the link http://xdaforums.com/showthread.php?t=944353&page=2 Download package located in post #17. Run the froyo bat script and not the eclair.
[Captivate Android Development] streetsmart999:
Flashed on APEX 7.1 ... went smooth with No issues.
[Captivate Android Development] KonaZXIII:
It worked the first time w/o a problem. Thanks!
[Captivate Android Development] WickedNite:
Why? Just wondering cos I want to change my Bootloaders to the AT&T one.
[Captivate Android Development] bigbadwolf311:
I am running mosaic iv on cappy. Can I flash these bootloaders or do I need to go back to stock?? Thanks in advance
[Captivate Android Development] RockRatt:
Not sure what I mucked up but I have this in the q&a section and I am posting it here for anyone that has a fix or so they do not run into the issue I am having.

http://xdaforums.com/showthread.php?t=1138132

Basically I had been running g the cappy gingerbread bootloaders dog's rom, went back to try out Apex 7.1 over it, then tried to go back using a nandroid backup. OOPS. I am not sure if it was that I didn't reflash DGs kernel before or what else went wrong but I cannot get phone to be recognized in Odin (though it did before I F'ed it up) and now it seems like I corrupted system, data, cache, sdcard and all so recovery mode is doing me NO good either. Anyone with ideas let me know on the links thread. Thanks

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] KayvinM:
You can flash them, no need to go to stock
[Captivate Android Development] keller.jeff:
Try reinstalling usb drivers, happens to everyone.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] RockRatt:
Did that multiple times on three different machines. I went in a deleted everything samsung and android and started over with reinstalling them. Been at it for two days now when I have the time to sit and mess with it.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] mrhaley30705:
Did you try installing the drivers that are included with Kies?
[Captivate Android Development] andrewdroid:
Cezar, can I update the bootloaders if I'm running Continuum 5.6? Will it mess up my Continuum installation?
[Captivate Android Development] mrhaley30705:
I am not Cezar, but yes you can update them even while running C5.6 (that's when I updated mine). No worries, you shouldn't lose any apps or data.
[Captivate Android Development] andrewdroid:
Did you notice any improvements?
[Captivate Android Development] mrhaley30705:
It's really difficult for me to say becauseI flash so many different tests.
[Captivate Android Development] sremick:
It keeps being asked but not being answered:

What is the point/benefit of using different bootloaders?

It seriously seems like changing from an AMD to Phoenix BIOS and expecting Windows to run faster/better. :rolleyes:

People are wanting so bad and trying so hard to do this, but other than the "gee whiz look what I did" factor, I haven't seen anyone list an actual benefit of doing this.
[Captivate Android Development] WickedNite:
+1

Sent from my Captivate
[Captivate Android Development] johan8:
Why ?

Why would you like to change the bootloader ?

The ATT bootloader won't make you phone run faster or smoother,

it won't change your boot-logo,

why would you need to change it ?

No matter it is i9000 bootloader, ATT bootloader,, from Froyo to GB....

they all do the same thing.

Just the key-combination is different, or it is 3keys locked.

The i9000 Froyo bootloader would be better,

just Up+Pwn=Recovery, Dn+Pwn=Downloader

Much more useful than the other.

Unless, one day the new rom and kernel need specific bootloader to run.

But at that time, you may probably using other android phone.
[Captivate Android Development] andrewdroid:
Well, eventually I might want to try Cognition 5 once they add Voodoo Sound. These i897 bootloaders are compatible with all nearly all the roms, while the i9000 bootloaders are not. Plus Cezar recommends updating them, and I'm a big fan of whatever Cezar says...
[Captivate Android Development] andrewdroid:
PS. I already did the update, it was pretty painless. I didn't need to reinstall any roms, or do anything crazy. Just made super sure my USB was properly connected. I agree the key combinations for the i9000 are much better, but I usually go to recovery using the menu, and usually go to download mode using my jig or the menu.

Perhaps the charging bug has something to do with the i9000 bootloaders? Now that would be a great reason to update. I'll have to test that.
[Captivate Android Development] johan8:
Yup.

In fact, Bootloader is totally different from computer BasicInputOutputSystem(BIOS).

BIOS has I/O system program in machine language.

After your computer has started and fully booted into OS,

the computer still keep accessing the BIOS for the I/O control programs (CPU,RAM,HDD,PCI,PS2 etc.. accessing IRQ DMA IO addresses etc...)

BIOS has bootloader too, it is in boot block.

Bootloader, is just a piece of program tell the system how to start/boot.

After the system bootup, everything control by the OS.

Some people would ask why just the bootloader, why not use a BIOS like computer?

I would only say, it is design like that.
[Captivate Android Development] mrhaley30705:
Actually, they do change the boot splash at startup (ATT World Phone screen) It's the param.lfs file.

They all do the same thing, but in a slightly different way.

While that may be the button combo for i9000, it isn;t specific to the froyo roms.

Look, they are the loaders made for this phone. They work better than i9000 loaders. I have yet to hear anyone say their phone goes up to 110F while using these loaders, unlike the i9000 roms. Cezar has made his case for flashing these in the op (yoiu read that, right?).

Let's try to save this thread for q&a about installation and any troubleshooting for these loaders. Open another thread to debate why or why not.
[Captivate Android Development] sremick:
In what way, though? That's all I'm asking.

I'm not trying to debate. I'm only asking for the reasons someone would go through all this trouble. There seems to be a huge chasm between effort and payback here so whatever I'm missing I'm hoping someone can elaborate. :)

Both get your phone to boot. The I897 bootloaders have different, more-difficult key combos to get into recovery and download modes. That seems to be about it. No feature, speed or performance benefits as far as I can tell. So I want to know what I'm missing here. :)

Cheers...
[Captivate Android Development] 4-2ndtwin:
This was answered from day 1 by

icezar1

himself...

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

This is in the OP...2nd paragraph.
[Captivate Android Development] sremick:
I guess I don't see there where actual benefits are listed? He only says that he "believes" that there "might" be benefits, simply because the I9000 and I897 are a bit different.

I did see that, but it didn't answer my question. ;)

Not sure why people are getting so up-in-arms and defensive here. I'm not trying to be annoying or troll... I'm being sincere when I ask if there are real, confirmed benefits. If there are I'll flash today. But what are they?

Cheers...
[Captivate Android Development] 4-2ndtwin:
^ I wasn't being defensive or anything like that. I just saw the discussion and thought I would post the only answer that is credible. :)
[Captivate Android Development] nkrick:
How about this reason: if you break your phone while it is still under warranty, you are less likely to encounter problems getting it replaced if you are running an i897 bootloader. ;)

Edit: Or perhaps this reason: if there was no reason to have a different bootloader between the i9000 and i897, why would Samsung waste R&D money to develop different bootloaders?
[Captivate Android Development] sremick:
Understood. No hard feelings. :)

That's kind of what I'm wondering. But this is AT&T we're talking about. Surely they had some reason... but is it one in the user's benefit? This is the same company that also wasted R&D money to add bloatware and remove the ability to sideload apps from the standard I9000.
[Captivate Android Development] bigbooty:
Their not ATT boot loaders their Samsungs.
[Captivate Android Development] nkrick:
I think you seem to be looking at the problem in reverse. You want someone to convince you to use the i897 bootloader. The way I see it, if there is no disadvantage to using an i897 bootloader, why would I use an i9000 bootloader? It seems the default rule should be, use the bootloader designed for your hardware unless there is a proven reason not to.
[Captivate Android Development] silverslotcar:
+1 Why use bootloaders that aren't meant for your device?? We are lucky enough that I9000 bootloaders even work on Captivates. And I would much rather see an AT&T boot screen for five seconds then an I9000 boot screen when I don't even have that particular phone. These new Cappy GB bootloaders are basically universal in every way. You can run Eclair, Froyo, or GB on them.
[Captivate Android Development] mrhaley30705:
Plus, it fixes the lack of3 button combo for a lot of people without causing a brick down the road.
[Captivate Android Development] silverslotcar:
Yea, I love that bcuz I have a batch 1008. I had to be VERY careful back in the day. Many times I lost recovery mode and had to invest in a jig to feel safer.