So now we have two S-OFF methods that are (almost) finished? Why didn't we concentrate our effort on one?
Two methods are better than one
I'd say we keep one of them as a backup,preferably the one that is 'Noob Friendly' so that we dont get "My phone's bricked!!! &%!@ You" from Non-readers
First you need to test if RUU (with diferent partition layout) is instalable to phone (that have another partition layout), than we can test exploit! Another thing. How you expect that s-off will be finished when no one want to test an simple ruu thing? Do not forget, wfs phone have two versions, one version is diferent than another version, there diference is only in two diferent nand partition layout... did you ever tried to install that diferent ruu that have diferent partition layout than your curent rom installed... etc? I just waiting that info first!
Forgot which one ruu I extracted but you must to have/find and install ruu that contain hboot_1.03.0001_181386c9.nb0
but ok I will do it for you if you are ready to test! First try to install that rom and let me know if you have success! If you have allready an rom that you tested allready (contain hboot 1.03.0000 than you no need to install http://xdaforums.com/showpost.php?p=19094201&postcount=45) please let me know
C'mon... if this works I'll have a go...
@munjeni could this brick my phone??? My mum would kill me...
Sent from my HTC Wildfire S with Beats Audio using xda app-developers app
Well, I patched misc.img just for test (without risk for brick) but before I continue to prepare hboot, first I want to be sure if misc exploit working! What you need to test now? You need to install this patched misc.img! Best way to do that is:
Please let me know! Password for archive I will send you by pm!
Do you want to upload hboot to an server and send me a link (no need whole ruu just hboot only)?
Great! Ok, I will patch hboot today (not surre) but tomorow for surre! I think today we will test it
Well I basically did a lot of of low-level (mostly hardware) stuff to the phone recently, not so much actual development. I found out how to configure OpenOCD (don't know whether the configuration is any good, since lots of values are more "good guesses" than actual knowledge but at least it's a starting point). I found how to get the board to boot without being attached to the Lithium cell which is not important for getting JTAG access (because this works as long as the board has power supply, being booted is not neccessary for JTAG to work) but will later be needed for tracing through the boot code, since the phone won't boot without what it thinks is a Lithium cell.
Apart from that munjeni and Antagonist42 also seem to make progress, but I must admit that I wasn't really able to keep track of all the things that they were doing recently. So basically we're now down at the actual physical layer and messing around with the electrical stuff that's going on on the phone's board and trying to find a way of actually talking to the processor to get the on-chip debugging working.
The far goal will be getting a patched HBOOT that has signature verification removed loaded into the device's memory via JTAG, then flash a patched HBOOT image via Fastboot. If this works it will be the first S-OFF GSM WFS that's neither shipped S-OFF nor turned S-OFF via xtc-clip, but this might still be a long long way.
).... I'll leave page as-is until I can sort it out Thankyou for your patience... and thankyou dropbox for the total lack of any idea of what went wrong 
~ # cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00040000 "misc"
mtd1: 00500000 00040000 "recovery"
mtd2: 00340000 00040000 "boot"
mtd3: 10400000 00040000 "system"
mtd4: 02300000 00040000 "cache"
mtd5: 09600000 00040000 "userdata"
mtd6: 00a00000 00040000 "devlog"
mtd7: 02fc0000 00040000 "radio"
~ #~ # cat /dev/mtd/mtd7 > /sdcard/radio.img