Skip to content

Panic occurred while running Atmosphere: Title ID 010000000000002B #1256

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
jlafaye opened this issue Dec 6, 2020 · 15 comments
Closed

Panic occurred while running Atmosphere: Title ID 010000000000002B #1256

jlafaye opened this issue Dec 6, 2020 · 15 comments

Comments

@jlafaye
Copy link

jlafaye commented Dec 6, 2020

Bug Report

What's the issue you encountered?

Atmosphere crashes with a panic error message shortly after the atmosphere spash screen.

Title ID: 010000000000002B
Error: std::abort (0xFFE)

How can the issue be reproduced?

The crash happens systematically.
I noticed it first with OFW 10.2.0 & atmosphere 0.15. Upgrading to 0.16 does not fix the issue.

On the same SD card, starting with a recreated emuMMC & a vanilla install of Atmosphere 0.16 and hekate_ctaer 5.5 allow the console to boot. Atmosphere is hosted on a FAT32 partition.

Restoring the (broken?) emuMMC leads to the panic error.

Crash Report

System Firmware Version

System version at time of crash 10.2.0
I am not able to start the CFM+emuMMC so I am not able to confirm if a console update is pending

Environment?

  • bootloader: hekate_5.5.0
  • official build of atmosphere, downloaded from github
  • Do you have additional kips or sysmodules you're loading: I don't think so because I started with a fresh install of atmosphere
  • Homebrew software installed: the ones provided with atmosphere + aio-switch-updated (never started though)

Additional context?

I am not able to mount the emu RAW partition with nyx.

Feel free to reach me if you need extra information.

@jlafaye
Copy link
Author

jlafaye commented Dec 6, 2020

Crash report.

I was not able to upload the binary file so I have base64 encoded it.

https://gist.github.com/jlafaye/907a3614e8f4d80d0d48c36ea753ae18

@EmmmaTech
Copy link

Try turning off Send Error Information in Settings? Same thing happened to me when I started out.

@SciresM
Copy link
Collaborator

SciresM commented Dec 6, 2020

You have a corrupt system settings save. Delete the relevant save file and allow settings sysmodule to recreate it, or just do what you did and create a fresh/clean system state.

Either way, not an atmosphere bug.

@SciresM SciresM closed this as completed Dec 6, 2020
@jlafaye
Copy link
Author

jlafaye commented Dec 7, 2020

Thank you for the quick reply. How can deleting the system settings save be achieved ?

@SciresM
Copy link
Collaborator

SciresM commented Dec 7, 2020

Pinging @Adubbz ^.

@Adubbz
Copy link
Collaborator

Adubbz commented Dec 7, 2020

You can use hekate's USB tools to mount your emuMMC's RAW GPP (Make sure you turn off Read-Only mode at the bottom). You can then use HacDiskMount's "Open physical drive" option on your PC (it'll show up as something like hekate SD GPP) to mount the SYSTEM partition of your NAND. From here, go into the save folder and delete the files named 8000000000000050 and 8000000000000052. Then, unmount the SYSTEM partition in HacDiskMount and then unmount the GPP in Windows and reboot your console.

@Adubbz
Copy link
Collaborator

Adubbz commented Dec 7, 2020

To add to this, you probably have a corrupt PRODINFO in your emuMMC. You can use HacDiskMount to restore that from a backup too. Make sure you restore this before regenerating your save files.

@jlafaye
Copy link
Author

jlafaye commented Dec 10, 2020

Thank you for your guidance. I deleted the files 8000000000000050 and 8000000000000052 as you mentioned but this resulted in a black screen.
Nevertheless, it pointed out that HacDiskMount can be used to mount the USER partition. Going this way, I was able to recover the saves and convert them into a suitable format for Edizon. So a new emuMMC indeed but with my BOTW save.

@bejamartins
Copy link

@jlafaye Can you go though the process on how to convert the saves in the user partition for Edizon?

@jlafaye
Copy link
Author

jlafaye commented Mar 16, 2021

I am pretty sure I started with @Adubbz's suggestion of mounting the firmware partition through HacDiskMount. I am not able to remember the exact procedure I followed but it involved no tool and a comparison of save filenames. I did not perform an actual conversion of the files. Sorry for not being able to provide more guidance.

@bejamartins
Copy link

bejamartins commented Mar 16, 2021

I am pretty sure I started with @Adubbz's suggestion of mounting the firmware partition through HacDiskMount. I am not able to remember the exact procedure I followed but it involved no tool and a comparison of save filenames. I did not perform an actual conversion of the files. Sorry for not being able to provide more guidance.

Thank you though. The mounting part I had understood, the conversion or compatibility part was where I was stuck at. Meanwhile, I discovered a tool called Switch Army Knife that did the trick for me. I used Checkpoint to restore it rather than EdiZon, can't get EdiZon to work with it.

@Tidybloke
Copy link

@Adubbz

I know this is closed but could you help?
I was directed here from my issue #1416 (which was closed before I could try this fix) and I followed your instructions but now I get a black screen. Not even the Atmosphere splash screen.

Is there anything you can think of that I could try to recover it?

@Adubbz
Copy link
Collaborator

Adubbz commented Apr 23, 2021

If that doesn't work I would suggest restoring a non-corrupt backup. https://suchmememanyskill.github.io/guides/unbrick/ is probably more comprehensive regarding what you should do in absence of one though.

@hero3210
Copy link

hero3210 commented Jun 17, 2023

You can use hekate's USB tools to mount your emuMMC's RAW GPP (Make sure you turn off Read-Only mode at the bottom). You can then use HacDiskMount's "Open physical drive" option on your PC (it'll show up as something like hekate SD GPP) to mount the SYSTEM partition of your NAND. From here, go into the save folder and delete the files named 8000000000000050 and 8000000000000052. Then, unmount the SYSTEM partition in HacDiskMount and then unmount the GPP in Windows and reboot your console.

Thank you so much for your helpful reply.

If you can please edit your reply to say "emu RAW GPP" instead of "emuMMC's RAW GPP" to avoid confusions since this is what it's called now in Hekate.
With a quick glance I actually edited the only one I saw with "MMC" which was the eMMC, and this caused the Home Button to stop working in SysNand, thankfully I made a backup beforehand and when I restored it everything went back to normal.
I am not trying to blame you or anything, just a small suggestion to avoid future confusions. Thanks again.

For everyone coming here:
eMMC is the for the SysNand
emuMMC is the for the EmuNand

@Chakyllfcu
Copy link

You can use hekate's USB tools to mount your emuMMC's RAW GPP (Make sure you turn off Read-Only mode at the bottom). You can then use HacDiskMount's "Open physical drive" option on your PC (it'll show up as something like hekate SD GPP) to mount the SYSTEM partition of your NAND. From here, go into the save folder and delete the files named 8000000000000050 and 8000000000000052. Then, unmount the SYSTEM partition in HacDiskMount and then unmount the GPP in Windows and reboot your console.

When I try to mount the disk I got this: what can I do?

image

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

8 participants