For the end user, the difference is meaningless. But it just seems odd to call RajNX a CFW since rajkosto didn't make Hekate or Atmosphere which is what RajNX is. It would be like calling tomGER's SD files a CFW which is also not true. These are bundles of pre-packaged CFW and homebrew to ease the transition from a clean Switch to a hacked one for the end user also known as Starter Packs (note the thread title).So from what understand from @Draxzelex ReiNX is built more from the ground up to be it's own thing, described as "a modular custom firmware for the Nintendo Switch that uses 'smart' patching for future proofing and just works" and RajNX is basically Hekate + Atmosphere with some added patches and tools. I'm thankful for this explanation but now what I'm wondering is what benefits or differences there is for the end user between the two CFW.
Ah I see. Then what are the differences between using Atmosphere in a starter pack like RajNX over ReiNX? Im guessing to the user there really might not be much of a difference but I like having an understanding of these things even if they arent important things to know.For the end user, the difference is meaningless. But it just seems odd to call RajNX a CFW since rajkosto didn't make Hekate or Atmosphere which is what RajNX is. It would be like calling tomGER's SD files a CFW which is also not true. These are bundles of pre-packaged CFW and homebrew to ease the transition from a clean Switch to a hacked one for the end user also known as Starter Packs (note the thread title).
Customization of the CFW differ greatly between the 2. Customizing Atmosphere involves changing the launch configuration of whatever bootloader you're using which for now is Hekate. Meanwhile ReiNX automatically supplements some of the most useful patches while others are optional and toggleable via the ReiNX toolkit with the Kip Manager feature. Functionally, both are identical for the end user.Ah I see. Then what are the differences between using Atmosphere in a starter pack like RajNX over ReiNX? Im guessing to the user there really might not be much of a difference but I like having an understanding of these things even if they arent important things to know.
Customization of the CFW differ greatly between the 2. Customizing Atmosphere involves changing the launch configuration of whatever bootloader you're using which for now is Hekate. Meanwhile ReiNX automatically supplements some of the most useful patches while others are optional and toggleable via the ReiNX toolkit with the Kip Manager feature. Functionally, both are identical for the end user.
ReiNX is designed for people who just want to do simple things without too much fuss between computer and Switch. It does most of what people want from a CFW such as playing homebrew and backups. Its sort of like the Windows of operating systems which makes Atmosphere the Linux in this metaphor. Its designed to completely replace the entire OS of the Switch (named Horizon) meaning its potential capabilities exceed that of ReiNX. What most users are anticipating from Atmosphere is the release of EmuNAND which ReiNX may or may not implement. However to most end-users, this difference is potential is not really utilized nor is it useful unless you're a developer. Personally, I'm waiting on whatever CFW implements a proper EmuNAND first so that means its Atmosphere until another development team announces they're working on it.Thank you for your responses. Ended up stalking your profile and reading through most of your recent posts in the SWITCH NOOB PARADISE thread. Probably learned more from your posts there than I have from all the guides and other posts I've read.
Which do you personally like to use between ReiNX and Atmosphere? I see that you recommend using one of these free CFW often but never really recommending one over the other, so if you really had to choose which would you recommend and why? I've been trying to see if there were any specific things that ReiNX or Atmosphere couldn't do or if there was a feature unique to that only one of those CFW but haven't found anything. I know it's probably dumb that I care but I'm pretty weak to my analysis paralysis which sorta makes it hard to be decisive.
I also see atmosphere getting a lot of hype in some posts because it's supposedly going to be better than ReiNX in the future and I'm curious why people think that. Just looking through the git repos for both it looks like there has been a lot more work put into Atmosphere, but of course idk if that actually means anything.
ReiNX is designed for people who just want to do simple things without too much fuss between computer and Switch. It does most of what people want from a CFW such as playing homebrew and backups. Its sort of like the Windows of operating systems which makes Atmosphere the Linux in this metaphor. Its designed to completely replace the entire OS of the Switch (named Horizon) meaning its potential capabilities exceed that of ReiNX. What most users are anticipating from Atmosphere is the release of EmuNAND which ReiNX may or may not implement. However to most end-users, this difference is potential is not really utilized nor is it useful unless you're a developer. Personally, I'm waiting on whatever CFW implements a proper EmuNAND first so that means its Atmosphere until another development team announces they're working on it.
did you made a nand backup first ?i did a ofw upgrade from 4.1 to 5.1 using choidujourNX. I am using RajNX and it stucks at nintendo logo.
Any help, please?
I did. Thanks.did you made a nand backup first ?
everything works fineDid anyone test current RajNX 0.7.5.1 with the newest OFW release (6.0.1-1.0) and have results to share?