Hacking Buy a SXOS Kit, and now?

r1ch4rd

Member
OP
Newcomer
Joined
Jun 10, 2019
Messages
21
Trophies
0
Age
33
XP
106
Country
Brazil
Hello, guys...

I buy a new nintendo switch unpatched and ordered a SXOS kit that should arrieve next week.
I read a lot of tutorials, videos on youtube but still have some questions....

I want to leave NAND as original and avoid to get ban, so the first thing that I have to do it's the backup of original NAND and creat a emuNAND?
Or should I hack before do the emuNAND?

To do a update just on emuNAND and avoid get ban, I have to update offline? Can I install the last uptade and keep the original NAND on 4.0.1?

Any other tips to avoid get ban?

Thanks
 

pLaYeR^^

Doctor Switch
Member
Joined
Sep 18, 2014
Messages
3,151
Trophies
1
Age
27
Location
Austria
XP
3,856
Country
Austria
Always create a clean backup of your switch before any hacking. Then you can create EmuNAND and only update EmuNAND. Your SysNAND will stay on 4.0.1. Never go online while you're in EmuNAND. Update EmuNAND offline with ChoiDujourNX.
 

CanIHazWarez

Well-Known Member
Member
Joined
Jan 21, 2016
Messages
371
Trophies
0
Age
32
XP
1,352
Country
United States
Make a clean NAND backup first thing. Then create emunand and activate autoRCM. You can then update either NAND using ChoiDujourNX (that way you don't burn fuses). Never update using the official method or else YOU WILL BURN FUSES! Only do hacking and backup loading in emunand. Never go online in emunand.
 
  • Like
Reactions: NoNAND and r1ch4rd

r1ch4rd

Member
OP
Newcomer
Joined
Jun 10, 2019
Messages
21
Trophies
0
Age
33
XP
106
Country
Brazil
I read in somewhere that when I update offline I should not use autoRCM, is that right? Can I uptade to the last version(8.0.1) or should I use other?

Can I get any conflict not updating the original NAND? Should I take any precaution?

About the fuses, could you pass me any article to read?

THANK YOU VERY MUCH guys
 

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,731
Trophies
1
XP
20,609
Country
United States
I read in somewhere that when I update offline I should not use autoRCM, is that right? Can I uptade to the last version(8.0.1) or should I use other?

Can I get any conflict not updating the original NAND? Should I take any precaution?

About the fuses, could you pass me any article to read?

THANK YOU VERY MUCH guys

If you are using emunand, feel free to update that as much as possible, AutoRCM and fusee only apply to sysnand, using autoRCM preserve your sysnand fuse, you should only restore your sysnand firmware if your fuse count match with your firmware version match what is on the fuse table.


https://switchbrew.org/wiki/Fuses
 
  • Like
Reactions: NoNAND and r1ch4rd

CanIHazWarez

Well-Known Member
Member
Joined
Jan 21, 2016
Messages
371
Trophies
0
Age
32
XP
1,352
Country
United States
I read in somewhere that when I update offline I should not use autoRCM, is that right? Can I uptade to the last version(8.0.1) or should I use other?

Can I get any conflict not updating the original NAND? Should I take any precaution?

About the fuses, could you pass me any article to read?

THANK YOU VERY MUCH guys
Your first sentence is VERY incorrect. When you update using ChoiDujourNX, you NEED autoRCM (ChoiDujourNX adds it automatically). The reason is that the official bootloader does a fuse check every single time you boot. When it sees that you updated the firmware and didn't burn fuses, it WILL burn your fuses. You want as few fuses burned as possible on your system. autoRCM makes it so that you can only use a third-party bootloader, which bypasses the fuse check. You can load emunand or sysnand from the third party bootloader and your fuses will be safe. Updating to 8.0.1 is fine as long as you are running the latest beta version of SX OS (2.7.1). There is no issue with sysnand and emunand being on different firmwares. This is a good explanation of fuses:
The Nintendo Switch's bootloader aka the part that controls the boot-up process for the console checks the number of fuses burnt and compares it to the current firmware. If they do not match, it will either prevent the console from turning on or it will burn them to compensate. While both Hekate and SX OS V1.2+ not only bypass the fuse check entirely as substitute bootloaders but also prevent fuses from being burnt, this is not enough protection against burning fuses during system updates. The reason for this is because when you update the Switch normally, it reboots the console so the Switch has a chance to burn fuses. Even if you initially boot the console with either Hekate or SX OS V1.2+, when you update normally within the Switch, the Switch's bootloader will take over when the console is rebooting after the update. Therefore, the guide not only has you install AutoRCM as a means to prevent you from accidentally booting the Switch normally which will burn fuses, but also has you install the update entirely offline. It should also be worth noting that updating removes any and all forms of AutoRCM which the guide has a section on how to recover it to prevent your Switch from trying to burn fuses.

In theory, you can update without following the tutorial and instead using the official way while not burning fuses IF you can stop the console from turning back on after it updates successfully. This is a very user-oriented window that if you miss will permanently burn the fuses and is a risk you can take should you acknowledge it. Another problem is that once you do manage to turn off the console with the correct timing, you have to ensure from that moment onwards that you will boot your console from RCM only because it will burn the fuses if you turn it on normally. This means you must have some means of inducing RCM with 100% confidence or you risk burning your fuses. AutoRCM cannot save you in this case as it will be removed during the system update and can only be re-installed via RCM.
 
  • Like
Reactions: PHiLiPZ and r1ch4rd

gizmomelb

Well-Known Member
Member
Joined
Jul 13, 2006
Messages
926
Trophies
0
XP
1,647
Country
Australia
Your first sentence is VERY incorrect. When you update using ChoiDujourNX, you NEED autoRCM (ChoiDujourNX adds it automatically). The reason is that the official bootloader does a fuse check every single time you boot. When it sees that you updated the firmware and didn't burn fuses, it WILL burn your fuses. You want as few fuses burned as possible on your system. autoRCM makes it so that you can only use a third-party bootloader, which bypasses the fuse check. You can load emunand or sysnand from the third party bootloader and your fuses will be safe. Updating to 8.0.1 is fine as long as you are running the latest beta version of SX OS (2.7.1). There is no issue with sysnand and emunand being on different firmwares. This is a good explanation of fuses:

your second sentence is very incorrect.

Once the emuNAND has been updated with ChoiDuJourNX you can DISABLED autoRCM and it will work fine. You do not NEED autoRCM at all with emuNAND.

My sysNAND is at 3.0.2 and my emuNAND is at 7.0.1, I disabled autoRCM.
 

CanIHazWarez

Well-Known Member
Member
Joined
Jan 21, 2016
Messages
371
Trophies
0
Age
32
XP
1,352
Country
United States
your second sentence is very incorrect.

Once the emuNAND has been updated with ChoiDuJourNX you can DISABLED autoRCM and it will work fine. You do not NEED autoRCM at all with emuNAND.

My sysNAND is at 3.0.2 and my emuNAND is at 7.0.1, I disabled autoRCM.
You don't need it, in the sense that it will work without it. You need it if you want to update without burning fuses. I suppose you could do without it if you don't ever update sysnand, but what would the point be? The only reason you would want to boot into sysnand is to play online, but you'd need to be on the latest firmware for that. Are you keeping your firmware low so that you can play carts without updating your card slot? Even then, there are better ways around it (and this situation doesn't apply to OP). If you are using emunand and have the sx dongle, I don't see what benefit you would gain from not having autorcm. That setup may work fine for you but I would not suggest it to other people because it's begging to have your fuses burned. You probably know what you're doing enough to avoid it, but most people won't.
 
  • Like
