Database Info

Odin doenst recognize, can i pull batt?

....on the way of a reflash, i want to go back to stock. cap is in download mode but odin doesnt recognize it.
how can i do it again ? yellow man says do not pull batt

Never a good idea to interrupt odin but if it is stalled and taking more then 5 minutes there is nothing you can do but pull battery and try again
Sent from my SGH-I897 using XDA App

If it did not start flash go ahead

I have to do this like 4 or 5 times every time I use Odin. It rarely works right the first time.

Many times, all that is needed is to pull the usb out and reconnect (pre-flash). Then it recognizes the port.

Open ODIN first...then get into download mode: (up/down volume + power), and then plug it in. ODIN should recognize it right away after that...works for me 100% of the time.

Gr8Danes said:
Many times, all that is needed is to pull the usb out and reconnect (pre-flash). Then it recognizes the port.
Click to expand...
Click to collapse
meyesme said:
Open ODIN first...then get into download mode: (up/down volume + power), and then plug it in. ODIN should recognize it right away after that...works for me 100% of the time.
Click to expand...
Click to collapse
I start Odin, put the phone in DL mode, and then plug it in. Odin always recognizes it. The problem is that when I click the button to flash, it starts and before any progress bars come up, it freezes at one spot indefinitely. It then requires a battery pull and restarting the whole process. Usually I get the exclamation mark error and have to do the vol+USB trick to get it in DL mode. It's so temperamental for me. Glad you guys have better luck.

fatbas202 said:
I start Odin, put the phone in DL mode, and then plug it in. Odin always recognizes it. The problem is that when I click the button to flash, it starts and before any progress bars come up, it freezes at one spot indefinitely. It then requires a battery pull and restarting the whole process. Usually I get the exclamation mark error and have to do the vol+USB trick to get it in DL mode. It's so temperamental for me. Glad you guys have better luck.
Click to expand...
Click to collapse
Do you suppose it is a driver problem? Try uninstalling and reinstalling the drivers on your computer? Just a thought.

I'm on a 1007 and don't appear to have access to 3-button download mode. I think volume + usb works, and I'm pretty sure adb reboot download works as well, but worried that if I get into a soft-bricked state I won't have access to adb.

Hey everyone,
This is as far as I cxan get. I am now stuck in download mode and ODIN3 won't do anything. Is there anyway to get the phone to reboot, I am sure it has not even tried to flash yet.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
Been waiting over 30 minutes, and no activity yet. Have a 2.1 Captivate, stock.
Thanks,
DC Miller

dcmille290 said:
Hey everyone,
This is as far as I cxan get. I am now stuck in download mode and ODIN3 won't do anything. Is there anyway to get the phone to reboot, I am sure it has not even tried to flash yet.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
Been waiting over 30 minutes, and no activity yet. Have a 2.1 Captivate, stock.
Thanks,
DC Miller
Click to expand...
Click to collapse
You are going to need to pull battery. what is the build number of your phone? Located under battery, mine is 1008

Build number is 1007. I just really need to know how can I get the phone out of download mode? I tried removing the battery and I got the icons showing a little phone, Exlation in Yellow and a little PC. I can get into download again using the volume buttons, and ODIN sees the phone, just stops after a few lines and does nothing more.
Thanks for any advice you may have,
DC Miller

Your build is fine, I am going to list the order I use with odin to make sure you are following.
First take your battery our of your phone snag leave it out for a couple minutes.
Open odin
Put battery back in
Enter dl mode
Run odin
I have had odin stall in me before. A couple tries pushed it through

I'll give it a shot and see what happens.
Thanks for your help,
DC Miller

Well after 6 times of trying to get past the fifth line in ODIN, it went past it!! It installed 2.2!!! FROYO is verified.
Thanks so much for helping me to stay with it.
DC Miller

i hope you backed up your nv_data.bin before you froyo'ed. good luck and enjoy!

Everything is good. Saved all I needed, I could not be happier.
Thanks everyone,
DC Miller

Good to hear

[Q] Unable to boot, not in debug mode

