Jump to content

3 posts in this topic

Recommended Posts

Posted (edited)

I managed to get a cracked, thinned, and working (game would still run even with the thinned binary) Brothers in Arms 3 binary. And in the back of my head I knew there was going to be a code check because of the topic in Cheaters about a binary with syscall and the code check removed. The problem is that for some reason the file is not avalible anymore so I can't compare it to a clean binary.

 

I proceeded to remove syscall, and succeeded, testing with "att -waitfor bia3" because I knew that the binary would crash now that I modded it. The debugger attached, and I made the app continue and it crashed as I expected it would. And then I began to try and disable to code check. Keep in mind that the app would crash immidiatly after launch with nothing but syscall removed.

 

The first thing I did was look for xrefs to _exit, and I did find something useful: I NOP'ed a "CBZ R0, loc_xxxxxx (forgot what it was)" and that would delay the crash to all the way up to right after the loading screen with the castle on it finished. I would also like to point out that the CBZ R0, loc_xxxxxx that I NOP'ed was near the strings that said "/etc/var", "/Applications/Cydia.app", etc.

 

Could anyone tell me what to look for to be able to remove the code check? Because right now I'm going into it blindly with no knowledge on this whatsoever. Thanks! :)

Updated by Guest

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...

Important Information

We would like to place cookies on your device to help make this website better. The website cannot give you the best user experience without cookies. You can accept or decline our cookies. You may also adjust your cookie settings. Privacy Policy - Guidelines