Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,182,326
  • Replies Replies 48,025
  • Likes Likes 66
So it doesn't matter if I install pirated stuff on sys cfw it'll effect both stock & sys cfw?
That's how I understood it back when I was researching what I can and can not do on a modded Switch if I want to be able to play online as well. Both sys CFW and stock system share the same NAND. With the emuNAND, things are a bit different. You're making a clone of your sysNAND and by installing pirated games you're making your emuNAND "dirty". If you block the Nintendo servers, blank the prodinfo and stuff, you're less likely to get your console banned.

don't have the original backup but I guess I'll keep it offline unless there's a method to clean it all
Sadly, the only safe way is to restore the clean NAND backup only if you haven't connected to the Nintendo servers after you created the backup. There are tools that clean your logs but that will trip the log mismatch and flag your console.

other than that how do I update the sys cfw
I'm not entirely familiar with the sysNAND CFW, but I assume that you can update it via the official way or via Daybreak. It should be the same, I think. Better wait for someone else to reply, someone who's using sysNAND CFW daily.

& I have installed few games but some of em are not loading what's the issue with it?
There are many things that could stop games from working. What did you use to install them with, which installer? Tinfoil, Goldleaf, DBI, etc.? Did you boot into CFW without up-to-date sys-patch/sigpatches? Game tickets could've gotten invalidated depending on the way you've installed those games. I usually suggest reinstalling the games with the latest DBI while having the latest sys-patch, that usually fix the issues. Make sure that you have the latest patch as well. Not 100% necessary, but sometimes games will start working again if they are up-to-date.
 
Hi, I've been completely out of the loop with switch hacking for a while. I want to update my switch I hacked a long time ago (18.1.0 emummc with atmosphere 1.8.0/19.0.1 sysmmc) and there are a few things I'm not sure about:

- how can I update sysmmc without disabling autorcm? I'd rather not do weird things to enter rcm to launch hekate to reenable it since I don't have a good setup for doing the thing with the joycon rail
- what do I need to do to actually boot into it from hekate after updating? I recall getting some errors about package1/package2 (I don't remember which) after updating last time, but I don't remember how I fixed them exactly
- would there be any benefit to updating emummc or can I just leave it at 18.1.0? If there are reasons to update it, how would I do that?

And one more question not related to updating:
- my Switch is currently not banned. Would using atmosphere with sysdvr to capture gameplay in sysmmc risk getting a ban?
 
Hi, I'm not sure what I did wrong. I tried installing a game update (console is running Pack Atmosphere 1.11.2 Hekate 6.5.3 & Sigpatch FW 22.5.0 & Firmware 22.5.0) but it failed because of lack of space on the USD. I turned off the console (pressing power for a few seconds then going to the turn off menu). I manually cleared a folder that held some file updates as I usually do) When I started again (I have to put the SXOS dongle at the bottom of the console to restart (not sure if this is normal or not) and I saw the green light on it blink as usual but the next step (blue light briefly blinking never occured). The screen remained dark. I tried powering off by maintaining the power button for 20+ seconds. Tried a few times but the screen remains dark. I hooked up the switch console to the PC and launched TegraRcmGUI_v2.6_portable and it detected the console (green RCM OK message). That usually means the console is on I suppose. I saw a few payloads I could try (I have no idea what I am doing at that point, and probably no idea with the previous steps as well). I tried a few of these and tried booting again but still getting the black screen. Any idea how I could restart the darn thing ? I copied the files from the pack over to the USD card again overwrtiting all files. No success booting again.
Please help ! I'm desperate.

1788447064968.png
1788447169929.png
 
Hi, I'm not sure what I did wrong. I tried installing a game update (console is running Pack Atmosphere 1.11.2 Hekate 6.5.3 & Sigpatch FW 22.5.0 & Firmware 22.5.0) but it failed because of lack of space on the USD. I turned off the console (pressing power for a few seconds then going to the turn off menu). I manually cleared a folder that held some file updates as I usually do) When I started again (I have to put the SXOS dongle at the bottom of the console to restart (not sure if this is normal or not) and I saw the green light on it blink as usual but the next step (blue light briefly blinking never occured). The screen remained dark. I tried powering off by maintaining the power button for 20+ seconds. Tried a few times but the screen remains dark. I hooked up the switch console to the PC and launched TegraRcmGUI_v2.6_portable and it detected the console (green RCM OK message). That usually means the console is on I suppose. I saw a few payloads I could try (I have no idea what I am doing at that point, and probably no idea with the previous steps as well). I tried a few of these and tried booting again but still getting the black screen. Any idea how I could restart the darn thing ? I copied the files from the pack over to the USD card again overwrtiting all files. No success booting again.
Please help ! I'm desperate.

View attachment 588996View attachment 588997
Not sure if the SXOS dongle works the same as other RCM Injectors (I have literally 0 experience with that hardware) but have always needed to update the fusee on the RCM Injectors when updating Atmos/Hekate. Version with TegraRcmGUI looks fairly old if the hekate version is any indication. Grab the latest hekate build from Github, manually add the fusee and/or hekate payloads and try to inject them. If they work, that's your issue.
 

Site & Scene News

Popular threads in this forum