[T-Mobile myTouch 4G Slide] Blue6IX:
We already have the solution.

I found a leaked PG59IMG.zip file signed by HTC that will install on a doubleshot and bring it to the 1.45.0013 hboot and 1.55.531.3 software version.

Another member here wrote a fantastic guide stickied in the dev section on how to use that package to fix the unlock problem.

IF you are S-ON before flashing, then you will not be able to get S-OFF afterwards, so if you are still on the 1.44.0007 hboot use the rev method to S-OFF first.

This file I found looking for a real RUU for our device (we don't have one) and I was searching to find a way to S-ON an already S-OFF device (mine).

I figured it out and posted how to do so, and turned one of my doubleshots back to S-ON.

I know the HTC unlock method works on the PG59IMG.zip I found, because I just unlocked that phone last night so I could flash kernels to it for testing.

The next step in the S-OFF issue for 1.45.0013 hboot is a doozy, and there is really no trail to follow so we are devising a solution out of thin air mostly.

That step requires a kernel hack, and so while working on that yogi2010 and I have been systematically working our way through the kernel code isolating all of the issues we have to overcome to make the file system writable where HTC doesn't want it to be.

Meantime, while we are working our way through the kernel code we are fixing what we see - might as well not waste the time invested anyways and i've been dabbling with the kernel code since release. You can consider the kernel project in dev to be tangential steps towards the S-OFF issue, however oblique they may appear.

Unless someone comes up with a different way, or some sudden flash of inspiration strikes someone and they post it here, we're at the stage where it will take time and patience. We have to find, identify all the code preventing us from writing to the filesystem (even though it says we have...) - and some of it's still unaccounted for.

After that... we have to keep reviewing and analyzing the code until we find a weakness or vulnerability that we can exploit to do the rest of the process we have sitting and waiting to be employed...

Pretty much all of my me-time has become doubleshot-time, and any spare moment I get to choose how to spend is spent on doing something for the device in all but the rarest of cases. This issue is a big thing on my mind and I want to knock it out, but it's not quick or easy.

I had two perfectly fine S-OFF doubleshots, and went way far out of my way to figure out how to make S-ON happen so I could go backwards just for this problem. I couldn't get a clear enough picture of what you guys were going through, so the best way to help was to kiss freedom goodbye on a device and lock myself in with you until the answer was found.

I just threw it through the unlock process from HTC last night so that I could use it to help test kernels - the second device is for dev purposes and being able to test two kernels simultaneously in real time is of more value to the S-OFF problem then leaving the phone locked. I can always re-lock it later.

(yes, accounting that it may be different on mine then a virgin device, but it's already been S-OFF'd too once, so the best I can do is find a probable solution that doesn't brick the device, and then find someone to test if it works on a device that's never been meddled with.)

Just wanted to let you know i'm still behind this all the way, especially since I got a hat (device) in the ring now too. It just doesn't seem like much is happening but nothing could be further from the truth, there's just a whole lot to do between here and being able to try again.

Any interest, thoughts, ideas or even just people saying they're still interested here and there is helpful because it keeps any one of the people actively or semi-actively working on this updated on who they can contact for testing or if they need info.