Hacking Question Virgin Switch on firmware 2.3.0

  • Thread starter Thread starter Jedis
  • Start date Start date
  • Views Views 4,545
  • Replies Replies 10

Jedis

Well-Known Member
Newcomer
Joined
Jan 10, 2009
Messages
79
Reaction score
7
Trophies
1
XP
375
Country
United States
Hello,

I haven't played my Switch in about 9 months or so. It is still on firmware 2.3.0.

All of this time, I am still buying games. I would like to start playing it again, but have been mainly holding out for the scene to mature so I can play emulators on it.

I do not want to risk being banned. From my reading, it seems like nothing is 100% certain, even if NSPs / downloaded games aren't used. Is this the case?

Basically, trying to determine if it's worth holding out or if I should just update it and start enjoying my Switch. If I should update it, should I update to the latest version, or use one of the game carts I have to update to something lower than firmware 6.2.0?

Thanks!
 
keep it for hack and piracy/homebrew, and buy a clean switch for your legit games and online?
 
If you don't care about online play right now, you can go ahead and make a NAND backup using Hekate, update to 6.2.0, and use CFW while always keeping the Switch offline. If you ever want to use online play in the future, you can restore the NAND backup from before you started hacking it.

If you do care about online play right now, then you should wait for a proper emuNAND solution from Atmosphere.
 
  • Like
Reactions: Albytrozz
If you don't care about online play right now, you can go ahead and make a NAND backup using Hekate, update to 6.2.0, and use CFW while always keeping the Switch offline. If you ever want to use online play in the future, you can restore the NAND backup from before you started hacking it.

If you do care about online play right now, then you should wait for a proper emuNAND solution from Atmosphere.
Thank you. Since updating will burn the fuses, will that potentially be an issue in the future if I were to restore the NAND backup, as more fuses would be burned than earlier firmware would look for?
 
Thank you. Since updating will burn the fuses, will that potentially be an issue in the future if I were to restore the NAND backup, as more fuses would be burned than earlier firmware would look for?
Yes. If there is a fuse mismatch like the one you've described, then you will need to boot OFW using Hekate and update in order for the system version to match the number of fuses.

Alternatively, you can update without burning fuses by using ChoiDujourNX, but that will require you to keep AutoRCM installed until the day you hypothetically decide to restore your clean NAND. With AutoRCM installed, your Switch will always coldboot into RCM, but that's not a problem if you keep your Switch in sleep mode when you're not using it.
 
Yes. If there is a fuse mismatch like the one you've described, then you will need to boot OFW using Hekate and update in order for the system version to match the number of fuses.

Alternatively, you can update without burning fuses by using ChoiDujourNX, but that will require you to keep AutoRCM installed until the day you hypothetically decide to restore your clean NAND. With AutoRCM installed, your Switch will always coldboot into RCM, but that's not a problem if you keep your Switch in sleep mode when you're not using it.
Thank you! I appreciate your help.

I think it's fairly safe to assume that once a proper emuNAND is released, it won't matter what version the NAND is, and there wouldn't be a need to downgrade? 6.2.0 is hackable or will be?
 
Thank you! I appreciate your help.

I think it's fairly safe to assume that once a proper emuNAND is released, it won't matter what version the NAND is, and there wouldn't be a need to downgrade? 6.2.0 is hackable or will be?
The point of having a sysNAND and an emuNAND is to use one for legitimate online play and to use the other for offline hackery.

The point of restoring your clean NAND backup is to be able to use online play without Nintendo seeing any of your hackery. With the ability to use a proper emuNAND, Nintendo won't be able to see your hackery, and there won't be any reason to restore your clean NAND before using online play.

There will never be any reason to specifically downgrade except for using new exploits that haven't been released yet, and they will only work if you haven't burnt additional fuses.

If your Switch is vulnerable to the RCM exploit, then it is forever hackable. 6.2.0 is compatible with CFW.

SX OS has "proper" emunand.
No. In principle, Nintendo can detect its usage.
 
Last edited by Lacius,
No. In principle, Nintendo can detect its usage.

That doesn't mean it's not "proper", it's just not safe.as with every single thingy on the Switch. No matter how hard you try, sooner or later you will get banned no matter what method you're using to stay hidden.

If OP wants to play online he should do it the legit way/buy another console just for that. His FW version is low enough for some cool exploits so emunand is the way to go here.
 
That doesn't mean it's not "proper", it's just not safe.as with every single thingy on the Switch. No matter how hard you try, sooner or later you will get banned no matter what method you're using to stay hidden.

If OP wants to play online he should do it the legit way/buy another console just for that. His FW version is low enough for some cool exploits so emunand is the way to go here.
The point of the thread is to be able to use CFW without being banned, so the SX OS emuNAND is improper. See my post above for the only viable options.
 

Site & Scene News

Popular threads in this forum