Hacking SWITCH NOOB PARADISE - Ask questions here

[Gamemaster1379]

I had my Switch sitting in sleep mode, docked, on Atmosphere in emuNAND on 13.2.1 The sysNAND is also 13.2.1 (though that shouldn't matter).

I recently had to restart my Switch. After I restarted it, the Switch, whenever it boots using Atmosphere into emuNAND, shows the Atmosphere logo, then the Switch logo, and then a black screen.

Although the screen is black, I can still access things like the power menu.

I made no system changes nor CFW changes before rebooting. I just rebooted. What happened and how do I fix it? Is my emuNAND corrupt?

If it is corrupt, am I able to back up my saves? I didn't back them up using Checkpoint before hand.

 

[vendettared]

I updated my brother's switch with the latest available atmosphere (by replacing the corresponding folders) and FW (using daybreak) and when I turn on the switch, I get the Fatal Error "Failed to state stage2 (atmosphere/fusee-secondary.bin).

I look into this problem and edited the "hekate_ipl.ini" and replaced all the names therein that has "fusee-seconday bin" to "package3" but it still shows the same error "Failed to state stage2 (atmosphere/fusee-secondary.bin)."

I tried everything I could but the same Error presents itself everytime

Also, I dont think my brother has ever used hekate before (or if he did, didnt notice) since he just launches straight into atmosphere (im fairly new to atmosphere myself so i definitely missed a step here). I updated hekate as well and it still has the same error.

Any help?

 

[Gamemaster1379]

^ Per above. I'm pretty sure my emuMMC is corrupt. I tried to mount with nxNandManager and supposedly backed up my Forgotten Land save.

Could I ask someone a massive favor and to check to see if my save works? https://www.mediafire.com/file/q7kk8vbv1oor0nu/0000000000000041_%5Bkirby_forgotten_land%5D.zip/file

Just a quick load in would be fantastic.

 

[Chaosta]

^ Per above. I'm pretty sure my emuMMC is corrupt. I tried to mount with nxNandManager and supposedly backed up my Forgotten Land save.

Could I ask someone a massive favor and to check to see if my save works? https://www.mediafire.com/file/q7kk8vbv1oor0nu/0000000000000041_%5Bkirby_forgotten_land%5D.zip/file

Just a quick load in would be fantastic.

if your sd card is exfat, thats probably why it corrupt. fat32 is best

 

[Gamemaster1379]

if your sd card is exfat, thats probably why it corrupt. fat32 is best

My storage partition is FAT32. Unclear if that means the emuMMC partition is also FAT32 or if it may be exFAT instead.

 

[Chaosta]

My storage partition is FAT32. Unclear if that means the emuMMC partition is also FAT32 or if it may be exFAT instead.

if you formatted the sd card to fat32 then yea your emunand would be fat32

 

[Gamemaster1379]

if you formatted the sd card to fat32 then yea your emunand would be fat32

Got a corrupted FAT32 partition then. Lame.
I imagine I probably went with FAT over exFAT at the time from the concerns around exFAT being unreliable.

 

[HelloShitty]

Yes, NSZ files work great with Tinfoil. Just compressed and installed one myself with nut.exe to make sure latest and greatest all work well together. They still do.

hmmm. Haven‘t had freezing.

Try just regular usb: instead of usbfs:

Do you have spaces in your folder names? Try getting the Organize Files feature working. It‘s what I use to normalize my game stash.

DBI is fantastic and absolutely handles NSZ files.
Tinwoo is another great installer that handles NSZs as well.

Nothing to stop you from trying other installers. We ain’t the installer police.

Loved that... ahahah. The installer police should be some kind of national saying! xD Sorry the offtopic!

 

[binkinator]

I updated my brother's switch with the latest available atmosphere (by replacing the corresponding folders) and FW (using daybreak) and when I turn on the switch, I get the Fatal Error "Failed to state stage2 (atmosphere/fusee-secondary.bin).

I look into this problem and edited the "hekate_ipl.ini" and replaced all the names therein that has "fusee-seconday bin" to "package3" but it still shows the same error "Failed to state stage2 (atmosphere/fusee-secondary.bin)."

I tried everything I could but the same Error presents itself everytime

Also, I dont think my brother has ever used hekate before (or if he did, didnt notice) since he just launches straight into atmosphere (im fairly new to atmosphere myself so i definitely missed a step here). I updated hekate as well and it still has the same error.

Any help?

Did you update your copy of fusee.bin? It’s in the same github release where you got atmosphere.

Heres a list of things that need to be done:
https://rentry.org/MigrateToAtmosphere1_0_0

* one change I recommend from this is

please ensure to delete copy your /contents/ folder located in /atmosphere/ to /atmosphere/contents.bak

having a backup copy of your sysmodules to copy from is easier than just reinstalling everything IMO

 

[vendettared]

How do I update the fusee.bin? Because I only placed the fusee.bin in the bootloader/payload, I didnt do anymore than that.

EDIT:

By the way,
I tried following this guide (posted on Dec. 2021) step-by-step but it didnt work. I still get the same error,

"- overwrite old Atmosphere content at SD root with new release (all the zip content : atmosphere, switch, and hbmenu.nro). This ensure you to keep previous configs, instead of deleting and reinstalling.
- overwrite old Hekate's "bootloader" folder at SD root with new release
- overwrite Atmosphere and/or Hekate's bootloader at SD root with the corresponding sigpatches's fusee.zip, based on the way you launch AMS (fusée or fss0). if you don't know, overwrite both. Attention, each new version of Atmosphere requires specific updated version of the patches. compare the "build hash" on the patch version against AMS zip package filename.
- copy Atmosphre's latest "fusee.bin" into sd:/bootloader/payloads/ folder
- copy sd:/bootloader/update.bin to a new file. Rename the copied file to "reboot_payload.bin", and move+overwrite it into Atmosphere folder. This will ensure you can reboot to Hekate from HB menu with "reboot to payload" app instead of rebooting AMS.
- verify if there's a new lockpick_RCM.bin released, and replace it in sd:/bootloader/payloads/ too."

However, the following part I'm not familiar with since my brother just uses a dongle to boot his switch.

"- Replace hekate_ctcaer_x.x.x.bin payload binary on your RCM booter/dongle/phone/chipset/computer/whatever you use to send payloads to RCM. But, this is unnecessary if your previous hekate is not too old, because it now always check if "update.bin" is newer and launch it instead. But I prefer having the correct one on my RCM device/dongle/app."

How exactly do I "Replace hekate_ctcaer_x.x.x.bin payload binary"??? Is this troubleshooting even relevant to my problem?

 

[binkinator]

How do I update the fusee.bin? Because I only placed the fusee.bin in the bootloader/payload, I didnt do anymore than that.

EDIT:

By the way,
I tried following this guide (posted on Dec. 2021) step-by-step but it didnt work. I still get the same error,

"- overwrite old Atmosphere content at SD root with new release (all the zip content : atmosphere, switch, and hbmenu.nro). This ensure you to keep previous configs, instead of deleting and reinstalling.
- overwrite old Hekate's "bootloader" folder at SD root with new release
- overwrite Atmosphere and/or Hekate's bootloader at SD root with the corresponding sigpatches's fusee.zip, based on the way you launch AMS (fusée or fss0). if you don't know, overwrite both. Attention, each new version of Atmosphere requires specific updated version of the patches. compare the "build hash" on the patch version against AMS zip package filename.
- copy Atmosphre's latest "fusee.bin" into sd:/bootloader/payloads/ folder
- copy sd:/bootloader/update.bin to a new file. Rename the copied file to "reboot_payload.bin", and move+overwrite it into Atmosphere folder. This will ensure you can reboot to Hekate from HB menu with "reboot to payload" app instead of rebooting AMS.
- verify if there's a new lockpick_RCM.bin released, and replace it in sd:/bootloader/payloads/ too."

However, the following part I'm not familiar with since my brother just uses a dongle to boot his switch.

"- Replace hekate_ctcaer_x.x.x.bin payload binary on your RCM booter/dongle/phone/chipset/computer/whatever you use to send payloads to RCM. But, this is unnecessary if your previous hekate is not too old, because it now always check if "update.bin" is newer and launch it instead. But I prefer having the correct one on my RCM device/dongle/app."

How exactly do I "Replace hekate_ctcaer_x.x.x.bin payload binary"??? Is this troubleshooting even relevant to my problem?

https://rentry.org/MigrateToAtmosphere1_0_0

(Im assuming you are on a V1 Erista…PLMK if that’s not the case.)

what type of dongle are you using to inject a payload while in RCM mode?

 

[vendettared]

I apologize but I have seem to forgotten the distinction between a Mariko and Erista.

I am using a "NS atmosphere dongle".

EDIT:
I reviewed what an Erista is and yes I have an Erista Switch.

I followed every step in "https://rentry.org/MigrateToAtmosphere1_0_0" and I still have the same ""Failed to state stage2 (atmosphere/fusee-secondary.bin)." when I boot the Switch.

 

[binkinator]

I apologize but I have seem to forgotten the distinction between a Mariko and Erista.

I am using a "NS atmosphere dongle".

EDIT:
I reviewed what an Erista is and yes I have an Erista Switch.

I followed every step in "https://rentry.org/MigrateToAtmosphere1_0_0" and I still have the same ""Failed to state stage2 (atmosphere/fusee-secondary.bin)." when I boot the Switch.

No worries. Please post your /bootloader/hekate_ipl.ini

 

[vendettared]

No worries. Please post your /bootloader/hekate_ipl.ini

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

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

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

 

[binkinator]

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

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

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

That’s as straight forward of an ini file as you’re going to get. I don’t see any issues.


Typically this is due to bootloader/payloads/fusee.bin not being updated. This error is specifically searching an old stage2 format that is no longer used. The newer stuff has noreference to fusee-primary.

Please double check that you are downloading a fresh copy of fusee.bin from the atmosphere GitHub page.

You‘re using this, right?

https://web.archive.org/web/20200629205538/http://www.ns-atmosphere.com/en/

And where it says Hekate 3.2.bin above your replaced it with Hekate 5.7.2.bin, correct?

 

[vendettared]

Typically this is due to bootloader/payloads/fusee.bin not being updated.

That’s as straight forward of an ini file as you’re going to get. I don’t see any issues.

You‘re using this, right?

https://web.archive.org/web/20200629205538/http://www.ns-atmosphere.com/en/


View attachment 306826

And where it says Hekate 3.2.bin above your replaced it with Hekate 5.7.2.bin, correct?

Uhh no, this is my first time seeing this lol.

My switch (using SXOS dongle) never needed this but I'm guessing my brother's switch (AMS dongle) will need to utilize this?

 

[binkinator]

Uhh no, this is my first time seeing this lol.

My switch (using SXOS dongle) never needed this but I'm guessing my brother's switch (AMS dongle) will need to utilize this?

The absolute surest-to-work thing I would recommend doing would be to start from a clean slate by moving /atmosphere to /atmosphere.bak and /bootloader to /bootloader.bak and then downloading fresh files from the links at the top of https://rentry.org/MigrateToAtmosphere1_0_0 and unzipping them to the top level of you sd card. Copy the hekate_ipl.ini from /bootloader.bak/ to /bootloader and reboot while injecting hekate_5.7.2.bin.

 

[vendettared]

The absolute surest-to-work thing I would recommend doing would be to start from a clean slate by moving /atmosphere to /atmosphere.bak and /bootloader to /bootloader.bak and then downloading fresh files from the links at the top of https://rentry.org/MigrateToAtmosphere1_0_0 and unzipping them to the top level of you sd card. Copy the hekate_ipl.ini from /bootloader.bak/ to /bootloader and reboot while injecting hekate_5.7.2.bin.

Well updating the dongle worked. It launched into hekate and I loaded the fusee.bin. Thank you! My 3 hours of troubelshooting aimless was not in vain.

 

[DJPlace]

hey guys how much would it cost to have a modchip installed on a nintendo switch lite? cause i want to edit save's and stuff since nintendo are asshole's and only let save's to the system... also i heard nintendo ban's for cloud save's for hacked switch's would that be true for modchip's has well. i don't know how to install a mod chip... so i would need help with that. so i'm wondering the cost for the modchip and install. let me know here.

 

[CassioAug]

Since there is probably around a year or more that I last updated my Swtich, I would like to make sure:

1) Should I just copy the latest Atmosphere files to the SD card, and then update the OFW?
2) Is OFW still being updated using ChoiDujourNX?
3) Is it safe to update OFW to 14.1.0? Or it isn't stable with the latest CFW yet?
4) And are sigpatches still necessary?