Database Develop

Bricked Rogers Samsung Captivate (i896)

silly me decided to install a custom battery icon. In the description for the mod on app planet it said to use with froyo but didnt say it would not work with eclair. I installed the mod without problems and I thought everything was going well, but now my phone is bricked, and wont load past the samsung i896 boot screen even after deleting all user data and wiping my cache in recovery mode. So I guess my only option now is to flash a rom using odin, but id rather prefer not to flash to a stock ATT 2.1 rom, i would like to flash back to my original stock rogers.
Is it possible to flash to an ATT rom, then do a factory reset from the privacy settings of the phone to bring me back to rogers stock rom?

ATT rom =/= Rogers rom
You'll need to search and find a Rogers rom you can stick in Odin and flash with if you want Rogers

I don't think you can easily return to Rogers stock rom using odin. Most people end up having AT&T logo on boot. However, since you're soft bricked anyways, why don't you try using Heimdall, new Open-Source Flashing Software and this dump generated from stock Rogers phone.
I haven't seen any reports of tests on Captivate yet, but it seems to work well on other Galaxies. Check Heimdall thread for more info, and if it works well for you, please report to this thread. Good luck!

thanks, i installed heimdall perfectly fine, it recognizes my device, but i cant download that PIT file from megaupload, its failed to download multiple times. Is there any other links?
I will keep trying

all good to go now,
used this rogers stock rom
http://www.megaupload.com/?d=BD2EF4WF
and flashed it without any problems. Glad to have a working phone again even though i lost everything

Did you use heimdall our some other method?
Sent from my SAMSUNG-SGH-I896 using XDA App

