Help a noob with if I need to update CFW to 18.0 or not

[4d1xlaan]

auto nogc isnt about those fuses, it's about preventing lotus3 fuses from burning

booting with hekate or fusee always bypasses firmware fuses

lotus3 fuses arent really relevant anymore anyway, because the last time fuses were burned for it was 12.0.0 (14.0.0 has a new lotus3 firmware, but didnt burn fuses.)

 

[TonyFerrol]

Based on that alone, I'd say that you can update your OFW safely enough. 17.0.0 was a bit problematic firmware as it changed the way saves were handled, which rendered some of the consoles reboot to black screen, even those that never had CFW on them. Since you're already on it, 18.0.0 and 18.0.1 shouldn't be problematic. At least, as far as I know.

According to the developer of the Atmosphere, in version 1.7.0 the basic support for firmware 18.0.0 (and by extension, 18.0.1) was added and everything should work from the user side of things. Not all the modules have been updated to the latest changes and they'll probably address them in one of the future releases.


One should never update their console's firmware unless the latest Hekate, Atmosphere and sigpatches are released for that firmware. This is even more important for the people that are using CFW on their sysNAND. emuNAND? Not so much. If you have an emuNAND setup, I believe that you can update OFW as long as Hekate is updated to support the latest firmware, but I can't say for sure. Someone else can further clarify (or rectify) on this.


If you haven't done anything mentioned but not limited to what's written here and you've been using your console's online features on OFW without issues so far (i.e. accessed eShop, bought and installed games, updates and DLC, played online games, etc.), I'd say that it should be fine. Nothing's 100% sure, but I'd say that I'm around 99% sure that it's fine to update.

Well, i've updated OFW, accessed the store, updated some games...and then gone to CFW and it is still all working

 

[rtncyp]

Hello GBATempers, not directly related to this but i am seeking advise on slightly related topic. So i bought my switch came with V16 firmware i am planning to instal NXV6S on it, should i update all the way and then install the modchip or leave it as is and install the modchip? I really would like to play games with my friends and when travelling on train play my offline games on CFW.

Thank you for any help

 

[kidkat210]

Hello GBATempers, not directly related to this but i am seeking advise on slightly related topic. So i bought my switch came with V16 firmware i am planning to instal NXV6S on it, should i update all the way and then install the modchip or leave it as is and install the modchip? I really would like to play games with my friends and when travelling on train play my offline games on CFW.

Thank you for any help

Doesn't matter if you update first or last. When it comes to switch modding, firmware doesn't matter anymore (it only matters if you have a switch on firmware 4.0 or lower since you then can use the Pegascape exploit. But that got patched out. After 4.x)

 

[rtncyp]

Doesn't matter if you update first or last. When it comes to switch modding, firmware doesn't matter anymore (it only matters if you have a switch on firmware 4.0 or lower since you then can use the Pegascape exploit. But that got patched out. After 4.x)

Thank you for the info, so it really doesnt matter if i update it to the latest and then dump it after chip install and not worry about convoluted update process?

 

[taffyponty]

If some games are saying my firmware is old (in dbi) specifically what is that referring too?
Is it atmosphere/ Hekate.
Can I just replace those or will it screw everything up? Is there an easier or safer way to update whatever firmware is ?

 

[RedColoredStars]

If some games are saying my firmware is old (in dbi) specifically what is that referring too?
Is it atmosphere/ Hekate.
Can I just replace those or will it screw everything up? Is there an easier or safer way to update whatever firmware is ?

When it says your firmware is old, it means your firmware is old. Does it say your Atmosphere is old? Or that Hekate is old? It specifically says FIRMWARE.

That said, you will still need to update all of them. First update Atmos and Hekate. Then find FW 18.0.1 by a Google search. We can't provide links to it here. Then use Daybreak to update your emummc's fw. Then update stock sysmmc's fw using the normal method of updating your Switch.

 

[taffyponty]

Can somebody please help me.
As somebody that barely ever touches this stuff?

I have a homebrew on my switch. But I guess it's about time to update it. Because of official Nintendo updates?
I guess some switch roms aren't working on my older homebrew??

Please tell me what steps I need to take to properly do this and not lose content or brick the switch ??

 

[Blythe93]

