Any solutions? my computer will recognize at first but then it says not connected and wont let me acess the files on my wing. Im using Windows Vista btw.
Can somebody help me with this problem?
I am using vista also.. try soft reseting it.
I tried soft resetting it and hard resetting it and it still doesn't work. Now I'm contemplating ever getting Touch It 2.3
Try going in settings->connections->usb to pc and either check it if its not checked or uncheck it if it is checked
Mine did this too last week. Reflash your phone with the official Tmobile RUU posted in the forum.
My steps were:
-Go into bootloader mannually (camera button plus voice command button and finally with those two press, click in the hole (between memory and volume key) with your styles)
-After it seems that pc loaded up some kind of driver, double click on the official Tmobile RUU and flash your phone to stock form.
this should work and goodluck...
I've connected my Wing on my friend's computer and it's recognized by his ActiveSync but its Windows XP he's using. Is there any way i can reinstall or change some settings on my computer so that it can recognize my Wing again? I really prefer the windows xp activesync over the windows vista version but theres no way of getting the old activesync on vista.
Finally!! I fixed the problem! I had to install version 6.1 from microsoft's website, and everything is good now. thanks for the help everybody.
do you have the link to that update im having the same problem
nm i got it, thanks for the solution though
I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
I have also tried to use ActiveSync to version 3.8 (I found this suggestion from this web site) but bad luck it can't detect my BA device at all. I have also tried to revert back to WM2003SE but still get the same problem. My system is WinXP SP2 & O2 IIs. So Please help I am in the dark right now.
Same problem here...
su2003 said:
I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
Click to expand...
Click to collapse
get into boot loader mode,then try
(press record button + power button and reset at same time)
addan said:
get into boot loader mode,then try
(press record button + power button and reset at same time)
Click to expand...
Click to collapse
Have tried that already but still get the same error. I have even reformatted my PC and reinstalled WinXP and ActiveSync 4.5 just in case there are viruses or so but also get no luck.
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Yes, at this time you asked me. Nothing changed.
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Yes.
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Yes. I did it.
More over, if I started BootLoader mode before execute MaUpgradeUt_noID.exe the program get struck while performs device information checking, I have to pull it out from Sync station the program then continue running but without any information (like the existing OS version etc.)
how long did you wait for the program to respond before you find that its stuck ?
Here it takes about 2 min to find the device
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
2. place it to cradle
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
4. start upgrade utility and follow the onscreen instructions
5. perform hard reset (the three options thing)
thats all
Xplode's new cube cab
deleted... off topic
how long did you wait for the program to respond before you find that its stuck ?
It was about 5 min and the program still had no responses. I then have to pull it out and the program continue running but without any information (like I had mentioned it before).
Here it takes about 2 min to find the device
Unfortunately not with mine.
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
Yes. I did it.
2. place it to cradle
Yes. I did it.
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
I have tried it both with and without killing the activesync.
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
su2003 said:
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
Click to expand...
Click to collapse
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
Good luck!
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
First of all, Sorry if I make you and other confused. I have began to unsuccessfully upgrade my device since Friday. So I decided to help myself at first by try to do everything I can do by myself. I have formatted PC HDD and also reinstalled activesync because I thought the utility may conflict with other program on my PC or from Viruses. I have also tried many ways with hard reset and cold reset etc. to upgrade my device but have no luck. That was with very fresh new installed WinXP PC. Unfortunately, I have to use this computer for my job also. So that's why I have to install printer & scanner driver including MS Office, AutoCAD and other necessary program to serve my job . I have falled with upgrading but I do not want to have problem with my job. Hope you understand my essential.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Since I began to upgrading and everytime I have executed the utility I have always wait & wait but I just never look at the clock to see how long I have waited. Xplode has just warned me to take enough time so I started to upgrading but with clock at this time. I have already mentioned that I have successfully upgrade from WM2003SE to the WM6 (previous version) so as a user I have enough experience and know what I am doing.
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
This is just my opinion to let you guy see and understand the problem. That's it.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
I think I have already put a lot of effort about upgradind my device. I have reformatted and reinstalled all necessary programs. It took me out almost half a day to do this. And not only with my PC I have also reinstalled all programs on my device with an old OS version since I have lost them all from hard reset. Other than that I have also tried & tested upgrading the device during the time. The only word I can say that It was not funny to do all of this. It was not really a hard job but it took almost my weekend time.
Good luck!
Yes I do need it barely. Actually I have already felt a little lucky got from all of you that try help me solving the problem. Thanks.
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
April 1 said:
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
Click to expand...
Click to collapse
Thanks for your additional.
I have also tried using different PC to upgrade the OS but got the same result.
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
I am quite sure that the screen has displayed USB but the number is 2.07 not 2.06. I am not sure about the meaning of the number, it could be the version.
I have also brought a new USB-XDA IIs cable yesterday, just in case the cardle was defected but it doesn't work also, I have got the same result.
khanem said:
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
Click to expand...
Click to collapse
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Conclusion:
Bad Hardware(Flash ROM)?
Your Bootloader is toasted or had it's LAST flash of it's lifetime???
We can say that... but hopefully not for your sake.
Because as you have said you've done EVERYTHING that was posted.
and though our Senior's "inputs" didnt worked out the way it SHOULD work.
I cant say it's a waste of time to answer your questions.
But there are no more questions to ASK
and there are no more questions to ANSWER
They're all been said here.
All you have to do is PRAY HARD leave the BA rest for a day...
remove the battery...
think things out, clear your mind... sleep...
then execute Xplode's Walkthrough from Step 1 the next day.
but be sure to have the battery fully charged.
Your BA is not dead and your bootloader is not toast. The only problem you have is probably you are impatient. Go to the Wiki and follow the procedure exactly as it is written. It will work. By the way, if you kill Activesync (ie disable USB connection in activesync connection setting), put your device in bootloader mode and connect your usb cable (in that order), run the upgrade and it will work. Forget about activesync.
su2003 said:
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Click to expand...
Click to collapse
I use xda IIs and the bootloader mode shows ver 2.07, and i dont have any probs installing. I dont think the version 2.07 has got something to do with your problem.
You said that you tried other pc and it doesnt work, and it worked before when you upgraded previously. I think you know enuf about upgrading if you have done it before....
did you have problem with sync connection before? I was just thinking maybe there is something wrong with your BA....like actual hardware problem with the cable connection??
what about firewall? would it affect it - I doubt it cause its not in sync mode.... but at this stage, maybe just try all possibilities to try to get it working.
Good luck
Mhm. I'm not sure I've really followed all the intricacies of this case ... But whatever, here's my two cents for a safe upgrading procecedure:
1) use a cradle, not a USB cable, and make sure the cradle's
power supply is plugged into a wall outlet. It also helps to make
sure the cradle is plugged directly into the PC, not via any kind of
USB hub. No other devices should be connected to that same USB
channel. I suppose temporarily disconnecting other (unneeded) USB
devices from the computer can't hurt, either.
2) I guess "kill ActiveSync" can mean various things ...
however, here's the best way to do it I think: as sofene mentioned,
disable USB connections (what the hell - disable ALL connections) in
ActiveSync settings. Then reboot the PC. No need to look for ActiveSync
processes and kill them manually -- disabling the connections will take
care of that. Rebooting ensures that ActiveSync's driver code is really
unloaded.
3) remove SD card and, for good measure, SIM card from the BA.
4) perhaps soft (or even hard) reset your device
5) put device in Bootloader mode
6) insert device in cradle, start upgrade utility, off you go ...
By the way, ActiveSync has got nothing to do with the ROM upgrade utility, and it should therefore not have been necessary to re-install ActiveSync, etc. You just have to make sure it does not get in the way of the upgrade process. As far as I understand the process, the ROM upgrade should work equally well on a PC that does not even have ActiveSync installed.
My HTC Touch Diamond2 never stays connected to my Windows 7 PC for long.
Therefore its not syncing everything.
If I go into Sync Center the status of the device is Disconnected.
To fix this problem I have to go into Device manager, Uninstall the Microsoft Windows Mobile Remote Adapter, unplug the phone from USB, plug the phone back into USB and Windows recognises the phone and reinstalls the driver.
But later in the day it will disconnect and I have to go through the reinstall process again.
Its really annoying.
How can I permanately fix this?
Try a Hard-Reset. It worked for me to. Or try to reinstall Windows mobile device center.
if that does not work, try to update hard-spl to 2.51 (if your device is already rooted). that helped me out, maybe it will help you, too.
wavesshock said:
Try a Hard-Reset. It worked for me to. Or try to reinstall Windows mobile device center.
if that does not work, try to update hard-spl to 2.51 (if your device is already rooted). that helped me out, maybe it will help you, too.
Click to expand...
Click to collapse
Thanks for the reply.
I have not done a hard reset but I updated the ROM, last week, to the latest that HTC have published.
It did not fix the problem.
I also reinstalled the Mobile Device Center and it didn't fix it.
I have now created a script to reinstall the driver for me. So I just double-click it on my PC and its automatic. Still annoying but now less so!
had same problem but Hard-Reset helped me
you can try do that in another pc ?
I have the same problem.... and I can't try do that in another pc.... what have I to do?
Is it a firewall problem?
Hi there,
I flashed my HD2 several times before, using winXP. Now I got a new laptop with
Win 7 64 bit. I want to flash my phone with a WM6.5 Dutty ROM. The phone syncs fine when running but when it switches to bootloader, the laptop doesn't recognize the phone anymore. It does not switch to USB and on the Laptop I get the message that there is no driver for "Qualcomm CDMA technologies MSM"
Help please, I tried to find some answers but couldn't find anything!
Thanks.
klumpbatsch said:
Hi there,
I flashed my HD2 several times before, using winXP. Now I got a new laptop with
Win 7 64 bit. I want to flash my phone with a WM6.5 Dutty ROM. The phone syncs fine when running but when it switches to bootloader, the laptop doesn't recognize the phone anymore. It does not switch to USB and on the Laptop I get the message that there is no driver for "Qualcomm CDMA technologies MSM"
Help please, I tried to find some answers but couldn't find anything!
Thanks.
Click to expand...
Click to collapse
Mate, this issue has been known since the beginning of HD2 using win 7 or vista. There is a thread duscussing about that, but unfortunately I forget the link for that.
I also use win 7 64 bit and I experienced that too.
What I did to solve it was turning off my phone and leave it for a while (at least 5 minutes) and also turn off my pc.
After that i turn it on again the pc and the phone and plug the phone to different usb port. It works.
If you still have problem, you can try to reinstall windows mobile center.
goodluck
Well, it's been almost a year since I've had the upgrade bug. I have been running the 8107 (unlocked, I think it was a YUKI/XBOXMOD ROM) version of Windows Phone 7.5 for a while now. I finally saw there's a new version, and I want to flash it.
Perhaps it is because it has been so long since I've done this, but I cannot get the USB connection I need when running DWI.exe.
I've tried all the fixes on my Windows 7 x64 bit computer and I'm stumped.
Tried running customRUU.exe while running DWI.exe...didn't work
Tried making sure DWI.exe was being run as Administrator...didn't work
Can anyone help? I'm just trying to get from one WP7 ROM to another...I already have HSPL 2.08 and Mag 1.13.
Is this a problem with the phone or the USB drivers on my PC?
Sorry for this, I used to remember all this stuff but my HD2 has been rock solid (except for touch tones not registering on calls...which means I can't call any customer service centers that require you to enter selections via touch tones) for so long I can't figure this out...
Do I need to do a hard reset? Go back to WM 6.5 and start all over?
Is it the USB drivers? Where are the ones you need for this?
Any help is appreciated. LONG LIVE THE HD2!!
UDPATE: Nevermind, re-installing the WMDC for WM 6.5 did the trick.