you mean atmosphere probably. as hekate is a custom bootloader and not a cfw, you can also boot ReiNX with hekate, custom bootloader + cfw is a good deal.
How to do this? I didn't succeed.
you mean atmosphere probably. as hekate is a custom bootloader and not a cfw, you can also boot ReiNX with hekate, custom bootloader + cfw is a good deal.
How to do this? I didn't succeed.
|-- loader
| |-- hekate-ipl.bin
| |-- loader.ini
| |-- whatever.bin
|-- hekate_ipl.ini
|-- whatever.ini
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
They go together. For clarity, here are the end user's main CFW options: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.
not to bother again, but you can add hekate to all of those entries, as for example a really nice setup is:They go together. For clarity, here are the end user's main CFW options:
- SX OS, which has signature patches but costs money
- 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
- 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.
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.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
yes I know, I was just telling my subjective opinion on what the most efficient setup would beAgain, 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.
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?
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:
Future plans:
- Loads all KIPs from /ReiNX/sysmodules/ directory
- Optional custom kernel/secmon/warmboot
- Default kips with exefs redir from /ReiNX/title/{tid}
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)
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.SX OS and ReiNX are also designed to be able to work independently from 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.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.
sure ill write one up right nowTutorial to use friend
sure ill write one up right now
gimmie about 10 minutes
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?for those who want it
not sureBlue 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?
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
They go together. For clarity, here are the end user's main CFW options:
- SX OS, which has signature patches but costs money
- 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
- 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.
yeah you dont knowWhy 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.