Hacking SWITCH NOOB PARADISE - Ask questions here

UltraSyko

Well-Known Member
Newcomer
Joined
Aug 14, 2019
Messages
63
Trophies
0
Age
25
XP
485
Country
United States
I wanted to dump my legal library and my emunand is so outdated. So many updates and DLC I can't play. Plus my cartridge of Ultimate does not work on emunand. I constantly get a cartridge error.
 

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,617
Trophies
1
XP
20,447
Country
United States
Hi all,

I need to update the firmware of my Switch again. I did it before as described above.

Currently installed firmware:
8.1.0 ReiNX(3.0)

10.1.0 is the latest firmware I can install, correct? Can I perform the same steps as I did before?

Latest is 11.0.1, and ReiNX doesn't support 11.0.1, you should switch over to Atmosphere, use Daybreak to update to 11.0.1.
 
  • Like
Reactions: phazer and BigOnYa

BigOnYa

Has A Very Big
Member
Joined
Jan 11, 2021
Messages
3,130
Trophies
1
Age
50
XP
7,372
Country
United States
Any quick way? I don't find that a good solution to my issue honestly. Not a fan of duplicating library. I don't fear getting banned. I don't install pirated nsps or cheat
Then why bother with emunand, or CFW, just run your normal OFW on sysnand. Using any homebrew or even running CFW you risk being banned. I don't use emunand or play online at all, so not sure the route to fix your emunand issue tho, other than update it, or delete n create new one. But good luck, plenty of info here if you search thru forums/tutorials for emunand.
 
Last edited by BigOnYa,

UltraSyko

Well-Known Member
Newcomer
Joined
Aug 14, 2019
Messages
63
Trophies
0
Age
25
XP
485
Country
United States
I play with mods. I overclock. I play homebrew apps. I use emulators. None of my friends got banned and they use sys cfw. My original question here is why does sys cfw crash and how can I possibly fix it. But it just shifted into questions on my preference.
 
Last edited by UltraSyko,

JS1025

Member
Newcomer
Joined
Apr 13, 2019
Messages
13
Trophies
0
Age
39
XP
72
Country
United States
Hey, so I recently updated my firmware to 11.0.1 without knowing it was a bad idea. It has been a long time since using the switch so I decided to start over. I got sx os installed and created the emunand and it is enabled and everything but I believe I am forgetting some step somewhere. When I try to load the cfw, the screen goes black after the nintendo logo. Thanks again for any help
 
Last edited by JS1025,

phazer

Well-Known Member
Member
Joined
Nov 17, 2006
Messages
116
Trophies
1
XP
406
Country
Antigua and Barbuda
Thanks! I mentioned 10.1.0 with regard to ReiNX.

I will look for a guide to switch to Atmosphere and look into Daybreak.

It looks like, that I could use some support.

I copied the latest Atmosphere files to the SD card and removed ReiNX files from it.
I can enter Hekate (latest release) through RCM.

What do I have to do next? Should I launch 'CFW' or do I have to chainload other payloads to launch Atmosphere?
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
Hey, so I recently updated my firmware to 11.0.1 without knowing it was a bad idea. It has been a long time since using the switch so I decided to start over. I got sx os installed and created the emunand and it is enabled and everything but I believe I am forgetting some step somewhere. When I try to load the cfw, the screen goes black after the nintendo logo. Thanks again for any help
SX OS does not support firmware 11.0.1 You will have to use Atmosphere instead as it has been a month since 11.0.1 was released and TX still hasn't released an update.

It looks like, that I could use some support.

I copied the latest Atmosphere files to the SD card and removed ReiNX files from it.
I can enter Hekate (latest release) through RCM.

What do I have to do next? Should I launch 'CFW' or do I have to chainload other payloads to launch Atmosphere?
Either option is fine. The only difference is launching directly from Hekate, which is called fss0, requires the fss0 patches to launch backups whereas chainloading into fusee_primary uses the fusee patches instead.
 
Last edited by Draxzelex,

phazer

Well-Known Member
Member
Joined
Nov 17, 2006
Messages
116
Trophies
1
XP
406
Country
Antigua and Barbuda
Either option is fine. The only difference is launching directly from Hekate, which is called fss0, requires the fss0 patches to launch backups whereas chainloading into fusee_primary uses the fusee patches instead.

Thank you. Launch backups means installed .nsp files? I still did not get the difference between fss0 patches and fusee patches. It looks like, that I have to read more documention :)

Using Launch 'CFW' results in:
No mandatory secmon or warmboot provided!
Failed to launch HOS!
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
Thank you. Launch backups means installed .nsp files? I still did not get the difference between fss0 patches and fusee patches. It looks like, that I have to read more documention :)

Using Launch 'CFW' results in:
No mandatory secmon or warmboot provided!
Failed to launch HOS!
You can read up on it here but to keep it short, there are 2 types of FS patches and these differ based on which bootloader you use to launch Atmosphere: Hekate/fss0 and fusee_primary.

As for your new issue, where did you download your Hekate and Atmosphere files from?
 

JS1025

Member
Newcomer
Joined
Apr 13, 2019
Messages
13
Trophies
0
Age
39
XP
72
Country
United States
SX OS does not support firmware 11.0. You will have to use Atmosphere instead as it has been a month since 11.0.1 was released and TX still hasn't released an update.

Either option is fine. The only difference is launching directly from Hekate, which is called fss0, requires the fss0 patches to launch backups whereas chainloading into fusee_primary uses the fusee patches instead.
Thanks for the reply. I went back to 11.0.0 after that to see what happened and it still didn't work. A video I watched said 11.0.0 is fine but 11.0.1 doesn't work yet which is what had me confused. What is the latest one I will be able to use? Appreciate the help
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
Thanks for the reply. I went back to 11.0.0 after that to see what happened and it still didn't work. A video I watched said 11.0.0 is fine but 11.0.1 doesn't work yet which is what had me confused. What is the latest one I will be able to use? Appreciate the help
My apologies. There was a bit of a typo in my original post. What I meant to say is that SX OS does not support firmware 11.0.1. I have just now rectified that to avoid further confusion.

Now to answer your question, SX OS currently supports up to firmware 11.0. If it is not working, make sure your SD card is formatted as FAT32 and that you have the latest boot.dat on your SD card.
 

phazer

Well-Known Member
Member
Joined
Nov 17, 2006
Messages
116
Trophies
1
XP
406
Country
Antigua and Barbuda
I think I've just about identified the issue but I want to be 100% certain. If you don't mind, can you either upload your hekate_ipl.ini file or maybe post whatever is inside of there on here?

[config]
autoboot=0
autoboot_list=0
bootwait=5
customlogo=1
verification=2
backlight=100
autohosoff=0

{tumGER/SDFilesSwitch v10.1}
{ }
{Discord: https://discord.gg/qbRAuy7}
{ }

{-- Custom Firmwares --}
[CFW]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
kip1=modules/required/fs_mitm.kip
secmon=modules/required/exosphere.bin
kip1patch=nosigchk
atmosphere=1
{ }

{---- Miscellaneous ---}
[Stock]
[No LayeredFS]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
secmon=modules/required/exosphere.bin
kip1patch=nosigchk
atmosphere=1
{ }
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
[config]
autoboot=0
autoboot_list=0
bootwait=5
customlogo=1
verification=2
backlight=100
autohosoff=0

{tumGER/SDFilesSwitch v10.1}
{ }
{Discord: https://discord.gg/qbRAuy7}
{ }

{-- Custom Firmwares --}
[CFW]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
kip1=modules/required/fs_mitm.kip
secmon=modules/required/exosphere.bin
kip1patch=nosigchk
atmosphere=1
{ }

{---- Miscellaneous ---}
[Stock]
[No LayeredFS]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
secmon=modules/required/exosphere.bin
kip1patch=nosigchk
atmosphere=1
{ }
To be honest, I was expecting a blank hekate_ipl.ini file. So by the looks of it, your hekate_ipl.ini file is highly outdated because its referring to a pack that no longer exists (SDFiles was eventually renamed to Kosmos but that was discontinued a while ago). You now have 2 options: you can either edit the file yourself or find another pre-configured file. I'm guessing you would prefer the latter so I will give you 2 more options to pick from. You can get one from DeepSea which is a spiritual successor to Kosmos (or SDFiles in your case) or, and this is the one I recommend, download a hekate_ipl.ini file from SDSetup. The reason I prefer SDSetup is that it lets me choose what files and tools I want to download then use unlike DeepSea which floods me with a lot of unnecessary bloat. Either way, both of them will give you a setup of Hekate that can boot into Atmosphere.
 
  • Like
Reactions: phazer

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Sorry for accidentally bending over