Hacking SWITCH NOOB PARADISE - Ask questions here

[BigOnYa]

I'm on a banned V1 Switch, on 15.0.1. Was wondering if I went online with it, to do something unrelated(FTP), Nintendy will send me the update nag. Can that update nag ( for the new 16 update) still be removed with Goldleaf?

 

[binkinator]

reinstalled AMS and Sigpatches..same

Yuck.

let’s do that again, but this time, before you do, let’s make a backup of /atmosphere/ and /bootloader/ by doing the following:

move/rename /atmosphere/ to /atmosphere.bk
move/rename /bootloader/ to /bootloader.bk

unzip atmosphere followed by hekate followed by Sigpatches and then copy /bootloader.bk/hekate_ipl.ini to /bootloader/helate_ipl.ini

reboot and test…

I'm on a banned V1 Switch, on 15.0.1. Was wondering if I went online with it, to do something unrelated(FTP), Nintendy will send me the update nag. Can that nag still be removed with Goldleaf?

Do this and you will have no worries. It blocks all of that.

https://rentry.org/ExosphereDNSMITM

 

[BigOnYa]

Do this and you will have no worries. It blocks all of that.

https://rentry.org/ExosphereDNSMITM

And later when new AMS full released, I want to update using Nintendy official update way, Can I just delete those files, and it's back to the previous state?

 

[Space_Goddess_Samus_Aran]

now i get a fatal error with 010041544D530000 when i try to boot cfw from hekate

Yuck.

let’s do that again, but this time, before you do, let’s make a backup of /atmosphere/ and /bootloader/ by doing the following:

move/rename /atmosphere/ to /atmosphere.bk
move/rename /bootloader/ to /bootloader.bk

unzip atmosphere followed by hekate followed by Sigpatches and then copy /bootloader.bk/hekate_ipl.ini to /bootloader/helate_ipl.ini

reboot and test…


Do this and you will have no worries. It blocks all of that.

https://rentry.org/ExosphereDNSMITM

 

[Hayato213]

now i get a fatal error with 010041544D530000 when i try to boot cfw from hekate

You on Mac?

 

[Space_Goddess_Samus_Aran]

no win 11...eww mac.xD

 

[Hayato213]

no win 11...eww mac.xD

It is a SD card problem, you can try to use Hekate archive bit to fix the problem or reformat the card again, that what people suggested for that error.

 

[Space_Goddess_Samus_Aran]

It is a SD card problem, you can try to use Hekate archive bit to fix the problem or reformat the card again, that what people suggested for that error.

sh...all my games and mods.....lmao..but why does Tinfoil or other homebrew work?

 

[Animage55]

?

 

[binkinator]

And later when new AMS full released, I want to update using Nintendy official update way, Can I just delete those files, and it's back to the previous state?

Yes, that will definitely work.

 

[SciGuy]

