My bad, I got confused by my own comparison windows. I meant Blastoise
I don't need the files. Was just asking whether you have a working copy of it ><
I had to perform trickery on the data to try to get it to decrypt.
0xFFs are normal, if they're at where they're supposed to be.
What is not normal is having absolutely no 0x00 in your save. Which I figured it was all replaced by 0x20.
The way decryption works is, every bit of data has to be unchanged, in order for decryption to work:
However, there are times where 0x20 can appear 'naturally'. How would I know if that value was meant to be a 0x00 (that got replaced to 0x20), or was already a 0x20 ('naturally' occurring 0x20, not a replaced 0x00)?
Here's an example where using trial and error, and keeping a 0x20 unchanged, and modifying the other to 0x00 led to your Charmander: charmander.ek4
Anyhow, here are two of my saves, each populated with your boxes.
One of it only has pairs of 0x20 changed to 0x00,
and the other has every 0x20 changed to 0x00.
As a result, there would be some Pokémon that appear in one but not another.
(As seen in the image with 2 windows of PKHeX above)
Pokémon Edición Platino dañado.sav
Pokémon Edición Platino dañado ver2.sav
The Charmander I provided earlier is one of the mons that are not covered by both versions of the saves, because it has multiple singular 0x20s, where one is natural and one is replaced. So if you want to salvage those mons, you gotta dump them manually and replace the bytes and see if it decrypts via trial and error.
Edit: Also, your extracted PKMs won't work in PKHeX, because pokesav dumped the sanity bytes (normally 0x0000) as 0x2020.
[because that's how they're saved in your save. It merely copied the incorrect bytes over.]