well, right, you can't access a console and dump...
btw, I don't think the rsa key is used at all for firmware upgrade... so you should be able to access recovery mode with he proper sdrescue package, if the rsa key was the problem

well, right, you can't access a console and dump...
btw, I don't think the rsa key is used at all for firmware upgrade... so you should be able to access recovery mode with he proper sdrescue package, if the rsa key was the problem

my problem, I m trying to get a dump of the partitions, I am at the beginning of the beginning... your flashing tools based on XXX update.package won't work for me as I believe the RSA key is different. I think the RSA key is somewhere stored around the beginning of the bootloader (I looked at your scripts to extract the .packages) I need a dump before.. so I am back to the beginning

If you have the Western or Japanese model of PRS-T1, your encryption keys are exactly the same as everyone else's. If you have a PRS-G1 or the Russian model of PRS-T1, the SD card update will not work for you, and the encryption method of the update packages is quite different. Beside the fact that they are signed by a private key.

One more thing to remember. If you have an update image on the SD card, it has priority over the update package in the internal memory. To get the "serial gadget" login you need to copy the XXX-Updater.package from the login_update folder in this archive into the root of the "internal memory" ("drive" READER).

If you have the Western or Japanese model of PRS-T1, your encryption keys are exactly the same as everyone else's. If you have a PRS-G1 or the Russian model of PRS-T1, the SD card update will not work for you, and the encryption method of the update packages is quite different. Beside the fact that they are signed by a private key.

One more thing to remember. If you have an update image on the SD card, it has priority over the update package in the internal memory. To get the "serial gadget" login you need to copy the XXX-Updater.package from the login_update folder in this archive into the root of the "internal memory" ("drive" READER).

the modified sdrescue image I have posted above should boots in recovery mode (I have not tested it)

I need to copy system fonts partition to cramfsck it, substitute the system font (the one that's responsible for book titles, bookmarks, file names etc. I don't know name of the font ) with my chosen font, mkcramfs it and write back modified fonts partition.

I don't understand why I need the steps to connect the reader in recovery mode to PC, why I don't use the below command with terminal emulator on my PRS T1?

Please, explain in detail I'm having hard time to understand this stuff.

# make a backup of fonts partition
dd if=/dev/mmcblk2p5 of=/mnt/sd/mmcblk2p5_fonts.img

I've made the following: Entered into recovery mode by using the app "@Test Mode"
Then, started Terminal emulator and typed the command

dd if=/dev/mmcblk2p5 of=/mnt/sd/mmcblk2p5_fonts.img

the result was

dev/mmcblk2p5: cannot open for read: No such file or directory

Any help much appreciated.

Without understanding what exactly you're trying to do (weren't there some other suggestions to use a mount -bind method to overwrite the system fonts?), the full name of the mmcblk2p5 file on my T1 is /dev/block/mmcblk2p5. Also, shouldn't your output file start with /mnt/sdcard?

Without understanding what exactly you're trying to do (weren't there some other suggestions to use a mount -bind method to overwrite the system fonts?), the full name of the mmcblk2p5 file on my T1 is /dev/block/mmcblk2p5. Also, shouldn't your output file start with /mnt/sdcard?

Cheers,
Simon.

Hi Simon,

My goal is to make PRS T1 show Georgian Unicode font correctly in book titles, bookmarks etc., now it shows ???????????. To achive this I've decided I need to substitute one of the systems/fonts/........ttf/otf (I'm not sure which one yet) with DejaVuSansCondensed.ttf

Please, correct my If I'm wrong.

I read there that mount -bind method to overwrite the system is not reliable method, the post said it need some apk to be installed to remount every time a device is restarted. That's why I've decided to go with modifying cramfs file for system fonts.

I figured out from previous post mmcblk2p5 is fonts cramfs image, correct me if I'm worng.

So I've copied that command above from previous post to transfer mmcblk2p5 (systems fonts folder in my understanding) to external microsd so as to transfer it later to PC modify it and flash it back. That's it.

My goal is to make PRS T1 show Georgian Unicode font correctly in book titles, bookmarks etc., now it shows ???????????. To achive this I've decided I need to substitute one of the systems/fonts/........ttf/otf (I'm not sure which one yet) with DejaVuSansCondensed.ttf

Please, correct my If I'm wrong.

I read there that mount -bind method to overwrite the system is not reliable method, the post said it need some apk to be installed to remount every time a device is restarted. That's why I've decided to go with modifying cramfs file for system fonts.

I've not looked at using mount -bind, so can't comment on how hard/easy/reliable that method is.

One question - the Deva Vu fonts aren't exactly small. Have you verified that there's enough room for a larger cramfs image on the T1 that includes that font?

Quote:

I figured out from previous post mmcblk2p5 is fonts cramfs image, correct me if I'm worng.

So I've copied that command above from previous post to transfer mmcblk2p5 (systems fonts folder in my understanding) to external microsd so as to transfer it later to PC modify it and flash it back. That's it.

And I'm stuck right at the start.

The info for the location of the cramfs image is right there on the T1. If you use the "mount" command (with adb, terminal, etc), you'll see:

/dev/block/mmcblk2p5 /ebook/fonts cramfs ro,relatime 0 0

Did you try using the correct paths in your dd command as I suggested in my previous post in this thread?

It really depends on how much space is available in the internal memory on the T1. If there's a gap after the end of the mmcblk2p5 partition before the next partition starts, you'll be OK. I don't know though how to check that, although this post from uboot seems to indicate there's no spare space.