Hacking SWITCH NOOB PARADISE - Ask questions here

[Draxzelex]

I wanted to know is it safe for a CFW Switch to use LAN (Router not connected to internet) play with a non CFW switch? I just want to make sure nothing will happen to my CFW Switch & Nintendo Account.

Thanks.

LAN is short for Local Area Network therefore it doesn't use the Internet but rather a local wireless connection. I also don't recall any mention in the Terms of Service that you cannot play locally with a hacked console. And even if there was, it would seem kind of unfair for people to be banned over that since the other party would not have any way of knowing your console is hacked. Therefore, I cannot see any logic behind an unhacked console getting banned for simply communicating locally with a hacked console.

 

[Draxzelex]

Right, will give it a try.

EDIT 1: Nothing, didn't work. I deleted the Atmosphere folder first and copied the files again and the error still persists. I read somewhere this error is related to burnt fuses?

@Draxzelex would really appreciate your help, man.

EDIT 2: Checked fuses:

Burnt fuses (odm 7/6): 15-0 (HOS:12.0.2+)

Am I screwed? Please I need help I'm getting kind of desperate. I read you need to restore a NAND back up but I don't have one.

EDIT 3: Tried a clean Atmosphere, Hekate and sigpatches update to no avail.

I didn't notice you edited your post. Although a bit impolite, you can double-post any updates. Did you put the bootloader folder from the latest version of Hekate onto your SD card?

 

[.Darky]

I didn't notice you edited your post. Although a bit impolite, you can double-post any updates. Did you put the bootloader folder from the latest version of Hekate onto your SD card?

I did. I download the latest version from here:

https://github.com/CTCaer/hekate/releases

I did notice the last modified date of the bootloader folder included in the .zip file is june of 2020. Perhaps that has something to do with this?

 

[godreborn]

nice hendrix avatar, @.Darky .

 

[.Darky]

nice hendrix avatar, @.Darky .

Cheers, man.

@Draxzelex I tried copying the file again and I keep getting the same error. By the way, I can boot emuNAND but can't put the system on sleep mode.

Perhaps the error is related to the hekate_ipl.ini file. My configuration is this:

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

[Atmosphere CFW]
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp
emummcforce=1
kip1patch=nosigchk

 

[RJMayhem]

LAN is short for Local Area Network therefore it doesn't use the Internet but rather a local wireless connection. I also don't recall any mention in the Terms of Service that you cannot play locally with a hacked console. And even if there was, it would seem kind of unfair for people to be banned over that since the other party would not have any way of knowing your console is hacked. Therefore, I cannot see any logic behind an unhacked console getting banned for simply communicating locally with a hacked console.

What I was more concerned about is the non CFW Switch saving any logs about the CFW Switch pr account and report back to Nintendo servers when the non CFW Switch goes back online. My CFW Switch isn't ban and would like to keep it that for for as long as possible. I've never used LAN on the Switch before modded or not so just checking.

 

[Draxzelex]

I did. I download the latest version from here:

https://github.com/CTCaer/hekate/releases

I did notice the last modified date of the bootloader folder included in the .zip file is june of 2020. Perhaps that has something to do with this?

While the last modified date of the /bootloader folder is June 2020, the more important folder is one inside the /bootloader folder which is the /sys folder because it was last modified on May 11th so this one should be updated on your SD card.

What I was more concerned about is the non CFW Switch saving any logs about the CFW Switch pr account and report back to Nintendo servers when the non CFW Switch goes back online. My CFW Switch isn't ban and would like to keep it that for for as long as possible. I've never used LAN on the Switch before modded or not so just checking.

Well as far as I know, nothing is saved to any system during local communications. If there was, people would have noticed a long time ago. Also just as an aside but Nintendo Accounts are rarely relevant for hacking or bans. Even if a console is banned, majority if not all the time the account is untouched. People have even been able to use accounts from banned consoles on unbanned consoles without issue so you don't need to worry about your account getting hit just because one of your consoles is hacked.

 

[RJMayhem]

