Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,097,521
  • Replies Replies 47,953
  • Likes Likes 66
That makes sense. So if I was crackheaded I could do whatever, restore, Play a week or so online cleanly, then do another dump, stay offline, cfw away, if wanting to back, repeat by restore nand, stay clean, etc?
I wanted to ensure I had an unpatched console for myself for future shenanigans, but potentially clean as my kids loved animal crossing online.
I had a 3dsxl and honestly had more fun modding it than playing any games. So I dont want to get banned in the event I dont even like it and kids cant go online.
I think I'll get at least 1 more switch and keep that offline.
Also from what I read the fuses would burn on an update, so would I still be able to restore and older nand?
Yes to your first question.

As to your second question, there are ways of updating without burning fuses. The easiest and most recommended is with the homebrew application ChoiDujourNX. It enables AutoRCM which prevents the console's bootloader from burning the fuses (AutoRCM boots the console automatically into RCM meaning you must send a payload to boot it and this payload is usually a bootloader that bypasses the fuse check). Another way is by installing the system update while using Atmosphere and having AutoRCM enabled. System updates normally remove AutoRCM however the latest version of Atmosphere now prevents this from happening. A faster but trickier method is rebooting the console into RCM after it finishes installing the system update.

Either way, right now there is no way of updating to the latest firmware and preserving your fuses because no CFW supports 7.0 so just think over your options until CFW supports the latest firmware.
 
Yes to your first question.

As to your second question, there are ways of updating without burning fuses. The easiest and most recommended is with the homebrew application ChoiDujourNX. It enables AutoRCM which prevents the console's bootloader from burning the fuses (AutoRCM boots the console automatically into RCM meaning you must send a payload to boot it and this payload is usually a bootloader that bypasses the fuse check). Another way is by installing the system update while using Atmosphere and having AutoRCM enabled. System updates normally remove AutoRCM however the latest version of Atmosphere now prevents this from happening. A faster but trickier method is rebooting the console into RCM after it finishes installing the system update.

Either way, right now there is no way of updating to the latest firmware and preserving your fuses because no CFW supports 7.0 so just think over your options until CFW supports the latest firmware.
Thanks. Lots of info and not all of this was covered in the guide I saw. So in meantime I guess itll be fine to play Mario odyssey which I bought for now.
I dont even know what version I'm on currently. Maybe I'll try cfw and retroarch.
Edit: I'm on 4.1. So I'll stick to this for now and follow the news. Once cfw is good for 7.0, then I should be able to ChoiDujourNX to 7.0, keep my fuses, correct?
Then if I wanted to roll back to this 4.1 stock nand it should be fine since fuses never touched?
Or likewise ChoiDujourNX allows downgrades as well?
 
Last edited by TheGlow,
hey what directory on the SD card are the contents for saved games stored? I dont want to lose my saves again so im going to back them up like once or at leats before I update anything in the future that may cause a restore of nand somehow etc.
 
This isn't something I'd considered, but makes sense if I'm understanding it correctly.

Playing online on the first "clean" NAND would make some changes to it, so restoring the same original NAND backup again would raise red flags as it would restore the NAND to the state it was before you went online and the NAND was changed by going online.

So after every period online with the "clean" NAND and before you go back to CFW, you should make a new backup to store the NAND at that point (with whatever changes were made by going online with it) ready to restore the next time you want to go back online.

Sort of like a rolling NAND backup system after every time you're done playing online and before you go back to CFW.

Am I understanding that right?
Essentially yes.
hey what directory on the SD card are the contents for saved games stored? I dont want to lose my saves again so im going to back them up like once or at leats before I update anything in the future that may cause a restore of nand somehow etc.
Saves are on the NAND as explained on Nintendo's own website.
 
  • Like
Reactions: DoobyDude
hmm well it sounds like i need to learn how to use checkpoint adn cheats

do you have a link to anything showing how to use cheats on games , i remember having game genie when i was younger that was a lot of fun
 
Edit: I'm on 4.1. So I'll stick to this for now and follow the news. Once cfw is good for 7.0, then I should be able to ChoiDujourNX to 7.0, keep my fuses, correct?
Then if I wanted to roll back to this 4.1 stock nand it should be fine since fuses never touched?
Or likewise ChoiDujourNX allows downgrades as well?
You can use ChoiDujourNX to update to 6.2 right now since CFW supports that and then update again to 7.0 once CFW supports that firmware. A lot of the newer games and updates won't run on 4.1.
hmm well it sounds like i need to learn how to use checkpoint adn cheats

do you have a link to anything showing how to use cheats on games , i remember having game genie when i was younger that was a lot of fun
If you have SX OS, you can just use their own cheat engine. Otherwise, there is sys-net cheat. It is a sysmodule for usage with ReiNX or Atmosphere and there is a tutorial on how to use it.
 
Would like to ask question about ban. Got my switch recently and try if is hackable. Turn out was from the patched ones. Waiting for cfw support if any for couple of years is no go. So decided to went legal and entirely digital. But to test it i already have enter rcm and send the payload (yeah no luck). My question is will i risk ban and basicly get a very nice brick?
Cool, after reading more i think maybe it's worth waiting and have question. For patched units the hacking is via deja vu which is browserhax > nvhax > gmmuhax > nspwn > [undisclosed] > warmboothax? The browserhax > nvhax have been released recently, allow userland and homebrew? The warmboothax part is the same as in current hack to enter in atmosphere? The gmmuhax > nspwn > [undisclosed] is unreleased yet due to still being present in unreleased new switchs? So the whole chain will allow running atmosphere on the patched swiches?
edit: on 4.1 firm (my firm) as on higher firm some of the chain have been pached and are needed additional hax?
 
