Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[smf]

It's the bootloader that checks and burns the fuses, not the actual OS, so as long as you don't use Nintendo's bootloader and instead use a custom one like Hekate or Fusée you won't burn fuses regardless if you boot into CFW or OFW afterwards.

AFAICT the fuse burning is done by the OS, but the payloads set a register that causes the OS to skip the check.

 

[SciresM]

AFAICT the fuse burning is done by the OS, but the payloads set a register that causes the OS to skip the check.

No, only package1loader can burn fuses (and it writes to a register disabling fuseburning in hardware until next reboot after it does its checks).

CFW just doesn't run package1loader (hekate/fusee both fulfill its functionality, anyway).

 

[smf]

No, only package1loader can burn fuses (and it writes to a register disabling fuseburning in hardware until next reboot after it does its checks).

CFW just doesn't run package1loader (hekate/fusee both fulfill its functionality, anyway).

Maybe I misunderstood what this code in hekate is for?

void reboot_normal()
{
sd_unmount();
display_end();
panic(0x21); // Bypass fuse programming in package1.
}

 

[SciresM]

Maybe I misunderstood what this code in hekate is for?

void reboot_normal()
{
sd_unmount();
display_end();
panic(0x21); // Bypass fuse programming in package1.
}

That is a special panic code that package1loader uses to signal to itself that fuses have just been burnt -- so yes, when rebooted into with that code, packag1loader assumes it has just burnt fuses and doesn't burn them.

I don't see the relevance, though, since that's handled by package1loader and "only package1loader can burn fuses" is what I just said?

Also, that's used only for rebooting into the OS without CFW. When booting CFW, that codepath isn't used/taken, since package1loader is not run.

 

[Krude]

*looks at calendar*

Oh my is it the 14th of June again already? A year goes by so fast

 

[SciresM]

Happy June 15th!

 

[Mata84]

Happy June 15th!

Thanks for your work SciresM [emoji4][emoji106]

Enviado do meu SM-G930F através do Tapatalk

 

[Derrin]

This is probably a very n00bish question, but I didn't find anything clear searching the forums. If I wanted to play, let's say, FF7 in English (as the Spanish translation is as mythical as it is abhorrent), should I create a config.ini file inside titles/[FFVIItitleID] and just add a line "override_config!override_language=en-GB" (or en-US)?

I'm probably doing it all wrong, I apologise in advance

 

[TamarindoJuice]

Support for language selection per game! Awesome, i missed it a lot since the 3DS!

Thank you @SciresM!

Plus - Cool new AMS icon at startup.

 

[SciresM]

This is probably a very n00bish question, but I didn't find anything clear searching the forums. If I wanted to play, let's say, FF7 in English (as the Spanish translation is as mythical as it is abhorrent), should I create a config.ini file inside titles/[FFVIItitleID] and just add a line "override_config!override_language=en-GB" (or en-US)?

I'm probably doing it all wrong, I apologise in advance

Create a config.ini file inside titles/[FFVIItitleID] and add the following to it:

[override_config]
override_language=en-GB
override_region=eur

 

[Derrin]

Create a config.ini file inside titles/[FFVIItitleID] and add the following to it:

Thank you SOOOO much ♥♥♥

 

[AnotherAlternative]

I know this sounds dumb but how do you make the nro ips patches for layeredfs mods?
Is it the same as making regular ips patches?

For example, I have an undub of twewy with all the audio and video files that will replace the english one, do I just make ips patches the normal way with the original and new files or is there something else I must do?

This isn't my first time modding games but I haven't done any for the switch before.

 

[ShadowOne333]

I just updated my AutoRCM 6.2.0 Switch to 8.0.1 through Choidujour, and I'm using the latest Kosmos package to load Atmosphere.

Now, when I inject the payload, I get the normal Kosmos Hekate splash screen, followed by a "sept" splash, then the Kosmos Hekate splash yet again, the Atmosphere splash and finally the Nintendo logo.Is that normal?
Why is it doing that now and not when I was in 6.2.0?

In 6.2.0 I only got the following splashes in order:
Kosmos Hekate -> Atmosphere -> Nintendo
But now in 8.0.1 I get:
Hekate -> Sept -> Hekate (again) -> Atmosphere -> Nintendo

Is it normal that it does that now?
Why is it doing so now when it didn't do that before?

 

[Hayato213]

I just updated my AutoRCM 6.2.0 Switch to 8.0.1 through Choidujour, and I'm using the latest Kosmos package to load Atmosphere.

Now, when I inject the payload, I get the normal Kosmos Hekate splash screen, followed by a "sept" splash, then the Kosmos Hekate splash yet again, the Atmosphere splash and finally the Nintendo logo.Is that normal?
Why is it doing that now and not when I was in 6.2.0?

In 6.2.0 I only got the following splashes in order:
Kosmos Hekate -> Atmosphere -> Nintendo
But now in 8.0.1 I get:
Hekate -> Sept -> Hekate (again) -> Atmosphere -> Nintendo

Is it normal that it does that now?
Why is it doing so now when it didn't do that before?

Does it boot? If it does leave it alone, just some screen it goes through as it boot up cfw.

 

[ShadowOne333]

Does it boot? If it does leave it alone, just some screen it goes through as it boot up cfw.

Oh yeah it does boot.
It's the sept splash screen that throws me off, but out of that everything seems to boot and work fine.

 

[ZachyCatGames]

I just updated my AutoRCM 6.2.0 Switch to 8.0.1 through Choidujour, and I'm using the latest Kosmos package to load Atmosphere.

Now, when I inject the payload, I get the normal Kosmos Hekate splash screen, followed by a "sept" splash, then the Kosmos Hekate splash yet again, the Atmosphere splash and finally the Nintendo logo.Is that normal?
Why is it doing that now and not when I was in 6.2.0?

In 6.2.0 I only got the following splashes in order:
Kosmos Hekate -> Atmosphere -> Nintendo
But now in 8.0.1 I get:
Hekate -> Sept -> Hekate (again) -> Atmosphere -> Nintendo

Is it normal that it does that now?
Why is it doing so now when it didn't do that before?

sept is used for keygen on 7.0.0+

 

[Hayato213]

Oh yeah it does boot.
It's the sept splash screen that throws me off, but out of that everything seems to boot and work fine.

It is normal, just some splash screen developers wanted.

 

[LapCheong]

I just updated my AutoRCM 6.2.0 Switch to 8.0.1 through Choidujour, and I'm using the latest Kosmos package to load Atmosphere.

Now, when I inject the payload, I get the normal Kosmos Hekate splash screen, followed by a "sept" splash, then the Kosmos Hekate splash yet again, the Atmosphere splash and finally the Nintendo logo.Is that normal?
Why is it doing that now and not when I was in 6.2.0?

In 6.2.0 I only got the following splashes in order:
Kosmos Hekate -> Atmosphere -> Nintendo
But now in 8.0.1 I get:
Hekate -> Sept -> Hekate (again) -> Atmosphere -> Nintendo

Is it normal that it does that now?
Why is it doing so now when it didn't do that before?

Don't worry mine was like that too
If I delete kosmos and start from fresh with only nintendo folder on the SD card. Then i reinstall kosmos or only pure atmosphere

 

[jmrodrigues]

I always use clean atmosphere, then patches, disabled cheats, hekate on boot and place a few manual cheats for edizon.

 

[snoofly]

sept is used for keygen on 7.0.0+

On 8..0.1 I get Load Argon, select Atmos then splash screen I get: Sept > Atmos > Atmos Graphic > Nintendo Switch
Not sure why you're getting the extra Hekate splash
That was meant for Shadow