Database Develop

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

Brick or not

Ok guys this is what i did...my friend said his phone was a samsung infuse 4g so i use the guide to root his phone..when i flash a rom on the phone come to find out it was a damn samsung captivate now it want do anything..but i can still get into the download mode..can someone guide me to the right thread

Maybe you should try with http://forum.xda-developers.com/showthread.php?t=1153310. If u can get into download mode should be easy to fix. What it's does when u turn it on?

Darkuso said:
Maybe you should try with http://forum.xda-developers.com/showthread.php?t=1153310. If u can get into download mode should be easy to fix. What it's does when u turn it on?
Click to expand...
Click to collapse
ITS DOING THIS http://www.youtube.com/watch?v=oDWmGrUPFjw

If you can get to download mode just try flashing any of Captivate ROM's (preferably stock).

gogoad said:
If you can get to download mode just try flashing any of Captivate ROM's (preferably stock).
Click to expand...
Click to collapse
As gogoad says, u can try with this http://forum.xda-developers.com/showthread.php?t=731989 that will leave the phone like new. But careful, dont unplug the phone in the process. There is http://forum.xda-developers.com/showthread.php?t=995143 too and it is safer but dosent contain bootloaders.

gogoad said:
if you can get to download mode just try flashing any of captivate rom's (preferably stock).
Click to expand...
Click to collapse
i know this is a damn question...but do i use one-click to flash a rom from download mode

thank you guys this thread can be deleted cause....ITS FIX FIX FIX FIX!!!!!!!!!!

jacsonmoore3 said:
ITS DOING THIS http://www.youtube.com/watch?v=oDWmGrUPFjw
Click to expand...
Click to collapse
I see that the issue was corrected.
For anyone else who has this issue: You will want to use a 301kohm factory mode download jig on resistor between usb pins 4 and 5. If you don't have a dongle, then just stick the leads into the usb port and fish around. This will put the device into download mode. It will work because I see that your phone is actually booting up.
Someone showed me this video last night in the Infuse4G chat room. I would have responded then, but I did not know that there was a thread. I saw that you were flashing using Infuse4G One-Click Back-To-Stock UnBrick. I took that download down because of the confusing name. I also made some changes to the wording.. Device ID is now "This package is intended for:". Infuse4G One-Click Back-To-Stock will be down until I can figure out some way of distinguishing it from One-Click UnBrick.
In the Infuse4G forums they don't have a problem with bricking, so they call flashing back to stock "unbricking"... lol.. Anyways, I figured "when in rome, do as the romans do" so I put the word UnBrick at the end. Sorry if the naming convention confused you and I am working to correct that.

Does that include bootloaders adam? Im guessing no thinking infuse bls would kill a cappy.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.

xijar said:
Does that include bootloaders adam? Im guessing no thinking infuse bls would kill a cappy.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
The infuse has locked bootloaders. This is the way it should be. We don't need to flash the bootloaders, so they are not included.
Think of the bootloaders as that which initializes the hardware and provides download mode. The kernel is what adds additional features. There is no reason to modify the bootloaders when the kernel can be changed.
The Captivate 2.3 upgrade was done improperly. Instead of changing the kernel, they went the lazy way and modified the bootloaders to use an existing kernel to save time. On HTC phones I guess the bootloader and the kernel are joined somehow so bootloader unlock is important. We don't have that problem. We have 4 stages of booting.
With this information, you should be able to see why ilI think the bootloaders should be locked on the captivate.

they should, less bricks.

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

[Q] Which Bootloaders am I Using?

Is there a commend to display which bootloaders I'm running? I've seen people say you can tell by which screens appear when booting or which buttons you have to press to get into recovery but I am looking for something more definitive or precise. Thx.

That is the only method, so you're best bet is that way -_-

b-eock said:
That is the only method, so you're best bet is that way -_-
Click to expand...
Click to collapse
Which metod? My Captivate does not show the Galaxy X screen when it boots up and to go into recovery mode I have to push both the volume up and volume down buttons and the power buttons. Which bootloader does that mean I'm running?

I897. Now which ROM are you running?
Sent from my SGH-I897 using xda premium

Here's the checklist:
First boot screen:
Black with "Galaxy S I9000" logo = i9000 bootloaders
White AT&T World Phone logo = i897 bootloaders
On a Gingerbread rom? You're using Gingerbread bootloaders
On an ICS rom? You're using Gingerbread bootloaders
On a Froyo rom? You could be on GB or Froyo/Eclair bootloaders. You'll have to remember whether you've ever flashed the GB bootloaders.
Or, you can just flash the GB bootloaders (i9000 or i897) and know for sure.

So, according to both of you my bootloaders are I897 (I didn't know I897 had anything to do with bootloaders!). I am running Doc's Master ICS V5 Final. I realize that theoretically you have to be using GB bootloaders to run ICS but I thought you could use the wrong bootloaders and just have a buggy phone. My broadband version starts with I9000 though. Is that unrelated to my "I897" bootloaders? Thanks for helping me learn!

The i9000 part you see is your modem which is required when using AOSP ROM (CM7, CM9, MIUI) Unless you want to use Nexus S modems. So yes you have I897 bootloaders. What ROM were you on before you flashed any ICS ROM?
@jmtheiss you don't have to have GB bootloaders to run ICS... Many people are too scared to flash them and don't want to.

Good to know. I thought that there might be a chance it was similar to the cm7 requirements.

I never knew CM7 required GB BL's....

lol scared to flash bootloaders... i flashed bootloaders 3 times on my two cappies the other day without palm sweat like i used to back in the day... lol running i9000 bootloaders with custom boot image now on both cappies. no more sleep death with Deep idle and liveOC!!
oh hey if going to ICS (which you will now or later) probably best to flash i9000 GB bootloaders. custom boot image link in my sig.

If I recall, from 2.2 I ran gb cyanogen rom for a few minutes then upgraded to ics and never looked back.
Sent from my SGH-I897 using xda premium

TRusselo said:
lol scared to flash bootloaders... i flashed bootloaders 3 times on my two cappies the other day without palm sweat like i used to back in the day... lol running i9000 bootloaders with custom boot image now on both cappies. no more sleep death with Deep idle and liveOC!!
oh hey if going to ICS (which you will now or later) probably best to flash i9000 GB bootloaders. custom boot image link in my sig.
Click to expand...
Click to collapse
i have read that flashing bootloaders is risky and can hard brick your phone? is this a common myth that people are scared of or is the process reversible? i am having a lot of random shut offs especially with wifi on. i clean and wiped everything and using GB bootloaders but it seems the issue persists. i am desperately trying to find a fix, i am running doc masters v6 rom. do you have any advice and if the i9000 bootloaders may fix my issue?

Its no myth. only way to hard brick is if the bootloaders are missing or corrupted.
he was just saying that people stress it too much. I too have flashed boots plenty of times with no issues at all. hell, we all used to use Odin one click, some even recommended it between every ROM flash (way back in the day), which contains boots.
My captivate is 17 months old and going strong, just make sure you've got a good connection by flashing a nobootloader package a couple times, then if that goes good, flash the bootloaders and you should be fine.

I felt same way about doing my first flashing. Now it is a walk in park!! I load a different ROM about every other day. Do your backups!!!
Sent from my SGH-I897 using XDA

You're using the normal gingerbread bootloaders for captivate, please correct me if I am wrong here.
Sent from my SGH-I897 using XDA