Hi! I just came across the same issue. I've been using the Cognition ROM on my Captivate for some months now and only today decided to switch to Perception 8. I downloaded the latter and rebooted through ROM Manager which, as I've done before, rebooted and backed up all my data. It then proceeded to erase all user data and cache and attempted to install Perception 8 ROM, but was unsuccessful. It provided me with a usual list of options, including 'Reboot', 'Backup' (i think) and others. I chose to Reboot thinking it would just go back to the last best ROM (i.e. Cognition latest, in my case).
Now it just reboots and refuses to go past the at&t World Phone boot screen.
I've tried the button combinations. Up-volume+down-volume+power button, up+power, up+home+power, down+home+power (!). All these seem to reboot the phone and in about 10 seconds after I press them, takes me right back to the same boot screen and not past it.
I'm fairly sure my old data is backed up somewhere inside.
I've tried to read the other forums, but nothing in particular seems to work for me. I run Ubuntu on my laptop, wanted to try Heimdall but its download page is down.
Any suggestions on how to proceed would be greatly appreciated.
1) Any other button combinations?
2) Any other tricks, including ways to using Heimdall (whose source files I can't seem to find), to get into my device?
Apologies for the detail, but I presume there's someone who knows exactly what I'm talking about.
OP, what software did you end up using on your computer to gain access to the device?
Thanks.

sshvetsov said:
Did you use heimdall our some other method?
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
yes i used it, installed the drivers on my pc, downloaded the rom i provided in my response and flashed it, worked flawlessly without problems.

nostratispeak said:
Hi! I just came across the same issue. I've been using the Cognition ROM on my Captivate for some months now and only today decided to switch to Perception 8. I downloaded the latter and rebooted through ROM Manager which, as I've done before, rebooted and backed up all my data. It then proceeded to erase all user data and cache and attempted to install Perception 8 ROM, but was unsuccessful. It provided me with a usual list of options, including 'Reboot', 'Backup' (i think) and others. I chose to Reboot thinking it would just go back to the last best ROM (i.e. Cognition latest, in my case).
Now it just reboots and refuses to go past the at&t World Phone boot screen.
I've tried the button combinations. Up-volume+down-volume+power button, up+power, up+home+power, down+home+power (!). All these seem to reboot the phone and in about 10 seconds after I press them, takes me right back to the same boot screen and not past it.
I'm fairly sure my old data is backed up somewhere inside.
I've tried to read the other forums, but nothing in particular seems to work for me. I run Ubuntu on my laptop, wanted to try Heimdall but its download page is down.
Any suggestions on how to proceed would be greatly appreciated.
1) Any other button combinations?
2) Any other tricks, including ways to using Heimdall (whose source files I can't seem to find), to get into my device?
Apologies for the detail, but I presume there's someone who knows exactly what I'm talking about.
OP, what software did you end up using on your computer to gain access to the device?
Thanks.
Click to expand...
Click to collapse
i used heimdall, which was linked above, but I was able to get into download mode through my phone since it was soft bricked. IF you can get back into Download mode, then you are fine... Keep trying until you do, otherwise you might have to use the JIG method.

stavs said:
yes i used it, installed the drivers on my pc, downloaded the rom i provided in my response and flashed it, worked flawlessly without problems.
Click to expand...
Click to collapse
That's great news! I'm sure a lot of rogers captivate users will be very happy to learn that. Just curious, where did the linked rom dump come from?
EDIT: Nevermind, found this thread describing Rogers stock restore procedure using Heimdall and the bundle you used.

@nostratispeak: if you have questions about Heimdall, you might want to check the official thread.

sshvetsov said:
@nostratispeak: if you have questions about Heimdall, you might want to check the official thread.
Click to expand...
Click to collapse
Yup. Just did. The site is back up and working. I've the downloaded the files too. Now, to get my phone to work.

@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
EDIT: I followed the instructions from this thread and I have the phone in what I believe, is the Download mode: Droid shoving dirt within a filled yellow triangle, with a message "Downloading" "Do not turn off Target". My device is connected to my laptop. I don't see anything popping up on the screen. I also have Heimdall frontend up and running in Ubuntu.
I've downloaded a few ROMs, including Cognition and some samsung stock firmware. There are conflicting information in different pages. Am not sure what to do next. Help?

nostratispeak said:
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
Click to expand...
Click to collapse
Your device isn't bricked as such, it's caught in a boot-cycle. This is actually worse than a soft brick and in some ways is comparable to a "hard" brick. It's comparable to a hard brick because when you're in a boot cycle you usually can't get into download mode. Presumably the only option is to use a custom JIG, as you've mentioned.
There is no official terminology but a soft brick is generally when your phone displays the "connect phone to pc" screen. A hard brick is a bit more difficult to define, but I'd say it's fairly reasonable to assume that this is when your phone won't turn on or charge. A brick (full brick?) is when your device is absolutely not recoverable by any means.

nostratispeak said:
@stavs Thanks.
Just curious. What's the difference between a soft brick and hard one? My Captivate simply refuses to get past the AT&T World Phone logo white boot screen - the very first one when you normally reboot the Captivate. I'm not sure if I'm in the 'Download' mode. And, I don't have access to the material required for the JIG. So, I'm hoping to get this done the software route.
Is there a chance that anything from my last best Cognition ROM is still active in there somewhere?
I'm also afraid that if I keep my phone ON for too long, it will simply die out and refuse to recharge.
Thanks.
EDIT: I followed the instructions from this thread and I have the phone in what I believe, is the Download mode: Droid shoving dirt within a filled yellow triangle, with a message "Downloading" "Do not turn off Target". My device is connected to my laptop. I don't see anything popping up on the screen. I also have Heimdall frontend up and running in Ubuntu.
I've downloaded a few ROMs, including Cognition and some samsung stock firmware. There are conflicting information in different pages. Am not sure what to do next. Help?
Click to expand...
Click to collapse
thats great news than, now with the one of the downloaded roms you have saved on your computer, take the data (ie Factoryfs.rfs,cache.rfs, modem.bin and Zimage) and link it appropriately in the program. Then just click the start button and it will automatically install the rom within minutes. You shouldnt see anything pop up, i dont remember seeing anything, but during the installation there should be a download bar on your phone to indicate data is being transfered and downloaded to your phone. After your phone should reboot and be back to normal.

stavs said:
all good to go now,
used this rogers stock rom
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Click to expand...
Click to collapse
Does this remove the AT&T boot logo and replace with the Rogers logo as well? Stavs, I'm assuming you went from the Rogers ROM, back to the Rogers ROM, so this probably not apply to you, but have any of you guys been able to get rid of the AT&T logo from a previous flash, and restore the Rogers logo using this method, and ROM?

stavs said:
all good to go now,
used this rogers stock rom
megaup*****com/?d=BD2EF4WF
and flashed it without any problems. Glad to have a working phone again even though i lost everything
Click to expand...
Click to collapse
used the same rom flashed it with odin but didnt load the pit file... made sure re-partitioned was UNchecked and off i went... restored my phone to 2.1 and was finally able to get kies to recognize my phone and upgrade it after 5 days in hell trying various things, flashing different "stock" ROMs... i finally did it tho... running froyo as we speak...

I am not sure if anyone suggested this already but i896 users can flash stock Rogers 2.1 using this method. No AT&T screens. Works great.
http://forum.xda-developers.com/showthread.php?t=979133

[Q] Galaxy S Problem...(S Logo Boot)

Hiya guys.
I've searched the forum as much as I can to try and solve my problems and it's got me so far but I can't find any more information to get my phone back working properly so though I'd bite the bullet and make a thread. If the information I require is actually lurking out there then I apologise just please point me in the right direction.
Here is my story.
Right I rooted my device through some video I followed on youtube (I cant post the link)
I think it successfully (as far as I know) rooted my SGS.
So with my newly rooted SGS I downloaded Darky's ROM and followed the instructions in the guide to flash it onto the device.
In the end it failed and the phone powered off and wouldn't power back on.
Panic Ensued.
I have since got my phone back into the download mode and flashed froyo 2.2 (I downloaded from some link on this site) it said it was successful but now it won't boot past the Samsung Galaxy S logo.
Please help?
Thanks alot in advance.

try to do a factory reset in recovery (sometimes it works)
and another thing, it may be that the froyo rom you downloaded was bad or something..
try to use this one with odin if the factory reset wont work. i know this one works.
Flash as PDA using Odin with repartition enabled and 512 pit
http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
that one fixed my friend phone when something slimier happened to him.

Right thanks alot mate don't know what the hell happened but left it off and just turned it on and now it's working fine!
Scared me a little that I nearly bricked it but I really wanna try installing a new rom but don't wanna break it again :S

Just read the flash instructions and you won't have any problems.
Sent from hell to take your soul

When you flash it can take up to 10 minutes for the 1st boot, so go have a cup of tea and be patient!
Sent from my GT-I9000 using XDA Premium App

Ah right that was my first time so it might have just been me being impatient and thinking it wasn't working because it had been broken.
Also just wondering, the link I downloaded this Froyo ROM from (from another thread on here, can't find it now) is it custom or stock?
Heres some details...
Firmware version
2.2.1
Kernel version
2.6.32.9
[email protected]#36
The phone feels much snappier than before!
I'm new to all this ROM/flashing bees wax so just wondering.
Thanks muchly!

If its from some thread on here its custom some how some way (unless you just changed the kernel - which is speedmod - a very popular one - from your details.
G

Yeah it's off here from a thread I was reading on how to sort my phone being stuck in download mode.
Is it alot faster than the original rom I was running then?

Flash to stock without Odin?

Hey guys. Forgive my lack of knowledge with the Captivate please, as I don't own one. I'm coming from the Evo 3D forums. My friend has a Cappy, and is having issues connecting to the pc via USB. I've searched a bit for some info, and all I came up with that was relevant was this :http://forum.xda-developers.com/showthread.php?t=808580. His problem started with extreme battery drain, lagginess, and freezing up. He decided he wanted to flash back to stock, and at that time discovered that his PC no longer recognizes the device. He gets an error complaining of unrecognized device. Apparently you need to run Odin in order to flash back to stock, from what I understand. Since his computer won't detect the phone, he can't use Odin. The phone does charge via USB and A/C. Also, he said that when he shuts the phone down, it won't reboot unless he does a battery pull, or reboots it from recovery.
Basically what I'm wondering, is there a way to flash back to stock without using Odin? With my Evo, you have two options of flashing back to stock. One, is using the RUU executable file from Windows, and letting that flash the phone back to stock. The other is to put a file called PC36IMG.zip on the sd card (of course the file would be pre packaged with the same images as the RUU would use) and boot to the bootloader. At that point, the bootloader would detect the file and ask to update. Then it'd flash back to stock using the bootloader, thus eliminating any need for a computer. Is there anything like that with the Sammy's? Thanks in advance for any input.
Btw, he has tried re-installing the drivers already, and is going to pick up a new usb cable on his way home. He hasn't tried the new cable yet. I know cables fail, but I'm skeptical due to the other issues he's having with the phone. It all started at the same time. I'm not sure which rom he was using at the time, I'm waiting for him to reply to me with that info. I know a month or so ago he was on some version of Cognition, but am not sure if he still was.

k2buckley said:
At that point, the bootloader would detect the file and ask to update. Then it'd flash back to stock using the bootloader, thus eliminating any need for a computer. Is there anything like that with the Sammy's? Thanks in advance for any input.
Click to expand...
Click to collapse
No the captivate dosen't have something like that (at the time maybe one day), their is heimdall which is an open source alternative to odin.
Why are you posting for your friend? if he's running on a custom ROM shouldn't he have an account?

k2buckley said:
Hey guys. Forgive my lack of knowledge with the Captivate please, as I don't own one. I'm coming from the Evo 3D forums. My friend has a Cappy, and is having issues connecting to the pc via USB. I've searched a bit for some info, and all I came up with that was relevant was this :http://forum.xda-developers.com/showthread.php?t=808580. His problem started with extreme battery drain, lagginess, and freezing up. He decided he wanted to flash back to stock, and at that time discovered that his PC no longer recognizes the device. He gets an error complaining of unrecognized device. Apparently you need to run Odin in order to flash back to stock, from what I understand. Since his computer won't detect the phone, he can't use Odin. The phone does charge via USB and A/C. Also, he said that when he shuts the phone down, it won't reboot unless he does a battery pull, or reboots it from recovery.
Basically what I'm wondering, is there a way to flash back to stock without using Odin? With my Evo, you have two options of flashing back to stock. One, is using the RUU executable file from Windows, and letting that flash the phone back to stock. The other is to put a file called PC36IMG.zip on the sd card (of course the file would be pre packaged with the same images as the RUU would use) and boot to the bootloader. At that point, the bootloader would detect the file and ask to update. Then it'd flash back to stock using the bootloader, thus eliminating any need for a computer. Is there anything like that with the Sammy's? Thanks in advance for any input.
Btw, he has tried re-installing the drivers already, and is going to pick up a new usb cable on his way home. He hasn't tried the new cable yet. I know cables fail, but I'm skeptical due to the other issues he's having with the phone. It all started at the same time. I'm not sure which rom he was using at the time, I'm waiting for him to reply to me with that info. I know a month or so ago he was on some version of Cognition, but am not sure if he still was.
Click to expand...
Click to collapse
There is a JH7 and a KB1 cwm flashable around here somewhere. Use the search button, it is your friend. and it has a better memory than I do.

speedy_11 said:
No the captivate dosen't have something like that (at the time maybe one day), their is heimdall which is an open source alternative to odin.
Why are you posting for your friend? if he's running on a custom ROM shouldn't he have an account?
Click to expand...
Click to collapse
Thanks, I didn't think so. And yea, he has an account but is a lurker, and was at work, so I posted for him.
mrhaley30705 said:
There is a JH7 and a KB1 cwm flashable around here somewhere. Use the search button, it is your friend. and it has a better memory than I do.
Click to expand...
Click to collapse
Thanks. I'll check it out. And yea, I know all about the search button (I did actually use it, just didn't have time to learn all the Sammy stuff). It's just that I don't have a Sammy, and everything here is wildly different than HTC. I didn't have the time to learn everything I'd need to in order to understand all the different terminology. I'll search for a JH7 and KB1 (although I don't even know what they are, haha) Sorry again for posting in your forum without having much knowledge on the Sammy stuff, and thanks for taking the time to reply.

It is my phone!!
The whole reason behind this is that I have till the end of August till the warranty expires. Running Serendipity VII. The phone will only boot with battery install, or power and volume up into recovery then reboot. So I want to go back to stock except PC won't see the phone. New cable, different PC deleted and re-install drivers. Still get usb device not recognized. With phone powered off plug in charger and nothing happens. Used to get image of battery. Any help or suggestions would be appreciated.

Thanks. I'll check it out. And yea, I know all about the search button (I did actually use it, just didn't have time to learn all the Sammy stuff). It's just that I don't have a Sammy, and everything here is wildly different than HTC. I didn't have the time to learn everything I'd need to in order to understand all the different terminology. I'll search for a JH7 and KB1 (although I don't even know what they are, haha) Sorry again for posting in your forum without having much knowledge on the Sammy stuff, and thanks for taking the time to reply.[/QUOTE]
Don't apologize for asking a question, that's why there is a q&a section. Search is a lot easier if you know what it is your searching for.
Jh7 and kb1 are firmware. Jh7 is the ota update that followed the release of jf6 (what a lot of captivates were shipped with) and is android 2.1. Kb1 is the 2.2 version that people upgraded to with kies mini(kies mini is the samsung online upgrade program).

