Database Develop

Bricked phone after updating to JH7 through Mini Kies

I recently found out I could update my captivate with Kies Mini. I updated and everything went smoothly. Kies told me update was successful and I unplugged my captivate. It was booting up fine until it reached the Galaxy S logo. It kept going through the logo animation for about 2 minutes before it shut off. I took the battery out and tried again. Same result. my soft buttons are lighted up. When I touch them It responds with a blink, but no haptic feedback. What is going on??How can I fix this? I tried using Odin to flash it back to stock but it won't recognize it. Mt phone was stock 2.1 with the Voodoo Lag Fix installed and everything ran fine and then after the JH7 update the phone messed up. I read that Launcher Pro causes problems with this update and you have to select the Touch Wiz UI when doing it which I forgot to do.
Please help, thank you.

Make sure your phone is powered down (remove then replace the battery if you have to), run odin, while holding both volume up and down buttons plug in the usb cable to enter download mode, flash with odin.

opcow said:
Make sure your phone is powered down (remove then replace the battery if you have to), run odin, while holding both volume up and down buttons plug in the usb cable to enter download mode, flash with odin.
Click to expand...
Click to collapse
Ya I did that. I get a failed message in red. I attached a picture showing what it shows me.

hve you tried the one click odin tht takes you all the wy back, or is that what you show in the screen shot? You may want to try a different computer or try a master clear.

j101399j said:
hve you tried the one click odin tht takes you all the wy back, or is that what you show in the screen shot? You may want to try a different computer or try a master clear.
Click to expand...
Click to collapse
I tried master clear, it says failed and then completed but it still won't boot up, the Galaxy S screen stays up while the S is flashing and then it goes black. If I press the power button the soft buttons light up but I can't see anything on the screen.

Hmm. And you are putting the phone in download mode (with the big yellow triangle and a shoveling bot pic) as opposed to recovery mode?

opcow said:
Hmm. And you are putting the phone in download mode (with the big yellow triangle and a shoveling bot pic) as opposed to recovery mode?
Click to expand...
Click to collapse
Yes, download mode with the android shoveling that rock stuff

Weird. The only suggestions I can think of then are, try running odin as admin, try using heimdall to flash.
Edit: if all that fails try a different computer and/or different USB cable.

opcow said:
Weird. The only suggestions I can think of then are, try running odin as admin, try using heimdall to flash.
Edit: if all that fails try a different computer and/or different USB cable.
Click to expand...
Click to collapse
I agree, I have bricked my phone and was able to come back with Odin. Even try downloading it again. Heck try flashing froyo odin one click as well

opcow said:
Weird. The only suggestions I can think of then are, try running odin as admin, try using heimdall to flash.
Edit: if all that fails try a different computer and/or different USB cable.
Click to expand...
Click to collapse
DUDE YOU FREAKING ROCK!!!! THANK YOU!!! (I ran as administrator and it worked this time)

Nice. Glad you got it working.

Word to the wise folks... disable any lagfixes before attempting to update. I had the same issue and had to Odin 1-Click to get it back to stock.

Bricked my phone while flashing from Phoenix to stock 2.3.3

Hi everyone! I have Captivate(1008 batch) with Phoenix Ultimate firmware. Today I tried to flash it with batch Gingerbread. Seems like my mistake was that I forgot to turn off lagfix. Odin halted. Now I'm getting "phone-!-PC" screen each time I connect phone to PC...
I can not get cappy into download mobe(tried all 3 ways)
Odin doesn't see phone...
Do I have any chaces to repair my phone or it's a brick? Is there a chance that jig will help?

There's a new thread in the dev section about a one click unbrick from that screen. I read that it's just downlad the software, plug in phone and click run.
AdamOutler made this -
http://forum.xda-developers.com/showthread.php?t=1153310

Ok, thanks I'll try that! BTW which fimware should I flash if my cappy is back to download mode? As I understand Phoenix formated my phone memory into ext4 filesystem. Is that possible to flash stock Gingerbread on ext4 filesystem?
UPD: Unfortunately software unbrick doesn't help I got "Phone is not connected" message. My PC doesn't see phone at all

The Jig should work, assuming you don't have mixed bootloaders. If you do have mixed bootloaders, JTAG service will be what you need.
If you do manage to get back to download mode, use the JF6 Odin 1-click.
You can get it here: http://forum.xda-developers.com/showthread.php?t=731989

