Database Develop

[Q] Bricked phone after JI6/Odin

Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?

You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.

ApplCobbler said:
Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
Click to expand...
Click to collapse
I feel your pain. Been there, done that. Although your process of bricking reminds me of a more sophisticated approach....lol....mine was out of total complete noobness.
Question:
1) Can you manually boot into download/ recovery manually using 3-button combo? If so you have hope (meaning your phone is basically "un-brickable").
-Bet that made you feel better huh?
-If you can't use 3-button to go into either modes, then you are in the same boat as i was. Hope you are still within your 30 days, or at least warranty. One way to tell if you can/ can't go into either modes is to check your "Batch #."
a) remove battery
b) look below your Serial Number
c) if your Batch # = 1007 = You are safe
d) Batch # = 1008 = good luck
2) When you say Brick, do you have the unfortunate "Phone (!) PC" screen? If yes, then its a "soft brick." If No, then its a "hard brick." I would start to worry.
3) According to your post, it sounds like you have the Regular Odin and NOT the One click version, correct? If you have regular Odin, i would at least try the One click. Regardless, both versions should be able to get you back to stock (JF6), but we already know how well your current version Odin has gotten you.
If you need help, there are TONS more knowledgeable people here in the Captivate forum than I. They should be able to help.
Good Luck!

1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.

Stop trying to flash Froyo. Flash back to stock then master clear. Then go read the threads in the development section of the forum before flashing anything. The fact that you tried to apply Voodoo to Froyo and you tried to use one click lagfix on Froyo shows you haven't read and don't know what your doing. You corrupted something by flashing incompatable stuff, flash back to stock and master clear for now. Read a bit and then flash Froyo.

ApplCobbler said:
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Click to expand...
Click to collapse
LOL . I as well. I know enough to be dangerous.
Now, on to business. If you actually read what Rhiannon has posted for you, and click on the actual link itself, you will realize that the version of Odin you are using (yes the one click) is NOT the correct version for flashing back to stock (JF6/ Eclair.....NOT froyo). Remember, if all else fails....."The One must return to the Source...." <-----Plus 9,000 to whoever can guess where thats from.
Obviously your phone falls within the 1007 since you have the Luxury/ Advantage of manually entering Download/ Recovery mode....i wish i did.
Rhiannon224 said:
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
Click to expand...
Click to collapse
Well Said!

Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.

Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Click to expand...
Click to collapse
I see you are still on Cog 2.2 B5......dont care for 8 or any of the new ones? Or Sheps? What's your story?
Mine is simple....Patience. lol

I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.

Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
Click to expand...
Click to collapse
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.

Rhiannon224 said:
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Click to expand...
Click to collapse
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"

spartan062984 said:
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
Click to expand...
Click to collapse
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.

ApplCobbler said:
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Click to expand...
Click to collapse
Again, sorry if I sounded harsh, i am just trying to help you get out of the mess you're in. You can flash Froyo in the future you just need to learn about these ROMS and fixes so you don't have these kinds of headaches. I will stop repeating now. i really hope this works. I know your stressed and wasn't trying to give you a hard time, I just thought you were missing something and I am from NY and we are pushy Let us no if you get it working.
I have made some mistakes along the way too and it was because I didn't read the instructions clearly so I do understand how you felt.

Rhiannon224 said:
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
Click to expand...
Click to collapse
""Sory to hijack the thread""
I started it. No worries. I too would love to have voodoo. So far, with stock OS, ext2 + OCLF seems to work for me....for now. Keep in mind that i too would like to have the functionality of a Phone. That was my intention in the first place...lol.

A little help for a n00b.

Alright. I have a Captivate on AT&T. It's bricked. It was one click rooted and had Perception 9.5 installed. I did the clockwork mod automatically when I rooted. I didn't use Odin. I dragged the Perception zip onto the SD. Restore mode via 3 button, install. I ran it first time no prob. I kept it for about 7 days, and I decided I wanted to try 10.1, and then if that didn't work, ROMkitchen custom.
So, I needed to go back to stock, right? I saw the Odin3 version, but on Designgear's thread, the Odin3 link was broken. So, I dl'ed the JH7_OTA.zip file, dragged to my SD, 3 button restore mode, install. WRONG! I now have a perma-AT&T screen. I don't wanna mess anything up, as I know just enough to get in trouble.
Please excuse me, as I'm sure it's been answered somewhere. I'm new from iPhone, and I know forum manners. I'm on my way out to my job, where I'll remain for the next 5 days. I only have access to an XP machine.
Please help if you can, and thanks in advance.

