[T-Mobile myTouch 4G Slide] Blue6IX:
Oh, and if we ever do manage to get our hands on a real engineering hboot - here are some of the commands we should have packaged right into the 1.45.0013:

ram_test
eraseconfig
writeconfig
readconfig
writesku
block_test
partition_test
btrouter
nfcrouter
nfcreader
heaptable
emapiTest
emapiCountryID
emapiWlanMac
emapiSetDefCal
emapiReadCal
resetautoimage
resetpreferdiag
resetRUUflag
writeserialno
readserialno
battcheck
gotofastboot
writemid
usbtestmode
eraseWifiFlash
readmbserialno
listpartition
erasebcid
writebcid
readbcid
fmrouter
bdaddress
readbdaddr
emptypagecheck
saveprt2sd
savemem2sd
savefb2sd
emapiInit
emapiChannel
emapiBand
emapiRate
emapiRateset
emapiCountry
emapiTXpwr1
emapiPkteng_start
emapiPkteng_stop
emapiOut
emapiFqacurcy
emapiCrsuprs
emapiDown
emapiMpc
emapiCounters
emapiVersion
emapiEtheraddr
emapinRate
emapiSetIrqPin
bkflash2emmc
loopback
pmic8058_led_test
get_identifier_token
checkSbl1
checkHWSecurity
powerdown
rebootRUU
heap_test
gotohboot

I keep finding reference to a 9v AC current - so maybe we need to supply the right voltage to the device to activate the ability to use some things we otherwise couldn't?

I've been on a mission to solve the S-OFF issue for a while, and i'm doing it out in the open, the way the open source community lives.

The one thing about security, be it physical locks or computer encryption/misdirection, is no security can be created that can't be broken - so HTC or any other manufacturer are playing a losing game, the best they can do is buy time until someone figures out a way around it - but there is no endgame on their side, only ours.

I can appreciate the idea behind people wanting not to release exploits they find until they are patched, and that is certainly their prerogative by virtue of finding the exploit...

...just as it's mine to freely share what I learn in public with everyone so that we can all learn from it.

I like the puzzle, and once this level is beat there is sure to be another following - i've got a ****-ton of notes and data here - reams of printed code and lots of notes pulled from a hexeditor and other methods.

As I get it organized and posted, well, it gets posted.

I'm free to do what I will with the information I find of my own accord, and this IS the open source community so... ;)

Edit: ...and I really can't give info to the people who created it in the first place, i'm sure they know about it all already given that they made it.

I purchased two of the same device and have access to two more. I paid cash money for the ability to compare data from device to device, so when I do get the chance to sit down and work on it there's a lot less head-scratching and wondering - I can see right in front of me what the differences are.

Heck, i'm about to buy ANOTHER damn doubleshot ( I really want a silver one) and that'll give me a virgin never revved or anything device now that I know how to pull the data I need off of it, so that'll speed things up dramatically.

Second edit:

After having determined long ago that hboot was simply passing a variable it read from elsewhere to show security on or off, it's been a mission to figure out where that was being read from.

Partition 3 is where the security comes from, and probably simlock too - so once both misc-versions are replaced and partition 3 is replaced with an S-OFF one, it's a matter of making sure the radio won't brick it.

I know that simply replacing the hboot will end up on a brick by it's lonesome, so the goal has been to work around the hboot in place now and just nerf it's version check against itself on the PG59IMG.zip files to enable the downgrade.

In the course of discovery, i've come to realize that the downgrade is ultimately not going to be necessary since we can just S-OFF it as it sits and skip the whole step.

I'm very, very close to a solution, and once I get the details worked out and don't brick my device (i'm overcautious) it'll be explained in detail out here on a public forum.

I'd rather not be running code on my device that I have no idea what it's doing to it - I know many others feel the same.

At the beginning I was at the mercy of the decision the Revolutionary team came to on not sharing their exploit (again, their right and I don't fault them the least) - because this was my first Android cellular device and I really had no idea what the hell was going on.

I've invested a significant portion of my life, time and money into gaining the knowledge of doing it myself so I know what's happening to something I paid a lot of money for - I intend to extend that courtesy to anyone else who wants to follow the code I write.

(yea, i'll learn git one of these days, haven't had the time to do so yet, i've been making up for that in other ways ... which are sometimes harder on me then simply commiting my changes would be but that's life I suppose)