Poke J

For myself I spliced the save into 3 parts: save A, save B, and then the reset of the save. To get a grasp of the situation I spliced both saves into their 14 data blocks. Then I checked the save index of each of the 14 block to see if they were all the same. Save A had 10 matching blocks that had the same save index and Save B had 12 matching blocks that had the same save index. Meaning that save A had 4 blocks that was a duplicate of an existing block in the save and save B had 2 blocks that was a duplicate in the save. For either of the saves to be valid the save will need all 14 blocks and not missing any section ID numbers from 0-13. Do note the blocks are not aways 0-13 and rotate each time you save. So after the first time you save the block order will be 13, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 but all must be present in a rotating numerical order. In your case you were lucky as blocks 0-4 were intact which include trainer info, team/items, game state, misc data, and rival info. If any of those blocks were missing that block would have to be provided from a doner save and you would have to use PKHeX to modify the data to match what you had before. In addition you PC box A was intact with the rest of them being empty. So then I stitch save A back together in numerical order 0-13 to make sure I didn't miss anything and the missing blocks were just PC boxes which I duplicated one of you empty boxes to fill out the save. After that I made sure all the section IDs were in the correct order and updated the section IDs of the added box blocks so all 14 sections were present. Then I placed the save into the save A spot and duplicated it into the save B spot that way both saves were valid and then stitch on the rest of the save that I spliced off. Afterwards I opened it in PKHeX to make sure it loaded and used it to export the save to update the checksums. Then loaded the save on an emulator to make sure it was good to go. For the record this is the first time I did a fix where I had to fix the save blocks so I was learning while I was doing this. All of these steps can be condensed and made more simple. Edit - Use this to help understand how the save is structured. https://bulbapedia.bulbagarden.net/wiki/Save_data_structure_(Generation_III)

Looked like the there was an interruption while saving so there where duplicate blocks in the save. There may be a bit of data loss but unless you had things in your last boxes then there shouldn't be too much loss. Pokemon - Edicion Esmeralda (Spain).sav

@AnneVM the bad news is there seems to be a lot of corruption in the save. When opened it in a hex editor there are large chunks were the data is just repeating values where there should be data, and trying to fix that manually is currently beyond my current understanding for gen 3 save file. The good news I was able to extract about 70 Pokémon from the file. I'm not sure if that is all of the Pokémon since the tool I used wasn't designed with Pokémon extraction from save files in mind. If there are important ones missing let me know and I can take another look. I've sent you them in a private message.

Without more information I think I know what might be going on. That Alakazam, I'm assuming you caught it in your gen 6 game and to simulate the trade you just changed the species to Alakazam. You are just missing a step to properly simulate a trade. On the "OT/Misc" tab you will find a section labeled "Latest (not OT) Handler". Put a word or letter into the textbox so it is not empty. Then set the "Current handler" drop down menu to "OT". The reason it is working in gen 7 when you move the Kadabra over then change the species is because the Pokémon is no longer in it's original game so the "Latest (not OT) Handler" information is filled in. The "Latest (not OT) Handler" shows that the Pokémon has been traded or transferred at some point in the past. However, do note that on the gen 7 game the "Current handler" drop down menu will be set to "HT" and that is because the Pokémon is not with its original trainer anymore.

Sorry, for not responding sooner. I didn’t see the notification. I’ll have to take a look at the program and fix it. I honestly haven’t looked at it since launch since I assumed no one was using it.

I have never tried mGBA to dump the RAM. Keep in mind when you do get the RAM dumped keep a backup of the save in case of corruption.

When you do any edits in HxD you’ll save it and then open the save in PKHeX and save it with PKHeX. The edit with HxD causes the checksum to be invalid and saving the file again with PKHeX will fix the checksum. That’s why when the value is changed back to the original value the save works again because the checksum is correct t once again.

@Miguel B I looked at the saves in a hex editor and unfortunately there is absolutely nothing there to recover. The file is filled with repeating FF hex values so there is nothing that can be done.

If you’re just wanting to know the natures and abilities you might want to check out speed running communities and talk to people who run categories that include the World Tournament. I’ve been told that they have information like that for gen 3 and 4 games so there is a chance they have gen 5.

When you say stats are you wanting to know natures and IVs or the raw stat at numbers? Are there particular trainers you’re wanting to know about or is it the entire facility? Are you trying to recreate certain trainers Pokémon? Have you checked out the Bulbapedia page for the World Tournament? Some of your answers might be there in the trivia section.

You’ll want to select the game that the Jirachi is being sent to. You do not do RNG manipulation on Pokémon Channel or edit the Pokémon in Channel (Channel doesn’t have any Pokémon). The Pokémon is generated in the target game that gets the Jirachi. The Channel option is there so the right method to use for Jirachi information.

From the looks of it that save file you’re trying to load is a Pokémon Channel save file. PKHeX does not support that game. Even if it can open the save file there are no Pokémon to edit in the file. You’ll need to load the save file and transfer the Jirachi to a GBA game.

@Benjamin. without opening the files I can see the Lugia, Salamence, and Snorlax are not legal. All XD Pokémon have the faithful encounter flag so the summary would state it’s from a faithful encounter. I’m not at my computer so I can’t say what’s wrong with the first 2, but I’ll go out on a limb and say they are not legal either. Did you modify all 5 of these in some way?

Computers do not let you remove hard drives from one computer and up it into another and have it work on that computer. That is a security feature to prevent data theft.

@jojo12100 I’ve been thinking about this this past weekend. I think there is a good chance it’ll work. All someone has to do is try it out. If it doesn’t I just need to get my hands on a RAM dump for the target generation and I can get it working. For the record I don’t have these builds and don’t plan on tracking them down. If the application needs updating I’ll need someone to donate a RAM dump of the target build.