yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] yguns76:
Had a similar problem after using odin. Odin experienced a hiccup and stopped.

I could not get the phone into download mode with my jig. Kept getting the pc ! Symbol. I resorted to using Odin again and pushing the one click and it worked.
[Captivate Android Development] agaruba:
Can anyone tell me how to do this if we were on the AT&T GB bootloaders? I can remove the AT&T logo but no SU request comes up to accept the new one so i end up wth just a garbage screen.
[Captivate Android Development] sepherian:
rated five stars and hit the thanks button.

amazing. time to CM7
[Captivate Android Development] nybmx:
Read this thread. http://xdaforums.com/showthread.php?t=1065743
[Captivate Android Development] Bruce Inman:
Ok, I one clicked back to stock JF6 to see if I could get rid of the charging bug I have been having. ROM boots fine. Then I install AT$T bootloaders and try to flash a 2.3.4 ROM. It then gets stuck in voodoo loop trying to set up ext4.

I even tried the i9000 GB ROM and it flashes to completion but opens in CWM with a bunch of write errors and cannot boot into ROM.

I should be able to flash any GB ROM for the captivate with just the AT$T bootloaders installed, right? I shouldn't have to flash the whole stock GB ROM?

Any ideas?
[Captivate Android Development] mrhaley30705:
With either set of BL, either I897 or I9000, You can flash any Gingerbread (2.3.3 or 2.3.4) Rom. You are not restricted to I9000 roms only with I9000 BL, or I897 roms with I897 BL.

Also, they are backwards compatible. You can flash froyo or eclair roms with them. BUT, make sure the rom doesn't use a single secondary bootloader (Sbl.bin), or you will have a permanent, useful as a paperweight, JTAG recoverable only, brick.
[Captivate Android Development] Bruce Inman:
Thanks, I understand all of that.

I guess my main question was; Can I go stock JF6, install BLs, then a custom 2.3.4 ROM w/o having to flash the entire stock GM ROM? It seems I should be able to.

I wonder if CWM is the issue? I downloaded from the market and its 2.5 but I believe I've seen issues with GB ROMs being flashed with 2.5 CWM.

Well, I'll give it another shot....
[Captivate Android Development] watsa:
yes u shud be able to flash BL --> Kernel to get CWM and then ROM
[Captivate Android Development] mrhaley30705:
When it comes to installing a rom, I have to refer you to the op (First post) of the rom you want to flash. It should have install instructions, plus links or downloads to everything you need to install that rom. Its also a good idea to read the first 4-5 pages.
[Captivate Android Development] Bruce Inman:
Thanks Watsa. I got it to boot finally, just had to go through entire process again. I wanted to see if the stock GB ROM was the source of my charging bug. ;)
[Captivate Android Development] Bruce Inman:
:DHaha, thanks for your reponses anyway. :D

I have flashed many ROMs, just wasn't sure why the ROM wasn't booting after going back to stock.

It was because I was using CWM from the market instead of flashing a kernel to get the newer CWM.
[Captivate Android Development] ameedi600:
I was wondering if I flash the gb bootloaders, would I be able to flash froyo roms as well as gb roms without fear of brick. Thanks in advance
[Captivate Android Development] mrhaley30705:
Just make sure the froyo rom doesn't use a lone Sbl.bin (secondary bootloader) in the flash. That would be a hard brick situation.
[Captivate Android Development] ameedi600:
How would I know if the froyo rom has sbl in it?
[Captivate Android Development] mrhaley30705:
Ask in the rom thread, or use 7zip to explore the zip's folders/files.
[Captivate Android Development] ameedi600:
Alright then thanks for all your help everyone
[Captivate Android Development] Justjusten:
Ive had this fail twice and had to use a jig to get my phone into download mode
[Captivate Android Development] rkkaranrk:
I doubt, if this fails ur phone will be dead nothing will work even the jig.

What error u got ?
[Captivate Android Development] mrhaley30705:
Try this one >>HERE<<

It's the same files (boot.bin, Sbl.bin, and param.lfs) as the one click, but it uses Odin 1.8.

Extract with 7zip, load into pda slot.

Also, what is the build number for your phone?

