Hacking Question [Poll] What CFW are you currently using

  • Thread starter Thread starter samsam91
  • Start date Start date
  • Views Views 17,427
  • Replies Replies 144
  • Likes Likes 3

What CFW are you using

  • SX OS

    Votes: 192 56.0%
  • ReiNX

    Votes: 115 33.5%
  • RajNX

    Votes: 36 10.5%

  • Total voters
    343
RajNX isn't technically a CFW either. Its just a modified Hekate running on Atmosphere. Seriously, Atmosphere has been out for months guys and everyone has been running it. Those SD files weren't compiled from thin air.

Why is ReinX considered a true CFW but not RajNX? Both can basically do the same thing, from what i read the only difference is that ReinX have anime
 
Why is ReinX considered a true CFW but not RajNX? Both can basically do the same thing, from what i read the only difference is that ReinX have anime
ReiNX was built from the ground up. The only similarity ReiNX has to anything else is Hekate because they use the same hwinit. Other than that, its patches are completely its own thing. RajNX is basically Hekate + Atmosphere with some IPS patches so people can play .NSP games they do not own. On top of that, it was bundled with other useful tools such as creport, disabling of eclct, and other homebrew. Its a mish-mash of forks most of which Rajkosto himself did not make.
 
ReiNX was built from the ground up. The only similarity ReiNX has to anything else is Hekate because they use the same hwinit. Other than that, its patches are completely its own thing. RajNX is basically Hekate + Atmosphere with some IPS patches so people can play .NSP games they do not own. On top of that, it was bundled with other useful tools such as creport, disabling of eclct, and other homebrew. Its a mish-mash of forks most of which Rajkosto himself did not make.

Thanks for explaining, but in practice for the end user there is not much difference between them no? And i choose RajNX precisely because it have these tools you mentioned, while ReinX did not, at least when i researched this some weeks ago.. maybe they have it now too.
 
Thanks for explaining, but in practice for the end user there is not much difference between them no? And i choose RajNX precisely because it have these tools you mentioned, while ReinX did not, at least when i researched this some weeks ago.. maybe they have it now too.
From the ReiSwitched server, it lacks the tools that rajkosto packages into ReiNX. However tomGER was kind enough to compile all of the tools RajNX uses for ReiNX in his SD files which now reduces the differences between the two to how their bootloaders differ. Hekate currently offers more options than ReiNX which is designed for ease of convenience.
 
  • Like
Reactions: Ivellios
Hs no clues why so many people use SX OS....maybe because they bought the pro license before reiNX and keep using to convince himself that have wasted no money?
 
Hs no clues why so many people use SX OS....maybe because they bought the pro license before reiNX and keep using to convince himself that have wasted no money?
That's what I was thinking. Even after a free alternative to Gateway came out for the 3DS, I still was using my Gateway (that I won on GBATemp) for months or years afterwards. It was a convenience thing, and it was what I already understood and had set up.

It should also be noted that a majority of people, according to this poll, don't use SX OS. As new users pick a free CFW and as old users switch to ReiNX or RajNX for new features, the percentage of SX OS users is likely to shrink. It's what happened to Gateway.
 
Hekate is NOT a CFW though...
This was already previously contested so I'll just bring up a few of the salient points. While it is technically a bootloader, the definition of a CFW is in of itself misleading as there are 2 different interpretations: a firmware that patches the existing one (CustomizedFW) or replaces the existing one (CustomFW). Now majority of end users couldn't care less what its called nor do most developers really care how it is referred to as long as the point gets through. There was debate on whether it was more appropriate to refer to Hekate as a HEN (Homebrew ENabler) because it avoids the usage of the misleading CFW but due to multiple reasons, it did not catch on. All that being said, Hekate has the power to not only act as a substitute bootloader but apply patches to the firmware. Not to mention that the current "CFWs" (namely ReiNX and Atmosphere, RajNX is Atmosphere with IPS patches) need a bootloader in order to boot up in the first place.
 
ReiNX was built from the ground up. The only similarity ReiNX has to anything else is Hekate because they use the same hwinit. Other than that, its patches are completely its own thing. RajNX is basically Hekate + Atmosphere with some IPS patches so people can play .NSP games they do not own. On top of that, it was bundled with other useful tools such as creport, disabling of eclct, and other homebrew. Its a mish-mash of forks most of which Rajkosto himself did not make.

An unofficial bootloader + Custom files and patches to the firmware that loads at boot... Thats sounds just about what all CFW's do..

Sure this is a Frankenstein creation and not a thing created from scratch in one project.

But I still feel like it qualifies as a CFW.
 
An unofficial bootloader + Custom files and patches to the firmware that loads at boot... Thats sounds just about what all CFW's do..

Sure this is a Frankenstein creation and not a thing created from scratch in one project.

But I still feel like it qualifies as a CFW.
Forgive me for being unclear initially however this is not what I was contesting. What RajNX accomplishes justifies calling it a CFW. However the entity known as RajNX refers to the collection of files that rajkosto compiled from pre-existing sources. RajNX does not refer to its own CFW and/or bootloader because it is quite literally a semi-modified Hekate plus a compilation of the latest build of Atmosphere with some IPS patches thrown in there. It'd be more accurate to to refer to RajNX as an early beta of Atmosphere but the way he packaged (and marketed) it was a combination of files most of which he did not himself to make. If we were to call RajNX a CFW, then that would make the SD files tomGER compiles a CFW even though all he did was combine files and package them into one package for public distribution. If you are fine with that last line, then yes RajNX is a CFW.
 

Site & Scene News

Popular threads in this forum