For those of you who have had trouble with getting the drivers for the Infuse, download this:
[Im new so cant post a link, but goto softpedia.com and search kies. The only kies program available will appear, and download and install that]
It wont recognize your phone, but after you install the program, the appropriate drivers will be present, and the root with SuperOneClick will work immediately.
*remember, the program wont recognize your phone if its plugged in, but that doesn't matter. It will just install the appropriate Samsung_Android drivers your PC needs to recognize the phone in SuperOneClick.
Hope this helps!
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
pvillasuso said:
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
Click to expand...
Click to collapse
404 Page Not Found
The page you requested was not found.
http://forum.xda-developers.com/showpost.php?p=13895587&postcount=7
posted here.
Phone doesn't exist on my PC.
Nope. Bought the infuse on day one. Installed Kies 2.0.0.11044_11_3. Phone not recognized, installed drivers, learned the truth about Kies. Phone would not be recognized but at least installing Kies made the phone visible to the PC, so I knew I could root if I so desired, read up about rooting and thought I was ready. The phone had other plans.
Decided the other day that I was ready to root. Plugged in the phone but it no longer showed up in Windows. Something about the phones compatibility with my system changed. Tried to install this Kies 2.2.1.11053_99_3 yesterday, reinstalled drivers, activated USB debugging, plugged the phone in started up SuperOneClick and . . . still nothing happened. So I deactivated USB debugging and started over. Followed all the directions in the root posts and and SuperOneClick threads . . .
But somehow between day one and today my Windows 7 64 bit system does not know that the phone is plugged into it.
When I plug the phone into USB the phone asks me how I want to interact with the computer, Kies (Firmware Update); Media player: Mass storage. But the computer shows nothing. Device Manager doesn't list the phone, Windows Explorer doesn't show the phone, Devices and Printers window shows everything that's connected but NOT the phone, it's as if I plugged nothing into the computer. The phone is charging so I know that it's plugged in, but it doesn't seem to be communicating with the PC. I've re-booted, re-installed, reviewed, rewired and re-alized that I have no clue what happened. (Tried different cables, different USB ports different times of the day)
It worked once upon a time, I tried rolling back restore points and disabling my kaspersky 2011, I've followed all rooting instructions in these threads to no avail.
I am now ready to hurl my phone out into traffic to see if that will help, but before I do I'm hoping someone here may have the answer I need.
. . . please . . .
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
For me, one of the SuperOneClick packages included Windows drivers.
Which is great since SOC is the only reason I needed Windows drivers. (SOC never works in Linux for me for whatever reason...)
All android phones are supported in linux natively.......jus t saying
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Well yeah - I've never had to install any drivers for ADB or anything else.
However, for whatever reason, superoneclick and Linux don't get along for me. So the only time I ever have to install drivers is when SOC rooting from Windows.
superweapons said:
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
Click to expand...
Click to collapse
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
menzoom said:
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
Click to expand...
Click to collapse
I've tried just about everything too, and nothing works to get my 64 bit Windows 7 PC to recognize the Infuse. Finally resorted to AndroidSync for file transfers, which worked fine, but it just makes me angry that I can't make the darn thing connect via USB.
http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT
And select SOFTWARE
Tried that last week. Didn't work for me. The PC does see the device, but never finds any files on it.
Drivers in that link
I was having the same issue mentioned yesterday after loading the Samsung Infuse drivers, where my PC still couldn't see the data on my phone. (I'm also running 64-bit Windows 7 OS.)
Once I loaded the drivers and plugged in my phone, I got the happy little "device drivers installed properly" message and thought I was good to go. Nope. No drives mounted and visible in Explorer.
Under Devices and Printers, I could see SAMSUNG_Android with the unhappy yellow exclamation point. The troubleshooting report just says "Problems with PnP devices."
So I dug into into Device Manager. Under Portable Devices, there were 2 new WPD FileSystem Volume Drivers. Both had the same yellow exclamation points and showed a Device Status of "This device cannot start. (Code 10)."
It turns out Windows 7 wasn't assigning drive letters to the new Android volumes. It creates two disk drives (one with pictures, videos, and ringtones and the other with music, external SD, and media). If you right-click on the drives and choose "Change Drive Letter and Paths," click Add, and assign it an unused drive mapping, it will then appear in Explorer.
Incidentally, the SAMSUNG_Android still shows up with its unhappy yellow exclamation point in Devices and Printers. So I imagine there's supposed to be a more user-friendly way that doesn't expose the true internal file structure when it's all working properly. But in the meantime, I can at least access my phone data via USB.
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Dude look at the date
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Hey there..
View attachment 876861
thanks
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Yep...
Ubuntu / Linux FTW!
Hmmm, native on Linux you say? Don't have to battle with windows composite USB hub bullcrap you say? I shall try this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Related
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Update driver
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
ShreddinPB said:
Hey guys, I followed the guide, added the lines to the inf, even downloaded the other inf and coppied over it. I can not get ADB to recognize my gTablet. I even removed the mass storage driver that was associated with the tablet
I know my adb works with my mytouch slide.
Has anyone else not been able to connect adb to the gTablet?
I followed the guide exactly.
There are no errors in my device manager.
USB debugging mode is on.
I cant think of anything else to try.
Click to expand...
Click to collapse
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Emul8or said:
This is the steps I took, FYI I'm running Windows 7 on my computer.
Completed the the steps in the Guide (as you did). Then had to Go to Control Panel>Device Manager; and had to manually update the drivers. In Device Manager select the G Tablet>Driver>Update Driver and navigate to your usb_driver folder in your SDK.
Click to expand...
Click to collapse
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
it2steve said:
Not sure what you are using ADB for however I have had issues with my PC retaining the driver for it as well. I use an app called ADBWireless that allows me to connect wirelessly and use ADB commands for a few simple things. It's a good workaround if your just pushing and pulling a few apps and such.
Click to expand...
Click to collapse
There is a fix posted for the slowdown issue after resume from sleep, and you ADB to fix it
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Here's what dev mgr looks like on XP...
Jim
ShreddinPB said:
Thats what I figured I would do. I am also in Windows 7 but X64. I go to the device manager and I dont have a gTablet listed anywhere that I can find, but like I said there are no exclamation points in the device manager.. no devices that are not working.
I tried to update the "Portable Devices>f:" that shows up when I plug in the tablet but it wont let me.
So in your device manager.. there is a top level listing for "gTablet"?
Click to expand...
Click to collapse
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
davinci07 said:
Is there anything under USB drivers at the bottom for android bridge, or something along those lines? If not does it list NVIDIA Harmony drives anywhere? If neither try unplugging and plugging in your device a few times to see what dissapears when you plug it in. Reply back and we can go from there.
Click to expand...
Click to collapse
Found it.. it was under "Universal Serial Bus Controllers" and called "USB storage device" i believe.
I tried updating the driver with the andoid one, but it errored out and wouldnt load it. After that however, 2 new devices popped up.. both the Nvidia harmony drive, and another nvidia tegra one. The harmony drivers failed to load.. so I pointed at the directory in the SDK and bam it works!!
Thanks guys!
But also btw.. before I got this working, I did use ADBWireless to run the adb shell and run that camand mentioned in the main thread that is supposed to stop the slow downs.. and I think its working.
enjoy, can you point me to the post that you needed this for? Also, now that ADB works you can start making your own apps. With either Eclipse and Android SDK (more advance route, but there is alot of good books that could help you alot) or with app invnetor that just got released to the public.
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.
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.
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
Run the trouble shooting guide in KIES to re-install the drivers . Also, use KIES AIR, that only needs WiFi and you can access files and folders via your pc browser. Hope that helps
unistaller old driver. go to samsung website download lastest driver and install it
depzaj said:
unistaller old driver. go to samsung website download lastest driver and install it
Click to expand...
Click to collapse
Yup that to. BUT, often on the Samsmug site the software version available is one version behind behind that available via online updates Kies.
Tried that
Hi, I have already done all of the above more than 3 times ive removed the drivers, kies and re installed and my computer will always just keep saying usb device not recognized with code 42.
This is what microsoft have to say:
"Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer."
I have to go out just now. I'll take a looky see when I get back.
error 43
oh im sorry its not error code 42 but 43
windows detectded problems with this device....
Do you have a Linux OS under the hand? It would give you a lot more information than Windows does... If you dont have but want to try, you can download the disc image from ubuntu.com or any other distro like linux mint or fedora etc.
Just to get information on your phone you dont have to install it, just starting on the liveCD, plugin the phone in and running comands like dmesg, lsusb and maybe hwinfo would be able to tell you what is happening with your phone.
Sent from my Nexus S using XDA
error 43
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
pacificblue03 said:
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
Click to expand...
Click to collapse
This is why I suggest you to try to plug it in a linux machine and run those commands, there is obviously a problem with your device and Linux could help you to define what it is since it gives more information on the hardware.
If you are unfamiliar with dmesg output you can create a pastebin and link it here I will try to help with it. The output of lsusb may provide interesting info too. (as hwinfo but I don't think it is available by default in Xubuntu)
Sent from my Nexus S using XDA
error 43
well i will try if i can but it will be in a day or two as im packed to the top with assignments
Also I did not mention that but you can access your phone via the wifi network starting an ssh or ftp server on it, the one I use is connect bot from the market. This way you can manage you music and files over the network.
Sent from my Nexus S using XDA
error 43
yes i have done it using kies air that works. i will try the ubuntu method as soon as i can. thanks for all your help so far everyone.
Can you confirm that your usb ports on the PC is working with other devices. Its starting to look like a faulty phone. Have you tried a different usb cable, or can you check the current one with another device. We need to exclude all other factors before we conclude it is a faulty phone.
error 43
other devices work yes.
OK, looks like a croaked phone. Last ditch effort. If you go over to the forums at http://www.sevenforums.com/ have a good search for that error 43 code, there might be an answer that I've missed. We could also have a good look at the windows error logs, but I don't hold much hope as you have proven the PC hardware works, and you have checked and cross checked the drivers. All the error logs will show is an expanded view of the error.
I would consider returning the device with a view to a new replacement. Sorry. :-(
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Got the same issue on 3 different W7 pc's. Got my sgs3 like 3 days. first day USB connection worked just fine but now there's no way of connection it to pc with USB. offcourse you can connect with WIFI but with USB link is much faster
Galaxy S3 drivers issue...resolved!
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
I had the same problem and could not figure out why...here is the deal:
Prior to SGS3, I had the old Samsung Galaxy S/Vibrant and was using the USB cable which came with it...then I thought; maybe the USB cable in the box of GS3 is different or superior...i tried it and VOILA! it worked...so that is all I had to do...all these reboots and re-installing drivers was just a waste of time...PS> I am running Win 7 64bit
USB ERROR
I still cant connect with 3 different cables, i am going to do a factory data reset and tell you all how i go in about 15 minutes...
When I plug my phone in I have no way to transfer files to and from the Nexus 5. Nothing comes up. Tried updating the drivers, but nothing works. Please help.
I haven't been able to do this either, anyone wanna help?
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Sent from my Nexus 5 using xda app-developers app
n7of9 said:
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Click to expand...
Click to collapse
Nope, still nothing. My Razr HD comes up fine, but not the Nexus 5. Think it's a conflict in drivers?
Tweaken said:
Think it's a conflict in drivers?
Click to expand...
Click to collapse
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Tweaken said:
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Click to expand...
Click to collapse
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thank you n7of9 the link you provided worked for me.
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
This worked and also fixed another popular issue
Not only does this fix the MTP connection issue to move folders to root folder. But it also now allows me to see the preview thumbnails of my media! This was a huge problem on my other phones and many many people including me were never able to fix that. All the ideas to get around or create USB Mass Storage instead of MTP after 4.1 were fails.
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Worked perfect, thanks
what worked for me
In windows 8.1
I plugged in my nexus and browsed to device manager in control panel
I uninstalled the device (and deleted the driver)
I unplugged the nexus 5
I plugged it back in
Windows recognized it as a proper MTP device
I think the problem was something to do with windows recognizing it as an ADB device (I had installed the toolkit before etc)
This fixed it for me
openlatedotorg said:
Worked perfect, thanks
Click to expand...
Click to collapse
Hi,
I did all the steps mentioned, and ran the driver test - everything works fine, success.
However, I still cant see my device in "This PC"...
What is even more weird, that it only disappeared couple of days ago, and I didnt do anything to my computer at all....
Any other way to get devices to show? (Nexus 10 or Nexus 4 stopped showing too).....
Maybe problem is that it is being shows as ACER ADB Interface? But i cant change that to MTP anyway..