Yellow Screening on Recent Switch Downloads (Hekate, Sigpatch, Firmware & Sys-Patch)

KlayTheCow

New Member
OP
Newbie
Joined
Oct 16, 2024
Messages
2
Trophies
0
Age
18
XP
7
Country
Canada
Hi, I'm still relatively new to switch modding, starting back in early August and getting jumpstarted on downloading everything I need to know. I've tried following a youtube video about downloading firmware updates for the switch to 19.0.0, getting the recent sigpatches, and downloading the recent hekate patch along with the sys-patch that a person in a forum (there was a link that led to the sys patch link) strongly advised to do before restarting. I did all the installations in Hekate through USB Tools, and after refreshing hekate to load into Atmosphere CFW, I immediately get a yellow screen. I am a little lost in this process and I am asking anyone what the issue is with my switch. At this point, I don't know if I should reinstall the updates, go back a version, or do a fresh install - which I feel nervous about doing because I feel like I might lose important stuff and the other important things that helped jumpstart my switch being modded, such as patching out the serial number and IP from Nintendo servers, etc. b/c I may have forgotten how to do them.

Please don't be too harsh on me, again I'll reiterate, I'm still new to switch modding and may have forgotten a few things since I started out with my modded switch a few months ago. If there is something I should provide so that you can get a better insight into the problem or questions to ask about how the problem happened, please let me know! I feel lost and confused in this matter and hopefully I didn't mess anything up too badly. Thanks in advance!! :)

Edit: I tried reinstalling with atmosphere and stuff to the root of SD card, and somehow, my Atmosphere CFW just disappeared from Hekate. This is really frustrating and annoying.
 
Last edited by KlayTheCow,

Maq47

Lord of Pyro
Member
Joined
Jan 7, 2012
Messages
1,380
Trophies
1
Location
Your basement
Website
idont.have.one
XP
3,643
Country
United States
patching out the serial number
I'm fairly certain that firmware 17.0.0 broke that functionality, and as a result, you cannot blank your serial number anymore, or you'll get a crash when attempting to use wifi at all, even with blocking Nintendo servers via 90DNS. You can use the AMS hosts method to loopback all web addresses to 127.0.0.1, which will fix it, but that still locks you out from even using FTP. The only fix is to have your original NAND backup on hand and follow these steps: https://gbatemp.net/threads/how-to-...prodinfo-on-firmware-17.643492/#post-10297361

Regarding your issue, yellow screen means that Hekate could not find the boot files for Atmosphere on your microSD card, so booting AMS failed. Please make sure you have properly extracted the /atmosphere/ folder and its contents from the AMS prerelease onto your microSD card and try again.
 

KlayTheCow

New Member
OP
Newbie
Joined
Oct 16, 2024
Messages
2
Trophies
0
Age
18
XP
7
Country
Canada
Regarding your issue, yellow screen means that Hekate could not find the boot files for Atmosphere on your microSD card, so booting AMS failed. Please make sure you have properly extracted the /atmosphere/ folder and its contents from the AMS prerelease onto your microSD card and try again.
Hi, thanks for the note. However, I have tried downloading atmosphere files and the same stuff I downloaded for the update on the root of my SD card, yet still the yellow screen problem persists. I am unsure if I am doing something wrong here and might be overcomplicating things, but I have followed through with your steps here. I don't think I quite understand the boot files missing even though everything should be provided with the files from Hekate and Atmosphere, so may you please clarify if there is something I am missing?

Edit: I kept on trying to install atmosphere and other recent things, and now Atmosphere CFW just straight up disappeared from the Hekate launcher. I have an assumption that its more of a firmware problem and that I have to wait until the next atmosphere update because I assume that jumping straight into the next firmware without a atmosphere update causes this problem. Hopefully someone can confirm this?
 
Last edited by KlayTheCow,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Veho @ Veho: Mmmm, stroke my ego.