Hacking Mistakenly updated Sysnand to 9.2 with ChoiDujourNX, only have 8.0 Backup

[Advanced User]

No idea how it happened. Unfortunately I only have a clean sysnand backup of 8.0. I suppose I can't restore it since the efuses are now burned and the system is stuck on 9.2.0? Am I screwed?
Is there any way to update my old clean sysnand image to 9.2 so I can go online without getting banned?

 

[Advanced User]

Sorry for answering my own question but I think this is the solution: https://gbatemp.net/threads/burned-fuses-by-mistake-clean-nand-backup-is-of-lower-fw.519685/
So Hekate can ignore the fuse count, and I can restore my clean backup, then upgrade to 9.2.0 using the official method.

 

[BaamAlex]

Why a downgrade? All cfw's work on the latest firmware. No need to do that.

 

[Advanced User]

I think you misunderstood. I used a CFW and ChoiDujourNX on my sysnand by mistake (instead of my emuMMC), meaning it is no longer clean, which would lead to a ban if I went online. Anyway, I solved it. I used Hekate to restore my clean, lower firmware backup to my sysnand. And thanks to Hekate it is possible to boot the lower firmware despite blown fuses, meaning I can now update the once again CLEAN sysnand to 9.2.0 using the official way (without risking a ban).
The lesson here: Backups are invaluable! Thankfully I had one.

 

[satan89]

I think you misunderstood. I used a CFW and ChoiDujourNX on my sysnand by mistake (instead of my emuMMC), meaning it is no longer clean, which would lead to a ban if I went online. Anyway, I solved it. I used Hekate to restore my clean, lower firmware backup to my sysnand. And thanks to Hekate it is possible to boot the lower firmware despite blown fuses, meaning I can now update the once again CLEAN sysnand to 9.2.0 using the official way (without risking a ban).
The lesson here: Backups are invaluable! Thankfully I had one.

Firstly, booting sysnand in CFW and using choinx will not make your sysnand unclean. There's almost no risk of ban

Secondly, updating with choi will not burn your fuses, so if you haven't updated officially, your fuse count is still what it was before you updated with choidujour, as long as you kept autorcm and hekate so it didn't directly boot into sysnand.

 

[BaamAlex]

updating with choi will not burn your fuses

If you don't enable autorcm, it will do exactly this. Only enabling autorcm is the only way to definitely NOT burn your fuses. Or you boot your console only in cfw.