Related
Anyone know how to sync with Windows 7???
I've tried to install Windows Mobile Device Center 6.1, but it don't recognize my phone.. And ActiveSync won't even be installed due to compability reasons. (Doh, it's Win7)
I really like Win7, so it would be great to sync the phone
Try another cable or something, the mobile center should work.
ChumleyEX said:
Try another cable or something, the mobile center should work.
Click to expand...
Click to collapse
But the mobile is charging =/ So i don't think something is wrong with the cable and it worked just fine in XP (ActiveSync). And when I connected the mobile first time, the PC recognized it and installed the drivers for the mobile and the ActiveSync started on the mobile. Should it start on the phone when mobile center is running on the PC?
So does that mean you didn't try anothe cable? Because if you had researched this sort of thing (aka searched) you would find that the cables do this quite often.
phjott said:
But the mobile is charging =/ So i don't think something is wrong with the cable and it worked just fine in XP (ActiveSync). And when I connected the mobile first time, the PC recognized it and installed the drivers for the mobile and the ActiveSync started on the mobile. Should it start on the phone when mobile center is running on the PC?
Click to expand...
Click to collapse
i don't know what is the issue for you as i have win7rc1 and i can sync fine using the mobile device center.
If you are using 64bit Windows 7 then you need to download the updated drivers for the HTC. I am not sure exactly where Microsoft has these located, but it automatically downloaded and installed the new USB drivers that it needed just the other day for me......
Works excellent. I was using the 32 Bit version of Windows 7 before this and even though its based under Vista couldn't get it to synch up.
I have Win7 64 bit...with internet already established through another source, when I plugged in my tilt, it found the driver and installed it and has worked flawlessly ever since.
Works fine for me too on Win7 x64.
First, try another cable. USB has 4 connections, only 2 are needed to make it charge, but for communication it needs all 4. Maybe try another USB port on your PC as well.
And as said before, make sure you have an internet connection so it can download the drivers.
WMDC is already built in with Win7, so don't install any other versions from Microsoft Download Center.
Works fine for Win7 x64.
but Win7 x86 "NO"
you can use virtual XP mode for 32bit version
Updates?
Hi. I had this same problem following a hard-reset of my phone. After a while of searching I found that an update (designed for Vista) is available on the microsoft website. Downloaded, installed and sync worked first time. Yey
It should work with Win 7 RC 32 bit - does for me!
mouradlayeb said:
Works fine for Win7 x64.
but Win7 x86 "NO"
Click to expand...
Click to collapse
Then you're doing something wrong (such as not having the TyTN II correctly connected to your desktop PC or not having internet access on it to download whats required perhaps). I plugged my TyTN II into my Win 7 RC (32 bit) PC and after a bit of hardware detection and some automatic downloading it works (allbeit still with slow file tranfers but at least the UI is better than Win XPs Activesync). Welcome to xda-dev by the way
I think that it matters wether or not it's Windows7 RC.. Right after it came out someone was using the beta and it wouldn't work for them.
ChumleyEX said:
I think that it matters wether or not it's Windows7 RC.. Right after it came out someone was using the beta and it wouldn't work for them.
Click to expand...
Click to collapse
I was wondering the same but as the RC version is still avail for free until 20 Aug, anyone with the Beta should be formatting and installing this instead. Grab it while you can
I am running RC 7100 and I have no problem syncing.
Only issue I have now is, when the phone is connected, it won't let me delete or replace any .xml files through file explorer. This was never an issue with XP and Active Sync.
i just found what the problem is. Open settings on phone, then connection tab, open usb to pc... and there uncheck (enable advanced network function)
With it checked it didnt work on mine win7
sipols said:
and there uncheck (enable advanced network function)
Click to expand...
Click to collapse
I had that problem when I first bought my TyTN II but it was because I was attempting to connect it to my ancient USB 1.1 ports on my Pentium III. As soon as I installed a modern (but cheap) NEC chipset USB 2.0 PCI adapter card, I found I could connect fine either with or without advanced network functionality enabled. This is a USB port hardware compatibility issue rather than a Win 7 issue and I suspect even if users have Win XP on the machine that behaves this way, they'd still get the exact same response.
your speaking about USB 1 when others is speaking about Win7. If you dont know win 7 is the newest MS OS. So, i belive, all who use win7 have USB2. So there is question why you mention usb1?
And i didnt sad whole story. I had used phone with win xp for long time with that check on, and with one cabler... now on win7 i tried 2 diferent cables with that check on. Didnt work. Took it off and it started to work. So its Win7 issue.
sipols said:
your speaking about USB 1 when others is speaking about Win7. If you dont know win 7 is the newest MS OS. So, i belive, all who use win7 have USB2.
Click to expand...
Click to collapse
Thanks for the explanation but my Pentium III is capable of running (or should that be walking) Win 7 RC and it has USB 1.1 ports (as well as a USB 2.0 card now). Given Win 7 RC was avail free of charge - don't know if it still is, I got mine in June, there'll be people who get it just to see what it looks like, even though the hardware isn't up to ideal spec.
I don't know what ports were being used in your case because as you mentioned, full details weren't supplied and we didn't have the whole story - we still don't know. Glad you've resolved the issue in your case but in a modern PC which can comfortably run Windows 7, I wouldn't typically expect this to be an issue. If the hardware is struggling to keep up or has USB ports of dubious quality/performance, then thats a different matter.
Sounds like win7 (my main OS now days) communicates with the USB ports in a different manner than XP or the other OS's. Good to know.
I've been using ADB the last couple of days to install apps on my Captivate and all of the sudden it stopped working today.
When I type 'adb devices' the phone comes up right away, but it shows offline.
I have tried reinstalling the drivers and Android SDK, but no luck. I've searched around and found some others with this issue, but haven't really found a fix that works for me.
Any idea why ADB would just stop working like that? I even performed a factory reset of the phone and put everything back to defaults.
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Man, I really thought I was going crazy.
wimbet said:
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Click to expand...
Click to collapse
What the hell is that about!? I wish all these companies would stop trying to break from standards by proprietizing common cables.
I can't get the drivers to work. Where did you get yours?
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Man, I really thought I was going crazy.
Click to expand...
Click to collapse
Yeah I buy that, I couldn't even get the thing to try and connect at all with out switching usb connections on my computer.
stock cable works. I just rooted and ran into that problem. In order to get around it if you cant get a diff cable, make sure that b4 you connect your phone to your pc you turn off your internet so it doesnt auto dl the drivers. b4 u connect, dl the drivers for your phone from the root thread. Plug your phone into ur comp with the internet off and close any pop ups. Go to device manager look for the notification labled usb or captivateand right click and select update. Select search from file on disk or select file (something like that, i forget) and scroll and select the folder where you extracted the usb drivers. Make sure the checkbox that says search subfolders is checked and click next to install. two more drivers will pop up in device manager after u install the first one. Repeat the same procedure for both of them and then you should be able to use adb just fine to root.
Just wanted to further confirm that using a different microusb cable works! I keep reinstalling the drivers but it kept showing the device was offline. Then I tried my old Nokia N85 cable and it worked like charm! So weird how usb cables aren't made equally, unless Samsung designed the cable to prevent using adb?
I had this issue for a little while, but I installed the Samsung Kies software (which contains drivers) and uninstalled the ADB drivers I had originally downloaded. It's worked like a charm since then.
Go to SamsungApps.com and then use the canada site, as the software isn't really available in the US yet.
I have had no problems using the stock cable on my Laptop and work PC, both are Win 7 32bit. The same cannot be said for my my main home PC which is Win 7 64bit. Neither the stock cable nor an after market cable worked with ADB.
For the 32bit OSes I installed the Kies software and the usb device gets installed correctly. for the 64bit OS, I installed the Kies software but could get the phone to connect correctly. I then tried to install the 64bit drivers that are floating around the web. The 64 bit drivers worked enough to get the phone connected to the PC but when I tried to query "adb devices" the phone would always appear as offline. I've tried several things: install/uninstall drivers and software on the PC, restart the PC and Phone, change cables. Nothing seems to help on Win 7 64bit.
It seems to me that there might be a bug in the 64bit driver, though I have no proof of a bug.
I am going to keep playing with the 64bit OS until i figure it out or get so annoyed a that I just give up.
I'll be using my Win 7 32 bit laptop until I get the 64bit PC to work.
TimF said:
I have had no problems using the stock cable on my Laptop and work PC, both are Win 7 32bit. The same cannot be said for my my main home PC which is Win 7 64bit. Neither the stock cable nor an after market cable worked with ADB.
For the 32bit OSes I installed the Kies software and the usb device gets installed correctly. for the 64bit OS, I installed the Kies software but could get the phone to connect correctly. I then tried to install the 64bit drivers that are floating around the web. The 64 bit drivers worked enough to get the phone connected to the PC but when I tried to query "adb devices" the phone would always appear as offline. I've tried several things: install/uninstall drivers and software on the PC, restart the PC and Phone, change cables. Nothing seems to help on Win 7 64bit.
It seems to me that there might be a bug in the 64bit driver, though I have no proof of a bug.
I am going to keep playing with the 64bit OS until i figure it out or get so annoyed a that I just give up.
I'll be using my Win 7 32 bit laptop until I get the 64bit PC to work.
Click to expand...
Click to collapse
i've been able to install .apk's with my win7 64-bit ADB :O
all i did was install Samsung Kies.
i don't think i've ever had a problem...?
EDIT: i'm using the cable that came with it and no problems yet.
I'm running win 7 x64 and Kies did the trick for me. I haven't had a single issue connecting my phone since I did that.
Sent from my SAMSUNG-SGH-I897 using XDA App
Justa dding to the anecdotes.
I was having problems with the included cable using the front USB. It would show as Device Offline, also the charging wasn't very strong.
I switched to the onboard USB at the back of the case, and adb worked fine with the included cable.
Looks like I'll be picking up a couple extra USB cables so I won't have to continuously do the desk dive everytime I need to use it somewhere else.
1. I installed the kies drivers first and it would say offline when i checked the device through the cmd prompt.
2. I then installed the adb drivers and it then said the device was online.
3. i then rooted the phone and went on my way. i then tried it a second time and it said device offline.
4. nothing changed during this time except that i turned off debug mode, changed it to mass storage and plugged it back into the usb to transfer some files.
5. on returning to debug mode it no longer tells me the device is online. i have tried different USB ports as well.
6. i deleted the drivers, and reinstalled and it still says offline.
very frustrating.
wow. i forgot to try plugging it into another USB port. that worked. sorry about previous post.
I am running Windows 7 Home Premium 64bit on my laptop,
I installed the samsung 64bit drivers, it was an installer i found on the web, not the kies installer packaged driver one.
i changed my setting on my captivate to Mass Storage.
I mounted usb and everything works, by that I mean i was able to ADB like no tomorrow without any issues.
Then I made the mistake of installing Samsung Kies and that messed up my previous drivers and I wasnt able to ADB to my phone. I had to uninstall Samsung Kies and my phone still wasnt being found I still couldnt ADB.
my solution to fixing was restarted my phone and computer, without my phone connected to USB i re-installed the Samsung 64bit Driver Package, then hooked up my phone made sure Mass Storage was selected and Mounted USB and bam was able to ADB again.
hope this helps! also i have been doing videos helping people with issues with samsung's captivate on youtube, youtube.com/johnnyzappone if anyone wants to check em out, if anyone has any suggestions please let me know and id be happy to release a video!
I resolved my issues, I plugged the stock cable into one of the rear usb ports and the device is now available on my main PC Win 7 64 bit.
wimbet said:
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Click to expand...
Click to collapse
Confirmed this made my device stop appearing as offline with adb.
How it is even possible that the cable prevents (only) adb access on the PC, I have no idea.
I have windows 7 and mac osx and I can use adb with both using the stock USB.
i have debugging active.
lol @ the samsung cable.
i've 2 indentic cables here, one doesn't work. plugged in the other one and this one works...
maby its just a strange issue on windows, next time try to pull out the cable and put in back in then connect your device again this should work.... :s
because earlier the cable just worked fine and now it doesn't.. so good luck xD
joelpt said:
Confirmed this made my device stop appearing as offline with adb.
How it is even possible that the cable prevents (only) adb access on the PC, I have no idea.
Click to expand...
Click to collapse
also can confirm PITA
I tried to do a search for this, and nothing came up for me. I recently purchased a new Laptop, running Windows 7 64 bit. My Nexus One will not install any of the drivers on such. I have downloaded the drivers from the Android Development, yet I am unable to actually use my Nexus One for ADB or for even Disk Mode. It keeps stating it is unable to install the drivers. I haven't ever tried to use my N1 with any 64 bit OS before this (except linux and mac, but that just seems to work) and my 32 bit OS's seem to work perfectly fine. Anyone else having this issue? Or possible solution?
I had the same problem when i went to root mine. I tried every tweak and hack and fix an update nothing worked.. but send someone at android community.com had it..
If you can wait a few hours i will post it when i get home..
Please don't even think of putting windows mobile on your nexus one. That is against Android law!
Sent from my CM6 Nexus One using XDA App
Keep trying and make sure you install the correct drivers. Try from another download source and don't let windows install the defaults.
naturefreak85 said:
I tried to do a search for this, and nothing came up for me. I recently purchased a new Laptop, running Windows 7 64 bit. My Nexus One will not install any of the drivers on such. I have downloaded the drivers from the Android Development, yet I am unable to actually use my Nexus One for ADB or for even Disk Mode. It keeps stating it is unable to install the drivers. I haven't ever tried to use my N1 with any 64 bit OS before this (except linux and mac, but that just seems to work) and my 32 bit OS's seem to work perfectly fine. Anyone else having this issue? Or possible solution?
Click to expand...
Click to collapse
I had the same problem. After hours trying things and searching for solutions in Google, finally MY solution was activate the USB Debug Mode
I hope this works for you too!
WaPeR32 said:
I had the same problem. After hours trying things and searching for solutions in Google, finally MY solutions was activate the USB Debug Mode
I hope this works for you too!
Click to expand...
Click to collapse
Same with me. USB Debug mode fixed it.
Im on Windows 7 x64 Pro. I havent had any problems getting ADB to work with my machine. I downloaded the SDK from the website and ran the sdk setup.exe. It will fail the first time, you have to close it and go to settings and FORCE HTTPS. once that is done. reopen it and reject everything except Device Drivers. This will download the drivers. When I connect my phone with debug mode on windows auto picks up the drivers and installs it.
I got it running on my machine ..windows64bit .. took a lil while but like someone said but it can be done ..or if all else fails install droid explorer ..and use its sdk directory
I had the same problem. In my case it was because I was plugging it into a usb port that was built into a card reader in my tower. As it turned out the usb port was not putting out enough power, so I decided to try some ports that are on the bottom of my case and the problem went away.
Each usb hub has to share power, so if you have several usb devices that pull some juice workin on the same hub you can try to get onto another hub via another port.
Win7 64 bit
I had the same problem. For me the solution was to use a legacy/older USB port on my laptop and not a highspeed one.
i am having this issue as well.
i have looked everywhere, and tried many solutions. i am lost.
my windows 7 32bit laptop sees the N1 is connected but cannot install or even find any drivers for it. i have USB debugging mode checked. i have tried ADK, using the USB drivers it provides, no luck there.
my N1 isn't rooted yet, and i'd like to trick it out. but i have to get access to it first. any help y'all can provide would be amazing.
it may be possible this is a windows 7 issue, with drivers and such. but i've been looking around for a while and can't find a solution anywhere.
I'm running Winxp SP3, Captivate with Cog2.8b3
I had installed the USB drivers for 32bit provided on these forums (before connecting my phone), then connected my phone and had windows throw up the "usb device not recognized" message. There's no android/samsung/etc. listing under the device manager.
Anybody else had this problem, or know how to fix it?
I had similar issues and reinstalled and uninstalled everything multiple times and that didnt fix anything. My suggestion would be to try a new USB cable or each of your USB ports.
My cable that came with my captivate was actually bad. It would charge the phone and even attempt to register with Windows by eventually fail with the same error you listed above.
MrSewerPickle said:
I had similar issues and reinstalled and uninstalled everything multiple times and that didnt fix anything. My suggestion would be to try a new USB cable or each of your USB ports.
My cable that came with my captivate was actually bad. It would charge the phone and even attempt to register with Windows by eventually fail with the same error you listed above.
Click to expand...
Click to collapse
I've tried each of my ports; the cable had worked previously, fairly recently, but I have a new windows install. I'll try a new one when I get back from school.
Try removing all bits of the USB Driver after un-installing them.. then try re-installing. XP is a pita with USB devices sometimes. Well windows in general for that matter.
Alright, so i have ARHD on the most recent 22.0 i think.. Can't recall exactly but that shouldn't be the issue anyway. Today, out of the blue, all three of my USB ports, two 2.0 one 3.0, are giving me a Device has Malfunctioned error, and not pulling up the internal storage in My computer as usual. It is allowing charge, from what i can tell, and it is working with the same cord/ports on a different computer, so i do not think its hardware.
Now i have uninstalled/reinstalled HTC sync manager, multiple times, I've uninstalled the usb drivers in the Device manager, and reboots, multiple times, and i've tested other USB equipment on the ports, works fine. Does anyone have any further suggestions on how to get my computer to recognize my HTC one properly?
I'm running 64bit Windows 8, on an ASUS Viviobook.
Edit: I've also did a system restore, which was unsuccessful in fixing the problem
ZeroAlphawolf said:
Alright, so i have ARHD on the most recent 22.0 i think.. Can't recall exactly but that shouldn't be the issue anyway. Today, out of the blue, all three of my USB ports, two 2.0 one 3.0, are giving me a Device has Malfunctioned error, and not pulling up the internal storage in My computer as usual. It is allowing charge, from what i can tell, and it is working with the same cord/ports on a different computer, so i do not think its hardware.
Now i have uninstalled/reinstalled HTC sync manager, multiple times, I've uninstalled the usb drivers in the Device manager, and reboots, multiple times, and i've tested other USB equipment on the ports, works fine. Does anyone have any further suggestions on how to get my computer to recognize my HTC one properly?
I'm running 64bit Windows 8, on an ASUS Viviobook.
Edit: I've also did a system restore, which was unsuccessful in fixing the problem
Click to expand...
Click to collapse
I have two 64 bit windows 8 machines and have the same problem, except mine has never worked on either machine. It is really driving me crazy. I have not been able to find a solution anywhere.
SortaSmart said:
I have two 64 bit windows 8 machines and have the same problem, except mine has never worked on either machine. It is really driving me crazy. I have not been able to find a solution anywhere.
Click to expand...
Click to collapse
Did you guys look at this: http://forum.xda-developers.com/showthread.php?t=2256359
I haven't tried (still Windows 7), but who knows.
Had same issue with my first HTC one. Turned out to be a hardware issue. My brother also had same issue. Wouldn't charge either. The odd thing was though is the phone would charge while completely off and also be recognized by PC in fastboot.
Sent from my HTC One using xda premium