That was the unintended bug introduced in 2.3.2, which is also still present in 2.3.4. The device is looking for a key to be present in the developer slot. Most users do not have this present, causing the freeze.
> nope, user clearly said that he was trying to update to 2.3.5 but his device has stuck, so problem do persists when updated to 2.3.5.
That's right, he is trying to update to 2.3.5 from his current version, but failing. This user is not currently running 2.3.5. Once they carry out the recovery steps correctly and successfully install 2.3.5, the issue does not persist and subsequent updates can be applied using the typical method.