Hi all,
First time hacking my 4.0.1 switch, everything seemed to work but after updating my CFW to 9.2.0 with ChoidujourNX it unexpectedly updated my stock firmware to 9.2.0 as well.
So, my question is, is my sysnand clean or should I restore to the nand backup I took? The last time I went online was probably two years ago!
These are the steps I followed:
Was on 4.0.1 (hadn’t used my switch in years).
Accessed RCM, injected TegraExplorer payload, and then on the Switch I formatted my SD card for EmuMMC setup. Then rebooted to RCM
Then copied the files I needed from my PC to the SD card, including Atmosphere 0.11.11, sig patches and hekate_ctcaer_5.1.4_J
Then, with the SD card back in the switch, got into Hekate and backed up eMMC boot0 & boot1 and also eMMC RAW GPP.
Then created an emuMMC partition (SD partition), and changed emuMMC from disabled to SD Raw 1. At this point emuMMC was showing as Enabled.
Then attempted to launch CFW EmuMMC from Hekate. I saw the Atmosphere loading screen but at some point after it stopped with a black screen and the CFW wouldn’t load. After a few attempts I managed to get back to Hekate but again the CFW wouldn’t load.
So back on the PC I decided to delete all the files on the SD card and re-transfer all my source files back on to the SD card, eg Atmosphere etc. Doing this seemed to work and was now able to load 'CFW EmuMMC' from Hekate. Looking at my system version confirmed I was on a Atmosphere CFW so then powered down and rebooted to stock. Again the system version showed I was on my original stock FW. So at this point I thought everything was fine
[EDIT: so then went through the RCM procedure again and reloaded CFW emuMMC from Hekate]
A little bit later that day I decided to upgrade my CFW from 4.0.1 to 9.2.0, which I did with ChoidujourNX (with autoRCM enabled).
[EDIT: when ChoidujourNX finished I selected Reboot which took me back into the CFW, was now on 9.2.0 and was able to see homebrew apps. So then powered off and booted stock.]
However, this updated my stock firmware to 9.2.0 as well, which I wasn’t expecting. When I had a look in Hekate, I noticed that emuMMC was showing as disabled again. Everything was working fine but I decided to recreate the EmuMMC partition. This is now showing as enabled again, both stock and CFW still appear to be working fine. The CFW system version has an E on the end, which I gather indicates that it’s using the EmuMMC partition.
First time hacking my 4.0.1 switch, everything seemed to work but after updating my CFW to 9.2.0 with ChoidujourNX it unexpectedly updated my stock firmware to 9.2.0 as well.
So, my question is, is my sysnand clean or should I restore to the nand backup I took? The last time I went online was probably two years ago!
These are the steps I followed:
Was on 4.0.1 (hadn’t used my switch in years).
Accessed RCM, injected TegraExplorer payload, and then on the Switch I formatted my SD card for EmuMMC setup. Then rebooted to RCM
Then copied the files I needed from my PC to the SD card, including Atmosphere 0.11.11, sig patches and hekate_ctcaer_5.1.4_J
Then, with the SD card back in the switch, got into Hekate and backed up eMMC boot0 & boot1 and also eMMC RAW GPP.
Then created an emuMMC partition (SD partition), and changed emuMMC from disabled to SD Raw 1. At this point emuMMC was showing as Enabled.
Then attempted to launch CFW EmuMMC from Hekate. I saw the Atmosphere loading screen but at some point after it stopped with a black screen and the CFW wouldn’t load. After a few attempts I managed to get back to Hekate but again the CFW wouldn’t load.
So back on the PC I decided to delete all the files on the SD card and re-transfer all my source files back on to the SD card, eg Atmosphere etc. Doing this seemed to work and was now able to load 'CFW EmuMMC' from Hekate. Looking at my system version confirmed I was on a Atmosphere CFW so then powered down and rebooted to stock. Again the system version showed I was on my original stock FW. So at this point I thought everything was fine
[EDIT: so then went through the RCM procedure again and reloaded CFW emuMMC from Hekate]
A little bit later that day I decided to upgrade my CFW from 4.0.1 to 9.2.0, which I did with ChoidujourNX (with autoRCM enabled).
[EDIT: when ChoidujourNX finished I selected Reboot which took me back into the CFW, was now on 9.2.0 and was able to see homebrew apps. So then powered off and booted stock.]
However, this updated my stock firmware to 9.2.0 as well, which I wasn’t expecting. When I had a look in Hekate, I noticed that emuMMC was showing as disabled again. Everything was working fine but I decided to recreate the EmuMMC partition. This is now showing as enabled again, both stock and CFW still appear to be working fine. The CFW system version has an E on the end, which I gather indicates that it’s using the EmuMMC partition.
Last edited by MesaNightDrone,