Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,740,133
  • Replies Replies 9,279
  • Likes Likes 92
Did anybody who fixed the abnormal battery drain via rebuilding their NAND or creating a new user have the issue return after upgrading their firmware?

Or is it likely to be gone for good once you've fixed it? Could anyone confirm that the problem did not return after a firmware upgrade? Thanks!
 
Last edited by XenoFredo,
Did anybody who fixed the abnormal battery drain via rebuilding their NAND or creating a new user have the issue return after upgrading their firmware?

Or is it likely to be gone for good once you've fixed it? Could anyone confirm that the problem did not return after a firmware upgrade? Thanks!
FWIW, replacing the user with an unlinked one on emuNAND did not fix the drain for me, see here.

Ended up upgrading sysNAND to 20.2.0 to delete the linked user the official way, creating new unlinked user in sysNAND, and then creating a new emuNAND from that. No unusual drain so far.
 
FWIW, replacing the user with an unlinked one on emuNAND did not fix the drain for me, see here.

Ended up upgrading sysNAND to 20.2.0 to delete the linked user the official way, creating new unlinked user in sysNAND, and then creating a new emuNAND from that. No unusual drain so far.
I created the new EmuNAND from firmware 20.1.1 and it indeed fixed the battery drain issue for me, even with a linked user.

But now I haven't updated to one of the higher firmwares because I'm wondering if it could make the issue return. I'd like to avoid going through making a new EmuNAND again.

Edit: I updated to 20.2.0 myself and the battery drain did not return on my two V1 Switches.
 
Last edited by XenoFredo,
  • Like
Reactions: THYPLEX and impeeza
Okay, what gives? I just updated from OFW 19.0.1 to 20.3.0 after also updating Atmosphere to 1.9.3.

Everything worked upfront, and loads correctly. But when I go to navigate through my games, the icons load VERY slowly, and selecting any game results in a generic "Failed to open Software" message. These were games that already worked on 19.0.1.

These are the steps I followed. Can someone please tell me what I missed? Please note that I do not use Hekate, and I keep my Switch on Airplane mode, so I didn't mess with any ini files.

(I did notice that there's no longer a dedicated sigpatches folder in the sigpacthes update zip, which I found on the sigpacthes thread here.)

- Plug SD card into PC.
- Delete the following atmosphere folders:
- contents (or titles)
- crash_reports
- erpt_reports
- fatal_reports

- Extract new atmosphere folder contents to SD card root.
- Copy sigpatches folder contents to root of SD, overwrite all duplicates.
- Create folder for firmware, copy over the extracted files.

- Plug in USB Dongle.
- Replace the "fusee.bin" file both on SD and USB Dongle.
- On the Dongle, you may need to rename the file to match the file name in the other folders.
- Eject SD and Dongle.

- Insert SD and Dongle onto Switch, power on.
- If everything looks ok, launch the Homebrew Loader and run Daybreak.
- Choose "FAT32 + exFAT, "Preserve Settings".
- After installation and reboot, check System Settings for updated FW.
 
Okay, what gives? I just updated from OFW 19.0.1 to 20.3.0 after also updating Atmosphere to 1.9.3.

Everything worked upfront, and loads correctly. But when I go to navigate through my games, the icons load VERY slowly, and selecting any game results in a generic "Failed to open Software" message. These were games that already worked on 19.0.1.

These are the steps I followed. Can someone please tell me what I missed? Please note that I do not use Hekate, and I keep my Switch on Airplane mode, so I didn't mess with any ini files.

(I did notice that there's no longer a dedicated sigpatches folder in the sigpacthes update zip, which I found on the sigpacthes thread here.)

- Plug SD card into PC.
- Delete the following atmosphere folders:
- contents (or titles)
- crash_reports
- erpt_reports
- fatal_reports

- Extract new atmosphere folder contents to SD card root.
- Copy sigpatches folder contents to root of SD, overwrite all duplicates.
- Create folder for firmware, copy over the extracted files.

- Plug in USB Dongle.
- Replace the "fusee.bin" file both on SD and USB Dongle.
- On the Dongle, you may need to rename the file to match the file name in the other folders.
- Eject SD and Dongle.

- Insert SD and Dongle onto Switch, power on.
- If everything looks ok, launch the Homebrew Loader and run Daybreak.
- Choose "FAT32 + exFAT, "Preserve Settings".
- After installation and reboot, check System Settings for updated FW.
You should install latest Sys-patch. Sigpatches doesn't work fully with fusee.bin anymore
 
not really related, but do you know if hekate still work fine or not ?
Wondering cuz I see it hasn't been updated yet.
 
  • Like
Reactions: Blythe93
Is it worth update atmosphere to 1.9.3 even with emuNAND in FW 19.1?

Which files i have to review?
- update atmosphere and hekate files of course
- update fusee payload
- update sys-patch 1.5.6?
- may i turn off custom theme?
- will I have any lack or mistakes respect the system as I have today (1.9 and 19.1)
- may I delete config files for regenerate as new one?
- is it worth to use AIO update app to update atmosphere and hekate files?

I don’t want to update emuNAND but I would like to boot in sysNAND to copy save games and took the last advances in my games to copy that in emuNAND
 

Site & Scene News

Popular threads in this forum