Yes, linked with valid NNID.Do you have any profile linked with a valid NNID?
Yes, linked with valid NNID.Do you have any profile linked with a valid NNID?
That is not true. Blocking nintendo servers doesn't fix the battery drain issue.The conclusion is obvious, when updating, if you have a valid id, it does some kind of compo and this drains the battery. By configuring exosphere.ini to not connect to the nintendo servers, it does not drain the battery for this reason.
I really didn't know about exosphere.ini, but there are already three or more solutions in this chat, so everyone can use the one they like the most.
So it's something related to the previously linked account and it seems that the only solution is the one Blythe93 and I were talking about, to recreate everything without a nintendo account?That is not true. Blocking nintendo servers doesn't fix the battery drain issue.


From the Atmosphere discord:SHIT!
Ver. 20.1.1 (Released June 2, 2025)
Fixed an issue where some software would not start after updating to system version 20.1.0.
https://switchbrew.org/wiki/20.1.1
View attachment 508879

I do not know what NS is.From the Atmosphere discord:
”Only NS was updated. Should be fine to update for now.”
”So obviously atmosphere will boot, and everything aside from anything that interacts with NS (i.e. patches or so) will work, that worked before, on 20.1.0”
@impeezaSHIT!
Ver. 20.1.1 (Released June 2, 2025)
Fixed an issue where some software would not start after updating to system version 20.1.0.
https://switchbrew.org/wiki/20.1.1

Reports are indicating, Atmosphère boots, but seems not work fine. as always we must to wait for a new version. So far the sigpatches and other services are the same.Battery Discharge (continued)
After installing Tesla and Sys-Patch, the battery loses 1% after 1 hour of standby.
Wi-Fi is active during standby.
So I installed all the homebrew I use, but no games or Tinfoil.
The battery lost 2% after 3 hours of standby.
Wi-Fi active.
This clearly shows that starting with a new emuMMC generated from a sysNAND linked to an active Nintendo account solves the problem of overheating and rapid battery drain.
From there, all that's left is to find a reliable and quick way to reinstall all the games.
JKSV will restore all the saves, which will likely need to be done individually.
Post automatically merged:
@impeeza
I ran the tests on version 20.1.0 and I see that 20.1.1 has just been released.
Is Atmosphere compatible to check if this battery issue is still present?
I think it will still be, but we need to check.
Thanks for your help.

yes,I have emuNAND with 19.0.1 and SysNAND with 20.1.1
Is it possible to stay in emuNAND while everything works and put the files in SD to load StockNAND with atmosphere
I mean emuNAND works isolate but needs files in SD
I switch between emuNAND with magic and OfficialFW
If I need copy saves from OfficialFW I use Stock to load magic without use emulate partition
How could I prepare the SD to make it works without update emuNAND?
so, the key is update atmosphere and hekate that will be retrocompatible with 19.0.1 and has both payload to boot emunand and put new payload to CFW SysNAND 20.1.1. Is it?yes,
yes.
Each NAND have a independant «Nintendo» folder
the only thing the NANDs share are the Atmosphère configuration and homebrew on SDMC:/switch FOLDER.
Post automatically merged:
Ha ha ha ha, Off-course SciresM WILL BE OUT UNTIL JUNE 15TH!!! Will be no June 15th without SciresM, IT IS IMPOSSIBLE!!!
View attachment 509049
June 15th only exist if SciresM allow it!

yes the tutorial is called Hekate's readme.md is on the front page of the hekate's github.so, the key is update atmosphere and hekate that will be retrocompatible with 19.0.1 and has both payload to boot emunand and put new payload to CFW SysNAND 20.1.1. Is it?
Is there any tutorial or some clue to know the config file to got this?

There is a file called SDMC:/atmosphere/config/override_config.ini on which you can setup the keys behaviordumb question, how do change it, so I have to hold L to enable mods, not to disable them
[hbl_config]
; Program Specific Config
; Up to 8 program-specific configurations can be set.
; These use `program_id_#`, `override_address_space_#`, and `override_key_#`
; where # is in range [0,7].
; program_id_0=010000000000100D
; override_address_space=39_bit
; override_key_0=!R
; Any Application Config
; Note that this will only apply to program IDs that
; are both applications and not specified above
; by a program specific config.
; override_any_app=true
; override_any_app_key=R
; override_any_app_address_space=39_bit
; path=atmosphere/hbl.nsp
override_key=R
[default_config]
; override_key=!L
; cheat_enable_key=!L
Battery Discharge (continued)
After installing Tesla and Sys-Patch, the battery loses 1% after 1 hour of standby.
Wi-Fi is active during standby.
So I installed all the homebrew I use, but no games or Tinfoil.
The battery lost 2% after 3 hours of standby.
Wi-Fi active.
This clearly shows that starting with a new emuMMC generated from a sysNAND linked to an active Nintendo account solves the problem of overheating and rapid battery drain.
Ha ha ha ha, Off-course SciresM WILL BE OUT UNTIL JUNE 15TH!!! Will be no June 15th without SciresM, IT IS IMPOSSIBLE!!!
View attachment 509049
June 15th only exist if SciresM allow it!


Or, unless some kind person that already has the environment set up to build a release with the USB fix can do so for all of us before SciresM does it.![]()



It is on the root of the SD card?I have payload.bin in SD card.
It's laters Hekate so are renamed.It is on the root of the SD card?
Is the latest Fusee.bin or latest Hekate renamed?
