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

EmuNand fusee.bin with Atmosphère 1.4.0 (pre-release) boot issue #1964

Closed whitezombie2000 closed 2 years ago

whitezombie2000 commented 2 years ago

Bug Report

What's the issue you encountered?

I updated to the latest Atmosphère 1.4.0 (pre-release), fusee.bin, and firmware 15.0.0 via Daybreak, deleted all old Atmosphère files and replaced with the new 1.4.0 (pre-release) files. When using a partition based EmuNand with Atmosphère 1.4.0 (pre-release), FW 15.0.0, using payload=bootloader/payloads/fusee.bin with hekate_ipl.ini, or chaining Hekate and choosing fusee.bin from payload, or loading fusee.bin directly with TegraRCMGui, it fails to boot, shows Atmosphere boot screen, fails to get to switch logo, gets a black screen, and requires a hard shutdown.

How can the issue be reproduced?

Issue can be reproduced by installing FW 15.0.0, clean Atmosphère 1.4.0 1.4.0 (pre-release) files, and Hekate v5.9.0. Injecting fusee.bin directly with TegraRCMGui, or chain booting fusee.bin with Hekate. Using a partition based EmuNandBoot, inject fusee.bin via TegraRCMGui, shows the Atmosphere boot screen, fails to get to the switch logo, gets a black screen, and requires a hard shutdown. Same issue can be reproduced if you use Hekate to chain fusee.bin via Hekate and choosing payload, selecting fusee.bin, or use payload=bootloader/payloads/fusee.bin with hekate_ipl.ini.

The only way I have gotten it boot successfully is by using fss0=atmosphere/package3 in my hekate_ipl.ini file. I downgraded the firmware via Daybreak back to 14.1.2 and everything works fine on 14.1.2 with the 1.4.0 (pre-release) files. I upgraded back to 15.0.0, put in clean files, and the issue persists. No matter what boot method I use with fusee.bin I always get the black screen.

System Firmware Version

15.0.0

Environment?

SciresM commented 2 years ago

I cannot actually reproduce this. My console boots into 15.0.0 sysmmc and emummc fine using fusee.bin, both directly and chained from hekate.

I always suspect this happens due to e.g. not updating fusee correctly or due to exFAT issues.

I know there's no issue fundamentally with fusee, btw -- if the console is getting past the atmosphere logo literally at all it's not a fusee problem.

whitezombie2000 commented 2 years ago

I should also mention I'm using FAT32.

SciresM commented 2 years ago

