Homebrew Safe to Update to 20 Now?

[bluedart]

I've been running sysnand 18.0.0 and atmosphere 1.7.0 on my launch switch (autoRCM) for over a year now without issues. It's great, and above all else everything works. I held back updating to 19.0.0 back when it seemed appropriate for games because it both didn't end up being necessary and there was some question of the safety of DBI, a homebrew I use excessively for the MTP functionality, and occasionally for its other functions. With 20.0.0, I remember specifically being told NOT to update because it breaks ToTK mods.

My question is: are these issues ironed out and is it safe to go to 20.0.0 now, or am I better off just having this device be where it is and passing on newer games on it?

I'm also using a special .bin that allows me to not use the syspatch module since it was an easier option. Is that still available for 20.0.0?

 

[Hayato213]

Firmware 20.x.x has less memory compare to 18.x.x, 20.x.x have 14MB while firmware 18.x.x have 40MB, also there is battery problem that be fixed.

 

[bluedart]

Firmware 20.x.x has less memory compare to 18.x.x, 20.x.x have 14MB while firmware 18.x.x have 40MB, also there is battery problem that be fixed.

I was hearing about a battery issue with 19, but the interesting thing is that sort of corresponded with the normal degradation for launch switches, so I figured it was a misunderstanding and mostly a nothing burger. I myself replaced my battery around 7 months ago since it was just old.

Atmosphere change logs on their github give me at least SOME hope as to the memory issue, since they did change their code around to "claw" some memory back, but I was hoping people using mods for that game could weigh in specifically. Also, did DBI end up bricking non-russian switches or was that also a nothing burger?

 

[CMDreamer]

Firmware 20.x.x has less memory compare to 18.x.x, 20.x.x have 14MB while firmware 18.x.x have 40MB, also there is battery problem that be fixed.

Could you please develop a bit more?

More/less memory for/to what? Is it better or worse?

[...] Also, did DBI end up bricking non-russian switches or was that also a nothing burger?

More like the "normal/common" drama from people that can't think by themselves and love trusting/spreading rumours.

Yes, I know duckbill did say that, but most people pissing their own pants for that reason, didn't cared to learn about the real whole background of it. No, I won't explain anything, keep spreading/trusting wrong information idc.

 

[Hayato213]

I was hearing about a battery issue with 19, but the interesting thing is that sort of corresponded with the normal degradation for launch switches, so I figured it was a misunderstanding and mostly a nothing burger. I myself replaced my battery around 7 months ago since it was just old.

Atmosphere change logs on their github give me at least SOME hope as to the memory issue, since they did change their code around to "claw" some memory back, but I was hoping people using mods for that game could weigh in specifically. Also, did DBI end up bricking non-russian switches or was that also a nothing burger?

The battery problem has to do with the system trying to connect online to accept Nintendo new EULA in sleep mode, we can use these line to stop the communication.

https://github.com/hanai3Bi/Switch-...ngs.md?rgh-link-date=2025-07-09T11:28:59.000Z

Im afraid that is just what we have to deal with if you want to play newer games.

Post automatically merged: Oct 13, 2025

Could you please develop a bit more?

More/less memory for/to what? Is it better or worse?

These are the changelog from Atmosphere 1.9.5 it did mention about less memory

Please note: As a result of changes made to nintendo's software in 20.0.0, there is roughly 10MB less memory available for custom system modules.

• We can only steal a maximum of 14MB from the applet pool, down from 40MB.
• To compensate for this, ams.mitm's heap usage has been reduced by 20MB.
  • To facilitate this, a new helper module (memlet) was added, so that memory may be temporarily stolen during the romfs building process.

 

[bluedart]

The battery problem has to do with the system trying to connect online to accept Nintendo new EULA in sleep mode, we can use these line to stop the communication.

https://github.com/hanai3Bi/Switch-OC-Suite/blob/master/system_settings.md?rgh-link-date=2025-07-09T11:28:59.000Z

Im afraid that is just what we have to deal with if you want to play newer games.

