Hi, I'm new to switch modding but not to console modding, the switch is an entirely different beast altogether. Still, I'm making headway. Now, onto my questions:
I recently bought an old, unpatched switch under 5.x FW. I followed the guide found
here and successfully booted from emuNAND into the most recent version of atmosphere and 5.x firmware. I have never taken my switch online since buying it and want to update my switches firmware to 13.2.0 then create a new emuNAND altogether.. I've already wiped my SD card and repartitioned it,I just need to create the new emuNAND. I am confused though, what is the e-fuse risk? Is it from taking my CFW switch online then updating in the system? I know that I need to use daybreak to update CFW but want to know what the process is that pops the fuse so I don't make that mistake. I just want to get my stock switch up to 13.2 and create my emuNAND.
Lastly, in my mind the process to do what I'm trying to achieve is:
•boot stock switch without my SD card inserted and take it online to allow it to update OFW/sysNAND
•after update is complete, system restore then power down
•go through the process of creating emuNAND as well as using lockpick to get prod.keys(I've already done this but is it different after a system restore)
•boot into cfw
•check settings to see that I've actually successfully updated to 13.2 with the most recent version of atmosphere
Am I wrong or missing anything? Is the system restore step just unnecessary steps?
Will my SD card still work with my switch's CFW since factory resetting it makes them not work together?
Why do you think the original owner remained on such a low firmware? I know things are patched out but those are reimplemented with CFW. What other benefits do I have being on such a low FW though?
Can I run 13.2 fw on emuNAND(by creating at.x emuNAND then updating emuNAND with daybreak) but remain on 5.x on sysNAND?
Sorry for so many questions, I just can't seem to find a straight answer to my questions.