Fatal flashing addiction - Captivate Q&A, Help & Troubleshooting

Hello astute folks on XDA!! My name is Brian and i'm a flash-a-holic. I'd like to share with you my experience that ultimately lead to me fubaring my beloved captivate.
I've flashed everything under the sun on this phone from roms to different kernels to modems. You name it, i flashed it with great success (after researching, never flashed on a whim.) UNTIL... Yesterday.. lol.. I was running a leaked 2.3.4 gingerbread rom and i noticed the problem first starting while trying to connect my phone to my computer via usb. The two didn't communicate when for the last 6 months, every single time i plugged in, my computer and phone recognized each other every single time. So that was my first clue that something aint right. Next thing i did was power the phone off. Went to turn it back on and NOOOOPPPEEEEE!!! Nothing!!!!! Held all three buttons and the little grey circular icon came on (the one that is initially in the battery icon when the phone is powered off but it's plugged in) but immediately shut off. Nothing turned my phone back on, but i was able to get into download mode. So thats what i did. I used odin3 oneclick to go back to stock eclair thinking that that will start everything all over, erase the bad/corrupt files and so forth. Flash was successful. Got back to stock eclair and got stuck in MTP initialization (you know, the screen in which you get if your debugging mode wasn't checked.) But it hung on that screen. No buttons would allow my to exit so, I pulled the battery. Then, the same damn thing.. I could NOT get the phone to power back on. Lesson learned for me. (today i learned that going back to stock is NOT a fresh install.) Used odin again, but this time unplugged my cord BEFORE i got to the eclair boot screen. As i'm peering at this home screen, i noticed that my USB connecting notification was flashing on, off, on, off yet my cord was unplugged. At this point i called tech AT&T tech support because i knew i was screwed. (i told them i tried to update to the 2.2 they provided on website and the phone cut out, lol).. I spent an hour on the phone and got no where other than determining that my phone is farked and they are gonna send me out a replacement (which will take 4 to 6 days) because luckily it was under warranty still. Tech support couldn't get my phone to turn on, but i could, lmao.. So... here i am stuck with a phone where usb debugging mode is buggin out!!!!!!! To wrap this story up, what i did was got back into download mode and flashed gingerbread bootloaders and a kernel and voila!! So long as i don't turn my phone off, i have a fully operational phone until my new cappy arrives in the mail in 4-6 days. (Dicks.. If i had been ordering a new phone, i'd have the option for next day shipping but thats another story.)
TLDR: Flashing too much will get you in a bad situation. Stick with a rom/modem/kernel setup that suits your needs because your next flash could be your last depending on the components in your phone.
EDIT: MAKE IT KNOWN THAT I HOLD NO ONE RESPONSIBLE OTHER THAN MYSELF FOR THE FUBARING OF MY CAPPY!!!!!!!!!!

Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.

Things break...and ppl make mistakes... I'm still trying to figure out which one happened in your situation.
Sent from my SGH-I897 using XDA Premium App

That's a common hardware issue with the captivate. Happened to me twice. Its just the USB port spassing out thinking tthe cable is constantly getting plugged in and unplugged and freezing tthe phone with its craziness. Both times it was replaced under warranty. I'm paranoid it'll happen again now that I'm out of warranty.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

speedy_11 said:
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Click to expand...
Click to collapse
Oops, my bad!! It needs to be somewhere as a precaution to those that think flashing is completely harmless
EDIT: upon further contemplation, it really is a question of what went wrong
Sent from my GT-I9000 using XDA Premium App

I am a flash addict as well
i have flashed all froyo based roms on my cappy !
Can anyone confirm that excessive flashing may risk my phone?

Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

Thanks for the quick response....!
now i dont need to worry

xijar said:
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'm 99% sure my board failed because of cheap, unreliable components. However, that 1% is still in the back of my mind that it could have been from something I flashed. I suppose I'll never know.
Sent from my fubared, soon to be replaced cappy running GT-I9000 gb rom using XDA Premium App

It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

Accidental post. Please delete.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

