Hacking [No longer maintained] RajNX - starter pack for Nintendo Switch

VMurphy · Dec 26, 2018

Is it possible to go from RajNX to Atmosphere while keeping your installed NSP's a savegames?

Migz · Dec 26, 2018

VMurphy said:
Is it possible to go from RajNX to Atmosphere while keeping your installed NSP's a savegames?

yes

tataniko · Dec 26, 2018

naddel81 said:
raj is not continuing his great project? why? what to use now that is as easy as rajNX?

I don't understand why Raj abandoned us, end users. I couldn't find any Atmosphere release as easy as RajNX. Nogc & Debug mode are not configured, too many kips, nros & so on. There is no Atmosphere release as easy as RajNX.

naddel81 · Dec 26, 2018

tataniko said:
I don't understand why Raj abandoned us, end users. I couldn't find any Atmosphere release as easy as RajNX. Nogc & Debug mode are not configured, too many kips, nros & so on. There is no Atmosphere release as easy as RajNX.

try SDSetup.com. worked fine for me.

mdmachine · Dec 26, 2018

Yeah sdsetup.com couldn't be any easier...
This was abandoned because its not doing anything that the newer atmosphere and the various bundles (like kosmos) aren't doing better at this point.

lorenzovaquero · Dec 26, 2018

Hi everyone!

Sorry to bother you @rajkosto , but I have a little "problem" running the Homebrew Menu, and so far RajNX has been the only way I could solve it.
That's why I would like to know a little bit more about the hbmenu.nro included in your RajNX 0.7.5.1a.

In a summary:
I have a 2.3.0 Nintendo Switch and I can boot normally into Atmospère (ReiNX gets stuck on the splash screen in "Read pkg1", but that is another subject). However, when I try to open the Homebrew Menu via Album, the Switch turns off or crashes (depending on the CWF "bundle" that I am using).
I have never been able to make it work until I tried using RajNX 0.7.5.1a, which worked without a problem (shotouts to @Skonikol ).
Digging a little bit more, I saw that using "vanilla" Atmosphère or the one bundled in SDFiles and replacing the hbmenu.nro with yours (the one inside RajNX 0.7.5.1a), also made the Homebrew Menu work (no other hbmenu.nro I found seems to work).

So my question is: What's the difference between your 0.7.5.1a hbmenu.nro (1.538.251 bytes) and the official 3.0.1 release one (1.501.423 bytes)?

(there are crash reports and a little bit more of info in Atmosphère's issue #309)
(sorry, but it seems that I can't use hyperlinks)

Thanks in advance and sorry for the inconvenience.

mdmachine · Dec 26, 2018

Why dont you just update to a newer firmware using ChoiDujourNX.
Then everything would work as intended. I think it'll be unlikely you'll get much info in regards to trying to run a newer hbmenu on a "ancient" FW. Not even sure rajkosto even comes around this thread anymore?

tataniko · Dec 26, 2018

naddel81 said:
try SDSetup.com. worked fine for me.

Not really, SDSetup can't cover all features of RajNX.
RajNX is easy, especially for end users who go from 1.0 firmware to other version without losing anything. There is not easier as RajNX.

naddel81 · Dec 26, 2018

tataniko said:
Not really, SDSetup can't cover all features of RajNX.
RajNX is easy, especially for end users who go from 1.0 firmware to other version without losing anything. There is not easier as RajNX.

what is missing to be precise? you can configure all sorts of stuff in sdsetup.

lorenzovaquero · Dec 26, 2018

I will probably end doing that more sooner than later (let's see if I don't burn fuses).

And I thought that older firmwares were "better" in terms of possible new exploits and compatibility, but I see that I am very mistaken.

Either way, I'm still intrigued on the root cause, and I think that it might be interesting for the hbmenu development.

Thanks for your reply!

mdmachine · Dec 26, 2018

tataniko said:
Not really, SDSetup can't cover all features of RajNX.
RajNX is easy, especially for end users who go from 1.0 firmware to other version without losing anything. There is not easier as RajNX.

Bro, you gotta take the time to read or something.

Yes it does cover all the features and more. And if you use ChoiDujourNX and keep autoRCM on, you lose nothing and can roll back to whatever FW you want, at any time.

Also RajNX is done! Been done for a while! So you can accept reality, take the time to get with the program and update. Or you can stay on RajNX and deal with increasingly less functionality indefinitely.

--------------------- MERGED ---------------------------

lorenzovaquero said:
I will probably end doing that more sooner than later (let's see if I don't burn fuses).

And I thought that older firmwares were "better" in terms of possible new exploits and compatibility, but I see that I am very mistaken.

Either way, I'm still intrigued on the root cause, and I think that it might be interesting for the hbmenu development.

Thanks for your reply!

ChoiDujourNX will update and enable AutoRCM, this prevents burning fuses. Which is the main argument in regards to lower firmwares. You can always roll back if/when the time comes that there is something that actually utilizes the fact your on a lower FW.

If I had to guess, the newer hbmenu uses features and functions introduced in later FW or CFW...

tataniko · Dec 26, 2018

mdmachine said:
Bro, you gotta take the time to read or something.So you can accept reality, take the time to get with the program and update. Or you can stay on RajNX and deal with increasingly less functionality indefinitely..

I am satisfied with RajNX on firmware 5.1, the only thing what I don't understand, why did Raj abandon us?

Esjay131 · Dec 26, 2018

tataniko said:
I am satisfied with RajNX on firmware 5.1, the only thing what I don't understand, why did Raj abandon us?

Because he was only seeking attention and just threw this starter pack together to accomplish what he wanted.

cyndor · Dec 26, 2018

tataniko said:
I am satisfied with RajNX on firmware 5.1, the only thing what I don't understand, why did Raj abandon us?

Probably because RajNX was a high quality(?) shitpost making fun of ReiNX?

Esjay131 · Dec 26, 2018

cyndor said:
Probably because RajNX was a high quality(?) shitpost making fun of ReiNX?

Have you read through this thread? That's low quality shitposting.

cyndor · Dec 26, 2018

Esjay131 said:
Have you read through this thread? That's low quality shitposting.

I believe in the beginning RajNX had patches and a couple of other things that the others didn't. That took some effort.

lorenzovaquero · Dec 26, 2018

mdmachine said:
If I had to guess, the newer hbmenu uses features and functions introduced in later FW or CFW...

It may be very possible. However, I'm still intrigued on why RajNX's one works on 2.3.0 and why I haven't seen more people with the same problem.

My Switch is second-handed and it is the first time I attempt to run any CFW, so I have not discarded that it may be a hardware issue (I'm a little bit pessimistic, but who would sell a "perfectly functional" Nintendo Switch).

tataniko · Dec 26, 2018

When will the founder of RajNX return?
Thank you very much.

Esjay131 · Dec 26, 2018

cyndor said:
I believe in the beginning RajNX had patches and a couple of other things that the others didn't. That took some effort.

All he did was compile patches from around the devscene. Anyone who hung around the ReiNX discord could've done this, but people wanted to wait for things to be more fleshed out.

cyndor · Dec 26, 2018

Esjay131 said:
All he did was compile patches from around the devscene. Anyone who hung around the ReiNX discord could've done this, but people wanted to wait for things to be more fleshed out.

The ES patches were his, as for any other things included that might have not been anywhere else I honestly don't remember.
Anyways, I don't know what to tell you buddy, you obviously dislike RajNX but I don't care enough to continue this.

Hacking [No longer maintained] RajNX - starter pack for Nintendo Switch

Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum