Hacking SWITCH NOOB PARADISE - Ask questions here

[Crowla33R]

The only negative repercussion I can think of is that you will never ever be able to recover that emuMMC to use with SX OS ever again.

Would there be a reason for me to want to use SXOS again in the future? I read they don't update those anymore, right?

So can I just delete the SXOS folder via USB in MTP responder?

 

[Ghostplane64]

no worries. Can you try spamming the (Vol -) button after you boot up? It should drop you into Hekate.

e: Are you injecting Hekate.x.x.x.bin or fusee.bin? What are you using to inject?

I'm using fusse.bin as a payload and tegrarcmgui as the injector. I have Hekate.x.x.x.bin on my switch's sd card as well.

Post automatically merged: Feb 11, 2023

I'm using fusse.bin as a payload and tegrarcmgui as the injector. I have Hekate.x.x.x.bin on my switch's sd card as well.

I just reread the guide and I feel so stupid. I think I'm suppose to use Hekate.x.x.x.bin as the injector right?

 

[Crowla33R]

You need to take it out if you are unsure, well atleast you can figure it out if it hidden by calculating the given space by the sd card, the emummc take up about 30 GB if you have hidden partition.

I don't see any emummc folder when looking inside my micro SD via MTP responder of DBI, and the used storage already added up to 128gb.

I want to know if I'd need to back up anything from my SD card in case it become unusable in future. Assuming I don't back them up, and have to buy new micro SD, will I be able to start fresh or do I need something from the current SD card (aka would it would be impossible for me to start CFW anew without some backup files from old SD)?

 

[binkinator]

I'm using fusse.bin as a payload and tegrarcmgui as the injector. I have Hekate.x.x.x.bin on my switch's sd card as well.

Post automatically merged: Feb 11, 2023

I just reread the guide and I feel so stupid. I think I'm suppose to use Hekate.x.x.x.bin as the injector right?

you can boot fusee.bin but I personally like to use Hekate to have a bit more control during boot.

 

[albedo4444]

get your Sigpatches here!

e: can you please cause the error again and take a screenshot? There is additional information on that page that will help troubleshoot.

Will do, and here's the screenshot (pokemon arceus if it helps

Have you tried to extract the NSZ files to NSP, then install. Some installers won't install NSZ.

Thanks, I'll keep that in mind (I could swear I've installed NSZs using awoo before, but still worth a try)

 

[Ghostplane64]

you can boot fusee.bin but I personally like to use Hekate to have a bit more control during boot.

God, I thought I fucked up something after updating my files, thank you man for putting up with my incompetence.

 

[binkinator]

Will do, and here's the screenshot (pokemon arceus if it helps

Let’s try this:

temporarily move /atmosphere/contents to /atmosphere/contents.bk and reboot. Then delete and reinstall the game and try to play it again.

(this ensures there are no sysmodules or cheats or what have you impacting the game’s boot process)

 

[The13thVessel]

please post the contents of your /bootloader/hekate_ipl.ini

Post automatically merged: Feb 11, 2023

I mean that your hekate_ipl.ini looks great.

now that I have explained myself, please post a screenshot of your emmc tab.

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

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

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

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

 

[binkinator]

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

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

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

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

Everything looks good here.


Is your SDCard formatted as exfat or FAT32?

Do you see any strange file/folder names when you put the SDCard in your PC?


Let’s try this:

temporarily move /atmosphere/contents to /atmosphere/contents.bk and reboot. Then delete and reinstall the game and try to play it again.

(this ensures there are no sysmodules or cheats or what have you impacting the game’s boot process)

 

[Hayato213]

I don't see any emummc folder when looking inside my micro SD via MTP responder of DBI, and the used storage already added up to 128gb.

I want to know if I'd need to back up anything from my SD card in case it become unusable in future. Assuming I don't back them up, and have to buy new micro SD, will I be able to start fresh or do I need something from the current SD card (aka would it would be impossible for me to start CFW anew without some backup files from old SD)?

Usually you want to back up you nand backup

 

[The13thVessel]

Everything looks good here.


Is your SDCard formatted as exfat or FAT32?

Do you see any strange file/folder names when you put the SDCard in your PC?


Let’s try this:

temporarily move /atmosphere/contents to /atmosphere/contents.bk and reboot. Then delete and reinstall the game and try to play it again.

(this ensures there are no sysmodules or cheats or what have you impacting the game’s boot process)

It's FAT32, I tried doing what you said but it keeps sending me to a black screen, about the folders I don't see nothing unusual but I'll upload an image just in case

 

[binkinator]