Reactions: r1ch4rd

nekkk

Member
Newcomer
Joined
May 17, 2018
Messages
10
Trophies
0
Age
41
XP
285
Country
Brazil
your second sentence is very incorrect.

Once the emuNAND has been updated with ChoiDuJourNX you can DISABLED autoRCM and it will work fine. You do not NEED autoRCM at all with emuNAND.

My sysNAND is at 3.0.2 and my emuNAND is at 7.0.1, I disabled autoRCM.

Hey man, one quick question, did you have to manually install exFAT on your 3.0.2 console?
 

r1ch4rd

Member
OP
Newcomer
Joined
Jun 10, 2019
Messages
21
Trophies
0
Age
33
XP
106
Country
Brazil
Your first sentence is VERY incorrect. When you update using ChoiDujourNX, you NEED autoRCM (ChoiDujourNX adds it automatically). The reason is that the official bootloader does a fuse check every single time you boot. When it sees that you updated the firmware and didn't burn fuses, it WILL burn your fuses. You want as few fuses burned as possible on your system. autoRCM makes it so that you can only use a third-party bootloader, which bypasses the fuse check. You can load emunand or sysnand from the third party bootloader and your fuses will be safe. Updating to 8.0.1 is fine as long as you are running the latest beta version of SX OS (2.7.1). There is no issue with sysnand and emunand being on different firmwares. This is a good explanation of fuses:

But if I eventually boot on original NAND, I have to take off my microSD? or I always has to boot in RCM mode after update the emuNAND even if I wanna boot on original one?

your second sentence is very incorrect.

