Database Info

anyone else having problems with 64bit galaxy S drivers?

I did the one click root with no problem, now can't do the clockwork mod because the drivers keep failng , even tried the root again and it won't work either because of the drivers. I can get it to sync like 1 in 10 times, verified because I can get adb shell working. but it seems if I try to do anything, the drivers basically reset themselves. i didn't have this problem previously, although i did have to reinstall the drivers everytime, now that isn't even working, has anyone got this working correctly? I only have windows 64 bit machines.
EDIT: if someone could post a link to drivers that are known to be working, that would be appreciated, then at least I know I'm using ones that are working for people.

What version of windows are you running?
does it give you any errors, or does it just not regonize it? Maybe an issue with driver signing.
Sent from my SPH-D700 using XDA App

windows 7 ultimate 64 bit. the device manager usually shows errors, i show a bunch of drives listed, after a few tries of deleting the J drive, I get it to show up as wpd file or something like that, then it works for a minute or so, it will let me into adb shell and I can do SU, but if i try adb push, it hangs. same thing when trying to do the 1 click scripts, I know if its working or not, because if it isn't working, the script just hangs, then 10 tries of unplugging and plugging in and it finally connects and runs the scrips although giving errors and such, I did root just fine using the scripts, so I'm not sure whats going on with these drivers. maybe if I knew which things to uninstall from the device manager, i could start from scratch, using back usb port, front usb port, makes no difference. i'm gonna wear out the micro usb port if I keep plugging and unplugging the phone like this.

Hmm it sounds to me that finding the associated driver files in the registry/file system and clearing them. Rebooting. And reinstall of driver would be the best plan of action.
In device manager you should notice a new driver pop up when you plug in your phone. From there you could uninstall the driver, but be aware if you just uninstall the driver without removing the driver files 7 will auto find them and reinstall them when it sees your device.
Without being able to look specifaclly at the computer its hard for me to tell if its a corupt/broken driver causing the problem. There could be a few things doing it.
Sent from my SPH-D700 using XDA App

is there a way to clean everything out? like what things in device manager would I clean out? I can't seem to find them all.
Nanncee said:
Hmm it sounds to me that finding the associated driver files in the registry/file system and clearing them. Rebooting. And reinstall of driver would be the best plan of action.
In device manager you should notice a new driver pop up when you plug in your phone. From there you could uninstall the driver, but be aware if you just uninstall the driver without removing the driver files 7 will auto find them and reinstall them when it sees your device.
Without being able to look specifaclly at the computer its hard for me to tell if its a corupt/broken driver causing the problem. There could be a few things doing it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse

It's not so much in device manager that your looking to remove it. Usually when a driver is installed, it places a directory on your c drive with all the files needed. now those files could be located in /windows or /program folders, or they could be in their own folder for titled samsung for example. (this usually isn't the case for storage drivers like we are dealing with)
I am not sure how samsung wrote their driver package, but you may be able to run it again and have it remove the files for you. I would verify on a windows system, but I don't have one running right now. You may also be able to use the driver installer to follow the path to where it places the files. again it all comes down to how the driver installer was written.
also just thought of this, and it is a long shot, but verify that you don't have an antivirus/firewall blocking the connection.
I don't know if you have another computer, if you do I would try it on that system as well.
Sorry I can't be more definitive on where to remove them. But without a windows system I hate to send you looking in the wrong spot and deleting things that shouldn't be.

http://www.nirsoft.net/utils/usb_devices_view.html this program will let you wipe any usb device from the history... worth a shot/try a different port

On 64-bit Windows, you'll probably need to manually set the driver for the ADB composite device. Just do update driver from the device manager, browse for drivers and hit let me pick from device drivers on my system.
Worked for me anyway.
But it sounds to me like your problem is not driver related. Try another USB cable. The stock one is pretty poor. My first Epic's had this problem, so I got another cable and it magically started working again. Also, front USB ports are more finicky, so you could try the back ones.

Linux FTW.

I never got the most recent clockwordmod one click method to work, I always have to use 2.5.0.9, then do the update.zip method for 2.5.1.0., I tried on both of my laptops, one running 7U64, the other running 7U32.

