@Draxzelex can you refresh my memory? (I'm about to update my emuMMC, and I can't seem to remember this, even though I ran into this issue once.,) When new switch firmware updates the cartridge slot, what does that affect again? I can't remember which one of the scenarios I am about to present is correct:
A. If I update my CFW for the emuMMC side of my switch and THEN update the Switch firmware on my emuMMC side, Does it matter if my emuMMC firmware is HIGHER than my sysMMC firmware? (Does this stop the cartridge slot from working on the sysMMC side if there is game cartridge slot firmware updates in the updated firmware? (I remember a scenario where my game slot wouldn't work, but I can't remember if that was the sysMMC side or the emuMMC side....if I update the firmware on my emuMMC side of my switch and THERE are game cartridge slot firmware updates in the firmware and the game cartridge slot gets the update, will that render the game cartridge slot on the sysMMC side un-usable until I update? As well, does this burn fuses...I just can't remember...
B. If I update my sysMMC firmware side first (which may update the game slot firmware), is this the safest bet because I can just dump the firmware from my sysMMC side and then apply it with daybreak on the emuMMC side and then all will be well because both sides will be on the same firmware and Game slot firmware correct?
As well, I believe I have my ini files set to nogc=1 which protects the firmware on the Game slot from being updated if the update is done on the emuMMC side,,,
I think the whole game cartridge slot rendered disabled ordeal I explained can occur from updating the firmware on the emuMMC side when nogc=0 is set which means the game cartridge slot gets updated on the emuMMC side, which burns fuses when you boot to the sysMMC side as it is discovered that somehow your game cartridge slot firmware is above the regular Nintendo firmware on the sysMMC side. Are my memories correct? Feel free to CORRECT me on any of this. I'm just making sure I have everything in order before I update.
(PS - Do you guys know how high my firmware has to be for TOTK?). As well I read some news about bugs in Atmosphere 1.5.3 and fixes possibly in pre-release 1.5.4 for problems with layeredfs mods. Do we know if these bugs are fixed in AMS 1.5.4? It seems from the read-me for pre-release 1.5.4 they are, but if anyone has tried it, and knows, that would be cool.
Thanks for everything in advance.
UPDATE: I solved my issues. I updated everything. Here what I did:
- Dropped new atmosphere 1.5.3 into SD Card (latest Stable) https://github.com/Atmosphere-NX/Atmosphere/releases
- Dropped newest Hekate 6.0.4
- Updated Sig Patches (Backward Compatible)
- Used TOTK cart to update Sysmmc side to 15.0.1
- Booted in RCM mode using TegraRCMGUI
- Loaded payload TegraExplorer.bin
- backed up firmware using TagraExplorer to SD Card
- Booted into emuMMC, Used Daybreak to upgrade firmware use backed up file from tagraexplorer
- Rebooted, Atmosphere puked onitseld dumping fatal error on TitleID 4200000000000010
- Pulled out SD card went to Atmosphere-->Contents-->Delete TitleID folder 4200000000000010
- Reboot to emuMMC, and emuMMC booted
- Updated any HROs that needed updating
- $Profited
- All games are Booting with the newest sig patches.
Yay.