Upgrading OFW with Daybreak

[AlhazenTheMad]

Quick noob question, but will doing this burn fuses?

 

[Draxzelex]

Quick noob question, but will doing this burn fuses?

The short answer is it depends. Fuses are burnt by the console's stock bootloader when it detects a firmware higher than the fuse count. So the only way to avoid burning fuses is to use a custom bootloader such as Hekate or fusee that ignore the fuse check. The problem is ensuring that we can use Hekate or fusee to boot the console every time otherwise we risk burning fuses if the console ever boots normally even once. That's where AutoRCM comes into play; because it 'bricks' the console, it will always boot into RCM and in RCM, we can use a custom bootloader to bypass the fuse check.

The other issue is keeping AutoRCM. Since AutoRCM is installed to BOOT0 and BOOT0 is changed during firmware updates, normal firmware updates will always remove AutoRCM. Therefore we need specialized tools that will enable AutoRCM after a system update such as ChoiDujourNX or Daybreak. Of course, this is only an option in those tools so if you disable it, you will burn fuses even if you use Daybreak.

 

[dehydrated_lemur]

The short answer is it depends. Fuses are burnt by the console's stock bootloader when it detects a firmware higher than the fuse count. So the only way to avoid burning fuses is to use a custom bootloader such as Hekate or fusee that ignore the fuse check. The problem is ensuring that we can use Hekate or fusee to boot the console every time otherwise we risk burning fuses if the console ever boots normally even once. That's where AutoRCM comes into play; because it 'bricks' the console, it will always boot into RCM and in RCM, we can use a custom bootloader to bypass the fuse check.

The other issue is keeping AutoRCM. Since AutoRCM is installed to BOOT0 and BOOT0 is changed during firmware updates, normal firmware updates will always remove AutoRCM. Therefore we need specialized tools that will enable AutoRCM after a system update such as ChoiDujourNX or Daybreak. Of course, this is only an option in those tools so if you disable it, you will burn fuses even if you use Daybreak.

I have a question regarding this. I have a hwfly console. Say I updated using daybreak in sysnand. it was successful. now I reboot my console. it automatically boots into Hekate. from Hekate I select reboot to get into OFW, not OFW CFW. when it boots OFW does that burn fuses? I want to play online with my carts.

 

[kidkat210]

I have a question regarding this. I have a hwfly console. Say I updated using daybreak in sysnand. it was successful. now I reboot my console. it automatically boots into Hekate. from Hekate I select reboot to get into OFW, not OFW CFW. when it boots OFW does that burn fuses? I want to play online with my carts.

The only time efuses are burnt is after updating sysnand firmware and booting sysnand. So yes it does. But unless you were planning on downgrading your firmware (for whatever God forsaken reason) efuses don't matter. The efuses just prevent the system from booting (without cfw) when the burnt efuse count isn't the same as the installed firmware. So bootloaders like fusee.bin and helate bypass the efuse check. But again burning efuses doesn't matter anymore since the main reason people kept a low efuse count was so they could downgrade and use a cold boot method, but a cold boot method never showed up. So its pointless to keep a low efuse count

 

[dehydrated_lemur]

this makes sense. thanks