Ah, I was basing that off of the file dates -- looks like the dump utility wasn't privy to the actual time set on the switch when it created the files. I found shchmue's Firmware Version Inspector python script and after scanning the dump verified that my dump is as you said:
Firmware version found: 5.1.0 (no exFAT)
Most recent boot: 2018-12-02 00:45:19
Different question -- with the EmuMMC partition setup, it looks like people are still booting into RCM+payload and then choosing to boot OFW or CFW. Isn't the point of having OFW so that you don't need to RCM+payload? One would just power off the switch and power it back on again to play "stock"? Or is the payload still necessary so that a future OFW can't detect things like the EmuMMC partition on the Micro SD card? Or is the payload still necessary to upgrade to newer firmwares without burning the fuses? I assume the payload would then be necessary to lie to OFW about the number of burnt fuses?
Assuming they are booting "Stock" mode, then they are trying to avoid burning fuses but want to boot into a mode without CFW. Stock is not truly OFW as Stock mode through a custom bootloader bypasses the fuse check thereby potentially telling Nintendo you have a mismatched fuse count. However there is no evidence Nintendo currently checks for this.
I have 2 questions, since I've been back and I'veseen a few things I'm interested in:.
1. What is warmboot? Benefits? Required firmware.
2. Is USB loading via the Dock a thing yet? I always imagined that XCI files would eventually be loadable through a USB.
- Warmboot is an exploit that is launched while the console is already on. An example is Deja Vu which is launched through the browser and you cannot launch the browser without turning the console on
- Currently, the only CFW that can manage this is SX OS and that is only with .XCI files. They offer support for installing .NSP files from an HDD but they do not allow for installation to HDD
Is there a way to get my switch to reboot to Hekate or emunand after restarting my sysnand instead of having it reboot sysnand again? I think i remember my switch rebooting directly to hekate from sysnand before i updated to 9.0.0.
When you are running CFW, the console's Reboot option is replaced with reboot_to_payload and reboots to the payload named "reboot_to_payload.bin" in your CFW folder.
So uhm, small problem here. Updated to 8.0.1 and no payload is booting up the system. ReinX flashes the splash screen, then the sept logo and then the switch turns off.
Anybody got any suggestions? Already restored the switch from a backup and it's still working fine, so no bricky here.
Any help is greatly appreciated.
Make sure you are running the latest version of ReiNX with ReiNX.bin on the root of your SD card.
Hello there. A question regarding updating: Should I update to a higher firmware?
My Switch is running firmware 3.0.1 and is not patched (vulnerable to fusee-gelee).
As far as I understand, the Switch being not patched means I can run CFW on any firmware.
But is there anything special I can do with a lower firmware? Or what are some arguments against updating (from 3.0.1 specifically)?
Lower firmware versions have access to potentially better exploits such as untethered coldboot. However since we can update without burning fuses, thereby allowing us to downgrade back to the firmware before the update, there is not much need to stay on lower firmware versions. emuMMC can accomplish the same thing by duplicating your eMMC onto your SD card which you can update freely without burning fuses or AutoRCM.
Looking for suggestions. I want to go online and have a clean nand backup on 6. Is there a way to upgrade my clean nand to 8.1.0 instead of being forced to jump to 9.0 after i restore the clean nand? Specifically looking for a clean way of doing this to prevent a ban or someone to let me know if 9.0 is ok to stay on (non patched switch, dont care about fuses). I could potentially downgrade my emummc once setup to 8.1.0 or stick with 9.0 if its fully supported now. Just worried about support for 9.0. Any ideas?
The only other clean way to update to firmware 8.1 is by performing a local game update with another console that has a game on a higher version as well as running firmware 8.1
Sorry if covered but I couldn’t find it anywhere else.
I have a Switch with SX OS and would like to transfer two saves over to a new Switch Lite, is it possible without updating OFW? (I use emunand if it helps) I don’t care if Sx unit gets banned (but it hasn’t been yet) but unsure if to create a Nintendo account and use it on the old Switch or the new one, or both?
As long as you are not transferring any hacked/edited save files, there is no risk. After all, majority of bans are console-based not account-based.
I just picked up a unpatched switch running 4.1.
I have a RCM jig and 128GB MicroSD on the way coming tomorrow.
I have a Mac and an Android phone.
Could someone point me in the direction for a good tutorial to follow if I'm not missing anything?
Also I know in the FAQ it says that all firmwares are fine but the switch is asking me to do a system upgrade to 9.0 which it seems like there isn't CFW running properlly for it yet. Should I avoid going online/updating for awhile? Will I need to update either way to mod it?
System updates are only required if a game requires that firmware version or if you wish to play online. Firmware version plays no part in accessing the exploit as it is a hardware-based one meaning the software does not affect how the exploit works. I do recommend not updating to firmware 9.0 until CFW & homebrew offer better support for it. If you need a good tutorial, I can recommend you
this
Hi guys, I'm trying to restore backup, I'm having 6.2 atmosphere but the backup is on 4.1 I think, do I need to match this software, downgrade with ChoiDujourNX to 4.1 and after that restore and backup with stock firmware?
No, simply restore your backup then if your fuse count exceeds the expected count of 4.1, then you will need to enable AutoRCM. If the fuse count matches, then you do not need AutoRCM. You can check the list of firmware versions and their expected fuse counts
here and you can check your fuse count with Hekate.
Can I do a system transfer all my games save data from my old switch to the new switch lite with out messing with the CFW on the old switch? Don't want to have the switch lite hacked, but I want my NNID and saves to transfer to the new system with out any problems.
As long as you are not transferring any hacked/edited save files, there is no risk. After all, majority of bans are console-based not account-based.