Hey everyone
I recently restored my 5.1 hacked Nand and because I currently have 8 burned fuses (FW 6.2), Sleep mode isn't working properly and I cannot wake it up again after I enter sleep mode. I thought Hekate 4.6 was supposed to fix this issue, but it isn't working for me. Any idea about what's going on would be greatly appreciated cuz frankly I am lost. It's been months since I last used my hacked Nand, but I am sure sleep mode worked just fine up until the point I accidently blew the fuses...
Maybe try another CFW like Atmosphere using Fusee or ReiNX?
Heya'll I've recently started to play some newer games and ran into some firmware related issues. (Deadcells V1.1). Would updating the switch to v6.2 from 5.1 allow the game to run without erroring out?
If i do update from 5.1 to 6.2 with Choidujour, would i have to do anything with the CFW?
If you update your firmware, make sure your CFW is updated to support the firmware you are updating to. The latest versions of all CFW support 6.2 so just replace the CFW files/folders then update your firmware with ChoiDujour
NX (ChoiDujour is a Windows exe program).
I am a little confused, i am on sysnand 6.1.0, can i setup an emunand to keep it on 6.2. and the sysnand as low as possible?
( could you please hint me a tutorial , i'm kinda lost)
Yes that is the original purpose of EmuNAND; to allow you to update your firmware without updating the firmware of the console. This also allows you to not have to rely on AutoRCM as it is impossible to burn fuses with EmuNAND but you can use AutoRCM in conjunction with EmuNAND if you so wish.
I am using xs os 2.53 and 5.1
My question is: is it safe to use retroarch emulator on switch with sd card, using exfat? There are some users expereinced corruption of data on sd card with exfat.
It is not safe to use exFAT in general, especially with homebrew such as Retroarch.
Just finished backing up everything via Hekate and about to install SXOS and emuNand.
However the guide I've read (can't post links yet but it's the "how to setup emunand" guide on this site) is saying to update SysNand to latest before setting up emuNand, but everywhere else I'm reading warnings to NOT update the SysNand to the latest 7.0 OFW.
Any advice on what the best option is and why?
I'm currently on 6.0.1 but it seems 6.2 is the most popular to be on - was something added in 6.2 that makes it the goto OFW?
Is the purpose of preventing the fuses being burnt just for a potential cold boot hack in future or are there other reasons I am unaware of?
I'm thinking of making an emuNand on 6.0.1 (or 6.2 if it's better?) and just updating the SysNand to 7.0 if the only reason to save fuses is for a possible future coldboot hack.
Any advice appreciated!
That guide sounds like its not updated, which is a bad sign, because likely the latest firmware at the time it was written did support CFW but currently the latest firmware does not support CFW yet. For now, you can just skip that step and update your SysNAND later such as when CFW does support the latest firmware. The only reason to have SysNAND on the latest firmware is to play the Switch online.
Should I install the Homebrew Menu .nsp or use the title override function of Atmosphere?
If it comes down to personal preference (or if the latter is better), what "dummy" title is recommended to use?
The developers behind Atmosphere are against any .NSP files you install because of multiple reasons (e.g. piracy, ban risk, etc.) so they created an override function to not only allow a safer way to use homebrew, but to also confuse pirates by creating another type of .NSP file. While this doesn't answer your question, just know that it is down to personal preference. The only noteworthy difference is that the override function has a lower ban risk but for people who don't care about being banned, that difference becomes negligible. Not sure which dummy title is preferred but any free game on the eShop should do like Pokemon Quest, Hulu, Fortnite, etc.
I just grabbed a serial that says should be good,xaw1, 0063...
I'll grab a 64gb sdcard in meantime to do a nand dump. My question is what's my fear in regards to upgrading the firmware after the dump? I'm under the impression without this being a patched model I can restore my dump any time and guess I can run cfw whenever.
Brief background is I've done x360 DVD firmware flashes, cool runner chip and a dual nand demon. Also some new 3dsxls.
The sole purpose of a NAND dump is to recover from a brick. In regards to your actual question, the Switch has fuses like the Xbox 360 that prevents downgrading. When you update the console's firmware, you will burn fuses when it reboots. And just like in the 360, these fuses are designed to prevent downgrades. This is important as there may be better or more convenient exploits on lower firmwares that may be released in the future. Now there is a way to update the firmware without burning fuses but this requires the usage of homebrew which may not appeal to people who want to play the console online.
so I dumped the NAND on 6.2 after I had upgraded to 7.0 OFW with nintendo and i restored my 6.1 nand and then updated to 6.2 with choi thing .
is it safe to save this NAND since the system was on 7.0 ofw? or should I just use the 6.1 nand instead to avoid any issues when backing up in the future since that was done PRIOR to any updates and or crazy issues past 6.1/6.2 I just am not sure if it even matters at all and someone who knows could answer this very easily to help save me some time and also create some peace of mind
There is not much difference in saving a 6.1 NAND versus a 6.2 NAND especially since your console has a fuse count of 9 on account of updating to 7.0. You can go ahead and make a copy of your 6.2 NAND but its about as useful as your 6.2 NAND. And by useful, I mean you can still use either one of those NAND backups to recover from a brick as long as you remember that the firmware of those NAND backups are lower than your fuse count meaning after you restore one of the NAND backups, you can only boot the console through RCM.
