Database Users

[HELP] Is my vibrant completely bricked?

Not sure if this is the right section or not, but I felt I would get the best response from this forum.
OK.. so I was running euegene's Vibrant6 ROM, but I was having trouble getting any of the lagfixes to work correctly. So I decided to follow the steps outlined in this post: ((apparently I cannot post links))To flash the stock rom and so on. I had never used odin before, but a quick google search found me some directions and it seemed simple enough. So I try to flash with odin and I kept getting stuck at "File analysis.." After disconnecting my phone and trying to restart it, the phone would just go to the screen with the phone + warning sign + a computer. I was able to get back in to download mode from there. Still could not progress past the file analysis. I tried all of the tips outlined in this thread(apparently I cannot post links)) and after reading that last post, I was able to uninstall my previously existing drivers from my moto cliq.
Finally, odin progressed passed the file analysis and was flashing the filesystem.rfs file. I had a nice blue progress bar on the downloading screen, I thought everything was going to be fine. Then my phone went to a blank Blue Screen. The progress bar in odin seemed stalled at about 25%. As this was my first time using odin, I had no idea if this was normal. I let it sit this way for a good 10 - 15 min. No change. At this point I started getting concerned and thinking this can't be normal. I gave it a few more minutes and still no change. Odin was still just sitting there, right about 25% on filesystem.rfs and blank blue screen on the phone. So then I unplugged the phone, pulled the battery and put it back in, expecting that phone - error sign - computer screen again and hoping to reboot the pc and try again. No such luck.
Now my phone will do nothing. Plugged in to the pc with odin running no response whatsoever from the phone. Plugged in to the wall, no response. It's like I'm trying to turn it on without the battery in. I fear the worst and I'm 99.9% sure you guys will just confirm this as I can't get in to ANYTHING. What I would really like to know though is where I went wrong. Is it really normal for an Odin flash to take that long and to sit at that point?
EDIT: Quick follow-up question, and this is probably going to sound completely stupid, but I don't really care: is the "internal sd" an actual micro sd card that can be accessed at all, so that I can at least get my pictures/videos and such off of if I have to get a new vibrant?

this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App

merrifield69 said:
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.

skoozi said:
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
Click to expand...
Click to collapse
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?

cdw9800 said:
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
Click to expand...
Click to collapse
Yes, I downloaded a rar for stock vibrant, it contains :
s1_odin_20100512.pit which i put in the PIT field, and T959UVJFD.tar, which i put in the PDA field
EDIT: this is from the "odin1.0_T959UVJFD_512.pit_rootupdate.rar" which is linked in a few posts in this forum.

yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??

rpesigan6 said:
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
Click to expand...
Click to collapse
Every time I try it with the re-partition option clicked it seems to hang at this status:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
I am retrying this now, I have a small fraction of the blue progress bar on the "Downloading..." screen on my phone. Neither the device nor odin seem to be doing anything. How long should this normally take?
As far as I know the drivers are correct.. I installed the x64 drivers from the link provided in the informative links sticky in this forum. adb was working fine.. device manager lists the phone as "SAMSUNG USB Composite Device" and Driver details window lists three .sys files w/ version 5.16 built by WinDDK
EDIT: not sure if this helps.. here is screen shot of odin & driver details h**p://i37.tinypic.com/2cn8501.jpg (will not allow me to link or post img)

ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it

rpesigan6 said:
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
Click to expand...
Click to collapse
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.

skoozi said:
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
Click to expand...
Click to collapse
a blank red screen? all i can say is possibly try using another windows computer.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B

vibrantFTW said:
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
Click to expand...
Click to collapse
I'm trying to do this, but if I open ODIN with the phone already in download mode, ODIN does not see it. Pulling the battery and putting back in (downloading screen still up during this) does not change that. Maybe I misunderstood?
yes, i did.. likely at 4 am i guess.. so far its gotten past the modem.bin which it hasnt done in a couple hours of messing with this.. now its on filesystem.rfs again and stalling again, only now its only at about 10 - 15% as opposed to the 25% i was getting a couple hours ago before it stalled. This is with re-partition unchecked, btw. With it checked, odin still just sits at do not remove target.

