Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,107,232
  • Replies Replies 47,954
  • Likes Likes 66
Yup.
Yes. My memory is slipping but in case I haven't told you already, if the SD card is larger than 32 GB, use a third-party program such as GUIFormat.

Will do. Also, you mentioned USB install as a highly recommended and faster method. Did you mean that for game backups? I tried searching the tutorials forum for a guide, but couldn't find one, would you mind linking it for me?
 
Will do. Also, you mentioned USB install as a highly recommended and faster method. Did you mean that for game backups? I tried searching the tutorials forum for a guide, but couldn't find one, would you mind linking it for me?

get tinfoil (here) and then use Aluminium Foil (here) then just follow the on screen instructions
 
  • Like
Reactions: CapCaveman
So, I can dump the NAND to an exFAT formatted card, but then I'll have to use a FAT32 one anyway to load a CFW and update with ChoiNX. Only after applying the exFAT patch, I'll be able to use exFAT cards.

While my sysNAND is being dumped (smooth sailing, so far), I was thinking about what to do after I create and update the emuNAND, since I'd like to later use exFAT (I've been warned about the risk of corruption, but the practicality of exFAT is more enticing).

@Draxzelex has already pointed out GUIFormat for FAT32. But what should I do with the files in the microSD before I format it back to exFAT? Can I just backup, then copy and paste them to the root of the formatted card? My main concern is the EmuNAND that I will create using SX OS (I won't have any games or save files in it).
 
While my sysNAND is being dumped (smooth sailing, so far), I was thinking about what to do after I create and update the emuNAND, since I'd like to later use exFAT (I've been warned about the risk of corruption, but the practicality of exFAT is more enticing).

@Draxzelex has already pointed out GUIFormat for FAT32. But what should I do with the files in the microSD before I format it back to exFAT? Can I just backup, then copy and paste them to the root of the formatted card? My main concern is the EmuNAND that I will create using SX OS (I won't have any games or save files in it).
Yes you can just backup whatever files are on the SD card, format it, then put them back.
 
I was just looking at what Goldleaf does as it seems to be the replacement for Tinfoil but either one in USB install seems to modify the Switch by replacing a library on it? Is that right? Seems like it would be pretty easy for Nintendo to write a future firmware that checks for such a driver being present. But I guess they could do that with a SD card as well, just look for the usual suspect directories, bootloader, etc.
 
Currently I am on 4.1.0 and I would like to set up emuNAND to 6.2

I have quite a few purchased/installed games. My question is if I play those games on the 6.2 emuNAND will I have to update the games to be able to play them? If possible I'd like to keep parity between the game versions on my 4.1 sysNAND and the 6.2 emuNAND
 
Hi. New to the scene switch. I havent done anything yet but I bought a 3d printed jig that will arrive around 20 Jan.
My question is... Seeing that the scene is currently a bit choppy jet (pin shorts, exFAT random corruptions+need to update, Fat32 limitations, nice and crispy BANS)... Os going to be another method of softmoding that doesnt require messing with pins nor purposely mid-briking the console [the AutoRMC method sounded like that to me]? Like, something easier and nooby friendly?
I heard of something like warmboot or something... What would that be? Is expected early or at least a few months?

Thans
 
Hi. New to the scene switch. I havent done anything yet but I bought a 3d printed jig that will arrive around 20 Jan.
My question is... Seeing that the scene is currently a bit choppy jet (pin shorts, exFAT random corruptions+need to update, Fat32 limitations, nice and crispy BANS)... Os going to be another method of softmoding that doesnt require messing with pins nor purposely mid-briking the console [the AutoRMC method sounded like that to me]? Like, something easier and nooby friendly?
I heard of something like warmboot or something... What would that be? Is expected early or at least a few months?

Thans

Sometime soon, when they get around to releasing the writeup and whatnot. Until then RCM is the only way. RCM + Jig is still the best option as it gives you more access imo


If you follow the guides it's hard to mess up, not to mention we are happy to help. We can bypass the fat32 limitation with usb/wifi install. 90DNS to block telemetry to nintendo. ChoidujourNX for updating. It's all quite simple now. The hardest part is getting into RCM for the first time
 
  • Like
Reactions: CapCaveman
Hello, ever since i switched from RajNX to Kosmos i have faced some problems:

1- Some NSPs just stopped working altogether, while others still works fine

2- On RetroNX my gba saves were completely lost and when i try to load states they just give a weird sound and crash

Is there anything i can do to solve this? thanks
 
Hello, ever since i switched from RajNX to Kosmos i have faced some problems:

1- Some NSPs just stopped working altogether, while others still works fine

2- On RetroNX my gba saves were completely lost and when i try to load states they just give a weird sound and crash

Is there anything i can do to solve this? thanks
Honestly I would revert back
 
Guys, help!

Finished backing up my NAND and BIS keys following this guide. Started SX OS for the first time, activated the license on my PC, and booted up SX OS for a second time with the license file in the SD card. Made sure to select CFW.

It loaded the Switch's home screen for a few seconds, then gave me an error message (error code: 2051-0006) and told me to hold on the power button for 12 seconds. Tried booting up again (in RCM), saw SX's logo, but it skipped the "select" screen (for CFW/OFW) and went it straight to the Switch's home screen. Again received the same error as before.

Not sure what I'm doing wrong. system version is 1.0.0, and I'm running SX OS's latest beta release (2.5) on a 128GB microSD card formatted to FAT32 using GUIFormat.

Update: Found someone on Team Xecuter's forums with the same problem as me. Apparently, you can only run SX OS 2.5 beta if you already have emuNAND on 6.2.0. Downloaded the previous beta version of SX OS (2.4.1) and it booted up just fine. I'm now in the process of creating the emuNAND.
 
Last edited by CapCaveman,
See if you can access the homebrew menu (launch album) if you can then you are in CFW. However to add the exfat support you need to update your system firmware. You can do this officially or using choidujourNX. Both are viable options and all cfw works on 6.2. I also recommend you follow the guide I linked above to make a backup if you haven't done so yet

Formatting to FAT32 with GUIFormat was the solution. Lockpick was success. I have the prod.key now, but not sure which of the XCI tools is the one I should use. Which one is relevant in Dec 2018 and splits the resulting NSP for FAT32?
 
Hey guys I have a problem.My switch worked fine until I updated my SD files and and my firmware to 6.2. Now every time that I try to inject a payload it always is trying to inject and fails and then on the second time that I try again it injects it normaly. Is this normal?? Why is this happening? Could it be that I stacked 2 auto RCM one on top of each other or is that not even possible?
 
I got the SX Pro a while back and I’ve been on 5.1 and haven’t kept up with the scene. Now that emunand is out, I want to switch to that. I backed up my nand and have no internet connections saved (although airplane mode is off) so I should not be banned. How should I go about this about switching to emunand and updating to 6.2?
 

Site & Scene News

Popular threads in this forum