View Single Post
Old 02-28-2016, 11:00 AM   #15
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by knc1 View Post
Actually, I did not see that question in your post.
Answer: No

You will have to re-apply the fake registration.
Same-Same as always for anything that touches system files.

Hint:
It is an upate_*.bin package == almost always touches system files.
And LibrarianSync is distributed via an update_*.bin as well, despite being nothing but a KUAL extension.
All this hack touches is the registration file in /var/local


Now, if you connect to WiFi in order to update, your Kindle will ping Amazon's servers and undo the forged registration -- but that is a different story.
eschwartz is offline   Reply With Quote