Exploding Frogs

It doesn't seem to have been any block. The file itself was being rejected, as far as I can tell, since copying all the data in the file (00000 to 655FF) and Ctrl+B at 00000 in the the new file had the game accepting it as not corrupt. Somehow. For some reason there was an actual difference between that and just using the old file.

Yes, I did. Well, that won’t be necessary anymore. I have fixed the problem. Shortly after my previous post, I thought to myself, “if copy-paste-writing the data from the new file to the old still has the old file read as corrupt, what will happen if I copy-paste-write from the old file to the new, which has never yet been rejected?” And, well, it worked. Even though it had no right whatsoever to do so. ??? In any case, thanks for all your help. I’d have never stumbled upon this…solution(?) if not for your suggestion to swap out blocks.

Um, bad news on that front. I did the first half of the save, and it was rejected as corrupt. Then I did the second half of the save, and it was also rejected as corrupt. Yes, even though the fresh save as a whole loads with no trouble. I then tried replacing the entire save at once with the data of the fresh save. (That is, I used Control + E to select the entire fresh save file from 00000 to 655FF, then copied and paste wrote from 00000 on the old save.) This was still rejected as corrupt. But the fresh save itself still loads fine. Even after being imported into and then exported from PKHeX. I’m starting to wonder if perhaps there is no file corruption; the game cart (which, I reiterate, is physical—not a digital download) is just refusing to accept this one file. Is that a thing that can happen? Did you ever check if you could load the save in question? Because knowing whether this issue is specific to my game/console/SD card would be quite helpful right now.

It has now been 48 hours, so I hope I don’t come across as impatient or ungrateful when I ask if this is still a thing that is going to happen.

Sounds great, except for the part where I know nothing about hex editing and thus have no idea what you just said. I’m willing to learn, mind you, I just have no idea where to even start. Sorry if I’m being obtuse, but could you point me in the right direction?

This sounds promising. How would I go about doing this?

I have already extracted my mons myself. The file loads correctly in PKHeX, so there was nothing stopping me from doing so. Thank you for the offer, though. I am more interested in finding out what exactly is causing my game to register this save file as corrupt (including Time Machine-recovered backups from before it started registering as corrupt, bizarrely enough) and if anything can be done to fix that: Should I switch to JKSM instead of Checkpoint, perhaps? Or would the Partial Savefile Fix Tool work? I haven’t tried deleting the secure value because I am under the impression that physical carts don’t use it, but is there some similar security measure that the save file is tripping? Stuff like that.

Yes to all. Name is correct, (lack of) extension is correct, no other files in the same folder, PKHeX doesn’t have any problems with the file, and Pokemon X doesn’t have any problem with new game saves even after they’ve been backed up and restored with Checkpoint.

With the SD card. I didn't even know there was any other way to do it until I started searching on this topic.

Pokemon X claims my save is corrupted, but PKHeX loads it just fine. Here's what happened: 1) Edited save data. Mostly just editing items and Pokemon, but since I was on a breeding spree, decided to edit O-Powers so I could use S- and MAX-level Powers--in particular, the Hatching Power. Selected Max Everything box. 2) Restored save (via Checkpoint, if that's relevant.) Attempted to load save. Game informs me that save is corrupt. 3) Did a few rounds of editing corrupted save (which loads fine in PKHeX, as mentioned) to see if removing the O-Powers will "uncorrupt" it. No dice. 4) Replaced corrupted save with backup of unedited save. 5) Tried the O-Powers thing again, just to check if it really was that and not an error elsewhere in the process. Save registered by game as corrupt. 6) Attempted to replace corrupted save with unedited backup. Found that backup no longer existed. Realized that I had inadvertently moved the file instead of copying it. 7) Used Time Machine (I'm on a Mac, and run PKHeX via a Windows 7 VirtualBox) to recover backup. 8 ) Restored save. Attempted to load save. Game informs me that save is corrupt, which is surprising since this is after all a backup from before the save was edited. 9) Used Time Machine to recover earlier backup of save, accepting that I'd have to lose a few hours of progress. 10) Restored save. Attempted to load save. Game informs me that save is corrupt. This is rather alarming. 11) Used Time Machine to recover even earlier backup from a month before this whole fiasco happened. Attempted to load save. Game informs that save is corrupt. At this point, it becomes clear that I have no save data that the game will recognize as uncorrupted. At some point during all this mess (I don't recall exactly when) I tried erasing my save data with D-Pad Up+B+X, saving, and then restoring the old save data with Checkpoint. This did not fix the problem, but it occurs to me that it might have in some way made things worse. I also took the opportunity to check if Checkpoint was the problem by backing up and restoring the new save, but the new save loaded normally. From what I've searched online, it is probably not anti save restore at work, because my game is a physical copy of Pokemon X, not a digital copy. Unless Pokemon XY has some other form of save "protection" that my save keeps tripping? Attached is a copy of my save. I would really rather not lose this save, though since it loads in PKHeX I can at least salvage my Pokemon if worst comes to worst. main