Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[Resaec]

Highest FW for that? I'm on 5.x

Sorry, 4.1.0

 

[Albytrozz]

In fact I want to play Zelda and it weighs 15GB. Can I somehow play it on FAT32 ?

I believe there are apps to split XCI into pieces so they fit on Fat32 but why would anyone bother?!?

Use an exFAT card for SX OS and a Fat32 card for homebrew and emulation and you're good to go. I haven't had a corrupt card since getting SX OS.

I don't understand what the issue is with updating to 5.1.0... if it's just to hope there will be a jigless boot it seems like a dumb reason not to be able to use your Switch properly for now. Either hack at 5.1.0 or keep it rotting in a box at 3.0, I don't see why everyone is going through all the hassle of bothering to hack a Switch just to keep it on a useless fw especially considering they can't soft patch the exploit.

 

[lawrence7]

I used this app (GUIformat) to format my sdxc card from exfat to fat32. I copied all the files from Atmosphere website and there is exactly the same problem.The black menu with CFW loads and when I choose from the boot menu to load CFW the screen blinks and loads the standard Nintendo system instead of homebrew. Any ideas?

 

[Joom]

I don't see why everyone is going through all the hassle of bothering to hack a Switch just to keep it on a useless fw especially considering they can't soft patch the exploit.

Sheep. That's why.

 

[guily6669]

I believe there are apps to split XCI into pieces so they fit on Fat32 but why would anyone bother?!?

Use an exFAT card for SX OS and a Fat32 card for homebrew and emulation and you're good to go. I haven't had a corrupt card since getting SX OS.

I don't understand what the issue is with updating to 5.1.0... if it's just to hope there will be a jigless boot it seems like a dumb reason not to be able to use your Switch properly for now. Either hack at 5.1.0 or keep it rotting in a box at 3.0, I don't see why everyone is going through all the hassle of bothering to hack a Switch just to keep it on a useless fw especially considering they can't soft patch the exploit.

Well maybe because a big shame is getting locked to jigs (without autoRCM) and payloads 4 ever...

And anyway when real emunand comes out, most likely we can just simply update the console to last FW and play backups while waiting for a <<jigless'n payload>> way to hack the console.

Some times I'm even lazy to press power button on my PC .

 

[ShadowOne333]

Well maybe because a big shame is getting locked to jigs (without autoRCM) and payloads 4 ever...

And anyway when real emunand comes out, most likely we can just simply update the console to last FW and play backups while waiting for a <<jigless'n payload>> way to hack the console.

Some times I'm even lazy to press power button on my PC .

Agree.
The main reason why I'm still holding off with my 3.0.0 console is because of the possible coldboot exploit for it.
Always carrying around a jig and a way to inject the payload from a powered off state is bothersome to say the least.
Besides, AutoRCM is hacky as all hell, and powering off the machine is a pain for those that tend to use it in handheld mode most of the time.

So yeah, I would much rather wait for the coldboot exploit rather than having to deal with things like AutoRCM or cables to just inject a payload.

 

[Spoda]

Agree.
The main reason why I'm still holding off with my 3.0.0 console is because of the possible coldboot exploit for it.
Always carrying around a jig and a way to inject the payload from a powered off state is bothersome to say the least.
Besides, AutoRCM is hacky as all hell, and powering off the machine is a pain for those that tend to use it in handheld mode most of the time.

So yeah, I would much rather wait for the coldboot exploit rather than having to deal with things like AutoRCM or cables to just inject a payload.

What do you mean by 'hacky' as all hell?
You know - reading posts like yours put me off AutoRCM, until one day I was stoned and just decided to do it.

Thank god I did, because it's not bad at all. I exclusively use my Switch in handheld mode and I am FUCKING glad that I use AutoRCM. There's nothing wrong with it. Just leave your Switch on sleep mode, it's not bothersome at all, and you don't even lost that much charge.

It's definitely worth it over having to use a jig and some way to inject a payload everytime you turn the damn console off.

I personally think you've never used autorcm and just listened to other people that bashed it, and now you've gotten some sort of skewed judgement over it.

 

[zragnarok]

