Homebrew Question Getting 2011-0301 error on every CFW boot

[ecore]

Hi,

I got an unpatched switch (XAW100315xxxxx) recently, the firmware version is 3.0.2. Using a jig I can boot to RCM and the exploit test is a success.

I then followed Homebrew's Guide to use fusee-gelee to backup original NAND, install Kosmos, setup EmuMMC, etc. without error.

However, every time I choose "Launch - CFW (SYSNAND)" or "Launch - CFW (EMUMMC)", the CFW boots to the menu page (i.e. a home icon with "A Start" under it), and in a few seconds, the following error shows up.

The OFW (SYSNAND) boots without issue.

========
Error Code: 2011-0301 (0x25a0b)
Program: 010000000000000C
Firmware: 3.0.2 (Atmosphère 0.12.0-master-7bc0250c)
...
========

BTW: I have tried clearing WiFi settings without luck.

Searched for hours, saw people hitting on this error, but no one seems constantly getting it on boot.

So I would ask GBATemp for help --- Any solution to this issue? Also is a firmware update on SYSNAND likely resolve it and safe for my unit?

Your response is greatly appreciated!

 

[Dothackjhe]

Any good reason why you're stuck at a very low firmware version?

 

[Hayato213]

chain boot using fusee-primary.

 

[ecore]

Any good reason why you're stuck at a very low firmware version?

No specific reason, I'm still new to Switch CFW and trying to confirm that a fireware update on an unpatched unit is safe (and I've read somewhere that there are fuses built-in to prevent too many shifts of the firmware versions, so being cautious...).

So it sounds like a fireware update is likely to solve this issue?

--------------------- MERGED ---------------------------

chain boot using fusee-primary.

Tried "hekate + fusee-primary" resulted in the same error. I probably should try update the firmware.

 

[Dothackjhe]

No specific reason, I'm still new to Switch CFW and trying to confirm that a fireware update on an unpatched unit is safe (and I've read somewhere that there are fuses built-in to prevent too many shifts of the firmware versions, so being cautious...).

So it sounds like a fireware update is likely to solve this issue?

Your console having an old firmware kind of just caught my attention. I'm not even sure if it's relevant to the issue you're having.

But, then again, I do not see the point of sticking to an old firmware when recent games are now requiring at least a 9.X.X firmware to be played. Especially that some of those games are no longer patchable for lower firmware.

For example, if you're planning on playing Animal Crossing: New Horizon on its latest version, you would need your console to be in firmware 9.2.0 at least to enjoy it.

And you're right, it takes a special method to prevent your console from burning switches when upgrading to a higher firmware. It can only be intimidating at first, but the notion becomes significantly familiar after each time you try it with success.

As for what special method that is--you just have to properly use ChoiDuJourNX for it.

 

[ecore]

Your console having an old firmware kind of just caught my attention. I'm not even sure if it's relevant to the issue you're having.

But, then again, I do not see the point of sticking to an old firmware when recent games are now requiring at least a 9.X.X firmware to be played. Especially that some of those games are no longer patchable for lower firmware.

For example, if you're planning on playing Animal Crossing: New Horizon on its latest version, you would need your console to be in firmware 9.2.0 at least to enjoy it.

And you're right, it takes a special method to prevent your console from burning switches when upgrading to a higher firmware firmware. It can only be intimidating at first, but the notion becomes significantly familiar after each time you try it with success.

As for what special method that is--you just have to properly use ChoiDuJourNX for it.

Thanks a lot for the information. I'd give it a try now

 

[Hayato213]

No specific reason, I'm still new to Switch CFW and trying to confirm that a fireware update on an unpatched unit is safe (and I've read somewhere that there are fuses built-in to prevent too many shifts of the firmware versions, so being cautious...).

So it sounds like a fireware update is likely to solve this issue?

--------------------- MERGED ---------------------------


Tried "hekate + fusee-primary" resulted in the same error. I probably should try update the firmware.

When you update with ChoidujourNX it preserve your fuse count. even though when you updated the firmware, you could try a CFW bundle pack like Kosmos, you might have to edit the config to boot with the fusee-primary.

 

[ecore]

Thanks a lot for the information. I'd give it a try now

Confirmed update of firmware resolves the issue. Thanks all!

When you update with ChoidujourNX it preserve your fuse count. even though when you updated the firmware, you could try a CFW bundle pack like Kosmos, you might have to edit the config to boot with the fusee-primary.

Thank you, I'm using Kosmos now.