Skip to content

Atmosphere refuses to boot [Title ID 010000000000002B] #1173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
EmmmaTech opened this issue Sep 26, 2020 · 4 comments
Closed

Atmosphere refuses to boot [Title ID 010000000000002B] #1173

EmmmaTech opened this issue Sep 26, 2020 · 4 comments

Comments

@EmmmaTech
Copy link

What's the issue you encountered?

[ Describe the issue in detail and what you were doing beforehand. ]

What I was doing is after I booted up with Hekake, I tried to launch Atmosphere after doing a full NAND Backup, and it had a panic attack and refused to boot.

[ Did you make any changes related to Atmosphère itself? ]

I did not make any changes to Atmosphere.

How can the issue be reproduced?

I'm not sure how to reproduce this problem.

Crash Report

My crash report is in the fatal_errors folder and cannot be read.

System Firmware Version

10.2.0

Environment?

  • What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
    I used Hekate.

  • Official release or unofficial build:
    Official Build version 5.3.3

  • Do you have additional kips or sysmodules you're loading:
    Nothing.

  • Homebrew software installed:
    I don't have any Homebrew software installed.

Additional context?

I'm using a Nintendo Switch from July 2017, and my serial number is XAW1001944

@SciresM
Copy link
Collaborator

SciresM commented Sep 26, 2020

"cannot be read"

upload the binary. I can parse it.

@EmmmaTech
Copy link
Author

Okay. Here's the file:

report_07931687.bin.zip

@EmmmaTech
Copy link
Author

I found the issue. I forgot to turn off Share Error Information in Settings. I never knew it would crash if it was on.

@SciresM
Copy link
Collaborator

SciresM commented Sep 27, 2020

This was actually the same issue as #1124, #1145, and was fixed recently. The next Atmosphere release won't trigger the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants