Hacking Question No Main Boot/Checkpoint

[EndymionXTV]

Hi,

Firmware: 12.1.0


https://github.com/CTCaer/hekate/releases
https://github.com/Atmosphere-NX/Atmosphere/releases

downloaded from both the above links and placed in the micro sd card and then launched via tegragui afterwards i created a NAND back up and transferred it to my PC and deleted the NAND back up from my switch.

It boots to Hekate fine, however here's where the problems begin:

1. I go to launch
a) says that
"No main boot entries found...
Check that bootloader/hekate_ipl.ini has boot entries
or use more configs button for more boot entries"
b) I double checked this is what is in my Hekate_ipl.ini
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[Payload Fusee Primary]
fss0=bootloader/payloads/fusee-primary.bin


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

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

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

2. since method one doesn't work I tried downloading fusee-primary.bin and putting it in the bootloader folder on the sd card from https://github.com/Atmosphere-NX/Atmosphere/releases and launched via Payload
a) it get to the home screen for the switch and I can see the applications in applet mode but cant launch Checkpoint.nro as it opens for a second and brings me back to the cfw apps . I downloaded the latest checkpoint here https://github.com/SciresM/Checkpoint/releases/tag/ams-19-compat



This is what my folders look like

 

[Lacius]

Is there a reason you're using applet mode over title override? Title override (holding R while launching a game) is highly recommended, and it is required for some homebrew applications to work properly.

Is there a reason you're using Checkpoint instead of JKSV?

 

[EndymionXTV]

Is there a reason you're using applet mode over title override? Title override (holding R while launching a game) is highly recommended, and it is required for some homebrew applications to work properly.

Is there a reason you're using Checkpoint instead of JKSV?

i want to be able to launch CFW(EMMUC) but it keeps saying no main boot found and it doesnt even show CFW(SYSNAND) CFW(EMMUC) STOCK SYSNAND , I only launched in applet mode cause it was the only way i can boot to the home screen by click on payload and select fuslee primary to boot.

I'm more familiar with using checkpoint is why im using it

 

[Lacius]

i want to be able to launch CFW(EMMUC) but it keeps saying no main boot found and it doesnt even show CFW(SYSNAND) CFW(EMMUC) STOCK SYSNAND , I only launched in applet mode cause it was the only way i can boot to the home screen by click on payload and select fuslee primary to boot.

I'm more familiar with using checkpoint is why im using it

You can't boot into an emuMMC unless you make an emuMMC first.

Applet mode is when you boot into the homebrew launcher by launching the photo app. This method of booting into the homebrew launcher is not recommended. Instead, hold R while launching a game to launch the homebrew launcher that way.

 

[EndymionXTV]

You can't boot into an emuMMC unless you make an emuMMC first.

Applet mode is when you boot into the homebrew launcher by launching the photo app. This method of booting into the homebrew launcher is not recommended. Instead, hold R while launching a game to launch the homebrew launcher that way.

So after i create the EmuMMC - I'll have those three options from bootloader? CFW(Sysnand), CFW(emummc), Stocksys?

"Instead, hold R while launching a game to launch the homebrew launcher that way" is this something new? as I never had to do that before last time I installed CFW was in 2019 all i did was

1) Inject payload using RCMLoader / Tegra GUI - Hekate
2) Launch CFW(EmuMMC)
3) Gallery/Photos -> Launch Checkpoint

but you're saying no need for step 3 anymore? only choose the game i want the save file from and hold R while launch the software? and it'll populate the homebrew menu for me?

 

[Lacius]

So after i create the EmuMMC - I'll have those three options from bootloader? CFW(Sysnand), CFW(emummc), Stocksys?

"Instead, hold R while launching a game to launch the homebrew launcher that way" is this something new? as I never had to do that before last time I installed CFW was in 2019 all i did was

1) Inject payload using RCMLoader / Tegra GUI - Hekate
2) Launch CFW(EmuMMC)
3) Gallery/Photos -> Launch Checkpoint

but you're saying no need for step 3 anymore? only choose the game i want the save file from and hold R while launch the software? and it'll populate the homebrew menu for me?

Using the photo app to launch the homebrew launcher is inferior and not recommended. Use R on a game instead.

Once you create an emuMMC, you should be able to boot into your emuMMC. Unless you plan on using a clean sysMMC to play online with legitimately purchased games, however, there is probably no need to create an emuMMC.

 

[EndymionXTV]

Using the photo app to launch the homebrew launcher is inferior and not recommended. Use R on a game instead.

Once you create an emuMMC, you should be able to boot into your emuMMC. Unless you plan on using a clean sysMMC to play online with legitimately purchased games, however, there is probably no need to create an emuMMC.

But the outstanding issue still remains though see picture when i press on launch

this issue pops up

 

[Lacius]

What does the hekate_ipl.ini contain in the ini folder?

 

[EndymionXTV]

What does the hekate_ipl.ini contain in the ini folder?

it's in my first post but here it is again

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

[Payload Fusee Primary]
fss0=bootloader/payloads/fusee-primary.bin


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

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

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

 

[Lacius]

it's in my first post but here it is again

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

[Payload Fusee Primary]
fss0=bootloader/payloads/fusee-primary.bin


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

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

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

You said this was bootloader/hekate_ipl.ini, not bootloader/ini/hekate_ipl.ini

 

[EndymionXTV]

You said this was bootloader/hekate_ipl.ini, not bootloader/ini/hekate_ipl.ini

this is what's in my bootloader ini hekate_ipl.ini

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

