MobileRead Forums - View Single Post

readz · 08-27-2026, 02:32 PM

Shortly I got my hands on a Pocketbook Touch HD 2. I was really eager to find out myself how the freeze hack performed on this device.

Clone the card. Apply the Perl script. But the reader stuck. It turns out there were errors on the 3. partition. Exactly this one with the .freezestatus file! So the filesystem was remount read-only and the changes weren't written. When you fix this with

Code:

fsck.ext2

, things will be fine. The Reader boots. I was also able to extend the internal memory to 30GB.

So, no sneaky code changes between Touch and Touch 2!

PS: It may be possible to fix the id without correcting the fs errors. Simply search your current code in the 3. partition image and replace the 4 Byte directly. Remove and replug it. *Test it* (e.g.

Code:

vbl /dev/sdc3 - 0x042400 4l

)

08-27-2026, 02:32 PM	#205
readz Junior Member Posts: 6 Karma: 10 Join Date: Dec 2025 Device: Pocketbook Touch HD	Shortly I got my hands on a Pocketbook Touch HD 2. I was really eager to find out myself how the freeze hack performed on this device. Clone the card. Apply the Perl script. But the reader stuck. It turns out there were errors on the 3. partition. Exactly this one with the .freezestatus file! So the filesystem was remount read-only and the changes weren't written. When you fix this with Code: fsck.ext2 , things will be fine. The Reader boots. I was also able to extend the internal memory to 30GB. So, no sneaky code changes between Touch and Touch 2! PS: It may be possible to fix the id without correcting the fs errors. Simply search your current code in the 3. partition image and replace the 4 Byte directly. Remove and replug it. Test it (e.g. Code: vbl /dev/sdc3 - 0x042400 4l )