Develop Bugs

Windows Vista, WM6, and Tethering

Ok I searched on the forums hard for this one so forgive me if this has already been answered. I see to find people with Windows Mobile 6 and Windows XP or people with Windows Vista but Windows Mobile 5.
Since I'm running Vista, I use Windows Mobile Device Center instead of ActiveSync. The functionality of the program is fine, so I have no complaints. However, to upgrade ROMs or anything...I use an XP Machine as it seems Vista seems to think the device disconnects upon the loading of the bootloader. I've read somewhere in the forums that there is a driver update to fix that, but after applying...WMDC doesn't work properly...so I'd save the trouble and use a machine that has XP running instead until a better fix comes along.
My 8525 came stock with a program called Wireless Modem as of ROM 1.34.502.1 shipped, which seems to have been replaced by Internet Sharing.
The Wireless Modem application worked fine after setting up the modem with the Vista driver also found in the forums. I also tested the bluetooth connection and set that up to tether as well and it worked fine.
I finally decided to upgrade after days of reading and I tried to use the Wireless Modem feature. I noticed it wasn't there and tried to use Internet Sharing. The layouts are similar...but when I hook up the phone under USB, my computer doesn't even recognize it as a new device (modem) as I did uninstall the last driver.
When connected via Bluetooth, it recognized the device and installed the driver as Windows Mobile-based device support by default. Under services, only Active Sync is only available...as opposed to before when I had Dial-Up networking available. When I set up a PAN, the computer and device are connected together, however I do get the same problem as some others with a connection that is limited or local only. So the tethering is unsuccessful.
I recently upgraded my Cingular 8525 to WM6BE v1.2 (Cingular Edition)...which I can't seem to find in the threads anymore. I'm also running Radio 1.38.00.11...but I don't think that would affect anthing. I reverted back to my shipped ROM to check for alternate settings that might have helped...then I was going to revert back to WM6BE v1.2 Cingular...then I realized I accidently deleted that custom ROM and I couldn't find it anymore. I was stuck putting on the WM6BE v1.2 on the sticky thread after which forced me to reinstall the data settings/keyboard fix from the cab files. Haven't had problems with them but I did like that customized ROM for Cingular a little better considering I really like "clean" ROMs.
Anyway, I'm attempted to connect via MEdia Net AND Cingular GPRS settings provided by the Cingular Data Settings cab floating around the forums. It works fine it seems...it just seems like the problem is getting Vista to recognize the device as a modem, or at least having modem capabilities.
I guess thats as detailed as I can get right now. Hopefully someone can help now ^_^

You are right. I tried updating rom on Vista's Windows mobile Device and end up damaging my xda2i. The device displays "USB" when connected to cradle and "Serial v1. 01" when not. Do you have a solution apart from upgrading?

Solution on Vista
Hello Guys, I'm running vista too and I bothered 2 hours before getting it done.
So this is one of the "Step-By-Step Instruction Guides".
0. Extract the attached file into a directory of your choice
1. Disconnect your Device
2. Goto Settings > Connections and choose "USB To PC"
3. Uncheck the option there
4. Reconnect your Device
5. Goto your DeviceManager and search for "HTC USB Sync", double click it and choose Drivers
6. Click on the "Update Driver"-Button and choose search on the computer
7. Click "Choose a driver from list..."
8. Click the button to the right (Open from Media)
9. Choose any INF File from the extracted ones.
10. You're done, upgrade your ROM.
11. To Rollback drivers, use the "Automatic Update" instead of Manually selecting (it will choose the newest ones)
12. Recheck the option of step 2 unless you're planning to use the slow variant.
Have Phun and Good Luck

Have I understand right? With this tweak We will be able to applied ROM upgrades to our HERMES from windows VISTA?

Confirmed.
I did already update my ROM in this way.
Cheers,
soniX
EDIT:
Please use HardSPL or something equal to be sure the risk is at a minimum.
And I can not be held responsible for any damage to your Hermes or your Brain
But as I said, for me it worked perfectly, remember to Restore the new Drivers or the Mobile Device Center will not work.

Hmm I don't think you people understand what I was asking...
I already know about that method to update with Vista...I actually tried it yesterday and for some reason it didn't work so I just use an XP Machine for now...but I was just asking merely about TETHERING.
I already have the ROMs of my choice loaded on my device.
In simpler words: How do I go about tethering (Running Internet Sharing) when my computer does not recognize the device as a modem...through USB or Bluetooth.
I'm running WM6BE v1.2 and Windows Vista Ultimate.

Maybe its Wm6BE, but I have used all the other roms (xda live, des, lsvw) and all I do is plug in the usb, start internet sharing and it connects no problem. Have to start internet sharing before wmdc starts. Internet Sharing works great, better than wireless modem. I was not able to use the WM6be due to problems with sbp pocket plus. I am currently using XDA live .30 and Vista Ultimate.

Does the technique in the post above work??
Also once that procedure is carried out can rom updates and RUU programs be used exactly the same as on XP??
If anyone is available to do some screenshots for me for an updated GUIDE, please PM me (i dont use or have a copy of vista )

I enjoy the community so I think I'll do my best to contribute to it. When I get the chance, I'll try to make a guide with screenshots on using Windows Vista and loading WM6.
I'm going to try to switch to LVSW build with his new update today and I'll see how that works out.
I REALLY like the one custom build someone made (I forgot who) with the Cingular connection settings defaulted from the Cingular Shipped ROMs...I wish I can find those files again.
It seems like the people developing the new Cingular data connection cab files are really working hard at getting the default settings as if they just bought their phoes straight from Cingular.
I'll let you know how LVSW goes with Internet Sharing and Windows Vista

sonixwarrior said:
Hello Guys, I'm running vista too and I bothered 2 hours before getting it done.
So this is one of the "Step-By-Step Instruction Guides".
0. Extract the attached file into a directory of your choice
1. Disconnect your Device
2. Goto Settings > Connections and choose "USB To PC"
3. Uncheck the option there
4. Reconnect your Device
5. Goto your DeviceManager and search for "HTC USB Sync", double click it and choose Drivers
6. Click on the "Update Driver"-Button and choose search on the computer
7. Click "Choose a driver from list..."
8. Click the button to the right (Open from Media)
9. Choose any INF File from the extracted ones.
10. You're done, upgrade your ROM.
11. To Rollback drivers, use the "Automatic Update" instead of Manually selecting (it will choose the newest ones)
12. Recheck the option of step 2 unless you're planning to use the slow variant.
Have Phun and Good Luck
Click to expand...
Click to collapse
Also, I've seen this guide posted twice...yours missing one step where I was supposed to "End WMDC.exe Process in Task Manager"
I still can't get Vista to run RUU...do you run the RUU with your device in Bootloader? I think I even tried that once and and still couldn't get it to work with the older Driver.
Not exactly sure what I'm missing or doing wrong...but its definitely after I install the driver. It acts as if I didn't install it at all, even if I check in drive details and its all correct in there.

i tried the method above for upgrading in vista and it didnt work for me...
what am i missing?

Where is it stopping?
Because I did it once, it has to work.
Where is it stopping? - At the bootloader (LSD-Screen with psychedelic colors ?) - or before ?
I will do an upgrade in the afternoon again and this time i will record ALL of my steps.
Hopefully I'll find the recept for the cake.
Cheers,
soniX

Yea it gets to the bootloader screen and I'm stuck as if I never loaded the AS4.5 drivers.

