Toggle sidebar

Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 5,887,721
  • Replies Replies 47,855
  • Likes Likes 66
sorry for a dumb question, i used this https://switch.hacks.guide/ guide to hack my first gen switch, i downloaded SMO with DBI just fine (but had to dwnld sigpatches or somethinh) and it opened just fine , but i cant crack the code on how to play tomodachi life, i already installes newest syspatch 1.6.2.0 and sigpatches for it tp, on previous syspatch v 1.5.6 it even let me enter the game, only to get thrown out to the main menu. it constantly says that game is corrupted or something, and i cant even proceed past initial 1sec balck screen loading. im on version 22.1.0|AMS 1.11.1|s, any advice would be great
 
switch when i put in dock/rest mode - it doesnt boot back up unless i inject payload
there is battery life as it shows lfor example 44% it never used to to this before, why do i get a black screen if i i leave it for a day etc and try to play again...

latest atmosphere/hekate/fw - nintendo switch v1
 
So recently bought a switch lite which is already modded, I came to realize that it was modded on it's sysnand, I want to remove the mod from sysnand for online play & redo mod on the emunand, Can someone help me out on this, Please guide me on this, I'm confused of what to do first thanks
 
Onepunchbruh said:
So recently bought a switch lite which is already modded, I came to realize that it was modded on it's sysnand, I want to remove the mod from sysnand for online play & redo mod on the emunand, Can someone help me out on this, Please guide me on this, I'm confused of what to do first thanks
Click to expand...
Without a backup of a clean sysnand, there's not much that can be done for official online play.
 
  • Like
Reactions: Blythe93
Onepunchbruh said:
So recently bought a switch lite which is already modded, I came to realize that it was modded on it's sysnand, I want to remove the mod from sysnand for online play & redo mod on the emunand, Can someone help me out on this, Please guide me on this, I'm confused of what to do first thanks
Click to expand...
Does it already have pirated games installed on sysNAND? If so, I'm not sure whether you'll be able to use sysNAND for online play. You might be able to use it for a while until your console gets banned (can be instant, can take months to get banned) if it even gets banned at all. I've read too many stories so far all over the place.

All I know for sure is that once you install anything the unofficial way onto the sysNAND, whether it's a pirated games, homebrew forwarder etc, you're pretty much screwed since you can't clean up your sysNAND afterwards UNLESS both of the following statements are correct:
1) you have a clean sysNAND backup that you can restore to the console
2) you never connected the console to the Nintendo servers after you made the backup i.e. to update the firmware the official way.

Let's say that you restore a clean sysNAND backup but you know that you've previously connected to the Internet on your sysNAND after making that backup, once you connect to the Nintendo servers again, your console will be flagged for a log mismatch i.e. Nintendo already has more of your logs on their servers than you have on your console, which will eventually lead to ban. That's the theory at least.

It all depends on what the previous owner did to the console.

If you don't have the backup and you don't know whether the previous owner connected to the Nintendo servers after they made that backup making it somewhat useless for restoring console to the clean state (still useful in case of a major brick), I would try to just do the factory reset (won't clean up logs, though, so you're just doing it for the sake of doing it) and try using the console for the official stuff only for a few days, weeks, months. If you get banned i.e. you got restricted access to the eShop and online services, you'll know whether you're banned or not.

I would recommend making a backup of your sysNAND after you do a factory restore, though, just so that you have it in case your console gets bricked sometime in the future. Even a dirty backup is better than no backup.

I would suggest against using those scripts or tools that clean up your Switch and its logs, they won't do much, I'm afraid and will probably just make things worse.
 
  • Like
Reactions: Nephiel and Onepunchbruh
Blythe93 said:
Does it already have pirated games installed on sysNAND? If so, I'm not sure whether you'll be able to use sysNAND for online play. You might be able to use it for a while until your console gets banned (can be instant, can take months to get banned) if it even gets banned at all. I've read too many stories so far all over the place.

All I know for sure is that once you install anything the unofficial way onto the sysNAND, whether it's a pirated games, homebrew forwarder etc, you're pretty much screwed since you can't clean up your sysNAND afterwards UNLESS both of the following statements are correct:
1) you have a clean sysNAND backup that you can restore to the console
2) you never connected the console to the Nintendo servers after you made the backup i.e. to update the firmware the official way.

Let's say that you restore a clean sysNAND backup but you know that you've previously connected to the Internet on your sysNAND after making that backup, once you connect to the Nintendo servers again, your console will be flagged for a log mismatch i.e. Nintendo already has more of your logs on their servers than you have on your console, which will eventually lead to ban. That's the theory at least.

It all depends on what the previous owner did to the console.

If you don't have the backup and you don't know whether the previous owner connected to the Nintendo servers after they made that backup making it somewhat useless for restoring console to the clean state (still useful in case of a major brick), I would try to just do the factory reset (won't clean up logs, though, so you're just doing it for the sake of doing it) and try using the console for the official stuff only for a few days, weeks, months. If you get banned i.e. you got restricted access to the eShop and online services, you'll know whether you're banned or not.

I would recommend making a backup of your sysNAND after you do a factory restore, though, just so that you have it in case your console gets bricked sometime in the future. Even a dirty backup is better than no backup.

I would suggest against using those scripts or tools that clean up your Switch and its logs, they won't do much, I'm afraid and will probably just make things worse.
Click to expand...
So bought it from a shop, it was not connected to internet previously & there are games tinfoil etc installed on it, I want to clean up the sysnand & then create an emunand for backups n stuff, can you guide me on how to clean it thoroughly & redo the mod on emunand? & also on how to create a new sysnand backup after cleaning

Edit: Should I use haku33 will it brick my console? also the games & other stuff is installed on a128gb sd
 
Last edited by Onepunchbruh,
Hey yall lowkey modding noob so i just wanna ask about sigpatches, i cannot seem to find any sigpatches for the latest atmosphere. if anyone can educate me on that typa stuff cuz i got some games but i cant seem to run them without it. Thanks
 
Onepunchbruh said:
So bought it from a shop, it was not connected to internet previously & there are games tinfoil etc installed on it, I want to clean up the sysnand & then create an emunand for backups n stuff, can you guide me on how to clean it thoroughly & redo the mod on emunand? & also on how to create a new sysnand backup after cleaning
Click to expand...
So if I understood you correctly, there are games and Tinfoil forwarder on your home screen as well? If so, there's a chance you'll get your console banned once you connect to the Internet even if you try to factory reset it. There's nothing much you can do to clean it up, I'm afraid. There are a couple of scripts and tools but they won't do much, especially with the logs if there happens to be a mismatch between your console and Nintendo servers.

If you still want to give it a try and see for yourself, you can do the following. Note that I'm not an expert and that I might make a mistake here and there since I'm not sure how hardware modded system behaves as I've only ever had two unpatched Erista models in my hands that didn't require a modchip in order to get hacked. You have been warned, do not proceed if you're not 100% sure. I won't be responsible for any damage you make to your console. I probably won't be able to help you out diagnose the issues if you run into some as troubleshooting isn't my expertise either. I'm just here to tell you your options and that's pretty much it. You decide what you'd like to do.

As I said, you can clean up your sysNAND a bit by doing a factory reset but that will only clear the USER partition of the console, won't clean the system logs which are sent to the Nintendo if their servers aren't blocked. You'll do it just for the sake of doing it as you won't need all those games installed on your NAND backup anyway. Whether it's safe to do a factory reset, depends on what the previous owner did to the console.

To be on a safe side, I would do the following:
1) Remove all the games and apps you see on your home menu, all the users (except a new one that you'll create as your main, no need for the NNID), also remove all the paired bluetooth devices, forget all the networks, remove all the save data, etc. Manually. Don't do the factory reset just yet.
2) Once done, reboot to the hekate and make a NAND backup. Check this guide for more info: https://switch.hacks.guide/user_guide/all/making_essential_backups
3) Once done, make sure to copy that backup somewhere to the safe place on your PC.

Now you'll be able reboot to CFW and do the factory reset. if anything goes wrong, you can always boot into hekate and restore the backup you've just created.
Now, I'm not sure how hardware modded system works but it should reboot to either hekate, recovery mode, default payload or something. If it works, congrats, now you can make a new backup of your "clean" sysNAND via hekate again. Obviously, it's not the 100% clean backup that we'd like to have but at least it doesn't have games, save data, saved connections etc. Note that factory reset doesn't clean up your NAND so that you can use it for online play.

Once you make all the backups, I would turn off the console and remove the SD card and try booting into stock sysNAND to see if it works. To do that, while the console is turned off, press and hold both volume buttons, press the power button and keep holding the volume buttons until your system boots. If it boots correctly and everything works, now you can proceed to make emuNAND. Check this guide and follow the on-screen instructions: https://switch.hacks.guide/

Additionally, you don't have to dump your own sysNAND firmware in order to update your emuNAND. There's a repository on Github with all Switch firmwares to this day, you'll need to look it up on your own as we aren't allowed to link to it. Also, in order to play game backups, you'll need sys-patch (instead of Tesla menu, you can grab Ultrahand) and an installer such as DBI in order to install those games (I'd suggest using the latest Russian version, don't forget to get your keys with Lockpick_RCM before that).

