??? unpacking .dll's

I'm trying to unpack the .dll's from combat arms... i'm getting a crap load of computer language... i get some code out of it.. the rest are symbols.. i'm using microsoft visual 2008 express... is it not compatible with it or am i just tarted... and i need to keep screwing with it... any info would really help..

why unpack the dll?

i am trying to make my own bypass for CA.. and from what i've gathered i needed to unpack the engine.exe (which i have) i've even found the string that says Hack detected.. if you want a copy of this unpacked engine.exe let me know. i'll subscribe to the thread so i can keep track. if you find anything out let me know too...lol

The unpacker stub will probably be run in the executable it's being loaded into. Break when libs are loaded, wait until it's the dll you want to unpack and step through, you should hit the unpacker stub. Or find the base address of the library when it's loaded, any RVAs off of it will most likely be write\reads to unpack it.

that would be awesome... Cut down a lot of time for me!! ur the best

NVM.....................

Try learning to use OllyDBG; it will become your best freind IMHO.

olydbg open only exe so why you gave him it if he want open dll?..

do you have any suggestions... I've done the c++ tuts... i understand what the codes mean... I have now unpacked the engine.exe.. which.. really doesn't help me with what im doing, I need the d3.dll's unpacked...

Originally Posted by JangoSolo

do you have any suggestions... I've done the c++ tuts... i understand what the codes mean... I have now unpacked the engine.exe.. which.. really doesn't help me with what im doing, I need the d3.dll's unpacked...

I'm going to assume you mean D3D9.dll, trust me, they're not packed. Don't even go into that library, it's going to be really confusing to analyze. Tell me what you're trying to achieve.

Originally Posted by da_je

olydbg open only exe so why you gave him it if he want open dll?..

Actually, you can use ollydbg to debug dlls. It runs an executable, injects the dll into the executable and sets EIP to the EP of the library your debugging.

I am trying to figure out how to make my own hacks.. and since no one will really help me on exactly what code i'm looking for... I'm trying to figure it out myself...I just want to be able to access the correct code in .dll With out the computer language and nonsense... I've gone thru the C++ tutorials.. I feel like I can do this on my own.. but I need to be pointed in right dirrection on where to start... sorry if i babbled..

im taking jetamay's advise

??? unpacking .dll's

Similar Threads

Tags for this Thread