Database Develop

How to Flash F/W after bricking my phone

Hello,
Well i'm new here and i had a little problem with my new Samsung Galaxy S i9000. Today i wanted to flash my phone but after the first time my 3G connection wouldn't work. So after that i did a second try but this time something went wrong and i pulled the cable of the phone (i know u shouldn't do that!). Now when i start up my phone it shows a picture that i need to connect my phone to my computer. But when i do that trying to reflash it, it takes ages and nothing happens, Odins shows only these Command lines and nothing more even after 15 minutes:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
Click to expand...
Click to collapse
I tried al kind things like these follow:
20.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
Most likely: YES! In almost any case, you should still be able to turn off the device (if necessary by removing the battery) and start into download-mode (VolumeDown+Home+Power) or recovery-mode (VolumeUp+Home+Power). After (for example) an unsuccessful flash, you can retry the flash in download-mode (same steps as when flashing a functioning device). If a flash to a function f/w (without apply any update.zip) doesn't help or you cannot get you PC to flash at all, you can ask for help here. (Please try to reboot your PC as well if you cannot flash and try FAQ8 if you have trouble with getting the phone recognized on Windows 7/Vista x64)
If you see a symbol asking you to connect to the PC, depending on how you arrived at this point, it may be sufficient to connect to the PC and run Odin (i.e. press "start" when the phone is recognized) without adding any files. This may, however, leave some residual issues if (for example) had an incorrect/incomplete flash so you may want to do a normal flash after this!
Click to expand...
Click to collapse
But still nothing works, but though i still can get the phone into download mode, Recovery mode (VolumeUp+Home+Power let me show the sign that i need my phone connect to the Pc).
Please help me i really could use some help with this!

http://forum.xda-developers.com/showthread.php?t=723596

Wait, what? So you're saying that the first time you flashed, everything worked but you forgot to put the correct APN settings from settings menu to enable 3G. If so,

it's hard to brick the phone.
I tried repartition the storage, while flash an small flash file, so in theory, a "clean" partition of storage w/o any kernel and what not, and I could still flash the f/w.
that said, when it happens to me (when it's an empty partition), the phone will appear not to be boot up, and then you may find yourself not being able to go into download mode. chances are, the phone might appear to be power off, but its probably in a panic mode at the previous boot up, so there's no way you can change to download mode.
just take out the battery, leave it for 30s-1min, and then put battery back and then do the volumne down + home button + power button to bring the phone into the download mode.

RTFFAQFFS!

I managed to get my SGS back to life after taken my battery out for like 2 minutes or more...
I'm flashing atm and still working great!
Now i need only make shore that my modem (3g connection) will work, last time i couldn't set my settings back for APN.
But still a question here,
Does anybody knows the best working firmware for europe, The Netherlands?
Thanks for the help Guys!!! i really do!

buddy01 said:
Wait, what? So you're saying that the first time you flashed, everything worked but you forgot to put the correct APN settings from settings menu to enable 3G. If so,
Click to expand...
Click to collapse
Haha indeed... just fill in the APN settings hahaha

Stuck at Galaxy S logo!

Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared

Please Help!
- UPDATE: SOLVED!
Hi there, I'm having the same problem on my I9000B. Please help me.
This is my story, I had upgraded my 2.1 firmware to VIVO's 2.2 Froyo via KIES with the Kies Registry Patcher (used ZVV). Everything worked perfectly, but I wanted to root my I9000B so I made the terrible mistake of using CF-Root via Odin, (http://forum.xda-developers.com/showthread.php?t=788108) following the exact instructions. The kernel replacement (zImage file) was for the I9000 so I had the touchscreen problems. When the phone booted showed Samsung galaxy S GT-I9000B and then inmeadeatly the "B" dissapeared.
Because of my n000bness I tried to use the zImage file from this ROM (VIVO's) (http://forum.xda-developers.com/showthread.php?t=858483), by downloading my own .tar created file (with 7-zip) of the zImage file. Here is were things went down. I got the android - USB cable boot icon. I could not go into recovery mode but I could do download mode, so I re-flashed VIVO's ROM (the one published here) with Odin:
I used the 803 .pit file, Odin 1.3
I did not check re-partition
I selected the ROM as the PDA file and I left PHONE and CSC blank.
the ROM was downloaded to the phone and Odin did not gave me problems.
My problem here is that I get the black screen with vibrations from time to time on boot. This is exactly what happens:
The phone starts showing "Samsung galaxy S.... GT I9000B (at least shows "B")
I can get into recovery mode but the following appears:
Code:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please us UI menu for format and reboot actions.
copy default media content failed.
Then I did a factory reset, succesfully completed, tried again flashing the ROM but with Re-partition box checked (as instructed here: http://forum.xda-developers.com/showthread.php?t=723596) but the same stuff happens.
Please tell me what to do! I know it was a stupid mistake trying to fix ony the zImage file, and stupider was using CF-Root on my non-compatible device.
PS: I can get into download mode with no problems
Code:
pda i9000bvjjpa
phone i9000bvjjpa
csc i9000bzwjp3

I have exactly the same problem
but i can go into recovery mode and download mode.
the galaxy screen is I9000 and my sgs is I9000B
any ideas?

A friend of mine has the same issue on his SGS. Both recovery and download mode working.

Have you done JUST like this:
Figueiredo81 said:
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Click to expand...
Click to collapse
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.

Thanks!!
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Margaliini said:
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Click to expand...
Click to collapse

Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.

Please, post the link or give me directions for the Claro's ROM. I am having the same problem here.
Thanks.

gtg2 said:
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Click to expand...
Click to collapse
worked here
thanks

thanks for the help i love you no homo !

Un Loko said:
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Click to expand...
Click to collapse
JM2 with pit method is perfect. my "E: can't mount /dev/block/mmcblk0p1" problem has finally been solved.
Thanks

This worked for me.
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)

???I bought my Phone from CSpire but stuck on At&t Logo???
Samsung Galaxy s Showcase stuck on the At&t Logo...Will not let me go into Download mode??? Help please?

[Q] Odin3 stuck on SetupConnection

Hi all
I stupidly upgraded to 2.2.1 the other night and for the last 2 days I have been trying to connect to the phone via Odin so I can apply the 2e Recovery and put Darky 8.0 on.
The problem I am having is that every time I try to apply the PDA file (from xda-devs), it just gets stuck on SetupConnection (I have booted the phone into Recovery mode). I have tried it on my Win7 x64 PC and I have tried it on my WinXP x86 laptop, same result. I have tried Odin 1.0, 1.3 and 1.7. I have uninstalled the Kies drivers, installed older ones, installed newer ones...nothing. I have tried removing the SD card, nothing.
Odin sees the phone when I plug it in, it show me the COM port and it says "Added!".
I'm at my wits end! 2.2.1 has fixed nothing for what I use, GPS is still rubbish, OneClickLagFix doesn't work on this version and they've put in this ridiculous 3e Recovery. So basically Samsung will not only not give us (in the UK) a decent version of their ridiculous firmware, but they have taken away our ability to fix up their garbage firmwares!
If anyone could help me get around this Odin problem, I would be most grateful! Thanks
If not, I'm going to get shut of this pile of pants and get a proper Android phone (which I don't want, because I really can see the potential)
Cheers!

You could try Heimdall instead of Odin its on the forum .
Odin sees the phone when I plug it in, it show me the COM port and it says "Added!"
Sounds like a duff file maybe .
I have flashed CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
at least twenty times in the last month without a problem .
jje

JJEgan said:
You could try Heimdall instead of Odin its on the forum .
Odin sees the phone when I plug it in, it show me the COM port and it says "Added!"
Sounds like a duff file maybe .
I have flashed CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1
at least twenty times in the last month without a problem .
jje
Click to expand...
Click to collapse
Hi
I have Heimdall, but I don't see which box to put the tar file in... There are several options under PDA/Code
Thanks for your reply
Edit: OK so my best guess is to put it under zImage. Done that, connected phone in Recovery for BML and the Start button stays greyed out.
Edit2: Do I need a .pit file? The instructions for CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1 don't mention one...
Edit3: Still with Heimdall, I unzipped the .tar so I have zImage unpacked, the Start button lit up, I click it:"Failed to detect a compatible device"
Edit4: Tried to downgrade to 2.1 Eclair using samfirmwares. Odin goes through md5 checks, they all pass and then....SetupConnection... What's going on?

Solved!
I used the Down Volume instead of Up Volume.

Yes! I solved too with this board. Thanks!

Huge problem. Bricked phone???

New member and somewhat stupid for trying to do this:
Long story short I attempted to throw gingerbread 2.3.X on the phone and now its stuck in either download mode, recovery mode, or if i just turn it on it comes up and says "GALAXY S GT-I9000 Samsung" The last thing that was successful was putting the SpeedMod Kernel on it.
In recovery mode it says "ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK" on top and bottom.
The phone started out with factory settings.
When i try and use the ODIN 3 and try to do the Mast Clear it says :
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> Master Clear Started.....
and then stays like that indefinately...
Same thing with hitting "start"
Please let me know how to fix this, I know there are some really brilliant individuals on this forum and it would be greatly appreciated.

search for odin, download it, follow the steps and flash back to stock. you'll be fine especially since you can get into download mode.
edit: gah you already have odin. do you have one click or the one where u have to put the pit and tar files?
the same advice applies though, find the stock files, and go into download mode, then plug it in and flash back to stock.
i think master clear only works when the phone is on and you have usb debugging enabled.

Ive got ODIN 1.7 and ODIN3. I can get them to both recognize the phone but when I try and hit "start" with v1.7 it ust sits there forever. and Im not able to get ODIN3 to do anything either.
Any way you could provide a more step by step solution?

If you're having problems with ODIN, something that seemed to work for me was to remove my SIM card.
Try removing it and see if you have any luck.

I dont have anything in the phone, no sim and no external.

Just left it alone for a bit and came back and turned the comp back on and everything worked for ODIN. Thanks for the help fellas

[Q] HELP! Fully bricked NEW Galaxy S?

Hello... just got a Galaxy S new and I think I have fully bricked it.
It was on 2.2 stock and I installed Darkys v10.1 extreme rom on it following the steps in this guide..
http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
I first installed
- Ficeto_JVH_I9000_Odin:
- DarkyROM_v10.1:
and installed the PIT and PDA.
I decided that I didn't like Darkys and tried to install Cyanogenmod 7 on it..
my friend said I needed to install a PIT first, then install a JPY rom afterwards.
I used Odin 1.3 and selected this pit "s1_odin_20100512"
and I think I pressed Re-Partition as previously in the guide that was what they did..
Auto reboot and F. Reset time were both ticked
This was the log
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
How can I save my new baby?!!!
When I mean bricked, I don't think it turns on at all...... doesn't light up or enter recovery.
Most ironic is, I bricked it relatively easily when people said it's virtually unbrickable.
!!!!!!!!

You may never flash just a pit file!!!
You only use it when you flash a 3file rom.
That's the same for repartition.
If you can get it in download mode, everything is fine.
Else your screwed...
A sgs is virtually unbrickable if you had flashed it correctly.
When you don't know how to flash always follow a tut!!!
Sent from my GT-I9000 using Tapatalk

I never realised you could just use a .pit without the rest.
The .pit file isn't "installed" it is a file which tells the system how to wipe and then repartition the memory in your phone. Essentially you wiped the phone without installing anything on it after that. I am not sure if it wipes the bootloaders as well (at the very least it has partially wiped them if recovery is not working)
If you can get download mode to work, then you should be alright. If it doesn't work, a jig may or may not help. If you can not get download mode to work, then you have no other recourse than to send it back for repairs. They will need to replace the erased bootloaders if this is the case.
If on the other hand you do manage to get it to work, read very carefully the process that is actually involved in flashing firmwares with odin/heimdall. Yes it is very hard to permanently brick your phone if you know what you are doing. Hell in most cases even if you don't know what you're doing it's hard to permanently brick your phone. You went ahead and did one of the few things that is a danger area though. In general though, you should not repartition (ie use the .pit file) unless necessary (although repartitioning wont really do anything bad it's completely unneeded in most cases) and don't flash boot-loaders unless necessary. NEVER repartition without flashing a rom with it.

Shanakin said:
I never realised you could just use a .pit without the rest.
The .pit file isn't "installed" it is a file which tells the system how to wipe and then repartition the memory in your phone. Essentially you wiped the phone without installing anything on it after that. I am not sure if it wipes the bootloaders as well (at the very least it has partially wiped them if recovery is not working)
If you can get download mode to work, then you should be alright. If it doesn't work, a jig may or may not help. If you can not get download mode to work, then you have no other recourse than to send it back for repairs. They will need to replace the erased bootloaders if this is the case.
If on the other hand you do manage to get it to work, read very carefully the process that is actually involved in flashing firmwares with odin/heimdall. Yes it is very hard to permanently brick your phone if you know what you are doing. Hell in most cases even if you don't know what you're doing it's hard to permanently brick your phone. You went ahead and did one of the few things that is a danger area though. In general though, you should not repartition (ie use the .pit file) unless necessary (although repartitioning wont really do anything bad it's completely unneeded in most cases) and don't flash boot-loaders unless necessary. NEVER repartition without flashing a rom with it.
Click to expand...
Click to collapse
Thanks for your long and detailed explanation of what I have exactly done..
I had kind of guessed by now of what I have done.. which is very unfortunate as like you said, "I never realised you could just use a .pit without the rest. ".
Such a dangerous thing, I wouldn't have expected the software to allow me to do that
Instead of making a jig with resistors, I have read that you can cut a micro usb cable instead??
Would you be able to direct me to other resources or information on how to make one?
If a jig doesn't work, how much money am I looking at for someone to fix it?
Thank you very much,
Kind regards

