View Single Post
Old 07-07-2016, 11:42 AM   #31
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 knc1 View Post
And would probably explain why the problem is hard to find.
Developers rarely use Special Offers enabled devices for development and testing.

Also, I suspect geekmaster's speculation that the internal control variables moved or changed format between PW-3 firmware versions (maybe in preparation for the White PW-3 release).

Hmm...
We probably need a "White PW-3" factory initial update image (I already have a place in the "credits" for that person).
Ah, so, the light dawns.

These 'Recovery' format packages are not signed.
Their components are signed, but the overall package is not.

If we find a 'general purpose' (handles all internal data formats) kernel/initramfs image (I.E: u-image) -
We can re-package the 'Recovery' format packages with our choice of (Amazon signed) components.

Problem solved if so (or as Branch Delay liked to say: "Game Over").
knc1 is offline   Reply With Quote