Hacking Burned fuses by mistake, clean nand backup is of lower fw

[DbGt]

Probably theres nothing i can do, but I have a clean nand backup of fw 4.1, i updated my switch long time ago using rajikosto method (long guide) to 5.1, had only 5 burned fuses.

I took a long flight with my switchs (autorcm) battery completely drained, i tried charging the switch with the planes power outlets but it was not charging at all, i was in fact losing charge (i was checking with hekate, had about 1% of battery).

I figured that maybe if i removed autorcm with hekate, the switch will charge normally. So i did that but only got my switch to burn the 4.1 fuses. The switch didnt charged normally, I couldnt charged it during the flight, I also never boot to horizon nor i was able to use the switch during the flight, but now i have 6 burned fuses.

I got somewhat annoyed as i have read a lot and thought i knew what i was doing. After thinking about it all, i dont care too much about burned fuses but i do care about my clean nand backup

is there something i could do?? could i edit my clean backup and change its fw from 4.1 to 5.1? so i can use it and restore it if necessary? Is my backup useless now?

how could i create another clean nand backup?

 

[asnka]

did you leave it in the dock charging over night yet?
I have had autorcm battery problems twice...and an over night dock charge fixed it..

 

[DbGt]

did you leave it in the dock charging over night yet?
I have had autorcm battery problems twice...and an over night dock charge fixed it..

I already fixed that and i have recovered a few times from a dead battery with autorcm

my problem is another, i burned my switch fuses by mistake and my clean nand backup is of a lower fw, i am asking if theres anything i could do to still be able to use this clean backup

 

[xabier]

Restore your backup, boot ofw with hekate(rcm) so it ignores the fuses, then update to a versión that match your fuse count with a game cart or just go online and update.

Another option is using choidujour, but its riskier ban wise because it involves cfw.

Once you update to a fw with the same fuse count number than your hardware you wont need hekate, if you update to a version with more burned fuses it will burn them and boot normally without the need of RCM.

 

[bundat]

• Restore your clean 4.1 NAND backup
• Boot using Hekate's "stock" option, which skips the fuse check (Personally, I'd just boot Hekate without the SD card inserted, to be 100% sure I don't have a "dirty" Nintendo folder)
• I'd then update using an "official" method (either directly to 6.0 using OFW update, or to 5.1 using an actual cartridge). Because ChoiDujourNX needs CFW and HB Loader, I personally don't want to use those when making my "clean" NAND backup
• Then make a new NAND backup after updating

EDIT: Ninja'd @xabier

 

[asnka]

I already fixed that and i have recovered a few times from a dead battery with autorcm

my problem is another, i burned my switch fuses by mistake and my clean nand backup is of a lower fw, i am asking if theres anything i could do to still be able to use this clean backup

As far as i know....youre boned..sorry..

 

[Ericthegreat]

As far as i know....youre boned..sorry..

No he's fine, he might have to update though.

 

[asnka]

No he's fine, he might have to update though.

the switch scene just moves too fast for this old man....sorry about the misinfo...
just so i know....he cant use his clean nand backup with the burned fuses right?

 

[bundat]

just so i know....he cant use his clean nand backup with the burned fuses right?

Hekate can skip the fuse check.
Sleep mode is broken though if you have too many burned fuses, so it's only good for restoring an old clean NAND backup that you will update.

 

[DbGt]

Restore your backup, boot ofw with hekate(rcm) so it ignores the fuses, then update to a versión that match your fuse count with a game cart or just go online and update.

Another option is using choidujour, but its riskier ban wise because it involves cfw.

Once you update to a fw with the same fuse count number than your hardware you wont need hekate, if you update to a version with more burned fuses it will burn them and boot normally without the need of RCM.

• Restore your clean 4.1 NAND backup
• Boot using Hekate's "stock" option, which skips the fuse check (Personally, I'd just boot Hekate without the SD card inserted, to be 100% sure I don't have a "dirty" Nintendo folder)
• I'd then update using an "official" method (either directly to 6.0 using OFW update, or to 5.1 using an actual cartridge). Because ChoiDujourNX needs CFW and HB Loader, I personally don't want to use those when making my "clean" NAND backup
• Then make a new NAND backup after updating

