PDA

View Full Version : RUU Works in Vista RTM!


sp3dev
27th January 2007, 10:08 AM
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.

shido6
28th January 2007, 09:06 PM
is this supposed to work for the WM6 upgrade?

Didnt work for me.

mamaich
2nd February 2007, 04:03 AM
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.

Anant
6th February 2007, 05:03 AM
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.

Huey85
6th February 2007, 04:15 PM
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!

lpsi2000
9th February 2007, 03:21 AM
yes, this is working out very well with vista.

Thank you.

froghat
11th February 2007, 04:56 AM
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!

ruskastud
11th February 2007, 03:04 PM
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....

vijovame
11th February 2007, 08:26 PM
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.

Thank You! Worked for me, using Vista Ultimate.

oVan
12th February 2007, 11:32 AM
Thank you! It works...

lanerebel
12th February 2007, 10:07 PM
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!

tvalentin
13th February 2007, 01:21 PM
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
driver.

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

lanerebel
13th February 2007, 02:46 PM
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).

robjae
13th February 2007, 05:23 PM
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.

lanerebel
13th February 2007, 07:40 PM
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!

popsi
23rd February 2007, 09:30 PM
Thanks for providing a solution that works on Vista.
Upgraded my Hermes using mtty and RUU, no problems with the driver posted.
:)

ericlin0122
24th February 2007, 07:11 AM
vista sucks big time...
best way -> uninstall -> xp

robjae
24th February 2007, 01:53 PM
vista sucks big time...
best way -> uninstall -> xp

Like they say, everyone has one.

Eluzion
26th February 2007, 07:47 AM
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.

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.

georgenana
28th February 2007, 05:10 PM
it workes finally but i realised that the 2.00.1 RUU is problematic, older versions work fine :D

houseyeah
1st March 2007, 03:12 AM
If I install older driver, RUU can work fine, but WMDC can't work except I recover original driver.:confused:

Any suggestion? I can't find any helpful information aboun USB serial driver on Vista. My boss didn't accept this way to solve it.:(

I7oobie
2nd March 2007, 07:45 PM
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.



Are these for 32-bit? I can't get them to work.

smart1
3rd March 2007, 11:52 AM
sp3dev YOU ARE A STAR

hbahaie
3rd March 2007, 08:55 PM
Does it has any effect on ordinary syncing afterwards, or i have to redo the changes to use windwos mobile cente to sync my data??

ChildOTK
3rd March 2007, 09:14 PM
Works, Vista Home Basic 32-Bit

I-Mate JASJAR :D

Clements
4th March 2007, 02:03 PM
vista sucks big time...
best way -> uninstall -> xp

It's always the meatware that sucks! ;-)

I run Vista since nov. 2005 (Beta 1) fulltime and have experienced very little problems except for the usual beta bugs.

Now this thread has solved my last need for XP! It works flawlessly for Vista Enterprise and Jasjar!

myname70
8th March 2007, 01:08 AM
Hi. I`ve First of all, connect your device when it`s in bootloader..

How to put my Qtek900 in Bootloader mode?

ChildOTK
8th March 2007, 11:01 AM
I downloaded the USB driver for Vista x64, and when I try update the device from the device manager, it doesnt work, when I right click on the inf file and select install, I get :

"The INF file you selected does not support this method of installation"

So back to the device manager, when I select the inf file, it doesnt seem to select, I click on open over and over again, and it doesnt do anything??

Any ideas??

ChildOTK
8th March 2007, 11:18 AM
Ok...erm...

I get it to load the file now, only problem is it tunes me

"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)"


What now??

HamiNguyen
8th March 2007, 02:29 PM
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).

Would U intruct me :(!!!!

I try step by step your intruction but I can't Uprom
I use Dopod 838 Wizard100 and I wait You Explain me :D

funtoosh
8th March 2007, 04:50 PM
It even worked for me. My XDA EXEC was dead as the rom update stopped in between due to vista, but after using this tweak the update has started again and my phone is responding.

Thanks a lot

greets

asci
8th March 2007, 07:25 PM
I did ROM upgrade with method...but now I can't sync anymore with vista. How can I reverse back to previous situation?

BigT
14th March 2007, 09:02 PM
wow, your method worked perfectly, i thougt i had to throw my mda against the wall because i spend nearly 48h with getting wm6 installed..and afet 245.353.235 tries i thougt that it might have something to do with vista...found your thread..and it worked: thank you!

romka
15th March 2007, 01:56 PM
Tried on 3 machines - 2 Ultimate's and one Home Premium

None of them seem to like the driver.. :(

Any ideas guys?


EDIT:

by not liking i mean windows complains that I should pick a driver compatible with 32bit windows. or something along those lines.

would appreciate a hand here.

DJaYKaY
15th March 2007, 09:21 PM
Windows Vista Business Edition
Totally works!
My Qtek9000 is alive!!! ;D

Thank's a lot!!

DJaYKaY
15th March 2007, 09:22 PM
I did ROM upgrade with method...but now I can't sync anymore with vista. How can I reverse back to previous situation?

You can try to "upgrade" the rom with an old rom (like pocketdevice.it original from dangaard)

Sappimi dire ;)

sickness
16th March 2007, 06:12 AM
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
driver.

pls see the following steps and tell me wut 2 do next:
when I go to device manager, then right click on the unkown device,then update driver, then brows my computer......., then let me pick from the list...,Now, which device should I pick among the other devices, there are a lot of devices e.g battaries, disk drives, bluetooth device,,,,,etc

so which device should i pick to assign wceusbsh.inf as a driver to it

thank you

naboleo
20th March 2007, 12:22 AM
And Paul even did a nice tutorial !!
http://www.modaco.com/index.php?showtopic=252977

c3l5o
20th March 2007, 03:02 PM
One more happy customer ;) Upgrading my beautiful prophet now :p