Some phones just don't like 1 clicks. This should get you going with the new bootloaders.
[Captivate Android Development] stewi21:
its possible, happened to me, my phone didnt like the oneclick package and i just got soft bricked everytime. Mrhaleys non one click package worked tho (:
[Captivate Android Development] yuki86:
after bad flash, I fixed the semi-brick (phone-!-pc) with home made jig (300k resistor and micro-usb plug)

thx XDA!!
[Captivate Android Development] alkiter:
I've been using these bootloaders with MIUI and it's working fine...
[Captivate Android Development] punisher2008:
worked for me perfectly the first time, running mosaic 4
[Captivate Android Development] drewbag:
Captivate i896

Hi,

I am just about to flash my first custom gingerbread rom to my rogers captivate. Can anyone tell me if this will work on the i896 captivate? Oh BTW the rom I'm looking to flash is Dlev's v 4.2 JVQ 2.3.4 ROM

Thanks
[Captivate Android Development] Bruce Inman:
Yes, it should work.
[Captivate Android Development] drewbag:
Thanks, I tried this but it froze during the install. I ended up using the i9000 bootloaders and flashed it with odin. Worked perfectly.
[Captivate Android Development] anadam:
Just for a info can these be flashed over froyo and then any gb rom ?

or one has to flash the whole stock gb rom ?
[Captivate Android Development] mrhaley30705:
Try using the one I posted a page or two back. Same files involved, but its not a one click.
[Captivate Android Development] mrhaley30705:
No need to flash a gb rom. They are backwards compatible with froyo/eclair roms. BUT, do not EVER, EVER, EVER, EVER UNDER ANY CIRCUMSTANCE FLASH THE OLD 3 BUTTON FIX. It will hard brick your phone, which is only repairable by jtag.
[Captivate Android Development] anadam:
Okie, will keep that in mind.
[Captivate Android Development] Kyuta Syuko:
As far as I've seen the 3-button combos are in these bootloaders. They're just different depending on which bootloaders you have.

I9000:

Vol Up + Power = Recovery

Vol Down + Power = Download

I897:

Vol Up + Down + Power = Recovery

Vol Up + Down + USB = Download
[Captivate Android Development] mrhaley30705:
Correct. But some people think that since they had to use the old fix before, they will need to now. This is not true. The new bootloaders will fix any old button combo problems.
[Captivate Android Development] Wdustin1:
So I flashed these last night and I have a 1010 model. Has anybody figured out a safer way to flash to stock for warranty repair reasons than one click I have never tried one click I always use 3 button fix. But I know that is a HUGE nono
[Captivate Android Development] RockRatt:
You can probably just flash one of the eclair stock roms that DO NOT USE the bootloaders. I can't remember what one that would be right off the top of my head. Then IF you have to take it back the button combs would be the same as with stock froyo/eclair and you would have the stock eclair on it. How else could they check/know you have the NEW BOOTLOADERS? I don't think they could as far as I can tell. Since with the NEW i897 bootloaders you can still run froyo or eclair roms without having to flash back to eclair with its boot loaders. Someone correct me if I am wrong with my thinking here.

NOW if you had the i9000 bootloaders they would be able to tell since the button combo would be different.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Kyuta Syuko:
I'm pretty sure they'll be able to tell if you have the GB bootloaders... They're probably able to hook your phone up to a computer/machine that gives them all the info about what all is on it and the BL info would be not what they expect...
[Captivate Android Development] Wdustin1:
yes thats exactly what i was thinking as well. anybody else got any suggestions
[Captivate Android Development] sepherian:
Hard brick it on purpose.
[Captivate Android Development] crt60:
My understanding is that they check the MD5, if it is off, they know it was tampered with.
[Captivate Android Development] Jow24:
any roms to recomend to use with this bootloaders? i want to be sure what i can flash with this bootloader on my cappy
[Captivate Android Development] 4-2ndtwin:
^ Cognition 5 is a good one... just saying :D
[Captivate Android Development] Wdustin1:
So nobody has any ways of returning to stock bootloaders and all on a 1010 model for warranty reasons. So these gingerbread bootloaders were extracted and turned into a one click could that be done with just the orginal bootloaders. Then flash a 3 button fix?
[Captivate Android Development] 4-2ndtwin:
^ It's already been done. There is a Stock Eclair 2.1 One Click Odin. Search the Development section. It's in there.

Unless u were talking about Froyo 2.2

edit: Here's the link... I897UCJF6 - Odin3 One-Click Downloader
[Captivate Android Development] drklazarus26:
boot.bin

how long should i wait for boot.bin to change?
[Captivate Android Development] olo567:
Nice job Cezar! Flashed these bootloaders in seconds.
[Captivate Android Development] Oxicottin:
I'm not sure if the bootloaders installed because after I saw the AT&T screen it went into the blue recovery. I selected the first selection "Reboot" and it rebooted. So are they installed? ODIN said everything went good. Thanks!
[Captivate Android Development] mrhaley30705:
If everything looks normal when you flash a gb rom, it worked. If you get a bunch of weird colors when the phone is booting up, flash them again.
[Captivate Android Development] Oxicottin:
Well Whats weird is nobody said anythig about it going into recovery. Here is what I did, I went back to stock JF6 then installed the KF1 bootloaders. It installed and rebooted with the AT&T logo and then recovery screen. I selected reboot and it booted back into the stock JF6 Froyo. I then installed DarkCore 3.0 unsing a ODIN kernel flasher and then I used the power + Up/Down key combo to get into recovery and selected my ROM "APEX 9" it installed and everything appears to be smooth. Now when I boot up it shows the AT&T logo then the DarkCore Kernel screen then boot screen. Does that sound correct? Thanks!
[Captivate Android Development] mrhaley30705:
Yeah, sounds like it worked.
[Captivate Android Development] TRusselo:
well got a little pickle. no big deal though

ran your one click booties exe and it ran great!! (the first time and the first time only)

but it gave me the ATT bootscreen, and ive been running a custom on the i9000 GB booties. so i tried to change it back using the package me and connecxion worked on, but it didnt work, i can only assume that the JPG has a different file name with the Captivate booties than it did on the i9000. it was just logo.jpg with i9000 and logo_atnt.jpg with froyo cappy.... but i am unable to browse the params folder.. a minor drawback to the params fix connexion made. so i was stuck with AT&T bootscreen and couldnt see what it was called.... GRR!

SO... i attempted to flash back to the i9000 booties with success! yay!

AND THEN i WAS GOING TO flash your package again and see what the ATT file was called to have connexion fix this again... BUT!!! heres the problem, i tried your program again and it failed at boot.bin!!! ya! ****ballz. reboot to brick! no nothing,

BUT!! i was able to boot into download mode

with a blank screen!!!

dunno how but it did! i was able to flash the i9000 booties again without issue. but still cant flash your package a second time! always failing on boot.bin and black screen bricking myself each time...

i can flash any bootloaders but yours now...

any thoughts...
[Captivate Android Development] topiratiko:
Bad download!?!?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] TRusselo:
i tried re-downloading for the hell of it.. still no go.

