View Single Post
Old 04-28-2017, 08:22 AM   #34
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 gabbia View Post
Thanks very much!
A further issue: if i were to give some things a try and the device "bricked", would i usually be able to bring it back to life?
With only a few exceptions, nothing except the update_*.bin packages are model number sensitive.
And that is only the packaging.

The few things that are firmware version specific will either work or not work.

Nothing, except the system backup routines (which we no longer use) are sensitive to the memory layout.
Well, except the one I am working on now, that one determines the memory layout so that it will always work.

Plus, with serial port access you have easy access to booting the device into the alternate operating system installation.
knc1 is offline   Reply With Quote