Hacking RELEASE [Official] ReiNX thread [DEAD]

[Draxzelex]

Thanks, so I can update my switch to the latest fw before doing ReiNX? and regarding (as long as your console's hardware is not patched which shouldn't be the case assuming you have a 3.0 Switch), how to identify a console that isn't hardware patched? well so I can prevent buying another switch that is hardware patched. TIA.

You can use this thread to identify if the hardware is patched or not. As for updating to the latest firmware, you can do that but I would recommend using this tool to do so as it lets you update without burning fuses. Fuses are literal microscopic eFuses embedded into your console that are burnt to prevent downgrades. Keeping the fuses for a 3.0 console means you might be able to take advantage of a future warmboot exploit that doesn't use a jig or USB cable which is needed for the current exploit that works on all firmwares.

 

[Khim09]

You can use this thread to identify if the hardware is patched or not. As for updating to the latest firmware, you can do that but I would recommend using this tool to do so as it lets you update without burning fuses. Fuses are literal microscopic eFuses embedded into your console that are burnt to prevent downgrades. Keeping the fuses for a 3.0 console means you might be able to take advantage of a future warmboot exploit that doesn't use a jig or USB cable which is needed for the current exploit that works on all firmwares.

Thanks so much, I need to learn more first before proceeding. Cheers.

 

[minooch_e]

So in the off-chance that ReiNX caused a Switch a brick, restoring the backed-up NAND will fix it?

Correct, you can still boot into RCM & then restore your NAND backup & then start again

 

[macia10]

any way to get sys-netcheat working on rei? When I add it to sysmodules dir it hangs on switch logo.

 

[BeardedGamer]

Correct, you can still boot into RCM & then restore your NAND backup & then start again

how do i make a NAND backup on ReiNX

 

[aGen4er]

hello this might have been answered before but whenever I completely power off my switch the homebrew channel is gone is it a common problem ?

 

[Ashura66]

hello this might have been answered before but whenever I completely power off my switch the homebrew channel is gone is it a common problem ?

...Completely powering off your system erases the CFW...meaning you'l have to enter RCM and inject the payload again

 

[Dothackjhe]

hello this might have been answered before but whenever I completely power off my switch the homebrew channel is gone is it a common problem ?

The jailbreak we have for the Switch is not permanent just yet. Like aforementioned, you would have to re-trigger the exploit again by re-injecting the payload if you had it turned off.

 

[aGen4er]

...Completely powering off your system erases the CFW...meaning you'l have to enter RCM and inject the payload again

so should i stick to sleep mode for now ?

 

[Ashura66]

so should i stick to sleep mode for now ?

Yep. Don't switch it off completely unless you need to access the SD card to update files or something like that. Other than that just go with sleep mode

 

[huma_dawii]

Yeah after the Wii I've been so paranoid about the sleep mode but it seems its not as bad on Switch

 

[Ashura66]

Yeah after the Wii I've been so paranoid about the sleep mode but it seems its not as bad on Switch

Sleep mode with CFW works just fine on the Switch now. It's perfectly fine to leave your system on sleep mode while CFW is running

 

[WD_GASTER2]

hello, sorry if im asking something that has been solved...
I am on 3.0.1 and get a blue screen after the splash. any suggestions?

thanks

 

[Dothackjhe]

hello, sorry if im asking something that has been solved...
I am on 3.0.1 and get a blue screen after the splash. any suggestions?

thanks

I Google it. Here's a Reddit thread I found: https://www.reddit.com/r/NintendoSw...ubleshooting_i_got_the_switch_blue_screen_of/

 

[WD_GASTER2]

this only happens when launching the cfw. and it works right after.

 

[Dothackjhe]

this only happens when launching the cfw. and it works right after.

Which CFW are you running?

 

[Clydefrosch]

I'm on 3.0.2, using the reifiles from the new sd files website (where you chose from a bunch of homebrew and cfw files)
I'm using recardo to boot reinx.bin, getting up to the splash screen, then the screen goes dark (with background light on) and then goes out completely.

here's my reinx folder, am i missing something?

 

[Dothackjhe]

I'm on 3.0.2, using the reifiles from the new sd files website (where you chose from a bunch of homebrew and cfw files)
I'm using recardo to boot reinx.bin, getting up to the splash screen, then the screen goes dark (with background light on) and then goes out completely.

here's my reinx folder, am i missing something?

I had been injecting the ReiNX payload via TegraRCMGUI, I never had problem with it. Right now, I'm using the latest version of Hekate as a bootloader and then consequently running ReiNX with it, still working smoothly with TegraRCMGUI.

The download the files from this YouTube video if you're interested:

 

[Clydefrosch]

I had been injecting the ReiNX payload via TegraRCMGUI, I never had problem with it. Right now, I'm using the latest version of Hekate as a bootloader and then consequently running ReiNX with it, still working smoothly with TegraRCMGUI.

The download the files from this YouTube video if you're interested:

I don't think recardo is the issue.
It boots hekate no problem and hekate has the same issue, it shows that boot screen with the text, the splash screen, 3 seconds of black screen and then turns off entirely.

I tried again with the sdfiles from tumger, booting Rei from hekate, same issue.

 

[gt10]

i had the same problem.
latest working version is with meteos stash 2.2
with new clear install of newest version from discord it goes to black screen.
but when i leave the old files from v2.2 on the sd card and just overwrite with the newest files it works.
there must be one ore more files from the v2.2 that seems to be needed to start the cfw successfully.

my fw is 4.1