View Single Post
Old 03-18-2023, 12:39 PM   #15
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 875
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
Quote:
Originally Posted by NiLuJe View Post
I'm not in a position to check and/or rebuild anything at the moment; but, as a rule, if the snapshot's thread timestamp at the bottom predates a FW release date, the hotfix will obviously not work .

On the upside, you don't need to run the hotfix at all, just reboot a couple of times.
My recollection is that the latest firmware release relocated the keystore and as such would require changes to the code to recover from an update of the firmware to that release. Unfortunately I don't recall what level incorporated that change, so I am unsure if he is being bit by it or not. I hope that you are correct and that the bridge code can recover things for him with a few reboots.

Dave

PS: from the Open Sesame Thread:

WARNING: FW >= 5.15.1.1 INTRODUCED A BREAKING CHANGE. DO NOT UPDATE!

Last edited by dhdurgee; 03-19-2023 at 06:49 PM.
dhdurgee is offline   Reply With Quote