Well as far as I know, nothing is saved to any system during local communications. If there was, people would have noticed a long time ago. Also just as an aside but Nintendo Accounts are rarely relevant for hacking or bans. Even if a console is banned, majority if not all the time the account is untouched. People have even been able to use accounts from banned consoles on unbanned consoles without issue so you don't need to worry about your account getting hit just because one of your consoles is hacked.

Thank you for explaining everything. I didn't know it didn't effect your account just the switch.

 

[.Darky]

While the last modified date of the /bootloader folder is June 2020, the more important folder is one inside the /bootloader folder which is the /sys folder because it was last modified on May 11th so this one should be updated on your SD card.

Well, it's there. So that's definitely not the issue. Like I said before, emuNAND was working fine until I updated sysNAND to 12.0.2 and installed the latest MH Rise update overnight while the system was on sleep mode. I played for a bit, restarted the system and when I tried to boot emuNAND again this happened.

I'm even starting to believe this may be a hardware issue. SciresM posted this back in february:

https://github.com/Atmosphere-NX/Atmosphere/issues/1359

Maybe it's related.

 

[Draxzelex]

Well, it's there. So that's definitely not the issue. Like I said before, emuNAND was working fine until I updated sysNAND to 12.0.2 and installed the latest MH Rise update overnight while the system was on sleep mode. I played for a bit, restarted the system and when I tried to boot emuNAND again this happened.

I'm even starting to believe this may be a hardware issue. SciresM posted this back in february:

https://github.com/Atmosphere-NX/Atmosphere/issues/1359

Maybe it's related.

Well its a bit hard to believe it is a hardware issue if it only manifests after a firmware update. Can you try booting Atmosphere with fusee_primary instead? Meaning instead of using Hekate, you will send fusee_primary as the payload.

 

[.Darky]

Well its a bit hard to believe it is a hardware issue if it only manifests after a firmware update. Can you try booting Atmosphere with fusee_primary instead? Meaning instead of using Hekate, you will send fusee_primary as the payload.

I copied the fusee_primary sigpatch and when I select it from Hekate I get a black screen with an error.

 

[Draxzelex]

I copied the fusee_primary sigpatch and when I select it from Hekate I get a black screen with an error.

What is the error?

 

[.Darky]

Fatal error: [NXBOOT] Failed to determine mariko warmboot firmware.

 

[Ed12]

I'm having maybe similar errors as the user above "Failed to match warmboot with fuses, if you continue sleep won't work". If I override the error it boots and runs backups fine, but going into sleep locks the unit until restarted. I recently switched from SXOS to Atmosphere on my Mariko SX Core unit. Had no sleep issues on first boot into Atmosphere, but after rebooting to attempt to add tinfoil I am now getting this error. I have updated Atmosphere/sigpatches/hekate & also updated system to 12.0.2 & CFW to 12.0.1 (might they need to be exactly matching?). Did I mess up something?

 

[DaveyMames]

When I try and launch a game on my EmuMMC I get the "checking whether this software can be played" message and it won't let me play the game. It says "An error has occurred. Please try again later. If the problem persists, please try performing a system update". How can I get the games to play?

Is it asking that because the game has an online multiplayer game mode as I thought since the main game is single player then I wouldn't need to download any system update to play it?

Do I need to install the system update on my internal storage or on my EmuMMC?

 

[Zetareta]

Device : Mariko FW 11.0.0
SX CORİ CHİP : 3.1.0
Nand : Sysnand ( Already N. banned and ı dont give a ......... )
I want atmos and l am plannig follow this ( rentry.co/mys8q ) guide. İf l will update OFW 12 blabla with offical way, my chip wont work,l am curious about if l update FW 12, can l reach sx cori menu that options selection that give me chance to reload my sysnand backup.

 

[Draxzelex]

Fatal error: [NXBOOT] Failed to determine mariko warmboot firmware.

Did you ever downgrade your firmware?

