Quote from: satscraper on Today at 04:25:24 PM

Quote from: foundationdvcs on Today at 03:17:51 PM

Fix is here for you.

https://docs.foundation.xyz/firmware-update-fix/

Thanks, I did it. Everything vent like a charm and my Passport 2 is on the latest 2.3.5. ^{Good that I was not hasty with the update and discovered from foundationdvcs that the problem was buried into version 2.3.2}.

May I ask ^{just of my curiosity} what could do in this case those users who have experienced frozen device . Instruction ^{you have referred to}says users should install developer key preliminary to avoid freeze but they will not be able to this if their devices are already stuck. Is there any workaround for such case?

We had an obscure bug that we missed when QAing v2.3.2. Essentially all of the developers and team who QAs Passport has developer pubkeys installed so we can install internal betas and public betas. The bug checked to see if there was a developer pubkey in the slot in the secure element – if the slot was empty, the firmware update froze.

We all missed the bug, as well as all external beta testers too, since to test the beta you needed to have the developer pubkey added!

The firmware update process didn't care what pubkey was in the slot, only that the slot was not empty. If it was empty it got stuck at 98%.

Was very hard to reproduce this, but once we did we quickly understood what happened and fixed it. Sincere apologies for the inconvenience.