Downgrading Question - Bypassing Picofly Will not Boot

[YoNoid]

I have a Switch and a Switch Lite that I’ve installed PicoFly (firmware 2.80) on. Both units are working great so far with no issues. However, I have a few questions about downgrading and booting into the official firmware (OFW) NAND, and would appreciate some clarification. I’m not an expert, so detailed feedback is welcome.

I wanted to try booting directly into the OFW NAND without involving the PicoFly at all. I was told that pressing both volume buttons while powering on would bypass the SD card. However, when I tried this, the screen stayed black every time — no luck after multiple attempts.

I’ve been upgrading both the EMUMMC and SYSMMC (CFW) via Daybreak. I don't remember the original firmware versions these consoles came with, but I do have a screenshot of the HW & Fuse Info screen from my regular Switch.

Someone on Reddit mentioned that upgrading SYSMMC through Daybreak doesn't burn fuses. Because of this, trying to boot SYSMMC without CFW results in a black screen or crash, since the system detects a mismatch between the firmware version and the expected fuse count.

I’m assuming I need to downgrade SYSMMC (CFW) to the appropriate version for the fuse count, then perform a normal system update from within the semi-stock SYSMMC to sync everything up and make it bootable without PicoFly.

Currently, both systems are on firmware 22.1.0.

Questions​

1. How can I determine what firmware version each system is expecting based on fuse count or other info?
2. Is my assumption about the downgrade and re-upgrade process correct?
3. Are there any steps I’m missing, or is there a guide you can recommend for this process?

Thanks in advance for your help!

 

[Hayato213]

The burnt fuses (ODM 7/6) tells you what fuse you are on, based on the photo is 19, but if you did boot into OFW and being on the latest firmware then you probably burnt your fuses, so most like likely you have fuse count 21.

 

[YoNoid]

The burnt fuses (ODM 7/6) tells you what fuse you are on, based on the photo is 19, but if you did boot into OFW and being on the latest firmware then you probably burnt your fuses, so most like likely you have fuse count 21.

Is this to say that system sees a mismatch and will not boot to OFW stock? I want to test bypassing the PicoFly but i can't get it to work. What would be the best course of action at this point based on that photo and the info I gave?

 

[Hayato213]

Is this to say that system sees a mismatch and will not boot to OFW stock? I want to test bypassing the PicoFly but i can't get it to work. What would be the best course of action at this point based on that photo and the info I gave?

If it is higher fuse count and lower firmware then it probably won't boot, if it is really firmware 22.1.0 you should expect fuse count 21 instead of 20, so that photo you show might not be up to date.

 

[YoNoid]

If it is higher fuse count and lower firmware then it probably won't boot, if it is really firmware 22.1.0 you should expect fuse count 21 instead of 20, so that photo you show might not be up to date.

Ok. So my final question is... is it safe to update firmware via CFW in SYSMMC via daybreak? If so, is the only way to bypass SD care with volume buttons?

 

[Hayato213]

Ok. So my final question is... is it safe to update firmware via CFW in SYSMMC via daybreak? If so, is the only way to bypass SD care with volume buttons?

If you have a clean NAND then use Nintendo server to do your update, use hekate stock boot option to boot into OFW/Stock and do update from Nintendo server.

 

[YoNoid]

If you have a clean NAND then use Nintendo server to do your update, use hekate stock boot option to boot into OFW/Stock and do update from Nintendo server.

Thanks for your feedback. Will try. Appreciate it.

Post automatically merged: Jul 18, 2025

Got it working! Thanks!