Sorry, too less time today for a screenshot-decorated guide.
I just upgraded my device again (only to proove it does work).
So here is again a guide, which differs to the first one.
I guess there are two ways to do this...
Prequesites:
- Search my previous post and download the USBAS.zip-File
- Extract it into a directory...
- You'll need your device and it has to be connected, too
The first approach:
Change the Serial-Driver
- On the device click Start > Settings, choose "Connections" there and click on "USB to PC"
- uncheck the item for "Enhanced..." there
- Click on OK.
- Now goto your Device Manager.
- Search an Item named "HTC USB Sync".
- Right-click it and choose "Update Driver".
- Choose the second option, then select to choose manually
- Select the directory where the zip has been extracted to and choose any inf file.
Start the Update-Tool
- After the driver-update you need to set the device back to RNDIS-Mode (follow Step 1 and recheck the option)
- Verify that you're running the correct drivers for the RNDIS-Device, the date in the device-manager has to be around January, 17th 2007.
- Start the ROM-Upgrade.
- It should work now.
For me it did not really work to switch from RNDIS to USB-Serial drivers in my localized (thanks bepe for the great work!) german WM6.
So if you have a problem with the first method use this one.
- Start your Device-Manager, we have to be very fast.
- Start the ROM-Upgrade as you've probably done before
- If the bootloader starts up, you'll notice a device/dettached,device/attached sound, this is your sign, goto to you Device-Manager.
- Search for the Entry "HTC USB Sync".
- Update drivers like it's written above.
- If it won't work and the upgrade tool dies with "cannot connect", don't worry. Reset your device (soft) and try again, this time you should not need to update the drivers.
Cheers,
soniX

I'm using XP and a USB cable. USed to work OK before upgrading to WM6 Black but now I get Error 797 on the PC saying modem not found or busy!

mrvanx said:
Does the technique in the post above work??
Also once that procedure is carried out can rom updates and RUU programs be used exactly the same as on XP??
If anyone is available to do some screenshots for me for an updated GUIDE, please PM me (i dont use or have a copy of vista )
Click to expand...
Click to collapse
Take a look here
Code:
http://www.modaco.com/index.php?showtopic=252977
For Vista guide with screen shots, so far i've only flashed HardSPLv4 from inside Vista, but it worked i'm still plucking up enough courage to do a full flash of WM6
Nic

I do this (for Hard-SPL, don't know for other):
I have made what it was written on modaco (http://www.modaco.com/index.php?showtopic=252977), but
1) I was not in bootloader.
2) While active sync try to connect (but it does not succeed because they are not its driver) I've stopped WMDC.EXE and now hermes is connected.
3) NOW I do a flash.
If there is something that is not clear you say it to me.

My method also works (for me)
Can somebody confirm that my method works for vista?
soniX

I'm based also to your method, but it would be more complete to integrate it with the method on modaco.

It seems that most people didn't get the point of this thread...weird considering I put TETHERING in the subject line. However, it is nice to see people trying to help others with Vista to flash. I have the same problem myself but access to machines with XP nullify my real need for flashing on Vista for now.
I'm about to reinstall LVSW's latest ROM set for the billionth time and I'll try out tethering on that. It seems that people who were on WM6BE were having a hard time with Internet Sharing. I'll load a new rom and let you know how it goes.

Using Windows Vista

I just post this thread in order to help others which are having the same problem as I am and to avoid looking arround on all the posts for this answer.
I'm so happy that I've not yet test this procedure wanted to share with you ASAP.
Thanks pvdhelm
pvdhelm said:
Follow these instructions and your vista problem is over.
I used this guide and it works for my artemis p3300 phone!
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 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
Drivers for Windows Vista x64
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.
NOTE:: This technique is still in testing so if you have any issues please post in the official thread. Until we find another way to get RUU working with vista you may need to revert back to XP for upgrading your Artemis.
Click to expand...
Click to collapse
Just test it without any problem. I confirm the feasability of this procedure.
It rocks!
Always restart after before trying. It has worked with me.

Ha, Well I have tested and all works well, after this I've flashed USPL and B&B 3.7 ROM with no difficulty.

Now if I could only figure out why Mobile device Center will not install properly on my Vista Ultimate that I just 'upgraded' to today. It connected once, ran the sync but did not back up the contacts on my phone to outlook, and now on subsequent tries, the program wont open because of 'unknown problems'.
Maybe it's a sign to roll back to XP.

uninstall wmdc and then re-install. I had this error at first but fixed now.

Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.

itschase said:
I had a feeling, I did that procedure once already with redundant results....but then again, half of my peripherals such as DVD-ROM, or wireless card didn't work, but then miraculously started working just as I was about to teach my laptop how to fly.
I will keep trying, thank you.
Click to expand...
Click to collapse
I'm not sure if that is the problem, but did you tried after restart vista?
When I made the procedure it was not working and then tried to restart and it was perfect.