It's FAT32, I tried doing what you said but it keeps sending me to a black screen, about the folders I don't see nothing unusual but I'll upload an image just in case

No recent upgrades to FW or Atmosphere?

what versions (FW, AMS, Hekate) are you on?

Please go into Hekate and hit the eMMC tab on the right and take a screen shot and post,that screen here.

here are two easy things to try:

Sometimes when handling the Switch's SD card files, some of the files can get their Archive bit removed automatically, which may cause the Switch to no longer recognize said files (like the ones inside the Nintendo folder). This can happen when handling the SD's data in other OS, like Linux or Mac (and sometimes even on Windows too).

This can be easily resolved by fixing the archive bit on the files on the SD card.
Fixing that archive bit with Hekate 5.3.3 or above (Under the "Tools" option) effectively restores said bit to all your SD Card's files for Switch usage.

Sometimes having a Switch just refuses to boot can be fixed by booting into Maintenance mode without doing anything else. To access Maintenance mode:

• Power off your console
• Get your payloads ready to inject
• When injecting the payload, press and hold volume + and - (when booting the console up).
• Once you reach the Maintenance Mode menu, reboot the console.
• Boot normally as you would to play

 

[fadafwet]

Hi

Atmosphere seem to come with a payload called fusee, but everyone is talking about hekate as a payload which is the one I use
Are these 2 payloads that basically do the same operation ?
Can anyone tell me the difference and what are the pro and cons of them ?

thank you

 

[The13thVessel]

No recent upgrades to FW or Atmosphere?

what versions (FW, AMS, Hekate) are you on?

Please go into Hekate and hit the eMMC tab on the right and take a screen shot and post,that screen here.

here are two easy things to try:

I'm on 15.0.1, Hekate 6.0.1 and the latest atmosphere, tried doing the archive bit but it's the same.

 

[Draxzelex]

Would there be a reason for me to want to use SXOS again in the future? I read they don't update those anymore, right?

So can I just delete the SXOS folder via USB in MTP responder?

SX OS is still the only CFW that can mount .XCI files without installing them which some people refuse to give up even if the latest supported firmware is 11.0. If you don't care about that functionality, you can delete it via USB in MTP responder.

Hi

Atmosphere seem to come with a payload called fusee, but everyone is talking about hekate as a payload which is the one I use
Are these 2 payloads that basically do the same operation ?
Can anyone tell me the difference and what are the pro and cons of them ?

thank you

Both Fusee and Hekate are payloads that launch Atmosphere. The difference lies in Hekate's additional functionality as a toolbox that is useful to everyone in some way, shape, or form. The only usefulness of Fusee is that its Atmosphere's default method of booting so you don't have to wait for it to be updated when Atmosphere is updated unlike Hekate. However, Hekate is usually also updated within the same day Atmosphere is updated. Also, some people prefer the fact that all it does is boot Atmosphere; it doesn't require additional input unlike a default setup with Hekate although you can setup Hekate that it automatically boots into Atmosphere.

Long story short, Hekate is objectively superior to Fusee unless you're an Atmosphere purist.

 

[binkinator]

I'm on 15.0.1, Hekate 6.0.1 and the latest atmosphere, tried doing the archive bit but it's the same.

Great. Your emummc is enabled.

Ok, let’s add another stanza to your /bootloader/hekate_ipl.ini and try booting it.

dowload fusee.bin from the official Atmosphere release page and place it in /bootloader/payloads/

[CFW - fusee]
payload=/bootloader/payloads/fusee.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

try to boot CFW-Fusee

 

[The13thVessel]

Great. Your emummc is enabled.

Ok, let’s add another stanza to your /bootloader/hekate_ipl.ini and try booting it.

dowload fusee.bin from the official Atmosphere release page and place it in /bootloader/payloads/

[CFW - fusee]
payload=/bootloader/payloads/fusee.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

try to boot CFW-Fusee

I may found what the issue maybe????? Because I resized the sd card before installing games yestarday, so it may have erased the partition that housed the emuCC?

 

[binkinator]

I may found what the issue maybe????? Because I resized the sd card before installing games yestarday, so it may have erased the partition that housed the emuCC?

That’s an important bit of info for sure. Do you still have a 30G partition available? We can use Helate to create a new one if you do.

 

[The13thVessel]

That’s an important bit of info for sure. Do you still have a 30G partition available? We can use Helate to create a new one if you do.

I'm trying creating it right now, if it resolves I'll inform you!

 

[binkinator]

I'm trying creating it right now, if it resolves I'll inform you!

Awesome! This would absolutely explain your symptoms so I’m feeling pretty good about it. GL!