No OFW, and semi-stock gives black screen

[J0T]

I bought recently modded OLED. EMUMMC (CFW) works great on 20.1.5 but I can't launch sysmmc SYSMMC (semi-stock) and can't see OFW. Seller told me that he upgraded to 21 and it needs to be fixed but after 3 days of reading I still don't know where to start. Removing SD card and replacing data using HATS (plus firmware update to 21 using daybreak) will be enough? Or I can make the situation worse? Are there any benefit of using official software except playing online and buying legal games?

 

[BigOnYa]

You can stay on 20.1.5, no games require 21 yet, or can't be patched to work on 20. And yes, only benefits of OFW is online play, legal bought games, and media apps like youtube.

 

[Hayato213]

If OFW was on 21.x.x then the expected fuse should be 22 instead of 21,

 

[dragonz]

Are there any benefit of using official software except playing online and buying legal games?

AFIK that's it. Have you tried hekate->reboot->OFW?

 

[J0T]

If OFW was on 21.x.x then the expected fuse should be 22 instead of 21,

This is what I got from seller. Hard to check as OFW doesn't work.

Post automatically merged: Dec 15, 2025

AFIK that's it. Have you tried hekate->reboot->OFW?

Yes, black screen

Post automatically merged: Dec 15, 2025

If OFW was on 21.x.x then the expected fuse should be 22 instead of 21,

Thank you for the answers. Seems there is no point to mess with HATS if I play offline only

 

[Hayato213]

This is what I got from seller. Hard to check as OFW doesn't work.

Post automatically merged: Dec 15, 2025

Yes, black screen

Post automatically merged: Dec 15, 2025

Thank you for the answers. Seems there is no point to mess with HATS if I play offline only

Well it kinda suck if the OFW doesn't boot, the thing is the fusee coun't get burn when sysnand boot successfully, regardless if it OFW or CFW, since it can't boot that is a problem, the seller didn't have a NAND backup to restore to I assume.

 

[J0T]

Well it kinda suck if the OFW doesn't boot, the thing is the fusee coun't get burn when sysnand boot successfully, regardless if it OFW or CFW, since it can't boot that is a problem, the seller didn't have a NAND backup to restore to I assume.

Nope, he doesn't but as I wrote above CFW works well. If I ever decide to upgrade what is the way in my case?

 

[Hayato213]

Nope, he doesn't but as I wrote above CFW works well. If I ever decide to upgrade what is the way in my case?

Well in your case your sysmmc doesn't boot, if you try semi stock, sysnand CFW, and hekate-> reboot -> OFW

I mean if you can't really get it to boot you can try to backup the emummc NAND and restore onto the Sysmmc. But that you won't be able to go online as you will just banned, who know if the original selller had a clean NAND or not. Do you know what modchip it is using?

 

[J0T]

Well in your case your sysmmc doesn't boot, if you try semi stock, sysnand CFW, and hekate-> reboot -> OFW

I mean if you can't really get it to boot you can try to backup the emummc NAND and restore onto the Sysmmc. But that you won't be able to go online as you will just banned, who know if the original selller had a clean NAND or not. Do you know what modchip it is using?

Picofly

 

[Hayato213]

Picofly

RP2040 picofly does have a history of corrupting NAND, if it was the hwfly style chip, that might explain why the OFW doesn't boot, probably a corrupted NAND.

I guess before trying the method below, you can try maintenance mode first,

Nintendo Switch Maintenance Mode (or Recovery Mode) helps fix issues by offering options to update the system, initialize without losing save data, or factory reset, accessed by holding Volume Up/Down and Power after a full shutdown. To enter, power off the Switch, then hold both Volume buttons ( + and - ) and press the Power button until the menu appears, allowing you to perform system fixes.

How to Enter Maintenance Mode

1. Power Off: Hold the Power button for a few seconds, select "Power Options," then "Turn Off". (If unresponsive, hold Power for 12 seconds to force shutdown).
2. Press Buttons: Press and hold the Volume Up (+) and Volume Down (-) buttons together.
3. Turn On: While holding the volume buttons, press the Power button.
4. Wait: Keep holding the volume buttons until the "Maintenance Mode" screen appears, then release them.

Alternative

Anyway I suggest you backup the SD Emummc Raw Partition, toggle that on then back up the NAND, and then try to see to restore it on to Sysmmc see if it will boot or not, I mean if it boot atleast you will have a working Sysmmc even though you can't go online.

 

[Drakull]

