Hacking [No longer maintained] RajNX - starter pack for Nintendo Switch

[rajkosto]

This project is no longer being maintained


Latest old version: RajNX 0.7.5.1a (released on 01.11.2018)
Download link: Get it from https://switchtools.sshnuke.net (as usual) !
Not really recommended for use anymore unless you need it for 1.0.0 easy run of ChoiDujourNX, for everything else use Atmosphere (or one of its repacks).


INSTALLATION
Extract the contents of the zip onto the root of your microSD (overwriting everything when prompted), then run rajnx_ipl.bin using TegraRcmSmash or whatever USB payload injector you have !

USE
Select "Launch firmware" from the menu, select the appropriate profile, and you should be good to go !

FEATURES

• Works on all Nintendo Switch firmwares AUTOMATICALLY, no need to manually swap files around on your microSD !
• Supports homebrew via latest hbloader and hbmenu (fully customizable button combo and titleId you want to use to enter hbmenu, default is to launch hbmenu instead of Album unless "R" is held)
• Supports exefs redirection, exefs patches, unsigned ncas and tickets ("sigpatching")
• Supports extra options like LayeredFS (for romfs patches) and PreventGCUpdate via launch menu options!
• Reduced telemetry by blocking eclct sysmodule from running, also uses creport that dumps to microSD instead of uploading to Nintendo.

ADD-ONS

• jakibaki sys-ftpd background ftp server sysmodule - get from https://github.com/rajkosto/sys-ftpd/releases/
• Tinfoil is no longer included, get latest build from https://buildserv.stayathomeserver.club/tinfoil/ and place tinfoil.nro into switch folder on microSD

Binaries contained in this release can be generated by compiling the following repositories:

Hekate fork : https://github.com/rajkosto/hekate/tree/rajnx
Atmosphere fork: https://github.com/rajkosto/Atmosphere/tree/rajnx
hbloader: https://github.com/rajkosto/nx-hbloader
hbmenu: https://github.com/switchbrew/nx-hbmenu​

SUPPORT
Ask your questions in this thread, no need to go to a separate Discord !
Serious discussion only, please do not spam it up with joke posts/bickering.

 

[Quantumcat]

If you want this thread to stay please explain what this is based on and what changes have been made, and provide the source. @rajkosto

 

[jakkal]

can you install nsps using this cfw?

 

[rajkosto]

can you install nsps using this cfw?

I don't see why not

 

[jakkal]

I don't see why not

k ill test it out

 

[Genwald]

Nice work and nice memes raj. Works great. Its nice to have options in cfw.

 

[Shubshub]

Does your Custom Firmware have an EmuNAND Solution? Or is it something that you have planned?

 

[Drakia]

@rajkosto I'm just going to state again, that as this has no apparent source changes over the underlying projects, this seems more similar to tomGER's SDFiles releases than it does a CFW.
Would you be opposed to re-labelling this to indicate it is a "Starter Pack", as opposed to trying to pass off others unmodified work as your own "CFW"?

Unless of course you are actually planning on developing this CFW independently of Atmosphere/Hekate.

 

[rajkosto]

My source changes to the underlying projects are already mainlined, I don't see why it would need to be my own fork ?

 

[Drakia]

My source changes to the underlying projects are already mainlined, I don't see why it would need to be my own fork ?

So in that case, you are a contributor to Atmos/Hekate, and this isn't actually its own standalone CFW/require its own thread?

 

[rajkosto]

Unfortunately it does not have emuNAND support at the moment, however it is the most feature-packed CFW yet !

 

[Drakia]

This CFW pack has additional files rather than just being hekate + atmosphere, though.

So, it's a starter pack?

 

[rajkosto]

What is your definition of a CFW that I must abide to ?

 

[Drakia]

No, it fits the definition of CFW like all others on this forum.

No, this has no plans outside of just bundling files together, and has no source changes (Or even forks) of the underlying code, nor any plans to fork/change the underlying code. That is a starter pack, not a custom firmware.

 

[rajkosto]

I don't see how you can know what my plans are for the future.

 

[jakibaki]

No, this has no plans outside of just bundling files together, and has no source changes (Or even forks) of the underlying code, nor any plans to fork/change the underlying code. That is a starter pack, not a custom firmware.

It has additional patches and Raj integrated a bunch of his work into the unterlying projects.

It has about as much of a right to call itself cfw as a certain other cfw which is basically just a bootloader + atmosphere sysmodules (and more features ).

 

[Darth Meteos]

I don't see how you can know what my plans are for the future.

Holy shit
the guy who says we're a copy cfw is trying to pull the "things will change" card

 

[Drakia]

I don't see how you can know what my plans are for the future.

I did include this in my above post, though I had edited it in a few seconds after I hit post, so you may have missed it, sorry about that
> Unless of course you are actually planning on developing this CFW independently of Atmosphere/Hekate.

So, do you have plans to develop this, independently of Atmos/Hekate? And is that a "near future" plan, or an "I'm making this up to keep the thread" plan? Because, if it's not near future, then again, this thread should be marked as a starter pack

 

[rajkosto]

I kept the folder name atmosphere so that it remains compatible with the currently-existing community work (where you add more exefs overrides to).
Apparently changing this folder name is something i must do to abide by your definition of CFW.

 

[ToOldGamer]

i will try it, you made so many usefull tools for the nsw
thanks,
TOG