Hacking Quick check about fuses before I FW upgrade

OriginalCopycat · Aug 5, 2021

Hi,

So I've just moved to Atmosphere and want to double check before I do something silly.

I'm booting via Hekate to AMS using EmuNAND (hidden partition). Currently both sysNAND and emuNAND are on 10.2.

I'm using SX Core, so really conscious about upgrading my FW beyond 11.0.

My question is: If I boot emuNAND and use Daybreak to upgrade to 12.x, this will not burn fuses and I can still boot sysNAND as 10.2, right? As I understand it, anything I do in emuNAND will not affect, or be visible to, SysNAND.

Anything else I need to bear in mind?

Thanks!

Kallrkyle · Aug 5, 2021

That is correct

laramie · Aug 5, 2021

OriginalCopycat said:
Hi,

So I've just moved to Atmosphere and want to double check before I do something silly.

I'm booting via Hekate to AMS using EmuNAND (hidden partition). Currently both sysNAND and emuNAND are on 10.2.

I'm using SX Core, so really conscious about upgrading my FW beyond 11.0.

My question is: If I boot emuNAND and use Daybreak to upgrade to 12.x, this will not burn fuses and I can still boot sysNAND as 10.2, right? As I understand it, anything I do in emuNAND will not affect, or be visible to, SysNAND.

Anything else I need to bear in mind?

Thanks!

Also if you are using an old switch model you should be good to update with daybreak, if you are using a modchip with a new model and used choi to update using daybreak will corrupt your boot0 and boot1

M7L7NK7 · Aug 5, 2021

Fuses only get burnt if you are on a higher firmware and let it boot normally, if you use any CFW it won't burn them

OriginalCopycat · Aug 5, 2021

Milenko said:
Fuses only get burnt if you are on a higher firmware and let it boot normally, if you use any CFW it won't burn them

Sorry - I don't understand what you mean - I WILL be on a higher firmware (in EmuNAND), and I DO want to be able to boot into OFW. Aren't you saying that if I do boot into OFW the fuses will then burn?

What do you mean by "boot normally"? I'm using SX Core modchip, so as far as I'm aware there is no way for me to boot "normally" - I must use a custom bootloader (Hekate/SX Gear or SXOS). If I boot OFW via Hekate, am I not protected from burns?

Thanks

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

laramie said:
Also if you are using an old switch model you should be good to update with daybreak, if you are using a modchip with a new model and used choi to update using daybreak will corrupt your boot0 and boot1

Thanks:

1) Yes, I'm on Mariko, using SX Core modchip.
2) Yes, I did update (only my EmuNAND, not SysNAND) using Choi, but I've dumped my SysNAND's Boot0/1 using Hekate and restored these to my EmuNAND using NXNandManager, so I HOPE they're ok now.

So I believe that's ok?

M7L7NK7 · Aug 5, 2021

But normally as in with Nintendo's bootloader, the others are fine

RichardTheKing · Aug 5, 2021

I don't use Daybreak or choi or whatever; I just use emuMMC for my CFW, and whenever I do update I do it through the Settings menu (whilst still on CFW). That updates my emuMMC, but when I do occasionally end up having to turn my Switch off the regular sysNAND version still works perfectly fine, except for not being able to use the gamecard slot, despite being on a significantly older firmware.

So yeah, I just don't see any point in using Daybreak or choi, when stuff on my launch-model Switch works perfectly fine without 'em.

OriginalCopycat · Aug 5, 2021

RichardTheKing said:
I don't use Daybreak or choi or whatever; I just use emuMMC for my CFW, and whenever I do update I do it through the Settings menu (whilst still on CFW). That updates my emuMMC, but when I do occasionally end up having to turn my Switch off the regular sysNAND version still works perfectly fine, except for not being able to use the gamecard slot, despite being on a significantly older firmware.

You mean you're updating your EmuNAND using official OTA update? Isn't that a massive ban risk?

laramie · Aug 5, 2021

OriginalCopycat said:
You mean you're updating your EmuNAND using official OTA update? Isn't that a massive ban risk?

Only if you have custom/pirated nsp's, I also use this option if and when Daybreak just won't work. I've only been banned on one console and it was because I disabled wifi but by letting someone play with it they ended up updating some stuff which banned me. I did have customs nsp's but no pirated stuff.

RichardTheKing · Aug 5, 2021

