- Dec 24, 2012
- 6
- 1
Hello, this evening I upgraded emunand from v6.0.1 to v8.0.1 using ChoiDujourNX and kept my system on v6.0.1. Once I restarted ChoiDujourNX by clicking the reboot option at the end of the install the Nintendo logo came up and it booted right into the sysnand v6.0.1. The prevent fuse burning option was enabled and I double checked everything before the install. I did not have the SXOS autoRCM enabled as I thought ChoiDujourNX would do that with the option selected.
My question is if the sysnand is still on v6.0.1 why would fuses get blown? How would the sysnand know that emunand is running at v8.0.1?
I have two historical 29.1G nand backups, are these backups useless now?
Also is there an option to check the number of fuses that I have blown in any of the SXOS tools?
Thanks much!
My question is if the sysnand is still on v6.0.1 why would fuses get blown? How would the sysnand know that emunand is running at v8.0.1?
I have two historical 29.1G nand backups, are these backups useless now?
Also is there an option to check the number of fuses that I have blown in any of the SXOS tools?
Thanks much!