Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[Lostbhoy]

If you update clean sysmmc online, and let it do the eula thing, can someone figure out what the right user account files are to copy over to emummc to make it believe it's done? Preferably without affecting other stuff like idk playtime records.

Serious question as I've seen a lot of comments mention the playtime thing....

Why do people care how long they have spent on a game?? Is your parents or something??

 

[UsernamesAreWeird]

Can't have as many custom sysmodules at once

What is the limit?

 

[hippy dave]

What is the limit?

They all use different amounts of memory so keep adding more until it breaks?

Post automatically merged: May 29, 2025

Serious question as I've seen a lot of comments mention the playtime thing....

Why do people care how long they have spent on a game?? Is your parents or something??

It's a stat, some people are interested in it, some people aren't. Some people count their steps I used it the other day to report how long it took me to finish a small puzzle game.

 

[hunter_x]

Like many people here, I'm having the battery drain issue. It's happened to me twice already. In 16 hours. I thought shutting down from Hekate might fix it, but no.

I've been reading a lot of posts, and some mention creating a new emmumc from 20.0.0, or something like that.

Is there a solution to keep firmware 17.0.1 in sysnand so that the emmummc is at 20.0.1 and doesn't drain the battery?

I've also read that airplane mode fixes it, I always have the console in airplane mode and it doesn't fix it at all for me.

 

[Blythe93]

Is there a solution to keep firmware 17.0.1 in sysnand so that the emmummc is at 20.0.1 and doesn't drain the battery?

I don't have the battery draining issue myself, mainly because I have no NNID linked to any of my profiles (except for the fake ones via linkalho). Not sure if that's the reason why I haven't run into any issue on my emuNAND CFW 20.0.1 (I'm yet to update to 20.1.0).

If I were you, I'd backup save files and whatever else you have of importance, recreate an emuNAND, update it to 19.0.1 and stay there as there's no real reason to update to 20.x.x yet.

 

[hunter_x]

I don't have the battery draining issue myself, mainly because I have no NNID linked to any of my profiles (except for the fake ones via linkalho). Not sure if that's the reason why I haven't run into any issue on my emuNAND CFW 20.0.1 (I'm yet to update to 20.1.0).

If I were you, I'd backup save files and whatever else you have of importance, recreate an emuNAND, update it to 19.0.1 and stay there as there's no real reason to update to 20.x.x yet.

Okay, I appreciate it. I'm going to do that, but I want to go a step further and be prepared for when if I have to upgrade.

If I format my switch, don't add the nintendo account I leave it at 17.0.1, back up the nand, of course, and create emunand. And I link with linkhalo some account in case I need it. should it be ok then at that point?

 

[Blythe93]

If I format my switch, don't add the nintendo account I leave it at 17.0.1, back up the nand, of course, and create emunand. And I link with linkhalo some account in case I need it. should it be ok then at that point?

