Hi folks,
I have tried to create some permanent method of installing customized fonts, with help the the Unitversal Reflasher.
Here is the Usage:
a. Install
1. In your Reader's internal memory disk, create the /FONT folder, as described in the begining of this thread
2. In your Reader's internal memory disk, create a /scripts folder, and unzip the scripts.zip into it. After that, you should have a tinyhttp_custom.sh file in that folder
3. extract the ReplaceTinyhttp.sh.zip to a SD card
4. follow the Universal Flasher's readme.txt to create and flash the new image (i.e. key 5. followed by key 6.)
After reader reboot, the new fonts in /FONT folder will be activated.
b. To revert back to original fonts, simply rename the /scripts/tinyhttp_custom.sh to a /scripts/tinyhttp_custom.sh.dis and reboot your reader (shutdown and power on again).
c. To change the fonts, you need to do b. to saftly umount the /FONT. Then you can copy the new fonts into the /FONT folder, and change back the /scripts/tinyhttp_custom.sh name. After reboot, the new fonts will be activated.
I have attached the packages here:
ReplaceTinyhttp.sh.zip: Basically a Universal Flasher, that will install the modified tinyhttp.sh
scripts.zip: the customized script to be called by the new tinyhtpp.sh
NOTE: changing tinyhttp.sh is risky, that may cause your unit to a deep brick if anything went wrong.
When that happened, the USB might not enumerate.
To recover from such condition, please follow "Recovering From Catastrophic Failure (Unbricking)" in this post:
https://wiki.mobileread.com/wiki/Sony...8Unbricking.29
(I have run into this 3 times when developing this hack).
This hack bascially installed a "hook" into the tinyhttp.sh. That would allow user script to run before the tinyhttp application (i.e. the main UI of the reader software).
To install a user script, you just need to ensure the script is stored at "scripts" folder in the reader's internal disk.
The name of the script need to be exactly "tinyhttp_custom.sh"
When this script runs, tinyhttp.sh mounted the internal disk at /tmp/Data, so your script can use that path to access the files in that disk.
My experiment shows that "/Data" is not mounted outside the tinyhttp application. So /tmp/Data would be handy to access the user files.
Comments and feedbacks are welcome!