Post: LAv8ed's Eboot Builder (TU 1.13)
Options
04-18-2015, 05:31 PM
#1
TheRealVate
Pokemon Trainer
Hey guy's, I wasn't planning on releasing this here but since Promise has decided to no longer update (we all appreciate his hard work), and the current tool of his updated here doesn't have all working functions I have decided to upload my builder here, I built this off his open source way back when and have been updating since, I also included a few extra's including a FPS to let you know that antiban has been enabled and also different color wallhack selections (only click one wallhack button) I however have not included the boot to zombies button because I do not play zombies but if you guys request it I can also put that in, full credit is given in the tool including the credits promise originally posted, this antiban is strong and has been updated from promises antiban addresses since the 1.06 tut and I haven't been banned even with using OSM's aimbot menu, I have gone22 prestige's with this with no problem, I fully intend to keep updating this as long as needed so no worries there, I also do no care about rep so you do not need to press that button, just enjoy 
(also for people not wanting to use this, or who don't think they can I included a bunch of pre-made eboots in here as well, just click the links in the tool to download)
You must login or register to view this content.
in case you guys forgot how to read and wanna continue bitching about this tool I uploaded to HELP you guys with\
You must login or register to view this content.
Since some people didn't think I gave credits, open tool and click about> credits
You must login or register to view this content.
Tool Download:
You must login or register to view this content.
Default_mp.elf Download:
You must login or register to view this content.
Virus Scan:
[url]https://www.virustotal.com/en/file/6ae219a064cec16169b172eb95cca74036a26cdd6aeacc2ad2 766371e3f34ba7/analysis/1429377843/[/url]
Use this method to help stay unbanned:
(also for people not wanting to use this, or who don't think they can I included a bunch of pre-made eboots in here as well, just click the links in the tool to download)
You must login or register to view this content.
in case you guys forgot how to read and wanna continue bitching about this tool I uploaded to HELP you guys with\
You must login or register to view this content.
Since some people didn't think I gave credits, open tool and click about> credits
You must login or register to view this content.
Tool Download:
You must login or register to view this content.
Default_mp.elf Download:
You must login or register to view this content.
Virus Scan:
[url]https://www.virustotal.com/en/file/6ae219a064cec16169b172eb95cca74036a26cdd6aeacc2ad2 766371e3f34ba7/analysis/1429377843/[/url]
Use this method to help stay unbanned:
[/COLOR]
Last edited by
TheRealVate ; 04-19-2015 at 12:19 AM.
Reason: added proof of credits given smh
The following 21 users say thank you to TheRealVate for this useful post:
The following 2 users groaned at TheRealVate for this awful post:
04-28-2015, 10:38 PM
#83
TheRealVate
Pokemon Trainer
Originally posted by Prom1ses
You might want to double check to see if the bytes are the same as the last few builds. A minor change in code can influence the use of whichever registers are used during that build. That's all pretty much determined by the compiler.
Here's an example to understand what i'm saying...
E.g (TU11): R30 = 0; if(R30 == 0) { // perform bancheck).
In this instance you can set R30 to anything other than zero (0) to make it not branch. But if the compiler during 1.13 for some reason changed to use R31 due to new code and what not, you'll need to appropriately change the bytes that set that register. If you don't... It'll look like this...
Before: R31 = 0; if(R31 == 0) { // perform ban check }
After: R30 = 0; if(R31 == 0) { // perform ban check }
Just make sure the bytes you are applying actually make sense logically when cod runs... IDA is your friend.
Here's an example to understand what i'm saying...
E.g (TU11): R30 = 0; if(R30 == 0) { // perform bancheck).
In this instance you can set R30 to anything other than zero (0) to make it not branch. But if the compiler during 1.13 for some reason changed to use R31 due to new code and what not, you'll need to appropriately change the bytes that set that register. If you don't... It'll look like this...
Before: R31 = 0; if(R31 == 0) { // perform ban check }
After: R30 = 0; if(R31 == 0) { // perform ban check }
Just make sure the bytes you are applying actually make sense logically when cod runs... IDA is your friend.
cool, thanks for the info.. ill check that out, been pretty busy with work so I haven't even poked around in ida but I will have sometime tonight or tomorrow so ill keep this in mind
04-28-2015, 10:40 PM
#84
TrillBrown
< ^ > < ^ >
Originally posted by Prom1ses
You might want to double check to see if the bytes are the same as the last few builds. A minor change in code can influence the use of whichever registers are used during that build. That's all pretty much determined by the compiler.
Here's an example to understand what i'm saying...
E.g (TU11): R30 = 0; if(R30 == 0) { // perform bancheck).
In this instance you can set R30 to anything other than zero (0) to make it not branch. But if the compiler during 1.13 for some reason changed to use R31 due to new code and what not, you'll need to appropriately change the bytes that set that register. If you don't... It'll look like this...
Before: R31 = 0; if(R31 == 0) { // perform ban check }
After: R30 = 0; if(R31 == 0) { // perform ban check }
Just make sure the bytes you are applying actually make sense logically when cod runs... IDA is your friend.
Here's an example to understand what i'm saying...
E.g (TU11): R30 = 0; if(R30 == 0) { // perform bancheck).
In this instance you can set R30 to anything other than zero (0) to make it not branch. But if the compiler during 1.13 for some reason changed to use R31 due to new code and what not, you'll need to appropriately change the bytes that set that register. If you don't... It'll look like this...
Before: R31 = 0; if(R31 == 0) { // perform ban check }
After: R30 = 0; if(R31 == 0) { // perform ban check }
Just make sure the bytes you are applying actually make sense logically when cod runs... IDA is your friend.
Brooooo
04-28-2015, 10:42 PM
#85
SONYS✮NIGHTMARE
League Champion
Originally posted by Prom1ses
You might want to double check to see if the bytes are the same as the last few builds. A minor change in code can influence the use of whichever registers are used during that build. That's all pretty much determined by the compiler.
Here's an example to understand what i'm saying...
E.g (TU11): R30 = 0; if(R30 == 0) { // perform bancheck).
In this instance you can set R30 to anything other than zero (0) to make it not branch. But if the compiler during 1.13 for some reason changed to use R31 due to new code and what not, you'll need to appropriately change the bytes that set that register. If you don't... It'll look like this...
Before: R31 = 0; if(R31 == 0) { // perform ban check }
After: R30 = 0; if(R31 == 0) { // perform ban check }
Just make sure the bytes you are applying actually make sense logically when cod runs... IDA is your friend.
Here's an example to understand what i'm saying...
E.g (TU11): R30 = 0; if(R30 == 0) { // perform bancheck).
In this instance you can set R30 to anything other than zero (0) to make it not branch. But if the compiler during 1.13 for some reason changed to use R31 due to new code and what not, you'll need to appropriately change the bytes that set that register. If you don't... It'll look like this...
Before: R31 = 0; if(R31 == 0) { // perform ban check }
After: R30 = 0; if(R31 == 0) { // perform ban check }
Just make sure the bytes you are applying actually make sense logically when cod runs... IDA is your friend.
Bro this is just a bad copy of your eboot hes just copy and paste he doesn't even know wat are you talking about
That's why he. Hasn't update this shit he's waiting for someone to update your eboot then he will update this bad copy of your tool
Sorry my English I'm french
The following user thanked SONYS✮NIGHTMARE for this useful post:
04-28-2015, 10:43 PM
#86
SONYS✮NIGHTMARE
League Champion
04-28-2015, 10:49 PM
#88
TheRealVate
Pokemon Trainer
Last edited by
TheRealVate ; 04-28-2015 at 10:51 PM.
04-28-2015, 11:57 PM
#89
TrillBrown
< ^ > < ^ >
Originally posted by NIGHTMARE
Bro this is just a bad copy of your eboot hes just copy and paste he doesn't even know wat are you talking about
That's why he. Hasn't update this shit he's waiting for someone to update your eboot then he will update this bad copy of your tool
Sorry my English I'm french
That's why he. Hasn't update this shit he's waiting for someone to update your eboot then he will update this bad copy of your tool
Sorry my English I'm french
Lol what a dick
04-28-2015, 11:57 PM
#90
SONYS✮NIGHTMARE
League Champion
The following user thanked SONYS✮NIGHTMARE for this useful post:
04-29-2015, 12:02 AM
#91
TheRealVate
Pokemon Trainer
Copyright © 2024, NextGenUpdate.
All Rights Reserved.