but it worked the first time!
[Captivate Android Development] mrhaley30705:
Tried the ones in my sig?
[Captivate Android Development] TRusselo:
ill give them a shot.

thanks hanley
[Captivate Android Development] Kyuta Syuko:
It's the same as Froyo so you can just flash the I9000 params file and change it that way.
[Captivate Android Development] ameedi600:
Can I flash miui with these bootloaders
[Captivate Android Development] mrhaley30705:
I'm running miui on these now. But the latest glitch test kernel may cause problems.
[Captivate Android Development] ameedi600:
Do you have any problems now?
[Captivate Android Development] mrhaley30705:
No. Nothing.
[Captivate Android Development] ameedi600:
Alright thanks and it works perfectly
[Captivate Android Development] keitaroguy:
Is there any differences out check to see if it took. I get the att world phone boot screen then the i9000 one after that is that right. Or is that rom based? plus does anything change on phone info everything still says i9000.
[Captivate Android Development] watsa:
If you see At&T screen that means you have At&T bootloaders. The I9000 screen after that comes from kernel, so if u flash say Talon you would see Talon' bootsplash, or SGH-I897 with darkcore. You wont see any changes in about phone section due to bootloaders, thats controlled by ROM(build.prop)
[Captivate Android Development] ph03nix42:
No Luck

Anyone else have a problem with the phone prompting for a password?

It won't let me get passed this screen
[Captivate Android Development] mrhaley30705:
Try rebooting a couple of times, with the sim and external sd removed.
[Captivate Android Development] Spidious:
If I put the AT&T i897 bootloader on my phone. Do I have to reinstall everything else again ?
[Captivate Android Development] mrhaley30705:
No. You can flash without losing anything.
[Captivate Android Development] Spidious:
Works great !

Thanks guys !
[Captivate Android Development] AnarchoXen:
Had the exact same thing. Didn't get past boot.bin. Booted to download via vol - and power and reflashed. Worked fine after the second try.

Runny Serendipty VII.

Thanks a lot!!
[Captivate Android Development] mrhaley30705:
Almost hard bricking is like being almost pregnant. Did you follow all the bootloader precautions?

