Incorrect fusee error on 14.0.0

[skykid]

A kid updated my Switch in lightning-quick speed about two hours ago. I snatched the thing immediately, but it already rebooted to Hekate, and since that the damage was done (seems to apply updates in the blink of an eye). I was relieved to find support for Atmosphere 14.0.0 dropped yesterday!

But after replacing the atmosphere folder with the latest (1.3.0), updating all sigpatches with the latest that support Atmos 1.3.0 and FW 14.0.0, I'm not having any luck actually booting into CFW. I get this error every time:

"A fatal error ocurred while running Fusee.
Incorrect fusee version! (program=0xb6b6ac70, mtc=0xb4dcf71)

Press POWER to reboot."

Pressing power takes me back to Hekate.

I'm not sure what's wrong here, I have updated all the files as far as I can tell, including Fusee. Unless there's another update that happened today that I'm unaware of, I'm not sure why it's not working.

Can anyone help?

Many thanks!

 

[Shadow#1]

A kid updated my Switch in lightning-quick speed about two hours ago. I snatched the thing immediately, but it already rebooted to Hekate, and since that the damage was done (seems to apply updates in the blink of an eye). I was relieved to find support for Atmosphere 14.0.0 dropped yesterday!

But after replacing the atmosphere folder with the latest (1.3.0), updating all sigpatches with the latest that support Atmos 1.3.0 and FW 14.0.0, I'm not having any luck actually booting into CFW. I get this error every time:

"A fatal error ocurred while running Fusee.
Incorrect fusee version! (program=0xb6b6ac70, mtc=0xb4dcf71)

Press POWER to reboot."

Pressing power takes me back to Hekate.

I'm not sure what's wrong here, I have updated all the files as far as I can tell, including Fusee. Unless there's another update that happened today that I'm unaware of, I'm not sure why it's not working.

Can anyone help?

Many thanks!

Update your payload

 

[skykid]

Update your payload

Sorry you bother you, and thanks for the response. Do you mean replace the Fusee.bin with the latest? I did that already, it's on the Atmosphere page. I use the Fusee.bin payload to boot into CFW always, and that's when I'm seeing the error.

 

[Hayato213]

Sorry you bother you, and thanks for the response. Do you mean replace the Fusee.bin with the latest? I did that already, it's on the Atmosphere page. I use the Fusee.bin payload to boot into CFW always, and that's when I'm seeing the error.

It is in pre-release state, not meant for general public use. You can try updating to the latest available fusee.bin if that doesn't help wait for official non pre release one.

 

[skykid]

It is in pre-release state, not meant for general public use. You can try updating to the latest available fusee.bin if that doesn't help wait for official non pre release one.

Right, I understand and I noticed it was pre-release. But I have seen other people updating using this already and it seems to work for them. That's why I can't understand why this Fusee.bin isn't running for me.

 

[Hayato213]

Right, I understand and I noticed it was pre-release. But I have seen other people updating using this already and it seems to work for them. That's why I can't understand why this Fusee.bin isn't running for me.

Have you try to replace all the cfw files?

 

[binkinator]

Sorry you bother you, and thanks for the response. Do you mean replace the Fusee.bin with the latest? I did that already, it's on the Atmosphere page. I use the Fusee.bin payload to boot into CFW always, and that's when I'm seeing the error.

did you update Hekate to latest release?

https://github.com/CTCaer/hekate

 

[skykid]

Ok, all fixed and updated to the latest everything!

Moral of the story: Don't be a moron like me. I completely forgot that now, using Hekate, the Fusee.bin that I kept overwriting in the root directory is useless, and it needs to be overwritten in the payloads directory that Hekate uses for boot options. I think that's what Shadow#1 was referring to when he said update payloads, I just misunderstood it for 20 minutes.

Allow me to apologise now twice, once for taking up your time (and I really appreciate the speed of response and help on this forum) and two, to allow me to piggyback with a further question:

At this point it would be wise to backup the emummc, I believe, in the event such a thing happens again so that I can restore the current working state. However I was SURE I did that when I first set up Hekate, yet when I restored the eMMC from the backup (and it seemed to process fine) it didn't actually have any effect.

Correct me if I'm wrong: I just go into Hekate (at this point) go to tools and click 'backup eMMC' and that should be it? Then if it's accidentally updated in future I can just restore eMMC?

EDIT: Ok ignore this. I don't have enough space on my card to partition and backup at the moment, it's almost full. This is probably why the restore didn't work the last time.

 

[Kulam]

Ok, all fixed and updated to the latest everything!

Moral of the story: Don't be a moron like me. I completely forgot that now, using Hekate, the Fusee.bin that I kept overwriting in the root directory is useless, and it needs to be overwritten in the payloads directory that Hekate uses for boot options. I think that's what Shadow#1 was referring to when he said update payloads, I just misunderstood it for 20 minutes.

Allow me to apologise now twice, once for taking up your time (and I really appreciate the speed of response and help on this forum) and two, to allow me to piggyback with a further question:

At this point it would be wise to backup the emummc, I believe, in the event such a thing happens again so that I can restore the current working state. However I was SURE I did that when I first set up Hekate, yet when I restored the eMMC from the backup (and it seemed to process fine) it didn't actually have any effect.

Correct me if I'm wrong: I just go into Hekate (at this point) go to tools and click 'backup eMMC' and that should be it? Then if it's accidentally updated in future I can just restore eMMC?

EDIT: Ok ignore this. I don't have enough space on my card to partition and backup at the moment, it's almost full. This is probably why the restore didn't work the last time.

 

[Kulam]

Ok, all fixed and updated to the latest everything!

Moral of the story: Don't be a moron like me. I completely forgot that now, using Hekate, the Fusee.bin that I kept overwriting in the root directory is useless, and it needs to be overwritten in the payloads directory that Hekate uses for boot options. I think that's what Shadow#1 was referring to when he said update payloads, I just misunderstood it for 20 minutes.

Allow me to apologise now twice, once for taking up your time (and I really appreciate the speed of response and help on this forum) and two, to allow me to piggyback with a further question:

At this point it would be wise to backup the emummc, I believe, in the event such a thing happens again so that I can restore the current working state. However I was SURE I did that when I first set up Hekate, yet when I restored the eMMC from the backup (and it seemed to process fine) it didn't actually have any effect.

Correct me if I'm wrong: I just go into Hekate (at this point) go to tools and click 'backup eMMC' and that should be it? Then if it's accidentally updated in future I can just restore eMMC?

EDIT: Ok ignore this. I don't have enough space on my card to partition and backup at the moment, it's almost full. This is probably why the restore didn't work the last time.

Hey mate, I am sorry, but what exactly did you do, to get it on work again. I am strugeling.

 

[skykid]

Hey mate, I am sorry, but what exactly did you do, to get it on work again. I am strugeling.

If you're having the exact same error as me, remember to download the latest atmosphere, and importantly, Fusee.bin. The Fusee.bin doesn't go in your root if you're using Hekate. You need to go to the Bootloader folder, and replace the Fusee.bin in there with the new one. I also updated literally everything else too in the process (sigpatches, hekate etc) but I think it was the Fusee.bin not being in the right folder that was causing the error.

 

[urherenow]

Hey mate, I am sorry, but what exactly did you do, to get it on work again. I am strugeling.

You need to update both hekate AND Atmosphere. If you inject the LATEST fusee, then hekate doesn't matter. If you inject hekate, you still need to make sure that you've updated all of Atmosphere, including fusee. fusee belongs in the /payloads folder (but could really be anywhere, as long as you manually create your own hekate_ipl.ini file). If you are still having issues, then you likely have a theme installed or an incompatible sys module. Just delete the entire Atmosphere folder, and extract Atmosphere from the latest release to have a fresh install. Test that first. THEN add your sys modules 1 by 1 until/unless something causes your system to not boot.

If you are using a mod chip, you likely need to rename hekate_ctcaer_5.7.2.bin to payload.bin, and place it in the ROOT of your sd card.

 

[PhyChris]

Kids! It can happen. Nature always finds a way.

 

[skykid]

Kids! It can happen. Nature always finds a way.

Never again.

 

[FungusCrunkus]

having the same issue. updated everything and nothing... started from new even and nothing, i dont know what i am doing wrong, but either way i have just wasted like 4 hours and im empty handed. im also new to this stuff so i probably could've done something stupid but i have been double checking and nothing still...

 

[Kulam]

It worked, deleting the atmosphere folder and intalling it new. Thank you so much.

 

[G33ksquad]

You helped me, thank you. Goofed after using the AIO updater.

 

[Don_Padoli]

RCM loader don´t work with 14.0.0 fusee.bin

 

[binkinator]

RCM loader don´t work with 14.0.0 fusee.bin

I just pushed fusee.bin from the latest 14.0.0 assets using my RCMLoader without issue. Mine is the older one (not the white box.) What version of RCMLoader are you using?

 

[Farkle]

If you're having the exact same error as me, remember to download the latest atmosphere, and importantly, Fusee.bin. The Fusee.bin doesn't go in your root if you're using Hekate. You need to go to the Bootloader folder, and replace the Fusee.bin in there with the new one. I also updated literally everything else too in the process (sigpatches, hekate etc) but I think it was the Fusee.bin not being in the right folder that was causing the error.