I made a mistake and accidently updated the OFW from 15 to 16 while booted into CFW SysNAND today (damn popup got me while I was trying to start a game). It updated and reset to CFW EmuNAND. I shut down the console, downloaded and updated the bootloader folder from Hekate 6.0.1 to 6.0.2, and updated the payload in the RCMloader, but whenever I try to boot up CFW SysNAND it just goes to black screen. If I have the RCMloader inserted then it will eventually say "HOS Panic Occurred" and load back into the boot menu. I can load into EmuNAND still, (I haven't updated the OFW yet), and if I turn off Auto RCM I can boot into the stock FW. Does anybody have any ideas? I'll copy and paste my ipl file, but I think it's all okay. It worked fine before the update and I hadn't changed anything in the file at all.

Spoiler: Hekate.ipl

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=113
noticker=0
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

[CFW SysNAND]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

 

[binkinator]

I made a mistake and accidently updated the OFW from 15 to 16 while booted into CFW SysNAND today (damn popup got me while I was trying to start a game). It updated and reset to CFW EmuNAND. I shut down the console, downloaded and updated the bootloader folder from Hekate 6.0.1 to 6.0.2, and updated the payload in the RCMloader, but whenever I try to boot up CFW SysNAND it just goes to black screen. If I have the RCMloader inserted then it will eventually say "HOS Panic Occurred" and load back into the boot menu. I can load into EmuNAND still, (I haven't updated the OFW yet), and if I turn off Auto RCM I can boot into the stock FW. Does anybody have any ideas? I'll copy and paste my ipl file, but I think it's all okay. It worked fine before the update and I hadn't changed anything in the file at all.

Spoiler: Hekate.ipl

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=113
noticker=0
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

[CFW SysNAND]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

you need to upgrade Atmosphere as well. 1.5.0 is in pre-release but it’s the best option at the moment.

https://github.com/Atmosphere-NX/Atmosphere/releases

(make sure you grab the latest fusee.bin as you have it in your helate_ipl.ini for CFW/Emunand )

 

[DaddyDingDong]

Just wanted to share an epiphany I had today I was having a hell of a time getting things to work on my V1 switch after the OFW 16 update. After reformatting my SD and going through the entire emummc process again I continued to have issues with TinFoil and loading NSPs via USB. I then thought... What if it's not my emummc, what if I have too much crap on my stock sysnand. So I did a factory reset on my switch then started the Hekate, Atmosphere setup from scratch and I have to say everything is running smoothly without an account linked to Nintendo and without any previous data on the switch. It's never ran this smooth on atmosphere ever.

 

[Pokefanlover94]

Move/rename /atmosphere/contents to /atmosphere/contents.bk and reboot to see if that fixes you.

Didn't I had to completely downgrade atmosphere to the ver I had before

 

[miniadri]

Hello, i have a problem with Digimon World Next Order, i'm trying to play it but it says "an error ocurred, returning to home".
I have erista switch on 15.0.1 with Atmosphere last version 1.5.0 pre-realease, the update fusee, hekate_ctcaer_6.0.2 and Nyx_1.5.2 and sigpatches compatible with the last version of atmos.
At the begining i had the problem with the game but it was because i was on switch v14, then i deleted the game, update my console with all atmos and so on and got fatal error with atmosphere, i had to delete the folder contents to solved it, i installed the game again with awoo via lan as always but the game still not working.
I have try Pokemon violet and this still working.

Any clue to solved it? It's the only game i can't play .
Thanks!

 

[binkinator]

To begin sorry if this is not in the right section new here Also I will give the most info I can as I don’t know what will all be needed.


Nintendo switch modded with a trinket M0
So since having my switched modded this is the first problem I have had.Downloaded Mario + rabbids sparks of hope and just getting a loading circle if I click on it nothing happens

Installed a trinket M0
Sthetix HATS installed

Current version of CFW is 11.0.1|AMS 1.4.0|s
Current version of OFW IS 11.0.1

What can I do to get Mario+rabbid spark of hope to work correctly it sits on the mainscreen now with the loading wheel if I click on it nothing happens

Also I have not done a backup yet since getting the switch SYSMMC CFW is how I am getting into the CFW AND EMUMMC gives a error when I click on it

Welcome to the Temp.

First, backup both your Sysnand and your Emunand using Hekate

https://rentry.org/BackupRestoreNAND

Next, backup your main partition by putting your SDCard in your PC and copy/paste.

Now, delete the game from Setting -> Data Management

Now that you‘re backed up and clean, you will need to update your system as this game requires FW 13.0.0+

Read through this doc from the top to get a handle on the overall process.

https://rentry.org/SwitchHackingIsEasy

Finally, execute the following to update your Switch:

https://rentry.org/UpdateCFW (use PC method)

Grab firmware from that Darthsternie guy and then do this:

https://rentry.org/UpgradeDowngrade

 

[LipefipeFelps]

Can i setup a modchipped switch using the "official" NH guide for unpatched v1s as base? Ofc skipping the unpatched related parts, like injecting a payload

 

[xsdfr]

is it worth modding a switch? and if so, what are the risks associated with it?

 

[Draxzelex]

Hello, i have a problem with Digimon World Next Order, i'm trying to play it but it says "an error ocurred, returning to home".
I have erista switch on 15.0.1 with Atmosphere last version 1.5.0 pre-realease, the update fusee, hekate_ctcaer_6.0.2 and Nyx_1.5.2 and sigpatches compatible with the last version of atmos.
At the begining i had the problem with the game but it was because i was on switch v14, then i deleted the game, update my console with all atmos and so on and got fatal error with atmosphere, i had to delete the folder contents to solved it, i installed the game again with awoo via lan as always but the game still not working.
I have try Pokemon violet and this still working.

Any clue to solved it? It's the only game i can't play .
Thanks!

Try the advice found in this thread.

Can i setup a modchipped switch using the "official" NH guide for unpatched v1s as base? Ofc skipping the unpatched related parts, like injecting a payload

I suppose you can. It does help in finding the files needed to use CFW and homebrew. Keep in mind not all hacks work on all consoles. For example, Mariko units cannot utilize reboot to payload.

is it worth modding a switch? and if so, what are the risks associated with it?

It depends who you ask. Worth is subjective and while some people focus on the positives. others will look at the negatives. Objectively speaking, there are a plethora of things you can only do with a modded Switch and the worst case scenario is that you are banned. However even in the worst scenario, there are ways to emulate online multiplayer such as LAN play or Xlink Kai so being banned isn't the end of the world. Couple that with the fact that hackable consoles, even banned, sell for far more than MSRP than consoles that require a modchip to be hacked and you will understand that many people are interested in hacking their device.

The most obvious risk was already stated to be being banned however there are ways to avoid a ban even with a modded Switch. The only other risk is the potential to brick the device. But as long as you create a dump of the eMMC (and BOOT0/1), you can always recover from a brick. Outside of that, there aren't really any other risks associated with hacking a Nintendo Switch. Of course, all of this only applies if your console isn't patched. If it is, then you will need solder a modchip inside which opens a whole other can of worms.

 

[xsdfr]

It depends who you ask. Worth is subjective and while some people focus on the positives. others will look at the negatives. Objectively speaking, there are a plethora of things you can only do with a modded Switch and the worst case scenario is that you are banned. However even in the worst scenario, there are ways to emulate online multiplayer such as LAN play or Xlink Kai so being banned isn't the end of the world. Couple that with the fact that hackable consoles, even banned, sell for far more than MSRP than consoles that require a modchip to be hacked and you will understand that many people are interested in hacking their device.

The most obvious risk was already stated to be being banned however there are ways to avoid a ban even with a modded Switch. The only other risk is the potential to brick the device. But as long as you create a dump of the eMMC (and BOOT0/1), you can always recover from a brick. Outside of that, there aren't really any other risks associated with hacking a Nintendo Switch. Of course, all of this only applies if your console isn't patched. If it is, then you will need solder a modchip inside which opens a whole other can of worms.

thanks. i own an (afaik) unpatched switch so softmodding is a possibility for me. also, does using emuMMC remove the risk of being banned?