2144 0001 ошибка switch

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

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

How can the issue be reproduced?

Crash Report

System Firmware Version

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

1. I only recently started modifying the Switch.

2. 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)

1. 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.

How can the issue be reproduced?

Crash Report

System Firmware Version

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 ]

Bug Report

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?

Crash Report

System Firmware Version

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.