Related
This is for everyone out there who upped to WM6 on wizard models and found ActiveSync not recognising your fone over USB. Download ActiveSyncMode.cab (sometimes named ActiveSyncMode.sa.cab) and install it on your Fone. Run it - Start/Programs/ActiveSyncMode.exe -
http://www.utstar.com/pcd/downloads/ActiveSyncMode.sa.CAB
Select 'USB Serial Sync Mode'. Now try connecting your fone and it should work.
I tried almost 50 posts and advices over 3 days and this one worked like a charm. I know there must be other issues with other fones which have different solutions. Please feel free to add to this thread all/any verified solutions.
hi,
i have tried it, but it doesnt work. do you have made spacially things to get i work ?
Not really. Installed ActiveSyncMode. Ran it and selected USB mode instead of RNDIS mode. This fixed the problem for me with a WM6 upgraded 8125 and 2 other friends with Original ROM 8125 and Original ROM MDA.
i unchecked "Enable advanced network functionality" in USB to PC settings on my phone and got activesync to work for me when i was having trouble
us687008 said:
This is to everyone out there who upped to WM6 on wizard models and found ActiveSync not recognising your fone over USB. Download ActiveSyncMode.cab (sometimes named ActiveSyncMode.sa.cab) and install it on your Fone. Run it - Start/Programs/ActiveSyncMode.exe -
http://www.utstar.com/pcd/downloads/ActiveSyncMode.sa.CAB
Select 'USB Serial Sync Mode'. Now try connecting your fone and it should work.
I tried almost 50 posts and advices over 3 days and this one worked like a charm. I know there must be other issues with other fones which have different solutions. Please feel free to add to this thread all/any verified solutions.
Click to expand...
Click to collapse
Hi! I've got the same problem, and i was solutionated with reinstall the activesync. So go to microsoft site, and download the activesync 4.5 again. After that try to sync your pda, and maybe its solve.
THANKS VERY MUCH
YOU SOLVE GREAT PROBLEM
us687008 said:
This is for everyone out there who upped to WM6 on wizard models and found ActiveSync not recognising your fone over USB. Download ActiveSyncMode.cab (sometimes named ActiveSyncMode.sa.cab) and install it on your Fone. Run it - Start/Programs/ActiveSyncMode.exe -
http://www.utstar.com/pcd/downloads/ActiveSyncMode.sa.CAB
Select 'USB Serial Sync Mode'. Now try connecting your fone and it should work.
I tried almost 50 posts and advices over 3 days and this one worked like a charm. I know there must be other issues with other fones which have different solutions. Please feel free to add to this thread all/any verified solutions.
Click to expand...
Click to collapse
THANK YOU!!! What exactly does this cab do to fix the problem?
us687008 said:
This is for everyone out there who upped to WM6 on wizard models and found ActiveSync not recognising your fone over USB. Download ActiveSyncMode.cab (sometimes named ActiveSyncMode.sa.cab) and install it on your Fone. Run it - Start/Programs/ActiveSyncMode.exe -
http://www.utstar.com/pcd/downloads/ActiveSyncMode.sa.CAB
Select 'USB Serial Sync Mode'. Now try connecting your fone and it should work.
I tried almost 50 posts and advices over 3 days and this one worked like a charm. I know there must be other issues with other fones which have different solutions. Please feel free to add to this thread all/any verified solutions.
Click to expand...
Click to collapse
I had to reinstall WM6 and now ActiveSyncMode.sa.CAB no longer fixes my connectivity problem. I'm getting fed up with WM6.
I have tried everything else and will now try this. I did not realize that this was such a problem, until I started researching to solve my own problem. So good luck to me.
Fixed it with my own build. So far. I still have to try and sync with another computer. That is where the biggest problem has been for me, is syncing with two computers.
Under Vista 64, I normally have McAfee firewall at the highest setting and also have Windows Firewall on.
At first, after upgrading to WM6, I could not sync. I then found some registry fix procedures and tried them but it did not work. I then installed ActiveSyncMode.sa.cab and it allowed me to sync. Maybe that combined with the prior registry fix might have allowed me to sync.
However, after I uninstalled WM6 and reinstalled it, I could not sync anymore. I installed ActiveSyncMode.sa.cab again, but it did not work this time. I did not try the registry fix this time because I can't find the procedures, which I originally found online. I can't remember how to find them again.
I then turned off both Windows Firewall and McAfee firewall and I was able to sync again.
I then reinstalled Windows Mobile Device Center while having the firewalls off, hoping it would allow the installations to complete properly.
I then turned on Windows Firewall but it was still blocking the sync.
I restored Windows Firewall back to default and it made it worse. I then had to reinstall Windows Mobile Device Center and was able to sync again with Windows Firewall on. Often I would have to disconnect the cradle to establish reconnection.
Next, I needed to figure out how to turn on McAfee firewall and allow it to sync.
I then contacted McAfee and they told me to exclude Universal Plug and Play (UPNP) port 5000 and Windows File Sharing (NETBIOS) port 137-139. It didn't work exactly until I lowered the firewall one level. What all this networking stuff means, I don't know. I'll have to do more searches on them.
I now need to figure out how to put McAfee firewall back at maximum level while still allowing me to sync.
a_ok2me said:
Under Vista 64, I normally have McAfee firewall at the highest setting and also have Windows Firewall on.
At first, after upgrading to WM6, I could not sync. I then found some registry fix procedures and tried them but it did not work. I then installed ActiveSyncMode.sa.cab and it allowed me to sync. Maybe that combined with the prior registry fix might have allowed me to sync.
However, after I uninstalled WM6 and reinstalled it, I could not sync anymore. I installed ActiveSyncMode.sa.cab again, but it did not work this time. I did not try the registry fix this time because I can't find the procedures, which I originally found online. I can't remember how to find them again.
I then turned off both Windows Firewall and McAfee firewall and I was able to sync again.
I then reinstalled Windows Mobile Device Center while having the firewalls off, hoping it would allow the installations to complete properly.
I then turned on Windows Firewall but it was still blocking the sync.
I restored Windows Firewall back to default and it made it worse. I then had to reinstall Windows Mobile Device Center and was able to sync again with Windows Firewall on. Often I would have to disconnect the cradle to establish reconnection.
Next, I needed to figure out how to turn on McAfee firewall and allow it to sync.
I then contacted McAfee and they told me to exclude Universal Plug and Play (UPNP) port 5000 and Windows File Sharing (NETBIOS) port 137-139. It didn't work exactly until I lowered the firewall one level. What all this networking stuff means, I don't know. I'll have to do more searches on them.
I now need to figure out how to put McAfee firewall back at maximum level while still allowing me to sync.
Click to expand...
Click to collapse
After doing all the steps above, I found that all I needed to do was lower the McAfee firewall level one notch to be able to sync. However, I'm still going to figure out why I had previously been able to sync at the maximum security level. There must be some exclusion that got remove that I need to add again.
Activesync and HTC s620 issues.
This issues is driving me completely insane, So far this thread is about the only related info on the problem too. I find it hard to believe there aren’t more people out there with these issues, anyway here’s were I’m at:
Got a HTC s620 Smartphone from BT, Active sync simply didn’t work from day one and me being an IT support guy I haven’t been able to resist going back to the issue.
For over a week I have made pretty much no progress at all, I can’t find a activesyncmode.sa.cab file for my phone that works yet so got nowhere with that, the HTC website is about as useful as a chocolate fire guard.
The first leap of progress was spotting a trick on here of disabling the advanced network functionality on the phone its self.
It was baffling me at first why my computer was picking up the phone as if it was a network adapter. (And trust me I tried all sorts of in depth stuff down that avenue). It makes sense now though that the Smartphone can be setup to act as a network adapter/modem. Hence now I’ve disabled the advanced network functionality on my phone Active sync instantly make noises and hey presto ‘Connected’ and then a few moments later I’ve now got some other critical error
So my quest continues, but I will get to the bottom of this if it kills me!
So for the record, anyone with a HTC s620 Smartphone running Windows Mobile 6, before you do anything else do this:-
Start
Settings
6. Connections
7. More…
4. USB to PC
(Remove the bloody tick from box) Enable advanced network functionality
I will report back with my next hurdle…
OK, as much as I’d played around with my firewall it would turn out that this is the second culprit causing my problems. I tried installing Activesync on my Laptop and Desktop and had the same errors, however the only thing those to computer have in common is the Iolo System Shield installed. Last night to just ensure I wasn’t going mad, I tried it on my wife’s laptop and hey presto! It worked first time. So naturally, I’ve uninstalled the Iolo System Shield from my computer and bingo, worked straight away.
This is annoying however, because I did everything from the Microsoft Help setting up exceptions etc. in my firewall. But there you go.
In brief:
Check your device has the advanced network functionality disabled.
Uninstall your 3rd party firewall and test to pin point the cause, then you know what you’re dealing with.
Just a second thought of advice, one of the first things I tried was disabling the firewall, from my experience that wasn’t enough, it had to be uninstalled to get it to work. Before anyone else goes down the hair pulling road of trying anything and everything under the sun, uninstall your firewall/system guard software. At least if it works after that you know exactly what is causing the problem.
Then getting it to work with the firewall installed is something you can focus on possible in conjunction with the software vendor.
I fixed teh same problem by unchecking the advanced box but .....
after oving back to wm5, I cant connect as well. I look for the working solution from WM6, but I cant find the menue to disable the advance usb connection.
It looks like that is the problem to sync with vista 64
Hope somebody has a idea.
thx in advance
My USB connection to activesync stopped working. (although at my second pc it still works OK)
It works via InfraRed though!
I think this USB problem started when I was trying to connect via bluetooth.
Don't you just hate ActiveSync!?
Well, maybe the problem is with Windows XP... because it doesn't recognizes the PDA.
Anybodies help? Thanks in advance.
No file ActiveSyncMode.cab !
Help
No worries, new link:
http://www.pcdphones.com/downloads/ActiveSyncMode.sa.CAB
Also attached to be safe
would be a shame to let a useful thread go into some archive, so I'm resurrecting this oldie.
Also, I remedied this activesync issue with a more straigtforward fix. Fresh flash of 6.5. After deleting all the USB devices in the device mgr (didn't help), I saw there was a WM6.5 setting for default behavior on PC Connection (or something similar to that). Changed it from "setup" to "sync" & that silly white toggling screen went away and allowed a flash back to 6.1.
Hello people.
I recently reinstalled my Win7 and I wanted to connect it with my X1, but when I plugged the phone in for the first time, Windows started downloading some weird drivers (RNDIS?) instead just opening the device control panel thing. Now I'm pretty much stuck and can't connect my phone to my PC (I get the connection error sound every time), except for the disk mode.
I've serched for some answers here on xda as well as on the internet and all the fixes I found either don't work, are already applied or open up new problems for me.
Here's what I've tried already:
Rebooting PC countless times
Turning off the advanced network settings in usb to pc menu on X1,
Reinstalling WMDC countless times
Downloading some weird WMDC updates from microsoft download center
Configuring the registry (Enum key) - getting access denied error to everything I'm trying to do there
Opening the device manager in Windows - It's just blank.
About the software and ROM status, my X1 was just HR'd and I've installed just some basic stuff like the performance pack (Advanced Config + SKTools), MortScript and S2P.
I know that the problem here is rather related to PC, but I hope you guys still can help me, as I'm running out of ideas (and sanity).
Sorry for my english (not my native language), and please do help me if you can.
Same problem here.
So far I've been able to troubleshoot it a little.
First off RNDIS is the regular WinMo driver. So nothing weird there.
Secondly WMDC does work when you run the app as an administrator (on my end anyways). That is in no way a solution though... just a workaround.
I now need to pinpoint the part that needs the actual admin rights.
I'm going to keep on trying to find the answer and I hope more people will help.
Thanks for replying for my post.
Launching WMDC isn't the problem for me though. It starts up fine, it just doesn't connect with the phone.
Keeping fingers crossed for a solution, and thanks again.
I managed to get it started too now.
Again, as an administrator it runs all fine and dandy, but no sigar as a user.
So after I get it started no connection whatsoever. Still looking...
Got it!
Installed the drivers through SCCM at system deployment. Then WMDC installs perfectly.
It still wouldn't run though. And this was because of a policy which was enabled: WPD Device: deny read/write access
Enabling write access solved my problem.
hi henk!
I had the same problem.
I changed the policy, then win7 installed drivers for the xperia, it recognizes the phone, I'm able to navigate into the memory card...
But the wmdc don't see my xperia is connected, and if I try to transfer some music from win7 to my xperia, it's very slow(1b/s)!
Have you got any idea?
Had you the same slow speed?
Ok, now I'm going into my third day with this phone, and I'm really struggling to find a way that it has made me happy. I mean, yeah, I like the OS and all, but Sprint still hasn't gotten back to me on whether they're going to send me a free Airave (I spend half the time in my home roaming). I had to reset the device yesterday to get it to connect to Marketplace - even though my account has never said anything but US (last time I left the country was in the Navy 21 years ago) - and even though I could connect to marketplace on Zune software, my phone wouldn't connect to it. Now I've got that working, by resetting the phone.
Now I can't get the phone unlocked. My developer account has been approved, identity verified, and the next step in my process is unlock my phone. I have tried all the tricks I've found so far: start phone, unlock the lock screen, turned off a bunch of services on my PC (like SQL, IIS, and more), reset my phone again, touch marketplace on the phone while connected so it says "connected" on the screen... Between all this and the lousy reception I get at home, I'm ready to just chuck this thing back at Sprint and say, "Thanks, but no thanks." The one thing keeping me from doing that is that Verizon is going to get the Trophy, and I want a phone with a keyboard. I've had keyboards on all my WinMo phones, and don't plan to stop now. I just wish this phone was available on VZW. I'm going to stick it out as long as I can, but iff I don't have an improved experience by day 28, Sprint gets it back... </rant>
Ok... Have I missed any other steps in getting this phone to connect to the Developer Phone Registration tool?
Have you tried following the directions here:
http://social.msdn.microsoft.com/Fo...s/thread/bfa70370-4926-4086-ad0e-febe716b8bf0
Yes, many times.... I never get past step 4.
Someone just told me an another thread that you have to be verfied through GeoTrust and to do that you must first create and submit an app that you have developed.
After you submit the app, supposedly GeoTrust will contact you via email and have you verify some personal information.
Make a fake app. That's all you have to do. Make one, then submit it. This will generate a claim number with GeoTrust. Trust me, I had to do this myself...
Have you got your certificate from msdn yet it takes a couple of days, once you get your certificate your account will be unloced
thealanshow said:
Make a fake app. That's all you have to do. Make one, then submit it. This will generate a claim number with GeoTrust. Trust me, I had to do this myself...
Click to expand...
Click to collapse
I just finished this. Hopefully by monday all will be well
My account has already cleared GeoTrust, and the next step is to unlock my phone. I'm not a student, but it wouldn't matter - I can't get that far. The reg tool doesn't even detect my phone.
If you're getting the dreaded "Check that the Zune software is running blah blah blah" message, this one is a PITA to deal with. From what I've seen poking around on the interwebs, it's hitting a good number of people. It happened to me too.
I have 2 systems that are identical hardware wise, and running 64 bit OSes.
I have 1 machine running a 32 bit OS (it's a much older system).
I was finally able to unlock the phone without any issues at all on the 32 bit system (after swapping out my phone and nearly a week of struggling with it) the very first time I tried.
I'm loving the phone, especially with it being unlocked, but it was a fight until I tried it on that last machine.
Poke Microsoft about it. The more they hear about it and the more information they get about it the faster they'll be able to fix it (that assumes the problem is even on their end).
I've heard using a USB hub (or if you're already using one then NOT using it) has helped some people. *shrug*
Thanks for all the suggestions - I appreciate them. I have yet to get my phone to get past the check zune... blah blah blah error, with the exception of one time. Here's what I did...
I reset my phone, got past the intro, added my live account, hooked it to the computer, let it sync with Zune (I had deleted the phone's proflie), opened the reg tool, and it found the phone. I entered my login info, and got the dreaded 0x64 error having to do with time on the phone.
Several posts I found had to do with people getting past this by using a different internet connection and finding success. Well, I have a rather odd internet connection going on. I live right behind my church, just beyond wireless range from the pastor's router. So here's what I have:
Scientific Atlanta DSL modem/router combo - pastor's connection
Buffalo high powered router running DD-WRT sitting on the platform (closest part of the building to my house), repeating the pastor's signal.
Buffalo high powered router running DD-WRT sitting in my computer room, repeating wireless to my house, and serving as wired router to the server and the HTPC.
Pastor's is 192.168.1.1, the one on the platform is 192.168.2.1, and the one in my house is 192.168.3.1, so they are all separate networks, each using the one upstream of it as a gateway.
So, given my success connecting to the phone, I walked over to church, phone still connected to the computer, connected to the pastor's router, and by this point in time, I can no longer connect to the phone.
I suspect that there is some update that Sprint is pushing that causes this problem, so I repeated the process several times, each time deleting the Zune profile, resetting the phone, going through enough of the startup to get to the settings, and putting it in airplane mode, then connecting in the specified order, allowing the new profile to be created, and still failing to connect to the phone from the reg tool.
Over on the App Hub forums, there are several of us with this problem, and a Microsoft team member said that they believe that it is something specific about the Sprint Arrive, and they are looking into it.
My main gripe about this whole thing is that since Sprint is a latecomer to the game, all the posts I'm finding about this are like six months old. Many people have overcome this problem, so you'd think that Microsoft would have figured out the problem by now, and fixed it.
I hope to get this figured out soon, as I am presently unemployed, and spent my $99 to join the App Hub, hoping to make a bit of money there until I get a job. I'm working on something, but until my phone is unlocked, I can't put my confidence in testing solely with the emulator.
Thanks for the tips guys. I do appreciate it.
I've heard really good things about the HTC arrive, I hope it works out for you. Who knows, it could be something NoDo related (because to the best of my knowledge those phones come with NoDo stocked on). I kinda hope it is, it would take the sting out of the fact that so many of us can't our hands on that update! haha ;-)
Yes, it does come with NoDo. It's interesting, takes a bit of getting used to, but it seems to work well. I love the phone. It feels more solid than my TP2. The only thing is that I wish the screen tilt wasn't spring-loaded. I got used to not using it most of the time on my TP2, so it's taking some getting used to on here.
Oh, frustration of all frustrations! I just grabbed my wife's phone and tried it for kicks. It took me all of 15 seconds to unlock her Sprint Arrive. So I know the problem isn't my computer. WHY WON'T MY PHONE WORK?????
(oh, and if it makes any difference, she's installed WAY more apps than I have)
did you try going to msdn?
My MSDN subscription has expired, but I have posted on App Hub forums. MS thinks it is something specific to the Sprint Arrive, but who knows?
If anyone else has had this problem, there is an official workaround posted on AppHub, but for those who don't have access to that forum, here's the copy/paste:
Re: Cannot register developer phone (HTC Arrive)
Reply Quote
Hi Folks,
There is now an understood issue with respect to the HTC Arrive that may be the cause of your problem. It can affect both developer unlock as well as the ability to update the phone. A KB article is in the works but here is the gist of it for developers having trouble unlocking the phone:
Windows Phone 7 Developer Unlock Tool cannot detect the HTC Arrive Phone
Abstract:
This article applies to developers of Windows Phone 7 applications who are testing their application using the Sprint HTC Arrive, model number PC93100, OS build 7389 or 7390. Developers may find that they are unable to unlock the Sprint HTC Arrive phone using the Windows Phone Developer Unlock Tool, for the purpose of deploying their applications to the phone for testing. This article offers a remedy.
Symptoms
The developer completes these steps to register the phone:
1. Registers through the App Hub as per the steps described in the App Hub registration walkthrough here.
2. Downloads and successfully install the latest version of the Windows Phone Developer Tools.
3. Owns an activated Sprint Arrive in which they personalize their settings (including date and time, and selecting a language).
4. Registers the Sprint Arrive with the same Live account they used in the app hub registration.
Next, the developer follows these steps for Developer specific registration:
5. Connects the Sprint Arrive to the developer's PC with the USB cable included with their device.
6. Ensures that the Zune software is running/open.
7. Launches the Windows Phone Developer Registration Tool.
8. The registration tool ultimately fails to detect the phone upon launch, reporting the following message:
"Unable to connect to phone. Please check that the Zune software is running and that the Zune's sync partnership with your phone has been established."
Cause
This occurs due to a specific state setting in the HTC Arrive that results in the phone not being able to make a desktop passthrough connection. This state condition can be mitigated by following the steps below.
Resolution
Use the following workaround.
1. If connected, unplug the phone device from the computer.
On the phone device:
2. Press the Windows button.
3. Press the right arrow button (on the top right of the screen) or swipe from right to left to expose the application list
4. Scroll to and select “Settings”.
5. Scroll to and select “Cellular”.
6. Select “Change Network Profile” and wait for this operation to complete (<-- this is a key step; you don't need to actually change it).
7. Press the Back or Windows key to exit the “Settings” menu.
After completing the above steps, follow through with the registration process:
8. Connect the Sprint Arrive to the development PC with the USB cable included with the phone device.
9. Launch the Windows Phone Developer Registration Tool (Zune software must be running).
10. The window titled "Windows Phone Developer Registration" appears which establishes a connection to the phone device and the following status message: "Status: Phone ready. Please enter your Windows Live ID and password and click Register to begin".
11. Enter the App Hub registered Windows Live ID and password, and then press the "Register" button.
12. The following status message appears in the window:
Status: Your phone has successfully been registered.
Click to expand...
Click to collapse
Thank you hopmedic that fixed it for me
this was driving me nuts and the info here solved it thanks
Thanks it worked.
Done the workaround, but nothing for me, still have the 0x64 error.
My phone was relocked after one year of AppHub. But now I can't unlock it again..
Also tried to deelete the phone in the device list on my account and use a proxy VPN network. I'm ttired of this. :/
http://www.mobiletechworld.com/2011/01/25/enable-tethering-on-htc-windows-phone-7-devices/
Trying this now.
eduncan911 said:
http://www.mobiletechworld.com/2011/01/25/enable-tethering-on-htc-windows-phone-7-devices/
Trying this now.
Click to expand...
Click to collapse
It says you need to have a developer unlocked phone and also have chevron.
Either a developer account, OR Chevron. Chevron only works on the older OS, and not the newer.
A $99 investment for a developer account is a small price to pay to load any application you want onto the phone (including c++ code to get to that Bluetooth radio!). You even get a nice little XAP deployment tool.
-E
eduncan911 said:
Either a developer account, OR Chevron. Chevron only works on the older OS, and not the newer.
A $99 investment for a developer account is a small price to pay to load any application you want onto the phone (including c++ code to get to that Bluetooth radio!). You even get a nice little XAP deployment tool.
-E
Click to expand...
Click to collapse
well you try it? and how is it working?
Has anyone got this to work? My Arrive is developer unlocked but I can't get the driver to show up in Device Manager on Windows 7 64bit. It seems to connect to my laptop but then no internet connection on the laptop from my arrive.
Thanks for any help,
Peacock93
eduncan911 said:
Either a developer account, OR Chevron. Chevron only works on the older OS, and not the newer.
A $99 investment for a developer account is a small price to pay to load any application you want onto the phone (including c++ code to get to that Bluetooth radio!). You even get a nice little XAP deployment tool.
-E
Click to expand...
Click to collapse
i am a student, and i got a free developer account via dreamspark. how can i do this?
I can't wait until tethering is an easier process for WP7
peacock93 said:
Has anyone got this to work? My Arrive is developer unlocked but I can't get the driver to show up in Device Manager on Windows 7 64bit. It seems to connect to my laptop but then no internet connection on the laptop from my arrive.
Thanks for any help,
Peacock93
Click to expand...
Click to collapse
Same here. has anyone got this to work?
I can't make it work.
Anyone have any new info on tethering the Sprint HTC Arrive?
I spent about 3 hrs on this today. Sprint arrive developer unlocked tried on my windows xp 32bit. It appears the drivers dont want to take. It says not recognized or something along those lines. Its a fairly common problem on the other thread but i have some ideas hopefully ill get to try in the upcoming days.
I have had some success. If you read the dfrouter thread than you are familiar with the process. 2 drivers must be installed on the pc first for it to work. I have the usb modem driver installed after messing around with the file. If i can get the other driver to go i believe ill be able to tether.
This modified driver is running on windows xp and appears to be ready. If anyone has a xp 32bit pc and please pm and we'll see if the driver works for you as well.
If I get the other driver to go ill tether and upload everything.
progress
I spent a few hours on trying to get the vcom driver working last night to no avail.
-on my first attempt i was able to get the driver to be recognized by the pc as the htc diagnostic tool but at the last screen it always said failed.
-on my second attempt i was able to get the driver installed but i dont think it was done properly because it was not recognized as the htc diagnostic tool.
I pm'd a few members on here so we'll see if one of them comes to the rescue, otherwise i'll try again this weekend.
after i get the xp drivers working i believe the windows 7 drivers will be easier.
To get the usbmodem driver to work i only had to change the device id to match the arrive's. the vcom doesnt appear to be that easy, df wrote that it has to be installed as its some kind of qualcom security check.
The weird thing was that i got the 6xx error that others reported when dialing out but it would only dial out in "zune mode" and not "router mode". I dont know if that is because of the vcom driver or not but that behavior was not mentioned at all in the other thread.
Driver?
I posted this in the "Update" thread, too....but figured it was relevant to this discussion....
So, I got the update a couple of days ago, daughter yesterday, wife this morning. I've got two more Arrives to go.
One thing I noticed was that when the phone was put into update mode, my Win7 gave the "found new hardware" dialog and I have a HTC 9#### (I don't remember the number but it was something like 96300 or so -- and a quick google the other day revealed it to be the right model number) driver show up when I clicked on the details. When I plug it in now, it just goes to Zune software again and I can't see the number.....but a driver got loaded.
Did MS push a driver or did whatever flashing mode cause Win7 to recognize it? This might go alonEg with the tethering work being carried out......
EDIT: 93100. Looked through history.
Thats good to know. ive yet to update but i seen it was available so i will do so tomorrow.
Does this driver remain when shown under device manager with the phone plugged in? I will upload the xp 32 htc usb modem driver tomorrow to this post. perhaps this driver can help.
After getting the update, when I plug in the phone, it shows up as "Windows Phone USB" (or was it USB Windows Phone) and not as the 91300. It only showed up in that mode when the phone screen was in a different mode....so, I guess similar to the HTC USB Modem driver screen shot shown above.
EDIT: Found a picture of what the screen looked like when the "New Hardware" was found.... http://www.wp7connect.com/tag/ssl/
success
I'll be updating this afternoon
Here's both the vcom and usbmodem drivers
I was able to get it to work after wahwka helped me
They should install 1st time when you manually force the drivers
here's the thread which I found very useful
http://forum.xda-developers.com/showthread.php?t=922000
Now here's what's really interesting
The modem ONLY dials out in "Zune Mode" not "Router Mode" which is the opposite of what everyone says on that thread.
So it would seem the dfrouter app is not needed at all on the arrive.
Like the modem can be used right out the box if the PC had drivers.
More people need to test what I've found.
I have not been able to connect yet I get error 692 but it may be just a setting is wrong as people have posted in that thread.
I will get working on some windows 7 drivers and see what happens on that PC
I believe the pc I have at my disposal is windows 7 64 so thats what I'll get working on next.
ALSO this app may be dangerous if you're only chevron unlocked read the thread
theres a possibility you may not be able to sync with zune.
I'm developer unlocked so I don't worry about this.
The developer took a lot of heat for this program and he was only trying to help the community so read first.
Id recommend making a backup first. Ill post the win 7 32 bit drivers here tomorrow. I'm still getting error 692 on this [email protected] computer too. I'm begining to wonder if something needs to be changed/tweaked in the phone program to get it to work. Ive just started learning silverlight so maybe ill ask dfvn.
Windows 7 32 Drivers attached.
I'll begin working on windows 7 64 next.
W7 64 Drivers
Windows 7 64 Drivers
This one seemed to be a b&%$h to install
Here's how I got them to install
I plug in the phone via usb
A bubble appears in the bottom right corner saying windows update is looking for drivers
click it
when the next window pops up click the cancel installing drivers
(These steps have to be done quickly or drivers will install and you will have 2 devices portable device HTC T7575 and windows usb device)
If done quick enough you will have two unknown devices _MI01 and _MI00
Force the drivers to install as previously written and ignore the MS warnings and they will install.
From here I notice the same things in all 3 PC setups
The drivers only appear to install in "Zune Mode"
In "Router Mode" I can only get one device to show up
"HTC" MI_00 and MI_01
If I uninstall, click usb sync, htc modem, no matter what I do I cannot get 2 unknown devices unless its in "Zune Mode"
--This needs to be tested by others--
If others come up with the same results
Then this tells us 2 things
1. Our phone or the way it interacts with dfrouter is different than the other wp7 phones that dfrouter works on
2. There is a chance that the htc arrive can be used as a modem without dfrouter and anybody will be able to use it as a modem
Has anyone called Sprint to see when they will offer tethering?
I have been using the APN "internet.com"
If this is not right it could be the reason I have'nt been able to connect
because the modem does appear to dial out
I might be wrong, but I think the APN is supposed to be blank for CDMA carriers. I can't post links but Google "tcp_apn_etc_for_sprint" and see the pinstack thread.
I have already been having problems with my Arrive's EVDO modem getting stuck in "null state" (kills all wireless data until RTN wipe) so I will probably wait for a more stable tethering solution.
For what it's worth I am running WinXP 32bit and using the attached drivers when playing around in QPST/QXDM and in USB Storage Mode. Hope some of this helps you!
I need a method of completely resetting any and all aspects of Microsoft active sync on the device side without resorting to a hard reset.
i do not care how long this takes or how many registry entries i need to change but i really really really need to get this sync issue fixed and every where else i turn has the same tired 5 step sorry your screwed speech and i have tried it many times.
please someone give me more advanced debugging that can actually help me fix this.
ok now that my pathetic rant is out of the way the issue is one of the classic device is plugged in. all drivers have been reinstalled multiple times and while the phone says it is connected windows mobile device manager says that there are no connected devices and will not display a dialogue to add a new connection. Bluetooth syncing is similarly impaired
steps taken to date.
deleted all current pairings
uninstalled all drivers and windows mobile device center allowed windows update to reinitialize everything.
tried plugging the phone in using active sync with both advanced network functionality and with this option disabled
so that is everything any of the trouble shooting sites have mentioned so far. at this point i believe the issue is at the phone level and has something to do with the network portion of the usb connection process as the network driver for the phone shows that the computer is sending data but receiving no packets from the phone.
all fire walls on my system have already been disabled.