Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[mrdude]

A quick reminder that when Atmosphere 0.13.0 is released, current signature patches for 10.0.x will probably not be compatible (I haven't checked if loader was updated). If you care about signature patches, please wait for them to be updated.

Edit: Patches need to be updated for homebrew forwarders. Game backups of any kind work fine.

I updated and all my games say they are corrupt - they work on sxos though, so I went back to 0.12.0 and now they are working again. Any idea why they appear corrupt in 0.13.0?

 

[Lacius]

I updated and all my games say they are corrupt - they work on sxos though, so I went back to 0.12.0 and now they are working again. Any idea why they appear corrupt in 0.13.0?

You need the 0.13 signature patches.
https://gbatemp.net/threads/sigpatches-for-atmosphere-0-13-0.567542/

 

[mrdude]

You need the 0.13 signature patches.
https://gbatemp.net/threads/sigpatches-for-atmosphere-0-13-0.567542/

Thanks dude

 

[Dothackjhe]

Anybody else having trouble booting their system after upgrading to Atmosphere 0.13.0?

So, I just recently upgraded to the latest version of Hekate (5.3.0) where it works just fine when the console was still on Atmosphere 0.12.0. But after using the files for Atmosphere 0.13.0, it no longer boots beyond the Hekate part of the chainload booting process.

System firmware: 10.0.2

 

[Lacius]

Anybody else having trouble booting their system after upgrading to Atmosphere 0.13.0?

So, I just recently upgraded to the latest version of Hekate (5.3.0) where it works just fine when the console was still on Atmosphere 0.12.0. But after using the files for Atmosphere 0.13.0, it no longer boots beyond the Hekate part of the chainlink booting process.

System firmware: 10.2.0

As a matter of troubleshooting, does it boot with the latest fusee-primary?

 

[Dothackjhe]

As a matter of troubleshooting, does it boot with the latest fusee-primary?

I am using the latest fusee-primary. Is it what's causing it?

 

[Lacius]

I am using the latest fusee-primary. Is it what's causing it?

I mean without chainloading with Hekate.

 

[Dothackjhe]

I mean without chainloading with Hekate.

I have not tried yet.

I thought Hekate is essential in this latest iteration of Atmosphere. I think that's what I read with the release's description.

 

[Lacius]

I have not tried yet.

I thought Hekate is essential in this latest iteration of Atmosphere. I think that's what I read with the release's description.

No, definitely not. Fusee-primary is the default method of booting Atmosphere.

From a personal perspective, I don't think Hekate should be used as a primary bootloader unless one is using an RCM loader of some sort.

 

[Dothackjhe]

No, definitely not. Fusee-primary is the default method of booting Atmosphere.

From a personal perspective, I don't think Hekate should be used as a primary bootloader unless one is using an RCM loader of some sort.

I've temporarily reverted to Atmosphere 0.12.0. The system booted just fine right off the bat with Hekate 5.3.0.

I uses NS-Atmosphere as an RCM loader.

 

[Lacius]

I've temporarily reverted to Atmosphere 0.12.0. The system booted just fine right off the bat with Hekate 5.3.0.

I uses NS-Atmosphere as an RCM loader.

What does the chainloading entry look like in your config?

 

[Dothackjhe]

What does the chainloading entry look like in your config?

What exactly do you mean?

 

[Lacius]

What exactly do you mean?

How are you chainloading fusee-primary? What does the boot entry look like?

 

[Dothackjhe]

Via Sysnand.

The interface looks exactly how the previous version of Hekate looked like. There's not much that has changed interface-wise. But Hekate 5.3.0 asked for a date and time on first boot with it (yesterday).

 

[Lacius]

Via Sysnand.

Did you manually add a boot entry for chainloading fusee-primary, or did you just click "CFW sysNAND" in Hekate?

 

[Dothackjhe]

Did you manually add a boot entry for chainloading fusee-primary, or did you just click "CFW sysNAND" in Hekate?

The latter, like I usually do.

 

[Lacius]

The latter, like I usually do.

You're not chainloading fusee-primary. You're booting a modified Atmosphere via Hekate as the primary bootloader.

 

[Dothackjhe]

You're not chainloading fusee-primary. You're booting a modified Atmosphere via Hekate as the primary bootloader.

Ohhh. How do I go about that, then?

 

[Lacius]

Ohhh. How do I go about that, then?

1. Put fusee-primary into the ‘/bootloader/payloads’ folder on your SD card.
2. Enter Hekate
3. Select ‘Payloads’
4. Select fusee-primary

 

[Dothackjhe]

1. Put fusee-primary into the ‘/bootloader/payloads’ folder on your SD card.
2. Enter Hekate
3. Select ‘Payloads’
4. Select fusee-primary

Thanks.