Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,779,595
  • Replies Replies 9,372
  • Likes Likes 93
@SciresM Now that it seems that atmosphere has been loaded successfully in 3.0.0 I am curious to know how to launch hbl inside it? atmosphere once loaded is able to read files directly nro ?? How do you access the homebrew inside what looks like the original operating system? should the programs appear in the main gallery? Could you clarify that a bit? thank you for your work is spectacular
 
@SciresM Now that it seems that atmosphere has been loaded successfully in 3.0.0 I am curious to know how to launch hbl inside it? atmosphere once loaded is able to read files directly nro ?? How do you access the homebrew inside what looks like the original operating system? should the programs appear in the main gallery? Could you clarify that a bit? thank you for your work is spectacular

Atmosphere isn't actually bootable yet via fusee.

What people have been booting with Hekate *is atmosphere* -- stuff will work the same way it does when you do that.
 
https://github.com/Atmosphere-NX/Atmosphere/commit/0f6d4baa8e3a5303b112dfdc568ed8488f2e3888

#ifdef I_KNOW_WHAT_IM_DOING_2

Inspires confidence!

Edit: I see the context in the file is to do with whether you want a particular build to load pkg2 from eMMC as opposed to SD in most other cases. So I take it back in a sense. Just struck me as unnerving when I first saw it.

Do not load package2 from eMMC, dump it with hekate then crop the file (start at offset 0x4000)
then like the code say just add something like this in your BCT.ini
[stage2]
package2 = package2.bin
 
Atmosphere isn't actually bootable yet via fusee.

What people have been booting with Hekate *is atmosphere* -- stuff will work the same way it does when you do that.
So what you're saying is that while people have already gotten hello world apps working on your firmware, they'll still work when it's released in a few months! Great! TX officially wrecked!

Edit:
I mean, once you've caught that shiny, sorry didn't mean any dis
 
Last edited by BryanNigson,
Atmosphere shouldn't be released until fusee gelee has at least a software warmboot exploit doesn't require Jigs/tethers IMO
 
Atmosphere shouldn't be released until fusee gelee has at least a software warmboot exploit doesn't require Jigs/tethers IMO

So... for nearly no one?

They're not going to release deja-vu until they know if it works or not on Mariko because its all that we really have left at this current moment. Without deja-vu almost no one will be able to do coldboots without jigs and a tethered payload.
 
Last edited by V-Temp,
Because CFW totally equals a tethered payload launcher. SX will end up just like everything that came before proper CFW. Dead.
You do realize that if/when coldboot CFW comes, SX can adapt, right?
 
You do realize that if/when coldboot CFW comes, SX can adapt, right?

Even if they do, then what? No one is going to pay for it when there is a fully featured, free option available.

Gateway dropped sales hard when the 3DS got full homebrew.
As did Sky.
As did many others for many other consoles.
 
  • Like
Reactions: Milad
Even if they do, then what? No one is going to pay for it when there is a fully featured, free option available.

Gateway dropped sales hard when the 3DS got full homebrew.
As did Sky.
As did many others for many other consoles.

I dont have a SX OS yet, but with how convenient it is, im probably gonna stick with it until something as easy/confortable to use gets released.

Im sure Atmos would get to that point eventually, bu for now, TX is the way to go for piracy.
 
But SX OS will not implement any custom modules loading so if you want a backend to browse game memory or anythings else that must be run as background worker you can't.

Therefore open source CFW will even be useful for casuals users
 
I'm honestly extremely curious how TX is going to handle the Mariko units. Once they're out in the wild, they definitely have to provide some sort of update in regards to their product. They probably will try to find another entry point but whether its a coldboot or warmboot is left to speculation.
 
I hope mariko helps improve the old Switch, like after RCM most ppl won't probably bother trying to find better way to hack it, instead most likely they make apps, CFW and adding stuff.

With the new Mariko hackers will again start looking for new exploits, hope they could get a way to coldboot on it that would also work on all old Switches regardless of FW until the date of release at least.
 
Even if they do, then what? No one is going to pay for it when there is a fully featured, free option available.

Gateway dropped sales hard when the 3DS got full homebrew.
As did Sky.
As did many others for many other consoles.
Gateway dropped because their support was absolute shit from the get go. Sky was just a 1:1 card clone. You can use SX OS for free. You just lose backups until you buy a license.. I'm not saying SX is the definitive answer here.. But your comparison just doesn't work.
 
Atmosphere is in continuous development, SciresM loves pokemon, as long as theres pokemon games, SciresM will be there to RE the game or console where the pokemon game runs.
 
  • Like
Reactions: Benoit934
People who are desperate to stay up to date with updates can always just read the #cfw-development channel in ReSwitched's discord, where I talk about what I'm working on pretty much every day. I don't really think it's necessary to provide push updates, so to speak, when anyone who wants them can listen in.

Someone got an invite for this channel please?
 

Site & Scene News

Popular threads in this forum