It'd be better on my sanity to have more devs PR-ing shit than my small team whom im teaching as we go lol.. The cynic in me thinks instead we'll just get SimonNX and RNXTools. kek
If anybody make commits to your git , does it grant them power to change the cfw name too? I I would like if you keep it as ReiNX, the first public cfwIt'd be better on my sanity to have more devs PR-ing shit than my small team whom im teaching as we go lol.. The cynic in me thinks instead we'll just get SimonNX and RNXTools. kek
The shit stirrer in me can't help but suggest asking ktemkin to come on boardIt'd be better on my sanity to have more devs PR-ing shit than my small team whom im teaching as we go lol.. The cynic in me thinks instead we'll just get SimonNX and RNXTools. kek
You're probably not wrong. Most of us are patient enough to wait for a full blown release. Take your time.It'd be better on my sanity to have more devs PR-ing shit than my small team whom im teaching as we go lol.. The cynic in me thinks instead we'll just get SimonNX and RNXTools. kek
If anybody make commits to your git , does it grant them power to change the cfw name too? I I would like if you keep it as ReiNX, the first public cfw
Inb4 LumaNXIt'd be better on my sanity to have more devs PR-ing shit than my small team whom im teaching as we go lol.. The cynic in me thinks instead we'll just get SimonNX and RNXTools. kek
That's probably going to happen regardless of when anything is released.The cynic in me thinks instead we'll just get SimonNX and RNXTools. kek
I see, then it's okay, take your time, we wouldn't want the name to be changed. The cfw is your baby afterall, a product of love and dedication.no but once it's made public anybody can fork the code and call it whatever they want.
I think that could fry your Switch.
I have a 2.3 if you need to test that fwworks on 4.x and up actually but tbh i blame Noor, think it's her console lmao.. idk
Thinking about just releasing the code since all the piracy patches i made seperate from the cfw ofc so doesnt make sense to hold on to the cfw.. so might upload in the next 5 hrs. ;p
lakka is also capable off running gpu docked speed in handheld modeHmm in dock mode the switch gpu runs in fullspeed and nothing got fried.
If your Switch is patched, you will not be able to load this CFW until another exploit is released.Should someone who's on 4.1 update to the latest version then? I thought I read somewhere that updating is now unsafe. I think that was on the ipatched switch discussions...
ugggg, if you are hoping for a hack that use software, stay on 4.1.Should someone who's on 4.1 update to the latest version then? I thought I read somewhere that updating is now unsafe. I think that was on the ipatched switch discussions...
Right, thanksugggg, if you are hoping for a hack that use software, stay on 4.1.
Mine is not patched.If your Switch is patched, you will not be able to load this CFW until another exploit is released.
Great info. ThanksFirst, ReiNX is compatible with 4.1.0.
Second, if you can use Fusée Gelée on your system and you're content with forever using Fusée Gelée to load CFW, then it is safe to update. You can also follow this guide to update while preserving a downgrade path to 4.1.0 by not burning efuses, but it requires that you install AutoRCM, which will cause your Switch to coldboot into RCM each time you power it on.
If you're on a newer Switch that is not vulnerable to Fusée Gelée, then you should not update.