Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,738,101
  • Replies Replies 9,278
  • Likes Likes 92
just want to ask question, its been a year since switch release, i just want to ask whats the most common firmware im going to get if i bought a switch today? thanks...
All current fw have a Exploit already coming soon so might as well get one now and do the dns trick to block a 5.0 update
 
  • Like
Reactions: noctis90210
Is it still safe to sit on my 2.0 firmware (can always upgrade to 3.0 with a game title) or should I update to 4.1.0 immediately before this is patched?
 
Ahh, I hadn't planned on making a thread about this.

Anyway, yes, my focus will be shifting towards spending all my time working on Atmosphere until it's usable (with a diversion to get a publically usable jamais vu PoC once some of the basic building blocks are in place).

I've put up a roadmap in the issues/projects section -- all of my development will be open source and done via commits to that repo. I don't want a repeat of previous consoles where CFWs get worked on behind closed doors before their initial releases -- all of atmosphere's broken, WIP code will be available as it's written.

Looking forward to working on atmosphere :)

So I have a question about the way you're handling making everything public as you're developing it; What's about the possibilities of Nintendo keeping an eye on your progress and they try patching it as you develop it?
 
@SciresM

I know you talked about emunand a few months back, but I wonder, does this cfw solution you are working on involve an emunand, or a direct sysnand approach?

Either way, thanks for the effort :)
 
Tell that to the ISP.

I would say more like paying for your internet twice, I have always had a bad taste in my mouth with paid online gaming services as such. I already pay for the internet, shouldn't have to pay for the online service to play with my friends if I can't go to their house.
 
Not like it really matters, online is becoming paid soon and you should never pay for online
Bans happened on the 3ds because of cias if you spoofed the home brew apps as an app on the 3ds you would be fine.

--------------------- MERGED ---------------------------
 
So I have a question about the way you're handling making everything public as you're developing it; What's about the possibilities of Nintendo keeping an eye on your progress and they try patching it as you develop it?

This is not exploit code, there's nothing to patch.

@SciresM

I know you talked about emunand a few months back, but I wonder, does this cfw solution you are working on involve an emunand, or a direct sysnand approach?

Either way, thanks for the effort :)

See: https://github.com/SciresM/Atmosphere-NX/projects/3

In general, if you want to know what kinds of stuff I'm aiming to get into Atmosphère, see: https://github.com/SciresM/Atmosphere-NX/projects
 
See: https://github.com/SciresM/Atmosphere-NX/projects/3

In general, if you want to know what kinds of stuff I'm aiming to get into Atmosphère, see: https://github.com/SciresM/Atmosphere-NX/projects
Perfect, I'll give than an extensive lead. Thanks for sharing the overall plan. I personally was hoping for an emunand approach, regardless of whether sysnand is possible or not.

2 more questions if I may:

- With emunand, I assume you could technically get that up to the latest fw. With sysnand on a lower fw, how would the fuse checks work? Do you plan on skipping them entirely? Or do you have something else in mind?

- Is coldboot in the scope of this? Or that would be a separate project?

Thanks again :)
 
Perfect, I'll give than an extensive lead. Thanks for sharing the overall plan. I personally was hoping for an emunand approach, regardless of whether sysnand is possible or not.

2 more questions if I may:

- With emunand, I assume you could technically get that up to the latest fw. With sysnand on a lower fw, how would the fuse checks work? Do you plan on skipping them entirely? Or do you have something else in mind?

- Is coldboot in the scope of this? Or that would be a separate project?

Thanks again :)

Fuse checks are irrelevant -- they are checked only in package1loader, which should never execute once the system has booted.

Atmosphere will always simulate a coldboot, regardless of how it is launched -- and thus it should work with any coldboot exploits.
 
Fuse checks are irrelevant -- they are checked only in package1loader, which should never execute once the system has booted.

Atmosphere will always simulate a coldboot, regardless of how it is launched -- and thus it should work with any coldboot exploits.
Thanks for the clarifications. Good luck on the project development:)
 

Site & Scene News

Popular threads in this forum