Last edited by fingolin,
I am experiencing a very odd problem that someone may be able to shed some light on.

I'm using a Mac with Parallels running simultaneously. My normal route to NSP installation is download NSP file to Mac, transfer to external HDD plugged into Windows (Parallels) and then copy to SD. That way I have a backup on the external HDD.

Problem is that doing it this way doesn't work - the NSP will never install on the Switch and it crashes every single time forcing me to reboot the system. It took me a while to figure this out. I initially thought the SD card was corrupted, but it turns out that that isn't the issue. If I download the NSP to Mac then transfer directly to the SD (again, with the SD mounted in Windows) they install flawlessly every time.

So the problem appears to be the transfer to HDD. If I remove this step, no problem. Does anyone have any idea why this might be? Because if I'm unable to use the external drive I can't actually keep too many large files on the Mac as it takes up too much disk space. I already reformatted the HDD partition with no success.

The HDD somehow seems to break the NSP when it's installed in and then back out. The HDD is split into two partitions. The HDD partition I'm using for NSPs is formatted to ExFat and is 350 GB approx.

Does anyone have any idea why this would happen and if there's a resolution to allow me to store usable NSPs on the HDD?

Following up on this, I've tested fairly extensively since adding this to page 507. I followed the archive bit removal guide to the letter and also used Hakate's boot menu archive bit remover. The issue remains: any NSP transferred to my HDD and to my SD is rendered useless by the process and causes Atmosphere error 2168-0002 on installation attempt. If I download the NSP and go straight to SD it's fine and installs first time with one exception (!): For some reason any patches or updates will not install no matter what. I have no idea why, but I've failed to successfully install every NSP format update or patch for any installed game. Furthermore, once the system has crashed and rebooted, no other NSP (update or full game) will work and I need to go into the SD via Windows and delete them, then add them back again.

Update patches are strange because on first run they seem to begin installing with the green goldleaf bar on the way, then they freeze and crash. Reboot and try again and they are then totally nuked and fail to manage a pixel on the progress bar before the system crashes.

Is this an HDD error, an SD incompatibility issue (I'm using a 64GB Sandisk) or both?

Thanks in advance!
 
Is anyone having troubles with sleep mode using latest Atmosphere (Kosmos)? 2 out of 3 times the switch just freezes when entering sleep mode, it's very very annoying.

I booted ReiNX and the problem is not happening there.

I don't know what's the issue since most people don't complain about it, maybe a module? I'm blaming sys-netcheat since they fixed some sleep mode related issues on the latest version, and Kosmos includes it.
 
Last edited by natkoden,
Is anyone having troubles with sleep mode using latest Atmosphere (Kosmos)? 2 out of 3 times the switch just freezes when entering sleep mode, it's very very annoying.

I booted ReiNX and the problem is not happening there.

I don't what's the issue since most people don't complain about it, maybe a module? I'm blaming sys-netcheat since they fixed some sleep mode related issues on the latest version, and Kosmos includes it.

if you want to go one by one, you can start by using clean microsd and put kosmos there (or just rename your atmosphere folder to atmosphere_old and extract a fresh one from the zip)
 
is there a guide anywhere to easily move game saves and installed games from one switch to another?

I currently have 2 switches, one is running 6.2 and SX OS emunand and one is clean with 4.0.1 installed, no CFW yet

I have NAND backups of both

Currently have a 400gb MicroSD with 10 games installed and BOTW saved on the 6.2 switch

I would like to move everything to the 4.0.1 switch (after updating to 6.2 and installing EMUNAND and a new SX OS license)

Any tips on where to start?

thanks in advance
 
is there a guide anywhere to easily move game saves and installed games from one switch to another?

I currently have 2 switches, one is running 6.2 and SX OS emunand and one is clean with 4.0.1 installed, no CFW yet

I have NAND backups of both

Currently have a 400gb MicroSD with 10 games installed and BOTW saved on the 6.2 switch

I would like to move everything to the 4.0.1 switch (after updating to 6.2 and installing EMUNAND and a new SX OS license)

Any tips on where to start?

thanks in advance
Use Checkpoint to backup decrypted versions of your saves, and use Checkpoint to restore them on the other Switch.
 
thanks, any way to move the games from the MicroSD card / use the same MicroSD card?
No. You will need to reinstall the NSP files on the second Switch.

Edit: If you're using XCI files, you can still use those.
 
Last edited by Lacius,
No. You will need to reinstall the NSP files on the second Switch.

Edit: If you're using XCI files, you can still use those.
thanks for your help - I have installed XCI files using SX OS on EmuNAND - presume I will therefore need to reformat the SD card and recreate EmuNAND and install the new SX OS license on the new switch?
 
thanks for your help - I have installed XCI files using SX OS on EmuNAND - presume I will therefore need to reformat the SD card and recreate EmuNAND and install the new SX OS license on the new switch?
I don't know how SX OS works since I don't use it on principle.
 
Is there guide for new ppl who have old switch on low frimwhere?
How add exfat support\backup nand\update to last cfw...
 
Last edited by k7ra,
Is there guide for new ppl who have old switch on low frimwhere?
How backup nand\update to last cfw...
Backup NAND with hekate, update with Choidujournx if you want to be able to downgrade later on. Just search for hekate and Choidujournx.
 
Backup NAND with hekate, update with Choidujournx if you want to be able to downgrade later on. Just search for hekate and Choidujournx.
Thanks, but I ask it bcs I don't know how...
I need FAQs or similar thing with step by step instruction.
There few cfw, what is better and what to choose =\
 
Last edited by k7ra,

Site & Scene News

Popular threads in this forum