OriginalCopycat said:
You mean you're updating your EmuNAND using official OTA update? Isn't that a massive ban risk?

I dunno, I can still use the eShop just fine, and I've been doing what I wrote before for years now.

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

laramie said:
Only if you have custom/pirated nsp's, I also use this option if and when Daybreak just won't work. I've only been banned on one console and it was because I disabled wifi but by letting someone play with it they ended up updating some stuff which banned me. I did have customs nsp's but no pirated stuff.

As for custom/pirated NSPs, I don't have any o' that. Don't see the point, on the Switch, so that probably helps me too.

And it's not like I'm ever going to get a bloody Switch Online subscription - fuck dat paywall - so even if I do eventually get banned I'll just not get to use the eShop. Annoying, especially for those rare download-exclusive titles, but not end-of-the-world; this ain't a disc-less PS5.

laramie · Aug 5, 2021

OriginalCopycat said:
Sorry - I don't understand what you mean - I WILL be on a higher firmware (in EmuNAND), and I DO want to be able to boot into OFW. Aren't you saying that if I do boot into OFW the fuses will then burn?

What do you mean by "boot normally"? I'm using SX Core modchip, so as far as I'm aware there is no way for me to boot "normally" - I must use a custom bootloader (Hekate/SX Gear or SXOS). If I boot OFW via Hekate, am I not protected from burns?

Thanks

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

Thanks:

1) Yes, I'm on Mariko, using SX Core modchip.
2) Yes, I did update (only my EmuNAND, not SysNAND) using Choi, but I've dumped my SysNAND's Boot0/1 using Hekate and restored these to my EmuNAND using NXNandManager, so I HOPE they're ok now.

So I believe that's ok?

depending if Nintendo updated the firmware update you'd like to use on the switch, it is possible that atmosphere will throw an error on boot saying error with boot zero and boot one.

OriginalCopycat · Aug 5, 2021

laramie said:
depending if Nintendo updated the firmware update you'd like to use on the switch, it is possible that atmosphere will throw an error on boot saying error with boot zero and boot one.

Oh, you mean the Boot(s) I've dumped from my 10.2 SysNAND and injected into my EmuNAND may not work once I update the EmuNAND to 12.x? Surely Daybreak also updates the Boot0/1 if the FW upgrade requires it to, no?

laramie · Aug 5, 2021

OriginalCopycat said:
Oh, you mean the Boot(s) I've dumped from my 10.2 SysNAND and injected into my EmuNAND may not work once I update the EmuNAND to 12.x? Surely Daybreak also updates the Boot0/1 if the FW upgrade requires it to, no?

Daybreak will update them but you'd need to boot 10.2 and update it with daybreak to 12.x. If you boot with a lower boot(s) atmosphere will panic. (lower boots with newer firmwares that had boot(s) updated)

OriginalCopycat · Aug 5, 2021

laramie said:
Daybreak will update them but you'd need to boot 10.2 and update it with daybreak to 12.x. If you boot with a lower boot(s) atmosphere will panic. (lower boots with newer firmwares that had boot(s) updated)

I think I understand you, but correct me if I go wrong....

I am currently 10.2 on both SysNAND and EmuNAND. Because I've nuked EmuNAND's Boots with Choi I've replaced its Boots with ones from my SysNAND. Therefore I currently have 10.2 on both (emu/sys) and both have working Boots.

Once I boot into EmuNAND, via Hekate and AMS, I'll use Daybreak to upgrade EmuNAND to 12.x. This will (if needed) update the Boots (but only on EmuNAND). I will then have SysNAND on 10.2 (with 10.2 Boots) and EmuNAND on 12.x (with 12.x boots).

Both should continue to work fine, with no knowledge of eachother and no "panics", right?

laramie · Aug 5, 2021

OriginalCopycat said:
I think I understand you, but correct me if I go wrong....

I am currently 10.2 on both SysNAND and EmuNAND. Because I've nuked EmuNAND's Boots with Choi I've replaced its Boots with ones from my SysNAND. Therefore I currently have 10.2 on both (emu/sys) and both have working Boots.

Once I boot into EmuNAND, via Hekate and AMS, I'll use Daybreak to upgrade EmuNAND to 12.x. This will (if needed) update the Boots (but only on EmuNAND). I will then have SysNAND on 10.2 (with 10.2 Boots) and EmuNAND on 12.x (with 12.x boots).

