Guide link

I plan on fully keeping it up-to-date.

Has instructions that should work for all firmwares, a part for software-side 1.0.0 (PegaSwitch + reboot_to_rcm) and an FAQ detailing some common questions + a guide on how to dump your NAND.

Hopefully this will be useful.

If something is unclear/could use clarification, please use the Issue Tracker. Same goes for suggestions to add to the FAQ.

ReiNX/SX OS/sigpatches into Atmosphere won't be supported, don't bother asking, FAQ explains why.

Credits:

• Individual credits are listed for each page
• Jisagi for layout, T3CHNOLOG1C for the original guide.
• All developers for the referenced tools and utilities.

 

[AliciaBurrito]

Nice guide, though ReiNX currently does not have any incompatibilities with homebrew unlike SX OS.

 

[RepeatingDigits]

Thanks.

 

[Draxzelex]

In your FAQ, you state that there are homebrew incompatibilities with ReiNX however I have yet to discover one for myself in the several months that it has been out. Care to elaborate further on these incompatibilities?

 

[tinbs]

just a little note, the layout is a little difficult to parse, with the different OS options listed one after the other every section on the same page.
maybe split the sections into different pages, or it might be worth having a page per OS?
either way good effort

 

[Reisyukaku]

Need to complete the cfw triforce and add ReiNX

 

[AliciaBurrito]

Need to complete the cfw triforce and add ReiNX

But haven't you heard? It's just an Atmosphere fork with many incompatibilities

 

[Reisyukaku]

But haven't you heard? It's just an Atmosphere fork with many incompatibilities

Nice meme mum. I'm just trying to help OP's guide stay relevant ;-;

 

[Kilim]

why does everyone have a guide now ;_;

 

[Ev1l0rd]

just a little note, the layout is a little difficult to parse, with the different OS options listed one after the other every section on the same page.
maybe split the sections into different pages, or it might be worth having a page per OS?
either way good effort

The OS sections have anchors in them and a TOC before them to easily jump to those parts.

 

[palantine]

Care to explain what the incompatibility with ReiNX is?

Having developed several pieces of homebrew using it and having worked with other homebrew authors like Adubbz (who made Tinfoil) I have never experienced any problems with it, and in fact the support for it by the developers seems to be extremely good.

If you can back it up then I'll believe you, but given my experience I find this extremely hard to believe.

 

[Kilim]

just read through the guide, im still kind of at odds with how, even though this is affiliated with the Official Nintendo Homebrew Discord (or whatever) - you seem to be ignoring ReiNX and spreading false information about its 'incompatibility with homebrew?'

just seems very immature and tactless - the entire purpose for multiple CFWs in a scene is to benefit the end user through competition and choice, but you're simply ignoring that to (what it seems like) push your own agenda, what's up with that?

also lol @ you ignoring everyone else and not replying, common tactic among your crowd

 

[Reisyukaku]

>Thermosphere is Atmospheres implementation of emuNAND
wrong. thermosphere is a hypervisor. They plan on using the hypervisor to impl emunand but thats it.

>ReiNX is unsupported due to being a fork of Atmosphere
wrong. The only code i forked was the optional sysmodules.

>ReiNX and SX OS both have homebrew compatability issues
wrong. No one's ever had any issues with homebrew

Please fix accordingly. Don't be a Trump.

 

[Ev1l0rd]

@Kilim @Reisyukaku @palantine @AliciaBurrito

Two things:

1. I've removed the compatibility claim for now, it may have been possible that it was mixed together w/ the claim about SX OS from the person I got it from.
2. I still won't add ReiNX to the supported list, as it's featureset is pretty much offered by Hekate anyway, and this guide does not aim to set people up with sigpatches/piracy.

--------------------- MERGED ---------------------------

wrong. thermosphere is a hypervisor. They plan on using the hypervisor to impl emunand but thats it.

When Thermosphere makes it into a release, it'll effectively be an emuNAND release, which for the average user going through the guide is much easier to explain than the fine technical details.

wrong. The only code i forked was the optional sysmodules.

Read the full sentence. The rest of the featureset that Atmosphere doesn't already have is offered by Hekate. (and this guide doesn't intent to set up sigpatches/piracy).

 

[masterspike52]

@Kilim @Reisyukaku @palantine @AliciaBurrito

Two things:

1. I've removed the compatibility claim for now, it may have been possible that it was mixed together w/ the claim about SX OS from the person I got it from.
2. I still won't add ReiNX to the supported list, as it's featureset is pretty much offered by Hekate anyway, and this guide does not aim to set people up with sigpatches/piracy.

honestly, your an idiot if you think ReiNX offers the same or less than hekate. The reality is ReiNX comes with more comfortable useability than hekate or atmosphere ever will mainly because with ReiNX i have a toolkit that not only allows me to choose what kips i want activated but also lets me backup my entire 32gb nand in a matter of at most 17 minutes (whereas ill watch hekate do it for half an hour) and i can update with it without having to wait for someone to compile it for me and set up the files. I've never had any problems with it whereas when i use atmosphere i have to learn this whole ini function crap thats unnecessary, go through a whole boot menu thats unneeded and to top it all off its a functioning product that someone doesnt have to tell me "dont run this if you dont know what your doing"

 