[Payload Fusee Primary]
fss0=bootloader/payloads/fusee-primary.bin


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

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

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

is there another Hekate_ipl.ini thats need to be placed somewhere and is it different?

 

[Lacius]

this is what's in my bootloader ini hekate_ipl.ini

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

[Payload Fusee Primary]
fss0=bootloader/payloads/fusee-primary.bin


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

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

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

is there another Hekate_ipl.ini thats need to be placed somewhere and is it different?

You have two versions of hekate_ipl.ini. You only need the one in the bootloader folder, not the one in bootloader/ini.

 

[EndymionXTV]

You have two versions of hekate_ipl.ini. You only need the one in the bootloader folder, not the one in bootloader/ini.

i deleted the one in the bootloader/ini and pasted its content in the sd card i now see the options however when i launch any of them it says:

 

[Lacius]

i deleted the one in the bootloader/ini and pasted its content in the sd card i now see the options however when i launch any of them it says:

View attachment 269397

If you have not created an emuMMC, you aren't going to be able to launch an emuMMC.

If you haven't updated Atmosphere/Hekate for compatibility with 12.1.0, then you are going to receive errors.

• Hekate: https://github.com/CTCaer/hekate/releases/latest
• Atmosphere: https://github.com/Atmosphere-NX/Atmosphere/releases/latest
• Signature patches: https://github.com/ITotalJustice/patches/releases/latest

 

[EndymionXTV]

If you have not created an emuMMC, you aren't going to be able to launch an emuMMC.

If you haven't updated Atmosphere/Hekate for compatibility with 12.1.0, then you are going to receive errors.

• Hekate: https://github.com/CTCaer/hekate/releases/latest
• Atmosphere: https://github.com/Atmosphere-NX/Atmosphere/releases/latest
• Signature patches: https://github.com/ITotalJustice/patches/releases/latest

Thanks, I managed to get the sigpatches error to disappear, however the switch boots really slow.. and opens things slow like the the nintendo switch logo was on the screen for at least a good minute before the switch timed out and i had to press the power to get me to the home screen

--------------------- MERGED ---------------------------

Also im trying to a software match version with local user with my second switch and it keeps saying cant find a group when i created a group on my non modded switch and click join a room on the modded switch.

they are both the same firmware

 

[Lacius]

Thanks, I managed to get the sigpatches error to disappear, however the switch boots really slow.. and opens things slow like the the nintendo switch logo was on the screen for at least a good minute before the switch timed out and i had to press the power to get me to the home screen

If it were me, I'd do the following:

1. Delete the atmosphere folder from your SD card.
2. Download the latest version of Atmosphere: https://github.com/Atmosphere-NX/Atmosphere/releases/latest
3. Download fusee-primary (next to Atmosphere).
4. Download these signature patches (choose the fusee patches): https://github.com/ITotalJustice/patches/releases/latest
5. Put Atmosphere onto your SD card.
6. Put the signature patches onto your SD card.
7. Enter RCM and boot into Atmosphere by pushing the fusee-primary.bin payload.

Does this resolve your issues?

Also im trying to a software match version with local user with my second switch and it keeps saying cant find a group when i created a group on my non modded switch and click join a room on the modded switch.

they are both the same firmware

Reboot both systems, and make sure they aren't in airplane mode.

 

[EndymionXTV]

It boots my problem now is..

Ive updated my pokemon shield cartridge on the switch and everything then i created a backup emummc now when i go and start up the game with the CFW it shows the game as though it wasnt updated when i already updated it before i created the emummc.

i've already done this update on stock, now when i launch cfw it shows me i gotta update it? when i already did

So i was thinking of doing match with local to update with non modded switch (the black and white joycon) with my modded switch(red and blue joycon) they are both off airplane mode. but the room isnt detected. They both have physical cartridges

 

[EndymionXTV]

If it were me, I'd do the following:

1. Delete the atmosphere folder from your SD card.
2. Download the latest version of Atmosphere: https://github.com/Atmosphere-NX/Atmosphere/releases/latest
3. Download fusee-primary (next to Atmosphere).
4. Download these signature patches (choose the fusee patches): https://github.com/ITotalJustice/patches/releases/latest
5. Put Atmosphere onto your SD card.
6. Put the signature patches onto your SD card.
7. Enter RCM and boot into Atmosphere by pushing the fusee-primary.bin payload.

Does this resolve your issues?


Reboot both systems, and make sure they aren't in airplane mode.

it does boot, but the modded switch keeps populating the update for my cartridge game

 

[Lacius]

it does boot, but the modded switch keeps populating the update for my cartridge game

Did you install the game update before or after you made the emuMMC?

1. If you installed it after you made the emuMMC, then you need to install the game update on the emuMMC too. You can use your favorite NSP installer (TinWoo and Awoo-Installer are recommended).
2. If you installed the game update before you made the emuMMC, then you need to make sure you've copied the contents of your Nintendo folder to your emummc folder. In the future, anything you install to the sysMMC will not be installed to the emuMMC, and vice versa.

 

[EndymionXTV]

Did you install the game update before or after you made the emuMMC?

1. If you installed it after you made the emuMMC, then you need to install the game update on the emuMMC too. You can use your favorite NSP installer (TinWoo and Awoo-Installer are recommended).
2. If you installed the game update before you made the emuMMC, then you need to make sure you've copied the contents of your Nintendo folder to your emummc folder. In the future, anything you install to the sysMMC will not be installed to the emuMMC, and vice versa.

thanks it works!