Hacking Switch blue screen after restoring NAND

[bobbio]

I restored my Switch to a NAND backup I made prior to using any custom firmware using Hekate, and now it boots into a blue screen, both CFW and stock. Luckily, I tried out that new sd card emunand thing, so I can boot through that, but I feel that's not a very solid solution. I was on 6.1.0 while my NAND backup was on 5.1.0 I believe, but I updated with choidujournx. I'm currently running a restore again with the same NAND backup, as it's the only one I have. Any help would be greatly appreciated.

 

[The Real Jdbye]

I restored my Switch to a NAND backup I made prior to using any custom firmware using Hekate, and now it boots into a blue screen, both CFW and stock. Luckily, I tried out that new sd card emunand thing, so I can boot through that, but I feel that's not a very solid solution. I was on 6.1.0 while my NAND backup was on 5.1.0 I believe, but I updated with choidujournx. I'm currently running a restore again with the same NAND backup, as it's the only one I have. Any help would be greatly appreciated.

If you booted 6.0+ OFW then it would burn your fuses even if you updated with ChoiDujourNX.

 

[bobbio]

If you booted 6.0+ OFW then it would burn your fuses even if you updated with ChoiDujourNX.

oof that was not made clear to me. Is there someway to update it without actually booting into it?

 

[Shift-X]

It's possible to boot OFW via Hekate though. Please current me if I'm wrong but doesn't RCM bypass e-fuse check thus allowing you to retain lower firmware e-fuse count? So if the OP loaded OFW via Hekate then technically, the system shouldn't burn any e-fuse.

 

[XaneTenshi]

oof that was not made clear to me. Is there someway to update it without actually booting into it?

ChoiDujorNX enables AutoRCM by default, so you shouldn't even be able to load OFW (outside of the stock setting in hekate, which is still SUPPOSED to skip the fuse check). So I don't get this answer unless something changed in 6.x firmware to possibly circumvent this.

I have another theory though; When you restored your nand, did you restore both the rawnand.bin AND the boot0/1 files?

It's possible to boot OFW via Hekate though. Please current me if I'm wrong but doesn't RCM bypass e-fuse check thus allowing you to retain lower firmware e-fuse count? So if the OP loaded OFW via Hekate then technically, the system shouldn't burn any e-fuse.

It's not, per say, AutoRCM that does it, but the custom bootloader itself. AutoRCM just prevents the console from booting normally and allows you to enter RCM automatically. Otherwise, you are correct. I don't get why his fuses would have been burned either.

 

[bobbio]

ChoiDujorNX enables AutoRCM by default, so you shouldn't even be able to load OFW (outside of the stock setting in hekate, which is still SUPPOSED to skip the fuse check). So I don't get this answer unless something changed in 6.x firmware to possibly circumvent this.

I have another theory though; When you restored your nand, did you restore both the rawnand.bin AND the boot0/1 files?

It's not just OFW, I can't boot into CFW either. I haven't tried booting from Hekate yet though, still restoring the NAND a second time.
I've restored rawnand.bin alone, but I do have a boot0/1 backup from before any tinkering.

 

[XaneTenshi]

It's not just OFW, I can't boot into CFW either. I haven't tried booting from Hekate yet though, still restoring the NAND a second time.
I've restored rawnand.bin alone, but I do have a boot0/1 backup from before any tinkering.

Aha! Okay, I thought as much. Just restoring the Nand by itself isn't enough. Data is written to the boot files on each boot, so you need to restore the boot files that you had at the time you took a backup of your nand (which luckily it sounds like you have.) Try restoring them aswell.

 

[bobbio]

Aha! Okay, I thought as much. Just restoring the Nand by itself isn't enough. Data is written to the boot files on each boot, so you need to restore the boot files that you had at the time you took a backup of your nand (which luckily it sounds like you have.) Try restoring them aswell.

Worked like a charm!!! You're a lifesaver!

 

[Quagmiire]

I'm able to boot atmostphere CFW utilizing the 6.2 method but my OFW firmware goes straight to the blue screen. Is there a way to restore the OFW utilizing the CFW?

 

[Agent Moose]

I am so glad I read this. thank you for the information because I wouldn't of known. I will keep this for future knowledge.