Database Develop

Captivate not Turning On

I installed speedmod kernel and perception 10.4 together in CWM. And i tried to restart the phone but it won't start. Screen doesn' t even light up. What do i do now ??? I have no warranty either.
If there is nothing that could be done is there a place to sell it for some bucks ??

You have a bricked bootloader which can be fixed through JTAG restoration. If you are interested just PM me. Same goes for anybody else in this situation...

Yes please. Let me know. I am dying to turn this on again. Thanks.

i am just wondering what exactly you did. by 10.4 do you mean the 2.3.3 perception beta that came out on the 10th of april or some other 10.4 version. if it was the perception 2 beta thats a 2.3.3 (or 2.3.4 cant remember) whereas speedmod kernal is for the original bootloaders and 2.1 and 2.2 you cant mix and match like that. and before you go and buy a jig from the guy above realize that your original 3 button combos arent the same as the ones from g12. try holding volume down the home soft key and power or volume up and power. if clock work (up and power) works then reflash g12 if download workd (android and shovel) plug it into computor and flash to stock using oden. if NONE of these things work buy the jug or buy a 301ohm resistor and build it yourself theres lots of tutorials

Perception 10.4 is the most stable version of FroYo perception.
Installing that after running GB without reinstalling the 2.1/2.2 bootloaders will brick. But if you never installed GB, or installed the 2.1/2.2 bootloaders first then your problem is elsewhere.
What were you running before you installed perception + speedmod? I'm guessing GB ROM of some flavor. If not, then it shouldn't be a bootloader issue.
Sent from my Captivate running GR-12

quarlow said:
Perception 10.4 is the most stable version of FroYo perception.
Installing that after running GB without reinstalling the 2.1/2.2 bootloaders will brick. But if you never installed GB, or installed the 2.1/2.2 bootloaders first then your problem is elsewhere.
What were you running before you installed perception + speedmod? I'm guessing GB ROM of some flavor. If not, then it shouldn't be a bootloader issue.
Sent from my Captivate running GR-12
Click to expand...
Click to collapse
Does perception have a froyo sbl.bin? Otherwise just flashing a froyo rom will not result in a hard brick at all. Gingerbread bootloaders are backward compatible as long they both match ... So if perception doesn't have any bootloaders at all and not just the froyo secondary bootloader it should be fine to flash from gingerbread. As long as you flash it from cwm 2.5 because cwm3 doesn't seem to want overwrite the kernel, but that won't even cause a hard brick just a bootloop, so you could odin a kernel after that and be golden.
the only thing that will cause a hard brick is either a plane old bad write/disconnection while the bootloaders are flashing. Which means, are you ready for a jaw dropper? odin one click is just as dangerous as flashing gingerbread!!!
Or now that there are new bootloaders the mixing if primary of froyo and secondary of gingerbread.

studacris said:
Does perception have a froyo sbl.bin? Otherwise just flashing a froyo rom will not result in a hard brick at all. Gingerbread bootloaders are backward compatible as long they both match ... So if perception doesn't have any bootloaders at all and not just the froyo secondary bootloader it should be fine to flash from gingerbread. As long as you flash it from cwm 2.5 because cwm3 doesn't seem to want overwrite the kernel, but that won't even cause a hard brick just a bootloop, so you could odin a kernel after that and be golden.
the only thing that will cause a hard brick is either a plane old bad write/disconnection while the bootloaders are flashing. Which means, are you ready for a jaw dropper? odin one click is just as dangerous as flashing gingerbread!!!
Or now that there are new bootloaders the mixing if primary of froyo and secondary of gingerbread.
Click to expand...
Click to collapse
DG has been known in the past to package sbl.bin's in his ROM's. I'd suspect a 2.1/2.2 sbl.bin was flashed with the 2.3 boot.bin. That will equal brick every time.

connexion2005 said:
You have a bricked bootloader which can be fixed through JTAG restoration. If you are interested just PM me. Same goes for anybody else in this situation...
Click to expand...
Click to collapse
He is the man. He fixed it for me. Unbricked it. You can trust him..

[Q] Odin one-click softbricks my phone

