Database Users

Just formatted and now my pc won't see my epic!!

I just got a win 7 x64 ultimate install disk. Now it won't even see my phone....I downloaded the correct drivers ad still nothing. I was on win 7 x32 ultimate and installed the 32 bit drivers and all went well. Now I'm on x64 bit version and with x64 drivers it ain't find my device!!!! I'm at a loss here.
Sent from my SPH-D700 using XDA App

did you get it resolved, I had the same issue. I then move to the rear usb port, you need to look for the safley remove media icon on the task bar. It should be there. when you plug the phone in the epic should show up. If not goto disk manager in windows and make sure that the drive letter that the epic is trying to use isnt already in use, i fit is change it.
The other thing is to make sure on the phone that you have selected the correct method, IE charging etc In my case the phone would show up as raw format yet it would show up fine on another PC. all i can think of is that it was something buggy with the USB.

Try a different USB port and if that doesn't work try a different cable.
If it still doesn't work try removing the drivers for the device manually, reboot the system and reconnect the device. It should automatically discover the drivers for you running Windows 7.
Also when you connect the phone to the system does the menu pop up asking you how you would like the phone to respond to the connection (IE. Mass Storage, Phone as Modem and whatever the 3rd option is)?

RRexA3 said:
Try a different USB port and if that doesn't work try a different cable.
If it still doesn't work try removing the drivers for the device manually, reboot the system and reconnect the device. It should automatically discover the drivers for you running Windows 7.
Also when you connect the phone to the system does the menu pop up asking you how you would like the phone to respond to the connection (IE. Mass Storage, Phone as Modem and whatever the 3rd option is)?
Click to expand...
Click to collapse
I've never gotten those options ever. Nothing pops up on my phone. I thought it was weird since I've heard about them, but never seen it, mac or pc. Any way this is connected to usb debugging being on?
Sent from my SPH-D700 using XDA App
Edit: yup, menu came up when I turned USB debugging off.

Glad the menu came up! The question is did the computer pick up the device?
Sent from my SPH-D700 using XDA App

Nope not even with the correct samsung epic win 64bit drivers. I couldn't for the life of me get then to see my phone. Reinstalled win 7 ultimate 32bit. Saw it right when hooked up! So I guess ill stay with my x32 edition :-(
Sent from my SPH-D700 using XDA App

You probably just got some drivers crossed. Manually removing the drivers should have fixed it versus reimaging the system =/

RRexA3 said:
You probably just got some drivers crossed. Manually removing the drivers should have fixed it versus reimaging the system =/
Click to expand...
Click to collapse
Thought this too...but I found 3 diffrent set of epic 6 bit drivers and no go...I'm up and running now. So ima stick with x32bit for now.
Sent from my SPH-D700 using XDA App

USB Mass Storage Issues - Vibrant

When I plug my Vibrant in by USB on WinXP I am getting a device not recognized error. I get nothing when plugging into a Mac. I've tried multiple cables and I have changed the USB options to each option.
I have rooted the phone and installed the GPS fix.
Any suggestions for fixing this would be appreciated.
Thank you

Load the galaxy s drivers, will work after that
http://forum.xda-developers.com/showthread.php?t=728929
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App

What about for Mac OS? The phone doesn't show up when I mount the cards. Is there a way to get mass storage to work on a Mac that doesn't involve turning on USB debugging?

I'm not a mac person, sorry, hopefully someone else can chime in on that.
Edited, if you go to the thread i linked, the op states for linux and mac the android sdk drivers should work, hope that helps.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App

When you plug it in are you sliding down the notification bar and selecting the USB Connected > Mount option?
As well when you are done you have to Unmount when you are done.

Yeah, like kizer said too, mount the device. I was assuming that step is s.o.p.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App

kizer said:
When you plug it in are you sliding down the notification bar and selecting the USB Connected > Mount option?
As well when you are done you have to Unmount when you are done.
Click to expand...
Click to collapse
Yes, I had a G1 for years and that always worked perfectly. The only way to get my Vibrant to show up though is to use USB debugging mode.

I just did some quick googling and it seems mac users are doing exactly what you said you don't want to do, setting usb debugging on, and that seems to be a quick fix. I'm sure there is more info out there in cyberspace, but if debugging works, I say go with it. I always have debugging turned on, incase I need that oops adb action.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App

