theSLAYER

Our forum is against using significantly hacked Pokémon against unsuspecting people. The act of changing the PID makes it significantly hacked. (A.k.a doing something that you can't do in-game; you can't make a mon go from non-shiny to shiny in-game)

can you upload the pk2 file?

Well, as long as you followed the guide to the letter, there should be little brick risk. After all, until certain steps that is later in the guide, you aren't actually writing anything into the memory of the Switch. To be fair, I didn't really comprehend all that until multiple CFW attempts. Frankly there is probably a higher risk of the Switch being banned than it being bricked. Tho the bans on the Switch, appears to be related to installing pirated games/apps and custom themes. Also, keep in mind that our site doesn't condone hacking in competitive mons to be used against unsuspecting opponents.

Being honest, I have no clue. I'm not you, not someone around you, so I would have no honest idea. Assuming you followed the guide to the letter, and used the appropriate jig (rather then trying to bend pins, use paper clips etc), the chances of messing up is pretty darn low. Let's assume it's a mess up on your part, and not system failure or code corruption or anything of that sort. It depends on which step you mess up, and how bad the mess up is. For example, if you pressed the wrong buttons to enter RCM, that's technically a mess up. But that "mess up" does nothing. Without the correct button combination + jig, your Switch would boot into OFW, cause you did nothing. (You gotta enter RCM to try to run the payload). Another example, you got into RCM but used the wrong payload. Thus your Switch didn't boot into CFW. As long as the "wrong payload" isn't a virus that wipes your system memory (Nand) clean, just hard power off your Switch, and on the next power on it'll boot normally into OFW. As it stands, CFW installation isn't permanent. Think of it as a tethered boot or cold boot. Every system reboot (if you don't use the reboot to payload homebrew) will require the payload to be sent into the Switch. (So another RCM -> connect USB C -> Send payload) I have Auto RCM, which is effectively a functionality to boot my Switch into RCM if I were to hard reboot, this way I don't have to keep using the Jig to enter RCM. And even that isn't fully permament; Auto RCM can be turned off with another payload. So as long as you managed to obtain a NAND dump (so that you can restore it in the event the NAND gets corrupted), and don't mess up the entering RCM portion (I don't know, crossing pins, shorting a fuse etc), you should be fine. All at your own risk, of course. Side-bar: it seems like you are sitting on doing the hack, and have been asking for assurance, and using that to stall the installation. I cannot give you the assurance you need. Either do it or not do it, your choice. Don't let someone else talk you into doing something you would regret. Ultimately you're the one that has to live with the regret. So my take is that you should just pick the choice you're less likely to regret, and go with it. Also, the thing about Recovery Mode (RCM), is that it is.. a Recovery Mode. It's something the manufacturers use to Recover the Switch. While we don't have software to recover a Switch that does not have a Nand Backup (manufacturers probably have that), as long as you have a Nand backup, just enter RCM and restore your Nand. So, when the guide tells you to do a Nand dump, do it. Anyhow, reread the guide multiple times. Understand that you aren't really overwriting the content of your Switch until later on (if you install Auto RCM). Learn how you're not really installing anything into your system permanently (unless Auto RCM. or not using Emunand/EmuMMC). [Running the Hekate payload just redirects the Switch in RCM to run the code on your SD card, your MMC should be fine unless you randomly overwrite it without reading the steps]

nice, thanks for the great work @Kev-randarso you can verify the legality of your copy by using the Developmental build of PKHeX

@Kaphotics I wanna confirm with you what's the state of this issue. Also this ain't the first post we've gotten. https://projectpokemon.org/home/forums/topic/58983-dragonite-pokémon-yellow-error/?tab=comments#comment-266972

There's a button for it. If you load LGPE into the latest pkNX, just click on it and play with the options. It's pretty intuitive. As far as I can tell, there is no such option for SWSH. So while the code may exist, it is pretty pointless if there's no option for it. There's probably a reason why the option isn't enabled..

oh you're right! I read it as NDS lite for some stupid reason. I should add that to the tutorial (or at least write up a basic page that links to it) And to add on to my previous reply, using a NDS flash cart to dump saves will not work for NDSi. (to dump a save using NDS flash cart, you'll need to eject the flash cart and insert your target NDS cart. However NDSi and 3DS both close the game [which in this case, the NDS save dumping homebrew] when you eject the cart.) Hence DSi CFW is the way to go.

Since you specified NDSi, I'm gonna assume you don't happen to have a 3DS. [it is a lot easier to just get CFW on your 3DS, then use the 3DS to natively dump the NDS save.] The next best option is probably to get a some kind of NDS flash cart, that you can use to dump the save of your NDS carts. However, given the tools used are so old, there isn't support (not really) if it the FTP or what not were to not work. An alternatively would be to get a dongle that connects to your PC's USB and dumps the save. Once again, old tool and lack of support issue exists. Anyhow, read this: https://projectpokemon.org/home/tutorials/save-editing/managing-nds-saves/

Probably. At least it sounds that way from your description. Now you can patch your Switch on your own prerogative.

I'm under the impression this requires ROM editing, not SAV editing. Sadly I don't have any real specifics on how to get this done Anyhow, I moved your post, as you posted this in the PKHeX subsection (sav editing).

As far as I can tell, pkNX only has shiny rate editing for LGPE, not SWSH.

You could also just inject one into your existing save.

I'm unsure if that's a PKHeX issue or user issue.

message has been split out of old post.

Just drag them into those saves with PKHeX. Just a minor thing that PKHeX fixes. Just set on that mon and move on.

yes.

No, follow the tutorial. edit: And no, older version of PKHeX won't help you mon become "legal". It's just that older versions don't check for the correlation that was recently discovered. Even if a mon was legal on an older version of PKHeX, it could still be illegal on a recent version of PKHeX. It just means the mon was always illegal to begin with, but the older version didn't detect it.

The common public method of getting CFW on a "unpatched" Switch is using a hardware vulnerability to access the Recovery Mode (RCM), then sending a payload into the device via the USB-C port. That hardware vulnerability has been patched for newer models, thus "patched" models. It is important to note that a hardware mod (soldering on a chip basically) allows for the Switch Lite to obtain CFW, however the producers are now all behind bars or missing. Hope this answers your question.

If my assumption is correct, you made an illegal edit, which you failed to mention. (I'm assuming you changed it's PID to make it shiny) Read: edit: You modified the IVs illegally (your IV edit broke overworld8). PKHeX is working as intended. It appears you may have followed my template for changes without realizing it has etc in that section. I changed up that line to hopefully make it more obvious :3

Yes.

Give this a try (and rename the file correctly before importing it) sav(2).dat

It's like that your Pikachu's OT isn't the same as your OT. Not just the visible OT, even the trash bytes.

If you already have a save, consider using this: If you don't have a save, download one of the many saves uploaded to our site, then use the Flag importer.