Database Info

Are you having problems upgrading your Universal to Crossbow?

99% of your questions can be answered by the wiki.
The main points are below. Please try and follow these instructions yourself before you start asking the questions everyone asks every week (sometimes every day) somewhere on this forum
Detailed Instruction On How To Upgrade with Bootloader method
Instructions for those stuck on Boot Screen
Instructions for those with Country Code error
Upgrade bootloader from 1.00 to 1.01
Instructions for those stuck on Boot Screen (UNI_exitbootloader)
If you have genuine problems that are not solved by reading these solutions, and performing the steps they say, then by all means, ask the question, but please, please please, don't fill the forum with useless questions that have been answered hundreds of times already.

Thanks for your help. but, i got errors with your link.

Sorry but they all work fine for me. Which link in particular are you having problems with?

All links are working fine here.
Nice job !!

Not my work, I'm just linking to the wiki pages that people are to stupid and lazy to look for themselves

So, the problem is me or my machine.. donna know...

By the way, upgrading bootloader is not necessary - everything works with BL 1.00

mamaich said:
By the way, upgrading bootloader is not necessary - everything works with BL 1.00
Click to expand...
Click to collapse
thats interesting, someone reported to me that 1.00 wasn't working (i have 2.01 so dont know )
OFF TOPIC:
how can i extract a bootloader dumped to sd card in windows or mac or linux? (preferably mac or linux cause they have sd card readers and i can't find my usb one)

Just to confirm that mine's still working fine with Bootloader 1.00 (as if anyone would doubt Mamaich!)

freezing problem with ActiveSync 4.2
Do not connect the Universal to your desktop unless you have ActiveSync 4.5 installed in the desktop or it will freeze your device.
Disable ActiveSync connection in Universal until ActiveSync is updated.

ActiveSync 4.5 beta 2
http://www.redirectto.com/?go=645c1c6e5b

Regarding instruction 7:
# Put the Universal in bootloader mode by pressing Power + Light + Reset, which brings up an un-backlit screen with "Serial" at the top, and "v0.XX" at the bottom. (A lot of people get an error message if they are not in bootloader mode. They can install the ROM a second time. If you are in bootloader mode, you won't get an error message.)
I dont get what you mean by press Power + Light + Reset? Are you talking about the button on the phone? On my O2 XDA Atom Exec there is no light button..cuz when i open the bootloader exe it goes this is not a valid win 32 program. Bootloader is not meant to be opened from the PDa but from your computer but i cant open it.

>> # Put the Universal in bootloader mode by pressing Power + Light + Reset
> On my O2 XDA Atom Exec there is no light button..cuz
So, is an O2 XDA Atom Exec an HTC Universal then?

ivorh said:
>>
> On my O2 XDA Atom Exec there is no light button..cuz
[/b] then?
Click to expand...
Click to collapse
Probably why it doesnt work..so i cant upgrade to WM6? I realyl dont get why Australia only have the ATOM and not the Exec?

Quick Question
I upgraded to WM6CB which I aquired from torrentspy, and the upgrade was sucessful. The device turns on after upgrade, and the extROM loads up. After the reset, a window pop-ups saying that I have illegally aquired this ROM. Im not sure what I did wrong. I used the maUpgrade file aswell. Any help is appreaciated.

davidw89 said:
Probably why it doesnt work..so i cant upgrade to WM6? I realyl dont get why Australia only have the ATOM and not the Exec?
Click to expand...
Click to collapse
In Australia, The HTC Universal is branded as the I-Mate Jasjar.
Cheers,
Ray.

neptune said:
I upgraded to WM6CB which I aquired from torrentspy, and the upgrade was sucessful. The device turns on after upgrade, and the extROM loads up. After the reset, a window pop-ups saying that I have illegally aquired this ROM. Im not sure what I did wrong. I used the maUpgrade file aswell. Any help is appreaciated.
Click to expand...
Click to collapse
I've never seen that, sounds like someone's either added in that popup as a joke, or it's from a ROM dump of one of the RTM or MVP builds, and your devices IMEI is different to the one it was for.
I know MVP's had the option of getting Crossbow, but they had to send their device to Microsoft to have it flashed. Perhaps these builds have something coded to the IMEI.

used BL 0.60 successfullty
Midget_1990 said:
thats interesting, someone reported to me that 1.00 wasn't working (i have 2.01 so dont know )
OFF TOPIC:
how can i extract a bootloader dumped to sd card in windows or mac or linux? (preferably mac or linux cause they have sd card readers and i can't find my usb one)
Click to expand...
Click to collapse
I could use BL 0.60 successfully

Hi!
I have using it for 2 days. Initailly it seem difficult to install soft. But now easer, the RAM still down like WM 05, Soft Reset time quite longer then Ivan test 2's ROM. But the icon look very nice.

Alan, i think u should add the solution for "stuck in the bootloader" problem, by using UNI_exitbootloader.exe. this is much simple than using mtty IMHO.

Windows Vista VS Flashing Firmware or Radio ROMs!

Upgrade OS pocket pc (RUU file problem how to solve ) in Windows Vista
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.
http://mahmood1.com/Documents/USBAS.rar
http://mahmood1.com/Documents/64bit.rar
Best reguards to mahmood

NetrunnerAT said:
First of all, connect your device when it`s in bootloader.
Click to expand...
Click to collapse
done.
NetrunnerAT said:
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
Click to expand...
Click to collapse
done.
NetrunnerAT said:
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
Click to expand...
Click to collapse
they were already running
NetrunnerAT said:
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
Click to expand...
Click to collapse
in the 64bit.rar there are drivers in the ruu-work-64bit folder and in the wce.zip. i tried both for my vista x64 system.
NetrunnerAT said:
then, kill wmdc.exe with any taskmanager
Click to expand...
Click to collapse
i also killed the mobsync.exe
NetrunnerAT said:
You are Ready. run ruu or connect MTTY.
Click to expand...
Click to collapse
the ruu simply crashes while trying to connect to the device. luckily the flash didn't start yet.

Not that you need this in pictures, but someone may:
http://www.modaco.com/index.php?showtopic=252977&st=0&gopid=814012&#entry814012
Anyways, I've got this fix working for the NVID ROM, but it won't work for other RUU-based upgrades, such as the one from PDAMobiz WM6 1.0. Perhaps there are different versions of the RUU utility that require or use different components.
Something else that is odd is that the drivers packaged in the "64 bit" rar are the same ones packaged in the VistaRUU.zip found in the Modaco link above, and which work on my 32-bit OS. So, they may not be 64-bit drivers at all.

Yeah I live in New Zealand and I think the 700wx here are different somehow. For example I don't think mine has a bootloader period.. I tried all 400 ways of getting it into bootloader and all I get is a reset back to normal screen no tricolour.
Weird but unless I can get it into bootloader first I don't think its going to get anywhere. Which my palm 700wx just doesn't have I think.

i managed to do it with vmware on vista. tried all these methods but the programs crashes all the time, luckily not frying my 818pro as well!

I have the same experience. The NVID RUU works, but al others don't. By the way, the NVID also work with only the "old" drivers installed, not dis-allowing USB connection, not starting in bootloader and not killing wmdc.exe.
I don't know for sure, I noticed the RUU Utility version is newer. But when I just switch the nb.nsk file, I get an error, or it crashes just like before. Can it has something to do with the fact that the NVID RUU updates the SPL as well?

floepie said:
Not that you need this in pictures, but someone may:
http://www.modaco.com/index.php?showtopic=252977&st=0&gopid=814012&#entry814012
Anyways, I've got this fix working for the NVID ROM, but it won't work for other RUU-based upgrades, such as the one from PDAMobiz WM6 1.0. Perhaps there are different versions of the RUU utility that require or use different components.
Something else that is odd is that the drivers packaged in the "64 bit" rar are the same ones packaged in the VistaRUU.zip found in the Modaco link above, and which work on my 32-bit OS. So, they may not be 64-bit drivers at all.
Click to expand...
Click to collapse
Try running command prompt as Admin and type
bcdedit /set nointegritychecks on
Then try again to install the 64 bit driver. It should work

I have just found the answer for Prime2007, i have a telecom treo 700wx and the previous codes for the bootloader didnt work for me either however if you go into your dailpad and press ##8778# your phone will reboot into bootloader also there is not colored strips just the treo logo with some numbers at the top.
If you want to exit without making changes you will have to pull out your battery

Unfortunally this doesn't work, as mentioned, with things such as Radio ROM update only...
If anyone finds out how to make it work for those I'd be greatly appreciative.

hey guys .. i follows all your step . but i still cant run the ruu sucessfull .. help please.. thanks

completed the tutorial exactly, and continued taking the same problem.
I get the same error. Help please.

Do you have a G3 or a G4 device? (G3 seems to work under Vista, G4s do not.)

l3v5y said:
Do you have a G3 or a G4 device? (G3 seems to work under Vista, G4s do not.)
Click to expand...
Click to collapse
Is G4 my prophet.
No have a solution?a new utility updater for Vista is posible?
Thanks.

HTC Tytn II recover from bad flash

Hi.
I have not posted much on this site, yet I have used it plenty of times. And first off I have to say "Thank you oh so very much" to everybody who frequent this site. Most of all I would like to thank the developers and rest of the crew that helps users on a daily basis.
I've had plenty of phones the last few years: 9090, 9100, Tytn and now Tytn II - all of which have been flashed - successfully I might add - with software and aid from you guys. (Ok, so my Tytn nearly ended up as a paperweight, but with some fancy maneuvers using the CE SDK from Microsoft I was able to use it as a PDA again)
Now, I am stuck. Really stuck. (Not saying I'm not to blame, but I am still stuck)
I've got a Tytn II (The P4550 HTC Kaiser 120 I believe). A few weeks back I flashed this with Alex's Home ROM (http://wiki.xda-developers.com/index.php?pagename=Alex's ROMs). At the time I was running Radio 1.27.12.11, and continued to use it after the Alex flash.
That worked perfectly.
But being interested in always trying new stuff I yesterday decided to flash Alex.v5.WM61.HTC.302.UltraClean.ROM.beta2. And it really went bad.
I studied up on many postings (obviously not enough) and started the process:
#1: Hooked up the pda to my computer
#2: HardSPL v1
#3: Tri-Color mode and activesync grey
#4: Started the upgrade with KaiserCustomRUU.exe
Everything went smoothly until it hit 99% - there it stuck and the program ended with a communication error. My computer runs Vista (yes, I know. I wont even consider flashing another phone using Vista), but it has worked flawlessly 25-30 times before.
Anyways, what happened when I tried to recover was that the phone went into tri-color mode. Needless to say it was unable to recover. After much back and forth I reinstalled an old laptop with XP (as mtty does not work on Vista) and was able to boot it back in to the OS using a walk trough from this site - cudos to Laurentius26 for the post)
Anyways - it came back. But since it failed the flash I tried it again to make sure it finished properly. What I did was flash back the Alex Home ROM I had in the first place - that worked. Then I flashed back the 1.27.12.11 Radio ROM - which failed - seriously.
It hung on 17% and when reset it would only boot to tri-color. And this is where I am now.
Every time the phone resets it boots to tri-color. I've done and redone the mtty (with and without the task 28), but it stops in tri-color mode. If I at that point hook it up to mtty and issue the boot command it will boot properly, but thats kinda annoying - having to carry with me a XP laptop for each time I have to reset the phone. (Ive also tried the set 14 0 when the phone is in this state, but it will still only boot to tri-color)
So - what now?
I've tried flashing the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship, but it stops with 294 - invalid vendor id. I've tried flashing the same ROM with HardSPL installed - no vender id error but it fails at 16%.
In desperation I've tried HTC_Kaiser_NL_ROM_1.56.404.6_Radio_22.45.88.07_1.27.12.17_Ship, but this also fails at 16%.
I've studied many a post on this site, but have so far been unable to recover from this error.
Is there any hope of regain the much needed functionality of normal booting?
Hopefully there is.
Thanks in advance.

Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo

Laurentius26 said:
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Click to expand...
Click to collapse
Most definetly.
These were also posted by e-men in another topic this morning so I am currently installing Windows XP on a computer at work to try this.
Will report back.

Laurentius26 said:
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Click to expand...
Click to collapse
Woohoo!!!
XDA wins again.
The proper commands for the mtty worked like a charm.
Thank you kindly Leo, this was much appreciated.
Now for a question if you have the time: Since I started this process yesterday I have not been able to flash a Radio rom properly. It stops on 17% or 99% and quits with communication error. Any ideas?
And can I trust that my phone now works?

Cool...., thank you
Would you like to give this a try as well maybe?
http://forum.xda-developers.com/showthread.php?t=366014
I never tried to flash a seperate radio ROM, I'm a 'chief de cuisine' so I cook it in
Cheers,
ulfthomas said:
Woohoo!!!
XDA wins again.
The proper commands for the mtty worked like a charm.
Thank you kindly Leo, this was much appreciated.
Now for a question if you have the time: Since I started this process yesterday I have not been able to flash a Radio rom properly. It stops on 17% or 99% and quits with communication error. Any ideas?
And can I trust that my phone now works?
Click to expand...
Click to collapse

WM6.0 and WM6.1 radio's are different, they are not compatible!
So be carefull which radio version you are flashing
Info about radio versions:
http://forum.xda-developers.com/showthread.php?t=349375
Cheers,

Laurentius26 said:
Cool...., thank you
Would you like to give this a try as well maybe?
http://forum.xda-developers.com/showthread.php?t=366014
I never tried to flash a seperate radio ROM, I'm a 'chief de cuisine' so I cook it in
Cheers,
Click to expand...
Click to collapse
But of course - now that I know how to reset.
One comment: I absolutely love the Palm SMS program added by Alex in his rom. You know if this is manually installable?

This is threaded SMS isn't?
That's default in WM6.1.
But if it's a seperate program there must be a cab out there.
I will have a look if it's that good you say!
Cheers,
Leo
ulfthomas said:
But of course - now that I know how to reset.
One comment: I absolutely love the Palm SMS program added by Alex in his rom. You know if this is manually installable?
Click to expand...
Click to collapse

Laurentius26 said:
This is threaded SMS isn't?
That's default in WM6.1.
But if it's a seperate program there must be a cab out there.
I will have a look if it's that good you say!
Cheers,
Leo
Click to expand...
Click to collapse
Well, good is subjective ... but I love it.
As for the updating: halted on 16% - communication error.
*Looks around - "Where's my mtty"
How can I get pass these updating issues?

Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
See if there are applications running on your desktop.
Disable your Firewall for example...
And please take your storage card out.
Some tips....
ulfthomas said:
Well, good is subjective ... but I love it.
As for the updating: halted on 16% - communication error.
*Looks around - "Where's my mtty"
How can I get pass these updating issues?
Click to expand...
Click to collapse

Laurentius26 said:
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
And please take your storage card out.
Some tips....
Click to expand...
Click to collapse
And all good tips Leo.
OS: Windows XP SP2. Freshly installed. Only Activesync 4.5 added.
HTC: Is orignial. Patched a few times using HardSPL
Original rom: As mentioned above I've tried a couple of them, but both ending in invalid vender id.
And no usb hub present.
Another comment - the flashing done today and yesterday has been done from two different xp computers - but with same result.

Laurentius26 said:
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
See if there are applications running on your desktop.
Disable your Firewall for example...
And please take your storage card out.
Some tips....
Click to expand...
Click to collapse
hehe... really? Remove my beloved SD card? Of course - always do.
No need for firewall as there are no nic's. And also no applications.

I'm going to upload a shipped ROM for you, this one if you didn't try it yet?
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
Another question... did you use Custom RUU with ROM update?
http://forum.xda-developers.com/showthread.php?t=334890
ulfthomas said:
hehe... really? Remove my beloved SD card? Of course - always do.
No need for firewall as there are no nic's. And also no applications.
Click to expand...
Click to collapse

Yup - that one has been tested - fails with invalid vender id.
Also tried flashing that rom with HardSPL - comm. error.
And no, I have not tried the Custom RUU. Will for sure try that now.

The Custom RUU is the same file that is included with your 6.1 Rom isn't it? If so I have used it with your ROM.
Do you think I should try it with another?

Yes... try with another shipped ROM please?
ulfthomas said:
The Custom RUU is the same file that is included with your 6.1 Rom isn't it? If so I have used it with your ROM.
Do you think I should try it with another?
Click to expand...
Click to collapse

Tried custom ruu with Radio 1.27.12.17.
Same results as other flashes - halts at 95%.
Seems like OS flashing hangs at 17% and Radio at 95%.

Use one more time MTTY, clear all FATS and I've send you a PM.
ulfthomas said:
Tried custom ruu with Radio 1.27.12.17.
Same results as other flashes - halts at 95%.
Seems like OS flashing hangs at 17% and Radio at 95%.
Click to expand...
Click to collapse

If you're getting an invalid vendor id it sounds like your hardspl or superCID isn't working correctly. Before going any further it's probably best to go to your bootloader screen and check that hardspl is still installed.
After that, I'd try flashing from the SD card.

Good point ach2, but when launching HardSPL and starting the update it lists the correct data on the bootscreen (Jumpspl or something equivavlent to that)
Leo: Looking around xda I found an article about dumping the ROM from another device. In the same thread I found a link to dumped original ROM. I patched that and it worked like a charm.
My PDA came back to its original state.
After arriving home just now I thought I would give your ROM another go, but same result - stuck at 16% (With HardSPL and Custom RUU)
What can cause this?

Stuck on the "boot" screen

Hi,
I tried to upgrade the ROM, unfortunately we had a power cut (sod's law haha) and my PC cut out. Now when I try to turn my XDA on (o2 exec) all I get is a dark screen with USB at the top and V1.01, I've tried the recovery tool included in the update but obviously didn't work because windows doesn't recognise the device.
Any ideas would be MASSIVELY appreciated.
btw I've tried doing a hard reset and pressing 0 but it just resets the device to the above screen =/
Thanks,
Lee

Just Re-Run The Rom Upgrade Utility And Reflash The Rom.
Regards,
OllieD

Tried that several times, the problem is that Vista isn't recognising the device thus the rom flash can't find it. Ive been through all the Wiki how-to's with no avail

Ive Never Flashed With Vista And Never Will.
I Read There Was Issues And Didnt Think It Was Worth The Risk.
Its Never Wise To Run Flashing Software In An OS It Wasnt Designed For.
Anyway Flash With XP And Your Problems Will Be Gone.
I Dont Think XP Even Recognises The Device When Its In Bootloader The Flashing Software Just Knows What To Do, Although The Software Wasnt Designed With Vista In Mind.
Regards,
OllieD

leedavid said:
Tried that several times, the problem is that Vista isn't recognising the device thus the rom flash can't find it. Ive been through all the Wiki how-to's with no avail
Click to expand...
Click to collapse
There are some year 2004 XP drivers available for Vista. Do a search and you will find it.
It is too late and I am tired. If you can't find it then I will try to help you later.
Good luck and don't worry as nothing is wrong with your device. Wrong drivers for PC.
KOR!

If nothing else works, try using mtty to erase the device, and reflash!
Oh, and word of advice: Never flash with Vista, it f.cks your device! Always do your falshing with XP, that's the most stable out there...

mzalan said:
If nothing else works, try using mtty to erase the device, and reflash!
Oh, and word of advice: Never flash with Vista, it f.cks your device! Always do your falshing with XP, that's the most stable out there...
Click to expand...
Click to collapse
I always flash my devices on Vista, and never had any problems. Though, you have to have proper XP 2004 year driver installed.
KOR!

leedavid said:
Tried that several times, the problem is that Vista isn't recognising the device thus the rom flash can't find it. Ive been through all the Wiki how-to's with no avail
Click to expand...
Click to collapse
Do you try to flash via a hub connection? Because it's recommended to connect the device directly to the PC!

brother go to this link your problem is fixed
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
or this
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
respectfully

King of Rapture™ said:
I always flash my devices on Vista, and never had any problems. Though, you have to have proper XP 2004 year driver installed.
KOR!
Click to expand...
Click to collapse
well, yeah. but in that case, I could argue that the driver, which counts, is from XP
But anyway, most people here would recommend against flashing in Vista, unless you must. XP is just a lot more stable, and causes fewer problems. but let's not get into which is better, shall we?

help!!!!!
hey guys, ive been stuck in this bootloader thing for ages now its been a day ive had no luck so far im using vista myself and there is no XP computer available to me unfortunately. the mtty utility says cannot open ports, im not using a hub either and the unit_exitbootloader.exe does not help either i need some serious help please. the screen is stuck at USB on the top (whe i take out the usb cable it says Serial on top) and v1.00 on the bottom. please help, ive got vodafone v1640 version of universal. thanks in advance

Frustrations with RUU

I just got my brother's MDA (mine got worn out), and he had upgraded to a TNT WM6 build (not sure which one). I would like to either downgrade back to OEM T-mobile, or try another of the WM6 builds.
The problem comes when I try to run RUU, with the T-mobile version, it gives me an error and wants me to start over, with the SNN 3.1 upgrade, it just shuts down RUU and with both errors it give me the tri colored screen. When I remove the battery and restart, it loads normally.
I have a G3 wizard, IPL/SPL: 2.26, I'm running Vista on my pc, and I have the latest Windows Mobile Device Center. Also the phone is cid unlocked from when my brother upgraded. This is driving me nuts. I am relatively new to the whole rom flashing world, so any thoughts would be appreciated.
As a side note, I also can't get Wizard Service Tools to work, it won't detect my phone, so if that's part of whatever suggestion might be made, I can't really use that.
Thanks.

have you tried flashing from bootloader?
Camera/reset combinaion?
the idea is that you put it into bootloader first, then run the ruu.

Simple answer to all of your problems is Vista,its still not compatible and has many problems.Do it on WinXP,there won't be any problems and its highly recommended.
Secondly,WST_4.2.2 will not work in Bootloaders,it must be run on a working OS.

Agian...
And again, And again, and again...
Why is a thread saying that is a proved method to flash by vista?

Which version of VIsta do you have ?
see this tutorial i have written for flashing RUU in Vista : http://forum.xda-developers.com/showthread.php?t=428469

Hey ather!!!
ather90 said:
Which version of VIsta do you have ?
see this tutorial i have written for flashing RUU in Vista : http://forum.xda-developers.com/showthread.php?t=428469
Click to expand...
Click to collapse
Is there a special version for vista that works? maybe changing the thread name especifying the Version could helps? wich is it? home basic? Bussines? Ultimate?

lol, i meant which Bit do you have, is it a 32-Bit version or a 64-Bit version ?, if its 64, the above tutorial will work...but you have to find the 64-bit version drivers

hi, I've updated a rom before but never on vista 64 where can I find this driver?

64-Bit Drivers :
http://mahmood1.com/Documents/64bit.rar
Notes :
1. YOUR DEVICE MUST BE IN BOOTLOADER BEFORE CONNECTING IT TO THE PC
2. If you are running Windows Vista 64-bit, then driver signing verification is on. In order to turn it off, and, thus, load this driver, you have to reboot the machine and turn driver signing verification off.
When the OS starts to load, hit the F8 key. That will bring up the boot options screen. The "Disable Driver Signing Verification" choice is towards the bottom of the list.
3. if you are running SP1 on your system...updating these drivers will cause RUU to crash when you try to do an upgrade.
4. If you get access denied, try closing your AV and disabling your Firewall
Hope this helps