xijar said:
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
As I started before, the phone is fully functional with gingerbread other than the occasional usb flickering..Only problem I have with it really is if I turn the phone off, it won't turn back on unless I hold power and volume up, enter cwm and then select reboot now.
Before I send it back, I'll odin back to jf6 first with oneclick. Without cwm on the phone, lol, it absolutely won't turn on by just using the power button. I made sure of this before I even called the warranty department and explained my dilemma
The nice thing is that I can use the phone while I wait fire the new one to arrive AND I can flash and experiment with everything now without worries!!!
Sent from my fubared chappy running GT-I9000 GB rom using XDA Premium App

I am also a flash-o-holic and I think that if you flash with odin lots with repartition checked or are enabling/disabling voodoo lots, it can mess up your phone. Has happened to me twice, just sent my phone today for the second time. Both times this happened to me it happened when successfully flashing back to stock with 512.pit and repartition checked. On boot up it stalls at the "S" screen and never goes past it and in recovery I get some errors like:
error: can't mount /dev/block/mmcblk0p1
error: can't mount sdcard
I flashed many different firmwares with different pit files and different android versions but all conclude the same, stuck at the "S" boot screen.
I have determined that the partition tables were messed up and I tried to fix it by putting parted on my phone and trying to repartition it from the shell. Both times I get the "unable to write to /dev/block/mmcblk0 - I/O error!" Also, from CWM Recovery I try repartition sdcard but it also comes up with an error. The last time I sent it into Samsung repair they had to replace the main board to get it working properly again. Think it is definitely a good idea to find a rom / kernel / modem you are happy with and stick with it for a while.

Related

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

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

Odin trouble!!!