I'm having a bit of trouble with Odin one-click. Last night I decided to upgrade from Perception 10.4 (Froyo based) to Perception 2b3 (Gingerbread based). I plugged it in, put it into download mode, and activated Odin. It ran just fine, but at the end, my phone rebooted into a boot loop. I ended up putting together a jig to get it back into download mode, and tried again. Same thing happened. I eventually ended up using a Froyo Odin to qwerty least get it working again. Does anyone have any ideas as to why Gingerbread Odin soft bricks my phone, and what I should do to fix it? Let me know if you need any more details. Thanks in advance.

I know this would do better in the odin thread, but I don't have enough posts to post there, mending the fact that I've been lurking around for close to a year

Guess I'll just keep posting here until a) someone responds or b) I have enough posts to ask in the proper thread

I'd ready like to be able to get my cappy running Gingerbread tonight. Anyone have any ideas?

What one click are you taking about? Is it this one?
http://forum.xda-developers.com/showthread.php?t=731989
If it is, this will take you to stock eclair. Not sure what ur talking about with one click froyo. There is a one click GB from Design Gears in the development section. It flashes the newest release of GB stock. If you can get into dl mode you can flash either of the one click odins, but read about both before you do. Bootloaders are involved, and if you don't know about them they can be trouble. Read in development section.
This is a link to one click for GB stock. CONTAINS BOOTLOADERS.
http://forum.xda-developers.com/showthread.php?t=1127249
Sent from my SAMSUNG-SGH-I897 using XDA App

Sorry, for some reason can't get that second link to work properly. Doing this from my phone. Just type in the url. If you decide to flash this GB oneclick, you'll be on the kf1 "official" release. Check dev section and you can flash beta cognition if you want. People are having great results with this rom, including myself. Good luck.
Sent from my SAMSUNG-SGH-I897 using XDA App

I recommend flashing the KF1 odin one-click. I just flashed that one, and it worked like a champ. Its in the Continuum v6 thread at http://forum.xda-developers.com/showthread.php?t=1136128. If you read the instructions it will work flawlessly. The only odin problems I've ran into have been user induced.

Okay, I'll try out that KF1. All I really need it for is to get the bootloaders so I can install other 2.3 roms. Will this work for that?
The Froyo Odin I was tackling about was just an older version, I think.
Edit: Why is it so much more difficult to go from 2.2 to 2.3 than it was going from 2.1 to 2.2? Upgrading to 2.2, I just had to use CWM to flash the new rom onto the phone.

Okay, I was trying to follow the instructions in the Continuum thread, and it looks like I am supposed to go back to Eclair before flashing Continuum. I was using this one-click Odin, and it was causing my phone to softbrick. No idea why. Will I be able to use that KF1 Odin to get to Gingerbread, then flash other GB based roms?
And by the trouble caused by bootloaders, you just mean how it will hardbrick if it loses connection in the middle of flashing, right? Or is there more. I've been switching out roms on phones for a while now, but it hasn't been this complex before...

If you mix bootloaders, you will hard brick ur phone. 2.1/2.2 roms have the same bootloaders. GB boots are different. That's why there is more involved to flash GB roms. Basically all the GB roms are I9000 based roms. The kf1 is an i897 based stock rom. If you flash kf1 stock rom, you will lose cwm. You can try cog beta 2 rom if you would like. After following steps to flash GB bootloaders with link mentioned above, check dev section. There are currently 2 kf1 custom roms. I use the cog beta 2, and it works great. people have mentioned that they have flashed i9000 roms over kf1, but I personally haven't, cuz so far cog beta is working great and the call quality is outstanding compared to any of the i9000 roms. Read read read read, before taking any steps. You don't want to ruin it phone! If you want to flash i9000 based GB, read this:
http://forum.xda-developers.com/showthread.php?t=1045734
Btw, what build is ur phone? (4 digit number under battery). Some builds, especially 1010 have trouble with oneclick.
Sent from my SAMSUNG-SGH-I897 using XDA App

So it sounds like what I need to do is use that KF1 Odin, then I can flash other roms over that? How can I tell which custom roms are KF1? Is Perception KF1 based? What would you recommend I read to make sure I'm doing it right? Are there specific threads that are especially helpful for this? Thanks for all of the help, I'd really like to learn how to do this.