I'm running rooted JH7 with Voodoo lagfix. I was playing around with the plumBob GPS fix and flashed 0.93 through CWM. When I rebooted, I got stuck on the AT&T screen. After pulling the battery and trying a few more times, I decided to restore from a nandroid that I did a few weeks ago. While the phone booted after restoring, I was constantly getting FCs, making the phone entirely unusable.
At this point, I decided to flash back to stock using the AIO Toolbox 3.0. I used the download mode jig to get into DL mode, plugged the phone into my computer, and told it to flash to stock. At this point, I was told that the phone needed to be in USB debugging mode. How am I supposed to accomplish this when the phone is non-bootable? Am I screwed?

Try using this to get back to stock http://forum.xda-developers.com/showthread.php?t=731989
Never used aio toolbox but i never heard download mode needing usb debugging mode enabled to flash.

peachpuff said:
Try using this to get back to stock http://forum.xda-developers.com/showthread.php?t=731989
Never used aio toolbox but i never heard download mode needing usb debugging mode enabled to flash.
Click to expand...
Click to collapse
How long is the file analysis step supposed to take? I've been stuck at it for 10-15 minutes.

frohman said:
How long is the file analysis step supposed to take? I've been stuck at it for 10-15 minutes.
Click to expand...
Click to collapse
It's not working then. I don't remember off hand, but I think less than 10 seconds.

Should I try a master clear first?

I've been sitting on Master Clear starting for 5 minutes. Is this supposed to take so long?

Odin One-Click for JH6 not working
I was having issues getting Odin One-Click to work after flashing a GPS fix that wasn't compatible with my kernel that left me with a non-booting phone. Odin was hanging at Analyzing Files and not going any farther. I eventually got my phone to boot by doing a nandroid restore and wiping data, but wanted to go back to stock to make sure that nothing was still messed up.
Unfortunately, now I'm stuck at DO NOT TURN OFF TARGET. I've been here for over 20 minutes. I already got impatient and killed the process once, leaving me with the dreaded phone+!+computer. Watching the MobileTechVideos vid on using Odin One-Click makes this look like it should happen quickly, but that isn't happening in my case. Any ideas?

Ok, I'm an idiot. Ends up you need your SIM card in the phone for ODIN to work. Back to stock now and very relieved. My phone works again!

i'm actually having a similar problem to frohman. odin shows this:
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> Set PIT file..
<ID:0/014> DO NOT TURN OFF TARGET!!
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> Sbl.bin
and gets no further. i tried it with and without sim with no changes. any idears?

Searched/Bibled/Need help w/brick please

I updated to Whitehawkx's Valhalla, and flashed successfully, although when booting I would get a fuzzy/snowy screen.
After reasearching, I found that I needed the GB bootloaders. So, I went to the Bible post, found the "updated bootloader" GB ROM, and attempted to flash it via odin.
Here's where I think I went wrong. I put the phone in download mode. In Odin, which I've used extensively in the past, I checked the "Phone Bootloader Update" checkbox, then attempted to load the PIT, Phone, and CSC files from that GB ROM linked in the Bible post.
It hung.. I let it sit for well over an hour, and it was just stuck on zImage, in the "Message" area of Odin, where it shows progress.
I unplugged the usb, replugged, tried again.. same thing.
I rebooted phone, and it no longer goes into bootmode. I get an active screen, that displays a small handset icon connected to a PC icon, with an orange warning triangle between..
Again, cannot get into download mode, even with every method posted. It always just displays this same graphic.
Since the display is functioning, I assume it is not hard bricked.. but hoping for something to help!
Thanks mucho in advance. I have many hours into trying to recover, before coming to the community with tail between legs.

hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
I wonder if you might need a jig to be able to get it into DL mode again? There is a post about that somewhere, but I can't seem to find it at the moment.

mike-y said:
hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
Click to expand...
Click to collapse
Yeah, as I mentioned, that's where I think I went awry as well. Figured that since I was primarily wanting to replace the bootloader, I should check it. Probably my big downfall though.

Odin should still be able to pick up your phone with that screen. It might take a bunch of tries as well as switching between 1.7 and 1.85. Just keep trying. Flash kg4 then Honks kernel. Should give you cwm access then reflash valhalla

You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App

CozzaFrenzyy said:
You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.

Bimboy said:
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.
Click to expand...
Click to collapse
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App

