SciresM
commented
2 years ago Fix your archive bits, this is an archive bit problem.
Closed admiralkikan closed 2 years ago
SciresM
commented
2 years ago Fix your archive bits, this is an archive bit problem.
admiralkikan
commented
2 years ago Interesting because I wouldn't have opened a ticket if I hadn't already tried to fix my archive bits. Whether through Hekate or manually setting/unsetting the archive box in properties settings. But thanks for the help I guess?
edit: Figured out the problem and fixed it. fixing the bit archive was not the solution.
ghost
commented
2 years ago You also didn’t fill out the help sheet correctly.
On Oct 30, 2021, at 9:02 PM, admiralkikan @.***> wrote:
Interesting because I wouldn't have opened a ticket if I hadn't already tried to fix my archive bits. Whether through Hekate or manually setting/unsetting the archive box in properties settings. But thanks for the help I guess?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
ghost
commented
2 years ago Actually never mind you have enough info, probably. But, if that didn’t help, try asking the switchroot discord?
On Oct 30, 2021, at 9:02 PM, admiralkikan @.***> wrote:
Interesting because I wouldn't have opened a ticket if I hadn't already tried to fix my archive bits. Whether through Hekate or manually setting/unsetting the archive box in properties settings. But thanks for the help I guess?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Bug Report
[ If any section does not apply, replace its contents with "N/A". ] [ Lines between [ ] (square brackets) should be removed before posting. ]
[ * ] [ Note: If the bug or crash you encountered is related to; ] [ - software used to make "backups", ] [ - software explicitly distributed for piracy, etc ] [ then contributors will not provide support for your issue and your issue will be closed. ]
What's the issue you encountered?
A fatal error occurred when running Atmosphére. Title ID: 010041544d530000 Error Desc: std::abort() called (0xffe)
[ Describe the issue in detail and what you were doing beforehand. ] [ Did you make any changes related to Atmosphère itself? ] [ If so, make sure to include details relating to what exactly you changed. ]
How can the issue be reproduced?
Boot into Hekate boot atmosphere in EmuMMC
[ * ] [ Include a detailed step by step process for recreating your issue. ]
Crash Report
Sorry, github kept giving my zip an error.
https://mega.nz/file/WvxgURjb#cpTeUi1jTkguVJ8ZsBbCzF92AUxIF1Snkar8wn_RCTI
[ Crash reports can be found under
/atmosphere/crash_reports. ] [ If your issue caused Atmosphère to crash, include the crash report(s) by creating a gist and pasting the link here. ] [ If you don't include a crash report in instances of crash related issues, we will ask you one to provide one. ]System Firmware Version
12.1.0
X.X.X [ Replace X's with system firmware version at time of crash. ] [ You can find your firmware version in the Settings -> System, under "System Update". ] [ If it says "Update Pending", you can clear the pending update by rebooting to Maintenance Mode. ]
Environment?
Hekate Atmosphère 1.2.2 sigpatches from itotaljustice EmuMMC is partitioned based
Additional context?
This was after having fixed sigpatch issue after updating Atmosphère from 1.0. Received an error in regards to 010041544f5300 even though the folder doesn't exist anywhere. I can only assume it's failing to create prodinfo backup. Card isn't corrupted, tried hekate bit fixer which resulted in no issues found. And I'm on windows so macOS solutions won't work. I did try a fresh Atmosphère folder, which landed me the same issue. The only thing I didn't try was restoring emuMMC. My prodinfo is encrypted though if that means anything.