theSLAYER

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.]

@Lt. Lynx am I right to assume that Ivysaur wasn't extracted by Pokesav? (the decryption previously failed, and I had to change a single 0x20 to 0x00)

I guess Pokesav just auto corrected 0x20 to 0x00, or just outright ignored those bytes. I too found a Donphan but it required changing 0x20 to 0x00. Your save is filled with a bunch of 0x20 that shouldn't be there, and a bunch of random data that is all over the place. It just looks like Pokesav is ignoring everything that is not used by the program, but in reality your save has a bunch of nonsense data is other areas. So just give up on this save.

Nope it's not just a header. Stuff like Trainer name and TID were there. I was also trying to find the party data, and it appears like this: I'm trying what I can. BTW, were there any blank slots in your party? You remember any PID they were supposed to have? edit: "PokéSav still reads them flawlessly" - that sounds like a lie. I don't see any proper data structure reminiscent of a pokemon.. Well, the save is a big mess, and beyond saving. Since you managed to extract the mons, I won't have to put in effort to try to convert data and look for mons.

@Lt. Lynx yes, because Pokesav is known for the being the authority of save data /s Elaborate on what you did to "damage the save".

Read and follow the guide:

The shiny Xor needs to = to 1. It's either Ctrl + Click on the shiny button.

Just to be clear, you're not trying to make it roam before you defeated E4 right? In your original scenario, E4 was defeated and it was once roaming right?

Thanks for reporting. Do you have a "before roaming save" and a "after roaming save" that is directly after the before roaming we could use to document it?

So the matter has been resolved. Anyhow, I'm gonna use this to document my findings until I get I get a separate page done.

good plan, hopefully you get a cheap one in working condition :3

You're gonna have to install Homebrew on your Wii. (hack your Wii). Only after you do that, are you able to run the homebrew. Instruction on how to run this homebrew app (after you hacked your Wii) should be in the about me description of the page I linked.

I think you may need homebrew on your Wii, but there's a method to dump your GBA save via the link cable from the Wii. https://github.com/suloku/gba-link-cable-dumper/releases/tag/0.2

VC - stands for Virtual Console. The thing on the 3DS. Nothing do with the issue you have on hand. Also, just to ask, you got a Wii and also a link cable?

It's probably stored as a full encrypted Pokemon file (an ek5). So if you already know where the PID is, just rip out the section (the size of an ek5), save it as a ek5, and see if PKHeX would read it. Also, this tool rips out all pkx in your ram (if you need it):

mind showing me a picture which exact plot you're referring to? I can try to work it out in my free time.

I don't know how the berry planting system works, but if you have a save that is before planting the berry at that spot, and a save directly after planting a berry at the spot, we may be able to try to work something out.

that's not the issue you're having. For what issue they are having, they still have proper functioning saves, just in the wrong size. What you're getting doesn't even qualify as a save. It's just garbage data.

yeah the GB/GBC games needs memory batteries. Gen 3 games didn't need memory batteries. RSE only had batteries to keep the RTC running. No idea what a SI file is. It's just this small file: Maybe we need to scour the net to check anyone that got Flash Boy working on their FRLG game.

Could potentially be a thing. Where is Silver's save stored at again? Also, if you could find a friend with a GBA cart of a Pokemon game, maybe could try backing those up too. Could be used to prove or disprove the theories we have.

yup. and it's always the same line of repeating rubbish. either it's reading from somewhere it's not supposed to, or the program is hiccuping and panics and keeps sending out the same stuff. Also, this is a long shot, but cleaning the contacts with some non-corrosive cleaning alcohol and try again. If not, just gotta find a working program I suppose. We pretty much know the hardware is working, so we just need to supplement it with a working software I suppose.

Yeah it's a proper Silver save. Also, if you saved over the corruption, it means you're back to a proper working save, no need to worry. I still think the software is not handled to deal with version 1.1 saves. So far it reads GB saves just fine. If only you have a Version 1.0 FireRed cart we could test with.

try dumping those saves and view the file with a hex editor, see if the files are different from each other. no worries, catch ya when you're back.

well, that would explain why you had to buy this. Not that I'm recommending anything to buy, but I got a second hand NDS lite below $10 (before shipping costs shot through the roof due to the global situation), and a cheap NDS flashcart may be able to do the job. Basically to run homebrew to read, dump and restore saves on GBA carts. Anyhow, in yet another different direction, do you have other GB, GBC or GBA carts to test with this?