farwek said:
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Excellent help, that allowed me to get the phone connected. Appreciate it.
However, I can get Odin to see the device, but do nothing with it. I've tried flashing the KG4 as recommended, then I tried a few others, including going back to KC1.
I can never get past "Setup Connection" in the log, which looks like this:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> pda.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
So, I'm connecting, starting the process, getting MD5 validation, and then not connecting. So, I think I am VERY close, but I can't get past this.
Greatly appreciate more thoughts, even if it's unrecoverable. You guys have got me this far, and I appreciate it.

I had this happen the other day and had to go back to KC1 "fix", found here.
That link 3/4 of the way down on the first post will give you like 3 or 4 files to put in odin. Before you try it restart your comp and phone. Good luck!

Hey golmar.... ... Did you use your own bible thread to find that link?

FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
List of dangerous ODIN stuffs.
1. Repartion with wrong pit(wrong means never able to boot again even with bootloader fix)
2. Check "bootloader update"
3. "EFS clear"
4. Put a file with bootloaders in the "bootloader" section. You have to put it in PDA.
5. flash wrong bootloaders. ( you can unbrick using a few methods)
6. flash the wrong rom.

airfluip1 said:
FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
Click to expand...
Click to collapse
Yes, I knew it, as soon as I did it, as I stated.
I got it to start to flash, and then hang.. for hours. I saw probably 5mm of a progress bar on the phone. From there, I can now go into download mode via battery pull/usb/volumes/battery insert. However, I can never get past "Setup Connection.." in ODIN.
Luckily, I have had a work holiday to day to "labor" over this less-then-optimal situation. Still nada though. I continue to get messed up drivers, and when I get the correct ones loaded, I only get to "Setup Connection..." on the ODIN flash.
Over the years, I've gotten into many "close to paperweight" situations, when cooking early WM ROMs. I've never been this deep in time to recover.. without results.

You must use heimdall to insure optimum results, also there is a different driver. Just follow my post on heimdall. It is in the development section. Also, I would suggest using version 1.1.1 instead of 1.3.x or whatever. It should be on the heimdall site. Just google it. All the archived versions are still there. 1.1.1 is easier, as it has a more easy to use GUI for some people and you don't need to use a pit file. Primary boot loader is boot.bin and secondary boot loader is sbl.bin. Make sure you have C++ 2010 redistributables on your computer and navigate to the "drivers" section in the folder you download. Open zadig, and then go to options and list all devices, you should then see Samsung composite USB or something like that, click install driver, when it is done, just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.

Thanks airfluip1! I'll give it a shot tonight. I already had tried Heindall, from you post, so I have it all downloaded already (1.1.1), along w/C++.

