reporting:
So the end, in my case, there were probably a collection of things going wrong at the same time that made it tricky to decypher indivdual root causes:
During this whole messy process, atmosphere and hetake got hotfix updates that fixed issues with Mariko, so they probably helped restoring ability to boot on my device.
Lesson I learned: stick to my usual principle which is be not a FW update early adopter and wait for stuff to iron out.
The positive thing is that going through all this process, I learn quite a bit, set up my system manually instead of exclusively relying on a package (HATS). During this endeavour I was communicating often with Sthetix ; he was very helpful patiently explaining stuff. Also kudo to him for being so reactive at keeping his package up to date with latest versions as they unfold.
I was fortunate in the end there was no serious fuck up (appart from losing my animal well save I'd forgot to back up >.<)
So the end, in my case, there were probably a collection of things going wrong at the same time that made it tricky to decypher indivdual root causes:
- I only use CFW@EmuMMC. However, when a FW update is released, I keep both SysMMC and EmuMMC up to date through daybreak (so SysMMC is only updated through CFW, never OFW).
- Early versions of 18.1.0-supporting Atmosphere and/or Hetake had issue, making booting to both CFW@emuMMC and CFW@SysMMC impossible ( it spat all sorts of unpleasant error screens).
- That is why I tried to fall back first to OFW to update SysMMC to 18.1.0, impossible because of the "invert" fuse mismatch (fuse count was lower (matching FW 16) than required by the fw 18.0.1 installed on SysMMC)
- Without OFW, CFW@SysMMC or CFW@EmuMMC accessible, I was only left with Semi-Stock, which by chance was still accessible.
- I online-updated SysMMC from semi-stock to 18.1.0, correcting the fuse issue.
- rebooting to semi-stock worked
- In the situation, I figured my emuMMC was probably corrupted (since error screens said so), and I was going to have to recreating from scratch. Figured I should start with a clean slate, completely factory resetting the SysMMC so in turn build a really clean emuMMC.
- That is why I ran the SystemWipe on SysMMC.
- Little did I know that SystemWip can actually make OFW unbootable.
- The fix is to boot CFW@SysMMC.
- Then OFW boots OK
- Now my system is fully 18.1.0, using latest sys-patch 1.5.2, latest patches from the dedicated thread
During this whole messy process, atmosphere and hetake got hotfix updates that fixed issues with Mariko, so they probably helped restoring ability to boot on my device.
Lesson I learned: stick to my usual principle which is be not a FW update early adopter and wait for stuff to iron out.
The positive thing is that going through all this process, I learn quite a bit, set up my system manually instead of exclusively relying on a package (HATS). During this endeavour I was communicating often with Sthetix ; he was very helpful patiently explaining stuff. Also kudo to him for being so reactive at keeping his package up to date with latest versions as they unfold.
I was fortunate in the end there was no serious fuck up (appart from losing my animal well save I'd forgot to back up >.<)
Last edited by ikynx,