Bluetooth sync works fine, but USB won't load driver. WM5 OEM, so no bootloader on my 8525. Will this solve my USB problem?

Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?

For French :
http://www.forummobiles.com/index.php?showtopic=136003&hl=nuls

scratch that .. i missed a bit

Shand359 said:
uninstall wmdc and then re-install. I had this error at first but fixed now.
Click to expand...
Click to collapse
Agreed. Some 'versions' of windows Vista have WMDC built in, it is no good, uninstall WMDC and download the version from MS web site. Once installed run Windows Update.

owencutajar said:
Hmm .. tried to follow the process above and Vista told me I already had the most recent version of the driver .. strange huh ?
Click to expand...
Click to collapse
I had this issue too, uninstall vista drivers first, then install those from XP.

I followed these directions to update my Himalaya/Alpine-like i-mate PDA2 with disappointing results -- at first. WMDC claimed there was an error and I could not get it to respond. I flounced away and pouted for a little bit, and when I came back decided the only thing I could think of to change now before re-installing WMDC altogether was to roll back the driver for the mobile devices (in device manager) and WA-LA! Pouting works! I am now able to sync and Klaus (the i-mate) plays nice with Bob (PC)... ah, household bliss!
Thanks!

i still cannot get my laptop to see the artemis when it is bootloader mode - i have the XP driver on!!!!

I would love to try it, but does anybody have a german manual, or a translation program that translates Windows English into Windows German?

help!!! my htc 3300 won't start anymore!!!

Hello,
I have 3 month's ago flashed my htc 3300 with wm6 english (pdavliet).
I have used uspl and the wm6 rom.
Today i flashed my phone again but with wm6 dutch.
And now i can't start my phone.
When i push the startbutton the phone start in de startmenu with bleu screen wich is from 02 and the phone still hanging on that screen.
I think i broke my phone i must have do something wrong.
Is there anyone who can help to get my phone fixed without sending it to the manufacturier.
Please help me i turned my phone into a brick.
I am waiting for a response (i hope i get some)
I am from holland and my phone is from mda pro 3
Thank you all

try to hard reset, if not follow the instructions here http://forum.xda-developers.com/showthread.php?t=308242

HELP me please,
I've got the same problem... it was working perfectly but at same point it freezes!! I’ve tried a soft reset but didn’t work, then tried a hardware reset but it says “Format failed”. Really don’t know what to do!
Do I have to re-flash my artemis, can I do that even if it freezes at the splash screen?
P.S.: i have the B&B 4.2
Thx very much

follow the abovr link to reflash bricked devices

Is that meaning it is brikked?
But it worked for couple of months!

no it doesn't mean it's bricked but you can't hard reset.
Maybe you can try to use uspl on it and see if it succeds, if then try to reflash....

Thank you very much
Just a last question if you don't matter can I run the UPLS even if my PDA freezes when the Spalsh screen appears?
Thank you!

I think so as the phone stops to be flashed.
You can check if the activ sync icone is green.
On another forum a guy had a similar problem, he tried to hard reset about 20 times and it finaly passed

what if i would take off the battery for few hours?
Do you think it will erase everything like an hardware reset?
Act syn dosn't get green.... and 20 hardware reset are too much
Thank you!

removing the battery won't change anything, imagin if it goes down for a few days and you don't charge it.
It's a flash memory.
The only thing lesft may be to get into the bootloader and reflash

OK.... i connected my pda to my computer and i bootloaded! But my computer dosen't reconize it and so i cannot run the UPLS
Any idea?
Thank guys

No USPL, 1st reflash your p3000 with your ORIGINAL HTC orT-Mobile Rom and correct language. WM6 is just released officially so i should not be a problem to find your ROM. In the past this was the biggest problem (no way to get the original rom).
When this is done, then USPL and change to another rom (other language and extra cherrys!).
GL
edit: To do so, put the artemis in bootloader mode, connect to usb and start RUUGetInfo.exe. Wait and see what happens . Should work fine.

THANK!!!
i'll try!

yessssssssssssssssssss
Thank you all!!!
I solved my problem. I turned my brick into a phone hahahaahh
I am very happy
How to get in the bootloader menu?
Start your phone
hold speedialbutton and softreset but still holding the speeddial button and then the bootmenu will appair (dont forget the usb cable it must plugged in before you go in to the bootmenu)
How do i get the 'wceusbsh.inf' file?
On your cd from the phone.
Before starting: Your device needs to be connected to the PC, and in BOOTLOADER mode.
Step 1 of 16: Extract this zip file to a memorable location on your machine (e.g. the desktop). 'wceusbsh.inf' This is the Activesync 4.5 RTM USB driver.
[attachment=21151:VistaRUU.zip]
Step 2 of 16: Run 'Windows Mobile Device Center', and click 'Connection Settings'.
Step 3 of 16: Uncheck the 'Allow USB Connections' box, and select 'OK'.
Step 4 of 16: Run 'Services' by clicking the Start Orb and typing 'Services', and ensure the 'Windows Mobile-based connectivity' and Windows Mobile 2003-based connectivity' services are started. If they are not, click the service name and press the 'play' button on the top bar.
Step 5 of 16: Load 'Device Manager' by clicking the Start Orb and typing 'Device Manager'. Expand the 'Mobile devices' section and click the 'HTC USB Sync' (or similarly named) item.
Step 6 of 16: Click the 'Action' menu and select 'Update Driver Software'.
Step 7 of 16: Click 'Browse my computer for driver software'.
Step 8 of 16: Click 'Let me pick from a list of device drivers on my computer'.
Step 9 of 16: Click 'Have Disk'.
Step 10 of 16: Click 'Browse', and browse to the location where you extracted the ZIP' wceusbsh.inf' file in Step 1.
Step 11 of 16: Double click 'wceusbsh.inf'.
Step 12 of 16: Select 'HTC USB Sync' from the list, and click 'Next'.
Step 13 of 16: Wait while your driver is installed.
Step 14 of 16: Run 'Task Manager' by clicking the Start Orb and typing 'taskmgr'. Then find the 'WMDC.EXE' item, and click 'End Process'.
Step 15 of 16: Install your update! Everything should now run fine! You just need to bear in mind the final step when you want to start syncing normally again...
Step 16 of 16: In 'Windows Mobile Device Center', re-enable the 'allow USB connections' checkbox you disabled in Step 2.

[HOWTO] Easy installation of drivers needed for adb/fastboot/...

Tested on Windows 7:
- start installing HTC Sync, the software which comes with your phone (and can also be downloaded from HTC web site).
- it begins with telling you it needs to install Adobe AIR, something else, and the drivers... let it continue at that stage.
- once the previous step is done and installer asks if you want to start installation of HTC Sync software -- select [Cancel]
This way the drivers needed for adb and fastboot get installed while the rest of the (not so useful) HTC software is not installed at all.

You realize that everyone on this forum knows that, don't you?

qktb said:
Tested on Windows 7:
- start installing HTC Sync, the software which comes with your phone (and can also be downloaded from HTC web site).
- it begins with telling you it needs to install Adobe AIR, something else, and the drivers... let it continue at that stage.
- once the previous step is done and installer asks if you want to start installation of HTC Sync software -- select [Cancel]
This way the drivers needed for adb and fastboot get installed while the rest of the (not so useful) HTC software is not installed at all.
Click to expand...
Click to collapse
actually ur wrong, u need different drivers for fastboot
ADB & Fastboot Guide

abaaaabbbb63 said:
You realize that everyone on this forum knows that, don't you?
Click to expand...
Click to collapse
1. There is a lot of info distributed among lots of guides, signatures, stickies, etc. Probably everything has been discussed and described somewhere some time ago. Maybe I'm slow, but it took me a while to find and figure out what is needed for what. I find short posts with quick and specific answers to specific problems/challenges quite useful.
2. Keep in mind that there are people using Google search who view xda forums in the middle of some long thread with lots of comments, trouble reports, etc. Not registered users. Maybe a short brief description will help someone?
3. I knew about stand-alone driver sets or "install/uninstall HTC Sync" way of installing the drivers, but someone may save some time knowing that it is enough just to cancel the installation after pre-requisites are installed.
Still if you think this thread is useless I will not cry and have no hard feelings if it is deleted.