EDIT: Ninja'd @xabier

Thank you very much for your help! wow didnt knew this was possible, i thought i was screwed

So, whats the point of doing a new clean nand backup if I still can use the one i have???

I dont have any game cart except for mario odyssey, so my only option would be to update by connecting online. But i would prefer not to burn more fuses, and I still dont see the need to update to 6.0

So, can i just keep my old clean backup and continue like nothing happened?

 

[bundat]

So, whats the point of doing a new clean nand backup if I still can use the one i have???

When using Hekate to boot a lower firmware (which requires less burned fuses than you have), sleep mode is broken, and when the Switch goes to sleep, it crashes:
https://gbatemp.net/threads/switch-...tore-crashes-after-sleep.519091/#post-8301468

Also, "continuity" is what matters most to Nintendo's logging, it seems. It's not only about having a "clean" NAND.
i.e. if some logs your Switch sent in the past suddenly go missing, it means you did something questionable to get rid of those logs.
So personally, I make a new NAND backup every time I go "off the grid" (i.e. going from online, then deleting my wifi settings)
And also after each update.

Of course, you don't have to do this NOW, but I recommend doing it when you finally want to connect your Switch to wifi.

 

[DbGt]

When using Hekate to boot a lower firmware (which requires less burned fuses than you have), sleep mode is broken, and when the Switch goes to sleep, it crashes:
https://gbatemp.net/threads/switch-...tore-crashes-after-sleep.519091/#post-8301468

Also, "continuity" is what matters most to Nintendo's logging, it seems. It's not only about having a "clean" NAND.
i.e. if some logs your Switch sent in the past suddenly go missing, it means you did something questionable to get rid of those logs.
So personally, I make a new NAND backup every time I go "off the grid" (i.e. going from online, then deleting my wifi settings)
And also after each update.

Of course, you don't have to do this NOW, but I recommend doing it when you finally want to connect your Switch to wifi.

I see, thanks. I use my switch completely offline, Im only interested in the clean backup in case I somehow screw up the switch. At the moment im not interested at all in playing online or connecting the switch online.

I will then keep my old clean backup for now as my main backup, thank again

 

[rychii]

Bumping this, I have the exact same issue. I have a clean backup of 4.1, didn't know anything about burning fuses and updated to 7.0 without realizing, then tried to downgrade back. My question is, if I boot into 4.1 using hekate after restoring the nand, and I go online and update officially, will I get banned? Do I need to wipe my logs or something?

 

[Hayato213]

Bumping this, I have the exact same issue. I have a clean backup of 4.1, didn't know anything about burning fuses and updated to 7.0 without realizing, then tried to downgrade back. My question is, if I boot into 4.1 using hekate after restoring the nand, and I go online and update officially, will I get banned? Do I need to wipe my logs or something?

Your fuse is burn so no point of downgrading as you would always have to use a boot loader now to boot.

 

[rychii]

Your fuse is burn so no point of downgrading as you would always have to use a boot loader now to boot.

Thing is I already downgraded and I've tried using the sdsetup instructions to help but with no avail. My problem is upgrading back to 7.0-7.01

 

[Hayato213]

Thing is I already downgraded and I've tried using the sdsetup instructions to help but with no avail. My problem is upgrading back to 7.0-7.01

Your fuse is burn so you wouldn't be able to boot into OFW without a bootloader, as for updating back into 7.0.1 you can use ChoidujourNX if you can boot into CFW.

 

[rychii]

Your fuse is burn so you wouldn't be able to boot into OFW without a bootloader, as for updating back into 7.0.1 you can use ChoidujourNX if you can boot into CFW.

I'm unable to boot into any bootloader, however when I pushed the sxos payloader, it booted into OFW, I'm just wondering if i go online to update, would I get banned or not

 

[Hayato213]

I'm unable to boot into any bootloader, however when I pushed the sxos payloader, it booted into OFW, I'm just wondering if i go online to update, would I get banned or not

Probably will get ban as it is not a clean nand.