search

Atmosphere-NX / Atmosphere

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

Could not boot when chainloaded with Hekate 5.3.0 #1041

Closed dothackjhe closed 4 years ago

dothackjhe commented 4 years ago

Bug Report

What's the issue you encountered?

The console goes into "black screen" after the Atmosphere logo when chainloaded with the latest iteration of Hekate (5.3.0).
The issue arose when I upgraded to Atmosphere 0.13.0.
The system boots fine when I reverted back to Atmosphere 0.12.0.

How can the issue be reproduced?

Chainload Atmosphere 0.13.0 with Hekate 5.3.0.

System Firmware Version

10.0.2

Environment?

HookedBehemoth commented 4 years ago

Assuming you mean launch fusee-primary by chainload:

fusee-primary was last updated in: 0.13.0.

Did you update it from where you chainload?

dothackjhe commented 4 years ago

Yes, I did. Within the /bootloader/payloads folder, specifically. @HookedBehemoth

dothackjhe commented 4 years ago

I do not think I was the only one who encountered it, though: https://gbatemp.net/threads/atmosphere-nx-custom-firmware-in-development-by-sciresm.496832/page-277#post-9096844

It's just funny no one made a report about it.

HookedBehemoth commented 4 years ago

Piracy is not supported.

dothackjhe commented 4 years ago

What if I say that I only run homebrews, will you even believe it?

Also, what made you think that I use Hekate for piracy purposes? Does it have something to do with me mentioning Atmosphere?

MichaelRebirth commented 4 years ago

Im having the same problem chainloading it error code was 010notsurehowmany03 after passing the sept logo.

ELY3M commented 4 years ago

just use fuse-primary like me.

xmun2k commented 4 years ago

Having the same problem with fusee-primary. Using a completely clean install even on a new SDCard with fresh eMMC partition created.

Edit: Since this doesn't match the description of the original post, I've opened my own issue. https://github.com/Atmosphere-NX/Atmosphere/issues/1053

KiraPT commented 4 years ago

I had the same issue and after some reading and some work I was able to fix the issue by using the fix from Hekate and rebuilding the hekate_ipl.ini file. Now it boots SysNand, EmuNand and Stock with no issues.

If it is any help, here's my hekate_ipl.ini file:

hekate_ipl.zip

[config] autoboot=2 autoboot_list=0 bootwait=2 backlight=100 autohosoff=0 autonogc=1 updater2p=0

[Atmosphere (SYSNAND)] fss0=atmosphere/fusee-secondary.bin kip1patch=nosigchk emummc_force_disable=1 logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_payload.bmp {}

[Atmosphere (EMUMMC)] payload=atmosphere/fusee-primary.bin kip1patch=nosigchk emummcforce=1 logopath=bootloader/bootlogo_emunand.bmp icon=bootloader/res/icon_payload.bmp {}

[Stock] fss0=atmosphere/fusee-secondary.bin stock=1 emummc_force_disable=1 {}

SciresM commented 4 years ago

This particular issue was solved by ctcaer using a fix I believe, the other one with xmun is maybe different.

dothackjhe commented 4 years ago

I actually had it resolved by deleting all the folders which pertains to the older version of Atmosphere and replacing everything with the ones that come with Atmosphere 0.13.0 as well as the latest sigpatch. As it appears, there are some leftover files from 0.12.0 that was in conflict with 0.13.0 that prevents the system from booting properly.

Either that is the case or the old hekate_ipl.ini in my micro-SD Card caused it, as KiraPT mentioned.