Once the emuNAND has been updated with ChoiDuJourNX you can DISABLED autoRCM and it will work fine. You do not NEED autoRCM at all with emuNAND.

My sysNAND is at 3.0.2 and my emuNAND is at 7.0.1, I disabled autoRCM.

Now I'm confuse hahah
When I uptade with ChoiDuJourNX I have to check the autoRCM box in instalation to prevent burn fuses and after that I can disable? Or I always have to has autoRCM mode on?

Thanks to everyone!
 
Last edited by r1ch4rd,

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,731
Trophies
1
XP
20,609
Country
United States
But if I eventually boot on original NAND, I have to take off my microSD? or I always has to boot in RCM mode after update the emuNAND even if I wanna boot on original one?



Now I'm confuse hahah
When I uptade with ChoiDuJourNX I have to check the autoRCM box in instalation to prevent burn fuses and after that I can disable? Or I always have to has autoRCM mode on?

Thanks to everyone!

Well if they don't want to use autorcm, then they need a jig, if the person had a modchip along with autoboot and autorcm, they can autoboot into emunand from being completely powered off. AutoRCM other feature is for fuse burning prevention, not really need it for emunand, as you would update to the latest on emunand.
 

r1ch4rd

Member
OP
Newcomer
Joined
Jun 10, 2019
Messages
21
Trophies
0
Age
33
XP
106
Country
Brazil
I still not get it the fuse parts and the AutoRCM parts of hacking, I'll study more.

from what i understand the AutoRCM prevent burn fuses, but as I'll update the emuNAND the AutoRCM will be not necessary. Would be if I do the update on the original NAND? right?

Thanks everyone.
 

gizmomelb

Well-Known Member
Member
Joined
Jul 13, 2006
Messages
926
Trophies
0
XP
1,647
Country
Australia
Hey man, one quick question, did you have to manually install exFAT on your 3.0.2 console?

I'd have to check.. I know I definitely installed the exFAT firmware option in my emuNAND - BUT I only use FAT32 formatted SD card (exfat support both formats by the way) due to exFAT likelihood of corruption.

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

I still not get it the fuse parts and the AutoRCM parts of hacking, I'll study more.

from what i understand the AutoRCM prevent burn fuses, but as I'll update the emuNAND the AutoRCM will be not necessary. Would be if I do the update on the original NAND? right?

Thanks everyone.

yes, autoRCM is needed if you want to upgrade your system NAND to a newer firmware BUT keep it so you can downgrade to older versions for firmware for the elusive ''warm boot'' exploit.

persoanll I've kept my sysem firmware at 3.0.2 and I never go online. I've done this more for potential resale on my switch rather than waiting for a coldboot exploit.

However IF you're going to take your sysNAND online then why not just update to 8.0.1 anyways without using CoiDuJourNX? As said, the likelihood of a coldboot exploit is next to nil. If you want to play online using 8.0.1 all of the CFW solutions support 8.0.1 exploits.. so may as well upgrade I guess.

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

Well if they don't want to use autorcm, then they need a jig, if the person had a modchip along with autoboot and autorcm, they can autoboot into emunand from being completely powered off. AutoRCM other feature is for fuse burning prevention, not really need it for emunand, as you would update to the latest on emunand.

even if you want to use autoRCM you still need a jig and usb dongle / pc / phone to inject the payload initially.

I disbaled autoRCM after initial emuNAND update on my switch and I've had to use the jibg maybe 3 times in almost a year.... the switch is on standaby / sleep mode and then put on the charger once a week or so when it is not in use.
 
  • Like
Reactions: r1ch4rd

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,731
Trophies
1
XP
20,609
Country
United States
I still not get it the fuse parts and the AutoRCM parts of hacking, I'll study more.

from what i understand the AutoRCM prevent burn fuses, but as I'll update the emuNAND the AutoRCM will be not necessary. Would be if I do the update on the original NAND? right?

Thanks everyone.

Fuse rule only applies to sysnand, if you accidentally update your system firmware via Nintendo server it burn your fuse. With autoRCM it put the switch into RCM 100% of the time. For emunand it doesn't matter if it on autorcm, leave it on autorcm only if you don't want to use a jig all the time.

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

I'd have to check.. I know I definitely installed the exFAT firmware option in my emuNAND - BUT I only use FAT32 formatted SD card (exfat support both formats by the way) due to exFAT likelihood of corruption.

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



yes, autoRCM is needed if you want to upgrade your system NAND to a newer firmware BUT keep it so you can downgrade to older versions for firmware for the elusive ''warm boot'' exploit.

persoanll I've kept my sysem firmware at 3.0.2 and I never go online. I've done this more for potential resale on my switch rather than waiting for a coldboot exploit.

