Hopefully this isn't too much. So a few weeks back I made a post on reddit about accidentally updating my switch, at which point I learned I would need to wait for the now released Atmosphere 1.11 to support 22.0. Well it turns out that the update was to 21.2 and I didn't realize it until I installed 1.11 today and booted.
After some reading about a lot of the homebrew apps needing to be recompiled, I found a post talking about downgrading to 20.5.0 for greater compatibility (let's say in the event a homebrew app isn't recompiled or updated often).
https://www.reddit.com/r/SwitchPira...to_downgrade_emummc_from_2100_to_2050_to_use/
I followed the guide successfully except I get a yellow screen of death when trying to boot using the fusee.bin payload and sort of where my initial confusion lies and what I think I could use some help cleaning. When I set this up many years ago, I believe I used the switch.hacks.guide site? I still don't quite understand how this is all partitioned, with there being a triple partitioned (???) setup involving CFW on sysMMC, CFW on emuMMC, and something called "Stock" that still seems different from either? Is that the ACTUAL stock, official Nintendo firmware loaded on its factory partitioning? What exactly is my SD card representing when I mount it from Hekate, is firmware for the console loaded to NAND but the CFW (Atmosphere) is loaded from it across the sysMMC and emuMMC payloads?
In Hekate v6.5.2, and even way back before in versions 5.x.x I have always had 4 payloads to choose from, CFW (sysMMC), CFW (emuMMC), Stock, and Fusee.
Only the first 3 work currently, and trying to load Fusee or Fusee.bin directly as a payload results in the hard stuck yellow screen. The fusee.bin file that is in the payload folder is one I grabbed from the Atmosphere 1.9.5 release.
Currently, my hekate_ipl.ini looks like this:
For the first 3 working payloads, the versioning is as such:
And what could I do to resolve the Fusee payload not working? Please correct me if I'm wrong, but my very high level ELI5 understanding was that booting with Fusee.bin was sort of just a "wrapper payload" for booting emuMMC, and that launching emuMMC from this list of payloads accomplishes effectively the same thing. Should I just get rid of it? I think I'd be more interested in learning why Fusee.bin is producing a yellow screen of death.
At this point I'd been almost playing exclusively out of the emuMMC (or Fusee payload?) and it's where I installed all of my backed up games.
I suppose lastly, when I'm referring to "cleaning up the switch", I guess at this point I've extracted and copied over and replaced Atmosphere and all of these NRO files and various folders so many times, upgraded and downgraded, that I don't know what's old or current anymore and what's compatible and what's broken/not broken. I also clearly have two different firmware versions across the sys and emuMMC. Is there an easy way I could just wipe the emuMMC and create another one from the current sysMMC and reinstall my backed up games? If I do that, will JKSV launched in the sysMMC be able to see my saves in the emuMMC for backed up games? To be quite honest, most of the saves I care about are for games I completed when I first played them as hard copies. I probably have like less than 5 hours of play time on back ups.
Thanks and try not to be too harsh!
After some reading about a lot of the homebrew apps needing to be recompiled, I found a post talking about downgrading to 20.5.0 for greater compatibility (let's say in the event a homebrew app isn't recompiled or updated often).
https://www.reddit.com/r/SwitchPira...to_downgrade_emummc_from_2100_to_2050_to_use/
I followed the guide successfully except I get a yellow screen of death when trying to boot using the fusee.bin payload and sort of where my initial confusion lies and what I think I could use some help cleaning. When I set this up many years ago, I believe I used the switch.hacks.guide site? I still don't quite understand how this is all partitioned, with there being a triple partitioned (???) setup involving CFW on sysMMC, CFW on emuMMC, and something called "Stock" that still seems different from either? Is that the ACTUAL stock, official Nintendo firmware loaded on its factory partitioning? What exactly is my SD card representing when I mount it from Hekate, is firmware for the console loaded to NAND but the CFW (Atmosphere) is loaded from it across the sysMMC and emuMMC payloads?
In Hekate v6.5.2, and even way back before in versions 5.x.x I have always had 4 payloads to choose from, CFW (sysMMC), CFW (emuMMC), Stock, and Fusee.
Only the first 3 work currently, and trying to load Fusee or Fusee.bin directly as a payload results in the hard stuck yellow screen. The fusee.bin file that is in the payload folder is one I grabbed from the Atmosphere 1.9.5 release.
Currently, my hekate_ipl.ini looks like this:
Code:
[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp
[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp
[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1
[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.binFor the first 3 working payloads, the versioning is as such:
- CFW (sysMMC)
- Firmware 18.0.0 | Atmosphere 1.9.5|S
- CFW (emuMMC)
- Firmware 20.5.0 | Atmosphere 1.9.5|E
- Stock
- Firmware 18.0.0
And what could I do to resolve the Fusee payload not working? Please correct me if I'm wrong, but my very high level ELI5 understanding was that booting with Fusee.bin was sort of just a "wrapper payload" for booting emuMMC, and that launching emuMMC from this list of payloads accomplishes effectively the same thing. Should I just get rid of it? I think I'd be more interested in learning why Fusee.bin is producing a yellow screen of death.
At this point I'd been almost playing exclusively out of the emuMMC (or Fusee payload?) and it's where I installed all of my backed up games.
I suppose lastly, when I'm referring to "cleaning up the switch", I guess at this point I've extracted and copied over and replaced Atmosphere and all of these NRO files and various folders so many times, upgraded and downgraded, that I don't know what's old or current anymore and what's compatible and what's broken/not broken. I also clearly have two different firmware versions across the sys and emuMMC. Is there an easy way I could just wipe the emuMMC and create another one from the current sysMMC and reinstall my backed up games? If I do that, will JKSV launched in the sysMMC be able to see my saves in the emuMMC for backed up games? To be quite honest, most of the saves I care about are for games I completed when I first played them as hard copies. I probably have like less than 5 hours of play time on back ups.
Thanks and try not to be too harsh!
