theSLAYER

No. Such a method only worked when HOME was first introduced. Has since been patched.

Yeah I get it. Was just answering your question + providing additional context.

Doesn't matter whether there's any demand, as the lead developer does not intend to include it. My (probably incorrect) base assumption is that it would be extra work when they're doing it for free, yadda yadda, etc. As inaccurate as it would be, you get how it's unfair to the lead developer to do something they don't wanna, right? Tagging me here won't be of any help; I don't use macOS. Find some way to boot windows somehow, then boot PKHeX. Most, if not all, of present day methods, revolve around that.

I just wanna say your save size is incorrect. It's clear you're using Nocash. And that line only appears when your settings is incorrect. We cannot render any more assistance, as it is evident that your save is from a pirated game.

As for the Pikachu, whether it gets added to PKHeX depends on whether there’s any documentation to confirm the various relationships to its RNG seed, like PID, IVs and OT gender.

Have you tried to hatch a nonshiny one?

Yup, most gifts do not have preset origin game. And it's not something a "normal person" can identify too, unless they transfer the mon away (cause only then origin game would be identifiable, as region name). Most gifts do not have preset origin game, and they normally just follow the received game. The ones that *might* have a preset origin game, are usually copies of mons belonging to real life trainers, like champions of VGC and stuff. That's why the Met location in Gen 6 is Route 7. It imitates the fact that it was a bred Tyranitar. (In the wonder card, you'll see there's an Egg Level and Met level. If you look at my app near the bottom left corner, it's the 1 and 55 respectively) edit: anyway, some of the info (in a more visual format) can be seen here:

Bulbapedia presumably never mentioned it has the origin game locked to X, because that's data one would normally not get to see unless one transfers out. They only mention games that can receive it, not origin game the file was preset too. Also, it's not confused with those two you linked. Look at the OT on my app. I'm looking at the right wonder card. Assuming you're referring to this. For the record, this is my app, not PKHeX. Also, the filename says "ORAS", because that is how the nomenclature for our files work. ORAS is the only pair of games that can receive this event. However origin game is preset to X, regardless of what game you receive it on. That is all there is to it. I've already given you the accurate recounting. It should be Kalos, since origin game is preset to X.

The shininess would normally depend on the hatching TID/SID...

Looking at the wonder card, the Pokémon was distributed with the Origin Game locked to X. Hence, when transferred up, it'll say Kalos. So PKHeX is working as intended.

Long story short, I think this is a an artifact of you messing around with saving into EmuMMC, and then transferring into SysNAND (which may or may not be successful). There's also a chance your EmuMMC and SysNAND is presently "synced", so there's already some weirdness when handling saves. (While this is thoroughly irrelevant to you, at some point I talk about 'syncing'. More background: sometimes, an odd thing happens, where injecting a save into Emu causes the save to appear in Sys. So people expect it to be fine, to just inject into Emu. However when the Emu/sys 'desync', they'll complain to the forums that injecting stopped working, when in fact, you're not supposed to be able to directly inject into Sys from Emu; it working previously is unintended. You likely have to do some kind of transfer mentioned in the video [I did not watch it].) In any case, this is not related to PKHeX, and until someone can reproduce it purely using SysNAND (no EmuMMC installed), I'm more or less convinced it is related to your setup. I sadly won't be of much help since I don't use your setup. edit: If your present EmuMMC is made recently, and it's made from a recent SysNAND, your profiles may very well be linked. Try injecting a save with Checkpoint in EmuMMC, and see if it shows up directly in SysNAND (like reboot your system and check).

In that case, it's likely illegal because PKHeX does not have checks implemented for it. Just carry on with it.

Before I answer that, are you injecting the edited save into EmuNAND, but trying to use HOME with SysNAND? (And hoping the edited save somehow goes into SysNAND when it was injected into EmuNAND?)

@Snackedfor it there any chance you're using EmuNAND/EmuMMC for CFW on your Switch?

Upload said file. Also where is the file from? Looking at it, there is a chance it is custom made, and the maker missed some important details.

You can go to the PKHeX page. There's an option near the bottom of the page (before comments/reviews) that let you change the version to download.

as in she can't be reached or she doesn't say anything? Doesn't sound mighty normal, but as long as it doesn't crash the game it should be fine.

no worries. Just let me know here if the save doesn't work out for ya.

Try this. Import the save as battery. It might start off from a slightly different spot than where you were at. (1) 6149 - Pokemon - Black Version 2 (USA, Europe) (NDSi Enhanced).sav (1) 6149 - Pokemon - Black Version 2 (USA, Europe) (NDSi Enhanced).sav

yeah my program doesn't deal with dsv, only sav files.

from what I can see, I've made some edits to that post while you were replying, and you didn't see them. It's just further elaboration for the most part. But yeah, it feels pretty definite to me. I tried looking at both saves and they were the same. My program was able to recognize them as saves due to the right halves still existing, but without the left halves we can't really obtain useful data. Yeah in any case good luck with the new journey. And remember not to tempt fate and let the battery die. Cheers.

There's no usable data whatsoever. The identifiable sections in each block is missing. It's not as easy as a checksum fix; this line sounds like you were just trying to repeat what I've said previously back to me. And based on what else you've said, you clearly don't know what you're talking about. I don't enjoy being the bearer of bad news, but it doesn't look good Maybe this would visually explain to you what's happening: It looks like all of the left half (for pretty much the entirety of both files) has been wiped clean. (Note: in case you don't understand what you're looking at, first, draw a line right down the middle. Then, compare both halves. It's as though the right side persistently have varying values for multiple rows, and the left side has nothing but zeros. This is the abnormal part, for this section of the save) Each Pokemon takes up about 4 complete rows, from left to right. With half of it literally missing, no Pokemon can be reconstructed. (Do remember the entire data for Pokemon itself is encrypted, so we cannot decrypt the data if it's not fully there) I cannot conceive of how the data is written like this. Maybe the data is cleared column wise before it is copied from the RAM, hence losing power caused the clearing to only work halfway through? In any case, while some remnants of data remains, there is no realistic way to use them. I hope this is enough of an explanation, and provides some closure to why no Pokemon can be extracted from the save.

As I've said before, this guide only works with 100%, and can't help with any other percentage. Is there any other problem you're having with the guide?

I hope you're not asking about which ROM to download, cause that is against our rules. Which part of the tutorial are you having trouble with?

@PKHex_User please read our rules and not upload a ROM again. Also, even if a save could be restored (from supposed corruption) in any way, there is no easy way to inject back into your fake game, so there isn't much of a point really. edit: For curiosity sake, I looked at the saves, and there's no usable data in them anyway..