I have used a video recording of my screen, which I go back and single-step to read the momentary screen that quickly flashed by. These days, you may be able to use a cellphone with camera to record that video, but you may need a magnifying glass between the camera and kindle screen to get a good closeup on the part of the screen with the error code.

I have used a video recording of my screen, which I go back and single-step to read the momentary screen that quickly flashed by. These days, you may be able to use a cellphone with camera to record that video, but you may need a magnifying glass between the camera and kindle screen to get a good closeup on the part of the screen with the error code.

The problem is that there is no reflesh between both errors, so both screens are shown at the same time in the display, so recording a video does not solve the problem.

The problem is that there is no reflesh between both errors, so both screens are shown at the same time in the display, so recording a video does not solve the problem.

If the screen changes too quickly, the eink drivers may not finish updating all the pixels. Seeing a combination of two messages could be an eink artifact (the first screen was not displayed long enough to finish drawing all the pixels).

... the obfuscation has, of course, changed once again. So Collections Manager won't work, and neither will JBPatch. Don't even try.

I'm sick and tired of this. Every new update brings more horrid obfuscation, and results in a repetition of the same stupid, boring, yet tedious, procedure: find out which classes/methods have been renamed to what. What a wonderful job.