Hacking How do you safely update sysNAND to 7.0 while using 6.2 emuNAND on sxOS?

[aslk]

I'd like to play smash online while still having a usable emuNAND on 6.2 for offline games. Haven't signed in in a while, so apologies if I missed something.

I read somewhere that you shouldn't be updating the sysNAND regularly for the 6.2 emuNAND to function properly. Is this true? If so, how do you update your sysNAND properly?

 

[lagjazz]

You can update your sysnand to 7.0, sx 2.5.3 now support booting up emunand 6.2

 

[pLaYeR^^]

You can update your SysNAND with normal official update if it‘s clean. Latest SX OS release supports 7.0 SysNAND and 6.2 EmuNAND.

 

[scouts]

Question:
I have a system nand of 5.1
I am installing EmuNAND as we speak. I want to play the lastest games in CFW. For example I downloaded some updates for XenoBlade Chronicles 2 and now it says I need to update system FW to be able to play it.

What is the best way to play keep sx CFW working and being able to play the lastest games? Do I update the SysNAND or EmuNAND. Do I update from within SX OS or in normal mode through nintendo?

 

[emilio546]

If I dont want to burn efuses updating sysnand to 7.0 can I stay on 6.2 and create emunand on 7.0? without burning efuses?

 

[phat_earth]

Does this apply with the recent 7.0.1 update as well?

 

[pLaYeR^^]

Question:
I have a system nand of 5.1
I am installing EmuNAND as we speak. I want to play the lastest games in CFW. For example I downloaded some updates for XenoBlade Chronicles 2 and now it says I need to update system FW to be able to play it.

What is the best way to play keep sx CFW working and being able to play the lastest games? Do I update the SysNAND or EmuNAND. Do I update from within SX OS or in normal mode through nintendo?

You can install updates or games with gold leaf or the stand-alone sx installer to ignore the firmware requirements. Keep in mind: You can only launch them, if they don't need higher master keys.

If I dont want to burn efuses updating sysnand to 7.0 can I stay on 6.2 and create emunand on 7.0? without burning efuses?

EmuNAND doesn't support 7.0 yet. If you don't want to burn fuses you should install autoRCM. Than you can update SysNAND to 7.0 and boot to SysNAND with sx os boot loader. Never ever go to SysNAND with nintendo boot loader or it will burn the fuses up to 7.0.

 

[bundat]

Than you can update SysNAND to 7.0 and boot to SysNAND with sx os boot loader.

Are you 100% sure this works?
That SX OS supports booting 7.x stock/OFW?

Because I know back when 6.2 was new, nothing would boot it as OFW/stock.
Not Hekate, not SX OS.
So I could not upgrade AND preserve my fuses, until they figured out a way around the "new TSEC trickery".

 

[pLaYeR^^]

Are you 100% sure this works?
That SX OS supports booting 7.x stock/OFW?

Because I know back when 6.2 was new, nothing would boot it as OFW/stock.
Not Hekate, not SX OS.
So I could not upgrade AND preserve my fuses, until they figured out a way around the "new TSEC trickery".

Check out their latest sx os release.

 

[bundat]

Check out their latest sx os release.

Latest version fixes the emunand implementation so that you can still run 6.2 emunand even if sysnand is on 7.x.

But I don't see anything that says their bootloader can now boot stock 7.x/OFW.

I mean, I currently have 5 burned fuses (since my 4.1.0 stock), BUT I'm running now 6.2.
I'd like to play online, specifically I wanna play Tetris 99, BUT I wanna keep my 5 fuses intact.
This means I have to upgrade to 7.0.1, AND boot that OFW using a custom bootloader (which AFAIK none can do, not even the latest Hekate).

Are you 100% sure?
Are you currently doing this yourself?
How many fuses do you have burned currently, and what firmware version are you running?

 

[darkfortedx]

i have 7.0.1 sx bootloader loads, can I still create emunand sysnand etc. Honestly is there a tutorial I can follow for this?

 

[pLaYeR^^]

Latest version fixes the emunand implementation so that you can still run 6.2 emunand even if sysnand is on 7.x.

But I don't see anything that says their bootloader can now boot stock 7.x/OFW.

I mean, I currently have 5 burned fuses (since my 4.1.0 stock), BUT I'm running now 6.2.
I'd like to play online, specifically I wanna play Tetris 99, BUT I wanna keep my 5 fuses intact.
This means I have to upgrade to 7.0.1, AND boot that OFW using a custom bootloader (which AFAIK none can do, not even the latest Hekate).

Are you 100% sure?
Are you currently doing this yourself?
How many fuses do you have burned currently, and what firmware version are you running?

The official statement of sx os:

What was fixed?

