hello ilies.chergui,
yes, please contact the NVIDIA Customer Care team for the RMA process.
I have more details regarding to the failure.
it’s bootrom always tries to verify the PKC hash first to communicate with the board.
due to the fuse is actually PKC hash, which is calculated based on a given PKC key.
so, the board is bricked, unless you can find a PKC key which has an all-zero PKC hash.
to summarize the status of SecureBoot package,
for l4t-r32.4.3, it’s comment #25 to have workaround to enable secureBoot by programming all fuse at once.
for l4t-r32.5, the fixes of fusing error has included, it’s suggest moving to the latest JetPack release to enable secureBoot.