From other user experiences here, seemsthe solution is to downgrade the firmware to an older version and then try again to update to 1.6.2.