did this and tried two cables from both of our epics, also, it worked fine to do the clockwork mod. used front and back usb ports. no luck.
Firon said:
On 64-bit Windows, you'll probably need to manually set the driver for the ADB composite device. Just do update driver from the device manager, browse for drivers and hit let me pick from device drivers on my system.
Worked for me anyway.
But it sounds to me like your problem is not driver related. Try another USB cable. The stock one is pretty poor. My first Epic's had this problem, so I got another cable and it magically started working again. Also, front USB ports are more finicky, so you could try the back ones.
Click to expand...
Click to collapse

Try a NON Samsung cable. Not one from another Epic box.

i finally got it to work, used the wifes laptop, something apparently is screwed up on my machine. wish I knew what.

robl45 said:
i finally got it to work, used the wifes laptop, something apparently is screwed up on my machine. wish I knew what.
Click to expand...
Click to collapse
Glad to hear you got it solved. As to whats wrong with your computer, I have no clue. Good luck though. If all else fails, wipe and reinstalls are your friend.
Sent from my SPH-D700 using XDA App

robl45 said:
EDIT: if someone could post a link to drivers that are known to be working, that would be appreciated, then at least I know I'm using ones that are working for people.
Click to expand...
Click to collapse
.....
I have had many problems with drivers on my windows 7 64 bit machine.
To get the epic drivers to work I had to uninstall all other samsung phone drivers first. Download the x64 drivers from that post, upzip.
Plug your epic in mount it. Open the device manager and manually point it at the unrecognized device at that folder. I had to do this for 3 or 4 separate entry's.
Play with it a bit and you should be able to get it working with those.
Hope this helps.
Bah new user bs. Cannt post the link. Go over to SDX developers epic development section. There is a sticky "Confirmed Working Drivers"

I said screw it with the Samsung Drivers. Just installed PDAnet when I got this computer a week ago and no issues (win7 home 64-bit). It asks during setup what phone drivers you want to install. Select Samsung, let it do its thing, and you're all set. ADB works flawlessly, no need to mount sd card to get it to work.

USB unknown device

I've tried the drivers from Samsung, Keis, ODIN one click. None of them worked on 4 different machines, Windows 7 both x64 and x86(which was a fresh install), and two Windows XP machines. I tried it on Ubuntu(10.04 LTS) and that recognized the captivate.
Anyone know how to get one of those to correctly recognize my Captivate so I don't stuck on Samsung's/AT&T's 2.2

uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers

What is it that you're trying to do?
Sent from my SAMSUNG-SGH-I897 using XDA App

If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.

Samsung really failed at the USB drivers for the Captivate. I would expect to be able to install the drivers from their website. Plug in my phone, and have it working.
trell959 said:
uninstall all of the driver that you downloaded. uninstall kies. then go to samsung.com search for the captivate, choose you phone, click the 'i own this' button. then go to get downloads, software. click on the .zip file icon next to usb drivers. if that didnt work uninstall them then download kies again. if it still doesn't install them, open kies, click menu, reinstall drivers
Click to expand...
Click to collapse
I tried that before, didn't work.
bornjamerican said:
What is it that you're trying to do?
Click to expand...
Click to collapse
I'm trying to:
1) connect as a mass storage devices. Yes I know turn on USB debugging and to mount the drive.
2) flash back to stock 2.1 or root my phone so I can install a custom ROM on it. Might go with CM7/MiUi or something from Team Phoenix. So use Odin3
shinji257 said:
If it is coming up unknown device try another port. You may want to try another microusb cable as well.
Click to expand...
Click to collapse
Tried all of the ports on the computers. I don't have another microusb cable to test to see if that's the problem, but I'll check that tomorrow.
Johnnie5000 said:
I've always had luck with the drivers in the captivate aio toolbox. Even on a fresh win7 64bit when I replaced my boot drive with a ssd a month ago.
Click to expand...
Click to collapse
I'm going to try a fresh install of windows 7 32-bit with aio toolbox see if that works.
Tried my friends brand new microUSB cable. It worked.

I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.

