View Single Post
Old 12-13-2013, 08:09 AM   #2
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
They are two ways of exploiting the same (unintended) feature of the Amazon firmware.

Since you have KUAL installed, use the KUAL version of the BackdoorLock (which gives you buttons to manage it).

Never, ever, contact Amazon again - not even on pain of death?
Install the KUAL firewall with BBB (Block Big Brother) enabled (the default).

Both of the above KUAL add-ins have buttons to allow you to change your mind in the future.

With the BBB filter active, your Kindle can no longer reach the Amazon servers to set its internal time.

Have a solution for that also:
Install the KUAL ntpdate add-in.
Allows the internal date/time to be set from public network time sources.
Your choice of sources, but the defaults should work anywhere in the world.

With the BBB filter active, your Kindle can not "test" its Wifi connection against the Amazon servers.
Search this forum for information on the "No Network Probe" flag file (I have forgotten its specific name).

What you end up with after doing the above is a device that behaves as if **YOU** own it, not as if Amazon still owns it.
Sorry Amazon.
knc1 is offline   Reply With Quote