[Q] FASTY III problem/question

HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.

When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.

HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK

studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again

Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.

I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.

If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?

No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS

studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^

All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.

studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....

the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.

Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!

another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...

Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.

oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!

[Q] How do I reboot after installing ClockworkMod?

I attempted to root my SGS (which had stock Gingerbread Value 2.3.6) using a guide on the Snappyguides blogspot page (the system won't let me, as a newbie, post the URL).
Odin did its thing and then the Samsung Galaxy screen came up (just the white lettering, not the multicoloured animated S) and then... nothing. It just stayed like that for about five seconds, then the white Samsung Galaxy S came up again, then the blank screen ad infinitum.
I can access the download screen and I can access the recovery screen (which does seem to indicate that ClockworkMod v2.5.1.0 has been installed). The trouble is that none of the options seem to do anything.
I have tried searching the forum for similar problems and have read the sticky. The only answers I seem to have been able to find so far suggest flashing a new Rom.
Before I go this far, is flashing a new Rom really necessary in this instance? I have never done this procedure before, so I'm wary of messing things up even further. But obviously if the phone is past the point of no return as far as the stock Rom is concerned, then that'll be what I have to do.
I'd appreciate some advice before doing anything else to my phone though.

I now seem to be able to get the recovery menu options to respond, so maybe all is not lost. Have set it to root and it's currently converting to EXT4 and is about halfway through that.
I'm hoping once that's done, it'll be bootable.
If not, what do I need to do to make the SGS boot again? Is there any way of getting back to stock or can I only flash a stock rom back on?

Nope, still not booting. It just keeps going to the Samsung I9000 white lettering, stays there for five seconds, goes blank for five seconds, then the white lettering goes back and on, off like that forever.
So... anyone willing to help?

...

have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879

Lexrsk said:
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Click to expand...
Click to collapse
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.

evilcartman2 said:
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
Click to expand...
Click to collapse
I'll help u, I went through this when I was a noob and because I didn't know about xda I had to just figure a way out, I am sorry to say but u have soft bricked your phone, luckily its not hard to unbrick, here's a link to a post i made the other day with proper guides that I use often and they are noob friendly, the files u need to download are there but it 2.3.3 and it JW4 but it will be a start to get ur phone back to life,
If you like my posts hit thanks

Here the link http://forum.xda-developers.com/showthread.php?p=25572245
If you like my posts hit thanks

OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.

evilcartman2 said:
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
Click to expand...
Click to collapse
Yip I guess that is right. I have never tried it but yes it should work
If you like my posts hit thanks

Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?

evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Yeah that or the wrong root file for ur baseband
If you like my posts hit thanks

evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Check in about phone for the kernel version. for example mine is 2.6.35.7-I9000TDVJV6-CL530973
The important part is the bold text.
search the link that i posted earlier for a odin version and flash as PDA
Good luck

Evilcartman, when u wanna get me help find me on the I9000 q&a-ask me anything I got the answer thread, it where I spend most of my time.
If you like my posts hit thanks