![[EXCLU] PlayStation Retro pour votre PS2](https://www.modconsoles.fr/uploads/monthly_2020_06/opl.jpg.e93e81ce45e8ecc0a94ba44064d4c721.jpg)
Le CFW libre et gratuit Atmosphère prend son envol en étant le premier cfw de la Switch à supporté le dernier firmware "majeure" et "dangereuse" de la Switch. 2 semaines pour que le firmware soit cracké et même pas une semaine que le premier cfw fait sa sortie et supporte pleinement cette version de firmware mais ce n'est pas tout. Le cfw Atmosphère apporte aussi son lot de nouveautés quand peut lire ci-dessous :
Citation
- A custom fatal system module was added.
- This re-implements and extends Nintendo's fatal module, with the following features:
- Atmosphère's fatal does not create error reports.
- Atmosphère's fatal draws a custom error screen, showing registers and a backtrace.
- Atmosphère's fatal attempts to gather debugging info for all crashes, and not just ones that include info.
- Atmosphère's fatal will attempt saving reports to the SD, if a crash report was not generated by creport.
- Title flag handling was changed to prevent folder clutter.
- Instead of living in atmosphere/titles/<tid>/%s.flag, flags are now located in atmosphere/titles/<tid>/flags/%s.flag
- The old format will continue to be supported for some time, but is deprecated.
- Flags can now be applied to HBL by placing them at atmosphere/flags/hbl_%s.flag.
- Changes were made to the mitm API, greatly improving caller semantics.
- sm now informs mitm services of a new session's process id, enabling custom handling based on title id/process id.
- smhax is no longer enabled, because it is no longer needed and breaks significant functionality.
- Users with updated HBL/homebrew should see no observable differences due to this change.
- Functionality was added implementing basic protections for NAND from userland homebrew:
- BOOT0 now has write protection for the BCT public key and keyblob regions.
- The ns sysmodule is no longer allowed to write the BCT public keys; all other processes can.
- This should prevent system updates from removing AutoRCM.
- No processes should be allowed to write to the keyblob region.
- By default, BIS partitions other than BOOT0 are now read-only, and CAL0 is neither readable nor writable.
- Adding a bis_write flag for a title will allow it to write to BIS.
- Adding a cal_read flag for a title will allow it to read CAL0.
- An automatic backup is now made of CAL0 on boot.
- fs.mitm maintains a file handle to this backup, so userland software cannot read it.
- To facilitate this, fs.mitm now mitms all sessions for non-system modules; content overriding has been made separate from service interception.
- Please note: these protections are basic, and sufficiently malicious homebrew can defeat them.
- Please be careful to only run homebrew software from sources that you trust.
- A bug involving HDCP titles crashing on newer firmwares was fixed.
- Support was added for system version 6.2.0; our thanks to @motezazer for his invaluable help.
- By default, new keys will automatically be derived without user input.
- Support is also present for loading new keys from atmosphere/prod.keys or atmosphere/dev.keys
- General system stability improvements to enhance the user's experience.
MAJ : v0.8.1
Citation
- 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 stratosphere 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.
MAJ : v0.8.2
CitationThe 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.
Dû au changement qu'apporte le firmware 6.2 sur la génération des clés, les cfw qui vont suivre changeront de manière de fonctionnement et il sera plus possible me mettre à jour son firmware avec ChoixDuJourNX ou autre outil d'installation de fichier de mise à jour jusqu'à voir une nouvelle version de ces dites homebrews.
Un grand merci de la part motezazer pour avoir apporté le support du firmware 6.2 sur le cfw.
Un nouveau module pour les codes erreurs a été introduit et il ne créera plus de rapports d'erreur mais affichera une écran d'erreur personnalisé, affichant des registres et une trace et tentera de sauvegarder les rapports sur la SD si aucun rapport d'incident n'a été généré.
Source et téléchargement
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now