It'll say in the title. Liked I said, currently there are only two kf1 based roms. Cog beta and another one that I can't remember the name of. If it says something in the title besides kf1/or i897, it's for i9000. Ex/ jvh, jvo, jvp are all i9000 based.
Sent from my SAMSUNG-SGH-I897 using XDA App

What do I need to do if I want to use a non-KF1 based GB rom? I've been very happy with Perception, and I'd like to keep using it.

If you want to flash GB stock that is based off of I9000 read and follow this, step by step:
http://forum.xda-developers.com/showthread.php?t=1045734
After you do this you can flash GB roms via cwm.
If you want to flash GB with kf1, you can, and people have been running I9000 based custom roms on the same bootloaders. JUST MAKE SURE YOU CHECK ANY ROM YOU'RE FLASHING TO SEE IF IT INCLUDES BOOTLOADERS. I personally haven't run any I9000 roms after flashing kf1, but I believe if you want to do this, (NOT POSITIVE ABOUT THIS, SO YOU MIGHT WANT TO RESEARCH THIS FIRST) you would have to flash an appropriate I9000 kernel using odin (not oneclick, but the full version). Put the kernel in the PDA slot, uncheck repartition, and auto reboot and flash. That way you will get cwm 2 or3 back which will enable you to flash the rom you want. (Remember, with stock KF1 you lose cwm). After kernel flashes, boot ONLY into recovery, and flash rom that you put on your SD card before doing any of this, and flash via cwm. AGAIN, NOT POSITIVE THIS IS WHAT YOU DO, SO RESEARCH.

That makes a lot more sense than the instructions I was trying to follow. I'll try that in a bit.

It worked! Thanks for all of your help

What did you end up doing? GB I9000 stock, or kf1 then flash I9000 custom rom over it?
Sent from my SAMSUNG-SGH-I897 using XDA App

I used the I9000 GB stock rom from that link you posted, then flashed a custom rom over it. I ended up using Perception 2 beta.

Glad it worked for you.
Sent from my SAMSUNG-SGH-I897 using XDA App

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.

[Q] What Bootloaders?

1st I'm a total noob!
So, I recently got a I897 with FROYO 2.2 on it from AT&T as an upgrade. It's my first Android (and my 1st smartphone for that matter)
I bricked it a couple of times, bought a jig then managed to successfully follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1127249
AND I got it rooted via the same post's instructions.
Now my phone shows:
SAMSUNG-SGH-I897
2.3.3
I897UCKF1
2.6.35.7-I897UCKF11-CL2373832
GINGERBREAD.UCKF1
What I don't know is am I running GB on the FROYO boot loaders?
And, should I update the boot loaders as described in this post:
http://forum.xda-developers.com/showthread.php?t=1129821
???
I'm wanting to upgrade the Kernel to KJ3 or maybe KK1...
Advice?
Thank You In Advance For Your Response!

