Hacking panic occured while running atmosphere, title ID: 010041544D530000 PLEASE LATEST FW 9.1.0

[williamxxll]

could someone help me with this error?
I'm not managing to solve
if anyone has a tutorial I would appreciate it

--------------------- MERGED ---------------------------

Would you help me ?

i'm solved!
i am incognitoed and i have backup file(prodinfo.bin)
i am version up to 9.1.0 then error title ID: 010041544D530000
incognito_rcm.bin restore not work!! fuck
so i restored with hetake emumm restore..
but not solved. same error
i can check NxNandManager_v3.0.3_x64
i know prodinfo not encrypt, prodinofof encrypt
you can see
switchbrew.org/w/index.php?title=Flash_Filesystem#User_Partitions
prodinfo encrypt
so i encrypt my prodinfo with NxNandManager_v3.0.3_x64
and restored with hetake emumm restore.

then incognito_rcm.bin WORK!!!!!!!!!!!!!!!!!!!!

Would you help me ?

 

[LyuboA]

i got the same error when i try to launch hbmenu - album in game on Atmos 0.11.1 FW 9.2.0 turns out it was the latest sys-con i turned that off issue was gone turn it back on same issue and if i try to open album while nsp forwarder is launched like for goldleaf app it crashes with the album title id guess they need to fix that

 

[mafaveli]

Getting the same error on firmware 10.0.0 "panic occured while running atmosphere, title ID: 010041544D530000", really unsure of what to do, first time hacking a switch. Should I start from scratch with my SD card formatting and preparation? I tried the archive bit fixing feature on hekate. No luck.

That stops the atmosphere crash, but the switch will not boot into cfw, just boots directly into stock. I used tegraexplorer payload to format and partition the sd card for emuMMC.

I used the sd card setup suggested from the ultimate noob switch homebrew guide which Links the sdsetup site. Where I selected the default kosmos package. I added tinfoil, and sig patches (found on done forum posts here for firmware 10.0.0).

Help on how I might resolve the issue would be great

 

[Chicky_Nuggie]

Getting the same error on firmware 10.0.0 "panic occured while running atmosphere, title ID: 010041544D530000", really unsure of what to do, first time hacking a switch. Should I start from scratch with my SD card formatting and preparation? I tried the archive bit fixing feature on hekate. No luck.

That stops the atmosphere crash, but the switch will not boot into cfw, just boots directly into stock. I used tegraexplorer payload to format and partition the sd card for emuMMC.

I used the sd card setup suggested from the ultimate noob switch homebrew guide which Links the sdsetup site. Where I selected the default kosmos package. I added tinfoil, and sig patches (found on done forum posts here for firmware 10.0.0).

Help on how I might resolve the issue would be great

since you said you're using Hakate and downloaded tinfoil the problem might be you still have the "ams_mitm.kip" file in sd card->atmosphere->kips folder. if you do also remove the line "kip1=atmosphere/kips/ams_mitm.kip" from your bootloader file. for me I had originally kept them on the sd cards in hopes that they'd still work on on latest atmosphere for use with tinfoil but removing them stopped giving me the panic occurred crash and let me boot normally after I updated.

 

[kyrusdemnati]

i am having same issue whats the fix?

 

[jpmasterflex]

i am having same issue whats the fix?

Did you try deleting the atmosphere folder then replacing it with the one from the latest release? i had this issue too and thats what i did...i think it had something to do with the amount of sys modules running or something

 

[CharredPotato]

Hi all. I made the mistake of updating from 9.2 to 10.0.2 on my emuMMC using ChoiDujourNX BEFORE updating Atmosphere and Hekate. I used this guide: *removed because I'm a noob and can't post links*

I updated Atmosphere and Hekate manually on the SD card. In Hekate, I tried to boot to emuMMC, and I land on a black screen with the following error:

Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)
Report saved to ////xxxxxx.bin​

I have no problem starting my setup from scratch if I need to, or if that's easiest. The only thing I would like to have back is an Animal Crossing save file. I tried backing up using Goldleaf, but it wouldn't show more than 16 titles on the screen, and I couldn't scroll, so I gave up thinking "I'm sure it'll be fine". So the save file is in it's native form in the emuMMC.

The micro SD card is 200gb, and is therefore formatted as exFAT. I know I selected exFAT when updating my firmware.

Should I run these scripts from my Mac?:

I can confirm that running sudo chflags -R arch on all directories aside from the official Nintendo directory has solved the issue.
​

Thanks in advance. Any help appreciated.

 

[Athan17]

Hello,

I ran into this error few days ago, however, this is due to me tinkering on Tinfoil (dunno what happened)
Then suddenly, my firmware 10.0.1 has been updated to 10.0.2. this was duriing the Nintendo server is having an error.

my switch before the error occured\:
FW 10.0.1
248GB exFat formatted
vanilla Atmosphere 0.12.0 (im using sysnand CFW, since my switch is banned anyway)

after the sudden update, switch got updated to 10.0.2, then this error occured.

A fatal error occurred when running Atmosphere.
Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)


then i searched the entire gbatemp forums, closed issues on github, same error with reddit users, etc.
i did what they mentioned,
the MacOS sudo chflags -R arch on all
Run archive bit fixer in hekate (yes i downloaded hekate just for this)
Formatted my SD card, Initialized my Switch (yes, goodbye save file)

The issue still persist. only then i fixed my switch after doing the ff:
1.) find a non exFAT SD card
2.) setup Atmosphere on that SD card (thankfully i have spare 4GB microSD, its enough)
3.) download the update for Firmware 10.0.1 and 10.0.2 and ChoiDujourNX
4.) put it on switch, open using atmosphere (it's better if you set the auto RCM)
- yes, the error will be gone once you inserted a non exFAT SD card, and it will boot normally into atmosphere (in my case)
5.) open ChoiDujourNX, downgrade to 10.0.1 exFAT (or non exFAT, your choice)
6.) after reboot, open again ChoiDujourNX (be careful here not to boot into stock sysnand)
7.) install 10.0.2 exFAT
8.) switch back to your old SD card (exFAT formatted)

After that, the error will be gone.
The reason on my error is that, the ninja update from Nintendo on my switch to latest firmware was a firmware without exFat support, i believe this is not a problem for normal switch users, but it is a huge problem for banned switch like myself (it will always ask for an update, but will say you cannot access it due to being banned)

the biggest question on my part is, how come i was able to update my switch if i'm banned? i think it's possible for Nintendo to update your switch even if you're banned, and i'm adding back the 90dns just to be sure i wont get this problem again.

Hope this helps someone with this infamous error.

 

[Tarsul]

(Solution below)

Hey guys just wanted to tell you that I had the same error (corruption number: 010041544D530000).

Switch v 3.0.0 and I tried hacking my Switch for the first time after the NH Switch Guide (followed it as good as possible). Windows. Got the error from this thread at the end.

What helped was this:
"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:
Get your switch in RCM mode.
Inject Hekate payload
Tap on "Tools" on top of the hekate screen.
Tap on "Archive Bit - AutoRCM" on the right bottom.
Tap on "Unset archive bit" button. This might take a while, be patient." [he means Fix archive bit - at least in my hekate version]
thanks goes to Manuel Flores from github [sorry, i would link but I'm not allowed but it's easy to google.] !! Thank you!!

 

[EmanueleBGN]

I solved it right now switching from an exFAT microSD card to a FAT32 microSD card.
With the FAT32 microSD card, the Switch booted immediatly.
Then, I've downgraded my Switch to 10.0.1 firmware and then re-updated it to 10.0.2.
Maybe I could not have to downgrade (the error appeared while I was updating ACNH linking my Switch to another one: when I booted again, the Switch still showing the window of the update even if it was powered off), but I did.

 

[Slim45]

panic occured while running atmosphere, title ID: 010041544D530000 PLEASE LATEST FW 9.1.0

PLEASE HELP!!!
I have tried everything cant get my switch pass the cfw boot