It could be that the installer updated your fw to 21 using daybreak (so the fuses count as they say is not matching.
If you update your sd card with the latest version of HATS (that by default also shows the sys-cfw boot mode), you could start on sys-cfw (that's the original nand with custom firmware), check what firmware is installed (if it really is 21 or if it's 20.x) and try to get it back to 20.5.0 (for example). Keep in mind you might have to use some tools to boot since there were changes between 20 and 21 that made things hard to go back. Then you could use an official update to get the OFW (after restarting) to 21 so the fuses count matches.
But if you don't really care that much about ofw and can wait... wait until a new update is released from Nintendo, boot in SYS-CFW and then do an official update to the latest firmware. (that should also fix the fuses in theory).

 

[J0T]

It could be that the installer updated your fw to 21 using daybreak (so the fuses count as they say is not matching.
If you update your sd card with the latest version of HATS (that by default also shows the sys-cfw boot mode), you could start on sys-cfw (that's the original nand with custom firmware), check what firmware is installed (if it really is 21 or if it's 20.x) and try to get it back to 20.5.0 (for example). Keep in mind you might have to use some tools to boot since there were changes between 20 and 21 that made things hard to go back. Then you could use an official update to get the OFW (after restarting) to 21 so the fuses count matches.
But if you don't really care that much about ofw and can wait... wait until a new update is released from Nintendo, boot in SYS-CFW and then do an official update to the latest firmware. (that should also fix the fuses in theory).

How to check which firmware is installed?

 

[Drakull]

How to check which firmware is installed?

If you can boot with sys-cfw (custom firmware with nand ) you can go to the console settings and check what version is installed.

 

[Hayato213]

If you can boot with sys-cfw (custom firmware with nand ) you can go to the console settings and check what version is installed.

He probably can't to be honest.

 

[Earthshine]

It is because I believe you updated ofw using daybreak and didn't boot back to ofw after. But it also looks like your hekate_ipl.ini file is messed up. If you copy/pasted latest HATS pack to your sd card, there should be more than two entries on your boot list when in Hekate.

 

[J0T]

He probably can't to be honest.

That's right. I can't

 

[Drakull]

He probably can't to be honest.

That's why I said "if he can".
If he has access to emu-cfw but not just to OFW, it's always just trying SYS-CFW (not semi-stock, but system nand custom firmware).

That's right. I can't

What error do you get trying to start on SYS-CFW ?

 

[J0T]

It is because I believe you updated ofw using daybreak and didn't boot back to ofw after. But it also looks like your hekate_ipl.ini file is messed up. If you copy/pasted latest HATS pack to your sd card, there should be more than two entries on your boot list when in Hekate.

The risk (should be) I am afraid to break what I have now, so working CFW. I do not know details of installation of previous owner. I suppose based on sale description that it was updated on OFW and then OFW stopped working but didn't find similar case and that's why I'm asking. It's it worth to risk to be compliant between OFW and CFW? What is the risk if I try e.g. Hekate replacement? Nintendo is new for me but it will stay longer with me.

 

[Drakull]

The risk (should be) I am afraid to break what I have now, so working CFW. I do not know details of installation of previous owner. I suppose based on sale description that it was updated on OFW and then OFW stopped working but didn't find similar case and that's why I'm asking. It's it worth to risk to be compliant between OFW and CFW? What is the risk if I try e.g. Hekate replacement? Nintendo is new for me but it will stay longer with me.

You usually can upgrade the SD card contents without a problem (just don't touch your emmc). It will provide support if you later decide to upgrade the firmware, but not force you to do so.
An easy way is:
Take a backup of your sd (so you can restore it back if you want to), and update the installed package (HATS or whatever you have) with the latest version. It would correct fixes, you can update the apps to latest versions for latest features/bug fixes and so... then try again. It shouldn't break anything (if you do it correctly).
And worse case scenario... restore the backup of the sd.
(or copy your sd card to another one and use that 2nd card to update amosphere/hekate and so)

 

[Earthshine]

The risk (should be) I am afraid to break what I have now, so working CFW. I do not know details of installation of previous owner. I suppose based on sale description that it was updated on OFW and then OFW stopped working but didn't find similar case and that's why I'm asking. It's it worth to risk to be compliant between OFW and CFW? What is the risk if I try e.g. Hekate replacement? Nintendo is new for me but it will stay longer with me.

I would get the latest hats pack and copy/paste everything to your sd card again, making sure to overwrite any already existing files. I still think something may be messed up with your hekate ini file because there should be more than two boot options in the first image you posted.