View Single Post
Old 07-16-2018, 11:19 AM   #10
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 encol View Post
adb shell
su
<commands>
Quote:
Originally Posted by SKK View Post
Thanks! It worked perfectly.
Nice.
A firmware version independent way to put our signature certificate (jail break) on those devices and firmware versions that are supporting ADB.
(Not all are.)

The "Cliff's Notes" version:
Code:
{whatever it takes to get the device into ADB (either main or diags) }
adb shell
su
cp -a /mnt/us/pubdevkey01.pem /etc/uks
{done}
NOTE: Since this often depends on some low-level code that is only installed at the factory (is not included in the Amazon image update files) it probably depends on ship date and the source (country) of the Kindle.

All we need is for someone with the time (and Kindles) to research the limitations.

Last edited by knc1; 07-16-2018 at 11:24 AM.
knc1 is offline   Reply With Quote