rmriggin said:
I have tried 4 known good cables know, 4 different computers and every USB port available on all 4 of the PCs I tried. Only once did it identify the device and install the drivers and I was able to root it but I still can't sideload because after the reboot after rooting it is back to device not recognized/unknown device. This has been a total pain. Any suggestions? I'm not with AT&T any more so I am out of luck for just bringing it into a store and asking them to take care of it.
Edit: Sorry for bumping an older post but I did it instead of starting a new thread.
Click to expand...
Click to collapse
If you're just trying to transfer apk files to it for sideloading, you can use a wifi transfer app. I use Wifi File Explorer and it's great. You can connect to your phone via web browser and upload/download anything on the SD card.
Another option is to use an external SD card that you can remove and plug into your computer, transfer the files to it, then insert it back into the phone.
This won't work for connecting to PC apps like Odin, Heimdall, or Kies, but for simple file transfers it works like a charm.
Additionally, regarding other usb cables, you didn't mention what types of cables you used, so I'll throw in another thought. The cables that come with the Captivate don't work on some PCs (like my new iMac). Third-party, generic usb cables might not work, either (I tried some and got a whole lot of fail). The only cable that works for me is the one that came with my wife's Motorola phone. If you haven't tried one yet, I would recommend getting your hands on a Motorola cable and testing it out. You'll immediately notice the cable is much thicker. I don't know if that has anything to do with why it works when others don't, but there's something about that cable that others don't have.

Bad Phone?
Could it be the phone port is having issues?
I've had the same problem and it seems that the port on the Captivate is shot which may be your issue. it will always charge; but tends to cause a lot of profanity when trying to get a PC connection to transfer files or flash it. It will be seen, then immediately play the 'unplugged' sound from windows. I've sat there and had it play the tones of plugged in and un plugged over and over again just by tilting the phone from side to side. No matter what cables I use (tried several but they are all samsung due to the recessed port). If it establishes the connection; I have to be very still with it or it'll lose it. If it loses it; I get unknown device messages or not functioning messages on that port until I reboot the PC.
Trying to flash anything via ODIN takes a lot of patience.
Those same cables / USB ports are used on my wife's Focus without ever having a problem. I wrote it off as too much flashing / overclocking of my phone but am not sure.

hi i was having this issue as well. i solved it by:
1. download a good & stable miui rom, rename it to update.zip and place it into your sd card. i took the sd card out of the phone and used a adapter to connect the sd card to my PC since i can't access my sd card through the usb port.
2. put the sd card back into my phone, turn off my phone. press and hold volume up and down buttons, then press n hold the power button till the screen shows something.
3. select install from sd. wait until the installation finishes and select reboot the phone.
4. when you're in your new miui rom, try to connect your phone to the pc via usb port again.
this worked like charm for me.
about the miui rom, i suggest you to use the one from miuiandroid.com (the UK version)
after flashing the rom im able to connect via usb and use mass storage.
hope this helps

Also, when you uninstall drivers, don't forget to look in the program files for anything that may have been left behind and delete it.

From the description it sounds strongly like you are actually experiencing a port failure which is common on the Galaxy S devices. PM me if you need this repaired...

Only try another usb cable, i bricked my cappy with a bad contact cable on odin, unknown device too, new cable=i897 device on windows notifications
try and feedback!

strange, this only happened to my when i soft bricked my phone. try connecting it to your computer in download mode

I had this issue once before. Here is what I did which resolved the problem. I was using a windows 7 PC
1. Download the ADB kit and extract it to C drive.
2. Connect your mobile to the PC on USB port
3. Wait for the drivers to be installed automatically (it might give you a failed to install message)
4. Never mind that message. Open Device Manager
5. In Device Manager, if you expand the "Universal Serial Bus Controllers", you'll see a device that has yellow question mark against it. This is your phone and since drivers are not installed properly, it has the question mark.
6. Right click that device, and select "Update Driver".
7. IN the window that comes up, select "I'll select a driver".
8. Browse to the folder where you have extracted the ADB kit on C drive
9. Check include subfolders and click Next.
10. The drivers should be be installed and your device should be identified by the computer.
Let me know if it works for you.

[Q] usb mounting issue on GB

ok I have searched, read and tried everything but I still can not get my phone to mount on a Windows 7 system. I am currently running 2.3.4 Bamf the newest preview. Can someone please post the drivers I need and a step by step if you have been able to get your to mount. I have been taking the card out and using a card reader to but my music on the phone but this is getting old.
Thanks,
Alan

AlanPototsky said:
ok I have searched, read and tried everything but I still can not get my phone to mount on a Windows 7 system. I am currently running 2.3.4 Bamf the newest preview. Can someone please post the drivers I need and a step by step if you have been able to get your to mount. I have been taking the card out and using a card reader to but my music on the phone but this is getting old.
Thanks,
Alan
Click to expand...
Click to collapse
Open your Device Manager on Windows and delete any Thunderbolt related devices that have a yellow exclamation mark. Re-plug in the device.