Here's another suggestion that I did with a 1008 that I had a while back. open Odin 1 click to prepare for download mode. (make sure it's not one with the three button fix - if you one click from gingerbread to 3 button fix stock, it is a certain hard brick).
Remove battery, count to 10, replace battery.
hold the vol up and vol down buttons at the same time until you see the screen flash. It should flash every 5-7 seconds as long as you continiuosly hold the buttons.
When you see the screen flash, insert usb cord (with it already connected to computer).
This got me to download mode. It mat take a few tries. sometimes it's a challenge to get to DL mode from this screen. This procedure worked on my 1008. Hope it works.
A jig may work too, but it n ever worked for me on the 1008.

Thank you guys. Hope your suggestions will help!

With the phone and PC screen the Jig will work for sure try and make one or u can buy it.
You can also try this, Remove the battery open odin 1 cick and plug the cable to the usb port at the back of the PC and then the phone and now put the battery see if the odin lits up if yes you are done.

I solved the problem(even without jig). So writing my solution, hope this will help someone.
1) I went home to use another PC. Installed Samsung drivers there.
2) I tried different key combos. Vol Up + Vol Down didn't worked but Vol Down + USB entered Download mode.
3) One guy from russian android forum told me to try with Odin 1 click 2.1 stock firmware. Only this version of firmware connected to my soft bricked phone.
One more time thanks everyone for your replies

For future reference.
If your phone turns on (you can see anything on the screen), then you do not have a perminate brick, and a jig will work.
And your filesystem/lagfix does not matter with odin 1click. It resets everything to the way it came, nomater what you came from. (It even works on cm7 witch repartisioned it and used MTD).

I have the same problem as you. I can't get get the one-click unbrick to work (doesn't detect a device). I ordered a jig yesterday, hopefully it comes soon. I have a 1010 though, which I heard had more problems than others.

use a JIG
i made my custom JIG for 60 cents, save my Cappy after a failed cyanogen install.

Interesting Problem with Cappy

I've Had my cappy for something over a year and up until i finally got a working jig it was out of commision for about a month, Then all was saved with the jig and i reflashed stock and started from scratch trying new roms, Then, when trying to go from stock to apex using their own odin flashers, Then when it went back into recovery i hit reboot to begin using CWM. Then all of a sudden, The Gingerbread version of the softbrick screen comes up, Phone----!-----Computer. No worries i have my jig, then when i remove the battery, wait and put the jig back in . . . the phone just shows me a bricked screen again, with a jig i know worked. What have i done?

SnowBlind182 said:
I've Had my cappy for something over a year and up until i finally got a working jig it was out of commision for about a month, Then all was saved with the jig and i reflashed stock and started from scratch trying new roms, Then, when trying to go from stock to apex using their own odin flashers, Then when it went back into recovery i hit reboot to begin using CWM. Then all of a sudden, The Gingerbread version of the softbrick screen comes up, Phone----!-----Computer. No worries i have my jig, then when i remove the battery, wait and put the jig back in . . . the phone just shows me a bricked screen again, with a jig i know worked. What have i done?
Click to expand...
Click to collapse
If by "bricked screen" you mean the Phone--!--Computer screen, you should be able flash back from that screen. In theory, ODIN should recognize your phone at that screen in a manner similar to the way it recognizes it at the normal download mode screen.

As long as you see the computer/phone symbol you should be able to get it reflashed with the J6 Oneclick. If it never appears in ODIN try all of your USB ports. Odin only sees my phone on the two rear ports, go figure.
As far as getting the yellow download screen goes you might consider some other key combos before you declare it non-functioning. Did you flash it back to stock J6? If so, did the 3-button stop working? That may be your issue. Also, you may have put boot loaders on it from another device such as an I9000 and changed the key combo while flashing another ROM. Try battery pull/replace with vol up and USB, vol down and usb, both up/down with USB and see if any of those work.

[Q] Captivate and soft boot loops???

