Database Info

What exactly bricks a Captivate?

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

[Q] Flashing Back To Stock With JVB *BUILD 1010*

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

Odin Stock Restore Stuck at Partition

So it seems like the first time stuck so it restarted, now it's stuck at partition. I selected the PIT and the PDA stock file, but it's just sitting there ... I'm on the phone + PC logo.
Am I totally screwed? What to do?

What pit did you select?

gtg465x said:
What pit did you select?
Click to expand...
Click to collapse
The one from the xda thread additional infuse files

bella92108 said:
The one from the xda thread additional infuse files
Click to expand...
Click to collapse
Not seeing that thread. Please provide a link.

i think he means from lost1
@op i think the 512pit from the sgsphones will work

gtg465x said:
Not seeing that thread. Please provide a link.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1084837
in OP additional files

It gets stuck at "Setup Connection.."

im gonna go out on a limb here and say use h8rifts stock rom with the 512pit found in the i9000 and captivate sections. h8's rom is missing the param.ifs though, not sure if you will need that.

Dani897 said:
im gonna go out on a limb here and say use h8rifts stock rom with the 512pit found in the i9000 and captivate sections. h8's rom is missing the param.ifs though, not sure if you will need that.
Click to expand...
Click to collapse
So I've been able to use the 512 pit and get it to get back to the "Downloading... Do not turn off Target". ... but then when I go back in and try to flash the stock Rooted ROM I get the "Initialization..." then it just stops there... ideas?

not sure. let it sit for a while. h8rift or somebody said it took his like 20 minutes(if i remember right) which seems weird. also you should be logged in windows as admin and the usb plugged into a port that connects to the mother board not a expansion card or hub.
honestly though i have only used heimdall on the infuse. and never repartitioned because heimdall requires bootloaders for repartition. im not sure i trust lost1's bootloaders and if there is an issue with them there are no others to use.
it might be a driver issue. maybe samsung needs some updated drivers for the infuse.
also are you sure you have your .net framework up to date on windows? i cant think of everything odin depends on but i think having .netframework4 helps with some things on the phone, cant remember ifodin depends on it though

Dani897 said:
not sure. let it sit for a while. h8rift or somebody said it took his like 20 minutes(if i remember right) which seems weird. also you should be logged in windows as admin and the usb plugged into a port that connects to the mother board not a expansion card or hub.
honestly though i have only used heimdall on the infuse. and never repartitioned because heimdall requires bootloaders for repartition. im not sure i trust lost1's bootloaders and if there is an issue with them there are no others to use.
it might be a driver issue. maybe samsung needs some updated drivers for the infuse.
also are you sure you have your .net framework up to date on windows? i cant think of everything odin depends on but i think having .netframework4 helps with some things on the phone, cant remember ifodin depends on it though
Click to expand...
Click to collapse
So I've been able to get it to say FACTORYFS now. I decided to just try the NON-rooted stock file to see if maybe it'll work. Right now it says Firmware update Start.... and there's a tiny green line flashing, but it's just been sitting there for 5 mins alrady.... just let it sit?

bella92108 said:
So I've been able to get it to say FACTORYFS now. I decided to just try the NON-rooted stock file to see if maybe it'll work. Right now it says Firmware update Start.... and there's a tiny green line flashing, but it's just been sitting there for 5 mins alrady.... just let it sit?
Click to expand...
Click to collapse
cant hurt to leave it there a little longer. the captivate never took that long but we also had a true factory flash oneclick odin that they use to reset refurbished phones. no such luck on the infuse unless someone wants to see if designgears has some sort of connection at samsung who can get it like he somehow was able to get it for the captivate. the significance of odin oneclick is that is has all the files. param.ifs, boot.bin, sbl.bin, and all the first boot scripts. our stock roms have come from rom dumps. the captivate stock roms came from samsung.
i would leave it for a good 20 minutes. then try something else. you may need to try files from lost1's stock rom you can use 7zip to manipulate the .tar files and magic ISO to manipulate the .rfs files within the .tar files, but atleast one ofthe files from lost1 doesnt work. if i had 2 infuses id experiment with you to be able to post what works and what doesnt. with only one phone im hesitant to try anything that is not tested