Find a link for a reupload of the Odin One Click, its in the thread. And then put your phone into download mode then flash.

ShredNasty said:
So, I needed to go back to stock, right? I saw the Odin3 version, but on Designgear's thread, the Odin3 link was broken. So, I dl'ed the JH7_OTA.zip file, dragged to my SD, 3 button restore mode, install. WRONG! I now have a perma-AT&T screen. I don't wanna mess anything up, as I know just enough to get in trouble.
Click to expand...
Click to collapse
No you really didn't need to go back to stock, but that's water under the bridge now. I don't know which firmware you need for your particular phone. For a batch 1009 and earlier this should be fine. For others you may need this. Personally, I'd stay away from the one-click which disables button combos on all newer builds.

K, well I feel dumb. I dl'ed Odin3, discovered "restore mode" and "download mode" aren't the same thing, put my phone in dl mode, clicked start on Odin, and was finished. Super simple back to stock.
Thaks for the help though guys. I appreciate it....

opcow said:
No you really didn't need to go back to stock, but that's water under the bridge now. I don't know which firmware you need for your particular phone. For a batch 1009 and earlier this should be fine. For others you may need this. Personally, I'd stay away from the one-click which disables button combos on all newer builds.
Click to expand...
Click to collapse
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?

ShredNasty said:
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
Click to expand...
Click to collapse
If you manage to mess things up to the point you can't flash a custom ROM through recovery/CWM. Or if you need to exchange/return the phone for some reason.

ShredNasty said:
So, going back to stock isn't needed when changing ROMs? Under what circumstance do I need to flash stock?
Click to expand...
Click to collapse
In my opinion, only if nothing else works. I went a couple of months flashing mine dozens of times without using odin. I only flashed to stock prior to sending my phone back to Samsung to see if I could get the GPS fixed/improved.

Right on man. I appreciate it. I'm learning fast. Next time I flash, I'll just flash right over P10.1....

From what I've read since joining this community is that people tend to have mixed results/opinions about flashing to stock before changing ROMS. Personally, I always do... Each Captivate out there seems to have different quirks that do odd things from time to time, and are sometimes completely random. If you have no problem simply flashing a new ROM over what your using currently... by all means. If you have problems or Force Close issues.. try going back to stock first... All depends on what you are comfortable with..

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] Boot Loop after soft brick and re-flash... Help!

So I can't even describe how many things I frigged up here. This is the basic way it all went down: I went to replace my boot image using a method I found from the guy that does the Mobile Tech Videos. His batch file pushed some stuff (I think it made changes to the file system?) and unfortunately I kept getting the garbage screen on startup instead of my logo. I was still able to boot into Fasty III v1.3 though.
I went looking for an alternate method and found one that dated back to January 2011. It involved a different push to the filesystem (I think) and a .PIT file. Well, then the phone soft-bricked. I was still able to get into download mode, so I flashed I896UXKH2-HOMEBINARY.tar.md5 which, if I recall, is the stock Rogers Gingerbread update. Now I'm stuck boot-looping between the Rogers splash screen and the Galaxy S animation. I'm not sure if it's because there are just way too many things going on in terms of bootloaders, kernels, file system changes and ROMs. Volume UP + Home + Power doesn't seem to get me into recovery mode, although I may be able to do that using adb... not sure. I had Boogs kernel on there, and Fasty III. Did they get wiped when I applied the KH2 tar?
I'm basically looking for the proper method to get this thing back to stock 2.3.3 so I can learn from my mistakes and, more importantly, get my phone working.
Heading to dinner, I'm hoping someone can link me to a guide so I can tackle this when I get back. If you have any questions about any more specifics I will try and answer when I get back home.
Thanks in advance!

So I've found a post on XDA for the Odin Master Wipe (One-Click)... I'd rather not lose my internal SD storage, does anyone know if there is a slightly more complex route to take that would restore all of the stock bootloaders, kernels and ROM?

I am going to say you might have messed up your Partition. You need to find what ever is a "stock" PIT for your phone. I can assume the I897's should work but I don't know. That garbage screen in the beginning seems like either the image was corrupted or you messed up on the process. Either way I would recommend either a 1 click to JF6 (if your phone like those) or use that same KH2.tar with a suitable PIT assuming KH2 is froyo or eclair. If that KH2 is GB try a froyo first, fix your phone then worry about GB. I use a i897 so I could be way off on this.