I rooted my cappy(cappy 1) and installed serendipity 6.4 on a clockwork kernel back in May for the first time based upon info I gathered here from all the experiences and advice. It went flawless. I odined back to stock and attempted to update the kernel to the one from the link on the serendipity 7 page and while it was doing the kernel flash it went into a boot loop that I apparently am not smart enough to recover from. Odin does see the phone for just a split second and starts but the phone restarts before it gets done. My wifes(cappy 2) came in the mail yesterday and she wanted freedom too so I rooted and tried to use a kernel I d/l from a site I recognized from everyones post and it said to use sgs kernel flash and I have had pretty much the same result in this phone too!! ??? whatsup?? I did it without fail the first time and now I am questioning myeslf. Neither will boot to recovery, neither will connect to pc via usb long enough to use odin. I am dumb about ADB. Clicked on the adb file and it flashes through really quick on my pc then closes. Tried to make the usb manual jumper with the resistors and I can't seem to have any luck with the technique. I ordered the jig for the usb connection for like 9.00 but I won't get it til next week. Any help would be appreciated...... I am at a total loss!!!

Are you using Odin from download mode? As long as you have a cappy with working button combos, start Odin (right click and run it as an administrator) without the phone plugged in. Pull the battery out, remove the SIM and external SD card if you have one, replace the battery and leave the phone off. With the phone off, hold both volume buttons and plug the usb cord in. The phone should turn itself on in download mode, at which point you can hit start in Odin.
If this is what you're already doing I'm not trying to talk down to you, I just couldn't tell from your post. If this is indeed what you are already doing, are you getting an error in Odin?

the three button was working on both before but now seems to no longer.... I can't for the life of me get to recovery or download mode.... I think I could revive both if I could just get that far. and had a good kernel file which I obviously am not getting or I am doing somthing way wrong. Neither are totally bricked... the try to come on but keep restarting themselves. BTW thanks for the help and I don't feel talked down to at all.... felling pretty silly/crappy about my abilities right now. Thought I had the whole root/kernel/rom thing figured out til now.....

as far as odin errors. my first phone would hook to odin and then lose the connection because the phone turned itself off. the second one will not eastablish a connection at all.... does that make sense??

I would shoot for download mode at this point. When you tried the resistors to build your own jig, was the phone off when you were trying to get it to work?
1whttcdreamer said:
as far as odin errors. my first phone would hook to odin and then lose the connection because the phone turned itself off. the second one will not eastablish a connection at all.... does that make sense??
Click to expand...
Click to collapse
If you're in download mode, your phone shouldn't turn itself off. What odin package are you using?

yes, phone was off and I had 4 resistors with a total value of just between 300K and 301K. I was in my opinion unsuccessful in touching the two pins correctly without the resistors touching. I may try to disect a usb cord tonight and solder my resistors to the black and green wires(think thats correct) and see if I have any better luck. To impatient to await the jig for 5 or so days. But at least i'll have it for later use. Then I guess go back stock and start over. but I gotta get D/L mode to work first. I think odin was version 3.1.7 I'm at work and don't recall exactly. I know I D/L'ed a odin console and a set of files to put in particular places as to direct odin what to use. It came as a complete D/L. I also have tried the one click odin files before(this is what I used the first time back in may) any and all help is greatly appreciated.

1whttcdreamer said:
yes, phone was off and I had 4 resistors with a total value of just between 300K and 301K. I was in my opinion unsuccessful in touching the two pins correctly without the resistors touching. I may try to disect a usb cord tonight and solder my resistors to the black and green wires(think thats correct) and see if I have any better luck. To impatient to await the jig for 5 or so days. But at least i'll have it for later use. Then I guess go back stock and start over. but I gotta get D/L mode to work first. I think odin was version 3.1.7 I'm at work and don't recall exactly. I know I D/L'ed a odin console and a set of files to put in particular places as to direct odin what to use. It came as a complete D/L. I also have tried the one click odin files before(this is what I used the first time back in may) any and all help is greatly appreciated.
Click to expand...
Click to collapse
I have never been successful in touching the pins without cutting apart a USB cord. With the cord, though, it's a piece of cake. You don't even have to solder them, just stick the plug in there and you can hold the resistors (as long as they're covered with something) to touch the right pins. I don't know that the color coding is consistent, but you can figure it out either with a multimeter or trial and error. I also think it's 3 resistors not 4, but your values are correct so that's probably what you were doing.
Once you get into DL mode, you have a couple of options:
1. Try Serendipity 7 again. I've done several installs from their instructions and they work perfectly, but there are a lot of steps and you need to be careful to hit them all in order (I've definitely ended up in your situation before because I thought I remembered what needed to do but missed something).
2. Flash a one click. You can find them all here:
http://forum.xda-developers.com/showthread.php?t=1300843
If you were going to go this route, what I would do is flash the one-click for KF1. This will give you Samsung gingerbread bootloaders which are both compatible with everything and will give you your button combos back for download and recovery modes. Once you flash this, you should only use bootloader-free packages and you will always have your button combos with no risk of a hard brick.
Once you have KF1, you can root it from here:
http://forum.xda-developers.com/showthread.php?t=1127249
then get CWM recovery, skip to step 13 in the S7 download instructions, and flash it in recovery.
Good luck!

