Database Info

So now I have a hard bricked cap..

The captivate cannot boot at all when pressing the power key, actually all three keys seems unresponsive. I can only use a Jig to get in into download mode, but it freezes using OdinV3 one click.. It freezes at dbdata.rfs or factoryfs.rfs.. If I waited long enough, it will show a green screen or sometime a yellowish orange screen..
So is my cap hard bricked then...?
I used the same computer/setting/cable to odin other devices and every time works..

Try installing the samsung driver, then restart your computer.
Now, go to development, find the odin thread by designgears, download those drivers. Install drivers. Restart computer. Start odin. Plug usb into port on backof computer. Put phone in dl mode. By now you should be ready to hit start. I would post a link for you, but it's hard to do from my phone.

I used that method for a numbers of cap and worked every time but not for this one. Think it is hardware malfunctioned..

sometimes the phone is actually on when the screen is black. see if you can see the phone in odin without being in download mode. if you can run master clear in odin one click. then try download again. try different firmware versions too. odin one click would fail to flash my phone untill after i flashed the jh2 leak with full odin. i dont know why but now both odins work. you can try to flash rogers stock 2.2 firmware. it wont hurt anything.

Keep trying, third has happened to me before. Eventually it went through. Also its possible different pc, or cable
Sent from my SGH-I897 using XDA Premium App

A good rule of thumb for checking if you have a hard brick is "Did something show up on the screen at any point?" If so, you aren't hard bricked. A hard bricked phone will be completely unresponsive to anything, including a jig.
I'd say keep trying. Odin is pretty buggy and sometimes refuses to work. You might also want to try a different usb cable, and a different usb port on your computer. It may be simply that you have a faulty cable or port, and it's losing connection to your phone in the middle of your flash.
Also, have you tried using Odin with repartition checked?

I used other ports and cables, but now it won't even boot into d/l mode with a jig.. just get warm at the back between the camera and TF slot.. think its really hard bricked now..

modest_mandroid said:
A good rule of thumb for checking if you have a hard brick is "Did something show up on the screen at any point?" If so, you aren't hard bricked. A hard bricked phone will be completely unresponsive to anything, including a jig.
I'd say keep trying. Odin is pretty buggy and sometimes refuses to work. You might also want to try a different usb cable, and a different usb port on your computer. It may be simply that you have a faulty cable or port, and it's losing connection to your phone in the middle of your flash.
Also, have you tried using Odin with repartition checked?
Click to expand...
Click to collapse
The Odin one click has no repartition option. When I tried to use Odin3 V1.7, the jig failed to take the phone into d/l mode and the phone got warm. btw, the jig is working.

Do you by chance have kies running. I once thought I had it off... But it was just minimized and it stopped odin from working.
Just a shot in the dark.
sent using a phone.

I had never installed Kies.. I actually odin another cappy right before this one, and that one works.. Think there is no hope and have to sell it for for parts then .

unrecoverable soft brick even with USB JIG

so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.

muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?

Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG

donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.

Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps

muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.

Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App

will do thanks guys, ill try it tonight and let ya know how it goes for me.

i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now

krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much

muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.

I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??

amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...

Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.

That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.

That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!

Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App

Woops ahahahha. Was talkin to my friend. SOrry!

fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/

*Help* Captivate won't boot.

Ok, so I was on CM7 and decided I wanted to go back to stock, so I used Odin 1 click to go back to 2.1 but in the middle of flashing it said "fail". After that, I unplugged the phone and nothing would work, not the power button and none of the combos to get it into download mode or recovery, the screen was completely dark.
After searching, I tried taking out the battery, pushing the - volume, connecting the usb, and then putting the battery back in. That worked and I was able to go into download mode only, but odin 1 click still fails. I then tried this method: http://forum.xda-developers.com/showthread.php?t=995143 with odin 1.3 but it still fails. I'm able to go into CWM3 recovery but it says the sd card is not mounted, so I can't flash a rom from there or do anything. I'm thinking maybe flashing 2.1 bootloaders, a 2.1 kernel and then ODIN 1 click might fix this. Can I be right?

What you want to do is get your phone/pc connection better do odin doesn't hang while flashing.
Make sure the cable is good.
Swap usb ports, madge sure it's in the back connected to a port on the motherboard not a front port, reboot the computer and try the package you linked cause if that fails it does not have bootloaders so there is very very little risk of bricking, whereas if odin one click hangs on boot.bin or sbl.bin you would brick.

studacris said:
What you want to do is get your phone/pc connection better do odin doesn't hang while flashing.
Make sure the cable is good.
Swap usb ports, madge sure it's in the back connected to a port on the motherboard not a front port, reboot the computer and try the package you linked cause if that fails it does not have bootloaders so there is very very little risk of bricking, whereas if odin one click hangs on boot.bin or sbl.bin you would brick.
Click to expand...
Click to collapse
Wow, I would've never guessed to use the rear usb ports. I plugged it into the back and it worked! I am now on 2.1. It's weird, I've done it many times with the front usb ports and never had a problem, I don't know what might have caused this.

Odin is touchy having the least amount if connections is the best, a port on the motherboard. Sometimes even one of those will decide to give you the finger for no reason. I'm pretty sure that happens to all of us at least once.