BossDj said:
Yeah, like kizer said too, mount the device. I was assuming that step is s.o.p.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App
Click to expand...
Click to collapse
With the OP having one post who knows if he/she really knew it had to be mounted. LOL Figured it wouldn't hurt just to mention just in case.

BossDj said:
I'm not a mac person, sorry, hopefully someone else can chime in on that.
Edited, if you go to the thread i linked, the op states for linux and mac the android sdk drivers should work, hope that helps.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App
Click to expand...
Click to collapse
When i use it on my Mac, i have to enable USB debugging. Then both drives (internal and SD) pop up just fine.
So it looks like someone answered this, just confirmation then.

Another theory
My Vibrant has mounted normally and without any problems on WinXP sp3 and Win7-64 systems, but I have also run into the occasional system where it will not work at all.
On the systems where things worked normally it was never required that I load a special Samsung USB driver for the phone. The standard mass storage drivers included with Windows worked fine.
My new theory is that there may be a drive letter collision issue in some cases. On the laptop that I use with my phone 90% of the time the phone always mounts as drive G: and H:.
On other machines I have noticed that the phone always seems to mount as G: and H: even if E: and F: are available. I'm not sure how/why it always gets mounted using those letters. It may somehow be defaulting to that because G: and H: were the first letters available on the first system I plugged it into.
I have a Win7-64 desktop machine that will not currently allow the phone to connect. This particular machine already has G: and H: assigned to hard drive partitions.
I will probably experiment with temporarily changing the letter assignments to see if I can get the phone to mount. It's worth a shot I guess.

Sorry, I didn't go into as much detail as I could have.
I've installed those drivers listed here as well as any other I could find. I've tried USB debugging mode, changed all the USB modes listed. I've mounted and unmounted the SD cards using the settings menu when doing this.
Is it possible that there is some background service that should be running? Or is it possible that something in the firmware is screwed up? I guess it's also possible that the USB plug itself is messed up?
Thanks for the help.
I used to use this forum years ago when I had a HTC WinMo phone, it seems to have lost any record of past posts due to inactivity.

As kizer stated in his post, are you mounting from the prompt on your phone's notification bar? Once plugged into your pc or mac, you slide down the notification bar from the top of your home screen, click on the usb prompt then select mount. Thats the only step you didn't list that may have been missed.
Edited - the prompt in the notification area may say mass storage, my home pc fried last week so i cant test it to get you the specific verbage.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App

BossDj said:
As kizer stated in his post, are you mounting from the prompt on your phone's notification bar? Once plugged into your pc or mac, you slide down the notification bar from the top of your home screen, click on the usb prompt then select mount. Thats the only step you didn't list that may have been missed.
Edited - the prompt in the notification area may say mass storage, my home pc fried last week so i cant test it to get you the specific verbage.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App
Click to expand...
Click to collapse
I don't get any prompt at all. At this point I will just install CM6.1 when it comes out and hope that fixes the issue. It's usable for now. I can transfer files using WiFi File Explorer for now.

