Hacking SWITCH NOOB PARADISE - Ask questions here

[Notshane]

Well, I'm primarily going to 4.0.1 so I can use GameCube controllers. One of the primary reasons I'm going from Wii U homebrew to Switch is cause it has more convenient controller options, most notably being able to use all four ports of said GameCube Controller Adapter for four player games once I can get N64 up and running. And I hear all firmware below 4.1.0 is the safest.

You didn't update so you could use the Deja vu exploit, right?

Don't know what that is.

 

[TPMJB]

Well, I'm primarily going to 4.0.1 so I can use GameCube controllers. One of the primary reasons I'm going from Wii U homebrew to Switch is cause it has more convenient controller options, most notably being able to use all four ports of said GameCube Controller Adapter for four player games once I can get N64 up and running. And I hear all firmware below 4.1.0 is the safest.



Don't know what that is.

Oh, I didn't know Wii U homebrew actually took off. I remember having to load some exploit from a browser hack. I was able to do it and didn't even bother using it after that.

The Deja Vu exploit is some exploit that was discovered which allows us to not have to use that stupid TegraRCMGui every time we want to load custom firmware. Nobody who discovered it is willing to release it.

 

[Notshane]

Oh, I didn't know Wii U homebrew actually took off. I remember having to load some exploit from a browser hack. I was able to do it and didn't even bother using it after that.

Oh yeah, it's really great. Haxchi is a good way to boot into it and from there, you can customize the menus real nicely and don't ever have to use the browser exploit again. I played hours of Mario Party on it and such. Only real shame was the lack of USB controller support, which is primarily why I'm going to Switch. It actually supports the GameCube Adapter on everything and isn't limited to a single game.

The Deja Vu exploit is some exploit that was discovered which allows us to not have to use that stupid TegraRCMGui every time we want to load custom firmware. Nobody who discovered it is willing to release it.

I'm trying to figure out how to just install the Homebrew Menu onto the dashboard using an NSP, but I don't know how to make one. I only have "hbmenu.nro" but I have the "NRO to NSP" converter, with no videos explaining how to use it. If I can figure it out, I'll never have to use that stupid payload method ever again. And right now, I'm currently updating to 4.0.1 with the assumption that my separated backup of 2.1.0 will be re-loadable. So, at least I will have the knowledge of being the first person to test and see if it's still loadable if I ever go back. Though, I will be in trouble if I get bricked for trying to experiment with this.

 

[Xana]

If I can figure it out, I'll never have to use that stupid payload method ever again.

Yes you will. It won't be loadable outside of CFW (and installing it as an NSP will get you banned if you go online in OFW), so you'll still have to inject a payload every time you turn on your switch.

And right now, I'm currently updating to 4.0.1 with the assumption that my separated backup of 2.1.0 will be re-loadable. So, at least I will have the knowledge of being the first person to test and see if it's still loadable if I ever go back. Though, I will be in trouble if I get bricked for trying to experiment with this.

The 2.1.0 backup will not be reloadable unless you use AutoRCM, as you'll burn fuses when you update. If you do re-load it after burning fuses, it'll only be reloadable with CFW, and you'll still have to push a payload every time.

 

[TPMJB]

Oh yeah, it's really great. Haxchi is a good way to boot into it and from there, you can customize the menus real nicely and don't ever have to use the browser exploit again. I played hours of Mario Party on it and such. Only real shame was the lack of USB controller support, which is primarily why I'm going to Switch. It actually supports the GameCube Adapter on everything and isn't limited to a single game.



I'm trying to figure out how to just install the Homebrew Menu onto the dashboard using an NSP, but I don't know how to make one. I only have "hbmenu.nro" but I have the "NRO to NSP" converter, with no videos explaining how to use it. If I can figure it out, I'll never have to use that stupid payload method ever again. And right now, I'm currently updating to 4.0.1 with the assumption that my separated backup of 2.1.0 will be re-loadable. So, at least I will have the knowledge of being the first person to test and see if it's still loadable if I ever go back. Though, I will be in trouble if I get bricked for trying to experiment with this.

I would follow this guide:

https://switchguide.xyz/

But to get a truly working setup, instead of following their "setting up your SD card" portion, I just used Kosmos. It's fairly easy to use and we have a thread here:

https://gbatemp.net/threads/kosmos-a-hekate-cfw-package.506280/

 

[Notshane]

Yes you will. It won't be loadable outside of CFW (and installing it as an NSP will get you banned if you go online in OFW), so you'll still have to inject a payload every time you turn on your switch.

Oh shoot. That's a bummer. Guess the Wii U is still the most convenient Nintendo console to hack at this point in time since Haxchi is always loadable. Hopefully, I can at least find the "hbmenu.nsp" anyway so I don't have to worry about the Home button accidentally exiting the game if I want to keep it open. Don't know what "OFW" is, but I assume it correlates with firmware versions 6.0.0 and above. I'm only going to update to 4.0.1 for controller support.

The 2.1.0 backup will not be reloadable unless you use AutoRCM, as you'll burn fuses when you update. If you do re-load it after burning fuses, it'll only be reloadable with CFW, and you'll still have to push a payload every time.

I was planning on using ChoiDujourNXv101, actually. I hear that method will keep the fuse safe.

I would follow this guide:

https://switchguide.xyz/

But to get a truly working setup, instead of following their "setting up your SD card" portion, I just used Kosmos. It's fairly easy to use and we have a thread here:

https://gbatemp.net/threads/kosmos-a-hekate-cfw-package.506280/

Alright, hopefully I can figure it out. I already put one into my microSD called "KosmosV1171" is that the same one as on that thread?

 

[TPMJB]

Oh shoot. That's a bummer. Guess the Wii U is still the most convenient Nintendo console to hack at this point in time since Haxchi is always loadable. Hopefully, I can at least find the "hbmenu.nsp" anyway so I don't have to worry about the Home button accidentally exiting the game if I want to keep it open. Don't know what "OFW" is, but I assume it correlates with firmware versions 6.0.0 and above. I'm only going to update to 4.0.1 for controller support.



I was planning on using ChoiDujourNXv101, actually. I hear that method will keep the fuse safe.



Alright, hopefully I can figure it out. I already put one into my microSD called "KosmosV1171" is that the same one as on that thread?

ChoiDuJour works well for using a higher firmware version. I'm using 6.2 after being on 4.0.

I had a hell of a time installing XCI files until I used Kosmos. With Kosmos I can finally install my switch carts to my SD card so I don't have to rummage through all my cards when I want to play a different game.

 

[Xana]

Don't know what "OFW" is

OFW = Official FirmWare, aka not CFW (what happens if you boot without a payload)

I was planning on using ChoiDujourNXv101, actually. I hear that method will keep the fuse safe.

It does, but only because it installs AutoRCM, which means you'll need to inject a payload every time you turn on (or turn off) your switch.

I recommend following the guide at guide.sdsetup.com . Even if you decide not to follow it, reading through it will at least give you a good overview of what everything is, what your options are, how it all comes together, etc.

 

[Notshane]

It does, but only because it installs AutoRCM, which means you'll need to inject a payload every time you turn on (or turn off) your switch.

I recommend following the guide at guide.sdsetup.com . Even if you decide not to follow it, reading through it will at least give you a good overview of what everything is, what your options are, how it all comes together, etc.

Shoot. I should have just bought a tablet with 4.0.1 on it naturally. Now I regret having 2.1.0 since I was hoping I could go up to 4.0.1 naturally. Since the primary reason I started Switch homebrew was so I could use GameCube controllers with the games, I will have to find a 4.0.1 tablet now. Seems to be the safest option I have.

Yeah, looks like I will need to, but by this point, I may have to just find a 4.0.1 tablet, assuming it still has the hardware exploit. Or, well, if there's no particular reason to stay on 2.1.0, couldn't I just go to 4.0.1 on my current tablet and simply burn the fuse? Or, would certain emulators and such be worsened by it?

 

[Expendablepanda]

OFW = Official FirmWare, aka not CFW (what happens if you boot without a payload)



It does, but only because it installs AutoRCM, which means you'll need to inject a payload every time you turn on (or turn off) your switch.

I recommend following the guide at . Even if you decide not to follow it, reading through it will at least give you a good overview of what everything is, what your options are, how it all comes together, etc.

Thanks for this post, that guide has made me want to mod my switch and that looks almost fool proof.

My only query with backups on CFW, because you have to load it every time you turn the switch on does progress save? Do the loaded nsps stay on or do they need to be installed each time too?

Sorry for the questions.

 

[Notshane]

Do the loaded nsps stay on or do they need to be installed each time too?

Well, based on their phrasing of what they told me, it's possible for them to stay on OFW, but opening them warrants a high chance for ban.

 

[Expendablepanda]

Well, based on their phrasing of what they told me, it's possible for them to stay on OFW, but opening them warrants a high chance for ban.

Ah right, makes sense!

 

[Notshane]

Which sucks, given the Wii and Wii U never had trouble with Homebrew Channel and Haxchi, respectively.

 

[Xana]

Yeah, looks like I will need to, but by this point, I may have to just find a 4.0.1 tablet, assuming it still has the hardware exploit. Or, well, if there's no particular reason to stay on 2.1.0, couldn't I just go to 4.0.1 on my current tablet and simply burn the fuse? Or, would certain emulators and such be worsened by it?

The reason people recommend staying on the lowest firmware possible (or keeping the ability to downgrade to such), is because the lower your firmware, the fewer potential exploits will have been patched. For example: you're more likely to have access to a coldboot exploit (like wiiu's haxchi) on lower firmwares than higher ones. Of particular note is that many necessary parts of the "deja-vu" toolchain were patched after 4.1, and if a coldboot exploit is ever found, this toolchain is your most likely bet at getting coldboot CFW.

