[T-Mobile myTouch 4G Slide] Blue6IX:
I kept them filed separately because I collected images from people with S-ON in addition to the S-OFF images I had.

I remember going over all of them with a hex editor line by line to compare the changes, but don't remember off the top of my head what I found.

Very near the beginning of the boot process on the device, the radio checks hboot for a sig match before moving on. If it doesn't match up, then the radio just shuts down - which also brings the boot process to an immediate end.

To fix it, you would have to get the hboot that matches the radio sig on the device or figure out how to S-OFF it... the catch is that you get no recovery, adb, or any kind of remote access with a computer. It will never boot far enough for you to see it do anything other then shut itself off.

So, not a brick because a brick means you might as well use it as one - this would be fixable but you would need to do what HTC would do to reprogram it if they got their hands on it.

I am pretty sure I remembered that I found most of rev's work when I went line by line on the various radio files with the hex editor, not the hboot, but i'd rather be safe then sorry. Kick up a hex editor and compare your hboot with the one you want to use.

Start with a question, add theory, eliminate obstacles, check theory - test.

Using the hex editor would be migrating from theory to eliminating obstacles, as you not knowing if the files are the same or not is an obstacle in determining whether or not to use it.

Before anyone comes along and suggests some snappy program to tell you if they are the same or not, try to maximize the learning experience/gain while minimizing risk. Especially on a file as small as that, I trust my eyes and brain more then something in the ram of my terminal.

Besides, if you can't do math you'll never know if your accountant is lying to you - and if you don't know what the code is doing on your machine, how can you trust it's results? Complex calculations aside for a minute - how do you know it's even looking for or at the right data? Shouldn't you go inspecting that data to see what it's looking at and if it's missing something?

Learn how to reverse engineer stuff - it's a lesson from the developer in the simplest, most concise form possible. It's a lesson from the manufacturer of that object, the design team that thought it up and the materials used in it.

The how will provide you with as many why's as you want or it takes to understand.

For as much information is exchanged posts at a time in threads across the boards here - it's really just a fraction of the knowledge shared. At such an abysmally slow rate. Reading a tutorial is the dialup of learning code. At first you need them to learn how, and throughout to progress at points, but the rate of information learned browsing code itself versus reading an explanation of the code is so vastly different it's almost incomprehensible.

The more code you read, the more code you can read, and you'll never learn if you don't just go look. If you (or anyone here) are asking questions based on how to go find something in code or how to read code or inspect parts of files (like reading in a hex editor the hboot, for instance) you will have virtually unlimited support and help across the device forums - it's only the very fine points that matter for specific devices for the most part anyways.

If you aren't browsing xda forums at large, then you are missing out on so much info before we even get into code - but i'm out of time at the moment, so:

You have your first how - check the hboot with a hexeditor as one means of determining if you can use it. Your first what should be finding a hex editor, and the answer you find either ends your search or leads to the next why, which would be "why can't I use this" and checking again with one of an unknown number of variables eliminated.

Laters!