KEEP CALM AND DONT PANIC

 

[orangpelupa]

i cant even open the album/homebrew menu. error 010041544d530000. There's no "archive" bit set on any files on sd card (according to hekate tools).

Googling around, tons of people got this issue and the solution was to unset "Archive" bit.

Downgraded to atmosphere 10.5 and it works fine again. But i can't use any layeredFS. I upgraded because maybe in latest atmosphere layeredfs works again

 

[altorn]

I got a couple of these issues with 2 sdsetup configurations of KOSMOS from their "last official" release.
My Switch emuMMC and SysNAND were on 9.1.0 and I wanted to update to 10.0.1.
first, i downloaded the packages from SDSetup with customized configuration (i am lazy to configure clean atmosphere so i'm using KOSMOS).
i downloaded the firmware 10.0.1 for ChoiNX.
i directly copied over the "sd" contents into my SD card (exFAT 256gb).
i haven't updated the firmware yet but I tried running a couple of games. They worked fine. Then I tried to get to HBMenu but I get the panic error 0x0FFE.
i downloaded packages from SDSetup with "Recommended Defaults" + sigpatches + retroarch and tried to replace just the atmosphere folder.
This time i can't even boot to horizon without getting the panic error which was now 0x0101.

This is how i fixed it.
I deleted most items in my sd card EXCEPT:
- keys.dat
- prod.keys
- emuMMC folder
- switch folder (contains the same nro's, configs, files, etc)
- Nintendo folder

I copied over all the "sd" contents from SDSetup files into my SD card.
And it worked. I have updated my emuMMC to 10.0.1 and I am also able to install latest nsps/xcis using Awoo Installer and GoldLeaf (Switch), and NS-USBLoader (PC side)

 

[ParadoxCataclysm0]

Hello,

I ran into this error few days ago, however, this is due to me tinkering on Tinfoil (dunno what happened)
Then suddenly, my firmware 10.0.1 has been updated to 10.0.2. this was duriing the Nintendo server is having an error.

my switch before the error occured\:
FW 10.0.1
248GB exFat formatted
vanilla Atmosphere 0.12.0 (im using sysnand CFW, since my switch is banned anyway)

after the sudden update, switch got updated to 10.0.2, then this error occured.

A fatal error occurred when running Atmosphere.
Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)


then i searched the entire gbatemp forums, closed issues on github, same error with reddit users, etc.
i did what they mentioned,
the MacOS sudo chflags -R arch on all
Run archive bit fixer in hekate (yes i downloaded hekate just for this)
Formatted my SD card, Initialized my Switch (yes, goodbye save file)

The issue still persist. only then i fixed my switch after doing the ff:
1.) find a non exFAT SD card
2.) setup Atmosphere on that SD card (thankfully i have spare 4GB microSD, its enough)
3.) download the update for Firmware 10.0.1 and 10.0.2 and ChoiDujourNX
4.) put it on switch, open using atmosphere (it's better if you set the auto RCM)
- yes, the error will be gone once you inserted a non exFAT SD card, and it will boot normally into atmosphere (in my case)
5.) open ChoiDujourNX, downgrade to 10.0.1 exFAT (or non exFAT, your choice)
6.) after reboot, open again ChoiDujourNX (be careful here not to boot into stock sysnand)
7.) install 10.0.2 exFAT
8.) switch back to your old SD card (exFAT formatted)

After that, the error will be gone.
The reason on my error is that, the ninja update from Nintendo on my switch to latest firmware was a firmware without exFat support, i believe this is not a problem for normal switch users, but it is a huge problem for banned switch like myself (it will always ask for an update, but will say you cannot access it due to being banned)

the biggest question on my part is, how come i was able to update my switch if i'm banned? i think it's possible for Nintendo to update your switch even if you're banned, and i'm adding back the 90dns just to be sure i wont get this problem again.

Hope this helps someone with this infamous error.

