Yes, it's working again after a fresh install, altohugh I had to delete my hekate_ipl.ini.
But what did I do wrong exactly ?
I'm 10.0.2 AMS 16.2 with Hekate 5.5.1 and sigpatches now....can I download firmware 11.0.1 ?
Last edited by Nashan67,
Yes, it's working again after a fresh install, altohugh I had to delete my hekate_ipl.ini.
But what did I do wrong exactly ?
I'm 10.0.2 AMS 16.2 with Hekate 5.5.1 and sigpatches now....can I download firmware 11.0.1 ?
Not sure what you did wrong, maybe something related to your .ini files? If you don't have anything specific for your setup in there, you might as well overwrite them when prompted. Could also be a combination of outdated sysmodule + hekate autoboot
And yeah, you should be able to download the latest FW just fine. Also about update.bin, it's just a renamed hekate payload.
Last edited by Homlet,
De rien kop1, sorry it went wrong the first time, but I believe the same would have happened if you did it manually. Hope everything goes well next time if you decide to use it again
Last edited by Homlet,
I had a similar issue to you.Used AiO updater for the first time today... my CFW won't boot anymore
I had emuMMC 10.0.2 with AMS 14.4 and hekate 5.5.1 working fine. I downloaded firmware 11.0.1 first (without updating yet) then I updated sigpatch then atmosphere to 16.2 and finally Hekate to 5.5.1 (because I think Hekate must be updated after atmosphere) I always answered no to overwrite .ini's files. Then I was prompted to reboot to a specific payload which I did...and then the Hekate's splashscreen showed up and I can't get anything else now.
I tried deleting Atmosphere, bootloader, config and firmware and making fresh copy of atmosphere and hekate from windows but I still get stuck at Hekate's splash screen and can't access Nyx.
Also I noticed an update.bin file is created on my microSD when I try booting the switch.
Any help ?
I updated hekate and fusee primary and atmosphere also allowed overwrite when it asked followed by firmware update.
It wouldn't reboot.
I had to manually put hekate , fusee primary bin with atmosphere and files onto the sd card to fix it.
I have another switch to do next weekend thats set up the same so will back up the sd card at each step tosee if I can narrow down what folder / file caused this.
Last edited by baileyscream,
I definitely will, I have a second switch to update.
My hekate_ipl.ini file had "atmosphere=1" which doesn't seem to be present anymore in new ini's files. Might it be the reason ?
It's the only difference I can find or think of.
No, if you click on it, it changes it!
You can also do customs pre-sets if you put internet.json (add what you want) at config/aio-switch-updater/internet.json https://github.com/HamletDuFromage/aio-switch-updater/blob/master/internet.json
Last edited by Homlet,
Another question: about cheats: how does it work exactly ?
I did download them and I had the bad surprise to discover cheats enabled on my super mario odyssey save, which makes the game pretty buggy and unplayable.
I tried disabling cheats with Checkpoint but it looks like they're always back and can't be removed.
Have I turned all my saves cheated and ruined without any way to return them without cheat ?
I did download them and I had the bad surprise to discover cheats enabled on my super mario odyssey save, which makes the game pretty buggy and unplayable.
I tried disabling cheats with Checkpoint but it looks like they're always back and can't be removed.
Have I turned all my saves cheated and ruined without any way to return them without cheat ?
https://www.cfwaifu.com/edizon-cheats/#disable-auto-cheats
You need to disable them being active by default in AMS
so i was under the assumption you couldnt update atmosphere anymore with tools like this? how does this get around it? I dont want to update if it might break stuff
"sept/payload.bin" and "atmosphere/fusee-secondary.bin" cannot be overwritten while HOS is running. The app extracts everything else, extracts those two files elsewhere, then reboots to a payload that moves those files where they should be and finally reboots to fusee-primary (or hekate)
I just updated to ams 0.17 yesterday without any hiccup
Last edited by Homlet,
So once I transfer the NRO to the /Switch file, do I just run this like Tinfoil and it updates both AMS and Sigs??
Any need for a new Payload or Hardboot?
Any need for a new Payload or Hardboot?
Once you run it, you'll have the ability to update atmosphere, hekate and sigpatches. You don't need to hardboot, but if you want to inject a payload at later time, you should make sure to inject the correct (latest) one
https://www.cfwaifu.com/edizon-cheats/#disable-auto-cheats
You need to disable them being active by default in AMS
Similar threads
