Related
It seems like a craps shoot for me if windows will recognize it... hell sometimes my notification bar tells me usb is connected but doesn't give me options to turn it on or off... and this is all with USB set to mass storage... is there possibly something I am doing wrong?
Like sometimes it hooks up without any issues, other times windows sees it, but after a few minutes says its failed to install a MTP USB device, so I have tried pointing it at the location where the sammy USB drivers were installed but nothing... I have tried uninstalling/reinstalling the drivers and manually switching them to other random things...
sometimes a reboot of the comp works it out, but other times it doesn't... I have the feeling I am just missing something...
Same here, except i'm on WinXp SP3. Get USB connected icon in notification bar of Vibrant, but windows task tray says failed to install device.
Looks like iffy drivers to me. Since samsung apps isn't available in the US yet, is there somewhere else we can get Kies?
The file you want for Windows 7 x64 is called GalaxyS_64.zip - worked perfect for me. Can't remember where I downloaded it from, though... uploading it now.
Edit: Here's the file you want.
http://www.filedropper.com/galaxys64_2
gordon.mott said:
The file you want for Windows 7 x64 is called GalaxyS_64.zip - worked perfect for me. Can't remember where I downloaded it from, though... uploading it now.
Edit: Here's the file you want.
http://www.filedropper.com/galaxys64_2
Click to expand...
Click to collapse
That's the same thing I have tried installing a few dozen times before... still won't work.
There are multiple notifications you have to deal with on the phone. Took me a while to figure it out, too.
First you have to pick the mode you connect to W64 in (Mass Storage), then you actually have to mount the internal memory and card as drives for W64 to see them. This is all in the Notification bar on your phone. Just because you see the USB icon does NOT mean you are supposed to be connected.
THEN you get the "What do you want to do with this?" from Windows.
I got so tired of all the confirmations I just installed Dropbox. Now if I want a file on the phone I just drop it into my Phone Stuff directory and pick it up on my phone. No USB cable, no WiFi, just grab it and go.
If you're looking to xfer over a big batch of media files there is DoubleTwist and several other apps like it that will do so over WiFi.
Col.Kernel said:
There are multiple notifications you have to deal with on the phone. Took me a while to figure it out, too.
First you have to pick the mode you connect to W64 in (Mass Storage), then you actually have to mount the internal memory and card as drives for W64 to see them. This is all in the Notification bar on your phone. Just because you see the USB icon does NOT mean you are supposed to be connected.
THEN you get the "What do you want to do with this?" from Windows.
I got so tired of all the confirmations I just installed Dropbox. Now if I want a file on the phone I just drop it into my Phone Stuff directory and pick it up on my phone. No USB cable, no WiFi, just grab it and go.
If you're looking to xfer over a big batch of media files there is DoubleTwist and several other apps like it that will do so over WiFi.
Click to expand...
Click to collapse
Well I am installing dropbox because this is getting ridiculous... after a fresh flash it mounted once, then after that it wouldn't ever again. I tell it to mount to my computer and everything, but the computer just shows an icon that it is trying to install the drivers and never does... Come on samsung, stop being so proprietary...
Wow guys I didn't have any problems at all. USB Mass Storage worked the first time and it keeps working. Where I encounter problems is when I set it to USB Debugging then it doesn't get recognized.
ETA: I'm on Windows 7 x64 with all the current updates.
My windows is 32bit XP, but try this trick i've discovered, may be it will help. Say into voice dialer "Open SD card" -> check "Enable USB mass storage". Let's know how it works
Hey Degeneration, you can also install the Android SDK.
Unfortunately I can't post external links until I'm validated by a mod, but if you google "screenshot vibrant" (w/o the quotes) it should be the top link.
The domain is know your cell dot com and it has links to the Android SDK and the Java SE SDK in the instructions to take screenshots of your Vibrant.
I personally think you should try this because your phone may be defective. I'm running W7-64 Pro and didn't have to do anything to get the phone and the PC to see each other.
Wow I had no idea people were having this issue. I'm running Win 7 Ult. x64 and for me it was just plug in and go. When I was rooted on my G1 I had a similar issue but using USB Debug and the Android SDK fixed that. hope you get it figured out.
Yeah I'm on win7 and I installed the drivers and plugged in the phone and was good to go
Sent from my Samsung Vibrant using XDA App
I installed the drivers before ever plugging the phone in. I also have had SDK, adb, and Odin3 ready before plugging it in. When I first got it I immediateness set it to mass storage and didn't have a problem. Then when I started messing with it more I started having trouble every once in a while with it mounting, to the point that now it works every once in a while, mostly right after a fresh flash. Personally I think it's a combo of both the phone and the computer doing crap, but it's pretty lame. I don't even remember installing drivers for my G1, and definitely nothing else and I never had an issue with it. I don't see why samsung can't kiss a little butt or pay a little money to have windows recognize the phone and be able to install the drivers from the net. Now if the problem was just for people messing with their phones it would be one thing, then it's on me. But last night I was running stock again and it only worked the first time it connected, but I forgot to switch to mass media so I disconnected, switched, reconnected, and nothing. Tried switching back and same thing...
Constantly just keep getting told at best that windows failed to install an MTP (or whatever, I just closed the thing in the notification area and when I tried reconnecting the USB cable I got the phone just telling me USB is connected but giving no options) device failed to install...
bah... oh well
OK, I've now officially burned 4 hours trying to get my Epic to work properly with Windows 7 (64 bit) for anything besides mounting it as a USB drive.
I tried the (32-bit?, and only?) driver Samsung seems to officially have for the Epic 4G.
I tried the 64-bit driver(s) apparently intended for Kies.
I've installed, uninstalled, shutdown-after-uninstall-instead-of-reboot, and sacrificed 3 chickens to the appropriate gods.
I temporarily made TouchWiz the homescreen instead of LauncherPro.
I made sure the phone was in "PDA" mode and NOT "modem" mode (##8778##, I think).
I've updated everything Windows Update will touch, then installed the Asus P5N-D motherboard chipset drivers straight from Asus' international site, just for good measure.
I've attempted to upgrade the Google USB driver through tools (the app that gets launched when you just type "android" from a command prompt).
Oh, I also made sure that USB Debugging was NOT enabled when I connected the phone for the first time after supposedly installing the Samsung USB drivers. Two of the drivers installed correctly. Then I enabled USB debugging, reconnected USB, and ended up (for the Nth time):
SAMSUNG Android USB Composite Device: v/ Ready to use
CDC Abstract Control Model (ACM) O Installing driver software... (for 20+ minutes)
S3C6410 Android ADB O Installing Driver Software (for 20+ minutes)
USB Mass Storage Device v/ Ready to use
For the record, I have a core2quad 9600 running at ~2.6GHz with SSD, so it seems almost inconceivable that it could legitimately take 20+ minutes to install ANYTHING.
In Device Manager, I have at least one "Other Devices" entry that just refuses to die -- Universal Serial Bus (USB) Controller. I've tried deleting it, uninstalling it, uninstalling it and shutting down (vs restarting windows), the works. NOTHING will kill it, or at least it won't stay dead when I try. Worse, when I try reinstalling the Samsung drivers, I usually get a message along the way that installation of the drivers for the Universal Serial Bus (USB) Controller failed, even though it's not even connected.
This is driving me insane. It worked fine under Vista/32, but I've never been able to get it to work properly since I got the SSD and Win7/64. Specifically, I've never been able to get ADB to work, and the USB driver situation appears to be completely fsck'ed.
Is there some secret strategy I'm forgetting for making Windows forget everything it thinks it knows about a corrupted USB driver installation and making it start over from a clean slate? I think the problem is that I have a driver that's latched onto something, refuses to be deleted, and won't allow itself to be overwritten.
Before I waste any more time on this, can anybody recommend any specific things to try? I have to get this working tonight
bitbang3r said:
OK, I've now officially burned 4 hours trying to get my Epic to work properly with Windows 7 (64 bit) for anything besides mounting it as a USB drive.
I tried the (32-bit?, and only?) driver Samsung seems to officially have for the Epic 4G.
I tried the 64-bit driver(s) apparently intended for Kies.
I've installed, uninstalled, shutdown-after-uninstall-instead-of-reboot, and sacrificed 3 chickens to the appropriate gods.
I temporarily made TouchWiz the homescreen instead of LauncherPro.
I made sure the phone was in "PDA" mode and NOT "modem" mode (##8778##, I think).
I've updated everything Windows Update will touch, then installed the Asus P5N-D motherboard chipset drivers straight from Asus' international site, just for good measure.
I've attempted to upgrade the Google USB driver through tools (the app that gets launched when you just type "android" from a command prompt).
Oh, I also made sure that USB Debugging was NOT enabled when I connected the phone for the first time after supposedly installing the Samsung USB drivers. Two of the drivers installed correctly. Then I enabled USB debugging, reconnected USB, and ended up (for the Nth time):
SAMSUNG Android USB Composite Device: v/ Ready to use
CDC Abstract Control Model (ACM) O Installing driver software... (for 20+ minutes)
S3C6410 Android ADB O Installing Driver Software (for 20+ minutes)
USB Mass Storage Device v/ Ready to use
For the record, I have a core2quad 9600 running at ~2.6GHz with SSD, so it seems almost inconceivable that it could legitimately take 20+ minutes to install ANYTHING.
In Device Manager, I have at least one "Other Devices" entry that just refuses to die -- Universal Serial Bus (USB) Controller. I've tried deleting it, uninstalling it, uninstalling it and shutting down (vs restarting windows), the works. NOTHING will kill it, or at least it won't stay dead when I try. Worse, when I try reinstalling the Samsung drivers, I usually get a message along the way that installation of the drivers for the Universal Serial Bus (USB) Controller failed, even though it's not even connected.
This is driving me insane. It worked fine under Vista/32, but I've never been able to get it to work properly since I got the SSD and Win7/64. Specifically, I've never been able to get ADB to work, and the USB driver situation appears to be completely fsck'ed.
Is there some secret strategy I'm forgetting for making Windows forget everything it thinks it knows about a corrupted USB driver installation and making it start over from a clean slate? I think the problem is that I have a driver that's latched onto something, refuses to be deleted, and won't allow itself to be overwritten.
Before I waste any more time on this, can anybody recommend any specific things to try? I have to get this working tonight
Click to expand...
Click to collapse
I had the same problem, but found out that its all b/c of my cheap 99cent usb cable. When I use the official usb cable that came with the phone it works fine.
Argh. It appears I've forgotten rule #27,326 of Android -- don't believe the error messages. Half the time they're wrong, and the other half of the time something is lying to you. Despite having the USB driver that I can't get rid of or fix and the error messages announcing that installation failed, it seems to work. At least, adb logcat works, and I was able to deploy an app from Eclipse to the phone right now.
(goes to bash head against wall in frustration)
Oh, I'm using the cable that came with the phone ;-)
Which particular driver did you end up with? I tried using the Samsung Moment drivers (saw a vid on Youtube using these as a substitute for the Intercept handset), and though I got similar errors as you - and supposed fixes - my Eclipse was never able to connect to the handset to debug an app, grab screen shots, or anything. Would love to figure out how to get my Intercept to work with my Win 7 64-bit setup.
First of all, a large number of people (myself included) agree that the stock USB-microUSB cable sucks balls. I ran into the same problems you're having, and then they magically went away when I replaced my cable. You can find super-cheap cables on Amazon.com, or if you're a "gotta have it now!" type I know the Radio Shack cable works great, I have it.
Secondly, I know the drivers on http://forum.xda-developers.com/showpost.php?p=7933592&postcount=1 work, they're what I'm using.
I would imagine you just need to replace that stock cable. Sometimes certain things will work, but I had almost exactly the same problems as you and they all went away when I changed my cables.
Also, try to use a USB socket that's directly attached to your motherboard, i.e., a USB port on the back of your PC, as apposed to front- or top-mounted USB ports, since those add extra hardware and connections that could decrease reliability.
Good luck!
For what it's worth, I am using the drivers from Samsungs website on all of my windows 7 x64 computers. Haven't had any problems.
Sent from my SPH-D700 using XDA Premium App
Use this to remove any residual drivers from your computer before installing your new drivers. It is a very useful tool when you have driver conflicts that may be happening.
http://www.multiupload.com/3PC2BBAFSO
Then use these drivers, they've worked on my many machines with Win 7 64 bit:
http://www.multiupload.com/LLOCCAMUT4
Wow just realized how old this thread is. LOL
heathmcabee said:
Wow just realized how old this thread is. LOL
Click to expand...
Click to collapse
Hmmm, I hadn't realized that! Why the Hell did CirrusFlyer resurrect this thread?
I had the same problem and the problem ended up being my new dell xps core i7 tower. Use a powered usb hub such as your monitor with the usb hub ( if you have one) and it will solve your headaches. I am willing to bet money this will work, everyone I know that has had the same problem has solved it this way.
Sent from my SPH-D700 using XDA Premium App
The usb socket directly attached to my motherboard was the problem a powered usb hub for some weird reason made it driver up every damn time and still works today.
Sent from my SPH-D700 using XDA Premium App
Cpagent is 100% correct on the powered usb port causing issues. And that goes for multiple devices for an assortment of usb drivers... I have to deal with it all the time with my customers (that's assuming I've already exhausted every other software possibility... for this reason I only work on customers phones on an older xp 32 pc with proper hardware) it really ticks me off how little software developers.care about adapting basic drivers to be compatible with the machines most commonly used by the people who actually have to use said software/hardware ...
Lol.... /rant
Sent from my DROIDX using XDA App
Still nothing. CDC serial is not installed.
sly21 said:
Still nothing. CDC serial is not installed.
Click to expand...
Click to collapse
That one is a Pain in the ass. Took 35 minutes on my laptop!
Sent from my SPH-D700 using XDA App
I am very impressed with my Galaxy Tab 10.1, but I'm having a glaring problem: my PC won't detect it as a storage device. This is the one that came with 3.1 out of the box, and I assumed that it would connect to my PC and play perfectly with it. I guess I've been spoiled by how my HTC Evo always connected perfectly to my PC with no issues or no drivers for me to hunt down and install, because it didn't work.
Okay, no sweat, I just need to download the drivers and install them, right? I did just that as well. I connect the tablet to the PC (which runs Windows 7 64-bit), and the PC gives me notifications saying my device is ready to use, but I can't find it as a storage device at all under My Computer. I do find it in my "Devices and Printers" list, but it doesn't show up with the rest of my devices at the top (it shows up with unspecified devices or something at the bottom of the list with a generic-looking icon representing it).
Okay, I probably need to just uninstall the drivers and maybe reinstall them and try again, right? Did just that, no dice. The exact same thing happens. On the tablet, I also probably need to point out that the only thing I get is the "USB Debugging Detected" notification or whatever it says while Windows 7 doesn't pick it up.
So now I ask what everybody else did to get theirs recognized. And I already tried switching USB ports and checking for updates. No dice there, either.
Wow, I feel like an idiot after solving this problem, but just so I can spare anybody else who has the same issue the trouble of going through this, I'll post what the solution was for me.
Unplug the tablet and disable USB debugging on the tablet first, then plug it back in and it'll be picked up as a generic cell phone by My Computer. Hope this helps somebody in the future. Heh...
Honestly, I really didn't think that would solve the problem, and I did search beforehand and found nothing of the sort telling me that doing just that would have fixed the problem.
Hey, everyone. I browse XDA a lot but I've never really had a reason to post. I do now, however.
Basically what I'm trying to do is unlock and root my Nexus 7. I discovered Wug's Nexus Root Toolkit which seems to be the best way to go about the process. From all the hubbub about it, I figured it was going to be quick and painless. Lucky me, I was wrong lol. At least for me. All I needed was to get the ADB installed with the device so I could get started, then my adventure began.
You see, whenever I connect the device via USB with debugging mode on, my PC goes mad and the device automatically connects and disconnects itself in a rapid fashion. I cannot get it connected long enough to install the correct drivers for it, the usb driver found with the Android SDK, or whichever one's the Toolkit provides as well. If it's not in debugging mode, all is normal, and the Nexus 7 installs as a simple portable device (due to windows). However, I'm unable to update it's driver with the "android_winusb".
I am running Windows Vista Home Premium and looked up ways to disable the automatic driver installation, since Windows wants to install specific drivers, figuring that was the issue. The Local Group Policy Editor is not found in my versions of Vista, so I can't disable it that way. When I disable it in Hardware of Advanced System Settings, it simply just doesn't work.
My USB cables are fine, so it's not that. I've tried every drive method in the Toolkit, and have had mild success getting the ADB drive to install properly and have "Android device" appear in the Device Manager with the ADB listed. However for it to be listed, it must be in debugging and the problem remains, it wont stay connected long enough to do anything with it. Much less root, unlock, or backup...or anything for that matter. Then windows tries to install the unwanted drivers again...ugh.
The problem seems to be narrowed down to the debugging mode issue when connected. It's hopefully my only hurdle. Has anyone else had this issue, and if so, found a working solution? This has become very frustrating and not something I expected to endure at all. Having spent a few hours trying to solve this, I hope someone else out there can help me out from here. It'd be much appreciated!
MegaMac said:
Hey, everyone. I browse XDA a lot but I've never really had a reason to post. I do now, however.
Basically what I'm trying to do is unlock and root my Nexus 7. I discovered Wug's Nexus Root Toolkit which seems to be the best way to go about the process. From all the hubbub about it, I figured it was going to be quick and painless. Lucky me, I was wrong lol. At least for me. All I needed was to get the ADB installed with the device so I could get started, then my adventure began.
You see, whenever I connect the device via USB with debugging mode on, my PC goes mad and the device automatically connects and disconnects itself in a rapid fashion. I cannot get it connected long enough to install the correct drivers for it, the usb driver found with the Android SDK, or whichever one's the Toolkit provides as well. If it's not in debugging mode, all is normal, and the Nexus 7 installs as a simple portable device (due to windows). However, I'm unable to update it's driver with the "android_winusb".
I am running Windows Vista Home Premium and looked up ways to disable the automatic driver installation, since Windows wants to install specific drivers, figuring that was the issue. The Local Group Policy Editor is not found in my versions of Vista, so I can't disable it that way. When I disable it in Hardware of Advanced System Settings, it simply just doesn't work.
My USB cables are fine, so it's not that. I've tried every drive method in the Toolkit, and have had mild success getting the ADB drive to install properly and have "Android device" appear in the Device Manager with the ADB listed. However for it to be listed, it must be in debugging and the problem remains, it wont stay connected long enough to do anything with it. Much less root, unlock, or backup...or anything for that matter. Then windows tries to install the unwanted drivers again...ugh.
The problem seems to be narrowed down to the debugging mode issue when connected. It's hopefully my only hurdle. Has anyone else had this issue, and if so, found a working solution? This has become very frustrating and not something I expected to endure at all. Having spent a few hours trying to solve this, I hope someone else out there can help me out from here. It'd be much appreciated!
Click to expand...
Click to collapse
I had that problem too, and it was solved by plugging the usb cable at the back of your pc.
Leonhan said:
I had that problem too, and it was solved by plugging the usb cable at the back of your pc.
Click to expand...
Click to collapse
Now that you mention it, I have heard of certain USB ports not liking certain things. What a simple solution. You know, lol...it'll probably work. Thanks so much for commenting. I'll edit this post if all is well.
I would have edited my previous message, but I'm afraid I still need help and needed to bump this up.
I plugged the USB cable into the back of my PC and all seemed well. I was able to painlessly get the ADB all set up without any interruptions. Needless to say, I was excited and ready to unlock and root and...not so fast. After a short bit, the disconnecting and reconnecting bull****, for the lack of a better word, began again. Windows ceaselessly wants to install the damn drivers as the MTP or Camera, regardless if it failed or succeeded. Because of this, the device manager loses the Android Device drop down and the ADB Composite interface along with it. It just doesn't exist and therefore, I can't proceed with the Nexus Root Toolkit.
This is insanity. Is there anything I haven't tried that could remedy this? It shouldn't be this nerve wracking just to root a device, I swear...lol.
Any chance you have access to another PC' maybe a family member? That way you can rule out your PC as the problem.
Sent from my Nexus 7 using xda premium
zPacKRat said:
Any chance you have access to another PC' maybe a family member? That way you can rule out your PC as the problem.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Well, I did plug it into my girlfriends laptop once to see if it would act up, and with USB debugging turned on, it did not. That may be my last resort, but ideally, I'd prefer to use my own PC for any business such as this, and it irritates me when there's an issue that shouldn't even be that I can't solve. I'm sure some out there can understand that feeling.
So at this point, I'm just looking for a possible solution on my end. If there isn't one, then I guess I'll have to submit and abduct her laptop...lol
MegaMac said:
Well, I did plug it into my girlfriends laptop once to see if it would act up, and with USB debugging turned on, it did not. That may be my last resort, but ideally, I'd prefer to use my own PC for any business such as this, and it irritates me when there's an issue that shouldn't even be that I can't solve. I'm sure some out there can understand that feeling.
So at this point, I'm just looking for a possible solution on my end. If there isn't one, then I guess I'll have to submit and abduct her laptop...lol
Click to expand...
Click to collapse
There was a time when my aunt's galaxy tab 2 will act like this. What I did was turn off usb debugging first and let it install the drivers. Then I turned usb debugging on again and I didn't have the problem. It could also mean that the cable you got is faulty or somethin.
Leonhan said:
There was a time when my aunt's galaxy tab 2 will act like this. What I did was turn off usb debugging first and let it install the drivers. Then I turned usb debugging on again and I didn't have the problem. It could also mean that the cable you got is faulty or somethin.
Click to expand...
Click to collapse
Well, if I connect it with debugging off, it installs as a typical portable device and when I try to update the drivers with the winusb drivers needed, it doesn't install properly. So far, it must be connected to where it creates the section in the device manager "Unknown Devices" and appears in its drop down list. I'm still tryin' guys. Thanks for the help so far!
MegaMac said:
Well, if I connect it with debugging off, it installs as a typical portable device and when I try to update the drivers with the winusb drivers needed, it doesn't install properly. So far, it must be connected to where it creates the section in the device manager "Unknown Devices" and appears in its drop down list. I'm still tryin' guys. Thanks for the help so far!
Click to expand...
Click to collapse
Hmm, try this. Connect your device and use it as PTP not MTP. Then install your drivers.
Leonhan said:
Hmm, try this. Connect your device and use it as PTP not MTP. Then install your drivers.
Click to expand...
Click to collapse
Already attempted. It seemed to alleviate the connection issues for a little bit, but the drivers still wont install the right way.
bump.
was OP able to fix his issue?
jt.one said:
bump.
was OP able to fix his issue?
Click to expand...
Click to collapse
Not sure how you would have missed the OP replying to the last suggestion, what maybe 20 minutes before your post.
zPacKRat said:
Not sure how you would have missed the OP replying to the last suggestion, what maybe 20 minutes before your post.
Click to expand...
Click to collapse
OP might have handled it himself and forgotten to update his thread you know.
but yeah, thanks for replying to me and not contributing to the OP's thread :highfive:
Quite the coincidence we posted around the same time. But yeah, still giving me trouble. I will try to tackle it again tonight, but if I can't find a solution soon, I suppose I'll at least get the unlocking and rooting done on the laptop I spoke of, then for future stuff, try to get the ADB working on my PC.
You can do what i did and just download one of the toolkits to install the drivers.
Sent from my Nexus 4 using xda premium
jnewman1991 said:
You can do what i did and just download one of the toolkits to install the drivers.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Toolkits? You mean like Wug's? I am using his Nexus Toolkit, or trying to rather. The issue lies within getting the Nexus 7 to stay connected correctly as an "Unknown Device" in Device Manager, in which to properly install the drivers to get Windows to identify it as an "Android Device" and have the ADB recognized successfully.
win vista
vista it's junk win8 working well for me
vital982 said:
vista it's junk win8 working well for me
Click to expand...
Click to collapse
I actually enjoy Vista. It had a rough start, but still. I don't think it's Vista because my gf's laptop runs it too, and when I tried connecting and doing everything with it, none of the connecting and disconnecting crap happened. I'm thinking there's a setting or something I'm overlooking on my own PC that's causing it in particular to do it.
Hello.
Three weeks ago my Nexus 4 is recognized by my three computers (work, home and friend) like a drive. Now it is not anymore recognized by friend 's computer: I hear the sound of connection but no change in file manager. However it works fine on two other computers (home and work). In addition the Nexus 4 of my friend is always recognized by these three computers.
I tried to install N4 drivers on Friend 's computer. No change, my Nexus 4 is not recognized by friend's computer. I tried the debug mode too. No change. And the nexus 4 of my friend works on the three comptuters. Very frustrating .
These two Nexus 4 is updated with 4.2.2, in stock rom, not rooted, 16Go, v11.
Does someone could help me to solve this problem without saving my data and then restoring to factory values?:highfive:
Thanks.
I forgot to write that i used only one usb wire on the same usb port. To be sure that the problem is not the wire or the usb plug.
Do you currently have USB Debugging turned on? Turn it off and see what happens...the reason I say is that my work PC can either see is as MTP with USB Debugging off or through adb with it on - not both.
My Windows 8 Pro laptop at home works fine for both at the same time...worth checking out
Maybe try to uninstall the driver using the device manager?
Sent from my Nexus 4
EddyOS said:
Do you currently have USB Debugging turned on? Turn it off and see what happens...the reason I say is that my work PC can either see is as MTP with USB Debugging off or through adb with it on - not both.
My Windows 8 Pro laptop at home works fine for both at the same time...worth checking out
Click to expand...
Click to collapse
nhatters said:
Maybe try to uninstall the driver using the device manager?
Thanks for your answer. I will try your solution today. But I don't understand why the other nexus, unlike mine works fine on every computer.
Sent from my Nexus 4
Click to expand...
Click to collapse
Envoyé depuis mon Nexus 4
EddyOS said:
Do you currently have USB Debugging turned on? Turn it off and see what happens...the reason I say is that my work PC can either see is as MTP with USB Debugging off or through adb with it on - not both.
My Windows 8 Pro laptop at home works fine for both at the same time...worth checking out
Click to expand...
Click to collapse
nhatters said:
Maybe try to uninstall the driver using the device manager?
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks i will try your solutions tomorrow. But these solutions doesn't explain why one Nexus 4 works on the friend 's computer and the other Nexus 4 doesn t work: same wire and same usb plug.
I plugged the nexus on my computer. And I unistalled the driver of nexus in my device manager unplugged and plugged again the nexus. And then let windows recognize the nexus and install his own compatible driver. Thanks nhatters.
The problem was that for run application named carbon I had to install in computer first the adb driver and carbon for computer. And this driver does not recognize my nexus which have not carbon (for mobile install).
i had the same problem few minutes ago .. i just turned USB Debugging on and voila the PC detected my nexus 4.
Aha i had the same problem i just lowered the notification shade selected usb device n selected camera option and reverted back to the media transfer and that fixed it
I am having the same issue but nothing seems to work and I dont even hear the connection sound in windows. I've tried uninstalling and installing drivers with sdk, device manager, and the other thing in windows which is callew dew I think and nothing no success, also I have tried to disable usb sebugging and mtf media storage and nothing. Is the only thing left to is buy a new micro usb cable?
juan_carlos__007 said:
I am having the same issue but nothing seems to work and I dont even hear the connection sound in windows. I've tried uninstalling and installing drivers with sdk, device manager, and the other thing in windows which is callew dew I think and nothing no success, also I have tried to disable usb sebugging and mtf media storage and nothing. Is the only thing left to is buy a new micro usb cable?
Click to expand...
Click to collapse
Same problem for me on Windows 7. I have tried everything - different cables, different ports, enable/disable USB debugging. Even uninstalled drivers etc. It is getting detected on Windblows and is showing up in the taskbar as an USB device with a green mark. But it is not showing up as a drive or the MTP device. Frustrating to no end!
im gonna try to research in microsoft website which drivers are not originally installed in my computer and delete all the wird ones maybe some other driver from another hardeare like another cell phone or something is interfering. Hope I dont delete something that will make my computer not work right.
Same here, I can no longer transfer any files on to my Nexus 4 anymore. I'm using a PC and it no longer reads it. Only fast boot and adb on recovery works.
Sent from my Nexus 4 using xda app-developers app
reiko09 said:
Same here, I can no longer transfer any files on to my Nexus 4 anymore. I'm using a PC and it no longer reads it. Only fast boot and adb on recovery works.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It's not the same because I've tried adb and nothing. Your problem can be fixed by modifying google drivers. In the other hand I tried a friends nokia phone with same usb cable and started installing drivers right away.. Mine does nothing, not even a connection sound just charging. so It's not the cable. I'm starting to think the micro usb port got damaged or something really wrong with the rom but still I've tried to see if reseting the phone works and nothing.
Seems like its an issue with 4.2.2. Since last week my N4 was acting very strange. when I connect to my pc; It would connect and disconnect every second. After checking in Device Manager; my Nexus 4 was listed under SAMSUNG Android Phone . I end up uninstalling it (plus check delete driver software). Then I rebooted my computer. It reinstalled the driver and now its working. Thought my wire was broke.
This worked for me, it shall work for everyone else
Open the start menu and type in device manager and click on it, it should npbringba window up. Now at the stop it should say android device or something similar, drop down that section and right click to delete "Google ADB Interface" which was for me should be for you also. After make sure you check the box in the confirmation to delete the driver. Reboot your PC plug in your device and enjoy!!!