I rooted my samsung captivate and installed the custom rom ginger clone. It wasn't increadably stable but it was ok. I wanted to try axura because apperantly it was very good, so i tried to use the odin 1-click thing and it seemed to work but then when it booted up it would get to the "AT&T world phone" thing and then it would go to a black screen for about 5 seconds then back to the world phone screen for about 20 min (actually the first time it turned on all the way was in the middle of class and I almost got it taken away) but it would eventually turn on. I have tried to get it into recovery/download mode but it won't work. I would like to know how to get my phone back to normal. Also when I go to update on settings or on kies mini it tells me i can and will let me download should i try this. Also I really don't want to try the usb jig if possible.
Samsung Captivate
Samsung-SGH-I897
Firmware 2.1-update1
baseband I897UCJF6
Kernel Version 2.6.29 jetaek.lee(at)sep-11 #2
Build number ECLAIR
Ok I got the usb jig specificly what odin should i get. I would prefer a link... I don't want to take any chances.
yamato2 said:
I rooted my samsung captivate and installed the custom rom ginger clone. It wasn't increadably stable but it was ok. I wanted to try axura because apperantly it was very good, so i tried to use the odin 1-click thing and it seemed to work but then when it booted up it would get to the "AT&T world phone" thing and then it would go to a black screen for about 5 seconds then back to the world phone screen for about 20 min (actually the first time it turned on all the way was in the middle of class and I almost got it taken away) but it would eventually turn on. I have tried to get it into recovery/download mode but it won't work. I would like to know how to get my phone back to normal. Also when I go to update on settings or on kies mini it tells me i can and will let me download should i try this. Also I really don't want to try the usb jig if possible.
Samsung Captivate
Samsung-SGH-I897
Firmware 2.1-update1
baseband I897UCJF6
Kernel Version 2.6.29 jetaek.lee(at)sep-11 #2
Build number ECLAIR
Click to expand...
Click to collapse
what batch phone do you have? (look under battery on back of phone). Mine is 1006 and I believe any made with 1009 (possibly 1010) or later won't be able to "one-click" back to JF6 and have to go back to JH7 instead. if you have one that can't go back to JF6 and tried to flash JF6, it's my understanding that there isn't a fix without the USB JIG... and having the JIG is always a safe bet/good idea.
also: wrong section, Q&A next time
If your phone is batch 1008 through 1010, Odin one-click will not work properly. Download Odin v1.7 and flash JH3 or later.
Update: http://forum.xda-developers.com/showpost.php?p=10309886&postcount=1469
I made a USB jig without even cutting any cables. Just some resistors and tape (and a steady hand).
What about the samsung update should i do that?
GGXtreme said:
If your phone is batch 1008 through 1010, Odin one-click will not work properly. Download Odin v1.7 and flash JH3 or later.
Click to expand...
Click to collapse
Not true, I have a 1010 and can one click back to 6 no problem, I just have to make sure I have an update.zip around and the 3 button fix. OP I think your best bet is to take out your battery leave it sit for about 5 minutes, startup one click on your computer, put battery back in phone and hold volume up & down while putting in the usb to your phone. Flash back to stock and profit!
Works for me every time.
Sent from me using this thing.
sjkoellner said:
Not true, I have a 1010 and can one click back to 6 no problem, I just have to make sure I have an update.zip around and the 3 button fix. OP I think your best bet is to take out your battery leave it sit for about 5 minutes, startup one click on your computer, put battery back in phone and hold volume up & down while putting in the usb to your phone. Flash back to stock and profit!
Works for me every time.
Sent from me using this thing.
Click to expand...
Click to collapse
well strike my whole comment, I guess I have a 1011, swore it was a 10!
sjkoellner said:
Not true, I have a 1010 and can one click back to 6 no problem, I just have to make sure I have an update.zip around and the 3 button fix. OP I think your best bet is to take out your battery leave it sit for about 5 minutes, startup one click on your computer, put battery back in phone and hold volume up & down while putting in the usb to your phone. Flash back to stock and profit!
Works for me every time.
Sent from me using this thing.
Click to expand...
Click to collapse
Same here...I had a factory new 1009..and had no issues...However...I am wondering if many who are having this using 1008..1009...1010 builds up..are having their problem with factory refurbs..or new phones..? Is Samsung doing something to the refurbs that is causing this issue ?
Mac
I have two phones from batch 1010...For one of them the 1-click works every time for the other I needed to use a Jig and JH3 + Odin 1.7 to get back in.
onelight said:
I have two phones from batch 1010...For one of them the 1-click works every time for the other I needed to use a Jig and JH3 + Odin 1.7 to get back in.
Click to expand...
Click to collapse
Are they both new factory issues..or is one of them a refurb and is the refurb one the one you can't?
Mac
Mac11700 said:
Are they both new factory issues..or is one of them a refurb ?
Mac
Click to expand...
Click to collapse
both factory new and got them both at the same time...
sjkoellner said:
Not true, I have a 1010 and can one click back to 6 no problem, I just have to make sure I have an update.zip around and the 3 button fix. OP I think your best bet is to take out your battery leave it sit for about 5 minutes, startup one click on your computer, put battery back in phone and hold volume up & down while putting in the usb to your phone. Flash back to stock and profit!
Works for me every time.
Click to expand...
Click to collapse
Whoever said it doesn't work is wrong. It works, but the one-click most people are using disables the button combo on all but early 1008 and older phones. There are flash packages which don't disable the buttons on any phones. If you must flash to stock (because you are selling or returning the phone or if some OTA update you want come out) just try to use the one with the fixed sbl.bin so you don't lose your button combos. If you just want to flash the latest perception or whatever then don't bother flashing to stock.
GGXtreme said:
If your phone is batch 1008 through 1010, Odin one-click will not work properly. Download Odin v1.7 and flash JH3 or later.
Click to expand...
Click to collapse
When did we get to v1.7? Haven't been paying attention in a while...
Sent from my SGH-I897 using XDA App
opcow said:
Whoever said it doesn't work is wrong. It works, but the one-click most people are using disables the button combo on all but early 1008 and older phones. There are flash packages which don't disable the buttons on any phones. If you must flash to stock (because you are selling or returning the phone or if some OTA update you want come out) just try to use the one with the fixed sbl.bin so you don't lose your button combos. If you just want to flash the latest perception or whatever then don't bother flashing to stock.
Click to expand...
Click to collapse
I'm pretty sure it just doesn't work...I tried to install JF6 with Odin 1.7 plus the 3 button fix and even that didn't work...I tried everything. The only ROM that took on my phone was JH3. Nothing else would work period...The jig was also necessary to get back into download mode...I almost got in with another ROM but eventually that also had a kernel panic as well. I probably should have posted a guide to what I did sooner but I didn't understand why my other 1010 phone didn't have this problem...now there is a guide already written to what I did...Although it is stated as using JH2 although I use JH3. I at least posted what I did on the 1-click forum in early december when I encountered this problem. I'm just glad the custom roms install ok over JH3 at least for now.
Mac11700 said:
Same here...I had a factory new 1009..and had no issues...However...I am wondering if many who are having this using 1008..1009...1010 builds up..are having their problem with factory refurbs..or new phones..? Is Samsung doing something to the refurbs that is causing this issue ?
Mac
Click to expand...
Click to collapse
When you say you can get to download mode no problem, you mean eclair right? Cause it works for everyone in Froyo.
I got 1008 no refurb and its broken in 2.1 without the swapped sbl.bin
Sent from my SGH-I897 using XDA App
opcow said:
Whoever said it doesn't work is wrong. It works, but the one-click most people are using disables the button combo on all but early 1008 and older phones. There are flash packages which don't disable the buttons on any phones. If you must flash to stock (because you are selling or returning the phone or if some OTA update you want come out) just try to use the one with the fixed sbl.bin so you don't lose your button combos. If you just want to flash the latest perception or whatever then don't bother flashing to stock.
Click to expand...
Click to collapse
Not true. About half of those who try it (including me) absolutely cannot flash anything pre-JH3 without using the special JH2 to JF7 method I linked. It seems odd, because I am on a brand new batch 1010 phone, and my friend who got his phone a bit before me (also batch 1010) has no problems plugging it into my computer and using Odin one-click. It has nothing to do with the button combo problem.
GGXtreme said:
Not true. About half of those who try it (including me) absolutely cannot flash anything pre-JH3 without using the special JH2 to JF7 method I linked. It seems odd, because I am on a brand new batch 1010 phone, and my friend who got his phone a bit before me (also batch 1010) has no problems plugging it into my computer and using Odin one-click. It has nothing to do with the button combo problem.
Click to expand...
Click to collapse
Interesting. I wonder if you have a checksumed boot loader.
fatttire said:
When you say you can get to download mode no problem, you mean eclair right? Cause it works for everyone in Froyo.
I got 1008 no refurb and its broken in 2.1 without the swapped sbl.bin
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
On my 1009 build..I had the 3 button on eclair..and on any rom I flashed..and I had used the JH6 odin to stock with out issue about 12 times..I tried it 1 time with my new 1012 build with out issue..but..I don't want to press my luck any further...I want to find out if doing this is even needed since I have my Nand of the original rooted stock JH7...
I see no need to even do a nand of the original rooted stock rom as what has been suggested just about everywhere as the first thing to be done on a new phone..if this won't allow me to return to stock in the first place..I mean what would be the point of just taking up space on your phone if it doesn't work ? If it doesn't work...then it shouldn't be recommended to do it...If it does work..then it really should be almost mandated as a precautionary DO THIS FIRST on every Rom on here for those who have the 1008 builds and up...shouldn't it ? If it does work...it sure will save folks a lot of grief and heads aches...and a lot of extra work...
Mac
Should i do the samsung upgrade though?
Mac11700 said:
Same here...I had a factory new 1009..and had no issues...However...I am wondering if many who are having this using 1008..1009...1010 builds up..are having their problem with factory refurbs..or new phones..? Is Samsung doing something to the refurbs that is causing this issue ?
Mac
Click to expand...
Click to collapse
I have a factory new 1009. I have used I897UCJF6-final-OCD-REV0 every time. No problem.

