a fatal error occurred when running atmosphere что делать
A fatal error occurred when running Atmosphere #847
Comments
HyImTIm commented Mar 23, 2020
Bug Report
A fatal error occurred when running Atmosphere.
Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_0000000061b2685.bin
What’s the issue you encountered?
After booting up Atmosphere, through Hekate, screen goes black and I receive the fatal error message
How can the issue be reproduced?
Boot to RCM
Launch Hekate
Boot Atmosphere through either fusèe-primary or emunand
Crash Report
System Firmware Version
The text was updated successfully, but these errors were encountered:
SciresM commented Mar 23, 2020
Run archive bit fixer in hekate, you have invalid archive bits (probably you use macOS) that are causing atmosphere to be unable to interact with the SD card the way it needs to.
HyImTIm commented Mar 23, 2020
I am using windows and when I ran it, it still persists
SciresM commented Mar 23, 2020
HyImTIm commented Mar 23, 2020
Okay so I am getting two different errors. When I boot atmosphere from launch
HyImTIm commented Mar 23, 2020
I still cannot boot through launch
CTCaer commented Mar 23, 2020 •
Irrelevant with your issue. This means that your hekate boot entry is wrong or you are missing files.
As for the archive bit, you need to run both options in hekate, which you didn’t run.
Reminder that Windows also sets that bit on new or changed files. And mostly depends on the program that created or changed that file. (So either you didn’t delete the atmosphere folder when extracting the files anew or your extractor sets the bit)
EDIT:
Same with the switch folder that hbmenu depends on. Archive bit set equals no apps showing.
HyImTIm commented Mar 23, 2020
My apologies but I am not sure what you mean by all that lol
HyImTIm commented Mar 23, 2020
Okay I got it all working now thank you.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Проблемы и их решения
Проблемы с запуском прошивки
Возможные пути решения проблемы:
Возможные пути решения проблемы:
Возможные пути решения проблемы:
Нажмите кнопку (POWER), чтобы запустить прошивку и обновите EmuNAND Полная копия NAND, расположенная на карте памяти. Применяется для того, чтобы оставить официальную прошивку в максимально нетронутом виде. Например, на приставке используется аппаратная уязвимость, поэтому пользователь может использовать чистый и не изменённый NAND обновив его до последней прошивки. Это будет назваться SysNAND. Он может использоваться для официальных игр и даже для онлайна. А в эмунанде уже будет находиться полная копия сиснанда, но использоваться уже с кастомной прошивкой и без доступа к сервисам Nintendo для игры в пиратку. до актуальной версии системного ПО
Отформатируйте вашу карту памяти в FAT32.
Если не помогает, переустановите kefir Сборник, состоящий из выбранного кастома, необходимых программ и скриптов, которые все это установят правильным образом. Состав кефира и инструкцию по установке можно посмотреть в его репозитории начисто. Для этого удалите с карты памяти всё, кроме папки Nintendo и emummc (или sxos/emunand) и ставьте кефир заново
Обновите kefir Сборник, состоящий из выбранного кастома, необходимых программ и скриптов, которые все это установят правильным образом. Состав кефира и инструкцию по установке можно посмотреть в его репозитории
Проблемы с запуском игр
Возможно, вы удалили тикеты всех игр. Для переустановки тикетов, запустите tinfoil, перейдите на вкладку “Тикеты”, и для каждой игры проделайте следующее:
Для переустановки тикетов, запустите tinfoil, перейдите на вкладку “Тикеты”, и для каждой игры проделайте следующее:
Проблемы с файлами / картой памяти
Нет ни одной причины закидывать игры на карту памяти. Сразу устанавливайте их рекомендуемым способом по MTP через DBI!
Перезагрузите приставку. Если это не помогло, исправьте атрибуты
Нужно исправить атрибуты.
Вам нужно установить драйвер exFAT. Для этого проделайте безопасное обновление прошивки. Его нужно делать даже в том случае, если у вас и так стоит последняя версия взламываемой прошивки! Повторное обновление просто установит отсутствующий драйвер. А вообще, переходите на FAT32!
Проверьте свою SD-карту на ошибки, а затем установите кефир через скрипт.
Проблемы с Homebrew или родительским контролем
Вам нужно обновить форвардер
Проблемы с железом
Проблемы с системой
Имеется ввиду обновление игры. Скачайте его и установите как обычную игру. Так же сбросить проверку версии можно через DBI. Запустите программу, выберите Browse installed applications, нажмите (Y), чтобы выделить все пункты, нажмите (A), а затем выберите Reset required version. DBI должен быть запущен из режима апплета, кефир должен быть свежим. Иначе магия не сработает.
Fatal error ocurred when running Atmosphére #010041544d530000 #813
Comments
DreamDevourer commented Feb 5, 2020
Bug Report [Fatal Error Ocurred when running Atmosphére.]
Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)
Press POWER to reboot.
What’s the issue you encountered?
I was in version 9.0.1, but when I had updated to the 9.1.0 using ChoiDujourNX, the Atmosphere stop working, I formated my SD (from ExFat) to FAT32 but that not worked,I’ve tried to use chmod and chflags, but nothing works. But the Update was sucessfully, because I tested using sxos, but I prefer Atmosphere.
I not changed anything in the atmosphere folder and a have tried a clean installation with only Atmosphere.
How can the issue be reproduced?
Just injecting the Atmosphere payload 10, 10.1 or 10.2
the issue happens after the White Icon splash screen
Crash Report
System Firmware Version
9.1.0 and Atmosphére 10, 10.1 & 10.2
Environment?
Additional context?
When I have tried with clean Atmosphere installation the report was the same, but the some description was in Bold and Yellow.
The text was updated successfully, but these errors were encountered:
Ness-666 commented Feb 15, 2020
I am having the exact same issue, the only thing I thing that I can think of is that i had removed my prod.info and since then lost my back up. Not sure if that would effect it though.
SciresM commented Feb 15, 2020
This currently isn’t supported by Atmosphere.
Manuel-Flores-F commented May 14, 2020
This is usually due to an archive metadata bit used by some OS’s that Horizon simply can’t deal with. Here’s how to fix it:
Barkermush commented May 17, 2020
I’m getting this exact same problem. It was fine until I updated from 10.0.1 to 10.0.2.
I updated atmosphere, I’ve formatted the memory card and tried a clean install but I’m still getting this error.
I think I might have to try a full nand backup too, as I don’t seem to be getting anywhere.
SciresM commented May 17, 2020
«same problem» probably not. literally any error in ams.mitm generates this symptom to user. Upload your report binary.
Barkermush commented May 17, 2020
Ah I never knew that, thanks.
I will do that now.
Barkermush commented May 17, 2020
«same problem» probably not. literally any error in ams.mitm generates this symptom to user. Upload your report binary.
Sorry to be a pain but do you have a link to something showing how to get the ‘binary report’ had a look on hekate and can’t see anything for that.
The only stuff I can dump to my sd card is ‘console info/soc info.. Ipatches & bootrom.. fuses’ etc
SciresM commented May 17, 2020
When an error occurs, a report is saved in /atmosphere/fatal_errors
Barkermush commented May 17, 2020 •
When an error occurs, a report is saved in /atmosphere/fatal_errors
Thanks.
Uploaded the error report below:
Barkermush commented May 17, 2020
Barkermush commented May 17, 2020 •
When an error occurs, a report is saved in /atmosphere/fatal_errors
Wow, I have managed to sort it. After looking at some other threads, I needed to format the sd card to fat32 (need to download a 3rd party app to do this, as Win10 as no fat32 option)
Never had a problem with atmosphere and exfat from 8.00 patches up until this 10.0.2 patch. This is the first time I have needed to have my sd card in fat32 format.
Ah well, just glad I didn’t have to do a full nand 😀
yokanes commented Sep 22, 2020 •
A fatal error ocurred when running atmosphere.
itittle ID: 010041544d530000
error desc: std::abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_00000000559655.bin
Press POWER to reboot.
I though is a problem with my micro sdxc 128 gb and decided bought a new micro sd xc of 256 gb and make the same steps for the new micro sdxc of 256 gb and the same issue appears again.
Can u help me?
Fatal error occured when running atmosphere #967
Comments
Ex0hm commented May 26, 2020 •
Bug Report
What’s the issue you encountered?
I updated from 9.2exfat to 10.0.2exfat with Choi after rebooting when i tried to play a game it prompted me if i want to update or start the software instead of starting I accidentally pressed update and now I’m on 10.0.3 and it asks me to update my sdxc to be able to use exfat but when i try to update it says firmware up to date so i rebooted to payload and this is the error im getting
Did you make any changes related to Atmosphère itself?
How can the issue be reproduced?
Updating to latest software via NSP?
Crash Report
A fatal error has occurred when running atmosphere
Title ID: 010041544d530000
Error desc: std : : abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_0000000005ec2477.bin
System Firmware Version
Environment?
Bootloader: Fuseè
AMS 0.12.0
Using android to copy and send files since I don’t have a laptop
The text was updated successfully, but these errors were encountered:
mikookoi commented May 27, 2020
man i have the same error i don know how fix that
Ex0hm commented May 27, 2020
man i have the same error i don know how fix that
I found out that it wasn’t an error from atmosphere but from the firmware it updated to instead of having the exfat driver it installed the non exfat version of the firmware, what I’m doing right now is using my 32gb SDHC card to reupdate my current 10.0.3 to 10.0.3 exfat by using choi but Incant seem to find any 10.0.3 Firmware dump.
Ex0hm commented May 27, 2020
man i have the same error i don know how fix that
I found out that it wasn’t an error from atmosphere but from the firmware it updated to instead of having the exfat driver it installed the non exfat version of the firmware, what I’m doing right now is using my 32gb SDHC card to reupdate my current 10.0.3 to 10.0.3 exfat by using choi but Incant seem to find any 10.0.3 Firmware dump.
Tried it but i can’t update my current 10.0.3 to 10.0.3exfat, so I really don’t know how to solve this and I don’t know if there is a way to just install the exfat driver manually since nintendo just says your firmware is already up to date.
SciresM commented May 28, 2020
@Ex0hm Format your SD card as FAT32, or overwrite package2 with exFAT firm manually. Either way, not an atmosphere issue, heh.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Panic occurred while running Atmosphere: Title ID 010000000000002B #1256
Comments
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?
Additional context?
I am not able to mount the emu RAW partition with nyx.
Feel free to reach me if you need extra information.
The text was updated successfully, but these errors were encountered:
jlafaye commented Dec 6, 2020
I was not able to upload the binary file so I have base64 encoded it.
EmreTech commented Dec 6, 2020
Try turning off Send Error Information in Settings? Same thing happened to me when I started out.
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.
jlafaye commented Dec 7, 2020
SciresM commented Dec 7, 2020
Adubbz commented Dec 7, 2020 •
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 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 commented Mar 16, 2021
@jlafaye Can you go though the process on how to convert the saves in the user partition for Edizon?
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 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.