Does FW 17 work? Stuck after Nintendo Logo

[hanswurst31]

Had to rebuild nand es previous emmc was faulty. replaced emmc and rebuild nand as always but the mariko stucks at nintendo logo. could be that something else is broken. could you please check if prodinfogen does work with fw 17? thx

[Masamune3210]

Will likely need a different solution, if one exists. 17.0.0 broke PRODINFO blocking due to the firmware now explicitly checking for the certs iirc, so if you don't have yours, you might be in a bit of a pickle

[laotoulyh]

It is an EMMCHACCGEN problem. There is a problem with the 120SAVE file generated. As long as you use the new version of ATMOSHPHERE to enter OFW once you can repair it.

[Masamune3210]

That has nothing to do with 17.0.0's inability to handle PRODINFO modifications.

[hanswurst31]

It is an EMMCHACCGEN problem. There is a problem with the 120SAVE file generated. As long as you use the new version of ATMOSHPHERE to enter OFW once you can repair it.

i have another switch here which failed an update and my review attamts with a working prod_info led also to stuck after nintendo logo. could you please explain more or link me to a thread where i can read? thx

[Masamune3210]

What they are talking about has nothing to do with Prodinfo. I'm not entirely sure why they even commented it. The issue they are talking about relates to a change in how one of the system saves is generated, a change in how the system uses said save, and a issue that comes up if the system has ever been wiped by something other than ninty's official firmware method.

The issue that is stopping Prodinfo modifications from being allowed to boot is caused by 17.0.0 adding checks for the contents of the Prodinfo partition, specifically the cert files iirc