Use USB port directly on motherboard?

A known, good cable?

Read any of this thread (if you had, you know that a flash can be accomplished from the newer phone-!-computer screen)?

Make sure your phone is in a stable position?

Forego the one click method if you have ever, EVER, just one time, had a failed flash?

I don't mean to rant, but too many people hook their phone into their computer and hit start before thinking about what they are doing, then get upset at the OP when something doesn't work. Read, research, read some more before beginning a new modification to your phone. It will save you a headache, and save xda an unneeded post. Good Day.
[Captivate Android Development] Kyuta Syuko:
Not to mention Odin itself isn't that great of a program and lots of people have issues with it, and the Samsung Windows drivers aren't very stable either. I personally prefer to flash with Heimdall on my laptop running Linux. I've also mentioned in a few threads a way to turn your Windows computer into a dual boot Windows/Ubuntu(or any of its variations) without having to mess with partitions or manually installing both OSes yourself.
[Captivate Android Development] wickerstick:
Been trying all afternoon

to Flash these stupid bootloaders and every time i do they fail and semi brick my phone.

i really want to go GB i had been running andromeda and tried to flash these boot loaders a semi bricked the device, then after finally getting it to find my phone i used the AIO toolbox and flashed back to stock and then a master clear.

then attempted to re download the file, extract and run, from stock 2.1 rooted all using AIO toolbox.

now im on 897ucjf6 and i want to badly try the new KH3 roms but the one i want to try say's i need these boot loaders. but no matter what i try they do not flash properly, i get a FAILED. my phone restarts to semi bricked screen. takes multiple 3 button the volume buttons to get back into d/l mode. i dont use windows so im using the girls NB. i use a mac, do you have to flash these boot loaders, is there a way to do it on mac? or a way it will work for sure on windows. please help im tired of running 2.1 2.2 i need me some 2.3.4
[Captivate Android Development] mrhaley30705:
Try the ones in my sig. Sounds like your phone doesn't like one clicks. Just put the PDA.tar.md5 file in the pda slot (not the bootloader slot).

PS, the ones in my sig are posted in this thread on page 11 (I think is 11).
[Captivate Android Development] wickerstick:
i kid you not i was literally trying just now and after reseting into d/lmode multiple time like seriously 10 times, it finally rebooted into recovery.....it said it passed so nvm that last post.
[Captivate Android Development] Kyuta Syuko:
You'll have to use Heimdall on Mac. It is in my opinion better anyways. With 1.3.0 You can choose which items you want to flash from the full RAR file you can download here.

You'll also need the pit file from the original KF1 which is here.
[Captivate Android Development] mrhaley30705:
I don't havethe pit, but the link in my sig has files for Odin or Heimdall.
[Captivate Android Development] Kyuta Syuko:
KH3 has an updated secondary bootloader (checked via WinMD5). Primary bootloader is the same though. Just fyi.
[Captivate Android Development] mrhaley30705:
Thanks. When I have enough time to sit at my computer I will have to update my bootloader packages.
[Captivate Android Development] Kyuta Syuko:
No problem. Maybe it fixes some of the issues some people have been having such as the I9000 default media player FCing.
[Captivate Android Development] bazarimajom:
Can i flash these bootloaders on a a phone flashed with this? sorry for the noob question
[Captivate Android Development] jecsah:
This worked fine on my wife's phone a few weeks ago. I just tried it on mine to flash Pinnacle....got stuck at setting PIT.

Pulled battery and rebooted to the phone/pc screen. Ok....rebooted into download and had a brain fart and ran Odin 1 click.....got stuck at factory.rfs.....pulled battery and now I've got nothing. Can I assume that this requires another run to the ATT store for warranty trade?
[Captivate Android Development] Kyuta Syuko:
You should be able to get back into download mode using a JIG.
[Captivate Android Development] ph03nix42:
tried and no such luck... this appears to be hardware based...

any suggestions?
[Captivate Android Development] JKelley103:
Has anyone with a 1010 build done this mod with success?
[Captivate Android Development] syanz87:
ya.. running this MOD on 1010 build for a long time... no problem at all......
[Captivate Android Development] mrhaley30705:
I consider it more of an upgrade than a modification. Just my opinion.
[Captivate Android Development] -Thrive-:
I have done it with two 1010 phones. First one worked perfectly. 2nd one soft bricked during the flash and I had to do a reset procedure (pull batt, open odin, insert usb, reinsert bat, and it should go into download mode) and then reflash and it worked the 2nd time. Both completely stable on these bootloaders. Always use caution when flashing bootloaders. Follow directions to the letter!
[Captivate Android Development] Myron94:
help

