Update 14.x.x -> 16.0.3 = OFW Black Screen, Rebuilt sys/emuMMC both work. Fuses?

[Loafdude]

This is my situation...

• Unpatched V1 switch with Trinket Mod.
• I wished to update
• I booted into OFW and updated 14.x.x -> 16.0.3 from Nintendo servers
• Update proceeded and rebooted console. Upon reboot I get black screen.
• sysMMC and emuMMC boot and work fine.
• Formatting new SD card and rebuilding emuMMC works fine.
• OFW still blackscreens
• Fuses show 16 which is 14.x.x (16.0.3 fuses should be 18)
• Would unblown fuses prevent 16.0.3 from booting?
  • If so how can I blow fuses if OFW is not booting?
  • I tried running FW update on sysMMC but it does not blow fuses.
  • If not, any thoughts why OFW now blackscreens or how I could recover this brick?

Any insights would be appreciated!
Thanks!

 

[leerz]

it will blow when you choose reboot to OFW or boot without a payload.

update to latest hekate, ams, sigs, and use Daybreak instead of using 910do server.

 

[Loafdude]

• I'm running latest Hekate, sigs etc. (Using HATS pack atm)
• sysMMC/emuMMC are working fine so the actual data on MMC is good
• Launching OFW from the trinket payload (no SD) or Hekate (with SD) results in blackscreen.
• Re-installing the fw update using Daybreak under either sysMMC/emuMMC works but no fuses are blown and OFW still does not boot
• It does not appear to be blowing fuses when booting OFW then crashes?
• Yes I'm dumb for updating from Nintendo's server

Any other thoughts?

 

[jkyoho]

DUMP KEY, use emmchaccgen rebuild boot.bis boot0 and boot1 from latest OFW FW, restore boot.bis via TegraExplorer systemrestore.ve. boot0/1 flash via hekate.
check guide like this

 

[Hayato213]

This is my situation...

• Unpatched V1 switch with Trinket Mod.
• I wished to update
• I booted into OFW and updated 14.x.x -> 16.0.3 from Nintendo servers
• Update proceeded and rebooted console. Upon reboot I get black screen.
• sysMMC and emuMMC boot and work fine.
• Formatting new SD card and rebuilding emuMMC works fine.
• OFW still blackscreens
• Fuses show 16 which is 14.x.x (16.0.3 fuses should be 18)
• Would unblown fuses prevent 16.0.3 from booting?
  • If so how can I blow fuses if OFW is not booting?
  • I tried running FW update on sysMMC but it does not blow fuses.
  • If not, any thoughts why OFW now blackscreens or how I could recover this brick?

Any insights would be appreciated!
Thanks!

No NAND backup?

 

[Loafdude]

No NAND backup?

I do but it would be from a previous firmware.
An old firmware won't boot with new fuses if I understand correctly.

 

[Hayato213]

I do but it would be from a previous firmware.
An old firmware won't boot with new fuses if I understand correctly.

You can backup current firmware and then restore the backup see if it boot.

 

[Jayro]

Saving excuses on the switch is pointless. Just blow them already.

 

[Loafdude]

Saving excuses on the switch is pointless. Just blow them already.

Yes I agree, but how to blow them from sysMMC or emuMMC?
I am going to try jkyoho's advise this evening.

 

[Loafdude]

As follow up for others who may run into it...

I reflashed Boot1/2 & raw to 14.x.x and it runs. No matter where and how I run the update on OFW it blackscreened after reboot.

Trinket mod always triggers RCM.
Either my payload chain or RCM itself prevented the OFW update from working.
After a natural boot without RCM the fuses are now blown and OFW works.

To natural boot with a trinket mod on your V1 you can disable ChipRCM mode through the trinket menu (Vol+) and it won't exploit automatically.
Use Vol+ during boot to exploit and re-enable ChipRCM mode in the trinket menu

I'm using trinket firmware from github mattytrog/FUSEE_SUITE

Thanks everyone for your help. Much appreciated.