I JUST completed the upgrade to latest atmosphere/hekate yesterday. I got a message while playing about updating software again... am I safe to do this in OFW?
Thank you in advance.
Thank you in advance.
https://gbatemp.net/threads/can-someone-help-me.606951/#post-9733551Hi, can anyone help? Didn't want to open a new thread as I've seen quite a few regarding it but I'm stuck - I have an SX Core Mariko switch that I've recently picked up again (not used for a year or so), so I've been trying to get it swapped over from SX OS 3.0.5 to Atmosphere.
When I launch Atmosphere through Hekate (downloaded all the latest stuff from hxxps://rentry.org/mys8q) I get the following error: Package1 seems corrupt!
I've done some digging and this is related to corrupted boot0/boot1 files from choi, for which I don't have a backup of, I think I was going from 11.0.0 -> 10.2.0, I've had a look around and everyone mentions to look on xbins, I couldn't find these on there and the instructions here (hxxps://rentry.org/SwitchFAQ#error-fatal-error-nxboot-couldnt-parse-boot0) didn't really make much sense to me - how can I check the following? Ensure that your SysNAND is on the same version as your EmuNAND
And once I've done that, it tells me to backup my EmuMMC and then restore the same EmuMMC, doesn't mention to restore a valid boot0/boot1?
I still have my SX OS SD card so I can boot into SX OS but really would like to get this patched and updated to Atmosphere so I can play later games like Pokemon Arceus, as my current FW is 10.2.0.
Any help for a noob is much appreciated!

It is only safe if you have never run CFW/homebrew. You risk a ban by doing so if you have used CFW or homebrew even once.I JUST completed the upgrade to latest atmosphere/hekate yesterday. I got a message while playing about updating software again... am I safe to do this in OFW?
Thank you in advance.
Well if you go into System Settings, you can check the firmware of sysMMC & emuMMC although if you can't boot into them, you'll have to go off of memory. Anyway, maybe the issue isn't a corrupt package1 but your CFW isn't fully updated. Download the latest Atmosphere & Hekate from the source; their official GitHub pages.Hi, can anyone help? Didn't want to open a new thread as I've seen quite a few regarding it but I'm stuck - I have an SX Core Mariko switch that I've recently picked up again (not used for a year or so), so I've been trying to get it swapped over from SX OS 3.0.5 to Atmosphere.
When I launch Atmosphere through Hekate (downloaded all the latest stuff from hxxps://rentry.org/mys8q) I get the following error: Package1 seems corrupt!
I've done some digging and this is related to corrupted boot0/boot1 files from choi, for which I don't have a backup of, I think I was going from 11.0.0 -> 10.2.0, I've had a look around and everyone mentions to look on xbins, I couldn't find these on there and the instructions here (hxxps://rentry.org/SwitchFAQ#error-fatal-error-nxboot-couldnt-parse-boot0) didn't really make much sense to me - how can I check the following? Ensure that your SysNAND is on the same version as your EmuNAND
And once I've done that, it tells me to backup my EmuMMC and then restore the same EmuMMC, doesn't mention to restore a valid boot0/boot1?
I still have my SX OS SD card so I can boot into SX OS but really would like to get this patched and updated to Atmosphere so I can play later games like Pokemon Arceus, as my current FW is 10.2.0.
Any help for a noob is much appreciated!
thanks so much.It is only safe if you have never run CFW/homebrew. You risk a ban by doing so if you have used CFW or homebrew even once.
I went through everything and checked but my hekate_ipl file looked correct, i.e it had the correct line in about the payload fusee.bin, was that the issue with yours?does this thread help you at all?
I downloaded the latest ones from the official GitHub pages, I know I've definitely used Choi before in the past so I'm guessing that's the case of a corrupted boot0/boot1Well if you go into System Settings, you can check the firmware of sysMMC & emuMMC although if you can't boot into them, you'll have to go off of memory. Anyway, maybe the issue isn't a corrupt package1 but your CFW isn't fully updated. Download the latest Atmosphere & Hekate from the source; their official GitHub pages.

Well you can if you want to take the risk. There is no guarantee you will be banned but there is also no guarantee you won't be banned.thanks so much.
does this mean I can't ever update software in OFW seeing as how I've played in CFW many times?

Try generating a new BOOT0/BOOT1 with EmmcHaccGenI downloaded the latest ones from the official GitHub pages, I know I've definitely used Choi before in the past so I'm guessing that's the case of a corrupted boot0/boot1
Thanks
I went through everything and checked but my hekate_ipl file looked correct, i.e it had the correct line in about the payload fusee.bin, was that the issue with yours?
Thanks anyway
Well you can if you want to take the risk. There is no guarantee you will be banned but there is also no guarantee you won't be banned.

Or you can do what I do and download the update files illegally from the Internet. I certainly have never had any issues while doing so.I suppose the only way to update a game is by downloading it on tinfoil and downloading all subsequent updates, and then playing it on cfw. is that a fair assessment?
i think i was launching the old payload. opened up my atmosphere had fusee mtc and fusee-secondary, i just copyed over the current fusee.bin off of the github site.@vampier206 Let me rephrase: what payload are you loading with Hekate? Specifically, are you using the old fusee-primary.bin payload or the new fusee.bin? If you've updated atmosphere recently, you also need to replace your old payload with the new one. Also, don't update your hekate payload without also updating the rest of hekate, or it won't load successfully.
yeahhh. I thought so. This was the kind of stuff I was referring to. Some people mention methods to avoid bans and speak definitively "Do this to avoid getting banned". And some users in their guides don't even talk about it. Its been very inconsistent tryting to learn about the Switch firmware scene.There is no guide to avoid getting banned because the only reason people get banned is going online after using CFW/homebrew. If you don't go online after using CFW/homebrew, you won't get banned.
update the bootrloader hekate _ipl file to select the new fusee.bin and got this.i think i was launching the old payload. opened up my atmosphere had fusee mtc and fusee-secondary, i just copyed over the current fusee.bin off of the github site.
do i need to change any files to see that new .bin file??

Personally, I try to avoid spreading any opinions & only stick to the facts. Problem is I can't speak for the rest of the community.yeahhh. I thought so. This was the kind of stuff I was referring to. Some people mention methods to avoid bans and speak definitively "Do this to avoid getting banned". And some users in their guides don't even talk about it. Its been very inconsistent tryting to learn about the Switch firmware scene.
The tism is very strong in these communities.
Post your hekate_ipl.ini fileupdate the bootrloader hekate _ipl file to select the new fusee.bin and got this. View attachment 295972
I did in my last postPersonally, I try to avoid spreading any opinions & only stick to the facts. Problem is I can't speak for the rest of the community.
Post your hekate_ipl.ini file
I did in my last postPersonally, I try to avoid spreading any opinions & only stick to the facts. Problem is I can't speak for the rest of the community.
Post your hekate_ipl.ini file
I just updated my switch to 13.0.0 using daybreak but now whenever I try to turn on my switch, it turns on and goes to hetake, when I open the fusee.bin file with the 13.0.0 update, it shows atmosphere then goes black, then the atmosphere logo then it stays black. What should I do so it can actually load up my switch again