[Ev1l0rd]

honestly, your an idiot if you think ReiNX offers the same or less than hekate. The reality is ReiNX comes with more comfortable useability than hekate or atmosphere ever will mainly because with ReiNX i have a toolkit that not only allows me to choose what kips i want activated but also lets me backup my entire 32gb nand in a matter of at most 17 minutes (whereas ill watch hekate do it for half an hour) and i can update with it without having to wait for someone to compile it for me and set up the files. I've never had any problems with it whereas when i use atmosphere i have to learn this whole ini function crap thats unnecessary, go through a whole boot menu thats unneeded and to top it all off its a functioning product that someone doesnt have to tell me "dont run this if you dont know what your doing"

Usability w/ my guide is pretty much the same as with any other guide. You don't need to wait for someone to compile anything, the files are pregenerated, the SD structure is copy-pastable and you don't need to learn how to use any ini files.

If I could ask... did you read the guide, or did you just read the replies here and assumed the rest?

The NAND dump I've kinda mentioned in an earlier post of mine somewhere, but since it's done while Horizon is booted, it may result in a corrupted dump as the NAND might change while it's dumping.

 

[AliciaBurrito]

But haven't you heard? It's just an Atmosphere fork with many incompatibilities

@Kilim @Reisyukaku @palantine @AliciaBurrito

Two things:

1. I've removed the compatibility claim for now, it may have been possible that it was mixed together w/ the claim about SX OS from the person I got it from.
2. I still won't add ReiNX to the supported list, as it's featureset is pretty much offered by Hekate anyway, and this guide does not aim to set people up with sigpatches/piracy.

--------------------- MERGED ---------------------------


When Thermosphere makes it into a release, it'll effectively be an emuNAND release, which for the average user going through the guide is much easier to explain than the fine technical details.


Read the full sentence. The rest of the featureset that Atmosphere doesn't already have is offered by Hekate. (and this guide doesn't intent to set up sigpatches/piracy).

I think it's important to give users a choice, and not strong-arm them into a solution because of personal morals of how someone might use a CFW. Especially since you can use the same sigpatches with Atmosphere/Hekate.

ReiNX has enough features and differentiators from Hekate/Atmosphere that I believe it would be best to at least mention it as a viable choice - even if you link off of your guide to something else like the ReiNX guide itself. Something that has been very popular among those that uses ReiNX is the Toolkit - manage kips, easily change splashscreen, OTA updater for both ReiNX and the toolkit to the latest ReiNX itself, a quick backup system, etc.

To say there are no differences and that it is just a fork of Atmosphere, or that the features are basically the same is not accurate and can be seen as misleading or outright false in terms of the Atmosphere fork part.

 

[nopjmp]

Usability w/ my guide is pretty much the same as with any other guide. You don't need to wait for someone to compile anything, the files are pregenerated, the SD structure is copy-pastable and you don't need to learn how to use any ini files.

If I could ask... did you read the guide, or did you just read the replies here and assumed the rest?

The NAND dump I've kinda mentioned in an earlier post of mine somewhere, but since it's done while Horizon is booted, it may result in a corrupted dump as the NAND might change while it's dumping.

most processes probably aren't writing in the background when homebrew is running. Also it would be as consistent as a "force" shutdown would be, so most of the important data would be safe. It's just another option of creating a dump and I wouldn't say it produces a corrupted dump, just not a 100% clean dump.

 

[palantine]

The NAND dump I've kinda mentioned in an earlier post of mine somewhere, but since it's done while Horizon is booted, it may result in a corrupted dump as the NAND might change while it's dumping.

This actually isn't true in practice. Using an IPC I lock the app from switching out while its dumping then nand. The only partition that can be written to by the OS while the app is running is the SYSTEM partition which can be worked around simply by ensuring that SYSTEM is dumped continuously so that nothing can write to it between partial dumps.

We were worried about this potential problem but after 100s of dump/restore cycle tests (before release) we were able to determine that our method prevented this from happening. Now that its been out for a while we are even more sure because so far there has not been a single reported issue with it.

 

[Ev1l0rd]

This actually isn't true in practice. Using an IPC I lock the app from switching out while its dumping then nand. The only partition that can be written to by the OS while the app is running is the SYSTEM partition which can be worked around simply by ensuring that SYSTEM is dumped continuously so that nothing can write to it between partial dumps.

We were worried about this potential problem but after 100s of dump/restore cycle tests (before release) we were able to determine that our method prevented this from happening. Now that its been out for a while we are even more sure because so far there has not been a single reported issue with it.

Fair enough, I did not know that. Thanks for said clarification.