View Single Post
Old 07-12-2017, 10:24 AM   #1432
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by dhdurgee View Post
Hmm. Would it be possible to relabel or rebundle the downgrade package to be acceptable to the FB03 flagged units? Obviously I have no idea what that would involve, but it might provide a route to JB the newer units.

Dave
Are the first four characters of the package included in the signed checksum?
If not, just hex edit them to one of the other package types.

The only change I have seen (so far) is that they took 'FB03' out of the acceptable package types case statement.
That is the package type used by the initial (load to anything) factory firmware packages.

Hmm...
Just hexedit the '3' to a '2' (or something else) and see if the signature check still passes.

Last edited by knc1; 07-12-2017 at 10:26 AM.
knc1 is offline   Reply With Quote