Hacking Question after NAND restore unable to boot OFW

krodami · Jun 19, 2019

Today my Switch would not load games from the SD card, i thought maybe the battery died and I just needed to reboot and inject the payload from RCM. However when I attempted to inject Fusee Atmosphere, it would display a short text and then...nothing just a blank screen, not off, just blank. I wasn't sure what the issue was at that point, I double checked and auto update was turned off. So I thought maybe something got messed up, I'll just restore from my NAND. That is where things seemed to go from bad to worse. After the NAND restore, I am no longer able to load OFW or Atmosphere which now I get the boot screen and then a white kind of curved triangle icon then it goes blank again. I can still get into RCM and run things like Hekate but that seems to be the extent of it. I followed the NAND restore guide to the letter, so I am not sure why it didn't work; is there anything I can do at this point to at least get back to factory settings? I also tried reformatting my SD card from exFat to Fat32 to see if that helped, it did not.

I am hoping someone here can lead me in the right direction.

Itsuki235 · Jun 19, 2019

krodami said:
After the NAND restore, I am no longer able to load OFW or Atmosphere which now I get the boot screen and then a white kind of curved triangle icon then it goes blank again.

It looks like your switch updated and burnt a fuse. The files on the SD card are probably old and no longer work on the newer OFW. To fix it:

Important: Delete the following folders from the SD card /Atmosphere /bootloader /sept /config.
Go to https://www.sdsetup.com/
Select Kosmos defaults and download
Extract the files to the SD card
Transfer the SD card to the switch
Launch Hekate again
(optional) Make sure AutoRCm is enabled
select Tools->Autoboot->CFW
Launch->CFW
Atmosphere should start

If you installed any NSPs they might need to be reinstalled. Signature and es patches might need to be added for still depending upon how you are using CFW.

PHiLiPZ · Jun 19, 2019

Good advice. I’d add to it that once he gets to hekate he should check the number of burnt fuses. If more fuses are burnt than 9 then CFW won’t work now. Removing AutoRCM might help to at least boot the OFW, which will be 8.1.0.

krodami · Jun 19, 2019

PHiLiPZ said:
Good advice. I’d add to it that once he gets to hekate he should check the number of burnt fuses. If more fuses are burnt than 9 then CFW won’t work now. Removing AutoRCM might help to at least boot the OFW, which will be 8.1.0.

I have 10 burnt fuses out of 64.

--------------------- MERGED ---------------------------

Itsuki235 said:
It looks like your switch updated and burnt a fuse. The files on the SD card are probably old and no longer work on the newer OFW. To fix it:
...

Thanks I am trying this now, quick question, if I have auto update turned off, any idea why it would have updated and burnt another fuse?

krodami · Jun 19, 2019

Thank you @Itsuki235! I did not have an option for "select Tools->Autoboot->CFW" however I was able to drop the latest fusee-primary.bin into bootloader\payloads and then Launch Hekate and go to "Launch->Payloads" and selected fusee-primary.bin and it successfully launched!

What should I do from here? What changes need to be done to avoid this in the future?

krodami · Jun 19, 2019

I believe I have discovered what may have happened, even though Auto Update was turned off, I think one of the games prompted that an update was available and one of the kids likely went ahead and ran the update.

ELY_M · Jun 19, 2019

the atmosphere dev team have atmosphere working on 8.1.0 it will be out very soon.

Lawa Ye · Jun 19, 2019

Itsuki235 said:
It looks like your switch updated and burnt a fuse. The files on the SD card are probably old and no longer work on the newer OFW. To fix it:

Important: Delete the following folders from the SD card /Atmosphere /bootloader /sept /config.

Go to https://www.sdsetup.com/

Select Kosmos defaults and download

Extract the files to the SD card

Transfer the SD card to the switch

Launch Hekate again

(optional) Make sure AutoRCm is enabled

select Tools->Autoboot->CFW

Launch->CFW

Atmosphere should start

If you installed any NSPs they might need to be reinstalled. Signature and es patches might need to be added for still depending upon how you are using CFW.

i have the same problem does that mean we can never open OFW again ?

krodami · Jun 19, 2019

Lawa Ye said:
i have the same problem does that mean we can never open OFW again ?

I'm not an expert but I suspect it means we need to wait for the devs to finish adding support to 8.1.0 for atmosphere, then i would think we could install the 8.1.0 firmware through ChoiDujour which should stop the bootloader panic. Hopefully someone can correct me if I am wrong.

Itsuki235 · Jun 21, 2019

krodami said:
What should I do from here? What changes need to be done to avoid this in the future?

Disable auto updates, use airplane mode or 90DNS

Lawa Ye said:
i have the same problem does that mean we can never open OFW again ?

It takes a few days to add support usually. It only took 2 days this time? I think that is a record.

So, Atmosphere and SXOS have now been updated to support native 8.1 now. Download the latest atmosphere and the related sig and es Patches.

Hekate still does not support 8.1 so you will have to do what krodami is doing and push fusee-primary.bin (part of atmosphere) to boot properly on native 8.1.

krodami · Jun 22, 2019

I updated to 8.1 with the latest atmosphere, no issues. I can also now boot OFW. Now to do another NAND dump, setup 90DNS, turn off wifi, and hopefully not hit this again moving forward.

Itsuki235 · Jun 24, 2019

krodami said:
I updated to 8.1 with the latest atmosphere, no issues. I can also now boot OFW. Now to do another NAND dump, setup 90DNS, turn off wifi, and hopefully not hit this again moving forward.

The point of 90 DNS is to be able to leave WiFi enabled to access other WiFi related features, while not connect to official servers. As long as the console never changes networks, WiFi can be left on. Do remember to turn off Auto-Updates however.

System Settings->System->AutoUpdate: Off

Hacking Question after NAND restore unable to boot OFW

Member

Well-Known Member

Well-Known Member

Member

Member

Member

Developer

Active Member

Member

Well-Known Member

Member

Well-Known Member

Similar threads

Popular threads in this forum