prbassplayer said:
I am going to say you might have messed up your Partition. You need to find what ever is a "stock" PIT for your phone. I can assume the I897's should work but I don't know. That garbage screen in the beginning seems like either the image was corrupted or you messed up on the process. Either way I would recommend either a 1 click to JF6 (if your phone like those) or use that same KH2.tar with a suitable PIT assuming KH2 is froyo or eclair. If that KH2 is GB try a froyo first, fix your phone then worry about GB. I use a i897 so I could be way off on this.
Click to expand...
Click to collapse
The I897 and I896 are, as far as I am aware, virtually identical. I'll try to find a stock partition file for Gingerbread I896/7. I just flashed the device with the stock 2.3.4 file found in this thread, http://forum.xda-developers.com/showthread.php?t=1232703 but I'm guessing you might be right about having frigged up the partitions. Thanks.

armadadrive said:
The I897 and I896 are, as far as I am aware, virtually identical. I'll try to find a stock partition file for Gingerbread I896/7. I just flashed the device with the stock 2.3.4 file found in this thread, http://forum.xda-developers.com/showthread.php?t=1232703 but I'm guessing you might be right about having frigged up the partitions. Thanks.
Click to expand...
Click to collapse
Well, I'm boned. I flashed the PIT file and then the device wouldn't even power on. So I finally frigged my way into download mode again and now I'm trying to apply the Odin One-Click program with the Master Wipe. Any other suggestions would be grand.

And now, it seems that Odin One-Click is hanging at the Set PIT file... command. It's been at least 10 minutes. This phone is still capable of download mode, I must be able to restore it!
Dammit.

Right click the Odin and run as administrator first then connect in download mode. Be sure to hook up your usb end to the back of the computer or if laptop- to the first port. And you may need to reboot your computer just cause.

^ What he said. DO NOT try restoring partitions with a package with bootloaders, reduce risk to hard brick

4-2ndtwin said:
Right click the Odin and run as administrator first then connect in download mode. Be sure to hook up your usb end to the back of the computer or if laptop- to the first port. And you may need to reboot your computer just cause.
Click to expand...
Click to collapse
Any attempt to get into recovery or download now has left me with
RST_STAT = 0x1
PWIC = 0x3c
...
etc. I'm sure this is a screen that is not a good sign.

What about pulling battery and then trying to get into download mode.
If that does not work, then u need a Jig.
Don't worry, I have seen that screen or one similar on my phone as well. But a jig got me into download.
Will ur phone power on at all ?

Well, six lines of red hex status codes. This can't be good.

At this point I can't seem to get it to do anything but the six lines of code. That seems to pop up with the typical recovery combo. I don't have a jig, not exactly sure what that is but at this point I'm looking for any suggestions to get me into Download mode. Pull battery, sim, leave them in, whatever might help. This is the most boned I've ever been with an Android phone and unfortunately I need to rely on your experiences in the matter because I am not ready to give up on this phone. It's still a challenge and I love that, but this is also my primary mode of communication and I am the primary contact for my band.

This post will show you how to make a Jig... [HOWTO] *Layman's iGo Jig* [Solderless]

Thankfully, I just got 'er back into download mode... I'll let you know.

Unbrickable mod doesn't cost that much . I think 30-40 bucks....and if your handy you can do it yourself ., to prevent hadlrdbricks
Sent from my SAMSUNG-SGH-I897 using XDA App

Odin One-Click just seems to hang now...It's now sitting at File Analysis. I am happy that Download Mode is still available, but I'm really unsure of what to do. I'm on a laptop, Dell StudioXPS laptop with Vista 32-bit, I ran ODIN3Excution v1.00 as administrator but I'm still getting nothing. I also moved the cable to the USB port closest to me.

True but those $30-$40 + shipping can reach close to $100 on my end, dont know for someone in Canada.
Do you have spare cable? Wich ODIN 1 click you using ?

prbassplayer said:
True but those $30-$40 + shipping can reach close to $100 on my end, dont know for someone in Canada.
Do you have spare cable? Wich ODIN 1 click you using ?
Click to expand...
Click to collapse
Yeah, I have a spare cable. I don't think there is anything wrong with the cable, I think my tinkering has progressively made the situation worse. I am not going to spend money on this, there IS a process I can follow I'm sure. I HAVE Download mode capability, and a working computer. The Odin One-Click I'm using is showing Odin2Excution v1.00 in the title bar.
What did I do? **** up the partition table? So the bootloader doesn't know where to find the ROM? How can I undo this mess simply?

What I find most ironic is that I've successfully flashed kernels and roms to the phone, but the minute that I go and try to change the boot image, I friggin' brick the phone.

Go to dev section on one of the stikies and download Cezar's bootloaderless JF6 and give it a go.

[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!