However IF you're going to take your sysNAND online then why not just update to 8.0.1 anyways without using CoiDuJourNX? As said, the likelihood of a coldboot exploit is next to nil. If you want to play online using 8.0.1 all of the CFW solutions support 8.0.1 exploits.. so may as well upgrade I guess.

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



even if you want to use autoRCM you still need a jig and usb dongle / pc / phone to inject the payload initially.

I disbaled autoRCM after initial emuNAND update on my switch and I've had to use the jibg maybe 3 times in almost a year.... the switch is on standaby / sleep mode and then put on the charger once a week or so when it is not in use.

That true, but I still really like the modchip option with autoRCM and autoboot w/hekate to boot up what I have specific to coldboot.
 
  • Like
Reactions: r1ch4rd

r1ch4rd

Member
OP
Newcomer
Joined
Jun 10, 2019
Messages
21
Trophies
0
Age
33
XP
106
Country
Brazil
Hey guys, I read a lot of things about the offline updates and efuses, And what I understand is:

If you update offline the emuNAND you don't has to worry about burning efuses because you can only access the emuNAND by the RCM mode and as the sysNAND isn't update, when you boot normaly you don't have to worry about burning efuse, cause your NAND is original. Is that right?

Burning efuses just ocuried when you update you sysNAND and bot normally.

So the autoRCM isn't necessary at all. Right?
Or I can burn efuse even updating emuNAND?

Thanks
 

CanIHazWarez

Well-Known Member
Member
Joined
Jan 21, 2016
Messages
371
Trophies
0
Age
32
XP
1,352
Country
United States
Hey guys, I read a lot of things about the offline updates and efuses, And what I understand is:

If you update offline the emuNAND you don't has to worry about burning efuses because you can only access the emuNAND by the RCM mode and as the sysNAND isn't update, when you boot normaly you don't have to worry about burning efuse, cause your NAND is original. Is that right?

Burning efuses just ocuried when you update you sysNAND and bot normally.

So the autoRCM isn't necessary at all. Right?
Or I can burn efuse even updating emuNAND?

Thanks
Correct. Although, I'm not sure why you wouldn't want autoRCM.
Fuse rule only applies to sysnand, if you accidentally update your system firmware via Nintendo server it burn your fuse.
Don't listen to this. If you update your sysnand (even using ChoiDujourNX) and your system EVER boots normally (as in, not booting into RCM and injecting a payload), you will burn fuses.
 
  • Like
Reactions: r1ch4rd

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,731
Trophies
1
XP
20,609
Country
United States
Correct. Although, I'm not sure why you wouldn't want autoRCM.

Don't listen to this. If you update your sysnand (even using ChoiDujourNX) and your system EVER boots normally (as in, not booting into RCM and injecting a payload), you will burn fuses.

Well that is because you aren't not using autoRCM, of course you would burn fuse if you boot into ofw without a bootloader, after a system update by Nintendo server it boot into OFW, you burn fuse that way.
 
Last edited by Hayato213,
  • Like
Reactions: r1ch4rd

r1ch4rd

Member
OP
Newcomer
Joined
Jun 10, 2019
Messages
21
Trophies
0
Age
33
XP
106
Country
Brazil
Well that is because you aren't not using autoRCM, of course you would burn fuse if you boot into ofw without a bootloader, after a system update by Nintendo server it boot into OFW, you burn fuse that way.

But I'll not update my OFM, just the emuNAND.

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

And what about exFAT formatation, Its really necessary? I have to prepare my switch isnt?
 

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,731
Trophies
1
XP
20,609
Country
United States
But I'll not update my OFM, just the emuNAND.

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

And what about exFAT formatation, Its really necessary? I have to prepare my switch isnt?

You can update the emunand as much as you want with ChoidujourNX, exFAT is more corruption prone, I switched from exFAT to FAT32.
 
  • Like
Reactions: r1ch4rd

punderino

aka Big-PeePee Swinger
Member
Joined
Jan 5, 2016
Messages
1,247
Trophies
0
Age
32
Location
Kansas City, Missouri
Website
www.anus.trade
XP
2,490
Country
United States
your second sentence is very incorrect.

Once the emuNAND has been updated with ChoiDuJourNX you can DISABLED autoRCM and it will work fine. You do not NEED autoRCM at all with emuNAND.

My sysNAND is at 3.0.2 and my emuNAND is at 7.0.1, I disabled autoRCM.
and winner of the weirdest emuNAND setup goes to gizmo!
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    LeoTCK @ LeoTCK: yes for nearly a month i was officially a wanted fugitive, until yesterday when it ended