My Samsung Intercept wont connect to my computer, everytime I plug it in, I get USB device not recognized, how can I get it to be recognized? Im running android 2.2.1, and my computer is running Windows 7 Ultimate 64-Bit
I tried posting a link but the spam prevention police apparently wont let me post links until I have 8 posts. So I'll just quote:
First I tried to use Win 7′s XP mode, which was a total failure. The Windows stock Virtual PC cannot control any devices, it just reads them as belonging to the real computer. After a lot of searching I found the open source Oracle Virtual Box, which is Windows Virtual PC on crack. With Virtual Box, you can mount any number of operating systems to play around with. As a bonus it has the capability to see external devices as its own. All you need is an install disk for your operating system of choice. I had gotten the Intercept to work with both XP and 7 32 bit, so I chose to install a Win 7 32 virtual machine.
For all the specifics on how to install a virtual operating system in Virtual Box, read the user manual. Its large and technical, but skimming the first two chapters should tell you all you need to know to get started. The short version, you set up a partition for your virtual machine, you then “boot” the virtual machine with the install disk of your operating system of choice. You then go through all the normal installation steps, and bingo-bango you now have a virtual copy of XP/7/whatever.
Here is where things get hazy. I was under the impression that the virtual machine would be where I would see the phone. However for mysterious reasons, suddenly the phone now gives me the option to mount and my main Windows 7 64 has no problem letting me into the phones drive!
I don’t know why. I can close the virtual machine and still have access when I plug in. I wish I knew what the heck was going on and how a virtual 32 bit 7 convinced a real 64 bit 7 that the Intercept is OK, but I do not. All I know is that Virtual Box somehow worked for me, perhaps it can work for you. Other than that Virtual Box is a nifty tool I should have had long ago. Good luck!
UPDATE: I wrote this a couple months ago and while it did work, I have a funny feeling that its all just pure luck as to if Windows will bother to recognize the phone. I have computers it works fine on and some that refuse to see the phone no matter what I do. The whole key is to just keep trying, something will work eventually. If all else fails get an app like SwiFTP and move on with your life.
Click to expand...
Click to collapse
Retrieved from wordpress.
Thank you very much for this information, I will get to trying the Virtual Box and the SwiFTP, thank you again.
The above information you gave still didnt work :/, do you or anyone else know what I could do to fix?
Hello, I wanted to say that the whole process for the computer to see the Samsung Intercept is buggy to say the least. I have a good knowledge base of computers as I work as a Desktop Support technician for the past 10 years. I read many posts and replies. None seem to be concrete on a resolution. I tried the usual methods. I downloaded the Samsung SWUpdate+Patch. I downloaded the Sprint USB Modem drivers from Samsung's Web site. I also downloaded the custom files for the Kernel and custom recovery. The first thing I tried on all four of my computers was to install the Samsung USB Modem drivers. The second thing I did was to install the SWUpate+Patch software. My first test computer was a Compaq D500 desktop. Windows XP-SP3 with USB 1.0 ports and a USB 2.0. I placed my phone in USB Debugguing Mode. I then powered off my Phone. I held down the three magic keys to get the phone in "Download" mode. I checked Add/Remove Programs both programs were installed- Samsung USB Modem Driver and the SWUpdate. I first opened the Samsung SWUpdate program. I followed the onscreen instructions of the Samsung program. The program could not communicate with the phone. Bottom right corner of the program said disconneted. I tried chaning the Port Settings in the program to COM1, COM2, etc. All said disconnected. I tried opening the Samsung program several times. Restarting the phone, unplugging the battery etc. I also tried using a different USB cable besides the one that came with the phone. No communication. I tried the same process on another PC which had Win7Pro 32Bit SP1. Almost same results, but I had the computer install these three devices when I opened the Samsung program and connected my phone:Android UMS, S3C6410 Android ADB, CDC Abstract Control Model (ACM) I thought I was good. Status still Disconnected. I restarted the computer tried the whole process again. This time the computer gave me three messages of "Device not Recognized." So I tried a few more different was to get the drivers into Device Manager nothing worked. I even tried that PDA2net app that app wouldn't see the phone wither. Then I looked into the PDA2net directory and saw some drivers .INFs that I thought might work.. I would get a little farther, but then the driver seemed to install and partially recognize the devices, but then a message said that it could start "Error 10" So I tried another computer. Windows 7-64bit. I knew this was going to be a long shot..and it was.. Samsung USB Modem Driver not supported on this version of Windows. So I tried my work computer Win7Enterprise 32Bit. Same issues Device not recognized three or four times. I tried the two USB cables for my phone the OEM one and Aftermarket. No luck. So I had my old trusty Dell D600 laptop. WinXP-SP3 32bit USB 1.0. I installed the Samsung USB Modem driver then the Samsung SWUpate app. I got my Recover.tar file dropped into the Bin dir. I opened the Samsung SWUpdate app and holy **** the damn program was able to connect to my phone I couldn't believe it.. I wanted to take a screen shot of it working just so I could make sure it wasn't B.S. I used my laptop with an Aftermarket USB Cable. I'm not sure if it's a Data USB cable or just a charging cable. I don't think there is two different cables as I've read many times on different fourms. I'm not sure why my laptop works with the phone. When my phone did finally connect it connected on COM3. So maybe it's a port setting/IRQ. I also turned off my Firewall each time just incase it was blocking communication.
If anyone has any questions please feel free to reply. I will try to help in any way possible. I wanted to say thanks to XDA Forum and to Super-6-1 on YouTube..you guys Helped Me more than you know.!!!!!
I'm having a problem getting my new Charge to connect to my computer in Download mode. It hooks in just fine when the phone is powered up, but of course I can't use ODIN and root my phone without it... and an unrootable phone is pretty much cause for return to sender, as far as I'm concerned. I've searched the forums and downloaded the same drivers at least four times (and several other sets that were probably the same ones), and every time, I get the same problem: no driver found for the "Gadget Serial" device that the computer detects. I heard ODIN was finicky (though that's not where the problem is, since Windows doesn't know what to do with the hardware), so I switched USB ports, and USB cables... no love.
So: has anybody had the same problem, with their Charge stubbornly refusing to connect in Download mode? Where did you find the drivers that worked? Links would be highly appreciated, as I spent about two hours searching both the forums and the interwebs to no good use yesterday. (Yes, I do understand basic forum etiquette and I really have searched, but can't find any drivers that fix the problem for me.)
Thanks in advance!
I just went through this myself the last couple of days.
Turn OFF USB Debugging. Plug the phone into your PC via USB. A "cd-rom" named Verizon should pop up in your drive list. There's four or five filess in there. Run the one to install the drivers. Once that's finished, you can turn off the phone, then boot it into download mode (I assume you know how) and Odin will recognize the phone at that point. The "cd-rom" drive would not pop open for me while USB Debugging was turned on, so I missed it.
Actually Odin 1.3 didn't see the phone for me, but Odin 1.83 did. I've read 1.7 works as well.
Fixed!
Gah--I'd gotten way ahead of myself. After trolling the forums extensively, I'd downloaded drivers before ever plugging the phone in. Once I *uninstalled* those drivers, the Verizon CD drive showed up. Prior to that, I had a CD drive appear, but not one that my computer could read data off of.
Thanks a zillion for the help. My computer is now happily recognizing the Charge in Download mode, and Odin 1.3 is seeing it, too. Now, to root!
hi,
I am an advance user and recently brought the Samsung Omnia W i8350 a.k.a Samsung Focus Flash. Initially it connected fine and updated twice with zune since the initial stock version.
I did not had time to explore much and I am pretty new to the Windows Phone 7 environment. few days back when I connected the phone to the PC, the device was recognized as GT-I8350 and windows kept on searching for drivers but no drivers were located. I tried installing the zune drivers but even they do not allow me to connect the device to zune (hence no music, no updates, no backups )
Then I downloaded drivers from tsar3000 and they automatically instal 3 devices off my phone, one was a com port, one was modem , and so on...
STILL NO CONNECTION TO ZUNE.
I have tried almost everything but to no avail. can you guys help me?...
Regards
PS: between the last successful connect and unsuccessful connect, there was a time when Win7 stopped booting, so I simply stopped many services and booted again because I had a presentation and no time for a fresh install, could this possibly be a service issue?... I tried starting some services but the did not work. Can anyone enumerate the services required by winP7.5?... also if a manual driver is available, it will be appreciated.
PPS: I also tried running the windows phone 7 drivers from zune folder, it gives an error the device cannot start.
You put the phone in tethering mode, it sounds like. The COM port and modem drivers indicate that the phone is sending a different USB device ID than normal. On the gen1 Samsung phones (and quite possibly on the gen2 ones, but I havne't checked) you could put the phone's USB port in a mode where it would act as a modem for the PC. It sounds like that's what you've done.
Try a search on "WP7 Samsung tethering" or similar and see if you can put the phone back in its normal mode.
GoodDayToDie said:
You put the phone in tethering mode, it sounds like. The COM port and modem drivers indicate that the phone is sending a different USB device ID than normal. On the gen1 Samsung phones (and quite possibly on the gen2 ones, but I havne't checked) you could put the phone's USB port in a mode where it would act as a modem for the PC. It sounds like that's what you've done.
Try a search on "WP7 Samsung tethering" or similar and see if you can put the phone back in its normal mode.
Click to expand...
Click to collapse
hey thanks,
I was just reminded, that I was one day testing the steps mentioned on this thread, to use the phone as USB modem, hence had left it there since then, Never used it though.
Great! Solved!
Hello
:crying:
I got my N5 today, and like my wife's N7 and my N10, NONE of them will show up on windows explorer (windows 8.1)
I can unlock, root, install custom recovery, all good, but as far as actually SEEING my device on the computer so I can drag and drop stuff, well, I literally have been spending almost a day trying to sort that out and have not got any closer at all. It is really pathetic.
I've changed the windows Unsigned drivers thing (though the drivers must be ok if I can do all that other rooting etc)
But yet when I uninstall the drivers to try installing them again, win8 says "Android ADB Interface. The third party INF does not contain digital signature information"
But I'm pretty sure that when I reinstall them AGAIN, I will still nto be able to see any of my Nexus devices on Windows explorer... despite them showing up in the Windows Notification under USB, and they are mounted there... I can UNmount them!
Something is way off kilter here, its with 3/3 devices, perhaps win8.1 is completly Android unfriendly, or?
Advice/help MUCH appreciated for someone who is going nuts here.
tx
Mark.
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Hello guys,
lowandbehold said:
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Click to expand...
Click to collapse
I did turn it iff to ADB but do not see where I would turn it back on, but that may be it with my N5...
EddyOS said:
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
Click to expand...
Click to collapse
I really dont know. I have 4 PC's in the house, and sometimes my old dell laptop (also 8.1) seems to be the most reliably connect-able.
hotleadsingerguy said:
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Click to expand...
Click to collapse
There has to be a physical reason for it (unless we are to consider the metaphysical - past lives, re-incarnation of gadgets, Steve Jobs curses and stuff...) and it does amaze me that it still seems so hit and miss. When I first got onto android a few years back, you just plugged your phone into USB, ANY ONE ON ANY COMPUTER and whammo, you'd get both Ext SD adn Int SD mounted... reliably. I'm sure that was causing security and stability issues so all manufacturers seem to have snuffed that out.
so that MTP toggle is at settings > Storage > settings in storage
but it makes no difference still not vis in WinExplorer
Cheers
Mark.
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
lowandbehold said:
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
Click to expand...
Click to collapse
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
fredphoesh said:
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
Click to expand...
Click to collapse
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
ZeroAlphawolf said:
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
I must say, I did leave that part out of my replies. I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Enable USB debugging in developer options.
Sent from my Nexus 7 using Tapatalk
Nexus Root Toolkit includes a variety of USB drivers you can try, as well as a few utilities to help you diagnose and fix android driver problems. That's where I would start. You don't need to use it to root or anything (unless you want to) but the driver utilities in the toolkit have fixed a number of problems I've had with android drivers over the years. I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Not really the same at all but I had a hard time getting my S3 to be recognized on my computer at work running XP.
In the end the problem was the generic USB drivers that were installed had to be manually removed; even the official Samsung drivers wouldn't overwrite them. After a bit of digging and prodding I got it to work.
My Nexus was recognized without issue on my Win 8 machine.
You'll have to try a variety of different drivers to get it to show up properly. My N4 and Note 3 had no issues showing up, but the N5 wouldn't. I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
This happens to me every single time with a new device so I know exactly what to do now. It's not a driver issue, it's a problem with windows 8 and how it searches for drivers.
If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Another problem I had was remembering to accept the ADB on my phones end, I never had to do that with my HTC one, so when going through rooting the raw drivers were likely unnecessary, I just hadn't noticed the primly on my phone when the first drivers I installed worked.
Hello guys, thanks for the various responses...
ZeroAlphawolf said:
Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers
--------also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
lowandbehold said:
I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Click to expand...
Click to collapse
I did initially install the raw drivers as they sounded like they would be best... will try the camera toggle and MTP toggle
rabidfurball said:
I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Click to expand...
Click to collapse
Encouraging!!! I know from my SGS3 and 4 and some generic chinese tablets ive had that the driver installation can be a major PITA but eventually you do the same thing for the 5th time, and it works, with no (seemingly) logical reason.
Stories said:
I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
Click to expand...
Click to collapse
I did a fresh install of windows 8.1 just yesterday... so it was pretty clean!
KiNG OMaR said:
It's not a driver issue, it's a problem with windows 8 and how it searches for drivers. If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Click to expand...
Click to collapse
Yeah, i have tried that and it says I have the best drivers already installed. Oddly I can use Nexus Root Toolkit fine, so there has to be something right about the drivers... just not the part that shows up on a computer.
I'm convinced there HAS to be some scientific way of doing this, its such a common problem, it would be great to really figure it out. The problem is, one has to try 100 things before it works, so it becomes almost impossible to know which actions to attribute as the solution!
tx again,
Mark.
a solution - possibly useful...
Hello guys
Following Wugfresh's instructions to the T...
I tried drivers Option 1, (Universal) and the result was exactly as with the Raw (Option 4) drivers... So I uninstalled the drivers, ran ran USBDeview and uninstalled 7 devices like "Google Nexus ADB Interface" and "USB Composite device" and "Nexus 10".
Then tried Option 2.
The installation did not go exactly according to Wugfresh visual guide, so I cant be certain, but I do know that installingPDANET drivers only work if you select MTP, otherwise it will not find the tablet/phone.
After the instalation, the app called PDANET installed on computer, not on my tablet. My PC showed a pop up notification when tablet USB debugging is turned on, but again, it was not visible in windows explorer.
I then was going to try Option 4 again, and Uninstalled drivers in device manager WHILE I STILL HAD THE TABLET STILL PLUGGED IN, so I am guessing though PDANET uninstalled, the drivers remained (which I think is what Wugfresh's process would have done if it had run according to plan. I ran USBDeview and uninstalled the same 7 devices.
Then
Plugged tablet back in to attempt Raw drivers, but all of a sudden, the device was recognised and for the first time visible fully in Internet Explorer!
So basically it seemed to be the PDANET drivers that worked, though I have no idea if that would have worked had I tried these drivers in the first place.
I hope that helps someone!
Cheers
Mark.
OP, are you running W8.1 64 bits or 32 bits ??
I had my Sony Viao running W8 64 bits & hated it, downgraded to W7 64 bits and it's very happy getting along with Nexus 7 - going to play with N5 later on. Good old Dell Latitude is running W7 32 bits and it's my main machine to unlock, root & flash and so far so good - yet, I was reading about someone running Vista and had issues with the usb drivers.
I have 2 fully licensed W8 safely tucked away and the way it's looking, I might never get out of W7 - let alone then upgrading to 8.1 for free - getting reminders from $S a few things already.
Most of the time, the mess are caused by conflicting drivers installed & loaded - I keep a clean & lean desktop to do these bench work, and even though it is a PITA, starting clean with minimal programs (and apps) installed is often a good start - turn off antivirus & firewall, especially if connectivity is not needed - enabled access only if it is required and/or necessary.
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Hello guys
Letitride said:
OP, are you running W8.1 64 bits or 32 bits ??
Most of the time, the mess are caused by conflicting drivers installed & loaded
Click to expand...
Click to collapse
64 on the two PC's in the same room, HTPC's and laptop are 32 I think, but I have not tried them. I did a fresh Win 8.1 install on Tuesday and had no drivers from any devices other than the ones I manually installed with Wug.
KiNG OMaR said:
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Click to expand...
Click to collapse
Yeah, well try the PDANET (worked for me, though was my last resort as I don't like to install stuff that is a/ meant for something else, b/has some software I dont need that comes with it... but I did manage to keep the drivers and UNinstall PDANET software by keeping the tablet plugged in when I uninstalled PDANET... try it.
tx
Mark.
I'm posting cuz I've literally spent hours and hours searching, trying things, etc, and am stuck. I have several PQs with various CM/LineageOS ROMs. It is not a ROM issue because if I plug via USB into my desktop pc running win 10, they all work as I want. Presumably, it's a driver issue or something related to my specific laptop - I recently bought an old used laptop, originally shipped with win7. After purchase I immediately removed all partitions and installed win10 from disc (fyi, you can d/l win10 iso from microsoft and use win7 oem key to legally install fresh win10, even now the free upgrade stuff is over - that surprised me).
I cannot, no matter what I do, get file access via usb to my phone. I've tried lotsa things. I don't remember if/what I had to do to make my win10 desktop see them - maybe it was automatic, i dont remember, if it wasnt, I easily downloaded/installed what was necessary - but nothing I've tried makes my win10 laptop load the drivers, although it does detect something when I plug it in, and something else when I select MTP on the phone (vs charge). But just exclamation points in device manager and nothing in explorer. Among other things, I've tried MotorolaDeviceManager_2.5.4
It's especially annoying as I have a video on my phone I wanted to send out tonite and can't, spent another couple hours trying. Bluetooth works fine for pictures but freezes at 10% for video, no idea why. But I'd much rather just use a cable than figure out any wireless BS.
Incase it's something specific to this laptop and someone is curious, it's a Sony VPCF115FM. That 'base system device' and "unknown device" are always "!", MTP with "!" only appears when phone plugged in.
Yea definitely a driver issue. When you plug the PQ into your desktop (which seems to work) what shows up in device manager?
Have you tried to right click on the devices with yellow exclamation points and update the driver from Windows update?
I never followed up on this, but still haven't found a solution, and kinda forgot about it. It does work in PTP mode. And works for a newer Moto (Lenovo) phone on this laptop. Yes, I tried the windows 10 device manager update auto search thing (in fact, just tried it again minutes ago before I read this). I'm about to wipe and install fresh as this phone is running crazy slow lately and wanted to copy everything off before I wipe which is what reminded me of this issue - funny thing is that a google search of this problem ("mtp driver motorola photon q windows 10") found this thread as the third search result and I completely forgot I posted it. I vaguely recall I read your reply but was waiting to see if anyone else responded and then just forgot to follow up when it wasn't on my new list...
PROBLEM SOLVED! It happened in TWRP too and sideload was failing (for another reason) but made me try to figure out MTP again.
Found solution here for anyone with similar issue:
https://answers.microsoft.com/en-us...0-solved/d2226a54-65db-41ba-9398-a12196cc279c
Gotta update driver and manually select "MTP USB" from list of devices, in my case I found it under portable devices.