But none of that even matters. There are no issues anymore with downgrading back to 4.1 or 3.0 if you feel like it (other than always having to use CFW, but that would be the point anyway, now wouldn't it?).
there very much is. the point of not burning fuses is to be able to have the console boot normally without needing jigs and payloads.
the potential cold boot exploit that might eventually be discovered boots normal horizon (or starts to boot it) and then escapes that environment into cfw (likely emunand), making jigs, payloads, trinkets and injectors unnecessary.
now granted, there is a chance that this exploit ends up not existing or not being found in our lifetimes.
and with autorcm and plenty methods to inject payloads, things are very much so comfortable, we might not even need that exploit anymore, compared to june and july, you can very much work with this.
what this solves is the 'i accidentally updated to a nonhackable fw, but I have a nand dump from before' situation, that till now was heavily hindered by the absence of sleep mode.
--------------------- MERGED ---------------------------
I dont understand how this works for the fuses on emunand. I mean you dont touch hekate with sxos so if your emunand is lower than sysnand,you are fucked without sleep Mode.
don't worry, sx will quickly steal whatever hekate did to fix the sleep mode issue.
--------------------- MERGED ---------------------------
Oh, I'm definitely dumping the clean NAND as soon as possible, don't worry about that. I just wanted to wait until I had a proper jig so I could boot into RCM without damaging the contacts by any other means.
My question is: since I don't have any dongles or jigs at the moment, but already own a physical copy of Super Mario Odyssey, is it okay if I at least play that game until I install any homebrew?
Doing that would would prompt an update to 3.0.1, so a later backup of the NAND would also carry that firmware, instead of the one that my launch day unit currently has (which is the original 1.0.0, I assume).
For the purposes of maintaining homebrew functionality and making the console more "future-proof" in terms of hacks, would a NAND backup of the original 1.0.0 firmware be preferable over one from a 3.0.1 system? Or it doesn't really matter, as long as the OFW is below a certain version (many are on OFW 4.0.1)?
well, you'd definitely be more future proof with a clean 1.0.0 nand backup and no fuses burnt, because you pretty much have every option from there.
(that said, I'm not sure if 1.0.0 works with all current homebrew, I feel like i heard there's some problems there, look into that)
updating to marios 3.0.1 would burn fuses, but 3.0.1 with burnt fuses is still a pretty good place to be, compared to 4.1 which is somewhat less ideal and everything after which will just deliver the standart switch hack experience.
it all depends on how patient you can wait, how much you care about a potential cold boot exploit, if you like using autorcm and what you want from the hacked switch overall.
currently, all firmware can be hacked for both backups and normal homebrew. even the latest 6.2 works fine and if you can deal with autorcm/injecting payloads through a dongle or a phone forever, you may not even care about the whole early nand stuff. in that case, any clean (or even unclean if you dont really expect to go legal and online with this console anyways) nand backup would suffice to restore from a brick, for example