jmcclue said:
actually ur wrong, u need different drivers for fastboot
Click to expand...
Click to collapse
For me both adb and fastboot work fine with the method described. There was nothing HTC-related installed earlier on the PC, it is a new laptop.
Edit: actually you are right and I am right (I guess): different drivers are needed and used for fastboot operation, but all of them are installed with the process described, no further action is needed when using fastboot later on. Windows just says "Installing drivers..." on the first use.

[GUIDE] Crash Course in ADB/Unlocking on WINDOWS

Just wanted to try and put together something helpful for those who are unlocking their devices who might be doing this for the first time or just are having issues.
THIS GUIDE ONLY WORKS FOR WINDOWS FOLK, SORRY! IF YOU HAPPEN TO BREAK YOUR DEVICE OR DO ANYTHING TO IT THAT PREVENTS YOU FROM USING, I AM NOT RESPONSIBLE, CAVETE LIBERUM OPUS.
ADB
Download ADB from here: http://developer.android.com/sdk/index.html
Make sure you install it where ever you are comfortable with, I tend to keep mine in my main installation (C: )
HTC Sync
Download HTC Sync here - http://www.htc.com/www/software/htc-sync-manager/
Why download HTC Sync? For the drivers. After the installation is complete you can remove HTC Sync, just not the drivers.
Appropriate Drivers
In your Program Files (x86) folder, there should be an HTC Folder, with the drivers in it.
What you are going to need to do is make sure that your device has the HTC drivers installed.
You'll need to open Control Panel ----> Hardware and Sound ----> Device Manager
Your HTC One should be under portable device or android phone, or something similar to that. If it is telling you the current drivers are up to date, you may need to disable driver signature enforcement, and that method is different between Windows 7 and 8.
You'll want to update the driver software by right clicking ----> Update Driver Software ----> Browse my computer for driver software ----> Browse...; then select the HTC Driver folder from within the HTC folder (you'll have to navigate to it)
If you need to disable driver signature:
Windows 7 - http://bit.ly/1bE0jZT
Windows 8 - http://bit.ly/1bE0mF7
Trouble Shooting ADB and Rumrunner
I am, in no way, saying that I am an expert in running rumrunner. If you can use irc and contact beaups please do. However, just in general, here are tips I think might work -
Go to "System and Security" from Control Panel and click "Allow an app through Windows Firewall." Click "Change Settings" at the top and then click "Allow another app...". Navigate to your extracted rumrunner file and select the soju.exe to be allowed through. Why do this? Because I personally rather not take down my entire firewall to allow this program to run. No offense to beaups, just doesn't seem terribly practical to me.
In your ADB installation folder, go into SDK -----> platform tools ----> Hold down left shift and right click -----> Open command window here
type in adb devices; if you are not seeing
List of devices attached
XXXXXXXXXXXXXXXXXX device (read the X's as a string of numbers which are your device)
then it isn't ready to be use rumrunner. You'll have to go into Settings -----> About Phone -----> Software Information -----> Then click 7 times on Build Number to unlock developer options. Go into "Developer Options" and enable USB Debugging.
As mentioned in Rumrunner, please run soju.exe AS ADMINISTRATOR, to avoid permission issues on computer-side.
OEM Cables are also ideal in this situation. Also make sure you downloaded the right file (.8 version versus .10)
Last but not least, IT TAKES A WHILE FOR SOJU TO RUN. BE PATIENT Your phone will reboot A LOT during the entire process. It'll take awhile, but if you run into the (.........) problems or an error because your drivers aren't installed correctly be patient.
The guide isn't perfect, but hopefully it helps. I'll add advice if it comes in.

Great guide!
Make sure to remember to do a fastboot devices check too. that is my problem adb works great fastboot is another story
Sent from my HTC6500LVW using xda app-developers app

It also hates USB3
It also hates USB 3.0, had to use my fiances laptop todo it, but very straightforward.