Did I completely mess up my Captivate?

So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.

I pull out my battery and let it discharge for about 15 secs and hold volume buttons then connect USB cable and finally insert battery while still holding volume buttons of course, it'll get you into download mode. Never failed me. I've had my phone not even turn on the screen, it stays dark during a screwed up flash with odin. I then flash UCKI2 with bootloaders and then flash to gingerbread ROM I like. If you plan on installing custom ROMs your phone will semi-brick numerous times. If its showing a phone, exclamation mark and computer with a message saying firmware flashing failed. That is perfect! Just make sure you have Samsung USB drivers and simply flash using odin, it'll show COM and a number like 5 (COM5) then just flash. I'd advise you to remove any external SD card and restart before using odin it acts up. Hope this helps

hupo224 said:
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
Click to expand...
Click to collapse
The "Phone - ! - PC" will be your download mode screen. Just download from there.

However, if a flash goes foul somehow, you may be left with the infamous "phone--/!\--PC" screen.
If you see this, don't panic. Although it's not technically the download mode screen, many users (including myself) have been able to successfully flash from that screen. Give it a try.
Click to expand...
Click to collapse
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.

asasione said:
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
Click to expand...
Click to collapse
100% - I had similar experience with my first flash but after a few goes at it and 3 or 4 "soft-bricks" all has been great!

Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..

It seems I got it in download mode this morning with the jig. Just trying to get my damn pc to read it. Sometimes the right drivers work sometimes they don't. ugh

Connection issue in my sig

Any chance you have another pc to try it with? Or possibly another cable?

Going to try one click on ubuntu...

Ive had issues in the past before with certain USB ports on my PC not reading the phone.
Try plunging in your phone to a different USB port and it can make a world of difference with the driver issue (even if you have to plug it in the back of your PC).

try one click unbrick in the android development page

hupo224 said:
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
Click to expand...
Click to collapse
Are you running x64? If so are you running the 64 bit drivers?

I also had the same issue a couple of times, which is technically called a "soft brick" . You could resolve this issue using ODIN flasher and reverting back to stock. Now coming to USB problem in windows, this is a known issue with windows (especially Vista and Win7) and samsung!! The remedy which I found is as follows :-
1.Disconnect the phone from USB
2.Remove samsung USB driver software from your windows PC.
3.Reboot and then navigate to C:\Program Files\ (assuming that C:\ is your windows OS partition)
Delete "samsung" folder.
4.Download latest samsung USB Drivers for captivate and install.
5.Reboot the phone.
6.Open ODIN and connect your Phone to PC.
It should detect the COM Port by now. Try this and get back
"Thanks" , If I helped U

[Q] Stuck in a soft boot (2nd time) trying Adb to get past the recovery file issue

I've spent weeks surfing the forums trying to get past the common recovery file rename and replacement with a system manager that is in super user mode etc. I don't know if it's the particular version of the recovery file that I've replaced being bad, but the first time I was soft bricked I was able to physically reset with a guitar wire in that whole ( was weird cuz it seemed like the button wasn't going to work cuz after minutes of turning the phone on and off it just randomly worked) Let me explain better because after chosing a different recovery file it soft bricked again however the reset isnt working. Ok so if I have USB cable in it brings up charging battery logo (showing the battery as dead which isnt true because the time it did reset... when it worked, the icon illuminated green suddenly. If the USB isnt connected upon turn on the samsung comes on indefinitely (forever)... tried with sim in & out etc. If I reset into download mode it just says downloading (let it go for three hours before stopping it once). Ive installed odin and tried to fix it that way... I made a Jig with 3X100k resistors and 1 1ohm 1watt ..( attempting to get the 301k resistance between the 4th and 5th pin in the micro usb connection... Didn't work ( used a voltmeter to test the jig but I didn't know what the reading should be but I saw a difference ( thougt the 1 watt addition was messing it up so I omitted that resistor. Still didnt work.... guess I could splurge and buy a jig online as a back up if I cant beat it differently. Lastly and more promising was downloading ADB and getting it running correctly... at first because of the inability to adjust bugging or not the device wasnt recognized... miraculously I left it alone andcame back and tried it... device is recognized... tried to adb pull recovery.orig file to C: to rename and push back but I didn't see it on the PC to rename after Adb says the pull file command was done. Thanks for your patience with all this info on first message. Im new to this. Im sad that I have to get into this just to take control bake but there is a user and or group that is runing in my background and changing my permissions and running so many processes its like slow motion. doing this so I can run the roms to control my traffic and get some Ram back... I wish I could just ask him to please stop. Thank you for any help.

If I reset into download mode it just says downloading (let it go for three hours before stopping it once)
Click to expand...
Click to collapse
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.

Odin
ApexPredatorBoids said:
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.
Click to expand...
Click to collapse
Odin wasn't recognizing the device before at all, but since I set up ADB and ran the adb sync comand, now when I run Odin it recognizes the device as com5 not com++ (not sure if that matters). I'll try and start a pit and see what happens.
If I went back to stock what kernel do you recomend I flash and do you know a good recovery file to replace the original one to get past the signature verification when reinstalling packets.

Flash entropy's dd kernel. There is no need to replace any recovery file in GB (that's only on froyo).
Sent from my sweet & buttery Infuse