[Q] Why go back to stock 2.1 before each flash?

Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!
HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX
I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course
jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?
Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.
Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.
Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App
I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.
To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?
I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.
There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App
I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months
I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.
I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App

[Q] Hard Brick without a reason?

I think its a hard brick, absolutely nothing happens to my phone. No Power, no nothing. Basically, i flashed back to stock eclair, and everythign was running smoothly. I used titanium backup to delete all user apps, and then restore them (from my other backup). Then i got rom manager, installed CWM, and rebooted into it. I then installed the 3 button fix. Went back into eclair, and transferred the cm7 file into the internal sd. Then i rebooted again into recovery... But this time, i realized i had to go out, so i pressed reboot phone. And now nothing works at all.
Any ideas?
try to build jig first, or go to ebay, search for "micro usb jig" and buy one.
supaphreek said:
I think its a hard brick, absolutely nothing happens to my phone. No Power, no nothing. Basically, i flashed back to stock eclair, and everythign was running smoothly. I used titanium backup to delete all user apps, and then restore them (from my other backup). Then i got rom manager, installed CWM, and rebooted into it. I then installed the 3 button fix. Went back into eclair, and transferred the cm7 file into the internal sd. Then i rebooted again into recovery... But this time, i realized i had to go out, so i pressed reboot phone. And now nothing works at all.
Any ideas?
Click to expand...
Click to collapse
You tried button all the button combos and ADB? Also did you try plugging the phone in to give it a source of power? ... pull battery and try again.
Have you tried to hold volume down + power for DL mode?
How did you flash back to eclair and what from?
@Mengbo, my jig should be arriving in a few days. But i do have a bunch of resistors, il give that a shot.
@Coreym, Its been charging for hours (well im not sure, because it shows no signs) ADB doesnt work unless its connecting in debugging mode i believe, and the button combos dont work
@Studacris, its the method you told me because my phone is a 1012 build. http://forum.xda-developers.com/showthread.php?t=979133
Any other suggestions? :S
EDIT : Just tried it with a jig, nothing happened.
may need to be JTAG'd. Couple guys doing that. Connexion2005 is debricking captivates and could probably help you as a last resort.
Hmm this is weird ... You used the rogers stock rom package first only right? That doesn't have bootloaders, then you flashed the 3 button fix with three gb bootloaders which should've bricked you right there ... But here is the weird part unless I've misread the sequence of events, you were able to boot into the OS after that, then booted into stock 2e recovery rebooted and thats where are now?
Yep, exactly. Also, how does the 3 button combo have GB bootloaders? I used to flash it to stock eclair all the time...
Oh wait I thought I read that you came from gingerbread at first, when you flashed to stock the first time. What were rom were you on when you first started?
Yeah, when i flashed back to stock, i was on GR-12 which is GB.
But then i successfully went back to stock, and eclair booted up just fine. Its after doing the whole CWM thing (on eclair) that this brick happened.
Ok that's what I thought. That's why this series of events is really weird. The way you flashed back to stock didn't contain bootloaders, so you still had the gb ones which is fine to run on eclair, but the 3 button fix contains only a eclair/froyo secondary bootloader no primary at all so it didn't overwrite the gb one, so a mix of a gb primary and eclair secondary should have bricked you right there no question. I have no idea how it booted after you flashed the 3 button fix.
Well that sucks. Any ideas on how to fix it? Is the JTAG fix the only option?
For the hell of it I've only heard this working once with a bootloader mix up:
remove battery
replace battery
DON'T PRESS ANY BUTTONS
insert jig
Now hold the volume buttons.
if that gets you to download mode use odin one click right away to restore both stock bootloaders, when that causes a bootloop because of your phone not liking one click, use the stock package you used before. But you need to use one click IF you ever get it in download mode. IF being the operative word, don't get your hopes up with this one.
Probably won't work but if it does, WIN!
Get a warranty replacement
(hint) kies
Otherwise if you don't have a warranty because it's used or whatnot jtag is the only thing that can fix it at this point.
haha, il give that a shot then. However, i sent my phone in (saying kies was the problem) about 2 weeks ago. Should i do the same thing again? Or would they catch on?
LOOOOL!
That's a good question ... They can't prove it wasn't kies, and to out right refuse a customer his warranty based on just speculation does not make good business sense.
Haha! I guess that's true. So i guess now my dilemna is, should i send it to Samsung and wait 2 weeks, or should i send it to mobiletechvideos, pay 50 bucks and recieve it back faster.
Do you know if the jtag would void the warranty for sure? (in a way that they would know its been voided)
Not sure, but if you're worried about that use the warranty while you still can cause the clock is ticking on that time limit...
^^ he's not kidding. Warrenty for all of us is almost up :/
Sent from my SGH-I897 using XDA Premium App
That's funny, now I have a question: is the year warranty based on the initial release of the captivates so all of the warranties expire at the same time, is it based on build date of the phone, or is it based on original purchase date?
I'm guessing the first, which blows, but I'm not 100%

Categories

Resources