Accidentaly updated my cfw switch to 17.0

[Tackskull]

Hi there,

each time running a game on my switch with atmosphere cfw, a message apper telling me "update now". Since I never clicked on it, I always pressed "run the game". But today I accidentally clicked on "Update" and now my switch have the official 17.0 firmaware, and all the games are not playable anymore. How can I solve this problem?

Thanks

 

[linuxares]

Let me get this right. You haven't done anything, except happened to update your system with the latest firmware?

Because some things doesn't add up.

 

[Goku1992A]

Wait for a new CFW to come out.... I'm not too sure why you still have your switch connected to the internet I'm still on firmware 15.0.0

Yuzu is so good I hardly use my switch except for pokemon.

 

[Tackskull]

Let me get this right. You haven't done anything, except happened to update your system with the latest firmware?

Because some things doesn't add up.

yes, I updated the switch

 

[linuxares]

Which atmosphere version do you run?

 

[shanefromoz]

Hi there, a message apper telling me "update now". Since I never clicked on it, I always pressed "run the game". But today I accidentally clicked on "Update" and now my switch have the official 17.0 firmaware, and all the games are not playable anymore. How can I solve this problem?

ThankUp

Update Atmophere 1.6.0 is the latest

 

[chikoo_69]

Update Atmophere 1.6.0 is the latest

The sigpatchs for Atmosphere 1.6.0 are not out yet. The best for now is downgrade to 16.1.0 and use the updated sigpatches for 16.1.0 or wait for the new sigpatch for 17.0.0...And FYI, i was able to downgrade from 17.0.0 to 16.1.0 using daybreak without any issues. When updating your sysnand when you are on atmosphere, this wont burn the efuses so you should be able to downgrade without any issues!

 

[Tackskull]

Which atmosphere version do you run?

The 16.10, the latest one.

Post automatically merged: Oct 19, 2023

The sigpatchs for Atmosphere 1.6.0 are not out yet. The best for now is downgrade to 16.1.0 and use the updated sigpatches for 16.1.0 or wait for the new sigpatch for 17.0.0...And FYI, i was able to downgrade from 17.0.0 to 16.1.0 using daybreak without any issues. When updating your sysnand when you are on atmosphere, this wont burn the efuses so you should be able to downgrade without any issues!

Are you sure I can downgrade the firmware just by using daybreak? I am so scared to do that

 

[Hayato213]

The 16.10, the latest one.

Post automatically merged: Oct 19, 2023

Are you sure I can downgrade the firmware just by using daybreak? I am so scared to do that

You on Sysnand or Emunand?

 

[Tackskull]

You on Sysnand or Emunand?

How I know that?

 

[Hayato213]

How I know that?

Normally you can find that out inside system string, but if you can't boot, you can check your fuse count in hekate it will give you an idea if your sysnand is on 17,0,0 or not, 17.0.0 has fuse count of 19.

 

[Tackskull]

Normally you can find that out inside system string, but if you can't boot, you can check your fuse count in hekate it will give you an idea if your sysnand is on 17,0,0 or not, 17.0.0 has fuse count of 19.

My switch is actually on, on "system" it say: 17.0.0/AMS 1.6.0/S

 

[Hayato213]

My switch is actually on, on "system" it say: 17.0.0/AMS 1.6.0/S

Check your fuse count, it probably would say 19, unless you have a v1 unpatched unit on autoRCM, if you downgrade you probably won't be able to boot due to mismatch fuse count.

 

[Tackskull]

Check your fuse count, it probably would say 19, unless you have a v1 unpatched unit on autoRCM, if you downgrade you probably won't be able to boot due to mismatch fuse count.

Can you explain me what I have to do to see the fuse count?

 

[Hayato213]

Can you explain me what I have to do to see the fuse count?

Load up Hekate go to Console info, HW and Fuses.

 

[jin521rin]

The sigpatchs for Atmosphere 1.6.0 are not out yet. The best for now is downgrade to 16.1.0 and use the updated sigpatches for 16.1.0 or wait for the new sigpatch for 17.0.0...And FYI, i was able to downgrade from 17.0.0 to 16.1.0 using daybreak without any issues. When updating your sysnand when you are on atmosphere, this wont burn the efuses so you should be able to downgrade without any issues!

I update to Firmware 17.0.0 too, and at the moment signpatch for cfw 16.1.0 work fine for me on my switch now, you and try to replace the signpatch (cfw 16.1.0 version) again after update the latest atmosphere

 

[Tackskull]

Load up Hekate go to Console info, HW and Fuses.

I have auto RCM on, and I don't know how I can get back to Heckate menù

 

[linuxares]

I have auto RCM on, and I don't know how I can get back to Heckate menù

hold down vol + when you boot and it will enter hekate if you have set autoboot.

 

[BaamAlex]

I have auto RCM on, and I don't know how I can get back to Heckate menù

Before you send the hekate payload, hold the vol - button. This should bring you into the hekate menu.

 

[Tackskull]

Before you send the hekate payload, hold the vol - button. This should bring you into the hekate menu.

So instead use the fuse.bin payload I have to use heckate, and press - button?

Edit: ok I got in to the Hekate menù, now I am in console info, but where I check the fuse count?