Post automatically merged: Oct 13, 2025

These are the changelog from Atmosphere 1.9.5 it did mention about less memory

Please note: As a result of changes made to nintendo's software in 20.0.0, there is roughly 10MB less memory available for custom system modules.

• We can only steal a maximum of 14MB from the applet pool, down from 40MB.
• To compensate for this, ams.mitm's heap usage has been reduced by 20MB.
  • To facilitate this, a new helper module (memlet) was added, so that memory may be temporarily stolen during the romfs building process.

Hey, thanks for specific info on that battery issue. I didn't realize that was happening, but it sounds like there's a fix already for it. So helpful!

Also that memory seems to work out to only -6MB, and since they added a buffer for loading, are people still having problems with mods now? I was on one of the ToTK modding discords earlier searching for this issue, and people don't seem to be talking about their switches crashing while playing on 20.0.0, so maybe it's fixed? This one is pretty important, as ToTK is the only switch game I've tried that I have found my rig can't emulate in a stable fashion better than actual hardware.

Oh, and to be fair, these concessions weren't actually necessary before right now for me, since everything I've wanted to play, including very new stuff, has actually run just fine on 18.0.0. The only software before [Z-A] I'm even aware of not working with this setup would be Silk Song for some reason, and that's not a switch exclusive.

That just leaves the DBI issue and possibly whatever that new module that made sigpatches more confusing is. Are those going to be problems?

 

[Hayato213]

Hey, thanks for specific info on that battery issue. I didn't realize that was happening, but it sounds like there's a fix already for it. So helpful!

Also that memory seems to work out to only -6MB, and since they added a buffer for loading, are people still having problems with mods now? I was on one of the ToTK modding discords earlier searching for this issue, and people don't seem to be talking about their switches crashing while playing on 20.0.0, so maybe it's fixed? This one is pretty important, as ToTK is the only switch game I've tried that I have found my rig can't emulate in a stable fashion better than actual hardware.

Oh, and to be fair, these concessions weren't actually necessary before right now for me, since everything I've wanted to play, including very new stuff, has actually run just fine on 18.0.0. The only software before [Z-A] I'm even aware of not working with this setup would be Silk Song for some reason, and that's not a switch exclusive.

That just leaves the DBI issue and possibly whatever that new module that made sigpatches more confusing is. Are those going to be problems?

If you used mod with totk you might run into problem as 14MB isn't enough, can't run pokemon games when mission control and salty NX is running, as figure TOTK probably have problem if you use mods.

 

[bluedart]

If you used mod with totk you might run into problem as 14MB isn't enough, can't run pokemon games when mission control and salty NX is running, as figure TOTK probably have problem if you use mods.

Yeah. It's in a nebulous space where everything could be fine, or it could be a problem. Then there's doing it correctly since it's been over a year since I messed with cfw maintenance. I also don't have the 32GB free to backup right now, so I'd be taking a gamble.

Really, Nintendo just made their firmware after 18 a batch of caveat soup. So far we've been able to patch down everything but Silk Song, which isn't even exclusive. It's probably not worth it for me right now for only one game. I'll keep you posted if I end up trying to update, but I doubt it.

Seriously, thanks for the heads up on the battery thing though. I'd have definitely freaked out when it started draining in sleep mode again.

 

[Jayro]

I updated my banned switch firmware to the latest, and latest atmosphere, lockpick_RCM, hekate, and sigpatches. Everything works fine to play Pokemon Legends Z-A.

 

[bluedart]

Update: All right. I ended up not updating, and I'll luckily be sticking with 18.0.0 for a while longer, since I was able to get the game in question installed and working on it. Thanks again for the info and heads-up for the potential issues in upgrading firmware.

 

[MrMittens1989]

I just updated mine, everything works fine, even the latest releases load and play with no issue.

 

[theShrike]

I updated my 19.0 to 20.x and ended up having an issue where the controller would stick running in random directions while playing games. Also, the title load screen was taking much longer to load titles. I didn't care for it and downgraded back to 19. It was a PITA but I was able to get it working.