Hacking SWITCH NOOB PARADISE - Ask questions here

[thekarter104]

Just Nintendo updated from 4.1.0 to 6.0.0.
It's still incredible how installing updates in just BLAZING fast, faster than even the PS4 and Wii U. Just unhuman, atleast compared from what I used to.
Can any hacker explain?

Also what do the controller updates do?

 

[Draxzelex]

Switch has been offline and flight mode long before fw 6 but when ever launching a game it says a software update is available and it will download now. Any way to get rid of this message?

If you can still play the game despite the update prompt, that can only be removed with a system update. Its not like it prevents you from launching the game.

Just Nintendo updated from 4.1.0 to 6.0.0.
It's still incredible how installing updates in just BLAZING fast, faster than even the PS4 and Wii U. Just unhuman, atleast compared from what I used to.
Can any hacker explain?

Also what do the controller updates do?

I'm pretty sure you don't need a hacker to explain this as the specs for the Switch are public. And controller updates do what it says on the box; updates the controllers. They can range from adding stability to having anti-hacker features such as making the Joy-Con not be docked if you enter RCM by bridging pins 9 and 10.

 

[anothertemper]

I tried to load ReiNX, and the system froze on the splash screen. I tried to load CFW through hekate, and when I loaded the album I just had a black screen. I'm on 1.0.0 and trying to update via ChoiDujourNX, but I can't get the homebrew menu to even load. I've tried nx-hbloader with debug svcs enabled as well, and I just keep getting black screens. What am I doing wrong?

 

[Draxzelex]

I tried to load ReiNX, and the system froze on the splash screen. I tried to load CFW through hekate, and when I loaded the album I just had a black screen. I'm on 1.0.0 and trying to update via ChoiDujourNX, but I can't get the homebrew menu to even load. I've tried nx-hbloader with debug svcs enabled as well, and I just keep getting black screens. What am I doing wrong?

For firmware 1.0, it needs debugmode=1 set to a launch profile. If you don't know how to add this, I suggest downloading and using RajNX to load ChoiDujourNX on firmware 1.0 as it has launch profiles with debugmode enabled.

 

[anothertemper]

For firmware 1.0, it needs debugmode=1 set to a launch profile. If you don't know how to add this, I suggest downloading and using RajNX to load ChoiDujourNX on firmware 1.0 as it has launch profiles with debugmode enabled.

Thank you! That was so much easier. Any reason not to use RajNX as a daily CFW?

 

[Draxzelex]

Thank you! That was so much easier. Any reason not to use RajNX as a daily CFW?

RajNX initially started as unnecessary drama but the creator does intend to continue providing support for this CFW for now. I also do not consider it a true CFW since in reality, its just a combination of Hekate and Atmosphere however that should hold no bearing on whether or not you use it.

 

[Gamemaster1379]

So as tonight, I have finally gotten my Switch to boot into RCM mode and am backing up my rawnand.bin now to keep for safe keeping.

I know a little bit here and there, but am not comfortable with the scene. My biggest goal is to, for now, preserve my ability to have Homebrew, but try to stay as clean as possible using OTA official updates.

Say, for instance, I want to update for when Smash Bros comes out. No homebrew, no nothing. Is there a way for me to do this, but have the ability to roll back later if I ever decide to? I know there's a little something about updating OFWs without burning fuses. Is that something that's doable without a serious risk of ban (I know tampering == risk of ban no matter what), but is there any reasonable practices that aren't believed to do so?


Also, as a secondary note, what all can I really do now for fun? I know some sort of backup loaders and homebrew exist. What are the states I can leave the system in to easily access/inject homebrew and the like? (Like, do I have to have the switch stay on after doing an injection and it'll lose it if I don't sort of thing)

 

[anothertemper]

RajNX initially started as unnecessary drama but the creator does intend to continue providing support for this CFW for now. I also do not consider it a true CFW since in reality, its just a combination of Hekate and Atmosphere however that should hold no bearing on whether or not you use it.

Is ReiNX the go-to for most people now?

 

[Draxzelex]

So as tonight, I have finally gotten my Switch to boot into RCM mode and am backing up my rawnand.bin now to keep for safe keeping.