joey jojo
2nd April 2007, 07:41 PM
And Paul even did a nice tutorial !!
http://www.modaco.com/index.php?showtopic=252977


this was perfect for me, was faster than normal xp upgrades, dunno why though.

i tried to find something like this for ages today, this should really be made as a sticky or added to wiki.:)

davidberrysmith
5th April 2007, 07:32 PM
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.

I've got Vista Ultimate 64bit and it worked like a charm.
to disable driver signature enforcment permanently, run the following command as administrator then reboot:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

create a .bat file with the above line, hold down shift and right click the bat file. click on "run as administrator"

;)

frankw
5th April 2007, 08:31 PM
Very nice this driver worked for me, but as a last step I had to re-enable USB connections within WMDC in order for RUU to see the phone. I was then able to flash HardSPLv6

kenwinfrey
7th April 2007, 11:44 AM
Thanks alot for the help, you saved me. i was stuck in the bootloader and was going to send my phone in for service, thanks again

kot_as_kot
15th April 2007, 07:05 AM
Vista Business 32 & Himalaya HimaUgradeUt.exe -- positive

Svenitos
15th April 2007, 10:48 PM
I added a page to the wiki, if you want to you can add things like problems with solutions or screenshots to make the page better.

http://wiki.xda-developers.com/index.php?pagename=Trinity_WindowsVista

CUGWMUI
16th April 2007, 08:09 AM
I'm following the steps mentioned for the ROM upgrade in Vista, but as soon as I reach "Verifying the information on your PDA Phone" screen, the RUU software crashes.

I'm using the RUU from Xplore_1.1 WM6 ROM.

Any suggestions?

dan13l
25th April 2007, 02:10 AM
This has never worked for me.

Could someone who's had success let us know what version of the upgrade utility you're using? I suspect that might have something to do with it (ie older ones work, newer ones don't).

Edit: Just tried the t-mobile rom, and that doesn't crash the upgrade tool. It won't install though, because it's not a modified upgrader. The search continues.

dan13l
25th April 2007, 03:44 AM
Fixed!

I used the files (except the .nbf) from here: ftp://xda:xda@ftp.xda-developers.com/Wizard/Radio_Roms/9100_radio_only_1.13.10.rar

Using the older update tool, I was able to upgrade to the Xplore rom via Vista Ultimate.

dim4x4
25th April 2007, 10:08 PM
After doing all the steps and trying to flash, I get the following error which closes the RUU :(

ROMUpdateUtility MFC Application has stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: ROMUpdateUtility_Wizard_NoID.exe
Application Version: 2.0.1.0
Application Timestamp: 42fb1e00
Fault Module Name: ROMUpdateUtility_Wizard_NoID.exe
Fault Module Version: 2.0.1.0
Fault Module Timestamp: 42fb1e00
Exception Code: c0000005
Exception Offset: 0000b1a0
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 2057
Additional Information 1: 1e54
Additional Information 2: bf1679ba9700126441e625946b80526e
Additional Information 3: b1ea
Additional Information 4: eafc8562c40a15d325e55326bebdc7d3

Any suggestions are welcome///

dan13l
26th April 2007, 03:44 PM
dim4x4 - did you try the update tool I posted in the link above?

daniel.eriksson
6th May 2007, 10:34 PM
hey there!

I wanted to test the latest rom released on the fourth.
It seem to have put me in the first bootloader level. It has happened to me before, so i tried in my new vista laptop, didnt really work so i tried the new "old" driver. Then it worked with the USB> set 14 0.
After that i was able to upgrade. However, i was never able to put it on! Its now entirely black (not even serial or usb without backlight). Hard reset is still doable (press both - and reset).

What can be done? I think i had bootloader 0.6, was i wrong to upgrade?

Appreciate all the help i can receive asap.

let me know. And your doing a great job everyone.

d

silverfox0214
8th May 2007, 04:56 AM
The new Dash ROM has a nice after affect: It actually works in Vista without having to mess around with the drivers.

It would be very cool if we could get our hands on this RUU and start using it for our ROMs.

Anyone have a contact for it?

eelco_akker
9th May 2007, 03:53 PM
Thanx works like a charm on my dutch Vista Business and MDA Pro upgrade to WM6.

Eelco

alexmi
14th May 2007, 09:11 PM
Can you believe that before discovering this post I had to install WinXP all over and flash my wizard from there ? :eek:

tonydeli7
16th May 2007, 12:50 PM
guys,today i flashed my prophet under vista with this utility... i thought it would crash...but it didn't...!try it...:)

LordDeath
16th May 2007, 08:34 PM
guys,today i flashed my prophet under vista with this utility... i thought it would crash...but it didn't...!try it...:)

under vista 32bit or vista 64bit?

tonydeli7
17th May 2007, 01:18 AM
under vista 32bit or vista 64bit?

Vista ultimate 32bit...

haythams
26th May 2007, 03:56 PM
thanx alot for this value added topic i've implemnted the steps three months ago and it was working fine but sudenly its not working even my PPC icon is not listed in my computer, when i connect the device alret sound is annoincing that my device is connected and even the connection arrows keep cyrcling and WMDC screen appears confermiong connection established but after a little while gives me error ? accordingly i repeat all the step started fro putting the PPC on BOOTLOADR mode but i didnt upgrade the device cause its already upgraded but i just softreset and insert to the cardle but its not working ? connection alret and WMDC screen try to connect but error ?after some search i discovered this in the device manager
http://www.9o9i.com/uploads/b10af6771c.jpg (http://www.9o9i.com)

any help

hazzoom
28th May 2007, 01:46 AM
Thank you very much!
its been 2 days trying to recover my i-mate jamin under vista ultimate your solution worked just fine!

epimazzo
16th June 2007, 03:38 AM
Thanks a lot for this post! It worked for me like a charm! :D

I've been wasting considerable time searching for a right package!:)

Regards.:cool:

Fixed!

I used the files (except the .nbf) from here: ftp://xda:xda@ftp.xda-developers.com/Wizard/Radio_Roms/9100_radio_only_1.13.10.rar

Using the older update tool, I was able to upgrade to the Xplore rom via Vista Ultimate.

nayga73
22nd June 2007, 09:05 PM
have exactly the same problem as you dim4x4,tried all the other methods,nothing seems to work with vista.i even tried to flash to the original tmobile uk rom and keep getting the same message!!!n e help would be extremely welcome!!i'm running vista ultimate x86,wish i'd never upgraded to it,xp never had these probs!!!! i'm very new to this,but find the tutorials on this site to be spot on!!!keep up da good work guys!!!!



Wizard G4 CIDLocked
Crossbow ReLoaded 1.5
Radio 2.40.11
protocol 4.1.13.20

hans-martijn
28th June 2007, 03:42 PM
The update program crashes every time I try (Vista home premium).

-hans

pvdhelm
28th June 2007, 04:57 PM
The update program crashes every time I try (Vista home premium).

-hans

Try this

Follow these instructions and your vista problem is over.
I used this guide and it works for my artemis p3300 phone! :D

Please try downloading the latest WMDC first before attempting anything in this section of the guides. you will find the latest version HERE .

To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here (http://www.microsoft.com/windowsmobile/devicecenter.mspx) to install it first.

One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.

For this guide firstly you need to download the new drivers:

Drivers for Windows Vista x32 (http://forum.xda-developers.com/attachment.php?attachmentid=33662&d=1169888879)

Drivers for Windows Vista x64 (http://forum.xda-developers.com/attachment.php?attachmentid=33892&d=1170385335)

Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.

Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.


Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon


In the connection settings menu untick "allow USB connections" then press OK.

Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.


Scroll down the list and make sure these services are present:

Windows Mobile-based connectivity

Windows Mobile 2003-based connectivity

If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.



Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".

This will bring up the properties of the currently connected device (the hermes in bootloader).



Go to the "Driver" tab and click "Update Driver".



Click "Browse My Computer for Driver Software".



Select "Let me pick from a list...."



Click the "Have Disk" button.



Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.



Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"

Then click Open.



click next and the driver will be installed (wait a moment).



Press close and escape back to the desktop now.

Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.



click the WMDC line and click "End Process". In the confirmation window, again press End Process.

Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").

Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which vista uses when the device is in bootloader mode.

102mm
30th June 2007, 03:06 AM
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.

wow!! it works fine with Vista. i was stuck in the bootloader mode and i thought i was gonna have to trash it Thanks a million!!!

LordDeath
30th June 2007, 04:31 AM
@pvdhelm: great tutorial!
it works with vista x64. but the problem is, that some custom roms have flashtools, which don't work with vista 64bit. maybe they are 16bit software :confused:

ripplingsnake
9th July 2007, 01:00 AM
i have vista x64 ultimate , it wont work , after i do all this , and go back into WMDC it still wont connect , to phone , it just sits there and does nothing , it says not connected , no matter if a pull the plug out of the phone and put it back there is nothing any suggestions?

computerchile
16th July 2007, 08:26 PM
i have a HTC P3300 buyed in Holland and try to install WM6 , and now is in blank screen with some codes. any help how to reflash

thanks

Smokinvegas
21st July 2007, 12:47 PM
Remember This will work correctly just make sure that your device is in the bootloader mode to upgrade. I have followed everthing exactly in this forum. It works just make sure your device is put back in the cradle in bootloader mode.

Power button then record then reset.

wanwarlock
23rd July 2007, 12:29 PM
did all the things above but everytime i try to update my spl to latest prophet spl, my prophet went to bootloader & this error came up "ROMUpdateUtility MFC Application has stopped working" any suggestions?

Roddles
27th July 2007, 02:41 PM
Hi - Followed your instructions and worked like a charm.

Hopefully there will be an rom updating program that can handle the latest Vista USB drivers so we dont have to do this in future

Thanks heaps for providing a working solution :)

Roddles

cptcoconut
28th July 2007, 05:50 PM
I was having the issue with the ROMUpdateUtility crashing (with the MFC error) after it put the device into bootloader mode. After a lot of failures, I finally found a solution (at least for me). You still have to follow all of the instructions in the other posts regarding the drivers, but the final catch was the executable version of the RUU.

The 2.00.3 ROMUpdateUtility.exe works every time without a flaw. I couldn't get any other version that I had to work. I tried 2.5.2 and 2.00.1 with no success.

Attached is the 2.00.3 version that worked for me. Just put the nk.nbf from the ROM you want to install into the same folder as these files, and run ROMUpdateUtility.exe.

I hope this helps someone else avoid the painful hours I spent trying to get it working.

Edit: I have no idea if the same RUU can be used for devices other than the Wizard; I don't have anything else to try it with.

wanwarlock
30th July 2007, 08:51 AM
had to dload and use vmware to make this work. the change in drivers did not help, would get the update error as above. vmware worked like a charm on the 1st attempt.

Chatty
1st August 2007, 12:14 AM
Hi,

I've put together a simple guide on how to update (actually downdate) bootloader drivers for RUU. No use of Device Manager but command shell instead. See here (http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeFAQ#Q24). Hope it helps some ppl.

charly_mx
2nd August 2007, 07:42 AM
I was having the issue with the ROMUpdateUtility crashing (with the MFC error) after it put the device into bootloader mode. After a lot of failures, I finally found a solution (at least for me). You still have to follow all of the instructions in the other posts regarding the drivers, but the final catch was the executable version of the RUU.

The 2.00.3 ROMUpdateUtility.exe works every time without a flaw. I couldn't get any other version that I had to work. I tried 2.5.2 and 2.00.1 with no success.

Attached is the 2.00.3 version that worked for me. Just put the nk.nbf from the ROM you want to install into the same folder as these files, and run ROMUpdateUtility.exe.

I hope this helps someone else avoid the painful hours I spent trying to get it working.

Edit: I have no idea if the same RUU can be used for devices other than the Wizard; I don't have anything else to try it with.

Is there any 2.5.2 or higher ROMUpdateUtility for windows vista. Because when I try to flash my G4 unlocked device with the tool yo attached it saw error 300>

ThanxS!

decknologist
27th August 2007, 02:16 AM
I did exactly as ps3dev said in the very first post (although I didn't kill 'wmdc.exe with any taskmanager' as I didn't see it running). Thanks man, it's the first time I have attempted an upgrade with vista and it worked a treat first time.

Other than that I followed your instructions to the point.

My laptop runs vista home basic - Dell inspiron 1501 - 32 bit - 2.00 GHz
My device specs are below - G3 unlocked. I downgraded from the WM6Xr3 to the o2 stock ROM and then to the new WM6 TNT 4.0 Professional.

;) confirmed working! ;)

BoardDWorld
19th September 2007, 12:20 PM
Thank you very much, the driver worked perfectly allowing me to use mtty to flash WM6 to feeler.

Cheers!

Drea@m
20th October 2007, 07:55 PM
nice, it`s work 4me. Snks vmatch

njmarchetti
20th October 2007, 08:33 PM
I have yet to try this process on my main Vista machine that I sync my device with (using WMDC)

Does downgrading the WMDC drivers to the activesync drivers have any effects on syncing with WMDC after your flashing is complete? Or are you suppose to revert your drivers back and forth everytime you flash?(b/c that sounds like a lot of work).

Can anyone explain in a little more detail how the drivers work after the flashing is complete and you want to resume regular syncing?

burnage
22nd October 2007, 05:57 PM
Has anyone done that with a x50v.
Can't get it to work.
I can install the driver and so on but when I run the AximUpdate.exe my x50v performs a reset instead of continuing the updating process???
-bootloader (waiting for usb sync....)
-runing updateaxim.exe (hanshaking pc)
-reset while in cradle
-windows says make sure you are connectet blabla

?

So far WM5 A01....

MiSSigNNo
26th October 2007, 07:59 PM
Worked great with my HTC Universal.

Good job.

rohitsharman
6th February 2008, 05:05 AM
This works perfectly well, i am usin' Vista and wuz stuck in bootloader for the last two days. Tried innumerable things, i wuz crazy thinkin' that how come mtty is workin' well for others, and not givin' any damn similar option to me.

Then at last, got redirected to this thread, and upgradin' at last.

PLZ ADD THIS THREAD TO WIKI OR MAKE IT STICKY as most of the people are usin' Vista now.

God bless..

makingmesick
16th March 2008, 08:43 AM
Thank you so much for this. I was having a hell of a time upgrading the radio on my Apache in Vista. After doing this, the upgrade went as smooth as butter. Awesome.

AlExAkE
3rd April 2008, 04:22 AM
Thank you, it worked for me! The only problem is I the bluetooh is not working but I guess that is up to the rom. I'll look for a solution :))

vettau
3rd April 2008, 05:45 AM
--------------------------------------------------------------------------------

Hi everyone ! I try Update Driver wceusbshx64 for My Vista x64 in order Upgrade for BA ROM but unsuccessful. In Vista x86 (System 32) it's working best ,I don't Know why ? Erro ( code 39)
What can i do? help me ? thanhk all !

shad2pl
4th April 2008, 08:07 PM
Hi.
I have the same problem. Error code 39.
I'm using Vista Business x64. Any suggestions?

crazigamer
18th April 2008, 01:09 AM
Ok I have tried installing the new driver posted all over this thread for vista 64 bit. every time i try to install it, it tells me that windows can not load the driver. The driver may be curropt or missing. (Code 39) any more suggestions?

a_ok2me
21st April 2008, 07:27 AM
--------------------------------------------------------------------------------

Hi everyone ! I try Update Driver wceusbshx64 for My Vista x64 in order Upgrade for BA ROM but unsuccessful. In Vista x86 (System 32) it's working best ,I don't Know why ? Erro ( code 39)
What can i do? help me ? thanhk all !Same here.

mech_supernova
13th May 2008, 12:33 AM
Same here.

im getting it too, then windows update updated it and it works but it dosent work and im back at

\\.\WVEUSBSH001: No such file or directory
cannot connect to \\.\WCEUSBSH001

I have serched and did everything I could posably think of

I used Olipro worked like a charm.

possamai
25th May 2008, 03:30 PM
I don't think it really matters which rom you'll be installing :)
It just makes sure the update tool can connect to your phone..

Seems to work fine so far

ixtraz
15th June 2008, 09:46 PM
Same error code 39 on Vista Ultimate x64 sp1

transmoral
2nd July 2008, 08:08 PM
oh wow! worked for me.. HTC TyTN (HERM200) + Vista Ultimate-32 SP1.. thanks you sp3dev!! :)

enegue777
2nd July 2008, 10:18 PM
I have followed the steps. When I enter the password I get the following:

Pass.

HTCST ÚÈÒHTCE
Cmd>


What do I do?

JerraLD
3rd August 2008, 01:06 PM
I have the same initial problem would this same method work on xp pro?

danroger
3rd August 2008, 09:40 PM
the only thing i had to do was download the Windows Mobile Device Center from here (http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center.mspx), install that and so on the phone (touch diamond) on connections - usb to pc - and unchecked the advanced option then just connect the phone to the pc.

Bruca66
12th August 2008, 10:28 PM
Reupload 64bit Drivers thx

iassael
24th August 2008, 12:30 AM
doesnt work with prophet g4 any suggestions?
The updater still closes...

viperbjk
24th August 2008, 08:32 PM
So ... I implemented now an interface that works with vista with the NEW driver.

That's how it worked :
Using activesync driver, a virtual serial port (CDC) was emulated.


How it works now :
As the virtual serial port is now deprecated, WinUSB is used.
This is the interface already used by new RUU. The CDC part is only
used for backward compatibility under win9x. For WinXP, also WinUSB
is preferred (using runtime libraries, these are not needed under vista)

If anyone is interested in how the interface can be programmed, I can help :)

Cya,

Viper BJK

Tyrone777
21st September 2008, 03:20 AM
Thank you soooo much. Worked like a charm on Vista Ultimate 32.:D

crooner999
12th October 2008, 05:59 PM
thanks it works...for a moment i thought that i lost my xda exec but your input helped me!

baucha
19th October 2008, 07:13 PM
It worked great wit perfection in my vista home premium,

Thanks a ton :)

MvSt
19th October 2008, 07:26 PM
I tryed it too, and it seems to work. I can make the first steps, but when the ruu starts coping the nbf to my phone, i get a message like: "Programs Name" won't work anymore... Wait for response or close?
When i make the same under win XP i have no problems, the ruu copies the nbf to my phone.

Any reason?

(I know my english is bad, but its better than a google translation.... )

DeeJ999
20th October 2008, 11:10 AM
I tried updating my SPV M2000, the power cable come loose half way through and now all I get on the screen is Serial v2.07 on the screen.

It is dead when connected to the PC.

I am running 64bit Vista.

I have tried everything on this thread to get it working but nothing happens, it just won't connect to the device.

It also won't go into bootloader.

Can someone help me please, email me at ukcarper999@hotmail.com

DeeJ999
22nd October 2008, 09:13 PM
I tried updating my SPV M2000, the power cable come loose half way through and now all I get on the screen is Serial v2.07 on the screen.

It is dead when connected to the PC.

I am running 64bit Vista.

I have tried everything on this thread to get it working but nothing happens, it just won't connect to the device.

It also won't go into bootloader.

Can someone help me please, email me at ukcarper999@hotmail.com



Used my XP pc and it worked fine

a_ok2me
24th October 2008, 06:15 AM
Used my XP pc and it worked fineBut it does not work in Vista.

dpdurst
24th October 2008, 11:21 PM
But it does not work in Vista.

Working fine in Vista I have flashed over 10+ times with no issue. Here is how I loaded these drivers. Using Vista RTM SP1

I replaced the drivers in device manager | network connections |Windows Mobile connection. Use the Rndis cfg

a_ok2me
25th October 2008, 02:29 AM
Working fine in Vista I have flashed over 10+ times with no issue. Here is how I loaded these drivers. Using Vista RTM SP1

I replaced the drivers in device manager | network connections |Windows Mobile connection. Use the Rndis cfgVista 64? I've tried various solutions posted in '07 and early '08 and non worked.

ed33
25th October 2008, 03:02 PM
Thanks alot. This saved my phone after installing a bad radio(pc wouldnt recognise phone through usb)

Thanks again.

Sledutah
27th October 2008, 04:08 AM
Ok I have tried installing the new driver posted all over this thread for vista 64 bit. every time i try to install it, it tells me that windows can not load the driver. The driver may be curropt or missing. (Code 39) any more suggestions?

I'm having the same problems. I just setup a new computer with Vista Home Premium 64-bit and have tried every method I could find to get it working so I can flash my Wizard. The one problem that I get hung up on is while installing a new driver for the Pocket PC (wceusbshx64.inf) in device manager I get the error message that the driver is not signed, I click next anyways. I then get the following message "The driver may be corrupt or missing (Code 39)".

Any ideas? I'm going through flashing withdrawals ;)

Thank you for your help

smallprint
28th October 2008, 10:23 PM
Ive done everything on the post and i started to upgrade my xda orbit. Then it stops at 3%. Can someone help me.

goli
28th November 2008, 12:00 AM
I've installed this drivers to flash my Universal ... perfect. It worked. I can use Tomal's 8.2 version now.

But, from the moment who I change the drivers, I cannot longer use my iPod nano ! He's not reconized any more ! and this is from the moment where I've change the drivers for the one from this thread !

Any idea ?

This is a full ball of s***t, I cannot live without my ipod :D

luckycris0
14th December 2008, 10:16 AM
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.



It's been awhile since I flashed my Uni - went to the Polaris, then cheated with the iPhone 3g for bit-

Needless to say... I had to come back to what's best. Anyway, after hours of searching- you, and only you, was able to save my Uni from being stuck in bootloader!

Vista is beautiful but it sucks!

Thanks,

luckycris0.

ady1234uk
15th December 2008, 02:56 AM
thanks your a life saver

Otets_vash
20th December 2008, 03:12 PM
IMPORTANT NOTE!!
==============

once uploaded a new ROM to my HTC Uni, I thinking that problem around Vista solved.
but next time when I try to upgrade HTC with new ROM I got an error 122
I just reinstall USB drivers again, and uploading finished OK.
may be Vista always reinstall drivers.

ramtek55
18th February 2009, 07:53 PM
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.

hey i'm kinda a noob to all this so i would really appreciate the help. i just got my ba TODAY and already jacked it up. its on the 'server v2.07' screen and wont get out of it. i've tried everything, even hard booting it. i guess my question is if it's in this state, is it also in bootloader mode? and if bootloader mode is different, how do i get there?

jimmyvincent13
25th February 2009, 02:43 PM
i was struggling with mtty.exe giving error "USB can not open port" But this worked like a charm and I was able to revive my HTC

Great !!!!
Thanks a lot

kyote
12th March 2009, 06:21 AM
This works. Now I have finally made it out of bootloader. Thanks.

ohayyam
18th March 2009, 03:12 PM
Thank you very much ))) mitty and ruu worked fine for me ...

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.

Pillar 13
26th March 2009, 01:43 AM
I have vista Ultimate x64 and after much searchng I
stumbled on a solution outlined in a microsoft whitepaper
on the subject.

Press and hold F8 while starting up, and then use the up/down
arrow keys to select "disable driver signing enforcement"

you have to do this every time you start up, and then re-install the drivers,
but for the truly desperate, it is a viable option.

Best of luck

(whitepaper here (http://www.microsoft.com/whdc/winlogo/drvsign/kmsigning.mspx))
(Holy thread revival batman! :( )

mkent_barbados
27th March 2009, 09:06 PM
Does this work on Windows 7 also? I have the latest WMDC and I can activesync fine, but trying to use USPL says can't find the device...

jasondundrup
6th April 2009, 06:24 PM
Hours of struggling finally at an end. Thank you!

viperbjk
6th April 2009, 07:04 PM
Using QMAT (async modem connection) is a lot easier as it supports true WinUSB connection under Vista. No need to install old drivers that won't even work under Windows 7 and mess up your system.

Cya,

Viper BJK

shazan
11th April 2009, 08:41 PM
it is working pefectly

willykatie
19th April 2009, 12:18 AM
Using QMAT (async modem connection) is a lot easier as it supports true WinUSB connection under Vista. No need to install old drivers that won't even work under Windows 7 and mess up your system.

Cya,

Viper BJK

How to use that? Step by step how to would be useful for all of us with Vista :D

scotty1413
10th May 2009, 01:54 AM
I tried eerything I read but only this worked for me and it was all down to the USB driver,

Thanks for your help. Great post

sochalewski
10th May 2009, 08:19 PM
Hi,

What to do, when I have Windows 7 RC? I have tried this method, but when I was installing driver from archive I saw error:
http://i44.tinypic.com/fvln35.jpg

Any ideas? :)

//Oh, I done it. ;)

mooland
23rd May 2009, 02:30 PM
i use windows 7 and it work !!
thank

Xerx3sxbl
29th May 2009, 05:21 PM
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.

I finally got it to accept this driver thingy but every time I try to go through the process of installing it, it giver me this error.

http://i44.tinypic.com/16k7ryb.jpg

Running windows 7x64. Tried the enable disable usb connections thing. The device is in bootload mode. Windows is in accept unsigned driver mode. Any idea's? I've been through this thread and can't find a solution.

EDIT:

So from what I understand, this whole thing is simply because WMDC doesn't have the drivers that the USPL needs. I have an XP laptop, if I would do the process on that, would I just be able to skip it all (as it uses AS4.5)? If so, would I just be able to continue to the second part of this (http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Vista) tutorial?

EDIT 2:

I guess not. Hmmm. Well that sucks balls.

salim950
21st June 2009, 08:00 PM
thank you it worked for me on my artemis on windows 7 i am now able to upgrade my rom at any time i apprectiate your work

here is a screen shot of it working:

http://i611.photobucket.com/albums/tt193/salim950/NewPicture.jpg

salim950
21st June 2009, 08:03 PM
I finally got it to accept this driver thingy but every time I try to go through the process of installing it, it giver me this error.

http://i44.tinypic.com/16k7ryb.jpg

Running windows 7x64. Tried the enable disable usb connections thing. The device is in bootload mode. Windows is in accept unsigned driver mode. Any idea's? I've been through this thread and can't find a solution.

EDIT:

So from what I understand, this whole thing is simply because WMDC doesn't have the drivers that the USPL needs. I have an XP laptop, if I would do the process on that, would I just be able to skip it all (as it uses AS4.5)? If so, would I just be able to continue to the second part of this (http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Vista) tutorial?

EDIT 2:

I guess not. Hmmm. Well that sucks balls.

have you tried removing the original driver and then when it is uninstalled replug your device and install the drivers given in this thread, thats how i fixed the problem on mine and got it to work like in the screenshot in my previous post

a_ok2me
21st June 2009, 08:06 PM
Does anyone using Vista 64 have problems with syncing? I didn't have problems in Vista 32. The last time I upgraded, I was unable to sync via the usb in Vista 64. The only way to sync was via bluetooth.

I'm assuming this fix will also fix the sync issue.

tiqui2787
8th July 2009, 04:10 AM
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.

sp3de,

I am having the same issue except that my OS is XP. I can't figure out what the problem is after doing everything from uninstalling sync, rebooting and checking the device, hubs etc.... Any thoughts please?

Thanks :confused:

tiqui2787
9th July 2009, 04:05 AM
Actually i got it to work! turns out it was the USB cable (phone end) that was missing the internal metal pins and that is why the device wasn't being recognized. Wow never thought it was a piece of hardware after days. :)

vsuprak
2nd August 2009, 07:13 AM
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.

This stuff really worked out perfecto.
Thanks a Ton Mate! Now I am just thinking of actuallty continuing with what I started. Upgrade my ROM on my HTC Touch. Am a little scared, but I know I'll be able to do with all the support on this forum.

Thanks a ton all you guys!:D

viatama
2nd August 2009, 12:12 PM
Works on Windows Seven 32bit RTM 7600.

Thank You

antonycdp
17th August 2009, 08:56 AM
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.

This works fine, however, you might need to run an extra task. I found the best thing when in Device Manager is to uninstall the Mobile Device Driver first and also remove it completely from Windows. Then run Scan for new devices, This should fail to load the driver which you can then do manually selecting the WCExxxxxx driver as noted above.
This will work, It took me a while to get to this point Always got report in MYYT that it could not open the USB

Prerna
17th September 2009, 10:21 PM
This works fine, however, you might need to run an extra task. I found the best thing when in Device Manager is to uninstall the Mobile Device Driver first and also remove it completely from Windows. Then run Scan for new devices, This should fail to load the driver which you can then do manually selecting the WCExxxxxx driver as noted above.
This will work, It took me a while to get to this point Always got report in MYYT that it could not open the USB

Thanks, that's exactly the info I needed to get it fine on Windows7. Thank you!

a_ok2me
18th September 2009, 05:46 AM
Thanks, that's exactly the info I needed to get it fine on Windows7. Thank you!32 bit? This is key because it does not work in Vista 64.

Prerna
19th September 2009, 02:28 PM
32 bit? This is key because it does not work in Vista 64.

Yep, 32bits.

heross
13th December 2009, 03:28 PM
Thanks

works great on Windows7 32Bit and solve my problem with RUU under Windows7.

johwei
2nd January 2010, 06:02 PM
I can confirm this - it works with windows 7 (32).
I followed the excellent instructions step by step.
Thank you.

Georgeous2008
27th February 2010, 10:33 AM
So as from what I can read here, it won't work under Windows 7 x64 ?

Hujvrot
10th March 2010, 01:57 AM
Thanks a lot!!!!

FIRO....AZM!!!
1st April 2010, 08:43 PM
Thanks alot....!!!

Now I can upgrade from Vista with no problem ....you are herooooooooooo!!!:D

sdjensen
12th April 2010, 09:38 PM
I have now tried to get this to work for some hours, but I simply can't.

I get this message when trying to install the driver on windows 7 64-bit professional (tranlated with google)

The digital signature for the drivers required for this device could not be confirmed. A change in hardware or software may have meant that there was installed a file that is signed incorrectly, damaged or which may be malicious software from an unknown source. (Code 52)

I have disabled unsigned driver - what to do?

EDIT: Solved by restarting computer - pressing F8 and disabled signed drivers - oh, why isnt it enough to just disable it in gpedit.msc sigh....

comablack666
12th May 2010, 01:12 AM
This usb driver works with an ELF touch?

moinag
22nd May 2010, 01:05 PM
i am using windows 7 ultimate and when i connect my toshiba G900 for installing new rom, it says waiting for usb connection...bt after that it comes ..updating..then nothing happens...also on computer screen its written waiting for usb...plz help

moinag
29th May 2010, 09:52 AM
thank you alot for your help..its now working in my toshiba G900 and i sucessfully installed windows 6.1 rom in it.

thnak you alot 4ur help and support guys..
keep it up.

THANKS:D

micro2s
21st July 2010, 07:15 PM
thank you alot for your help..its now working in my toshiba G900 and i sucessfully installed windows 6.1 rom in it.

thnak you alot 4ur help and support guys..
keep it up.

THANKS:D

Tell me... how was resolved this, because i have same problem. I have a Toshiba G900 and i tried connect to PC with Windows 7 (x86) but i don't have a driver.

Thanks in advance!

matll
16th September 2010, 10:04 PM
Hi, for those one who already search a solution for WIndows 7 x64, thomasck found one that works (I tested it).

eheh, NP..

i just tried booting up pressing F8, using disable the driver signing or smt like that.. well, it "worked" w/o any erros, BUT, the status stills in 0%, heuehue.. oh my god..

edit

alright, i thing i can help everybody that is using windows 7 x64 (maybe x86)..

my windows version is x64, so, i installed the windows mobile center x64.. then i booted up w/ f8 pressed, e got in "disable the driver bla bla bla"..

once in there, put the device bootloader mode, plug it, reinstall the "vista_drivers", e try again..

b4, i did not tried to install th vista_drivers in signature mode, and now after install, i heard the sound meaning a device has been plugged in!

now is update like a charm :D

habarahu
8th June 2011, 10:09 PM
Sir i did every step... didn't work for me.. still stuck at bootloader

HTC ELF0100
IPL 2.20.0002
SPL 2.28.0000

is there a way i can downgrade mt SPL like before... Ver... SPL 2.20

im still stuck... can anyone help me and thanks a lot...