WOOOOOOOOWWWWWWWWWWWWWW THANKS A LOT. Easy fix for anyone stuck in this error that seems to strike continuously.
In short, what worked for me was:
- Get another non exFAT SD Card
- Put latest Atmosphere in there, (it should let you boot without the error.)
- Download 10.0.0 or previous stable firmware you were in
- Downgrade with Choi
- Turn of instead of rebooting.
- Swap SD Cards, use the one you were using.
- Done.

 

[derteufel]

Have been using atmosphere for months now without issue. Loaded up my switch today for the first time in days and the screen remained black after the atmosphere splash screens. Found a "solution" for that problem which involved formatting my microsd to fat32. So I tried it.

Now I'm getting this error:

panic occurred while running atmosphere
title ID: 010041544D530000
error desc: std: :abort () (0xffe)

Things I've tried:
- formatting back to exfat (didn't work, getting the same error still)
- going back to fat32 didn't work either
- read somewhere that deleting that specific titleid had fixed the problem for them, but no such file or folder even exists in my sd card (???)
- all of my files are up to date but just to make sure i went ahead and re-downloaded everything


I'm going to try with a different microsd card all together to see if maybe that's the issue. Right now I'm using a 120GB Nintendo microSD which means I had to go through a third party program in order to format it to fat32. And after powering up my switch regularly (without homebrew) it wasn't able to read the microSD in fat32 format. It reads it just fine when it's formatted to exfat, but if fat32 is the solution and my switch can't properly read it then maybe I just need a different card all together.

Going to Walmart in a bit so I figured I might as well pick up a new one while I'm at it. Hopefully that will be the solution. If not I don't know what else to do. Don't have too much hope for this since I've been using the same card for months without issues, but it's the only other thing I can think of to do at this point.

Will update in a couple of hours I guess.

 

[scandal_uk]

Right now I'm using a 120GB Nintendo microSD which means I had to go through a third party program in order to format it to fat32.

You can format the SD card using Hekate - don’t over-complicate it! Follow these steps to get your emuMMC setup and the remainder as FAT32. (e.g. if you have a fully allocated exFAT partition to begin with)

- Download latest Hekate
- Extract "bootloader" folder to SD card
- Inject Hekate bin payload

Create emuMMC partition:
- In Hekate, select "Tools"
- Select "Archive bit * AutoRCM * Touch Tuning"
- Select "Partition SD Card"
- Drag slider for "emuMMC (RAW)" so it's 29GB then "Next Step"
- Select "Start", wait then tap OK and close

Create emuMMC:
- In Hekate, tap "emuMMC"
- Select "Create emuMMC"
- Select "SD Partition"
- Select "Part 1", wait then select "Close" when done
- emuMMC info should show enabled, if not change emuMMC to SD RAW1

 

[derteufel]

You can format the SD card using Hekate - don’t over-complicate it! Follow these steps to get your emuMMC setup and the remainder as FAT32. (e.g. if you have a fully allocated exFAT partition to begin with)

- Download latest Hekate
- Extract "bootloader" folder to SD card
- Inject Hekate bin payload

Create emuMMC partition:
- In Hekate, select "Tools"
- Select "Archive bit * AutoRCM * Touch Tuning"
- Select "Partition SD Card"
- Drag slider for "emuMMC (RAW)" so it's 29GB then "Next Step"
- Select "Start", wait then tap OK and close

Create emuMMC:
- In Hekate, tap "emuMMC"
- Select "Create emuMMC"
- Select "SD Partition"
- Select "Part 1", wait then select "Close" when done
- emuMMC info should show enabled, if not change emuMMC to SD RAW1

I wish I had posted here sooner instead of trying out random stuff for hours. This fixed the problem for me. Thank you so much!

 

[HOOKSHOT]

DUDE IT WORKS, THANK YOU SO MUCH!

try to delete folder 010041544D530000 inside Atmosphere/contents folder on your sd

 

[mattxx3120]

Fixed this by using the "Fix Archive Bit" on hekate (tools -> Arch bit * RCM -> Fix Archive Bit). Seems it's a sd card issue.