Recent content by PHiLiPZ

  1. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    I understand all of that. And exactly due to lack of new bugs and commits and the information “1.5.4 will transition to release after a short(!!!) amount of time has passed without pressing bug reports” I’m surprised it wasn’t released yet.
  2. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    Thanks for the reply but that doesn’t explain the very long pre-release phase. If there are no bugs why not properly release it? Without version bump.
  3. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    Any reason why 1.5.4 is still in pre-release? Usually the releases are “promoted” in a few days. Any known issues?
  4. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    New Atmosphere works with old OFW. New OFW often breaks old Atmosphere. So definitely update Atmosphere first.
  5. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    That support was improved for 14.0.0+ does not mean, that 14.1.1 is supported. Previous Atmosphere release specifically mentions support for 14.1.0 but 14.1.1 I have not seen mentioned anywhere. So from my point it was a valid question, definitely better than excuses that brother/dog/offspring...
  6. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    https://github.com/Atmosphere-NX/Atmosphere/issues/1797#issue-1176119072 https://github.com/Atmosphere-NX/Atmosphere/issues/1797#issuecomment-1075961444 Nice work done on FW14 support. Thank you SciresM
  7. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    If you’re very unlucky, starting from scratch means starting with buying a new console. Making backup after the Switxh now longer boots is pretty much useless. If you have your keys extracted you might be able to save it by recreating the system partition.
  8. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    There are no two Switches with the same serial number.
  9. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    Just you. In releases it says for release 1.2.1, that it added support for 13.1.0. And newer one still support it.
  10. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    Hm, it’s 13.1.0 (not 13.0.1 like someone above wrote) so the changes are probably bigger.
  11. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    According to the changelog of Atmosphere 1.2.0 the “target firmware” checking changed, which should “improve our compatibility with micro firmware releases, making it more likely that atmosphere "just works" if nothing important has changed”. So maybe current Atmosphere works also with firmware...
  12. P

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

    Atmosphere 1.0.0 doesn’t support AMS FW 13
  13. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    Python scripts can be compiled to binary executables as well. Maybe that’d be easier for some than installing the Python interpreter.
  14. P

    Hacking Atmosphere-NX - Custom Firmware in development by SciresM

    It’s been a week since the last release (aka June 15th). Writing such posts makes it seem, as if there was a new release, which is confusing. It’s like saying “happy Birthday” to someone two months after the birthday. Keep your “happy June 15th” posts for the day of the next release please.
  15. P

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

    Never had issues before after following all the steps and didn’t have them now either. People who can read and wait at least two days after a release should not worry. It’s always been either installing fw update before Atmosphere was updated, using wrong patches or not cleaning the installation...
See more