I know a little bit here and there, but am not comfortable with the scene. My biggest goal is to, for now, preserve my ability to have Homebrew, but try to stay as clean as possible using OTA official updates.

Say, for instance, I want to update for when Smash Bros comes out. No homebrew, no nothing. Is there a way for me to do this, but have the ability to roll back later if I ever decide to? I know there's a little something about updating OFWs without burning fuses. Is that something that's doable without a serious risk of ban (I know tampering == risk of ban no matter what), but is there any reasonable practices that aren't believed to do so?


Also, as a secondary note, what all can I really do now for fun? I know some sort of backup loaders and homebrew exist. What are the states I can leave the system in to easily access/inject homebrew and the like? (Like, do I have to have the switch stay on after doing an injection and it'll lose it if I don't sort of thing)

You're going to have stay 100% offline with all of your hacks then restore a clean hack-free NAND before going online to minimize your chances of being banned. You will also need to make new subsequent NAND backups everytime you go online since your NAND will be different than the original backup. I included a minor guide on the proper way to avoid bans here.

Also at this point, we can do pretty much everything apart from have access to a true untethered coldboot exploit as well as an EmuNAND that runs from the SD card.

Is ReiNX the go-to for most people now?

Well ReiNX is officially out unlike ReiNX so more people are able to associate with it over Atmosphere which hasn't been officially released yet. However there are plenty of people who have been using tomGER's SD files which were one of the first distributions of Atmosphere as a CFW.

 

[Gamemaster1379]

You're going to have stay 100% offline with all of your hacks then restore a clean hack-free NAND before going online to minimize your chances of being banned. You will also need to make new subsequent NAND backups everytime you go online since your NAND will be different than the original backup. I included a minor guide on the proper way to avoid bans here.

Also at this point, we can do pretty much everything apart from have access to a true untethered coldboot exploit as well as an EmuNAND that runs from the SD card.
Well ReiNX is officially out unlike ReiNX so more people are able to associate with it over Atmosphere which hasn't been officially released yet. However there are plenty of people who have been using tomGER's SD files which were one of the first distributions of Atmosphere as a CFW.

Your guide is good, thank you.

Am I to understand there is no "clean" way to update the NAND without burning fuses?

 

[Draxzelex]

Your guide is good, thank you.

Am I to understand there is no "clean" way to update the NAND without burning fuses?

The cleanest way to update the NAND would be to burn fuses. If you want to avoid burning fuses but still want to update as clean as possible, then you can follow this tutorial.

 

[Gamemaster1379]

The cleanest way to update the NAND would be to burn fuses. If you want to avoid burning fuses but still want to update as clean as possible, then you can follow this tutorial.

Very interesting, so the first launch of a new firmware is when the fuses are burned.

So basically, you're skipping the "initial reboot" by jumping to RCM mode?

 

[Adran_Marit]

Very interesting, so the first launch of a new firmware is when the fuses are burned.

So basically, you're skipping the "initial reboot" by jumping to RCM mode?

The fuses are burnt when the nintendo bootloader runs. Using RCM and hekate or a cfw bypass this bootloader allowing you to update (and downgrade if you wish) without burning fuses or causing the console to panic

 

[Gamemaster1379]

The fuses are burnt when the nintendo bootloader runs. Using RCM and hekate or a cfw bypass this bootloader allowing you to update (and downgrade if you wish) without burning fuses or causing the console to panic

Oh, I see. So if I upgrade the OFW and bypass fuse burning with RCM/hekate--I'll have to do that for EVERY boot in that OFW if I don't use those fuses burned?

If that's the case, there is no way to permanently boot from a CFW from a cold boot, right? A CFW from cold boot must come through RCM, correct?

 

[Adran_Marit]

Oh, I see. So if I upgrade the OFW and bypass fuse burning with RCM/hekate--I'll have to do that for EVERY boot in that OFW if I don't use those fuses burned?

If that's the case, there is no way to permanently boot from a CFW from a cold boot, right? A CFW from cold boot must come through RCM, correct?