Once done, you should have a working sysNAND and emuNAND setup on your console. I'd suggest swapping Atmosphere's reboot_payload.bin with the hekate's as you can run reboot to payload app in your homebrew launcher in order to access hekate easier.

On sysNAND, I'd create a new account (wouldn't use my main one) and see if you can connect to the eShop and other services, play around with it for a while and see if you'll get banned. If you get banned, you can still use your console for pirated games and stuff. If not, you can enjoy your legally purchased games as well.
Post automatically merged:

brdsaikush said:
Hey yall lowkey modding noob so i just wanna ask about sigpatches, i cannot seem to find any sigpatches for the latest atmosphere. if anyone can educate me on that typa stuff cuz i got some games but i cant seem to run them without it. Thanks
Click to expand...
Sigpatches are bit hard to make nowdays since there aren't noob-friendly guide on how to make them on your own. Therefore, I suggest switching to sys-patch instead. if you still want to use sigpatches, these are probably the latest ones. Make sure that you're booting into Atmosphere via hekate or that you're using a modified fusee.bin with the ips kip patches support restored. Otherwise, they won't work.
 
  • Like
Reactions: Onepunchbruh
Blythe93 said:
So if I understood you correctly, there are games and Tinfoil forwarder on your home screen as well? If so, there's a chance you'll get your console banned once you connect to the Internet even if you try to factory reset it. There's nothing much you can do to clean it up, I'm afraid. There are a couple of scripts and tools but they won't do much, especially with the logs if there happens to be a mismatch between your console and Nintendo servers.

If you still want to give it a try and see for yourself, you can do the following. Note that I'm not an expert and that I might make a mistake here and there since I'm not sure how hardware modded system behaves as I've only ever had two unpatched Erista models in my hands that didn't require a modchip in order to get hacked. You have been warned, do not proceed if you're not 100% sure. I won't be responsible for any damage you make to your console. I probably won't be able to help you out diagnose the issues if you run into some as troubleshooting isn't my expertise either. I'm just here to tell you your options and that's pretty much it. You decide what you'd like to do.

As I said, you can clean up your sysNAND a bit by doing a factory reset but that will only clear the USER partition of the console, won't clean the system logs which are sent to the Nintendo if their servers aren't blocked. You'll do it just for the sake of doing it as you won't need all those games installed on your NAND backup anyway. Whether it's safe to do a factory reset, depends on what the previous owner did to the console.

To be on a safe side, I would do the following:
1) Remove all the games and apps you see on your home menu, all the users (except a new one that you'll create as your main, no need for the NNID), also remove all the paired bluetooth devices, forget all the networks, remove all the save data, etc. Manually. Don't do the factory reset just yet.
2) Once done, reboot to the hekate and make a NAND backup. Check this guide for more info: https://switch.hacks.guide/user_guide/all/making_essential_backups
3) Once done, make sure to copy that backup somewhere to the safe place on your PC.

Now you'll be able reboot to CFW and do the factory reset. if anything goes wrong, you can always boot into hekate and restore the backup you've just created.
Now, I'm not sure how hardware modded system works but it should reboot to either hekate, recovery mode, default payload or something. If it works, congrats, now you can make a new backup of your "clean" sysNAND via hekate again. Obviously, it's not the 100% clean backup that we'd like to have but at least it doesn't have games, save data, saved connections etc. Note that factory reset doesn't clean up your NAND so that you can use it for online play.

Once you make all the backups, I would turn off the console and remove the SD card and try booting into stock sysNAND to see if it works. To do that, while the console is turned off, press and hold both volume buttons, press the power button and keep holding the volume buttons until your system boots. If it boots correctly and everything works, now you can proceed to make emuNAND. Check this guide and follow the on-screen instructions: https://switch.hacks.guide/

Additionally, you don't have to dump your own sysNAND firmware in order to update your emuNAND. There's a repository on Github with all Switch firmwares to this day, you'll need to look it up on your own as we aren't allowed to link to it. Also, in order to play game backups, you'll need sys-patch (instead of Tesla menu, you can grab Ultrahand) and an installer such as DBI in order to install those games (I'd suggest using the latest Russian version, don't forget to get your keys with Lockpick_RCM before that).

Once done, you should have a working sysNAND and emuNAND setup on your console. I'd suggest swapping Atmosphere's reboot_payload.bin with the hekate's as you can run reboot to payload app in your homebrew launcher in order to access hekate easier.

On sysNAND, I'd create a new account (wouldn't use my main one) and see if you can connect to the eShop and other services, play around with it for a while and see if you'll get banned. If you get banned, you can still use your console for pirated games and stuff. If not, you can enjoy your legally purchased games as well.
Post automatically merged:


Sigpatches are bit hard to make nowdays since there aren't noob-friendly guide on how to make them on your own. Therefore, I suggest switching to sys-patch instead. if you still want to use sigpatches, these are probably the latest ones. Make sure that you're booting into Atmosphere via hekate or that you're using a modified fusee.bin with the ips kip patches support restored. Otherwise, they won't work.
Click to expand...
I saw on youtube people using the haku33 to format their switch, should I go with that is that method safe? Should I create backup before doing that, when I launch haku33 I get a different msg at the bottom, reboot to payload cannot be used on a mariko system so I backed off from it incase it's something different, let me attach a pic of it at the bottom so you can get the idea
 

Attachments

  • IMG_20260603_192852.jpg
    IMG_20260603_192852.jpg
    1.6 MB · Views: 1
Onepunchbruh said:
I saw on youtube people using the haku33 to format their switch, should I go with that is that method safe? Should I create backup before doing that, when I launch haku33 I get a different msg at the bottom, reboot to payload cannot be used on a mariko system so I backed off from it incase it's something different, let me attach a pic of it at the bottom so you can get the idea
Click to expand...
Do not blindly follow random YouTube videos, they are usually outdated.

I'd start with the 3 steps @Blythe93 suggested before anything else. It's good to have a full backup before messing with it, otherwise you will have a much harder time if something goes wrong.
 
  • Like
Reactions: Blythe93
I apologize for this:

I've had my switch modded since OFW 10. Early on updating seemed easy as I recall. It was just updating with the Atmosphere zip contents, sigpatches, and a few minor things like the hekate ini with the FW boot options being populated and a few issues here and there with Tinfoil. But I always managed to get it all running with few problems other than Tinfoil breaking here and there and needing reinstalled.

Once TOTK came out, things started getting confusing. I distinctly remember having to download and install a Nintendo FW. I thought I remember it was 19.0.x (not sure 0 or 1), and Atmosphere was 1.8.0. But my OFW SYSMMC is still showing 10.0.4, so I didn't update that. Does the CFW SYSMMC use the SD card? It makes it sound like it uses the Switch memory, so I don't want to touch it, but again, I can't remember how it works. Anyway, I got it running eventually. Had a bunch of issues, but once I updated using the Nintendo FW, then went into Atmosphere, everything finally worked, except Tinfoil. (I have given up on that.)