airfluip1 said:
... just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.
Click to expand...
Click to collapse
Well, with Heimdall, I get consistent, replicatable failures. I can flash the primary bootloader, but it always fails at 20% on the secondary bootloader (even tried the "backup secondary bootloader" flash with the same result:
Code:
c:\heimdall>heimdall flash --primary-boot boot.bin --secondary-boot-backup sbl.b
in
Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading backup secondary bootloader
20%
Failed to send file part packet!
Backup secondary bootloader upload failed!
For some reason, it will not let me flash it.. So close, I can taste it. FWIW, MD5 checks fine on the SBL file. Also, I started with the heimdall_frontend, but prefer the feedback the commandline offers.

Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App

Light-라이트 said:
Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thanks! That was something I tried immediately. I may be looking at something I need a jig for. I wonder if partitioning got hosed, and it is not allowing me to write to disk, where it thinks it should be. Also, not sure if it is worth my time, compared to buying the next latest and greatest. Kind of a good news/bad news scenario.

Just wanted to thank everyone for this thread... I ran into the same problem as the OP did when I tried flashing Valhalla.... Somehow I manged to completely overlook the giant red bold message about needing the GB bootloader. So, I got the boot loop and the fuzzy screen mentioned, but what I did was go into download mode and Odin flashed Krylon's stock+root per this extremely detailed tutorial.
Tomorrow I'll probably entertain flashing up to GB, but for now I'm just glad not to be bricked....

Try this DL mode method
Get the KG4 leak and load it into Odin.
Leave everything as-is (including re-partition).
Pull the battery from your phone.
Plug the phone into the PC.
Hold Vol+Up and VOL+Down while connecting the battery.
Once Odin picks your phone up, hit start.
You *really* shouldn't have any problems at that point. I've encountered the exact same issue, and entering DL mode using this method worked for me.
Once your phone is up and going on KG4, use Odin again to flash Valhalla, and you're good to go
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4

Thank you! This thread saved my bacon. I had the snow after a failed Heimdall. Odin 1.7 and a different USB port enabled me to get back.

[Q] Odin Stuck

Hey guys.
Earlier today, my phone ran out of batteries and shut down. When I rebooted it, everything was in stock settings of Octane 2.X. I have no idea why that happened, since I've rebooted the phone plenty of times before.
Since that problem didn't seem to have a solution, I decided to Odin and flash Octane 3.0 instead. The first time I used Odin, everything was fine. I Odin'd to KC1, just to remove any gremlins. Next, I tried to Odin to KI3. However, that was stuck.
In the end, nothing moved for several minutes, so I unplugged it and reboot my computer. My phone was still able to enter into download mode. I've also tried different USB ports. All have the same outcome.
Now, Odin recognizes my phone, but I can't get pass: <ID:0/013> Get PIT for mapping..
I've attached a picture of what's happening below.
I've searched for the solution to this problem, but the only solutions I've really found were about letting the phone rest for a while. Of course, I let it rest, but the same thing keeps happening.
Please help.
EDIT: Now it seems like I can't get pass <ID:0/009> Initialzation..

bkoon1218 said:
Hey guys.
Earlier today, my phone ran out of batteries and shut down. When I rebooted it, everything was in stock settings of Octane 2.X. I have no idea why that happened, since I've rebooted the phone plenty of times before.
Since that problem didn't seem to have a solution, I decided to Odin and flash Octane 3.0 instead. The first time I used Odin, everything was fine. I Odin'd to KC1, just to remove any gremlins. Next, I tried to Odin to KI3. However, that was stuck.
In the end, nothing moved for several minutes, so I unplugged it and reboot my computer. My phone was still able to enter into download mode. I've also tried different USB ports. All have the same outcome.
Now, Odin recognizes my phone, but I can't get pass: <ID:0/013> Get PIT for mapping..
I've attached a picture of what's happening below.
I've searched for the solution to this problem, but the only solutions I've really found were about letting the phone rest for a while. Of course, I let it rest, but the same thing keeps happening.
Please help.
EDIT: Now it seems like I can't get pass <ID:0/009> Initialzation..
Click to expand...
Click to collapse
Weird. I've had mine stuck at the PIT file before but rebooting my PC and the phone seemed to fix it. Does the phone boot up to an OS at all? Maybe get it into recovery, factory data reset, then try again?

Thanks for the response stephen_w.
I can't get into recovery, only download mode. I managed to get it to work again after reinstalling drivers and rebooting my computer.
However, I think Odin needs to be run with nothing in the background or something. After I Odin'd KC1 successfully, I tried to Odin KI3 (which progressed till factory). My girlfriend IM'd me and it suddenly stopped.
I'm gonna try redoing it all over again and seeing how that works. FML!

bkoon1218 said:
Thanks for the response stephen_w.
I can't get into recovery, only download mode. I managed to get it to work again after reinstalling drivers and rebooting my computer.
However, I think Odin needs to be run with nothing in the background or something. After I Odin'd KC1 successfully, I tried to Odin KI3 (which progressed till factory). My girlfriend IM'd me and it suddenly stopped.
I'm gonna try redoing it all over again and seeing how that works. FML!
Click to expand...
Click to collapse
Weird man. Have you tried the factory reset after KC1? I hate using that factory reset crutch but it's helped me plenty of times. Then again, maybe I just keep effing up my phone LOL

Seems like the solution was just to change computers. Weird how my sister's laptop used to be unable to use Odin, but now it can. Now I really wonder wtf happened to my computer. I used to be able to do everything on it.

bkoon1218 said:
Seems like the solution was just to change computers. Weird how my sister's laptop used to be unable to use Odin, but now it can. Now I really wonder wtf happened to my computer. I used to be able to do everything on it.
Click to expand...
Click to collapse
Definitely odd but I'm glad you got it going. Maybe the drivers got hosed? It's really hard to say I guess. If you get bored & get really curious about it, uninstall Kies Mini if you have it installed, uninstall the drivers, then go into the device manager and make sure there's nothing Samsung USB related or "gadget serial" left over. Then maybe reinstall Kies Mini and install the drivers from there.

I have bricked my phone :(

Hi everyone. I've been reading these forums for quite some time and I have been flashing some of the custom roms that the developers have made (I think they're all awesome). I thought that I was confident enough with flashing to give the CM7 rom a try. I followed FBis directions (not the one click but the slighter harder version) and upon flashing using heimdall I had an error saying that the PIT was flashed but the Kernel wasn't (unfortunately I was too stupid to write down the exact error).
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue but another problem exists, my computer (win 7) upon plugging in the phone only sees it as a unknown device. I tried changing the driver manually to Samsung USB composite but it gives an error saying device is not working properly. Is there anything I can do to fix this brick? I just can't get my computer to recognize that my phone is connected so it's not possible to heimdall since it also thinks no device is connected.
Any help is greatly appreciated it. I have searched the forums for a similar situation but I think mine is unique so I made a new post, I know people don't like to repeat what is widely available.

Whenever i had that happen trying to install cm7 i just used the 1 click gremlin remover and it flashed back to stock for me.
http://forum.xda-developers.com/showthread.php?t=1500427
Sent from my SGH-T959V using XDA

Hi, nvm I fixed my issue
Yes I've tried to heimdall back to stock (or rather the new AntonX one-click that Bryan had made) but my phone was unrecognized. Instead of trying to update the driver manually through Device Manager I downloaded the Samsung 64bit drivers for our phones and ran the setup.exe. That seemed to overwrite the drivers and next time I put my phone into download mode it was recognized and all was well.
Sorry for taking up your time.

Turns out I haven't fixed my problem. My computer is able to recognize my phone now and so I've tried One-click heimdall back to Stock UVKJ6 under Bryan's thread. I flash it, however, I get the Samsung splash screen and nothing else happens. I go into recovery and it is still the blue CWM and it gives me errores that it cannot mount or open /cache/recovery/log. If a try a nandroid restore it cannot format volume and says make_extf4fs failed on /dev/block/stl10
I tried the one-click again, I flash once, let it restart, the flash again with bootloaders but still get blue CWM. Even if I try to flash bryan's SMSKJ6bml-rc2 kernel, I still end up with the blue CWM.
Anyone have ideas on what can be wrong?

http://sourceforge.net/projects/tea...T959VUVKJ6_STOCK-UVKJ6-One-Click.jar/download

oh wow, I was just flashing the one-click kernel, I'm a noob.
Thanks a lot FBis, I should have known better.

How did you solve it, now?
johndeere5 said:
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue
Click to expand...
Click to collapse
Hi! I'm having a similar problem with that "firmware upgrade encountered an issue" message, driving me crazy. I gather you fixed the issue? Maybe I'm dense, but I can't figure out exactly how you did it. What exactly is Heimdall? Is that what you used? Other posts in this thread mention Gremlin Remover, did you use that? Where can I get Heimdall, and how do I use it if I do get it? I'm definitely a noob, but my need is real, any help will be appreciated. Thanks! R

The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.

Why Not ODIN?
lumin30 said:
The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.
Click to expand...
Click to collapse
Thanks, a few things I want to clear up though? I've heard that Heimdall doesn't work with Galaxy S2. Is that correct? In any case, isn't it just the same kind of program that ODIN is? I've been trying to use ODIN to flash a file called
recovery-cmw-hercules.tar
but it always fails. What will Heimdall do differently?
You can tell I'm pretty new to this, have patience with me please.
Incidentally, when I try to run ODIN, on the assumption that I'm seeing a download mode screen, I can get ODIN to detect the phone and I see COM(6) usually in the yellow-highlighted screen. I check only "auto reboot" and "PDA," and in the PDA field I insert the location of the tar file (above). Here's the result:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Every single time.
Kindly, R

Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.

Make sure you're using a samsung galaxy s 4g sgh-t959v. If that is not your phone stop flashing, look up the correct forums and only flash files from THAT forum, not from any other one.

lumin30 said:
Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.
Click to expand...
Click to collapse
Oops! Where should I go then? Thanks, R

The T-Mobile galaxy s2 forums would be my first guess