Database Develop

[Q] GT-I9000 bootloader on Captivate?

Hi guys,
Can anyone tell me how to remove a bootloader or switch it to another bootloader?
I accidently flashed GT-I9000 bootloader onto my captivate and now my phone thinks that it's GT-I9000.
In bootup, a screen of "Galaxy GT-I9000 Samsung" stays on for 5 sec, and then AT&T logo&animation shows up after that.
Below is the full explanation how I ended up with this situation. It's kinda long, so if you know the solution to this problem right away, I guess you don't need to read all of it.
Anyways, thanks in advance!
So Here's what happened. I was upgrading my (rooted/froyo) captivate to gingerbread (continuum v5.4.1) In the instruction, it suggested to return to stock so I did that and my phone went back to eclair.
Then there was another optional suggestion saying that "only if you don't have bootloaders - install JVB bootloaders" and that's where my problem began.
I downloaded the 'galaxys-bootloader-JVB.tar.md5' and flashed it in Odin and my phone now thinks that it's GT-I9000. For a moment, I thought my phone was bricked, but I managed to turn it back to 2.1.
but still whenever I turn on my phone the 'Galaxy S GT-I9000 Samsung' screen shows up for like 8 seconds and then move onto AT&T screen.
Phone still operates and runs on eclair, but funny thing is every time I want to use "download mode" I have to press 'Volume down key + power, which is for Vibrant or Fascinate, instead of holding both volume up + down keys, which is for Captivate.
Same thing for "recovery mode" I have to press down VOL down + power button. This clearly shows that the phone thinks it's Vibrant, not Captivate.
Please Please Please can anybody tell me how to revert it?

samzoferrari said:
Hi guys,
Can anyone tell me how to remove a bootloader or switch it to another bootloader?
I accidently flashed GT-I9000 bootloader onto my captivate and now my phone thinks that it's GT-I9000.
In bootup, a screen of "Galaxy GT-I9000 Samsung" stays on for 5 sec, and then AT&T logo&animation shows up after that.
Below is the full explanation how I ended up with this situation. It's kinda long, so if you know the solution to this problem right away, I guess you don't need to read all of it.
Anyways, thanks in advance!
So Here's what happened. I was upgrading my (rooted/froyo) captivate to gingerbread (continuum v5.4.1) In the instruction, it suggested to return to stock so I did that and my phone went back to eclair.
Then there was another optional suggestion saying that "only if you don't have bootloaders - install JVB bootloaders" and that's where my problem began.
I downloaded the 'galaxys-bootloader-JVB.tar.md5' and flashed it in Odin and my phone now thinks that it's GT-I9000. For a moment, I thought my phone was bricked, but I managed to turn it back to 2.1.
but still whenever I turn on my phone the 'Galaxy S GT-I9000 Samsung' screen shows up for like 8 seconds and then move onto AT&T screen.
Phone still operates and runs on eclair, but funny thing is every time I want to use "download mode" I have to press 'Volume down key + power, which is for Vibrant or Fascinate, instead of holding both volume up + down keys, which is for Captivate.
Same thing for "recovery mode" I have to press down VOL down + power button. This clearly shows that the phone thinks it's Vibrant, not Captivate.
Please Please Please can anybody tell me how to revert it?
Click to expand...
Click to collapse
Odin3 one click back to stock. Your fine that's just the kernel bootloader. If you want continuum it will have the GT-I9000 bootloader, but there are other roms and kernels without it. The odd button combinations you have to use are part of the kernel as well. Flash stock then I suggest flashing Cognition after if it will not revert to stock kernel. You can flash froyo over eclair without having to update bootloaders. Also if your running a AT&T Captivate you should be having that boot animation before the GT-I9000 anyways. Sorry if this doesn't help your problem.

thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.

