Switch not booting into OFW

[bruhjohn]

Hi, my current setup is a v2 switch with a HFWFLY modchip installed and till today i had system version 18.1.0. I decided to update it so I used sthetix's HATS pack update video on youtube step by step. I first pasted and replaced the new hats pack contents on my sd card and then i used daybreak to update the Sysmmc cfw as well as Emummc cfw. Now when I reboot to OFW from hekate menu, i'm stuck in a black screen and i need to long press power button to get back in hekate. What should I do? I didn't update from the OFW on wi fi, but I don't think that this is the problem. pls help

 

[SadeyJade]

I’m having the exact same problem!! Plz help!

 

[impeeza]

DO NOT USE PREPACKAGED PACKS, INSTALL ALL HOMEBREW BY YOURSELF.

 

[ikynx]

DO NOT USE PREPACKAGED PACKS, INSTALL ALL HOMEBREW BY YOURSELF.

HATS work, stop with the elitist bullshit please.

Post automatically merged: Mar 26, 2025

for you guys having issues booting into OFW, go through my old post (and my comments there) : https://gbatemp.net/threads/18-1-0-ofw-does-not-boot-on-modded-oled.657003/

It's probably the same issue I faced, with an inverted unmatching fuse count.

 

[impeeza]

HATS work, stop with the elitist bullshit please.

But when you have problems, and you will, will be a nightmare to diagnose, INSTALL ALL YOUR HOMEBREW by hand and you always will know what you have and how to diagnose it.

 

[ikynx]

But when you have problems, and you will, will be a nightmare to diagnose, INSTALL ALL YOUR HOMEBREW by hand and you always will know what you have and how to diagnose it.

It is indeed best to take the time to understand and do manually everything. I get it. I went through the hassle myself. But that said, once I set up all the stuff myself, I also took the time to compare all the set up to what HATS packages contain, and it's near identical. Other packages maybe contain crap, but HATS, not the case. Also Sthetix has made probably the best unfucking vids and tutorials out there, and is a treat to chat with on Discord (and he helped me out on several occasions).

Also, not everyone wants / is able to understand every damn detail about how to set up atmosphere/hetake/sigpatches... If a package is trustworthy, it'd be plain stupid to not want to leverage it. Not everybody is a geek, some people want to play.

 

[The_Chaotician]

I’m with @impeeza on this. There is no way to know which of the packages in a HATS pack is causing the problem if any without extensive investigation and/or a help request thread. Both can be avoided with careful addition of each package and incremental testing to determine the cause.

Post automatically merged: Mar 26, 2025

It is indeed best to take the time to understand and do manually everything. I get it. I went through the hassle myself. But that said, once I set up all the stuff myself, I also took the time to compare all the set up to what HATS packages contain, and it's near identical. Other packages maybe contain crap, but HATS, not the case. Also Sthetix has made probably the best unfucking vids and tutorials out there, and is a treat to chat with on Discord (and he helped me out on several occasions).

Also, not everyone wants / is able to understand every damn detail about how to set up atmosphere/hetake/sigpatches... If a package is trustworthy, it'd be plain stupid to not want to leverage it. Not everybody is a geek, some people want to play.

Great if you have the time to cross check. Shit out of luck if you don’t. I don’t own a v2 so can’t comment on videos published by Sthetix.

Don’t think the latter comment was necessary. This type of thread comes in at 10 a penny and @impeeza is one of the few that usually always comments to help with a solution. It’s not about being a geek or elitist, but sharing years of experience thats known to work.

 

[SadeyJade]

HATS work, stop with the elitist bullshit please.

Post automatically merged: Mar 26, 2025

for you guys having issues booting into OFW, go through my old post (and my comments there) : https://gbatemp.net/threads/18-1-0-ofw-does-not-boot-on-modded-oled.657003/

It's probably the same issue I faced, with an inverted unmatching fuse count.

Thanks for your help. I went through your post & it turned that i had fuse mismatch. I had 19 fuse counts while i should have had 20 fuse counts. I installed 18.1.0 through Daybreak on my SysNAND to match the fuse count, then updated from the OFW to 19.0.1. Btw, i originally used the HATS pack & it was great with no issues. The problem was from the guy who installed my Chip, as he installed CFW 19.0.0 without updating the OFW. He left it on 18.1.0 & updated the emuNAND & sysNAND to 19.0.0, thus creating the mismatch. Now i’m able to play online on OFW & offline on emuNAND.

 

[ikynx]

I'd like to add that (inverted) fuse mismatch detection with a big fat warning of symptoms that might occur (and possible resolution paths or even assistance) would be a valuable addition to Hetake. Even doing everything manually (i.e without relying on a pack such as HATS), unless one has taken the time to get a pretty deep understanding of how the switch firmware updates work and this weird business of CPU fuses, which is far from being straightforward, the usual reaction is "wtf fuses are getting burnt in my device wtf wtf wtf", and ends up spawning more confusion and worried questions than anything else.

Post automatically merged: Mar 27, 2025

Thanks for your help. I went through your post & it turned that i had fuse mismatch. I had 19 fuse counts while i should have had 20 fuse counts. I installed 18.1.0 through Daybreak on my SysNAND to match the fuse count, then updated from the OFW to 19.0.1. Btw, i originally used the HATS pack & it was great with no issues. The problem was from the guy who installed my Chip, as he installed CFW 19.0.0 without updating the OFW. He left it on 18.1.0 & updated the emuNAND & sysNAND to 19.0.0, thus creating the mismatch. Now i’m able to play online on OFW & offline on emuNAND.

yeah, and the guy who installed your chip is probably not to be blamed either. It's a case of bad luck since not all FW updates (from what I remember, only major updates) change fuse count. I had the issue because I am pretty risk averse and cautiously NEVER used the OFW or SysNAND, only EmuNAND. Anyway, I've really glad my old issue was of help! Enjoy gaming