View Single Post
Old 12-08-2019, 01:47 PM   #5
minigendo
Junior Member
minigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolateminigendo is generous with chocolate
 
Posts: 6
Karma: 33914
Join Date: Dec 2019
Device: Kindle 2
I rooted the device, and reset the time as outlined in your link.

As I expected, synching and registration began to work again afterwards.
So, success!

I also took the opportunity to look at the /usr/sbin/updatetime

For the K2i, it seems that it does not use the time reported by the cell network, or an ntp server. Instead it runs
nc kindle-time.amazon.com 80
passes it a header
and then greps a time value out of the returned value.

This gets passed to /usr/sbin/setdate
which runs a bit of validation before using date and hwclock to set the new time.

All of which is to say, it seems that either kindle-time.amazon.com is currently down, or something about it has changed such that it requires ssl, which won't work if the clocks wrong because of the valid from date they've put on the latest certificate.

To summarize, at the moment, any action which resets the clock of a k2i will also disable the Kindle's ability to communicate securely with Amazon. This in turn means no sync-ing, and no registration.
Assuming no other issues, manually resetting the clock will restore these functions.

My thanks again for your help.
minigendo is offline   Reply With Quote