First, the new button combos are not part of the kernel. They are part if the secondary bootloader. If you think you are going to flash another gingerbread rom in the future, just leave it as is. They are compatible with 2.1/2.2 roms, with the exception of Cognition. DO NOT FLASH COGNITION UNTIL YOU ARE 150% CERTAIN YOU HAVE FROYO/ECLAIR BOOTLOADERS. The reason is, cog adds a secondary bootloader(sbl.bin) to its flash. If you try mixing aGB primary bootloader with a froyo secondary, you will have a permanent, can't recover, $500 paperweight, brick. Also, do not try to use the odin with 3 button fix, for the same reason above.

mrhaley30705 said:
First, the new button combos are not part of the kernel. They are part if the secondary bootloader. If you think you are going to flash another gingerbread rom in the future, just leave it as is. They are compatible with 2.1/2.2 roms, with the exception of Cognition. DO NOT FLASH COGNITION UNTIL YOU ARE 150% CERTAIN YOU HAVE FROYO/ECLAIR BOOTLOADERS. The reason is, cog adds a secondary bootloader(sbl.bin) to its flash. If you try mixing aGB primary bootloader with a froyo secondary, you will have a permanent, can't recover, $500 paperweight, brick. Also, do not try to use the odin with 3 button fix, for the same reason above.
Click to expand...
Click to collapse
Secondary as in the 3rd animation because I highly doubt that.You should have an AT&T screen, then your galaxy s bootloader, then your rom bootloader. the rom bootloader animation is changable and does not include the power button volume up combo. I'm not a developer, but based on my experience you CAN use odin with 3 button fix over contiuum and then flash cognition after. I highly doubt there will be a brick. For example, you want the new cm7 build. You can flash odin 3 button, flash cmw through rom manager or a zip with 2e recovery. Then flash cognition. you are at the 2.2 bootloader now. You can now begin to work towards the 2.3.4 without any issues. And there are different requirements for different gingerbread roms. some are 2.3.3 and some are 2.3.4 and you CAN NOT flash between the two.

samzoferrari said:
thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
Click to expand...
Click to collapse
It's no big deal don't let this guy make you think your about to brick if your not 150% sure. There are also different bricks and this could cause a soft which is also recoverable by odin.

thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
Click to expand...
Click to collapse
Just for safety's sake, though, it would probably be good to read through this before moving forward:
The Definitive Guide to Bricking

jmtheiss said:
Just for safety's sake, though, it would probably be good to read through this before moving forward:
The Definitive Guide to Bricking
Click to expand...
Click to collapse
That guide knows a lot more then I do. I suggest reading that aswell! I was speaking strictly based on experience.

If you attempt to flash the 3 button fix with gb bootloaders, you will brick. Go ask any one in gb rom forum. If you reflash froyo bootloaders, to replace gb bootloaders, before you flash 3 button, you should be ok. But if you choose to believe the other guy, and your still under warranty, tell att that your phone stopped working when you tried to update with kies.

EsotericSYN said:
Secondary as in the 3rd animation because I highly doubt that.You should have an AT&T screen, then your galaxy s bootloader, then your rom bootloader. the rom bootloader animation is changable and does not include the power button volume up combo. I'm not a developer, but based on my experience you CAN use odin with 3 button fix over contiuum and then flash cognition after. I highly doubt there will be a brick. For example, you want the new cm7 build. You can flash odin 3 button, flash cmw through rom manager or a zip with 2e recovery. Then flash cognition. you are at the 2.2 bootloader now. You can now begin to work towards the 2.3.4 without any issues. And there are different requirements for different gingerbread roms. some are 2.3.3 and some are 2.3.4 and you CAN NOT flash between the two.
Click to expand...
Click to collapse
Cm7 doesn't use gb bootloaders

Please don't double post.

Miami_Son said:
Please don't double post.
Click to expand...
Click to collapse
I apologize. The tone conveyed by the person I was responding to simply infuriated me. I do know better, just lost it for a second.

