Help why my activesync cant connect with my PPC?
Thanks
Did you use xp sp2 and activesync 4?
I used to have ActiveSync 4.0 problems too... Device manager detected the device but failed to install driver.
In my case it started working once I swaped the cradle's USB connector to another USB jack with the PDA in the cradle.
Windows XP found the "new" device and installed properly this time... Now I can Synch fine through USB.
Also some say that you need to change something on you PPC, so go to Start/Settings/Conenctions/Network Cards and select "Remote-NDIS Host" and change it to "Server-assigned IP address" and then Ok, Ok, Ok...
I hope this helps you...
Rayan
Hi. I`ve finally found the way to connect mtty and run rom update utility in Vista. tested on rtm 6000.
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
Didnt work for WM6 update
is this supposed to work for the WM6 upgrade?
Didnt work for me.
Attached the files for x64 version of vista (taken them from x64 XP).
Drivers are unsigned, so you have to turn off driver signature enforcement in vista. Google how to do this.
And yes, this can be used to upgrade uni to WM6.
No this method did not work for me for O2 Atom.
Using Vista Business with released final windows mobile device driver. No use. Able to sync perfectly. But RUU ROM update is failing. Trying to disable the firewall also no good.
omg thank you so much for this! i was trying to downgrade my hermes from 1.06 to 1.04 CID but vista's windows mobile device centre or whatever its called is dodgy as hell and i couldn't run RUU. you are a god send, thanks again!
yes, this is working out very well with vista.
Thank you.
Vista cannot find drivers for Hermes after flash
I used these drivers to allow me to flash my Hermes with the latest Cingular image. After the device reboots, Vista no longer recognizes it. Vista prompts me to search for a driver but cannot find one. Is this related to installing the back-level drivers above? Anyone know how to recover from this?
Thanks!
No joy....
This did not work for me. I'm running Vista Ultimate and a TMO MDA.. I hope there is a solution soon.. I really want WM6 on my phone, but I don't want to have to have an XP machine around....
sp3dev said:
Hi. I`ve finally found the way to connect mtty and run rom update utility in Vista. tested on rtm 6000.
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
Click to expand...
Click to collapse
Thank You! Worked for me, using Vista Ultimate.
Thank you! It works...
I was also unable to get this working. I am running Vista Enterprise RTM. I followed the steps in the list exactly, and also tried restarting the services (they were already started) and killed mobsync.exe (Sync Center). No such luck . RUU crashes while trying to read information from my phone. Has anyone who had problems earlier got it working yet?
Thanks!
sp3dev said:
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
driver.
Click to expand...
Click to collapse
Hi,
I'm having difficulty updating the Build in driver with the one you supplied. As soon as I try to update the driver I get a meesage saying the one installed is already the most recent. As soon as I uninstall the original driver it is redetected and reinstalled.
Anyone have any help on this.
Thanks,
Tom
Right click on the device and click "Update Driver Software"
Click "Browse my computer for driver software"
Below the textbox, click "Let me pick from a list of devices on my computer"
Now you can click "Have Disk" and choose the drivers you downloaded
Pick the device it pulls from the .inf file
Step through the rest of the wizard and you should be set.
The wording of the buttons may vary but should be similar to what you have (I'm running Vista).
RUU Version
What version of the RUU software is working, I tried the 2.00.1 that came with the 2.61 radio upgrade and it did not work.
I, too, am using 2.00.1. I'm going to try these steps on one other machine I have that's running Vista. We'll see what happens!
Thanks for providing a solution that works on Vista.
Upgraded my Hermes using mtty and RUU, no problems with the driver posted.
vista sucks big time...
best way -> uninstall -> xp
Opinions
ericlin0122 said:
vista sucks big time...
best way -> uninstall -> xp
Click to expand...
Click to collapse
Like they say, everyone has one.
mamaich said:
Attached the files for x64 version of vista (taken them from x64 XP).
Drivers are unsigned, so you have to turn off driver signature enforcement in vista. Google how to do this.
And yes, this can be used to upgrade uni to WM6.
Click to expand...
Click to collapse
That zip file is corrupt. Anyone else know where I can get it?
Also, why do the steps in the first post say to uncheck "Allow USB connections"? When I do that, I can't find it in the device manager.
it workes finally but i realised that the 2.00.1 RUU is problematic, older versions work fine
Hi all, I run Vista x64 Ultimate and connect my devices with Windows Mobile Device Center (WMDC) I recently dug my O2 Xda Exec out but its stuck at the boot screen, i.e. says serial at the top then v1.00 at the bottom, if I connect the USB cable the word 'Serial' changes to USB
I have unchecked the 'Allow USB Connections' in WMDC and the PC does it's USB Bing Bong sound as you plug in the xda to the USB, unfortunately when using Mtty I get no USB option, consequently I can't input the commands and continue with the install. I have also tried using the Uni_exitbootloader.exe, again this states there is no USB option. I was trying to get either the Ranju v77 rom or the original xda exec rom installed.
I have checked the USB ports using other devices and all function ok, so what's going wrong?
Going to try from another machine today, its running XP pro so I should have more luck!
**SOLVED**
Problem solved.
Advice: Don't use Vista x64 to update these PDA's
The solution was to go to my XP system and upgrade from there, installed original Xda_Exec_Upgrade_v1.30.162.exe then once that was ok I tried out Ranju_v77_WM61_19900_19900_1_0_2.exe.
my issue now is wireless encryption, apparently I only have up to WEP and I use WPA, will do a search but if anyone knows how to deal with this can you post.
tia
Vista fix
Check this out:
http://forum.xda-developers.com/showthread.php?t=391452
I had the same problem, it is Vista so here's a fix if it happens again!
All the best.
Apologises for the delay in replying, Cheers Joey.
regards Lee
Hi members of XDA-Developers. I'm new here and just getting my self into this with updating my Windows Mobile 6.1 to 6.5 on HTC Touch Pro. I've read the guide how to do and got all the necessary programs, but run into a problem.
Can start by mentioning that I use parallels desktop on my mac with active sync. When I get to the step where I will update my flash with "RaphaelHardSPL-Unsigned_190_1_3.exe" it does everything fine until I press the "update" button, accept the program on my phone and then the phone close down and my computer unplugged the USB cable for some reason! Get an error message that the USB cable is not connected?
Why it does this I spent last 3 hours to find out and also browsed all possible topics on this forum for an answer! Grateful if anyone can help me out on this one.
I would try redoing it on a pc
Rudegar said:
I would try redoing it on a pc
Click to expand...
Click to collapse
Well I thought that would help as well so guess I just install windows on my mac with bootcamp instead.
Strange tho that I got this problem. Read that everyone else recommends to use parallels desktop?
hi,
i am using win7 (64bit) and just upgraded my xda3 from 2003 to 6.5.. how?
just by using oracle's virtual box
i have installed xp on that.. then connected the xd3 over the cradle..
used the utilities for xp (maupgrade) and finished.. as on a real xp machine.. so easy!
here is a pic:
http://img844.imageshack.us/f/unbenanntxvy.jpg/
excuse my bad english.. i have blacked out some private stuff on the screen.. btw, i am using dualview.., thats why the screen is soo wide
HF with that information
Serce1975 said:
hi,
i am using win7 (64bit) and just upgraded my xda3 from 2003 to 6.5.. how?
Click to expand...
Click to collapse
Heyho,
just read this Fu**ing great Tut from D-Two:
http://www.mediafire.com/?wozgwddo3ay
all you need is in this PDF, also all Software Downloads as Links...
So, there´s no need for Virtual Crap, but anyway...Thanks for that
at first i use Win 7 64bit I'm get confuse too, but that Tut give me a light.
im already try almost all rom in this forum for BA, but i think the best room is WM6.1+Manila by dtwo http://bit.ly/b44Dwe.
the important thing is, it worked. but to get on with galluslongus' idea, for flashing with win 7 (even x64) you don't need to run a virtual machine. i tried them all and encountered that to correctly loop through the usb correctly to any virtual machine (vmware, virtual box, virtual pc xp mode, virtual pc 2007...) you need the correct windows 7 drivers anyways. after installing those drivers you can flash in win7 directly, like the way, most people do.
i open this thread again.. because i am now at the point to flash RC5 on my BA. but first i had to downgrade to 2003 to upsize to 60MB Space.. but i cant downgrade, although the right image is in the folder with MaUpgade and i have done all the things in the PDF Guide like driver change and further steps..
if i start MaUpgrade (BA is in USB mode) the tool didnt detect the version.. if i press next, the tool checks the device and then notice me of successfull upgrade.. but my device is still running 6.5.3??!
Any advice?
Serce1975 said:
i open this thread again.. because i am now at the point to flash RC5 on my BA. but first i had to downgrade to 2003 to upsize to 60MB Space.. but i cant downgrade, although the right image is in the folder with MaUpgade and i have done all the things in the PDF Guide like driver change and further steps..
if i start MaUpgrade (BA is in USB mode) the tool didnt detect the version.. if i press next, the tool checks the device and then notice me of successfull upgrade.. but my device is still running 6.5.3??!
Any advice?
Click to expand...
Click to collapse
you don't need downgrade!!! flash the rc5 it has an app for rezise at the beginning!!
PS: You must put the Blueangel into the Bootloader!!
its not my first time, and i did the previous steps.. driver update for win7 64bit. look sreen:
My device is running WM 6.5.3 Beta with 1.15.0 Radio
but i still get that Error 150.. i tried both RC5s on ur mainpost. i tried it with your updater.. what i am doing wrong? cant figure it out - the BA is in Bootloader and the cradle is connected via backside USB Port, not Hub or frontside. On Screen i see USB!
EDIT:
Now its working!!
I just reinstalled the driver and then sign it again via dseo13b (putin .sys in win32\drivers) - restarted pc and now it works!! YES!!
?? didnt understand anything.. sry! whats the problem?
omg zonice nomne