so i did this process and it went completely through, the only thing that i did not see was the i9000 splash screen i usually do. So idk if the bootloaders went through or not? how can i tell:confused:
[Captivate Android Development] syanz87:
If odin says process completed successfully... then you are done.. you are now on GB bootloaders....This is AT&T Captivate bootloader MOD, so there will b no i9000 splash screen instead AT&T Screen.........
[Captivate Android Development] rjyanj:
Did I just brick my damn phone?!

*fixed it* phew. learning experience, for real.

Thanks. -r
[Captivate Android Development] Ashyford:
Just so folks know, in my experience, MIUI works well with these bootloaders and is quite awesome with the glitch beta v12. (I use high leakage.)
[Captivate Android Development] vuoflfan:
epic fail

ran the odin...it failed...then it put the phone into the '''phone! computer'' sign....I tried up + down +usb....up+down+power+usb....down+usb....up+down+battery+power....up+down+power+battery +usb.....sometimes it will go off....but goes right back on...any suggestions?...the phone ! computer just stays on consistently now and wont be recognized by either of my computers...i am runinning cog 4.5.3
[Captivate Android Development] 4-2ndtwin:
^ That screen will work the same as the download screen.

Reboot ur computer. Use a usb port in back of computer. Right click and run Odin as adminstrator first, then pull battery out of ur phone, replace it and cover. Hold volume+/- and insert micro usb into phone (having already connected usb end of cable to computer). Ur phone should be recognized by Odin regardless of u not having download screen. Then start. Don't touch til done.
[Captivate Android Development] vuoflfan:
omg...thx...i was lost ...that was the first time that had happened...i am working on a 2010 model and it dont have the 3 key combo...didnt know if that had something to do with it...again i appreciate it....thx....now i gotta come up with some other excuse to get a sg 2 ....lol....i do want to add the reason i attempted to do this was because i thought i was having problems with my original bootloader...everytime i plugged up the phone to charge it would show the debugg or file transfer screen...i hope this solves that problem....unless u can think of something else that may b causing it...it had only started to do it recently...
[Captivate Android Development] 4-2ndtwin:
Don't flash the Odin with the 3 button fix or u will b hard bricked.

And as for ur problem it seems i do recall reading something about it, but don't remember where it was. sorry. Did u try searching about ur phone being plugged into charger and then showing what u mentioned?

edit:

Try going into ur settings uncheck

debugging mode then go to usb settings and select "mass storage" then go back and reselect debugging mode.
[Captivate Android Development] vuoflfan:
it really didnt start doing it til i downloaded ''words with friends'' and ''word feud''...the thing is it dont do it all the time..about every other time...that problem and noticing a an occasional lost of data and or phone signal....I was thinking about doing a gingerbread rom anyway...still undecided on DG's 5.2 or pinnacle....any suggestions?
[Captivate Android Development] 4-2ndtwin:
I edited my post.

And either Pinnacle or Fusion would b really good kh3 roms. The dev of cog 5 has moved on to sgs 2, so no more development.
[Captivate Android Development] guilleglad:
Stuck on Boot.bin

Hi there i have a problem, ODIN 1-click gets stuck on boot.bin, i've tried everything but no luck. The only thing that is working is the Download mode but i can't install anything. The PIT partition can be created via Heimdell but everytime i try to install the bootloader it got stuck. Please help me . Thank you in advance.
[Captivate Android Development] mrhaley30705:
Use the i897 GB bootloader link in my sig. Same as Cezars, but set up to be used with full Odin. Just put the pda.tar.md5 file in the pda slot.
[Captivate Android Development] guilleglad:
Stuck Again :(

<ID:0/019> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> PDA.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/019> Odin v.3 engine (ID:19)..

<ID:0/019> File analysis..

<ID:0/019> SetupConnection..

<ID:0/019> Initialzation..

<ID:0/019> Set PIT file..

<ID:0/019> DO NOT TURN OFF TARGET!!

<ID:0/019> Get PIT for mapping..

<ID:0/019> Firmware update start..

<ID:0/019> boot.bin

Stuck Again :( i don't know what is wrong. The difference now is that the blue progress bar is full now but still stuck. this happened when i tried to install UCJF6 it screwed up my bootloaders :( now i dont know what to do :(