Hacking SWITCH NOOB PARADISE - Ask questions here

[AlphaBravo]

Well, why not knock down two birds with one stone? Not only does this thread include its own hekate_ipl.ini file but you can also just download the patches. By the way, there is no universal up-to-date hekate_ipl.ini file because its designed to be customizeable to the user and thus every user will have their own hekate_ipl.ini file.

Well i am honesly stuck. This is my setup and other info:
V1 Switch with firmware at 5.1.0. I boot into hekate via an SX pro dongle. I had to convert the hekate.ipl.bin file into boot.dat via https://sx-boot-dat-creator.herokuapp.com/
It all worked no problem until i created a partition and setup emummc with this guide.
When using hekate "Launch option" i can do "cfw (sysmmc) with no issue. So for example i know it works because under system, the firmware shows as atmosphere with S. CFW (emuMMC) will launch atmosphere logo but wont boot past the nintendo logo. Stock option will launch no probs. And finally Fusee will launch atmosphere but wont go past Nintendo Logo.
So the main problem is not being able to launch atmosphere in emummc and having system show up with "E" under the firmware section...

Spoiler: Hekate.ipl.ini

[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

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

Spoiler: emymmc.ini

[emummc]
enabled=1
sector=0xb438000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

Using latest atmosphere and hekate.
Fusee.bin has been placed in payload folder in hekate
Autorcm is not enabled.
I have test the sd card with both chkdsk in windows and Rufus showing no errors. Card is formated in fat32.

 

[Windsall]

Thanks for the help! I tried that using goldleaf and my switch said the data was corrupted. After deleting all the BotW data and trying again by downloading it from the eshop without CFW then copying it to my emuMMC, I got it to update (kinda). When I press + on the home screen, my switch says it's version 1.6.0 but when I launch the game itself, it loads version 1.5.0, and thus, when I try to start a new game with mods, it loads indefinitely because the mods are made for 1.6.0.

I don't understand why the switch home screen says one thing and the game itself says another, but it's most certainly running 1.5.0. Any idea why it could be doing this?

How did you install the update? And what makes you think it's 1.5.0

 

[Chaosta]

Thanks for the help! I tried that using goldleaf and my switch said the data was corrupted. After deleting all the BotW data and trying again by downloading it from the eshop without CFW then copying it to my emuMMC, I got it to update (kinda). When I press + on the home screen, my switch says it's version 1.6.0 but when I launch the game itself, it loads version 1.5.0, and thus, when I try to start a new game with mods, it loads indefinitely because the mods are made for 1.6.0.

I don't understand why the switch home screen says one thing and the game itself says another, but it's most certainly running 1.5.0. Any idea why it could be doing this?

do you have sigpatches? you need them to run installed nsp.

 

[OggieBoogie]

Using atmosphere, how can i install nsz files? Goldleaf doesn't work

 

[Chaosta]

Well i am honesly stuck. This is my setup and other info:
V1 Switch with firmware at 5.1.0. I boot into hekate via an SX pro dongle. I had to convert the hekate.ipl.bin file into boot.dat via https://sx-boot-dat-creator.herokuapp.com/
It all worked no problem until i created a partition and setup emummc with this guide.
When using hekate "Launch option" i can do "cfw (sysmmc) with no issue. So for example i know it works because under system, the firmware shows as atmosphere with S. CFW (emuMMC) will launch atmosphere logo but wont boot past the nintendo logo. Stock option will launch no probs. And finally Fusee will launch atmosphere but wont go past Nintendo Logo.
So the main problem is not being able to launch atmosphere in emummc and having system show up with "E" under the firmware section...

Spoiler: Hekate.ipl.ini

[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

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

Spoiler: emymmc.ini

[emummc]
enabled=1
sector=0xb438000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

Using latest atmosphere and hekate.
Fusee.bin has been placed in payload folder in hekate
Autorcm is not enabled.
I have test the sd card with both chkdsk in windows and Rufus showing no errors. Card is formated in fat32.

your hekate ini is all kinds of messed up, contradictions. use this one.
make sure you have sigpatches, and make sure you put fusee.bin in the
SD:Bootloader/Payloads folder

CFW - sysMMC will boot ofw layered with cfw (will show the S next to firmware)
CFW - emuMMC will boot into emunand using fusee.bin (will show the E next to firmware)
and stock will boot stock

 

[Chaosta]

Using atmosphere, how can i install nsz files? Goldleaf doesn't work

can try tinfoil, tinleaf, tinwoo, dbi.

 

[Draxzelex]

Well i am honesly stuck. This is my setup and other info:
V1 Switch with firmware at 5.1.0. I boot into hekate via an SX pro dongle. I had to convert the hekate.ipl.bin file into boot.dat via https://sx-boot-dat-creator.herokuapp.com/
It all worked no problem until i created a partition and setup emummc with this guide.
When using hekate "Launch option" i can do "cfw (sysmmc) with no issue. So for example i know it works because under system, the firmware shows as atmosphere with S. CFW (emuMMC) will launch atmosphere logo but wont boot past the nintendo logo. Stock option will launch no probs. And finally Fusee will launch atmosphere but wont go past Nintendo Logo.
So the main problem is not being able to launch atmosphere in emummc and having system show up with "E" under the firmware section...

Spoiler: Hekate.ipl.ini

[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

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

Spoiler: emymmc.ini

[emummc]
enabled=1
sector=0xb438000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

Using latest atmosphere and hekate.
Fusee.bin has been placed in payload folder in hekate
Autorcm is not enabled.
I have test the sd card with both chkdsk in windows and Rufus showing no errors. Card is formated in fat32.

Is that a spelling mistake or is your emummc.ini file actually spelled as emymmc.ini? If it is actually spelled like that, then there is your problem. The obvious fix is to rename it to emummc.ini

 

[AlphaBravo]

your hekate ini is all kinds of messed up, contradictions. use this one.
make sure you have sigpatches, and make sure you put fusee.bin in the
SD:Bootloader/Payloads folder

CFW - sysMMC will boot ofw layered with cfw (will show the S next to firmware)
CFW - emuMMC will boot into emunand using fusee.bin (will show the E next to firmware)
and stock will boot stock

Evening. I replaced the hekate ini file with your one. CFW emummc still wont launch (see below).

Spoiler: hekate.ipl.ini

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

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

[CFW - emuMMC]
payload=bootloader/payloads/fusee.bin
icon=bootloaderresicon_payload.bmp

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

CFW - sysMMC.......: Confirmed working (atmosphere-S) but this was fine anyway as stated above.
CFW - emuMMC....: Still wont post past the Nintendo logo. Black screen after. Power button held 15sec to restart.
Stock - Boot fine but did anyway.

Fusee.bin definitely in payloads folder.

Kip&exefs Patches placed in Atmosphere folder. Patches.ini placed in Bootloader folder...

@Draxzelx
No bud, just a spelling mistake in the post and not with the file name

 

[Draxzelex]

Evening. I replaced the hekate ini file with your one. CFW emummc still wont launch (see below).

Spoiler: hekate.ipl.ini

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

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

[CFW - emuMMC]
payload=bootloader/payloads/fusee.bin
icon=bootloaderresicon_payload.bmp

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

CFW - sysMMC.......: Confirmed working (atmosphere-S) but this was fine anyway as stated above.
CFW - emuMMC....: Still wont post past the Nintendo logo. Black screen after. Power button held 15sec to restart.
Stock - Boot fine but did anyway.

Fusee.bin definitely in payloads folder.

Kip&exefs Patches placed in Atmosphere folder. Patches.ini placed in Bootloader folder...

@Draxzelx
No bud, just a spelling mistake in the post and not with the file name

Well I have 2 other things you can try. First, when the console gets stuck at the Nintendo logo, try simply pressing the Power button once. This was reported to have worked for someone else. Another thing you can try is replacing your /atmosphere folder. I recommend deleting your old one (after backing up any game mods and/or cheats you may have inside) then downloading a new from the official GitHub page and placing it on your SD card.

 

[AlphaBravo]

Well I have 2 other things you can try. First, when the console gets stuck at the Nintendo logo, try simply pressing the Power button once. This was reported to have worked for someone else. Another thing you can try is replacing your /atmosphere folder. I recommend deleting your old one (after backing up any game mods and/or cheats you may have inside) then downloading a new from the official GitHub page and placing it on your SD card.

I tried both with no success. So annoying as i followed this guide to the letter and tried two different sd cards.
Stock and cfw_sysmmc launch with no issue.
CFW_emummc still wont boot past the nintendo logo.
Can it be something simple like an incorrect backslash (/) or some other pathway issue?

 

[Chaosta]

I tried both with no success. So annoying as i followed this guide to the letter and tried two different sd cards.
Stock and cfw_sysmmc launch with no issue.
CFW_emummc still wont boot past the nintendo logo.
Can it be something simple like an incorrect backslash (/) or some other pathway issue?

View attachment 326917

the guide you posted doesnt include this step "Tap on Change emuMMC, then SD RAW 1" after selecting part 1.

have you done this?

only other things i can think of is emunand corrupted or maybe doesnt support such a low fw, idk.
whats the reason your keeping sysnand on 5.1?

 

[AlphaBravo]

the guide you posted doesnt include this step "Tap on Change emuMMC, then SD RAW 1" after selecting part 1.

have you done this?

only other things i can think of is emunand corrupted or maybe doesnt support such a low fw, idk.
whats the reason your keeping sysnand on 5.1?

I tried tapping SD RAW1. Gave me message "the emummc config was saved to the sd card." Still same issue.

Wanted to keep 5.1 in case any other interesting hacks come out, also keep it clean while i messed around with emummc.
Is there any evidence that there are firmware clash between hekate emummc and stock firmware?

Or is also possible for an app to completely remove a games firware requirement to play on 5.1 or whatever. That would be temporary solution and could use cfw_sysmmc

 

[Draxzelex]

I tried both with no success. So annoying as i followed this guide to the letter and tried two different sd cards.
Stock and cfw_sysmmc launch with no issue.
CFW_emummc still wont boot past the nintendo logo.
Can it be something simple like an incorrect backslash (/) or some other pathway issue?

View attachment 326917

It has absolutely nothing to do with backslashes otherwise CFW or Stock wouldn't boot so I have no idea what that other guy is talking about. Try changing the sector in your emummc.ini file to 0X03CBB000. It worked for another person in this thread.

I tried tapping SD RAW1. Gave me message "the emummc config was saved to the sd card." Still same issue.

Wanted to keep 5.1 in case any other interesting hacks come out, also keep it clean while i messed around with emummc.
Is there any evidence that there are firmware clash between hekate emummc and stock firmware?

Or is also possible for an app to completely remove a games firware requirement to play on 5.1 or whatever. That would be temporary solution and could use cfw_sysmmc

The whole point of emuMMC is to be on a different firmware than sysMMC in the first place. Them being on the same firmware almost defeats the purpose of emuMMC. Unfortunately, there is no workaround to make games work on whatever firmware you want because of the SDK they are built with which are hard-coded to whatever firmware they correspond with. If the issue truly is your firmware, then that is something that should be brought up with to the Atmosphere team and SciresM because Atmosphere as well as emuMMC is meant to be supported on all firmware versions.

 

[AlphaBravo]

It has absolutely nothing to do with backslashes otherwise CFW or Stock wouldn't boot so I have no idea what that other guy is talking about. Try changing the sector in your emummc.ini file to 0X03CBB000. It worked for another person in this thread.

The whole point of emuMMC is to be on a different firmware than sysMMC in the first place. Them being on the same firmware almost defeats the purpose of emuMMC. Unfortunately, there is no workaround to make games work on whatever firmware you want because of the SDK they are built with which are hard-coded to whatever firmware they correspond with. If the issue truly is your firmware, then that is something that should be brought up with to the Atmosphere team and SciresM because Atmosphere as well as emuMMC is meant to be supported on all firmware versions.

Changing the bootsector just sent the switch into a feedback loop. Thought boot sectors and their values were unique to each user unless they used the same card and size?
Only other things i could try is using option 2 or 3 when choosing a partition during emummc setup? Or using file based instead? I saw a conversation about formatting the emummc partition as exfat despite the issues that might happen with that....

 

[Lucky Dearly]

hey guys, been trying to get back into CFW but whenever I try to inject the payload with Tegra, Tegra stops responding. I'm not sure what else to do, it also keeps telling me the apx driver is missing and to reinstall it and restart my pc but nothing changes and Tegra continues to stop responding during injection.

I tried to reinstall the driver with zandig but zandig keeps aborting the installation.

 

[Chaosta]

Changing the bootsector just sent the switch into a feedback loop. Thought boot sectors and their values were unique to each user unless they used the same card and size?
Only other things i could try is using option 2 or 3 when choosing a partition during emummc setup? Or using file based instead? I saw a conversation about formatting the emummc partition as exfat despite the issues that might happen with that....

last resort can wipe sd card, partition it on pc using ezpartition or similar program, then use hekate to create a emunand and mount it to that partition. perhaps just hekate effed up the partitioning process.

this is how i made my current 4yr old emunand before hekate offered such options.

 

[KingxHyruler]

I have my Switch on Atmosphere CFW and I hacked it back when emuNand wasn’t even an option so basically everything has been done on my Sysnand since the beginning. I still have my clean Nand from way back when I hacked it (6.2). Is it too late for me to restore it and have a clean Sysnad for online play and a emuNand for offline play? If so how do I go about it?

 

[Draxzelex]

Changing the bootsector just sent the switch into a feedback loop. Thought boot sectors and their values were unique to each user unless they used the same card and size?
Only other things i could try is using option 2 or 3 when choosing a partition during emummc setup? Or using file based instead? I saw a conversation about formatting the emummc partition as exfat despite the issues that might happen with that....

At this point, anything is worth a shot which is why I recommended to you to try and change the boot sector. I'm pretty sure it is unique per user but for whatever reason, it worked for another person. The only other thing I can recommend trying besides a clean installation from scratch is using a different SD card. Its almost like a fresh installation but someone else reported using a new SD card fixed their problem after trying 3 other SD cards.

hey guys, been trying to get back into CFW but whenever I try to inject the payload with Tegra, Tegra stops responding. I'm not sure what else to do, it also keeps telling me the apx driver is missing and to reinstall it and restart my pc but nothing changes and Tegra continues to stop responding during injection.

I tried to reinstall the driver with zandig but zandig keeps aborting the installation.

Zadig doesn't install the APX driver, it installs the libusbk driver which can only be installed once the APX driver is installed which is probably why its aborting the installation. Have you tried using TegraRCMSmash?

I have my Switch on Atmosphere CFW and I hacked it back when emuNand wasn’t even an option so basically everything has been done on my Sysnand since the beginning. I still have my clean Nand from way back when I hacked it (6.2). Is it too late for me to restore it and have a clean Sysnad for online play and a emuNand for offline play? If so how do I go about it?

As long as you haven't gone online with your tainted sysMMC, you can always restore make an emuMMC and restore your clean backup prior to going online. You can do both of those things with Hekate. Its fairly straightforward.

 

[elecu]

Hey guys, my emuMMC is on 14.1.2|AMS 1.3.2|E and my stock Sysnand is on 10.2.0. I want to play Splatoon 3 online with as little risk as possible and keep my emuMMC like everyone else. Could I update my Stock Sysnand to 14.1.2 to play online without affecting access to Heckate and emuMMC?

I think is a similar question from @KingxHyruler but I haven't never go online on my stock sysnand since I installed emuMMC.

 

[Hayato213]

Hey guys, my emuMMC is on 14.1.2|AMS 1.3.2|E and my stock Sysnand is on 10.2.0. I want to play Splatoon 3 online with as little risk as possible and keep my emuMMC like everyone else. Could I update my Stock Sysnand to 14.1.2 to play online without affecting access to Heckate and emuMMC?

I think is a similar question from @KingxHyruler but I haven't never go online on my stock sysnand since I installed emuMMC.

As long your Sysnand is a clean NAND you should be fine to play online