you never said whether download mode works or not ??

azzledazzle said:
you never said whether download mode works or not ??
Click to expand...
Click to collapse
From what it appears, it doesn't seem to turn on at all...

Removed because azzledazzle beat me to it

Altimas said:
So can you confirm you cannot get into download mode?
Click to expand...
Click to collapse
How can I confirm that I can't get into download mode?

Volume DOWN button + home button + power button all at same time,

azzledazzle said:
Volume DOWN button + home button + power button all at same time,
Click to expand...
Click to collapse
Unfortunately it's not looking like it works :'(

USB JIG may be your only hope then.
but before you do that, take battery out for 5 mins. Then hold the 3 button combo for DOWNLOAD mode, THEN put the battery back in, STILL holding the 3 button combo.
and also, does the phone do anything when plugged in ?? no charging indicator or lights, vibrations ???

azzledazzle said:
USB JIG may be your only hope then.
but before you do that, take battery out for 5 mins. Then hold the 3 button combo for DOWNLOAD mode, THEN put the battery back in, STILL holding the 3 button combo.
and also, does the phone do anything when plugged in ?? no charging indicator or lights, vibrations ???
Click to expand...
Click to collapse
I will try taking the battery out and putting it back in with the three buttons together.
Also, no light or vibration when plugged in USB..
If the jig fails, any idea of the ball park for the cost for it to be repaired?

if the jig fails, send it off to samsung a blame it on a failed KIES update, act dumb and hope for the best, chances are they wont charge

azzledazzle said:
usb jig may be your only hope then.
But before you do that, take battery out for 5 mins. Then hold the 3 button combo for download mode, then put the battery back in, still holding the 3 button combo.
And also, does the phone do anything when plugged in ?? No charging indicator or lights, vibrations ???
Click to expand...
Click to collapse
yes omfg you don't understand how happy i am righ tnow.
I took out the battery and did what you said and i get the downloading screen now.
It is 1am in sydney and i am willing to stay up to get my phone on the downloading screen!!
It has finally turned on!
Please help me, what do I need to do next?

jing713 said:
yes omfg you don't understand how happy i am righ tnow.
I took out the battery and did what you said and i get the downloading screen now.
It is 1am in sydney and i am willing to stay up to get my phone back up running!!!!
Please help me !
Click to expand...
Click to collapse
first of all CHILL OUT !! dont panic or you could make the same mistake.
Download this http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
DO NOT use pit and DO NOT select re-partition
let me know the outcome, if the above firmware dont fix it, we need to get you a 3 file firmware THEN and only THEN do we add PIT and REPARTITION

azzledazzle said:
first of all CHILL OUT !! dont panic or you could make the same mistake.
Download this http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
DO NOT use pit and DO NOT select re-partition
let me know the outcome, if the above firmware dont fix it, we need to get you a 3 file firmware THEN and only THEN do we add PIT and REPARTITION
Click to expand...
Click to collapse
Thanks for the encouraging words..
I'm downloading it now, 370mb?!
After download, do I use Odin 1.3 or 1.7 to flash the TAR and ONLY THE TAR?
BTW I'm with Windows 7 64 bit, I've seen guides saying 1.7 may not work perfectly... however It worked fine for me with installying Darkys rom..

i use 1.7 too, also running win 7 64 bit. no problems for me.
the firmware is a FULL FROYO including all dbdata's bootloaders, kernel the full monty
only insert the .tar file in the PDA section of odin.
it may not fix you completely, but it will restore most of the corruption, however we may need a 3 file firmware with PIT to fix the file system.
but we will cross that bridge when we need to

azzledazzle said:
i use 1.7 too, also running win 7 64 bit. no problems for me.
the firmware is a FULL FROYO including all dbdata's bootloaders, kernel the full monty
only insert the .tar file in the PDA section of odin.
it may not fix you completely, but it will restore most of the corruption, however we may need a 3 file firmware with PIT to fix the file system.
but we will cross that bridge when we need to
Click to expand...
Click to collapse
Ahh okay.
At the moment, I'm getting a "USB Device Not Recognized" notice with plugging it in..

right ok........
do you have kies installed on your PC ?? if you do uninstall it, and then re install it, this will re-install the drivers,
if you dont have kies, try this http://forum.xda-developers.com/showthread.php?t=728929
Finally, when you are about to flash using odin MAKE SURE KIES IS **NOT** RUNNING, EVEN IN THE ICON TRAY.

azzledazzle said:
right ok........
do you have kies installed on your PC ?? if you do uninstall it, and then re install it, this will re-install the drivers,
if you dont have kies, try this http://forum.xda-developers.com/showthread.php?t=728929
Finally, when you are about to flash using odin MAKE SURE KIES IS **NOT** RUNNING, EVEN IN THE ICON TRAY.
Click to expand...
Click to collapse
Nah I don't have kies.... I installed the drivers itself instead. hmm hah.