AutoRCM is easy but I already waited this long (launch Switch on 3.0.0)... so I can easily wait a bit longer for a cold-boot method. Especially since im working through my PS4 backlog at the moment.

 

[M7L7NK7]

The only issue anyone ever has with auto RCM is not reading what it actually does and then freaking out when their switch doesn't turn on normally

And yeah if you don't want to use auto RCM and fuselessly update your 3.0.0 so you can actually use it for a decent amount of stuff that's your loss

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

Especially now ChoiDujour exists it's so easy, when it didn't it took an hour and that felt hacky

 

[ShadowOne333]

What do you mean by 'hacky' as all hell?
You know - reading posts like yours put me off AutoRCM, until one day I was stoned and just decided to do it.

Thank god I did, because it's not bad at all. I exclusively use my Switch in handheld mode and I am FUCKING glad that I use AutoRCM. There's nothing wrong with it. Just leave your Switch on sleep mode, it's not bothersome at all, and you don't even lost that much charge.

It's definitely worth it over having to use a jig and some way to inject a payload everytime you turn the damn console off.

I personally think you've never used autorcm and just listened to other people that bashed it, and now you've gotten some sort of skewed judgement over it.

Thing is that I use the Switch on handheld all the time, and usually when I'm not home, so that's why I am not too keen on AutoRCM, because it might get tricky if the battery dies. I also don't like to leave the device in sleep mode but rather turn it off completely to save battery as well, and to turn off the Switch completely with AutoRCM installed is tricky too.

 

[aos10]

AutoRCM is easy but I already waited this long (launch Switch on 3.0.0)... so I can easily wait a bit longer for a cold-boot method. Especially since im working through my PS4 backlog at the moment.

there is no "cold boot" method, only a mythical "worm boot" that i don't even they will release it this year, as till now there is no "mariko" switch in the wild.
so we have to wait for mariko, then the dev may release it.

 

[mariogamer]

AutoRCM is easy but I already waited this long (launch Switch on 3.0.0)... so I can easily wait a bit longer for a cold-boot method. Especially since im working through my PS4 backlog at the moment.

The only firmware confirmed to receive a coldboot in a "short" period of time is firmware 1.0.0. 2.0.0 and higher to 3.0.1 have a not impossible (enphasis on the "" and not impossible) chance of getting in a very long time.
I think it is worth getting something to boot your switch even for handheld usage.

Other bootrom exploits have been found, but those might get patched wih mariko/aren't enough (deja vu's case) if I remember.

 

[Resaec]

so we have to wait for mariko, then the dev may release it.

Thats my guess to. Sure it will be a new board, but if they use a NVidia chip again, chances are that there is another known bootrom bug that might carry over.
If N makes their own bootrom (highly unlikely) like some say, there will be new bugs.
It's wait and pray. And god damn Nintendo, just release mariko :/

 

[mariogamer]

Thats my guess to. Sure it will be a new board, but if they use a NVidia chip again, chances are that there is another known bootrom bug that might carry over.
If N makes their own bootrom (highly unlikely) like some say, there will be new bugs.
It's wait and pray. And god damn Nintendo, just release mariko :/

The fact that it's taking so long get us to two possible point:
1. It doesn't exist everything is a lie (lol)
2. It'll be hell of a wall in security and/or [NINTENDO REASONS]

So yeah let's wait another year....

 

[Resaec]

I also thought about the lie thing... That would be a clever move to delay the scene, but RCM came way too late into the distribution and the fix even later.
Security of the Switch was unseen good for Nintendo. RCM was an "unfortunate" bug undermining everything Nintendo worked for...

 

[M7L7NK7]

Was anything actually confirmed about Mariko? Or was it just the reference to the word in the code

 

[Dona97]

When atmosphere coming out??? Now i have see on atmosphere site that is fix for switch 6.0.0...

 

[maxx488]

When atmosphere coming out??? Now i have see on atmosphere site that is fix for switch 6.0.0...

AtmosNever.

 

[mariogamer]

Was anything actually confirmed about Mariko? Or was it just the reference to the word in the code

I think devloppers found evidence of a new crypto used + new files using that crypto. (It should be referenced somewhere too? Idk)

 

[M7L7NK7]

Who knows when if ever they decide to use it... They could even just stick with the ipatches to save money