Flashing a New rom from Mosaic II
mrhaley30705 said:
Cm7 doesn't use gb bootloaders
Click to expand...
Click to collapse
So not to dig up an old post, but I guess I will...
I am running
Mosaic II
Kernel 2.6.35.7-I9000XWJVB-CL118186
2.3.3
So basically in the same boat as the OP. Running GB boot loaders for the I9000, I'm ready for a new ROM and for the first time I'm worried about a perma brick.
I am wanting to load up CyanogenMod 7
http://forum.xda-developers.com/showthread.php?t=978150
What do I need to do abt the boot loaders, can I leave them and just flash with ClockworkMod Recovery?
Thanks!
JP

Don't **** with the bootloaders. flash back and keep them stock. It's risky and unneeded. Flashing them for ANY ROM is retarded. The developers who require this are retarded. RETARDED.
The only reason to upgrade bootloaders is for the unofficial 2.3 upgrade... Which is likely laziness on Samsung's part. Do not go flashing a SBL without a PBL ever. This is bad practice and can only lead to several bricks when a SBL is released without a matching PBL. The developers who require flashing a SBL without a PBL are retarded. RETARDED.
Yep. I said it, we have retarded developers here in the forums who should be stripped of their recognized tag.

OK on the subject but not so much.... Is there a code or system manager (like sgs tools) that indicates what BL you have installed?
Or does the kernel spell that out for you? ex. Kernel version 2.6.35.7-i9000xxjvr-clCL425308 Would this indicate a i9000 BL?
I notice on the rom I use, people are asking constantly which BL is the right one!
I understand both have their + & - but there must be a way of finding which one is installed, through the phone

tomween1 said:
OK on the subject but not so much.... Is there a code or system manager (like sgs tools) that indicates what BL you have installed?
Or does the kernel spell that out for you? ex. Kernel version 2.6.35.7-i9000xxjvr-clCL425308 Would this indicate a i9000 BL?
I notice on the rom I use, people are asking constantly which BL is the right one!
I understand both have their + & - but there must be a way of finding which one is installed, through the phone
Click to expand...
Click to collapse
Hold Vol - and Power for about 10 seconds. If you reboot to download, you have the I9000 GB bootloaders. That's at least one variable eliminated.
If, after doing that, you realize you're on a Gingerbread rom without issues and the button combo does nothing, you have the i897 GB bootloaders.

jmtheiss said:
Hold Vol - and Power for about 10 seconds. If you reboot to download, you have the I9000 GB bootloaders. That's at least one variable eliminated.
If, after doing that, you realize you're on a Gingerbread rom without issues and the button combo does nothing, you have the i897 GB bootloaders.
Click to expand...
Click to collapse
Sorry should have stipulated.... other then the step you've mentioned.
I was looking to see if anyone has created a script or app that can tell you this

[Q] GB Bootloaders

I am running Cog 5B2. It has the captivate GB bootloaders. If i want to change to a i9000 GB rom say Apex do I need to change bootloaders or will the GB captivate ones work?

No you do not need to change bootloaders to go to any other gb rom. Plus I've read on here that the gb bootloaders are backwards compatible with froyo/eclair though I have not confirmed that yet myself.

So there really is no need to ever flash bootloaders again.

I wouldn't say never. But it is good to avoid flashing bootloaders if possible, if something goes wrong flashing bootloaders can result in an actual bricked phone.
On the other hand just flashing roms, kernels and modems sans bootloaders the worst you can likely do is get into soft brick situation or a bootloop which can be easily fixed.

Yup I flashed Serindipty7 right on top of cog 5.2 and then Mosaic V right on top of that no issues to report just make sure you wipe data factory reset before. I haven't flashed anything that has the talon kernel, but still no need to flash bootloaders
Sent from my phone on vacation

Keep it mind GB bootloaders are not backwards compatible with all of them. I know that CM7 does not work with GB bootloaders.

I prefer the I9000 gb bootloaders. They both work the same but The captivate ones have the same button combos which I've always thought were really stupid. The I9k's combos are just more intuitive and simplistic the way they should have always been if you ask me.
Vol up + power = recovery
Vol down + power = download
Nice
Clean
Simple

Well turns out going from Cog5b2 to OBSSESSION puts you in a bootloop. Reflashing Cog I guess for now.

