Updated OFW and Atmos - Now no games work

[CasuallyDressed]

So I went about updating my Switch today, this is what I did:

1. Downloaded Atmosphere 1.6.2
2. Downloaded OFW 17.0.1 (this may have been a mistake, should I have got 17.0.0?)
3. Plugged my SD card in, deleted folders Atmosphere, Switch and the file hbmenu.nro (also probably a mistake, normally I just copy/overwrite, for some reason this time I deleted/copied). Also deleted the old fusee.
4. Copied over the new folders Atmosphere, Switch and the file hbmenu.nro, and copied the new fusee. Also copied over the 17.0.1 firmware.
5. New Atmosphere confirmed installed, opened Daybreak and went about updating OFW.
6. OFW confirmed installed. Everything up to date.
7. Had a weird issue where the Switch would crash and report an error. Googled the error and an easy fix was to turn on Airplane Mode. Whatever, I'm banned anyway, so turned it on and the Switch doesn't crash any more. Will look further into it later or wait for a new version of Atmosphere which may fix it.

Now, no games are booting. I get "Could not start the software. Please try again from the HOME Menu." I tried copying over a new game via DBI to see if a freshly installed game would boot. DBI reported that it installed correctly, but my dashboard just shows a spinning wheel and "Could not start the software".

Any ideas? Thanks in advance.

 

[BigOnYa]

https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
You need sigpatches.

 

[CasuallyDressed]

Thanks for the reply! What do I do with the files in the zip? Sorry, not had to update sig patches before!

 

[BigOnYa]

Thanks for the reply! What do I do with the files in the zip? Sorry, not had to update sig patches before!

You unzip it to, or copy both folders, to your sd card.

 

[CasuallyDressed]

You unzip it, or copy both folders to your sd card.

Is that it? Ok cool, will do it now!

EDIT - Quickest fix ever. All done! Thanks man

 

[petspeed]

7. Had a weird issue where the Switch would crash and report an error. Googled the error and an easy fix was to turn on Airplane Mode. Whatever, I'm banned anyway, so turned it on and the Switch doesn't crash any more. Will look further into it later or wait for a new version of Atmosphere which may fix it.

You need to block Nintendo servers with DNSmitm. That will fix the crash
https://rentry.org/ExosphereDNSMITM

 

[BigOnYa]

You need to block Nintendo servers with DNSmitm. That will fix the crash
https://rentry.org/ExosphereDNSMITM

No he's banned already, so that won't matter

 

[petspeed]

No he's banned already, so that won't matter

So blanking the serial without blocking Nintendo servers doesn't result in a crash with fw 17.x if the Switch is banned?

 

[BigOnYa]

So blanking the serial without blocking Nintendo servers doesn't result in a crash with fw 17.x if the Switch is banned?

Not for me atleast, Im on a banned unit, did not block servers and have had no problems since updating to 17.0, then to 17.0.1. I think when you are banned, you are already being blocked from big N to those servers anyways.

 

[kidkat210]

Not for me atleast, Im on a banned unit, did not block servers and have have had no problems since updating to 17.0, then to 17.0.1. I think when you are banned, you are already being blocked from big N to those servers anyways.

But is your prod.info blanked out by other means that's not atmosphere?

 

[BigOnYa]

But is your prod.info blanked out by other means that's not atmosphere?

Nope, I have never blanked my prod.info or serial#.

 

[kidkat210]

Nope, I have never blanked my prod.info or serial#.

Ever since fw 17. If your prod.info is blanked out on fw 17. Itll crash the switch unless you do 1 of 4 things.
1) restore prod.info
2) always have airplane mode on
3) setup dnsmitm.
4) disconnect swotch from internet (cant remember if this work or not but I've seen it floating around)
It's the reason I haven't jumped to 17 on my emunand

 

[BigOnYa]

It's the reason I haven't jumped to 17 on my emunand

Then you don't get to play any newer games. Games coming out now require 17.0 FW.

 

[kidkat210]

Oh I know, been in the scene since fw 4.x back before sx os and atmosphere got emunand. I havent made the jump cause I havent been too interested in my switch lately and I don't feel like going through the hassle atm to do one of the 4 things to rectify the problem.

But anyways, if your prod.info is blanked. It's gonna crash on 17.x. gotta do one of the 4 things I mentioned before to fix it

 

[masterkill3234]

Hi guys,

I'm very very new to the world of modding in general (still very unfamiliar with the terms/apps used here) and I'm facing problems with updating my switch's CFW.. I've checked out tutorials on Youtube and tried following the instructions here on gbatemp but still haven't managed to solve the problem

So my little brother accidentally updated my switch's OFW to 18.0.1, and since then the CFW won't load when I turn on the switch. What usually happens is that the screen will stay black for a while, and then the OFW will automatically be loaded. According to the serial no. on the box my switch is already a patched version, however the switch has been modded by the seller before I bought it.

Based on the seller's description it seems the CFW is booted in emunand, and the ofw is in nand. Back when the switch was still working fine, CFW will always be loaded automatically when pressing the power button normally; and OFW will be loaded only when pressing power button together with the volume button.

The method I've tried is: (1) formatting my sd card; (2) copying the most updated atmosphere & hekate to my sdcard; and (3) triggering RCM with the jig. However as soon as I try injecting payload with tegrarcm, the software is not responding anymore (indicating that the switch is patched).

Could you guys advise me further on what to do?

Thanks so much in advance for your help!