Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/10/21 in all areas

  1. Oh, I get it. Yeah, I got the trial and error thing. I have to think about that. Welp, that would be a better chance of revisiting Sinnoh than the remakes IMO.
    1 point
  2. that is because those are my saves. the only data from you is the box data. well, the saves I provided you are only a fraction on the mons. To reclaim the rest, you gotta perform trial and error. (my message above about altenating 0x00 and 0x20 thing) In any case, you definitely have to play the game over for other stuff, such as progress. Alternatively, take someone else's save, and change all the trainer details to yours. Yeah I kinda wish that wasn't the case. I've tried overwriting all the pairs of 0x20 to 0x00 and copy and pasting over some parts that look fine-ish, but still nothing. If we were to verify then copy over every byte, it would be possible to end up with something that looks kinda like your save. (tho do remember, your TID, SID, OT, Gender and any other important trainer data is gone, since your first 0x100 is pretty much garbage). In any case, it would be less effort to replay 500 hours, then to check every byte by byte, and see which byte allows the game to load
    1 point
  3. 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.]
    0 points
×
×
  • Create New...