What exactly bricks a Captivate? - Captivate General

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

Related

[Q] Build 1010 and afraid to flash

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.

How I hard bricked my Captivate (FYI)

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

flashing back & forth between gb & froyo

i just wanted this all in one place.i wanted my daily driver to be torch or fusion cause of call quality but also want to play around on gb roms.i found a safe way to go back and forth.if something happens to your phone i'm not responsible this is what works for me.
1.flash gb stock just like it says here:http://forum.xda-developers.com/showthread.php?t=1045734
2.i wanted mosaic on to play around with so i flashed mosaic.now from mosaic( I have only tried mosaic so far) you can flash back to 2.2 or 2.1 rom that has NO secondary bootloaders(this is very important).and you have to be on http://forum.xda-developers.com/showthread.php?t=1042543 the kernel from here in order for this to work cause it uses cwm 2.5 still.
3.make sure you wipe data/factory reset and also wipe cache partition and dalvik cache in between flashing roms.
4.if on talon kernel you cant flash from 2.3 to 2.2 cause it uses cwm 3.0.so you need to get kernel flasher from market and the this file http://etc.muteheadlight.net/android/I9000_reoriented_vG.1.1_novoo.tar and flash it from kernel flasher it will put you back on cwm 2.5 and you can go back to 2.2 from there.
this has worked for me several times today i wanted to make sure it worked go and thank all the devs on there respected paged.they work hard on all this development show some appreciation.
again dont mix boot loaders make sure the rom you are flashing does not flash boot loaders.just stay on gb boot loaders.as it is stated you will brick your phone mixing boot loaders.
I hope this helps some people out and explains it good enough.
I just use odin one click to flash back to stock then flash by froyo rom of choice.
To Gingerbread from 2.1 bootloaders:
odin flash bootloader and reorient kernel package HERE (7mb)
odin flash talon or other kernel with CWM3 built in
boot into CWM3
CWM3 flash GB wipe rom!
Back to Eclair/Froyo: (keeping GB booties)
Odin flash a Kernel with CWM2.5 built in (onix)
boot into CWM2
CWM2 flash 2.1 or 2.2 wipe rom.
------AVOID ROMS WITH SBL (secondary boot loader) LIKE A PLAGUE!!! or built-in 3 button fix!----- YOU WILL BRICK!!
****To not worry about mixing Bootloaders or the SBL on Eclair/Froyo roms flash odin-one-click to get stock booties before Odin flashing a Cwm2.5 kernel.
Easy Peasy Lemon Squeezy
i also use odin one-click to get back to stock
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
studacris said:
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
Click to expand...
Click to collapse
I'm on a mac I have a pc around but I swear if you saw it you'd be a little nervous to it's a cheap old lap top running xp it doesn't even have a battery, I'd be fine with odin if I had faith in my pc. That being said don't mention heimdall it doesn't recognize 2.1 bootloaders so in order to move up I still need odin.
Sent from my SAMSUNG-SGH-I897
heimdall doesnt recognize 2.1 bootloaders? really?
how was it created with 2.1 bootloaders before the 2.3 ones ever existed??
thats news to me.... learn somethin new every day...
*sarcasm*
This an interesting post from the guys that wrote heimdall the first is a list of confirmed devices that work with heimdall the eighth post is a list of confirmed working bootloaders and osx compatability i9000 this should give you an idea of what I'm talking about. Out of ten only two support osx. As far as the i897 is concerned if you ever flashed your phone with odin 1click and I have the boot loaders included do not support osx. THAT'D be a fact . *touchee*
Sent from my SAMSUNG-SGH-I897
Here's the linkhttp://forum.xda-developers.com/showthread.php?t=891518
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
no problems so far.just wipe everything and factory reset clear data in recovery the key there is to be in cwm2.5 and not 3.0. and to never flash anything with secondary bootloaders.
Hey if Im currently on a JVH ROM, and want to try out the Galaxy Sense i9000, but the whole deal about the bootloaders is a little irrating. And its even trickier for me to go back to stock considering I have a build 1010, thus One Click soft bricks my phone (*I have a jig*). But it really isnt a big deal because I use the JH2 method and iCezars method for flashing back without risk, without replacing the bootloaders. Those are the two methods I have had to flash back to stock while on a Gingerbread ROM.
But my question lies in whether I can flash back to stock using one of the two methods I stated above which DO NOT FLASH BOOTLOADERS and follow the instructions in the Sense i9000 thread (This isnt a how to, to flash, because from December--February all I did was flash MIUI and CM7), but rather do you know if I could flash with GB bootloaders or would it be too big of a mess?
And if I cant can someone point me into a direction of a .tar file that contains BOTH BOOTLOADERS such as Odin One Click but I have to use Odin 3 and manually put it in and flash.
Thanks!
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
studacris said:
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
Click to expand...
Click to collapse
Hmm.. I was seriously thinking that but I was worried that it would completely brick the phone because it does flash both bootloaders thus completely bricking the phone.
If I knew I could just Jig it back like ive had to do twice when I used Odin One Click Id use the JH2 package or Cezars and be good.
But since im playing with bootloaders Im worried that it will completely brick cause One Click doesnt even work on my phone.
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
studacris said:
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
Click to expand...
Click to collapse
yes I know that im not trying to argue you with you... hahah
Im just saying that I dont know Im just a little hesitant as I havent used Odin One Click in a while, plus the fact that it'll be twice the nerve racking coming from Gingerbread Bootloaders.
That is the one thing that is a little scary, but I know if anything flashes on to the screen im good to go, but just a little nervous, but am seriously considering just using the Odin One Click, and just praying that it at least flashes the AT&T screen then off like it normally does.
But I dont know if it'll work the same with GB, I know its mostly in my head but hahahaha
EDIT: I havent used One Click in a while should I wipe my phone before? And secondly I assume disabling lagfix?
FLASHED ONE CLICK.... Going now I will keep it posted when I get back to stock.
the bootloaders though flash went well so I think im in the clear. Lets hope : D
UPDATE: It soft bricked, Jig--> now on Stock.
THANKS SO MUCH!
No problem man.
TRUST THE ZOMBIE!!
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Soccer_Dad said:
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Click to expand...
Click to collapse
please read post 3
i wrote it. i know its there..

bootloaders! aka fix the rainbow garbage on awesome rom leaks

ok i see since it has been so long since all the rogers development started people dont really remember about all the rainbow problems and how they were fixed and how the fix needs source code.
we now have bootloaders available in leaks from samsung. they are needed with the stock kernels that come in the leaks to avoid rainbow garbage. i am providing the bootloaders to be flashed in heimdall without having to flash a whole rom.
i would like to make this explicitly clear that if this bricks your phone i am not to blame. there is a significant risk when flashing bootloaders! though the infuse seems to have safety measures i strongly recommend only flashing once. and if your phone becomes a brick you will need to solder things to the phone to fix it via j-tag or adam outlers unbrickable mod. be cautious! dont flash boot.bin without sbl.bin, dont flash sbl.bin without boot.bin, dont mix up the partitions, and if the phone bricks i dont want to know about it unless you want to pay me to fix it!
heimdall package
http://www.multiupload.com/GXUTF4QCJX
odin package (untested)
http://www.multiupload.com.... REMOVED May be failing to flash. very dangerous situation...
bootloaders for heimdall to be added through the "flash" tab (unzip first! ibl/pbl-boot.bin, sbl-sbl.bin)
http://www.multiupload.com/NAIA23JZL1
good luck!
Thanks for posting this. Hopefully it will help out with leak questions that tend to get asked over and over again.
Sent from my SAMSUNG-SGH-I997
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
MattSoRaven said:
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
Click to expand...
Click to collapse
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
yes. that's how I would do it. the PDA slot seems to be automatic as far as partition sorting. the phone slot is for modems but if a modem is included in a package for the PDA slot it flashes just fine. the bootloaders are in the PDA packages normally so that's how I would do it.
please report results because I don't run windows and did not test that package.
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Dani897 said:
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
Click to expand...
Click to collapse
I've been using the UCKJ2 bootloaders since they came out with no issues.
Entropy512 said:
I've been using the UCKJ2 bootloaders since they came out with no issues.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
schmidtty661 said:
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
Click to expand...
Click to collapse
don't select repartition, no need for a pit, the rom shouldn't matter, the file should go in the PDA slot. remember I haven't tested it in Odin. I don't run windows and have little interest in using Odin for anything. phone needs to be in download mode just like flahong a rom. it should only take a second or two to flash. good luck
Cool i should be able to figure this out. Thanks for the quick response.
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
schmidtty661 said:
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
Click to expand...
Click to collapse
I have a bunch of downloads but nobody reported anything at all till now.
ill pull the Odin version for now. try it in heimdall. its not any harder to use.
Can you post an odin package.
I had an Odin package. I got a few downloads, didn't get any people thanking for it, didn't get any positive feedback that it worked and had one user report problems, see the last couple posts. I pulled the file for lack of evidence that it worked. I don't run windows and prefer heimdall so I haven't tested it in Odin. sorry but I suggest you either flash an entire rom leak then flash a non secure kernel through Odin ( any custom kernel should do also flashing back to stock should also do just fine) and then flash a rom or learn heimdall which works on windows as well as Mac and Linux. I would have done a oneclick package but it still requires the installation of the heimdall back end and I figured it was really no harder to just use the heimdall package system.
any chance of relink thats not at multiupload?
edit: disregard, found a workaround. might be useful in future tho.

[Q] Where to start...

Ok so I have a rooted infuse 4G and am a complete noob when it comes to flashin roms and mods... I am still on the froyo 2.2.1and hate it lol. Which brings me to my first query, I know its possible to upgrade my android version to the GB and JB with multiple methods but I'm extremely scared that I'm going to brick my phone. It was some forums on here that helped me decide to root my phone so now I'm hoping that you guys can help me take the next step. So whats the safest, easiest way to upgrade my os.. Odin didnt work and I no longer have a computer, so heimdall is out as well. Oh not sure if this is important but I'm not registered on any network nor have I unlocked my phone's sim. Well that's a start. I really hate froyo 2.2.1 so please if anyone can help I definitely could use it.
treyserits said:
Ok so I have a rooted infuse 4G and am a complete noob when it comes to flashin roms and mods... I am still on the froyo 2.2.1and hate it lol. Which brings me to my first query, I know its possible to upgrade my android version to the GB and JB with multiple methods but I'm extremely scared that I'm going to brick my phone. It was some forums on here that helped me decide to root my phone so now I'm hoping that you guys can help me take the next step. So whats the safest, easiest way to upgrade my os.. Odin didnt work and I no longer have a computer, so heimdall is out as well. Oh not sure if this is important but I'm not registered on any network nor have I unlocked my phone's sim. Well that's a start. I really hate froyo 2.2.1 so please if anyone can help I definitely could use it.
Click to expand...
Click to collapse
From Froyo 2.2.1, there is an official build GB 2.3.6 UCLB3 out for the Infuse.
You will need a computer though. Without a computer to restore your phone to stock from soft bricking, you should not be flashing anything. It may be possible for you to bring your phone to an AT&T store and have them update you if you don't have a PC. You will need a computer to root the GB UCLB3.
Where to start? Read the Q/A as much as you can. Then move into the Development section.
http://forum.xda-developers.com/showthread.php?t=1437548 - read it all
thanks
qkster said:
From Froyo 2.2.1, there is an official build GB 2.3.6 UCLB3 out for the Infuse.
You will need a computer though. Without a computer to restore your phone to stock from soft bricking, you should not be flashing anything. It may be possible for you to bring your phone to an AT&T store and have them update you if you don't have a PC. You will need a computer to root the GB UCLB3.
Where to start? Read the Q/A as much as you can. Then move into the Development section.
http://forum.xda-developers.com/showthread.php?t=1437548 - read it all
Click to expand...
Click to collapse
Thanks qkster.. I really appreciate your help. I follow alot of your threads and am so hapoy thst there are infuse users that actually are willing to take the device to the next lvl. Now for another question.
Will it be easier to flash the jellybean 4.1.1 from the froyo or the gb? Or would it be possible to just flash a higher kernel? I'm not syre if that would help me or not, I really want to speed up my infuse and stop it from rebooting so much.
treyserits said:
Thanks qkster.. I really appreciate your help. I follow alot of your threads and am so hapoy thst there are infuse users that actually are willing to take the device to the next lvl. Now for another question.
Will it be easier to flash the jellybean 4.1.1 from the froyo or the gb? Or would it be possible to just flash a higher kernel? I'm not syre if that would help me or not, I really want to speed up my infuse and stop it from rebooting so much.
Click to expand...
Click to collapse
You cannot flash JB from Froyo and need to go to Gingerbread, then ICS then JB.
http://forum.xda-developers.com/showthread.php?t=1878458
Kies?
psal217050 said:
You cannot flash JB from Froyo and need to go to Gingerbread, then ICS then JB.
http://forum.xda-developers.com/showthread.php?t=1878458
Click to expand...
Click to collapse
Would it be best to use kies to update to GB? I'm a little concerned as to what would happen to my Infuse all around.. What will need backed up?
I have titanium backup but if the app gets wiped wont i lose all my back-ups? For some reason it wont sync to my dropbox app force closes every time I try. Sorry about all the questions I'm just short on the amount of time I am able to browse threads at the moment but I do have use of a computer for awhile so that kinda helps.
I personally prefer using odin or heimdall. Don't quite trust kies and it often gives issues.
all mayor changes will occur on system partitions. Your internal sd will remain untouched, and there you will titanium backups. Just reinstall TB app later and restore apps, not data.
Sent from my SGH-I997 using xda app-developers app
Ok well here goes nothing.
andros11 said:
I personally prefer using odin or heimdall. Don't quite trust kies and it often gives issues.
all mayor changes will occur on system partitions. Your internal sd will remain untouched, and there you will titanium backups. Just reinstall TB app later and restore apps, not data.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Well I'm going to install and give it a try with Heimdall. I'll let you know how it goes. Thanks everyone for all your help. I'm sure I'll have more questions before long. XD
andros11 said:
I personally prefer using odin or heimdall. Don't quite trust kies and it often gives issues.
all mayor changes will occur on system partitions. Your internal sd will remain untouched, and there you will titanium backups. Just reinstall TB app later and restore apps, not data.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Will this even work if i'm not registered to a network with the phone still locked? And I see that it will also unroot my phone which isnt a problem I'm just curious whether or not I can still root with super one click or if i need a different root tool?
treyserits said:
Will this even work if i'm not registered to a network with the phone still locked? And I see that it will also unroot my phone which isnt a problem I'm just curious whether or not I can still root with super one click or if i need a different root tool?
Click to expand...
Click to collapse
It doesn't matter if your phone is unregistered and locked. You cannot use SuperOneClick on Gingerbread. What you should do is (this is the Heimdall version):
Flash this rooted version of stock GB:
http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
You do that and you already have root.
If you want to then graduate on to Jelly Bean you must:
Flash ICS (follow directions carefully!):
http://forum.xda-developers.com/showpost.php?p=24901014&postcount=1
Once you've done that, flash any of the JB ROMs you like, but make sure to read the directions carefully. I strongly recommend that you consult the Super Everything Thread for links to the ROMs and tweaks you need, particularly if you are interested in unlocking your phone.
http://forum.xda-developers.com/showthread.php?t=1610374
I'm feeling kinda stupid..
Can somebody give me the right link for downloading Heimdall One-click w/root? For some reason I'm not able to get any to work on this computer.. I downloaded the ink provided labeled UCLB3 -DEBLOATED-ODEX - ROOTED - BUSYBOX- STOCK KERNEL on
http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
but am unsure if that actually is the one containing Heimdall or just the rom i'm flashing or both.. I'm extremely sorry about my noobishness of just posting all these already answered questions. I've gone and confused myself and have like ten tabs with different threads open please don't hate me. I have a bad habit of asking questions..
Oh and what apps do i need on my phone in order to flash? And I mean absolutely need. I've also noticed that most threads say to format my mounted sd card But i really dont want to do that if i dont need to.
It should all be bundled together. Heimdall is a java based interface so it should just open up. Sorry, it's been a long time and I'm an Odin person!
You don't need any apps on your phone. When you flash, everything on the small partition will be wiped (apps, app data, etc). Flashing will not usually wipe your pictures, videos etc. but it's always a good idea to back up. For now, don't worry about formatting anything. When you get to ICS, you'll need to format as it says in the instructions. Otherwise, if it works, don't fix it!
When you flash ICS and JB, all you need to do is to put the zip files on to your internal SD card (not the one you can take out). You can then flash from CWM (which will already be on your phone - don't download Rom Manager).
Once again thank you all. I'm running GB and loving it. My fiance is shocked at how much help I needed though usually I'm the person everyone comes to with their tech issues LOL. But I absolutely did not want to mess my infuse up. I thought I did but the issue was such a noob mistake that I had to smack myself in the face at my stupidity. Forgot to unzip the cwm ect folder I downloaded. XD not sure I'm ready to try ICS or JB yet though.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
The odd thing is you could have updated to GB through AT&T and used mini kies. But at least you are now rooted and able to go to ICS and JB.
Read the instructions on the next step before moving on.
Sent from my SGH-I997 using xda premium
Kinda wish I would have done it that way... I wanted to get some practice flashing roms tho. And now my phone is bootlooping, computer says the device is incompatible I can only get into the samsung recovery even tho the rom i flashed had cwm packaged in. I tried to change my boot animation following the steps provided in my boot animation thread then again with the steps in tsqers rom thread I apologise if thats mispelled. I tried updating from sd but get a sign error Can get into download mode but same issue with it being incompatible usb device. I tried holding down the power button for 1 minute and then rebooting no luck there. I tried wiping data/fact. reset,... nothing. I tried wipe cache partition,...still looping.
The loop samsung screen two seconds, black screen 1 1/2 seconds,... over and over and over...
My battery is full. Any advice???
treyserits said:
Kinda wish I would have done it that way... I wanted to get some practice flashing roms tho. And now my phone is bootlooping, computer says the device is incompatible I can only get into the samsung recovery even tho the rom i flashed had cwm packaged in. I tried to change my boot animation following the steps provided in my boot animation thread then again with the steps in tsqers rom thread I apologise if thats mispelled. I tried updating from sd but get a sign error Can get into download mode but same issue with it being incompatible usb device. I tried holding down the power button for 1 minute and then rebooting no luck there. I tried wiping data/fact. reset,... nothing. I tried wipe cache partition,...still looping.
The loop samsung screen two seconds, black screen 1 1/2 seconds,... over and over and over...
My battery is full. Any advice???
Click to expand...
Click to collapse
Which ROM did you flash and which CWM recovery can you see (which version)?
I used the http://forum.xda-developers.com/show...43&postcount=2 thread to get the rooted rom UCLB3 -DEBLOATED-ODEX - ROOTED - BUSYBOX- STOCK KERNEL.
Saved I think.
So I finally Got it to connect to my comp and re-flashed the rom can i get a link to an ICS heimdall one click package to flash before restoring anything and this happening again?
You should be able to find it on the ISET page.
http://forum.xda-developers.com/showthread.php?p=32876425
Sent from my SGH-I997 using xda premium

Categories

Resources