MobileRead Forums - View Single Post - PW3

knc1 · 08-21-2015, 09:59 AM

Some of us have a tendency to keep anything binary that passes by our way.

A possible note of interest for the future:
For the KT2, PW3 and KV -
The complete, initial, factory install of "main" bootloader, kernel, and filesystem is safely tucked away on a private network server (at least one, probably two).

I (we) don't yet know if the "downgrade attack" protection applies to installing the **initial** factory update package.
Something that is planned to be tested in the near future (RSN tm).

We have to thank Lab126 for shipping those to us.

Edit:
A note for anyone trying to reformat the FAT32 user storage partition (KT2, PW3, KV) -
It uses a 8192 byte block size, not 512 byte.
That probably has to do with eMMC erase block alignment.
And the cluster size is 16 -
I.E: This FAT32 storage only assigns/frees clusters sized for a pair of (4096) erase blocks.

08-21-2015, 09:59 AM	#11
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Some of us have a tendency to keep anything binary that passes by our way. A possible note of interest for the future: For the KT2, PW3 and KV - The complete, initial, factory install of "main" bootloader, kernel, and filesystem is safely tucked away on a private network server (at least one, probably two). I (we) don't yet know if the "downgrade attack" protection applies to installing the initial factory update package. Something that is planned to be tested in the near future (RSN tm). We have to thank Lab126 for shipping those to us. Edit: A note for anyone trying to reformat the FAT32 user storage partition (KT2, PW3, KV) - It uses a 8192 byte block size, not 512 byte. That probably has to do with eMMC erase block alignment. And the cluster size is 16 - I.E: This FAT32 storage only assigns/frees clusters sized for a pair of (4096) erase blocks. Last edited by knc1; 08-21-2015 at 10:14 AM.