Both should continue to work fine, with no knowledge of eachother and no "panics", right?

Depends on how you updated both sysnand and emunand, if both were updated at any point with choi they are borked. SX core and lite just repatch the boots after to work. Other than that yeah, if you know you have a clean backup, you could restore it to emunand then update with daybreak (backup must not include any updates using choi). If you'd like different firmwares than i'd suggest restoring a clean backup, updating emunand to 10.2, dumping that, restore that dump to sysnand then boot emunand again and update to 12.x. Also maybe backup emunand if you care for anything currently on it.
@OP I did find this as well, I've never used this method but ScriesM did use my messed up boot0 and boot1 files and sent them back to me privately. I watched the video and can't again confirm this sorry but maybe SciresM manually edited my files and now there is a tool. I'd recommend since in the video the user ends up with exFAT which isn't stable so I'd recommend updating with daybreak afterwords and selecting FAT32 instead. I hope this helps as it is much quicker than what I mentioned above!
https://www.sthetix.info/generating-a-fresh-boot0-from-scratch-fix-your-switch-now/

laramie · Aug 5, 2021

@OP, idk if the edits notify you so I'm tagging as well! @OriginalCopycat

OriginalCopycat · Aug 5, 2021

laramie said:
Depends on how you updated both sysnand and emunand, if both were updated at any point with choi they are borked. SX core and lite just repatch the boots after to work. Other than that yeah, if you know you have a clean backup, you could restore it to emunand then update with daybreak (backup must not include any updates using choi). If you'd like different firmwares than i'd suggest restoring a clean backup, updating emunand to 10.2, dumping that, restore that dump to sysnand then boot emunand again and update to 12.x. Also maybe backup emunand if you care for anything currently on it.
@OP I did find this as well, I've never used this method but ScriesM did use my messed up boot0 and boot1 files and sent them back to me privately. I watched the video and can't again confirm this sorry but maybe SciresM manually edited my files and now there is a tool. I'd recommend since in the video the user ends up with exFAT which isn't stable so I'd recommend updating with daybreak afterwords and selecting FAT32 instead. I hope this helps as it is much quicker than what I mentioned above!
https://www.sthetix.info/generating-a-fresh-boot0-from-scratch-fix-your-switch-now/

@laramie Thanks - I'm pretty sure my SysNAND's Boots are fine as I never updated SysNAND with Choi, only EmuNAND. I only ever updated SysNAND OTA as I've only ever used OFW with SysNAND.

Also, that video link you sent (great vid, btw - thanks) says "PSA : This guide will only fix the SYSNAND, not the EMUNAND.", just below the video. I wonder if that's because he restored the BOOT0/1 to eMMC and not to emuMMC?

Thanks!

laramie · Aug 5, 2021

OriginalCopycat said:
@laramie Thanks - I'm pretty sure my SysNAND's Boots are fine as I never updated SysNAND with Choi, only EmuNAND. I only ever updated SysNAND OTA as I've only ever used OFW with SysNAND.

Also, that video link you sent (great vid, btw - thanks) says "PSA : This guide will only fix the SYSNAND, not the EMUNAND.", just below the video. I wonder if that's because he restored the BOOT0/1 to eMMC and not to emuMMC?

Thanks!

I'd just use sysnand then no worries

Yeah that video is all I could really find at 4am well that's all I could find at all. It might be true with that PSA but you could easily do it to sysnand then inject it into emunand if on the same firmware. I thought I'd mention it since once we get you squared away others can reference the thread incase they are experiencing the same problems.

Let us know what fixes or doesn't work for reference. Heading to sleep but Good luck! Glad I could help any way I could!

OriginalCopycat · Aug 5, 2021

laramie said:
I'd just use sysnand then no worries Yeah that video is all I could really find at 4am well that's all I could find at all. It might be true with that PSA but you could easily do it to sysnand then inject it into emunand if on the same firmware. I thought I'd mention it since once we get you squared away others can reference the thread incase they are experiencing the same problems. Let us know what fixes or doesn't work for reference. Heading to sleep but Good luck! Glad I could help any way I could!

Thank you for your help - forgot you were in a totally different timezone haha - hope you sleep well.

Cheers!

Hacking Quick check about fuses before I FW upgrade

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Honestly XC2>XC3...

Well-Known Member

Well-Known Member

Honestly XC2>XC3...

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum