So I'm transitioning to a clean SysNAND OFW from a stock backup I made on 4.1 and a incognito emuMMC 9.2 CFW (running Atmosphere). I want to be safe and not burn fuses when I update my OFW from 4.1 to 9.2 but also don't want to be banned by using ChoiDujourNX to update it (this has been known to happen right?). Question is: can I enter RCM right after the restart from updating the OFW online through Nintendo to keep fuses from burning? Or is there some way of keeping AutoRCM enabled through that process on OFW?
One way I could think of it working is launching ChoiDujourNX from RCM as a .bin and updating the OFW that way but idk if anyone has made that yet, or if it's even possible?
Or do I need to make an sysMMC too in order to play online to avoid burnt fuses (like ksanislo says in this thread)
Just for reference I have an old non-patched switch with 5 fuses burnt, so I could run Caffeine but I don't want to since I have a dongle.
One way I could think of it working is launching ChoiDujourNX from RCM as a .bin and updating the OFW that way but idk if anyone has made that yet, or if it's even possible?
Or do I need to make an sysMMC too in order to play online to avoid burnt fuses (like ksanislo says in this thread)
Just for reference I have an old non-patched switch with 5 fuses burnt, so I could run Caffeine but I don't want to since I have a dongle.
Last edited by fusobotic,