Hacking can't boot into ofw

[poopascoopa9000]

recently I decided to restore a backup that was like from a year ago or something and now I have a fuse mismatch because I didn't know they existed until now lolol (retrard moment). can I boot into ofw somehow and update it?

 

[Kubas_inko]

recently I decided to restore a backup that was like from a year ago or something and now I have a fuse mismatch because I didn't know they existed until now lolol (retrard moment). can I boot into ofw somehow and update it?

Boot through any custom bootloader and update.

 

[poopascoopa9000]

So do I just boot to my emuMMC and system update my sysnand and everything from there so that ofw doesn't black screen?

 

[Lacius]

So do I just boot to my emuMMC and system update my sysnand and everything from there so that ofw doesn't black screen?

No, boot your sysNAND using the latest version of Hekate. Then, you can update your clean sysNAND from the system settings.

 

[poopascoopa9000]

booting stock still gives me a black screen, i reinstalled atmosphere and hekate and tried booting stock again but still nothing

 

[Kubas_inko]

booting stock still gives me a black screen, i reinstalled atmosphere and hekate and tried booting stock again but still nothing

And are you booting through hekate to stock?

 

[poopascoopa9000]

I do, I run hekate 5.3.0 through rcm mode. only thing I could boot into is my CFW emummc

 

[crazy_p]

Add this line to your Hekate Setting to force SysNand:

emummc_force_disable=1

or rename your emummc Folder temporary to emummc.bak

 

[poopascoopa9000]

OK so I think I might've done something, so I renamed the emuMMC folder to emummc.bak and launched through fusee-primary because the stock option still wasn't working, but launching through fusee-primary I now see that my system is at 9.0.1|AMS 0.13.0|S. guess I can update now right?

 

[Lacius]

OK so I think I might've done something, so I renamed the emuMMC folder to emummc.bak and launched through fusee-primary because the stock option still wasn't working, but launching through fusee-primary I now see that my system is at 9.0.1|AMS 0.13.0|S. guess I can update now right?

Yes, you can update while using Atmosphere.

 

[poopascoopa9000]

thanks 4 da help i have 2 brain cells

 

[Skynet211]

Sorry to jump onto this thread, seemed more fitting than starting a new one. I have a similar situation but sysnand is missing from Hekate.

I too have a fuse mismatch. I somehow burnt 12, but the OFW on the Switch was 6.2.0, so it was quite a surprise when I found out it was 12 not 8 fuses.

I can boot via fusee-primary payload only to 9.2.0 CFW. I have no boot options either. I can upload images from Hakate if required.

I guess my problem is that my Switch appears to be missing OFW completely. I assume I've borked my Switch entirely? I've seen guides on how to install OFW via ChoiDujour from PC, which WOULD work but my keys file doesn't work if trying it for the 9.2.0 FW, I'm guessing because this actually came from 6.2.0?

EDIT: So not showing any boot options was a config issue, which I've fixed. So I've got listed CFW and 6.2.0. I also restored Boot0/1 and nand from backup. When I boot into OFW I get Error Code 2002-2634 "An error has occurred" at the bottom it then lists my serial and 6.2.0

EDIT: Well after 2 days total (was tinkering well before I posted) I have it sorted. After the last edit I googled the error code and saw it was cartridge slot related. I took the cart out. I'm now back on my 6.2.0 OFW and can boot into 6.2.0 CFW

This has been a nightmare, but it's all sorted now. Let's see how long until I can break it and unbreak it again.