Help Cracking Buildbox(2.0)

[detrix]

Hi, I have tried many attempts to crack buildbox 2.0. But I failed. The easiest way I thought to crack the second version would be to compare the old crack version. But it seems harder than I thought. And I have tried searching for text strings and names for the dialog box that shows up when you enter the wrong code. 

Here are the software I used:

Immunity Debugger

OLLYDBG

ida64plus

beyond compare 4

 

Hope that's enough information. Please let me know if you need more. I appreciate any suggestions or assistance. Thank you.

[fellkis]

Hi, I have tried many attempts to crack buildbox 2.0. But I failed. The easiest way I thought to crack the second version would be to compare the old crack version. But it seems harder than I thought. And I have tried searching for text strings and names for the dialog box that shows up when you enter the wrong code. 

Here are the software I used:

Immunity Debugger

OLLYDBG

ida64plus

beyond compare 4

 

Hope that's enough information. Please let me know if you need more. I appreciate any suggestions or assistance. Thank you.

as I do to the like to someone , help me please

[nasty]

I study a bit the BB2 protection.

In this new version they enhanced the protection adding a packer on the .exe.

Is normal detrix that you not find the string to replace .. is all packed!

You need first to unpack all the exe file rebuilding the file (find the new OEP, rebuild IAT, ...).

 

If you not know about unpacking you can know more on google ... the simpler example that you can take a look to understand something about is the UPX unpacking (sarch on google: "ollydbg upx manual unpack").

 

 

The problem is that they have used a strange packer on.

So the first step is detect the packer used and unpack, but with this packer (on BB2) i'm useless (need a work of an expert in unpacking).

Someone "expert" can help at least to detect the packer used on??

[detrix]

I study a bit the BB2 protection.

In this new version they enhanced the protection adding a packer on the .exe.

Is normal detrix that you not find the string to replace .. is all packed!

You need first to unpack all the exe file rebuilding the file (find the new OEP, rebuild IAT, ...).

 

If you not know about unpacking you can know more on google ... the simpler example that you can take a look to understand something about is the UPX unpacking (sarch on google: "ollydbg upx manual unpack").

 

 

The problem is that they have used a strange packer on.

So the first step is detect the packer used and unpack, but with this packer (on BB2) i'm useless (need a work of an expert in unpacking).

Someone "expert" can help at least to detect the packer used on??

Thanks for the info, I appreciate it.

[blad300]

The problem is a "packed exe" , if we unpack it , everything work fine.

have also IfDebuggerPresent

[stewfeedsiento]

Have one quick question guys. Will you able to open the program by using their 30days trial key?

[detrix]

Have one quick question guys. Will you able to open the program by using their 30days trial key?

It has to be your first time because they check if your computer or email is already registered. And I used it on Buildbox 1.3.5. 

[stewfeedsiento]

I tried their blank keys and it allows me to try the verion 2.0. The problem is there are only 5 available Gameplay Settings in 30days trial. So it need really need to crack this software.

[blad300]

I tried their blank keys and it allows me to try the verion 2.0. The problem is there are only 5 available Gameplay Settings in 30days trial. So it need really need to crack this software.

 

what blank keys ?

How did you do that ? 

[kurapsing]

I study a bit the BB2 protection.

In this new version they enhanced the protection adding a packer on the .exe.

Is normal detrix that you not find the string to replace .. is all packed!

You need first to unpack all the exe file rebuilding the file (find the new OEP, rebuild IAT, ...).

 

If you not know about unpacking you can know more on google ... the simpler example that you can take a look to understand something about is the UPX unpacking (sarch on google: "ollydbg upx manual unpack").

 

 

The problem is that they have used a strange packer on.

So the first step is detect the packer used and unpack, but with this packer (on BB2) i'm useless (need a work of an expert in unpacking).

Someone "expert" can help at least to detect the packer used on??

I try to used RDG Packer Detector, BB2 is used multi protections.. Inno setup installer (delphi) and EXeCryptor v 2.1.21

Edited by kurapsing, 19 February 2016 - 07:27 AM.