Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 5,912,398
  • Replies Replies 47,857
  • Likes Likes 66
Like when I turn on the console no, It just looks like the normal Switch Menu, Firmware 20.1.1
you mentioned you already modded your switch 1 , meaning you must have injected RCM payload. Did you install hekate..etc too? Did you ever boot into hekate?
 
you mentioned you already modded your switch 1 , meaning you must have injected RCM payload. Did you install hekate..etc too? Did you ever boot into hekate?
Yes, though only once. I heard there were some risks at the time over modded switches getting Switch 2 bricked so i didn't do much with it. The last thing I did with my Switch was following some guide to help block updates and Nintendo sites to minimize risk of bans, but I don't even remember how I did that, Though my Switch still doesn't connect to the eshop and can't update through Wi-Fi so that's still in effect.

Edit: Took a bit to figure out but didn't realize i had to re inject the payload if the system powers off and managed to update everything with guide, but how do i fix whatever i did that prevents me from using internet in SysMMC, My main goal currently is to be able to send save files to my Switch 2 safely.
 
Last edited by Enigma424,
i ant seem to get my savefile from pokemon SP i played in ryujinx to run on my switch, everytime the game just starts a new savefile
 
So... say I did install Firmware 22.1.0, and I can't booth into CFW anymore. I can still access the Hekate screen. How can I lockpick myself outta this?
 
Well first question would be did you had an emunand or was everything on sysnand?
Well now I'm not sure, because now I can't boot into Hekate. This screen keeps popping up. I think maybe I was on emunand?
 

Attachments

  • 20260421_221217.jpg
    20260421_221217.jpg
    2.2 MB · Views: 14
Yes, though only once. I heard there were some risks at the time over modded switches getting Switch 2 bricked so i didn't do much with it. The last thing I did with my Switch was following some guide to help block updates and Nintendo sites to minimize risk of bans, but I don't even remember how I did that, Though my Switch still doesn't connect to the eshop and can't update through Wi-Fi so that's still in effect.

Edit: Took a bit to figure out but didn't realize i had to re inject the payload if the system powers off and managed to update everything with guide, but how do i fix whatever i did that prevents me from using internet in SysMMC, My main goal currently is to be able to send save files to my Switch 2 safely.
at least good you re-injected the payload , honestly i'm more than happy to help about CFW but i have never moved any save as i have only one switch :(
 
at least good you re-injected the payload , honestly i'm more than happy to help about CFW but i have never moved any save as i have only one switch :(
No worries and thanks, I "Think" I have a solution, Though I'm scared to test it if anyone has any experience it'd be helpful but if boot back into SysMMC and turn off the Switch and remove the SD Card and turn it on again, My internet function seems to work again so in theory I think I could upload my save to the Cloud with NSO and redownload it on Switch 2?
 
No worries and thanks, I "Think" I have a solution, Though I'm scared to test it if anyone has any experience it'd be helpful but if boot back into SysMMC and turn off the Switch and remove the SD Card and turn it on again, My internet function seems to work again so in theory I think I could upload my save to the Cloud with NSO and redownload it on Switch 2?
i think SysMMC is the way as you said , it allows you to be in the grey area but risk of being banned by Nintendo :unsure:
 
Hi everyone. I haven't used the Switch for a while and I have version 1.9.4 of Atmosphere (OFW 20.1.1). I was about to update to the new version of Atmosphere, but, when it was time to try to download the sigpatches, I realized that something has changed. I read the thread about sigpatches, but I didn't understand well. Can someone recap me of the latest events and advise me whether to update or not? Thanks!
 
Hi everyone. I haven't used the Switch for a while and I have version 1.9.4 of Atmosphere (OFW 20.1.1). I was about to update to the new version of Atmosphere, but, when it was time to try to download the sigpatches, I realized that something has changed. I read the thread about sigpatches, but I didn't understand well. Can someone recap me of the latest events and advise me whether to update or not? Thanks!
it should be fine to update as the sig patches have been updated although its being recomended to use syspatch instead. the events were impeeza anouncing that he was no longer going to update the sig patches or the ips patcher for it however a user by the name of alexios or something like this i might have the wrong name sorry if i do any ways she has updated the sig patches, also sciresm has retired from developing and updating atmosphere, and it was taken over by alula and another user whos name i dont remember so no need to worry atmosphere is updated as well as syspatch and the sig patches. if you have all the recompiled apps that were done for 21.10 you should be fine if not there is a thread dedicated to them with links to all the updated apps just search compiled apps and you should be able to find the thread. as for advice its up to you if you want to update. if you are wondering is it safe to update with out messing anything up yes it is as long as you do it correctly.
 
This might be addressed somewhere here, but I am a little swamped for time right now to browse through everything.

I usually update my CFW and console firmware every year or so. Recently updated to atmosphere 1.11.1 and firmware 22.1.0 and it seems like most homebrew crashes either immediately, or upon executing certain actions with the black "The software was closed because an error occured" screen. For example, DBI crashes when trying to install something with the MTP responder, but only during the last phase of the installation. Goldleaf seems to crash immediately upon opening. Installed games run just fine, although I haven't tested playing anything for a long period of time for stability, just very quick boot to title screen, load save file, etc checks.

I didn't do anything different than the usual proceedure of overwriting files, installing sig patches (which I understand have changed), etc. Any advice on what to look for to troubleshoot?
 

Site & Scene News

Popular threads in this forum