Related
So I finally decided to attempt to flash my phone, but realized I have a build 1010. After reading about all the issues with flashing back with ODIN not working or disabling the 3 button download mode after using, I'm nervous now. I consider myself fairly tech savvy, but get easily frustrated. I downloaded Bay-wolf's AIO Tool and it took the phone into Download Mode without trouble, should this still work after flashing a new ROM, or will this not work just like the 3 button combo?
I really want to flash a custom ROM, but should I want to try another or flash back to stock, I would really like for it to not be a horrible or complicated process.
TIA
Seanbest said:
So I finally decided to attempt to flash my phone, but realized I have a build 1010. After reading about all the issues with flashing back with ODIN not working or disabling the 3 button download mode after using, I'm nervous now. I consider myself fairly tech savvy, but get easily frustrated. I downloaded Bay-wolf's AIO Tool and it took the phone into Download Mode without trouble, should this still work after flashing a new ROM, or will this not work just like the 3 button combo?
I really want to flash a custom ROM, but should I want to try another or flash back to stock, I would really like for it to not be a horrible or complicated process.
TIA
Click to expand...
Click to collapse
Yeah, I have build 1010. Flashed back via odin 1 click and needed a jig to get my phone working again. Then I found this post:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I've used this method several times and it's worked like a charm every time.
I have never lost three button combo from flashing a rom. I think that its more a concern for those who do not have it, which you obviously do, you got into dl mode.
There is a procedure out there for flashing stock in build 1010. It its not at easy as one click but it works
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
If your posting this you are going to flash. it is just a matter of when, tonight? ;p
Edit: beat me to it
mcord11758 said:
I have never lost three button combo from flashing a rom. I think that its more a concern for those who do not have it, which you obviously do, you got into dl mode.
There is a procedure out there for flashing stock in build 1010. It its not at easy as one click but it works
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
If your posting this you are going to flash. it is just a matter of when, tonight? ;p
Edit: beat me to it
Click to expand...
Click to collapse
bahaha XD
Just barely
I also have a build 1010 phone, and have used odin 1-click about a dozen times. Works great. I also keep a jig handy just in case, and would advise the same if you want to try odin 1-click. If it works, it's a bit easier than the other method.
Good luck!
My 3 button combo stopped working after flash, but it's no big deal, just use the android dev kit and a little command prompt. No biggie. Flash away!
Sent from my SAMSUNG-SGH-I897 using XDA App
bobtukin said:
My 3 button combo stopped working after flash, but it's no big deal, just use the android dev kit and a little command prompt. No biggie. Flash away!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
What's that?
Just got for it :]] You have a whole community to help you if you screw up. At least there's plenty of ways of flashing/reverting back to stock/and plenty froyo flavors to try. Rewind back two months ago and there were waaayy too many noobs that bricked their phones and only half the cool froyo-ness the xda developers came out with. 2.1 Eclair is too much of a kill-joy on this phone. You won't regret it.
Seanbest said:
What's that?
Click to expand...
Click to collapse
You can use the android sdk tools (ADB command prompts) (Think ms-dos) to put the phone into download/recovery mode if you lose the 3-button ability.
Just use the program in my signature to flash. Select the 3 button fix option and you're good to go. It's the AIO Captivate Toolbox in the Captivate Development section in case you can't see my signature.
I got a build 1010, must have done odin 1-click about 300 times now.
bay_wolf said:
Just use the program in my signature to flash. Select the 3 button fix option and you're good to go. It's the AIO Captivate Toolbox in the Captivate Development section in case you can't see my signature.
Click to expand...
Click to collapse
Already using it, it's how I enabled non-market apps and already tested Download Mode. Awesome app btw.
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
Hey guys I am currently running Hamsterbread with X'Cals latest kernel.
And I have been reading everywhere that for flashing back to stock YOU MUST use Odin One CLick and if you use the 3-Button Fixed Odin you will brick you phone for good.
If I am a build 1010 and cannot use Odin One Click do y'all think this method would work:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Any Help will be GREATLY appreciated.
The only thing that could possibly happen to a later build phone using that odin one click is you will lose the 3 button combo (MAYBE) I flash and mod 3 captivates, 1 is a 1010 the other 2 are 1012 I have never used anything other than the one click to flash to stock, never even lost the button combo on ANY of those. But if you do lose the combo just use the odin with the button fix after you use the normal one.
The one with the button combo doesn't contain the second bootloader, so if you use that to go back to eclair from gb, you will have 2 incompatible bootloaders resulting in an unfixable BRICK. The normal one click contains BOTH bootloaders that is why you need to use it. But like I said once you are back on eclair and IF you have lost the button combo then you can use the other odin to get the combo back but only AFTER using the normal one click.
I don't know if that version of odin you posted contains both bootloaders so I personally wouldnt try it because of the reason I stated earlier.
studacris said:
The only thing that could possibly happen to a later build phone using that odin one click is you will lose the 3 button combo (MAYBE) I flash and mod 3 captivates, 1 is a 1010 the other 2 are 1012 I have never used anything other than the one click to flash to stock, never even lost the button combo on ANY of those. But if you do lose the combo just use the odin with the button fix after you use the normal one.
The one with the button combo doesn't contain the second bootloader, so if you use that to go back to eclair from gb, you will have 2 incompatible bootloaders resulting in an unfixable BRICK. The normal one click contains BOTH bootloaders that is why you need to use it. But like I said once you are back on eclair and IF you have lost the button combo then you can use the other odin to get the combo back but only AFTER using the normal one click.
I don't know if that version of odin you posted contains both bootloaders so I personally wouldnt try it because of the reason I stated earlier.
Click to expand...
Click to collapse
I just hear stories about Build 1010's and up who flash back to stock using Odin One Click and then they get a soft brick where the device flashes the AT&T screen then turns off.
Luckily i have a jig but I still dont really know what to do.
Dlev7 said:
I just hear stories about Build 1010's and up who flash back to stock using Odin One Click and then they get a soft brick where the device flashes the AT&T screen then turns off.
Luckily i have a jig but I still dont really know what to do.
Click to expand...
Click to collapse
First: no such thing as a "soft brick" that's a stupid name and it confuses people ... There is one kind of brick. When the phone does exactly the same as a brick. Nothing.
If you get a bootloop after using the one click I'm pretty sure the boot loaders have been flashed successfully (not 100% sure about that so wait for someone else to confirm/deny) in which case you could use another odin to recover from that.
If you weren't sure about how to return you really shouldn't have upgraded. As the deving for gingerbread is still in it's infancy. And might not be suited for daily use yet.
If you're still worried about all of it then just stay on gb and the devs will catch up and you will have more of options for roms/kernels, and maybe another way for later build phones to flash to stock with out the one click...
studacris said:
First: no such thing as a "soft brick" that's a stupid name and it confuses people ... There is one kind of brick. When the phone does exactly the same as a brick. Nothing.
If you get a bootloop after using the one click I'm pretty sure the boot loaders have been flashed successfully (not 100% sure about that so wait for someone else to confirm/deny) in which case you could use another odin to recover from that.
If you weren't sure about how to return you really shouldn't have upgraded.
If you're still worried about all of it then just stay on gb and the devs will catch up and you will have more of options for roms/kernels, and maybe another way for later build phones to flash to stock with out the one click...
Click to expand...
Click to collapse
I flashed GB when X'Cal released his beta and I was testing for him it is recently though that people are saying that you cannot use anything but Odin One Click. And I know what I am doing in regards to flashing Gingerbread and the kernels and such so thats why I upgraded.
I will try Odin One-Click if I ever need too, but if someone can confirm or deny the fact that if you get in a bootloop after flashing Odin One-Click the Bootloaders successfuly flashed?
I would guess thats correct and then Id just use my normal method and Jig it into Download mode.
Thanks again though.
Try and go look around samfirmware.com
and see if you you can't find the .pit flies that contain both bootloaders they should have every odin file. and use the full version of odin with the other corresponding files needed.
studacris said:
Try and go look around samfirmware.com
and see if you you can't find the .pit flies that contain both bootloaders they should have every odin file. and use the full version of odin with the other corresponding files needed.
Click to expand...
Click to collapse
Alright thanks
Sorry to be a noob but what exactly should I be looking for in specific? How do I navigate and find pit files with both bootloaders are they categorized? Thanks
I actually have no idea ... I'm looking now.
Look in the toolbox section at the top and navigate your way through the menus.
I'll post it if I find it.
studacris said:
I actually have no idea ... I'm looking now.
Look in the toolbox section at the top and navigate your way through the menus.
I'll post it if I find it.
Click to expand...
Click to collapse
Alright thanks so much.
And and we are looking for a pit file with both bootloaders?
And if we find one just use regular Odin and use the .pit file we find and like a JH6 or JH2.tar file for PDA.
One last thing although there is nothing wrong and I do have a jig, you think I should try flashing Odin One Click and see what happens? : D. I dont want too because my set up currently is un real haha.
I do not think odin one click is wise, it only flashes secondary boot loader not primary. If you use it worth out chanting the primary back you will have non matching primary and secondary boot loaders. Nothing good can come of that
Sent from my SGH-I897 using XDA Premium App
the pit file has nothing to do with the bootloaders. the bootloaders are in the .tar file which is inside the zip files on samfirmware.com
the pit file is for repartitioning, probably not needed, but probably worth doing just in case
mcord11758 said:
I do not think odin one click is wise, it only flashes secondary boot loader not primary. If you use it worth out chanting the primary back you will have non matching primary and secondary boot loaders. Nothing good can come of that
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Then how in the world do we flash back to stock with Gingerbread bootloaders?
As above I said I have always flashed back to stock using the Build 1010+ method with the JH2.tar pda file. But I dont know if that will work.
Can someone who has successfuly flashed back to stock with Gingerbread Bootloaders please create like a guide hahahah
Pirateghost said:
the pit file has nothing to do with the bootloaders. the bootloaders are in the .tar file which is inside the zip files on samfirmware.com
the pit file is for repartitioning, probably not needed, but probably worth doing just in case
Click to expand...
Click to collapse
Ya thats what I thought has anyone found a firmware .tar file with both bootloaders and post it so we can create a way for people to successfuly flash back to stock with GB bootloaders.
Dlev7 said:
Ya thats what I thought has anyone found a firmware .tar file with both bootloaders and post it so we can create a way for people to successfuly flash back to stock with GB bootloaders.
Click to expand...
Click to collapse
every firmware found on samfirmware.com has the boot loaders.......
Alright so we just have to get a .tar file form one of the firmwares at Samfirmware.com and put that in the PDA file of the Original Odin and flash normally?
This particular issue its going to explode. Get ready for the omg odin one click back from gingerbread, now my phone is unresponsive
Sent from my SGH-I897 using XDA Premium App
Dlev7 said:
Alright so we just have to get a .tar file form one of the firmwares at Samfirmware.com and put that in the PDA file of the Original Odin and flash normally?
Click to expand...
Click to collapse
yep. pretty much. i would go ahead and select the box that says repartition and include the 512.pit file so that it wipes it all....
mcord11758 said:
This particular issue its going to explode. Get ready for the omg odin one click back from gingerbread, now my phone is unresponsive
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Ya I know, there is currently nothing wrong with my phone and no need but I just wanted to know to help other if the are flashing back to stock currently, and also to help me in the future.
I am just confused if you cannot use Odin One-Click or the method I used above to go back to JH2 what are we supposed to do
I just downloaded the jf6 firmware rar but I can't extract it because it's password protected??
studacris said:
I just downloaded the jf6 firmware rar but I can't extract it because it's password protected??
Click to expand...
Click to collapse
Password is either:
www.samfirmwares.com
or
samfirmwares.com
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."
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...