Support Rthlauncher With Retail Default.xex

[Schewe 1]

My RTE worked fine but I wanted to title update Halo: Reach to 1.1 so I extracted all the files from my retail Hard Drive, applied the update, disabled RSA checks in the xex, etc.

Anywho, long story short...

Obviously this updated default.xex is going to return a "failed to load socket error" when launched with rtelauncher.xex so my question is, how does one go about setting up the default.xex to work with rtelauncher?

I know there is a modded xex that comes with the rte files but it's either: 1) not title updated or 2) not updated to my specific update.

Sorry if it's a dumb question or has been answered before but I've already searched a bit and found nothing.

Edited June 30, 2012 by Schewe

[Lord Zedd 1,771]

There isn't a TU1 xex out there with secure sockets.

To set it up yourself, make sure the xex is unencrypted and uncompressed, then change the byte at offset 0x77 to "40". Then use an early version of xextool to convert the xex to devkit and then back to retail.

Though it is recommended that you just install Neighborhood and run XBDM.

[Schewe 1]

Ah sounds good, thanks. One last question... actually having trouble with disabling RSA checks. Is it even possible to disable them in a not-clean default.xex? I've tried doing so with Reach Unlock but the game just freezes at the intro. I do have "-ignore" added to properties in the shortcut too.

[Lord Zedd 1,771]

Ah sounds good, thanks. One last question... actually having trouble with disabling RSA checks. Is it even possible to disable them in a not-clean default.xex? I've tried doing so with Reach Unlock but the game just freezes at the intro. I do have "-ignore" added to properties in the shortcut too.

ReachUnlock only works with non-TU. Patch with the TU ppf from here:

[Schewe 1]

Following your guide, patching a clean .iso extracted default.xex with the TU ppf returns a "game can not be started" error when attempting to launch it.

Edited June 30, 2012 by Schewe

[Lord Zedd 1,771]

Following your guide, patching a clean .iso extracted default.xex with the TU ppf returns a "game can not be started" error when attempting to launch it.

You need to apply the ppf to a TU xex.

Either make one with the xexp file from the TU package or use "ReachTU1.xex" from Halo Anniversary.

You will also need patched dlls from the dllp's or from Anniversary.

[Schewe 1]

Ah I see. I had tried that too but had the same problem. I already have the dllp's I extracted from the iso in the game folder.

I need BOTH ppf patched non-TU xex and TU xexp in the game folder, and just launch via the xexp to play with the title update? That's just the last part that's got me confused.

Thanks for your patience, I hate asking so many stupid questions as much as you probably do answering them.

[Lord Zedd 1,771]

You need to patch the dllp and xexp files over the files of the same name using Xextool.

And of course make a copy before patching the xexp so that you can jump between both versions.

So your root folder in the end will have:

wavesLibDLL.dll - patched with the "wavesLibDLL.dllp" file from the update.

waveShell-Xbox.dll - patched with the "waveShell-Xbox.dllp" file from the update.

default.xex - clean rip, no change

*defaultTU1.xex - patched with the "default.xexp" file from the update.

*defaultmod.xex - patched with blueflames nonTU ppf.

*defaultTU1mod.xex - patched with the "default.xexp" file from the update, then patched with the blueflames TU ppf.

"waves" folder:

L360.dll - patched with the "L360.dllp" file from the update.

Q10.dll - patched with the "Q10.dllp" file from the update.

Files I put a star by can be named whatever suits you.

[Schewe 1]

Ah, problem solved! Thank you very much sir, you are an evil genius.