[geekmaster]

Originally Posted by hostar

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.

Thank you! That looks like something useful to add to my kindle "recovery system".

For people with bricked kindles who are anxiously waiting more progress on these tools, sorry about the delay -- a tiny mistake to my payload while testing new stuff bricked my touch in a way that I have not yet discovered how to repair, despite a lot of time diverted from development to repair attempts. I have also diverted a lot of time to helping others fix their kindles, in PMs and IRC private channel conversations (there has been a very high success rate). Now, if I could just succeed on my own Touch). Time to stop poking around in USB methods and go deeper into serial port recovery like I used the first time. I think the Touch does not work as well in fastboot mode as my K4NT did ("fastboot flash system mmcblk0p1.imf" reports "success" much to quickly, and it does not fix the problem). My soldering iron is warming up now...