I'm having maybe similar errors as the user above "Failed to match warmboot with fuses, if you continue sleep won't work". If I override the error it boots and runs backups fine, but going into sleep locks the unit until restarted. I recently switched from SXOS to Atmosphere on my Mariko SX Core unit. Had no sleep issues on first boot into Atmosphere, but after rebooting to attempt to add tinfoil I am now getting this error. I have updated Atmosphere/sigpatches/hekate & also updated system to 12.0.2 & CFW to 12.0.1 (might they need to be exactly matching?). Did I mess up something?

First, there is no such thing as "CFW 12.0.1" because CFW follows a different numbering scheme. 12.0.1 only refers to your firmware which can either be sysMMC or emuMMC. I don't know what version of CFW you are using but the latest version of Atmosphere is 0.19.3. Also, upon further research, this error pops up if you have tried downgrading like the user above you. Did you ever downgrade? If yes, do you have an eMMC backup?

When I try and launch a game on my EmuMMC I get the "checking whether this software can be played" message and it won't let me play the game. It says "An error has occurred. Please try again later. If the problem persists, please try performing a system update". How can I get the games to play?

Is it asking that because the game has an online multiplayer game mode as I thought since the main game is single player then I wouldn't need to download any system update to play it?

Do I need to install the system update on my internal storage or on my EmuMMC?

If you are trying to launch a pirated game, you need patches to play it. Those patches can be downloaded from the pinned thread on this forum.

Device : Mariko FW 11.0.0
SX CORİ CHİP : 3.1.0
Nand : Sysnand ( Already N. banned and ı dont give a ......... )
I want atmos and l am plannig follow this ( rentry.co/mys8q ) guide. İf l will update OFW 12 blabla with offical way, my chip wont work,l am curious about if l update FW 12, can l reach sx cori menu that options selection that give me chance to reload my sysnand backup.

Well updating your firmware is not going to break your chip. In fact, no firmware is ever going to stop your chip from working. The SX Core relies on the hardware, not the software, of your console in order to exploit it therefore the firmware is irrelevant to making it work or not. And because of this fact, you can always boot the SX OS menu on your console regardless of your firmware. The only firmware-specific features are CFW and homebrew because these are loaded when the firmware is running therefore they are affected by the current firmware (e.g. you cannot boot the CFW SX OS on any firmware higher than 11.0).

 

[Zetareta]

Hmmm then l will go update OFW 12 and go this ( rentry.co/mys8q ) guide and will install atmos,heka,do you have something to say about it?

 

[Draxzelex]

Hmmm then l will go update OFW 12 and go this ( rentry.co/mys8q ) guide and will install atmos,heka,do you have something to say about it?

I am not familiar with that guide so I do not have an opinion on it. I have been recommending this guide since its from the forum to help people transition from SX OS to Atmosphere.

 

[Ed12]

First, there is no such thing as "CFW 12.0.1" because CFW follows a different numbering scheme. 12.0.1 only refers to your firmware which can either be sysMMC or emuMMC. I don't know what version of CFW you are using but the latest version of Atmosphere is 0.19.3. Also, upon further research, this error pops up if you have tried downgrading like the user above you. Did you ever downgrade? If yes, do you have an eMMC backup?

Thank you for your reply. Apologies as I meant I have since upgraded the emuMMC's firmware to 12.0.1 with Daybreak whereas the sysMMC is currently on 12.0.2. I'm still a noob especially with Atmosphere so hope that makes sense. I'm using the latest Atmosphere ver 0.19.3 (when I switched over from SXOS I believe I got 0.19.2 and my firmware was 11.x on both CFW & OFW and I was still on these versions when I started getting the error).

Unfortunately I can't really pin where I went wrong as the installation appeared to work fine when I switched over a few days. I was on CFW without the error, then rebooted into OFW for a couple of days, shut down the console and dropped Tinfoil onto the sd card then when I went to boot Atmosphere I got that error. I have since updated everything to latest (apart from emuMMC not being 12.0.2) but no luck. I haven't attempted to downgrade but I do have an eMMC backup. Do you think if I get the emuMMC updated to 12.0.2 it might help, or might I be looking at possibly doing a restore? Thank you!