Hacking Question Atmosphere fatal error on boot with EmuMMC

  • Thread starter Thread starter pman152
  • Start date Start date
  • Views Views 8,093
  • Replies Replies 3

pman152

Well-Known Member
Member
Joined
Dec 29, 2015
Messages
2,262
Reaction score
1,448
Trophies
2
XP
5,148
Country
United States
The latest version of Atmosphere results in a black screen after it displays the "Atmosphere" text splash screen that occurs after the sept splash screen.
Atmosphere v11.1 results in a black screen after a black and white mono-logo splash screen (so it gets further than the latest version by a small amount).
Both Atmosphere v10.5 and v10.4 result in a fatal error after all the splash screens:
A fatal error occurred when running Atmosphere.
Title ID: 010000000000002b
Error Desc: std::abort() called (0xffe)
Report saved to /atmosphere/fatal_errors/report_0000000008bd6463.bin

Press POWER to reboot
Atmosphere v10.3 results in a boot loop, it shows all splash screens and boot loops after the black and white mono-logo splash screen.
Atmosphere v10.2 and v10.1 are odd, all of the splash screens finish in mere milliseconds and results in a black screen. When I press power button, it instantly starts sept up again.

I attached the report file in case it helps.

P.S.:
I only ever use EmuMMC. My SysNAND isn't even past installation setup screen yet, it still doesn't even know what language I want.
I last used Atmosphere v10.3, and haven't used my switch in months.

How im booting is, running the lastest version of Hekate, and then Payloads -> fusee-primary.bin
 

Attachments

Last edited by pman152,
Fix!
upload_2020-4-30_22-10-17.png


Thank EmmoEmmo for the fix xd I should of tried that earlier.
 

Site & Scene News

Popular threads in this forum