Well I think we found the source of your problem at least. Never ever use the AIO Updater. It is highly notorious for causing more issues than it fixes. Its going to be better to start fresh because there is no telling what stupid files it may or may not have installed. For starters, delete the /atmosphere folder and download the newest from the official GitHub page.
Well heck. There’s only one more directory to look at so we might as well finish the job…
Was mistaken, I actually used daybreak. Think I attempted to use AIO before but like you said its garbo. Anyways, for this problem specifically though I had successfully updated and everything was going fine, but I let the battery die and had to charge from AutoRCM for a bit.. then boom this issue.
No dice
Soooo, you’ve updated /atmosphere, Sigpatches and now /bootloader. You already updated /bootloader/payloads/fusee.bin. Your hekate_ipl.ini file is good and there are no archive bit issues. That’s almost the entire shootin match at this point. We might have to consider backing up your Emunand and formatting. How is that going btw? If Hekate isn’t your speed you can backup your emunand using EmuTool.
Had already backed up with hekate last night trying to solve this issue using this guide. Couldnt get EmmcHaccGen to create NX-(fw version)_exFAT so I came here.
Once you have a backup, use NXNandManager to see if you can recover your :USER/saves directory on from your emunand. If you can do this then it’s safe to simply format your SDCard and start from scratch. You will be able to manually recover your saves using JKSV like so:
What does your /bootloader/hekate_ipl.ini look like and do you have a file called /atmosphere/package3? If not you need to grab the latest atmosphere and unzip atmosphere.x.x.x.zip at the top level of your SDCard.
Figured haha. Appreciate you taking the time to help!
Yeah, sorry man. Once we’ve run through all that you’ve been through already, there’s not much else to look at. When you format, make sure you stick w/ FAT32. I use rufus to do so and set it as non-bootable and 32k block size.
I used the switch.homebrewguide one, and installed the recommended settings it prompted from sdsetup atmosphere was within those settings, could it be an outdated version tho? do you have a link to the most recent version? and it would be a case of removing the atmosphere folder and putting the other version in?
No worries. This one is fine: https://switch.homebrew.guide/
Just a matter of preference. I like to use an emunand in case anything happens to it I always have a clean Sysnand to go back to.
Sweet. While we're both here.. is there a way to make my sysnand 'clean' for the purposes of avoiding a ban? Believe I tampered with it when those early beta versions of atmosphere came out and emmummc wasnt available yet.
i removed the atmosphere that was the default one in the sdsetup package, and reinstalled the latest one from source at the top level of the sd card. the error message i'm now getting is:
Go into Hekate and see if you have an emunand (big emuMMC tile on the right of main page)created and enabled. If it says disabled then you missed a step somewhere.
perfect, it says disabled. do i just create one through the button on the right? also, what type do i need, SD file or SD Partition? is there a guide for creating one? i feel i'm so close, thanks so much for all your help
Great!
i followed the instructions on the guide and it said enabled, but wiped the sd card of all games and the atmosphere files. so I readded them, but now when I try to boot using tegrarcmGUI it accepts the payload, hetake logo comes up on the switch, then the noise to say the switch has been disconnected from my pc sounds and the screen goes black on the switch?
Great. Let me go back and look at your hekate_ipl.ini (assuming it’s been copied back).
