MobileRead Forums - View Single Post - PRS+: Enhanced firmware for Sony Reader, Folders, Games & more

Analogus · 05-21-2011, 08:58 AM

Hm, I'm a bit ashamed... the reason is my inquisitiveness and curiosity

Long story short:

Tried serveral times to upgrade/downgrade to/from newest Sony firmare as you know

Flashing with BORODAS packages worked still fine in both directions

What I do like ist to have my own fonts all over the reader, even in TXT and RTF files. Boroda doesn'n offer that

Ergo: Tried to manage it with my own hands. Read about cramfs. Extracted the original firmware offered by boroda --> modified the adobe programm with an hexeditor (found on the internet) & changed 1 font (I did it the right way including changing internal fontnames) --> compiled with cramfs --> flashed with borodas flasher.

Worked fine! Did it several times to optimize fonts and played around with changing font sizes. At the final flash something went wrong. I used a former working image (not 100% shure about that), but this time it leads into the mentioned boot loop.

A.

Edit: maybe I made a mistake and took the wrong image for extracting for the final task. For example one image (can't remember which one) has slightly other fontnames mentioned in one of the xml-files (something like XYwin95...ttf versus XY...ttf). Maybe I overlooked that.

05-21-2011, 08:58 AM	#2129
Analogus Fanatic Posts: 568 Karma: 2170348 Join Date: Apr 2011 Device: 2x Sony PRS-350; PRS-300 (†), Paperwhite (†), Voyage	Hm, I'm a bit ashamed... the reason is my inquisitiveness and curiosity Long story short: Tried serveral times to upgrade/downgrade to/from newest Sony firmare as you know Flashing with BORODAS packages worked still fine in both directions What I do like ist to have my own fonts all over the reader, even in TXT and RTF files. Boroda doesn'n offer that Ergo: Tried to manage it with my own hands. Read about cramfs. Extracted the original firmware offered by boroda --> modified the adobe programm with an hexeditor (found on the internet) & changed 1 font (I did it the right way including changing internal fontnames) --> compiled with cramfs --> flashed with borodas flasher. Worked fine! Did it several times to optimize fonts and played around with changing font sizes. At the final flash something went wrong. I used a former working image (not 100% shure about that), but this time it leads into the mentioned boot loop. A. Edit: maybe I made a mistake and took the wrong image for extracting for the final task. For example one image (can't remember which one) has slightly other fontnames mentioned in one of the xml-files (something like XYwin95...ttf versus XY...ttf). Maybe I overlooked that. Last edited by Analogus; 05-21-2011 at 09:20 AM.