and or download htcsync off their website for the thunderbolt. that installs all necessary drivers

I have to download the HTC Sync drivers in order to get mine to work in Win7. The other issue is that on GB you can't or may not be able to go from charge to disk drive without first going to internet connection and then disk drive. That is a known issue.

Silvus said:
and or download htcsync off their website for the thunderbolt. that installs all necessary drivers
Click to expand...
Click to collapse
I have done this but I still can't get windows to "see" my phone. It worked on Froyo?

dpdurst said:
I have to download the HTC Sync drivers in order to get mine to work in Win7. The other issue is that on GB you can't or may not be able to go from charge to disk drive without first going to internet connection and then disk drive. That is a known issue.
Click to expand...
Click to collapse
I have tried this also with no luck.

droidisawesome said:
Open your Device Manager on Windows and delete any Thunderbolt related devices that have a yellow exclamation mark. Re-plug in the device.
Click to expand...
Click to collapse
I thought you might be on to something here but alas there where no problems but the only thing listed under Android phone is MyHTC?

OMG I just fixed it. The problem was in Device Manager! Thanks a lot!

I cannot get mine to connect either. Tried the devicemanger route with no luck, Also tried to re-install the HTC drivers, same result.

Unable to mount File System

I just flashed to Pinnacle 1.3( was on Fasty III before ) and I've noticed that with Gingerbread Roms, i just cant seem to be able to Mount the File system on my Windows 7 pc.
Using USB-Debugging mode, i connect my Capy to my pc and then mount the file system, but it doesnt show up in my PC
i also tried directly mounting it as Mass Storage, again not showing up!
Tried all USB Ports, Different Cable etc etc
Weird thing is, when i flash back to Stock using Odin 1 click, ie when im on JF6, I am able to Mount the File system!!!
Another Weird thing is, that i am able to Mount my phone ( with Pinnacle or Fasty) on my friends PC, by installing the same drivers that i have for my PC
whats Wrong? I have also uninstalled all drivers and re installed them, used driver cleaners etc

Never had that problem on win 7. Don't know what to tell you.

Are you using the correct drivers?

Yea!! i am...i really dont know whats the problem! and i dont wanna format the whole thing!
Im using the drivers mentioned in the Sticky Threads...ODIN 1 click thread to be precise

neo_31591 said:
Yea!! i am...i really dont know whats the problem! and i dont wanna format the whole thing!
Im using the drivers mentioned in the Sticky Threads...ODIN 1 click thread to be precise
Click to expand...
Click to collapse
When you say you tried another cable, do you mean another SAMSUNG cable or something else? The problem you describe is very often attributable to the cable. The Samsung cable that came with my Cappy worked just fine with my old computer (PowerMac G5), but refused to work with my new iMac.
I tried also using a RocketFish micro USB cable, and had zero luck with that.
After much screwing around and swearing, I tried using my wife's MOTOROLA cable, and the computer recognized the phone with that.
I'm nothing close to an expert on electronics, but I suspect it has something to do with voltages on different computers.
I suggest trying to get your hands on a Motorola cable and seeing if that fixes it. Perhaps the Gingerbread ROMs have different voltage settings? Dunno...but try a Motorola cable.

hmmmm, i just tried a micro usb cable from a blackberry....ill try out the Motorola one....thanks for the suggestion

neo_31591 said:
hmmmm, i just tried a micro usb cable from a blackberry....ill try out the Motorola one....thanks for the suggestion
Click to expand...
Click to collapse
You may have another option, too...at least for transferring files. I've been using an app called WiFi File Explorer PRO for several weeks, and I love it. You can connect to the phone via WiFi (if you have it available) and transfer files back and forth just using a web browser on your computer.
https://market.android.com/details?id=com.dooblou.WiFiFileExplorerPRO&feature=more_from_developer
Since I started using this app, I haven't needed to futz with a cable at all. It obviously won't help you with Odin, Heimdall, or any one-click utilities that require you to be connected via USB, but it will help you get files on your phone for flashing with CWM.
Not sure if it's an option for you, but it might help alleviate some of your issue.

Great Suggestion and seems very handy...thanks a lot!

[Q] SK4G not being recognized on PC

I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.

What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.

Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA

Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.

I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.

I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.

More info request.
Can you provide us with the names and links to the drivers you have tried?

DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.

Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.

DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.

Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.

Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?

Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...

Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?

DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.