Thanks Ever So Much!!
:cool Well long story short my jig worked. You were right, it was very easy to make. Soldered resistors to pins so now I have a working jig. My original phone is so totally fixed. Running rooted 2.3.3 Serendipity 7 with CWM. Thank you very much for the confidence building and advice on where to start and finish.

[Q] Phone Exclamation Point Computer

Got stuck here working with a friend's captivate. We were in the process of cobbling together a jig when we notices that Odin seemed to recognize the phone whenever it was at the P!C screen.
The jig wasn't working out (resistors were 5% weaker than nominal), so we just gave Odin the go ahead at the P!C screen. To our surprise, a progress bar popped up on the phone and Odin successfully flashed the stock kernel back on.
So my question is, is the P!C screen just another face for download mode? Do you really need to jig from P!C to DL mode, or are you already there?

Not 100% of the time, but most of the time yes.

studacris said:
Not 100% of the time, but most of the time yes.
Click to expand...
Click to collapse
Cool, that makes life easier. When it isn't, does Odin not pick it up? Or does it show but fail to flash? Just trying to get an idea of how these things act when they're pseudo-bricked. I'm coming from Droid X land where 2nd-init and SBF solve everything.

Odin will only find the phone if it can get into download mode. (Usually vol up + vol down > plug in cable)

Not true, Odin shows a com port when booted into Android and in recovery. But will only succeed if download mode protocol is initiated on the phone.

studacris said:
Not true, Odin shows a com port when booted into Android and in recovery. But will only succeed if download mode protocol is initiated on the phone.
Click to expand...
Click to collapse
And to further add clarity, it's only the phone-!-computer screen that says "Hardware Upgrade Failure" (or something like that) that doubles as download mode. Coincidentally, that is only found in Gingerbread bootloaders. Happy Flashing

"Firmware upgrade failed" and even that's not completely true...if the flash you're attempting fails before the image for download mode is rewritten, then when download mode is initiated there is nothing to call on but that "flash failed screen" regardless of bootloaders.
That happened to me on my sisters captivate once...with eclair boots.

studacris said:
"Firmware upgrade failed" and even that's not completely true...if the flash you're attempting fails before the image for download mode is rewritten, then when download mode is initiated there is nothing to call on but that "flash failed screen" regardless of bootloaders.
That happened to me on my sisters captivate once...with eclair boots.
Click to expand...
Click to collapse
Weird. So, that would explain our situation. The flash failed while it was trying to negotiate the connection with the phone (or something worded like that, one of the first steps). So this jig is for real huh... Nothing like that in DROIDX land. Now that we've got it built right (no multimeter at the time, 301.6k ohms now) can we test it without altering anything? In other words, if we initiate download mode with the jig does any other kind of hard reset happen? NAND wipe or something like that? Or can we jig in to download mode to test the jig, then battery pull and reboot normally? (without plugging it in to a computer obviously - just a dry run)

Yeah, forcing dl mode shouldn't hurt anything. How do you think they test the ones that they make?

And you don't even need to yank the battery..just hold all 3 buttons and it'll reboot, if you hold them slightly too long it'll boot into recovery, but you can reboot it from there no big deal

Nice, thanks for the tip. I'll test it out tomorrow and see if my handiwork paid off. These unlocked bootloaders are fun! I do love my droid x but maybe the Verizon Galaxy S (fascinate?) would have been a good pick too.
Tangent: my friend is now up and running with the Corn KK4 7.06 under the stock ROM, got his root back. Next step, rom land.

ive Odined from the Exclamation point screen a couple of times
phone still running amazing

jayRokk said:
ive Odined from the Exclamation point screen a couple of times
phone still running amazing
Click to expand...
Click to collapse
Me too!
I'm glad to hear you got your phone back up and running. This phone is pretty hard to kill for good, and with the unbrickable mod its impossible!
Sent from my SGH-I897 using xda premium