Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,726,205
  • Replies Replies 9,260
  • Likes Likes 92
Then please explain what will be detected by nintendo?

The emunand is a full copy of the sysnand.
All patching occures there on sdcard. The eMMC wont get touched during that process.
Therefore there wont be any trace on sysnand.
Remember to keep your device offline while in CFW!

For Online Usage:
- Power down your device
- Remove the sdcard containing cfw
- bootup to Stock FW

Again: How should they detect that you've used an cfw before?




Never use Atmosphere or any other cfw online
My point is that you don’t need emuNAND to achieve that.

Boot into CFW on sysNAND - remember to disable online, maybe use a different SD card.

Boot into stock FW on sysNAND - clean fw, no trace of CFW.

For example, Luma 3DS doesn’t need to make any permanent changes to the FW. Patches are applied on the fly. Remove boot.firm and you get a clean stock FW.
 
My point is that you don’t need emuNAND to achieve that.

Boot into CFW on sysNAND - remember to disable online, maybe use a different SD card.

Boot into stock FW on sysNAND - clean fw, no trace of CFW.

For example, Luma 3DS doesn’t need to make any permanent changes to the FW. Patches are applied on the fly. Remove boot.firm and you get a clean stock FW.
You COULD do that, but to me an offline emuNAND is the best solution. You might be fine if you keep yourself offline when in CFW, but I'm paranoid. lol Having it completely isolated would make me feel better....don't want to get banned from Splatoon 2 or something like that.
 
My point is that you don’t need emuNAND to achieve that.

Boot into CFW on sysNAND - remember to disable online, maybe use a different SD card.

Boot into stock FW on sysNAND - clean fw, no trace of CFW.

For example, Luma 3DS doesn’t need to make any permanent changes to the FW. Patches are applied on the fly. Remove boot.firm and you get a clean stock FW.

But using CFW in sysnand will leave traces that even persist after a full reboot.

The Horizon OS stores a launch history. Nintendo could check that you've used hbl or any other homebrew app before.
Even if the app itself is gone.

And: the 3ds does that too.
It won't be a problem for Nintendo to check your history.
No one knows why they dind't do that.
 
Last edited by MHDestination,
Now I am wondering why CFW on 3DS uses sysNAND. Why doesn't it use isolated emuNAND like Atmosphere will do? Nintendo can only check sysNAND, right?
 
Now I am wondering why CFW on 3DS uses sysNAND. Why doesn't it use isolated emuNAND like Atmosphere will do? Nintendo can only check sysNAND, right?

Because nintendo seems to tolerate cfw on 3ds.

Nintendo can check every nand that connects to their servers. Doesn't matter if emu or sys

In the early days of 3ds-cfw everyone was using emunand.
But since nintendo didn't ban, many users started modifying their sysnand instead.
There was no reason to hide.

But i'm sure that Nintendo will change their behavior for Switch
 
Last edited by MHDestination,
Because nintendo seems to tolerate cfw on 3ds.

Nintendo can check every nand that connects to their servers. Doesn't matter if emu or sys

In the early days of 3ds-cfw everyone was using emunand.
But since nintendo didn't ban, many users started modifying their sysnand instead.
There was no reason to hide.

But i'm sure that Nintendo will change their behavior for Switch
I suppose we don't know for sure, but this is my assumption. I have a 3DS that's been running CFW for a long time and it's not banned, but I don't know that I want to roll the dice again on my Switch.
 
Because nintendo seems to tolerate cfw on 3ds.

Nintendo can check every nand that connects to their servers. Doesn't matter if emu or sys

In the early days of 3ds-cfw everyone was using emunand.
But since nintendo didn't ban, many users started modifying their sysnand instead.
There was no reason to hide.

But i'm sure that Nintendo will change their behavior for Switch

But what were the benefits that made people use sysNAND instead?

And if Nintendo can check sysNAND and emuNAND why would Atmosphere use emuNAND only? Unless they want to isolate CFW I see no other reason.
 
But what were the benefits that made people use sysNAND instead?

And if Nintendo can check sysNAND and emuNAND why would Atmosphere use emuNAND only? Unless they want to isolate CFW I see no other reason.

The benefit of sysNAND is less storage consumption on SD card. And reading from internal memory is faster than reading from sd.

We don't know yet, but emunand might be just an option.
Maybe we can use atmosphere from sysnand (but i won't do so ^^ )
 
On the 3DS, the primary reason emuNAND was used is because we relied on older FW sysNAND for the exploits. As soon as boot time exploits such as A9LH arrived, emuNAND was deemed unnecessary.

The Switch situation is slightly different of course in that we have the boot time exploit so soon. I guess we’ll see when Atmosphere arrives.
 
Last edited by sj33,
I have no problem to be banned from online gaming, because I don't use it.
If they ban me from eShop - so, there are other ways to get games. Hope they will think about this.

I think, who knows, how to get and install a CFW, he knows where to find games outside the eShop.
 
I have no problem to be banned from online gaming, because I don't use it.
If they ban me from eShop - so, there are other ways to get games. Hope they will think about this.

I think, who knows, how to get and install a CFW, he knows where to find games outside the eShop.

Yeah might be true... banning won't keep anyone from pirating more games.
Therefore it isn't the badest idea to grant them access to eshop.

Previously nintendo only banned for online cheating and playing games before release
 
Previously nintendo only banned for online cheating and playing games before release
And the smartest choice would be to keep it like that because 'ol Nintendo won't get a single penny from people that pirate games but could at least earn the 20 bucks for the online play per year. That's better than nothing.

Then again it's Nintendo so I expect bans to the same extend as on the 3DS except that they will be permanent this time.
 
Last edited by LysergCooltyp,
And the smartest choice would be to keep it like that because 'ol Nintendo won't get a single penny from people that pirate games but could at least earn the 20 bucks for the online play per year. That's better than nothing.

Then again it's Nintendo so I expect bans to the same extend as on the 3DS except that they will be permanent this time.

Until just like on the 3ds someone finds a way to unban the switch with some unorthodox thing like friendcodeseed_b
 
and Xeno2's japanese voice pack!

p.s. i see u have japan flag, have you ever played Xeno2 with english dub? which one's better dub quality?

Not to go off topic, but I felt the jap voices were nice but I eventually went back to english dub. They get better once you get used to them, but the jap voices still felt a bit flat when I was using jap audio. DM me if you want to discuss more, or we can make a thread in the appropriate section if there isn't one already.
 
was wondering when cfw finally arrives will it be as simple as copying a few files on the micro sd and launching a program on the switch? or will it be we load up a game to get to hbl? plz like if this helps anyone else who was thinking the same. edit: im looking for a reply to my question.
 
Last edited by ZanderX420,
  • Like
Reactions: Koksi__
was wondering when cfw finally arrives will it be as simple as copying a few files on the micro sd and launching a program on the switch? or will it be we load up a game to get to hbl? plz like if this helps anyone else who was thinking the same. edit: im looking for a reply to my question.

Before running files on your SD will you need to gain access to the system through an entry exploit (e.g Fusée Gelée), then you will be able to run CFW. More on that should be disclosed in the coming weeks, just wait a bit more.
 
Last edited by lukhart,
  • Like
Reactions: ZanderX420
On the 3DS, the primary reason emuNAND was used is because we relied on older FW sysNAND for the exploits. As soon as boot time exploits such as A9LH arrived, emuNAND was deemed unnecessary.

The Switch situation is slightly different of course in that we have the boot time exploit so soon. I guess we’ll see when Atmosphere arrives.
Pretty much in a nutshell. But the difference between the 3DS bootrom exploits and Fusee Gelee is that the latter is tethered which makes it a hell of a pain to boot. True some people have made strides in allowing us to load payloads using an Android, but its still more work than using B9S. I think another reason they're developing Atmosphere to work with EmuNAND is so we can use the software exploits to boot into the CFW rather than tethering our Switches every time we turn it off (because not everyone keeps their Switch on 24/7).
 
... is that the latter is tethered which makes it a hell of a pain to boot. True some people have made strides in allowing us to load payloads using an Android, but its still more work than using B9S...

Honestly getting into RCM using a jig and running payloads off an android phone takes me maybe max 20 seconds, it's really a very minor inconvenience as opposed to losing online access. Given a choice between an untethered boot vs keeping your console safe from online bans, the answer should really be obvious for any gamer. The online services is only beginning to get better and I'm certain it will become an essential part of most multiplayer games soon.
 
  • Like
Reactions: LysergCooltyp

Site & Scene News

Popular threads in this forum