Universal Software brute-force version ver2.0

With the deepening of the understanding of the assembly code and the improvement of the level, the study of PJ suddenly generated a dream one day, why do we manually analyze the section where the core code is located, why can't I find it? Why can't I use my mind to automate the program and achieve the goal of improving PJ? Why are there password computing tools such as od automatic shelling scripts, WinRAR, and lucky cracking tools on Android? Why don't we try it? The following tools are born.
Modify call and jxx specially (for other codes, modify the code separately)
Use the following brute force cracking tips:
One (HOP) will die, and nine (90) will be Hu (changed to NOP)
One (HOP) and one (EB) serve (changed to JMP)
When my wife dies (74) (change), my wife does not (75)
No wife (75), no wife (74)
Dad died (84) (changed) Dad Wu (85)
Dad Wu (85) (changed) Dad died (84)

Use of this product: keypaster + Disassembly tool + code purification tool + address conversion tool + hexadecimal modification Tool
A variety of operating skills are concentrated and suitable for beginners who use PJ. If you compile intermediate players (you can find the source target range to effectively reduce the code range)

Quickly achieve the goal of cracking down without detours.

It also takes time and luck to crack. If you can narrow down the scope of the Code, the speed of everything is naturally high. Otherwise, you can only try your luck ~~~

Insufficient: The shell Edition program is limited, with fewer judgment conditions.

After two weeks of success, the program has changed 7 or 8 hexadecimal modification tools and finally found the most suitable (@_@)

Screen recording demonstration (including the Unpack password !)

Download the master program of the universal software brute-force cracking program:(Including the unpacking Password !)