Related
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
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
Hey all-
Just got the Razr M and am loving it so far. On a side to note to this topic, I have to give a shout to the CyanogenMod team. I was using CM7 on my old Incredible and it really gave the phone new life. One of the reasons I picked the Motorola was the fact that they seemed to have the closest to 'stock' android out there. I have noticed that a lot of the things I loved about CM7 are included in the new JB operating system in the new Razr. I'm not as much of an expert at many of you, so I don't know who was talking to whom there, but it really seems like Android got the best bits of the CM7 release installed stock in my new phone. I'm sure I'll find gripes and get the urge to root this one after a while, but I had to give credit to the CM team for a great product.
Anyway, here's the reason for my post. I was stuck trying to transfer files between the phone and PC to no avail, much like many other people I came across on the net while researching the problem. I ran across a solution at another forum that worked for me (I don't know why, but there it is...). I went to the development tab and chose 'allow USB debugging' and 'allow mock locations'. For some reason that got the Motorola connect software (which I installed out of desperation and takes me to Verizon's unwanted backup website) to realize my phone was there, and also gave me full access to file transfers.
If this is old news, please disregard, but at the risk of sounding like a noob I'll post it in case it helps anyone else.
Cheers!
Ryan
I have tried that numerous times and even reinstalled the drivers a few times and my phone still won't show up in my computer, what os are you running? I'm running XP pro still no dice..
Sent from my rooted RAZR M via XDA app
Drivers
hellknight4206 said:
I have tried that numerous times and even reinstalled the drivers a few times and my phone still won't show up in my computer, what os are you running? I'm running XP pro still no dice..
Sent from my rooted RAZR M via XDA app
Click to expand...
Click to collapse
I'm running Vista 64 bit. You may mock me now!
I just let Motorola install the drivers, didn't go to the website and add extras or anything like that. Sorry about the issues, good luck!
Another thought?
You know, I forgot about this, but it bears mentioning. I have one USB port on my PC that operates at 1.1 speeds (or whatever it was before 2.0). It was one of those fancy cases where there were all kinds of extra goodies on it, but for some reason just this one lone port wouldn't take anything at 2.0 or better speeds for the life of me. When I plugged my data cable into that by accident, it timed out with an error. When I used a proper USB 2.0 port, everything went find\e. So, it may be a long shot, but you might want to check that you're on a fast USB port; otherwise, the timeout error sort of looks like a complete hang/crash...
I am pretty sure all my USB Ports are 2.0 I could be wrong tho, I installed the drivers with the software from the site that maybe my problem actually, I'll try again tonight
::Edit:: ok so I found out my USB Ports are not 2.0 I had my EVO 4g plugged in charging and when I got home my PC had a dialog stating that my device would perform better on a hi-speed USB port, that's a bummer cuz it is the only port I have
Sent from my rooted RAZR M via XDA app
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.
Help please... I got it unlocked and rooted but can't load anything on it... can't seem to get the drivers right
Sent from my Galaxy Nexus using Tapatalk 2
if your on a CM based ROM then you need to unlock developer options and then check "enable USB debugging"
click on settings and about. keep clicking about like 8 times and it will tell you, you have unlocked developer mode. click usb debbuging.
or
I would check drivers under control panel and see if you have all your drivers up to date. It should say Android device or Nexus 10. You shouldn't have any yellow flags.
I have USB debugging enabled. In on a windows xp laptop and these drivers are crazy. I tried deleting all of my old ones and when I plug in my nexus sometimes MTP pops up... Sometimes Android Adb pops up... sometimes just adb pops up. Honestly I don't even know how I got it rooted but I'm glad I did. Used wugs toolkit
Sent from my Galaxy Nexus using Tapatalk 2
Memp2Atl85 said:
I have USB debugging enabled. In on a windows xp laptop and these drivers are crazy. I tried deleting all of my old ones and when I plug in my nexus sometimes MTP pops up... Sometimes Android Adb pops up... sometimes just adb pops up. Honestly I don't even know how I got it rooted but I'm glad I did. Used wugs toolkit
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I believe that Microsoft really hates Android. I have the N4, N7, and the N10 and every one of them was a major pain in the butt getting Windows to recognize them. Of course none of them can use the same drivers..
Same problem here, diver will show but won't recognize to the point where I can get any files transfered... help?
HillsRider said:
I believe that Microsoft really hates Android. I have the N4, N7, and the N10 and every one of them was a major pain in the butt getting Windows to recognize them. Of course none of them can use the same drivers..
Click to expand...
Click to collapse
Yeah but my galaxy nexus works with no problem
Sent from my Galaxy Nexus using Tapatalk 2