[HTC Wildfire S] Kierandw:
I have had the same problem with the screen and the debugging, I did however find a kind of workaround for the debugging issue.

I searched for hours and hours for posts on how to enable debugging via ADB command line. The bottom line is that you can't. When I say you I mean "us plebs" can't. I have read the arguments about security and I say cool fair enough. I also noticed that when you run the RUU with the phone connected via USB the RUU activates "USB Debugging" on the handset irrespective of if it was enabled via the handset menu. I can understand this is done for obvious reasons as the RUU is supposed to be an easy way for end users to update their ROM's. It does however beg the question of how a stock ROM can alter the USB debugging switch on the phone via software/usb interface and the rest of the internet claims it is not possible via ADB/command line. Anyone who seems to ask about it is immediately suspected of being a phone thief and the forum responses become a mud slinging match.

So I did some experimenting with the HTC Wildfire S:

Basically I ran the RUU and left it on the Readme page running in the background I could then access the handset via ADB. I don't know ADB well but I was able to see the device listed using adb devices where as before I got nothing. When in Fastboot mode I saw that the handset was also receiving data via the Console on the PC using the fastboot reboot type commands.

It didn't really help me too much as all I wanted to do was update the stock ROM to see if it resolved my touchscreen issue. Unfortunately it didn't. So I'm still stuck with a fully functional handset minus the touchscreen.

I then decided to try and unlock the bootloader so that I could try with a custom ROM. Following the process on HTCdev I got a "Radio" update for the handset. At first I couldn't load it because the base ROM was too old. I found the latest update. It failed with a USB connection error. I found an older version about halfway back between what I had (X.1.33.X) and the new (X.2.16.X) this was (X.1.66.X). It worked but the "Radio" update still needed the latest version. I re-ran the latest RUU and it failed with the same error.

Determined to get it done here is what I did:

1. Re-Ran the (X.2.16.X) Installer

2. At Readme screen I navigated to the standard %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)

3. I copied the entire contents to a folder on my desktop

4. Closed the (X.2.16.X) Installer and re-ran the (X.1.66.X) Installer

5. At the Readme screen I navigated back to the %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)

6. I pasted and replaced all the files back. Now you get a lot of failures because the Intaller is runnning so I just skipped those files.

7. Went back to the installer running in the background and completed the process.

I used the older installer to flash the newer ROM. I have no idea which files (apart from the rom.zip) were critical but if you copy only the rom.zip it fails on the device when checking the security certificates.

After that I successfully flashed the "Radio" update. The next step in the HTCdev process is to get a device ID via a Flashboot command. I still couldn't do this because the touchscreen still wasn't working after the update. So I Re-Ran the (X.1.66.X) Installer and left it in the background. The phone went into debug mode and I could run the command. I got the info and completed the process with HTCdev. This gave me a unique file to unlock the boot loader.

I then used the same method to get into debug mode and used the HTC Wildfire S All-In-One Toolkit (http://xdaforums.com/showthread.php?t=1809751) to unlock the bootloader with the file HTC sent me.

I now have an HTC Wildfire S with the latest stock ROM, Bootloader unlocked and still no working touchscreen. This took me the better part of 10 hours. When I have the energy to continue I'll try a installing Root and custom ROM.

I apologise in advance for the RUU version number above being severely shortened but they have so many versions of the RUU depending on where you are and who your provider is and such, you will need to do your own research on the specific RUU's you will need and where to get them. The method to get debug I have illustrated should not change if you use a different version of RUU. If you're lucky your stock ROM is also updated and you can skip that part or the RUU you do download works without the tweaking l had to do.