NINTENDO SWITCH HELP-Black screen Missing warmboot.bin / secmon.bin

  • Thread starter Thread starter Killa_kelvv
  • Start date Start date
  • Views Views 16,755
  • Replies Replies 16
Status
Not open for further replies.

Killa_kelvv

Active Member
Newcomer
Joined
Mar 8, 2020
Messages
44
Reaction score
4
Trophies
0
Age
30
XP
184
Country
United States
So this error occured after attempting to inject the fusee payload after updating atmosphere after 13.0 switch update that included the bluetooth compatibility
The following screenshots is what i have in the SD card, i even formatted it after backing up on an external drive,
and afterwards added the updated atmosphere/hekate files & still nothing.
Also included a screenshot of what my system settings ipl looks like.



 
Last edited by VinsCool,
Somethings to look at:
* Did you have EmuNand on a partition? I don't see anything that shows emuMMC. Were you using CFW sysNand?
* If you had emuNand on a partition, and reformatted the card, then copy over the files, that's not going to work - You wiped your emuNand.
* Have you ever booted stock firmware using this SD card? I don't see the Nintendo folder if you did.
* If you upgraded to 13, you need the latest Atmosphere and Hekate. If you uncompress Hekate zip correctly, you should see a file named hekate_ctcaer_5.6.2.bin at the root of the SD card. It's not important that the file has to be there, but instructions says you decompress Hekate zip file to the root of the SD card, and something tells me that you may not have unzip the Atmosphere and Hekate files correctly
* What does the content of the Atmosphere folder look like?
* Have you tried booting into Hekate?

Just try to wipe the SD card clean (hope you had backups - saves and NAND), then start fresh. Get the latest Atmosphere, Hekate, ITotalJustice patches. Then try to boot into Hekate to see if you can get that far.
 
Somethings to look at:
* Did you have EmuNand on a partition? I don't see anything that shows emuMMC. Were you using CFW sysNand?
* If you had emuNand on a partition, and reformatted the card, then copy over the files, that's not going to work - You wiped your emuNand.
* Have you ever booted stock firmware using this SD card? I don't see the Nintendo folder if you did.
* If you upgraded to 13, you need the latest Atmosphere and Hekate. If you uncompress Hekate zip correctly, you should see a file named hekate_ctcaer_5.6.2.bin at the root of the SD card. It's not important that the file has to be there, but instructions says you decompress Hekate zip file to the root of the SD card, and something tells me that you may not have unzip the Atmosphere and Hekate files correctly
* What does the content of the Atmosphere folder look like?
* Have you tried booting into Hekate?

Just try to wipe the SD card clean (hope you had backups - saves and NAND), then start fresh. Get the latest Atmosphere, Hekate, ITotalJustice patches. Then try to boot into Hekate to see if you can get that far.
The guys at the Atmosphere discord solved it , they’re legends , regardless I appreciate you taking the time to look into my thread .
The problem was that atmosphere came out with fusee.bin & i went along and replaced payload.bin in my rcmloader to fusee.bin , it caused that error . I added payload.bin back in
 

Attachments

  • C7186614-A34F-4B80-80A1-1C1200E9D8F3.jpeg
    C7186614-A34F-4B80-80A1-1C1200E9D8F3.jpeg
    1.9 MB · Views: 460
What I was supposed to do was rename the fusee.bin to payload.bin for it to boot straight to atmosphere, it boots to hekate now but regardless i can access the fusee through the payload list . I did in fact format my sd card of course after backing up all my files .
 
  • Like
Reactions: canichegotico
Hello, could you tell me in which folder you have changed the names of fusee.bin to payload.bin? I have the same error as you with the latest update. Thanks
What I was supposed to do was rename the fusee.bin to payload.bin for it to boot straight to atmosphere, it boots to hekate now but regardless i can access the fusee through the payload list . I did in fact format my sd card of course after backing up all my files .
 
having the same problem now, so is th sd card that need to be replace fusee bin to payload bon? or into the rcm loader?
Anybody knows why that happens and how can be avoid it?
 
IMG_8128.jpeg

Ok in which folder exactly i'm
bit lost really , thanks for replying
Post automatically merged:

 
Last edited by Caniche,
View attachment 394799
Ok in which folder exactly i'm
bit lost really , thanks for replying
Post automatically merged:
Try hekate.bin as payload.bin instead of fusee.bin
but where ?please 🙏 i can't use anytjing atm and i have 30hours flight back to Australia 😩
Post automatically merged:

The guys at the Atmosphere discord solved it , they’re legends , regardless I appreciate you taking the time to look into my thread .
The problem was that atmosphere came out with fusee.bin & i went along and replaced payload.bin in my rcmloader to fusee.bin , it caused that error . I added payload.bin back in
Could you explain how to do it please?
i don't know folder exactly or if is injecting a payload with the rcmloder etc 🤷🏻‍♂️, losing the hope.
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum