Kaphotics

Different emulators store the RTC data at the end of the save file differently. PKHeX does not do any conversion between emulator save files. Try finding a converter online, or refer to the emulator documentation online.

Update your program. The program tells you it is out of date.

BDSP does not have trash bytes on Eggs; you can clear the trash bytes via the trash byte editor (hold control and click on the nickname text box).

Open the save file in a hex editor, and set the width to 0x1000. You can then look for the end part of each block to see where each block resides in the file. Generally, they're stored in order, but they start saving from a random block ID and loop until all are saved.

Referring to the wiki on save file structure and the recovery tool's output, your save file is missing critical parts of it (namely, blocks 0, 1, 2, which store your party, game progress, and trainer information). So there's not much to be able to recover besides box data. I copied the 3 missing blocks from a donor save file (mine) and ran it through the recovery program to even out the blocks. I don't advise trying to play the save file; only use it to recover your box data by dumping it into another save file. Pokemon - Emerald Version (USA, Europe) (1).sav

PKHeX tells you the playtime at the top of the program window. The pokedex editor opens just fine.

Probably is because of a vblank that occurred between the RNG calls, which is statistically infeasible (but not mathematically impossible, I guess). The game generates your SID & TID via two successive RNG calls (SID first, then TID) via 2 rand calls back to back. The assumption is that there should always be a RNG state that can yield the SID & TID. If we assume there is a vblank, then only 1 seed can generate the SID & TID: 0xc69e5f27 I think the community consensus was to prefer to flag these vblank splits for SID & TID save files, because more often than not, it's because the 'mon was manually created, rather than a save file lucked upon. Relevant source code in pokeruby, dug up via Copilot Chat: pokeruby/src/new_game.c at afcbea1f17d8c68b1aad22ab5ab1768cb5cf36d5 · pret/pokeruby

Edit their flag in the pokedex

The previous release had fixed the program to not decrease values that were above 999. Shortly after release, a fix was added to allow more than 3 digits to be entered. https://github.com/kwsch/PKHeX/commit/91ac18dd34cfa6871c5cafa0024629ed1102a72c The next release will be made available in the next few days along with the new Box Search feature, but if you cannot wait you can always try the Development build:

PKHeX does not support ROM hacks.

ty fixed on latest commit: Update EncounterStatic3XD.cs · kwsch/PKHeX@dd1b55c

-1 is the magic number for "can be random".

If you are too specific with your request, like having 6IV adamant for a gen3 wild encounter, then it will fail to find anything. When it can't find anything to satisfy your specific request, you need to be less specific. Click the Reset button to see what an unspecified criteria is -- IVs are frequently a reason why a criteria is impossible to satisfy.

Use the Criteria tab and ensure it is filled out the way you want. Hardy is the 0th nature, and it is the default nature of the Pokémon when you launch the program. It seems you're not specifying your criteria, thus the program is always trying to match the initial default from tabs since you forgot to specify it.

Please check the status of the event flag I listed at the end of my message. I am still skeptical that you didn't accidentally change the flag's state when trying to activate Mewtwo.