search

Atmosphere-NX / Atmosphere

Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.
GNU General Public License v2.0
14.42k stars 1.22k forks source link

Fatal error title ID 0100000000000001 when opening hbmenu on 0.14.4 #1166

Closed slickrasta closed 4 years ago

slickrasta commented 4 years ago

Bug Report

What's the issue you encountered?

I keep getting the fatal error on title ID 0100000000000001 everytime I launch hbmenu (select Album) on the newest Atmosphere version (0.14.4). Currently on FW 9.0 and Atmosphere 0.9.4 and works fine with payload Hekate 5.0.2 including hbmenu with no issues. All I'm trying to do is update to FW 10.2.0 via Daybreak so I can play my physical copy of All-Stars.

I've tried deleting atmosphere/sept/switch folders and putting fresh files. Even tried with a brand new SD card formatted to FAT32 with only the atmosphere files on it literally nothing else, exact same error every time I try to open hdmenu on new Atmosphere version using the fusee primary payload. Tried Hekate archive bit fix already as well. I am completely baffled how it can even happen on a brand new SD card with no other files whatsoever.

How can the issue be reproduced?

No idea if this is reproducible since I'm not seeing anyone else reporting this specific issue when I Google it / look here.

  1. Format SD card to FAT32
  2. Copy Atmosphere 0.14.4 files onto SD
  3. Boot using fusee-primary.bin payload via TegraRCMGUI
  4. Select Album icon, instantly crashes to this: 1

Crash Report

Bin from current SD (FAT32): report_00000000265510bc (current sd).zip Bin from brand new SD (FAT32): report_00000000179ec795 (brand new sd).zip

System Firmware Version

9.0.0

Environment?

SciresM commented 4 years ago

@slickrasta Please contact me (SciresM#0524) on discord.

I am highly confident this isn't an atmosphere issue, but an issue with your current firmware installation.

SciresM commented 4 years ago

Confirmed issue was partial update, NCM kip vs package1 had differing pre/post 9.0.0 which lead atmosphere to use incorrect service command ABI.

Issue was solved by having user do enable_ncm = 1, so that NCM was replaced by atmosphere's (which guaranteed same ABI for loader vs NCM), followed by an update to 10.2.0 using daybreak.

EfLemon commented 2 years ago

@SciresM Podrias ayudarme de igual manera por favor, tengo el mismo problema y no logro resolverlo, intente buscarte en discordia pero no doy con tu perfil, muchas gracias, saludos.

Masamune3210 commented 2 years ago

Try following the same steps, might be the same issue

Masamune3210 commented 2 years ago

If that doesn't work make a new issue and fill out the template