Yep, updating without burning fuses, AutoRCM is highly suggested as that way you can't accidentally burn your fuses as it will always re-enter RCM mode. the downside is you will need a way to always launch the payload file

 

[Gamemaster1379]

Yep, updating without burning fuses, AutoRCM is highly suggested as that way you can't accidentally burn your fuses as it will always re-enter RCM mode. the downside is you will need a way to always launch the payload file

So what is AutoRCM exactly? I think I read something about SOME tech that "corrupts" a bootloader section into forcing into RCM?

So if I understand, you corrupt into a forced RCM, but cold boots would REQUIRE an injector or the console is a brick until you have access to that?

I don't expect to be terribly portable with my unit, so my PC should generally be accessible. That'd be fine by me.

Is AutoRCM risky to install? Assuming it does "corrupt", is there any forseeable long term damage?

EDIT: Lastly, is AutoRCM easy to revert if I decide I don't want it any longer?

 

[Adran_Marit]

So what is AutoRCM exactly? I think I read something about SOME tech that "corrupts" a bootloader section into forcing into RCM?

So if I understand, you corrupt into a forced RCM, but cold boots would REQUIRE an injector or the console is a brick until you have access to that?

I don't expect to be terribly portable with my unit, so my PC should generally be accessible. That'd be fine by me.

Is AutoRCM risky to install? Assuming it does "corrupt", is there any forseeable long term damage?

Pretty much. AutoRCM corrupts a section of your nands boot0 partition to enable RCM by default every reboot (no jig + button pressing required) but still requires a .bin file and without it you're stuck there until you do send one. (This can be restored to default by uninstalling AutoRCM)

There is a option to install it with hekate, reinx toolkit, choidujourNX and sxos (if you use that). The only issue I'm aware of with AutoRCM is battery drain if you you don't shut the console down properly. Sleep mode is fine. @Draxzelex posted more on this a few pages ago.

 

[Gamemaster1379]

Pretty much. AutoRCM corrupts a section of your nands boot0 partition to enable RCM by default every reboot (no jig + button pressing required) but still requires a .bin file and without it you're stuck there until you do send one. (This can be restored to default by uninstalling AutoRCM)

There is a option to install it with hekate, reinx toolkit, choidujourNX and sxos (if you use that). The only issue I'm aware of with AutoRCM is battery drain if you you don't shut the console down properly. Sleep mode is fine. @Draxzelex posted more on this a few pages ago.

Pretty much. AutoRCM corrupts a section of your nands boot0 partition to enable RCM by default every reboot (no jig + button pressing required) but still requires a .bin file and without it you're stuck there until you do send one. (This can be restored to default by uninstalling AutoRCM)

There is a option to install it with hekate, reinx toolkit, choidujourNX and sxos (if you use that). The only issue I'm aware of with AutoRCM is battery drain if you you don't shut the console down properly. Sleep mode is fine. @Draxzelex posted more on this a few pages ago.

I see. AutoRCM seems like something I'd want then.

So if I understand, the whole charging issue is it'll either charge slow or not at all if you power off using the Switch's OFW power off. In order to completely power off, you would need to "shut down" the system with OFW, restart it (in autoRCM mode), inject your payload, and use the Hekate power down to ACTUALLY power it down?

 

[Adran_Marit]

I see. AutoRCM seems like something I'd want then.

So if I understand, the whole charging issue is it'll either charge slow or not at all if you power off using the Switch's OFW power off. In order to completely power off, you would need to "shut down" the system with OFW, restart it (in autoRCM mode), inject your payload, and use the Hekate power down to ACTUALLY power it down?

Yea it's super slow to charge in RCM, again @Draxzelex posted more on this a few pages ago

 

[Gamemaster1379]

Yea it's super slow to charge in RCM, again @Draxzelex posted more on this a few pages ago

Gotcha. I'll look into it. Although it seems I just avoid RCM charging if at all possible. Am I understanding what I have to do to actually turn it off?


Also, regarding charging, is that only while in sleep? Or is that even while I"m playing the console (meaning that if I autoRCM, I can only play for the life of the battery, then must turn it off if I want to stop and recharge?)