Het is vandaag opnieuw “15 juni” en dat betekend dat Custom Firmware Atmosphère van SciresM een update heeft gekregen. Versie 0.8.3 is voorzien van enkele bugfixes en nieuwe features. De ontwikkelaar / hacker is vooral blij met een nieuwe functie die er voor zorgt dat je onmiddellijk herstart vanuit de atmosphere en vervolgens een payload injecteert zonder dat RCM mode geactiveerd moet worden.

Daarnaast werden de problemen opgelost die zich voordeden wanneer een console met een gedowngraded NAND uit standby modus kwam en werden de laatste Nintendo geëncrypteerde PK11 binary verwijderd. Met Content Override kan je nu alle applicaties overschrijven om de Homebrew Launcher te laden, in tegenstelling tot een specifieke titel.


Atmosphère is een gezamelijk project van SciresM, TuxSHhexkyz en fincs.

  • switchbrew
  • devkitPro
  • ReSwitched Team
  • ChaN
  • Marcus Geelnard
  • naehrwert en st4rk
  • CTCaer
  • Riley
  • Hedgeberg
  • lioncash
  • jaames
Changelog 0.8.3:

0.8.3 is Atmosphère’s tenth official release.

fusee-primary was last updated in: 0.8.3.

The following was changed since the last release:

  • A custom warmboot firmware was implemented, which does not perform anti-downgrade fuse checks.
    • This fixes sleep mode when using a downgraded NAND.
    • This also removes Atmosphère’s final dependency on Nintendo’s encrypted PK11 binary; all components are now re-implemented.
  • The ExternalContentSource API was changed to not clear on failure.
  • Content override now supports an “app” setting, that causes all applications to be overridden with HBL instead of a specific title.
    • Note: because override keys are system-wide, using this setting will prevent using mods in games (as every game will be HBL).
  • A bug was fixed causing incorrect fatal-error output when svcBreak was called on 5.0.0+.
  • An extension was added to set.mitm to support customization of system settings.
    • These are controlled by atmosphere/system_settings.ini, see herefor documentation.
    • By default, this is used to disable error report uploading, and enable USB 3.0 superspeed when possible.
  • An extension was added to sm, adding a new sm:dmnt service.
    • This can be used by a debug monitor in order to debug the registration state of various other services.
  • A bug was fixed in the MitM API that could sometimes cause a system hang during boot.
  • A change was made to the MitM API: in cases where sm would have returned 0xE15 when installing a mitm service, it now defers the result (following GetService semantics).
  • Support for booting into maintenance mode by holding */- was added to PM.
  • An extension was added to exosphere, adding a custom SMC that allows for DMA to IRAM.
  • In addition, smcGetConfig was extended to reboot to a payload in IRAM at 0x40010000 when ConfigItem 65001 is set to 2.
    • Fatal will now use this to reboot to sdmc:/atmosphere/reboot_payload.bin if present, when a vol button is pressed.
    • An example homebrew (“reboot_to_payload”) was also written and is now included with Atmosphère.
  • General system stability improvements to enhance the user’s experience.

For information on the featureset supported by 0.8.0, please see the official release notes.

Changelog 0.8.2:

0.8.2 is Atmosphère’s ninth official release.

fusee-primary was last updated in: 0.8.2.

The following was changed since the last release:

  • A number of bugs were fixed causing users to sometimes see Key Derivation Failed!.
    • KFUSE clock enable timings have been adjusted to allow time to stabilize before TSEC is granted access.
    • A race condition was fixed that could cause wrong key data to be used on 6.2.0
    • The TSEC firmware is now retried on failure, fixing a failure affecting ~1/50 boots on 6.2.0.
  • A bug was fixed causing some modules to not work on firmware 1.0.0.
  • A bug was fixed causing sleep mode to not work with debugmode enabled.
    • As a result, debugmode is now enabled in the default BCT.ini.
  • General system stability improvements to enhance the user’s experience.

For information on the featureset supported by 0.8.0, please see the official release notes.

Changelog 0.8.1:
  • A bug was fixed causing users to see Failed to enable SMMU! if fusee had previously rebooted.
    • This message will still occur sporadically if fusee is not launched from coldboot, but it can never happen twice in a row.
  • A race condition was fixed in Atmosphere bis_protect functionality that could cause NS to be able to overwrite BCT public keys.
    • This sometimes broke AutoRCM protection, the current fix has been tested on hardware and verified to work.
  • Support was added for enabling debugmode based on the exosphere section of BCT.ini:
    • Setting debugmode = 1 will cause exosphere to tell the kernel that debugmode is active.
    • Setting debugmode_user = 1 will cause exosphere to tell userland that debugmode is active.
    • These are completely independent of one another, allowing fine control of system behavior.
  • Support was added for nogc functionality; thanks to @rajkosto for the patches.
    • By default, nogc patches will automatically apply if the user is booting into 4.0.0+ with fuses from <= 3.0.2.
    • Users can override this functionality via the nogc entry in the stratosphere section of BCT.ini:
      • Setting nogc = 1 will force enable nogc patches.
      • Setting nogc = 0 will force disable nogc patches.
    • If patches are enabled but not found for the booting system, a fatal error will be thrown.
      • This should prevent running FS without nogc patches after updating to an unsupported system version.
  • An extension was added to exosphere allowing userland applications to cause the system to reboot into RCM:
    • This is done by calling smcSetConfig(id=65001, value=<nonzero>); user homebrew can use splSetConfig for this.
  • On fatal error, the user can now choose to perform a standard reboot via the power button, or a reboot into RCM via either volume button.
  • A custom message was added to fatal for when an Atmosphère API version mismatch is detected (2495-1623).
  • General system stability improvements to enhance the user’s experience.
Changelog 0.8.0:
  • Support for firmware 6.2.0 with automatic system key generation. Special thanks to motezazer
  • A custom ‘fatal’ system module was created which displays a custom error screen giving the user information about registers and a backtrace
  • Some partitions like BOOT0 now have basic protections applied to them
    • This stops malicious homebrew from messing with such partitions
    • However, this doesn’t mean that you can now install everything you can get your hands on as malicious homebrew can still find ways to bypass this protection
  • HDCP titles running on newer firmwares no longer crash
  • Numerous other more technical improvements such as disabling smhax

Hulp nodig of een vraag voor ons team? Join onze Discord community: