Hacking 8.0.1- 6 burnt fuses. I Want to restore a Clean NAND backup to use EmuMMC. Am i in trouble?

[Roxasorg13]

Hi! how are you?
I have a switch on 8.0.1 and i use AutoRCM, but before i updated my switch version i didnt use AutoRCM, so i booted to OFW and burnt fuses, right now my counter is at 6.
I want to use EmuMMC (maybe right now, maybe in the next couple of weeks/months when there is a simpler way to do it) but i want to know if i will be able to do it.
I have a Clean NAND backup, the thing is i dont remember if the backup is from 4.0-4.1 or from 5.0 (is there a way to check that)
So. assuming the absolute worst case scenarios (the backup is from 3.0-4.1 will i be able to restore mi NAND backup? or am i screwed because of my burnt fuses?

Im sorry if this is a dumb question, but i tried to do some research and im just getting more and more confused.

 

[Lacius]

Hi! how are you?
I have a switch on 8.0.1 and i use AutoRCM, but before i updated my switch version i didnt use AutoRCM, so i booted to OFW and burnt fuses, right now my counter is at 6.
I want to use EmuMMC (maybe right now, maybe in the next couple of weeks/months when there is a simpler way to do it) but i want to know if i will be able to do it.
I have a Clean NAND backup, the thing is i dont remember if the backup is from 4.0-4.1 or from 5.0 (is there a way to check that)
So. assuming the absolute worst case scenarios (the backup is from 3.0-4.1 will i be able to restore mi NAND backup? or am i screwed because of my burnt fuses?

Im sorry if this is a dumb question, but i tried to do some research and im just getting more and more confused.

Any emuNAND version will work regardless of the fuse count. Fuses only matter when it comes to booting the sysNAND without a bootloader like fusee-primary or Hekate.

 

[Roxasorg13]

Any emuNAND version will work regardless of the fuse count. Fuses only matter when it comes to booting the sysNAND without a bootloader like fusee-primary or Hekate.

But i have to restore my cleand nand before the emunand process, right?
idk im so confused, can you help me number the steps needed (in a very simple way so i dont waste your time)?

 

[Lacius]

But i have to restore my cleand nand before the emunand process, right?
idk im so confused, can you help me number the steps needed (in a very simple way so i dont waste your time)?

First, what is your ultimate goal? Are you wanting to play online?

 

[Roxasorg13]

First, what is your ultimate goal? Are you wanting to play online?

Yes, i have a few cartridges i would like to play online. I mean, is not an absolute necessity, but it would be nice to have a good set up that allows me to have the best of both worlds you know?

(Also, My switch hasnt been connected to internet since the day i first installed CFW and my NAND backup is totally clean)

 

[Lacius]

Yes, i have a few cartridges i would like to play online. I mean, is not an absolute necessity, but it would be nice to have a good set up that allows me to have the best of both worlds you know?

(Also, My switch hasnt been connected to internet since the day i first installed CFW and my NAND backup is totally clean)

If you don't care about downgrading and future exploits, I would do the following:

1. Make an emuNAND partition copying your dirty 8.0.1 sysNAND.
2. Restore your clean NAND backup to your sysNAND.
3. Update your clean sysNAND to 8.1.0 through the system settings.
4. On your dirty 8.0.1 emuNAND, keep it offline. Alternatively, install 90DNS and/or Incognito so it never accidentally connects to Nintendo's servers.
5. Update your dirty emuNAND to 8.1.0 using ChoiDujourNX.

This will leave you with a clean sysNAND on 8.1.0 for online play with legitimate games, and you will have a dirty emuNAND on 8.1.0 for hacking and backup-loading.

You can also install AutoRCM if you want to preserve your fuses, if you do care about downgrading in the future. If you want to preserve fuses but don't want to install AutoRCM, you could also setup a second emuNAND that's clean and on 8.1.0 for online play, but that's a lot more complicated and a lot more space.

 

[Roxasorg13]

If you don't care about downgrading and future exploits, I would do the following:

1. Make an emuNAND partition copying your dirty 8.0.1 sysNAND.
2. Restore your clean NAND backup to your sysNAND.
3. Update your clean sysNAND to 8.1.0 through the system settings.
4. On your dirty 8.0.1 emuNAND, keep it offline. Alternatively, install 90DNS and/or Incognito so it never accidentally connects to Nintendo's servers.
5. Update your dirty emuNAND to 8.1.0 using ChoiDujourNX.

This will leave you with a clean sysNAND on 8.1.0 for online play with legitimate games, and you will have a dirty emuNAND on 8.1.0 for hacking and backup-loading.

You can also install AutoRCM if you want to preserve your fuses, if you do care about downgrading in the future. If you want to preserve fuses but don't want to install AutoRCM, you could also setup a second emuNAND that's clean and on 8.1.0 for online play, but that's a lot more complicated and a lot more space.

I think i got the logic of it.
But will i face any problems with the NAND restore? What i mean is: Is fuse count irrelevant to the restore process? Which would be the absolute worst case scenario? Me booting Sysnand via Hetake? That is the only part i dont understand/has me a little afraid.

Also, would you do this process right now? or would you wait a little longer till a easier/more practical solution arrives?

Do you personally have this set up? or you dont mind about EmuNAND right now?

 

[Lacius]

I think i got the logic of it.
But will i face any problems with the NAND restore? What i mean is: Is fuse count irrelevant to the restore process? Which would be the absolute worst case scenario? Me booting Sysnand via Hetake? That is the only part i dont understand/has me a little afraid.

Also, would you do this process right now? or would you wait a little longer till a easier/more practical solution arrives?

Do you personally have this set up? or you dont mind about EmuNAND right now?

The fuse count is irrelevant to the restore process, only the boot process. As long as you make a NAND backup before restoring your old NAND backup, there isn't much of a worst case scenario that's unfixable.

There's no reason not to do this process now. emuNAND is going to become more stable over time, but the setup process isn't going to get any easier.

I don't personally have this setup, since I don't care about online play. I have one dirty sysNAND on 8.1.0 that's kept offline. I also have AutoRCM installed to make entering RCM easier and to prevent my fuses from being burnt (I have 3 burnt fuses).

 

[wolverine92]

As far as I understand it once you restore to your clean NAND since your fuses are burnt you will have to use Hekate to be able to boot to the clean sysNand then update through settings to 8.0.1 then you will no longer need to use Hekate.

I am not sure if using Hekate with burnt fuses to boot to a clean sysNand is safe or not.

 

[Danttebayo]

Hopefully this is on topic and helpful to OP.
One thing I'm not clear on is how to update a 'clean' Emunand to the latest version without burning fuses. I've got a clean backup of my Sysnand at 7.0.1 and however many burnt fuses come with that version. I've been told a good way to do things is to leave Sysnand alone and have both clean and dirty Emunands for their respective purposes.

The question is, if I restore 7.0.1 to a clean Emunand, how do I get it to 8.1.0? I can't use ChoiDuJour because it needs to be clean but if I use the system update on an Emunand will it still burn fuses?

 

[gohan123]

sorry to come in between this thread. I'm thinking to do the same just to have clean sysnand for fortnite for my nephew. but 29gb emunand + 20+gb fortnite is a huge size. so my actual question is: does emunand have to be 29gb or can I make it less? right know on dirty sysnand my nand is almost empty.

 

[OrGoN3]

Hopefully this is on topic and helpful to OP.
One thing I'm not clear on is how to update a 'clean' Emunand to the latest version without burning fuses. I've got a clean backup of my Sysnand at 7.0.1 and however many burnt fuses come with that version. I've been told a good way to do things is to leave Sysnand alone and have both clean and dirty Emunands for their respective purposes.

The question is, if I restore 7.0.1 to a clean Emunand, how do I get it to 8.1.0? I can't use ChoiDuJour because it needs to be clean but if I use the system update on an Emunand will it still burn fuses?

If you boot through Hekate, your efuses will be preserved no matter what you do.

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

sorry to come in between this thread. I'm thinking to do the same just to have clean sysnand for fortnite for my nephew. but 29gb emunand + 20+gb fortnite is a huge size. so my actual question is: does emunand have to be 29gb or can I make it less? right know on dirty sysnand my nand is almost empty.

No, it will not work if you make it less. and 49GB is not a large amount on microSD cards that go up to 1TB.

 

[POONpirate]

Okay so I'm in a very similar situation. I want to use emummc for my dirty cfw backup (on v 6.2 currently) and i want to restore my clean backup (v 5.10) but i have 8 fuses burnt. So my question would how to upgrade my sysnand to where i can boot without to bl panic from too many burnt fuses. Do i just boot ofw through hekate and update like that or do I choidojour the backup before restore? My assumption would be restoring the clean nand and booting ofw with hekate but is this safe?

 

[Danttebayo]

If you boot through Hekate, your efuses will be preserved no matter what you do.

Thank you kindly. I’m going to pick up a 256GB card (fingers crossed for a deal on Prime Day) and then go for it.

 

[Roxasorg13]

Okay so I'm in a very similar situation. I want to use emummc for my dirty cfw backup (on v 6.2 currently) and i want to restore my clean backup (v 5.10) but i have 8 fuses burnt. So my question would how to upgrade my sysnand to where i can boot without to bl panic from too many burnt fuses. Do i just boot ofw through hekate and update like that or do I choidojour the backup before restore? My assumption would be restoring the clean nand and booting ofw with hekate but is this safe?

As far as i understand you have to boot from hetake and update via System settings and you should be safe as long as you enable AutoRCM.
NOTE: I am not sure if you can enable AutoRCM before the restore process without any risk. That is maybe one of the few little doubts i have before doing the process.

Also, do you know if you need a NAND backup to do the EmuMMC? or does it create the Emunand Based on your current SysNAND?

If you boot through Hekate, your efuses will be preserved no matter what you do.

Hey! as i stated before, do you know if i can enable AutoRCM before the update via system settings? My jig is not 100% reliable (heck, i would say it isnt even 33% reliable lol) so i dont want to risk the fuse count if i cant boot hetake in the first try via jig after the update.
I dont really mind about downgrading, but one never knows, i think a 6 fuse count could be useful in the future.

 

[POONpirate]

As far as i understand you have to boot from hetake and update via System settings and you should be safe as long as you enable AutoRCM.
NOTE: I am not sure if you can enable AutoRCM before the restore process without any risk. That is maybe one of the few little doubts i have before doing the process.

I just wouldn't want to go online with 5.1 and 8 burnt fuses and I'd need to go online to update through system settings without a gamecart with an update right?
Why would i want autorcm? I intend to just burn the other two fuses and update my clean ofw to 8.1 and go online so I don't see where autorcm would matter.

Also, do you know if you need a NAND backup to do the EmuMMC? or does it create the Emunand Based on your current SysNAND?

Yeah I do have a nand backup of the nand ive been on cfw with but i also backed up all my saves through checkpoint so if it makes a emunand off my sysnand without my saves I'll leave it like that and restore my saves.

 

[Sayern]

I think enabling AutoRCM is not safe if you want to go online and avoid ban (it could leave traces on sysnand)
Also booting ofw with hekate to avoid burnt fuse seems ok (better have confirmation from someone with more experience)
Have a trustful jig or let your fuses burn. I don't see the point to downgrade in the future but who knows?
Maybe for new exploits with warm boot? Cold boot with fusée gelée is fine and everyone is going forward with that.
I still preserve my fuses I'm not using emunand and I don't plan going online on ofw atm

 

[Lacius]

I think enabling AutoRCM is not safe if you want to go online and avoid ban (it could leave traces on sysnand)
Also booting ofw with hekate to avoid burnt fuse seems ok (better have confirmation from someone with more experience)
Have a trustful jig or let your fuses burn. I don't see the point to downgrade in the future but who knows? I still preserve mine i'm not using emunand and i'm not going online on ofw atm

AutoRCM is highly unlikely to cause a ban. BCT verification occurs outside of Horizon.

 

[OrGoN3]

As far as i understand you have to boot from hetake and update via System settings and you should be safe as long as you enable AutoRCM.
NOTE: I am not sure if you can enable AutoRCM before the restore process without any risk. That is maybe one of the few little doubts i have before doing the process.

Also, do you know if you need a NAND backup to do the EmuMMC? or does it create the Emunand Based on your current SysNAND?


Hey! as i stated before, do you know if i can enable AutoRCM before the update via system settings? My jig is not 100% reliable (heck, i would say it isnt even 33% reliable lol) so i dont want to risk the fuse count if i cant boot hetake in the first try via jig after the update.
I dont really mind about downgrading, but one never knows, i think a 6 fuse count could be useful in the future.

Yes, you can enable AutoRCM before updating via system settings, but doing so will also remove AutoRCM. So you need to make sure to re-enable it right after the update.

I don't think 6 fuses would be useful for anything in the future. Deja Vu is already out (in the form of Caffeine), and it still requires a tether (aka WLAN host/access point). Persistent coldboot won't happen on 4.1+. 6 fuses is 5.0+. In my opinion, I wouldn't bother keeping them.

 

[Roxasorg13]

Yes, you can enable AutoRCM before updating via system settings, but doing so will also remove AutoRCM. So you need to make sure to re-enable it right after the update.

I don't think 6 fuses would be useful for anything in the future. Deja Vu is already out (in the form of Caffeine), and it still requires a tether (aka WLAN host/access point). Persistent coldboot won't happen on 4.1+. 6 fuses is 5.0+. In my opinion, I wouldn't bother keeping them.

Yeah, i was thinking the same. Also, as it is an unpatched unit i guess the jig exploit is quite unpatcheable lol. Do you know if i have to make an Extra NAND backup to create EmuMMC or does it creates itself from the current SysNAND?

Also, huge thanks to @Lacius , his help has been extremely helpful over the last few days and he sure knows his sh*t about this scene. Teached me a couple of useful things