Dani897 said:
cant hurt to leave it there a little longer. the captivate never took that long but we also had a true factory flash oneclick odin that they use to reset refurbished phones. no such luck on the infuse unless someone wants to see if designgears has some sort of connection at samsung who can get it like he somehow was able to get it for the captivate. the significance of odin oneclick is that is has all the files. param.ifs, boot.bin, sbl.bin, and all the first boot scripts. our stock roms have come from rom dumps. the captivate stock roms came from samsung.
i would leave it for a good 20 minutes. then try something else. you may need to try files from lost1's stock rom you can use 7zip to manipulate the .tar files and magic ISO to manipulate the .rfs files within the .tar files, but atleast one ofthe files from lost1 doesnt work. if i had 2 infuses id experiment with you to be able to post what works and what doesnt. with only one phone im hesitant to try anything that is not tested
Click to expand...
Click to collapse
I'm using H8rift's restore... and both of the two (rooted and non) have the same issue for me.
It just sits... I've used the rooted and non-rooted.... ugh.
It goes to firmware update start then has a little greenness in the progress bar on the computer, and a little blueness in the progress bar on the phone, but I let it sit for 30 minutes and it never progresses any further, so there's something going on.
I've tried other usb ports, updated drivers, every method of compatibility and admin mode, even reinstalled windows basic version, haha.... ugh, this is hopeless.
I think it's time to chalk this up to a very very expensive lesson learned and go out and buy a replacement... not happy about that :-(

bella92108 said:
I'm using H8rift's restore... and both of the two (rooted and non) have the same issue for me.
It just sits... I've used the rooted and non-rooted.... ugh.
It goes to firmware update start then has a little greenness in the progress bar on the computer, and a little blueness in the progress bar on the phone, but I let it sit for 30 minutes and it never progresses any further, so there's something going on.
I've tried other usb ports, updated drivers, every method of compatibility and admin mode, even reinstalled windows basic version, haha.... ugh, this is hopeless.
I think it's time to chalk this up to a very very expensive lesson learned and go out and buy a replacement... not happy about that :-(
Click to expand...
Click to collapse
Why did you use a .pit? Did I not state in the OP of the Odin thread not to use one? take out the .pit, uncheck re-partition and flash the package as it was originally attended. you will NEVER need to re-partition your phone until we actually start CHANGING your partitions sizes (i.e. CM7, MIUI, possibly Samsung's gingerbread, etc.)

h8rift said:
Why did you use a .pit? Did I not state in the OP of the Odin thread not to use one? take out the .pit, uncheck re-partition and flash the package as it was originally attended. you will NEVER need to re-partition your phone until we actually start CHANGING your partitions sizes (i.e. CM7, MIUI, possibly Samsung's gingerbread, etc.)
Click to expand...
Click to collapse
He doesn't follow directions well.This much we know. He royally screwed up flashing my ROM as well and then proceeded to blame his problems on my ROM being crappy.

gtg465x said:
He doesn't follow directions well.This much we know. He royally screwed up flashing my ROM as well and then proceeded to blame his problems on my ROM being crappy.
Click to expand...
Click to collapse
Sorry to hear that.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

I am putting up another Odin package right now for him to try if h8rift's doesn't get him going since he tried to repartition.

gtg465x said:
I am putting up another Odin package right now for him to try if h8rift's doesn't get him going since he tried to repartition.
Click to expand...
Click to collapse
...... She ...
Sent from my SAMSUNG-SGH-I997 using XDA App

Gtg the man
hoofadoo said:
...... She ...
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
see how nice he was to help you! ive listened to these guys from day one never one problem and if there is they help you untill its fixed. they were once like us too bu now deserve respect in the developing\helping noob world lol

Poor bella, she seems to be having a tough time lately...
Sent from my Samsung Infuse 4G

[Q] Download mode but unable to unbrick

Just what everyone wants.... another thread about a bricked phone.
I have no idea what happened to my phone.... I have been running Valhalla Final for a week now with no issues to speak of and lost all my ringer tones after a failed attempt to put sound on a boot-loader using Absolute System. I rebooted into recovery and tried to restore my nandroid which failed when it said unable to unmount system. when I rebooted it had fc in android.core multiple times so I rebooted again and after it loaded had no control. did a battery pull and then would not go past the power up screen. downloaded heimdall one click file T959V-UVKJ6-One-Click.jar and put it into download mode. flashed and it went fine until factoryfs failed. now still in download but img is pic of phone to computer. last 2 attempt was
SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar and it failed first at loading the modem and then at loading recovery.
I am lost. seems like everything I try makes it little worse. Have not tried ODIN yet.
Is there any hope or am I out a phone?

Give Odin a try. Last time I used Odin it froze so I pulled the plug, and when I put my phone back in download it showed that same screen, yet Odin still went through.
So no, that screen doesn't mean you're out a phone.
Sent from my SGH-T959V using xda premium

95Z28 said:
Give Odin a try. Last time I used Odin it froze so I pulled the plug, and when I put my phone back in download it showed that same screen, yet Odin still went through.
So no, that screen doesn't mean you're out a phone.
Click to expand...
Click to collapse
I was hoping to hear that... what odin file do you suggest... A lot of the links are now dead.

ShadyAce80 said:
I was hoping to hear that... what odin file do you suggest... A lot of the links are now dead.
Click to expand...
Click to collapse
Grab chadster's KG4 here. I believe it has ODIN 1.85 included in the file. Don't mess with any of the check boxes in ODIN; let ODIN decide what to check.
After that, you should be able to get back to KJ6 via a one-click.

Shady grab Ravers stock GB and honks GB odin kernel. Flash Ravers, If you can, then honks. That will give you stock plus cwm. You know where to go from there. Funny thing is just yesterday FB had a post about leaving BOOTLOADERS alone w/o unbrickable mod. Good luck.

Downloading now from sendspace.com
I'm hoping this works...

hechoen said:
Funny thing is just yesterday FB had a post about leaving BOOTLOADERS alone w/o unbrickable mod. Good luck.
Click to expand...
Click to collapse
LOL yeah I read that AFTER the fact... I have been messing with the animations for a few days with out issue... it was only after I trying sound for a day or two that I crashed.
Live and Learn

ShadyAce80 said:
Downloading now from sendspace.com
I'm hoping this works...
Click to expand...
Click to collapse
wait no dude i downloaded that one from sendspace does the download stop and download stop download etc... for you? it did for me i think the files corrupt thomas.raines gave me a newer download link that one from sendpsace is like 197mb the one thomas gives me is 300mb and he said dont flash pit file (he did not include ) because is risky try this one first!!! i tried the sendspace one and it stop at setup connection...
http://dl.dropbox.com/u/54863010/T959VUVKG4.zip

shady
Are you going with the chadsters leak or ravers stock?

I don't know why you guys keep recommending old (leaked) ROMs to debrick with.
@Shady if you see anything posted by myself, dsexton, bhundven or raverx3x you can bet that we've tested it extensively and that it'll work on your phone.
On that note I recommend you read the whole page here:
http://forum.xda-developers.com/showthread.php?t=1358498
Download from the SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders link. This will get you a one click flash solution that you can go back to when you have problems. This, unlike the KG4 file others have been recommending, is the latest version of gingerbread (KJ6 is 2.3.6) and you'll have a custom kernel + root to boot so you can get flashing other gingerbread ROMs. I hope you don't have trouble flashing, and if you do, read the OP to what I linked you to. All the instructions are there.
I know this file has been failing for you but you can try restarting your computer and flashing it from safe mode. When your computer is booting up, keep pressing F8 until you get a menu. Pick "Safe mode with networking" from the menu using your arrow keys and press enter.

sorry too many tabs open

FBis251 said:
I don't know why you guys keep recommending old (leaked) ROMs to debrick with.
Click to expand...
Click to collapse
Only because he was failing with one-clicks and wanted to use ODIN. That one (KG4) has always worked for me, so I was basing it off of experience. Never claimed it was optimal
I know this file has been failing for you but you can try restarting your computer and flashing it from safe mode. When your computer is booting up, keep pressing F8 until you get a menu. Pick "Safe mode with networking" from the menu using your arrow keys and press enter.
Click to expand...
Click to collapse
Never thought about trying it from safe mode. Nice idea.

FBis251 said:
I don't know why you guys keep recommending old (leaked) ROMs to debrick with.
Click to expand...
Click to collapse
That's what I'm saying. I don't use heimdell(because my computer hates it for some reason). So ravers stock GB and honks kernel to get cwm works well to set me back up.

ShadyAce80 said:
glad you posted this. download just completed. i haven't done anything with this file yet... will follow your link.
Click to expand...
Click to collapse
oh after they say to flash the bhuvden kernel well that is what they told me to get rid of gremlines or something, then flash the custom rom, youll have cwm and such, tell me how it goes .

To all of you thank you very much for your help... I think I have my phone back.... Our fembot Linda is doing her thing right now...
@FB I tried one click method in safe-mode and it was unable to find the drivers even after reinstalling a few times.. restarted in normal mode and gave it one more shot and I now have my phone back.
Thanks again for all the help.

hechoen said:
That's what I'm saying. I don't use heimdell(because my computer hates it for some reason). So ravers stock GB and honks kernel to get cwm works well to set me back up.
Click to expand...
Click to collapse
I totally forgot he made a stock ODIN. My bad!

I really need to rewrite the starter pack to have heimdall one click instructions. Nobody ever got around to making it.

I've only given the guide a cursory look at times, but I'd be willing to draft something for the guide if thst helps keep you focused on developing.
Sent from my SGH-T959V using xda premium

stephen_w said:
I've only given the guide a cursory look at times, but I'd be willing to draft something for the guide if thst helps keep you focused on developing.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
A video would be perfect. Been busy with school since I just started and now I got a gig making a website so I'm also working on that.

FBis251 said:
A video would be perfect. Been busy with school since I just started and now I got a gig making a website so I'm also working on that.
Click to expand...
Click to collapse
I've never done the video thing. Guess I can research it and give it a go.

Weirdest thing I've ever seen in my Android life. Help!

OK I'm in front of the weirdest thing I've ever seen in my Android life. Turns out I got my Infuse 4G and turn it back to stock AT&T Gingerbread 2.3.6 using Heimdall One-click Back-To-Stock UCLB3, and in the middle of process it seems my USB port disconnected my phone and I though I would see a brick, but thank God it was not that bad (I thought). I change the USB port and put my Infuse in download mode again, passed the tool again and everything went like heaven (again: I thought). I got my stock AT&T Gingerbread 2.3.6, but I never seen CWM anymore, I just can't because the weirdest screen I've ever seen (you'll see).
I thought my phone was unrooted, so I maded my way straight to SuperOneClick v2.3.3 and begin the simplest process. Well... it was unable to root my phone and believe me, it's not ADB problems, I know it because I can install apps through Android Commander without any problem... so that's the first weird thing I have here.
Until that moment I thought my phone was bad-flashed or something, so I tried with another tool, the mythic Odin with h8rift's [UCKD5] Odin - Stock (Root+3e) and with my device in download mode it never shown itself as COM## on Odin (required to start the process), however I clicked on PDA button, selected the .tar.md5 file and start the process that never started (logically).
So right now I have no idea what to do or where to go.
I'm apologize if I explain every little detail, the thing is that most of the time one get answers starting with "You did this?" "Have you tried that?" I all I want is to avoid that. For example, I have USB debugging, ok? Another thing someone could ask.
Please help me guys. I madded a video so you can see what happens when I try to enter CWM. Even when my phone starts, during AT&T logo screen flashes with a strange distortion. I madded this video and post it to YouTube so you can see what is hard for me to explain.
Please HELP!
I need anything that from scratch clean everything and put my phone shiny.
Best regards.

You have "rainbows" because you don't have Gingerbread bootloaders.
You need to use odin a GB leak or Heimdall a GB leak to correct the problem.
Your initial failed flash on heimdall was due to a bad connection -usb data cord or computer usb port.

qkster said:
You have "rainbows" because you don't have Gingerbread bootloaders.
You need to use odin a GB leak or Heimdall a GB leak to correct the problem.
Your initial failed flash on heimdall was due to a bad connection -usb data cord or computer usb port.
Click to expand...
Click to collapse
Man I thank you with all my heart... can you give me some resource? Sorry to bother you with that, the problem is I've been reading since yesterday and my head is about to explode.
Please I'll appreciate it.
Best regards.

Stickied "Super Thread" in Development.
Sent from my SAMSUNG-SGH-I997 using xda premium

Radiotsar said:
Stickied "Super Thread" in Development.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks, I'll check it right now

alainalemany said:
Man I thank you with all my heart... can you give me some resource? Sorry to bother you with that, the problem is I've been reading since yesterday and my head is about to explode.
Please I'll appreciate it.
Best regards.
Click to expand...
Click to collapse
There are some links on my signature line, including the superthread.

If reading right, you are on uclb3 now. Soc can't root that. I don't think anything can. You have to load another kernel. Like qkster said see his sig. I used both uclb3 packages two night ago. Both work.
(thanks qk)
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Well that is really a super thread... right now I have no idea what to do, where to go. Please can anyone tell me which option take in order to disappear this "rainbows", root my Infuse and finally can install whatever ROM I want?
Best regards.
EDIT: OK I've installed (again) Heimdall UCLB3 2.3.6 but with the Flash Bootloader box checked and everything goes like heaven, NO MORE RAINBOWS However I can't root it with SuperOneClick v2.3.3, why is that? How can I root it?
Best regards.

I see you have not read either the original post
http://forum.xda-developers.com/showthread.php?t=1524081
there clearly says that the only way to root in 2.3.6 is by flashing DD Entropy512's kernel.

kalebdevil said:
I see you have not read either the original post
http://forum.xda-developers.com/showthread.php?t=1524081
there clearly says that the only way to root in 2.3.6 is by flashing DD Entropy512's kernel.
Click to expand...
Click to collapse
OK I flashed Entropy512's kernel correctly but the problem is now I see only Samsung logo, I'm stuck there. However I can see a red CWM.

qkster said:
You have "rainbows" because you don't have Gingerbread bootloaders.
You need to use odin a GB leak or Heimdall a GB leak to correct the problem.
Your initial failed flash on heimdall was due to a bad connection -usb data cord or computer usb port.
Click to expand...
Click to collapse
Why is it that you can go from froyo stock rooted with cwm recovery straight to flashing zeus for example? What step added the gingerbread bootloaders? Just trying to learn myself!
Sent from my SAMSUNG-SGH-I997 using XDA App

SnowBeer said:
Why is it that you can go from froyo stock rooted with cwm recovery straight to flashing zeus for example? What step added the gingerbread bootloaders? Just trying to learn myself!
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
from froyo with recovery, you can flash any rom. bypassing the bootloader.
a lot of people do this w/o prob until they run into recovery issue.
i'm not sure re: the exact architecture why this occurs.
the kernel gurus can tell you more.
if you use odin, and install one the gb leaks, you will have that BL, until you do a repartition with gtg's ultimate unbrick which brings you back to froyo. I think you will lose the bl's.
In good practice, I use the 1click heimdall w/ repartition - these are packaged with "official" GB leaks. imho, i believe they are better suited for a base to get to your custom GB rom.
if you're running infused 1.6, there is no needed 'cause it's froyo.
no rainbows there
edit: to each his/her own i guess. the reason why gtg's "unbrick" seems like a life saver is due to repartition with PIT files image.
the heimdall 1 click does the same thing but takes the guess work out from the inexperience user.