Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Black screen after Nintendo logo when selecting CFW #172

Closed
dogepotion opened this issue Dec 28, 2018 · 30 comments
Closed

Black screen after Nintendo logo when selecting CFW #172

dogepotion opened this issue Dec 28, 2018 · 30 comments
Labels
ghost Something weird is happening that cannot be explained normally

Comments

@dogepotion
Copy link

dogepotion commented Dec 28, 2018

I am unable to boot into Atmosphere via Hekate. If I try to do so, there is text output that appears as if things are loading correctly and the Nintendo logo appears, but I get a black screen indefinitely (I've tried letting it sit for 20+ minutes, no change), right before the Switch logo.

I'm using Kosmos, and I've tried just about everything I and the people who were helping me on the Kosmos Discord could think of including:

  • Quick reformatting SD card (both FAT32 and exFAT)
  • Full reformatting SD card (FAT32)
  • Doing a surface test on SD card (0 read errors found)
  • Trying multiple versions of both Hekate and Kosmos (v4.5, v4.6 // v11.5, v11.7)
  • Trying multiple versions of Atmosphere
  • Updating 6.2.0 (orig. installed with system update prompt) => 6.2.0 (installed with ChoiDujoirNX, exFAT support enabled)
  • Trying with AutoRCM off/on
  • Trying with auto boot off/on
  • Unplugging USB from Switch as soon as Hekate is injected (I am using a computer to inject payloads)

Here's what Hekate says after I select CFW, before the Nintendo logo:

Initializing...

Identified Pkg1 ('20181107XXXXXX')
Keyblob Version 6

Loaded Pkg1 and keyblob
Decrypted and unpacked Pkg1
Patching Warmboot
Loaded warmboot.bin and secmon
Read Pkg2
Parsed ini1
Patching Kernel
Patching Kernel initial processes
Decomping FS KIP1 sect 0 of size 873176...
Applying patch 'nosigchk' on FS KIP1 sect 0
Rebuilt and loaded Pkg2

Booting...

(No idea if the pkg1 number is identifying at all, but I replaced the last 6 digits with X)

Something random (or not) is that the Switch never seems to leave RCM mode when this is happening.

I'm not sure why this is happening, and nobody I've asked has an explanation so I am posting this issue as I think it might be related to Hekate. fusee_primary boots into Atmosphere normally, but I am unable to with Hekate.

@CTCaer
Copy link
Owner

CTCaer commented Dec 28, 2018

What's your config? (boot entry)

@dogepotion
Copy link
Author

dogepotion commented Dec 28, 2018

What's your config? (boot entry)

Not exactly sure what you mean, do you mean hekate_ipl.ini? If so, it's:

[config]
autoboot=0
autoboot_list=0
bootwait=5
customlogo=1
verification=2
backlight=100
autohosoff=0

{AtlasNX/Kosmos v11.7}
{ }
{Discord: https://discord.gg/qbRAuy7}
{ }

{-- Custom Firmwares --}
[CFW]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
kip1=modules/required/fs_mitm.kip
secmon=modules/required/exosphere.bin
kip1patch=nosigchk
atmosphere=1
{ }

{---- Miscellaneous ---}
[Stock]
{ }

@CTCaer
Copy link
Owner

CTCaer commented Dec 29, 2018

Your ini seems legit.
Can you take a photo of Console info -> Sd card?

@dogepotion
Copy link
Author

dogepotion commented Dec 29, 2018

Your ini seems legit.
Can you take a photo of Console info -> Sd card?

Sure, here you go:
20181228_214136

Github rotated it for some reason, if you click it it's right side up

@CTCaer
Copy link
Owner

CTCaer commented Dec 29, 2018

Hmm your sd card seems like a legit sandisk A1. So it shouldn't be a fake card problem.
So it shows the nintendo logo and not the switch logo? Or it shows both?

@dogepotion
Copy link
Author

Hmm your sd card seems like a legit sandisk A1. So it shouldn't be a fake card problem.
So it shows the nintendo logo and not the switch logo? Or it shows both?

Yeah I bought it at Walmart. And it only shows the Nintendo logo, it does not show the Switch logo.

@CTCaer
Copy link
Owner

CTCaer commented Dec 29, 2018

Can you add debugmode=1 in your config and try?

[CFW]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
kip1=modules/required/fs_mitm.kip
secmon=modules/required/exosphere.bin
kip1patch=nosigchk
atmosphere=1
debugmode=1

@dogepotion
Copy link
Author

dogepotion commented Dec 29, 2018

Sure, I'll try that right now

@dogepotion
Copy link
Author

Yeah, same thing, black screen after Nintendo logo, and I left it on until just now. No change.

@CTCaer
Copy link
Owner

CTCaer commented Dec 29, 2018

I'll have some time tomorrow to test some things.
I'll send you a msg when it's possible

@dogepotion
Copy link
Author

Alright, I am probably going to be out after 12:00pm EST until probably 10-11pm, but I should still probably be able to reply to messages and possibly do things with the Switch. I appreciate the help a lot :]

@knox
Copy link

knox commented Jan 10, 2019

I wonder whats the current status of this because i am having exactly the same issue

@dogepotion
Copy link
Author

dogepotion commented Jan 10, 2019

I wonder whats the current status of this because i am having exactly the same issue

wow, nice username

also, it hasn't been resolved, its a very odd issue that nobody else seems (or I guess seemed now) to have until I presented it. CTCaer has been working a lot on trying to figure out what this is and nothing's been determined as a cause yet

with that being said, while a bit redundant to ask, have you tried everything I originally listed that I tried in the OP? and it's a black screen after the Nintendo logo in Hekate? Fusee works fine?

Also, if you're on OSX, setting up the SD card might be a bit weird, as I think it appends information or just creates new files that don't work with Hekate. A lot of people experience a black screen at some point during the boot process if they had been using OSX to copy over files.

@knox
Copy link

knox commented Jan 10, 2019

Well, thanks for your fast reply.

To be honest, it's my very first time trying to boot a CFW at all. So i did not try out all the details you have mentioned before yet. Basically, i've read a ton of tutorials before i carefully backed up my device and then used sdsetup to create a zip which i'm currently trying to boot. After selecting "Custom FW" in hekate 4.6 i get a nintendo logo and then a black screen. Same happens when i manually choose the payload.

Fusee itself (that refers to the base exploit itself, doesn't it?) works fine on my device. At least i have successfully bootet several times into a bunch of different payloads.

Good hint regarding the usage of macOS. Indeed thats my current OS and obviously that's not the best choice for creating a sd for the switch. I'll give Linux a try tomorrow and see how it goes.

Probably a github issue is not a good place to discuss this kind of newbie topics so i'm sorry for disturbing here. On the other hand, if there is anything i can do to help sorting out this problem i'd be glad to help.

@dogepotion
Copy link
Author

There are a lot of good Discords and websites (gbatemp.net is a pretty good place to start) that can help with setting up and booting CFW.

My mistake, I should've been more descriptive- by fusee I meant the fusee-primary payload that comes with Atmosphere. It boots Atmosphere slightly differently than Hekate. Not sure if it will make a difference if it's OSX messing with the files on the SD card, but if you try it and it doesn't work it's probably a good indication that OSX is doing something. There are a bunch of people who can't use OSX to create SDs for the Switch at all, while some can. Not sure what's the difference between those who can't and can.

@knox
Copy link

knox commented Jan 10, 2019

I'm well aware of gbatemp and those other resources, thank you ;-) I came across your issue because the symptomes are matching mine exactly.

Manually selecting fusee_primary payload leads to the same results for me.

I'm a bit astounded what possibly could have gone wrong when i extraced the files using homebrewed 7z directly onto the sdcard but surely you're right with your hints macOS beeing a rather well known source of problems here.

@CTCaer
Copy link
Owner

CTCaer commented Jan 11, 2019

@knox Your sd card is probably exFAT and you are missing the micro update. Reformat it to FAT32 with 32KB cluster and try again.

@knox
Copy link

knox commented Jan 11, 2019

@CTCaer Thank you very much! This solved my issue.

@CTCaer CTCaer added the ghost Something weird is happening that cannot be explained normally label Jan 14, 2019
@Bruce055
Copy link

Hello, I'm having the exact same problem.
Tried everything in the OP and nothing seems to solve it.

The switch shows the nintendo logo, but not the switch logo.

Any idea on what may be causing it, or how can I fix it? downloaded everything (the SD content, the payload, Tegra, etc, from the SDsetup, so I assume everything is from the latest version).

One thing that I'm noticing is that, when i boot the OFW with the SD card on, a message is shown that says I should make an update to use a microSD. But since I'm already on version 6.2.0 I don't want to do it as the new version is not supported yet.

Any help would be greatly appreciated.

@knox
Copy link

knox commented Jan 31, 2019

@Bruce055 see this answer #172 (comment)

Your SD card is in exFAT format. That is why OFW asks you to install the update. There are two solutions: either reformat the SD card with FAT32 or install the update.

@Bruce055
Copy link

Damn, It was that... I misread when CTCaer answered you and though I should format for exFAT with 32Gb Cluster ¬¬

Sorry for the trouble and thank you very much for the help!!

@CalBear91
Copy link

I am having the same issue with the black screen after nintendo logo when booting CFW or OFW.. My sd card is formatted to FAT32. So Im not quite sure what the issue is? Any help much appreciated!

@urherenow
Copy link

First, google “switch sdfiles”, get the latest package, and overwrite everything. If it still doesn’t work, ask on Discord or gbatemp

@MrAttraction
Copy link

MrAttraction commented Feb 17, 2019

I'm having the same issue :/ everything was working normally, now when I inject fusee primary I get stuck at a black screen after Nintendo logo (when it shows up.. sometimes I get stuck after KIP patching screen goes by)

I'm on 6.2 and I have the exfat update, I was playing fine till now

Edit: weird but something happened to the theme I had installed and I had to reinstall it, that's why my screen was black lol.

@akwiz
Copy link

akwiz commented Mar 9, 2019

Hey guys I know this is an old thread but I was having similar issues for a while. Do you have autoRCM enabled and do you have a jig in your switch? I was having the same problems but my switch would not boot with the jig inserted.

@CTCaer
Copy link
Owner

CTCaer commented Mar 10, 2019

OP had a very different problem. One that doesn't make sense.
Even the BIS keys didn't match. I assume that like how the keygen is now, it may work now.

Feel free dogepotion to reopen if hekate 4.8 and up didn't fix that.

@CTCaer CTCaer closed this as completed Mar 10, 2019
@justusiv
Copy link

justusiv commented May 28, 2019

@akwiz did you ever see logos or after hekate menu it would just go black? Mine just goes black currently and will try your comment when i get home.

@justusiv
Copy link

For anyone reading this later.... it appeared to be a corrupt internal nand. After a restore of a previous backup it is boot just fine.

@yratof
Copy link

yratof commented Sep 24, 2019

How did you restore the internalnand @justusiv ? A link to follow for other?

@justusiv
Copy link

@yratof
I had a backup of my nand. However any time i upgraded firmware i had this problem using any bootloader except the paid one :( . I tested the paid bootloader which i wont name, but it just worked so i just started using it. I have not gone back and tested with any newer versions since i posted about my issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ghost Something weird is happening that cannot be explained normally
Projects
None yet
Development

No branches or pull requests

10 participants