>>167121861. Download the latest versions of: Pokesav, HxD (or any other hex editor) and Legal.exe
2. Create a pokémon that needs to be fixed with pokesav (for this tutorial use a Pal-Parked pokémon) into storage. Or download the pokémon I used for this tutorial
http://www.mediafire.com/?mgzjjtyttn03. Make sure all aspects of the pokémon are legal (excluding trash bytes)
4. Once you have made the pokémon, save it and close pokesav
5. Check it with legal.exe. it should look like
http://i335.photobucket.com/albums/m443/damio91/Aron_no_TB.jpg6. Now, open the pokémon in a hex editor and find the bytes 0x48 through to 0x5D
7. Find the terminator (FF FF) and count how many bytes are after that until you reach 0x5D. If you are using my pokémon there should be 12 bytes
8. Now we will actually do some trash byte fixing. We will make it seem as if it got transferred to an English game.
http://db.pokesav.org/main/?q=Trash-Bytes-Guide (other language strings here)
Migrated to English DP
18 20 0D 02 42 00 00 00 00 00 00 00 48 A1 0C 02 E0 FF
05 00 00 00 <8E - 96> 27 02 26 02 E9 9A 06 02 00 00
The first string is if it was transferred into slot 1 of Pal-Park The second string is if it was transferred to any of slots 2-6 of Pal-Park We will use the first string to make it seem like we Pal-Parked it to slot 1
9. Count from the end of the first string, back however many bytes we counted before (in my case 12)
10. Now type over the bytes after the terminator with the bytes counted out (the last 12)
11. We have finished with the pokémon name trash bytes and will now move on to OT trash bytes.
12. Look through the bytes 0x68 to 0x77 and find the terminator again (FF FF).
13. Type over the bytes after the terminator with the bytes from 2 rows up (the corresponding bytes are 0x48 to 0x57)
