You should upgrade or use an alternative browser.
Hacking (Atmosphere) Error when trying to run anything from album — Error code 2144-0001 (0x290)
-
Thread starterSagarc
-
Start dateMay 24, 2021
-
Views
36,731 -
Replies
33
-
#1
I switched from SXOS to Atmosphere recently because SXOS is not supporting FW after 11.0.0, so i needed to start using Atmosphere to be able to update to 12.0.2 and play newer games like Miitopia, but now i’m facing a problem when i try to run anything from the album, like ChoiDuJourNX for example. I tried running ChoiDuJourNX on SXOS and it works perfecly, but on Atmosphere it gives this error, both on the same FW (11.0.0). I don’t know if i’m missing a file or doing something wrong, i just don’t want to have to downgrade to 11.0.0 every time i need to update the firmware of my Switch using SXOS. I tried FW 10.2.0, 11.0.0, 12.0.0 and 12.0.2. All of them give the same error when trying to run anything from the album using Atmosphere. I even bought a brand new Micro SD card but the problem persists.
May 24, 2021
-
#2
Second, start homebrew via title redirection (hold r while starting a game) to use full ram memory. Album has only a few 100 mb’s.
-
#3
First of all, use daybreak for updating
Second, start homebrew via title redirection (hold r while starting a game) to use full ram memory. Album has only a few 100 mb’s.
Ok, i did the title redirection and the Atmosphere error didn’t show, but now the switch gives me another error when i try to launch from the album: «The software was closed because an error occurred» I tried 5 different softwares, the only one that didn’t crash was daybreak
May 24, 2021
-
#4
- Joined
- Jun 12, 2018
- Messages
- 145
- Trophies
- 0
- Age
- 51
- XP
-
135
- Country
-
-
#5
——————— MERGED —————————
I am getting the same error, how do I fix this, I see this when I try to run Goldleaf.
Attachments
-
#6
How do I fix this error 2144?——————— MERGED —————————
I am getting the same error, how do I fix this, I see this when I try to run Goldleaf.
TinWoo or Awoo-Installer are recommended instead of Goldleaf.
- Joined
- Jun 12, 2018
- Messages
- 145
- Trophies
- 0
- Age
- 51
- XP
-
135
- Country
-
-
#7
TinWoo or Awoo-Installer are recommended instead of Goldleaf.
Could the issue be that my game backup is an xci file?
-
#8
Could the issue be that my game backup is an xci file?
Modern NSP installers can also install XCI files, so that is unlikely the issue.
-
#10
This is the error I get. Also How do I remove Applet Mode?
To avoid applet mode, use a game title to launch homebrew instead of the photo album. By default on Atmosphere, holding R on a game will launch the homebrew launcher in title override, which will give homebrew more memory to function.
You need to make sure you have the proper signature patches on your SD card. You can find the proper patches here:
https://github.com/ITotalJustice/patches/releases
Use the fusee patches if you launch Atmosphere with fusee-primary. If you are using Hekate, and you aren’t using it to chainload fusee-primary, use the hekate patches instead.
- Joined
- Jun 12, 2018
- Messages
- 145
- Trophies
- 0
- Age
- 51
- XP
-
135
- Country
-
-
#11
Jun 5, 2021
- Joined
- Jun 12, 2018
- Messages
- 145
- Trophies
- 0
- Age
- 51
- XP
-
135
- Country
-
-
#12
——————— MERGED —————————
ok, I used Atmosphere, went to Awoo, it still shows Applet Mode, but when I tried to install the game from my sd card, I got an NCA signature error, I let it installl the game anyway to see if it works. but once the game is installed, what do I use to play the game?
Nevermind, I just went to the home menu, and the game was there.
- Joined
- Mar 10, 2020
- Messages
- 4
- Trophies
- 0
- Age
- 38
- XP
-
37
- Country
-
-
#13
-
#14
May I know how you solve this? I got the same issue
Reading the complete post the instructions are there:
- Always use title redirection to run homebrew loader (not applet mode)
- Use daybreak to update firmware
- Update all your homebrew
- And if you use it, upgrade all sigpatches
-
#15
May I know how you solve this? I got the same issue
What homebrew application is causing the issue?
——————— MERGED —————————
- Joined
- Apr 10, 2020
- Messages
- 217
- Trophies
- 0
- Age
- 33
- XP
-
1,043
- Country
-
-
#16
-
#17
Ditto, I just started having this same issue
What homebrew application is causing the issue?
- Joined
- Apr 10, 2020
- Messages
- 217
- Trophies
- 0
- Age
- 33
- XP
-
1,043
- Country
-
-
#18
What I read was that the applet form only has 100mb of memory so having multiple things running in the background would make it crash
-
#19
I installed a game and when i try to load with atmoopshere it says cant start software.
When i go to album its in applet mode but i cant get out becuase i have no games working
-
#20
I am having the same issue.
I installed a game and when i try to load with atmoopshere it says cant start software.
When i go to album its in applet mode but i cant get out becuase i have no games working
This is likely due to not having the most recent sigpatches. Accessing the homebrew launcher through the album will always result in applet mode (limited memory). What you need to do is holding R button while launching a game, which should bring you to the homebrew launcher with full memory access (no applet mode displayed on your screen).
https://github.com/ITotalJustice/patches/releases
Similar threads
You may also like…
- No one is chatting at the moment.
-
@
x65943:
Finally they are banning teaching gravity in school, little pricks can get back to farming and praising the lord+2
-
@
BigOnYa:
Funny, i remember having to learn cursive writing, square dancing, ebonics… what happen to those? -
@
Veho:
They were replaced by «cell theory».+1
-
@
Veho:
The silly notion that human bodies are composed of «cells» and powered by «mitochondria» and not composed from clay and powered by the soul.+1
-
@
Psionic Roshambo:
My new religion is going to be awesome, orgies and booze and fun rides!+1
-
@
Psionic Roshambo:
Our father who is currently on the water slide, forgive our party and someone turn up that song it’s awesome!+1
-
@
The Real Jdbye:
i don’t recall ever having to learn dancing in school -
@
BigOnYa:
yup in gym class, middle school… we had to pair up boy with girl, random picked, and learn square dancing. Yeee hah! 30+ years ago. -
@
Psionic Roshambo:
Lucky when I was in school we had to learn to hide from nuclear bombs and eat bugs and basic survival skills lol+1
-
@
Psionic Roshambo:
Psi lived in a different lifetime… They made us to be like Rambo lol+1
-
@
Psionic Roshambo:
Sure I can operate most weapons and I know a thousand ways to kill someone, but who teaches us how to live a quiet life?+1
-
@
K3N1:
Stop trying to cancel people ReZ -
@
Psionic Roshambo:
New roofie jello pudding pops. -
@
K3N1:
Did he buy Hogwarts legacy also what an evil man -
@
Psionic Roshambo:
He just needs Harry Potter’s sleep spell -
@
Psionic Roshambo:
Rapius Maximus Sleepy Time Perversio! -
@
K3N1:
Or maybe engorgio so he can actually get someone -
@
K3N1:
Rezsmum told me about them said it’s the perfect size for her stealth toys
@
K3N1:
Rezsmum told me about them said it’s the perfect size for her stealth toys
Today at 6:49 PM
Содержание
- Служба поддержки Nintendo приветствует вас
- Описание:
- Необходимые действия:
- Появляется ли ошибка после перезапуска консоли?
- На вашей консоли установлена новейшая версия системы?
- Сохраняется ли ошибка?
- Проблема не была решена:
- Сохраняется ли ошибка?
- Проблема не была решена:
- Проблема не была решена:
- Поиск в разделе «Поддержка»
- Error code 2144-0001 #1511
- Comments
- Bug Report
- What’s the issue you encountered?
- How can the issue be reproduced?
- Crash Report
- System Firmware Version
- Environment?
- Additional context?
- Homebrew RetroArch and pFBA: Error 2144-0001 (0x290)
- c0dehunter
- Error Code: 2144-0001 (0x290) Appears after update
- Bug Report
- What’s the issue you encountered?
- How can the issue be reproduced?
- Crash Report
- System Firmware Version
- Environment?
- Additional context?
- Atmosphere crashing after update to 1.1.1 Error code 0x290 (2144-0001) qlaunch process
- DonKedick
Служба поддержки Nintendo приветствует вас
Описание:
На консоли Nintendo Switch появляется код ошибки 2144-0001.
Необходимые действия:
- Перезапустите консоль Nintendo Switch, удерживая кнопку POWER в течение трех секунд, а затем выберите «Параметры электропитания» > «Перезапустить».
- Если консоль не отвечает, удерживайте кнопку POWER в течение двенадцати секунд, чтобы принудительно отключить ее, а затем снова включите устройство.
Появляется ли ошибка после перезапуска консоли?
На вашей консоли установлена новейшая версия системы?
Сохраняется ли ошибка?
Проблема не была решена:
Консоль Nintendo Switch необходимо отдать в ремонт.
Щелкните здесь, чтобы оформить заявку на техобслуживание.
Если ошибка исчезла, вероятно, предыдущие действия способствовали ее устранению.
Продолжайте пользоваться консолью и наблюдайте за ее состоянием.
Сохраняется ли ошибка?
Проблема не была решена:
Если проблема сохраняется, консоль Nintendo Switch необходимо отправить в ремонт.
Щелкните здесь, чтобы оформить заявку на техобслуживание.
Если ошибка исчезла, вероятно, предыдущие действия способствовали ее устранению.
Продолжайте пользоваться консолью и наблюдайте за ее состоянием.
Проблема не была решена:
Если проблема сохраняется, консоль Nintendo Switch необходимо отправить в ремонт.
Щелкните здесь, чтобы оформить заявку на техобслуживание.
Поиск в разделе «Поддержка»
Вы собираетесь покинуть сайт Nintendo of Europe. Компания Nintendo of Europe не несет ответственность за контент и безопасность сайта, который вы собираетесь посетить.
Русский язык недоступен.
Вы пытаетесь получить доступ к контенту, который не переведен на русский язык, но эта информация есть на английском языке. Хотите посмотреть?
Спасибо, что зашли на веб-сайт Nintendo! Наша система выбрала вас для участия в опросе. Уделив всего лишь несколько минут и поделившись своим мнением, вы поможете нам улучшить наш веб-сайт.
Естественно, вся информация, предоставленная вами в данном опросе, будет рассматриваться как конфиденциальная.
Источник
Error code 2144-0001 #1511
Bug Report
I am getting Error code 2144-0001. I just updated to the latest software of atmosphere
[ 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?
[ 1- I updated my switch to the latest software. I uploaded the latest atmosphere software. When I clicked on albums, it gave me Error code 2144-0001]
[ Did you make any changes related to Atmosphère itself? I did not make any changes to atmosphere. This was my first time performing the install of a software ]
[ If so, make sure to include details relating to what exactly you changed. ]
How can the issue be reproduced?
[ Include a detailed step by step process for recreating your issue.I followed the steps in downloading the sdsetupzip file and dragging hekate to my dad card and atmosphere, boot loader, sept, switch.
the upload was successful and when going to my album the error occured ]
Crash Report
[ 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
[ 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?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate
- Official release or unofficial build:
- [ Official release version x.x.x (or) unofficial build ]
- [ If using an unofficial build, include details on where/how you acquired the build. ]
- [ Ex: Self-compilation ]
- [ Ex: Kosmos’ distribution of Atmosphère ]
- Do you have additional kips or sysmodules you’re loading:
- Homebrew software installed: [ * ]
- EmuMMC or SysNAND:
- [ If using an EmuMMC, include whether it’s partition-based or file-based. ]
Additional context?
- Additional info about your environment:
- [ Any other information relevant to your issue. ]
The text was updated successfully, but these errors were encountered:
Источник
Homebrew RetroArch and pFBA: Error 2144-0001 (0x290)
c0dehunter
Well-Known Member
Hello all,
Here is my dilemma:
When I was on firmware 9.0.1 (using Hekate 5.0.2, and Atmosphere 2018 version (I am not sure about the exact version), both RetroArch and pFBA loaded fine, and I could get all the arcade and SNES/GENESIS ROMs running on the system.
If I updated my Atmosphere / Hekate, both pFBA and RetroArch would generate 2144-0001 (0x290) , as soon as I launched them.
So, I decided to have TWO different miniSD cards:
— One miniSD card with the latest Atmosphere / Hekate, for Switch games (you know, modern, recent games)
— The other miniSD card with the initial versions of Atmosphere / Hekate (when I jailbroken my Switch, back in 2018), for running pFBA and (RetroArch (basically old school retro games)
This dual setup worked really well, until some newer games forced me to upgrade firmware from 9.0.1 to the latest 12.0.3 (as of 06/22/2021 that is).
Now here is the issue:
When I insert my original miniSD card (with 2018 versions of Atmosphere / Hekate), the Switch does not boot at all (blank screen, but I know it is ON).
If I run the Hekate_ctcaer_5.0.2 payload, I get to the Hekate screen, but when I click on any of the three boot options, screen goes blank, and I get back to the main Hekate screen.
How can I run RetroArch and pFBA without the getting the error 2144-0001 (0x290) .
Источник
Error Code: 2144-0001 (0x290) Appears after update
Anakin072 opened this issue a year ago · comments
Bug Report
Error Code: 2144-0001 (0x290) Will not let me launch any homebrew applications. I have tried to reinstall atmosphere, my sigpatches, specific homebrew applications that don’t work to no avail.
What’s the issue you encountered?
I was attempting to update Pokemon Brilliant Diamond until Tinfoil failed to launch. I then noticed no other homebrew programs were working either.
How can the issue be reproduced?
I updated my Switch firmware and my atmosphere and I can no longer do any homebrew-related tasks. It does boot into atmosphere though, just nothing homebrew related is usable.
Crash Report
System Firmware Version
Environment?
I have been using the latest version of atmosphere, replacing the files and sigpatches don’t see, to work.
Additional context?
None of this happened before updating to 1.3.2.0, no apps installed through homebrew will launch or will say there is an error.
Piracy is not supported
- Piracy/signature patches not supported.
- 2345-0007 from hbloader means sd card corruption, not an atmosphere issue.
There is no piracy involved. I own Brilliant Diamond but cant update through nintendo online as my switch is banned.
Источник
Atmosphere crashing after update to 1.1.1 Error code 0x290 (2144-0001) qlaunch process
DonKedick
Member
Atmosphere crashing after update to 1.1.1.
Atmosphere was updated from 0.19.3 to 1.1.1. After updating, Atmoshpere was working and booting into CFW just fine but after switching games the system crashed and I got error code Error code 0x290 (2144-0001). Full error report pasted below. After performing the 30 second power reset the switch rebooted into the stock mode. I was then able to enter RCM and injected fusee.bin via TegraRcm (the fusee.bin associated with the Atmoshpere 1.1.1 release. The switch booted, passed the first two atmosphere splash screens, got to the switch splash screen then had another fatal error 0x1B5C02 (2002-3502). I am using FW 11.0.1. Please help!
First crash while loading a game:
Atmosphère Fatal Report (v1.1):
Result: 0x290 (2144-0001)
Program ID: 0100000000001000
Process Name: qlaunch
Firmware: 11.0.1 (Atmosphère 1.1.1-master-99c74469e)
General Purpose Registers:
Start Address: 00000039be600000
Stack Trace:
ReturnAddress[00]: 00000039be80e098
ReturnAddress[01]: 00000039be68c7b4
ReturnAddress[02]: 00000039be8e61b0
ReturnAddress[03]: 00000039be8e629c
ReturnAddress[04]: 00000039be8e5d30
ReturnAddress[05]: 00000039bef51264
ReturnAddress[06]: 00000039bef28788
ReturnAddress[07]: 00000039be93c9b0
ReturnAddress[08]: 00000039be93c1dc
ReturnAddress[09]: 00000039be7f1618
ReturnAddress[10]: 00000039be7f4884
ReturnAddress[11]: 0000000000000000
ReturnAddress[12]: 0000000000000000
ReturnAddress[13]: 0000000000000000
ReturnAddress[14]: 0000000000000000
ReturnAddress[15]: 0000000000000000
ReturnAddress[16]: 0000000000000000
ReturnAddress[17]: 0000000000000000
ReturnAddress[18]: 0000000000000000
ReturnAddress[19]: 0000000000000000
ReturnAddress[20]: 0000000000000000
ReturnAddress[21]: 0000000000000000
ReturnAddress[22]: 0000000000000000
ReturnAddress[23]: 0000000000000000
ReturnAddress[24]: 0000000000000000
ReturnAddress[25]: 0000000000000000
ReturnAddress[26]: 0000000000000000
ReturnAddress[27]: 0000000000000000
ReturnAddress[28]: 0000000000000000
ReturnAddress[29]: 0000000000000000
ReturnAddress[30]: 0000000000000000
ReturnAddress[31]: 0000000000000000
Second Crash when loading fusee.bin via Tegra
Atmosphère Fatal Report (v1.1):
Result: 0x1B5C02 (2002-3502)
Program ID: 0100000000000024
Process Name: ssl
Firmware: 11.0.1 (Atmosphère 1.1.1-master-99c74469e)
General Purpose Registers:
Start Address: 0000006f23000000
Stack Trace:
ReturnAddress[00]: 0000006f23008d58
ReturnAddress[01]: 0000006f23036bac
ReturnAddress[02]: 0000006f2306a99c
ReturnAddress[03]: 0000006f23069a78
ReturnAddress[04]: 0000006f23069878
ReturnAddress[05]: 0000006f23061388
ReturnAddress[06]: 0000006f2322bda4
ReturnAddress[07]: 0000006f2322b9e4
ReturnAddress[08]: 0000006f231c57a4
ReturnAddress[09]: 0000006f231bac54
ReturnAddress[10]: 0000006f231baee8
ReturnAddress[11]: 0000006f231ce184
ReturnAddress[12]: 0000006f231cda74
ReturnAddress[13]: 0000006f231d66c8
ReturnAddress[14]: 0000006f231bc630
ReturnAddress[15]: 0000006f231bc3ac
ReturnAddress[16]: 0000006f231740d0
ReturnAddress[17]: 0000006f23171f0c
ReturnAddress[18]: 0000006f2316f898
ReturnAddress[19]: 0000006f231596e0
ReturnAddress[20]: 0000006f2315939c
ReturnAddress[21]: 0000006f2315cda8
ReturnAddress[22]: 0000006f230cce1c
ReturnAddress[23]: 0000006f230cd620
ReturnAddress[24]: 0000006f230c7fc4
ReturnAddress[25]: 0000006f230d83fc
ReturnAddress[26]: 0000006f2304b93c
ReturnAddress[27]: 0000006f2304baec
ReturnAddress[28]: 0000006f2304b9b0
ReturnAddress[29]: 0000006f2304bc10
ReturnAddress[30]: 0000006f23043150
ReturnAddress[31]: 0000006f2306482c
Источник
Bug Report
I am getting Error code 2144-0001. I just updated to the latest software of atmosphere
[ 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?
[ 1- I updated my switch to the latest software. I uploaded the latest atmosphere software. When I clicked on albums, it gave me Error code 2144-0001]
[ Did you make any changes related to Atmosphère itself? I did not make any changes to atmosphere. This was my first time performing the install of a software ]
[ If so, make sure to include details relating to what exactly you changed. ]
How can the issue be reproduced?
[ * ]
[ Include a detailed step by step process for recreating your issue.I followed the steps in downloading the sdsetupzip file and dragging hekate to my dad card and atmosphere, boot loader, sept, switch.
the upload was successful and when going to my album the error occured ]
Crash Report
[ 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.0.2
[ 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?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate
- Official release or unofficial build:
- [ Official release version x.x.x (or) unofficial build ]
- [ If using an unofficial build, include details on where/how you acquired the build. ]
- [ Ex: Self-compilation ]
- [ Ex: Kosmos’ distribution of Atmosphère ]
- Do you have additional kips or sysmodules you’re loading:
- Homebrew software installed: [ * ]
- EmuMMC or SysNAND:
- [ If using an EmuMMC, include whether it’s partition-based or file-based. ]
Additional context?
- Additional info about your environment:
- [ Any other information relevant to your issue. ]
Recommended Posts
-
- Share
Updated my Nintendo Switch and Atmosphere Files on my Nintendo Switch and downloaded the updated version on Checkpoint and every time I go to Album on my Nintendo Switch to open up the Homebrew menu I then go to Checkpoint and I get this error code. I looked up how to fix it and nothing is making any sense. Can anyone help me fix this issue?
Link to comment
Share on other sites
-
- Share
7 minutes ago, Gajeel said:
Updated my Nintendo Switch and Atmosphere Files on my Nintendo Switch and downloaded the updated version on Checkpoint and every time I go to Album on my Nintendo Switch to open up the Homebrew menu I then go to Checkpoint and I get this error code. I looked up how to fix it and nothing is making any sense. Can anyone help me fix this issue?
I don’t think Checkpoint has updated in a while, especially not with recent Atmosphere changes.
You may have to stop using Checkpoint for the time being. (I switched over to JKSV a while back)
Link to comment
Share on other sites
- Author
-
- Share
Just now, theSLAYER said:
I don’t think Checkpoint has updated in a while, especially not with recent Atmosphere changes.
You may have to stop using Checkpoint for the time being. (I switched over to JKSV a while back)
Okay so do you recommend I look up a video on how to use JKSV with Pkhex?
Link to comment
Share on other sites
-
- Share
9 minutes ago, Gajeel said:
Okay so do you recommend I look up a video on how to use JKSV with Pkhex?
Yes and no.
It’s rather simple. Just load the homebrew, and dump the save.
Then you’ll get the same save format as the one checkpoint would have provided.
I would think you should be able to figure it out by performing trial and error on it for a small bit :3
Link to comment
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Sign in
Already have an account? Sign in here.
Sign In Now
Bug Report
Error Code: 2144-0001 (0x290) Will not let me launch any homebrew applications. I have tried to reinstall atmosphere, my sigpatches, specific homebrew applications that don’t work to no avail.
What’s the issue you encountered?
I was attempting to update Pokemon Brilliant Diamond until Tinfoil failed to launch. I then noticed no other homebrew programs were working either.
How can the issue be reproduced?
I updated my Switch firmware and my atmosphere and I can no longer do any homebrew-related tasks. It does boot into atmosphere though, just nothing homebrew related is usable.
Crash Report
(https://gist.github.com/Anakin072/1a017065dbaf623f5b027e4f6f78dd32)
System Firmware Version
1.3.2.0|AMS 1.2.5|S
Environment?
I have been using the latest version of atmosphere, replacing the files and sigpatches don’t see, to work.
Additional context?
None of this happened before updating to 1.3.2.0, no apps installed through homebrew will launch or will say there is an error.
Bug Report
n/a
What’s the issue you encountered?
Local multiplayer for animal crossing new world results in communication error regardless of game version. Not sure if I’ve enabled some sort of setting to disable local multiplayer as it finds the village but instantly fails to connect. Was working on atmosphere 1.0 but since updating to 1.2.5 on firmware 13.1.0 the feature seams broken.
How can the issue be reproduced?
Trying to connect 2 switchs on local multiplayer
Crash Report
N/a
System Firmware Version
13.1.0 U
Environment?
- fusèe bootloader
- Official release version 1.2.5
- Do you have additional kips or sysmodules you’re loading: no
- Homebrew software installed: [ Goldleaf, tinfoil, Daybreak, retroarch, lockpick, reboot-to-payload ]
- SysNAND:
Additional context?
I have tried on both Animal Crossing New Horizon version 2.0 as well as 1.1.0 and both have failed. I am not using idnmitm cfg. The 2 consoles do connect receiving a message «We found the island, loading now» following by «Preparing to board» Then instantly receiving » Communication error» then returning to the game. Any help would be much appreciated.
My Switch was working fine. Then I downloaded the tinfoil «self installer» and after running that, I can no longer get into CFW sys Atmosphere.
To be clear, what I see is the Atmosphere logo, and then a persistent black screen.
I can get into Hekate payload using my RCMloader, but not the fusee payload. Selecting «CFW (sysMMC)» in Hekate used to work fine, but now I get the same persistent black screen that I do when trying to use fusee payload. Selecting CFW emuMMC just complains with an error because I don’t have that setup. Selecting Fusee from Hekate gives me the same black screen. Selecting Stock loads me into the stock firmware without CFW as expected.
I also tried to re-initialize from within the stock firmware so that the internal memory would be reset. That changed nothing. I have 3 different cards, all of them work, and I’ve tried both FAT32 and exFAT.
Any ideas? Any way I can get some debug out of this situation?
Bug Report
What’s the issue you encountered?
After upgrading firmware to 13.0.0+exfat on HOS using daybreak, crashes on startup. Trying to resurrect a HOS that was upgraded with a fat32 version, i performed an upgrade on fat32 card to add exfat drivers, then copying back file-based firmware to exfat card. HOS launches on fat32 card, crashes on exfat card.
A fatal error occurred when running atmosphere
Program ID: 010041544d530000
Error Desc: std::abort() called (0xffe)
How can the issue be reproduced?
startup of HOS from atmosphere launch screen generates error after atmosphere logo
Crash Report
report_0000000006e7c6ac.bin.txt
System Firmware Version
13.1.0. HOS 13.0.0
Environment?
hekate official 5.6.5. atmosphere 1.2.4
Homebrew software installed: most of the normal. Tinfoil. Checkpoint. a pretty long list, no emuiibo or other apps, no custom themes
Emummc File based
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?
The fusee is not mounting to my sd card. My sd card works fine and have a storage space of 128gb. I couldn’t figure out the error and it was working before hand. I made no changes and the crash error report file is empty
[ 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?
[ * ]
[ Include a detailed step by step process for recreating your issue. ]
Crash Report
[ 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
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?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
- Official release or unofficial build:
- [ Official release version x.x.x (or) unofficial build ]
- [ If using an unofficial build, include details on where/how you acquired the build. ]
- [ Ex: Self-compilation ]
- [ Ex: Kosmos’ distribution of Atmosphère ]
- Do you have additional kips or sysmodules you’re loading:
- Homebrew software installed: [ * ]
- EmuMMC or SysNAND:
- [ If using an EmuMMC, include whether it’s partition-based or file-based. ]
Additional context?
- Additional info about your environment:
- [ Any other information relevant to your issue. ]
##I’m needing help to fix this
Bug Report
Panic occured while running Atmospherre .
Title ID: 01007EF00011E000
Error: std : : abort (OxFFE)
What’s the issue you encountered?
When I started a with atmospherre modified game I got this report: (look to Bug report)
How can the issue be reproduced?
Don’t know it
Crash Report
Error report can be found under /atmosphere/fatal_errors/report_0a0971eee.bin.
I can’t tranfer it to my PC because it’s saying that the file is damaged
System Firmware Version
My version is 13.1.0
Environment?
bootloader Atmosphère was launched by: fusee
- Do you have additional kips or sysmodules you’re loading: No
- Homebrew software installed: Yes
- EmuMMC or SysNAND: EmuMMC
-If using an EmuMMC, include whether it’s partition-based or file-based: Don’t know it
Additional context?
It is only crashing by loading modded Zelda BOTW
I was Just modding my Switch for a few days.
(Sori for bat inglish)
Bug Report
-
I only recently started modifying the Switch.
-
When I started a with atmospherre modified game I got this error code:
Panic occured while running Atmospherre .
Title ID: 01007EF00011E000
Error: std : : abort (OxFFE)
- I would look forward to some nice tips.
Bug Report
What’s the issue you encountered?
Ring Fit Adventure always crash when enter settings of the game.
How can the issue be reproduced?
Open the game, select Adventure, press Y to go into Settings, wait or select anything and crash into atmosphere error screen.
Crash Report
Is an atmosphere crash but there is nothing inside crash_reports
System Firmware Version
12.0.3
Environment?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
- Hekate 5.6.5
- Official release or unofficial build:
- Atmosphere 1.2.4-master-e256261b8
- EmuMMC or SysNAND:
- SysNAND
Additional context?
- Additional info about your environment:
Error Code: 2162-0002 (0x4a2)
Program: 010000000000100F
Firmware: 12.0.3 (Atmosphere 1.2.4-master-e256261b8)
Game: Ring Fit Adventure (1.2.0)
Other games work fine for this console, even this game if you dont enter in settings.
Bug Report
What’s the issue you encountered?
Switch doesn’t automatically wake-up from sleepmode when undocking.
How can the issue be reproduced?
- Put switch in sleepmode
- Undocking
- Switch doesn’t automatically wake-up (Switch wake up and show lock screen on OFW 13.1.0)
Crash Report
N/A, no crash on my switch
System Firmware Version
12.1.0 on emuNand, 13.1.0 on sysNand
Environment?
Hekate v5.6.5
Atmosphere v1.2.4 w lastest sigpatches
Homebrew app:
Checkpoint
No theme
No game mode installed
Additional context?
N/A
Ring Fit Adventure crashed while entering settings of the game.
Error Code: 2162-0002 (0x4a2)
Program: 010000000000100F
Firmware: 12.0.3 (Atmosphere 1.2.4-master-e256261b8)
Game: Ring Fit Adventure (1.2.0)
Other games work fine for this console, even this game if you dont enter in settings.
Bug Report
What’s the issue you encountered?
Atmosphere’s ams_mitm seems to abort in a specific modded game when game started
[Error message]
Panic occured while running atmosphere
TitleID: 010041544D530000
Error Desc: std:abort() (0xFFE)
How can the issue be reproduced?
Most of the modded game files, (except for the romfs.bin) are well applied but cause errors in certain games.
The following three games where the errors I found occur.
:
Resident Evil 6 — (01002A000CD48000)
Dragon’s Dogma (JPN) — (010032C00AC58000)
Football Manager 2020 Touch — (0100DA500EFB0000)
※ The following three games have an error, even if put an empty single folder in a romfs folder.
※ What’s unusual is that the Dragon’s Dogma (JPN) makes errors, but the Dragon’s Dogma (USA) works well without errors.
Crash Report
N/A
System Firmware Version
9.1.0
Environment?
What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate
Official release or unofficial build: Official release version — Atmosphère 0.10.1
Do you have additional kips or sysmodules you’re loading: sys-clk
Homebrew software installed: N/A
Additional context?
Additional info about your environment: N/A
[ Any other information relevant to your issue. ]
Bug Report
N/A
What’s the issue you encountered?
I got brilliant diamond and shining pearl from gamestop and started playing them
after that, atmospere stopped booting. it always panics when trying to boot
I tried to edit some of the config files
I removed the ; ‘s from the system settings config files
How can the issue be reproduced?
just boot into amosphere after installing updates and playing bdsp.
Crash Report
I couldn’t find one
System Firmware Version
13.1.0
Environment?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate
- Official release or unofficial build: Official release version 1.2.4
- Do you have additional kips or sysmodules you’re loading: yes
- Homebrew software installed: [ * ]
- EmuMMC or SysNAND: SysNAND
Additional context?
Bug Report
What’s the issue you encountered?
Pokemon Brilliant Diamond and Shining Pearl occasionally crashes when I’m using cheat codes. I’ve mostly been using the 60fps cheat. The Error code I get is 2168-0002 (0x4a8) Program: 420000000007E51A.
I haven’t made any changes to Atmosphere beside from adding the necessary folders for cheats under the contents directory, changing ;dmnt_cheats_enabled_by_default = u8!0x1 to dmnt_cheats_enabled_by_default = u8!0x0 under system settings, and adding overlays and other things to use Tesla and EdiZon.
How can the issue be reproduced?
The issue can be reproduced by often turning cheats on and off in rapid succession but also by normally playing the game with a cheat on.
Crash Report
Gist
System Firmware Version
13.1.0
Environment?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by: Fusee
- Official release or unofficial build: Official release Atmosphère 1.2.4
- Do you have additional kips or sysmodules you’re loading: Does nx-ovlloader count as a sysmodule? I’m not sure what a sysmodule is. Also I have sigpatches.
- Homebrew software installed: JKSV, AIO Switch Updater, Goldleaf, Daybreak, and others.
- EmuMMC or SysNAND: EmuMMC not sure if file or partition based because it’s been a while since I hacked my switch.
Additional context?
N/A
What’s the issue you encountered?
panic occured while running atmosphere..
How can the issue be reproduced?
i dont know just randomly
Crash Report
https://drive.google.com/file/d/1FH45Al7q5FI2hjFy44KcKGwKxvh19To6/view
System Firmware Version
13.1.0
Environment?
i use hekate 5.6.5
ams 1.2.4
-
Homebrew software installed
sys-clk
jksv
hb appstore
ftpd
nxshell
nxtheme installer
themezernx -
EmuMMC or SysNAND:
emummc — partition base
Bug Report
What’s the issue you encountered?
Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)
Press POWER to reboot.
[ attempting to boot atmosphere in any capacity from hekate on my switch always will receivethe aforementioned fatal error.]
[ Did you make any changes related to Atmosphère itself?
No. ]
[ N/A ]
How can the issue be reproduced?
[ * ]
[ launch Atmosphere from hekate launch menu.]
Crash Report
[ N/A ]
[ sorry gist doesnt let me upload an atmos report
https://www.dropbox.com/s/mjr9g4awkk3yj43/report_00000000082d1980.bin?dl=0 ]
[ N/A ]
System Firmware Version
13.1.0
[ Mariko Hoag ]
[ N/A]
Environment?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by: Hekate
- Official release or unofficial build:
- [ 5.6.5 official build, Atmosphere 1.2.4 latest Fusee]
- [ N/A]
- [ Ex: Self-compilation ]
- [ Ex: Kosmos’ distribution of Atmosphère ]
- Do you have additional kips or sysmodules you’re loading: N/A
- Homebrew software installed: [ Atmosphère defaults]
- EmuMMC or SysNAND: Both
- [ File based but also attempted with it completely wiped]
Additional context?
- Additional info about your environment:
- [ N/A ]
Hi
Im not sure what to put here but whenever I try to load atmosphere I get a yellow screen after i select the one I want to load. I have updated both Hekate and Atmosphere.
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?
[ The Fatal Error code (stated above) showed up and I did everything to make atmosphere work again, but I keep getting that error]
How can the issue be reproduced?
[ * ]
[ I downloaded the new firmware release here and unzipped the file into my SD card, then booted it with fusee, but it showed the error message and I didn’t change anything internal in atmosphere. ]
Crash Report
[ 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
13.1.0
[ 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?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by: Fusee
- Official release or unofficial build: Official Release
- [ Official release version x.x.x (or) unofficial build ]
- [ If using an unofficial build, include details on where/how you acquired the build. ]
- [ Ex: Self-compilation ]
- [ Ex: Kosmos’ distribution of Atmosphère ]
- Do you have additional kips or sysmodules you’re loading: N/A
- Homebrew software installed: N/A [ * ]
- EmuMMC or SysNAND: (IDK)
- [ If using an EmuMMC, include whether it’s partition-based or file-based. ]
Additional context?
- Additional info about your environment:
- [ Any other information relevant to your issue. ]
What’s the issue you encountered?
Hello, I am having an issue with my joy-cons not staying connected to my switch when undocking them from handheld mode. , I’ve tried using 2 different pairs of switch Joy-Cons and 1 Switch Controller, which were working fine before, This problem seems to happen with every other update for me. When in OFW it works fine.
added:
Sys-Bot latest
Checkpoint
EdiZon SE
Goldleaf
Hb App Store
JKSV
Nxdumptool
Sys clk Management
How can the issue be reproduced?
Undocking switch controller from the switch
Crash Report
N/A My switch hasn’t crashed.
System Firmware Version
13.1.0
Environment?
Atmosphere v1.2.4
The bootloader I use is Hekate v5.6.5
Software added:
Sys-Bot latest
Checkpoint
EdiZon SE
Goldleaf
Hb App Store
JKSV
Nxdumptool
Sys clk Management
Additional context?
If you need any more info, just ask. I have also Kept the same software on each update. It has happened to be previous in other versions but it normally gets fixed in the next update.
Bug Report
What’s the issue you encountered?
When try to load a FIFA 19 game cartridge or in any other format in atmosphere 1.2.4…..an error ocurred and game close
The game can charge until black screen whith nintendo switch logos in the corners…. but after that… an error message is received while starting the game «the software was closed because an error occurred»
This error only show in recents release of atmosphere
the game not start in:
13.0 or 13.1 / atmos 1.0.0 or 1.1.1 or 1.2.0 or 1.2.1 or 1.2.4
12.1 / atmos 1.0.0 or 1.1.1 or 1.2.0 or 1.2.1 or 1.2.4
the game work on:
13.1 stock
12.1 / atmos 19.5
12.1 / atmos 20.1
other cartridge games work in any version of atmosphere… older and newer version of atmos….. only fifa 19 not work
How can the issue be reproduced?
starting a fifa 19 original game cartridge or any other digital format
Crash Report
an error message while starting FIFA 19 «the software was closed because an error occurred»
01637129791_0100ffa0093e8000.log
System Firmware Version
13.1 , also tried on 12.1
Environment?
Clean and fresh atmosphere new release whith newest hekate bottloader… and chainload fusee.bin payload
-
Clean atmosphere 1.2.4
-
Clean Hekate
-
All other complementary files updated needed to work
-
No sysmoduls installed
-
Homebrew software installed:
- JKSV
- HEKATE TOOLBOX
-
EmuMMC:
- EmuMMC partition-based
Additional context?
tried on three diferent switch with same results
The game work with atmosphere 20.1 or lower…. the issues may be releated to the old file folder sept… but i not an expert
all other game cartridge works fine
Stratosphere configurated with NOGC = 0
I tried with airplane mode on and off
Sorry for my english is not my mother tongue
When I try to play newly downloaded music onto sys tune and play them, my switch either ignores it or crashes. I have been trying to fix it for over a week and nothing has worked. Please let me know how to fix this.