Hacking SWITCH NOOB PARADISE - Ask questions here

[Nintendai1]

This means I can keep my wifi on when using emummc cfw(fusee)?

 

[Game_Fr3akz]

Use Disk Manager to remove all partitions. make a new single partition. Format the partition to FAT32 using Rufus.

This can do all steps in one tool: https://www.partitionwizard.com/free-partition-manager.html

This can do it too: https://www.aomeitech.com/aomei-partition-assistant.html

Thank you

 

[binkinator]

Yes, they were all indeed green.

I'll do this right now.

It is correctly named "exosphere.ini".

Great. Follow the second test in the link to see if your serial number is zeroed out.

 

[Nintendai1]

Great. Follow the second test in the link to see if your serial number is zeroed out.

I'll do this immediately.

 

[Nintendai1]

Yes, although I had to download some other exosphere.ini config file from some youtube tutorials. But it does work, shows XAW0000s.

 

[binkinator]

Yes, although I had to download some other exosphere.ini config file from some youtube tutorials. But it does work, shows XAW0000s.

great! Your switch is officially not talking to Ninty (as far as we can possibly know…)

 

[bupeapoop]

How often should I update CFW? That being Hekate, Atmosphere and fusee?

Last I heard, there is a new update. This is the first time ever needing to make a necessary update.

Is this guide HERE in this link, it instructs you on how to update/upgrade.

Thanks and I look forward to hearing from you.

 

[Draxzelex]

How often should I update CFW? That being Hekate, Atmosphere and fusee?

Last I heard, there is a new update. This is the first time ever needing to make a necessary update.

Is this guide HERE in this link, it instructs you on how to update/upgrade.

Thanks and I look forward to hearing from you.

That depends on you. Are you a person who likes being on the bleeding edge of software? Or are you someone who only updates when its absolutely necessary? The only time when you will need to update your CFW is if you update to a firmware that isn't supported by your current version of CFW. Other cases include when you want to try a new feature that is implemented. Anyways, I don't understand the point of a guide for updating CFW when its just downloading the new files & putting them on your SD card. Its the same steps as when you first setup CFW except that you're just updating the files.

 

[ivangeek999]

I updated the atmosphere version to 14.0.0 yesterday. Today when I went to download a game via nsp it worked but when I tried to open the game it said I couldn't play because "I didn't buy the software"

What Can I Do ?

 

[Draxzelex]

I updated the atmosphere version to 14.0.0 yesterday. Today when I went to download a game via nsp it worked but when I tried to open the game it said I couldn't play because "I didn't buy the software"View attachment 303571
What Can I Do ?

When you updated your firmware, did you update your ES, FS, & Loader patches? Those also need to be updated whenever you update your firmware alongside your CFW. If you haven't downloaded the latest patches, you can download them from here.

 

[bupeapoop]

That depends on you. Are you a person who likes being on the bleeding edge of software? Or are you someone who only updates when its absolutely necessary? The only time when you will need to update your CFW is if you update to a firmware that isn't supported by your current version of CFW. Other cases include when you want to try a new feature that is implemented. Anyways, I don't understand the point of a guide for updating CFW when its just downloading the new files & putting them on your SD card. Its the same steps as when you first setup CFW except that you're just updating the files.

Thanks for the swift response @Draxzelex . No, I'm not someone who plays my Switch all day, everyday. All I want is to ensure is that I can play my Switch on the weekend without any issues. If I can get away without updating, that's what I'd do. If, however, I need to need to update to ensure I can continuously play without issue, then I'm happy to update.]

Do you recommend that I update if it's as easy as copying/pasting files? For someone like myself that's a casual gamer, and not a hardcore gamer, what do you recommend?

 

[Draxzelex]

Thanks for the swift response @Draxzelex . No, I'm not someone who plays my Switch all day, everyday. All I want is to ensure is that I can play my Switch on the weekend without any issues. If I can get away without updating, that's what I'd do. If, however, I need to need to update to ensure I can continuously play without issue, then I'm happy to update.]

Do you recommend that I update if it's as easy as copying/pasting files? For someone like myself that's a casual gamer, and not a hardcore gamer, what do you recommend?

Typically, updating CFW is not required at all to play your Switch without issues. As I said, you only ever need to update CFW if you update to a firmware past what your current CFW version supports. And you'd only ever need to update your firmware if a game or other content requires a higher firmware than you are currently on. I don't know how often you update your firmware or your other habits so I cannot make a recommendation on what you should personally do. This is why you should make your own informed decision based on the information I & others give you.

 

[binkinator]

Thanks for the swift response @Draxzelex . No, I'm not someone who plays my Switch all day, everyday. All I want is to ensure is that I can play my Switch on the weekend without any issues. If I can get away without updating, that's what I'd do. If, however, I need to need to update to ensure I can continuously play without issue, then I'm happy to update.]

Do you recommend that I update if it's as easy as copying/pasting files? For someone like myself that's a casual gamer, and not a hardcore gamer, what do you recommend?

it’s as easy as the three steps stated in the guide.

Literally this:

What you'll need:

• Hekate
• Atmosphere
• fusee
  • Only download this if you are using fusee.bin.
• Sigpatches

Steps:

1. Extract the following files to your SD card:
   • atmosphere-x.xx.x-master-xxxxxxxx+hbl-x.x.x+hbmenu-x.x.x.zip
   • hekate_ctcaer_x.x.x_Nyx_x.x.x.zip
   • SigPatches.zip
2. When asked to overwrite any files, click Yes.
3. Move fusee.bin to /bootloader/payloads/.
   • If you inject fusee.bin with a payload injector, then update the payload on your injector.

…as for timing, if you just want to play games, play them until one of the games you’re wanting to play insists that’s you upgrade.

As an example, here’s the requirements for a recently released game…release this weekend…requires 11.0.0.

You’re on 13.2.1…you’re safe from upgrades for a very long time. It will be a very long time until a game requires 14.0.0 so people upgrading now are doing it for the Groups feature (a kinda weak ass feature if you ask me) as opposed to upgrading just to play games.

 

[ivangeek999]

When you updated your firmware, did you update your ES, FS, & Loader patches? Those also need to be updated whenever you update your firmware alongside your CFW. If you haven't downloaded the latest patches, you can download them from

Is the link right? Is that he led to a post about a post of "Switch rebooting always to Hekat instead of Atmosphere"

 

[binkinator]

Is the link right? Is that he led to a post about a post of "Switch rebooting always to Hekat instead of Atmosphere

https://gbatemp.net/goto/post?id=9781284

Draxzelex said:
Do you have the ES, FS, & Loader patches? If not, download them from this thread…

*shit @Draxzelex I thought you logged off. My bad.

 

[Draxzelex]

Is the link right? Is that he led to a post about a post of "Switch rebooting always to Hekat instead of Atmosphere"

My bad, this is the proper link.

 

[donnyp]

I just finished up my jailbreak and everything seems to be working fine. I have all the apps installed that I need. I'm just unsure about my boot process. When creating my hekate_ipl.ini, it shows as the following.....

[config] autoboot=0 autoboot_list=0 autohosoff=0 autonogc=1 backlight=100 bootwait=3 updater2p=0 bootprotect=0 [CFW (sysMMC)] emummc_force_disable=1 fss0=atmosphere/package3 icon=bootloader/res/icon_payload.bmp [CFW (emuMMC)] emummcforce=1 fss0=atmosphere/package3 icon=bootloader/res/icon_payload.bmp [Stock] emummc_force_disable=1 fss0=atmosphere/package3 icon=bootloader/res/icon_switch.bmp stock=1 [Fusee] icon=bootloader/res/icon_payload.bmp payload=bootloader/payloads/fusee.bin

Current version 13.2.1 with AMS 1.2.6 and SigPatches to match.

Now when I'm presented with the Hekate launch screen I have 4 options. With sigpatches loaded I've been using Fusee, as when reading the readme from the main github, its was recommended to use that payload style for compatible if I remember correctly.

Would any option work for my current sigpatches? Would their be an easier way then having 4 different versions on launch screen? I setup an emuMMC as a partition if that matters.

Thanks!

 

[ivangeek999]

Thanks!

My bad, this is the proper

 

[Draxzelex]

I just finished up my jailbreak and everything seems to be working fine. I have all the apps installed that I need. I'm just unsure about my boot process. When creating my hekate_ipl.ini, it shows as the following.....

[config] autoboot=0 autoboot_list=0 autohosoff=0 autonogc=1 backlight=100 bootwait=3 updater2p=0 bootprotect=0 [CFW (sysMMC)] emummc_force_disable=1 fss0=atmosphere/package3 icon=bootloader/res/icon_payload.bmp [CFW (emuMMC)] emummcforce=1 fss0=atmosphere/package3 icon=bootloader/res/icon_payload.bmp [Stock] emummc_force_disable=1 fss0=atmosphere/package3 icon=bootloader/res/icon_switch.bmp stock=1 [Fusee] icon=bootloader/res/icon_payload.bmp payload=bootloader/payloads/fusee.bin

Current version 13.2.1 with AMS 1.2.6 and SigPatches to match.

Now when I'm presented with the Hekate launch screen I have 4 options. With sigpatches loaded I've been using Fusee, as when reading the readme from the main github, its was recommended to use that payload style for compatible if I remember correctly.

Would any option work for my current sigpatches? Would their be an easier way then having 4 different versions on launch screen? I setup an emuMMC as a partition if that matters.

Thanks!

There's actually no reason to use fusee unless you're a purist. Hekate not only works as well but is better than fusee. As long as you downloaded your patches from here, you will have patches for both Hekate & fusee. If you want less options, you will have to remove them from your hekate_ipl.ini file which you just listed.

 

[binkinator]

I just finished up my jailbreak and everything seems to be working fine. I have all the apps installed that I need. I'm just unsure about my boot process. When creating my hekate_ipl.ini, it shows as the following.....

[config]
autoboot=0

you can set autoboot to the stanza you want to autoboot. 0 is off and 1-4 are for the 4 stanzas you have below. I would set it to 2 or 4.

autoboot_list=0
autohosoff=0
autonogc=1
backlight=100
bootwait=3

bootwait can be reduced to 1 so you get a faster boot time. 1 second is plenty of time to press (vol -) to stop the boot and manually chose (kinda like F2 on your PC BIOS)

updater2p=0
bootprotect=0

[CFW (sysMMC)]

1) This one boots Atmosphere on your stock Sysnand

emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]

2) This one boots Atmosphere on your emulated nand. I would make this or 4 your autoboot=.

emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]

3) This one boots bone stock with no CFW on your stock Sysnand

emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]

4) This one boots CFW on emunand (implied). It‘s using fusee direct rather than fss0 mode. Otherwise identical to stanza 2. Make this or 2 your autoboot=.

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

Current version 13.2.1 with AMS 1.2.6 and SigPatches to match.

perfect….good for a very long time.

Now when I'm presented with the Hekate launch screen I have 4 options. With sigpatches loaded I've been using Fusee, as when reading the readme from the main github, its was recommended to use that payload style for compatible if I remember correctly.

4 options are fine…set autoboot=2 and you’ll skip right by this and boot up unless you press (vol -)

Would any option work for my current sigpatches? Would their be an easier way then having 4 different versions on launch screen? I setup an emuMMC as a partition if that matters.

Nope, you’re good to go.

Thanks!