[el-sahef]

When the device is powered back on it starts with the correct page number. Only the cover image is wrong.

When the next archive is automatically started and I quit the application after that (via menu ---> exit) the taskmanager shows no other running instance of pbimageviewer. I hope that I tested this the right way.

The internal SD card works fine, I can do everything without any issues.

I don't think that it is the firmware that damages the internal SD cards but that they are just of very poor quality and fail often after some time.

I have three inkpad 1 devices in total, two working ones and one with some cracks in the touch layer (for parts). Two of them were bought as defective on ebay, one as used but working. Of the two defective ones, the first one just had a completely discharged battery (easy fix) and the other one had a failed internal SD card with corrupted firmware that did not boot anymore and the card did not accept any writes. I could not simply take an image (taken with dd on linux) of a working card with working firmware and transfer it to another card and use that. The firmware image of a card is tied to the card ID and the ID of the card to which you write the image must match the ID of the original card from which the firmware image was taken. As long as firmware image and card ID match you can swap cards between devices. Because I only need two working devices at once I did not care at first as I had two working cards with valid firmware.

Normally this card ID is not changeable by the user because it is also used in some copyright protection schemes, e. g. car navigation map updates, but some older samsung evo SD cards have a bug that allows to change this card ID to any value with a tool you can find on the internet. So I bought a bunch of these cards. They are increasingly hard to find but if you know what to look for and are a little patient you can still get them on ebay.
Last year the next device had the problem that the internal SD card changed to read-only mode (but the firmware on it is still bootable, sounds like your case). I took one of the samsung evo cards, changed the card ID to the same ID as the internal card that changed to read-only mode, put the image from this card with dd on the samsung evo card and swapped the cards. No more problems, everything working again.

The two internal cards that failed were 4 GB cards and had no brand name on them. The third one that is still working is also 4 GB and has the brand name "Gigastone" on it. If this fails too it is no problem as I have bought enough samsung evo cards with changeable card ID.

I suspect that your internal card failed just because there were many writes to it when you updated the firmware. I never use the internal SD card to store anything, just external cards and I still had one of the internal SD cards fail. So if you use the internal storage to store anything, the internal card will probably fail even faster.