You can use creport on reinx though. And nothing is sent to nintendo because of the custom PM implemented. The toolkit is pretty solid. And we have more features coming soon
Is that not the case with atmosphere also?
You can use creport on reinx though. And nothing is sent to nintendo because of the custom PM implemented. The toolkit is pretty solid. And we have more features coming soon
Is that not the case with atmosphere also?
I think what Rei was getting at is "Medoli900 was mistaken, ReiNX can use creport if you want and nothing is sent to Nintendo..." Basically, he's refuting the cons listed for ReiNX. Also, and I'm speaking for myself here, using a "deprecated way" of getting into the homebrew menu doesn't mean much because I consider having to use hblauncher to override another app as being deprecated when you could have just installed it a month ago as an NSP instead and already get the "new" features that hbmenu now implements.
Why is Switches with lower serial#s with the original firmware at 4.1 prefable?
as someone who haven't tried atmosphere, how do you access homebrew channel on atmosphere?ReiNX:
Cons: Uses a deprecated way to redirect the gallery to the Homebrew Channel.
as someone who haven't tried atmosphere, how do you access homebrew channel on atmosphere?
as someone who haven't tried atmosphere, how do you access homebrew channel on atmosphere?
The same way you access it on all the others. Via the Album app
oh i see, so it's different on how it was implemented but nothing changes on the user endI believe this is referring to the fact that ReiNX uses the exefs of hbloader to redirect to homebrew menu instead of using the made up "hbloader.nsp" that switchbrew released for 2.0. It's a moot point, really, but clearly that's the only "flaw" they were able to find.
Huh. I read that your Creport was an old implementation pre-Atmosphère 0.7.5. It's great if you updated it. Admittedly, keeping up with the Switch scene is pretty hard while you have 3 projects and 4 homeworks to do, plus finals that are comingYou can use creport on reinx though. And nothing is sent to nintendo because of the custom PM implemented. The toolkit is pretty solid. And we have more features coming soon
>falling for the memeInteresting.. Most of you keep mention ReiNX but what about RajinX?
>falling for the meme
you must be new
Yes but I was told that RajinX is better than ReiNX and some said it is better than RajinX. That's why I am not sure which one.
RajiNX is a project born out of salt. The only reason it exists is as an excuse for the developer to create the patches that allow piracy for the Atmosphere CFW without openly saying he made them for Atmosphere, because you know, "Piracy is bad, mmkay."
rajkosto has also stated that he will no longer be supporting RajNX in an effort for people to move to the CFW it is actually based off of which is Atmosphere.Interesting.. Most of you keep mention ReiNX but what about RajinX?
rajkosto has also stated that he will no longer be supporting RajNX in an effort for people to move to the CFW it is actually based off of which is Atmosphere.
Why not just use and try out both to see which one you prefer? The differences between them aren't all that large to end-users.Ahh, I see. So, I should get ReiNX and Atmosphere or should I get Atmosphere ? I am a little bit confused. Sorry.
EmuNAND isn't shitty anymore. In fact, it's better than what we have on 3DS.SX OS:
Pros: You can load XCI, I guess. I think dOPUS can install XCI on other CFW, but I'm not sure.
Cons: Behind a payed license. Closed-Source (if that's a cons for you). Shitty "EmuNAND".
ReiNX:
Pros: Can install NSP. Has a toolkit homebrew (I'm not sure of the quality of it though).
Cons: Doesn't have Creport reimplemented, so every time the console crashes the logs are sent to Nintendo. Uses a deprecated way to redirect the gallery to the Homebrew Channel.
Atmosphère:
Pros: Is the original CFW that other CFW is based on. Has the reimplementation of Creport.
Cons: Doesn't natively support unsigned NSP installation (some kips has been made to enable it though).
Every CFW needs a way to push payloads (through TegraRCM and a USB-* to USB-C cable, an Android phone, or a dongle) and a way to enter RCM.
Déjà-Vu is an exploit in the making which will works for 2.0-4.0 (maybe more) firmware which will not need a jig. If you want to use a jig, the firmware kinda doesn't matter (6.x has some issue with some homebrew, like custom theme).
Also, the "emuNAND" on SX OS is not really an emuNAND.
https://gbatemp.net/threads/how-does-sx-os-emunand-work.518936/