First thing I've done when I found browser doesn't work was recovery
of Browser.jar from backup.
After I read your answer (thanks for that), I had an idea.
I checked (almost) all files on Kindle with md5sum,
and did same thing with files in backup.
Now the curious thing: even if I have already replaced the Browser.jar, it's md5 was different from backup!
Also some other files has different md5.
So I replaced the Browser.jar again.
But the browser actually run after correcting file called "internal.conf", where
was on last line:
com.lab126.booklet.a.Y instead of com.lab126.booklet.a.y
So everything is fine now, I'm writing this only because someone might have similar problem in future.
|