When I got my Captivate, it had 3 button combo. I flashed back to stock with Odin One Click many times, and it still worked. Even after MIUI and CM7. I just flashed Torch 2.03, and I don't have it anymore... it doesn't work no matter what I do. I flashed the special stock ROM with working 3 button for now... but how did Torch kill my 3 button combo and how do I permanently get it back if I had it?
Haloruler64 said:
When I got my Captivate, it had 3 button combo. I flashed back to stock with Odin One Click many times, and it still worked. Even after MIUI and CM7. I just flashed Torch 2.03, and I don't have it anymore... it doesn't work no matter what I do. I flashed the special stock ROM with working 3 button for now... but how did Torch kill my 3 button combo and how do I permanently get it back if I had it?
Click to expand...
Click to collapse
Look in the zip package and see if there is a sbl.bin, I think that is what overwrites the 3 button combo on some model versions.
jhernand1102 said:
Look in the zip package and see if there is a sbl.bin, I think that is what overwrites the 3 button combo on some model versions.
Click to expand...
Click to collapse
No sbl, ROMs usually don't flash that. I just don't get it, it worked perfectly, through MIUI, CM7, and KB1, but after Torch it doesn't work.
Is torch based on GB? If so using odin can cause problems.
Sent from my SAMSUNG-SGH-I897 using XDA App
megatronisabeast said:
Is torch based on GB? If so using odin can cause problems.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I897UCKB1 ROM, 2.2 official Froyo for Captivates.
Also I tried, standard 3 button, and the ones for Gingerbread (even though it isn't) just in case, I tried every possible combo. I've always done it easily, since July.
When you flashed the 3 button Odin package you got your 3 button combo back right? Then you flashed torch again and you lost it? I think you will need to pull the fixed sbl.bin out of a working ROM and place it in the torch package to get it back.
jhernand1102 said:
When you flashed the 3 button Odin package you got your 3 button combo back right? Then you flashed torch again and you lost it? I think you will need to pull the fixed sbl.bin out of a working ROM and place it in the torch package to get it back.
Click to expand...
Click to collapse
I had it, flashed Torch and lost it, and got it back with the 3 button stock package. I refuse to flash Torch again... I don't want to lose it. Anyway most ROMs don't flash sbl.bin.
Haloruler64 said:
I had it, flashed Torch and lost it, and got it back with the 3 button stock package. I refuse to flash Torch again... I don't want to lose it. Anyway most ROMs don't flash sbl.bin.
Click to expand...
Click to collapse
Well DG's uses a fixed sbl.bin with his ROM's so people won't loose it. You can pull it out of his and put it in torch and it should work.
jhernand1102 said:
Well DG's uses a fixed sbl.bin with his ROM's so people won't loose it. You can pull it out of his and put it in torch and it should work.
Click to expand...
Click to collapse
Oh, really? Cool.
I didn't want Torch to begin with, I just wanted to play around with it. I just posted here because it's scary having a ROM kill your combo.
Try flashing Cog 4.3. If I remember correctly, all the cog roms include an sbl.bin with a working 3 button combo. Once you have a working sbl, don't flash roms that include their own sbl and you should be fine.
Also, be aware that flashing sbl can brick your phone.. like, permanently. So, once you have a working sbl in place, I'd keep bootloader flashing to an absolute minimum.
modest_mandroid said:
Try flashing Cog 4.3. If I remember correctly, all the cog roms include an sbl.bin with a working 3 button combo. Once you have a working sbl, don't flash roms that include their own sbl and you should be fine.
Also, be aware that flashing sbl can brick your phone.. like, permanently. So, once you have a working sbl in place, I'd keep bootloader flashing to an absolute minimum.
Click to expand...
Click to collapse
Thanks for the advice. I have a working one using the 3 button stock package at the moment. sbl is in the updates folder in the zip?
I'm just upset that I had a permanent 3 button combo and it's somehow gone. I really enjoyed being one of those people with a permanently working combo, being able to flash to stock and stuff.
Haloruler64 said:
Thanks for the advice. I have a working one using the 3 button stock package at the moment. sbl is in the updates folder in the zip?
I'm just upset that I had a permanent 3 button combo and it's somehow gone. I really enjoyed being one of those people with a permanently working combo, being able to flash to stock and stuff.
Click to expand...
Click to collapse
My Cappuccino has had problems with the 3 button combo since I flashed a Gingerbread ROM.
CM7 Inspire 4G
So there are only three reasons that the button combo can go away:
1 - You inadvertently flashed either sbl.bin and/or boot.bin at some point, or if you use Odin 1-click, your copy is corrupted, as all of the 1-click's will flash both sbl.bin and boot.bin.
2 - Something horrible has gone wrong from a software standpoint. Nothing in Android SHOULD ever be able to touch the SBL or BOOT partitions, but it doesn't mean it's not possible. A "bad program" of some sort, running around with root access, may have accidentally corrupted something, which is causing your problems. More likely, you had an incompatible version of Clockworkmod running at some point, and that screwed with one of those boot partitions.
3 - Your device is developing slash has developed, a hardware problem. Either causing some corrupt sectors in the boot or sbl partitions, or perhaps even at a lower level. Could be something as simple as a few bits got corrupted, and it will never happen again, or it could be indicative of more problems to come.
~~~~~~~~~~~~~~~
To fix it, I would simply flash the "3 button combo fix" that is floating around these forums, and see if that helps you. If you have a pre version 1010 Captivate, and were lucky enough to always have the 3-button combo working, simply flash back to the stock 1-click JF6 and that should fix all your problems.
If neither of those work, then perhaps there is a more serious hardware problem developing, in which case, I would replace your Captivate while it's still under warranty.
And PS, I would refrain from flashing boot.bin and sbl.bin updates from CWM. Yes, I know everyone seems to think it's safer, (though errors in file copy can happen just as easily and as undetected as in an ODIN flash), but I've quite literally re-flashed my boot.bin and sbl.bin via 1-click hundreds of times without bricking. Just make sure your cable is securely attached to both phone and computer, and that your girlfriend, cat, roommate, pet dinosaur, etc are kept far away from you and your computer while flashing. I say this because if something has already going wrong, CWM style flashes may not completely fix the problem. Whereas ODIN style flashes (either from the standalone ODIN, or via 1-click) tend to have more power to "overwrite" whatever has gone wrong. I'm sure many people will disagree with that, but hey, I've been flashing and screwing with my Captivate for some 7 months now, "soft bricked" it more times then I can remember, but have never had a single problem that couldn't be fixed with a nice stock 1-click flash.
~~~~~~~~~~~~~~~
Hope that helps!
Shammyh said:
So there are only three reasons that the button combo can go away:
1 - You inadvertently flashed either sbl.bin and/or boot.bin at some point, or if you use Odin 1-click, your copy is corrupted, as all of the 1-click's will flash both sbl.bin and boot.bin.
2 - Something horrible has gone wrong from a software standpoint. Nothing in Android SHOULD ever be able to touch the SBL or BOOT partitions, but it doesn't mean it's not possible. A "bad program" of some sort, running around with root access, may have accidentally corrupted something, which is causing your problems. More likely, you had an incompatible version of Clockworkmod running at some point, and that screwed with one of those boot partitions.
3 - Your device is developing slash has developed, a hardware problem. Either causing some corrupt sectors in the boot or sbl partitions, or perhaps even at a lower level. Could be something as simple as a few bits got corrupted, and it will never happen again, or it could be indicative of more problems to come.
~~~~~~~~~~~~~~~
To fix it, I would simply flash the "3 button combo fix" that is floating around these forums, and see if that helps you. If you have a pre version 1010 Captivate, and were lucky enough to always have the 3-button combo working, simply flash back to the stock 1-click JF6 and that should fix all your problems.
If neither of those work, then perhaps there is a more serious hardware problem developing, in which case, I would replace your Captivate while it's still under warranty.
And PS, I would refrain from flashing boot.bin and sbl.bin updates from CWM. Yes, I know everyone seems to think it's safer, (though errors in file copy can happen just as easily and as undetected as in an ODIN flash), but I've quite literally re-flashed my boot.bin and sbl.bin via 1-click hundreds of times without bricking. Just make sure your cable is securely attached to both phone and computer, and that your girlfriend, cat, roommate, pet dinosaur, etc are kept far away from you and your computer while flashing. I say this because if something has already going wrong, CWM style flashes may not completely fix the problem. Whereas ODIN style flashes (either from the standalone ODIN, or via 1-click) tend to have more power to "overwrite" whatever has gone wrong. I'm sure many people will disagree with that, but hey, I've been flashing and screwing with my Captivate for some 7 months now, "soft bricked" it more times then I can remember, but have never had a single problem that couldn't be fixed with a nice stock 1-click flash.
~~~~~~~~~~~~~~~
Hope that helps!
Click to expand...
Click to collapse
I haven't actually, Torch killed it and it doesn't have an sbl in it. Flashing back to stock always kept 3 button combo, even though it flashes an sbl that people without the combo need to avoid.
Nothing new on my phone really. CWM is for i897, also used CM7's CWM 3.0.0.5.
Very possible.. hope not.
I did get it back with the proper sbl, it worked. Nothing serious.
I didn't know you can flash an sbl from CWM before today, scary. I know how dangerous it is.
I've used One Click since July or so, it's always worked perfectly.
Well I really appreciate the help man. I am ordering a JIG already, just in case. Never thought I'd need one. I mean, I guess it isn't a big deal, not having a permanent 3 button combo.
Torch doesn't flash any bootloaders, it can't possibly kill 3-button recovery.
Haloruler64 said:
Thanks for the advice. I have a working one using the 3 button stock package at the moment. sbl is in the updates folder in the zip?
Click to expand...
Click to collapse
Usually, yes. If you're going to remove it from roms that have it, make sure you also remove the line that flashes it in the update script (META-INF/com/.../update-script)
ryude said:
Torch doesn't flash any bootloaders, it can't possibly kill 3-button recovery.
Click to expand...
Click to collapse
I know it doesn't, I checked for it. But I got into recovery to flash Torch, and after flashing it I couldn't gt into recovery anymore....
Haloruler64 said:
I know it doesn't, I checked for it. But I got into recovery to flash Torch, and after flashing it I couldn't gt into recovery anymore....
Click to expand...
Click to collapse
There are other ways your bootloader can get corrupted. I understand you're upset, but you shouldn't immediately place blame on my ROM.
ryude said:
There are other ways your bootloader can get corrupted. I understand you're upset, but you shouldn't immediately place blame on my ROM.
Click to expand...
Click to collapse
No, Torch wouldn't have done it. At least it's an easy fix.
CM7 Inspire 4G
ryude said:
There are other ways your bootloader can get corrupted. I understand you're upset, but you shouldn't immediately place blame on my ROM.
Click to expand...
Click to collapse
I didn't blame it, I simply provided info on the situation. I never said "don't use Torch."
Related
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
thats funny. i have run every froyo rom available to us, i9000 w/voodo, ulf, cognition with voodoo, and i have yet to brick my phone. i flash to stock between EVERY new rom.
there is something you are not doing right. did you disable voodoo before attempting to flash stock?
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I always flash back to JF6 via Odin 1 click before going to any new rom. It does not matter for whether voodoo is disabled or not because Odin 1 click repartitions everything to RFS. Also, the orange screen is not that big a deal. Reflashing JF6 via Odin once more is the solution.
If you continually have these problems when flashing to JF6:
1. Try re-downloading Odin 1 click.
2. Follow correct procedure for Odin flashing (Read OP's)
3. Try other USB ports
4. Uninstall and install fresh drivers that match your operating system (eg. 32bit/64bit)
Further, this post is not for the development section, but belongs in General or Q&A.
I think even without voodoo disabled, flashing back to stock will break voodoo and it wont be functional anymore. I personally never disable voodoo when flashing back to stock. You need to Master Clear after flashing back to stock.
Never bricked my phone flashing all the time.
I do it all the time! Never bricked my phone... EVER! The closest I came was when I tried flashing to another rom with CVM with voodoo still enabled. got stuck in loop, but to rectify the situation I "flashed back to stock with one click ODIN" and all was well.
i9000 is not the captivate argh different kernel
Odin gave me Blue, Light Blue, Orange, White and Black Screens of Death, no matters if i had Voodoo or not..
I think it sometimes hangs without any reason, but the drivers/program itself..
Thanks God my phone doesn't have the Bootloader's 3 Button issue..
Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
I believe he was referring to i9000 roms. I have never had any issues flashing back to stock from any rom. It has to be something you are doing. Might be the answer you want but probably going to be the most common answer you will get. Check your steps.
Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
i never said i am running an i9000 HARDWARE, i said ROMS
like everyone else has said. its something YOU are doing wrong. please dont spread FUD
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Sometimes its not the arrow....
its the Indian. The majority of the people who flash follow the same procedure with no issues. While its nice of you to try to caution folks, maybe you need to look at what you're doing instead of jumping to conclusions.
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
Agreed 10char
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
AGREED!
one person has problems with multiple devices=look for the common denominator.
if not deleted then at least OP change the title because its misleading.
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I have flashed i9000 roms, kernels, modems, themes, and anyting else imaginable, with and without voodoo, with and without master clear, and have NEVER gotten the orange death screen before, during, or after Odin flashing back to stock. I've flashed just about every iteration of the Cognition FroYo roms and have never had an issue.
Re-download odin, maybe? But it's not an issue with Cognition.
Belaflek said:
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Click to expand...
Click to collapse
Yo only need to disable voodoo when you are upgrading from one version to another but when you are flashing back to stock it will repartition everything for you back to RFS.
I've run all the Froyo kernels, ROMs, even i9000 Froyo ROMs on the Froyo reoriented kernel, with or without voodoo, it doesn't matter, and I flash back to stock all the time. Odin wipes everything out, it doesn't matter what you are running.
the "factoryfs.rfs" screen-o-death is a well known problem. fortunately, factoryfs.rfs doesn't really matter (it's only the /system partition), your phone just won't boot. Likely you'll hit the phone--!--PC screen, but as long as you have 3 button recovery working, you're safe.
this issue crops up when you have a bad USB connection to your phone. I'm willing to bet 90% of the people with this problem are running outdated hardware (made before 2006 or so) that can't keep up with ODIN's pace or are using a desktop and not plugging the USB into a port connected to the motherboard (you should be using one on the back of the tower)
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
posts like this... littering the dev forum
From the Serendipity thread:
If the extra flash involves unnecessarily flashing sbl.bin then your risk of not being able to recover increases. If the user is unaware of which stock firmware package they need in order to preserve their download mode combo (and you might be surprised at how many people are unaware that this is even and issue) then it just gets worse.
Click to expand...
Click to collapse
I'm trying to understand this. How would you 'flash sbl.bin' incorrectly?
This incorrect flash causes the loss of the three-button combo?
How do you avoid this problem?
The conversation was about flashing with Odin back to stock before flashing a new ROM. Some say they don't bother and I've heard that's looking for trouble, then again, it sounds as though following a ROM sequence (going up by version numbers) might be what they're talking about.
Any help wrapping my mind around all of this would be appreciated!
reinbeau said:
From the Serendipity thread:
I'm trying to understand this. How would you 'flash sbl.bin' incorrectly?
This incorrect flash causes the loss of the three-button combo?
How do you avoid this problem?
The conversation was about flashing with Odin back to stock before flashing a new ROM. Some say they don't bother and I've heard that's looking for trouble, then again, it sounds as though following a ROM sequence (going up by version numbers) might be what they're talking about.
Any help wrapping my mind around all of this would be appreciated!
Click to expand...
Click to collapse
They are probably talking about using th manual ODIN, where you have to select the files.
If you are using the One click Odin version you should not have any problems. Just verify that you have the button combos before you do anything. Vol-up + Vol-Dwn + Plug in usb for download mode. If you can get there you are good
Yes, I've verified I have the three button combo, I just wanted to make sure I didn't do anything to cause a loss of the ability. Thank you for your help!
What's your batch number? I believe this whole problem is isolated down to some batch 1008 phones. Even if you happen to have one of these phones, there are solutions out there to avoid losing 3 button combo.
Batch #1007. As I said, I just want to avoid the problem. So could you explain what methods there are to avoid the loss? All to further my knowledge
Here is it simply put: DG's Odin One Click flashes an sbl.bin that breaks the 3-button combo for a large percentage of batch 1008 users. Therefore, ppl with batch 1008s are urged to use C3POLOL's Odin flasher that contains an sbl.bin that does NOT break the 3-button recovery. So if a 1008 user accidently knocked his/her battery out while falshing with odin one click, they could be TRULY bricked bcuz they have a bad bootloader and will have no access to download/recovery modes. This would require a jig to force the phone into download mode and then use C3POLOL's regular Odin to flash the stock rom with fixed sbl.bin. Hopefully this clears things up.
PS. You said you have a batch 1007, so if you flash to stock with Odin One Click by DG and then afterwards you STILL have the 3-button combo then your perfectly fine.
silverslotcar, based on what you've told me, I'll be sure to not flash with Odin One-Click from DG! I don't know which one I downloaded, I"ll have to check. I haven't played with Odin yet, but I may be doing so this weekend.
You have a batch 1007. You should be fine using the one click odin. You said it didn't break your 3-button combo so your fine. If you use it and then still can get to recovery by holding both volumes and power til the second black screen then your good.
I'm batch 1007. I have NO problems using Designgear's Odin One-Click. You being 1007 as well, you should have the same experience!
Awesome, thanx, guys, for the education!
What about batch 1010
avs420 said:
What about batch 1010
Click to expand...
Click to collapse
Batch 1010 users need to follow these directions to flash with Odin
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
rufex2001 said:
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you test the phone to make sure it can accept the button combinations to go into download mode (almost all do, except for a batch of faulty ones), there is almost nothing you can do that will truly "brick" the phone. A bad or interrupted flash will result in a boot loop, which you can recover from by forcing download mode, and using Odin to reflash back to stock.
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Basically what causes a brick in any electronic equipment is from an interruption/error in any boot critical files. The item does not have the proper/complete instruction to turn on. You could say it is like starting a car being told to first put the key in
Sent from my SAMSUNG-SGH-I897 using XDA App
If you can use the 3 button combos to get into download or recovery mode, you are good to go. The only danger would be a bad Odin flash, but even so you'll have a chance to recover it by making a cheap USB jig (3 100k Ohm resistors into pins 3 and 4, I think, of the usb port) or buying one. This will boot the phone straight into Download mode.
When using Odin, there is only one stage where you can brick your phone for good, during the bootloader copy process, which probably takes less than a second.
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
rufex2001 said:
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
Click to expand...
Click to collapse
My Cappy is a 1007 build, too. I've soft bricked my phone more times than I can count, but Odin hasn't had anything to do with it. It can do it, though.
At one time in my life I flashed a new ROM every day, and I used Odin every time before I flashed.
On a side note, back when I flashed my first ROM, I pulled the battery during the first boot, dropped it, and then flashed another ROM without using Odin, and it never bricked it, so that should give you a good idea of how hard it is to brick these phones. Lol
Stupidity.
Sent from my Captivate.
opcow said:
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Click to expand...
Click to collapse
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
No odin really is not that bad just don't unplug it while it is running. You would not want to unplug your computer when flashing a new bios
Sent from my SAMSUNG-SGH-I897 using XDA App
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Sorry for any dumb or repeated question I may be asking.
Sent from my SAMSUNG-SGH-I897 using XDA App
Pierce533 said:
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
Click to expand...
Click to collapse
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
rufex2001 said:
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Click to expand...
Click to collapse
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
opcow said:
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
Click to expand...
Click to collapse
Thanks for the info. Is there a stock I897UCJF6 ROM that can be flashed with CWM? I haven't been able to find one and if there is one I would like to have one around to use. Thanks for taking the time to answer my questions.
opcow said:
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
Click to expand...
Click to collapse
That is exactly the sort of thing I had in mind! So I guess I could keep a CWM update.zip and a stock rom update.zip and some custom roms and just do everything directly from the phone and without Odin, right? Or am I missing something?
Sent from my SAMSUNG-SGH-I897 using XDA App
Guns don't kill people
opcow said:
Odin isn't bad so much as an unnecessary risk. Then there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build.
Click to expand...
Click to collapse
Yep. I have build 1008 that has always had the 3-button combo and lost it after using ODIN 1-click (I restored the combo with a later flash).
I believe opcow and others when they say that flashing back to stock is unnecessary. I just don't understand why the authors of some of these ROMs leave this as part of their installation guide.
Sent using XDA App
Pay close attention to the options in recovery when you are using a custom rom. It's part of the custom kernal, and of used properly can help you avoid odin. I avoid it because I have a mac and odin won't run on anything but windows. Custom recovery will allow you to format every part of the OS but the sbl.bin. Also in some custom recoveries there is an option to mount usb. This will allow you to format the internal sd then copy a new rom.zip and flash if you really want a clean flash. If your doing this make sure you are able to mount your sd before you format anything. Avoid stock 2.2 kernals because they have 3e recovery. There are ways around that but they have to be in play before you end up in a bootloop.
3e recovery + bootloop= odin recovery "only option".
Make sure lag fix for rom kernal A understands lag fix for rom kernal B. Also usually only a concern for stock 2.2 kernal. Other than that really hard to brick this phone.
Sent from my SAMSUNG-SGH-I897 using XDA App
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
ryude said:
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
Click to expand...
Click to collapse
Could you please explain what a wipe ROM is? Thanks
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
bigbyte.me said:
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
Click to expand...
Click to collapse
U got a jig?
Sent from my Captivate using XDA Premium
Zig won't help as nothing is helps only in case of Soft brick.
BTW i figured out where I went wrong, The cognition ROM contains seconday bootloader. So when I flashed it I ended up with Gingerbread primary and Froyo secondary bootloader and hence the Brick. I request all the rom dev to mention at the start of their post if their ROm contains bootloaders.
bigbyte.me said:
Flashed Cognition 4.3.2, flashed successfully.
Click to expand...
Click to collapse
^ That's where you went wrong. Cog flashes sbl. You ended up with one bootloader from 2.3, and one bootloader from 2.2.
There are videos of how to unbrick a perma-bricked phone with a riff box jtag unit on youtube. It'll require you to remove the motherboard and blow $150 or so on a riff box, though.
or you send it to someone with the equiptment, like mobiletechvideos.com and not learn about riff/boxing and spend less money... and and and...
or because it doesnt boot and they cant prove you voided your warranty send it back!
So, this could be avoided doing what?
-Going back to GB stock and from there going back to froyo stock (without 3 button fix)?
I don't think moviletech does crappys something about the solder points too close together.
Edit: but could be wrong.
Sent from my GT-I9000 using XDA Premium App
i was in a similar situation, no 3 button nothing worked my phone wouldn't even power on
but the one method that saved me was this,
Remove battery, SIM card, SD card (if present)
Connect USB cable from computer
While holding down up & down volume, re-insert battery
may be this could help you too.
mobile tech does and has been for over a month, and the first few people are free!
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
for me if i touched any buttons the jig would not work.
other methods wouldnt work either.
worth a shot.
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
1tontomato said:
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
studacris said:
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
Click to expand...
Click to collapse
Yea your right it is the sbl.bin. It was a good idea before gingerbread, but I think it's time has passed especially since it's really easy to get past not having a button combo with a jig. A bad combination of bootloaders is a "brick" for sure.
Sent from my SAMSUNG-SGH-I897
amtrakcn said:
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
Click to expand...
Click to collapse
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
bigbyte.me said:
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
Click to expand...
Click to collapse
I say none. ANYTIME you touch bootloaders there is a chance of hard bricking. If they don't have any, worst case is a "clay" (soft brick)
TRusselo said:
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
....
Click to expand...
Click to collapse
Perhaps I;m not out of the woods yet but a wrong action in ODIN had HB'd my Cappy. Your steps got me back to DL mode. Perhaps it is the 5 count. Patience not being my strong pt I had "not waited" until your recommendation.
I was trying from Continuum5.3 to get back to eclair so to carrier unlock when I made an ODIN error. Still need do that but for now I'll just be thankful that it lives, and move only forward..
its the not touching buttons that makes this trick work
if you replace the battery, what is your normal instinct?
try the power button! or try the button methods...
you are the first to confirm my trick!
congrats!
http://forum.xda-developers.com/showthread.php?t=731989
Use this to get back to stock safely!
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE
use the thanks button!
Hmm very interesting...
I thought your trick worked because it was a screw up in the param.lfs not a bootloader brick, guess not.
im surprised too...
I was able to flash from the "phone ! pc" screen (kinda) May be useful for bricks?
If this post proves to be useful and would serve better in another section then please move it.
Yesterday (June.09.2011) I got a refurb replacement for my Captivate, it was actually a new phone though and as far as I can read it's an 1105 build.
It came with Froyo 2.2 and no software updates from AT$T were available when I checked from the phone.
GPS didn't seem to do so well according to My Tracks recording a 22 mile motorcycle trip home.
I was going to try Cognition (Froyo based)
I was able to use the buttons on the phone to get into recovery 3e but it checks for signatures and I couldn't figure out how to root the phone and replace recovery.
I would have used one click root from my pc but I didn't have the proper windows drivers (net framework?)
I decided to flash Odin one click to stock (Eclair 2.1)
I also have the Odin stock 2.1 with 3 button fix that I had used on my other refurb captivate successfully.
This is where things went bad for me.
I used the 3 button fix version of Odin (I don't know if my result would have been different if I had used One click Odin instead and I'd like to know for later)
After the flash the phone would only boot to the phone ! pc screen no matter how many different button, battery, power button, usb cable, jig combinations I tried (Yes I have a jig)
Anyways, I had Odin one click (not the three button fix version) open and even though I only ever saw the ! screen on the phone I noticed that Odin was showing the device connecting and disconnecting when I pulled the usb cable.
What the hell, I thought I was bricked anyways so I hit Start. The phone showed a progress bar that mirrored what Odin was showing me, right below the ! icons on the phone.
After that I was able to use the jig to enter download mode, I tried both Odin (stock 2.1) versions I had and they ran the flash but the phone boot looped when I tried to start it up.
I then tried the method to update the bootloaders and move onto Gingerbread and I was successful, Running Serendipity VII now (Thanks MikeyMike01, ChanceM)
It was a nerve racking experience and I'm nervous if I decide to try to go back to Froyo again.
Maybe this info isn't new, maybe it's helpful. I may summarize later.
Any thoughts or tips to get back to Froyo if I want to later?
not weird at all.
here's what happened:the phone...!...pc screen just signifies that a flash was incomplete, the first flash with the 3 button fixed failed before it ever loaded any firmware, therefor the image for when download mode is initiated was missing, all that is is a .png. since it was missing the incomplete flash screen was the only thing there for it to call upon when DL mode was started.
odin one click bootlooped you cause it just does that to new phones...to get back to stock bootloaders use odin one click then use this http://forum.xda-developers.com/showthread.php?t=995143... or just use that and go back to stock eclair with the GB bootloaders. DO NOT FLASH THE 3 BUTTON FIX PACKAGE WITH GB BOOTLOADERS THAT WILL BRICK YOUR PHONE.
Thanks for the explanation!
studacris said:
not weird at all.
here's what happened:the phone...!...pc screen just signifies that a flash was incomplete, the first flash with the 3 button fixed failed before it ever loaded any firmware, therefor the image for when download mode is initiated was missing, all that is is a .png. since it was missing the incomplete flash screen was the only thing there for it to call upon when DL mode was started.
odin one click bootlooped you cause it just does that to new phones...to get back to stock bootloaders use odin one click then use this http://forum.xda-developers.com/showthread.php?t=995143...or just use that and go back to stock eclair with the GB bootloaders. DO NOT FLASH THE 3 BUTTON FIX PACKAGE WITH GB BOOTLOADERS THAT WILL BRICK YOUR PHONE.
Click to expand...
Click to collapse
Is there a reason they don't just include the intended PBL with that SBL for the 3 button fix? it would solve all the problems... I'll go figure this one out.
AdamOutler said:
Is there a reason they don't just include the intended PBL with that SBL for the 3 button fix? it would solve all the problems... I'll go figure this one out.
Click to expand...
Click to collapse
they dont have the PBL file. all they have had is the SBL
A similar thing happened to me on my replacement. It came with stock 2.2 and when I tried to use Odin one click it failed. I pulled the plug and after that nothing was getting me into download mode. No button combinations or jig worked. When I was trying more combinations I had left odin open and realized it was showing as connected even though I was only getting the phone ! pc screen. So just like you I figured what the hell and went for it. 2 minutes later I was at stock 2.1.
nybmx said:
A similar thing happened to me on my replacement. It came with stock 2.2 and when I tried to use Odin one click it failed. I pulled the plug and after that nothing was getting me into download mode. No button combinations or jig worked. When I was trying more combinations I had left odin open and realized it was showing as connected even though I was only getting the phone ! pc screen. So just like you I figured what the hell and went for it. 2 minutes later I was at stock 2.1.
Click to expand...
Click to collapse
What build number on yours?
I'm still having problems, post to follow...
I just tried to go back to Froyo from Gingerbread.
I followed the instructions linked to in this thread (thanks) http://forum.xda-developers.com/showthread.php?t=995143...
The following 4 flashes just left me in a boot loop but I was able to use my jig to get into d/l mode each time.
I did get a random Odin 3 v1.3 from the net that had GT-P1000 instead of i897 or i9000 on it's title when run. I don't think it was the issue though since OneClickDownloader also failed the same way for me.
Odin 3 v1.3 JF6 Secure
Odin 3 v1.0 OneClickDownloader
Odin 3 v1.3 JF6 Secure
Odin 3 v1.7 JF6 Secure (This Odin came with the Gingerbread installation package I got from Cezar/icezar1 (I think)
Now I am running a fever and I'm generally slow but I think I'm following your suggestions.
edit; I wrote 1.2, I meant 1.3
Pirateghost said:
they dont have the PBL file. all they have had is the SBL
Click to expand...
Click to collapse
God damnit.... NEVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER flash a PBL without a matching SBL.... This is the cause of bricking for 90% of captivates.
AdamOutler said:
God damnit.... NEVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER EVER flash a PBL without a matching SBL.... This is the cause of bricking for 90% of captivates.
Click to expand...
Click to collapse
yep. but the sbl was all that was needed when that package was created months and months ago. we didnt have any need to worry about pbls at that time...then 2.3 came along
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
daveyian said:
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
Click to expand...
Click to collapse
Well I know 4.5 and above for cognition doesn't have boatloaders in it. You might want to unzip roms and check for bootloaders just to be safe.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
daveyian said:
DG said somewhere that Gingerbread (2.3) bootloaders are backward compatible with Froyo (2.2) ROMs.
Apparently this is not true with CM7 ROM (I dunno)
Can I keep my Gingerbread bootloaders and safely flash a Froyo ROM such as Cognition? (will it work?)
Click to expand...
Click to collapse
It will work. I am running firefly 3.0 at the moment, on GB bootloaders. I have not tried cyanogen yet. I'm sure eventually all the little bugs will get worked out of gingerbread, and I'll be back on it.
wow i posted about this MONTHS ago....
heres the link.....
http://forum.xda-developers.com/showthread.php?t=988927&highlight=flash+from+soft+brick
I got that phone ! pc last night while trying to odin back to 2.1 from stock. Odin didnt make any progress for 10 mins and I removed battery. Thought I was screwed. Removed the usb and pulled the bat. Opened odin and plugged it back in and the same screen came right up. Just held down the volume keys and power button till the screen flashed once and noticed odin recognized the com port. Then tried odin again and it worked fine... even displayed the little blue progress bar on that screen lol.
daveyian said:
What build number on yours?
I'm still having problems, post to follow...
Click to expand...
Click to collapse
A refurb 1008
true story!
happened to me 2!