Hacking rebuild nand(lost backup)

[stefanbk]

hey guys,
I was away for a long time and don't really know what's happened in the meantime.
My current situation is that I have switch on 9.0, lost my old 2.3 backup but my fuse count is still 2.
Can I do something like "rebuild nand" to get a clean 2.3 version again?

What's your advice?
Should I even bother to keep my fuses?
I don't even have emunand too, wasn't there at the time.

 

[thesjaakspoiler]

I've updated every time the geniuses from Hekate and Atmosphere throw out an update.
Why even bother staying on a lower firmware?
There is no advantage and also no outlook that someone will find some ultimate bug that can do a cold boot into CFW.
I think nobody is looking for that anymore.

 

[Draxzelex]

hey guys,
I was away for a long time and don't really know what's happened in the meantime.
My current situation is that I have switch on 9.0, lost my old 2.3 backup but my fuse count is still 2.
Can I do something like "rebuild nand" to get a clean 2.3 version again?

What's your advice?
Should I even bother to keep my fuses?
I don't even have emunand too, wasn't there at the time.

There is no advantage to burning fuses so I would still try to preserve them especially since there are many ways of updating without burning fuses.

 

[stefanbk]

There is no advantage to burning fuses so I would still try to preserve them especially since there are many ways of updating without burning fuses.

thx got it

 

[Hayato213]

You could try to rebuild your NAND down to 2.3 but you should make a backup of your current NAND and keep autoRCM on. I don't know if you can go online with rebuilded 2.3 NAND, you would get a ban if it doesn't match the data that is on Nintendo server.

 

[Lacius]

There's no reason to burn your fuses, but there's also no reason to rebuild a 2.3 sysMMC or downgrade to 2.3. Just make sure you have an eMMC backup (from any system version) on hand in case of a brick.

If, in the future, you want to downgrade to 2.3, use Daybreak to do so.