Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[ZachyCatGames]

Okay thanks. but still inconvenient. I don't get it. At least there should be an option to make it like it was before.
Haven't updated yet.

It's done to break updating atmosphere while the system is running.
And it will not be reverted.

 

[linuxares]

It's done to break updating atmosphere while the system is running.
And it will not be reverted.

I still wonder why the reason for it is. It always been the solution just to delete Atmosphere and Sept folders if someone is breaking and replace them with new once.

So it's baffling why they've done this.

 

[ZachyCatGames]

I still wonder why the reason for it is. It always been the solution just to delete Atmosphere and Sept folders if someone is breaking and replace them with new once.

So it's baffling why they've done this.

He did it because users shouldn't be messing with those files while the system is running. Just use hekate UMS.

 

[linuxares]

He did it because users shouldn't be messing with those files while the system is running. Just use hekate UMS.

Why not let people decide, give them an opt-out feature? I just don't get the elitism of "Nope, my way or the highway" of late with Atmosphere :/

Heck I don't see anything about full lockdown in the changelog either. I don't even know how easy/hard it will be to update cheats now. I guess we got to ask @WerWolv if Edizon can look in a new folder and "redirect" it to Atmosphere.

 

[ZachyCatGames]

Heck I don't see anything about full lockdown in the changelog either. I don't even know how easy/hard it will be to update cheats now. I guess we got to ask @WerWolv if Edizon can look in a new folder and "redirect" it to Atmosphere.

This doesn't impact that at all.
It only blocks fucking with sd:/atmosphere/fusee-secondary.bin and sd:/sept/payload.bin

 

[linuxares]

This doesn't impact that at all.
It only blocks fucking with sd:/atmosphere/fusee-secondary.bin and sd:/sept/payload.bin

Ah I see... It sounded like it blocked everything with Atmosphere

 

[1basti1]

This doesn't impact that at all.
It only blocks fucking with sd:/atmosphere/fusee-secondary.bin and sd:/sept/payload.bin

You sure? I've read otherwise. For example, Sigpatches can't be copied with ftp. The Switch must be turned off.

As I said, I did not update yet. I don't have to do it yet...

 

[ZachyCatGames]

You sure? I've read otherwise. For example, Sigpatches can't be copied with ftp. The Switch must be turned off.

As I said, I did not update yet. I don't have to do it yet...

There was briefly a "bug" that caused some shit to not be able to touch it at all. But that was fixed in a silent update.
https://github.com/Atmosphere-NX/Atmosphere/commit/1c71d12d9da5a4602e12b084394518fb7cecc011
I personally have copied over mods using nxmtp while the system was running and had absolutely no issues

 

[ScottNBNP]

Updated recently, and can't launch any homebrew from the switch's menu. I can get into the HBMenu by going into Gallery, but my forwarders i guess you would call em don't load, Tinfoil, GTA3 and most importantly the Mario decompiled NSP

However games load and play fine? What did i break haha.

 

[duckbill007]

I personally have copied over mods using nxmtp while the system was running and had absolutely no issues

I even replaced whole atmosphere folders while updating to new version via mtp and reboot to apply changes. All works just fine!

 

[LyuboA]

i saw theres a new build of AMS 0.15.0 to fix the issue with ftp cant access the atmosphere folder atleast thats what says into atmosphere notes but it dosnt fix anything i still dont have access to atmosphere folder from ftp

 

[LyuboA]

deleted

 

[annson24]

Edit: just great why not locked it down completely like SXOS he said new build should allow access to read only but it dosnt even work for that too

Why not post an issue from their github rather than whining here?

Sent from my SM-N975F using Tapatalk

 

[LyuboA]

Why not post an issue from their github rather than whining here?

Sent from my SM-N975F using Tapatalk

no point in that ppl already spoke to him and he wont change it and i already figured it out theres is a way

 

[peteruk]

I just wanted to feed back that since swapping over to mesosphere experimental that my Switch seems a lot more snappy (responsive) than it did previously. I wasn't looking for it but it's real so I don't think I'm imagining it.

I changed nothing else, so it has to be that. Either way I'm happy.... thanks to SciresM and the team for the continued goodness.

 

[alba93]

few news regarding Mariko's support

Still a lot of work to do before it's ready for non-development use (fatal errors are broken, shut down/reboot are broken, reboot to payload doesn't work...), but (This uses modchip cfw/drm bypass, mariko still does not (and likely never will) have softwarehax).

For testing/development I am using a custom firmware/drm bypass for the gateway modchip, since no open/reversed solution exists.

 

[alba93]

a new update is coming soon

This is a really large update under the hood, so please give atmosphere a day or two to get updated with support.

I'll be working my hardest/doing my best

 

[BaamAlex]

a new update is coming soon

We know

 

[alba93]

## 0.16.0 changelog

+ Support was added for 11.0.0.
+ `exosphère` was updated to reflect the latest official secure monitor behavior.
+ `mesosphère` was updated to reflect the latest official kernel behavior.
+ `loader`, `sm`, `boot`, `pgl` were updated to reflect the latest official behaviors.
+ **Please Note**: 11.0.0 implements an opt-in version of the atmosphère `sm` extension that allows for closing session without unregistering services.
+ Correspondingly, the extension will be deprecated in favor of the new official opt-in command. In 0.17.0, it will be removed entirely.
+ If your custom system module relies on this extension (however unlikely that seems to me), please update it accordingly.
+ `erpt` was partially updated to provide compatibility with 11.0.0.
+ The latest firmware attaches additional fields and context information to logs.
+ A future atmosphère update will implement this logic, so that users who are interested can also get the new information when examining their logs.
+ The `boot` system module was rewritten to reflect the huge driver changes introduced in 8.0.0.
+ This includes a number of improvements to both logo display and battery management logic.
+ Support was added for configuring the address space width for `hbl`.
+ The `hbl_config!override_address_space_(#)` and `hbl_config!override_any_app_address_space` can now be set to `39_bit`, `36_bit`, or `32_bit` to control the address space for hbl on a per-override basis.
+ If a configuration has not been set, hbl will now default to 39-bit address space.
+ Previously, a legacy 36-bit address space was always used to maintain compatibility with 1.0.0.
+ A new loader extension was added to support 39-bit whenever possible (including mesosphere-on-1.0.0), with fallback to 36-bit when unavailable.
+ Support was added to a number of components for running on Mariko hardware.
+ The `boot` system module can now safely be run on mariko hardware, performing correct hardware initialization.
+ Daybreak (and generally, system update logic) were updated to be usable on Mariko.
+ Boot0 protection/management logic was updated to perform correct actions on Mariko.
+ Reboot to payload does not and cannot work on Mariko. Correspondingly, A "fatal error" handler was written, to display and save fatal errors from within TrustZone.
+ **Please Note:** Atmosphere is still not properly usable on Mariko hardware.
+ In particular, wake-from-sleep will not properly function (the magic numbers aren't set correctly), among a few other minor issues.
+ `exosphère` received support for building under debug configuration.
+ A small (otherwise unused) portion of IRAM is now reserved for debug-only exosphere code (this region is unused/untouched under release config).
+ This enables logging (including printf) to uart from the secure monitor, for those interested.
+ A number of bugs were fixed, including:
+ Minor issues in a number of filesystem related code were fixed.
+ An issue was fixed that could cause NCM to abort on consoles which came with 3.0.x and were never updated.
+ Several issues were fixed, and usability and stability were improved.

 

[SciresM]

Happy June 15th(-prerelease)!