Yeah. Honestly, if you want to debug on discord, feel free to DM me (SciresM#0524), but I really don't believe these are actual code problems. I'll re-open given compelling evidence that it's actually a problem with fusee, but in the mean-time if you can boot via hekate...boot via hekate?

mrdude2478 commented 2 years ago

I know there's no issue fundamentally with fusee, btw -- if the console is getting past the atmosphere logo literally at all it's not a fusee problem.

It doesn't get past the Atmosphere logo - it shows the Atmosphere boot screen and then goes black before it gets to the logo, and therefore doesn't get to the switch logo either.

whitezombie2000 commented 2 years ago

fusee.bin MD5 Checksum: 96540968BAD561E6B945C191A29F5CBB SHA-1 Checksum: 3F01BC1BC74CF0BDDBF5A1BAC5101BB160504B82

SciresM commented 2 years ago

I will comment again that if you're interested in debugging, you should DM me on discord.

SciresM commented 2 years ago

@whitezombie2000 @mrdude2478 Is the issue fixed using this fusee binary?

fusee.bin.zip

whitezombie2000 commented 2 years ago

I just reinstalled FW 15 and that worked via chain booting. Let me try direct and editing the hekate_ipl.ini file.

whitezombie2000 commented 2 years ago

OK, chain booting that new fusee.bin via Hekate and choosing payload works, calling it from payload=bootloader/payloads/fusee.bin with hekate_ipl.ini works, and injecting it directly with TegraRCMGui works with FW 15.0.0. What did you change?

SciresM commented 2 years ago

I'll commit the change after dinner, and it will make it into 1.4.0 non-prerelease.

The nogc patch for exFAT firmware had an off-by-one...so I guess you were installing exFAT firmware even though you weren't using exFAT?

whitezombie2000 commented 2 years ago

When I installed the firmware via Daybreak I always choose Preserve Settings and Install (FAT32 + exFAT). Also, thank you SciresM!

SciresM commented 2 years ago

Yeah, I tested booting into non-exFAT emummc, tested booting into exFAT emummc, and tested nogc...but I don't actually use exFAT firmware so this escaped testing.

My apologies both for the issue and the insistence that it wasn't a code issue. The clarification that it wasn't getting past the ams logo was very helpful.

Still, do reach out on discord! I am a lot faster there and also provide support for a lot of issues that wouldn't be covered on GitHub.

mrdude2478 commented 2 years ago

Yep, thanks for fixing this. I tried it and it's working fine now.

tbensonwest commented 2 years ago

Thought I was going nuts. Exactly the issue I was facing yesterday. Will try this method later.

Inclsevd commented 2 years ago

I also got hit with this and couldn't figure it out but finally found this issue, everything is working smoothly now. Thanks!

hsuanpai commented 2 years ago

Try this boot loader parameter with hekate_ipl.ini . I had boot success with 15.0.0 of AMS 1.4.0. of EMUMMC.

[CFW (EMUNAND)] emummcforce=1 fss0=atmosphere/package3 kip1patch=nosigchk atmosphere=1 logopath=bootloader/bootlogo.bmp icon=bootloader/res/emunand.bmp id=2

hsuanpai commented 2 years ago

@whitezombie2000 @mrdude2478 Is the issue fixed using this fusee binary?

fusee.bin.zip

Updated this fixed fusee bin is also workable.

Waifu4Life commented 2 years ago

Same issue on both my Switch systems (OG V1 and Switch Lite with modchip). It seems totally random however, sometimes it boots, sometimes I get a black screen.

zemixe commented 2 years ago

Try this boot loader parameter with hekate_ipl.ini . I had boot success with 15.0.0 of AMS 1.4.0. of EMUMMC.

[CFW (EMUNAND)] emummcforce=1 fss0=atmosphere/package3 kip1patch=nosigchk atmosphere=1 logopath=bootloader/bootlogo.bmp icon=bootloader/res/emunand.bmp id=2

Irrelevant and piracy is not supported.

Same issue on both my Switch systems (OG V1 and Switch Lite with modchip). It seems totally random however, sometimes it boots, sometimes I get a black screen.

So download the fixed fusee.bin above and test it. However this issue should not be random, it should be pretty clear cut as to whether you can boot or not.

Waifu4Life commented 2 years ago

So download the fixed fusee.bin above and test it. However this issue should not be random, it should be pretty clear cut as to whether you can boot or not.

Didn't change anything and also, it is random, but most of the time, I do not to restart at least one but forcing a shutdown.

tbensonwest commented 2 years ago

Thought I was going nuts. Exactly the issue I was facing yesterday. Will try this method later.

Worked like a charm. Thanks @SciresM 👍🏻

ghost commented 2 years ago

@whitezombie2000 @mrdude2478 Is the issue fixed using this fusee binary? fusee.bin.zip

Updated this fixed fusee bin is also workable.

this new binary fixed my problem not booting at all into the CFW. I got always the error that there is an error with warmboot...

{-- Custom Firmware --} [NSW emuMMC] payload=bootloader/payloads/fusee.bin kip1patch=nosigchk atmosphere=1 emummcforce=1 logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_atmo.bmp

on not updated cfw yet. (ofw of course)

But still has the error that there is just the screen lighted on with "black". this happens a lot now.. I use system reboot or shutdown and on boot screen just lighted on with nothing.

zemixe commented 2 years ago

@whitezombie2000 @mrdude2478 Is the issue fixed using this fusee binary? fusee.bin.zip

Updated this fixed fusee bin is also workable.

this new binary fixed my problem not booting at all into the CFW. I got always the error that there is an error with warmboot...

{-- Custom Firmware --} [NSW emuMMC] payload=bootloader/payloads/fusee.bin kip1patch=nosigchk atmosphere=1 emummcforce=1 logopath=bootloader/bootlogo.bmp icon=bootloader/res/icon_atmo.bmp

on not updated cfw yet. (ofw of course)

But still has the error that there is just the screen lighted on with "black". this happens a lot now.. I use system reboot or shutdown and on boot screen just lighted on with nothing.

This is impossible to understand I'm afraid, the hekate config you posted is terrible and does nothing when using fusee.bin. Additionally, piracy is not supported.

SciresM commented 2 years ago

Closing this because it's resolved by 05fee5d.