So, possibly the last game I want to install was Metroid Prime 4. I was discouraged to learn I'd need to update again. I'm trying to not update the SYSMMC since I'd prefer to keep it on 10.0.4 (for no good reason?) I keep trying to return to 19.0.1, but nothing seems to work correctly. I download HATS, I've tried VenomNX, etc. If I try to inject Fusee, I get a yellow screen. If I inject hekate, then try to run EMUMMC, I get yellow screen. I've done all the alleged steps of removing all folders except Nintendo and emuMMC. Nothing works. I've recently learned that sigpatches are different now, and things typically go through Sys Patch (which if I read correctly, I don't need to do anything other than properly place it on the card). I also learned after trying to change that apparently there was a way to make MP4 work on 19.0.1 using SDK manipulation or something. So that was depressing to learn that maybe all of this could have been avoided!

The reason I'm reticent to updating to current FW is I've read about issues with homebrew (likely nothing I use) but more importantly, I've read about potential problems with BOTW/TOTK and a languages bug with it being 17+ languages or something causes issues.

I guess if anyone can alleviate my concerns about the newest official FW I'd be willing to update to that. Or if I'm supposed to update the CFW SYSMMC option first, then the atmosphere and that's how it's supposed to work, then cool. Is there any valid reason anymore to not update everything to current FW?
 
hypernova said:
Does the CFW SYSMMC use the SD card?
Click to expand...
sysMMC CFW uses internal storage for the internal storage and SD card for the SD card storage.
emuMMC CFW uses SD storage for both internal and SD card storage.

hypernova said:
for no good reason?
Click to expand...
That makes two of us. :D Both of my hacked Switches are on 16.x.x or something. :D I just use emuMMC anyway on those models, while I do have another Switch for legally purchased stuff.

hypernova said:
I've read about potential problems with BOTW/TOTK and a languages bug with it being 17+ languages or something causes issues.
Click to expand...
First time hearing that. The only thing I've seen floating around is that users sometimes aren't able to install and run BOTW/TOTK even though all other games work just fine. It's been a while since I had either one of those games on my Switch so I'll have to check personally to see if it works on my end and report back.

hypernova said:
Or if I'm supposed to update the CFW SYSMMC option first, then the atmosphere and that's how it's supposed to work, then cool. Is there any valid reason anymore to not update everything to current FW?
Click to expand...
Since you're on 10.x.x, I'd still stay on that firmware on sysMMC, there's no reason to lock yourself out from a new hack that may or may not be available in the future. The way things are now, it's highly unlikely that we'll ever get anything better than what we already have but there's still that non-zero chance. I'm currently on latest & greatest firmware on my emuMMC and from what I can see everything works properly, maybe a homebrew here and there doesn't work but that's a minor issue to me. Also, I don't use mods or anything like that so I don't run into memory issues.

The only reason why you may stay on the lower firmware (like 19.0.1 or even 18.1.0) is the amount of available memory for the sys-modules and mods if you're using them. If not, I don't really see a reason to stay on those firmware revisions.

Anyway, I'll check if BOTW/TOTK works on my end i.e. if it starts and plays well, that will be as far as I'll test it out.
Post automatically merged:

Blythe93 said:
Anyway, I'll check if BOTW/TOTK works on my end i.e. if it starts and plays well, that will be as far as I'll test it out.
Click to expand...
Both of them install and run as expected so I'm not sure what others are using that continuously breaks their games. Too many sys-modules? Mods? Those all-in-one packs sometimes break your CFW setup without you knowing it until you run into an issue. For example, I had a game that had conflict with the TriPlayer's sys-module, therefore I disable it when I'm not using it and game runs totally fine. That's not the issue with the TOTK or BOTW, though.

@hypernova If you'd like to update your Switch, I'd suggest checking this guide. You don't need to update your sysMMC in order to dump your firmware in order to update your emuMMC, you can download firmware files from a certain Github repo that I believe we aren't allowed to link to here. It's not hard to find it with the right keywords.

I also highly suggest that instead of using packs like HATS you build your own as most of us did. Why? It'll be so much easier for you to figure out what broke your CFW sometime in the future. At the very least you'll need: hekate, Atmosphere, sys-patch and an installer such as DBI. Additionally, I suggest getting Ultrahand (so that you can manage your sys-modules and overlays, such as sys-patch, emuiibo, etc.), emuiibo (if you'd like to make use of virtual amiibos), sphaira (replacement homebrew menu), JKSV (save manager), MissionControl (if you'd like to pair any other non-Nintendo controller) and linkalho mod (by mrdude, works on the 21.x.x or higher, required for making fake NNIDs so that certain games may work on your Switch such as NSO emulators). Anything else? Make sure that your keep your setup up-to-date and avoid unnecessary clutter. Check this thread if you're looking for unofficial updated versions of the apps you're using.
 
Last edited by Blythe93,
@Blythe93 Hey so after doing the format I think my console is bricked or something it doesn't boot into hakate & some weird menu pops up, can you guide me on this, I did my a backup before doing the format

Edit: while holding the volume down & power button I boot into this, I'm so confused I don't know what to do at this point, if I click on boot atmosphere it just loades me to switch home menu & nothing was erased from it, I did the haku33 & now am at this thing? Should I have just used system format normally instead of haku33 tool? I thought of trying haku to do a clean format if things go wrong I have a backup but this is just getting confusing now for me, instead of going to hekate It's just loading a different menu...
 

Attachments

  • IMG_20260604_222448.jpg
    IMG_20260604_222448.jpg
    1.4 MB · Views: 1
  • IMG_20260604_223702.jpg
    IMG_20260604_223702.jpg
    1.6 MB · Views: 1
Last edited by Onepunchbruh,
Onepunchbruh said:
Hey so after doing the format I think my console is bricked or something it doesn't boot into hakate & some weird menu pops up
Click to expand...
Onepunchbruh said:
if I click on boot atmosphere it just loades me to switch home menu & nothing was erased from it
Click to expand...
Good news is that it's not bricked.

Onepunchbruh said:
I did the haku33 & now am at this thing? Should I have just used system format normally instead of haku33 tool?
Click to expand...
It's been a while since I saw haku33 tool and I definitely didn't recommend it so I'm not sure what exactly did you clean with it, nor do I know what it actually did to your console so I can't really help you out. If you can select the Reboot to bootloader/update.bin, that will lead you back into hekate.

Onepunchbruh said:
I thought of trying haku to do a clean format if things go wrong I have a backup but this is just getting confusing now for me, instead of going to hekate It's just loading a different menu...
Click to expand...
It could be that files on your SD card are set up so that your console boot into tegraexplorer on boot or something.
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Is it fixable

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Hacking Emulation  Switch Prod Keys downloading from sites okay?