• EmuNAND 6.2 booting again after updating System NAND to 7.0

Some of you who updated their System NAND to version 7.0 notified us their EmuNAND on version 6.2 would no longer boot, thus they were unable to continue using SX OS! This of course is unacceptable, so we decided to investigate and fix it. You can now enjoy the latest firmware on your System NAND again while keeping a compatible firmware in your EmuNAND partition.

An no, I am not running 7.0.0.

 

[bundat]

The official statement of sx os:

You can now enjoy the latest firmware on your System NAND again while keeping a compatible firmware in your EmuNAND partition.

Yes, because the way they were implementing emunand was broken when 7.0 came out.

Because the way they implemented it earlier, they were getting some FW data from sysnand to use in emunand.

BUT now, to run 7.0 sysnand, you STILL have to use the official bootloader, because you can't use a custom bootloader to load OFW/CFW/or any variation thereof without having all the keys (and if they're already known, then we'd have a 7.0 CFW).

So you still have to burn your fuses to run 7.x sysnand.

An no, I am not running 7.0.0.

 

[pLaYeR^^]

Yes, because the way they were implementing emunand was broken when 7.0 came out.

Because the way they implemented it earlier, they were getting some FW data from sysnand to use in emunand.

BUT now, to run 7.0 sysnand, you STILL have to use the official bootloader, because you can't use a custom bootloader to load OFW/CFW/or any variation thereof without having all the keys (and if they're already known, then we'd have a 7.0 CFW).

So you still have to burn your fuses to run 7.x sysnand.

If your 100% sure, why ask?

 

[bundat]

If your 100% sure, why ask?

No I was not 100% sure it's like that now for 7.x.
BUT I AM 100% sure it WAS like that for earlier versions.

As this has already come up as an issue for me in the past, when 6.2 first came out, and there were no CFWs yet.

Which I asked here:

Would adding the ability to boot stock 6.2 be possible?
Or would it also require the keys (i.e. also have to wait for TSEC re or userland exploit like any CFW)?

In case someone wants to boot stock 6.2 (to access eShop, or even play online), but wants to preserve fuses (also to be able to downgrade to a CFW-capable FW version).

And I got this response.

the same obstacle blocks all loading from custom bootloaders, regardless of stock or CFW

I am not 100% sure because THINGS CAN CHANGE.

CTCaer (dev of the current Hekate fork) once said "sleep mode being broken with incorrect number of fuses can't be patched" here:
https://gbatemp.net/threads/switch-...tore-crashes-after-sleep.519091/#post-8301468

Yet here we are, Hekate 4.6 and SX OS 2.5 fixed that.

I was TOTALLY HOPING what you were posting was also something new that had changed from what I had last known, and that it was actually something you had tested out yourself.

 

[pLaYeR^^]

No I was not 100% sure it's like that now for 7.x.
BUT I AM 100% sure it WAS like that for earlier versions.

As this has already come up as an issue for me in the past, when 6.2 first came out, and there were no CFWs yet.

Which I asked here:


And I got this response.


I am not 100% sure because THINGS CAN CHANGE.

CTCaer (dev of the current Hekate fork) once said "sleep mode being broken with incorrect number of fuses can't be patched" here:
https://gbatemp.net/threads/switch-...tore-crashes-after-sleep.519091/#post-8301468

Yet here we are, Hekate 4.6 and SX OS 2.5 fixed that.

I was TOTALLY HOPING what you were posting was also something new that had changed from what I had last known, and that it was actually something you had tested out yourself.

The best is to test it out yourself since you can restore backup if it doesn’t work...

 

[bundat]

The best is to test it out yourself since you can restore backup if it doesn’t work...

Backing up your nand and restoring a nand backup takes almost an hour each.

I'm not about to waste several hours trying out something I know doesn't work in previous fw versions.

I've managed to get by just by going on information I know is 100% correct (and tested myself) and avoiding all misinformation just fine, I still have 5 burned fuses, 6.2 fw installed, and not banned from online. Thanks.

 

[pLaYeR^^]

Backing up your nand and restoring a nand backup takes almost an hour each.

I'm not about to waste several hours trying out something I know doesn't work in previous fw versions.

I've managed to get by just by going on information I know is 100% correct (and tested myself) and avoiding all misinformation just fine, I still have 5 burned fuses, 6.2 fw installed, and not banned from online. Thanks.

So you want other people to test it but not yourself?

 

[bundat]

So you want other people to test it but not yourself?

No I am relying on accurate information provided by people who actually know what they're doing, like scene devs. Instead of wasting hours doing things that I have no idea how it works.

What are you even trying to argue about here?
It'd be great if you'd just admit that the misinformation you posted about being able to boot 7.x without using the official bootloader was wrong.