Team-Xecuter Community
Hi, I'm getting a second switch and plan to keep that one official (for a while at least) to download updates officially. From there I would like to transfer the updates to the Switch using SX Pro. However, this officially requires that both switches have the same firmware and, for obvious reasons, I would rather not update to 6.2 just yet.
Since updates are downloaded to the microSD card I was wondering if there was some way to use that in SX Pro to install the updates manually, without having to download them from a 3rd party.
Alternatively, might there be some way of spoofing the custom firmware version in emuNAND? or will there be? If I could just present a 6.1 Switch as 6.2 it would allow the official transfer of game updates easily.
If this is not possible, than my alternative question is about how to update the emuNAND without using auto RCM and without screwing up the sysNAND. I mean, if I update the emuNAND to 6.2 (after it's officially supported by SX OS, of course) without Auto RCM that would mean that whenever I boot into sysNAND next the eFuses would burn, right? But if sysNAND is on 6.1 and emuNAND is on 6.2 and then it boots to 6.1 and burns the eFuses, wouldn't that mean that the eFuses don't match and thus cause the system to panic? Basically, treating the official firmware as if I downgraded it? If that is the case, couldn't I update both the sysNAND and emuNAND to the same version, and not worry about the eFuses? Granted, this means I won't be able to downgrade, but I am more worried about the battery drain issues from auto RCM anyway, or have those been fixed? and it's not like I can just choose not to boot into sysNAND - I get an error every other day on SX Pro that forces it to reboot into sysNAND.
If I was to update both sysNAND and emuNAND together, without worrying about eFuses - but wanting to be able to restore to a virgin state in case I want to take that Switch official in the future, would there be a simple way of removing the old emuNAND and creating a new emuNAND and then restoring all the installed content from the old emuNAND?
Obviously, the best solution (for me) would be to stay on 6.1 and find some unofficial way of transferring update files from an unmodified Switch on the latest firmware to a modified Switch on 6.1 FW.
Since updates are downloaded to the microSD card I was wondering if there was some way to use that in SX Pro to install the updates manually, without having to download them from a 3rd party.
Alternatively, might there be some way of spoofing the custom firmware version in emuNAND? or will there be? If I could just present a 6.1 Switch as 6.2 it would allow the official transfer of game updates easily.
If this is not possible, than my alternative question is about how to update the emuNAND without using auto RCM and without screwing up the sysNAND. I mean, if I update the emuNAND to 6.2 (after it's officially supported by SX OS, of course) without Auto RCM that would mean that whenever I boot into sysNAND next the eFuses would burn, right? But if sysNAND is on 6.1 and emuNAND is on 6.2 and then it boots to 6.1 and burns the eFuses, wouldn't that mean that the eFuses don't match and thus cause the system to panic? Basically, treating the official firmware as if I downgraded it? If that is the case, couldn't I update both the sysNAND and emuNAND to the same version, and not worry about the eFuses? Granted, this means I won't be able to downgrade, but I am more worried about the battery drain issues from auto RCM anyway, or have those been fixed? and it's not like I can just choose not to boot into sysNAND - I get an error every other day on SX Pro that forces it to reboot into sysNAND.
If I was to update both sysNAND and emuNAND together, without worrying about eFuses - but wanting to be able to restore to a virgin state in case I want to take that Switch official in the future, would there be a simple way of removing the old emuNAND and creating a new emuNAND and then restoring all the installed content from the old emuNAND?
Obviously, the best solution (for me) would be to stay on 6.1 and find some unofficial way of transferring update files from an unmodified Switch on the latest firmware to a modified Switch on 6.1 FW.