0


All i see is what looks like hex or binary coded decimal but I can't seem to translate the codes to ascii or any thing in which i can actually read it.
In other words, how do I know what this even means???
Code:28200FA0 0000XXXX 054D23C8 49742400 054D2CF8 49742400 054D2D68 01000000 054D2DD8 01000000 054D2E48 49742400 054D2EB8 49742400 054D32A8 01000000 054D3318 01000000 054D33F8 49742400 054D3468 49742400 054D34D8 49742400 E0000000 80008000
Gecko codes aren't made to be translated into ascii, i believe. I know they're in hex, though.
Well, i know that hex is based on 16. So if you need to know what they are, you use a hex to decimal converter. But i don't know how to read hex.
you would usualy use a usb gecko to make the codes so that might help using that to understand it
nice job tipped i love them <3
wtf are you on about
He's obviously thanking tipped for this thread. Not sure why though..?
Gecko codes are not translated from any specific text. Instead they represent addresses (locations) in which the console reads the games code. Try to think of the game's RAM as a map, and gecko codes are coordinates to specific locations on that map. Obviously this is a VERY watered down explaination but it helped me understand how to read them and what to look for in the memory viewer when i first got started.
Lets take the code you posted as an example:
28200FA0 0000XXXX
054D23C8 49742400
054D2CF8 49742400
054D2D68 01000000
054D2DD8 01000000
054D2E48 49742400
054D2EB8 49742400
054D32A8 01000000
054D3318 01000000
054D33F8 49742400
054D3468 49742400
054D34D8 49742400
E0000000 80008000
Ok, lets take the very first line. the first 8 digits represent the location to the game's controller. The 2nd 8 digits represent the value for the controllers buttons. (which buttons you want to use to activate your code)
Nity you would probably see this as an If-Then command. "If" i push this button on this controller, "Then" execute this following changes to the listed addresses.
Now the 2nd line of code, the first 8 digits are the address (location in the memory) of the output you want to change. The 2nd 8 digits are the value you are changing the address to output.
The command will continue to change the address values throughout the code.
The last line is a termination line, telling the code engine that your editing of the memory is complete.
Last edited by riZe; 06-28-2011 at 06:32 PM.
A simple way I learned to read a command code is by reading MaDc0w's tut on .gsc file resizing. For a command code you take the beginning of that button layout's ( which always starts with the hex value 78 ) and copy from that hex value until the end of that button layout ( A button layout always ends before the hex values 00 00 00 00 ) and save all that junk in HxD as command_code.zlp. You MUST save it as .zlp or you can not decompress it with SimplyZip. Now open up SimplyZip, then go to "ExternalProgs" and select ZLIB(Pack/Unpack)
Then find the file you saved earlier as command_code.zlp and select "Decompress".
Now a new file will save wherever you have command_code.zlp saved. It will have no extension ( .exe, .zlp, etc. )
Now right click on that file and select properties, and rename it to command_code.TXT.
Open it up and viola, change whatever you want.
And to make it a new code again, do this process backwards.
But when you compress it again in SimplyZip, it will then save another file.
Open that file in HxD and copy then open up the original command code that you had, and ONLY replace the part of the original code you took away. ( To Decompress )
And there you have it, A new code.
P.S. please +rep me if this helped you in any way![]()
Bookmarks