It should be OK because that's how i did it with mine: my sysNAND Is on 16.0.0 or something and my emuNAND is on 20.0.1, I never had NNID linked to any profile on my sysNAND so it didn't carry over to emuNAND. You could try unlinking the account with the NNID with linkalho on emuNAND and see if that fixes the battery draining issue (make a backup of your account so that you can restore if it doesn't work). If it does, you can use fake NNID for the games that require it.

Otherwise, just recreate the emuNAND from scratch and update to 19.0.1.

As for future-proofing, if you decide to remove your profiles with linked NNIDs or factory reset your console, note that e.g. Animal Crossing New Horizons has some extra in-game items (Mario-themed ones, if I remember correctly) that you won't be able to get unless you have real NNID linked. Sadly, it doesn't work with fake one for some reason. It's a small issue but worth mentioning, I guess if you're ACNH fan. Personally, that's the only issue I've run into.

Hopefully, you'll be able to fix the battery draining issue. Being offline/airplane mode does "fix" it but if you need the Internet connection for some reason or another you'll probably run into it again.

 

[hunter_x]

It should be OK because that's how i did it with mine: my sysNAND Is on 16.0.0 or something and my emuNAND is on 20.0.1, I never had NNID linked to any profile on my sysNAND so it didn't carry over to emuNAND. You could try unlinking the account with the NNID with linkalho on emuNAND and see if that fixes the battery draining issue (make a backup of your account so that you can restore if it doesn't work). If it does, you can use fake NNID for the games that require it.

Otherwise, just recreate the emuNAND from scratch and update to 19.0.1.

As for future-proofing, if you decide to remove your profiles with linked NNIDs or factory reset your console, note that e.g. Animal Crossing New Horizons has some extra in-game items (Mario-themed ones, if I remember correctly) that you won't be able to get unless you have real NNID linked. Sadly, it doesn't work with fake one for some reason. It's a small issue but worth mentioning, I guess if you're ACNH fan. Personally, that's the only issue I've run into.

Hopefully, you'll be able to fix the battery draining issue. Being offline/airplane mode does "fix" it but if you need the Internet connection for some reason or another you'll probably run into it again.

In the case of Animal Crossing, I haven't played it in a long time, but if it's just something thematic like the Mario thing and it doesn't affect the game, it doesn't matter. For the rest, I prefer to recreate the emunand and stay on 19.0.1 for a while and be calm without a linked account, and then use linkhalo if I need to.

 

[Sodamyte]

*whew* got it all updated and everything works perfectly.

 

[hunter_x]

Since yesterday I decided to do some tests. As I said before, format sysnand, do not link any account (This as Blythe93 said) seems to be the key, I deleted the emunand and recreated them, I have two SD cards.

Sysnand in 17.0.1, SD01 19.0.1, I'm testing with SD02, 20.1.0, 3-4 hours, has not happened the battery drain. Right now I'm going to perform the last test I have linked an account with linkalho, creating 2 users. I have only linked one of them. I also linked a remote with mission control. At 12:21 I have turned it off, about 3:00 pm, or 3:30, I will turn it on again, to see if it has drained something, according to some calculations in that time interval should drain about 15%.

It seems that recreating the emunand, and putting it all back on without a nintendo account linked, may be the solution, although I understand that it is very tedious to do. The aeroplane mode, which many commented on didn't work for me.

Once these 3 hours are over, I will edit the comment adding the result.

Translated with DeepL.com (free version)

Edit 1, 15:37. After 3h and 15 minutes, turned off at 100%, it is still at 100% after turning it on, I'll keep an eye out in case something changes, tomorrow, but for the moment in my case it seems to be solved.

Thank you very much @Blythe93 for your help.

 

[Sodamyte]

Mine never goes on the internet anyway, so i don't think battery drain will be an issue.

 

[impeeza]

Guys,have the sigpaches been updated?

yes on the sigpatches thread on the OP there is the v2 for ATM 1.9.1 and FW 20.1.0

 

[Andre63]

The aeroplane mode, which many commented on didn't work for me.

From what I understand, airplane mode does not fix the problem, but bypasses it by preventing any attempt to connect to Wi-Fi.

No?

 

[hunter_x]

From what I understand, airplane mode does not fix the problem, but bypasses it by preventing any attempt to connect to Wi-Fi.

No?

At the time I had an account linked to sysnand, because I didn't know Linkalho, when I created emunand that account remained. I even before creating emunand removed the wifi, but not only with the aeroplane mode, from the configuration the password and everything. And even with all that plus aeroplane mode it didn't solve it.

If the account is linked, something happens that the battery heats up and wears out. The most feasible solution is to redo the emunand, with a sysnand that has no accounts or anything linked. And if you need to use linkalho.

Some people on atmosphere's github say that creating the emunand from 20.1.0 has not experienced the problem.

 

[its-my-right]

At the time I had an account linked to sysnand, because I didn't know Linkalho, when I created emunand that account remained. I even before creating emunand removed the wifi, but not only with the aeroplane mode, from the configuration the password and everything. And even with all that plus aeroplane mode it didn't solve it.

If the account is linked, something happens that the battery heats up and wears out. The most feasible solution is to redo the emunand, with a sysnand that has no accounts or anything linked. And if you need to use linkalho.

Some people on atmosphere's github say that creating the emunand from 20.1.0 has not experienced the problem.

Is your switch banned ? If no, did you try this procedure ?
- Be connected to N servers via wifi/ethernet from sysnand, on firmware v20+. Access channels, eshop, etc, to be sure (the point is to make sure your N account has been connected to N servers, after installing firmware v20+)
- Remove wifi connections from switch menu
- Disable cloud saves (if you have it) from switch menu
- Make a new emunand from sysnand
- enable wifi on emunand (of course with proper dns blocking: dns mitm from atmosphere (hosts folder) + 90dns maybe)
- check if battery drain is solved

This is the exact procedure I followed and now the battery drain has disappeared. Maybe your battery drain has a different source, but if your procedure vary from this one, maybe you could try it just to see (use an other micro SD card so you don't have to delete your current emunand, this is just to check, and then you could decide if you do it for "production" if the problem is solved or not)

 

[Bigdrago]

Update will soon be finished. But why are you using CFW on Sysmmc? Any advantages? I only use this conf file:

[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=100
noticker=0
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[CFW - emuMMC]
pkg3={atmosphere/package3
emummcforce=1
cal0blank=1
kip1patch=nosigchk
icon=bootloader/res/emu_boot.bmp

[Stock - sysMMC]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/stock_boot.bmp

 

[hunter_x]

Is your switch banned ? If no, did you try this procedure ?
- Be connected to N servers via wifi/ethernet from sysnand, on firmware v20+. Access channels, eshop, etc, to be sure (the point is to make sure your N account has been connected to N servers, after installing firmware v20+)
- Remove wifi connections from switch menu
- Disable cloud saves (if you have it) from switch menu
- Make a new emunand from sysnand
- enable wifi on emunand (of course with proper dns blocking: dns mitm from atmosphere (hosts folder) + 90dns maybe)
- check if battery drain is solved

This is the exact procedure I followed and now the battery drain has disappeared. Maybe your battery drain has a different source, but if your procedure vary from this one, maybe you could try it just to see (use an other micro SD card so you don't have to delete your current emunand, this is just to check, and then you could decide if you do it for "production" if the problem is solved or not)

I used Sysnand on an early version of the CFW before emunand existed without internet or anything, when I updated it was not banned, look a bit at the eshop and stuff to check. But that's way behind me, I don't use Sysnand for a long time, and I don't need it now either, I don't usually pay for online console games, for that I have PC.

The procedure that I told served me, today I checked it again and everything was perfect.

But reading your procedure and mine. The thing is clear. It's some kind of weird check that the Nintendo account does when updating to 20.0.0+.

I now use a linkalho account, because I didn't really need mine either, I just didn't know the application when I did it, and I was too lazy to recreate emunand and everything, but to solve this problem I wasn't lazy at all, it was necessary.

 

[iluvfuzz]

So banned switches don't experience the power drain?... Because I updated my switch to the newest everything... (which might have been a mistake, but it wouldn't boot) and I noticed my battery draining really fast. I do have wifi on, but my switch is banned so.... I just thought it was because my kids keep letting it die.

 

[Andre63]

Hi all,

I wanted to test the battery drain.
So I took a brand new SD card, straight out of the box.
Formatted it to FAT 32 with FAT32Format GUI.

With only Hekate 6.3.1, Atmosphere 1.9.1, new emuMMC from SysNAND 20.1.0, and exosphere.ini configured to prevent connection to Nintendo servers, the battery only drained 1% after an hour of standby.
I left Wi-Fi active during these process.
I'm now going to install Tesla and Sys-Patch.

I'm proceeding by elimination.

If you have any criticism or advice, you're welcome.

 

[Blythe93]

If you have any criticism or advice, you're welcome.

Do you have any profile linked with a valid NNID? If not, that might be why you aren't getting an increased battery drain even when connected to the Internet and Nintendo servers are blocked. I only have fake NNIDs linked to my profiles via linkalho and there's no battery draining issue while connected to the Internet.

I'm now going to install Tesla and Sys-Patch.

Those things most likely won't cause the battery draining issue. Still, better safe than sorry and do the test and let us know the result.