I would try to load your backup. boot1/2 and sys partition.So if I still have 8, then it's not that risky?
I would try to load your backup. boot1/2 and sys partition.So if I still have 8, then it's not that risky?

yes as long as you can still boot RCM you can restore a backup. You will just need to restore boot0/1 as wellIt is a damn shame to post this thread, with this subject but it happened.
My console was updated, to blame anyone in my family would be stupid as I had time to prevent this from happening, anyway, I just want to ask... I have a backup that I made in 12/30/18, 6.2 and I use Kosmos CFW, and I wanted to restore my backup with hekate.
Don't really know much about fuses and that stuff so I wanted to know what risks I have in restoring it from the latest firmware...
Again I am terribly sorry to ask for help with this stupid issue but I really appreciate your help in responding my questions...
dont fking do it, I JUST BRICKED MY SWITCH OH MY FUK GOD
You never know, maybe it won't be too long.It is a damn shame to post this thread, with this subject but it happened.
My console was updated, to blame anyone in my family would be stupid as I had time to prevent this from happening, anyway, I just want to ask... I have a backup that I made in 12/30/18, 6.2 and I use Kosmos CFW, and I wanted to restore my backup with hekate.
Don't really know much about fuses and that stuff so I wanted to know what risks I have in restoring it from the latest firmware...
Again I am terribly sorry to ask for help with this stupid issue but I really appreciate your help in responding my questions...
Hmm. Seems that nobody mentioned this.
You can downgrade to/restore older versions but you would need to boot through bootloader which bypasses fuze check. If you have proper files for restoration, go ahead and restore, but first do a new backup.
Exactly this!
In the worse case scenario you'll have your ver 7 backup.
I can confirm, only downgrading to 6.2.0 is broken.
6.1.0 and lower are "safe" because they don't use the TSEC.
I'm on 7.0.0 with burned efuses and 6.1.0 emunand...
Can you boot in OFW with hekate now?Yet I downgraded to 6.2? *thonk* lemme try again
EDIT: I upgraded to 7.0 now have 9 burnt fuses, downgraded back to 6.2 using hekate. Booted CFW fine using both Hekate and ReiNX.bin
When I restored my backup I restored boot 0/1 as well.
Thanks
Can you boot in OFW with hekate now?
But with official nintendo bootloader it won't work right?Yep, booted fine into OFW from hekate
But with official nintendo bootloader it won't work right?
I don't get why people think that a NAND backup would brick your Switch if you restore it? It doesn't!
If your fuse count is wrong it only means you'll have to boot via hekate (custom bootloader everytime).
If you used Choixdujour, this does not even apply!
sometimes you need to restore boot0/1 as well, and if you don't have those that's when issues arise
Yep! That's what would make a complete NAND backup no?
Why bakcup 29 GB and only leave out a few bytes?
PSA: Boot0/1 are part of the backup process (has always been!)
Yet I downgraded to 6.2? *thonk* lemme try again
EDIT: I upgraded to 7.0 now have 9 burnt fuses, downgraded back to 6.2 using hekate. Booted CFW fine using both Hekate and ReiNX.bin
When I restored my backup I restored boot 0/1 as well.
Thanks
Nice news..
I'm with SXOS and emunand 6.2.0 don't work so I assumed that 6.2.0 OFW won't boot.
So, SXOS seems to have the key embebbed and hekate/Atmosphere extract it from TSEC...