Homebrew Question Problems trying to hack my switch

[natanqb]

Hi, i am following this guide https://nh-server.github.io/switch-guide/user_guide/launching_cfw/ and arrived at this last page. But now when i try to Power on my Switch into RCM it always turns on normally. I am trying to hold the volume + button when i power it on, but its not working. And i have another doubt, where should i put the Atmosphere FSS0 file? Thank you.

 

[M7L7NK7]

Are you using a jig? Is your switch hackable?

 

[natanqb]

Are you using a jig? Is your switch hackable?

Yes it is hackable, i was using tinfoil paper and it was working. Now i am on this last step of the process but when i press the power button while holding volume + and the console immediately turns on.

 

[NFates]

Try placing the tinfoil again or try another method to access RCM.

 

[mattytrog]

Yes it is hackable, i was using tinfoil paper and it was working. Now i am on this last step of the process but when i press the power button while holding volume + and the console immediately turns on.

You aren`t triggering RCM then sir.

 

[natanqb]

Try placing the tinfoil again or try another method to access RCM.

Ok i will try, also where should i put the Atmosphere FSS0 file?

 

[mattytrog]

Put it wherever the ini is looking for it. Probably SD root.

 

[natanqb]

Put it wherever the ini is looking for it. Probably SD root.

Just to make sure, can you tell me if this file is named "Atmosphere FSS0" if not, what is it named? And where can i download it? I download everything the guide said to download, but i can't find this file. Thank you.

 

[natanqb]

i was able to enter RCM, but i can't find the Atmosphere FSS0, take a look at the picture please.

 

[LapCheong]

Why not just use this? https://www.sdsetup.com/
Select what you want and download, extract it to the of sd card and done.
And before you struggle getting into RCM, while you are in hekate enable AutoRCM under "tools" or "optoins" cant remember

 

[NFates]

i was able to enter RCM, but i can't find the Atmosphere FSS0, take a look at the picture please.

Do you have hekate_ipl.ini on the /bootloader folder?

Why not just use this? https://www.sdsetup.com/
Select what you want and download, extract it to the of sd card and done.
And before you struggle getting into RCM, while you are in hekate enable AutoRCM under "tools" or "optoins" cant remember

Why SDSetup/Kosmos isn't recommended
Kosmos makes you load all the various parts of Atmosphere through Hekate. This is bad for several reasons:
- Kosmos occasionally makes use of nightly versions of Atmosphere. This means that Kosmos cannot be properly troubleshooted as a result.
- SDSetup specific: SDSetup bundles certain KIP patches optionally. This is bad because it results in fractured (and therefore hard to troubleshoot) setups.

What you should use instead
Use the official NH guide over at https://nh-server.github.io/switch-guide/

 

[LapCheong]

Do you have hekate_ipl.ini on the /bootloader folder?

I see thank you for your insight. I have been using kosmos for so long without problem. Sorry for my ignorance

 

[natanqb]

Do you have hekate_ipl.ini on the /bootloader folder?

I will check if i have hekate_ipl.ini on the /bootloader folder when i get home. Is it safe to enable auto RCM like LapCheong said?

 

[LapCheong]

i was able to enter RCM, but i can't find the Atmosphere FSS0, take a look at the picture please.

Sorry i didn't answer your question. The reason why there is no payload to boot. Is because the .ini file is missing. Hekate does not know what to boot if do not specify them in the config. The "Atmosphere FSS0" is just a name given in the "hekate_ipl.ini"
AutoRCM has nothing to do with the files on the sdcard since it corrupt the boot files and forces your switch into RCM state.

 

[natanqb]

Sorry i didn't answer your question. The reason why there is no payload to boot. Is because the .ini file is missing. Hekate does not know what to boot if do not specify them in the config. The "Atmosphere FSS0" is just a name given in the "hekate_ipl.ini"
AutoRCM has nothing to do with the files on the sdcard since it corrupt the boot files and forces your switch into RCM state.

Ok ty, but is it safe to enable auto RCM? Even befoe i finish the hacking process?

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

Sorry i didn't answer your question. The reason why there is no payload to boot. Is because the .ini file is missing. Hekate does not know what to boot if do not specify them in the config. The "Atmosphere FSS0" is just a name given in the "hekate_ipl.ini"
AutoRCM has nothing to do with the files on the sdcard since it corrupt the boot files and forces your switch into RCM state.

i checked and the hekate_ipl.ini file is on the bootloader folder on my sd card. How to i specify it on the config?

 

[LapCheong]

Ok ty, but is it safe to enable auto RCM? Even befoe i finish the hacking process?

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


i checked and the hekate_ipl.ini file is on the bootloader folder on my sd card. How to i specify it on the config?

As long you have access to hekate, you can always disable autoRCM. The biggest reason for AutoRCM to be enable is to prevent fuse-burning and hence the possibility of warmboot to emunand in the future. Furthermore, atmosphere fixed the issue with autoRCM and power off. So i dont see a reason not to do so

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

Ok ty, but is it safe to enable auto RCM? Even befoe i finish the hacking process?

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


i checked and the hekate_ipl.ini file is on the bootloader folder on my sd card. How to i specify it on the config?

Check that fusee-primary.bin exist in bootloader/payload (Not sure if this helps) and double check that hekate_ipl.ini is the correct version from the website and not generated by hekate. Since when the hekate_ipl.ini is missing, hekate will automatically generate a clean version with basic configuration. Open the file in the editor to ensure it is not the basic setting. If you are confuse send me a pm i will forward the files to you

 

[natanqb]

As long you have access to hekate, you can always disable autoRCM. The biggest reason for AutoRCM to be enable is to prevent fuse-burning and hence the possibility of warmboot to emunand in the future. Furthermore, atmosphere fixed the issue with autoRCM and power off. So i dont see a reason not to do so

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



Check that fusee-primary.bin exist in bootloader/payload (Not sure if this helps) and double check that hekate_ipl.ini is the correct version from the website and not generated by hekate. Since when the hekate_ipl.ini is missing, hekate will automatically generate a clean version with basic configuration. Open the file in the editor to ensure it is not the basic setting. If you are confuse send me a pm i will forward the files to you

This is what is written on the hekate_ipl.ini "
{------ Atmosphere ------}
{Pick this option to launch CFW.}
[Atmosphere FSS0]
fss0=atmosphere/fusee-secondary.bin
kip1=atmosphere/kips/*
{ }
{------ Stock ------}
{NOTE: This option does not launch CFW.}
[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
{ }"

If im not mistaken this guide that i was following doesn't use fusee-primary.bin .

 

[natanqb]

I managed to make atmosphere fs50 appear by replacing the files with the ones from the guide.
But when i tried to launch it i got the following messages:


Foundpkg1 <'20190314172056'>.
Identified pkg1 and keyblob 7
Errow while loading fss0:
atmosphere/fusee-secondary.bin
wrong ini cfg or missing files
failed to launch firmware.

 

[NFates]

Check your files are all there, specially the /atmosphere folder.

 

[natanqb]

This is how my atmosphere folder looks like.