Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,743,687
  • Replies Replies 9,313
  • Likes Likes 92
Hello Impeeza,

So it seems that there is another way to prevent battery drain -> instead of doing a full format, connect the Switch to Ninja Servers and accept the EULA stuff from first Nintendo Account connection attemp, right?

Do you know whether is there any tutorial to do so?

Thanks in adavance,

Best regards

Willsito
You can't do that without risking a ban, unless you never did anything the Ninjas wouldn't approve of (and if that was the case, you wouldn't have the drain issue to begin with, since you could just let it go online normally).

So, the real solution to this drain issue is to:
  1. First of all, back up any saves you care about, with JKSV, DBI, or whatever you use. Do it now. If you aren't doing that regularly already, you probably should.
  2. Then, start from a clean OFW, update that to 20.x, let it call home once (just to appease the Ninjas, no need to link an account if you don't need to).
  3. Finally, create a new emuNAND from that, reinstall your stuff, and restore any saves you want to keep.
Everything else (airplane mode, turning wifi off, changing config settings...) are just workarounds, not a solution.
 
Hello Impeeza,

So it seems that there is another way to prevent battery drain -> instead of doing a full format, connect the Switch to Ninja Servers and accept the EULA stuff from first Nintendo Account connection attemp, right?

Do you know whether is there any tutorial to do so?

Thanks in adavance,

Best regards

Willsito

Yes, is in the post https://gbatemp.net/posts/10708649/

You can't do that without risking a ban, unless you never did anything the Ninjas wouldn't approve of (and if that was the case, you wouldn't have the drain issue to begin with, since you could just let it go online normally).

So, the real solution to this drain issue is to:
  1. First of all, back up any saves you care about, with JKSV, DBI, or whatever you use. Do it now. If you aren't doing that regularly already, you probably should.
  2. Then, start from a clean OFW, update that to 20.x, let it call home once (just to appease the Ninjas, no need to link an account if you don't need to).
  3. Finally, create a new emuNAND from that, reinstall your stuff, and restore any saves you want to keep.
Everything else (airplane mode, turning wifi off, changing config settings...) are just workarounds, not a solution.


This is the «correct» solution. but only is possible if you have a CLEAN OFW if you do not have one you will be banned, also if you console is banned this solution might not work.
 
There are 14 setting to be changed. That's insane. I bet not all of them are necessary.
Perhaps somebody with the right equipment could test one by one to find out a minimal configuration.

The thing is I find that the 14 lines isn't enough I even used the background services one.
 
There are 14 setting to be changed. That's insane. I bet not all of them are necessary.
Perhaps somebody with the right equipment could test one by one to find out a minimal configuration.
Go ahead and try it, thanks for your work

and by the way for OLED consoles you need a lot more than 14 lines.
 
  • Like
Reactions: Blythe93
so whats the best Fw to stay on atm?? 12.0 atm but still setting it up.
You need the latest FW and a clean NAND for Online.
Other than that:
  • first, decide which games you want to play,
  • then, find out what's the minimum required FW version that lets you play all of those,
  • last, ensure all the homebrew you want to use is up-to date and supports that version,
and that will be the best FW version to stay at.
Without online, there's no sense in updating before some game you want requires it.

Also, 18.x and above have downsides:
  • Significantly less memory for homebrew (overlays, sysmodules, mods...)
  • Possible overheating/battery drain in sleep mode, that requires workarounds or a reformat/reinstall to fix.
So, stay on 18.x or below while you can.
 
It's been a long time since I've updated my cfw. What's a good one? v20.1.5? I'm getting my v1 switch ready for Pokemon. The only apps I really care about are cheats, and the ones to update. I also don't remember how to do it lol, what files and is there a tutorial. Also I don't care about online (well somewhat since I do use wireless controllers ). I also saw there's a fix for battery drain, how can I do that too
 
It's been a long time since I've updated my cfw. What's a good one? v20.1.5? I'm getting my v1 switch ready for Pokemon. The only apps I really care about are cheats, and the ones to update. I also don't remember how to do it lol, what files and is there a tutorial. Also I don't care about online (well somewhat since I do use wireless controllers ). I also saw there's a fix for battery drain, how can I do that too
https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148/
 
  • Like
Reactions: Blythe93
what about the apps?
Which Apps?

I don't remember the cheats overlay
This was handled by Tesla before, today tesla was replaced by Ultrahand.


Im confused about the battery drain fix.
You and almost all of us, in summary what I know is:
Big N put a new EULA on their firmware and you need to connect to ninja servers to accept it. but if you *NAND is isolated from N servers, your console never go to sleep and try to connect all times to that servers while on sleep, wasting your battery and keeping your console hot. there is only two ways to avoid that:
  • Starting over from a clean NAND which can be upgraded to FW20+ accept the new EULAS and then create a new EmuNAND copying it. but you need a clean no banned OFW for that.
  • putting a set of lines on the SDMC:/atmosphere/config/system_settings.ini file to avoid the console try to connect to network while on sleep.
 
Which Apps?


This was handled by Tesla before, today tesla was replaced by Ultrahand.



You and almost all of us, in summary what I know is:
Big N put a new EULA on their firmware and you need to connect to ninja servers to accept it. but if you *NAND is isolated from N servers, your console never go to sleep and try to connect all times to that servers while on sleep, wasting your battery and keeping your console hot. there is only two ways to avoid that:
  • Starting over from a clean NAND which can be upgraded to FW20+ accept the new EULAS and then create a new EmuNAND copying it. but you need a clean no banned OFW for that.
  • putting a set of lines on the SDMC:/atmosphere/config/system_settings.ini file to avoid the console try to connect to network while on sleep.
I don't remember all of them. But the one I can think of is the cfw c something app to update the cfw.

Ok so I'll add that and figure out how to turn it on mod game to see cheats and enable/disable them.

Oh yeah that. Well I do think I added the line in the setting file but since I'll be updating to 20 I I guess I'll make sure it's there so the system doesn't overheat (I'm not wanting to replace the battery since I rarely use it).

I messaged on the thread you linked. I need to refind that battery fix so can copy/paste it on the right section.
 
I have 2 dock, and 1 is connected to a tv that doesn't have sound output. Is there a a way to get a sound output from the tablet even if it's docked ?

I have the Samsung C24FG73 that doesn't have built-in speakers, only a jack for headphones.
 
I have 2 dock, and 1 is connected to a tv that doesn't have sound output. Is there a a way to get a sound output from the tablet even if it's docked ?

I have the Samsung C24FG73 that doesn't have built-in speakers, only a jack for headphones.
You're in a wrong thread for that kind of question.
But to answer your question, headphone jack (3.5mm) is a source of sound output.
 
  • Like
Reactions: impeeza
You're in a wrong thread for that kind of question.
But to answer your question, headphone jack (3.5mm) is a source of sound output.
not really wrong since there may be an ams settings I don't know or a related sys-plugin that work in background
 
I have 2 dock, and 1 is connected to a tv that doesn't have sound output. Is there a a way to get a sound output from the tablet even if it's docked ?

I have the Samsung C24FG73 that doesn't have built-in speakers, only a jack for headphones.
Several ways come to mind:
- The headphone jack on the console should still output audio, even while docked,
- A cheap HDMI extractor can get analog audio (or even digital, depends on the adapter) from the HDMI out,
- a USB audio card that supports UAC 1 or claims to be compatible with Switch should work with the USB ports of the dock.

However, for all those, you need wired active speakers (or earphones) and you might as well plug them into the jack on the TV.

Then, there's also
Bluetooth, but the audio might be a bit laggy.
 
  • Like
Reactions: Blythe93
Hello everyone!

First time poster and a fan of the community. Sort of regretting not joining sooner....

I took the plunge to try and update to 20.x and dove right into errors.

I'm getting the Error Code: 2162-0002 (0x4a2) Program 010000000000100C

I don't have any themes installed.

010000000000100 folder was no where to be found

My firmware is 17.0.0 and did a fresh install of:
- Atmo 1.9.5-master-de9b02007
- Hekate 6.3.1
- sig patches
- syspatch 1.5.6

I tried to revert back to my previous atmo and hekate version but am still getting the error.

My switch is able to boot into the stock nand but the it crashes when trying to load atmo on the emuMMC

My hekate ipl settings are:
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
noticker=0
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[CFW - emuMMC]
pkg3=atmosphere/package3
kip1patch=nosigchk
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

What did I do wrong :T...
Post automatically merged:

I tried to update my switch and failed.

I'm now receiving the
atmosphere error code 2162-0002 (0x4a2) 010000000000100c

I was not able to find any folder named 010000000000100 and removing the contents folder doesn't change anything.

My firmware version is 17.0.0

I did a fresh install of :
- atmosphere 1.9.5 from github (1.9.5-master-de9b02007)
- hekate 6.3.1 from github
- sig patches
- syspatch 1.5.6

My next step was to revert to my back up but that also failed and gave me the same error.

The switch is able to boot into the stock os

I use rcm to inject hekate so no mod chip is installed.

Here are my hekate ipl settings
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
noticker=0
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[CFW - emuMMC]
pkg3=atmosphere/package3
kip1patch=nosigchk
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

What did I do wrong :T...

Edit:
I saw the noob question section and have added this post there as well. I'd delete this post but I don't see the option to
 
Last edited by imp69,
Just discovering that this issue wasn't caused by my console's battery being too old or something lmao



But I see that some people need to have a clean nand ? Is that because their emunand was the clean one ? I don't really understand if I'm risking something right now. My emunand is dirty, my sysnand is clean (even tho I can sometimes boot atmosphere on it, but nothing too crazy besides save backups and menu themes, still not banned). What I understand is that booting into that sysnand with atmosphere and those things enabled is risky ? Usually I just update that sysnand officially (and my emunand with daybreak)
 
  • Like
Reactions: impeeza

Site & Scene News

Popular threads in this forum