I had this problem.. what I basically did was:
- Open Odin... add all the PIT and PDA files up (Re-partition UNCHECKED)
- Plug the phone in USB
- When the green battery was on the screen: hold volume buttons (basically.. get into download mode)
- Once in download Odin doesn't detect anything? Unplug USB and replug it back in
- Odin should detect your phone and one of the boxes should be labeled: COM[#]
Any # should be fine as long as you have the proper drivers
Then hit the start button. During this whole process, you should see the Android digging with a blue bar right below it. The screen shouldn't go black, blue, or anything crazy. Just android digging and a blue progress bar.
http://forum.xda-developers.com/showthread.php?t=734475&highlight=Stock Was the thread I used. Download hashtab (google it) and verify that the MD5 checksums are correct, once installed right click the file -> properties -> hashtab and then copy paste the MD5 on that thread an verify that it is correct.
For me the Odin process took less than a minute, the trick for me was to preload everything in Odin before plugging in the phone otherwise it would get stuck.
Personally, I don't think your phone is bricked anyway. Just some technical difficulties with getting Odin to work. The first time around when I was trying out Odin, it was messing up for me. Hope this helps.
Vibrant Drivers: http://forum.xda-developers.com/showthread.php?t=728929 -- If these aren't the set of drivers you're using, then uninstall yours and install this. This one works with no problems.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
Was able to try this this morning.. it worked first try. With all the problems I was having, I was dumbfounded with how smooth it went. Don't know what was going on. Thank you all for your help with this

Hey guys, I figured I'll post here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6 and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else... what can I do? Anyone can help me?
Thanks.

I fear my problem is worse as i was having the same issue with it loading filesystem.rfs and was stalling so i attempted to restart the process and now all that will display on my phone is an image of a cell phone a computer and a yield sign between. Plz help

Sounds like you need to upgrade Odin3 1.0 to Odin3 1.7

Ok i DL'ed Odin3 1.7 and still the same. The vibrant screen doesn't even come up, just an image of a cell phone and a comuter with a yield sign in between.

Start odin on your pc, remove batt, insert USB, hold down volume buttons and pop in the batt. This always gets me into download.
Sent from my SGH-T959 using XDA App

May god bless you and your children, and your childrens children, and their children!!!!!!!!!

(HELP) phone wont boot up did i brick

heres more trouble that this dang epic is causing
i was trying to just start all over and go back to stock i used odin
and it froze so i unplugged when i tryed to power on
it just has a phone with a line going to a pc with a yellow triangle
what to do this epic is drivin me crazy did
i brick it and is there a way to fix

???????????????????

Nope just a bad flash just pull the battery and do it again
Sent from my SPH-D700 using XDA App

How. Do I put it back in download mode for Odin to recognized it when I plug it in does nothing when I tturn it on all it is is that screen

Basically just pull the battery and unplug the usb cable, restart odin, put put the phone in download mode i.e., yellow triangle, and plug in usb to computer. Make sure odin show connection on the com port. Put your .tar file in the pda section and hit start. No need for pit or zimage files

what do i do if when i take out the battery unplug usb the put it in download mode and plug it back it nothin happends no com shows up or anything
so i put tar in and hit start all it does is says
<osm> all threads completed. (succeed 0 / failed 0)

the wierd thing is sometimes when it acts like its chargin and its off then
some how i get it to go to clockwork recovery
and i could not get clockwork to come up for anything when the phone worked

does any one have any other device i am so mad lol
and i have tried everthing possible known i cant get anything
i even got in the recovery flashed a rom still wont turn on only goes to that screen

sense i can get to clockworkis there a special .zip file i can flash that will help this because odin dont reconize it and there is no com port select place
i have wiped in clockwork i have flashed a rom but nothin
clockwork would not load up when phone worked now it will but phone wont load lmao
is there any help or do i just keep pluggin up a 500 dollar papper wieght ????
i am about to explode

Voodoo install from OCLF Ryan bricked the Vibrant

I had the update with OCLF installed and it worked fine until I decided "accidentally" (very very regretful now) to install Voodoo from the OCLF app. Then the phone went into a soft reset and got stuck at the Vibrant screen.
Since then I've tried to select "install packages" or "reboot system" options in the recovery mode, but it showed only a partial progress bar at the bottom, then it got stuck at the Vibrant screen.
I gave Odin a try but the app does not see any com port after use ADB reboot or recovery commands.
Btw I did NOT select USB debugging mode before installing voodoo. I did install the USB driver for the Vibrant but am not sure it even works because the Odin app did not see any com port.
Any help is appreciated! I don't want to loose data and files in the internal storage. This is kinda urgent because I need to use phone.

i900 said:
I had the update with OCLF installed and it worked fine until I decided "accidentally" (very very regretful now) to install Voodoo from the OCLF app. Then the phone went into a soft reset and got stuck at the Vibrant screen.
Since then I've tried to select "install packages" or "reboot system" options in the recovery mode, but it showed only a partial progress bar at the bottom, then it got stuck at the Vibrant screen.
I gave Odin a try but the app does not see any com port after use ADB reboot or recovery commands.
Btw I did NOT select USB debugging mode before installing voodoo. I did install the USB driver for the Vibrant but am not sure it even works because the Odin app did not see any com port.
Any help is appreciated! I don't want to loose data and files in the internal storage. This is kinda urgent because I need to use phone.
Click to expand...
Click to collapse
The same thing happened to me. I even posted it yesterday to warn people to be careful with RYANZA Voodoo and I got flamed and insulted. Basically you fried your kernel. I tried different things and what worked for me was ODIN the JI6 back. Go to Vibrant Directory Bible under Samsung Vibrant--Android Development and find that thread. Go to the ODIN section and download the JI6 package. You will need to get into 'Download" mode on your Vibrant for ODIN to work. You need to have the phone plugged into computer via USB, hold down both volume buttons and the power button at the same time. When the screen becomes black, release only the power button and download mode will pop up. Then bring up ODIN and make sure the yellow com message pops up. With ODIN it will work right away (like 2 minutes). If you see it hanging then you need to try it again. When you get your phone back up you need to disable voodoo. Good luck. Know that the Vibrant is almost impossible to kill, you will be able to bring the phone back to life.
here's the link: http://forum.xda-developers.com/showthread.php?t=771111
instructions here: http://forum.cyanogenmod.com/topic/...r-vibrant-and-return-to-stock-phone-pc-error/

I tried flashing it using odin but the phone would start, show the tmobile thingy and just turns off. Is there any way around this?
Sent from my HTC Glacier using XDA App

Thank you for your prompt reply
quest4fire said:
The same thing happened to me. I even posted it yesterday to warn people to be careful with RYANZA Voodoo and I got flamed and insulted. Basically you fried your kernel. I tried different things and what worked for me was ODIN the JI6 back. Go to Vibrant Directory Bible under Samsung Vibrant--Android Development and find that thread. Go to the ODIN section and download the JI6 package. You will need to get into 'Download" mode on your Vibrant for ODIN to work. You need to have the phone plugged into computer via USB, hold down both volume buttons and the power button at the same time. When the screen becomes black, release only the power button and download mode will pop up. Then bring up ODIN and make sure the yellow com message pops up. With ODIN it will work right away (like 2 minutes). If you see it hanging then you need to try it again. When you get your phone back up you need to disable voodoo. Good luck. Know that the Vibrant is almost impossible to kill, you will be able to bring the phone back to life.
here's the link: http://forum.xda-developers.com/showthread.php?t=771111
instructions here: http://forum.cyanogenmod.com/topic/...r-vibrant-and-return-to-stock-phone-pc-error/
Click to expand...
Click to collapse
I'll give it a try later. Is there a good link to download the USB driver? I did but am not sure it will work with Odin. I also forgot to release the pwr button only when the Vibrant screen came on. You said release it at the black screen.

Theres voodoo on the oclf app? Where do you download it? When I downloaded it from the market it wasn't there. Do I need to install a supported kernel before it shows up?

Another thing is the phone is not in USB debugging mode before. Is this needed for Odin to work?

It is in OCLF app
krackers said:
Theres voodoo on the oclf app? Where do you download it? When I downloaded it from the market it wasn't there. Do I need to install a supported kernel before it shows up?
Click to expand...
Click to collapse
I don't remember exactly how it looks but the app has like 3 tabs: 2nd is available, 3rd unavailable or vice versa, 1st is probably the voodoo one. BE CAREFUL, read the kernel instruction first! I am sure they are not compatible. It should be disabled one or the other so users wouldn't get hacked.

ok the 3 button procedure got the phone into Recovery mode like this screen with yellow text:
--------------------------------------
Android system recovery <2e>
reboot system now
reinstall packages
--Appling Multi-CSC
Installing Multi-CSC
------------------------------------
Selecting either "reboot system now" or "reinstall packages" gives this screen:
----------------------------------------
Installing from sd card completed
rebooting..
Phone reset done
-----------------------------------------
The phone now got stuck at the Vibrant screen!
How to get into the download mode?

Holding vols up down with battery in and then plug in the USB cable, the Downloading screen came up with the digging icon and a message "do not turn off target" but it just got stuck there. I typed in the adb reboot download under the folder containing the adb files but it said "error no device found". I installed both drivers, one from Samsung site and one x86 from Softpedia site. Is it time to get a new one?

Try this.
Click HERE FOR ODIN 1.30
Samsung USB Drivers MS Windows 64bit HERE 32bit drivers HERE pick the drivers that work with your pc I have windows 7 so I use 64bit.
Step 1. Download the 512 PIT file HERE this file needs to be un rared with Winrar its a free program its HERE.
Step 2. Download the T959UVJFD.tar HERE
Step 3. Get your phone in download mode try just holding the volume up and down at the same time then plug the usb in, you might have to pull the battery and then put it back in the phone then hold volume up and down at the same time then plug the usb in it should go into download mode.
Step 4. Open Odin 1.30.
Step 5. Load the 512 PIT file you extracted with winrar into Odin 1.30 PIT section of Odin
Step 6. Load the T959UVJFD.tar you downloaded into Odin 1.30 into the PDA section of Odin.
Step 7. Click the Star button in Odin.
Step 8. Let it do its thing.
Step 9. Thank me
Step 10. Hope this helped it really doesn't get much easier then what Ive given you in this list.

Will the pit file WIPE the data (photo..)?
AustinKnight45 said:
Try this.
Click HERE FOR ODIN 1.30
Samsung USB Drivers MS Windows 64bit HERE 32bit drivers HERE pick the drivers that work with your pc I have windows 7 so I use 64bit.
Step 1. Download the 512 PIT file HERE this file needs to be un rared with Winrar its a free program its HERE.
Step 2. Download the T959UVJFD.tar HERE
Step 3. Get your phone in download mode try just holding the volume up and down at the same time then plug the usb in, you might have to pull the battery and then put it back in the phone then hold volume up and down at the same time then plug the usb in it should go into download mode.
Step 4. Open Odin 1.30.
Step 5. Load the 512 PIT file you extracted with winrar into Odin 1.30 PIT section of Odin
Step 6. Load the T959UVJFD.tar you downloaded into Odin 1.30 into the PDA section of Odin.
Step 7. Click the Star button in Odin.
Step 8. Let it do its thing.
Step 9. Thank me
Step 10. Hope this helped it really doesn't get much easier then what Ive given you in this list.
Click to expand...
Click to collapse
Somewhere in the forum said that selecting the pit file will wipe all data. Is that true because I so want to keep EVERYTHING intact! Just got back from a short vacation in Waikiki
I got the PC to see the Vibrant now with Odin but I downloaded the newer tar file T959UVJI6 (2.1 updated ver) but can not see it from selecting PDA button, it can only see the old T959UVD (stock 2.1). I am at the no point of return now so within 15mins if there is no answer then I must get going.
Thanks again!

Never mind guys! my bad did not unrar the tar file..going to download it now..wish me best of luck!

ok downloading now... it is a nerve wrecking experience comparing to WM6.1 custom rom flash which was very smooth going. I still miss the original i900 Omnia. I am going to be late for the church but God please forgive me! Oh it passed the downloading and got the S logo..

it booted up but stuck at black screen with all soft keys lighted up, tried the install packages in recovery mode again..

I guess I need to download the pit file? Will this wipe out all data?

I don't have voodoo... where did you get your oclf app from? Is it not showing because I have stock JI6 kernel?

i900 said:
I guess I need to download the pit file? Will this wipe out all data?
Click to expand...
Click to collapse
Did you follow my to-do list to the T?
this might help
you need to flash this PDA file with odin EUGENE373_SamsungS_Froyo_PDA along with the PIT 512 you should still have from the unbrick instruction odin forum then after you flash those files you need to let it do its thing it will prob take you to recovery just long press the power button and when it turns off put the usb back in the phone to get it into Download mode(just get back into download mode any way you know how) and then follow those instructions you did earlier with the unbrick instructions forum just flash the Eugene373 SamsungS Froyo PDA file first then after you flash it get right back into download mode and flash stock vibrant rom through odin.

Odin in eugenes froyo that doesnt brick.Make sure you use the 513 pit file that comes with it. When its done, pull the battery and odin the jfd. Use the 512 pit file with jfd. Check the repartition box for this one. You will be back to stock and all the lag fixes will be gone. This process works to save your vibrant from ALMOST everything
^^^oops, didnt make it to your post...just tryin to help

OCLF from the market by Ryan
krackers said:
I don't have voodoo... where did you get your oclf app from? Is it not showing because I have stock JI6 kernel?
Click to expand...
Click to collapse
But use it with extreme CAUTION at your own risk. Don't brick it like mine

Again guys thanks for your time and help but just one more time, I am still a bit confused, can you list exactly what files to download in order to get the phone back alive without loosing any data and files?
Download 512 or 513 pit first? Do it together with the tar file (check both boxes in Odin)? I understand 512 pit go with JFD (stock 2.1 rom before the update). How about the latter one? It goes with JI6? Now I got only the JI6 in the phone without the pit file. Should I download 512 with JFD first then do the latter one with JI6, and all data still remain intact?

[Q] how do i fix my phone when it froze during update

i was trying to update my epic 4g to 2.3.3 efo2 and it froze at factoryfs.rfs any help i had to unplug and take battery out for phone to shut off and when i turn on it shows a phone and a computer with a caution sign in the middle any way i can go back to factory settings or does anyone know were i can get that eb13 update that samsung let use dl from there website because that software also flashed the phone and helped me before when i screwed up my phone any help would be great

Can you bring download mode up again? Did you try to odin it again? Maybe try changing out the USB cable, especially if you are using the stock cable, it sucks.
For further help with odin, qbking77 has very helpful videos with a link in his signature.

kgs385 said:
i was trying to update my epic 4g to 2.3.3 efo2 and it froze at factoryfs.rfs any help i had to unplug and take battery out for phone to shut off and when i turn on it shows a phone and a computer with a caution sign in the middle any way i can go back to factory settings or does anyone know were i can get that eb13 update that samsung let use dl from there website because that software also flashed the phone and helped me before when i screwed up my phone any help would be great
Click to expand...
Click to collapse
if you can still get into dl mode i would suggest trying the odin again with a different cable or put the ef02 tar in pda if you put it in phone. or try to odin in the stock ec05 tar

You could try a friends computer...or a different usb port.

Also try it with the battery out. Plug into computer, push 1 key and power to get into download mode, then start Odin. Make sure only reboot and PDA is checked with EF02 tar file in PDA section.
Sent from my SPH-D700 using XDA App

Update Bricked Phone?

Received a OTA update yesterday on my Rooted, Samsung Fascinate. After the update phone hangs on boot screen. Powering the device while holding the volume buttons gives me the Android System Recovery <3e> Screen. On this screen I have a bunch of E: Failed to open Recovery, cache, data kernal etc. (I can give all specifics if needed)
If I press the home button I get what looks like a screen to update the phone (Android Character with Triangle) From here I tried the instructions from the "How to recover from any brick" thread. Neither method is working. Any ideas?
From the boot screen I am also not able to scroll up or down to select a wipe apply update from SD Card etc.
Any help would be appreciated.
Thanks

I don't know how to fix it (don't get discouraged I don't know a lot in this area) but it seems to me if you play your cards right you might be able to complain to verizon and get an early upgrade out of it. A galaxy nexus would look mighty fine in your pocket.

probably a conflict with being rooted when it updated. Odin back to stock and update completely and then re-root.
Sent from my icecream fast

1. Download this file to your PC get you to a rooted ROM with the proper recovery: http://www.mediafire.com/?d0wha8lc1hjxxdf/geewiz-2.3-fullwipe-11302011.tar.md5 (this is the EH03 GeeWiz Odin Package ROM by djp952)
2. Boot phone in download mode by powering phone off, hold down vol button on phone, connect cable to PC (there is no need to remove battery)
3. Open Odin and Place the GeeWiz file you just downloaded into the PDA slot, click Start
4. Your phone should now be on the EH03 GeeWiz ROM
5. If you want to flash a different ROM, download the zip file for the ROM of your choice onto your phone (use the phone to download it), reboot into Recovery (what you booted into before is the stock Samsung recovery, not the Clockwork Recovery you need), choose "install zip from sd card", select "choose zip from sd card", choose the Download folder (the folder in which your zip file should appear), choose that zip file, and install.
6. Profit.
Has anyone seen John Connor?

I gave this a shot, and I am thinking either my phone is not in "Download Mode" if that's possible or its a driver issue. Here is the response I get from Odin V1.83
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> geewiz-2.3-fullwipe-11302011.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I have multiple Samsung Cables (I tried all of them) but it is possible I am not using the one that came with this phone (Could this be an issue?)
I am using windows 7 64 X64 The phone shows up in the in the device manager as LibUsb>Samsung Andriod
On the recovery screen I have noticed if I push the home button it flips between the Android and the Triangle to a screen that shows all the files the boot loader cannot find. Does it matter what screen I am on when I try the upload?
Thanks in advance for any advice for a n00b!

You need to download the Samsung USB drivers for your PC, as it appears to be not recognizing your phone properly. You should be able to find what you need on Samsung's website. Hope this works.
Has anyone seen John Connor?

Ok So I have removed / Re-Installed the drivers on 2 different machines (One Win 7 64 Bit other is Win Vista 64 bit. I get the same results on both machines. Any other ideas?

Have you tried Heimdall? For some screwed up reason odin will not recognize my phone but Heimdall will.

mentose457 said:
Have you tried Heimdall? For some screwed up reason odin will not recognize my phone but Heimdall will.
Click to expand...
Click to collapse
I gave this a second try. The "Driver" portion of the software detected the Samsung_Device and I was able to install the driver. However when I try the front end I get an error "Failed to Detect Compatible Device"
Im getting really close to jumping ship on this one and going out and getting a new phone.
I appreciate all the help!

Found a few threads on Verizon forums. Sounds like there have been a few people run into the same issues. Anyone tried returning a rooted phone to Verizon? If so and they caught it what were the repercussions?

ascottn said:
I gave this a second try. The "Driver" portion of the software detected the Samsung_Device and I was able to install the driver. However when I try the front end I get an error "Failed to Detect Compatible Device"
Im getting really close to jumping ship on this one and going out and getting a new phone.
I appreciate all the help!
Click to expand...
Click to collapse
Just to be clear, you are putting the phone in download mode then installing the drivers via zadig right? That should work.
loading drivers in windowz is the most retarded thing in the world. You dont happen to have access to a computer running linux do you? Heimdall works flawlessly in linux.

Good Questions
1- Yes I am installing the windows drivers as you describe
2- As for download mode how do I go about doing that? All I can seem to do is to boot to the <3e> bootloader. I cannot scroll up or down through the options. However I can press the home button and it goes to a picture of an Androind with a triangle around it (Green Droid, White Triange, Orange !)
3 -I didn't realize that heimdall worked in linux. I just downloaded it and gave it a spin in Ubuntu. I am getting the same error "Cannot Detect Download mode Device"

ascottn said:
Good Questions
1- Yes I am installing the windows drivers as you describe
2- As for download mode how do I go about doing that? All I can seem to do is to boot to the <3e> bootloader. I cannot scroll up or down through the options. However I can press the home button and it goes to a picture of an Androind with a triangle around it (Green Droid, White Triange, Orange !)
3 -I didn't realize that heimdall worked in linux. I just downloaded it and gave it a spin in Ubuntu. I am getting the same error "Cannot Detect Download mode Device"
Click to expand...
Click to collapse
To enter download mode power off your phone, pull the battery, hold the volume down button while plugging in your phone. The screen should show a yellow triangle with the Android guy in the middle.
Sent from my SCH-I500 using XDA App

I have been digging around and I stumbled onto the correct procedure for getting to download mode. I don't know how I missed this *FACEPALM*
I want to say thanks to everyone. I am back up and running. Thanks to all for the help!

Excellent! I was starting to think you had a hardware problem as in a faulty micro USB port on the phone...
Has anyone seen John Connor?

Would just like to add that the 2.3 OTA soft bricked my fathers stock phone. I am now hunting the non rooted file in another thread to odin or heimdal back to 2.2 to alow me to try again.
Verizon LVL 2 says he checked and I am the first customer to report a bricked phone from the OTA to 2.3. Yea... right.

Here is the guide I followed to get my phone back to stock (It includes download links for stock roms.
This is the one part missing from this tutorial. Probably because it assumes that these steps are known if someone has bricked a phone
make sure u have your samsung usb cable plugged into the pc but not into the phone (not yet at least) and make sure u remove your battery.
step 1. hold down the volume down button and continue holding
step 2. whille still holding down the volume down button, plug your phone into the usb cable
step 3. while still holding down the volume down button, pop your battery in.