Hacking Can I still use SD Emunand 6.1 if I update my Sysnand to 6.2?

[Aniblaze]

Hi guys, relatively new to emunand, so I was wondering if emunand checks the burned fuses if I were to update my sysnand to 6.2. Has anybody tried doing this?

 

[Kubas_inko]

To boot to EmuNAND, you need to boot thru RCM, so you will bypass the fuse check.

 

[Fafner]

I saw a post in the Darkumbra forum stating that 6.2.0 won't let you access your CFW anymore. Can't see how it could do this, it could just be a fake, but I prefer to wait just a bit

 

[Kubas_inko]

I saw a post in the Darkumbra forum stating that 6.2.0 won't let you access your CFW anymore. Can't see how it could do this, it could just be a fake, but I prefer to wait just a bit

New way of generating keys.

 

[Fafner]

Don't know what this exactly means but I guess it's nothing nice

 

[Bedel]

Hi guys, relatively new to emunand, so I was wondering if emunand checks the burned fuses if I were to update my sysnand to 6.2. Has anybody tried doing this?

You should be able since, as stated before, RCM bypass the fusee check. This means: as long as you can lunch the CFW with RCM, you can lunch any version you want, not depending in wich was the last firmware installed in your console.
Still, I'd wait for further confirmation (someone who tries it out)

 

[Deleted-188346]

You should be able since, as stated before, RCM bypass the fusee check. This means: as long as you can lunch the CFW with RCM, you can lunch any version you want, not depending in wich was the last firmware installed in your console.
Still, I'd wait for further confirmation (someone who tries it out)

Yep, I'm able to boot into my SD emuNAND on 5.x with my clean NAND on 6.2.

To anyone with AUTORCM: Booting into "original firmware" with SX OS results in a black screen though, so AUTORCM isn't very helpful right now with SX OS.

 

[x7l7j8cc]

yes, im using Original NAND with 6.2 , and SD EmuNAND 6.1 ...
i dont use autorcm, so if i want to boot original, i just switch on. if i want sxos i do the rcm everytime and boot CFW with EmuNAND.

 

[Fafner]

6.2? Isn't 6.2 blocking all CFWs around? These are the voices which are spreading around in these hours.
Or do they mean you can't actually have a 6.2 CFW (with Emunand or whatever else) but you can boot into your 6.1 CFW?
I'm confused about being able to update the OFW to 6.2 without making SX Pro useless.

 

[Kubas_inko]

6.2? Isn't 6.2 blocking all CFWs around? These are the voices which are spreading around in these hours.
Or do they mean you can't actually have a 6.2 CFW (with Emunand or whatever else) but you can boot into your 6.1 CFW?
I'm confused about being able to update the OFW to 6.2 without making SX Pro useless.

But if you are not booting to 6.2.0, how can it block anything?
EmuNAND 100% does not care about your SysNAND.

 

[xs4all]

You should be able since, as stated before, RCM bypass the fusee check. This means: as long as you can lunch the CFW with RCM, you can lunch any version you want, not depending in wich was the last firmware installed in your console.
Still, I'd wait for further confirmation (someone who tries it out)

All this lunch talk is making me hungry

 

[DaveLister]

All this lunch talk is making me hungry

Starving . It's still breakfast.

 

[wurstpistole]

I saw a post in the Darkumbra forum stating that 6.2.0 won't let you access your CFW anymore. Can't see how it could do this, it could just be a fake, but I prefer to wait just a bit

6.2? Isn't 6.2 blocking all CFWs around? These are the voices which are spreading around in these hours.

New way of generating keys.

This is the exact same situation for almost every FW update. Couldn't boot CFW on 6.0 either right at first. Woke up next morning, SX OS update, everything working again.
The keys leak a few hours after a fw releases, CFWs are updated, everything works again. If you can stop yourself from updating THE VERY SECOND a new fw. hits, then you'll be fine anyway.

 

[The Real Jdbye]

You should be able since, as stated before, RCM bypass the fusee check. This means: as long as you can lunch the CFW with RCM, you can lunch any version you want, not depending in wich was the last firmware installed in your console.
Still, I'd wait for further confirmation (someone who tries it out)

Don't eat your Switch, it tastes bad.

 

[Kubas_inko]

This is the exact same situation for almost every FW update. Couldn't boot CFW on 6.0 either right at first. Woke up next morning, SX OS update, everything working again.
The keys leak a few hours after a fw releases, CFWs are updated, everything works again. If you can stop yourself from updating THE VERY SECOND a new fw. hits, then you'll be fine anyway.

Nope this is for the first time ninty has implemented something like this. A whole new way of generating the keys.

 

[wurstpistole]

Nope this is for the first time ninty has implemented something like this. A whole new way of generating the keys.

Yet still we will have working 6.2 CFW in a matter of hours, days tops.

 

[Kubas_inko]

Yet still we will have working 6.2 CFW in a matter of hours, days tops.

I am not saying we won't.

 

[Hayato213]

Don't eat your Switch, it tastes bad.

They can try licking switch game cartridge.

 

[Bedel]

Don't eat your Switch, it tastes bad.

All this lunch talk is making me hungry

Lmao didn't even saw it. I was just letting my phone keyboard write for me most of that post. Sorry about that, but as it seems so funny, I won't correct it xD

 

[arianadark]

DO NOT UPDATE TO 6.2