vdubguy said:
Well turns out going from Cog5b2 to OBSSESSION puts you in a bootloop. Reflashing Cog I guess for now.
Click to expand...
Click to collapse
Try flashing to stick KF1 before flashing a new rom (there is a 1 click without bootloaders to minimize risk)

I haven't still figured out a reliable way to flash back to Stock Froyo on my 2 captivates which ended up being bricked. I was on Cezar's 897 GB bootloaders. Tried flashing back to Froyo KB1 from here but it failed using Odin3 1.3. I got a new phone, which now has stock KB2. Does anyone know how to flash stock Froyo reliably ?

prbassplayer said:
Try flashing to stick KF1 before flashing a new rom (there is a 1 click without bootloaders to minimize risk)
Click to expand...
Click to collapse
Really didn't know there was a 1 click without bootloaders. Time to hit up the search!

vdubguy said:
Well turns out going from Cog5b2 to OBSSESSION puts you in a bootloop. Reflashing Cog I guess for now.
Click to expand...
Click to collapse
I read someone have similar issue and I was also on cog5b2 and followed their instructions (which I'm going to paraphrase now) and worked perfectly. I'm now running Mosaic V with the KF1/i897 boot loaders...
OP on Mosaic V has link for xcal's 1.2 i9000 kernel.tar download that. Start at step 5 on that OP, use Odin 1.7 (linked as 'Files you will need' in the MV OP) to flash xcal's kernel, make sure to not auto reboot from Odin and when it's done flashing kernel, do a battery pull and then go to recovery mode, factory reset and then flash Obsession.
Sent from my GT-I9000 using XDA App

vdubguy said:
Really didn't know there was a 1 click without bootloaders. Time to hit up the search!
Click to expand...
Click to collapse
This is KF1 without Bootloaders

Madtowndave said:
I read someone have similar issue and I was also on cog5b2 and followed their instructions (which I'm going to paraphrase now) and worked perfectly. I'm now running Mosaic V with the KF1/i897 boot loaders...
OP on Mosaic V has link for xcal's 1.2 i9000 kernel.tar download that. Start at step 5 on that OP, use Odin 1.7 (linked as 'Files you will need' in the MV OP) to flash xcal's kernel, make sure to not auto reboot from Odin and when it's done flashing kernel, do a battery pull and then go to recovery mode, factory reset and then flash Obsession.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Cool Thanks everyone for the help. I may try Obsession again tomorrow. Gotta hit the sheets....and up early for work.

Srikar_NBK said:
I haven't still figured out a reliable way to flash back to Stock Froyo on my 2 captivates which ended up being bricked. I was on Cezar's 897 GB bootloaders. Tried flashing back to Froyo KB1 from here but it failed using Odin3 1.3. I got a new phone, which now has stock KB2. Does anyone know how to flash stock Froyo reliably ?
Click to expand...
Click to collapse
this is the recommended way to go back to stock that contains both main and secondary bootloaders http://forum.xda-developers.com/showthread.php?t=731989
also this one which contains no bootloaders http://forum.xda-developers.com/showthread.php?t=995143

CremeFraiche said:
this is the recommended way to go back to stock that contains both main and secondary bootloaders http://forum.xda-developers.com/showthread.php?t=731989
also this one which contains no bootloaders http://forum.xda-developers.com/showthread.php?t=995143
Click to expand...
Click to collapse
Yes, but aren't both of them methods to go back to Eclair and not Froyo ? My earlier Cappy got bricked bcoz I tried stocking back to Eclair, when it came with Froyo.

My question is how do you flash custom rom while on kf1 boots? Running cog 5 beta 2 with cwm4. Can I flash roms like I did before via cwm, even though I'm on cwm4, or should I flash a kernel with cwm 2 or cwm3 first, than flash rom thru that?. This question is for both froyo and GB/i9000 roms
Sent from my SAMSUNG-SGH-I897 using XDA App

Cdub3 said:
My question is how do you flash custom rom while on kf1 boots? Running cog 5 beta 2 with cwm4. Can I flash roms like I did before via cwm, even though I'm on cwm4, or should I flash a kernel with cwm 2 or cwm3 first, than flash rom thru that?. This question is for both froyo and GB/i9000 roms
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Well most roms have a Kernel that they recommend. Best I can figure if you want to flash a froyo rom go back down to stock eclair with one click (don't flash bootloaders) and flash rom of your choice. For GB just flash stock KF1 and flash gb rom? That's just me guessing though.

prbassplayer said:
Well most roms have a Kernel that they recommend. Best I can figure if you want to flash a froyo rom go back down to stock eclair with one click (don't flash bootloaders) and flash rom of your choice. For GB just flash stock KF1 and flash gb rom? That's just me guessing though.
Click to expand...
Click to collapse
Oneclick eclair contains bootloaders.
To simplify my question, are rom flashes compatible with cwm4, or do I need cwm2/or 3 to flash roms, whether froyo/GB?
Sent from my SAMSUNG-SGH-I897 using XDA App

Cdub3 said:
Oneclick eclair contains bootloaders.
To simplify my question, are rom flashes compatible with cwm4, or do I need cwm2/or 3 to flash roms, whether froyo/GB?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
JF6 is eclair is it not? If it is here is a JF6 odin with out bootloaders. If Jf6 is Froyo well my mistake. Still 2.2 stock would still work i think. Point is cmw version wont matter if you go back to stock and flash from there, and its usually a better idea to flash to stock anyways.

3 button fix?

I'm new to the Captivate. Coming from Xperia x10, this phone is alien to me in regards to installing custom roms. I've been reading and apparently I need the 3 button fix because I can't get into Recovery mode without Rom manager. All the download links I've found are broken. Where can I get it? Is this even necessary? Has there been a more recent fix?

use adb and buy or make a usb jig for your phone to have incase. Its best to just avoid using the 3-button fix as it has broken a lot of cappys.

I will say flash a GB Rom for that u will need GB bootlaoders when u flash the GB Bootloaders it will fix ur 3 button combo, Gor flashing a GB rom you need the DL mode that can be achieved though ADB or a Jig.
But remember do not flash the 3 button fix over it.

xArtanis said:
I'm new to the Captivate. Coming from Xperia x10, this phone is alien to me in regards to installing custom roms. I've been reading and apparently I need the 3 button fix because I can't get into Recovery mode without Rom manager. All the download links I've found are broken. Where can I get it? Is this even necessary? Has there been a more recent fix?
Click to expand...
Click to collapse
Read well on each and every rom you want to use. IF you are inclined on flashing a GB rom with bootloaders I recommend this one. Run it as Admin put your phone in download mode. click start and you should be on 2.3.3 with bootloaders and 3button fix. Flashing bootloaders carries risk on hard bricking, and DO NOT flash the "3 button fix" if you are on GB bootloaders.

Just don't flash the 3 button lol its evol
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.

xijar said:
Just don't flash the 3 button lol its evol
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
Its not evil its just outdated. It was used pre GB bootloaders. Its ment to fix the 3 button issue by JUST flashing a secondary bootloader. Now that we have GB bootloaders people think they need the "fix" and end up mismatching a GB primary bootloader and a eclair/froyo secondary bootloader creating a very expensive paper weight.

Meh can still jtag. Not too expensive and gets the phone going again. I understand why the fix breaks phones I just think its best to stay away from it since adb + jig work without it.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.

xijar said:
Meh can still jtag. Not too expensive and gets the phone going again. I understand why the fix breaks phones I just think its best to stay away from it since adb + jig work without it.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
Ive read issues with ADB and CM7 based roms not working properly though. But I dislike AOSP roms on captivate, haven't had great experiences with them. But thats just personal observation. Although I quoted you my explanation was directed at OP sorry if that was confusing, just noticed it xD

xijar said:
Meh can still jtag. Not too expensive and gets the phone going again. I understand why the fix breaks phones I just think its best to stay away from it since adb + jig work without it.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
Adb doesn't work in all states such as a soft brick when you would need it.
And a jig only boots to download mode, meaning something that could have been fixed by a cwm flash is now a flash to stock using odin. And THEN the custom rom you could've flashed if your combos worked...
The aio toolbox has the 3 button fix, if you don't plan on flashing gingerbread any time soon then use that.
JUST DO NOT USE IT ONCE YOU'VE MADE THE JUMP TO GINGERBREAD. Unless first using odin one click jf6, that replaces both bootloaders with eclair ones, first.

Is risky applied this fix? If i have a jig, can i avoid try this fix rigth?

Darkuso said:
Is risky applied this fix? If i have a jig, can i avoid try this fix rigth?
Click to expand...
Click to collapse
Keel in mind you wont be able to reach recovery, jig only gets you in download mode. As ti risk flashy any type of bootloaders carries some risk for a hard brick. Id recommebd GB bootloaders and just forget about bootloaders. Just my 2 cents. But like always read read read =)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

studacris said:
Adb doesn't work in all states such as a soft brick when you would need it.
And a jig only boots to download mode, meaning something that could have been fixed by a cwm flash is now a flash to stock using odin. And THEN the custom rom you could've flashed if your combos worked...
The aio toolbox has the 3 button fix, if you don't plan on flashing gingerbread any time soon then use that.
JUST DO NOT USE IT ONCE YOU'VE MADE THE JUMP TO GINGERBREAD. Unless first using odin one click jf6, that replaces both bootloaders with eclair ones, first.
Click to expand...
Click to collapse
That's because THOSE gingerbread bootloaders are not for our phones. Tell whoever your ROM developer is to change his methods. He's causing bricks.

AdamOutler said:
That's because THOSE gingerbread bootloaders are not for our phones. Tell whoever your ROM developer is to change his methods. He's causing bricks.
Click to expand...
Click to collapse
So it won't brick with kf1 pbl mixed with a froyo (kb1) sbl?

studacris said:
So it won't brick with kf1 pbl mixed with a froyo (kb1) sbl?
Click to expand...
Click to collapse
Never mix bootloaders and never run bootloaders which are not for your phone. That's how you end up with a brick.

AdamOutler said:
Never mix bootloaders and never run bootloaders which are not for your phone. That's how you end up with a brick.
Click to expand...
Click to collapse
Good to know this, question: that is why u and ur team made andromeda3 in froyo? is safer stay with those bootloaders?

Andromeda is based off of the armani source code, which a gingerbread source has not been released for. So they haven't updated it.
But yes it is safer to never flash bootloaders as that is the only time you risk a brick. So if you never touch them you have a very tiny chance of ever bricking as it would be a hardware malfunction that would not allow you to flash out of a "soft brick" Such as a broken usb port...

Darkuso said:
Good to know this, question: that is why u and ur team made andromeda3 in froyo? is safer stay with those bootloaders?
Click to expand...
Click to collapse
Andromeda (in all its renditions up to and including 3) were based on Froyo because GB wasnt even a spec on the map for Galaxy S devices when it began life.
If we see some Armani source drop, we will work on a GB version, but we decided to stick true to the game and only work on armani source.
some of us have other projects we work on outside of a teamkomin build.

Pirateghost said:
Andromeda (in all its renditions up to and including 3) were based on Froyo because GB wasnt even a spec on the map for Galaxy S devices when it began life.
If we see some Armani source drop, we will work on a GB version, but we decided to stick true to the game and only work on armani source.
some of us have other projects we work on outside of a teamkomin build.
Click to expand...
Click to collapse
Right. Like my heimdall one-click project is designed to take the guesswork out of flashing for noobs. If you stick with one-clicks for your device, then you are using proper firmware which has been tested or at least pre-paired by someone for your device. It's not a Team project.

Going from i9000 to Captivate GB ROM? Bootloaders?

I'm planning on going from JVS to KH3 or KI2 but really don't feel like ODIN'ing back to stock. I know issues could arise if I just flash the i897 Rom over JVS due to bootloaders.
Any way to do this and get the Captivate GB bootloader without wiping with ODIN?

The only confirmed issue I've seen is that the I897 GB Bootloaders break the I9000 Music player. You should be fine just flashing whatever ROM with your current Bootloaders just do the typical clearings/wipes. Might have issues with the music player but that's easily fixed.

I did the same thing you're hoping to do, but all I did was ODIN the I897 BLs. No back to stock, nothing, just the BLs. I did it with the Pinnacle or Apex flasher package (can't remember which one right now). Worked like a charm.

This is Just the I897 GB bootloaders

edtonn said:
I did the same thing you're hoping to do, but all I did was ODIN the I897 BLs. No back to stock, nothing, just the BLs. I did it with the Pinnacle or Apex flasher package (can't remember which one right now). Worked like a charm.
Click to expand...
Click to collapse
Fix you flash the BL prior to the new ROM or after?
Thanks for the replies!
I don't think my phone gets along with JVS so well...

Either way is fine, before or after.

qwertyaas said:
Fix you flash the BL prior to the new ROM or after?
Thanks for the replies!
I don't think my phone gets along with JVS so well...
Click to expand...
Click to collapse
studacris said:
Either way is fine, before or after.
Click to expand...
Click to collapse
Agree with studacris—order doesn't matter. My experience was flashing the I897 BLs while still on Apex, then waited for the Pinnacle 1.3 update and flashed the ROM.

Best way to do this? Bootloaders...

I'm pretty confident at modding my phone, and have basically done everything that doesn't involve messing with odin or bootloaders. However, I would like to upgrade to GB bootloaders, mainly for features in the new glitch kernel (and perhaps better performance in some way). And yes, I have searched and read many threads on this, but there are so many different options and many things seem irrelevant. I am on CM7 Glitch v13, and I'm not sure what the best path is.
First of all, what stock firmware do I go to? There are so many, and I would assume something 2.3.x. But which? And I would assume with bootloaders? Once I get there, I would be able to figure out getting CWM. I think. But I'm mainly concerned about which stock firmware to pick. Thanks!

Look for the kf1 one-click. Can't get any easier.
Sent from my I9000 using xda premium

mbc663 said:
Look for the kf1 one-click. Can't get any easier.
Click to expand...
Click to collapse
Ummm yes it can
You can flash the bootloaders only right over top cm7.

studacris said:
Ummm yes it can
You can flash the bootloaders only right over top cm7.
Click to expand...
Click to collapse
I've never had any luck trying that. Usually end up bootlooping.

mrhaley30705 said:
I've never had any luck trying that. Usually end up bootlooping.
Click to expand...
Click to collapse
I heard that that's what happens. By usually, do you mean it can sometimes work? How would you recover
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate

korockinout13 said:
I heard that that's what happens. By usually, do you mean it can sometimes work? How would you recover
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Click to expand...
Click to collapse
Put phone in dl mode and flash stock. Just back everything up before you start. Some have reported that it's worked for them, but most havesended up looping. I personally have looped the last time
I tried it.

Yahh flashing BL while on a MTD partitioned ROM will not work, have to be on BML(STOCK ROM)

b-eock said:
Yahh flashing BL while on a MTD partitioned ROM will not work, have to be on BML(STOCK ROM)
Click to expand...
Click to collapse
Yeah that's what I thought. I saw your posts in the ICS thread. Thanks
EDIT: But wait, do I need to go back to stock froyo first or can I go straight on to KF1?

I would go to froyo first, then the kf1. Just to be safe, and you ALWAYS want to be as safe as possible with bootloaders.

mrhaley30705 said:
I would go to froyo first, then the kf1. Just to be safe, and you ALWAYS want to be as safe as possible with bootloaders.
Click to expand...
Click to collapse
I did that, but I never went to kf1. I followed some other guide that installed speedmod and GB bootloaders, and am now back on CM7 after flashing froyo again. That was much easier than I expected.
NOW: Crap, no matter what I do, I can't get signal. I get no SIM passcode prompt, and my imei is unknown. What now?
NOW: Well it works on stock Froyo, but no connection on CM7