Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

I didn't know that, thanks. But now I've tried downloading the same game again from another site and I'm getting the "old firmware" error.

Good idea to tell us what firmware is the system on.

 

[Flama2309]

19.0.1 I honestly don't know anything about that; when I bought my NS, it was already hacked.

 

[Hayato213]

19.0.1 I honestly don't know anything about that; when I bought my NS, it was already hacked.

The base game needs firmware 19.0.0 without patching the game if you patch it you can run it on firmware 17.0.1

The day 1 update needs 20.1.5, don't really know the firmware requirements for latest game update , your best shot is to update your firmware.

 

[Hamburglar]

Complete noob here. I have weird problem with my modded switch and I tried a bunch of stuff but I'm stumped. I recently got my OLED switch modded and the person also set up Hekate for me on my SD card. I got an eMMC backup before doing anything else. Afterwards I tried updating Atmosphere using daybreak. That is when I got the blue screen of death. So now Hekate launches but OFW and emuMMC both don't boot. emuMMC gives a blue screen but OFW says "Failed to identify kernel. Failed to launch hos." I checked the backup on my PC and there are 29 rawnand.bin files and 25 to 28 are duplicates and have the exact same hash. I was sure my sysNAND was corrupted but I was able to boot into OFW through TegraExplorer and also using the reboot option from Hekate main menu. I have no clue what the problem is or how to fix it at this point. Any help would be appreciated.

 

[froggy55]

Complete noob here. I have weird problem with my modded switch and I tried a bunch of stuff but I'm stumped. I recently got my OLED switch modded and the person also set up Hekate for me on my SD card. I got an eMMC backup before doing anything else. Afterwards I tried updating Atmosphere using daybreak. That is when I got the blue screen of death. So now Hekate launches but OFW and emuMMC both don't boot. emuMMC gives a blue screen but OFW says "Failed to identify kernel. Failed to launch hos." I checked the backup on my PC and there are 29 rawnand.bin files and 25 to 28 are duplicates and have the exact same hash. I was sure my sysNAND was corrupted but I was able to boot into OFW through TegraExplorer and also using the reboot option from Hekate main menu. I have no clue what the problem is or how to fix it at this point. Any help would be appreciated.

update your hekate to the latest version also install latest sys patch and atmosphere 1.10 if your hekate is outdated the fuses wont match and you will get a kernal error what firmware are you on

 

[Hamburglar]

update your hekate to the latest version also install latest sys patch and atmosphere 1.10 if your hekate is outdated the fuses wont match and you will get a kernal error what firmware are you on

I'm using atmosphere-1.10.0-prerelease hekate_ctcaer_6.4.2_Nyx_1.8.2 and Hekate+AMS-package3-sigpatches-1.9.5P-cfw-20.5.0_V0 However I'm on 21.0.1 firmware. No fuse mismatch.

 

[froggy55]

I'm using atmosphere-1.10.0-prerelease hekate_ctcaer_6.4.2_Nyx_1.8.2 and Hekate+AMS-package3-sigpatches-1.9.5P-cfw-20.5.0_V0 However I'm on 21.0.1 firmware. No fuse mismatch.

you need to use the latest sys patch for atmosphere 1.10 its 1.5.8v5 and either remove the sigpatches you have as they are aout of date here are the latest sig patches and syspatch i use these together and everything works fine

 

[Hamburglar]

you need to use the latest sys patch for atmosphere 1.10 its 1.5.8v5 and either remove the sigpatches you have as they are aout of date here are the latest sig patches and syspatch i use these together and everything works fine

Thank you for the sigpatches! Unfortunately, I still get the same error.

 

[vador]

i have an OLED with an annoymous S/N (donated motherboard) which I don't have the prod.keys (see the error on secure boot key and device key) to recover hence is permanently ban. I can't use the Nintendo servers to update the firmware will get the 2123/2153 error.

Anyhow I have update to firmware 21.0.1 via daybreaker both SYSMMC (semi-stock and cfw) and EMUMMC. However, I can't boot to OFW since I get blackscreen which I think is due to fuse mistmatch. How can I force a fuse burn so that OFW boots?

 

[mtgforger]

What's everyone using these days to install NSP backups? My outdated DBI 658 crashes on the latest Atmosphere and with the dev having injected malicious code into the tool apparently I would rather move away from it entirely. The MTP responder was the only feature of it that I ever used.

 

[Hayato213]

i have an OLED with an annoymous S/N (donated motherboard) which I don't have the prod.keys (see the error on secure boot key and device key) to recover hence is permanently ban. I can't use the Nintendo servers to update the firmware will get the 2123/2153 error.

Anyhow I have update to firmware 21.0.1 via daybreaker both SYSMMC (semi-stock and cfw) and EMUMMC. However, I can't boot to OFW since I get blackscreen which I think is due to fuse mistmatch. How can I force a fuse burn so that OFW boots?

