Well, according to the wiki, 0xD4-0xEB are seal coordinates, so that's not a footer. There is no footer as far as I know.
In a little while when I have some time, I will run those files through some software of mine. But in the meantime, it looks like the checksum is probably different because the Encounter info is different (the infamous 0x85).
My Pokémon stuff on Google Drive!
To use (some of) my software you need the .Net Framework!
Pokémon Black 2: 1507-3503-1914
Hehe. Overlooked 0x85h So the only difference between legit pokemon & pokesav pokemon is the seal coordinates. If you set the seal coordinates to what my chimchar has (no seals), then there is no way to tell if its legit or not Thanks everyone =)
just found out that the trace that we are talking about is only in the "Seal Coordinate"
somehow there are also some traces if you write down the amount of PP left manually
.. but most probably, it can be fixed by redepositing the pokemon in your pokebox
so the remaining one is the seal coordinate ... but i believe that it will also be fixed if it is deposited in the pokebox ...
well .. here is the result of the trace
and also there are some fact that ...-- seal coordinate
at hex location 0x0EB(235h)
==> using pokesav, the value is : (0x00)
==> after using GTS trading method, the value is (0x03)
GTS will not fix hidden values, fateful encounter, trashbytes, etc etc etc ..
it will only fix the seal coordinate and the amount of PP left =_=
anyway, here is the result (PKM and BIN) for deposited GTS' pokemon and the pokesav's pokemon
as for the checksum ... it will not change ... as long as you don't write anything in the amount of PP left for each move(in pokesav) , and redeposited the pokemon in the box(in the game) =_=
and also 85h hidden value for pokemon data will be the same whether you use GTS or pokesav, it will not change =_=
Diamond FC : 1634 0973 3127