Is there a tool i can use to scan/check if a xci/nsp is legit and not have a brick code?
If you don't really care about getting banned, then it shouldn't matter too much. But you could get superbanned if you pirate games through NSPs and you won't be able to access any online features including the eshop, perform system update and software update on the switch anymore through normal means. You can still do these with other methods but it's clearly a lot less convenient, but that's about all the drawback I can think of if you really never ever plan to touch any online features.I only want to play single player games, does it even matter if I get banned for using cfw? Are there any negative effects from getting banned that I should worry about? Is see a lot of people worried about being banned but I can't really understand why.
If its linked, the Nintendo folder will be linked to the SysNAND. Thus when you boot into EmuNAND, it will flag you to delete the folder (the actual message reads that the SD card does not match the system). If you have any games and/or content installed to the SD card that is used by SysNAND, do not let EmuNAND delete the folder.What is the difference between linked and unlinked EmuNAND in SX OS?
The primary purpose of backing up the NAND is to recover from a brick. Just because you didn't make one before you hacked the console does not mean you can't still make one.Hi guys! I have never made a NAND backup before hacking my switch. Is it still an advisable thing to do now that I'm already using SX OS? If so, which one of the option should I choose, Nand or EmuNAND? Which one is it to back up the system file so I can restore in case of soft brick (how do soft brick happen anyway?)
Thanks a lot!
As a precautionary message, delete any ReiNX.bin files on your SD card. First, did you use ChoiDujour or ChoiDujourNX? If you used ChoiDujourNX, did you select with or without exFAT? Lastly, what version of ReiNX are you using?Ok i have a problem here. I tried to update to 6.1.0 with choidujnor. It seemed to work fine. I get to the reboot step so i then inject the renix payload and i keep getting a error saying i have to reboot. Any help??
I do have a NAND backup so im not completely screwed but still seems weird this would happen as i sure i followed all the steps correctly.
As a precautionary message, delete any ReiNX.bin files on your SD card. First, did you use ChoiDujour or ChoiDujourNX? If you used ChoiDujourNX, did you select with or without exFAT? Lastly, what version of ReiNX are you using?
All I have left to recommend is try using another CFW like Atmosphere which you can find here. If that still doesn't work, you may need to restore your NAND as well as boot0/boot1.I used NX. I did it with exfat even though i do have a fat32 card. The instructions didn't really say anything about that.
Im not sure what version i was using before but i did swap it out for the latest (halloween) edition. When i did that it just got stuck on the "nintendo switch" loading screen.
All I have left to recommend is try using another CFW like Atmosphere which you can find here. If that still doesn't work, you may need to restore your NAND as well as boot0/boot1.
Since you're going to be restoring boot0/boot1, which is where AutoRCM is stored, it doesn't matter if you disable it prior to restoring or not. What does matter is if you backed up boot0/boot1 before or after you enabled AutoRCM because that will determine if AutoRCM will persist after the restore.Yea the other cfw not working either. Im gonna just restore my nand.
Should i remove auto rcm before doing this? And if so how do i do that?
Since you're going to be restoring boot0/boot1, which is where AutoRCM is stored, it doesn't matter if you disable it prior to restoring or not. What does matter is if you backed up boot0/boot1 before or after you enabled AutoRCM because that will determine if AutoRCM will persist after the restore.
Just try restoring the NAND with Hekate and it'll automatically create the folder structure for you. And since the SD card has to be in exFAT (no, you cannot restore the NAND in parts), you should format the SD card before running Hekate to create the folder structure.Edit so now im confused again lol. So im reading on how to backup my nand and it seems i dont have a folder it's saying i should have,
I do have all 3 files and a "Restore" Folder. BOOT0,BOOT1 and rawnand.bin
But the tutorial is saying i need to have some "numbersletters" folder. Which i dont have
Also it says my card should be exformat. So should i reformat my fat32 card to exformat before restoring? And once i do reformat and have a blank card where do i put the files? I thought on the root of the card there should be a folder called "Restore" and then i put the 3 nand files in that folder and that should be it. Is that not the case?
For USB installation, you don't have to split the .NSP file because USB installation breaks up the .NSP into files smaller than 4 GB while its working. Also, the files inside the folder aren't supposed to have an extension since the Switch will be reading the folder name, not the files inside. When it is installing, it will install the files inside.Ok I'm using SplitNSP I get a folder with the split parts inside. Can I just install the folder through usb using tinfoil? Also, the parts inside have no file extension do I need to rename them to .nsp or just leave them alone?
For USB installation, you don't have to split the .NSP file because USB installation breaks up the .NSP into files smaller than 4 GB while its working. Also, the files inside the folder aren't supposed to have an extension since the Switch will be reading the folder name, not the files inside. When it is installing, it will install the files inside.
I have a patched switch (XAW100899), it was running 4.1.0. I haven't set it up online at all, but when I went to play Diablo 3 on it, it wouldn't let me play until I upgraded the system. I hit ok and it updated the system (offline) to 5.1.0.
So I've got two questions:
- The system version, just to make sure I'm looking at the right thing, is under system settings -> system -> Current Version.
- I know Deja Vu is unreleased, but I keep reading some people saying Deja Vu only works on 4.1 and in later versions that was patched. But I also keep reading that one of the reasons it's not released is because it still works on later firmwares, so they want to wait to get maximum effect. Is that confirmed, do we know if it will eventually work on 5.1 when it is released?
I'm hoping I haven't screwed the chance of me eventually being able to install CFW in order to modify saves on this :/
- Yes. If there is a pending system update, it will block this and has to be removed by booting into maintenance mode which you do by holding volume + and - when turning the console on
Initially, Deja Vu was confirmed to work as far as firmware 4.1 but when firmware 5.0 came out, it still wasn't released. This is because parts of the exploit weren't fully patched out and with a few tweaks to Deja Vu, the exploit could be made to work on firmwares higher than 4.1. However, firmware 6.1 eventually came around right after someone disclosed part of a bug used to load Deja Vu which may have possibly fully patched it out on that firmware.
So technically, Deja Vu can be made to work on firmware 6.0.1 but that still doesn't mean its going to be released anytime soon as the main reason it is still being held back is because it may be the only exploit for the new Mariko units that may pop up on the market sometime next year.