Hacking RELEASE [Official] ReiNX thread [DEAD]

  • Thread starter Thread starter Reisyukaku
  • Start date Start date
  • Views Views 1,098,871
  • Replies Replies 2,959
  • Likes Likes 240
Status
Not open for further replies.
I read that, I was referring to "no advantages over hekate" as hekate is essentially "just" a bootloader and thus it's atmosphere which is being used to boot
For the moment, there's no reason for the average user to use this over Hekate plus the AiO SDFiles. In the future, ReiNX will get more features, such as signature patching.
They go together. For clarity, here are the end user's main CFW options:
  1. SX OS, which has signature patches but costs money
  2. Hekate plus the AiO SDFiles, which doesn't have signature patches, but it's free and currently has the most features for a free CFW
  3. ReiNX, which can launch without Hekate. It's free, but it's unfinished and presently doesn't have anything the other two options above don't have. It will probably have signature patches in the near-ish future.
 
They go together. For clarity, here are the end user's main CFW options:
  1. SX OS, which has signature patches but costs money
  2. Hekate plus the AiO SDFiles, which doesn't have signature patches, but it's free and currently has the most features for a free CFW
  3. ReiNX, which can launch without Hekate. It's free, but it's unfinished and presently doesn't have anything the other two options above don't have. It will probably have signature patches in the near-ish future.
not to bother again, but you can add hekate to all of those entries, as for example a really nice setup is:

SX Pro Dongle -> Boot custom bootloader (hekate) w/ many tools -> autoboot desired cfw -> ReiNX/ATM/SXOS
 
At the core, all existing - and most likely future - Switch CFWs use Hekate's hardware init and bootloader, launching Stratosphere's sysmodule reimplementations, with Switchbrew's Homebrew Launcher bundled up somewhere inside, being run through an exploit developed independently by Ktemkin and F0verflow, on a Nintendo console with Nvidia guts in it.
People really need to stop playing whodunit and picking favorites, we're all in this together.
 
  • Like
Reactions: CptPotato
not to bother again, but you can add hekate to all of those entries, as for example a really nice setup is:

SX Pro Dongle -> Boot custom bootloader (hekate) w/ many tools -> autoboot desired cfw -> ReiNX/ATM/SXOS
Again, I'm aware that Hekate is a bootloader, not a CFW. What I described are the three main CFW options for end users. SX OS and ReiNX are also designed to be able to work independently from Hekate.
 
Again, I'm aware that Hekate is a bootloader, not a CFW. What I described are the three main CFW options for end users. SX OS and ReiNX are also designed to be able to work independently from Hekate.
yes I know, I was just telling my subjective opinion on what the most efficient setup would be
 
VBliYDB.png

This will be the official thread for things related to ReiNX.


What is ReiNX?:
Its a modular custom firmware for the Nintendo Switch that uses 'smart' patching for future proofing and just works™

Features:
  • Loads all KIPs from /ReiNX/sysmodules/ directory
  • Optional custom kernel/secmon/warmboot
  • Default kips with exefs redir from /ReiNX/title/{tid}
Future plans:
I want to maintain the modularity of the codebase and focus on custom sysmodules.


Credits:
See github page.

FAQ:
Is your code political?
No. My code isn't sentient enough to understand politics. But considering it runs on anyone's switch, I can assume it's at least not a bigot.

Main branch: https://github.com/Reisyukaku/ReiNX

Discord: https://discord.gg/NxpeNwz
(Discord supports free speech and memes)
I would like to know if this completely eliminates access to the Nintendo servers and that they see the console certificate, be able to test applications and copies without fear of being banned?
 
But at least ReiNX uses for it's hwinit naehrwert's code. So you can't really say "independently from hekate" because it is actually based on hekate.
Yes, I'm aware of this too, but what I mean is you don't need to specifically launch Hekate to boot ReiNX. You do need to do that with one of the three main CFW options for end users.
 
for those who want it
Blue screen after splash screen. Same thing happened when i compiled my self. Thats why i tried yours. Are we suppose to add other .kip's to get it working?

Im on 4.1.0 with Hekate fliles on still on SD card
 
Last edited by kylum,
Can anyone confirm after sending payload you get the splashcreen then bluescreen on switch? I'm on 3.0.1 new out the box switch.
 
--------------------- MERGED ---------------------------

Blue screen after splash screen. Same thing happened when i compiled my self. Thats why i tried yours. Are we suppose to add other .kip's to get it working?

Can anyone confirm after sending payload you get the splashcreen then bluescreen on switch? I'm on 3.0.1 new out the box switch.

not sure
i only use sx os

I don't have the blue screen issue :/ Boots up just fine (OFW 5.1) and I have used SX OS before. I formatted my SD card Fat32 and everything works fine :)
 
They go together. For clarity, here are the end user's main CFW options:
  1. SX OS, which has signature patches but costs money
  2. Hekate plus the AiO SDFiles, which doesn't have signature patches, but it's free and currently has the most features for a free CFW
  3. ReiNX, which can launch without Hekate. It's free, but it's unfinished and presently doesn't have anything the other two options above don't have. It will probably have signature patches in the near-ish future.

Why no one yes hacked SX OS and dicovery how signature patches works? I mean maybe there's no signature patch at all and SX OS uses layeredfs to play games idk.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum