Quote:
Originally Posted by jesse
I've been focused elsewhere (crosscompiler).
Did you modify /usr/java/lib/font.properties or did you just drop new fonts into /usr/java/lib/ with the same names as existing fonts?
Which did you replace?
|
Just bricked my Kindle 2
here's how:
1) created subfolder fonts subfolder under system folder on the Kindle drive and copied unicode fonts there.
2) /usr/java/lib/font.properties (replaced font file names and added appendedfontpath=/mnt/us/system/fonts)
3) copied edited file to Kindle drive along with the update that would copy it over the original file
4) installed the update
Unfortunately for me I made a typo in the appendedfontpath value so when Kindle tried to load the fonts it fails and screen goes dark (just about the time boot progress bar gets to letter "n" in the word amazon)
USB drive still mounts though. I put an update that would revert /usr/java/lib/font.properties to the origianl state and tried forcing the update blindly (pressing menu-down-down-down-click-menu-down-down-click-click). Nothing happens though. I guess that the app that is supposed to receive keyboard input never starts because of the font issue.
Tried waiting for 10 minutes until it would fall asleep and install the update automatically and then reboot. But I guess that it only autoinstalls updates that are download from Whispernet.
Turning it on and off as well and hard reset still work.
I guess it's officially bricked now unless someone can point me to a way to forcing it to install the update package that is there on the USB drive right after it starts up.
I knew what I was risking when I started messing with it so I don't blame anyone except myself.