Database Info

I bricked my phone!!!!!!

HELP! I was trying to frehsly install a rom..
so i used odin to "master clear" everything
it deleted everything!
hoping that in recovery mode, it'll let me "mount storage" so i can transfer my new rom into the phone, that didnt happen!!!
so, then i tried to go with odin 1 click to install i896 stock...
and it doesnt work , so i unplugged phone, and now i get that mobile phone error..
please help, the only thing i can do successfully do is put my phone in download mode! D:
PLEASE! PLEASE!
THANK YOU!

Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Sent from my SAMSUNG-SGH-I897 using XDA App

Read carefully.....
ags on board said:
Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Click to expand...
Click to collapse
+1
Go into the ODIN thread and read extensively. Since you can get into download mode, make sure that once you connect your phone you get the COM notification in ODIN. Mine always appears in the small box in the upper left portion of ODIN one-click (if you don't get this, reinstall the samsung drivers found in the ODIN thread and reboot. If you're running Win7, make sure you run ODIN as admin).
Master Clear does exactly what it says...it wipes all of your data. MC is only supposed to be used when your phone is on and fully booted up with USB debugging on.
Flashing back to stock should only take ~5 minutes max - if it halts unplug, pull your battery, wait a few seconds, and restart. If it continues to fail, try a different USB port. If using a PC, use the back USB ports. If it still fails, try a different system. (I had this issue this weekend and finally got it on the first run on my friend's laptop - not sure what happened, had flashed 5-6 times on mine previously).
Hope this helps. Once you're back to stock, be sure to thank designgears for his killer dev work!
EDIT:
PS It's pretty tough to brick a cappy - read extensively in the ODIN thread and you'll see what I mean.

Its always good practice to back everything up and know the step by step procedures before you ever do anything. Good luck!

Connexxions "how to" videos are VERY detailed and shows you step by step how to do just about everything on this phone. I highly recommend them.

don't panic, ur lucky that u can still get into download mode. that is just soft brick I think..
Sent from my SAMSUNG-SGH-I897 using XDA App

Bricked, need help.

So, I bricked my Infuse last night at work when I tried installing MIUI from ROM Manager. I've been trying to unbrick using gtg's Ultimate Unbrick method, but no luck. I believe it's something to do with the Samsung Drivers since my phone is not recognized in Odin. Tried to redownload the Drivers from Samsung's website, but still doesn't work.
Any ideas?
BTW, running Windows 7 32bit

why would you install a rom that's for a different phone?
can you boot into recovery mode? did you try the "jig"?

Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.

the reason other roms pop up in rom manager is because you are using the galaxy recovery. unless it says "for infuse" (there is only one, gtg's rom) it wont work. bummer dude. im all out of ideas, never had this happen. hopefully someone who's been through this can chime in and provide some info that will help you.
on a side note, why cant you take it to an att branch and have them exchange it for you?

Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
I hope u have USB debugging turned on. If yes, u cud try this:
1. Download and install android SDK (search google for this if don't know how to).
2. Open a command prompt
3. Type in "adb reboot recovery" without quotes, and don't hit enter
4. Connect phone to PC
5. Turn the phone on
6. Wait for "samsung" to appear, and hit enter in command prompt
7. If it says "device not found", use the up arrow to get the command from history, and hit enter again. At some point, it should issue the command to the device.
8. If u can get to recovery, well, u have a way to now try to flash any other ROM.
Don't give up. Samsung has strong phones that could be got out of soft bricks most of the time.

Delete/reinstall the drivers.
Infuse 4G

Just tried Diablo's method, and it tells me command not recognized...

Download Kies on your pc to have it recognize ur phone. Run odin. Put ur phone in download mode (pull out battery, put it back in, hold both volume buttons down, plug in ur usb) and use gtg's unbrick.
Sent from my SAMSUNG-SGH-I997 using XDA App

Tried Kies before and it would never recognize the Infuse. Should I pick Galaxy?

UPDATE!!
Redownloaded Kies and installed the drivers (for the 500th or so time) and now Odin is recognizing a device. It's showing [COM3] instead of COM## but I'm letting Odin do its thing. Seems to be working... Crossing my fingers!
EDIT::
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
****in A! Thanks for the help guys!

Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251

Misterjunky said:
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251
Click to expand...
Click to collapse
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D

Pat713 said:
Just tried Diablo's method, and it tells me command not recognized...
Click to expand...
Click to collapse
That means u do not have android toolkit installed on ur system. You should install it first for the adb commands to work.
I would recommend downloading and learning the basics of adb. This could be a life saver in many no-so-happy situations.

Pat713 said:
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D
Click to expand...
Click to collapse
Had this same problem and it turned out to be a hardware problem. There was no gix for it. Also youll notice that gtgs recovery includes a preroot. If you need to send your phonr back like i did youll need to get that off. It was tricky for me because the hardware was so screwey. I got it off after a few reboots of the phone and a couple of trys with superoneclick.
Sent from my SAMSUNG-SGH-I997 using XDA App

[Q] Another Brick Thread - Not recognized by ODIN/ADB??

Hey everyone, I'm quite the lurker on these forums and don't post very often at all. I just want to first and foremost say that everyone here has been amazing and the work that has gone on for this phone is truly astonishing.
Now, with that being said... I'm bricked.
I was running CM7 today and decided (don't ask why) to try that ICS for the i9003. Dumb move. Hopefully someone is getting a laugh out of this as well.
I expected the results to be bad, but not disastrous. In the process of trying to do this I bricked the phone. When I had the ICS ROM on it, it got stuck on the AT&T screen. No worries, I made a back up this morning... I figured just pop back into recovery and restore myself back to normal and everything's fine.
Well, here's where it gets bad. I cannot get into recovery. After multiple attempts of trying to get into recovery. ADB nor Odin even see my phone in download mode. I do have a USB JTAG jig, which has saved me quite a few times.
I started downloading stock ROM's like crazy today. The only one that I could get to install was stock 2.3.5 with Boog's kernel with CWM. I booted into the OS and all seemed well at the time... except there's no modem! I have no internet, service, or anything. This is the only time ADB can see my phone, is when it's booted up. As soon as it's in download mode, ADB can no longer see my phone. The same with ODIN.
ODIN sees my phone when it's booted up, but doesn't actually make the handshake for an install of another version. I've tried to root it, in hopes of being able to push ROM Manager, Super User, and restore my back up in CWM. This didn't work either. During the rooting, using a one-click, it hangs up trying to run the psneuter exploit.
If I'm booted into this 2.3.5 stock of android with no modem, I tried to reboot into recovery using ADB running reboot recovery. This just boots the phone back into Android as if there's no recovery on the device at all.
Soon as I'm back in download mode I cannot push any files with ODIN or ADB. Neither one of them see my device at this point. Even using the JTAG jig.
This is where I'm now at. I'm not sure what else to try at this point. Is there a reason that my device is no longer being recognized in ADB when in download mode?
Any insight would be greatly appreciated. I've been trying to scour forums and search engines with no luck so far. This is my only phone, so it's a little depressing to be without any means of communication on the go, but that's the chance you take...right?
p.s. I do have all the Samsung USB drivers as I normally push files with ADB and have just done so earlier this week. Had the same luck on my computer at work today. So, I know it's not a PC related issue.
Thank you to everyone in advance.

I've also tried to push a modem to the phone with no luck.
I installed 2.3.5 with the Executable JAR of Heimdall AndroidOS 2.3.5 to push the files and that JAR version is the only device that will install to my phone and makes the handshake. Just no modem

You may want to give Heimdall a try - it installs its own USB drivers, so it's possible it might be able to see your phone that way. Nevermind - just saw your post. Which Heimdall did you grab?
Also try switching USB ports - sometimes a different port makes a difference.
There's a one-click in my signature if you need it.

I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
edit: Just to be sure I did try the one in your sig. It installs no problem, but ROM manager crashes and the screen distorts right before home screen loads. Once it's loaded it seems OK. Might be a boot loader issue.. but not sure. Once in download moad Odin3 doesn't recognize the device. The one click app does, but not Odin3 v. 1.3 to flash rooted kernel. It just doesn't recognize the device for some reason, but java installer still recognizes it.
I cannot get into CWM as it just crashes. Doesn't reinstall correctly, gets stuck on running privileged commands. Cannot boot into it since it's a privileged command as well. Only version of odin that recognizes my phone is the one in your link and it's a JAR Exe lol. This is the strange part.. no modem. Just got the wifi to work to at least make it to the market place. Still no modem, broadband is 'unknown'.
When I go back into download mode to flash a kernel in Odin v1.3 it doesn't recognize my device. ADB does not recognize my device. The java installer for the stock rom I just used in your sig still recognizes the device. Only the java installer recognizes it. Tried using Heimdall 1.1 for the kernel flash and it also does not recognize my phone.

I do have an HP TouchPad running CM7 alpha 2.1 as well. Not sure if this will help, unless someone can think of something clever by having an extra Android device. Just throwing it out there.

sunfirex said:
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
Click to expand...
Click to collapse
As far as I know, that should have CWM installed in the file. Depending on which bootloaders you have, either holding V+ and Power from a powered-off state, or V+/V-/Power should put you straight into CWM.
If that isn't working for you, but you're at least on a Gingerbread rom, try this. It appears Heimdall is ok with your phone, and this kernel I'm certain has CWM baked in. You might bootloop, but you should definitely get to CWM from this.

That's exactly what it was. That version of Heimdall in the link you provided solved my issue.
Thank you so much!

Glad to hear it.

[Q] Tried Heimdall One-Click. Never finished, now USB won't recognize. Bricked phone?

I was previously running MIUI (not sure which version) and something went wrong with it. Random processes just kept "unexpectedly stopping." I found the Heimdall One-Click and tried it. The process never finished (failed to upload FACTORYFS everytime :/). I tried checking the Flash Bootloaders option. It got the FACTORYFS upload percent a bit further along, but still failed. Opened up Odin, and it wouldn't find any device plugged in.
After a couple more tries at this, suddenly, no matter which USB port I plug in to, my computer fails to recognize the device when previously it would on a couple specific ports. Odin will not recognize it, either.
Am I screwed?
Edit:
I've gotten the USB to recognize. I'm scared to do anything now, for fear I won't get it to recognize again. Odin still does not see the device. What other tools can I use to unbrick this?

I believe the driver for heimdall "takes over" the port. You have to use a different port or uninstall the driver to use Odin on it again. Also it seems when the upload won't complete most have success with another cable....nothing wrong with qksters uclb3 return to stock. I've used it several times.
Sent from my SGH-I897 using Tapatalk

I had the same issue a few days ago. SCARED me to...
Powered the phone off.
Unpluged USB
Rebooted Windows PC
Rebooted phone
Started at step one again
This time try another USB Port on computer
This time everything worked

I've had this happen before. After much panicking, I used GTG unbrick.
Thread located here → http://forum.xda-developers.com/showthread.php?t=1116251
download is here → http://www.mediafire.com/?i57410xodydx5l1
Follow it verbatim. Worked like a charm!

unistall
i had the same thing happen the other day i opened device manager and unistalled the driver for the phone then pluged the phone back in let it reistall and away i went may have to reistall drivers from kies

All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.

AdamOutler said:
All you need to do is install Samsung drivers again or switch USB ports. The LibUSB Zadig drivers are installed on a single USB port. No need to uninstall anything at all. Heimdall drivers are only installed to the USB port you had the device plugged into when you installed the drivers.
A better option would be to dual boot into Linux and One-Click just works every time.
It sounds like you are using a bad cable. Try using Heimdall one-click with a good cable. It works every time.
Click to expand...
Click to collapse
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux

cobraa783 said:
That works if you don't have to jumble things around to switch USB ports and/or your computer is set up for dual boot the other option would be to run a virtual disk that runs linux
Click to expand...
Click to collapse
No. The device is controlled by windows in a virtual machine.

AdamOutler said:
No. The device is controlled by windows in a virtual machine.
Click to expand...
Click to collapse
Actually ur windows didn't even need drivers for the device ur using in a vm

cobraa783 said:
Actually ur windows didn't even need drivers for the device ur using in a vm
Click to expand...
Click to collapse
It does. Otherwise it will be an unrecognized device and you can't connect it to the VM.

just wanted to chime in here and verify. had a similar problem with odin not working after using heimdall.. used another usb port and odin now sees my infuse.. no problems. thanks guys

Also, wanna say that, for some reason, I had better luck using different version of Odin. Can't remember exactly but I think 1.7 worked & 1.8 didn't - not at PC right now to verify.
Sent from my SAMSUNG-SGH-I997 using XDA

once you install zadig...driver installation for heimdall, it takes over that 1 port.
you can always go back to that 1 port or designate it for heimdall.
odin will not be usable for that port unless you re install samsung drivers again.
I have an (old -6yrs) pc with 1 usb same cord ($1) and 1 usb back port...same 1 for 6 months with heimdall - never had to mess with anything else...successful restore everytime...
use what you're comfortable with.
save that 1 configuration as your rescue if possible.

This topic was as close as I could find to my issue... Heimdall One-Click Kernel...
First of all, let me say that I appreciate all the work everyone has done on the Infuse forums. It has expanded my knowledge by leaps and bounds just by reading for about 5 hours today. I know this will be a long post, and I apologize. I am just trying to show that I have done everything (so far) that is within my ability to try.
I inherited a "mostly working" (sound doesn't work at all) AT&T Infuse 4G, and am trying to install CWM and root the bugger in order to use it on WiFi as a mini tablet. I Do Not have a SIM card for it (I am on SIMple Mobile, not AT&T), and do not plan to use it for calls (already have a phone for that). It was already running UCLB3, but I wasn't sure if that was how the phone came, or if it had been upgraded from Froyo at some point with or without the bootloaders. I had planned to play with this phone some and maybe try out some Jelly Bean since my T-Mobile G2x has lost most of the wonderful devs that it had.
First, I used the Settings>Privacy>Factory Data Reset to clear all the information on my phone and my internal SD card. I made sure that Java was the latest version on my laptop and DL'd qkster's [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3. I spent the next 2 hours reading and re-reading the OP and all the resulting posts to make sure I had a firm grasp on how to do everything. I first booted into stock Recovery and did another Factory Reset from there and also cleared Cache. I booted into Download mode on the Infuse 4G and ran Heimdall One-Click. Installed the Heimdall driver, closed all programs, rebooted the computer, went back into Heimdall One-Click, put the phone back into Download mode, clicked Flash, waited for phone to reboot, turned phone off, went back into Download mode and flashed again, this time with BL checked.
This entire process went off without a hitch. Phone boots into GB and all is glittery gold. It's when I come to the next step in the thread that I started having the issue. Again, from an overabundance of caution, I made sure that I read the thread again, absorbing all the information pertinent to loading the Kernels from One-Click. Deciding to try InfuZen-A16 Kernel, I downloaded it and ran it just as I had the previous One-Click. Opened the .jar, booted the phone to Download mode, clicked Flash, and let the phone reboot. Uh oh. Samsung splash screen is staying on my screen now...
Maybe it just needs a while to process. Left the phone plugged in so it wouldn't lose too much battery life and went and did some more reading on the forums. 5 minutes, still Samsung screen. 10 minutes, still Samsung... No biggie, I'll just read some more. Maybe this is just a longer process than I thought. 30 minutes later, still Samsung. Okay, something must be wrong... Hold down power button to shut it off. 3 minutes holding button, still on. Battery pull...
3-button workout for recovery... Nope, no such luck, still showing the persistent Samsung screen. Back to Heimdall One-Click for recovery to UCBL3. That works. Back into stock recovery. Again, Factory Reset, clear Cache. Download mode, try again. Flash InfuZen-A16 Kernel a couple more times (flashing back to Stock between attempts), using a different USB cable and different USB ports, but still same thing each time, leaving the phone for at least 15 minutes on the Samsung splash screen to see if it moves anywhere. I then tried the ENTROPY512's 4.4.2012 kernel, hoping for different results. Same thing. Tried it 2 more times with different cables and different ports. Each time that I flashed back to Stock, it worked on each USB port and cable I was trying, so I don't "think" it could be the cables or the ports that are causing the issue.
Any help is greatly appreciated. It is my understanding that to get root on UCLB3 and above, I need to have CWM installed, but other than Heimdall One-Click Kernels, the only way to get CWM on a phone is by having it already Rooted. If I am erroneous in this understanding, please point it out and I will happily do my due diligence to fix my own problem.
Thanks in advance for any help anyone gives me.

The custom GB kernels for infuse start a file system conversion immediately upon reboot (from rfs to ext4). If your sound was working, you would hear a robotic female voice providing status updates. This process typically takes no more than 20 minutes to complete, usually less.
If the phone is just sitting there at a samsung logo, try leaving it longer to see if it completes and boots the phone OS.
If it still doesn't work, try the jscott30 Odin package instead:
http://forum.xda-developers.com/showthread.php?p=27286083
Here are the custom kernels in Odin packages:
http://forum.xda-developers.com/showthread.php?t=1698367
IMPORTANT: If you try Odin, use a different USB port than the one you set up for Heimdall. Reserve the Heimdall port for only Heimdall flashing.
For Heimdall, make sure you are using this one (kernels in posts 2 & 3):
http://forum.xda-developers.com/showthread.php?t=1524081
(looks like you are based on the files you referenced above)
Regardless, make sure your USB connection is 100% reliable and you do not interrupt the flashing process - otherwise you may brick the phone.

Thanks for the reply, Zen. I'll try it again when I get home and just let it run for at least an hour.
I have a minor aversion to using Odin, just because it is closed source as opposed to open source for Heimdall. I will take it under advisement, though.
Thanks for all the words of wisdom you give to all the members of xda. :thumbup:
*edit* - Well, decided to just let it ride for over an hour. Took an extended nap after I got home, so after flashing, the phone has been on the Samsung screen for well over 3 hours. I am going to presume that the Heimdall kernel install packages are a no go for me. I will read up on Odin and give it a shot. Thanks again. - *edit*
Sent from my LG-P999 using xda app-developers app

Do you think these problems are more likely hardware or software?

Hey guys,
I've got a Galaxy S 4G currently running the CM 9 build Release 8 (from August) and here are the problems I'm experiencing:
- random failure to reconnect to the phone network after I've been in the subway (have to reboot)
- just plain random reboots, though they're rare
The lack of reconnectivity is driving me up the wall. How likely is it that this problem is just with the OS? I don't want to have to get a new phone but maybe I've dropped this one too may times. :silly:

You might try a different modem to see if reconnecting works better or put airplane mode in you status bar toggles and toggle it off/on when you get off the subway for a fresh connection.

Thank you, lumin!
edited: I'll direct other questions to the CM9 thread.

Sorry guys, returning to this thread rather than clogging up the Heimdall thread or the CM9 thread.
I'm having a very basic problem and am feeling very stupid and very frustrated. I can't get Heimdall to recognize my phone.
Last attempt steps I took:
- Installed Win64 Samsung drivers
- Rebooted PC
- Connected phone to computer when in each of regular, recovery, and download mode.
- Ran Zadig as administrator and selected List All Devices
- Phone does not show up as Samsung anything, just as Gadget Serial
- Hit Install Driver (Note: this has never changed to "Reinstall Driver" or anything
- Ran Heimdall as admin
- Doing a test for compatible devices turns up nothing.

Use the Odin one click here http://forum.xda-developers.com/showthread.php?t=1500427
Use a different USB port and you should be fine
Sent from my SGH-T959V using xda app-developers app

Additionally, installing the official drivers will make the phone not connect if you're using one of the MTD (ICS/JB/newer-CM7) roms. Since they use the generic Google Android driver rather than the Samsung one.
Another thing is, zadig includes (for me) 3 or 4 different driver options, and only one of them actually works. For me, that's WinUSB. For you, might be something else. But try installing one, rebooting the computer, restarting the phone, and seeing if it works. Then move on to the next one. Once you figure out what works for you, write it down somewhere and use it for the future.

Thanks, I'll give that a shot.

Theraze said:
Additionally, installing the official drivers will make the phone not connect if you're using one of the MTD (ICS/JB/newer-CM7) roms. Since they use the generic Google Android driver rather than the Samsung one.
Click to expand...
Click to collapse
Can you elaborate on that for me? By connect, what do you mean? Connect to the computer?
P.S. is this the driver you're referring to? So I should be using this and not the Samsung one?
http://developer.android.com/sdk/win-usb.html

I meant that uninstalling the Kies/official drivers, rebooting, and only using the zadig drivers is likely to give you better results if you're using newer roms. Since the Kies drivers are only helpful if you're on GB and can only cause you problems otherwise.
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works. If not, run zadig, list all devices, select the phone, install libusbK driver, reboot, unplug, reboot phone into download, plug back in, check if flashing works. Repeat with libusb0 if needed.

Theraze said:
I meant that uninstalling the Kies/official drivers, rebooting, and only using the zadig drivers is likely to give you better results if you're using newer roms. Since the Kies drivers are only helpful if you're on GB and can only cause you problems otherwise.
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works. If not, run zadig, list all devices, select the phone, install libusbK driver, reboot, unplug, reboot phone into download, plug back in, check if flashing works. Repeat with libusb0 if needed.
Click to expand...
Click to collapse
Aaaaahhh. Ok, I'll try that.

Oh, and when having zadig/driver issues... always try to flash twice. And when it gives you an error, after the second failed flash, reboot the phone and flash again. Then move on to the next driver/attempt.
When this phone gets finicky, you need to get the yellow-caution flash screen to bypass its paranoia about your flashing.

Theraze said:
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works
Click to expand...
Click to collapse
Ok, one question about this:
- you've plugged the phone in while it's in download mode
- then in the second sentence you wrote "REBOOT phone into download mode" but the phone was in download mode before, so was a reboot actually necessary?
edit: And, I haven't actually tried flashing at all in Heimdall, I've just been checking to see if it sees a compatible device. Would you suggest I just try to go ahead with the flash, with each driver? (I'm not sure if I've seen the option to select anything more than Windows USB, but at least with that?)

Specially, shut down the phone and boot into download mode again. Easiest way to do it is probably to unplug USB, pull the battery, plug in USB, put the battery back in, etc... Guarantees that you've got your full phone-reboot cycle.
And regarding alternate drivers, there's a little up-down arrow next to the driver name. Click that to override the current best-driver-guess and manually pick your choice.

Damn, there's a bunch of reboots I was missing... I really hope I haven't screwed anything up permanently.

Theraze said:
And regarding alternate drivers, there's a little up-down arrow next to the driver name. Click that to override the current best-driver-guess and manually pick your choice.
Click to expand...
Click to collapse
Yeah.......... I don't have that. I looked again, it's not there.
edit: it would appear that Heimdall 1.3.1 came with Zadig 1.0 only... I just grabbed 2.0 from github.

Personally, I'm using Heimdall 1.3.2 and that's been working fine for me. But some people have issues with that one, so... no comments/complaints about Heimdall 2.0 RC1 yet on his site.

Theraze, if you could speak more specifically about one point here: all I have been doing is changing drivers (I've just tried all three) and then I've used Heimdall's Detect Device utility to try to detect the phone. Which has failed.
You have repeatedly said "try flashing". Do you think that can work even if Detect Device isn't working? I got the impression that was dangerous.
edit: well that's obviously what you're suggesting, but - how safe is this? Perfectly? Mostly?

If it doesn't see your phone, it won't flash. If it does, it should work or at least do... something. At which point, it probably hit the half-flash yellow screen I get every time I use Heimdall to flash a new kernel.
That's basically how complicated as I see this... Regardless of how well the detection tool is working, if it actually succeeds...
The 959V is nifty in that it's ALMOST impossible to hard-brick. If you're flashing bootloaders and pull the cord there, maybe... but if you screw up the kernel or one of the other things that make normal phones into depressing paperweight reminders, it just means reboot and flash again.

Thanks, man. Going to try flashing now.

Zilch. Can't see the phone with any of the three drivers.
Starting to give up hope of fixing this, honestly.