My guess is (and it's just a guess) that since you're running a Gingerbread rom, you have Gingerbread bootloaders.
V V V Froyo bootloaders will boot into gingerbread. The kernel splash will be broken and recovery is unaccessable.
That being said, leave the bootloaders alone. At this point, there are really no reasons to touch them again except in extreme circumstances (warranty return, some future update that has new bootloaders like ICS).

^^^Froyo bootloaders will boot into gingerbread. The kernel splash will be broken and recovery is unaccessable.
Op, When you boot up do you get a weird screen that looks like white noise? If so you have froyo bootloaders, if all looks ok then they are gingerbread.

My guess is that the one click you used included the boot loaders. Don't remember ever seeing a one click without them.
Sent from my SAMSUNG-SGH-I897 using XDA App

When I boot up I get the AT&T screen, followed by a lock screen that tells me there's no sim card installed... (This phone is for playing with... I bought another just like it from EBAY already 2.3.3 and rooted to use )
Then it scans everything and acts just as you would expect... No White noise or other visible glitches.
studacris said:
^^^Froyo bootloaders will boot into gingerbread. The kernel splash will be broken and recovery is unaccessable.
Op, When you boot up do you get a weird screen that looks like white noise? If so you have froyo bootloaders, if all looks ok then they are gingerbread.
Click to expand...
Click to collapse

So I should be good to upgrade to kj3 just using Odin3v1.85 and the boog_Kj3_kernel3.tar?
If I do that will I need to re-root? and will the Fugu Root (zImage-root.tar) work on this kernel as well??
THANKS AGAIN for all the answers!

Yup to both

studacris said:
Yup to both
Click to expand...
Click to collapse
COOL!! The object here is to use the "Test" phone to find the upgrade(s) I like best. Then, once I know everything works I'll upgrade my "in-use" phone and start playing with the test phone again!
I've already found that the boot mode jig and Titanium Backup Pro are my FRIENDS!
Thanks for answering all my noobie questions Y'all!

How can you find wich Gingerbread bootloader your using I9000 or I897.

Easy...does the very first screen when you boot say at&t world phone or gt-I9000?
To get into recovery do you press all 3 buttons or just volume up and power?
If the first options are what you have that is the captivate boots.
The second options are I9000.
Also if you PAY ATTENTION TO WHAT YOU FLASH you should know...

MidniteMarauder said:
My guess is that the one click you used included the boot loaders. Don't remember ever seeing a one click without them.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My kf1 thread (see sig) didn't have bootloaders. Also, jmtheiss made one or two Heimdall one clicks without then. Just fyi.

[Q] ICS ROMS and Bootloaders

I hate to even have to ask this, and I can't search the forum for the answer that I know already exists because of my laptop being out of commission (which is where my actually question comes in), but I have the Froyo bootloader on my phone as far as I know, running MIUI 1.10.14 and was wondering if it'd be possible to flash an ICS ROM over this set-up.
Most threads I've browsed through mention ODIN One-Clicking the Gingerbread bootloader as necessary part of the process to flashing an ICS ROM, but like I mentioned, I can't search too deeply as I am, and was wondering if GB BLs are mandatory or just recommended.
Thanks in advance.
Sent from Premium Captivity

Need to have Gingerbread Bootloaders.

Absolutely no way around it?
Sent from Premium Captivity

Unfortunately, no. You have to use a computer to flash bootloaders.

Read the team Hacksungs forum. I believe some people are running froyo bootloaders, but I don't think it's recommended.
Sent from my SGH-I897 using xda premium

To clear up the confusion, the answer is yes and no. Yes I know, more confusing. It all depends on what ROM you are going to. Onecosmic's ICS REQUIRES GB bootloaders, while Teamhacksung's doesn't require them, but CAN be used with either. Also, some features in Glitch V14 require or benefit from GB bootloaders. But it may be a good idea to get GB's since that way you can use anything and never have to worry about switching again

^this 10char

Im not positive but i think you may be able to flash bootloaders from the mobile odin app but its probably easier and safer to flash bootloaders from a computer

Have to do it from computer... Mobile ODIN will not do that for you

Ahh, that may be how I just bricked my cappy then. It may have still had froyo bootloaders on it, and I flashed ICY Glitch from within CWM; and after that I rebooted and the phone wouldn't boot and I had to use my jig to get to download mode, but no computer will recognize it in download mode now do you think that going from froyo to icy glitch could have caused it not to be recognizeable now? I'm praying there is a way to reflash it somehow.

jnthnmc01 said:
Ahh, that may be how I just bricked my cappy then. It may have still had froyo bootloaders on it, and I flashed ICY Glitch from within CWM; and after that I rebooted and the phone wouldn't boot and I had to use my jig to get to download mode, but no computer will recognize it in download mode now do you think that going from froyo to icy glitch could have caused it not to be recognizeable now? I'm praying there is a way to reflash it somehow.
Click to expand...
Click to collapse
This post has nothing to do with bootloaders really. Your phone is fine. If you are on froyo bootloaders, the kernel bootscreen will be a black screen. Why can't you use recovery?
Sent from my CM9 ICS i897 Captivate

That is a great question, i dont know why button recoveries wont work. Only my jig gets me to download mode, but no device recognition.
Sent from my SGH-I897 using xda premium

jnthnmc01 said:
That is a great question, i dont know why button recoveries wont work. Only my jig gets me to download mode, but no device recognition.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Try another version of Odin and drivers, I believe that the Odin v1.3 is use for Froyo bl, and the latest version is use for GB bl because when i've got GB bl on my phone, i cannot use the Odin 1.3 anymore