**Issue:** Switch (unpatched, Hekate 6.5.3 / Atmosphere 1.11.2-master-5388824be / HOS 22.5.0) fails to boot on every path.
**Crash:**
- Error 2002-3539 (0x1BA602)
- Program ID: 0100000000000024 (ssl)
- Type: User Break
- Identical on SysNAND Atmosphere AND emuNAND Atmosphere (100% reproducible now)
- Stock/OFW and Maintenance Mode all hang indefinitely on the Nintendo logo (no crash screen)
**Ruled out already (all retested, no change):**
- Fresh official Atmosphere 1.11.2 reinstall (package3 SHA256 identical to previous install)
- atmosphere/contents temporarily disabled
- kip1=atmosphere/kips/* removed
- cal0blank removed
- Hekate reports 0 SDMMC errors on the SD, eMMC "Maintenance: OK", reserved blocks normal
**Full rawnand.bin backup:** taken via Hekate (BOOT0/BOOT1/GPP), 100% success, "Finished and verified", no read errors during the ~83min dump (strong argument against a physical eMMC/connector issue).
**Analysis done on the rawnand.bin with NxNandManager v5.2 (keys imported, Explorer feature):**
- /Contents/registered on SYSTEM: ssl (0100000000000024) present with normal-looking Meta+Program NCA sizes, not corrupted.
- /save on SYSTEM: sorted the full list of SystemSaveData IDs present. Per SwitchBrew's SystemSaveData table, ssl's savedata should be **0x8000000000000060** (SslSave:/). This ID is **absent** from the list — confirmed by sorting alphabetically, list jumps directly from ...0053 to ...0061, no ...0060 entry anywhere.
**Hypothesis:** ssl fails to mount/create SslSave:/ at boot (missing SystemSaveData), triggering the User Break -> 2002-3539. Would also be consistent with Stock/OFW hanging at a similar stage without a crash screen.
**Constraint:** Can no longer reach the Homebrew Menu (was reachable once, briefly, but now the ssl crash is 100% systematic on both SysNAND and emuNAND before reaching Home), so Daybreak (reinstalling the exact same 22.5.0 firmware, which was the planned next step) is currently unreachable.
**Question:** Is there a known-safe way to recreate SystemSaveData 0x8000000000000060 for ssl from a pre-OS payload (e.g. TegraExplorer), that properly registers it in the save indexer rather than just creating a raw folder? Or is there another documented fix for this specific scenario (missing ssl SystemSaveData) that doesn't require booting into HOS?
I have a full verified rawnand.bin backup, so recovery from a failed attempt is possible. Happy to share NAND partition list / save list screenshots if useful. img
**Crash:**
- Error 2002-3539 (0x1BA602)
- Program ID: 0100000000000024 (ssl)
- Type: User Break
- Identical on SysNAND Atmosphere AND emuNAND Atmosphere (100% reproducible now)
- Stock/OFW and Maintenance Mode all hang indefinitely on the Nintendo logo (no crash screen)
**Ruled out already (all retested, no change):**
- Fresh official Atmosphere 1.11.2 reinstall (package3 SHA256 identical to previous install)
- atmosphere/contents temporarily disabled
- kip1=atmosphere/kips/* removed
- cal0blank removed
- Hekate reports 0 SDMMC errors on the SD, eMMC "Maintenance: OK", reserved blocks normal
**Full rawnand.bin backup:** taken via Hekate (BOOT0/BOOT1/GPP), 100% success, "Finished and verified", no read errors during the ~83min dump (strong argument against a physical eMMC/connector issue).
**Analysis done on the rawnand.bin with NxNandManager v5.2 (keys imported, Explorer feature):**
- /Contents/registered on SYSTEM: ssl (0100000000000024) present with normal-looking Meta+Program NCA sizes, not corrupted.
- /save on SYSTEM: sorted the full list of SystemSaveData IDs present. Per SwitchBrew's SystemSaveData table, ssl's savedata should be **0x8000000000000060** (SslSave:/). This ID is **absent** from the list — confirmed by sorting alphabetically, list jumps directly from ...0053 to ...0061, no ...0060 entry anywhere.
**Hypothesis:** ssl fails to mount/create SslSave:/ at boot (missing SystemSaveData), triggering the User Break -> 2002-3539. Would also be consistent with Stock/OFW hanging at a similar stage without a crash screen.
**Constraint:** Can no longer reach the Homebrew Menu (was reachable once, briefly, but now the ssl crash is 100% systematic on both SysNAND and emuNAND before reaching Home), so Daybreak (reinstalling the exact same 22.5.0 firmware, which was the planned next step) is currently unreachable.
**Question:** Is there a known-safe way to recreate SystemSaveData 0x8000000000000060 for ssl from a pre-OS payload (e.g. TegraExplorer), that properly registers it in the save indexer rather than just creating a raw folder? Or is there another documented fix for this specific scenario (missing ssl SystemSaveData) that doesn't require booting into HOS?
I have a full verified rawnand.bin backup, so recovery from a failed attempt is possible. Happy to share NAND partition list / save list screenshots if useful. img