My only query with backups on CFW, because you have to load it every time you turn the switch on does progress save? Do the loaded nsps stay on or do they need to be installed each time too?

Once you've installed backups, they're installed, whether you're in OFW or in CFW (or which CFW you use). Just be aware that, if you install backups, allowing your switch to connect to Nintendo's servers runs a high risk of a ban - not just launching them (which will error or crash on OFW), but just having them installed - and that's why the guides recommend taking a 'clean nand backup' immediately after launching a payload the first time, BEFORE doing anything CFW-related, homebrew or otherwise, and then blocking Nintendo's servers with 90DNS or removing wifi connections.

 

[Expendablepanda]

The reason people recommend staying on the lowest firmware possible (or keeping the ability to downgrade to such), is because the lower your firmware, the fewer potential exploits will have been patched. For example: you're more likely to have access to a coldboot exploit (like wiiu's haxchi) on lower firmwares than higher ones. Of particular note is that many necessary parts of the "deja-vu" toolchain were patched after 4.1, and if a coldboot exploit is ever found, this toolchain is your most likely bet at getting coldboot CFW.



Once you've installed backups, they're installed, whether you're in OFW or in CFW (or which CFW you use). Just be aware that, if you install backups, allowing your switch to connect to Nintendo's servers runs a high risk of a ban - not just launching them (which will error or crash on OFW), but just having them installed - and that's why the guides recommend taking a 'clean nand backup' immediately after launching a payload the first time, BEFORE doing anything CFW-related, homebrew or otherwise, and then blocking Nintendo's servers with 90DNS or removing wifi connections.

Amazing thank you. Will make sure to back up as as advised.

 

[TWilliamson]

I backed up my 2.1.0, but they are all separated:

In the videos I saw, it's normally just one "rawnand.bin" so I am confused. Should I just accept this result or will it be screwed up if I ever revert it.

Whether you plan to change to exFAT in the future or not, your NAND is in 15 parts because you used FAT32. Therefore if you want to use this to restore, then use joiner scripts to merge them into one large file.

 

[Notshane]

The reason people recommend staying on the lowest firmware possible (or keeping the ability to downgrade to such), is because the lower your firmware, the fewer potential exploits will have been patched. For example: you're more likely to have access to a coldboot exploit (like wiiu's haxchi) on lower firmwares than higher ones. Of particular note is that many necessary parts of the "deja-vu" toolchain were patched after 4.1, and if a coldboot exploit is ever found, this toolchain is your most likely bet at getting coldboot CFW.

Shoot. But, I thought early tablets always had the hardware exploit, so wouldn't I be able to always load Hekate, even on, say, 5.1? Which I am now...considering over 4.0.1 because I also want to mod Super Smash Bros. Ultimate.

 

[ZanderX420]

I will ask again since my first post never got answered. Is there any plans for a game cube and ps2 emulator for the switch? or r there already ones out to download? P.s will they be added to the hb app store.

 

[jackirate]

EmuNAND has a few advantages. For one thing, it can let you enjoy the benefits of being on a higher firmware without updating SysNAND or dealing with AutoRCM. Another advantage is that EmuNAND can act as a sort of "ban prevention" tool. If you do all CFW and homebrew in EmuNAND but keep all legitimate online play in SysNAND, your chances of being banned reduce dramatically since SysNAND and EmuNAND don't share any information whatsoever. The last advantage of EmuNAND is that if EmuNAND gets bricked, it won't brick your SysNAND. The cons of course is that you will need the required space to install EmuNAND whether it be the internal memory or on the SD card. And of course, the only way to update EmuNAND is with ChoiDujourNX because updating online will flag the whole console for a ban, both SysNAND and EmuNAND.

Hi guys,

Ive been reading as much as i can to prepare myself to install my SXPRO but still have a few questions.

So i know i need to create a back up of my clean NAND before installing the SXPRO cfw, probably a silly question but how is this done?

Also i still need some clarification on updating the system software once CFW is installed. Am i right in saying that once i have created emuNAND i can use ChoiDujourNX to update sysnand from 5.1.0 to 6.1?

is 6.1 the most desirable to to upgrad sysnand to?

Lastly, once i have updated my sysnand to 6.1 what version will emuNAN be on?

Thanks in advance, really appreciate the support this site offers!

 

[Xana]

Shoot. But, I thought early tablets always had the hardware exploit, so wouldn't I be able to always load Hekate, even on, say, 5.1? Which I am now...considering over 4.0.1 because I also want to mod Super Smash Bros. Ultimate.

You seem to not want to use the hardware exploit, given that you want to avoid injecting payloads. Yes, the hardware exploit is firmware-independent and unpatchable, but it will also always require a payload injection. I was suggesting that, if you want to maintain the highest chance of a haxchi-like coldboot exploit, maintaining the ability to downgrade is desirable.