Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,306,580
  • Replies Replies 7,368
  • Likes Likes 266
@impeeza As usual, thanks for your multitude of contributions. just upgraded to 20.4.0 and followed your various pieces of advice here and there to ensure the uplift of atmosphere, syspatch and sigpatches were prepared accordingly. The most complicated was actually digging up your valuable posts (including your upgrade guide that should really be pinned to the very top of the switch section...). Again, thanks!

by the way, I remember coming across a post of yours helping out a community member to minimise battery drainage while device is asleep (you included config file content in that regards). Cannot find this >.<
 
@impeeza As usual, thanks for your multitude of contributions. just upgraded to 20.4.0 and followed your various pieces of advice here and there to ensure the uplift of atmosphere, syspatch and sigpatches were prepared accordingly. The most complicated was actually digging up your valuable posts (including your upgrade guide that should really be pinned to the very top of the switch section...). Again, thanks!

by the way, I remember coming across a post of yours helping out a community member to minimise battery drainage while device is asleep (you included config file content in that regards). Cannot find this >.<

https://gbatemp.net/threads/atmosph...pports-switch-ofw-20-4-0.674925/post-10725874
Post automatically merged:

Be aware some posts later there are another staggering the lines needed for OLED
 
Last edited by impeeza,
  • Like
Reactions: Blythe93
Will this config affect anything noticable except better battery life?
For me the only caveat is the USB Ethernet sometimes do not get connected until I remove the console from the dock and put again. But I do not use too many network features

UPDATE: It turned out that my USB adapter have a faulty USB cable!!
was a coincidence what when I upgraded to 20.5.0 I moved the setup and the cable got a different position, and taking out and in the console to the dock moved the cable enough to work, I just Replaced the USB cable of the adapter and now the connection works always even with all lines added!

Sorry for the confusion.
 
Last edited by impeeza,
if my stock firmware is 20.4.0, is downgrading an option? I feel like 20.4.0 is not stable
No, if you downgrade to any firmware lower than 20.0.0. your user partition become unusable.

Feels are not evidence, what are your problems?
 
Last edited by impeeza,
No, if you downgrade to any firmware lower than 20.0.0. your user partition become unusable.

Feels are not evidence, what are your problems?
Half my games dont launch with "The software was closed because an error occured", I know for a fact some of the .NSP file is good, which points to some other issue. I have crash reports but I'm not sure how readable they are
 
Half my games dont launch with "The software was closed because an error occured", I know for a fact some of the .NSP file is good, which points to some other issue. I have crash reports but I'm not sure how readable they are
Which Sys-Patch Sysmodule version do you have?
 
For me the only caveat is the USB Ethernet sometimes do not get connected until I remove the console from the dock and put again. But I do not use too many network features
This doesn't compute (I don't understand). If you have a dock (which most people do, unless you bought a lite), then what's the USB ethernet for? The dock already has ethernet...
 
This doesn't compute (I don't understand). If you have a dock (which most people do, unless you bought a lite), then what's the USB ethernet for? The dock already has ethernet...
No the old ones, My console is a Unpatched one and that docks do not have Ethernet embedded.
 
Half my games dont launch with "The software was closed because an error occured", I know for a fact some of the .NSP file is good, which points to some other issue. I have crash reports but I'm not sure how readable they are
Try disabling SaltyNX if you're using it, or upgrading it.
 
  • Like
Reactions: laz305 and impeeza
Half my games dont launch with "The software was closed because an error occured", I know for a fact some of the .NSP file is good, which points to some other issue. I have crash reports but I'm not sure how readable they are

Disable your sysmodules
 
NO THAT IS JOB OF ATMOSPHÈRE.
for those who care, fuses don't burn on updating, they burn on boot. you will still burn fuses if you boot without rcm, even if you updated while on atmosphere. the best way to avoid burning fuses is auto rcm to prevent ever using the official bootloader, then you only use fusée for atmosphere or hekate if you need to boot 'stock'

updating while on ofw might also burn fuses on update, even if you immediately reboot into rcm afterwards, but point is just because you updated while on atmosphere doesnt mean you're safe to do whatever you want and not burn fuses later. original nintendo bootloader will check the firmware version and burn fuses to match if the fuse count is lower

with modchip is probably different but I dont know modchips
 
  • Like
Reactions: laz305

Site & Scene News

Popular threads in this forum