Toggle sidebar

OFW WONT BOOT AFTER UPDATING FIRMWARE FROM 19 TO 21

  • Thread starter Thread starter phoenix0812
  • Start date Start date
  • Views Views 1,143
  • Replies Replies 10
phoenix0812

phoenix0812

New Member
Newbie
Level 1
Joined
Apr 1, 2026
Messages
3
Reaction score
0
Trophies
0
Age
22
XP
8
Country
Philippines
Hi, I updated my firmware from 19 to 21 then tried to boot to the ofw, but it wont work, only a black screen, and I can reboot to hekate by charging. But the sysmmc and emummc are working fine.
My nintendo switch is an OLED, with a modchip installed (idk what modchip was used)
 
Sort by date Sort by votes
Maybe check your fuse count in Hekate and see if that matches FW21.
In that case the OFW won't boot because of an incorrect fuse count.
sysMMC and the emuMMC are the custom firmwares and they don't care about the fuse count afaik.
 
Upvote 0 Downvote
phoenix0812 said:
It does not match, how can these be fixed?
Click to expand...

If you are on 21.x.x then your expected fuse count is 22, as for ofw boot you can check if your secure boot key and device key are shown, if it says locked out it, it mean you won't be able to ofw boot without a custom bootloader like hekate.
 
Upvote 0 Downvote
Hayato213 said:
If you are on 21.x.x then your expected fuse count is 22, as for ofw boot you can check if your secure boot key and device key are shown, if it says locked out it, it mean you won't be able to ofw boot without a custom bootloader like hekate.
Click to expand...
It is locked out, and i am using hekate
 
Upvote 0 Downvote
Well, I think you must disable autorcm on hekate, then reboot... you will not be able to use atmosphere (yet)
Post automatically merged:

Well, I think you must disable autorcm on hekate, then reboot... you will not be able to use atmosphere (yet) or homebrew
 
Upvote 0 Downvote
razovya said:
How hekate ini file should look like?
Since now we are recommended to just use sys patch no sigpatches
Click to expand...

You can use something like this

[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=1
updater2p=1

[100% STOCK OFW]
ofw=1
icon=bootloader/res/ofw.bmp

[SEMI-STOCK (SYSMMC)]
pkg3=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp



[CFW (SYSMMC)]
pkg3=atmosphere/package3
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp



[CFW (EMUMMC)]
pkg3=atmosphere/package3
emummcforce=1
icon=bootloader/res/emummc.bmp
 
  • Like
Reactions: razovya
Upvote 0 Downvote
Use Downgrade fixer on SysMMC as a payload using Hekate payloads.

It will fix the boot issue.

I'd suggest to never update SysMMC using Hekate+Daybreak and only update EmuMMC as they are completely separated.

Updating SysMMC through Daybreak tends to "miss-align" the fuse count, causing the no boot issue on OFW.
 
Upvote 0 Downvote
phoenix0812 said:
Hi, I updated my firmware from 19 to 21 then tried to boot to the ofw, but it wont work, only a black screen, and I can reboot to hekate by charging. But the sysmmc and emummc are working fine.
My nintendo switch is an OLED, with a modchip installed (idk what modchip was used)
Click to expand...
Try updatting sysmmmc or semistock fw to match the same version as ofw
 
Upvote 0 Downvote

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Is it fixable

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Hacking Emulation  Switch Prod Keys downloading from sites okay?