Hacking SWITCH NOOB PARADISE - Ask questions here

[impeeza]

Hey, I wanna update my Switch (running on atmosphere, all updated) on 9.1.0 to the newest FW.
Wanna avoid burning my fuses (originally still on 4.0.0) - should I still use ChoiDojourNX or is there any other, newer Homebrew?
Red about one a few days ago, forgot its name, tho

please read guides on how to update, a summary:

https://gbatemp.net/threads/firmware-and-nand-questions.612782/post-9835101

 

[VIERcntHOLZ]

Use Atmosphere's daybreak to update firmware.

https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.3.2

Will Daybreak also not burn my fuses?

 

[impeeza]

Will Daybreak also not burn my fuses?

Daybreak do no burn fuses, Daybreak is ONLY for install firmware avoid to burn fuses. but you need a CFW to avoid the fuses be burned on the system start.

the OFW burn fuses if are less than the actual firmware. so a CFW intercept the fuses module and avoid to be burnt.

 

[binkinator]

All correct. 2 points for everyone!

Here’s how the fuses work behind the scenes.

Fuses — Hekate bypasses the anti-downgrade fuse process but you still might be curious how many fuses are expected to burn for each FW version

 

[877]

You didn't mention it but I'm going to assume you are using partition-based emuMMC since you mentioned having 2 partitions. To start off, let's talk about your Nintendo folder for emuMMC. Within your emuMMC folder, there is an emummc.ini file which indicates what Nintendo folder to use for emuMMC. Based on your info, it seems that your Nintendo folder for emuMMC is inside that folder. Just like the Nintendo folder for sysMMC, the Nintendo folder is where all content installed to the SD card is stored. That only leaves save files which are located within the console's internal memory. In the case of partition-based emuMMC, that would be the partition itself; therefore, your save files are technically stored in the partition you made in order to use emuMMC. All other files and folders such as homebrew files are read from the same place as sysMMC.

Yes it's a partition based emuMMC. Thanks for the explanation, it all makes sense

I wanted to check I'm having trouble restoring ACNH save, but I think the issue is specific to the game as I can save/restore other games fine with JKSV.

Strangely it saves to Device/BCAT, whereas normal games save to the player slot. Not sure why..

 

[Okayermi]

I know this question has been answered before but I haven't figured out a way to make mine work. I was able to install a partition based Emunand and was frequentlly shutting it off to play my legit online games. All of a sudden when I tried loading fuse.bin I got both atmosphere logos and a black screen afterwards. This happened in a day and i dont know what triggered it or how to fix it. I've already replaces my old atmos folder with a new one and the payload too.

Any comments are of great help!

 

[binkinator]

I know this question has been answered before but I haven't figured out a way to make mine work. I was able to install a partition based Emunand and was frequentlly shutting it off to play my legit online games. All of a sudden when I tried loading fuse.bin I got both atmosphere logos and a black screen afterwards. This happened in a day and i dont know what triggered it or how to fix it. I've already replaces my old atmos folder with a new one and the payload too.

Any comments are of great help!

Possible somebody upgraded your firmware.


Please list out your versions for:

FW:
Atmosphere:
Hekate:

Please paste the contents of your /bootloader/hektate_ipl.ini file:

 

[Okayermi]

Possible somebody upgraded your firmware.


Please list out your versions for:

FW:
Atmosphere:
Hekate:

Please paste the contents of your /bootloader/hektate_ipl.ini file:

FW: 14.1.1
Atmos: (last time i was able to check, stuck in hekate menu) 1.3.2
hekate: v5.7.2

Idk why i have two hekate_ipl.ini

First one (document):
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=115
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

Second one (text document without format)
[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


And btw who could've updated my switch... only I use it?

 

[impeeza]

FW: 14.1.1
Atmos: (last time i was able to check, stuck in hekate menu) 1.3.2
hekate: v5.7.2

Idk why i have two hekate_ipl.ini

First one (document):
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=115
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

Second one (text document without format)
[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


And btw who could've updated my switch... only I use it?

you should enable to see extensions on explorer, you have "duplicate" files but with different extension

 

[Okayermi]

I'm using a Mac, what can i do?

 

[Okayermi]

you should enable to see extensions on explorer, you have "duplicate" files but with different extension
View attachment 311637
View attachment 311638

View attachment 311639

Okay so in my mac I checked and now know which one is a .txt and which one is .ini

 

[impeeza]

if you use mac you should enter to nyx on switch and fix archive bit on your SD Card.

 

[Okayermi]

if you use mac you should enter to nyx on switch and fix archive bit on your SD Card.

View attachment 311640

done. nothing changed

 

[impeeza]

neither, [Atmosphere CFW] nor [Stock SysNAND] boots?

do you have a working SYSNAND backup?

 

[Okayermi]

neither, [Atmosphere CFW] nor [Stock SysNAND] boots?

I can boot on Sysnand cause I don't have AutoRCM on, but when i enter hekate and inject payload after both atmos logos it still goes (and remains) black

 

[impeeza]

if you inject hekate and get in NYX you have two boot options [Atmosphere CFW] & [Stock SysNAND] none works?

 

[Okayermi]

if you inject hekate and get in NYX you have two boot options [Atmosphere CFW] & [Stock SysNAND] none works?

Oh, through "launch", I didn't use launch or other launch options because I got the error "check that bootloader/hekate_ipl.ini has boot entries" and i haven't solved that one, i just resorted to always injecting payload

 

[impeeza]

ok, going to anywhere.

can you please show us the content of the file "SD:\emuMMC\emummc.ini"

ps. What payload do you normally inject?

 

[Okayermi]

ok, going to anywhere.

can you please show us the content of the file "SD:\emuMMC\emummc.ini"

ps. What payload do you normally inject?

Okay, in inside the emummc folder and emummuc.ini (that I opened with text), it says
[emummc]
enabled=1
sector=0xb3c8000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

And i normally inject Hekate ? I think? or the fusee.bin that comes with atmos. I got it absolutely scrambled trying to fix this

 

[impeeza]

Then by now we can tell this:

• You have a EmuNAND as RAW partition, not working, going to black screeen after atmosphère logo.
• Your Hekate config is something messed up but normally you don't use it.
• your SYSNAND is working fine an loads if you don't go to RCM and inject a payload.

at first look you emunand get damaged somehow nothing comes to my mind, but @binkinator could enlighten us a bit.

a firts test could be reinstall to your SD card new downloaded Hekate and Atmosphere from GitHub to discard a damaged file.