View attachment 543513

What is sysnand firmware?

 

[vador]

What is sysnand firmware?

So I have updated to 21.0.1 with daybreaker. Both semi-stock and sysnand boot but not the OFW (blackscreen). Also if I am in semi-stock for a few minutes I get the 2123-0011

 

[Hayato213]

So I have updated to 21.0.1 with daybreaker. Both semi-stock and sysnand boot but not the OFW (blackscreen). Also if I am in semi-stock for a few minutes I get the 2123-0011

Your fuse and firmware doesn't match if you are on 21.0.1 on sysnand.

 

[vador]

Your fuse and firmware doesn't match if you are on 21.0.1 on sysnand.

Hayato thank for helping!

I have the latest HATS release (HATS-21112025-00b00fd.zip) so it has the fuse.bin for 21.0.0 (includes the Atmosphère 1.10.0 ). Before I read your comment I restored the firmware 21.0.1 with my prod.keys using the EMMCHaccGen to create the package and then TegraExplore to restore it (followed this procedure Switch Unbrick Guide - Such Meme, Many Skill's Dumping Ground).

Current state change:
- OFW and SYSMMC (Semi-Stock): before total black screen - now stuck on nintendo switch logo
- SYSMMC (CFW): before would boot - now black screen
- EMUMMC: working well as usual (expected didn't touch it).

Do you think that the fuse for 21.0.1 will be different than for the 21.0.0 ? If so I am stuck until a release by Atmosphere.

 

[Earthshine]

What's everyone using these days to install NSP backups? My outdated DBI 658 crashes on the latest Atmosphere and with the dev having injected malicious code into the tool apparently I would rather move away from it entirely. The MTP responder was the only feature of it that I ever used.

I have been using Sphaira with (almost) no issues. Only files that currently wont install with it are ones compressed to nsz with a compression level of 22.

 

[Hayato213]

Hayato thank for helping!

I have the latest HATS release (HATS-21112025-00b00fd.zip) so it has the fuse.bin for 21.0.0 (includes the Atmosphère 1.10.0 ). Before I read your comment I restored the firmware 21.0.1 with my prod.keys using the EMMCHaccGen to create the package and then TegraExplore to restore it (followed this procedure Switch Unbrick Guide - Such Meme, Many Skill's Dumping Ground).

Current state change:
- OFW and SYSMMC (Semi-Stock): before total black screen - now stuck on nintendo switch logo
- SYSMMC (CFW): before would boot - now black screen
- EMUMMC: working well as usual (expected didn't touch it).

Do you think that the fuse for 21.0.1 will be different than for the 21.0.0 ? If so I am stuck until a release by Atmosphere.

Well the thing is the fuse is burnt when you boot into OFW or Sysnand CFW on an OLED, sound like problem with NAND.

 

[vador]

Well the thing is the fuse is burnt when you boot into OFW or Sysnand CFW on an OLED, sound like problem with NAND.

For sure. Do you know any other option I could try to recover it?

 

[darelphilip]

Yeah, I just updated to 1.11.0 a day or two ago, it came out last week. I was previously on 1.10.2. The base game is only like 34mb and the update file is 3 or 4gb, requires the update to play. Either way currently on 1.11.0. I'll try updating to 18.1.0 tonight, is sys-patch the same process as installing sigpatches?

my wife was happy enjoying the 1.11.0 when i thought to give her something additional with dlcs and updated it to latest version, dumb me. now all links are dead.. would you be kind to share the 1.11.0 link

 

[TheJinKazama]

Hi,

I have an original switch (RCM jig type) which I am selling. I haven't used it for some time but I can confirm that I can still boot into the version of software which allows for playing backup games. How do I prepare it for sale so as to maintain this but remove all personal details? I intend on keeping the SD card for myself.

Thanks

 

[vador]

For sure. Do you know any other option I could try to recover it?

Well the thing is the fuse is burnt when you boot into OFW or Sysnand CFW on an OLED, sound like problem with NAND.

I finally managed to fix my console.

The issue was the PRODINFO partition, which was damaged on the sysnand. I used TegraExplore to copy the PRODINFO from the emummc to the sysnand. After that, the firmware booted normally.

I still get the usual 2123-0011 error, but I added a DNS redirect that points all Nintendo servers to localhost. With that in place, it no longer crashes in Semi-stock or CFW. On the official firmware, it still crashes if I try to go online, but that is fine. I also use a donor prod keys to install a game cert so I can play cards (even if I don't do that much).

I now have a stable sysmmc that I can always clone to emummc. The console is banned and in a strange way. Someone (previous owner of this motherboard which was cheap and I knew it) anonymised the serial number, so it cannot update software through official channels. I have to use Daybreak for updates. But for local gaming works-flawless and I never play online so is perfect.