It helps if you know if you are USB 1.0 or 1.1 or 2.0....or even 3.0.
Also, are the USB ports powered ?
Are the USB ports on the computer in question filled with dust and dirt ?
Contacts corroded ?
Are the ports recognized by the operating system correctly (you know, drivers loaded since it's old arsed WinXP) ?
Do you undertand how to operate a computer at a higher level than just being able to install viral apps ?
Malware ?
Trojans ?
I could go on all day.
It works fine here, on Win7x64, WinVistax64, and *nix.

That is bizarre you should get a least something in your taskbar.
Click for larger photos if you like.
Heres what my looks like and of course I have the taskbar pulled down so you can see it.
Below that is the box you would click to say connect it.

I did have a freind who didn't realize he could pull down the notification bar. Could that be the case here?
Op, you do know you can pull down the bar at the top of your screen, the one with your clock and battery icon etc., put your finger up there and swipe in a downward motion.
Sent from my SGH-T959 using XDA App

n2ishun said:
It helps if you know if you are USB 1.0 or 1.1 or 2.0....or even 3.0.
Also, are the USB ports powered ?
Are the USB ports on the computer in question filled with dust and dirt ?
Contacts corroded ?
Are the ports recognized by the operating system correctly (you know, drivers loaded since it's old arsed WinXP) ?
Do you undertand how to operate a computer at a higher level than just being able to install viral apps ?
Malware ?
Trojans ?
I could go on all day.
It works fine here, on Win7x64, WinVistax64, and *nix.
Click to expand...
Click to collapse
I have tried this on a corporate IT managed WinXP system (running Kapersky AntiVirus) and a currently updated Snow Leopard MacBook. I could give details all day as well. Both are in good condition and very likely not the issue.
Seriously, if you have nothing useful to say don't say anything at all.

vkewalra said:
I have tried this on a corporate IT managed WinXP system (running Kapersky AntiVirus) and a currently updated Snow Leopard MacBook. I could give details all day as well. Both are in good condition and very likely not the issue.
Seriously, if you have nothing useful to say don't say anything at all.
Click to expand...
Click to collapse
they don't understand i had this issue too man and i fixed it.
first go to that link and download those drivers... use the uninstall app to uninstall the drivers off your computer.
while your doing that go into your phone setting>applications>usb settings
make sure it says "ask on connection" (you can change it later) go back and go to development to turn on usb debugging.
reinstall drivers, connect phone wait for the drivers to load. the un-connect phone turn debugging off.
and it was fixed for me.
hope this helps

"usb device not recognized" with two diff. win7 installations.

as title states.
It doesn't seem to be the samsung drivers
as I have uninstalled and reinstalled.
but the Android drivers. I have no Android drivers installed anymore
(the 3 of 4 that installs)
therefore i lose adb connectivity
*This has happened on 2 different Windows 7 installations. (switching between 2 different hdds, on this laptop)
I have usb debug on ofcourse.
I have uninstalled reinstalled latest samsung drivers.
I have installed pdanet drivers.
I have turned off phone, while connected then boot up. still no fix.
I am using acs froyo dk17. But this happened with dk05 as well.
Is there a fix for this?

I've had this problem twice. The way I fixed it was to wipe the sd card. Its a pain but that's what fixed it
Sent from my SPH-D700 using XDA App

If not a driver problem (doesn't sound like it is) the next *usual* suspect would be the usb cable. The samsung cable that shipped with these phones is crap. I got a 6' belkin one on amazon for $8 that has worked flawlessly.

Make sure you're not using a USB port that's on a hub or daughtercard. It should be one that's directly on the motherboard.

I kept fiddling with settings and rebooting both phone and computer and got past this once on my old win7 box. On my new one, I got nowhere after an hour or so. Worked first thing with the same cable on my win xp machine.
Plug your phone into a USB1 only hub, or on the same channel as a usb 1 keyboard or mouse and it will detect just fine... it won't really be useful because it won't be able to flash still (I believe it should detect as a composite device with several facets and only some of those are usb1-only compatible). I believe that the underlying problem is a bad implementation of the usb spec on one of the usb2 only parts, but I didn't feel like digging any deeper. I might try a win xp vm on the same physical hw to see if I can narrow it down to a win7 usb2 + device usb2 compatibility issue. Might be worth making sure our win7 patches are up to date, too.
Sent from my SPH-D700 using XDA App

Thanks for the replies guys.
The usb trick won't work because it's a laptop. And I tried all four of them. I only have windows 7 machines. One being a ultra sff and has like 12 usb ports. It hasn't failed me yet, but happens on the laptop.
It wouldn't hurt to get another cable, a longer one. And my sd is maxed out, I will pull it instead of format.
Thanks all
Sent from my SPH-D700 using Tapatalk

I had this problem. Plugged into the back instead if the hub and reinstalled everything. Now it's working like a charm on all usb ports. Really odd problem.
Sent from my SPH-D700 using XDA App

I had this problem. I was using a USB extension cable that was a bit long. All the other phones and USB devices worked fine with it. EPIC did not want to. I got the impression that EPIC needs more power from the USB port than most of these other devices. For me, skipping the USB extension cable did the trick. I also used a powered USB hub and that worked well too. You might want to try different USB ports. Some may provide more power than others. Also try a powered USB hub (some are built into monitors) if you have access to one.

I had the same issue with my laptop as well. It is most likely the cable. The samsung one is crap. I tried every port and installed the usb drivers a dozen times with no success. Used the cable from my wifes blackberry and worked on the first try. Just pick up a new cable. Try monoprice.com they have awesome deals.
Sent from my SPH-D700 using XDA App

I just had this problem, I switched my cable and then it worked fine.

hayabusa1300cc said:
as title states.
It doesn't seem to be the samsung drivers
as I have uninstalled and reinstalled.
but the Android drivers. I have no Android drivers installed anymore
(the 3 of 4 that installs)
therefore i lose adb connectivity
*This has happened on 2 different Windows 7 installations. (switching between 2 different hdds, on this laptop)
I have usb debug on ofcourse.
I have uninstalled reinstalled latest samsung drivers.
I have installed pdanet drivers.
I have turned off phone, while connected then boot up. still no fix.
I am using acs froyo dk17. But this happened with dk05 as well.
Is there a fix for this?
Click to expand...
Click to collapse
Also make sure your antivirus is off although that's likely not the culprit. Do you install the drivers as administrator?
Try a new cord. If that doesn't work, try deleting/uninstalling the device and/or hub from the device manager - plug the phone in, letting win7 do its worst by not recognizing it, then open the device manager and find the usb hub. try deleting/uninstalling. unplug the phone and scan for hardware changes. I think this may force windows to reinstall the drivers for the usb hub. Disclaimer, it's been a while since I spent significant time fooling with windows computers so take this advice at your own risk - I'm feeling my way like an old man with cataracts trying to find his way around his long-lost childhood home. in the dark. With unfamiliar furniture. In an earthquake. While in a wheelchair. With flat tires....
My computer did this for a while and now it doesn't although it's certainly possible I changed the cord I was using.

The best way to get drivers to work is install PDAnet IMO..
I had driver problems upon driver problems.. swapped cables, etc.
went through all the motions that you all are describing here and what fixed it for me was installing PDAnet. Worked like a charm.
Hope this helps.

I agree about using pdanet for drivers. Unfortunately this problem isn't with the driver not being installed correctly. I got it on one machine and not another, using the same friver. In fact I got it to work on the same machinewith the same driver ... just different ports (one was stuck in usb1/ohci nd worked, the usb2 port never worked on one machine and a usb1 port never worked on a different one).
Sent from my SPH-D700 using XDA App

warlar12 said:
I just had this problem, I switched my cable and then it worked fine.
Click to expand...
Click to collapse
This worked for me when I had the problem. This will be the second time I had a usb cable go bad on me. Maybe I shouldn't buy those cheap ones from China...

I've had this problem with numerous cables on Dell E series laptops with 3 Epics and a Moment. For the life of me I couldn't get the phone to be recognized when using the USB ports on the left side of the machine. Plugged it into the ones on the right and have never had a problem. I think with the Dells it's a low current issue on the left side ports. The shorter the USB cable the better off you'll be if it is a low current problem.

thanks but i did alot of that last night and today, uninstall/reinstall drivers, usb hubs.. nothing
i may need to try another cable because i am workign on a friends epic sunday.
bilestoad said:
Also make sure your antivirus is off although that's likely not the culprit. Do you install the drivers as administrator?
Try a new cord. If that doesn't work, try deleting/uninstalling the device and/or hub from the device manager - plug the phone in, letting win7 do its worst by not recognizing it, then open the device manager and find the usb hub. try deleting/uninstalling. unplug the phone and scan for hardware changes. I think this may force windows to reinstall the drivers for the usb hub. Disclaimer, it's been a while since I spent significant time fooling with windows computers so take this advice at your own risk - I'm feeling my way like an old man with cataracts trying to find his way around his long-lost childhood home. in the dark. With unfamiliar furniture. In an earthquake. While in a wheelchair. With flat tires....
My computer did this for a while and now it doesn't although it's certainly possible I changed the cord I was using.
Click to expand...
Click to collapse

It HAS to be the power differences NOT cable.
Same cable as I charge with, plugged into the front of the computer (hub).
Plugged into the back of the computer recignized the first time.
=USB power

In my case, tried several micro USB cables, no dice. Tried my laptop and desktop, no dice. Tried USB hub or direct to PC usb ports, no dice. Device manager shows the right comm port but all the one-click roots i've tried can't find the phone. USB storage has never mounted for me from day one either.
Sigh, never had this issue with any other Android phone.

Finally figured out my issue. I had set it to "modem" while doing something else in an epst menu rather than "pda". Since I corrected that, works dandy.
I feel so stupid.
Forgive My Brevity. To Be Or Not To Be...

Would using my friends droid x cable work with the Samsung epic?
Sent from my SPH-D700 using XDA App

[Q] Aaaaarrrrgh. USB drivers not working under Windows 7/64

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

[Q] Nexus 4 charging but doesnt connect as mtp adb or fastboot

Hello sir,
I have a nexus 4 stock unlocked and android 4.4.2 KOT4H i have a issue that my phone is connected for charging on pc but doesn't show up as mtp adb or even fastboot , however it connected for sometime during the day and when i rebooted it ..!! It was just charging and again no adb fastboot or mtp! Please help me solve the issue

Most likely issues would be either drivers, USB cable or USB port. Try a different PC, try to reinstall drivers, try another cable, check to see if any physical damage to USB. Maybe test to see if adb over WiFi works ad well to help narrow down the issue
Sent from my Nexus 4 using XDA Premium 4 mobile app

I have the same problem often too. What I do to fix it ranges from so many things. Some times a simple reboot helps (PC and phone) sometimes a different PC helps. Sometimes switching to PTP instead of MTP helps adb. Sometimes its the driver. Use a universal adb driver. Or use nexus 4 drivers. Or sometimes it's the SDK. Redownload the SDK and install the Google USB driver things. I have never got wireless adb working so you can try it. Sometime switching to USB 2.0 or 3.0 helps. Or switching to the ones on the front of my case helps, Even though I have a good motherboard. Try using adb in recovery.
Oh and last thing. It might be your custom kernel/rom (if your running one). Or USB fast charge is on. Just a possibility. Hope this helps.
Sent from my Nexus 4 using xda app-developers app

no i tried everything in my windows pc it doesnt even connect as adb now
I cant connect my device from adb or fastboot , the phone is just charging, the usb cable is fine i tested other phones too.. I and what is fast charging?

Fast charging means sucking more power from the USB port to charge faster. Anyways do other android devices show up when you type adb devices with others plugged in?
Sent from my Nexus 4 using xda app-developers app

yesss every device is visible
gravitysandwich said:
Fast charging means sucking more power from the USB port to charge faster. Anyways do other android devices show up when you type adb devices with others plugged in?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes all devices are mounting as mtp adb and fastboot but not mine

Make sure you got good drivers, like the ones I mentioned. And make sure you have ADB on(about phone > tab build number, then in developer options enable adb) and try changing/ messing around with storage mounts ( storage > tap option/menu at corner> USB computer connection) that's all I got. hope I help. I don't what's wrong though...
Sent from my Nexus 4 using xda app-developers app

yesss drivers are correct
gravitysandwich said:
Make sure you got good drivers, like the ones I mentioned. And make sure you have ADB on(about phone > tab build number, then in developer options enable adb) and try changing/ messing around with storage mounts ( storage > tap option/menu at corner> USB computer connection) that's all I got. hope I help. I don't what's wrong though...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes i have everything , two days ago everything was working with my phone and then suddenly when i connected my phone i saw that the phone was just charging and not even connected as mtp!

Can anyone help me! :'( :crying:

so there's hardware problem then

RolF2 said:
so there's hardware problem then
Click to expand...
Click to collapse
What kind of hardware problem is this do need to get the charging port connector replaced?

looks like connector fault if sometimes it's working & sometimes not ...

RolF2 said:
looks like connector fault if sometimes it's working & sometimes not ...
Click to expand...
Click to collapse
I doubt it, could be though. Thank god the USB port on the nexus 4 is easily replaceable. In this situation, go download a toolkit (I know, they are bad), and install the adb drivers from there. And try doing some adb/fastboot commands in he toolkit. Also try relocking/unlocking the Bootloader/rooting because that involves fast boot and adb commands. Last thing I would do is try a different PC. Even if all your phones work on the PC your using right now.
Sent from my Nexus 4 using xda app-developers app

im having this exact problem and have tried everything i can think of.....leads diff pc drivers but nothing

why do so many of these threads just stop???????????ive tried EVERYTHING. ALL I CAN MAKE ANY PC SEE MY PHONE IS AS AN UNKNOWN DEVICE...........DIFFERENT PCS USB LEADS ETC...................WHAT IS WRONG WITH THE PIECES OF ****??????????????

Wow, all caps... That gets people flocking to help quickly...
Sounds like you need to uninstall then reinstall proper drivers manually or move to a Linux PC
Sent from my Nexus 4 using XDA Premium 4 mobile app