Can somebody please help me.
As somebody that barely ever touches this stuff?

I have a homebrew on my switch. But I guess it's about time to update it. Because of official Nintendo updates?
I guess some switch roms aren't working on my older homebrew??

Please tell me what steps I need to take to properly do this and not lose content or brick the switch ??

I've wrote a short guide here.

 

[taffyponty]

I don't know where to begin with this.



If I put my SD card into my pc. What am I needing to to update/replace/delete .



This forum thread seems to be several questions and answers like how to identify if it's emu or sys. How to update sigpatches etc . How does this apply to updating the firmware and therefore to update everything else for ROMs to work like before.



I'm curious but if I'm in flight mode and atmosphere. Why do roms not work. Cause I am not online so how does my system expect a firmware update and everything else. I didn't have this problem before. Only now.



My head feels like it's going to explode trying to understand all this. But I'm not using sigpatches I couldn't figure that out. I've been using the syspatch thing and atmosphere.

I previously followed a guide *somewhere* to set this up from scratch. But now I guess it's more complicated to update and preserve my stuff than a clean install.



Oh importantly. I got a problem here which just popped up. But I see no charging l.e.d. Or a battery charge icon on the screen when it's plugged into a usbc .

Is the whole thing dead or just the battery or something else



I want to take it to get it repaired but I'm a bit apprehensive as it's obviously modded should I just take out my SD with all that stuff on there or will they still know



I do appreciate help. Just wow I can't follow this I only messed with this stuff on initial setup really. Then left it alone except for transferring roms over.

Which I also had problems with because I couldn't use files bigger than 4 gig and installing from a remote location using db

I've wrote a short guide here.

i thing just didn't work

 

[Blythe93]

If I put my SD card into my pc. What am I needing to to update/replace/delete .

It's usually Hekate and Atmosphere, and sys-patch when needed. If the latest firmware is supported, you'll need to find those files somewhere on the Internet (recommended) of dump them by yourself once you update your sysNAND on stock firmware. I've explained in detail that post of mine so take a look one more time, and a couple more times after that until you understand it completely.

how to identify if it's emu or sys

Go to the System Settings > System and check current system version. If you have E at the end, you're on emuNAND. If you have S at the end, you're on sysNAND.

How to update sigpatches etc

Find the latest ones and drag and drop, overwriting the existing ones. Otherwise, delete the previous ones (check the folder structure in your latest set of sigpatches and remove whatever you find on the same folders on your SD card). OR switch to the sys-patch instead, which is what I personally use these days. Easier to update and. if we're lucky, we don't have to update it at all.

How does this apply to updating the firmware and therefore to update everything else for ROMs to work like before.

Before you update the firmware, you should always check if the latest firmware is supported by Hekate, Atmosphere and sigpatches/sys-patch at the very least i.e. whether the newer version of all or any of these is required for your CFW to work, games included. Also, if you're using additional sys-modules or homebrew apps that might need an update as well, you may want to wait for a bit until developers update their apps.

I'm curious but if I'm in flight mode and atmosphere. Why do roms not work. Cause I am not online so how does my system expect a firmware update and everything else. I didn't have this problem before. Only now.

You were lucky before, I guess? Newer games more often than not require higher firmware. Especially if you install the latest updates as well.
To put it simply, the game itself knows that it needs the higher firmware version and relays that info to the console which tells you that you need to update your firmware in order to use that game from now on.

Which I also had problems with because I couldn't use files bigger than 4 gig and installing from a remote location using db

I've linked to the video guide on how to use DBI. You don't have to transfer your games files over to the SD card in order to install them.

 

[nitrozz]

Big problem :
update ofw to 19.0.1
And emummc to same firm
system show 1.8.1 in emummc and fuse show 20
runing dbi shows 19.0.1
Cant understand. Help

 

[Draxzelex]

Big problem :
update ofw to 19.0.1
And emummc to same firm
system show 1.8.1 in emummc and fuse show 20
runing dbi shows 19.0.1
Cant understand. Help

What don't you understand?

 

[TomSwitch]

People often confuse the Atmosphere version with the firmware version because the decimal point is hard to see.

 

[nitrozz]

Yep, my mistake confused with firmware and ams. Sorry