Hacking Atmosphere to be estimated released in Summer 2018 for ALL firmwares.

[Ericthegreat]

Sounds like time is running out for Team Xecuter to put up or shut up.
Should be an interesting couple of months ahead.

Gotta remember might be a while till cfw gets "backup" loading, where as that's what the mod chip will be made for.

 

[Viri]

Since Nintendo seems to be in their "stability" phase when it comes to updates. I look forward to when Homebrew will be fully unlocked, and we can get a proper web browser, and when homebrew creators can bring Netflix to Switch before Nintendo does.

 

[TheCyberQuake]

Not yet I think. 5.0.0 is so new they haven't really had a chance to look into it yet, and obviously the devs aren't exactly eager to update in order to test things.
It will be easier once we have an emuNAND solution, then testing for exploits on newer firmware will be possible while keeping CFW access.

Testing on newer firmwares is already possible for devs because they have bootrom exploit. How do you think 5.0.0 data mining is happening? Its one of the reasons we know the changes so far in 5.0.0 including the added kaslr.

 

[mastermx]

So there's no reason for me to stay on 2.80?

I have had a copy of mario odyssey for a long time. Because it updates you to 3.1. But does this mean I can finally open up my copy of the game and enjoy it?!

 

[ehnoah]

Sad IS that he active block Backups no?

 

[whateverg1012]

SciresM and team are legends, can't believe we're getting a CFW this early.

 

[Onibi]

So there's no reason for me to stay on 2.80?

I have had a copy of mario odyssey for a long time. Because it updates you to 3.1. But does this mean I can finally open up my copy of the game and enjoy it?!

If they stay true to their word, no.
When in doubt ask them on discord. But answer will likely be: "go ahead".

I will do so myself.

 

[DarkCrudus]

Soooooon my paper weight of a 2nd switch will have use

 

[Deleted User]

That's a lot of replies and likes for something that was posted just over four hours ago. Most of OP's likes have come from this one post.

 

[V-Temp]

Not yet I think. 5.0.0 is so new they haven't really had a chance to look into it yet, and obviously the devs aren't exactly eager to update in order to test things.
It will be easier once we have an emuNAND solution, then testing for exploits on newer firmware will be possible while keeping CFW access.

Its already been tested and poked, and we know they fixed *nearly* everything already or made old methods of access completely broken, either by audit or by report or by both. The last few vestiges will not be released, maybe not even mentioned, because Mariko may potentially close all other entries into the system.

If Mariko makes hardware exploitation impossible, then every even small exploit left becomes extremely valuable because, otherwise, we potentially lose *all* access to Mariko-Switches.

 

[Onibi]

That's a lot of replies and likes for something that was posted just over four hours ago. Most of OP's likes have come from this one post.

View attachment 118984

Prestige farming Likes by proxy
Here you get one too

--------------------- MERGED ---------------------------

Its already been tested and poked, and we know they fixed *nearly* everything already or made old methods of access completely broken, either by audit or by report or by both.

Out of interest: What access is needed to pull of the bootrom bug from software? Kernel?

 

[Greymane]

Woop Woop, let the anticipation train begin.

 

[SexiestManAlive]

YES I STILLHAVE A CHANCE AT FREE CFW THANK THE LORD XD

 

[konamicode89]

If CFW is going to be released for all firmwares in the summer should I stay on 1.0? Maybe update to 3.0 to at least enjoy the homebrew menu until then? Wouldn't have to worry about grabbing that japanese hard copy of puyo puyo tetris for 1.0 if I updated to 3.0

Thoughts?

 

[The Real Jdbye]

Testing on newer firmwares is already possible for devs because they have bootrom exploit. How do you think 5.0.0 data mining is happening? Its one of the reasons we know the changes so far in 5.0.0 including the added kaslr.

Data mining is one thing, but that doesn't mean they're actually able to run the newer firmware, only that they were able to decrypt it.

Its already been tested and poked, and we know they fixed *nearly* everything already or made old methods of access completely broken, either by audit or by report or by both. The last few vestiges will not be released, maybe not even mentioned, because Mariko may potentially close all other entries into the system.

If Mariko makes hardware exploitation impossible, then every even small exploit left becomes extremely valuable because, otherwise, we potentially lose *all* access to Mariko-Switches.

That's true.
Although I doubt they will be able to fix every single flaw, there are probably some that haven't even been found yet. Just look at how long it took for sighax to be discovered on the 3DS. It could be years before another such exploit is found in the new hardware revision though.
It remains to be seen if this new hardware revision has more space for bootrom updates. Since on current Switches that space is all filled up and that makes it difficult, if not impossible to fix bootrom exploits.

 

[owek1]

damn, being in Australia means Summer is December for me here..

 

[MisterGoat]

Nice work!
So am i safe to update my 2.3.0 switch through Mario Odyssey? Or would it be stillt better to stay at 2.3.0?

 

[TheCyberQuake]

Sad IS that he active block Backups no?

He isn't actively blocking backups. But he probably won't be adding the necessary patches to allow backup loading. That will have to be done by someone else later, probably by forking the atmosphere-nx github.

 

[TheCyberQuake]

Nice work!
So am i safe to update my 2.3.0 switch through Mario Odyssey? Or would it be stillt better to stay at 2.3.0?

If you aren't on 1.0.0 and SciresM stays to his word, it should be fine to update to any firmware 4.1.0 or lower.

 

[MisterGoat]

If you aren't on 1.0.0 and SciresM stays to his word, it should be fine to update to any firmware 4.1.0 or lower.

Thanks mate!